Data compression method, system and related device in satellite communication system

Abstract

The invention discloses a data compression method and system in a Beidou communication system and a related device, a terminal compresses a user ID of the terminal and encodes the user ID into binary data, and then the terminal fills the binary data into a user ID field contained in frame header information of a first user frame generated by the terminal; and the terminal sends the first user frame to the Beidou network device. In this way, the frame header overhead in the user frame can be reduced.

Description

[0001] This application is a divisional application. The original application has the application number 202111069259.8 and the original application date is September 13, 2021. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the fields of BeiDou communication technology and compression technology, and in particular to a data compression method, system and related apparatus in a satellite communication system. Background Technology

[0003] The BeiDou Navigation Satellite System is a major infrastructure project independently developed by my country, integrating positioning, timing, and communication. The BeiDou Short Message Service utilizes the BeiDou satellite system to send short message information. It is particularly suitable for communication in areas such as oceans, deserts, grasslands, and uninhabited areas where mobile communication is unavailable, lacks coverage, or where communication systems are damaged.

[0004] The short message system of the BeiDou-3 satellite has upgraded the short message technology system and realized the separation of military and civilian signals. At present, under the premise of ensuring that military needs are fully met, the country has opened up some necessary resources of the BeiDou short message system to civilian use. In view of the characteristics of civilian services and equipment, communication protocols need to be designed according to the characteristics of the BeiDou short message system.

[0005] Currently, in the BeiDou short message communication system, each user is assigned a user number to identify their identity; this user number is also known as the user ID. Due to the limitations of current satellite communication transmission and reception capabilities of mass-market terminals, the frame header overhead for uplink and downlink transmissions should be minimized as much as possible. Traditional mobile phone number encoding methods use BCD (Binary-Coded Decimal) codes, but using this encoding method would waste even more frame header overhead.

[0006] Therefore, how to encode user IDs in the BeiDou system and minimize frame header overhead is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0007] This application provides a data compression method, system, and related apparatus in a satellite communication system. The method provided in the embodiments of this application can reduce frame header overhead when transmitting data.

[0008] In a first aspect, a data compression method is provided in a satellite communication system. The method may include: a first terminal encoding a first user ID of the first terminal into binary first data at the Satellite Link Control Layer (SLC), the first user ID including second data and third data, the first data including binary fourth data and binary fifth data, the fourth data being encoded from sixth data, the sixth data being compressed from the second data, the data length of the sixth data being less than that of the second data, and the fifth data being encoded from the third data; the first terminal filling the first data into the user ID field in the frame header information of the first user frame at the SLC layer; and the terminal sending the first user frame to the BeiDou network equipment.

[0009] The first user ID can be the mobile phone number of the first terminal, the second data can be the domestic destination code (NDC) in the mobile phone number, and the third data can be the customer number (SN) in the mobile phone number.

[0010] This reduces the number of bits allocated to the user ID in the user frame header information. When the terminal sends user frames to BeiDou network equipment, this reduces header overhead.

[0011] In conjunction with the first aspect, in one possible implementation, the first terminal encodes its first user ID into binary first data at the Satellite Link Control (SLC) layer, including: the first terminal compressing the second data in the first user ID into sixth data at the SLC layer, wherein the first user ID is composed of the second data and the third data, and the data length of the sixth data is less than that of the second data; the first terminal encodes the sixth data into fourth data and the third data into fifth data at the SLC layer; and the first terminal combines the fourth data and the fifth data to form the first data.

[0012] This reduces the number of bits allocated to the user ID in the frame header information of user frames.

[0013] In conjunction with the first aspect, in one possible implementation, the first terminal compresses the second data in the first user ID of the first terminal into the sixth data at the SLC layer, including: the first terminal maps the second data in the first user ID to the sixth data in the mapping table at the SCL layer; the mapping table includes multiple values ​​of second data and multiple values ​​of sixth data, wherein the multiple values ​​of second data include the second data of the first value, the multiple values ​​of sixth data include the sixth data of the second value, and the second data of the first data is mapped to the sixth data of the second value.

[0014] In this way, a second piece of data can be compressed into a sixth piece of data with a shorter length. Furthermore, the second and sixth pieces of data have a one-to-one correspondence, preventing a single compressed piece of data from corresponding to a single uncompressed piece of data. This ensures that no errors occur during decoding.

[0015] In conjunction with the first aspect, in one possible implementation, the first terminal compresses the second data in the first user ID of the first terminal into the sixth data at the SLC layer, including: the first terminal subtracts a preset offset value from the second data in the first user ID at the SCL layer to obtain the sixth data.

[0016] In this way, a second piece of data can be compressed into a sixth piece of data with a shorter data length.

[0017] In conjunction with the first aspect, in one possible implementation, the first terminal encodes the sixth data into the fourth data and the third data into the fifth data at the SLC layer, including: the first terminal converts the sixth data as a decimal integer into the fourth data in binary at the SLC layer; and converts the third data as a decimal integer into the fifth data in binary.

[0018] Because the length of the binary data obtained by encoding a single data point as a whole is shorter than the length of the binary data obtained by encoding a single data point using the 8421 encoding method, the sixth and third data points can be encoded into shorter binary data.

[0019] In conjunction with the first aspect, in one possible implementation, before the first terminal encodes its first user ID into binary first data at the Satellite Link Control (SLC) layer, the method may further include: the first terminal detecting a first operation, the first operation being used to instruct the first terminal to send a first message to the second terminal; the first terminal compressing and encoding the second user ID of the second terminal into seventh data at the Application Programming (APP) layer; and the first terminal generating a first message message at the APP layer, the first message message including a message header and message data; the message header including the seventh data, and the message data including the content of the first message.

[0020] This reduces the number of bits occupied by the user ID in the message header.

[0021] In conjunction with the first aspect, in one possible implementation, after the first terminal generates the first message message at the APP layer, the method may further include: the first terminal sending the first message message to the SLC layer to obtain one or more Satellite Link Control Layer Service Data Units (SLC SDUs), wherein the one or more SLC SDUs include the first SLC SDU; and the first terminal segmenting the first SLC SDU into one or more user frames, wherein the one or more user frames include the first user frame.

[0022] In conjunction with the first aspect, in one possible implementation, the method may further include: a first terminal receiving a second user frame sent by a BeiDou network device, the second user frame being sent from the second terminal to the first terminal; the first terminal decoding and decompressing the user ID field in the frame header information of the second user frame at the SLC layer to obtain the first user ID of the first terminal.

[0023] In this way, the terminal can decompress the terminal's user ID from the user ID field in the frame header information of the user frame.

[0024] In conjunction with the first aspect, in one possible implementation, the method may further include: a first terminal receiving a second user frame sent by a BeiDou network device, the second user frame being sent from the second terminal to the first terminal; the first terminal decoding and decompressing the user ID field in the frame header information of the second user frame at the SLC layer to obtain user ID data; if the first terminal determines that the user ID data is the same as the first user ID, the first terminal uploading the second user frame to the message data aggregation MDCP layer; if the first terminal determines that the user ID data is different from the first user ID, the first terminal discarding the second user frame.

[0025] In conjunction with the first aspect, in one possible implementation, after the first terminal decodes and decompresses the user ID field in the frame header information of the second user frame at the SLC layer to obtain the first user ID of the first terminal, the method may further include: the first terminal uploading the user data in the second user frame to the application layer to obtain a second message packet; the first terminal decoding and decompressing the user ID field in the header of the second message packet at the APP layer to obtain the second user ID of the second terminal; and the first terminal determining, based on the second user ID, that the second message packet was sent by the second terminal.

[0026] Secondly, a data compression method is provided in a satellite communication system. This method may include: a BeiDou network device encoding a first user ID of a first terminal into binary first data at the Satellite Link Control (SLC) layer. The first user ID includes second and third data. The first data includes binary fourth and fifth data. The fourth data is encoded from sixth data, which is compressed from the second data. The length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. The BeiDou network device fills the first data into the user ID field of the frame header information of a second user frame at the SLC layer. The BeiDou network device then sends the second user frame to the first terminal.

[0027] The first user ID can be the mobile phone number of the first terminal, the second data can be the domestic destination code (NDC) in the mobile phone number, and the third data can be the customer number (SN) in the mobile phone number.

[0028] This reduces the number of bits allocated to the user ID in the user frame header information. When BeiDou network equipment sends user frames to terminals, it reduces header overhead.

[0029] In conjunction with the second aspect, in one possible implementation, before the BeiDou network device encodes the first user ID of the first terminal into binary first data at the Satellite Link Control Layer (SLC), the method may further include: the BeiDou network device acquiring the first user ID of the first terminal.

[0030] In conjunction with the second aspect, in one possible implementation, the BeiDou network device obtains the first user ID of the first terminal by: the BeiDou network device receiving a first user frame sent by the first terminal, wherein the user ID field in the frame header information of the first user frame is used to indicate the first user ID of the first terminal; and the BeiDou network device decoding the first user ID from the first user frame.

[0031] In conjunction with the second aspect, in one possible implementation, the BeiDou network device obtains the first user ID of the first terminal by: the BeiDou network device receiving a first user frame sent by the first terminal, wherein the user ID field in the frame header information of the first user frame is used to indicate the first data; and the BeiDou network device decompressing and decoding the first data to obtain the first user ID.

[0032] In conjunction with the second aspect, in one possible implementation, the BeiDou network device obtains the first user ID of the first terminal by: the BeiDou network device receiving a second message, the second message being sent from the second terminal to the first terminal via the BeiDou network device, the second message including a user ID field indicating the first user ID of the first terminal; and the BeiDou network device decoding the first user ID from the user ID field in the header of the second message.

[0033] In conjunction with the second aspect, in one possible implementation, the BeiDou network device encodes the first user ID of the first terminal into binary first data at the Satellite Link Control (SLC) layer, including: the BeiDou network device compressing the second data in the first user ID of the first terminal into sixth data at the SLC layer, wherein the first user ID is composed of the second data and the third data, and the data length of the sixth data is less than that of the second data; the BeiDou network device encoding the sixth data into fourth data and the third data into fifth data at the SLC layer; and the BeiDou network device combining the fourth data and the fifth data into the first data.

[0034] This reduces the number of bits allocated to the user ID in the frame header information of user frames.

[0035] In conjunction with the second aspect, in one possible implementation, the BeiDou network device compresses the second data in the first user ID of the first terminal into the sixth data at the SLC layer, including: the BeiDou network device maps the second data in the first user ID to the sixth data in the mapping table at the SCL layer; the mapping table includes multiple values ​​of second data and multiple values ​​of sixth data, wherein the multiple values ​​of second data include the second data of the first value, the multiple values ​​of sixth data include the sixth data of the second value, and the second data of the first data is mapped to the sixth data of the second value.

[0036] In this way, a second piece of data can be compressed into a sixth piece of data with a shorter length. Furthermore, the second and sixth pieces of data have a one-to-one correspondence, preventing a single compressed piece of data from corresponding to a single uncompressed piece of data. This ensures that no errors occur during decoding.

[0037] In conjunction with the second aspect, in one possible implementation, the BeiDou network device compresses the second data in the first user ID of the first terminal into the sixth data at the SLC layer, including: the BeiDou network device subtracts a preset offset value from the second data in the first user ID at the SCL layer to obtain the sixth data.

[0038] In this way, a second piece of data can be compressed into a sixth piece of data with a shorter data length.

[0039] In conjunction with the second aspect, in one possible implementation, the BeiDou network equipment encodes the sixth data into the fourth data and the third data into the fifth data at the SLC layer, including: the first terminal converts the sixth data as a decimal integer into the fourth data in binary at the SLC layer; and converts the third data as a decimal integer into the fifth data in binary.

[0040] Because the length of the binary data obtained by encoding a single data point as a whole is shorter than the length of the binary data obtained by encoding a single data point using the 8421 encoding method, the sixth and third data points can be encoded into shorter binary data.

[0041] Thirdly, a satellite communication system is provided, which may include a first terminal and BeiDou network equipment. Wherein: The first terminal is used to encode the first user ID of the first terminal into binary first data at the Satellite Link Control Layer (SLC). The first user ID includes second data and third data. The first data includes binary fourth data and binary fifth data. The fourth data is encoded from the sixth data. The sixth data is compressed from the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. The first terminal is used to fill the first data into the user ID field in the frame header information of the first user frame at the SLC layer; The first terminal is used to send the first user frame to the BeiDou network equipment. The BeiDou network equipment is used to receive the first user frame and decode the first user ID from the user ID field in the frame header information of the first user frame.

[0042] In conjunction with the third aspect, in one possible implementation, BeiDou network equipment is used for: At the Satellite Link Control (SLC) layer, the first user ID of the first terminal is encoded into binary first data. The first user ID includes second and third data. The first data includes binary fourth and fifth data. The fourth data is encoded from the sixth data. The sixth data is compressed from the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. In the SLC layer, the first data is filled into the user ID field in the frame header information of the second user frame.

[0043] In conjunction with the third aspect, in one possible implementation, the BeiDou network equipment can also execute the methods in any of the possible implementations in the second aspect mentioned above.

[0044] In conjunction with the third aspect, in one possible implementation, the terminal can also execute the methods in any of the possible implementations of the first aspect mentioned above.

[0045] Fourthly, this application provides a communication device including one or more processors, one or more memories, and a transceiver. The transceiver, the one or more memories, and the one or more processors are coupled together. The one or more memories are used to store computer program code, which includes computer instructions. When the one or more processors execute the computer instructions, the communication device performs the method in any of the possible implementations of the first aspect described above.

[0046] The communication device can be a terminal or other product-type equipment.

[0047] Fifthly, this application provides a communication device including one or more processors, one or more memories, and a transceiver. The transceiver, the one or more memories, and the one or more processors are coupled together. The one or more memories are used to store computer program code, which includes computer instructions. When the one or more processors execute the computer instructions, the communication device performs the method in any of the possible implementations of the second aspect described above.

[0048] The communication device can be a BeiDou network device, or any network element or a combination of multiple network elements in a BeiDou network device.

[0049] In a sixth aspect, this application provides a computer storage medium including computer instructions that, when executed on a computer, cause the computer to perform the method in any possible implementation of the first aspect described above.

[0050] In a seventh aspect, this application provides a computer storage medium including computer instructions that, when executed on a computer, cause the computer to perform the method in any possible implementation of the second aspect described above.

[0051] Eighthly, this application provides a computer program product that, when run on a computer, causes the computer to perform the method in any possible implementation of the first aspect described above.

[0052] Ninthly, this application provides a computer program product that, when run on a computer, causes the computer to perform the method in any possible implementation of the second aspect described above.

[0053] In a tenth aspect, this application provides a chip or chip system for use in a terminal, including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method in any possible implementation of the first aspect described above. Attached Figure Description

[0054] Figure 1 This is a schematic diagram of the architecture of a Beidou communication system 10 provided in an embodiment of this application; Figure 2 This is a schematic diagram of the data ingress and egress transmission process in a BeiDou communication system provided in an embodiment of this application; Figure 3 This is a schematic diagram of the protocol encapsulation architecture for inbound data of a Beidou communication system 10 provided in an embodiment of this application; Figure 4 This is a schematic diagram of the protocol parsing architecture for inbound data of a Beidou communication system 10 provided in an embodiment of this application; Figure 5 This is a schematic diagram of the protocol encapsulation architecture for outbound data of a Beidou communication system 10 provided in an embodiment of this application; Figure 6 This is a schematic diagram of the protocol parsing architecture for outbound data of a Beidou communication system 10 provided in an embodiment of this application; Figure 7 This is a schematic diagram of the frame format of an SLC frame provided in an embodiment of this application; Figure 8 This is a schematic diagram of another SLC frame format provided in an embodiment of this application; Figure 9 This is a schematic diagram of another ACK frame format provided in the embodiments of this application; Figure 10 This is a schematic diagram of the frame format of another application layer receipt frame provided in the embodiments of this application; Figure 11A This is a schematic flowchart of a data compression method in a BeiDou communication system provided in an embodiment of this application; Figure 11B This is a schematic flowchart of a data compression method in a BeiDou communication system provided in an embodiment of this application; Figure 12 This is a schematic diagram of the structure of the terminal 100 provided in the embodiments of this application; Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application; Figure 14 This is a schematic diagram of another communication device provided in an embodiment of this application; Figure 15 This is a schematic diagram of another communication device provided in an embodiment of this application; Figure 16 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0055] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items.

[0056] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0057] The following describes a Beidou communication system 10 provided in an embodiment of this application.

[0058] Figure 1 A schematic diagram of the architecture of a Beidou communication system 10 provided in an embodiment of this application is shown.

[0059] like Figure 1 As shown, the BeiDou communication system 10 may include a terminal 100, a BeiDou short message satellite 21, a BeiDou network device 200, a short message center 25, and a terminal 300. Optionally, the BeiDou communication system 10 may also include a national emergency rescue platform 26 and a national emergency rescue center 27.

[0060] Terminal 100 can send short message information to BeiDou short message satellite 21. BeiDou short message satellite 21 only acts as a relay, directly forwarding the short message information sent by terminal 100 to BeiDou network equipment 200 on the ground. BeiDou network equipment 200 can parse the short message information forwarded by the satellite according to the BeiDou communication protocol and forward the message content of the general message type parsed from the short message information to the short message service center (SMSC) 25. Short message service center 25 can forward the message content to terminal 300 through traditional cellular communication network. BeiDou network equipment 200 can also send emergency distress messages sent by terminal 100 to the National Emergency Rescue Center 27 through the National Emergency Rescue Platform 26.

[0061] Terminal 300 can also send short messages to Short Message Service (SMS) Center 25 via traditional cellular communication networks. SMS Center 25 can forward the short messages from Terminal 300 to BeiDou network device 200. BeiDou network device 200 can then relay the short messages from Terminal 300 to Terminal 100 via BeiDou short message satellite 21.

[0062] The aforementioned BeiDou network equipment 200 may include a BeiDou ground transceiver station 22, a BeiDou central station 23, and a BeiDou short message fusion communication platform 24. The BeiDou ground transceiver station 22 may include one or more devices with transmitting and receiving functions, or it may include one or more devices with both transmitting and receiving functions; this is not limited here. The BeiDou ground transceiver station 22 can be used for data processing by the BeiDou network equipment 200 at the physical layer protocol (PHY) layer. The BeiDou central station 23 can be used for data processing by the BeiDou network equipment 200 at the satellite link control protocol (SLC) layer and the message data convergence protocol (MDCP) layer. The BeiDou short message fusion communication platform 24 can be used for data processing at the application layer protocol (APP) layer.

[0063] Because the BeiDou-10 communication system communicates via satellite links, its main characteristics are: long latency (approximately 270ms one-way) and high link loss. Currently, the BeiDou-10 system mainly supports bursty short message services and does not support link status management, mobility management, broadcast control information, etc.

[0064] Among them, the Beidou network equipment 200 can operate in full-duplex mode, allowing it to send and receive data simultaneously.

[0065] In this embodiment, data sent from terminal 100 to BeiDou network device 200 can be referred to as inbound data. Data sent from BeiDou network device 200 to terminal 100 can be referred to as outbound data. Figure 2 As shown, terminal 100 can send inbound data to BeiDou short message satellite 21, and then the BeiDou short message satellite 21 sends the inbound data to BeiDou ground transceiver station 22. BeiDou ground transceiver station 22 can then send the inbound data to BeiDou central station 23. BeiDou central station 23 in BeiDou network equipment 200 can send outbound data to BeiDou ground transceiver station 22. Then, BeiDou ground transceiver station 22 sends the outbound data to BeiDou short message satellite 21, and then the BeiDou short message satellite 21 sends it to terminal 100.

[0066] The following describes a protocol encapsulation architecture for inbound data of a Beidou communication system 10 provided in the embodiments of this application.

[0067] Figure 3 This paper illustrates a schematic diagram of the protocol encapsulation architecture for inbound data of a Beidou communication system 10 provided in an embodiment of this application.

[0068] like Figure 3 As shown, the BeiDou message transmission protocol layer on terminal 100 can be divided into the application layer protocol (APP), message data convergence protocol (MDCP), satellite link control protocol (SLC) and physical layer protocol (PHY).

[0069] When terminal 100 sends data to BeiDou network device 200, the workflow of the BeiDou message transmission protocol on terminal 100 can be as follows: At the APP layer, terminal 100 can compress the original data into compressed data using a compression algorithm, and add a compression indicator field to the front of the compressed data. This compression indicator field indicates the type of compression algorithm used. Next, terminal 100 can encrypt the compressed data to obtain encrypted data, and add an encryption algorithm field to the header of the encrypted data. This encryption algorithm field indicates the type of encryption algorithm used. Terminal 100 can then encapsulate the encrypted data, the compression indicator field, and the encryption indicator field into an application layer message and send it to the MDCP layer. This application layer message includes a header and data. The header includes the compression indicator field and the encryption indicator field, etc. The data includes the aforementioned encrypted data.

[0070] Optionally, terminal 100 can also encrypt the compression instruction field together with the compressed data to obtain encrypted data.

[0071] At the MDCP layer, terminal 100 can obtain application layer messages sent from the APP layer through the inter-layer interface and treat the application layer messages as an MDCP service data unit (SDU). At the MDCP layer, terminal 100 can add padding data to the end of the MDCP SDU to a specified length and add a redundancy length indicator field to the header of the MDCP SDU. This redundancy length indicator field indicates the length of the padding data. Terminal 100 can split the MDCP SDU with the padding data and the added redundancy length indicator field into one or more fixed-length MDCP segments (M_segement), and add a successor indicator field to the header of each MDCP segment to obtain an MDCP protocol data unit (PDU). That is, an MDCP PDU includes an M_segement and a successor indicator field. The successor indicator field indicates whether the current MDCP PDU is the starting MDCP PDU, intermediate MDCP PDU, or last MDCP PDU among multiple consecutively sent MDCP PDUs; or it can be a single MDCP PDU sent independently.

[0072] At the SLC layer, terminal 100 can obtain the MDCP PDU issued by the MDCP layer through the inter-layer interface, and use it as an SLCSDU. At the SLC layer, terminal 100 can segment the SLC SDU into one or more (up to four) fixed-length SLC segment data (S_segement), and add frame header information to the header of each S_segement to obtain the SLC PDU. The frame header information includes a service data unit alternated indicator (SAI) field, a total number of frames field, and a frame sequence number field.

[0073] The SAI field can be used to indicate whether the SLC PDU belongs to an unsent SLC SDU.

[0074] The total number of frames field can be used to indicate the total number of SLC PDUs included in the SLC SDU to which this SLC PDU belongs.

[0075] The frame sequence number field can be used to indicate the sequence number of the SLC PDU within its respective SLC SDU.

[0076] At the PHY layer, terminal 100 can obtain the SLC PDU issued by the SLC layer through the inter-layer interface, using it as a code block for the PHY layer. A synchronization header is added to the beginning of the code block, and a checksum field is added to the end. In the aforementioned BeiDou communication system 10, cyclic redundancy check (CRC) can be used to verify the code block; therefore, the checksum field can include the CRC code. Terminal 100 can encode the code block and checksum field (e.g., polar encoding) to obtain coded data. Pilot signals are then inserted into the coded data to obtain pilot coded data. Terminal 100 then modulates the synchronization header and pilot coded data sequentially using the underlying hardware to obtain modulated data. Terminal 100 can spread the modulated data to obtain spread-modulated data. Terminal 100 can then send the spread-modulated data to BeiDou short message satellite 21, which relays it to BeiDou network equipment 200.

[0077] The following describes a protocol parsing architecture for inbound data of a Beidou communication system 10 provided in an embodiment of this application.

[0078] Figure 4This paper illustrates a schematic diagram of the protocol parsing architecture for inbound data of a Beidou communication system 10 provided in an embodiment of this application.

[0079] like Figure 4 As shown, the BeiDou short message transmission protocol layer of the BeiDou network device 200 can be divided into an application layer protocol (APP), a message data convergence protocol (MDCP), a satellite link control protocol (SLC), and a physical layer protocol (PHY). The BeiDou network device 200 may include a BeiDou ground transceiver station 22, a BeiDou central station 23, and a BeiDou short message fusion communication platform 24. The BeiDou ground transceiver station 22 is responsible for protocol processing at the PHY layer. The BeiDou central station 23 is responsible for protocol processing at the SLC and MDCP layers. The BeiDou short message fusion communication platform 24 is responsible for protocol processing at the APP layer.

[0080] When BeiDou network device 200 receives data sent by terminal 100, the workflow of the BeiDou short message transmission protocol layer of BeiDou network device 200 can be as follows: At the PHY layer, the BeiDou network device 200 can acquire the modulated and spread-spectrum pilot coded data sent by the terminal 100. The BeiDou network device 200 can despread the received spread-spectrum modulated data to obtain modulated data. Then, the BeiDou network device 200 can demodulate the modulated data to obtain pilot coded data. Next, the BeiDou network device 200 removes the pilot information from the pilot coded data to obtain coded data. Then, the BeiDou network device 200 can decode the coded data and verify the integrity of the code block using the checksum in the check bit field. If complete, the BeiDou network device 200 can extract the code block and present it to the SLC layer through the inter-layer interface as the SLC PDU of the SLC layer.

[0081] At the SLC layer, the BeiDou network device 200 can combine SLC PDUs belonging to the same SLC SDU into a single SLC SDU based on the frame header information of the SLC PDU. The BeiDou network device 200 can then present the SLC SDU to the MDCP layer through the inter-layer interface, serving as the MDCP PDU for the MDCP layer.

[0082] At the MDCP layer, the BeiDou network device 200 can concatenate all MDCP PDUs belonging to the same MDCP SDU into a single MDCP SDU. The BeiDou network device 200 can then present the MDCP SDU to the APP layer through the inter-layer interface, serving as an application layer message received by the APP layer.

[0083] At the APP layer, the Beidou network device 200 can decrypt and decompress the application layer message based on the message header to obtain the original data.

[0084] In the embodiments of this application, the above protocol processing procedure is only an example for illustration, and this application does not limit the specific operation of protocol processing.

[0085] The following describes a protocol encapsulation architecture for outbound data of a Beidou communication system 10 provided in the embodiments of this application.

[0086] Figure 5 This paper illustrates a schematic diagram of the protocol encapsulation architecture for outbound data of a Beidou communication system 10 provided in an embodiment of this application.

[0087] like Figure 5 As shown, the BeiDou short message transmission protocol layer in the BeiDou network equipment 200 can be divided into an application layer protocol (APP), a message data convergence protocol (MDCP), a satellite link control protocol (SLC), and a physical layer protocol (PHY). The BeiDou network equipment 200 may include a BeiDou ground transceiver station 22, a BeiDou central station 23, and a BeiDou short message fusion communication platform 24. The BeiDou ground transceiver station 22 is responsible for protocol processing at the PHY layer. The BeiDou central station 23 is responsible for protocol processing at the SLC and MDCP layers. The BeiDou short message fusion communication platform 24 is responsible for protocol processing at the APP layer.

[0088] When BeiDou network device 200 sends data to terminal 100, the workflow of the BeiDou short message transmission protocol in BeiDou network device 200 can be as follows: At the APP layer, the BeiDou network device 200 can compress the raw data into compressed data using a compression algorithm, and add a compression indicator field to the front of the compressed data. This compression indicator field indicates the type of compression algorithm used. Next, the BeiDou network device 200 can encrypt the compressed data, obtaining encrypted data, and add an encryption algorithm field to the header of the encrypted data. This encryption algorithm field indicates the type of encryption algorithm used. The BeiDou network device 200 can then encapsulate the encrypted data, the compression indicator field, and the encryption indicator field into an application layer message and send it to the MDCP layer. This application layer message can include a message header and message data. The message header may include the compression indicator field, encryption indicator field, etc. The message data includes the aforementioned encrypted data.

[0089] Alternatively, in one possible implementation, the BeiDou network device 200 divides the MDCP SDU into multiple MDCP PDUs at the MDCP layer, and the BeiDou network device 200 can transmit the multiple MDCP PDUs together to the SLC layer of the BeiDou network device 200.

[0090] At the MDCP layer, the BeiDou network device 200 can obtain application layer messages sent from the APP layer through the inter-layer interface and treat each application layer message as an MDCP SDU. At the MDCP layer, the BeiDou network device 200 can split an MDCP SDU into one or more fixed-length MDCP segments (M_segement) and add a successor indication field to the header of each MDCP segment to obtain an MDCP PDU. That is, an MDCP PDU includes an M_segement and a successor indication field. The successor indication field can be used to indicate whether the current MDCP PDU is the starting, middle, or last MDCP PDU of a series of consecutively sent MDCP PDUs; or it can be a single, independently sent MDCP PDU.

[0091] At the SLC layer, the BeiDou network device 200 can obtain the MDCP PDU issued by the MDCP layer through the inter-layer interface, and use it as the SLC SDU. At the SLC layer, the BeiDou network device 200 can segment the SLC SDU into one or more (up to four) fixed-length SLC segment data (S_segement), and add frame header information to the header of each S_segement to obtain the SLC PDU.

[0092] At the PHY layer, the BeiDou network device 200 can obtain SLC PDUs from the SLC layer through the inter-layer interface. The BeiDou network device 200 can obtain SLC PDUs from one or more users from the SLC layer. The BeiDou network device 200 can concatenate the SLC PDUs from multiple users together, add the frame header of the physical frame (e.g., version number) as a code block for the PHY layer, and add a check bit (e.g., cyclic redundancy check (CRC) code) to the end of the code block. The code block and CRC code are then encoded (e.g., polar encoding). The encoded physical frame, plus a reserved segment, can form the encoded data of a fixed-length physical time slot message branch (S2C_d branch). The BeiDou network device 200 can place multiple SLC PDUs from one user into different physical frames. Then, the BeiDou network device 200 combines the encoded data of the S2C_d branch with the pilot information of the pilot branch (S2C_p branch) to form pilot encoded data, i.e., outbound data. The Beidou network device 200 can send outgoing data to the Beidou short message satellite 21, which then relays it to the terminal 100.

[0093] Understandably, the pilot information of the S2C_p branch is related to the satellite beam. When the satellite beam number is known, the pilot information of the S2C_p branch is also known and does not require decoding. However, the encoded data of the S2C_d branch requires decoding.

[0094] The following describes a protocol parsing architecture for outbound data of a Beidou communication system 10 provided in the embodiments of this application.

[0095] Figure 6 This paper illustrates a schematic diagram of the protocol parsing architecture for outbound data of a Beidou communication system 10 provided in an embodiment of this application.

[0096] like Figure 6 As shown, the BeiDou short message transmission protocol layer of terminal 100 can be divided into application layer protocol (APP), message data convergence protocol (MDCP), satellite link control protocol (SLC) and physical layer protocol (PHY).

[0097] When terminal 100 receives data sent by BeiDou network equipment, the workflow of the BeiDou short message transmission protocol layer of terminal 100 can be as follows: At the PHY layer, terminal 100 can obtain the modulated and spread-spectrum pilot coded data sent by BeiDou network device 200. Terminal 100 can despread the received spread-spectrum modulated data to obtain modulated data. Then, terminal 100 can demodulate the modulated data to obtain pilot coded data. Next, terminal 100 can remove the pilot information from the pilot coded data to obtain coded data. Then, terminal 100 can decode the coded data and verify the integrity of the code block through the check bit field. If complete, terminal 100 can extract the code block and present it to the SLC layer through the inter-layer interface as the SLC PDU of the SLC layer.

[0098] Here, the pilot coded data is the outgoing data sent by the Beidou network device 200 mentioned above. The outgoing data consists of the coded data of the S2C_d branch and the pilot information of the pilot branch (S2C_p branch).

[0099] At the SLC layer, terminal 100 can concatenate SLC PDUs belonging to the same SLC SDU into a single SLC SDU based on the frame header information of the SLC PDU. Terminal 100 can then present the SLC SDU to the MDCP layer through the inter-layer interface, serving as the MDCP PDU for the MDCP layer.

[0100] At the MDCP layer, terminal 100 can concatenate all MDCP PDUs belonging to the same MDCP SDU into a single MDCPSDU. Terminal 100 can then present the MDCP SDU to the APP layer through the inter-layer interface, serving as an application layer message received by the APP layer.

[0101] At the APP layer, terminal 100 can decrypt and decompress the application layer message based on the message header to obtain the original data.

[0102] In the embodiments of this application, the above protocol processing procedure is only an example for illustration, and this application does not limit the specific operation of protocol processing. In the BeiDou communication system 10, terminal 100 can generate user frames at the SLC layer. The header information of this user frame may include a user ID field, which contains the user ID of terminal 100. The user frame generated by terminal 100 may include an SLC PDU, an acknowledgement character (ACK) frame, and an application layer acknowledgment frame. BeiDou network device 200 can also generate user frames at the SLC layer. The header information of this user frame may include a user ID field, which contains the user ID of the terminal receiving the user frame. The user frame generated by BeiDou network device 200 may also include an SLCPDU, an ACK frame, and an application layer acknowledgment frame.

[0103] Figure 7 The image shows a frame format of an inbound SLC PDU provided in an embodiment of this application.

[0104] like Figure 7 As shown, when entering the network, the frame header information of the SLC PDU sent by terminal 100 to Beidou network device 200 may include: version number field, subtype indication field, user identity document (ID) field, acknowledgment mode enable (AM enable) field, total number of frames field, frame sequence number field, SAI field, and reserve (RSV) field.

[0105] The version number field indicates the version of the BeiDou communication protocol, allowing the protocol to evolve for each frame type. This embodiment does not limit the length of the version number field.

[0106] The subtype field indicates that the frame type of the user frame sent by terminal 100 is a general data frame, i.e., SLCPDU. The length of the subtype field can be 1 bit. For example, a value of "0" in the subtype field indicates that the user frame is a general data frame, i.e., SLC PDU. A value of "1" in the subtype field indicates that the user frame sent by terminal 100 is an ACK frame. Since SLC PDU is a general data frame sent by terminal 100, the subtype field in the SLC PDU takes the value of "0". This embodiment does not limit the length of the subtype field.

[0107] The User ID field can be used to indicate the user ID of terminal 100. The User ID field contains the user ID of terminal 100.

[0108] The AM enable field can be used to indicate whether the terminal 100 uses acknowledgment mode to transmit the SLC PDU. This application embodiment does not limit the length or specific value of the AM enable field.

[0109] The total frame count field indicates the total number of SLC PDUs contained within the SLC SDU containing this SLC PDU. The total frame count field can be 2 bits long. When the total frame count field is 2 bits long, an SLC PDU can contain a maximum of 4 SLC PDUs.

[0110] The frame sequence number field can be used to indicate the sequence number of the SLC PDU within an SLC SDU. The length of the frame sequence number field can be 2 bits. This application embodiment does not limit the length of the frame sequence number field.

[0111] The Service Data Unit Alternated Indicator (SAI) field occupies 1 bit. When terminal 100 transmits SLC PDUs in acknowledged mode (AM-enable field value is "1"), the SAI field can be used to indicate whether the SLC PDU is a retransmitted SLC PDU. When terminal 100 transmits SLC PDUs in unacknowledged mode (AM-enable field value is "0"), the SAI field can be reserved for other functions.

[0112] The RSV field can be used for byte alignment of the frame header data and reserved for other functions. The length of the RSV field can be 4 bits or other bit numbers. This application embodiment does not limit the length of the RSV field.

[0113] Understandable Figure 7 The frame format shown for the outbound SLC PDU is merely an example. The order of the cell parameters in the frame header information field is not limited in this application embodiment.

[0114] Figure 8 The image shows a frame format of an outbound SLC PDU provided in an embodiment of this application.

[0115] like Figure 8 As shown, when leaving the station, the frame header information of the SLC PDU sent by the Beidou network device 200 to the terminal 100 may include: frame type field, acknowledge mode enable (AM enable) field, frame length field, user ID field, total number of frames field and frame sequence number field.

[0116] The frame type field indicates the type of the SLC frame. The frame type field can be 2 bits long. This application does not limit the length of the frame type field in its embodiments.

[0117] The AM enable field indicates whether the BeiDou network device 200 uses acknowledgment mode to transmit the SLC PDU. The length of the AM enable field can be 1 bit. If the value in the AM enable field is the first value (e.g., 1), it indicates that the terminal 100 needs to reply with an ACK after receiving the SLC PDU sent by the BeiDou network device 200. If the value in the AM enable field is the second value (e.g., 0), it indicates that the terminal 100 does not need to reply with an ACK after receiving the SLC PDU from the BeiDou network device 200. This application embodiment does not limit the length or specific value of the AM enable field.

[0118] The frame length field is used to identify the length of the SLC frame, and the length of the frame length field can be 8 bits. This application embodiment does not limit the length of the frame length field.

[0119] The User ID field can be used to indicate that the SLC PDU was sent to terminal 100 by Beidou network device 200. The User ID field may contain the user ID of terminal 100.

[0120] The total frame count field indicates the total number of SLC PDUs contained within the SLC SDU containing this SLC PDU. The total frame count field can be 2 bits long. When the total frame count field is 2 bits long, an SLC PDU can contain a maximum of 4 SLC PDUs.

[0121] The frame sequence number field can be used to indicate the sequence number of the SLC PDU within an SLC SDU. The length of the frame sequence number field can be 2 bits. This application embodiment does not limit the length of the frame sequence number field.

[0122] Understandable Figure 8 The frame format of the outbound SLC PDU shown is merely an example. The embodiments of this application do not limit the order of the cell parameters in the frame header information field.

[0123] Figure 9 The image shows a frame format for an ACK frame provided in an embodiment of this application.

[0124] like Figure 9As shown, an ACK frame may include frame header information and user information. The frame header information may include a frame type field and a user ID field. The frame type field can be used to indicate the type of the ACK frame. The length of the frame type field can be 2 bits. This embodiment does not limit the length of the frame type field. The user ID field can indicate the user ID of the terminal sending or receiving the ACK frame.

[0125] The ACK frame is used to indicate whether the terminal 100 that sent the ACK frame or the Beidou network device 200 successfully received the SLCSDU.

[0126] Understandable Figure 9 The frame format of the ACK frame shown is merely an example. The embodiments of this application do not limit the order of the cell parameters in the frame header information field.

[0127] Figure 10 The image shows a frame format for an application layer receipt frame provided in an embodiment of this application.

[0128] like Figure 10 As shown, the application layer receipt frame may include frame header information and user information. The frame header information may include a frame type field and a user ID field. The frame type field can be used to indicate the type of the application layer receipt frame. The length of the frame type field can be 2 bits. This embodiment does not limit the length of the frame type field. The user ID field can indicate the user ID of the terminal sending or receiving the application layer receipt frame.

[0129] The application layer acknowledgment frame is used to indicate whether the terminal 100 or the BeiDou network device 200 that sent the application layer acknowledgment frame successfully parsed the received application layer message.

[0130] Understandable Figure 10 The frame format of the application layer receipt frame shown is merely an example. This application embodiment does not limit the order of the information cell parameters in the frame header information field.

[0131] In this embodiment, the binary data in the user ID field included in the frame header information of the user frame can indicate the mobile phone number of terminal 100. Currently, mobile phone numbers worldwide use the E.164 code format published by the International Telecommunication Union (ITU). E.164 is an international public telephone numbering scheme defined by the ITU for use in the public switched telephone network (PSTN) and some data networks, and it defines the specific code format. E.164 defines a maximum of 15 digits, and the complete number includes an international calling prefix. E.164 defines the specific format of the mobile subscriber international integrated service digital network number (MSISDN).

[0132] An MSISDN number is a number that a calling user dials to make a call to a user in a mobile communication network. The format of an MSISDN number is briefly described below. Table 1 shows an example of the MSISDN format.

[0133] Table 1

[0134] As shown in Table 1, MSISDN numbers can be arranged according to Format 1, where Format 1 is: MSISDN = CC + NDC + SN (CC = Country Code; NDC = National Destination Code; SN = Subscriber Number). That is, the MSISDN consists of the country code (CC), the national destination code (NDC), and the subscriber number (SN).

[0135] According to the current definition and distribution of country codes, CC is the longest with 4 digits, such as Guam's 1671, while most are two digits, such as China's 86.

[0136] NDC, also known as Network Access Code, refers to the network access codes that each sovereign state can authorize one or more network operators to build and operate mobile networks. For example, among China's three major mobile operators, China Mobile's network access codes are 134-139, 150-152, 188, etc.; China Unicom's network access codes are 130-132, 185, 186, etc.; and China Telecom's network access codes are 133, 153, 180, 189, etc.

[0137] The SN is no more than 8 digits.

[0138] The structure of MSISDN in Format 1 can be expressed as follows: MSISDN=CC+N1N2N3+H0H1H2H3+ABCD The NDC portion can consist of three digits, N1N2N3, while the SN portion can consist of eight digits, H0H1H2H3 and ABCD. H0H1H2H3 can be the identification number of the Home Location Register (HLR) for each mobile service's local network within the SN, and ABCD represents the mobile subscriber code.

[0139] As shown in Table 1, the MSISDN number can be “8613966666666”, where “86” is the CC code, “139” can be the NDC code, or N1N2N3; “66666666” can be the SN code, or H0H1H2H3+ABCD.

[0140] In this embodiment, the portion of the MSISDN that does not contain the CC (i.e., NDC and SN) can be referred to as the terminal's domestic identification number, or as a mobile phone number, or simply a phone number. For ease of description, the portion of the MSISDN that does not contain the CC will be referred to as the phone number below. In China, a terminal's phone number is generally an 11-digit decimal string.

[0141] Generally, MSISDN numbers are encoded using binary coded decimal (BCD) encoding. BCD uses four bits to store a decimal digit. Thus, an 11-digit mobile phone number (i.e., the MSISDN code excluding the CC) requires 44 bits of capacity when encoded using BCD. For example, as shown in Table 2, the mobile phone number "13966666666" can be encoded into a 44-bit binary string using BCD.

[0142] Table 2

[0143] As shown in Table 2, each decimal character in the mobile phone number "13966666666" can be encoded into a four-bit binary string. For example, the decimal character "1" can be encoded into the four-bit binary string "0001" using BCD encoding. The decimal character "3" can be encoded into the four-bit binary string "0011" using BCD encoding. The decimal character "9" can be encoded into the four-bit binary string "1001" using BCD encoding. The decimal character "6" can be encoded into the four-bit binary string "0110" using BCD encoding. Thus, the mobile phone number "13966666666" can be encoded into a 44-bit binary string "0001 0011 1001 0110 0110 0110 0110 0110 0110 0110 0110". This requires a 44-bit capacity for the user ID field, resulting in a large frame header overhead.

[0144] This application provides a data compression method in a satellite communication system. This data compression method can be applied to a terminal 100. The compression method includes: the terminal 100 encoding its user ID into binary first data. The user ID may contain second and third data. The first data includes binary fourth and fifth data. The fourth data is encoded from sixth data, which is compressed from the second data, and the length of the sixth data is less than the length of the second data. The fifth data is encoded from the third data. The terminal 100 fills the first data into the user ID field included in the frame header information of a first user frame. The first data in the user ID field can be used to indicate the user ID of the terminal 100.

[0145] Among them, the user ID can be the mobile phone number of terminal 100, the second data can be the NDC data in the mobile phone number of terminal 100, and the third data can be the SN data in the mobile phone number of terminal 100.

[0146] The compression method provided in this application embodiment allows the terminal 100 to compress its user ID, encode the compressed user ID, and fill it into the user ID field. This reduces the number of bits occupied by the user ID field, thereby reducing frame header overhead.

[0147] Figure 11A An exemplary flowchart of a data compression method in a satellite communication system provided in this application is shown. Taking a mobile phone number as an example, the data compression method may include the following steps: S101, Terminal 100 encodes the mobile phone number of Terminal 100 into binary data D1. The mobile phone number includes NDC1 and SN1. Data D1 includes data D2 and data D3. Data D2 is obtained by encoding data D4. Data D4 is obtained by compressing NDC1. The data length of data D4 is less than the data length of NDC1. Data D3 is obtained by encoding SN1.

[0148] Table 3

[0149] As shown in Table 3, the mobile phone number of terminal 100 may include NDC1 and SN1. Terminal 100 can compress NDC1 into data D4 at the SLC layer, where the data length of data D4 is less than the data length of NDC1. Then, data D4 is encoded into data D2, and SN1 is encoded into data D3. Data D2 and data D3 can be combined into data D1.

[0150] In this embodiment of the application, terminal 100 may be referred to as a first terminal. The user ID of terminal 100 may be referred to as a first user ID. Data D1 may be referred to as first data, NDC1 may be referred to as second data, SN1 may be referred to as third data, data D2 may be referred to as fourth data, data D3 may be referred to as fifth data, and data D4 may be referred to as sixth data.

[0151] If the mobile phone number of terminal 100 is from a country other than China, terminal 100 can convert the mobile phone number to a Chinese mobile phone number. In this embodiment of the application, a Chinese mobile phone number can be referred to as a domestic mobile phone number, and a mobile phone number from a country other than China can be referred to as a foreign mobile phone number.

[0152] In one possible implementation, terminal 100 can map all foreign mobile phone numbers to domestic mobile phone numbers. Terminal 100 can contain a mapping table that includes foreign numbers and their corresponding domestic numbers.

[0153] Alternatively, in one possible implementation, terminal 100 can convert the NDC in a foreign mobile phone number to a domestic NDC, and then combine the domestic NDC and the SN in the foreign mobile phone number into a mobile phone number.

[0154] In one possible implementation, terminal 100 can compress NDC1 into data D4, and then terminal 100 can encode data D4 into data D2.

[0155] Optionally, in one possible implementation, the process of terminal 100 compressing NDC1 into data D4 may include: terminal 100 mapping NDC1 to mapping table relationship data D4, where data D4 is the short message communication identity document (SMCID) corresponding to NDC1 in the mapping table relationship. SN1 can be converted into a binary short message communication subscriber number (SMCSN). That is, data D1 includes the encoded SMCID and SMCSN. Terminal 100 maintains a mapping table between NDC and SMCID.

[0156] For example, the mapping relationship between NDC and SMCID of domestic mobile phone numbers can be shown in Table 4.

[0157] Table 4

[0158] As shown in Table 4, the NDC (Network Data Center) segments of mobile phone numbers in China are currently distributed between 13x and 19x. Therefore, the mapping table shown in Table 4 can be used to achieve the mapping conversion from NDC to SMCID. When NDC is 130, it can be mapped to 1 in SMCID; when NDC is 139, it can be mapped to 10 in SMCID. When NDC is between 130 and 139, it can be mapped to 1 to 10 in SMCID. When NDC is between 144 and 159, it can be mapped to 11 to 26 in SMCID. When NDC is 162, it can be mapped to 27 in SMCID; when NDC is 165, it can be mapped to 28 in SMCID; when NDC is 166, it can be mapped to 29 in SMCID; when NDC is 167, it can be mapped to 30 in SMCID. When NDC is between 170 and 178, it can be mapped to 31 to 39 in SMCID. When the NDC is in the range of 180~189, it can be mapped to 40~49 in SMCID. When the NDC is 191, it can be mapped to 50 in SMCID. When the NDC is 195, it can be mapped to 51 in SMCID. When the NDC is 198, it can be mapped to 52 in SMCID. When the NDC is 199, it can be mapped to 53 in SMCID.

[0159] The value range of SMCID is generally 0x00 to 0x7F, encompassing 128 SMCID categories. A 7-bit binary number can hold 128 SMCIDs. Of these, the SMCID for dedicated terminals is fixed at 0, while the remaining 127 SMCIDs are used by civilian terminals.

[0160] Furthermore, optionally, only 54 SMCIDs are shown in Table 4. The remaining 74 SMCIDs can be reserved as resources. If the operator adds new NDCs in the future, the mapping relationship between the new NDCs and the reserved SMCIDs can be added to the mapping relationship table shown in Table 3 through over-the-air (OTA) upgrade.

[0161] In Table 4, NDCs can be referred to as the second set of data, and SMCIDs as the sixth set of data. Table 4 contains multiple NDCs and multiple SMCIDs. Each NDC corresponds one-to-one with a single SMCID.

[0162] Thus, in some feasible cases, SMCID encoding can yield 7 bits of binary data. If the binary data obtained by SMCID encoding is less than 7 bits, the high-order bits can be padded with 0s to make it 7 bits.

[0163] The value range of SN is 0 to 99999999, therefore a 27-bit binary number is needed to store all SNs. If the SMCSN obtained after encoding SN is less than 27 bits, the high-order bits of SMCSN can be padded with 0s to make it 27 bits.

[0164] For example, let's take the mobile phone number "13966666666" as an example. In the mobile phone number "13966666666", the NDC is "139" and the SN is "66666666". The NDC "139" can be mapped to "10" in Table 3, which is data D4. "10" can be encoded into the binary data "1010". Since "1010" is less than 7 bits, the high-order bits are padded with 0s, resulting in the 7-bit binary data "0001010". Therefore, the encoding result of NDC "139" is "0001010", which is data D2. "66666666" can be encoded into the binary data "111111100101000000101010", a 26-bit binary number. Since it's less than 27 bits, the high-order bits are padded with 0s, resulting in the 27-bit binary data "0111111100101000000101010". Therefore, the encoding result of the SN "66666666" is "0111111100101000000101010", which is also the data D3. Terminal 100 can combine the encoding result of NDC "139" and the encoding result of SN "66666666" to form the encoding result of the mobile phone number "13966666666", which is "00010100111111100101000000101010", a total of 34 bits of binary data, also known as binary data D1.

[0165] Alternatively, in another possible implementation, the terminal 100 compressing NDC1 into data D4 may include: the terminal 100 subtracting a preset offset value from NDC1 to obtain data D5, wherein the data length of data D5 is less than the data length of NDC1.

[0166] Since the current NDC number segments are distributed between 13x and 19x, and the 7-bit SMCID value ranges from 0 to 127, the SMCID can be obtained by subtracting a preset offset value from the NDC.

[0167] For example, the preset offset value can be 100. Taking the mobile phone number "13966666666" as an example, the NDC is "139" and the SN is "66666666". The NDC "139" minus the preset offset value "100" equals "39", which is data D5. "39" can be encoded as binary data "100111". Since "100111" is less than 7 bits, the high-order bits are padded with 0s, resulting in 7-bit encoded data "0100111". Therefore, the encoding result of NDC "139" is "0100111", which is data D2. "66666666" can be encoded into the binary data "111111100101000000101010", a 26-bit binary number. Since it's less than 27 bits, the high-order bits are padded with 0s, resulting in the 27-bit binary data "0111111100101000000101010". Therefore, the encoding result of the SN "66666666" is "0111111100101000000101010", which is also the data D3. Terminal 100 can combine the encoding result of NDC "139" and the encoding result of SN "66666666" to form the encoding result of the mobile phone number "13966666666", which is "01001110111111100101000000101010", a total of 34 bits of binary data, also known as binary data D1.

[0168] It is understood that the preset offset value can be 100 or other values, and this application embodiment does not limit it.

[0169] S102, Terminal 100 fills data D1 into the user ID field contained in the frame header information of the first user frame.

[0170] Terminal 100 can fill data D1 into the user ID field contained in the frame header information of the first user frame at the SLC layer. For example, when the user ID is the mobile phone number "13966666666", the binary data D1 filled into the user ID field can be "00010100111111100101000000101010" or "01001110111111100101000000101010", a total of 34 bits of binary data.

[0171] Furthermore, after executing step S102, terminal 100 can send the first user frame to Beidou network device 200.

[0172] Furthermore, the BeiDou network device 200 can decode and decompress the user ID field in the first user frame at the SLC layer to obtain the original user ID. For example, if the user ID is a mobile phone number, the BeiDou network device 200 can decode and decompress the binary user ID field at the SLC layer to obtain an 11-digit mobile phone number.

[0173] Specifically, the BeiDou network device 200 can decode the binary user ID in the user ID field, i.e., data D2 in data D1, into data D4, and decode data D3 in data D1 into SN1. Then, it decompresses data D4 into NDC1.

[0174] In one possible implementation, the user ID field of the first user frame may include a user ID compression indication field, which indicates the compression method for the user ID. The BeiDou network device 200 can decompress data D4 into NDC1 according to the compression method indicated by the user ID compression indication field.

[0175] Alternatively, in another possible implementation, if terminal 100 compresses NDC1 into data D4 in only one way—for example, terminal 100 maps NDC1 to mapping table relationship data D4, where data D4 is the SMCID corresponding to NDC1 in the mapping table relationship—then BeiDou network device 200 decompresses data D4 according to the method terminal 100 used to compress NDC1 to obtain NDC1. For instance, BeiDou network device 200 can look up the NDC1 corresponding to data D4 in the mapping table.

[0176] Optionally, in another possible implementation, if the terminal 100 has multiple methods to compress NDC1 into data D4, the BeiDou network device 200 can decompress the data D4 according to a preset decompression method order. For example, if the terminal 100 has three methods to compress NDC1 into data D4, such as compression method 1, compression method 2, and compression method 3, and the first user frame sent by the terminal 100 does not indicate the compression method for the user ID field, the BeiDou network device 200 presets the user ID decompression method, decompression method 1 (which can decompress data compressed by compression method 1), decompression method 2 (which can decompress data compressed by compression method 2), and decompression method 3 (which can decompress data compressed by compression method 3). The preset decompression method order is: first, decompress using decompression method 1; if decompression fails, then decompress using decompression method 2; if decompression still fails, then decompress using decompression method 3.

[0177] It is understood that in this embodiment of the application, the user ID of terminal 100 is not limited to the mobile phone number of terminal 100, but can also be the MSISDN, International Mobile Subscriber Identification Number (IMSI), or International Mobile Equipment Identification Number (IMEI) of terminal 100, etc.

[0178] According to the data compression method in a satellite communication system provided in this application embodiment, terminal 100 can compress user IDs. When the user ID is an 11-digit mobile phone number, the prior art uses BCD encoding, which requires the user ID field to occupy 44 bits. However, the data compression method in this application embodiment only requires the user ID field to occupy 34 bits. This reduces the number of bits occupied by the user ID field in the frame header information of each user frame.

[0179] Terminal 100 can send a first user frame to BeiDou network device 200. This first user frame can be used to query cellular network information near terminal 100, or the number of emails received by terminal 100, or the content of emails received by terminal 100. Alternatively, the first user frame can also indicate whether terminal 100 successfully received a user frame sent by BeiDou network device last time, or whether terminal 100 successfully parsed an application layer message sent by BeiDou network device 200. When BeiDou network device 200 receives the first user frame from terminal 100, BeiDou network device 200 can reply with a second user frame to terminal 100. The second user frame can be used to indicate the query result of cellular network information near terminal 100, or the number of emails received by terminal 100, or the content of emails received by terminal 100. Alternatively, the second user frame can also indicate whether BeiDou network device 200 successfully received the first user frame sent by terminal 100, or whether BeiDou network device 200 successfully parsed an application layer message sent by terminal 100. The user ID of terminal 100 is included in the frame header information of the second user frame sent from BeiDou network device 200 to terminal 100. This allows terminal 100 to also know that the second user frame was sent from BeiDou network device 200.

[0180] In existing technologies, the user ID field requires a significant number of bits, resulting in high overhead in the frame header.

[0181] This application provides a compression method that can be applied to a BeiDou network device 200. The compression method may include: the BeiDou network device 200 obtaining the user ID of the terminal 100, then the BeiDou network device 200 compressing the user ID of the terminal 100 and encoding it into binary data D6, and the BeiDou network device 200 filling the data D6 into the user ID field contained in the frame header information of the second user frame.

[0182] The user ID can be the mobile phone number of terminal 100.

[0183] The compression method provided in this application embodiment allows the BeiDou network device 200 to compress the user ID of the terminal 100, encode the compressed user ID, and fill it into the user ID field. This reduces the number of bits occupied by the user ID field, thereby reducing frame header overhead.

[0184] Figure 11B An exemplary flowchart of a data compression method in a communication system provided in this application is shown. Taking a mobile phone number as an example, the data compression method may include the following steps: S201, Beidou network equipment 200 obtains the user ID of terminal 100.

[0185] The Beidou network device 200 can obtain the user ID of the terminal 100 from the user ID field of the first user frame received from the terminal 100.

[0186] In one possible implementation, the BeiDou network device 200 parses the binary data in the user ID field of the first user frame sent by the terminal 100 into a user ID (e.g., the mobile phone number of the terminal 100, "13966666666").

[0187] Alternatively, in another possible implementation, the BeiDou network device 200 can obtain the binary data from the user ID field in the first user frame of the terminal 100. The BeiDou network device 200 can then directly fill the binary data from the user ID field into the user ID field of the second user frame. The BeiDou network device 200 does not need to execute steps S202-S203.

[0188] S202, Beidou network equipment 200 compresses the user ID of terminal 100 into data D6, and encodes data D6 into binary data D7, wherein the data length of data D6 is less than the data length of user ID.

[0189] The user ID of terminal 100 can be the mobile phone number of terminal 100, where the mobile phone number includes NDC1 and SN1. Beidou network device 200 can compress NDC1 from the mobile phone number to obtain SMCID1, where the data length of SMCID1 is shorter than the data length of NDC1. Data D6 is SMCID1 and SN1. Then, Beidou network device 200 can encode SMCID1 and SN1 to obtain binary data D7.

[0190] The Beidou network device 200 compresses NDC1 to obtain SMCID1. For details, please refer to the implementation process of terminal 100 compressing NDC1 into data D4 in step S101 above. It will not be repeated here.

[0191] For example, the user ID of terminal 100 can be the mobile phone number of terminal 100, such as "13966666666", where NDC1 can be "139" and SN1 can be "66666666". If Beidou network device 200 maps NDC1 to SMCID1 according to the method in step S102 above, Beidou network device 200 can compress NDC1 "139" to "10". If Beidou network device 200 compresses SMCID1 by subtracting a preset offset value from NDC1 according to the compression method in step S102 above, taking a preset offset value of 100 as an example, Beidou network device can compress NDC1 "139" to "39".

[0192] When "139" is compressed to "10", "13966666666" can be encoded into binary data D7, which is "00010100111111100101000000101010". When "139" is compressed to "39", "13966666666" can be encoded into binary data D7, which is "01001110111111100101000000101010".

[0193] S203, Beidou network equipment 200 fills data D7 into the user ID field contained in the frame header information of the second user frame.

[0194] The Beidou network device 200 can fill data D7 into the user ID field contained in the frame header information of the second user frame. For example, when the user ID is the mobile phone number "13966666666", the binary data D1 filled into the user ID field can be "00010100111111100101000000101010" or "01001110111111100101000000101010", a total of 34 bits of binary data.

[0195] Furthermore, after executing step S203, the BeiDou network device 200 can send the second user frame to the terminal 100.

[0196] It is understood that in this embodiment of the application, the user ID of terminal 100 is not limited to the mobile phone number of terminal 100, but can also be the MSISDN of terminal 100, or the international mobile equipment identity (IMEI), etc.

[0197] According to the data compression method provided in this application embodiment of a satellite communication system, the BeiDou network device 200 can compress the user ID of the terminal 100. When the user ID is an 11-digit mobile phone number, the prior art uses BCD encoding, which requires the user ID field to occupy 44 bits. However, the data compression method of this application embodiment only requires the user ID field to occupy 34 bits. This reduces the number of bits occupied by the user ID field in the frame header information of each user frame.

[0198] In some scenarios, terminal 100 can operate under the BeiDou network, meaning it is not registered on a cellular network. When the BeiDou communication module in terminal 100 is enabled, terminal 100 can send and receive SMS messages from terminal 300 via BeiDou network device 200. Terminal 300 may be registered on a cellular network or it may be operating under the BeiDou network but not on a cellular network; this is not a limitation.

[0199] Understandably, referring to the above Figure 1 When terminal 100 sends a message to terminal 300, the BeiDou short message fusion communication platform 24 in the BeiDou network device 200 can determine whether the receiving terminal 300 is under the BeiDou network or under the cellular network. If terminal 300 is under the cellular network, the BeiDou short message fusion communication platform 24 can send the message to the short message center 25, and then the short message center will send it to terminal 300.

[0200] When terminal 100 under the BeiDou network sends a message to terminal 400 under the BeiDou network equipment, firstly, the message sent by terminal 100 is forwarded to BeiDou ground transceiver station 22 via BeiDou short message satellite 21. Then, BeiDou ground transceiver station 22 sends the message to BeiDou central station 23, and then BeiDou central station 23 sends the message to BeiDou short message fusion communication platform 24. BeiDou short message fusion communication platform 24 can parse the user ID of terminal 400 and determine that terminal 400 is under the BeiDou network based on the user ID. Then, BeiDou short message fusion communication platform 24 sends the message to BeiDou central station 23. Then, BeiDou central station 23 sends the message to BeiDou ground transceiver station 22. Finally, BeiDou ground transceiver station 22 sends the message to terminal 400 via BeiDou short message satellite 21.

[0201] Scenario 1: Terminal 100 under the BeiDou network sends a message to terminal 300 under the cellular network. When terminal 100 sends a short message to terminal 300 via BeiDou network device 200, the short message may carry the user IDs of both terminal 100 and terminal 300. Specifically, terminal 100 generates a first message packet at the application layer, which may include the specific message content and the user ID of terminal 300. Terminal 100 can compress and encode the user ID of terminal 300 into binary data at the application layer, and then fill the binary data into the header of the first message packet. Specifically, terminal 100 can compress and encode the user ID of terminal 300 into binary data at the application layer according to the method shown in steps S101-S102 above, which will not be repeated here. After the first message packet is sent to the SLC layer, terminal 100 adds the user ID of terminal 100 and generates a first user frame. Terminal 100 compresses and encodes the user ID of terminal 100 into binary data at the SLC layer and fills it into the frame header information of the first user frame. Specifically, terminal 100 can compress and encode its user ID into binary data at the APP layer according to the method shown in steps S101-S102 above, and then fill it into the frame header information of the first user frame. Further details are omitted here. Then, terminal 100 sends the first user frame to BeiDou network device 200.

[0202] After receiving the first user frame, BeiDou network device 200 can decode and decompress the user ID field of terminal 100 in the first user frame at the SLC layer, i.e., at the BeiDou central station 23 within BeiDou network device 200, to obtain the user ID of terminal 100. Then, at the APP layer, i.e., at the BeiDou short message fusion communication platform 24 within BeiDou network device 200, BeiDou network device 200 can decode and decompress the user ID field of terminal 300 to obtain the user ID of terminal 300. Finally, BeiDou network device 200 can send the message message carried in the first message message to terminal 300 at the APP layer.

[0203] Scenario 2: Terminal 100 under the BeiDou network receives messages sent by terminal 300 under the cellular network. In some scenarios, BeiDou network device 200 will only forward messages sent to terminal 100 by other devices to terminal 100 if terminal 100 automatically sends a request to it. This saves transmission resources in the satellite communication system and reduces the cost of sending and receiving messages on the BeiDou network. After receiving a message request from terminal 100, BeiDou network device 200 can decompress and decode the user ID of terminal 100 from the message request at the SLC layer and then save the user ID. BeiDou network device 200 can also retrieve messages sent from terminal 300 to terminal 100. BeiDou network device 200 can parse the user ID of terminal 300 contained in the message at the application layer. Then, BeiDou network device 200 can encapsulate the message sent by terminal 300 into a second message message at the APP layer. This second message message may include the specific message content and the user ID field of terminal 300. The BeiDou network device 200 compresses the user ID of the terminal 300, encodes it into binary data, and fills it into the user ID field of the header of the second message message. Specifically, the BeiDou network device 200 can compress the user ID of the terminal 300 into binary data at the APP layer according to the method shown in steps S201-S203 above, and fill it into the frame header information of the second message message. The BeiDou network device 200 can segment the second message message into one or more user frames when sending it to the SLC layer, with multiple user frames including the second user frame. The BeiDou network device 200 compresses the stored user ID of the terminal 100, encodes it into binary data, and fills it into the user ID field of the frame header information of the second user frame. Specifically, the BeiDou network device 200 can compress the user ID of the terminal 100 into binary data at the SLC layer according to the method shown in steps S201-S203 above, and fill it into the frame header information of the second user frame, which will not be elaborated here. Then, the Beidou network device 200 sends the second user frame to the terminal 100.

[0204] After receiving the second user frame, terminal 100 can decode the user ID field of terminal 100 in the second user frame at the SLC layer to obtain the user ID of terminal 100. Terminal 100 can also decode and decompress the user ID field of terminal 300 at the APP layer to obtain the user ID of terminal 300.

[0205] Alternatively, in other scenarios, terminal 100 may not need to send a request to BeiDou network device 200. When BeiDou network device 200 receives a message sent to terminal 100 by another terminal, BeiDou network device 200 can send the message to terminal 100. In this way, terminal 100 can receive messages sent to it by other devices in a timely manner.

[0206] The BeiDou network device 200 can obtain messages sent from terminal 300 to terminal 100. Then, at the APP layer, the BeiDou network device 200 can parse the user ID and the terminal 300's user ID from the messages sent by terminal 300. The BeiDou network device 200 can encapsulate this message into a second message packet. This second message packet may include the specific message content and the terminal 300's user ID field. The BeiDou network device 200 compresses the terminal 300's user ID, encodes it into binary data, and fills it into the user ID field of the second message packet. Specifically, the BeiDou network device 200 can compress the terminal 300's user ID at the APP layer and encode it into binary data, then fill it into the header of the second message packet, following the method shown in steps S201-S203 above. The BeiDou network device 200 then sends the second message packet to the SLC layer, segmenting it into one or more user frames, each of which includes the second user frame. Then, the BeiDou network device 200 compresses the user ID of the terminal 100, encodes it into binary data, and fills it into the user ID field of the frame header information of the second user frame. Specifically, the BeiDou network device 200 can compress the user ID of the terminal 100 into binary data at the SLC layer and fill it into the frame header information of the second user frame according to the method shown in steps S201-S203 above, which will not be elaborated here. Then, the BeiDou network device 200 sends the second user frame to the terminal 100.

[0207] Scenario 3: Terminal 100 under the BeiDou network sends a message to terminal 400 under the BeiDou network. When terminal 100 sends a short message to terminal 400 via BeiDou network device 200, the short message may carry the user IDs of both terminal 100 and terminal 400. Specifically, terminal 100 generates a third message in the application layer, which may include the specific message content and the user ID of terminal 400. Terminal 100 can compress and encode the user ID of terminal 400 into binary data at the application layer, and then fill this binary data into the header of the first message. Specifically, terminal 100 can compress and encode the user ID of terminal 400 into binary data at the application layer according to the method shown in steps S101-S102 above, which will not be repeated here. After the first message is sent to the SLC layer, terminal 100 adds the user ID of terminal 100 and generates a first user frame. Terminal 100 compresses and encodes the user ID of terminal 100 into binary data at the SLC layer and fills it into the frame header information of the first user frame. Specifically, terminal 100 can compress and encode its user ID into binary data at the APP layer according to the method shown in steps S101-S102 above, and then fill it into the frame header information of the first user frame. Further details are omitted here. Then, terminal 100 sends the first user frame to BeiDou network device 200.

[0208] After receiving the first user frame, BeiDou network device 200 can decode and decompress the user ID field of terminal 100 in the first user frame at the SLC layer, i.e., the BeiDou central station 23 within BeiDou network device 200, to obtain the user ID of terminal 100. Then, at the APP layer, i.e., the BeiDou short message fusion communication platform 24 within BeiDou network device 200 can decode and decompress the user ID field of terminal 400 to obtain the user ID of terminal 400. BeiDou short message fusion communication platform 24 determines that terminal 400 is under the BeiDou network, and then compresses and encodes the user ID of terminal 400 to obtain the compressed and encoded user ID. Then, BeiDou short message fusion communication platform 24 encapsulates the compressed and encoded user ID and the specific content of the message into a fourth message. Then, BeiDou short message fusion communication platform 24 sends the fourth message to BeiDou central station 23. BeiDou central station 23 can segment this fourth message into one or more user frames, each of which includes the fourth user frame. The BeiDou central station 23 compresses and encodes the user ID of terminal 100 and fills it into the user ID field of the fourth user frame. Then, the BeiDou central station 23 sends the fourth user frame to the BeiDou ground transceiver station 22. The BeiDou ground transceiver station 22 sends the fourth user frame to terminal 100 via the BeiDou short message satellite 21. Specifically, the BeiDou network device 200 can compress the user ID of terminal 400 at the APP layer and encode it into binary data, then fill it into the user ID field in the header of the fourth message, following the method shown in steps S201-S203 above. Specifically, the BeiDou network device 200 can compress the user ID of terminal 100 at the SLC layer and encode it into binary data, then fill it into the user ID field in the frame header information of the fourth user frame, following the method shown in steps S201-S203 above.

[0209] After receiving the second user frame, terminal 100 can decode the user ID field of terminal 100 in the fourth user frame at the SLC layer to obtain the user ID of terminal 100. Terminal 100 can also decode and decompress the user ID field of terminal 400 at the APP layer to obtain the user ID of terminal 400.

[0210] Scenario 4: Terminal 100 under the BeiDou network receives messages sent by terminal 400 under the BeiDou network. The process by which terminal 400 sends a message to terminal 100 can be referred to the descriptions in scenarios 1-3 above, and will not be repeated here.

[0211] It is understandable that BeiDou network device 200 can send the message sent by terminal 400 to terminal 100 after receiving a request from terminal 100 to receive a message. Alternatively, BeiDou network device 200 can also send the message sent by terminal 400 directly to terminal 100 after receiving it, without requiring a request from terminal 100. When BeiDou network device 200 sends the message sent by terminal 400 to terminal 100, BeiDou network device 200 can obtain the user ID of terminal 100 from the message sent by terminal 400. BeiDou network device 200 can also obtain the user ID of terminal 100 from the request sent by terminal 100.

[0212] In the embodiments of this application, terminal 300 or terminal 400 may be referred to as a second terminal, and the user ID of terminal 300 or the user ID of terminal 400 may be referred to as a second user ID.

[0213] The exemplary terminal 100 provided in the embodiments of this application will be introduced first below.

[0214] Figure 12 This is a schematic diagram of the structure of the terminal 100 provided in the embodiments of this application.

[0215] The following description uses terminal 100 as an example to illustrate the embodiment. It should be understood that terminal 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have different component configurations. The various components shown in the figures can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0216] Terminal 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0217] It is understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal 100. In other embodiments of this application, the terminal 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0218] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0219] The controller can serve as the central nervous system and command center of the terminal 100. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0220] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0221] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0222] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the terminal 100.

[0223] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0224] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0225] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.

[0226] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the terminal 100 to perform its shooting function. The processor 110 and the display screen 194 communicate via the DSI interface to enable the terminal 100 to perform its display function.

[0227] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0228] The SIM interface can be used to communicate with the SIM card interface 195 to transmit data to or read data from the SIM card.

[0229] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge terminal 100, and can also be used for data transfer between terminal 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0230] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the terminal 100. In other embodiments of this application, the terminal 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0231] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.

[0232] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

[0233] The wireless communication function of terminal 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0234] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0235] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on the terminal 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low-noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0236] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0237] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), BeiDou communication module, frequency modulation (FM), near field communication (NFC), and infrared (IR) technology. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0238] The BeiDou communication module can be used to communicate with the BeiDou network device 200. The BeiDou communication module supports short message transmission with the BeiDou network device 200.

[0239] In some embodiments, antenna 1 of terminal 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling terminal 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0240] Terminal 100 implements display functions through a GPU, display screen 194, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0241] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, terminal 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0242] Terminal 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0243] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0244] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, terminal 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0245] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when terminal 100 selects a frequency point, the DSP can perform Fourier transforms on the frequency energy.

[0246] Video codecs are used to compress or decompress digital video. Terminal 100 may support one or more video codecs. Thus, terminal 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0247] NPU stands for Neural Network (NN) Computing Processor. By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs can enable intelligent cognitive applications in terminals, such as image recognition, facial recognition, speech recognition, and text understanding.

[0248] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM).

[0249] Random access memory can include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, fifth-generation DDR SDRAM is generally called DDR5 SDRAM), etc. Non-volatile memory can include disk storage devices and flash memory.

[0250] Flash memory can be classified according to its operating principle, including NOR FLASH, NAND FLASH, 3D NAND FLASH, etc.; according to the level of the storage cell, including single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc.; and according to the storage specification, including universal flash storage (UFS) and embedded multimedia card (eMMC), etc.

[0251] The random access memory can be directly read and written by the processor 110. It can be used to store executable programs (such as machine instructions) of the operating system or other running programs, as well as user and application data.

[0252] Non-volatile memory can also store executable programs and user and application data, and can be pre-loaded into random access memory for direct reading and writing by the processor 110.

[0253] Terminal 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0254] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0255] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The terminal 100 can listen to music or make hands-free calls through the speaker 170A.

[0256] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the terminal 100 receives a phone call or voice message, the receiver 170B can be brought close to the listener's ear to hear the voice.

[0257] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Terminal 100 may have at least one microphone 170C. In some embodiments, terminal 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, terminal 100 may have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0258] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0259] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Terminal 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, terminal 100 detects the intensity of the touch operation based on pressure sensor 180A. Terminal 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0260] The gyroscope sensor 180B can be used to determine the motion attitude of the terminal 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the terminal 100 around three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the terminal 100's shake, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the terminal 100 through reverse movement, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0261] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0262] The magnetic sensor 180D includes a Hall sensor. The terminal 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the terminal 100 is a flip phone, the terminal 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0263] The 180E accelerometer can detect the magnitude of acceleration of terminal 100 in various directions (typically three axes). When terminal 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices, and is applied to applications such as screen orientation switching and pedometers.

[0264] A distance sensor 180F is used to measure distance. The terminal 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, the terminal 100 can utilize the distance sensor 180F to measure distance for rapid focusing.

[0265] The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The terminal 100 emits infrared light outward through the LED. The terminal 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal 100. When insufficient reflected light is detected, the terminal 100 can determine that there is no object near the terminal 100. The terminal 100 may use the proximity sensor 180G to detect when a user holds the terminal 100 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180G can also be used in holster mode and pocket mode for automatic unlocking and screen locking.

[0266] The ambient light sensor 180L is used to sense the ambient light intensity. The terminal 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light intensity. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the terminal 100 is in a pocket to prevent accidental touches.

[0267] The fingerprint sensor 180H is used to collect fingerprints. The terminal 100 can use the characteristics of the collected fingerprints to unlock the device, access application locks, take photos with fingerprints, and answer calls with fingerprints.

[0268] Temperature sensor 180J is used to detect temperature. In some embodiments, terminal 100 uses the temperature detected by temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, terminal 100 reduces the performance of the processor located near temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is below another threshold, terminal 100 heats battery 142 to prevent abnormal shutdown of terminal 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, terminal 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

[0269] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of terminal 100, in a different position than display screen 194.

[0270] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Terminal 100 can receive button input and generate key signal inputs related to user settings and function control of terminal 100.

[0271] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0272] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0273] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the terminal 100. The terminal 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, and other SIM cards. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal 100 interacts with the network through the SIM card to realize functions such as calls and data communication.

[0274] The foregoing details the method provided in this application. In order to facilitate better implementation of the above-described solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

[0275] This application embodiment can divide the terminal 100 and Beidou network device 200 into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0276] The following will combine Figures 13 to 16 The communication device of the present application embodiment is described in detail.

[0277] In the case of using integrated units, see Figure 13 , Figure 13This is a schematic diagram of the structure of the communication device 1300 provided in an embodiment of this application. The communication device 1300 can be the terminal 100 in the above embodiments. Optionally, the communication device 1300 can be a chip / chip system, such as a Beidou communication chip. Figure 13 As shown, the communication device 1300 may include a transceiver unit 1310 and a processing unit 1320.

[0278] In one design, the transceiver unit 1310 can be used to send the first user frame to the BeiDou network device 200.

[0279] The processing unit 1320 can compress the user ID of the terminal 100, encode the compressed user ID into binary data, and then fill the binary data into the user ID field contained in the frame header information of the first user frame.

[0280] Optionally, the transceiver unit 1310 can also be used to perform the above-mentioned tasks. Figure 11A The method embodiment shown illustrates the functional steps related to sending and receiving performed by terminal 100.

[0281] Optionally, the processing unit 1320 can also be used to perform the above-mentioned tasks. Figure 11A The method embodiment shown illustrates the functional steps performed by terminal 100 related to protocol parsing, encapsulation, and computation determination.

[0282] It should be understood that the communication device 1300 in this design can perform the method steps executed by the terminal 100 in the aforementioned embodiment, and for the sake of brevity, it will not be described again here.

[0283] In the case of using integrated units, see Figure 14 , Figure 14 This is a schematic diagram of the structure of the communication device 1400 provided in this embodiment. The communication device 1400 can be the BeiDou network device 200 in the above embodiments. Optionally, the communication device 1400 can be a specific network element in the BeiDou network device 200, such as one or a combination of multiple network elements from the BeiDou ground transceiver station 22, the BeiDou central station 23, and the BeiDou short message fusion communication platform 24. Figure 14 As shown, the communication device 1400 may include a transceiver unit 1410 and a processing unit 1420.

[0284] In one design, the transceiver unit 1410 can be used to receive user frames sent by the terminal 100.

[0285] The processing unit 1420 can be used to obtain the user ID of the terminal 100 from the user frame sent by the terminal 100, compress the user ID of the terminal 100, encode the compressed user ID into binary data, and finally fill the binary data into the user ID field contained in the frame header information of the user frame sent by the Beidou network device 200 to the terminal 100.

[0286] Optionally, the transceiver unit 1410 can also be used to perform the above-mentioned tasks. Figure 11B The method embodiment shown illustrates the functional steps related to sending and receiving performed by the BeiDou network device 200.

[0287] Optionally, the processing unit 1420 can also be used to perform the above-mentioned tasks. Figure 11B The method embodiment shown illustrates the functional steps of protocol parsing, encapsulation, and computation determination performed by the BeiDou network device 200.

[0288] It should be understood that the communication device 1400 in this design can perform the method steps executed by the Beidou network device 200 in the aforementioned embodiment, and for the sake of brevity, it will not be described again here.

[0289] The terminal 100 and Beidou network device 200 of this application embodiment have been described above. It should be understood that any device possessing the above-described... Figure 12 Any product of the aforementioned terminal 100 functions, as long as it possesses the above-mentioned features. Figure 13 Any form of product that incorporates the functions of the Beidou network device 200 falls within the protection scope of the embodiments of this application.

[0290] As a possible product form, the terminal 100 described in this application embodiment can be implemented using a general bus architecture.

[0291] See Figure 15 , Figure 15 This is a schematic diagram of the structure of the communication device 1500 provided in an embodiment of this application. The communication device 1500 may be a terminal 100, or a device therein. Figure 15As shown, the communication device 1500 includes a processor 1501 and a transceiver 1502 internally connected and communicating with the processor. The processor 1501 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU) for satellite communication. The baseband processor can process satellite communication protocols and data, while the CPU can control the communication device (e.g., baseband chip, terminal, terminal chip), execute computer programs, and process data from these programs. The transceiver 1502, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1502 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function. Optionally, the communication device 1500 may also include an antenna 1503 and / or a radio frequency unit (not shown in the figure). The antenna 1503 and / or radio frequency unit may be located inside the communication device 1500 or separate from the communication device 1400, that is, the antenna 1503 and / or radio frequency unit may be deployed remotely or in a distributed manner.

[0292] Optionally, the communication device 1500 may include one or more memories 1504, which may store instructions, which may be computer programs, that can be executed on the communication device 1500 to cause the communication device 1500 to perform the methods described in the above method embodiments. Optionally, the memory 1504 may also store data. The communication device 1500 and the memory 1504 may be provided separately or integrated together.

[0293] The processor 1501, transceiver 1502, and memory 1504 can be connected via a communication bus.

[0294] In one design, the communication device 1500 can be used to perform the functions of the terminal 100 in the aforementioned embodiments; the processor 1501 can be used to perform the above-mentioned functions. Figure 11A In the illustrated embodiment, the terminal 100 performs functional steps related to protocol parsing and encapsulation, as well as computational determination, and / or other processes used in the technology described herein; the transceiver 1502 can be used to perform the above-mentioned... Figure 11A The terminal 100 in the illustrated embodiment performs functional steps related to protocol parsing and encapsulation, as well as calculation and / or other processes used in the technology described herein.

[0295] In any of the above designs, the processor 1501 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0296] In any of the above designs, the processor 1501 may store instructions, which may be computer programs. These computer programs, running on the processor 1501, cause the communication device 1500 to execute the method steps executed by the terminal 100 in the above method embodiments. The computer program may be embedded in the processor 1501; in this case, the processor 1501 may be implemented in hardware.

[0297] In one implementation, the communication device 1500 may include circuitry capable of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0298] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 15 The communication device 1500 may be a standalone device or part of a larger device. For example, the communication device 1500 may be: (1) Independent integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs; (3) ASIC, such as modem; (4) Modules that can be embedded in other devices; (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.; (6) Others, etc.

[0299] As a possible product form, any network element in the BeiDou network device 200 described in this application embodiment (e.g., BeiDou ground transceiver station 22, BeiDou central station 23, BeiDou short message fusion communication platform 24) can be implemented by a general bus architecture.

[0300] See Figure 16 , Figure 16 This is a schematic diagram of the structure of the communication device 1600 provided in an embodiment of this application. The communication device 1600 may be a BeiDou network device 200, or a device therein. Figure 16 As shown, the communication device 1600 includes a processor 1601 and a transceiver 1602 internally connected and communicating with the processor. The processor 1601 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU) for satellite communication. The baseband processor can process satellite communication protocols and data, while the CPU can control the communication device (e.g., a baseband chip), execute computer programs, and process data from those programs. The transceiver 1602, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1602 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function. Optionally, the communication device 1600 may also include an antenna 1603 and / or a radio frequency unit (not shown in the figure). The antenna 1603 and / or radio frequency unit may be located inside the communication device 1600 or separate from the communication device 1600, that is, the antenna 1603 and / or radio frequency unit may be deployed remotely or in a distributed manner.

[0301] Optionally, the communication device 1600 may include one or more memories 1604, which may store instructions, which may be computer programs, that can be executed on the communication device 1600 to cause the communication device 1600 to perform the methods described in the above method embodiments. Optionally, the memory 1604 may also store data. The communication device 1600 and the memory 1604 may be provided separately or integrated together.

[0302] The processor 1601, transceiver 1602, and memory 1604 can be connected via a communication bus.

[0303] In one design, the communication device 1600 can be used to perform the functions of the BeiDou network device 200 in the aforementioned embodiments: the processor 1601 can be used to perform the above-mentioned functions. Figure 11B The BeiDou network device 200 in the illustrated embodiment performs the relevant protocol parsing, encapsulation, and computational determination functional steps and / or other processes used in the technology described herein; the transceiver 1602 can be used to perform the above. Figure 11B The embodiments shown include the protocol parsing and encapsulation and computational determination functional steps performed by the BeiDou network device 200 and / or other processes used in the technology described herein.

[0304] In any of the above designs, the processor 1601 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0305] In any of the above designs, the processor 1601 may store instructions, which may be computer programs. These computer programs, running on the processor 1601, cause the communication device 1600 to execute the method steps executed by the terminal 100 in the above method embodiments. The computer program may be embedded in the processor 1601; in this case, the processor 1601 may be implemented in hardware.

[0306] This application also provides a computer-readable storage medium storing computer program code, which, when executed by the processor, causes the communication device to perform the method in any of the foregoing embodiments.

[0307] This application also provides a computer program product that, when run on a computer, causes the computer to perform the methods in any of the foregoing embodiments.

[0308] This application also provides a communication device, which can exist in the form of a chip. The device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device can execute the method in any of the foregoing embodiments.

[0309] This application also provides a satellite communication system, including a terminal 100 and a BeiDou network device 200, which can perform the methods in any of the foregoing embodiments.

[0310] This application fully describes the short message communication function in the BeiDou communication system. It is understood that other satellite systems may also support short message communication functions. Therefore, it is not limited to the BeiDou communication system. If other satellite systems also support short message communication functions, the method described in this application is also applicable to the communication of other satellite systems.

[0311] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0312] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining...", "in response to determining...", "when (the stated condition or event) is detected", or "in response to detecting (the stated condition or event)".

[0313] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0314] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A data compression method in a satellite communication system, characterized in that, include: The first terminal encodes the first user ID of the first terminal into binary first data. The first user ID includes second data and third data. The first data includes binary fourth data and binary fifth data. The fourth data is encoded from sixth data. The sixth data is compressed from the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. The first terminal sends a first user frame to the satellite network device, and the first user frame carries the first data.

2. The method according to claim 1, characterized in that, The first terminal encodes its first user ID into binary first data, including: The first terminal compresses the second data in the first user ID of the first terminal into the sixth data at the satellite link control (SLC) layer. The first user ID is composed of the second data and the third data, and the data length of the sixth data is less than that of the second data. The first terminal encodes the sixth data into the fourth data and the third data into the fifth data at the SLC layer. The first terminal combines the fourth data and the fifth data to form the first data.

3. The method according to claim 2, characterized in that, The first terminal compresses the second data in the first user ID of the first terminal into the sixth data at the Satellite Link Control (SLC) layer, including: The first terminal maps the second data in the first user ID to the sixth data in the mapping table at the SCL layer; the mapping table includes multiple values ​​of second data and multiple values ​​of sixth data, wherein the multiple values ​​of second data include the second data of a first value, the multiple values ​​of sixth data include the sixth data of a second value, and the second data of the first data is mapped to the sixth data of the second value.

4. The method according to claim 2, characterized in that, The first terminal compresses the second data in the first user ID of the first terminal into the sixth data at the Satellite Link Control (SLC) layer, including: The first terminal subtracts a preset offset value from the second data in the first user ID at the SCL layer to obtain the sixth data.

5. The method according to any one of claims 2-4, characterized in that, The first terminal encodes the sixth data into the fourth data and the third data into the fifth data at the Satellite Link Control (SLC) layer, including: The first terminal converts the sixth data as a decimal integer into the fourth data in binary at the SLC layer; and converts the third data as a decimal integer into the fifth data in binary.

6. The method according to any one of claims 1-5, characterized in that, The first user ID is a mobile phone number, the second data is the domestic destination code (NDC) in the mobile phone number, and the third data is the customer number (SN) in the mobile phone number.

7. The method according to any one of claims 1-6, characterized in that, Before the first terminal encodes the first user ID of the first terminal into binary first data, the method further includes: The first terminal detects a first operation, which instructs the first terminal to send a first message to the second terminal. The first terminal compresses and encodes the second user ID of the second terminal into the seventh data at the application (APP) layer; The first terminal generates a first message message at the APP layer. The first message message includes a message header and message data. The message header includes the seventh data, and the message data includes the content of the first message.

8. The method according to claim 7, characterized in that, After the first terminal generates the first message message at the APP layer, the method further includes: The first terminal sends the first message to the SLC layer to obtain one or more Satellite Link Control Layer Service Data Units (SLC SDUs), wherein the one or more SLC SDUs include a first SLC SDU. The first terminal segments the first SLC SDU into one or more user frames, and the one or more user frames include the first user frame.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: The first terminal receives a second user frame sent by the satellite network device, and the second user frame is sent from the second terminal to the first terminal. The first terminal decodes and decompresses the user ID field in the frame header information of the second user frame at the SLC layer to obtain user ID data; If the first terminal determines that the user ID data is the same as the first user ID, the first terminal will upload the second user frame to the message data aggregation MDCP layer. If the first terminal determines that the user ID data is different from the first user ID, the first terminal discards the second user frame.

10. The method according to claim 9, characterized in that, After the first terminal decodes and decompresses the user ID field in the frame header information of the second user frame at the SLC layer to obtain the first user ID of the first terminal, the method further includes: The first terminal uploads the user data in the second user frame to the APP layer to obtain the second message message; The first terminal decodes and decompresses the user ID field in the header of the second message in the APP layer to obtain the second user ID of the second terminal; The first terminal determines that the second message message was sent by the second terminal based on the second user ID.

11. A data compression method in a satellite communication system, characterized in that, include: The satellite network equipment encodes the first user ID of the first terminal into binary first data. The first user ID includes second data and third data. The first data includes binary fourth data and binary fifth data. The fourth data is encoded from sixth data. The sixth data is compressed from the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. The satellite network device sends a second user frame to the first terminal, the second user frame carrying the first data.

12. The method according to claim 11, characterized in that, Before the satellite link control layer (SLC) encodes the first user ID of the first terminal into binary first data, the method further includes: The satellite network device obtains the first user ID of the first terminal.

13. The method according to claim 12, characterized in that, The satellite network device obtains the first user ID of the first terminal, including: The satellite network device receives a first user frame sent by the first terminal, and the user ID field in the frame header information of the first user frame is used to indicate the first user ID of the first terminal. The satellite network device decodes the first user ID from the first user frame.

14. The method according to claim 12, characterized in that, The satellite network device obtains the first user ID of the first terminal, including: The satellite network device receives a first user frame sent by the first terminal, and the user ID field in the frame header information of the first user frame is used to indicate the first data; The satellite network device decompresses and decodes the first data to obtain the first user ID.

15. The method according to claim 12, characterized in that, The satellite network device obtains the first user ID of the first terminal, including: The satellite network device receives a second message, which is sent from the second terminal to the first terminal via the satellite network device. The second message includes a user ID field that indicates the first user ID of the first terminal. The satellite network device decodes the first user ID from the user ID field in the header of the second message.

16. The method according to any one of claims 12-15, characterized in that, The satellite network equipment encodes the first user ID of the first terminal into binary first data, including: The satellite network device compresses the second data in the first user ID of the first terminal into a sixth data at the satellite link control (SLC) layer. The first user ID is composed of the second data and the third data, and the data length of the sixth data is less than that of the second data. The satellite network equipment encodes the sixth data into the fourth data and the third data into the fifth data at the SLC layer. The satellite network device combines the fourth data and the fifth data into the first data.

17. The method according to claim 16, characterized in that, The satellite network device compresses the second data in the first user ID of the first terminal into sixth data at the Satellite Link Control (SLC) layer, including: The satellite network device maps the second data in the first user ID to the sixth data in the mapping table at the SCL layer; the mapping table includes multiple values ​​of second data and multiple values ​​of sixth data, wherein the multiple values ​​of second data include the second data of the first value, the multiple values ​​of sixth data include the sixth data of the second value, and the second data of the first data is mapped to the sixth data of the second value.

18. The method according to claim 16, characterized in that, The satellite network device compresses the second data in the first user ID of the first terminal into sixth data at the Satellite Link Control (SLC) layer, including: The satellite network device subtracts a preset offset value from the second data in the first user ID at the SCL layer to obtain the sixth data.

19. The method according to any one of claims 16-18, characterized in that, The satellite network equipment encodes the sixth data into the fourth data and the third data into the fifth data at the Satellite Link Control (SLC) layer, including: The first terminal converts the sixth data as a decimal integer into the fourth data in binary at the SLC layer; and converts the third data as a decimal integer into the fifth data in binary.

20. The method according to any one of claims 12-19, characterized in that, The first user ID is a mobile phone number, the second data is the domestic destination code (NDC) in the mobile phone number, and the third data is the customer number (SN) in the mobile phone number.

21. A satellite communication system, characterized in that, Includes the first terminal and satellite network equipment, of which: The first terminal is used to encode the first user ID of the first terminal into binary first data. The first user ID includes second data and third data. The first data includes binary fourth data and binary fifth data. The fourth data is encoded by sixth data. The sixth data is compressed by the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded by the third data. The first terminal is used to send a first user frame to the BeiDou network equipment, and the first user frame carries the first data; The satellite network device is used to receive the first user frame and decode the first user ID from the first user frame.

22. The system according to claim 21, characterized in that, The satellite network equipment is used for: At the Satellite Link Control (SLC) layer, the first user ID of the first terminal is encoded into binary first data. The first user ID includes second data and third data. The first data includes binary fourth data and binary fifth data. The fourth data is encoded from the sixth data. The sixth data is compressed from the second data. The data length of the sixth data is less than that of the second data. The fifth data is encoded from the third data. In the SLC layer, the first data is filled into the user ID field in the frame header information of the second user frame.

23. A communication device, characterized in that, The device includes one or more processors, one or more memories, and a transceiver; wherein the transceiver, the one or more memories, and the one or more memories are coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the communication device to perform the method as described in any one of claims 1-10.

24. The communication device according to claim 23, characterized in that, The communication device is a terminal.

25. A communication device, characterized in that, The device includes one or more processors, one or more memories, and a transceiver; wherein the transceiver, the one or more memories, and the one or more processors are coupled together, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the communication device to perform the method as described in any one of claims 11-20.

26. The communication device according to claim 25, characterized in that, The communication device is a satellite network equipment.

27. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-10.

28. A chip or chip system, used in a terminal, characterized in that, It includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as described in any one of claims 1-10.

29. A computer program product, when run on a computer, causes the computer to perform the method as described in any one of claims 1-10.

Images