Mobile terminal data transmission method and device

Abstract

The invention provides a mobile terminal data transmission method and device, and the method comprises the steps: obtaining the communication attribute information of a mobile terminal, carrying out the filling of an initial independent transmission protocol according to the communication attribute information, and obtaining a target independent transmission protocol; the independent transmission protocol comprises a message header and a message body; the message header comprises a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the message body comprises a label identifier, a label data length and a label value of the message body; and configuring the target independent transmission protocol in a data transmission system of the mobile terminal, so that a communication system of the mobile terminal encapsulates and transmits data to be subjected to communication transmission according to the independent transmission protocol.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for mobile terminal data transmission. Background Art

[0002] At present, with the development of mobile communications, BIP (Bearer Independent Protocol) has gradually become the mainstream in mobile communications. However, in the existing technology, since the format of BIP is not standardized and due to different requirements, it is often necessary to design a dedicated BIP for a device or a class of devices according to different requirements, which makes the use of BIP difficult. Summary of the invention

[0003] In view of this, the purpose of the present application is to provide a mobile terminal data transmission method and device for solving the problem of how to quickly generate a standardized BIP in the prior art.

[0004] In a first aspect, an embodiment of the present application provides a mobile terminal data transmission method, the method comprising:

[0005] Acquire the communication attribute information of the mobile terminal, fill the initial independent transmission protocol according to the communication attribute information, and obtain the target independent transmission protocol; the independent transmission protocol includes a message header and a message body; the message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the message body includes a message body tag identification, a tag data length and a tag value;

[0006] The target independent transmission protocol is configured in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal encapsulates and transmits the data to be communicated according to the independent transmission protocol.

[0007] In some embodiments, the message definition byte includes a message sequence number bit, a response message bit, and a reserved bit;

[0008] If the transmission data is a request message, the value of the response message bit is 0; if the transmission data is a response message, the value of the response message bit is 1.

[0009] In some embodiments, the message type byte includes a response flag bit, an encryption flag bit, a version bit, and a reserved bit;

[0010] If the transmitted data does not require a response, the value of the response flag bit is 0; if the transmitted data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1;

[0011] If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1;

[0012] The version bits occupy two consecutive bits of the message type byte.

[0013] In some embodiments, the tag type corresponding to the tag identifier of the message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, patch card unique identifier.

[0014] In a second aspect, an embodiment of the present application provides a mobile terminal data transmission device, including:

[0015] A generation module, used to obtain the communication attribute information of the mobile terminal, fill the initial independent transmission protocol according to the communication attribute information, and obtain the target independent transmission protocol; the independent transmission protocol includes a message header and a message body; the message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the message body includes a message body tag identification, a tag data length and a tag value;

[0016] The configuration module is used to configure the target independent transmission protocol in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal encapsulates and transmits the data to be communicated according to the independent transmission protocol.

[0017] In some embodiments, the message definition byte includes a message sequence number bit, a response message bit, and a reserved bit;

[0018] If the transmission data is a request message, the value of the response message bit is 0; if the transmission data is a response message, the value of the response message bit is 1.

[0019] In some embodiments, the message type byte includes a response flag bit, an encryption flag bit, a version bit, and a reserved bit;

[0020] If the transmitted data does not require a response, the value of the response flag bit is 0; if the transmitted data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1;

[0021] If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1;

[0022] The version bits occupy two consecutive bits of the message type byte.

[0023] In some embodiments, the tag type corresponding to the tag identifier of the message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, patch card unique identifier.

[0024] In a third aspect, an embodiment of the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any one of the methods described in the first aspect when executing the computer program.

[0025] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described in any one of the above-mentioned first aspects are executed.

[0026] A method for data transmission of a mobile terminal proposed in an embodiment of the present application completes data filling of an unfilled initial independent transmission protocol by acquiring communication attribute information of the mobile terminal when the mobile terminal is started, so as to obtain a target independent transmission protocol, and enable the mobile terminal to transmit data through the target independent transmission protocol. The method for data transmission of a mobile terminal proposed in an embodiment of the present application provides a standardized initial protocol and filling rules for the independent transmission protocol used for mobile terminal communication, so that the independent transmission protocol of the mobile terminal can be quickly and automatically improved, thereby improving the efficiency of the configuration of the independent transmission protocol.

[0027] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0029] Figure 1 A flowchart of a mobile terminal data transmission method provided in an embodiment of the present application;

[0030] Figure 2A schematic diagram of the structure of an independent transmission protocol provided in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of the structure of a message header in an independent transmission protocol provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of the structure of a message body in an independent transmission protocol provided in an embodiment of the present application;

[0033] Figure 5 A schematic diagram of the structure of message definition bytes in an independent transmission protocol provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of the structure of the message type byte in the independent transmission protocol provided in an embodiment of the present application;

[0035] Figure 7 A comparison table of message body tag identifiers in the independent transmission protocol provided in the embodiment of the present application;

[0036] Figure 8 A comparison table describing data in an independent transmission protocol provided in an embodiment of the present application;

[0037] Fig. 9 A schematic diagram of the structure of a mobile terminal data transmission device provided in an embodiment of the present application;

[0038] Fig.10 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0040] The present application embodiment provides a mobile terminal data transmission method, such as Figure 1 As shown, the following steps are included:

[0041] Step S101, obtaining the communication attribute information of the mobile terminal, filling the initial independent transmission protocol according to the above communication attribute information, and obtaining the target independent transmission protocol; the above independent transmission protocol includes a message header and a message body; the above message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the above message body includes a message body tag identification, a tag data length and a tag value;

[0042] Step S102: configuring the target independent transmission protocol in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal encapsulates and transmits the data to be communicated according to the independent transmission protocol.

[0043] Specifically, an automatic filling program of an independent transmission protocol BIP is pre-loaded in the mobile terminal. When the mobile terminal communicates, the program automatically obtains the communication attribute information of the mobile terminal. The communication attribute information includes the communication mode, identification code, physical card information, time information, data processing time interval, IP address, etc. of the mobile terminal.

[0044] Then, the initial BIP to be filled is filled according to the above communication attribute information to obtain the target BIP, and the target BIP is used as the communication protocol used to encapsulate and transmit data in data transmission.

[0045] The above independent transmission protocols are as follows Figure 2 As shown in the figure, it consists of two parts: the message header and the message body.

[0046] The data length of the message header is 8 bytes, such as Figure 3 As shown, the fixed identification byte occupies 2 bytes, that is, Figure 3 The N (0x78) and Q (0x81) in the message header, the message definition byte and the message type byte each occupy 1 byte, and the message body data length byte (Payload Data Size) occupies 2 bytes. The remaining 2 bytes are reserved for the message header content extension.

[0047] The message body is a data table filled in TLV (Tag Length Value) format, such as Figure 4 As shown, the message body includes a tag identifier, a tag data length, and a tag value, wherein the tag occupies 1 byte and the tag data length occupies 2 bytes.

[0048] In some embodiments, the message definition byte includes a message sequence number bit, a response message bit, and a reserved bit;

[0049] If the transmitted data is a request message, the value of the above response message bit is 0; if the transmitted data is a response message, the value of the above response message bit is 1.

[0050] Specifically, Figure 5 As shown, the message definition byte is defined in Little Endian (low byte order), and the message definition byte includes a message sequence number bit, a response message bit and a reserved bit, wherein the message sequence number bit occupies 4 bits and the response message bit occupies 1 bit.

[0051] The message sequence number bit is a hexadecimal message sequence number, and the response message bit is filled according to the message type of the transmitted data. If the response type is a request message, the response message bit is 0, and if the response type is a response message, the response message bit is 1.

[0052] In some embodiments, the message type byte includes a response flag bit, an encryption flag bit, a version bit, and a reserved bit;

[0053] If the transmission data does not require a response, the value of the response flag bit is 0; if the transmission data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1;

[0054] If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1;

[0055] The above version bits occupy two consecutive bits of the above message type byte.

[0056] Specifically, Figure 6 As shown, the message type byte is defined in binary MSB (Most Significant Bit) mode, and the message type byte includes a response flag bit, an encryption flag bit, a version bit, and a reserved bit, wherein the response flag bit and the encryption flag bit each occupy 1 bit, and the version bit occupies 2 bits.

[0057] The response flag bit is filled according to the response type of the transmitted data. If the response type is no response required, the response flag bit is 0; if the response type is a response required, the response flag bit is 1.

[0058] The encryption flag is filled according to the encryption status of the message body. If the message body is not encrypted, the encryption flag is 0. If the message body is encrypted, the encryption flag is 1, and the message body must carry encrypted data.

[0059] The version bits are 2 consecutive bits. The version bits corresponding to version 1 are 00, the version bits corresponding to version 2 are 01, the version bits corresponding to version 3 are 10, and the version bits corresponding to version 4 are 11.

[0060] In some embodiments, the tag type corresponding to the tag identifier of the above message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, patch card unique identifier.

[0061] Specifically, according to the data corresponding to the tag type in the communication attribute information of the mobile terminal, the corresponding tag identifier is added to the message body, and the value corresponding to the tag identifier is filled in according to the filling rule, and finally a message body data table is formed.

[0062] The label is a hexadecimal number, for example Figure 7 As shown, the encrypted data (CheckSum Data) is 0x00, the International Mobile Subscriber Identity (IMSI) is 0x01, the International Mobile Equipment Identity (IMEI) is 0x02, the response message processing result is 0x03, the entity card identification code is 0x04, the description data is 0x05, the time data is 0x06, the timer time interval (Interval) is 0x07, the mobile terminal local service status (Location Status) is 0x08, the description operation is 0x09, the independent protocol address update status is 0x10, the port IP address is 0x11, and the patch card unique identifier is 0x12.

[0063] The tag data length corresponding to the tag identifier is pre-set, and the value corresponding to the tag identifier is filled according to the filling rule of the tag type corresponding to the tag identifier. The specific rules are as follows: Figure 4 shown.

[0064] If the value of the response message processing result is 0x00, it indicates that the response message processing is successful; if it is 0x01, it indicates that the response message processing fails.

[0065] Profile data is also stored in TLV format. The profile data is equivalent to the sub-data table of the message body. The corresponding relationship between the profile data tag identifier, data length and description is as follows: Figure 8 shown.

[0066] The present application also provides a mobile terminal data transmission device, such as Fig. 9 As shown, including:

[0067] The generation module 30 is used to obtain the communication attribute information of the mobile terminal, fill the initial independent transmission protocol according to the above communication attribute information, and obtain the target independent transmission protocol; the above independent transmission protocol includes a message header and a message body; the above message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the above message body includes a message body tag identification, a tag data length and a tag value;

[0068] The configuration module 31 is used to configure the target independent transmission protocol in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal can encapsulate and transmit the data to be communicated according to the independent transmission protocol.

[0069] In some embodiments, the message definition byte includes a message sequence number bit, a response message bit, and a reserved bit;

[0070] If the transmitted data is a request message, the value of the above response message bit is 0; if the transmitted data is a response message, the value of the above response message bit is 1.

[0071] In some embodiments, the message type byte includes a response flag bit, an encryption flag bit, a version bit, and a reserved bit;

[0072] If the transmission data does not require a response, the value of the response flag bit is 0; if the transmission data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1;

[0073] If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1;

[0074] The above version bits occupy two consecutive bits of the above message type byte.

[0075] In some embodiments, the tag type corresponding to the tag identifier of the above message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, patch card unique identifier.

[0076] Corresponds to Figure 1 A mobile terminal data transmission method in the present application embodiment further provides a computer device 400, such as Fig.10As shown, the device includes a memory 401, a processor 402, and a computer program stored in the memory 401 and executable on the processor 402, wherein the processor 402 implements the above-mentioned mobile terminal data transmission method when executing the above-mentioned computer program.

[0077] Specifically, the above-mentioned memory 401 and processor 402 can be general-purpose memory and processor, which are not specifically limited here. When the processor 402 runs the computer program stored in the memory 401, it can execute the above-mentioned mobile terminal data transmission method, solving the problem of how to quickly generate a standardized BIP in the prior art.

[0078] Corresponds to Figure 1 A mobile terminal data transmission method in the present application, an embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned mobile terminal data transmission method are executed.

[0079] Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, etc. When the computer program on the storage medium is run, it can execute the above-mentioned mobile terminal data transmission method, which solves the problem of how to quickly generate a standardized BIP in the prior art. The mobile terminal data transmission method proposed in the embodiment of the present application completes the data filling of the unfilled initial independent transmission protocol by obtaining the communication attribute information of the mobile terminal when the mobile terminal is started, so as to obtain the target independent transmission protocol, so that the mobile terminal can transmit data through the target independent transmission protocol. The mobile terminal data transmission method proposed in the embodiment of the present application provides a standardized initial protocol and filling rules for the independent transmission protocol used for mobile terminal communication, so that the independent transmission protocol of the mobile terminal can be quickly and automatically improved, thereby improving the efficiency of the independent transmission protocol configuration.

[0080] In the embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0081] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0082] In addition, each functional unit in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0083] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0084] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0085] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A mobile terminal data transmission method, characterized in that: include: Acquire communication attribute information of the mobile terminal, and fill the initial independent transmission protocol according to the communication attribute information to obtain the target independent transmission protocol; The independent transmission protocol includes a message header and a message body; the message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the message body includes a message body label identification, a label data length and a label value; The target independent transmission protocol is configured in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal encapsulates and transmits the data to be communicated according to the independent transmission protocol.

2. The method according to claim 1, characterized in that The message definition byte includes a message sequence number bit, a response message bit and a reserved bit; If the transmission data is a request message, the value of the response message bit is 0; if the transmission data is a response message, the value of the response message bit is 1.

3. The method according to claim 1, characterized in that The message type byte includes a response flag bit, an encryption flag bit, a version bit and a reserved bit; If the transmitted data does not require a response, the value of the response flag bit is 0; if the transmitted data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1; If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1; The version bits occupy two consecutive bits of the message type byte.

4. The method according to claim 1, characterized in that The tag type corresponding to the tag identifier of the message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, and patch card unique identifier.

5. A mobile terminal data transmission device, characterized in that: include: A generation module, used to obtain the communication attribute information of the mobile terminal, fill the initial independent transmission protocol according to the communication attribute information, and obtain the target independent transmission protocol; the independent transmission protocol includes a message header and a message body; the message header includes a fixed identification byte, a message definition byte, a message type byte, a message body data length byte and a reserved byte; the message body includes a message body tag identification, a tag data length and a tag value; The configuration module is used to configure the target independent transmission protocol in the data transmission system of the mobile terminal, so that the communication system of the mobile terminal encapsulates and transmits the data to be communicated according to the independent transmission protocol.

6. The device according to claim 5, characterized in that The message definition byte includes a message sequence number bit, a response message bit and a reserved bit; If the transmission data is a request message, the value of the response message bit is 0; if the transmission data is a response message, the value of the response message bit is 1.

7. The device according to claim 5, characterized in that The message type byte includes a response flag bit, an encryption flag bit, a version bit and a reserved bit; If the transmitted data does not require a response, the value of the response flag bit is 0; if the transmitted data requires the peer end for data transmission with the mobile terminal to return a response message carrying a response result after processing the data transmission request sent by the mobile terminal, the value of the response flag bit is 1; If the message body does not need to be encrypted, the value of the encryption flag bit is 0; if the message body needs to be encrypted, the value of the encryption flag bit is 1; The version bits occupy two consecutive bits of the message type byte.

8. The device according to claim 5, characterized in that The tag type corresponding to the tag identifier of the message body includes at least one of the following: encrypted data, international mobile user identity code, international mobile equipment identity code, response message processing result, entity card identification code, description data, time data, timer time interval, mobile terminal local service status, description operation, independent protocol address update status, port IP address, and patch card unique identifier.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are executed.

Images