This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories:
MCData UE configuration data (see sub-clause A.2);
MCData user profile configuration data (see sub-clause A.3);
MCData related group configuration data (see sub-clause A.4); and
MCData service configuration data (see sub-clause A.5).
For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element.
The columns in the tables have the following meanings:
Reference: the reference of the corresponding requirement in TS 22.282 or TS 22.280 or the corresponding subclause from either the present document or the referenced document.
Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy.
When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used:
"Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column.
"N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column.
Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">"
in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">"
character. Parameters that have one or more ">"
characters are child parameters of the first parameter above them that has one less ">"
character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters.
Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
The general aspects of MC service user profile configuration data are specified in TS 23.280
. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData‑2
Table A.3-1 and Table A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Table A.3-1 and Table A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in Table A.3-1 and Table A.3-3 can be configured offline using the CSC-11 reference point.