Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   A…   B…

 

A (Normative)  Configuration data for MC servicesWord‑p. 256

A.1  General

This Annex provides information about the static data needed for configuration for MC services, which belong to one of the following categories:
  • MC service UE configuration data (see subclause A.2);
  • MC service user profile data (see subclause A.3);
  • MC service group configuration data (see subclause A.4);
  • MC service configuration data (see subclause A.5); and
  • Initial MC service UE configuration data (see subclause A.6).
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 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. 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.280 or TS 22.281 or TS 22.282 or TS 22.179 or the corresponding subclause from the present 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 the 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 MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
Up

A.2  MC service UE configuration dataWord‑p. 257
MC service UE configuration data has to be known by an MC service UE after MC service authorization. The CSC‑4 reference point 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.
MC service UE configuration data is specific to each MC service and is specified as follows:
  • MCPTT UE configuration data is specified in TS 23.379;
  • MCVideo UE configuration data is specified in TS 23.281; and
  • MCData UE configuration data is specified in TS 23.282.
Within each MC service, the MC service UE configuration data can be the same or different across MC service UEs.
Up

A.3  MC service user profile configuration data

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).
MC service user profile configuration data can be configured offline using the CSC‑11 reference point.
MC service user profile configuration data is specific to each MC service and is specified as follows:
  • MCPTT user profile configuration data is specified in TS 23.379;
  • MCVideo user profile configuration data is specified in TS 23.281; and
  • MCData user profile configuration data is specified in TS 23.282;
Up

A.4  Group configuration data

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) and the MC service server (CSC‑3).
A single group can support one or multiple MC service configurations. Hence, the MC service group configuration data is divided into common group configuration data and MC service specific group configuration data.
The group configuration data can be configured offline using the CSC‑12 reference point.
The common group configuration data are specified in Table A.4-1. Table A.4-1 and Table A.4-2 contain the group configuration required to support the use of on-network MC service. Table A.4-1 and Table A.4-3 contain the group configuration required to support the use of off-network MC service.
The MC service related group configuration data specific to each MC service is specified as follows:
  • MCPTT related group configuration data is specified in TS 23.379;
  • MCVideo related group configuration data is specified in TS 23.281; and
  • MCData related group configuration data is specified in TS 23.282;
Reference Parameter description MC service UE MC service Server Group management server
[R-5.17-004], [R-6.4.3-001], [R-6.4.3-002], [R-6.9-004] and [R-5.1.3-002] of TS 22.280MC service group IDYYY
[R-5.17-004], [R-6.4.3-001], [R-6.4.3-002] and [R-6.9-004] of TS 22.280Group Alias (Contact URIs)YYY
List of group members (see NOTE 1) (see NOTE 8)
 
Reference Parameter description MC service UE MC service Server Group management server
Reference Parameter description MC service UE MC service server Group management server
Subclause 8.1.3.2 ProSe layer-2 group ID (as specified in TS 23.303)YNY
Subclause 8.1.3.2 ProSe group IP multicast address (as specified in TS 23.303)YNY
Subclause 8.1.3.2 Indication of whether the UE shall use IPv4 or IPv6 for the MC service group (as specified in TS 23.303)YNY
MC service specific configuration
> MCPTT configuration (see NOTE 1)
> MCVideo configuration (see NOTE 2)
> MCData configuration (see NOTE 3)
Up

A.5  MC service configuration dataWord‑p. 261
The MC service configuration data is stored in the MC service server. The configuration management server is used to configure the MC service configuration data to the MC service server (CSC‑5) and the MC service UE (CSC‑4).
The MC service configuration data can be configured offline using the CSC‑11 reference point.
The MC service configuration data is specific to each MC service and hence the detailed list of MC service configuration data is listed as follows:
  • MCPTT service configuration data is specified in TS 23.379;
  • MCVideo service configuration data is specified in TS 23.281; and
  • MCData service configuration data is specified in TS 23.282;
Up

A.6  Initial MC service UE configuration data

The initial MC service UE configuration data is essential to the MC service UE to successfully connect to the MC system. The initial MC service UE configuration data can be the same or different across MC service UEs.
Data in Table A.6-1 is provided to the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client) during the bootstrap process (see subclause 10.1.1), 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 MCPTT client's provisioning on the UE, using a device management procedure.
Reference Parameter description
Subclause 10.1.1 PDN connectivity information
> HPLMN ID and optionally VPLMN ID to which the data pertains
> MC services PDN
>> APN
>> PDN access credentials
> MC common core services PDN
>> APN
>> PDN access credentials
> MC identity management service PDN
>> APN
>> PDN access credentials
Subclause 10.1.1 Application plane server identity information
> Identity management server
>> Server URI
> Configuration management server
>> Server URI
> Key management server
>> Server URI (also known as KMSUri for security domain managed by KMS)
> Indication of whether the UE shall use IPv4 or IPv6 for on-network MCPTT
> MCPTT Server
>> Server URI
> Indication of whether the UE shall use IPv4 or IPv6 for on-network MCData
> MCData Server
>> Server URI
> Indication of whether the UE shall use IPv4 or IPv6 for on-network MCVideo
> MCVideo Server
>> Server URI
> Location management server
>> Server URI
Up

Up   Top   ToC