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

Content for  TS 23.282  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.1.10…   7.4.2.2…   7.4.2.5…   7.4.2.8…   7.4.3…   7.5…   7.5.2.1.12…   7.5.2.2…   7.5.2.4…   7.5.2.6…   7.5.2.8…   7.5.2.11…   7.5.2.14…   7.5.3…   7.6   7.7…   7.7.2.3…   7.8…   7.9…   7.13…   7.13.3.1.19…   7.13.3.2…   7.13.3.8…   7.13.3.16…   7.13.4…   7.14…   7.14.2.2…   A…   B… 
7.9 Enhanced status  7.9.1 General  7.9.2 Preset values for enhanced status  7.9.3 Enhanced status for on-network  7.9.4 Enhanced status for off-network  7.10 MCData emergency alert (on-network and off-network)  7.11 User authentication and authorization for MCData service  7.12 MCData resource management (on-network) 
...

 

7.9  Enhanced status  p. 164

7.9.1  General  p. 164

Enhanced status corresponds to information specific to the activities performed by the mission critical service users during their operation(s) e.g. available, in operation on site, going to the operation site, or just arrived.
Enhanced status for on-network is described in clause 7.9.3 and for off-network in clause 7.9.4. Off-network enhanced status is based on ProSe capabilities as described in clause 7.16.
Up

7.9.2  Preset values for enhanced status  p. 164

The enhanced status information i.e. the set of possible values corresponding to the activities of the MCData user, shall be configured by the MCData administrator. The configuration of status values is applicable on a per-group basis, and therefore shall be part of the MCData group configuration data as described in Annex A.4.
The configuration mechanism shall allow the MCData administrator to configure a minimum of 32 possible values and allow up to 65536 separate values. The set of values may be divided into a fixed set of values defined by 3GPP standards which are common across all MCData systems, and a set which may be freely configured for any purpose.
Up

7.9.3  Enhanced status for on-network  p. 164

7.9.3.1  Sharing enhanced status information  p. 164

7.9.3.1.1  Procedure  p. 164
The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in Figure 7.9.3.1.1-1.
Pre-conditions:
  1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service.
  2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service.
  3. The MCData group is pre-configured with the possible values for enhanced status information.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.9.3.1.1-1: Sharing enhanced status information
Figure 7.9.3.1.1-1: Sharing enhanced status information
(⇒ copy of original 3GPP image)
Up
Step 1.
The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group.
Step 2.
The procedure of group standalone SDS using signalling control plane as described in subclause 7.4.2.5, is used to deliver the enhanced status information.
Step 3.
The MCData users at MCData client 2 and n are notified of the enhanced status information.
Up

7.9.4  Enhanced status for off-network  p. 165

7.9.4.1  Sharing enhanced status information  p. 165

7.9.4.1.1  Procedure  p. 165
The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in Figure 7.9.4.1.1-1.
Pre-conditions:
  1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1.
  2. MCData client 1, 2 and n are members of the same MCData group.
  3. The MCData group is pre-configured with the possible values for enhanced status information.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.9.4.1.1-1: Sharing enhanced status information
Figure 7.9.4.1.1-1: Sharing enhanced status information
(⇒ copy of original 3GPP image)
Up
Step 1.
The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group.
Step 2.
The procedure of off-network group standalone SDS using signalling control plane as described in subclause 7.4.3.4, is used to deliver the enhanced status information.
Step 3.
The MCData users at MCData client 2 and n are notified of the enhanced status information.
Up

7.10  MCData emergency alert (on-network and off-network)  p. 166

The MCData service shall support the procedures and related information flows as specified in subclause 10.10 of TS 23.280 with the following clarifications:
  • The MC service client is the MCData client;
  • The MC service server is the MCData server;
  • The MC service group ID is the MCData Group ID; and
  • The MC service user profile index is the MCData user profile index.

7.11  User authentication and authorization for MCData service  p. 166

A procedure for user authentication is illustrated in Figure 7.11-1. The user authentication is performed based on the procedure specified in subclause 10.6 of TS 23.280.
Copy of original 3GPP image for 3GPP TS 23.282, Fig. 7.11-1: MCData user authentication and registration, single domain
Figure 7.11-1: MCData user authentication and registration, single domain
(⇒ copy of original 3GPP image)
Up
Step 1.
The user authentication is performed as per the general user authentication procedure specified in subclause 10.6 of TS 23.280.
Step 2.
MCData client performs the MCData service authorization for the user. Step 2 utilizes the results of step 1.

7.12  MCData resource management (on-network) |R15|  p. 167

7.12.1  General  p. 167

Procedures for resource management are defined in subclause 10.11 of TS 23.280.

7.12.2  MCData services not handled by SIP core  p. 167

MCData services that do not utilize the SIP core e.g. IP connectivity, cannot utilize the resource control functionality of the local outbound / inbound proxy. For these types of service, resource management is handled directly by the Rx interface from the MCData server to the PCRF, which is the MCData-5 reference point. The Rx interface is defined in TS 29.214.
The same types of resource management procedures as defined for SIP based services in TS 23.280 may also be applied for non SIP based services. That is:
  • Request for unicast resources at session establishment (in this case service initiation);
  • Request for modification of unicast resources; and
  • Request for resources with shared priority.
Up

Up   Top   ToC