5 MCData generic capability requirements common for on-network and off-network

22.2823GPPMission Critical (MC) dataTS

5.1 Introduction

MCData makes frequent use of a set of capabilities and enablers that allows for many end user services to be built on a common foundation. Several generic capabilities are defined for use in the MCData Service. These capabilities can be used on their own to transfer files, messages and other content to individuals and affiliated members of groups or combined with other services, through an application, to provide complete end users services as determined by the authorities implementing the service. The MCData generic capabilities are common for on-network and off-network.

It is not intended to invent new protocols for the MCData Service. Where existing protocols are efficient and sufficient, the service should make use of these protocols.

5.2 SDS feature

5.2.1 General

The SDS feature of the MCData Service could be considered as a basic protocol carrying a limited size, but variable content, payload message. This message could be text or could be marked for extensible purposes including short binary messages for application communication. Messaging could be one-to-one messaging or could be group messaging using groups as specified in MCCoRe.

5.2.2 Requirements

[R-5.2.2-001] The MCData Service shall provide an SDS feature for conveyance of limited size, variable content, messages.

[R-5.2.2-002] The MCData SDS shall provide a group service to affiliated members with policy assertion capabilities (e.g. certain types of message or content may only be relevant to certain members of a group due, for example, to location).

[R-5.2.2-003] The MCData SDS shall provide a one to one service with policy assertion capabilities (e.g. policy to limit certain types of message or content to certain users due, for example, to location or user privilege).

[R-5.2.2-004] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of 8 bit text or [500] characters of 16 bit text or [250] characters of 32 bit text and the necessary character encoding information (for example to identify alphabet used).

[R-5.2.2-005] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of hyperlink or interleaved text and hyperlink(s) to allow subsequent access to linked content (which may be a large file).

[R-5.2.2-006] The MCData SDS shall provide the option to include a content payload of at least [1000] bytes of binary data to be used by a local running application and the necessary addressing detail to identify the intended application.

[R-5.2.2-007] The MCData SDS shall provide a message thread indication so that multiple message flows can be managed independently.

[R-5.2.2-008] When replying to a message on the MCData SDS or sending any message which should be coupled with previously sent or received messages or message flows; the message thread indication shall use the same indication as was used for those previous messages.

[R-5.2.2-009] The MCData SDS shall provide a selectable read receipt indication. When requested, the receiving entity shall provide receipt indication for delivered and read messages as appropriate.

NOTE 1: The read indication will implicitly indicate delivered as well.

[R-5.2.2-010] The MCData SDS shall provide a configurable read receipt indication. When configured, the receiving entity shall provide receipt indication addressed to the application for delivered and read messages as appropriate.

NOTE 2: The read indication will implicitly indicate delivered as well.

[R-5.2.2-011] The MCData SDS shall permit delivery history interrogation for suitably authorized users.

[R-5.2.2-012] The MCData SDS shall provide the option to add a field indicating location of the sending user/UE.

[R-5.2.2-013] The MCData SDS shall allow empty messages including only a field indicating location of the sending user/UE.

5.2.3 Remote Start Requirements Using SDS

[R-5.2.3-001] SDS content received in a UE, addressed to a known local application that is not yet running shall cause the UE to start the local application and pass the content to the application. This could be used to start an application and pass to it the initial data.

[R-5.2.3-002] The MCData SDS shall provide the capability to remotely start a local application (e.g. situational awareness). This may be through specific use of binary payload on theSDS.

5.3 File distribution capability

5.3.1 General

File distribution is a fundamental capability of the MCData Service. File distribution can be used to provide a standalone file transfer capability or can be invoked by a controlling application to support the purpose of the application.

5.3.2 Requirements

[R-5.3.2-001] The MCData Service shall provide a file distribution capability.

[R-5.3.2-002] The MCData file distribution capability shall provide a service to allow a user to send a file to any combination of individual users and/or affiliated groups.

[R-5.3.2-003] The MCData file distribution capability shall provide an option for each recipient to choose to receive the file or not (e.g. by storing the file and sending a link (URL) to all relevant members).

NOTE 1: By using this capability a user can choose when to receive the file.

[R-5.3.2-004] The MCData file distribution capability shall allow a user to reject to receive the file where appropriate.

[R-5.3.2-005] The MCData file distribution capability shall provide a sending user selectable indication for mandatory download so that the UE, for all relevant receiving members, will automatically download the file.

NOTE 2: The mandatory indication provides a system level capability and could be invoked automatically by need of the application or might be provided for selection by the user.

[R-5.3.2-006] The MCData file distribution capability shall provide download complete indications for each recipient successfully downloading the file.

[R-5.3.2-007] The MCData file distribution capability shall allow the sender to select to send the file immediately to all chosen users.

[R-5.3.2-008] The MCData file distribution capability shall make use of available system delivery efficiencies for distribution of common information to users within a specific geographic area and able to receive at the same time.

[R-5.3.2-009] The MCData file distribution capability shall allow a user to cancel distribution of files they have sent, but have not been delivered.

[R-5.3.2-010] The MCData file distribution capability shall allow an authorised user to cancel distribution of files being sent or waiting to be sent.

5.4 Data streaming capability

5.4.1 General

Data streaming is a fundamental capability of the MCData Service. Data streaming can be used to provide a standalone data streaming capability or can be invoked by a controlling application to support the purpose of the application.

5.4.2 Requirements

[R-5.4.2-001] The MCData Service shall provide a data streaming capability.

[R-5.4.2-002] The MCData data streaming capability shall provide an option that allows each recipient to choose to receive the data stream or not (e.g. by sending a link (URL) to all relevant members).

[R-5.4.2-003] The MCData data streaming capability shall allow a user to reject to receive the datastream.

[R-5.4.2-004] The MCData data streaming capability shall provide a sending user selectable indication for automatic reception by the UE.

[R-5.4.2-005] The MCData data streaming capability shall provide start and stop records to the sender for each recipient successfully receiving the data stream.

[R-5.4.2-006] The MCData data streaming capability shall make use of available system delivery efficiencies for streaming of common information to users within the same relevant area and able to receive at the same time.

[R-5.4.2-007] The MCData data streaming capability shall allow a user to cancel streaming of data they have initiated including data remaining buffered in the system waiting to be streamed.

[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being sent and cancel streaming of data remaining buffered in the system waiting to be streamed.

[R-5.4.2-009] The MCData data streaming capability shall provide setup time of:

– Less than 1 second for immediate setup of a data communication.

– Less than 3 second for normal setup of a data communication.

NOTE 1: Setup time of a communication is essential because of their safety related character.

NOTE 2: Communication setup encompasses the value of the elapsed time between the communication establishment request and the indication of successful communication establishment.

5.5 IP connectivity

5.5.1 Service description

IP connectivity can be used for MCData applications that are based on the IP client-server paradigm. The UE can contain a client using a service in the network (e.g. a police officer accessing a server on the police Intranet from his mobile phone). The UE can also contain a server that is accessed by other UEs (e.g. a mobile information display that is controlled by a police officer from his mobile phone). As an UE for MCData application can be an unmanned device, or device without user interface, authorization of IP data transport can be provided remotely by an authorized user for the UE.

5.5.2 Requirements

[R-5.5.2-001] The MCData Service shall enable an MCData user to initiate transport of IP data towards a server in the network or another MCData user.

[R-5.5.2-002] The MCData Service shall enable incoming transport of IP data towards an MCData user, initiated by another MCData user.

[R-5.5.2-003] The MCData Service shall enable an authorized person for an MCData user to authorize initiation of transport of IP data from that MCData user to specific destinations. This authorization may be preconfigured or may be provided by the authorized person when IP data transport to a new destination is initiated. Authorization may be revoked on demand by the authorized person.

[R-5.5.2-004] The MCData Service shall enable a MCData user or authorized person for this MCData user to authorize initiation of incoming transport of IP data from specific other MCData users. This authorization may be preconfigured, or may be provided by the authorized person when IP data transport from a new destination is initiated. Authorization may be revoked on demand by the authorized person.

[R-5.5.2-005] The MCData Service shall support incoming and outgoing IP data transport for a MCData user with a higher per packet priority .

[R-5.5.2-006] The MCData Service shall enable an authorized person to remotely authorize the use of higher per packet priority for a particular MCData user.