|
US$279.00 · In stock
Delivery: <= 3 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 36622.1-2018: Smart city -- Support platform for public information and services -- Part 1: General requirements
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 36622.1-2018 | English | 279 |
Add to Cart
|
3 days [Need to translate]
|
Smart city -- Support platform for public information and services -- Part 1: General requirements
| Valid |
GB/T 36622.1-2018
|
PDF similar to GB/T 36622.1-2018
Basic data | Standard ID | GB/T 36622.1-2018 (GB/T36622.1-2018) | | Description (Translated English) | Smart city -- Support platform for public information and services -- Part 1: General requirements | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L67 | | Classification of International Standard | 35.240.01 | | Word Count Estimation | 14,136 | | Date of Issue | 2018-10-10 | | Date of Implementation | 2019-05-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 36622.1-2018: Smart city -- Support platform for public information and services -- Part 1: General requirements
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Smart city - Support platform for public information and services - Part 1.General requirements
ICS 35.240.01
L67
National Standards of People's Republic of China
Smart city public information and service support platform
Part 1.General requirements
2018-10-10 released
2019-05-01 Implementation
State Administration of Market Supervision and Administration
Issued by the National Standardization Administration of China
Table of contents
Foreword Ⅰ
Introduction Ⅱ
1 Scope 1
2 Normative references 1
3 Terms and definitions 1
4 Abbreviations 1
5 Overall reference frame 2
6 Technical support 2
6.1 ICT infrastructure access 2
6.2 Data Support 3
6.3 Environmental Support 5
7 Data and Service Management 5
7.1 Data Management 5
7.2 Service Management 6
7.3 Data and Service Resources 8
8 Ability Open 9
8.1 Resource authorization 9
8.2 Confirmation of resources 9
8.3 Resource Gateway 9
8.4 Portal display 9
8.5 Circulation Management 10
8.6 Development Environment 10
8.7 Operating environment 10
9 Security Management 10
10 Operation and Maintenance Management 10
Smart city public information and service support platform
Part 1.General requirements
1 Scope
This part of GB/T 36622 specifies the overall reference framework, technical support, and data of the smart city public information and service support platform
And overall requirements for service management, capability opening, security management, operation and maintenance management, etc.
This part is applicable to the planning and construction of smart city public information and service support platform projects.
2 Normative references
The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article
Pieces. For undated reference documents, the latest version (including all amendments) is applicable to this document.
GB/T 22239 Information Security Technology Information System Security Level Protection Basic Requirements
GB/T 28827.1 Information Technology Service Operation and Maintenance Part 1.General Requirements
GB/T 29263-2012 Information Technology Service-Oriented Architecture (SOA) Application General Technical Requirements
GB/T 32419.3 Information Technology SOA Technical Implementation Specification Part 3.Service Management
GB/T 34678 Smart City Technical Reference Model
3 Terms and definitions
The following terms and definitions apply to this document.
3.1
Public information and service support platform supportplatformforpublicinformationandservices
Relying on scalable ICT infrastructure, under the guarantee of security and operation and maintenance mechanisms, to achieve unified access and access to shared data and services,
An information system that provides the data and service capabilities required for the opening of smart city applications.
XML. Extensible Markup Language (ExtensibleMarkupLanguage)
5 Overall frame of reference
The smart city public information and service support platform provides basic services for the city through technical support, data and service management, and capacity opening.
The overall framework is shown in Figure 1.According to Figure 1, the platform consists of ICT infrastructure, technical support, data and service management, capability opening, and smart applications.
It consists of 8 parts. application, user, security management, and operation and maintenance management.
The various parts are described as follows.
a) Technical support. Follow the principles of regionalization, hierarchization and modularization to achieve scientific management and service of ICT infrastructure access
It also improves the scalability, security and manageability of the bearer business system through environmental support and data support.
b) Data and service management. The platform relies on technical support to realize data catalog management, modeling, integration, association, metadata management, etc.
Function, to realize the functions of service catalog management, aggregation, evaluation, integration, use, interaction, life cycle management and so on. Simultaneous passes
Data resources, API resources, microservice resources, etc. provide support for the platform's external services.
c) Capability opening. The platform uses resource authorization, resource confirmation, resource gateway, portal display, circulation management, development environment, and operating environment
It is provided to various smart applications in a unified interface, and can be dynamically adjusted according to business development needs.
d) Security management. a general term for mechanisms and strategies to ensure the safe operation of public information and service support platforms for smart cities.
e) Operation and maintenance management. the monitoring of the platform operation and maintenance process and the guarantee of service quality.
Note 1.Technical support, data and service management, and capability opening (solid line box content) are the core of the platform and the core scope of the constraints of this section.
Note 2.ICT infrastructure, smart applications, and users (the content of the dashed box) are related to the platform and are not within the scope of this section.
6 Technical support
6.1 ICT infrastructure access
6.1.1 Overview
The specific requirements of the smart city public information and service support platform in terms of ICT infrastructure access are the same as those specified in GB/T 34678
Relevant requirements remain consistent.
6.1.2 Secure access
Secure access is used to connect devices to the platform. The functional requirements include.
a) Identity authentication. Before the platform establishes a secure connection to the device, the device should perform secure identity authentication;
b) Access control. The platform authenticates and authorizes the device.
6.1.3 Device management
Equipment management provides the management of equipment capabilities and information. The functional requirements include.
a) Device configuration. The configuration of device capabilities should be provided, including the discovery, use or prohibition of a device, etc. of device management objects and attributes;
b) Equipment diagnosis and monitoring. fault diagnosis of equipment capabilities shall be provided, including but not limited to.
1) Configuration of equipment diagnosis and monitoring parameters;
2) Retrieve device information used to identify device model, mode and manufacturer;
3) Retrieve the device information of the software and firmware installed on the device;
4) Retrieve the relevant information of the battery in the device;
5) Retrieve related information about the internal memory of the device;
6) Retrieve the event log of the device;
7) Device restart diagnosis operation;
8) Device factory reset diagnosis operation;
c) Device firmware management. The life cycle management function of device firmware should be provided, including firmware modules and accessories on the device (for example, configuration
Configuration file), the firmware life cycle includes downloading, updating or removing firmware;
d) Management equipment. functions such as adding, deleting, modifying, and querying equipment should be provided;
e) Device information management. The function of modifying the basic information of the device or the sensor to which the device belongs should be provided, including but not limited to the device name
Name, device user, device status, manufacturer, device location, device type, model, protocol type, etc.
6.1.4 Data reporting
Data reporting is to report the data collected by the device to the platform. The functional requirements should include. The device passes through the platform according to the predetermined parameters.
Report the collected data.
6.1.5 Command issuance
Command issuance provides control or sends commands to the device side. The functional requirements include.
a) The support platform should send command messages to the equipment to realize real-time control of the equipment.
b) The support platform should provide the issued control commands, and the specific format of the issued message needs to be customized by the application and the device.
6.1.6 Message Push
The message push provides the platform to push the messages subscribed by the device. The functional requirements should include. support the device to subscribe to the platform
When the station information changes, the platform pushes this message to the device, and the device performs corresponding processing operations based on the message.
6.2 Data support
6.2.1 Overview
Data support includes the functions of the public information and service support platform in data collection, storage, processing, and analysis.
6.2.2 Data Collection
Data collection function requirements include.
a) The collection of structured data and unstructured data should be supported;
b) Should support the collection of batch data, quasi real-time data and real-time data;
c) Should support the batch import and export of data and exchange between the platform and external data sources (such as relational databases, file servers, etc.)
data;
d) It should support the provision of task scheduling interfaces for third-party scheduling platforms to call;
e) Should support the customization of the data sender in the platform, collect data and write it to the data recipient (customizable);
f) Collection methods such as automatic collection, exchange, manual reporting, file upload, and interface call should be supported;
g) Should support unified management data collection on the platform, including data source, collection frequency, collection range, etc.
6.2.3 Data storage
Data storage function requirements include.
a) It should support massive data storage functions and provide a distributed storage system built on top of a distributed file system;
b) Should support high-throughput data access, support large-scale data integration applications, and be stored in a distributed file system
Provide fast retrieval and interactive query of the data;
c) Should support data warehouse functions, provide structured data storage services and basic data analysis services;
d) Basic operations on the file system should be supported, such as. file upload, file download, directory view, directory creation, directory deletion
Delete, file permission modification, etc.;
e) It should support multiple storage dimensions, including but not limited to KV type, relational type, file type, etc., and support data between different storage dimensions
The conversion;
f) Multi-tenancy should be supported, resource isolation and customized configuration should be supported;
g) Data encryption should be supported.
6.2.4 Data processing
Data processing function requirements include.
a) Data modeling capabilities should be provided, and data models should be customized according to business needs and metadata information;
b) The function of real-time or regular data extraction of various types of data according to customized conditions should be provided;
c) Visual data processing tools should be available, and the tools should be componentized;
d) Distributed data processing should be supported, and batch data processing and real-time streaming data processing capabilities should be provided;
e) A variety of mainstream data processing and computing frameworks should be supported, including but not limited to batch processing, interactive query, real-time streaming, memory computing
Calculate;
f) Should support memory-based high-performance distributed KV caching capabilities;
g) The ability to create, arrange, execute, and monitor data processing tasks should be supported;
h) A variety of data analysis capabilities should be provided, including but not limited to descriptive analysis, diagnostic analysis, predictive analysis, and causality analysis.
Analysis, etc.;
i) It should support multiple analysis modes, including but not limited to offline analysis, real-time analysis, interactive analysis, etc.;
j) The functions of data extraction, cleaning, conversion, and loading should be supported;
k) Should support data retrieval and query functions;
l) Various analysis methods, models and tools such as statistical analysis, machine learning, text analysis, and video analysis shall be provided;
m) Visual algorithms, tools, and component capabilities should be provided, including but not limited to interactive tables, highlight tables, histograms, box plots, and report tools.
Tools, BI tools, etc., to show the relationships, characteristics or trends that exist in the data;
n) Should support data mining algorithm library, graph processing algorithm library, etc.;
o) Data analysis process planning should be supported;
p) It should support interactive data analysis and mining capabilities in multiple languages such as SQL, Scala, R, and Python.
6.3 Environmental support
6.3.1 Overview
Environmental support includes database, middleware and application management requirements configured by the public information and service support platform according to business needs.
6.3.2 Database
Database function requirements include.
a) Distributed relational databases for structured data should be provided, which can effectively handle data volumes of PB or higher;
b) It should support the data processing performance requirements of users in multiple industries, and provide a cost-effective general-purpose computing platform for ultra-large-scale data management.
It can also be used to support various data warehouse systems, BI systems and decision support systems, and unified into the decision analysis of upper-level applications.
For service;
c) Should support the seamless connection of distributed relational databases and traditional relational databases and data warehouses;
d) Support large-scale parallel processing, support non-shared resource, fully symmetrical, distributed multi-node cluster architecture, system design without single
Point failure;
e) When the database node fails, the system automatically detects and switches over the fault, and the business is not interrupted;
f) Support row storage, column storage, KV storage, and support table storage in row or column format;
g) Support full-text search, support full-text data and row-column-stored table related queries;
h) Supports hierarchical storage of hot and cold data.
6.3.3 Middleware
Middleware should include but not limited to terminal emulation or screen conversion middleware, data access middleware, remote procedure call middleware, consumer
Information middleware, transaction middleware, object middleware, etc.
6.3.4 Application Management
Application management function requirements include.
a) Should support life cycle management from application modeling, orchestration and deployment to resource scheduling, elastic scaling, and monitoring and self-healing;
b) It should support the provision of a unified resource management and scheduling framework for the platform, which can perform resource management and scheduling for various applications;
c) The application development pipeline should be supported to open up the process from writing code submission to automatic compilation and packaging, continuous integration, and automatic deployment.
Series CI/CD full process automation;
d) Support applications can be automatically deployed in multiple environments such as containers, virtual machines, or bare metal.
7 Data and Service Management
7.1 Data management
7.1.1 Overview
Data management includes but is not limited to functional modules such as data catalog management, data modeling, metadata management, data integration, and data association.
7.1.2 Data Catalog Management
The data catalog management function requirements include.
a) According to different application themes, a data classification catalog should be formed to support classification category name management, category code management, etc.
Management of data classification catalog;
b) According to the content of public data, a data catalog should be formed in combination with relevant requirements to support metadata management, catalog compilation, and catalog distribution.
The management of data catalogs from the perspectives of distribution and catalog information maintenance.
7.1.3 Data Modeling
Data modeling function requirements include.
a) Mature data modeling techniques should be used to establish data models for smart city applications;
b) It should include determining the data and its related processes, defining the data, verifying the integrity of the data, defining the operation process, and selecting data storage
Technology and other processes;
c) Should include conceptual modeling, logical modeling and physical modeling;
d) Data modeling should be carried out from hierarchical model, network model and relational model.
7.1.4 Metadata Management
Data management and governance include the management and disposal of the acquisition, storage, quality, responsibility, authority, and monitoring of metadata and transaction data.
Its functional requirements include.
a) Should provide metadata management capabilities, support persistent storage of metadata, support the creation and maintenance of metadata organization models, and provide
Metadata content update maintenance, retrieval query, version control and other functions;
b) A metadata management system should be established to ensure the integrity, uniqueness, consistency, accuracy, legality, and timeliness of the collected data;
c) It should be ensured that there are multiple copies of metadata. When the copy is lost or damaged, the system will automatically detect and restore it;
d) Should be responsible for triggering accessibility updates of data or data sets in accordance with policy and legal requirements;
e) Basic operations such as adding, deleting, modifying, and checking metadata should be provided;
f) The life cycle management capabilities of metadata should be provided to support users to formulate clear data management strategies, processes and activities, and manage and
Control the creation, reception, distribution, use and destruction of data.
7.1.5 Data Integration
Data integration function requirements include.
a) It should provide automatic analysis and synthesis of multi-source data under certain criteria to complete the required decision-making and estimation tasks;
b) Should support multiple levels of data integration;
c) It should include basic functions such as correlation, estimation and identification;
d) Support the development of migration and configuration strategies for data state transition and disposal mechanisms, including the transfer of archived old data to lower
Level of storage, or removal of data, or marking of the original location of the data;
e) The relationship between the original data of data integration and model data should be managed.
7.1.6 Data Association
Data association function requirements include.
a) Find frequent patterns, associations, correlations or causal structures that exist between data should be provided;
b) Should include static data association and dynamic data association;
c) Should include the association of catalog data and the association of technical metadata.
7.2 Service Management
7.2.1 Overview
Service management includes but not only service catalog management, service aggregation, service life cycle management, service integration, service use, service
Functional modules such as evaluation and service interaction.
7.2.2 Service catalog management
Service catalog management function requirements include.
a) It should be compiled with a hierarchical directory structure;
b) A unified service catalog view should be provided;
c) The service catalog should be managed in accordance with the requirements of GB/T 32419.3.
7.2.3 Service aggregation
Service aggregation function requirements include.
a) The services of each service provider shall be accessed in accordance with the requirements of 7.3 and 7.8 of GB/T 29263-2012;
b) The adaptation and conversion function of common communication protocols should be provided;
c) A service catalog should be provided to support authorized users to view all business services and detailed information related to smart cities through the service catalog.
Information, support users to subscribe to the combination of services they are interested in;
d) Arrangement and routing of business service processes should be provided, and semantics such as sequence, condition, loop, and exception handling should be supported;
e) Should support service timing start and event start;
f) Service monitoring functions should be provided to monitor the running status of the aggregated business services, access success rate, access statistics, and access time
Distribution and access logs; for abnormal conditions, it can automatically alert and try to recover automatically according to the preset plan; the alert mode supports SMS,
Various methods such as mail and system messages.
7.2.4 Service life cycle management
Service life cycle management function requirements include.
a) The service registration function should be provided to support authorized users to register self-developed business services into the service catalog;
b) A service review and service release mechanism should be provided to support the business services registered by authorized users on the service catalog.
Release it to the public and provide it to the public or specific departments, specific roles, and specific users in accordance with the requirements of access control;
c) The service start/stop function should be provided to support system administrators or advanced authorized users to manually control the business services that are open to the outside world.
Start state;
d) The service cancellation function should be provided to close the business service that is no longer open. Users who subscribe to the service should receive the service cancellation
Notice that the business service after logout can no longer be accessed in the service catalog.
7.2.5 Service Integration
Service integration function requirements include.
a) The selection function of service routing should be provided, and routing methods such as point-to-point, publish and subscribe, and content-based routing should be supported;
b) The business service process orchestration function shall be provided, and the original service shall be combined into a new service through a certain logic, and the sequence, conditions, and cycle shall be supported.
Semantics such as loop and exception handling;
c) Functional support at the system engine level should be provided;
d) The node catalog and basic information should be provided for the service management nodes in the platform, and for the registration and exit of nodes, as well as global parameters.
Provide tools for data configuration;
e) Distributed coordination of service management nodes should be performed, and the synchronization of attributes such as data, heartbeat, and time should be maintained, and service management nodes should be provided
Synchronization function ensures node consistency;
f) The identity recognition function of the service management node should be provided to ensure that the node is not maliciously hijacked by a third party and protect the security of the platform.
7.2.6 Service use
Service use function requirements include.
a) An authentication interface should be provided to support authentication of upper-layer applications;
b) A user interface should be provided to support the direct activation, configuration, and deactivation of the device and the use of various functions of the device by the upper-level application;
c) A management interface should be provided to support upper-layer applications to query, schedule, and manage devices through the interface;
d) A query interface should be provided to support upper-layer applications to perform statistical analysis on the device through the interface;
e) Provide unified management of smart city services from service permissions, operating status, and configuration information;
f) Service authority control should be provided to authenticate users and authorize service access and invocation according to the user's authority;
g) Provide unified management of operating status during service use, including service monitoring, service log management, etc.;
h) Unified management of information during service use shall be provided, including service access management, service interface...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 36622.1-2018_English be delivered?Answer: Upon your order, we will start to translate GB/T 36622.1-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 36622.1-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 36622.1-2018_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|