HOME Cart(12) Quotation About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

GB 33473-2016 English PDF

US$259.00 · In stock
Delivery: <= 3 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB 33473-2016: General technical requirements of handover interface for instant communication services
Status: Valid

Standard ID	Contents [version]	USD	STEP2	[PDF] delivered in	Standard Title (Description)	Status	PDF
GB 33473-2016	English	259	Add to Cart	3 days [Need to translate]	General technical requirements of handover interface for instant communication services	Valid	GB 33473-2016

PDF similar to GB 33473-2016

Standard similar to GB 33473-2016

GB/T 41301 YZ/T 0173 YD/T 1548.1 GB/T 41922 GB/T 37081

Basic data

Standard ID	GB 33473-2016 (GB33473-2016)
Description (Translated English)	General technical requirements of handover interface for instant communication services
Sector / Industry	National Standard
Classification of Chinese Standard	M19
Classification of International Standard	33.030
Word Count Estimation	13,191
Date of Issue	2016-12-30
Date of Implementation	2017-01-01
Regulation (derived from)	National Standard Notice No.27 of 2016
Issuing agency(ies)	General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China

GB 33473-2016: General technical requirements of handover interface for instant communication services

---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.
General technical requirements of handover interfacefor instant communication services ICS 33.030 M19 National Standards of People's Republic of China HI IM service interfaces in general technical requirements Published 2016-12-30 2017-01-01 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China issued

Preface Ⅰ 1 Scope 1 2 Normative References 1 3 terms, definitions and abbreviations 1 4 3 Basic requirements The basic principle 4.1 HI interface 3 4.2 Functional Requirements 3 5 Network architecture 3 4 6 logo 6.1 identifies 4 goals 6.2 Communication Identification 4 6.3 5 request identifier 6.4 IRI SEQ ID NO 5 6.5 session sequence number 5 6.6 RD record number 5 6.7 CC record number 5 6.8 Retained lot identification data query results 6 7 HI interfaces in claim 6 7.1 HI1 interface requirements 6 7.2 HI2 interface requirements 6 7.3 HI3 interface requirements 7 8 8 safety requirements 8 8.1 certification requirements 8.2 confidentiality requirements 8 8.3 integrity requirements 8 8.4 submit network 8 Annex A (normative) using the FTP protocol in claim 9 A.1 configuration settings 9 A.2 Basic requirements 9 A.3 FTP timer and threshold 9

Foreword

All technical contents of this standard is mandatory. This standard was drafted in accordance with rules GB/T 1.1-2009 given. Please note that some of the content of this document may involve patents. The issuing authority of this document does not assume responsibility to identify these patents. The standard proposed by the People's Republic of China Ministry of Industry and Information Technology. This communication standard by the National Standardization Technical Committee (SAC/TC485). Drafted by. China Information and Telecommunications Research Institute. The main drafters. Lin Meiyu, Jiang Jian, Wu Hong Jian, Yang Bin, Zhang Yuanjing, Wu Shao-hung. HI IM service interfaces in general technical requirements

1 Scope

This standard specifies the basic requirements of real-time communication services HI Interface IP-based networks provide, network architecture, logo, HI interfaces to Summing safety requirements. This standard applies to IP-based instant messaging services provided by the network.

2 Normative references

The following documents for the application of this document is essential. For dated references, only applies to the version dated paper Pieces. For undated references, the latest edition (including any amendments) applies to this document. IETFRFC3261 SIP. Session Initiation Protocol (SIP. SessionInitiationProtocol) Shibian IETFRFC3325 for Session Initiation Protocol (SIP) for the yet to be demonstrated in the trusted network of privately extension [Private ExtensionstotheSessionInitiationProtocol (SIP) forAssertedIdentitywithinTrustedNetworks] 3 terms, definitions and abbreviations 3.1 Terms and Definitions The following terms and definitions apply to this document. 3.1.1. Instant messaging service provider instantcommunicationserviceprovider Providing a point-to-multipoint communication features of the service provider. 3.1.2. Instant messaging service instantcommunicationservice Relying on relevant business instant messaging service provider. Note. multimedia sessions such as Internet business. 3.1.3 Network multimedia session services IPmultimediaservice Relying on IP data network, providing point to point, multipoint real-time multimedia session services, including voice and video communications. 3.1.4 Submit interfaces handoverinterface Instant messaging service provider technical interface, also known as HI interfaces, including HI1, HI2 and HI3 three interfaces. 3.1.5 Management module administrationfunction Submit function module gateway handling HI1 interface. 3.1.6 Intermediary function module medicationfunction Submit function module gateway handling HI2 and HI3 interface. 3.1.7 Transmission of information transportrelatedinformation For maintenance, testing HI interfaces and protection purposes, information sent on HI2 interface. 3.1.8 Target relevant information interceptrelatedinformation Target use instant communication service-related information, including information related to a communication (e.g., communication connection attempt fails), business-related letter Information (such as the user's business management), and location information. 3.1.9 Communication content contentofcommunication In addition to the target information, instant messaging business interaction between the target user and other users or network element information. Note. multimedia sessions such as network traffic content. 3.1.10 Encumbrance retaineddata Instant messaging service provider retained within its network data associated with a particular business. Retained data typically includes several business use Data, user data, device data, submit data gateway and billing data. 3.1.11 Submit enforcement facilities lawenforcementmonitoringfacility And submit a gateway connected to collect and submit the results to submit the results of processing equipment. 3.1.12 First session acommunicationsession Initiate session establishment process request to begin the end of this session from the network side. 3.1.13 Permanently marked permanentidentity From the business user to apply some kind of write-off of this business process, can uniquely identify the business instant messaging service providers in a Users and does not identify the change. Note. for example, when the user registration, instant messaging service providers internal identifier assigned to the user, before the user logs off, the logo can not be assigned again To other users. 3.1.14 Temporary identity temporaryidentity Being able to uniquely identify a user in a certain business instant messaging service provider over a period of time and allows changes Identity. Note. for example, instant messaging services allow users to bind or unbind the mobile phone number in the phone number during the binding can be used as a temporary identifier of the user, Users may need to change the binding mobile phone number at any time. 3.1.15 Group group A plurality of users use the same instant messaging service application logic group session temporary or permanent use. 3.2 Abbreviations The following abbreviations are applicable to this document. AF management module (AdministrationFunction) CC communication content (ContentofCommunication) Communication identification CID (CommunicationIdentifier) CIN communication identification code (CommunicationIdentityNumber) FTP File Transfer Protocol (FileTransferProtocol) GWID submitted gateway identifier (GatewayIdentifier) HI submitted Interface (HandoverInterface) IP Internet Protocol (InternetProtocol) IPSec Internet Protocol Security (InternetProtocolSecurity) IRI target information (InterceptRelatedInformation) LEA law enforcement agencies (LawEnforcementAgency) LEMF Law Enforcement submit Facilities (LawEnforcementMonitoringFacility) MF intermediary function modules (MediationFunction) RD encumbrance (RetainedData) SFTP SSH File Transfer Protocol (SSHFileTransferProtocol) SIP Session Initiation Protocol (SessionInitiationProtocol) SSH Secure Shell (SecureShel) SvP service provider (ServiceProvider) SvPID service provider identifier (ServiceProviderIdentifier) TRI transmission related information (TransportRelatedInformation)

4 Basic requirements

4.1 HI basic principles of interface HI interfaces should follow the relevant national laws and regulations. Communication between the activities of non-target user, should not trigger submit function. And the device does not allow any access to instant communications service providers (hereinafter referred to as SvP) sensitive data domain, including LEMF feature Configuration information, and submit a gateway between the LEMF and certificate authentication parameters, target information, such as data retention SvP domain. In SvP network Inside, it should adopt the necessary measures to ensure the security of sensitive data, such as encrypted storage. SvP available to business users, should support the HI interface functions; but not yet available for SvP SvP business and existing business flow Information process is not obtained, we do not need to get back to provide through additional process. If the LEA has to SvP other than those specified in this standard Useful information can be reported by extensive information field. HI interface includes HI1, HI2, HI3 interfaces, message interfaces, and three function completely different content delivery, and should be independent of each other. Communication process, if SvP network involved in the encryption process, the communication should be submitted SvP decrypted content. If encryption is not a SvP Network and provide SvP can not obtain a key, decryption is not required SvP. If two target users communicate with each other, the two targets were submitted results should be reported process. With the development and updating of technology needs, HI interfaces should be extended. 4.2 Functional requirements HI interfaces should support real-time (quasi real time) to submit features, namely real-time (quasi real time) to the active process of communication with the user through the contents of the target HI interfaces submitted to the LEMF. HI interface shall support queries and query results submitted to the LEMF SvP domain for retained data. By submitting content SvP HI interfaces include. target-related information (IRI), transmission of information (TRI), the communication content (CC) and left Stored data (RD) and the like. Further, SvP be obtained by HI instruction information submitted interface, comprising target identifier, the end time of submission, The LEMF address.

5 Network Architecture

Figure 1 shows the network architecture filed interface. SvP domain includes network elements, retained the database and submit the gateway network element which includes all relevant business server providing the service. considering Various forms of networking is SvP different, the business form may be provided also vary, for the convenience of management, the gateway requires submission of each side using SvP Formula provides centralized delivery interfaces, each network element without using an interface provided separately submission. Submit gateway management functions including AF, IRI intermediary function module and CC/RD mediation modules. Retained database, network elements and interfaces for submitting SvP internal network between the gateway Network interface. SvP interaction between HI Facility LEMF via an interface with law enforcement to submit. The standard only specifies the interface provided by the gateway HI submit demands to not within the scope of this standard internal network interface. HI interface includes HI1, HI2, HI3 interfaces three interfaces. Which, HI1 for the management interface for submitting and gateway between the LEMF Delivery management instruction; reporting the HI2 interface to the target interface information for submission to the LEMF gateway submitted IRI message, alarm and failure TRI maintenance such heartbeat message class; HI3 interface to the communications and reporting interfaces for data retention, for submission to the CC filed gateway LEMF And retention of data. Figure 1 Figure submit Interface Architecture

6 logo

6.1 target identification SvP target identification for identifying a particular target region, such as user accounts, the internal identifier and the like. Interim target identification can not be used to activate target users to submit feature, considering that most of the public is not permanently marked with User identification, if the LEA does not know the user's identity permanently, you need to identify the query interface uses temporary corresponding permanent by HI Logo, and then permanent markings activate the target user. 6.2 Communication logo Communication ID (CID) used to distinguish different sessions during certain activities, and for associating in the same session HI2 activity during IRI report and HI3 of CC content. CID produced by the submission gateway. SvP identified by the CID (SvPID), submitted gateway identifier (gwid) and a communication code (CIN) composition. SvP identifier used to uniquely identify a SvP of a business product, the LEMF responsible for each SvP business products division With. 8 SvP identified as fixed-length string. Submit gateway identifier (gwid) for respectively identifying submitted standby gateway, responsible SvP allocated as a character string. CIN identification code for communication with SvP a business product that uniquely identifies a communication session within a goal of submitting a gateway. All results are submitted in time during a session should use the same CIN. If there are two same target in the same SvP them Or more communication sessions, CIN each session should not be the same. If two or more targets involved in the same communication session, submit CIN gateway should allocate the same value for different objectives. Related to the session IRI and CC should carry CIN. Satisfy the following three conditions IRI message may not carry CIN. IRI itself Any target user's communication session does not matter; IRI itself with any CC does not matter; IRI itself with any other IRI are It does not matter. Depending on the particular business process, when a system failure or accident, with IRI-REPORT during a session may be Can occur before IRI-BEGIN message may also be generated after IRI-END message, such as IRI-REPORT also be assigned the same A communication session with other HI2 and HI3 interfaces same CIN. CIN is a number ranging between 0 to 232-1, in order from the zero cycle number. 6.3 Request ID Request identifier used to associate HI1 interface request message and response message corresponding relationship between, and the HI2 interface associated contact HI1 Encumbrance port query request message and HI3 interfaces retained correspondence between the data query result. Request identification of all messages are Generated by the sender of the message. TRI request identifies each type of request message individually numbered. Request identifies a digital value between 0 ~ 232-1, in order from the zero cycle number. 6.4 IRI sequence number IRI IRI message sequence number is used to check whether the loss of HI2 interface. IRI submitted serial number generated by the gateway. IRI serial number Is a number ranging between 264-10 ~, connecting the IP address (the IP layer communication parties in the submission of a gateway to the LEMF HI2 interface Port transport layer, a transport layer protocol to determine the connection), the sequence from the zero cycle number. For session-unrelated business, IRI sequence number used to correlate IRI message further interface HI2 and HI3 interface communication contents. 6.5 session sequence number Session sequence number for a communication session on the IRI message reported by the identification process can be used for checking a session Whether the IRI lost. Session number sequence generated by the submission gateway. Value session sequence number is a number between 0 ~ 232-1. When the target start a new communication session, the session sequence number Numbered sequentially starting from 0. 6.6 RD record number The query is used to identify each record to the data retained in a query. Record number RD is generated by submitting the gateway. RD record number is a number ranging between 1 and 232-1, all records in chronological order generated numbered sequentially from 1. when The value is a record number can not find any record "0." 6.7 CC record number When the communication content submitted by SFTP manner, in a communication content submitted ZIP compression all communication through the bag contents CC record number identification. Record number is generated by submitting the gateway. CC record number is a number ranging between 1 and 232-1. ZIP compression in the packet communication content may be a document, it may be A related text message conversation. All communication content according to the time order of the sorted order from the generated number 1. 6.8 Retained lot identification data query results When using a batch submission encumbrance manner, the identification used to identify each particular batch, the specific defined in Appendix A.2.

7 HI interface requirements

7.1 HI1 interface requirements HI1 interface is bidirectional. LEMF by sending delivery command interfaces HI1, such as activation, deactivation, etc., and receives from the interface means HI1 So that response information. For real-time submission of IRI and CC (near real-time), we need to provide the following information to SvP. a) the target identification information for identifying a user or a user activates the query; b) request identifier for identifying the request message and submitting LEMF gateway in response to a correspondence between the message; c) End time of activation; d) LEMFHI2 address, IP address and port identifier when the interface LEMFHI2 SvP reporting IRI used; e) LEMFHI3 address, IP address and port identifier when the interface LEMFHI3 SvP reported CC used; f) other information required. For the retained data submitted, the need to provide the following information to SvP. a) priority requests; b) query, for example, query a specific period of time specify a particular type of user data retention; c) LEMFHI3 address, IP address and port identifier when the interface LEMFHI3 SvP report encumbrance used; d) Returns the maximum number of records; e) when submitted in batches, each batch of the maximum number of records returned; f) other information required. 7.2 HI2 interface requirements 7.2.1 HI2 interface functions 7.2.1.1 Summary HI2 interface to submit message gateway submitted TRI IRI fault alarm message and the like heartbeat and the like to maintain the LEMF. 7.2.1.2 IRI news Target user communication process-related information should be reported by IRI messages. HI2 interface shall chronological order and are sequentially generated IRI submit. IRI instant messaging service message includes the following four types. --- IRI-BEGIN, generated in the first communication event a request for opening IRI transaction; --- IRI-END, generated in the communication request when the communication end, or the end of IRI for closing the transaction; --- IRI-CONTINUE, at any time produce a IRI affairs; --- IRI-REPORT, etc. for events unrelated to the session. For the first event of the beginning of the session by IRI-BEGIN reported, the last session of the event reported by IRI-END, the session The other events reported by IRI-CONTINUE, non-session class events reported by IRI-REPORT. Multimedia sessions for the network service, if the communication control signaling protocol is SIP and H.323, the cost may be selected map standard gauge Suitable IRI events given by IRI-REPORT type filed, may submit the original signaling IRI and select the appropriate type of report; Preferred to submit the original signaling. If the communication control signaling is employed in addition to other SIP protocol and the H.323 protocol, the target user The mapping process should be suitable related activities IRI event cost criteria defined by IRI-REPORT type submit. Defined in this standard IRI business network multimedia session events include. call start event, the call is ringing/ringback event, call answering events, call release event, Business events, operational events. 7.2.1.3 TRI message TRI request message includes a heartbeat, the heartbeat response, alarm, option negotiation request, the option negotiation response, the end of the option negotiation, test PDU, Padding PDU, news reports and other information. among them. --- heartbeat message for checking whether the interface HI2 normal connection between the gateway and submit the LEMF; --- alert message indicating the gateway for submission to the LEMF SvP submitted within the relevant equipment or process alarm events generated; --- option negotiation message is used between the gateway and the LEMF submit TRI negotiation messages and the ability of both supported, such as filling PDU and so on; --- test PDU is an interface test packets to ensure HI interface function between the gateway and the LEMF submit proper test PDU take-end transmission mode; --- filling some traffic PDU is a padding packet, the packet itself no specific meaning, for changing only the rate of data traffic to prevent illegal Analysis of the user data traffic model; padding PDU generated by submitting the gateway, transmitted to the LEMF the LEMF is deleted by, filled SvP charge PDU needs to include the identification and submission gateway identifier, content is not limited, in principle, allow pass meaningful The content, in particular, is not allowed to pass sensitive information; --- Report for submission of the report indicates the gateway operating results related to the LEMF SvP domain, and the domains need to SvP LEMF provide additional supplemental information. Submit gateway should support heartbeat, alarm, option negotiation, information reports, test PDU, etc. TRI messages, optional support for padding PDU, etc. TRI messages. TRI messages can determine the optional peer support through option negotiation. 7.2.2 HI2 interface protocol HI2 interfaces should be safe and reliable, to achieve a common mechanism to submit messages interaction between the gateway and LEMF, and encryption machines Communication switching system the information...

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB 33473-2016_English be delivered?

Answer: Upon your order, we will start to translate GB 33473-2016_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 33473-2016_English with my colleagues?

Answer: Yes. The purchased PDF of GB 33473-2016_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+ countries

Question 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.