Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.18…   10.6.2.2.34…   10.6.2.3…   10.6.2.3.2…   10.6.2.4…   10.6.2.5…   10.6.2.6…   10.6.2.7…   10.6.2.9…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.6…   10.9…   10.9.1.3…   10.9.2…   10.10…   10.14…   A…   A.4…   B…

 

A (Normative)  MCPTT related configuration dataWord‑p. 228

A.1  General

This Annex provides information about the static data needed for configuration for the MCPTT service, which belongs to one of the following categories:
  • MCPTT UE configuration data (see sub-clause A.2);
  • MCPTT user profile configuration data (see sub-clause A.3);
  • MCPTT related group configuration data (see sub-clause A.4); and
  • MCPTT 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 MCPTT UE, MCPTT group, MCPTT user and MCPTT service configuration data refers to the information that will be stored against each MCPTT UE, MCPTT group, MCPTT user and MCPTT 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.179 or TS 22.280 or TS 23.280 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 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 MCPTT UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
Up

A.2  MCPTT UE configuration dataWord‑p. 229
The general aspects of UE configuration are specified in TS 23.280. Data in Table A.2-1 and Table A.2-2 have to be known by the MCPTT UE after MCPTT authorization.
Data in Table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-2 contains the UE configuration required to support the use of off-network MCPTT service.
Reference Definition
[R-5. 4.2-002] of TS 22.280Maximum number of simultaneous group calls (Nc4)
[R-5.4.2-003] of TS 22.280Maximum number of transmissions (Nc5) in a group
[R-5.5.2-007] of TS 22.280Maximum number of private calls (N10)
 
Reference Definition
Subclause 5.2.3 of TS 23.280Relay service (Y/N)
Subclause 5.2.3 of TS 23.280List of allowed relayed MCPTT groups and their relay service code (as specified in TS 23.303) (optional) (see NOTE)
> MCPTT group ID
> Relay service code (as specified in TS 23.303)
Up

A.3  MCPTT user profile configuration data

The general aspects of MC service user profile configuration data are specified in TS 23.280. The MCPTT user profile configuration data is stored in the MCPTT user database. The MCPTT server obtains the MCPTT user profile configuration data from the MCPTT user database (MCPTT‑2).
Table A.3-1 and Table A.3-2 contain the MCPTT user profile configuration required to support the use of on-network MCPTT service. Table A.3-1 and Table A.3-3 contain the MCPTT user profile configuration required to support the use of off-network MCPTT service. Data in Table A.3-1 and Table A.3-3 can be configured offline using the CSC-11 reference point.
Reference Parameter description MCPTT UE MCPTT Server Configuration management server MCPTT user database
 
Reference Parameter description MCPTT UE MCPTT Server Configuration management server MCPTT user database
 
Reference Parameter description MCPTT UE MCPTT Server Configuration management server MCPTT user database
Up

Up   Top   ToC