The present document studies use cases that assess under which circumstances interconnected MCX Service Systems exchange administrative and security relevant data and information.
Its objective is to identify new potential requirements related to the use cases and new high-level security requirements related to interconnection of MCX Service Systems and migration of MCX Users and MCX Service Groups.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
For the purposes of the present document, the terms given in TR 21.905
and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905
For the purposes of the present document, the following symbols apply:
For the purposes of the present document, the abbreviations given in TR 21.905
and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905
Considering public safety users specifically, different scenarios of public safety broadband wireless communications systems deployments will emerge, but some requirements remain common. In international or multi agency collaboration scenarios public safety MCX Service Users are required to roam or migrate from one system to another, need to use MCX Services or be included in specific communication events in a Partner MCX Service System on a temporary basis.
Public safety may also deploy their own mobile, local, countrywide or national broadband communications systems. In order to grant visiting MCX Service Users access to a Partner MCX Service System and its services, a mechanism is required which allows the request and/or transmission of administrative configuration data, to be exchanged between connected MCX Service Systems. This type of administrative configuration data is used for adding MCX Service Users into a Partner MCX Service System's user database and for enabling or disabling certain services. Relevant information can be exchanged prior to the visiting MCX Service Users arriving from a Partner MCX Service System or dynamically during events for example.
Such mechanism can be realised with the administrative configuration data and information exchange concept, discussed in this study.