This Annex provides information about the static configuration data needed for the support of MC services in the IOPS mode of operation. The configuration data belong to one of the following categories:

• MC service UE configuration data (see subclause A.2);
• MC service user profile configuration data (see subclause A.3);
• MC service group configuration data (see subclause A.4); and
• MC service configuration data (see subclause A.5).

The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MC service UE, MC service group, MC service user and MC service configuration data refers to the information that will be stored against each MC service UE, MC service group, MC service user and MC service. The columns in the Tables have the following meanings:

• Reference: the reference of the corresponding requirement in TS 22.346 and TS 22.280 or the corresponding clause 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 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 MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.

MC service UE configuration data has to be known by an MC service UE after MC service authorization. The CSC-4 reference point, specified in TS 23.280, is used for configuration between the configuration management server and the configuration management client on the MC service UE when the MC service UE is on-network. MC service UE configuration data can be configured offline using the CSC-11 reference point specified in TS 23.280. Within each MC service, the MC service UE configuration data can be the same or different across MC service UEs. The MCPTT UE configuration data specified in Table A.2-1 in TS 23.379 is also used, as needed, in the IOPS mode of operation for the MCPTT service. The MCData UE configuration data specified in Table A.2-1 in TS 23.282 is also used, as needed, in the IOPS mode of operation for the MCData service.

The MC service user profile configuration data is stored in the MC service user database. The configuration management server is used to configure the MC service user profile configuration data to the MC service user database (CSC-13) and MC service UE (CSC-4), as specified in TS 23.280. MC service user profile configuration data can be configured offline using the CSC-11 reference point specified in TS 23.280. For the MCPTT service, the MCPTT user profile configuration data specified in Table A.3-1 in TS 23.379 is also used, as needed, in the IOPS mode of operation, wherein the IOPS MCPTT user identity (IOPS MCPTT ID) can be the MCPTT user identity (MCPTT ID) or a specific ID configured for the IOPS mode of operation. For the MCData service, the MCData user profile configuration data specified in Table A.3-1 in TS 23.282 is also used, as needed, in the IOPS mode of operation, wherein the IOPS MCData user identity (IOPS MCData ID) can be the MCData user identity (MCData ID) or a specific ID configured for the IOPS mode of operation. Table A.3-1 described below contains additional MC service user profile configuration required to support MC services in the IOPS mode of operation.

As specified in TS 23.280, the group configuration data is stored in the group management server. The group management server is used to configure the group configuration data to the MC service UE (CSC-2). The group configuration data can be configured offline using the CSC-12 reference point. The common group configuration data specified in Table A.4-1 in TS 23.280 is also used, as needed, in the IOPS mode of operation. Table A.4-1 described below contains additional group configuration data required to support MC services in the IOPS mode of operation.

As specified in TS 23.280, the configuration management server is used to configure the MC service configuration data to the MC service UE (CSC-4). The MC service configuration data can be configured offline using the CSC-11 reference point. Table A.5-1 and Table A.5-2 describe the configuration data required to support in IOPS the use of MCPTT service and MCData service, respectively.

 

Initial MC service UE configuration data is essential to the MC service UE to successfully connect to the MC system, as described in TS 23.280. The configuration data defined in Table A.6-1 is additionally provided to the MC service UE's clients to successfully connect to the IOPS MC system in the IOPS mode of operation. The MC service UE's clients (e.g. MC service client, IOPS connectivity client) obtain the data during the bootstrap process (described in clause 10.1.1 of TS 23.280), and can be configured on the MC service UE offline using the CSC-11 reference point or via other means e.g. as part of the MC service client's provisioning on the UE, using a device management procedure.