GA/T 1365-2017Police digital trunking communication system - Technical specifications for network management (English PDF)

3.1 Terms and definitions

The following terms and definitions apply to this document.

3.2 Abbreviations

The abbreviations as defined in GA/T 1056, as well as the following abbreviations, apply to this document. For ease of use, some abbreviations in GA/T 1056 are repeated below.

4.1 Architecture

The network management system of the police digital trunking adopts a three-level network management structure, as shown in Figure 1.

4.2 Classification of network management centers

Network management centers are divided into the following three types.

4.3 Classification of network management interfaces

5.1 Functional description

5.1.1 User management

User management shall include the following contents of management and configuration of user rights to use system resources.

5.1.2 Device management

Device management shall include the following contents of information statistics, parameter configuration, data maintenance of the device in the system.

5.1.3 Performance management

The network management center shall provide a basis for system optimization, through statistics and analysis of the following performance data.

5.1.4 Alarm management

Alarm management shall include the following contents. monitoring operation status, collecting alarm information, assisting in fault location, ensuring the normal operation of the system.

5.1.5 Security management

To ensure the security of the network management system, the following measures shall be taken for security management.

a) Database backup.

5.2 Functional requirements

The network management functions of network management centers at all levels shall comply with the provisions of Table 1.

6.1 Interface description

The network management interface is used for data transmission between two-level network management centers, including reporting various types of data from the lower- level network management center to the upper-level network management center, as well as sending configuration or query instructions from the upper-level network management center to the lower-level network management center.

6.2 Interface requirements

6.2.1 Interface protocol requirements

6.2.2 Interface service requirements

6.2.2.1 Namespace

The namespace shall be "http.//[domain name]/[service name]", or "https.//[domain name]/[service name]" where there are security requirements.

6.2.2.2 Calling method

When calling the interface service, the URL shall be "[namespace]/[interface operation name]".

6.2.2.3 Custom parameter requirements

The custom parameter settings of the interface service shall meet the following requirements.

6.2.3 Call of interface service

6.2.3.1 Call process description

The parameter setting requirements during the interface service call process are shown in Appendix C.

6.2.3.2 Call test operation process

Before using the service provided by the server system, the client system can determine whether the server system service has been deployed, by calling the test operation (isAlive) to determine whether the other methods called are currently working properly, see Figure 2.

6.2.3.3 Task customization operation flow

The upper-level network management center customizes tasks to the lower-level network management center, through the taskDistribute operation, including the creation, modification, synchronization, deletion of fault tasks, performance indicator tasks, topology tasks, as shown in Figure 3.

6.2.3.5 Task synchronization operation flow

The lower-level network management center can initiate a task synchronization request, through the taskSync operation, as shown in Figure 5.

6.2.3.7 Topology data reporting operation flow

The upper-level network management center pre-customizes the topology task to the lower-level network management center, through the task customization operation.

When the conditions for topology reporting are met, the lower-level network management center calls the topReport operation of the upper-level network management's ReportTopService, to report the topology data to the upper-level network management, as shown in Figure 7.

6.2.3.8 Performance data reporting operation flow

The upper-level network management center pre-customizes the performance task to the lower-level network management center, through the task customization operation.

When the conditions for performance reporting are met, the lower-level network management center calls the pefReport operation of the upper-level network management's ReportPefService, to report the performance data to the upper-level network management, as shown in Figure 8.

6.2.3.10 Customized task data reporting operation flow

The customized task data reporting process is shown in Figure 10.The upper network management center customizes the data reporting task to the lower network management center.

6.2.3.11 Supplementary reporting operation flow

If the indicator data cannot be fully transmitted to the upper network management center within the specified time due to network reasons or other reasons, the upper network management center and the lower network management center will make a supplementary report in one of the following two ways.

Appendix A (Normative)

Ministry-province interface service

A.1 Overview

Ministry network management centers and province network management centers provide services in the form of web service interfaces. Ministry-province network management interface services are divided into 9 categories, see Table A.1.

A.2 Interface service

A.2.1 Province task service

A.2.2 Province user services

A.2.2.1 User roaming rights configuration operation

The priority and rights of mobile stations roaming from the ministry network management center to the province network management center in the roaming area.

The specific requirements are as follows.

A.2.2.2 User roaming rights deletion operation

Used for the province network management center to delete the roaming mobile station permissions to the city network management center. The specific requirements are as follows.

A.2.2.3 System-level cross-system group call area configuration operation

Used for the ministry network management center to configure the cross-system group call area to the province network management center, the specific requirements are as follows.

Table A.20 -- Input parameters for system-level cross-system group call area configuration operation

Parameter name Parameter type Parameter description Attribute id int Talk group ID, all base stations in the system, valid for a long time M priority int Parameter value can be "0", "1", "2", "3", the larger the number, the higher the level M roamToList list String type exchange center domain name M

......