Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 33.127  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   5…   5.4…   5.6…   5.7…   6…   6.2.2…   6.2.3…   6.2.5…   6.3…   6.3.3…   6.3.4…   6.4…   7…   7.3…   7.4…   7.4.7…   7.5…   7.6…   7.7…   7.8…   7.9…   7.10…   7.11…   7.12…   7.13…   7.14…   7.15…   7.16…   8…   A…   A.2…   A.3…   A.4…   B…   D…   E… 
7.6 PTC service  7.6.1 General  7.6.2 Target identities  7.6.3 IRI events  7.6.4 Common IRI parameters  7.6.5 Specific IRI parameters  7.6.6 Common CC parameters  7.6.7 Specific CC parameters  7.6.8 Network topologies 
...

 

7.6  PTC service  p. 102

7.6.1  General  p. 102

In the present clause, "PTC" will be used to reference events or services that occur in either of two different architectures unless specified otherwise, e.g., Mission Critical Push To Talk (MCPTT) or Push to talk over Cellular (PoC).
The following servers support PTC architecture:
The PTC server will be used to represent the MCPTT server or PoC server for group communication services.
If two or more different parties involved in a PTC communication are each a target of interception, each interception shall operate independently of the others and the results of each intercept shall be delivered to the respective LEMF in accordance with the applicable warrant.
Up

7.6.2  Target identities  p. 103

A provisioned target identity can be the following:
  • MCPTT ID.
  • Instance Identifier URN.
  • IMPU.
  • IMPI.
  • PTC Chat GroupID.
The interception performed on the above identities are mutually independent, even though, an xIRI may contain the information about the other identities when available.

7.6.3  IRI events  p. 103

The IRI-POI present in the PTC Server shall generate xIRI when it detects the following specific events or information:
  • PTC service registration.
  • PTC session initiation.
  • PTC session abandon.
  • PTC session start.
  • PTC session end.
  • PTC start of interception.
  • PTC pre-established Session.
  • PTC instant personal alert.
  • PTC party join.
  • PTC party drop.
  • PTC party hold.
  • PTC media modification.
  • PTC group advertisement.
  • PTC floor control.
  • PTC target presence.
  • PTC associate presence.
  • PTC list management.
  • PTC access policy.
The events above trigger the transmission of information from the IRI-POI to the MDF2.
Up

7.6.4  Common IRI parameters  p. 104

Each xIRI shall include at the minimum the following information:
  • Target identity.
  • Time stamp.
  • Correlation information.
  • Location information (if required and available).
  • PTC related information (e.g., PTC group ID, PTC party).
  • Encryption parameters (if required and available).
  • Direction (floor control source or destination port).

7.6.5  Specific IRI parameters  p. 104

The parameters in each xIRI are defined in TS 33.128.

7.6.6  Common CC parameters  p. 104

In addition to the intercepted content of communications, the following information needs to be transferred from the CC-POI to the MDF3 in order to allow the MDF3 to perform its functionality:
  • Target identity.
  • Correlation information.
  • Time stamp.
  • Identity of source of media (communications content) for group call.

7.6.7  Specific CC parameters  p. 104

The parameters in xCC are defined in TS 33.128.

7.6.8  Network topologies  p. 104

The PTC server resides in the home network and shall provide IRI-POI and CC-POI functionality.

Up   Top   ToC