Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 22.179  Word version:  19.2.0

Top   Top   Up   Prev   Next
0…   4…   4.3   4.4…   4.6…   5…   5.6…   5.7…   5.8…   6…   6.4…   6.6…   6.8…   6.12…   6.16…   7…   7.11…   A…

 

5  MCPTT Service requirements common for on the network and off the networkp. 22

5.1  General group call requirementsp. 22

5.1.1  General aspectsp. 22

[R-5.1.1-001]
Void
[R-5.1.1-002]
Void
[R-5.1.1-003]
Void
[R-5.1.1-004]
Void
[R-5.1.1-005]
Void

5.1.2  Group/status informationp. 22

[R-5.1.2-001]
Void
[R-5.1.2-002]
Void

5.1.3  Group configurationp. 22

[R-5.1.3-001]
Void
[R-5.1.3-002]
Void

5.1.4  Identificationp. 23

[R-5.1.4-001]
Void

5.1.5  Membership/affiliationp. 23

[R-5.1.5-001]
Void
[R-5.1.5-002]
Void
[R-5.1.5-003]
Void
[R-5.1.5-004]
Void
[R-5.1.5-005]
Void
[R-5.1.5-006]
Void
[R-5.1.5-007]
Void
[R-5.1.5-008]
Void

5.1.6  Group Call administrationp. 23

[R-5.1.6-001]
Void

5.1.7  Prioritizationp. 23

[R-5.1.7-001]
Void
[R-5.1.7-002]
Void

5.1.8  Charging requirements for MCPTTp. 23

[R-5.1.8-001]
Void
[R-5.1.8-002]
Void
[R-5.1.8-003]
Void
[R-5.1.8-004]
Void
[R-5.1.8-005]
Void
[R-5.1.8-006]
Void
[R-5.1.8-007]
Void
[R-5.1.8-008]
Void
[R-5.1.8-009]
Void
[R-5.1.8-010]
Void
[R-5.1.8-011]
Void

5.2  Broadcast Groupp. 23

5.2.1  General Broadcast Group Callp. 23

[R-5.2.1-001]
Void
[R-5.2.1-002]
Void

5.2.2  Group-Broadcast Group (e.g., announcement group)p. 24

[R-5.2.2-001]
Void
[R-5.2.2-002]
Void
[R-5.2.2-003]
Void
[R-5.2.2-004]
Void

5.2.3  User-Broadcast Group (e.g., System Call)p. 24

[R-5.2.3-001]
Void
[R-5.2.3-002]
Void

5.3  Late call entryp. 24

[R-5.3-001]
Void
[R-5.3-002]
Void
[R-5.3-003]
Void
[R-5.3-004]
Void
[R-5.3-005]
Void

5.4  Dynamic group management (i.e., dynamic regrouping)p. 24

5.5  Receiving from multiple MCPTT callsp. 24

5.5.1  Overviewp. 24

MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCPTT User is deployed to provide additional support for that event. The MCPTT User might be assigned to support the activities of more than one MCPTT Group on the same shift. This means that the MCPTT User receives multiple MCPTT Groups.
An MCPTT User with limited speaker resources (e.g., a handheld UE) might find that playing out concurrent received audio from multiple active MCPTT Groups becomes confusing and could also cause undesired voice distortion for the receiving user. During periods of time when the MCPTT User is receiving audio from multiple MCPTT Groups, which MCPTT Group's audio is presented to the MCPTT User is determined by the MCPTT User's choice, the priority associated with the talker of the Selected MCPTT Group(s), other considerations or combinations of these. The MCPTT UE is aware of all the active groups to which the MCPTT User has affiliated or selected and the identity of the other active receiving groups is available for display on the MCPTT UE. When the receive activity from the Selected MCPTT Group stops, the MCPTT UE might present the audio from the next group per the MCPTT User's choice or by other means.
If none of the multiple groups to which the MCPTT User has affiliated or selected is active, the MCPTT UE would continue to monitor for activity by any of the multiple affiliated or Selected MCPTT Groups. Monitoring for activity of multiple MCPTT Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
Up

5.5.2  Requirementsp. 25

[R-5.5.2-001]
Void
[R-5.5.2-002]
Void
[R-5.5.2-003]
Void
[R-5.5.2-004]
Void
[R-5.5.2-005]
Void
[R-5.5.2-006]
The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-007]
The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N10) of MCPTT Private Calls (with Floor control) in which an MCPTT UE simultaneously participates.
[R-5.5.2-008]
Void
[R-5.5.2-009]
The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N7) of MCPTT Group transmissions that an MCPTT User simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-010]
Void
[R-5.5.2-011]
Void
[R-5.5.2-012]
Void
[R-5.5.2-013]
Void
Up

Up   Top   ToC