Skip to product information
1 of 12

PayPal, credit cards. Download editable-PDF and invoice in 1 second!

GB/T 41239-2022 English PDF (GBT41239-2022)

GB/T 41239-2022 English PDF (GBT41239-2022)

Regular price $470.00 USD
Regular price Sale price $470.00 USD
Sale Sold out
Shipping calculated at checkout.
Quotation: In 1-minute, 24-hr self-service. Click here GB/T 41239-2022 to get it for Purchase Approval, Bank TT...

GB/T 41239-2022: Public telecom network - Requirements for vehicle information service

This Standard specifies proposes an overall framework for vehicle information services based on the public telecom network. It specifies the requirements of perception extension layer, network transport layer, business layer, application layer, security requirements, service QoS requirements, data storage requirements and exception handling requirements. This Standard applies to the system, equipment and business of vehicle information service based on the public telecom network.
GB/T 41239-2022
NATIONAL STANDARD OF THE
PEOPLE REPUBLIC OF CHINA
ICS 33.030
CCS L 67
Public telecom network - Requirements for vehicle
information service
ISSUED ON: MARCH 09, 2022
IMPLEMENTED ON: OCTOBER 01, 2022
Issued by: State Administration for Market Regulation;
Standardization Administration of the People's Republic of China.
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative references ... 4
3 Terms and definitions... 5
5 General overview ... 6
5.1 System structure ... 6
5.2 Main interface requirements ... 8
6 Perception extension layer requirements ... 10
6.1 General requirements ... 10
6.2 Technical requirements ... 11
7 Network transport layer requirements ... 13
7.1 General requirements ... 13
7.2 Technical requirements ... 13
8 Business layer requirements ... 14
8.1 General requirements ... 14
8.2 Technical requirements ... 16
9 Application layer requirements ... 18
9.1 Business scope ... 18
9.2 Business categories ... 19
10 Security requirements ... 27
10.1 Perception extension layer ... 27
10.2 Network transport layer ... 28
10.3 Business layer ... 28
10.4 Application layer ... 29
11 Service QoS requirements ... 29
12 Data storage requirements ... 30
13 Exception handling requirements ... 30
Annex A (informative) Business process ... 31
Annex B (informative) Typical use case ... 35
Public telecom network - Requirements for vehicle
information service
1 Scope
This Standard specifies proposes an overall framework for vehicle information services based on the public telecom network. It specifies the requirements of perception extension layer, network transport layer, business layer, application layer, security requirements, service QoS requirements, data storage requirements and exception handling requirements.
This Standard applies to the system, equipment and business of vehicle information service based on the public telecom network.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. GB/T 6107-2000, Interface between data terminal equipment and data circuit terminating equipment employing serial binary data interchange
GB/T 15629.15-2010, Information technology - Telecommunications and
information exchange between systems local and metropolitan area networks - Specific requirements - Part 15: Wireless medium access control and physical layer (PHY) specification for low-rate wireless personal area networks
ISO 11898-1:2015, Road vehicles - Controller area network (CAN) - Part 1: Data link layer and physical signaling
ISO 11898-2:2016, Road vehicles - Controller area network (CAN) - Part 2: High- speed medium access unit
ISO 11898-3:2006, Road vehicles - Controller area network (CAN) ?€? Part 3: Low- speed, fault-tolerant, medium-dependent interface
TIA/EIA-485-A, Electrical Characteristics of Generators and Receivers for Use in Balanced Digital Multipoint Systems
3GPPTS102250-7, Speech and multimedia Transmission Quality (STQ); QoS
aspects for popular services in mobile networks; Part 7: Network based Quality of access technologies such as 2G, 3G, 4G, 5G, and WLAN. The core network sublayer implements data transmission between the vehicle terminal and the service layer. The business layer consists of a business management platform and a business support platform. The business management platform and the business support platform jointly complete the support and management of various applications of vehicle information services. The business management platform realizes functions such as application management, user management, order management, terminal management, business management, and system management. It is connected with peripheral systems such as intelligent customer service centers, rescue management agencies, etc. The business support platform mainly realizes the functions of partner management, user relationship management, billing, comprehensive collection, comprehensive settlement, and business analysis.
The application layer consists of various application systems that provide vehicle information services. There are mainly communication services, road navigation, driver assistance, remote monitoring and infotainment applications.
5.2 Main interface requirements
5.2.1 Interface between TCU and automotive CAN bus
The interface between TCU and automobile CAN bus includes the following: a) Electrical interface between TCU and CAN bus: TCU shall have the ability to adapt and convert the existing communication interface (such as GB/T 6107-2000, USB) to the CAN bus interface, and realize the physical interface with the CAN bus;
b) Physical layer interface between TCU and CAN bus: shall comply with ISO 11898-2:2016 and ISO 11898-3:2006;
c) Data link layer interface between TCU and CAN bus: shall comply with ISO 11898-1:2015;
d) Application layer interface between TCU and CAN bus: shall comply with one or more standards such as CAN Open (application standard of CAN-based
distributed industrial automation system and CAN application layer
communication standard), DeviceNet (applicable to the lowest field bus). 5.2.2 Vehicle terminal and TCU interface
The interface between the vehicle terminal and the TCU includes wired and wireless: a) Wired transmission interface: shall comply with GB/T 6107-2000 and TIA/EIA- 485-A and other standards;
b) Wireless transmission interface: shall comply with standards such as Bluetooth. 5.2.3 Network transport layer and vehicle terminal interface
Network transport layer and vehicle terminal interface: shall support GPRS, SMS, MMS, USSD, and so on.
5.2.4 Business management platform and network transport layer interface Interface between the business management platform and the network transport layer: it shall support both wired and wireless and conform to standards such as Ethernet and WLAN.
5.2.5 Interface between business management platform and business support platform
The business support platform accepts user account opening, business opening, data entry and maintenance, complaints and suggestions to realize business marketing, accounting and billing. The business support platform can open user and business data to the business management platform through API.
5.2.6 Business management platform and peripheral system interface
5.2.6.1 Business management platform and intelligent customer service center system interface
The business management platform can open business data to the intelligent customer service center system through API, so that the agents of the intelligent customer service center can obtain business data related to the vehicle terminal and provide human services.
5.2.6.2 Interface between the business management platform and the information system of the rescue management agency
The business management platform can open data such as vehicle speed, acceleration, steering wheel position, steering, steering speed and vehicle damage degree at the time of the accident to the rescue management agency information system through API. 5.2.6.3 Interface between business management platform and traffic management information system
The business management platform can open to the traffic management information system the data such as the position and speed of the vehicle periodically reported by the vehicle terminal through the API. The business management platform can extract real-time dynamic road condition information from the traffic management information system through the interface, so as to provide real-time road condition navigation services to drivers and passengers.
corresponding ECU and enabling components through the CAN bus to realize the control of the car.
6.1.2 Reliability
In the sensing extension layer device, if a sensing node fails, it shall be able to automatically close and cut off the connection with the bus, without affecting the communication of the bus. It has hardware CRC and automatic retransmission function. 6.1.3 Consistency
The equipment of various transmission control protocols, interface protocols and data formats used in the perception extension layer of vehicle information services shall be adapted and converted through the gateway device, and unified into a consistent protocol and data format, so as to realize interconnection and resource sharing among heterogeneous multi-systems.
6.2 Technical requirements
6.2.1 Automobile ECU output data requirements
The output data of automobile ECU in vehicle information service shall include basic indicators and fuel economy indicators, maintenance indicators related to safe driving of cars, and auxiliary indicators of traffic accident handling.
6.2.2 Vehicle terminal functional requirements
The requirements of the vehicle information service for the functions of the vehicle terminal shall include:
a) Support business state management, including seven business states: un-preset serial number, preset serial number, registration failure, registration success, normal connection, abnormal connection, and connection alarm. It is required that the terminal can correctly judge the current service state. According to the business state migration conditions, it migrates to the correct business state under the action of actual business activities. During the process of business state migration, it shall be ensured that the data unrelated to the business state migration is not changed;
b) Support terminal serial number management. It is required to support two serial number implantation methods. When the vehicle terminal is used for the first time, it will automatically register with the business management platform to obtain the serial number and implant it. Apply serial numbers in batches from the business management platform in advance by car manufacturers. The serial number is directly implanted manually before the vehicle terminal leaves the factory or is used;
c) Support session management, including message retransmission mechanism, connection detection and connection exception handling.
d) Support terminal registration. Support terminal login and logout of the business management platform;
e) Support terminal parameter configuration management, including setting vehicle terminal parameters on the business management platform. The vehicle terminal requests parameter configuration from the business management platform, manually configures vehicle terminal parameters locally, and handles abnormal configuration of vehicle terminal parameters. Support core parameter consistency; f) Support terminal state reporting, including terminal abnormal state reporting, real- time data extraction and reporting from the business management platform to the terminal, terminal remote control execution state reporting, and terminal heartbeat message and communication state reporting in long-connection
application mode;
g) Support information reporting, including application software installation and uninstallation reporting on the terminal, business usage reporting, alarm information reporting, statistical information reporting, and information reporting exception handling;
h) Support software download and upgrade, including software download
notification response, software downloads and software upgrade, software upgrade exception handling, and can be rolled back to the previous version after the upgrade fails;
i) Support the adaptation of data in different formats collected by different ECUs of car manufacturers;
j) Support two-way security authentication mechanism of vehicle terminal and SIM card. The vehicle terminal can access the mobile communication network only after the mutual authentication between the vehicle terminal and the SIM card is completed;
k) Support 2G, 3G, 4G or 5G and other communication access methods. Support circuit switching, SMS, USSD, GPRS, WAP and other methods to realize voice and data communication with the business management platform;
l) The communication module of the mobile communication terminal can be used to connect with the vehicle terminal through USB or the standard interface specified in GB/T 15629.15-2010, so as to assist the vehicle terminal to realize the function of voice and data transmission;
m) The vehicle terminal shall distinguish different services according to different characteristics and choose the best service access mechanism.
The access network not only provides physical channels for signaling control and service flow transmission, but also logically divides different service sub- channels. Support the mapping of services to sub-channels according to priority. Guarantee the quality of service of high-priority service sub-channels; b) The access network supports the unified signaling control capability in the process of establishing and dismantling the session channel of the vehicle terminal. 7.2.2 Core network
The vehicle information service shall meet the following requirements for the core network:
a) Since the transmission of various data types is required in the vehicle information service, the core network is required to support the application of comprehensive services including voice, video and data of various magnitudes. At the same time, corresponding QoS guarantee is required;
b) The core network shall support mechanisms to avoid network congestion; c) The core network shall provide a mechanism to avoid terminal identification shortages;
d) The core network shall provide an optimized transmission mechanism for low data traffic.
8 Business layer requirements
8.1 General requirements
8.1.1 Business continuity
The business realization of vehicle information service shall be independent of network. Continuity of vehicle information service business across heterogeneous networks shall be supported.
8.1.2 Scalability
The business layer shall provide open management interfaces for various business and product applications of vehicle information services. It can support business version update and upgrade management. At the same time, it can support the rapid provision of effective support management for various expansion services that may appear in the future.
8.1.3 Reliability
Critical servers in the business layer shall adopt a high-availability solution. The system shall be redundantly configured, so as to ensure that the system has no single point of failure. It can be switched quickly after a fault occurs to ensure uninterrupted operation of 7d ?? 24h. The system shall have good backup means. System data and business data can be backed up and restored online. The restored data shall maintain its integrity and consistency.
8.1.4 Interoperability
The business management platform shall support the interoperability of management capabilities between different owned application systems, between basic networks in different management domains, and between different types of vehicle terminals. 8.1.5 Unified resource management capability
The business management platform shall support unified management capabilities for various resources:
a) Support unified management capabilities for multiple heterogeneous networks and devices;
b) Provide common abstraction capabilities for management parameters of multiple types of network elements and their equipment;
c) Support the consistent description ability of various network resources and operating environments;
d) Provide global identification planning, storage and coordination and allocation capabilities for resources registered on the business management platform. 8.1.6 Configuration management capability
The business management platform shall support configuration management capabilities:
a) Be applied to access network and core network facilities. Provide real-time monitoring capabilities;
b) Support the collection of dynamic information such as the location, state, and reachability of network devices;
c) The automatic configuration of static information related to the capabilities of the public telecommunication network shall be supported;
d) Provide the ability to customize business information (business configuration list). Provide device information (device configuration list) and firmware
customization and upgradeability.
The business management platform shall realize the management of registration, cancellation, login, login and logout of the vehicle terminal; condition monitoring and fault management of vehicle terminals; parameter configuration and remote control of vehicle terminal; information query and arrears query on the vehicle terminal; version management and download management of vehicle terminal software.
The business management platform shall realize the identity authentication function of the vehicle terminal participating in the vehicle information service. The function identification function can be performed on the service request initiated by the vehicle terminal according to the order relationship and configuration information. The business management platform shall support the terminal to access the system in various communication modes.
8.2.1.5 Business management
The business management platform shall support the information maintenance and management of the entire life cycle of the vehicle information service business and products, including the definition, change, release, and cancellation of business and products.
8.2.1.6 System management
The business management platform shall realize the configuration and modification of system parameters through the operation and maintenance interface. Make that the modification of parameters does not require restarting the platform application software system. System parameters shall include region, user type, service type, number segment, port configuration and so on.
The business management platform shall implement corresponding authority management, mainly including maintenance functions such as adding, deleting, modifying, and searching for the function point resource list of various businesses and products. It shall support the management of operator accounts, including adding, deleting, and modifying operator accounts. Support centralized management of function point permissions through roles to simplify the configuration of authorization and recovery permissions. Support role creation, modification and deletion. Multiple system function point permissions can be assigned to a role. Assign the role to the account. Permission settings shall be done by authorized system administrators. Administrators cannot set permissions greater than their own permissions. Permission management adopts a hierarchical management method. The upper level can set the management authority of the lower level.
The business management platform shall support log management. Support log query and display. It may support print and export functions. The export file can be in formats such as csv and html. Logs shall at least include operation logs and business logs. Operation log management is mainly used to record who (account), where (IP address), and when they have logged into the business management platform. Record any operation. Only users with administrator privileges can query the operation log. No one is allowed to delete the operation log. The platform keeps the oper...

View full details