SIST ETS 300 392-11-22 E1:2003

Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 22: Dynamic Group Number Assignment (DGNA)

Analysis of predicted needs for digital trunked systems in Europe; definition of services to be provided; analysis of spectrum req ments; characteristics of relevant interfaces Contains: TETRA 08.60 to 08.85

Prizemni snopovni radio (TETRA) – Govor in podatki (V+D) – 11. del: Dopolnilne storitve stopnje 2 – 22. poglavje: Dinamično dodeljevanje skupinskih številk (DGNA)

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• Withdrawal Date: 30-Jun-1999
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 392-11-22 ed.1 (2000-04) - Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 22: Dynamic Group Number Assignment (DGNA)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 392-11-22
01-MXOLM
3UL]HPQLVQRSRYQLUDGLR7(75$±*RYRULQSRGDWNL9'±GHO'RSROQLOQH
VWRULWYHVWRSQMH±SRJODYMH'LQDPLþQRGRGHOMHYDQMHVNXSLQVNLKãWHYLON
'*1$
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary
services stage 2; Sub-part 22: Dynamic Group Number Assignment (DGNA)
Ta slovenski standard je istoveten z: ETS 300 392-11-22 E
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 392-11-22 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 392-11-22 E1:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 392-11-22 E1:2003
DRAFT
EUROPEAN pr ETS 300 392-11-22
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-06001-11-22
ICS: 33.060, 33.060.50
Key words: TETRA, V+D, DGNA
Radio Equipment and Systems (RES);
Trans-European Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 11: Supplementary Services (SS) Stage 2;
Part 11-22: Dynamic Group Number Assignment (DGNA)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1996. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 2
Draft prETS 300 392-11-22: September 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 3
Draft prETS 300 392-11-22: September 1996
Contents
Foreword .5
1 Scope .7
2 Definitions and abbreviations .7
2.1 Definitions .7
2.2 Abbreviations .8
2.2.1 General abbreviations .8
3 Supplementary Service Dynamic Group Number Assignment (SS-DGNA) stage 2 specification.8
3.1 Functional model.8
3.1.1 Functional model description.8
3.1.2 Description of FEs.9
3.1.2.1 Affected user's functional entity, FE1 .9
3.1.2.2 SS-DGNA functional entity, FE2.9
3.1.2.3 Authorized user's functional entity, FE3.10
3.1.2.4 Functional entity in system 2, FE4.10
3.1.3 Relationship with a basic service .10
3.2 Information flows.11
3.2.1 Definition of information flows .11
3.2.1.1 Addition/modification of SS-DGNA number.11
3.2.1.1.1 DEFINE request.12
3.2.1.1.2 DEFINE-ACK .12
3.2.1.2 Deletion of SS-DGNA number and/or removal of affected
users from the group .13
3.2.1.2.1 DELETE request.13
3.2.1.2.2 DELETE-ACK .13
3.2.1.3 DGNA assignment to affected users .13
3.2.1.3.1 ASSIGN request .14
3.2.1.3.2 ASSIGN-ACK.14
3.2.1.4 DGNA de-assignment of affected user.14
3.2.1.4.1 DEASSIGN request .15
3.2.1.4.2 DEASSIGN-ACK.15
3.2.1.5 Interrogation of the definition .15
3.2.1.5.1 INTERROGATE request.16
3.2.1.5.2 INTERROGATE-ACK .16
3.2.1.6 Cancellation of a SS-DGNA number addition/modification .17
3.2.1.6.1 CANCEL request .17
3.2.1.6.2 CANCEL-ACK.17
3.2.1.7 Information flows between different TETRA systems.18
3.2.2 Relationship of SS-DGNA information flows to other information flows.18
3.3 Information flow sequences of call unrelated DGNA definition.18
3.3.1 Successful addition/modification and operation when authorized user in
system 1 .18
3.3.2 Successful deletion and removal operation when authorized user in
system 1 .19
3.4 FE actions of call unrelated DGNA definition and operation.19
3.4.1 FE actions of FE1.19
3.4.2 FE actions of FE2.20
3.4.3 FE actions of FE3.20
3.4.4 FE actions of FE4.20
3.5 Information flow sequences of call unrelated DGNA interrogation .21
3.5.1 Interrogation when authorized user in system 1.21
3.5.2 Interrogation when authorized user in system 2.21
3.6 FE actions of call unrelated DGNA interrogation .22
3.6.1 FE actions of FE2.22
3.6.2 FE actions of FE3.22

---------------------- Page: 5 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 4
Draft prETS 300 392-11-22: September 1996
3.6.3 FE actions of FE4 . 22
3.7 Information flow sequences of call related DGNA definition and operation . 22
3.7.1 Definition and operation when authorized user in system 1 . 22
3.8 FE actions of call related DGNA definition and operation . 23
3.8.1 FE actions of FE1 . 23
3.8.2 FE actions of FE2 . 23
3.8.3 FE actions of FE3 . 24
3.8.4 FE actions of FE4 . 24
3.9 Examples of exceptional operation of call unrelated and call related DGNA. 24
3.9.1 Cancellation request of call unrelated or call related DGNA definition . 24
3.9.2 FE actions of DGNA definition cancellation request. 25
3.9.2.1 FE actions of FE2 . 25
3.9.2.2 FE actions of FE3 . 25
3.10 Allocation of FEs to physical equipment. 25
3.11 Inter-working considerations . 25
History. 26

---------------------- Page: 6 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 5
Draft prETS 300 392-11-22: September 1996
Foreword
This draft European Telecommunication Standard (ETS) has been produced by the Radio Equipment and
Systems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI),
and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.
This ETS is a multi-part standard and will consist of the following parts:
Part 1: "General network design".
Part 2: "Air Interface (AI)".
Part 3: "Inter-working", (DE/RES-06001-3).
Part 4: "Gateways", (DE/RES-06001-4).
Part 5: "Terminal equipment interface", (DE/RES-06001-5).
Part 6: "Line connected stations", (DE/RES-06001-6).
Part 7: "Security".
Part 8: "Management services", (DE/RES-06001-8).
Part 9: "Performance objectives", (DE/RES-06001-9).
Part 10: "Supplementary Services (SS) Stage 1".
Part 11: "Supplementary Services (SS) Stage 2".
Part 12: "Supplementary Services (SS) Stage 3".
Part 13: "SDL Model of the Air Interface".
Part 14: "PICS Proforma", (DE/RES-06001-14).
Part 15: "Inter-working - Extended Operations", (DE/RES-06001-15).
Proposed transposition dates
Date of latest announcement of this ETS (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa

---------------------- Page: 7 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 6
Draft prETS 300 392-11-22: September 1996
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 7
Draft prETS 300 392-11-22: September 1996
1 Scope
This European Telecommunication Standard (ETS) defines the stage 2 specifications of the
Supplementary Service Dynamic Group Number Assignment (SS-DGNA) for the Trans-European
Trunked Radio (TETRA).
The SS-DGNA enables a user to dynamically define group identities and group related parameters to the
TETRA system and to the subscribers in the system. These definitions are used to enable group call
invocations to dynamically defined groups. This ETS specifies the creation, modification, deletion and
interrogation of group definitions in the Switching and Management Infrastructure (SwMI), in the Mobile
Station (MS) and in the Line Station (LS). The operations can be made within one TETRA system or over
the Inter System Interface (ISI).
This specification does not include the specification for access priority used for random access in uplink
and call priority used by SwMI for resource allocation for a group. Access priority and call priority can be
specified for groups using Supplementary Service Access Priority (SS-AP), Supplementary Service
Priority Call (SS-PC) and Supplementary Service Pre-emptive Priority Call (SS-PPC).
Man-Machine Interface (MMI) and Charging principles are outside the scope of this ETS.
Stage 2 describes the functional capabilities of the Supplementary Service introduced in stage 1
description. Stage 2 identifies the functional capabilities for the management of the service in the SwMI, in
the MS and in the LS. Stage 2 describes the information flows exchanged between these entities, and it
also describes the flows sent over the ISI.
NOTE: The stage 2 description is followed by the stage 3 description, which specifies the
encoding rules for the information flows and process behaviour for the different entities
in SwMI, MS and LS of the service.
2 Definitions and abbreviations
2.1 Definitions
For the purposes of this ETS, the following definitions apply:
affected user: An identified MS or LS user to whom the service is assigned.
authorized user: A user who is authorized to define, cancel, delete and interrogate SS-DGNA numbers.
bearer service: A type of telecommunication service that provides the capability for the transmission of
signals between user-network interfaces.
call related DGNA: Creation of a group based on the participants of a referenced call.
call unrelated DGNA: Creation of a group based on identities.
Mobile Station (MS): A physical grouping that contains all of the mobile equipment that is used to obtain
TETRA services. By definition, a mobile station contains at least one Mobile Radio Stack (MRS).
provision: The act of supplying a given service.
supplementary service: A supplementary service modifies or supplements a bearer service or a
teleservice. A supplementary service cannot be offered to a customer as a stand alone service. It should
be offered in combination with a bearer service or a teleservice.
Switching And Management Infrastructure (SwMI): All of the TETRA equipment for a Voice plus Data
(V+D) network except for subscriber terminals. The SwMI enables subscriber terminals to communicate
with each other via the SwMI.

---------------------- Page: 9 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 8
Draft prETS 300 392-11-22: September 1996
teleservice: A type of telecommunications service that provides the complete capability, including
terminal equipment functions, for communication between users according to agreed protocols.
2.2 Abbreviations
2.2.1 General abbreviations
For the purposes of this ETS, the following general abbreviations apply:
AP Access Priority
CC Call Control
CCA Call Control (functional entity Agent)
DGNA Dynamic Group Number Assignment
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
ISI Inter-System Interface
MS Mobile Station
LS Line Station
PC Priority Call
PPC Pre-emptive Priority Call
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SwMI Switching and Management Infrastructure
3 Supplementary Service Dynamic Group Number Assignment (SS-DGNA)
stage 2 specification
3.1 Functional model
3.1.1 Functional model description
The functional model shall comprise the following Functional Entities (FEs):
- FE1 Authorized user's definition, cancellation and interrogation functional entity in the SS-DGNA
system 1;
- FE2 Dynamic Group Number Assignment functional entity;
- FE3 Affected user's functional entity;
- FE4 Generic Dynamic Group Number Assignment functional entity in system 2;
- CC Call Control (functional entity);
- CCA Call Control (functional entity Agent).
The following relationships shall exist between these FEs:
- ra between FE1 and FE2;
- rb between FE2 and FE3;
- rc between FE2 and FE4;
- rd between FE4 and FE1;
- re between FE4 and FE3.
Figure 1 shows these FEs and their relationships.

---------------------- Page: 10 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 9
Draft prETS 300 392-11-22: September 1996
  SYSTEM 1
rb ra
FE3 FE2 FE1
authorized SS-DGNA affected
user FE user
rc rc
ISI
  SYSTEM 2
re rd
FE3 FE4 FE1
authorized SS-DGNA FE affected
user user
ISI
  SYSTEM 3
rd
FE4 FE1
SS-DGNA FE affected
user
Figure 1: Functional model for SS-DGNA
3.1.2 Description of FEs
3.1.2.1 Affected user's functional entity, FE1
FE1 shall receive the SS-DGNA addition/modification and removal information flows to affected users
from FE2. When the addition/modification data is sent to FE1, FE1 shall add the SS-DGNA number and
parameters to the database in the MS; in case of removal of SS-DGNA number, FE1 shall remove the
SS-DGNA number and its parameters from the database in the MS. FE1 should acknowledge the
definition/deletion requests to FE2 if acknowledgement have been requested.
In case of addition/modification or removal of SS-DGNA, the FE1 may make local checks before
accepting the request. FE1 should also use the network authorization procedure before accepting any
SS-DGNA changes. However, FE1 should accept the SS-DGNA requests if they are authorized and valid.
At the reception of interrogation request from a service user, FE1 should send the request to FE2. When
FE1 receives the response from FE2, FE1 should indicate the response to the service user.
3.1.2.2 SS-DGNA functional entity, FE2
FE2 shall make the SS-DGNA additions/modifications, deletions, cancellation and interrogations in the
SwMI.
At the reception of any SS-DGNA request, FE2 shall verify the SS-DGNA identity, check the validity of
parameters and verify that the request is authorized. Upon these checks, FE2 shall reject the service
request or accept and perform it.

---------------------- Page: 11 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 10
Draft prETS 300 392-11-22: September 1996
In case of an accepted SS-DGNA addition/modification, FE2 shall save the definition to the database in
SwMI. In case of an on-going call to which the user requests a call related SS-DGNA definition, FE2 shall
also fetch the call related data from CC.
When the user requests the addition/modification of SS-DGNA, optionally, the FE2 may make the
operation to assign the SS-DGNA number and group-related data to affected users.
As an operator option, when the user requests addition/modification of SS-DGNA, FE2 may verify the
dynamic group composition. If the composition exists as a group number, FE2 may offer the authorized
user the possibility to cancel the SS-DGNA definition request. In that case, FE2 shall send the SS-DGNA
cancellation request and receive the response. If the response indicates to continue to make the
definition, FE2 shall do so; if the response indicates that FE2 shall not continue, FE2 shall stop the service
execution, but FE2 shall send an acknowledgement to FE3.
In case of SS-DGNA deletion, FE2 shall remove the definition from the database in SwMI. Optionally, the
FE2 may also remove the SS-DGNA number and group-related data from the database of affected users.
In case of interrogation, FE2 shall fetch the SS-DGNA data from the database and send the interrogation
response to the requesting party.
If the system enables SS-DGNA service to be requested for a released call, FE2 shall be able to provide
means to recover the call specific data needed for the definition when the request is made. It shall be an
operator option defined by the CC-SS call retention timer, if the call related DGNA definition can be
invoked within a time limit.
3.1.2.3 Authorized user's functional entity, FE3
FE3 shall receive addition/modification, deletion, cancellation or interrogation requests from the user. FE3
may check these requests and if FE3 finds them valid, it shall send them to FE2. When FE2 sends the
responses for these requests FE3 displays them to the user.
FE2 may also request continuation for a requested SS-DGNA addition, if a SS-DGNA definition with the
same parameters is found in the system. FE3 shall receive and display these request to the user and
return the user's response to FE2.
If the user requests a call related DGNA addition, FE3 shall fetch the call identifier and add it to the
definition request.
3.1.2.4 Functional entity in system 2, FE4
FE4 shall act as an control entity in an other TETRA system, if the SS-DGNA service request are sent
over the Inter System Interface. FE4 shall deliver SS-DGNA service requests from FE2 to FE1 or FE3, or
from FE1 or FE3 to FE2. The FE4 shall also add the (V)GTSIs or GTSIs to messages, and in case of call
related SS-DGNA definition FE4 shall provide the information flows with the system 2 or home system call
identifier. FE4 shall also add the routeing addresses and may perform authorization checks.
3.1.3 Relationship with a basic service
In case of call related SS-DGNA FE1 shall be collocated with user A's CCA. The CCA shall support the
definition process by giving the call identifier used for the definition request.
In case of call related SS-DGNA FE2 shall be collocated with CC in SwMI as the CC provides FE2 with
the call related data used for the SS-DGNA definition.
Figure 2 shows the relationships that shall exist between FEs and CC/CCA in case of call related
SS-DGNA definition. There shall not be any relationships between FEs and CC/CCAs in case of
interrogation or call unrelated SS-DGNA definition, deletion or interrogation.

---------------------- Page: 12 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 11
Draft prETS 300 392-11-22: September 1996
  SYSTEM 1
rb ra
FE3 FE2 FE1
CCA CC
affected
authorized SS-DGNA user
user FE
rc
ISI
rc
  SYSTEM 2
re rd
FE3 FE4 FE1
CCA
SS-DGNA FE affected
authorized user
user
ISI
  SYSTEM 3
rd
FE4 FE1
SS-DGNA FE affected
user
Figure 2: The relationships between the basic service and call related SS-DGNA FEs
3.2 Information flows
3.2.1 Definition of information flows
The definitions of information flows define the informational contents exchanged between the different
functional entities.
In the tables listing the element type indicates whether the data type is mandatory "M", conditional "C" or
optional "O". The responses to request or interrogation messages are named as the request/interrogation
messages with the extension "ACK".
3.2.1.1 Addition/modification of SS-DGNA number
A SS-DGNA definition can comprise of an addition or modification of a DGNA number definition. The
addition and modification are made with the same SS-DGNA information flow.
The SS-DGNA addition shall be call related or call unrelated. When authorized user is making a call
related DGNA addition, he shall refer to a call with call identifier. The SwMI should define the call
parameters according to the referred call. However, the authorized user can define some or all parameter
values by giving the values explicitly in the definition command. After the SS-DGNA addition (creation) is
completed, the call related DGNA shall be ended. After that, there is no difference between the call related
and call unrelated DGNA. The modification, deletion and interrogation of SS-DGNA shall be done
independently of any ongoing call, and these actions shall be always call unrelated.

---------------------- Page: 13 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 12
Draft prETS 300 392-11-22: September 1996
In case of call unrelated SS-DGNA addition, the authorized user shall give the parameters for the
definition. However, the authorized user can omit the DGNA number, in which case SwMI shall find a valid
DGNA, make the definition for that number and return it to the authorized user.
The authorized user can change the parameters of a group, e.g. new affected users can be added to the
group. For addition and modification the same information flow (DEFINE) shall be used, as described
below.
The authorized user can make DGNA definitions to the SwMI only or to the SwMI and to the affected
users.
At the reception of SS-DGNA definition request, FE2 can authenticate FE3 that made the request before
accepting the definition. For that purpose, the general authentication procedures, that are defined for
TETRA in order to authenticate MS- or LS-subscribers, shall be applied.
3.2.1.1.1 DEFINE request
The DEFINE information flow shall be for the relationship rb, rc and re. The flow shall be sent from FE3 to
FE2 or from FE3 to FE2 via FE4. The flow shall be used to add and modify a call related and call
unrelated SS-DGNA number.
The addition and modification shall be done with the same information flow. The parameters included in
an addition/modification request shall override the previously defined parameters, if any. If a parameter is
not given in the request, the previously defined parameter value shall be valid for the group identity.
It shall be possible to modify groups with SS-DGNA defined in FE1 or in FE2, even if the group is not
created with SS-DGNA.
The defined DGNA number shall be allocated by the FE2, if the number is not given by FE3.
The DEFINE information flow elements are described in table 1.
Table 1: Contents of DEFINE
Element Type
Defining authorized user M
Call identifier C
Defined group identity (identities) C
Reference to a pre-defined parameter set O
Additional authorized user(s) O
Acknowledged group call O
Broadcast group call O
Mnemonic group name O
Affected user(s) O
Acknowledgement request from aff. users O
Importance of group O
Group activation in MS/LS O
Duration of assignment O
3.2.1.1.2 DEFINE-ACK
The DEFINE-ACK information flow shall be for the relationship rb, rc and re. The flow shall be sent from
FE2 to FE3 or from FE2 to FE3 via FE4. The flow shall be used to acknowledge a previously sent DEFINE
request to a call related or call unrelated SS-DGNA definition.
The DEFINE-ACK information flow shall be used for both addition and modification acknowledgement.
The acknowledgement may be positive or negative indicating the result of the attempt to add/modify the
group number.
The DEFINE-ACK information flow elements are described in table 2.

---------------------- Page: 14 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 13
Draft prETS 300 392-11-22: September 1996
Table 2: Contents of DEFINE-ACK
Element Type
Receiving party address M
Call identifier C
Defined group identity (identities) M
Result for definition M
3.2.1.2 Deletion of SS-DGNA number and/or removal of affected users from the group
An authorized user can delete the group definition from the SwMI or from the SwMI and from all affected
users. Or, the authorized user can remove the group only from all or some affected users. The affected
users can be requested to acknowledge the removal request.
At the reception of SS-DGNA deletion request, FE2 can authenticate FE3 that made the request before
accepting the deletion. For that purpose, the general authentication procedures, that are defined for
TETRA in order to authenticate MS- or LS-subscribers, shall be used.
3.2.1.2.1 DELETE request
The DELETE information flow shall be for the relationship rb, rc and re. The flow shall be sent from FE3 to
FE2 or from FE3 to FE2 via FE4. The flow shall be used to delete groups from the system and de-assign
(remove) group identities from affected users.
The DELETE information flow elements are described in table 3.
Table 3: Contents of DELETE
Element Type
Deleting authorized user M
Deleted group identity (identities) M
Group deleted from SwMI M
Removal of group from affected users(s) M
Affected user(s) C
3.2.1.2.2 DELETE-ACK
The DELETE-ACK information flow shall be for the relationship rb, rc and re. The flow shall be sent from
FE2 to FE3 or from FE2 to FE3 via FE4. The flow shall be used to acknowledge a previously sent deletion
and/or removal request to a call related and call unrelated SS-DGNA number. The acknowledgement may
be positive or negative indicating the result of the attempt to delete and/or remove the group number.
The DELETE-ACK information flow elements are described in table 4.
Table 4: Contents of DELETE-ACK
Element Type
Deleting authorized user M
Deleted group identity (identities) M
Result for deletion M
3.2.1.3 DGNA assignment to affected users
The authorized user can make DGNA definitions to the SwMI only or to the SwMI and to the affected
users. These affected users can be requested to acknowledge these assignment requests or the requests
can be sent unacknowledged.
If the SwMI does not succeed in delivering the assignment(s) to affected user(s). The SwMI may, as an
operator option, send the request(s) to affected user(s) at a later time.

---------------------- Page: 15 ----------------------

SIST ETS 300 392-11-22 E1:2003
Page 14
Draft prETS 300 392-11-22: September 1996
At the reception of SS-DGNA assignment, FE1 can authenticate FE2 (FE4) that is making the request
before accepting the assignment. For that purpose, the general authentication procedures, that are
defined for TETRA in order to authenticate SwMI, shall be used.
3.2.1.3.1 ASSIGN request
The ASSIGN information flow shall be for the relationship ra, rc and rd. The flow shall be sent from FE2 to
FE1 or from FE2 to FE1 via FE4. The flow shall be used to add and modify a call related and call
unrelated SS-DGNA number to an affected user.
The addition and modification are done with the same information flow. The parameters included in a new
addition/modification override the previously defined parameters for the group. If a parameter is not given
in the request, the previously assigned parameter value shall be valid.
The ASSIGN information flow elements are described in table 5.
Table 5: Contents of ASSIGN
Element Type
Assigned affected user M
Added/modified group identity(ies) M
Acknowledgement requested for assignment O
Acknowledged group call O
Broadcast group call O
Mnemonic gr
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.'*1$Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 11: Supplementary services stage 2; Sub-part 22: Dynamic Group Number Assignment (DGNA)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:ETS 300 392-11-22 Edition 1SIST ETS 300 392-11-22 E1:2003en01-december-2003SIST ETS 300 392-11-22 E1:2003SLOVENSKI
STANDARD



SIST ETS 300 392-11-22 E1:2003



EUROPEANETS300392-11-22TELECOMMUNICATIONApril2000STANDARDSource:TETRAReference:DE/TETRA-03001-11-22ICS:33.020Keywords:Data,radio,speech,stage2,supplementaryservices,TETRA,V+DTerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part11:Supplementaryservicesstage2;Sub-part22:DynamicGroupNumberAssignment(DGNA)ETSIEuropeanTelecommunicationsStandardsInstituteETSISecretariatPostaladdress:F-06921SophiaAntipolisCEDEX-FRANCEOfficeaddress:650RoutedesLucioles-SophiaAntipolis-Valbonne-FRANCEInternet:[e-mail]-http://www.etsi.orgTel.:[phone]-Fax:[phone]CopyrightNotification:Nopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST ETS 300 392-11-22 E1:2003



Page2ETS300392-11-22:April2000Whilsteverycarehasbeentakeninthepreparationandpublicationofthisdocument,errorsincontent,typographicalorotherwise,mayoccur.Ifyouhavecommentsconcerningitsaccuracy,pleasewriteto"ETSIStandardsMakingSupportDept."attheaddressshownonthetitlepage.SIST ETS 300 392-11-22 E1:2003



Page3ETS300392-11-22:April2000ContentsForeword.51Scope.72Normativereferences.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.84Functionalmodel.84.1Functionalmodeldescription.84.2DescriptionofFEs.94.2.1Affecteduserfunctionalentity,FE1.94.2.2SS-DGNAfunctionalentity,FE2.94.2.3Authorizeduserfunctionalentity,FE3.94.2.4FunctionalentityFE2invisitedSwMI.94.3Relationshiptobasiccallfunctionalmodel.95Informationflows.105.1Generaloninformationflows.105.2DefinitionofSS-DGNAnumber.105.2.1DEFINE.105.2.2DEFINEACK.115.3ModificationofSS-DGNAnumberand/oradditionand/orremovalofaffectedusers.125.3.1MODIFY.125.3.2MODIFYACK.135.4DeletionofSS-DGNAnumber.135.4.1DELETE.135.4.2DELETEACK.135.5DGNAassignmenttoaffectedusers.145.5.1ASSIGN.145.5.2ASSIGNACK.155.6DGNAde-assignmentofaffectedusers.155.6.1DEASSIGN.155.6.2DEASSIGNACK.165.7Interrogation.165.7.1INTERROGATEGROUP.165.7.2INTERROGATEGROUPACK.175.7.3INTERROGATEGROUPMEMBERS.175.7.4INTERROGATEGROUPMEMBERSACK.185.7.5INTERROGATEMSGROUPS.185.7.6INTERROGATEMSGROUPSACK.195.8RelationshipofSS-DGNAinformationflowstobasiccallinformationflows.195.9Serviceprimitives.196Informationflowsequences.206.1InformationflowsequencesofcallunrelatedDGNAdefinition.206.1.1Successfuldefinition/modificationandgroupassignmentwhentheauthorizeduserisregisteredinthegrouphomesystem.206.1.2Successfuldefinition/modificationandgroupassignmentwhentheauthorizeduserisregisteredinanotherthanthegrouphomesystem.216.1.3Successfuldeletionanddeassigmentwhenauthorizeduserinthegrouphomesystem.226.1.4SuccessfuldeletionanddeassigmentwhenauthorizeduserinanotherthanthegrouphomeSwMI.236.2FEactionsofcallunrelatedDGNAdefinitionandoperation.23SIST ETS 300 392-11-22 E1:2003



Page4ETS300392-11-22:April20006.2.1FEactionsofFE1.236.2.2FEactionsofFE2.246.2.3FEactionsofFE3.246.2.4FEactionsofFE2invisitedSwMI.246.3InformationflowsequencesofcallrelatedDGNAdefinitionandassignment.256.3.1Definitionandoperationwhenauthorizeduserinthegrouphomesystem.256.3.2Definitionandoperationwhenauthorizeduserinanotherthanthegrouphomesystem.266.4FEactionsofcallrelatedDGNAdefinitionandoperation.266.4.1FEactionsofFE1.266.4.2FEactionsofFE2.266.4.3FEactionsofFE3.276.4.4FEactionsofFE2invisitedSwMI.276.5Informationflowsequencesofinterrogation.286.5.1Interrogationofgroupwhenauthorizeduseringrouphomesystem.286.5.2Interrogationofgroupwhenauthorizeduserinanotherthangrouphomesystem.286.5.3Interrogationofgroupmemberswhenauthorizeduseringrouphomesystem.296.5.4Interrogationofgroupmemberswhenauthorizeduserinanotherthangrouphomesystem.296.5.5SwMIInterrogationofMSgroups.306.5.6InterrogationofMSgroupswhenauthorizeduseringrouphomesystem.306.5.7InterrogationofMSgroupswhenauthorizeduseringrouphomesystem.316.6FEactionsofinterrogation.316.6.1FEactionsofFE1.316.6.2FEactionsofFE2.316.6.3FEactionsofFE3.326.6.4FEactionsofFEinvisitedSwMI.327AllocationofFEstophysicalequipment.328Inter-workingconsiderations.32History.33SIST ETS 300 392-11-22 E1:2003



Page5ETS300392-11-22:April2000ForewordThisEuropeanTelecommunicationStandard(ETS)hasbeenproducedbytheTerrestrialTrunkedRadio(TETRA)ProjectoftheEuropeanTelecommunicationsStandardsInstitute(ETSI).ThisETSconsistsof14partsasfollows:Part1:"Generalnetworkdesign";Part2:"AirInterface(AI)";Part3:"InterworkingattheInter-SystemInterface(ISI)";Part4:"Gatewaysbasicoperation";Part5:"PeripheralEquipmentInterface(PEI)";Part6:"LineconnectedStation(LS)";Part7:"Security";Part9:"Generalrequirementsforsupplementaryservices";Part10:"Supplementaryservicesstage1";Part11:"Supplementaryservicesstage2";Part12:"Supplementaryservicesstage3";Part13:"SDLmodeloftheAirInterface(AI)";Part14:"ProtocolImplementationConformanceStatement(PICS)proformaspecification".TranspositiondatesDateofadoptionofthisETS:31March2000DateoflatestannouncementofthisETS(doa):30June2000DateoflatestpublicationofnewNationalStandardorendorsementofthisETS(dop/e):31December2000DateofwithdrawalofanyconflictingNationalStandard(dow):31December2000SIST ETS 300 392-11-22 E1:2003



Page6ETS300392-11-22:April2000BlankpageSIST ETS 300 392-11-22 E1:2003



Page7ETS300392-11-22:April20001ScopeThisEuropeanTelecommunicationStandard(ETS)definesthestage2specificationsoftheSupplementaryServiceDynamicGroupNumberAssignment(SS-DGNA)fortheTerrestrialTrunkedRadio(TETRA).TheSS-DGNAenablesausertodynamicallydefinegroupidentitiesandgrouprelatedparameterstotheTETRAsystemandtothesubscribersinthesystem.Thesedefinitionsareusedtoenablegroupcallinvocationstodynamicallydefinedgroups.ThisETSspecifiesthecreation,modification,deletionandinterrogationofgroupdefinitionsintheSwitchingandManagementInfrastructure(SwMI),intheMobileStation(MS)andintheLineStation(LS).TheoperationscanbemadewithinoneTETRAsystemorovertheInterSystemInterface(ISI).ThisspecificationdoesnotincludethespecificationforaccesspriorityusedforrandomaccessinuplinkandcallpriorityusedbySwMIforresourceallocationforagroup.AccesspriorityandcallprioritycanbespecifiedforgroupsusingSupplementaryServiceAccessPriority(SS-AP),SupplementaryServicePriorityCall(SS-PC)andSupplementaryServicePre-emptivePriorityCall(SS-PPC).Man-MachineInterface(MMI)andChargingprinciplesareoutsidethescopeofthisETS.Stage2describesthefunctionalcapabilitiesoftheSupplementaryServiceintroducedinstage1description.Stage2identifiesthefunctionalcapabilitiesforthemanagementoftheserviceintheSwMI,intheMSandintheLS.Stage2describestheinformationflowsexchangedbetweentheseentities,anditalsodescribestheflowssentovertheISI.NOTE:Thestage2descriptionisfollowedbythestage3description,whichspecifiestheencodingrulesfortheinformationflowsandprocessbehaviourforthedifferententitiesinSwMI,MSandLSoftheservice.2NormativereferencesThisETSincorporatesbydatedandundatedreference,provisionsfromotherpublications.Thesenormativereferencesarecitedattheappropriateplacesinthetextandthepublicationsarelistedhereafter.Fordatedreferences,subsequentamendmentstoorrevisionsofanyofthesepublicationsapplytothisETSonlywhenincorporatedinitbyamendmentorrevision.Forundatedreferencesthelatesteditionofthepublicationreferredtoapplies.[1]ETS300392-2:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part2:AirInterface(AI)".[2]ETS300392-1:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part1:Generalnetworkdesign".[3]ETS300392-12-22:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part12:Supplementaryservicesstage3;Sub-part22:DynamicGroupNumberAssignment(DGNA)".[4]ETS300392-10-22:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part10:Supplementaryservicesstage1;Sub-part22:Dynamicgroupnumberassignment".[5]ETS300392-7:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part7:Security".[6]ETS300392-9:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part9:Generalrequirementsforsupplementaryservices".[7]ETS300392-7:"TerrestrialTrunkedRadio(TETRA);VoiceplusData(V+D);Part7:Security".SIST ETS 300 392-11-22 E1:2003



Page8ETS300392-11-22:April20003Definitionsandabbreviations3.1DefinitionsForthepurposesofthisETS,thefollowingtermsanddefinitionsapply:affecteduser:identifiedMSorLSusertowhichthesupplementaryserviceoperationassignsordeassignsthegroupnumberNOTE:Insomespecificcases,thetermaffectedusersmayapplytoallthe(assigned)usersofanexistinggroup.authorizeduser:userwhoisauthorizedtodefine,modify,deleteandinterrogateSS-DGNAnumberscallrelatedDGNA:creationofagroupcomprisingtheparticipantsinacallcallunrelatedDGNA:creationofagroupbasedonidentitiesDGNAnumber:groupnumberadded,modified,deletedand/orinterrogatedwithSS-DGNA3.2AbbreviationsForthepurposesofthisETS,thefollowingabbreviationsapply:CCCallControlCCACallControl(functionalentityAgent)DGNADynamicGroupNumberAssignmentFEFunctionalEntityGSSIGroupShortSubscriberIdentityGTSIGroupTETRASubscriberIdentityISIInter-SystemInterfaceLSLineStationMSMobileStationSSSupplementaryServiceNOTE:TheabbreviationSSisonlyusedwhenreferringtoaspecificsupplementaryservice.SwMISwitchingandManagementInfrastructure4Functionalmodel4.1FunctionalmodeldescriptionThefunctionalmodelshallcomprisethefollowingFunctionalEntities(FEs):-FE1Affecteduserfunctionalentity;-FE2DynamicGroupNumberAssignment(DGNA)functionalentityinhomeSwMIandinvisitedSwMI;-FE3Authorizeduserfunctionalentity.ThefollowingrelationshipsshallexistbetweentheseFEs:-rabetweenFE1andFE2;-rbbetweenFE2andFE3.SIST ETS 300 392-11-22 E1:2003



Page9ETS300392-11-22:April2000Figure1showstheseFEsandtheirrelationships.rbraFE3FE2FE1authorisedSS-DGNAaffecteduserFEuserFigure1:FunctionalmodelforSS-DGNA4.2DescriptionofFEs4.2.1Affecteduserfunctionalentity,FE1TheFEthatservestheaffecteduserforDGNAnumberassignment,deassignmentandinterrogations.4.2.2SS-DGNAfunctionalentity,FE2TheFEwithinthenetworkwhichensuresSS-DGNAoperations:assignment,deassignment,definition,deletion,modificationandinterrogationsinthehomeSwMIofthegroupforwhichSS-DGNAhasbeeninvoked.ThisFEalsodistributesassigment/de-asssignmentrequeststoFEsinvisitedSwMIs.4.2.3Authorizeduserfunctionalentity,FE3TheFEthatservestheauthorizeduserforDGNAnumbercallrelatedandcallun-relateddefinitions,deletion,modificationandinterrogations.Someoftheauthorizedusercapabilitiesmaybeallocatedtotheaffectedusere.g.tointerrogatehisowngroups.4.2.4FunctionalentityFE2invisitedSwMITheFEwithinthenetworkwhichensuresSS-DGNAoperations:assignment,deassignment,definition,deletion,modificationandinterrogationsinanotherthanhomeSwMIofthegroupforwhichSS-DGNAhasbeeninvoked.ThisFEalsodistributesassigment/de-asssignmentrequeststoFEsinthatSwMI.4.3RelationshiptobasiccallfunctionalmodelIncaseofcallrelatedSS-DGNAFE3shallbecollocatedwiththeauthorizeduserCCAwhenthissupplementaryserviceisdefinedandtheninvoked.NOTE:FE1isnotcollocatedwiththeaffecteduserCCAbecauseFE1doesnothaveanyfunctionduringthedefinitionandinvocationofSS-DGNAandtheassignmentisindependentofthecallalthoughacallrelatedsignallingmaybeutilized.IncaseofcallrelatedSS-DGNAFE2shallbecollocatedwithaCCentitywhichwillprovideFE2withthegroupcomposition.rbraFE3FE2FE1CCACCaffectedauthorisedSS-DGNAuseruserFEFigure2:TherelationshipsbetweenthebasicserviceandcallrelatedSS-DGNAFEsSIST ETS 300 392-11-22 E1:2003



Page10ETS300392-11-22:April20005Informationflows5.1GeneraloninformationflowsThedefinitionsofinformationflowsdefinetheinformationalcontentsexchangedbetweenthedifferentfunctionalentities.Inthetableslistingtheelementsininformationflows,thecolumnheadedtypeindicateswhichoftheseelementsaremandatory"M",conditional"C"oroptional"O".Theresponse/confirmationinformationflowsforconfirmedinformationflows(e.gdefinitionorinterrogationrequests)havebeennameddifferentlyfromthecorrespondingrequest/indicationinformationflowsothatthesamenamescanbeusedforthecorresponding(stage3)PDUmessages.Howeverthisdifferenceconsistsonlyintheadditionoftheextension"ACK"afterthenameofthecorrespondingrequest/indicationinformationflow.Thedetailsoftheelementvaluesaredescribedinstage3asserviceprimitiveparametervalues,refertoETS300392-12-22[3]subclause5.4.5.2DefinitionofSS-DGNAnumberCallrelatedandcallunrelatedDGNAnumbersshallbecreatedusingtheDEFINErequest/indicationinformationflow.Forcallunrelated-DGNAnumberdefinition,theparticipantsinthegroupandthecorrespondinggroupparametersmaybeincludedinthisinformationflowormodificationinformationflowwillbeusedlaterforcompletionofthedefinition.ForthecreationofacallrelatedDGNAgroup,theuserscurrentlyparticipatinginthegroupcall(butnotthosenominallyinthegroupandnotparticipatinginthecall,e.g.becausetheywerenotpoweredon,ortheyhadnotattachedtothegroup)shallbeimplicitlydefinedasaffectedusers,andthecorrespondinggroupparametersshallbeimplicitlydefinedasbeingthoseofthegroupcall.ThusthereisnoneedtoincludetheseusersorparametersinthecorrespondingDEFINEinformationflow.However,itshallbepossiblefortheauthorizedusertoaddaffecteduserstothisgroupindefiningtheirgroupparametersand/ortochangesomecommongroupparameters(comparedtothoseofthegroupcall),inexplicitlyincludingtheseusersand/orparametersintheDEFINErequest/indicationinformationflowusedtodefinethecallrelatedDGNAnumber.CallrelatedDGNAnumberdefinitionshallbeendedafterthissingleDEFINErequest/indicationinformationflowhasbeenacknowledged,i.e.anyadditionalmodificationshallbepartofcallunrelatedSS-DGNAdefinition.5.2.1DEFINEDEFINEisaconfirmedinformationflowacrossrelationshiprbfromFE3toFE2.NOTE:Theresponse/confirmationinformationflowcorrespondingtotheDEFINErequest/indicationinformationflowisDEFINEACK(seesubclause4.1).TheDEFINErequest/indicationinformationflowshallbeusedtodefineacallunrelatedorcallrelatedDGNAnumber,withthepossibilityinthelattercasetoaddaffecteduserstotheDGNAnumberbeingdefinedand/ortochangesomecommongroupparameters(comparedtothoseofthegroupcall),atthesametime.Theparametersincludedinthedefinitionrequestshalloverridethecallparameters,ifany.Ifaparameterisnotgivenintherequest,adefaultvalueshallbevalidfortheDGNAnumber.InthecaseofcreationofaSS-DGNAgroup,theauthorizedusershalldeterminethenumberwhichshallbeincludedintheDEFINErequest/indicationinformationflow,unlessasanoption,FE2canallocateit.Ifthisoptionissupported,thenumberofthegroupbeingdefinedbySS-DGNAdoesnotneedtobeincludedintheDEFINErequest/indicationinformationflow:ifithasnotbeenincluded,FE2shallfindavalidgroupnumber,makethedefinitionforthatnumberandreturnittoFE3intheDEFINEACKinformationflow.SIST ETS 300 392-11-22 E1:2003



Page11ETS300392-11-22:April2000IfFE2supportsthisoption,itshouldcheckwhethertheDEFINErequest/indicationinformationwouldnotresultincreatingagroupwiththesamecompositionasanalreadyexistingone.Table1liststheelementswithintheDEFINErequest/indicationinformationflow.Table1:ContentsofDEFINEinformationflowElementTypeCallrelatedorcallunrelatedMCallidentifierC(note1)GroupidentityO(note2)SetreferenceOGroupmnemonicnameOSecurityrelatedgroupinformationOAdditionalgroupinformationOGroupidentityattachmentmodeOGroupidentityattachmentmodeOClassofusageOAcknowledgementrequestfromaffectedusersOAffecteduseridentity/identitiesO(note3)NOTE1:Thisinformationelementshallbepresentonlywhenthedefinitioniscallrelated.NOTE2:Thiselementshallbeincludedunlessasanoption,FE2canallocateit:ifthisoptionissupported,thiselementdoesnotneedtobeincluded.NOTE3:ThiselementmaybeincludedfortheadditionofaffecteduserstothegroupbeingcreatedbycallrelatedSS-DGNA.ItshallalsobeincludedforcallunrelatedSS-DGNAdefinitionofgroupmembers.Asanoptionthiselementmaybeagroupidentity.Itmaybeagroupidentity.5.2.2DEFINEACKDEFINEACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheDEFINErequest/indicationinformationflow.ItisthusacrossrelationshiprbfromFE2toFE3.DEFINEACKinformationflowshallbeusedtoacknowledgeagroupdefinition.TheacknowledgementshallindicatewhethertheresultoftheDEFINEinformationflowhasbeenpositiveornegative.IftheDEFINEinformationflowdidnotincludeadefinedgroupidentityandiftheresultispositive,thegroupnumberallocatedbyFE2shallbeincludedintheDEFINEACKinformationflow.NOTE:ThedefinitionofhowagivenDEFINEACKinformationflowrelatestothecorrespondingDEFINEinformationflowisoutsidethescopeofthestage2description:itwillbegiveninthestage3description,seesubclause4.1.Iftheresultofdefinitionisdifferentfordifferent(set)ofaffectedusers,thentherewillbemultipleDEFINEACKinformationflowsduetoasingleDEFINEinformationflow.SIST ETS 300 392-11-22 E1:2003



Page12ETS300392-11-22:April2000Table2liststheelementswithintheDEFINEACKinformationflow.Table2:ContentsofDEFINEACKinformationflowElementTypeCallrelatedorcallunrelatedMCallidentifierC(note1)GroupidentityMAcknowledgementcompleteMResultofdefinitionMAffecteduseridentity/identitiesO(note2)NOTE1:Thisinformationelementshallbepresentonlywhenthedefinitioniscallrelated.NOTE2:Thiselementisincludedtoidentifytheaffectedusersforwhichtheresultofdefinitionisapplicable.5.3ModificationofSS-DGNAnumberand/oradditionand/orremovalofaffectedusers5.3.1MODIFYMODIFYisaconfirmedinformationflowacrossrelationship(s)rbfromFE3toFE2.NOTE:Theresponse/confirmationinformationflowcorrespondingtotheMODIFYrequest/indicationinformationflowisMODIFYACK(seesubclause4.1).TheMODIFYinformationflowshallbeusedtoadd(assign)affecteduserstoanexistinggrouporremove(deassign)affectedusersfromanexistinggroup,whetherthisgrouphasbeencreatedbySS-DGNAorbyoperator,and/ortochangesomegroupparameterseithercommontoallassignedusersorspecifictosomeaffectedusers.Theparametersincludedinamodificationrequestshalloverridethepreviouslydefinedparameters.Ifaparameterisnotgivenintherequest,thepreviouslydefinedparametervalueshallbevalidforthegrouporaffecteduseridentity.Table3liststheelementswithintheMODIFYrequest/indicationinformationflow.Table3:ContentsofMODIFYinformationflowElementTypeGroupidentityMSetreferenceOMnemonicgroupnameOSecurityrelatedinformationOAdditionalgroupinformationOGroupidentityattachmentmodeOClassofusageOAssignedaffecteduseridentity/identitiesO(note1)AcknowledgementrequestfromtheassignedaffectedusersODeassignedaffecteduseridentitiesO(note2)AcknowledgementrequestfromdeassignedaffectedusersONOTE1:Thiselementshallbeincludedfortheadditionofaffecteduserstoanexistinggrouporforchangeofclassofusageand/orgroupidentityattachmentmodeparametersofthoseaffectedusers.Asanoptionthiselementmaybeagroupidentity.NOTE2:Thiselementshallbeincludedfortheremovalofaffectedusersfromanexistinggroup.Asanoptionthiselementmaybeagroupidentity.SIST ETS 300 392-11-22 E1:2003



Page13ETS300392-11-22:April20005.3.2MODIFYACKMODIFYACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheDEFINErequest/indicationinformationflow.Itisthusacrossrelationship(s)rbfromFE2toFE3.MODIFYACKinformationflowshallbeusedtoacknowledgetheadditionofaffectedusersand/orthemodificationofsomegroupparametersand/orremovalofaffectedusers.TheacknowledgementshallindicatewhethertheresultoftheMODIFYinformationflowhasbeenpositiveornegative.NOTE:TheMODIFYACKinformationflowrelatestothecorrespondingMODIFYinformationflowbythegroupidentity,seesubclause4.1.Table4liststheelementswithintheMODIFYACKinformationflow.Table4:ContentsofMODIFYACKinformationflowElementTypeGroupidentityMResultofmodificationMAcknowledgementcompleteMAffecteduseridentity/identitiesO5.4DeletionofSS-DGNAnumberTheauthorizedusershallusecallunrelatedSS-DGNAtodeletethegroupdefinitionfromtheSwMIandinadditionmayuseittoremove(deassign)alsothegroupfromallorsomeaffectedusers.5.4.1DELETEDELETEisaconfirmedinformationflowacrossrelationshiprbfromFE3toFE2.Itshallbeusedtodeleteagroupfromthesystemandoptionallyremove(deassign)thegroupfromallorfromsomeaffectedusers.NOTE:TheDELETEACKresponse/confirmationinformationflowrelatestothecorrespondingDELETErequest/indicationinformationflowbythegroupidentity,seesubclause4.1.Table5liststheelementswithintheDELETErequest/indicationinformationflow.Table5:ContentsofDELETEinformationflowElementTypeGroupidentityMGroupdeassignmentfromaffectedusersMAffectedusersO(notes1and2)AcknowledgementrequestedfromaffectedusersO(note1)NOTE1:Thiselementmaybepresentonlywhenadeassignmentfromaffectedusersisindicated.NOTE2:Asanoptionthiselementmaybeagroupidentity.5.4.2DELETEACKDELETEACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheDELETErequest/indicationinformationflow.Itisthusacrossrelationshiprb.DELETEACKinformationflowshallbeusedtoacknowledgeagroupdeletionandoptionalremoval(deassignment)ofthegroupfromaffectedusers.TheacknowledgementshallindicatewhethertheresultoftheDELETEinformationflowhasbeenpositiveornegative.NOTE:TheDELETEACKinformationflowrelatestothecorrespondingDELETEinformationflowbythegroupidentity,seesubclause4.1.SIST ETS 300 392-11-22 E1:2003



Page14ETS300392-11-22:April2000Table6liststheelementswithintheDELETEACKinformationflow.Table6:ContentsofDELETEACKinformationflowElementTypeGroupidentityMResultofdeletionM5.5DGNAassignmenttoaffectedusersOncetheauthorizeduserhascreatedaSS-DGNAgrouporhasaddedaffecteduserstoanexistinggroupormodifiedgroupparameters,FE2shallsendtheASSIGNrequest/indicationinformationflowtoaffecteduserstoassignittothegroup,togetherwithitsdefinedgroupparametersasindicatedinthecorrespondingDEFINEorMODIFYinformationflow.TheassigmentoperationshallbethesamewhethertheSS-DGNAdefinitionhasbeencallrelatedorcallunrelated.WhentheonlymodificationchangesmadearegroupparameterschangestheSwMImayinformthechangestotheaffectedFE1sinanASSIGNinformationflowasdefinedintheMODIFYinformationflow.Theaffectedusermayormaynotberequestedtoacknowledgetheassignmentrequest.IfFE2doesnotsucceedindeliveringtheassignmenttotheaffecteduser,FE2may,asanoption,sendtherequesttotheaffecteduseratalatertime.5.5.1ASSIGNASSIGNisaninformationflowacrossrelationshiprafromFE2toFE1.DependingonwhetherornotanacknowledgementisrequestedintheASSIGNrequest/indicationinformationflow,ASSIGNshallorshallnotbeaconfirmedinformationflow.NOTE:WhenASSIGNisaconfirmedinformationflow,theresponse/confirmationinformationflowASSIGNACKcorrespondstotheASSIGNrequest/indicationinformationflowbythegroupidentity/identities,seesubclause4.1.Iftheassignmentismadetogroupmembers,FE2maysendthisinformationflowtoallgroupmembersusingindividualorgroupaddressing.ThegroupparametersincludedintheASSIGNrequest/indicationinformationfloweithershallbeneworshallmodifypreviouslydefinedones.Ifaparameterisnotgivenintherequest,thepreviouslyassignedorifnoassignedvalueavailableadefaultparametervalueshallbevalid.Table7liststheelementswithintheASSIGNrequest/indicationinformationflow.Table7:ContentsofASSIGNinformationflowElementTypeAdded/modifiedgroupidentity/identitiesMAcknowledgementrequestedfromaffecteduserMGroupidentityattachmentmodeM(note1)ClassofusageOMnemonicgroupnameOSecurityrelatedinformationOAdditionalgroupinformationOVisitedSwMITETRAidentityofthegroup,(V)GSSIO(note2)NOTE1:Thedetailsofthatelementisdefinedinstage3.NOTE2:ThiselementshallbepresentiftheaffecteduserisinavisitedSwMIonthegroupidentitypointofviewandthegroupisattachedasdefinedbyGroupidentityattachmentmodeelement.SIST ETS 300 392-11-22 E1:2003



Page15ETS300392-11-22:April20005.5.2ASSIGNACKASSIGNACKisactuallytheresponse/confirmationinformationflowcorrespondingtotheASSIGNrequest/indicationinformationflowwhenASSIGNisaconfirmedinformationflow.ItisthusacrossrelationshiprafromFE1toFE2.TheASSIGNACKinformationflowshallbeusedtoacknowledgeagroupassignmenttotheaffectedusertogetherwiththecorrespondinggroupparameterssenttothisuser.ItshallindicatewhethertheresultoftheASSIGNinformationflowhasbeenpositiveornegative.Table8liststheelementswithintheASSIGNACKinformationflow.Table8:ContentsofASSIGNACKinformationflowElementTypeAssignedgroupidentity/identitiesMResultofassignmentM(note)ResultofattachmentM(note)NOTE:Theresultmaybedifferenttoeachassignedgroupidentity.5.6DGNAde-assignmentofaffect
...