Method, system and related device for mailbox profile inquiry in satellite communication system

Abstract

This application discloses a method, system, and related apparatus for querying mailbox information in a satellite communication system. The method includes: a terminal sending a mailbox information query request message to a BeiDou network device. The mailbox information query request message includes a service type field and a message ID field. The service type field indicates the service type of the mailbox information query request message, and the message ID field indicates the ID of the last successfully received email by the terminal. The terminal receives a mailbox information query result message sent by the BeiDou network device. The mailbox information query result message includes a whitelist indication field and a message quantity field. The whitelist indication field is used to determine how the terminal parses the message quantity field. The message quantity field indicates the number of messages sent to the terminal by one or more target terminals. In this way, users can also query whether other users have sent them emails under the BeiDou network.

Description

Technical Field

[0001] This application relates to the field of BeiDou communication technology, and in particular to a method, system and related device for querying mailbox information in a satellite communication system. Background Technology

[0002] 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 the communication system is damaged. When a terminal is in an environment where mobile communication is unavailable, lacks coverage, or the communication system is damaged, the terminal cannot promptly obtain information about incoming messages through cellular networks or wireless local area networks (e.g., Wireless Fidelity, Wi-Fi).

[0003] Therefore, how a terminal can know whether it has received a message when there is no cellular network or wireless local area network in its environment is a problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a mailbox information query method, system, and related apparatus in a satellite communication system. Through the mailbox information query method in a satellite communication system provided by the embodiments of this application, the terminal can know the number of letters sent to it by other terminals even when there is no cellular network or wireless local area network in the environment where the terminal is located.

[0005] In a first aspect, this application provides a mailbox overview query method in a satellite communication system. The method may include: a first terminal sending a mailbox overview query request message to a BeiDou network device. The mailbox overview query request message is used to query the number of emails sent to the first terminal by one or more second terminals. The mailbox overview query request message includes a message ID field, which indicates the ID of the first email successfully received by the first terminal. The ID of the first email is used to instruct the BeiDou network device to delete the first email. The first terminal receives a mailbox overview query result message sent by the BeiDou network device. The mailbox overview query result message includes an email quantity field. The email quantity field indicates the number of emails sent to the first terminal by one or more second terminals, and the number of emails sent to the first terminal by one or more second terminals does not include the number of the first email.

[0006] In this way, even when the first terminal is in an environment without a cellular network or wireless LAN, the terminal can still know whether other terminals have sent emails to it, and the number of emails sent by other terminals. Furthermore, the number of emails sent by other terminals does not include emails that have already been downloaded. This prevents the BeiDou network equipment from repeatedly counting already sent emails and resending the same emails to the first terminal.

[0007] In conjunction with the first aspect, in one possible implementation, the mailbox overview query request message further includes a service type field. When the service type field has a first value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal within the whitelist to the first terminal. When the service type field has a second value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal not within the whitelist to the first terminal. When the service type field has a third value, it indicates that the mailbox overview query request message is used to query the total number of emails sent from all second terminals to the first terminal. The first terminal has a whitelist, which stores the identifiers of the second terminals associated with the first terminal and their serial numbers.

[0008] In this way, the first terminal can specify the specific service type of the mailbox overview query request message through this service type field. After receiving the mailbox overview query request message, the Beidou network equipment can also know the service type of the mailbox overview query request message through this service type field.

[0009] In conjunction with the first aspect, in one possible implementation, when the service type field is a first value, the mailbox overview query request message also includes a sender ID field, which is a whitelist bitmap, and the first bit of the whitelist bitmap is used to indicate the identifier of the second terminal with the first sequence number in the whitelist; when the service type field is a second value, the mailbox overview query request message also includes a sender ID field, which is used to indicate the mobile phone number of the second terminal that is not in the whitelist.

[0010] In this way, after receiving the mailbox overview query request message, the Beidou network equipment can determine which terminal sent the number of letters to the first terminal based on the identifier in the sender ID field.

[0011] In conjunction with the first aspect, in one possible implementation, the mailbox overview query request message also includes a receipt indication field. This receipt indication field can be used to indicate whether the receiving device (e.g., a BeiDou network device) of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal. The application layer receipt can be used to indicate whether the receiving device has successfully received the mailbox overview query request message. The length of the receipt indication field can be 1 bit. When the receipt indication field is the value D1 (e.g., 0), it can be used to indicate that the receiving device of the mailbox overview query request message does not need to reply with an application layer receipt to the first terminal. When the receipt indication field is the value D2 (e.g., 1), it can be used to indicate that the receiving device of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal.

[0012] In conjunction with the first aspect, in one possible implementation, the mailbox profile query request message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query request message is encrypted.

[0013] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0014] In conjunction with the first aspect, in one possible implementation, the mailbox profile query request message also includes a compression indication field, which can be used to indicate whether the mailbox profile query request message is compressed.

[0015] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0016] In conjunction with the first aspect, in one possible implementation, the mailbox profile query request message also includes an application layer authentication code field, which can be used for application layer authentication.

[0017] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0018] In conjunction with the first aspect, in one possible implementation, the mailbox overview query result message also includes a whitelist indication field. When the whitelist indication field has a fourth value, it is used to indicate the number of letters sent from a second terminal that is not on the whitelist to the first terminal. When the whitelist indication field has a fifth value, it is used to indicate the number of letters sent from a second terminal on the whitelist to the first terminal, or the number of letters sent from all second terminals to the first terminal.

[0019] In this way, after the first terminal receives the mailbox overview query result message, it knows how to parse the number of letters field in the mailbox overview query result message.

[0020] In conjunction with the first aspect, in one possible implementation, the mailbox overview query result message also includes a message type indicator field. When the message type indicator field has a sixth value, it indicates that the mailbox overview query result message is used to query the number of emails sent by one or more second terminals to the first terminal. When the message type indicator field has a seventh value, it indicates that the mailbox overview query result message is used to download the content of emails sent by one or more second terminals to the first terminal.

[0021] In this way, after receiving the mailbox overview query result message, the first terminal can determine the type of the mailbox overview query result message based on the message type indicator field in the message. Therefore, the first terminal can correctly parse the mailbox overview query result message.

[0022] In conjunction with the first aspect, in one possible implementation, when the service type in the mailbox overview query request message is a second value, the whitelist indication field in the mailbox overview query result message is a fourth value, and the message type indication field in the mailbox overview query result message is a sixth value; when the service type in the mailbox overview query request message is a first value or a third value, the whitelist indication field in the mailbox overview query result message is a fifth value, and the message type indication field in the mailbox overview query result message is a sixth value.

[0023] In conjunction with the first aspect, in one possible implementation, the mailbox profile query result message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query result message is encrypted.

[0024] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0025] In conjunction with the first aspect, in one possible implementation, the mailbox profile query result message also includes a compression indication field, which can be used to indicate whether the mailbox profile query result message is compressed.

[0026] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0027] In conjunction with the first aspect, in one possible implementation, the mailbox overview query result message also includes an application layer authentication code field, which can be used for application layer authentication.

[0028] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0029] In conjunction with the first aspect, in one possible implementation, the first terminal sends a mailbox overview query request message to the BeiDou network equipment, specifically including: the first terminal sending the mailbox overview query request message to the MDCP (Message Data Convergence Protocol) layer of the first terminal at the application (APP) layer, as the MDCP Service Data Unit (SDU) of the MDCP layer; the first terminal adding padding data and redundancy length indication fields to the MDCP SDU, and then splitting it into one or more MDCP Protocol Data Units (PDUs); the one or more MDCP PDUs include the first MDCP PDU; the first terminal sending the first MDCP PDU to the Satellite Link Control (SLC) layer, as the SLC SDU of the SLC layer; the first terminal splitting the SLC SDU into one or more SLC PDUs; and the first terminal sending the one or more SLC PDUs to the BeiDou network equipment.

[0030] In conjunction with the first aspect, in one possible implementation, the first terminal receiving the mailbox overview query result message sent by the BeiDou network device specifically includes: the first terminal receiving P SLC PDUs sent by the BeiDou network device; where P is a positive integer; the first terminal concatenating the P SLC PDUs into Q SLC SDUs at the SLC layer; where Q is a positive integer, Q is less than or equal to P; the first terminal uploading the Q SLC SDUs to the MDCP layer as Q MDCP PDUs of the MDCP layer; the first terminal concatenating the Q MDCP PDUs into an MDCP SDU at the MDCP layer; and the first terminal removing padding data and redundant length indicator fields from the MDCP SDUs at the MDCP layer and uploading them to the APP layer as the mailbox overview query result message.

[0031] In conjunction with the first aspect, in one possible implementation, after the first terminal receives the mailbox overview query result message sent by the Beidou network device, the method further includes: the first terminal parsing out the number of letters sent by one or more second terminals to the first terminal from the letter quantity field in the mailbox overview query result message; and the first terminal displaying the number of letters sent by one or more second terminals to the first terminal on a display screen.

[0032] Secondly, a mailbox overview query method is provided in a satellite communication system. This method may include: a BeiDou network device receiving a mailbox overview query request message sent by a first terminal, the mailbox overview query request message being used to query the number of emails sent to the first terminal by one or more second terminals, the mailbox overview query request message including a message ID field, the message ID field indicating the ID of the first email successfully received by the first terminal, the ID of the first email indicating that the BeiDou network device should delete the first email; based on the mailbox overview query request message, the BeiDou network device generating a mailbox overview query result message, the mailbox overview query result message including a message quantity field; the message quantity field indicating the number of emails sent to the first terminal by one or more second terminals; the number of emails sent to the first terminal by one or more second terminals not including the number of the first email; and the BeiDou network device sending the mailbox overview query result message to the first terminal.

[0033] In this way, even when the first terminal is in an environment without a cellular network or wireless LAN, the terminal can still know whether other terminals have sent emails to it, and the number of emails sent by other terminals. Furthermore, the number of emails sent by other terminals does not include emails that have already been downloaded. This prevents the BeiDou network equipment from repeatedly counting already sent emails and resending the same emails to the first terminal.

[0034] In conjunction with the second aspect, in one possible implementation, the mailbox overview query request message also includes a service type field. When the service type field has a first value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal within the whitelist to the first terminal. When the service type field has a second value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal not within the whitelist to the first terminal. When the service type field has a third value, it indicates that the mailbox overview query request message is used to query the total number of emails sent from all second terminals to the first terminal. The first terminal has a whitelist, which stores the identifiers of the second terminals associated with the first terminal and their serial numbers.

[0035] In this way, the first terminal can specify the specific service type of the mailbox overview query request message through this service type field. After receiving the mailbox overview query request message, the Beidou network equipment can also know the service type of the mailbox overview query request message through this service type field.

[0036] In conjunction with the second aspect, in one possible implementation, when the service type field is the first value, the mailbox overview query request message also includes a sender ID field, which is a whitelist bitmap, and the first bit of the whitelist bitmap is used to indicate the identifier of the second terminal with the first sequence number in the whitelist; when the service type field is the second value, the mailbox overview query request message also includes a sender ID field, which is used to indicate the mobile phone number of the second terminal that is not in the whitelist.

[0037] In this way, after receiving the mailbox overview query request message, the Beidou network equipment can determine which terminal sent the number of letters to the first terminal based on the identifier in the sender ID field.

[0038] In conjunction with the second aspect, in one possible implementation, the mailbox overview query request message also includes a receipt indication field. This receipt indication field can be used to indicate whether the receiving device (e.g., a BeiDou network device) of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal. The application layer receipt can be used to indicate whether the receiving device has successfully received the mailbox overview query request message. The length of the receipt indication field can be 1 bit. When the receipt indication field is the value D1 (e.g., 0), it can be used to indicate that the receiving device of the mailbox overview query request message does not need to reply with an application layer receipt to the first terminal. When the receipt indication field is the value D2 (e.g., 1), it can be used to indicate that the receiving device of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal.

[0039] In conjunction with the second aspect, in one possible implementation, the mailbox profile query request message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query request message is encrypted.

[0040] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0041] In conjunction with the second aspect, in one possible implementation, the mailbox profile query request message also includes a compression indication field, which can be used to indicate whether the mailbox profile query request message is compressed.

[0042] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0043] In conjunction with the second aspect, in one possible implementation, the mailbox profile query request message also includes an application layer authentication code field, which can be used for application layer authentication.

[0044] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0045] In conjunction with the second aspect, in one possible implementation, the mailbox overview query result message also includes a whitelist indication field. When the whitelist indication field has a fourth value, it is used to indicate the number of letters sent from a second terminal that is not on the whitelist to the first terminal. When the whitelist indication field has a fifth value, it is used to indicate the number of letters sent from a second terminal on the whitelist to the first terminal, or the number of letters sent from all second terminals to the first terminal.

[0046] In this way, after the first terminal receives the mailbox overview query result message, it knows how to parse the number of letters field in the mailbox overview query result message.

[0047] In conjunction with the second aspect, in one possible implementation, the mailbox overview query result message also includes a message type indicator field. When the message type indicator field has the sixth value, it indicates that the mailbox overview query result message is used to query the number of emails sent by one or more second terminals to the first terminal. When the message type indicator field has the seventh value, it indicates that the mailbox overview query result message is used to download the content of emails sent by one or more second terminals to the first terminal.

[0048] In this way, after receiving the mailbox overview query result message, the first terminal can determine the type of the mailbox overview query result message based on the message type indicator field in the message. Therefore, the first terminal can correctly parse the mailbox overview query result message.

[0049] In conjunction with the second aspect, in one possible implementation, when the service type in the mailbox overview query request message is a second value, the whitelist indication field in the mailbox overview query result message is a fourth value, and the message type indication field in the mailbox overview query result message is a sixth value; when the service type in the mailbox overview query request message is a first value or a third value, the whitelist indication field in the mailbox overview query result message is a fifth value, and the message type indication field in the mailbox overview query result message is a sixth value.

[0050] In conjunction with the second aspect, in one possible implementation, the mailbox profile query result message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query result message is encrypted.

[0051] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0052] In conjunction with the second aspect, in one possible implementation, the mailbox profile query result message also includes a compression indication field, which can be used to indicate whether the mailbox profile query result message is compressed.

[0053] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0054] In conjunction with the second aspect, in one possible implementation, the mailbox overview query result message also includes an application layer authentication code field, which can be used for application layer authentication.

[0055] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0056] In conjunction with the second aspect, in one possible implementation, the BeiDou network device receives a mailbox overview query request message sent by the first terminal, including: the BeiDou network device receiving X SLC PDUs sent by the first terminal; X being a positive integer; the BeiDou network device assembling the X SLC PDUs into Y SLC SDUs at the SLC layer; Y being a positive integer, Y being less than or equal to X; the BeiDou network device uploading the Y SLC SDUs to the MDCP layer as Y MDCP PDUs; the BeiDou network device assembling the Y MDCP PDUs into an MDCP SDU at the MDCP layer; and the BeiDou network device removing padding data and redundant length indicator fields from the MDCP SDUs at the MDCP layer and uploading it to the APP layer as a mailbox overview query request message.

[0057] In conjunction with the second aspect, in one possible implementation, based on the mailbox overview query request message, the BeiDou network device generates a mailbox overview query result message, including: the BeiDou network device queries the short message center for the number of emails sent by one or more second terminals to the first terminal based on the mailbox overview query request message; the BeiDou network device generates the mailbox overview query result message based on the number of emails sent by one or more second terminals to the first terminal.

[0058] In conjunction with the second aspect, in one possible implementation, the BeiDou network device sends a mailbox overview query result message to the first terminal, including: the BeiDou network device sending the mailbox overview query result message to the MDCP (Message Data Convergence Protocol) layer of the BeiDou network device at the application (APP) layer, as an MDCP service data unit (SDU) of the MDCP layer; the BeiDou network device adding padding data and redundancy length indication fields to the MDCP SDU, and then splitting it into one or more MDCP protocol data units (PDUs); the one or more MDCP PDUs include a second MDCP PDU; the BeiDou network device sending the second MDCP PDU to the Satellite Link Control (SLC) layer, as an SLC SDU of the SLC layer; the BeiDou network device splitting the SLC SDU into one or more SLC PDUs; and the BeiDou network device sending the one or more SLC PDUs to the first terminal.

[0059] Thirdly, a BeiDou communication system is provided, which may include a terminal and BeiDou network equipment, wherein:

[0060] The first terminal is used to send a mailbox overview query request message to the Beidou network device. The mailbox overview query request message is used to query the number of letters sent to the first terminal by one or more second terminals. The mailbox overview query request message includes a message ID field. The message ID field is used to indicate the ID of the first letter that the first terminal successfully received last time. The ID of the first letter is used to instruct the Beidou network device to delete the first letter.

[0061] Beidou network equipment is used to receive mailbox information query request messages;

[0062] The Beidou network equipment is used to generate a mailbox overview query result message based on the mailbox overview query request message. The mailbox overview query result message includes a message quantity field. The message quantity field is used to indicate the number of messages sent by one or more second terminals to the first terminal. The number of messages sent by one or more second terminals to the first terminal does not include the number of the first message.

[0063] Beidou network equipment is used to send mailbox overview query result messages to the first terminal;

[0064] The first terminal is used to receive mailbox overview query result messages.

[0065] In this way, even when the first terminal is in an environment without a cellular network or wireless LAN, the terminal can still know whether other terminals have sent emails to it, and the number of emails sent by other terminals. Furthermore, the number of emails sent by other terminals does not include emails that have already been downloaded. This prevents the BeiDou network equipment from repeatedly counting already sent emails and resending the same emails to the first terminal.

[0066] In conjunction with the third aspect, in one possible implementation, the mailbox overview query request message also includes a service type field. When the service type field has a first value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal within the whitelist to the first terminal. When the service type field has a second value, it indicates that the mailbox overview query request message is used to query the number of emails sent from a second terminal not within the whitelist to the first terminal. When the service type field has a third value, it indicates that the mailbox overview query request message is used to query the total number of emails sent from all second terminals to the first terminal. The first terminal has a whitelist, which stores the identifiers of the second terminals associated with the first terminal and their serial numbers.

[0067] In this way, the first terminal can specify the specific service type of the mailbox overview query request message through this service type field. After receiving the mailbox overview query request message, the Beidou network equipment can also know the service type of the mailbox overview query request message through this service type field.

[0068] In conjunction with the third aspect, in one possible implementation, when the service type field is the first value, the mailbox overview query request message also includes a sender ID field, which is a whitelist bitmap, and the first bit of the whitelist bitmap is used to indicate the identifier of the second terminal with the first sequence number in the whitelist; when the service type field is the second value, the mailbox overview query request message also includes a sender ID field, which is used to indicate the mobile phone number of the second terminal that is not in the whitelist.

[0069] In this way, after receiving the mailbox overview query request message, the Beidou network equipment can determine which terminal sent the number of letters to the first terminal based on the identifier in the sender ID field.

[0070] In conjunction with the third aspect, in one possible implementation, the mailbox overview query request message also includes a receipt indication field. This receipt indication field can be used to indicate whether the receiving device (e.g., a BeiDou network device) of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal. The application layer receipt can be used to indicate whether the receiving device has successfully received the mailbox overview query request message. The length of the receipt indication field can be 1 bit. When the receipt indication field is the value D1 (e.g., 0), it can be used to indicate that the receiving device of the mailbox overview query request message does not need to reply with an application layer receipt to the first terminal. When the receipt indication field is the value D2 (e.g., 1), it can be used to indicate that the receiving device of the mailbox overview query request message needs to reply with an application layer receipt to the first terminal.

[0071] In conjunction with the third aspect, in one possible implementation, the mailbox profile query request message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query request message is encrypted.

[0072] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0073] In conjunction with the third aspect, in one possible implementation, the mailbox profile query request message also includes a compression indication field, which can be used to indicate whether the mailbox profile query request message is compressed.

[0074] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0075] In conjunction with the third aspect, in one possible implementation, the mailbox profile query request message also includes an application layer authentication code field, which can be used for application layer authentication.

[0076] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0077] In conjunction with the third aspect, in one possible implementation, the mailbox overview query result message also includes a whitelist indication field. When the whitelist indication field has a fourth value, it is used to indicate the number of letters sent from a second terminal that is not on the whitelist to the first terminal. When the whitelist indication field has a fifth value, it is used to indicate the number of letters sent from a second terminal on the whitelist to the first terminal, or the number of letters sent from all second terminals to the first terminal.

[0078] In this way, after the first terminal receives the mailbox overview query result message, it knows how to parse the number of letters field in the mailbox overview query result message.

[0079] In conjunction with the third aspect, in one possible implementation, the mailbox overview query result message further includes a message type indicator field. When the message type indicator field is a sixth value, it indicates that the mailbox overview query result message is used to query the number of letters sent by one or more second terminals to the first terminal. When the message type indicator field is a seventh value, it indicates that the mailbox overview query result message is used to download the content of one or more letters sent by one or more second terminals to the first terminal.

[0080] In this way, after receiving the mailbox overview query result message, the first terminal can determine the type of the mailbox overview query result message based on the message type indicator field in the message. Therefore, the first terminal can correctly parse the mailbox overview query result message.

[0081] In conjunction with the third aspect, in one possible implementation, when the service type in the mailbox overview query request message is a second value, the whitelist indication field in the mailbox overview query result message is a fourth value, and the message type indication field in the mailbox overview query result message is a sixth value; when the service type in the mailbox overview query request message is a first value or a third value, the whitelist indication field in the mailbox overview query result message is a fifth value, and the message type indication field in the mailbox overview query result message is a sixth value.

[0082] In conjunction with the third aspect, in one possible implementation, the mailbox profile query result message also includes an encryption indication field, which can be used to indicate whether the mailbox profile query result message is encrypted.

[0083] Furthermore, in one possible implementation, the length of the encryption indicator field can be 2 bits.

[0084] In conjunction with the third aspect, in one possible implementation, the mailbox profile query result message also includes a compression indication field, which can be used to indicate whether the mailbox profile query result message is compressed.

[0085] Furthermore, in one possible implementation, the length of the compression indicator field can be 2 bits.

[0086] In conjunction with the third aspect, in one possible implementation, the mailbox overview query result message also includes an application layer authentication code field, which can be used for application layer authentication.

[0087] Furthermore, in one possible implementation, the length of the application layer authentication code field can be 16 bits.

[0088] In conjunction with the third aspect, in one possible implementation, the first terminal is specifically used for:

[0089] The message data aggregation MDCP layer, which sends mailbox overview query request messages to the first terminal at the application APP layer, serves as the MDCP service data unit (SDU) of the MDCP layer.

[0090] After adding padding data and redundancy length indication fields to the MDCP SDU, it is split into one or more MDCP Protocol Data Units (PDUs); the one or more MDCP PDUs include the first MDCP PDU;

[0091] The first MDCP PDU is sent to the Satellite Link Control (SLC) layer as the SLC SDU of the SLC layer.

[0092] The SLC SDU is split into one or more SLC PDUs; the first terminal sends one or more SLC PDUs to the BeiDou network equipment.

[0093] In conjunction with the third aspect, in one possible implementation, the first terminal is specifically used for:

[0094] Receive P SLC PDUs sent by the BeiDou network device; P is a positive integer;

[0095] In the SLC layer, P SLC PDUs are combined into Q SLC SDUs; Q is a positive integer, and Q is less than or equal to P.

[0096] Upload Q SLC SDUs to the MDCP layer as Q MDCP PDUs for the MDCP layer;

[0097] In the MDCP layer, Q MDCP PDUs are combined into an MDCP SDU;

[0098] After removing padding data and redundant length indicator fields from the MDCP SDU at the MDCP layer, it is uploaded to the APP layer as a mailbox overview query result message.

[0099] In conjunction with the third aspect, in one possible implementation, the first terminal is also used to: parse the number of letters sent to the first terminal by one or more second terminals from the letter count field in the mailbox overview query result message; and display the number of letters sent to the first terminal by one or more second terminals on the display screen.

[0100] In conjunction with the third aspect, in one possible implementation, BeiDou network equipment is specifically used for:

[0101] Received X SLC PDUs from the first terminal; X is a positive integer;

[0102] In the SLC layer, X SLC PDUs are combined into Y SLC SDUs; Y is a positive integer, and Y is less than or equal to X.

[0103] Upload Y SLC SDUs to the MDCP layer as Y MDCP PDUs of the MDCP layer;

[0104] In the MDCP layer, Y MDCP PDUs are assembled into an MDCP SDU;

[0105] After removing padding data and redundant length indicator fields from the MDCP SDU at the MDCP layer, it is uploaded to the APP layer as a mailbox overview query request message.

[0106] In conjunction with the third aspect, in one possible implementation, the BeiDou network equipment is specifically used to: query the number of emails sent from one or more second terminals to the first terminal in the short message center according to the mailbox overview query request message; and generate a mailbox overview query result message based on the number of emails sent from one or more second terminals to the first terminal.

[0107] In conjunction with the third aspect, in one possible implementation, BeiDou network equipment is specifically used for:

[0108] The message data aggregation layer of the Beidou network equipment, which sends the mailbox overview query result message to the MDCP layer at the application APP layer, serves as the MDCP service data unit (SDU) of the MDCP layer.

[0109] After adding padding data and redundancy length indication fields to the MDCP SDU, it is split into one or more MDCP Protocol Data Units (PDUs); one or more MDCP PDUs include a second MDCP PDU;

[0110] The second MDCP PDU is sent to the Satellite Link Control (SLC) layer as the SLC SDU of the SLC layer.

[0111] The SLC SDU is split into one or more SLC PDUs; the BeiDou network device sends one or more SLC PDUs to the first terminal.

[0112] 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.

[0113] 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.

[0114] 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.

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

[0116] 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.

[0117] 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.

[0118] 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 of the possible implementations of the first aspect described above.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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

[0123] Figure 1 This is a schematic diagram of the architecture of a Beidou communication system 10 provided in an embodiment of this application;

[0124] Figure 2 This is a schematic diagram of a BeiDou communication protocol layer provided in an embodiment of this application;

[0125] 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;

[0126] 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;

[0127] 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;

[0128] 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;

[0129] Figure 7 This is a schematic flowchart of a mailbox information query method in a satellite communication system provided in an embodiment of this application;

[0130] Figures 8A-8C These are schematic diagrams of a set of user interfaces provided in the embodiments of this application;

[0131] Figure 8D This is a schematic diagram of the terminal structure provided in the embodiments of this application;

[0132] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0133] Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0134] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0135] Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0136] 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.

[0137] 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.

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

[0139] Figure 1 A schematic diagram of the architecture of a Beidou communication system 10 according to an embodiment of this application is shown.

[0140] like Figure 1 As shown, in the BeiDou communication system 10, the BeiDou communication system 10 may include a terminal 100, a BeiDou short message satellite 21, a BeiDou network device 200, and a short message service center (SMSC) 41.

[0141] In this scenario, terminal 100 is under the BeiDou network, meaning the BeiDou communication module in terminal 100 is enabled, and terminal 100 is not registered under a cellular network. Terminal 100 can query one or more terminals registered under a cellular network through BeiDou network device 200 (e.g., ...). Figure 1 The number of short messages sent by terminal 300 to terminal 100 as shown in the figure.

[0142] Specifically, terminal 100 can send a mailbox overview query request to BeiDou network device 200. This mailbox overview query request is used to query BeiDou network device 200 for the number of emails received by terminal 100. Based on this mailbox overview request, BeiDou network device 200 can query the short message center 41 for the number of emails sent to terminal 100 by other terminals. Then, BeiDou network device 200 can reply to terminal 100 with the query result, that is, the number of emails received by terminal 100.

[0143] The BeiDou network equipment 200 may include a BeiDou ground receiving station 31, a signal receiving and processing device 32, a signal processing center 33, a BeiDou ground transmitting station 35, a signal transmitting and processing device 36, an operation control center 37, and a BeiDou short message fusion communication platform 34.

[0144] In some embodiments, the signal processing center 33 and the operation control center 37 may be referred to as the BeiDou central station. In other embodiments, the signal receiving and processing device 32, the signal processing center 33, the signal transmitting and processing device 36, and the operation control center 37 may be referred to as the BeiDou central station.

[0145] For example, the BeiDou ground receiving station 31 can receive a mailbox information query request sent by terminal 100, forwarded by the BeiDou short message satellite 21. The BeiDou ground receiving station 31 can send this mailbox information query request to the signal receiving and processing device 32, which can then send the message to the signal processing center 33. The signal processing center 33 and the BeiDou short message fusion communication platform 34 can parse the mailbox information query request forwarded by the BeiDou short message satellite 21 according to the protocol, and forward the parsed content of the mailbox information query request to the Short Message Service Center (SMSC) 41. The Short Message Service Center 41 can then use the content of the mailbox information query request to find the number of messages sent by other terminals to terminal 100.

[0146] In some examples, terminal 100 can also send data to terminal 300 via BeiDou network device 200.

[0147] The BeiDou network device 200 can transmit data to the terminal 100 via the BeiDou short message satellite 21. For example, if the terminal 100 queries mailbox information, the BeiDou network device 200 can return the query results to the terminal. Specifically, the operation control center 37 can send the mailbox information query results to the signal transmission and processing device 36, which then sends the results to the BeiDou ground transmitter 35. The BeiDou ground transmitter 35 then sends the results to the BeiDou short message satellite 21, which relays them to the terminal 100. The mailbox information query results in the operation control center 37 can also be obtained from the signal processing center 33.

[0148] Here, the BeiDou ground transmitter station 35 and the BeiDou ground receiver station 31 may be composed of one or more devices with transmitting functions and one or more devices with receiving functions, or they may be one or more devices with both transmitting and receiving functions, without limitation here.

[0149] In this way, even if terminal 100 is under the BeiDou network and not registered on the cellular network, for example, if terminal 100 is in an area without cellular network coverage, terminal 100 can still query whether there are terminals under the cellular network sending emails to terminal 100, and can also know the number of emails sent to terminal 100 by terminals under other cellular networks.

[0150] In this embodiment, data sent to terminal 100, such as messages, short messages, SMS messages, emails, etc., is referred to as mail. Specifically, mail can refer to user A (e.g., not connected to a cellular network or Wi-Fi) in a non-network state (i.e., not registered on a cellular network or connected to Wi-Fi). Figure 1 The terminal 100 shown in the figure receives data from other terminals (e.g., Figure 1 The terminal 300 shown in the image sends a short message to user A. Mailbox overview query refers to the user sending a query message to the BeiDou network device 200, and the BeiDou short message fusion communication platform 34 within the BeiDou network device 200 receiving the query message. This query message carries query information, indicating the sender's phone number information of the short message the user needs to query. Mailbox overview refers to the mailbox overview information returned by the BeiDou network device 200. This mailbox overview information is not the content of the specific emails in the mailbox, but rather the number of emails sent by the sender corresponding to the query information. For example, if user A queries whether their parents have sent them any messages, the returned mailbox overview information will be the number of emails sent by their parents.

[0151] Figure 2 A schematic diagram of the BeiDou communication protocol layer of a BeiDou communication system 10 according to an embodiment of this application is shown.

[0152] like Figure 2 As shown, the BeiDou communication protocol layer can include an application layer protocol (APP) layer, a message data convergence protocol (MDCP) layer, a satellite link control protocol (SLC) layer, and a physical layer protocol (PHY) layer.

[0153] The BeiDou ground receiving station 31 and BeiDou ground transmitting station 35 can be used for data processing at the PHY layer of the BeiDou network equipment 200. The signal receiving and processing equipment 32, signal transmitting and processing equipment 36, signal processing center 33, and operation control center 37 can be used for data processing at the SLC and MDCP layers of the BeiDou network equipment 200. The BeiDou short message fusion communication platform 34 can be used for data processing at the APP layer.

[0154] Currently, only dedicated terminals can receive short messages (hereinafter referred to as "messages") relayed via BeiDou satellites in offline conditions. The specific process is as follows: when a dedicated terminal captures and tracks a BeiDou signal, it proactively initiates a power-on report. Upon receiving this report, the short message transmission and processing system station, if it has any cached messages (hereinafter referred to as "messages") for the user, directly sends all of the user's messages. Based on the user's receipt (feedback information regarding message reception), the BeiDou network equipment 200 decides whether to delete the cached messages. The cached messages are managed through a dedicated server built by the BeiDou system; no cellular operator network elements directly participate in the management, thus limiting their usage.

[0155] Currently, there is no public civilian terminal mailbox mechanism for BeiDou satellite short messages. This application embodiment redesigns the data transmission protocol in the BeiDou communication system, mainly including a mailbox overview query part.

[0156] In this embodiment, data sent from terminal 100 to BeiDou network device 200 can be referred to as inbound data. 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.

[0157] The following describes the encapsulation process of the mailbox information query request sent by terminal 100 to Beidou network device 200, and the parsing process of the mailbox information query request received by Beidou network device 200.

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

[0159] 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.

[0160] like Figure 3 As shown, the BeiDou message transmission protocol layer on 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).

[0161] 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:

[0162] At the APP layer, terminal 100 can encapsulate raw data (e.g., a mailbox overview query request) into an application layer message. Then, terminal 100 can send the application layer message to the MDCP layer through the inter-layer interface. The format of this application layer message will be described in detail below and will not be repeated here.

[0163] 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 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.

[0164] 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.

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

[0166] 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.

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

[0168] 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 check bit 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 check bit field can include the CRC code. Terminal 100 can encode the code block and check bit 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.

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

[0170] Figure 4 This 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.

[0171] like Figure 4As shown, the BeiDou short message transmission protocol layer of the BeiDou network equipment 200 can be divided into the application layer protocol (APP), the message data convergence protocol (MDCP), the satellite link control protocol (SLC), and the physical layer protocol (PHY). The BeiDou network equipment 200 may include a BeiDou ground receiving station 31, signal receiving and processing equipment 32, a signal processing center 33, a BeiDou ground transmitting station 35, signal transmitting and processing equipment 36, an operation control center 37, and a BeiDou short message fusion communication platform 34.

[0172] The BeiDou ground receiving station 31 and BeiDou ground transmitting station 35 can be used for data processing at the PHY layer of the BeiDou network equipment 200. The signal receiving and processing equipment 32, signal transmitting and processing equipment 36, signal processing center 33, and operation control center 37 can be used for data processing at the SLC and MDCP layers of the BeiDou network equipment 200. The BeiDou short message fusion communication platform 34 can be used for data processing at the APP layer.

[0173] 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:

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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 raw data. This raw data can be a mailbox overview query request.

[0178] 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.

[0179] After receiving a mailbox information query request from terminal 100, BeiDou network device 200 can reply to terminal 100 with the query results. The following describes the encapsulation process of the mailbox information query results sent by BeiDou network device 200 to terminal 100, and the parsing process of the query results received by terminal 100.

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

[0181] 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.

[0182] like Figure 5As shown, the BeiDou short message transmission protocol layer of the BeiDou network equipment 200 can be divided into the application layer protocol (APP), the message data convergence protocol (MDCP), the satellite link control protocol (SLC), and the physical layer protocol (PHY). The BeiDou network equipment 200 may include a BeiDou ground receiving station 31, signal receiving and processing equipment 32, a signal processing center 33, a BeiDou ground transmitting station 35, signal transmitting and processing equipment 36, an operation control center 37, and a BeiDou short message fusion communication platform 34.

[0183] The BeiDou ground receiving station 31 and BeiDou ground transmitting station 35 can be used for data processing at the PHY layer of the BeiDou network equipment 200. The signal receiving and processing equipment 32, signal transmitting and processing equipment 36, signal processing center 33, and operation control center 37 can be used for data processing at the SLC and MDCP layers of the BeiDou network equipment 200. The BeiDou short message fusion communication platform 34 can be used for data processing at the APP layer.

[0184] 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:

[0185] At the APP layer, the BeiDou network device 200 can encapsulate raw data (e.g., the query results of mailbox overview) into application layer messages. Then, the BeiDou network device 200 can send these application layer messages to the MDCP layer via the inter-layer interface. The format of these application layer messages will be described in detail below and will not be repeated here.

[0186] 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.

[0187] 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.

[0188] 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.

[0189] 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, 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.

[0190] 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.

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

[0192] 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.

[0193] 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).

[0194] 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:

[0195] 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.

[0196] 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).

[0197] 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.

[0198] 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.

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

[0200] 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.

[0201] This application provides a mailbox overview query method in a satellite communication system. The method includes: a terminal 100 sending a mailbox overview query request message to a BeiDou network device 200. The mailbox overview query request message includes a service type field and a message ID field. The service type field indicates the service type of the mailbox overview query request message, and the message ID field indicates the ID of the last successfully received email by the terminal. The terminal receives a mailbox overview query result message sent by the BeiDou network device 200. The mailbox overview query result message includes a whitelist indication field and a message quantity field. The whitelist indication field is used by the terminal 100 to parse the message quantity field. The message quantity field indicates the number of messages sent to the terminal 100 by one or more target terminals. Thus, users on the BeiDou network can also query whether other users have sent messages to the terminal 100.

[0202] Figure 7 An exemplary flowchart illustrates a method for querying mailbox information in a satellite communication system according to an embodiment of this application. Figure 7 As shown in the embodiments of this application, a mailbox information query method in a satellite communication system may include the following steps:

[0203] S701, Terminal 100 generates a mailbox overview query request message based on user operation. The mailbox overview query request message is used to query the number of emails sent to Terminal 100 by one or more target terminals.

[0204] Terminal 100 is operating within the BeiDou network, meaning it is in a scenario without cellular or wireless local area networks. Terminal 100 is not registered with a cellular network, and its BeiDou communication module is activated. Terminal 100 can communicate with BeiDou network device 200 through this module. Terminal 100 can query the number of messages sent to it by one or more target terminals via the BeiDou network. The identifiers of one or more target terminals can exist in a whitelist configured by terminal 100, or they may not exist in the whitelist configured by terminal 100.

[0205] In the embodiments of this application, terminal 100 may be referred to as a first terminal, and one or more target terminals may be referred to as one or more second terminals.

[0206] Terminal 100 can be configured with a whitelist, which includes the identifiers of N terminals associated with terminal 100 and the sequence number of each identifier in the whitelist. For example, the identifiers of the N terminals could be the mobile phone numbers of each of the N terminals. Optionally, the whitelist configured by terminal 100 can be stored in both terminal 100 and BeiDou network equipment 200 (e.g., BeiDou short message fusion communication platform 34). Optionally, the whitelist configured by terminal 100 can also be stored on the server of the operator (e.g., China Mobile, China Unicom, China Telecom) corresponding to the identifier of terminal 100 (e.g., [missing information]). Figure 1 The present application embodiment does not limit the short message center 41 shown in the figure.

[0207] Understandably, the sequence number of the identifiers for N terminals in the whitelist can be adjusted.

[0208] In this embodiment, the terminal identifier can be a mobile phone number, login number, International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identification Number (IMSI), or Mobile Subscriber International Integrated Service Digital Network Number (MSISDN). The following explanation uses a mobile phone number as the terminal identifier.

[0209] When a user of terminal 100 wants to query the number of emails sent to terminal 100 from a target terminal, the user can click the control on terminal 100 used to query mailbox information. Based on the user's click on the control on terminal 100 used to query mailbox information, terminal 100 can generate a mailbox information query request message.

[0210] Terminal 100 can query the number of emails sent to terminal 100 by a target terminal, or the number of emails sent to terminal 100 by one or more target terminals under a cellular network.

[0211] In one possible implementation, if the identifier of target terminal A (e.g., mobile phone number) is in a whitelist, the user can determine the number of emails sent by target terminal A to terminal 100 on terminal 100. For example, the user can enter the sequence number of target terminal A in the whitelist on terminal 100, or the user can enter the mobile phone number of target terminal A on terminal 100. Then, the user can click on the control for querying mailbox information on terminal 100.

[0212] In this embodiment of the application, a target terminal identified in the whitelist can be referred to as a target terminal within the whitelist, and a target terminal identified not in the whitelist can be referred to as a target terminal outside the whitelist.

[0213] In one possible implementation, if the identifier of target terminal B (e.g., mobile phone number) is not in the whitelist, the user can determine the number of emails sent by target terminal B to terminal 100 in terminal 100. For example, the user can enter the mobile phone number of target terminal B in terminal 100. Then, the user can click on the control for querying mailbox information in terminal 100.

[0214] Furthermore, terminal 100 may contain control 1, control 2, and control 3. Control 1 can be used to query the number of emails sent to terminal 100 by one or more target terminals in the whitelist. Control 2 is used to query the number of emails sent to terminal 100 by a single target terminal not in the whitelist. Control 3 is used to query the number of emails sent to terminal 100 by all target terminals, i.e., all target terminals in the whitelist and all target terminals not in the whitelist.

[0215] In one possible implementation, the format of the mailbox profile query request message can be as shown in Table 1 below.

[0216] Table 1

[0217]

[0218] As shown in Table 1 above, the mailbox overview query request message may include a receipt indication field, a service type field, an encryption indication field, a compression indication field, an application layer authentication code field, a sender ID field, and a message ID field. It is understood that the specific fields included in the mailbox overview query request message and their order are not limited in this embodiment. For example, when the mailbox overview query request message does not require application layer receipts by default, the receipt indication field may be omitted from the message.

[0219] The detailed descriptions of each field in the mailbox overview query request message shown in Table 1 are illustrated in Table 2 below. Table 2 provides an example of the length and detailed description of each field in Table 1.

[0220] Table 2

[0221]

[0222]

[0223] As shown in Table 2, the receipt indication field can be used to indicate whether the receiving device (e.g., Beidou network device 200) of the mailbox overview query request message needs to reply with an application layer receipt to the terminal 100. The application layer receipt can be used to indicate whether the receiving device has successfully received the mailbox overview query request message. The length of the receipt indication field can be 1 bit. When the receipt indication field is the value D1 (e.g., 0), it can be used to indicate that the receiving device of the mailbox overview query request message does not need to reply with an application layer receipt to the terminal 100. When the receipt indication field is the value D2 (e.g., 1), it can be used to indicate that the receiving device of the mailbox overview query request message needs to reply with an application layer receipt to the terminal 100. It is understood that this application embodiment does not limit the length of the receipt indication field or its specific value.

[0224] As shown in Table 2, the service type field can be used to indicate the service type of the mailbox overview query request message. In the BeiDou communication system, the service type of the message can include general messages, mailbox services (including mailbox overview query services, letter download services), etc. The length of the service type field can be 3 bits. It is understood that the length of the service type field is not limited in this application embodiment. As the number of service types increases, the length of the service type field can become longer. This application embodiment uses a service type field length of 3 bits as an example for illustration. When the service type field is 000, it indicates that the service type of the mailbox overview query request message is a general message. When the service type field is 001, it indicates that the service type of the mailbox overview query request message can be the mailbox overview query service in the mailbox service, and the mailbox overview query request message only queries the number of letters sent by the target terminal in the whitelist to terminal 100. When the service type field is 010, it indicates that the service type of this mailbox overview query request message is the mailbox overview query service within the mailbox service, specifically querying the number of emails sent to terminal 100 by all target terminals (including whitelisted and non-whitelisted target terminals). When the service type field is 011, it indicates that the service type of this mailbox overview query request message is the mailbox overview query service within the mailbox service, specifically querying the number of emails sent to terminal 100 by individual non-whitelisted target terminals. When the service type field is 100, it indicates that the service type of this mailbox overview query request message is the email download service within the mailbox service, specifically downloading emails sent to terminal 100 by whitelisted target terminals. When the service type field is 101, it indicates that the service type of this mailbox overview query request message is the email download service within the mailbox service, specifically downloading emails sent to this terminal user by all target terminals. When the service type field is 110, it indicates that the service type of this mailbox overview query request message is the mailbox service for mail downloading, specifically for downloading mail sent to this end user by a non-whitelisted user. "111" is a reserved field.

[0225] In one possible implementation, when the service type of the mailbox overview query request message is to query the number of letters sent by all target terminals to terminal 100, the mailbox overview query request message may not include the sender ID field.

[0226] As shown in Table 2, the encryption indicator field can be used to indicate whether the mailbox profile query request message is encrypted. For example, the encryption indicator field can be 2 bits long. When the encryption indicator field is the value D3 (e.g., 00), it indicates that the mailbox profile query request message is not encrypted. It is understood that this application embodiment does not limit the length of the encryption indicator field or its specific value.

[0227] As shown in Table 2, the compression indicator field can be used to indicate whether the mailbox profile query request message is compressed. For example, the length of the compression indicator field can be 2 bits. When the encryption indicator field is the value D4 (e.g., 00), it indicates that the mailbox profile query request message is not compressed. It is understood that this application embodiment does not limit the length of the compression indicator field or its specific value.

[0228] As shown in Table 2, the application layer authentication code field can be used for application layer authentication. For example, the length of this application layer authentication code field can be 16 bits. It is understood that the embodiments of this application do not limit the length of this application layer authentication code field.

[0229] As shown in Table 2, the Sender ID field can be used to indicate the identifier of the target terminal for the number of emails sent to Terminal 100 that Terminal 100 is querying. If the target terminal is in the whitelist configured by Terminal 100, then the Sender ID field contains the whitelist bitmap. If the target terminal is not in the whitelist configured by Terminal 100, then the Sender ID field contains the identifier of the target terminal (e.g., a mobile phone number).

[0230] If the whitelist contains identifiers of N target terminals, then the length of the whitelist bitmap can be N bits. For example, if the whitelist contains identifiers of 10 target terminals, then the length of the whitelist bitmap can be 10 bits. In this embodiment, N is an integer, and there is no limit to the specific value of N. The following explanation uses N equal to 10 as an example.

[0231] For example, the whitelist configured in terminal 100 can be shown in Table 3 below.

[0232] Table 3

[0233]

[0234] As shown in Table 3, the whitelist configured by terminal 100 may include the identifiers of 10 target terminals and the corresponding serial numbers of the 10 target terminals. It is understood that different users may set different whitelists. The whitelist shown in Table 3 above is only an example, and the specific identifiers and serial numbers of the terminals in the whitelist are not limited in this application embodiment.

[0235] For example, taking the whitelist shown in Table 3 as an example, the whitelist can be shown in Table 4 or Table 5 below.

[0236] Table 4

[0237]

[0238] Table 5

[0239]

[0240]

[0241] As shown in Table 4, the whitelist bitmap can occupy 10 bits, with each target terminal's identifier occupying 1 bit. In one possible implementation, the identifier of target terminal number 1 in the whitelist can occupy the most significant bit (MSB), i.e., bit 9. Then, the identifier of target terminal number 10 in the whitelist can occupy the least significant bit (LSB), i.e., bit 0. The identifier of target terminal number 2 in the whitelist can occupy bit 8. The identifier of target terminal number 3 in the whitelist can occupy bit 7. The identifier of target terminal number 4 in the whitelist can occupy bit 6. The identifier of target terminal number 5 in the whitelist can occupy bit 5. The identifier of target terminal number 6 in the whitelist can occupy bit 4. The identifier of target terminal number 7 in the whitelist can occupy bit 3. The identifier of the target terminal with sequence number 8 in the whitelist can occupy bit 2 of the 10 bits. The identifier of the target terminal with sequence number 9 in the whitelist can occupy bit 1 of the 10 bits. For example, if a user wants to query the number of emails sent to terminal 100 by the target terminal with sequence number 1 in the whitelist, then the whitelist bitmap entered by terminal 100 in the sender ID field can be "1000000000".

[0242] Optionally, in one possible implementation, as shown in Table 5, the identifier of the target terminal with sequence number 10 in the whitelist can occupy the MSB (bit 9) of the 10-bit list. Then, the identifier of the target terminal with sequence number 1 in the whitelist can occupy the LSB (bit 0) of the 10-bit list. The identifier of the target terminal with sequence number 9 in the whitelist can occupy bit 8 of the 10-bit list. The identifier of the target terminal with sequence number 8 in the whitelist can occupy bit 7 of the 10-bit list. The identifier of the target terminal with sequence number 7 in the whitelist can occupy bit 6 of the 10-bit list. The identifier of the target terminal with sequence number 6 in the whitelist can occupy bit 5 of the 10-bit list. The identifier of the target terminal with sequence number 5 in the whitelist can occupy bit 4 of the 10-bit list. The identifier of the target terminal with sequence number 4 in the whitelist can occupy bit 3 of the 10-bit list. The identifier of the target terminal with sequence number 3 in the whitelist can occupy bit 2 of the 10-bit list. The identifier of the target terminal with sequence number 2 in the whitelist can occupy bit 1 of the 10-bit list. For example, if a user wants to query the number of emails sent to terminal 100 by target terminal with sequence number 1 in the whitelist, then the whitelist bitmap that terminal 100 fills in in the sender ID field can be "0000000001".

[0243] If a user queries the number of emails sent to terminal 100 by a target terminal not on the whitelist, the sender ID field will contain the target terminal's mobile phone number. The length of this sender ID field can be 44 bits or 34 bits; there is no limitation here. For example, a user of terminal 100 wants to query the number of emails sent to terminal 100 by a target terminal with the mobile phone number "158xxxxxxxx". If this target terminal is not on terminal 100's whitelist, terminal 100 can encode the target terminal's mobile phone number "158xxxxxxxx" into 44 bits of binary data and fill it into the sender ID field. Alternatively, terminal 100 can also compress the target terminal's mobile phone number "158xxxxxxxx" and encode it into 34 bits of binary data before filling it into the sender ID field.

[0244] As shown in Table 2, the Message ID field can be used to indicate the ID of the first email successfully received by terminal 100. The first email successfully received by terminal 100 refers to the email received by terminal 100 before the user clicks the control for querying mailbox information, and the email with the shortest interval between the reception time and the time between clicking the control for querying mailbox information. The first email is sent from the target terminal to the first terminal. Specifically, the target terminal first sends the first email to the short message center 41. Then, when terminal 100 initiates email download, Beidou network device 200 can obtain the first email from the short message center 41 and send it to terminal 100.

[0245] Optionally, after terminal 100 receives the first email, BeiDou network device 200 can receive a notification that terminal 100 has successfully downloaded the first email. Upon receiving this notification, BeiDou network device can notify the short message center 41 to delete the contents of the first email. The short message center can retain the ID and sending time of the first email. The sending time of the first email can refer to the time when the target terminal sends the first email, that is, the time when the target terminal sends the first email to the short message center 41.

[0246] Optionally, if terminal 100 sends a mailbox overview query request to BeiDou network device 200 for the first time, i.e., terminal 100 has not received any emails before, then the message ID field can be an initial value (e.g., 0). When the message ID field is an initial value, it indicates that the mailbox overview query request message is used to query the number of emails sent to terminal 100 by one or more target terminals starting from the sending time of the first email sent to terminal 100 stored in the short message center 41.

[0247] S702, Terminal 100 segments the mailbox overview query request message into one or more Satellite Link Control (SLC) layer protocol data units (PDU1).

[0248] Specifically, terminal 100 can send a mailbox information query request message to the MDCP layer via the inter-layer interface. Terminal 100 can then segment the mailbox information query request message into one or more MDCP PDUs at the MDCP layer. Next, terminal 100 sends one or more MDCP PDUs to the SLC layer. At the SLC layer, terminal 100 can segment each MDCP PDU into one or more SLC PDU1s. At the SLC layer, terminal 100 can fill in its own identifier (e.g., terminal 100's mobile phone number) in the user ID field of the frame header of each SLC PDU1. For more details, please refer to [link / reference]. Figure 3 The description of the inbound data encapsulation process in the BeiDou communication system 10 will not be repeated here.

[0249] S703, Terminal 100 sends one or more SLC PDU1s to Beidou network equipment 200.

[0250] Terminal 100 can send one or more SLC PDU1s to BeiDou network device 200. Specifically, after sending one SLC PDU1 and receiving a successful reception reply from BeiDou network device 200, terminal 100 can send a second SLC PDU1 to BeiDou network device 200. Optionally, terminal 100 can also send one or more SLC PDU1s to BeiDou network device 200 sequentially, and BeiDou network device 200 can reply to terminal 100 with a successful reception reply after receiving all SLC PDU1s.

[0251] S704, Beidou network equipment 200 receives one or more SLC PDU1.

[0252] The Beidou network device 200 can receive one or more SLC PDU1s.

[0253] In one possible implementation, after the BeiDou network device 200 has received one or more SLC PDU1s, it replies to the terminal 100 that it has received all of the one or more SLC PDU1s. If the terminal 100 has sent all of the one or more SLC PDU1s, but the BeiDou network device 200 has not received all of them, the BeiDou network device 200 can send an Acknowledge (ACK) frame to the terminal 100. This ACK frame indicates that the BeiDou network device 200 has not received all of the SLC PDU1s. The terminal 100 can then resend the remaining SLC PDU1s to the BeiDou network device 200.

[0254] Furthermore, the BeiDou network device 200 can parse the identifier of the terminal 100 (e.g., mobile phone number 138xxxxxxxx) in the user ID field of the frame header of each SLC PDU1 at the SLC layer.

[0255] S705 and Beidou network equipment 200 combine one or more SLC PDU1s into a mailbox information query request message.

[0256] Specifically, the BeiDou network device 200 can assemble one or more SLC PDU1s sent by the terminal 100 into one or more SLC SDUs at the SLC layer. Then, the BeiDou network device 200 uploads the one or more SLC SDUs to the MDCP layer as...

[0257] One or more MDCP PDUs at the MDCP layer. Then, the BeiDou network device 200 can assemble one or more MDCP PDUs into an MDCP SDU at the MDCP layer. Then, the BeiDou network device 200 can upload the MDCP SDU to the APP layer as a mailbox overview query request message. (See reference here.) Figure 4 The process of decapsulating incoming data in the BeiDou communication system will not be described here.

[0258] S706 and Beidou network equipment 200 generate mailbox overview query result messages based on mailbox overview query request messages. These mailbox overview query result messages are used to indicate the number of emails sent by the target terminal to terminal 100.

[0259] The BeiDou network device 200 can query the number of emails sent to the terminal 100 in the short message center 41 based on the mailbox overview query request message. Then, the BeiDou network device 200 can generate a mailbox overview query result message, which is used to indicate the number of emails sent by the target terminal to the terminal 100.

[0260] Specifically, in one possible implementation, when the mailbox overview query request message indicates a query for the number of letters sent by all target terminals to terminal 100, the Beidou network device 200 can query the short message center 41 for the number of letters sent by all target terminals to mobile phone number 138xxxxxxxx, excluding the letter with letter ID 1, based on the identifier of terminal 100 parsed from SLC PDU1 (e.g., the mobile phone number of terminal 100 138xxxxxxxx) and the ID of the last letter received by terminal 100 parsed from the message ID field in the mailbox overview query request message.

[0261] Alternatively, in another possible implementation, when the mailbox overview query request message indicates the number of emails sent to terminal 100 by a target terminal within the whitelist, the BeiDou network device 200 can parse the identifier of terminal 100 (e.g., the mobile phone number of terminal 100, 138xxxxxxxx) from the SLC PDU1. The BeiDou network device 200 can also parse the identifier of the target terminal within the whitelist (e.g., the mobile phone number "13xxxxxxxx0") from the whitelist bitmap in the sender ID field of the mailbox overview query request message, and parse the ID of the last email received by terminal 100 (e.g., "1") from the message ID field, using the whitelist corresponding to terminal 100 stored in the BeiDou network device. The BeiDou network device 200 can query the Short Message Service (SMS) center 41, based on the identifier of terminal 100, the identifier of target terminals in the whitelist, and the ID of the last message received by terminal 100, to determine the number of messages sent from whitelisted mobile number 13xxxxxxxx0 to mobile number 138xxxxxxxx (excluding the message with message ID 1). Alternatively, in another possible implementation, when a mailbox overview query request message indicates a query for the number of messages sent from a single non-whitelisted target terminal to terminal 100, the BeiDou network device 200 can parse the identifier of terminal 100 (e.g., mobile number 138xxxxxxxx) from the SLC PDU1. The BeiDou network device 200 can also parse the identifier of the non-whitelisted target terminal (e.g., mobile number "158xxxxxxx0") from the sender ID field of the mailbox overview query request message, and the ID of the last message received by terminal 100 (e.g., "1") from the message ID field. The Beidou network device 200 can query the SMS center 41, based on the identifier of the terminal 100, the identifier of the target terminal in the whitelist, and the ID of the last message received by the terminal 100, the number of messages sent from the whitelisted mobile number 158xxxxxxx0 to the mobile number 138xxxxxxxx, excluding the message with message ID 1.

[0262] Furthermore, if the BeiDou network device 200 still stores a message with message ID 1, then upon receiving the mailbox overview query request message, the BeiDou network device 200 will delete the message with message ID 1 based on the message ID field in the mailbox overview query request message. In this way, the BeiDou network device 200 will not repeatedly count already sent messages and send the same message repeatedly to the terminal 100. It is understood that the short message center 41 can store the number of messages sent to the terminal 100 by different terminals. For example, the format of the number of messages sent to the terminal 100 by different terminals stored in the short message center 41 can be as shown in Table 6A below.

[0263] Table 6A

[0264]

[0265]

[0266] As shown in Table 6A, the SMS center 41 can store recipients of different mobile phone numbers and the sending time of the messages. For example, the recipient is mobile phone number 138xxxxxxxx (which is the mobile phone number of terminal 100 described above), and the senders in the whitelist corresponding to mobile phone number 138xxxxxxxx (e.g., mobile phone number 13xxxxxxxx0, mobile phone number 13xxxxxxxx1, etc.), the senders not in the whitelist (e.g., mobile phone number 158xxxxxxx0, mobile phone number 158xxxxxxx1, etc.), and the message sending time, etc. The recipient is mobile phone number 136xxxxxxxx, and the senders in the whitelist corresponding to mobile phone number 136xxxxxxxx (e.g., mobile phone number 159xxxxxxx0, mobile phone number 159xxxxxxx1, etc.), the senders not in the whitelist (e.g., mobile phone number 166xxxxxxx0, mobile phone number 166xxxxxxx1, etc.), and the message sending time, etc. The following is a specific explanation using the mobile phone number "138xxxxxxxx" as the recipient.

[0267] Specifically, as shown in Table 6A, 13xxxxxxxx0 is in the whitelist corresponding to mobile number 138xxxxxxxx. Mobile number 13xxxxxxxx0 sent two emails to mobile number 138xxxxxxxx, with the emails being sent at "2021 / 09 / 01 08:00:00" and "2021 / 09 / 01 18:30:05" respectively.

[0268] Specifically, as shown in Table 6A, 13xxxxxxxx1 is in the whitelist corresponding to mobile number 138xxxxxxxx. Mobile number 13xxxxxxxx1 sent two emails to mobile number 138xxxxxxxx, with the emails being sent at "2021 / 09 / 01 14:30:05" and "2021 / 09 / 01 19:35:40" respectively.

[0269] Specifically, as shown in Table 6A, 158xxxxxxx0 is not in the whitelist corresponding to mobile number 138xxxxxxxx. Mobile number 158xxxxxxx0 sent an email to mobile number 138xxxxxxxx at "2021 / 09 / 02 19:00:00". 158xxxxxxx1 is not in the whitelist corresponding to mobile number 138xxxxxxxx. Mobile number 158xxxxxxx1 sent an email to mobile number 138xxxxxxxx at "2021 / 09 / 02 19:05:10".

[0270] Optionally, the SMS center 41 may also store the content of specific messages sent by the sender to the receiver. It is understood that Table 6A above is only an example, and the embodiments of this application do not limit the format of messages sent by different target terminals to the terminal 100 stored in the SMS center 41.

[0271] Optionally, the SMS center 41 may not need to know the whitelist information of the terminal 100. That is, the SMS center 41 does not store the whitelist corresponding to the terminal 100, but only caches the SMS messages sent to the terminal 100 by different terminals. The SMS center 41 only sends the number of messages sent to the terminal 100 by one or more target terminals to the Beidou network device 200, which then determines whether the one or more target terminals are whitelisted based on the stored whitelist.

[0272] In one possible implementation, after receiving a message destined for terminal 100, the short message center 41, after determining that terminal 100 is under the BeiDou network, sends the message destined for terminal 100 to the BeiDou network device 200.

[0273] Alternatively, in another possible implementation, when the BeiDou network device 200 receives the email download query request message from the terminal 100, the BeiDou network device 200 then retrieves the email sent to the terminal 100 from the short message center 41 based on the email download query request message.

[0274] Furthermore, in one possible implementation, the BeiDou network device 200 can store the emails sent to the terminal 100. The BeiDou network device 200 can store these emails in a queue according to their original sending time. This queue can follow a first-in, first-out (FIFO) principle. That is, if the same target terminal sends multiple emails to the terminal 100, the BeiDou network device 200 will send the emails with earlier original sending times to the terminal 100 first. Then, the BeiDou network device 200 will send the emails with later original sending times to the terminal 100.

[0275] For example, the format of the messages sent from different terminals to terminal 100 stored in Beidou network device 200 can be as shown in Table 6B below.

[0276] Table 6B

[0277]

[0278] As shown in Table 6B, the BeiDou network device 200 stores messages sent from different terminals to terminal 100. Specifically, the BeiDou network device 200 can store messages from different terminals 100 in the form of a queue, arranging the messages sent to terminal 100 in chronological order of their sending time. The BeiDou network device 200 can also store the sender's identifier (e.g., mobile phone number), whether the sender's identifier is on a whitelist, the message sending time, and the message content, etc., for each message sent to terminal 100. The messages stored in the BeiDou network device 200 can follow a first-in, first-out (FIFO) principle. That is, when terminal 100 downloads messages sent by a single target terminal, the BeiDou network device 200 sends the message with the earliest sending time among the multiple messages sent by that single target terminal to terminal 100 first. And when the terminal downloads messages sent by all target terminals, the BeiDou network device 200 sends the message with the earliest sending time among the multiple messages sent by all target terminals to terminal 100 first.

[0279] In some scenarios, as shown in Table 6B, the mother's terminal (hereinafter referred to as "mother") sends two emails to terminal 100, and all users' terminals send six emails to terminal 100. If terminal 100 last downloaded the email sent by mother on "2021 / 09 / 01 14:30:05", with email ID 1, then when terminal 100 queries the number of emails sent by mother, Beidou network device 200 will reply with a message count of 1. If terminal 100 last downloaded the email sent by mother on "2021 / 09 / 01 14:30:05", with email ID 1, then when terminal 100 queries the number of emails sent by all users' target terminals, Beidou network device 200 will reply with a message count of 5.

[0280] When Beidou network device 200 successfully sends the email sent by the mother at 14:30:05 on "2021 / 09 / 01", it deletes the email (i.e., the email sent by the mother to the terminal 100 at "2021 / 09 / 01 14:30:05"); or, when Beidou network device 200 receives a mailbox overview query request message from the terminal 100, and the message ID field in the message indicates that the email ID is the same as the email ID of the email successfully sent by the mother at 14:30:05 on "2021 / 09 / 01 14:30:05" to the terminal 100, it deletes the email (i.e., the email sent by the mother to the terminal 100 at "2021 / 09 / 01 14:30:05").

[0281] In one possible implementation, the SMS center 41 and / or the BeiDou network device 200 only store messages within a preset time period. For example, if the BeiDou network device 200 only stores messages from the past three days, then the BeiDou network device 200 will delete messages sent more than three days ago after three days. As shown in Table 6B, if terminal 100 does not download the message sent on September 1, 2021 at 08:00:00 on September 4, 2021, the BeiDou network device 200 will delete the message sent on September 1, 2021 at 08:00:00 on September 4, 2021. Therefore, when terminal 100 performs a mailbox overview query at 08:00:00 on 2021 / 09 / 04, the BeiDou network equipment will not count the number of emails sent to terminal 100 by other terminals at 08:00:00 on 2021 / 09 / 01 and 08:00:00 on 2021 / 09 / 01. This can promptly reduce the cache size of the BeiDou network equipment and free up its memory space.

[0282] After the BeiDou network device 200 retrieves the number of emails sent by the target terminal to the terminal 100 from the short message center 41 in the mailbox overview query request message, the BeiDou network device 200 can generate a mailbox overview query result message based on the number of emails.

[0283] In one possible implementation, the format of the mailbox overview query result message can be as shown in Table 7 below.

[0284] Table 7

[0285]

[0286] As shown in Table 7 above, the mailbox overview query request message may include a message type indication field, an encryption indication field, a compression indication field, an application layer authentication code field, a whitelist indication field, and a message quantity field. It is understood that the specific fields included in the mailbox overview query result message in this embodiment are not limited in their order. For example, if the BeiDou network device 200 does not encrypt the mailbox overview query result message, the encryption indication field may not be included in the message.

[0287] The detailed descriptions of each field in the mailbox overview query result message shown in Table 7 are illustrated in Table 8 below. Table 8 provides an example of the length and detailed description of each field in Table 7.

[0288] Table 8

[0289]

[0290] As shown in Table 8, the message type field indicates the specific type of the mailbox overview query result message within the mailbox service. The length of this message type field can be 1 bit. When the message type field is 0, it indicates that the specific service type of the mailbox overview query result message is mailbox overview. When the message type field is 1, it indicates that the specific service type of the mailbox overview query result message is mail download.

[0291] Optionally, the message type field can also be 2 bits long. The detailed definition of the message type indicator field is shown in Table 9 below, which illustrates the types corresponding to different values ​​in the message type indicator field.

[0292] Table 9

[0293] Message type indication type 00 Mailbox Overview 01 Letters and messages 10 RSV 11 RSV

[0294] As shown in Table 9, when the message type indicator field is 00, it indicates that the specific business type of the mailbox overview query result message is mailbox overview. When the message type field is 01, it indicates that the specific business type of the mailbox overview query result message is mail download. When the message type indicator field is 10 or 11, it does not currently correspond to the message type and is reserved for later use.

[0295] It is understood that the embodiments of this application do not limit the length of the message type indicator field or the specific value of the message type indicator field.

[0296] As shown in Table 8, the encryption indicator field can be used to indicate whether the mailbox profile query request message is encrypted. For example, the encryption indicator field can be 2 bits long. When the encryption indicator field is the value D3 (e.g., 00), it indicates that the mailbox profile query request message is not encrypted. It is understood that this application embodiment does not limit the length of the encryption indicator field or its specific value.

[0297] As shown in Table 8, the compression indicator field can be used to indicate whether the mailbox profile query request message is compressed. For example, the length of the compression indicator field can be 2 bits. When the encryption indicator field is the value D4 (e.g., 00), it indicates that the mailbox profile query request message is not compressed. It is understood that this application embodiment does not limit the length of the compression indicator field or its specific value.

[0298] As shown in Table 8, the application layer authentication code field can be used for application layer authentication. For example, the length of this application layer authentication code field can be 16 bits. It is understood that the embodiments of this application do not limit the length of this application layer authentication code field.

[0299] As shown in Table 8, the whitelist indication field can be used to instruct terminal 100 to parse the message quantity field. The length of the whitelist indication field can be 1 bit. When the whitelist indication field is the value D5 (e.g., 0), it is used to instruct terminal 100 to parse the message quantity field according to the number of messages sent by a single target terminal not in the whitelist. When the whitelist indication field is the value D6 (e.g., 1), it is used to instruct terminal 100 to parse the message quantity field according to the number of messages sent by target terminals in the whitelist, or the number of messages sent by all target terminals not in the whitelist. It is understood that the embodiments of this application do not limit the length of the whitelist indication field or the specific value of the whitelist field.

[0300] As shown in Table 8, the "Number of Messages" field can be used to indicate the number of messages sent to terminal 100 by the target terminal queried by terminal 100. Specifically:

[0301] When terminal 100 queries the mailbox overview query request message for the number of emails sent to terminal 100 by a single target terminal not on the whitelist, the whitelist indication field in the mailbox overview query result message will be the value D5, and the email quantity field will contain the number of emails sent to terminal 100 by the single target terminal not on the whitelist. In this case, the length of the email quantity field can be 4 bits. Specific values ​​for the email quantity can be shown in Table 10 below.

[0302] Table 10

[0303] Fields meaning Fields meaning 0000 The target number has 0 messages. 0001 The target number has 1 message. 0010 The target number has 2 pieces of information. 0011 The target number has 3 pieces of information. … 1111 The target number has 16 messages.

[0304] As shown in Table 10, when the message count field is 0000, it indicates that a single target terminal not on the whitelist sent 0 messages to terminal 100. When the message count field is 0001, it indicates that a single target terminal not on the whitelist sent 1 message to terminal 100. When the message count field is 0010, it indicates that a single target terminal not on the whitelist sent 2 messages to terminal 100. When the message count field is 0011, it indicates that a single target terminal not on the whitelist sent 3 messages to terminal 100. Similarly, when the message count field is 1111, it indicates that a single target terminal not on the whitelist sent 16 messages to terminal 100.

[0305] Optionally, the current protocol specifies that when the number of emails field is 4 bits, if the number of emails sent to terminal 100 by the target terminal exceeds 16, when terminal 100 sends a mailbox overview query, it first replies that the number of emails sent to the terminal by the target terminal is 16 (i.e., the number of the first 16 emails). When terminal 100 performs a mailbox overview query again, it replies to terminal 100 with the number of emails after the 16th email.

[0306] Understandably, as the protocol evolves, the length of this message quantity field may not be limited to 4 bits.

[0307] When terminal 100 queries the mailbox overview query request message for the number of emails sent to terminal 100 by target terminals within the whitelist, the whitelist indication field in the mailbox overview query result message will be the value D6, and the email quantity field will contain the number of emails sent to terminal 100 by target terminals within the whitelist. In this case, the length of the email quantity field can be 40 bits. The detailed definition of the email quantity is shown in Table 11 below.

[0308] Table 11

[0309]

[0310] As shown in Table 11, taking the example of a user setting the identifiers of 10 target terminals associated with terminal 100 in the whitelist, each target terminal identifier occupies 4 bits, and the identifiers of the 10 target terminals total 5 bytes (i.e., Byte 00, Byte 1, Byte 2, Byte 3, and Byte 4). Each byte has eight bits (bits 0-bit 7). The MSB (bit 7) is the leftmost bit, representing the most significant bit, and the LSB (bit 0) is the rightmost bit, representing the least significant bit. The identifier of target terminal 1 in the whitelist occupies the high 4 bits of byte 0 (bits 7, 6, 5, and 4). The identifier of target terminal 2 in the whitelist occupies the low 4 bits of byte 0 (bits 3, 2, 1, and 0). The identifier of target terminal 3 in the whitelist occupies the high 4 bits of byte 1 (bits 7, 6, 5, and 4). The identifier of target terminal 4 in the whitelist occupies the low 4 bits of byte 1 (bits 3, 2, 1, and 0). The identifier of target terminal 6 in the whitelist occupies the high 4 bits of the second byte (bits 7, 6, 5, and 4). The identifier of target terminal 6 in the whitelist occupies the low 4 bits of the second byte (bits 3, 2, 1, and 0). The identifier of target terminal 7 in the whitelist occupies the high 4 bits of the third byte (bits 7, 6, 5, and 4). The identifier of target terminal 8 in the whitelist occupies the low 4 bits of the third byte (bits 3, 2, 1, and 0). The identifier of target terminal 9 in the whitelist occupies the high 4 bits of the fourth byte (bits 7, 6, 5, and 4). The identifier of target terminal 10 in the whitelist occupies the low 4 bits of the fourth byte (bits 3, 2, 1, and 0).

[0311] When terminal 100 queries the mailbox overview query request message for the number of emails sent to terminal 100 by all target terminals (all target terminals not on the whitelist and all target terminals on the whitelist), the whitelist indication field in the mailbox overview query result message will be the value D6, and the email quantity field will contain the number of emails sent to terminal 100 by all target terminals not on the whitelist and all target terminals on the whitelist. That is, the email quantity field includes 40 bits of the number of emails sent by all target terminals on the whitelist, and N bits of the number of emails sent by all target terminals not on the whitelist.

[0312] The number of emails from all non-whitelisted target terminals in this Nbit is the sum of the number of emails sent by all non-whitelisted target terminals, without distinguishing which specific non-whitelisted target terminals sent this sum of emails.

[0313] It is understood that the length of the letter quantity field is not limited in the embodiments of this application.

[0314] S707 and Beidou Network Equipment 200 segment mailbox overview query result messages into one or more SLC PDU2.

[0315] Specifically, the BeiDou network device 200 can send mailbox overview query result messages to the MDCP layer via the inter-layer interface. The BeiDou network device 200 can then segment the mailbox overview query result messages into one or more MDCPPDUs at the MDCP layer. Next, the BeiDou network device 200 will send one or more MDCP PDUs to the SLC layer. At the SLC layer, the BeiDou network device 200 can segment each MDCP PDU into one or more SLC PDU2s. At the SLC layer, the BeiDou network device 200 can fill in the identifier of terminal 100 (e.g., the mobile phone number of terminal 100) in the user ID field of the frame header of each SLC PDU2. For more details, please refer to [link / reference]. Figure 5 The description of the outgoing data encapsulation process in the BeiDou communication system 10 will not be repeated here.

[0316] S708, Beidou network equipment 200 sends one or more SLC PDU2 to terminal 100.

[0317] The BeiDou network device 200 can send one or more SLC PDU2s to the terminal 100. Specifically, after sending one SLC PDU2 and receiving a successful reception reply from the terminal 100, the BeiDou network device 200 can send a second SLC PDU2 to the terminal 100. Optionally, the BeiDou network device 200 can also send one or more SLC PDU2s to the terminal 100 sequentially, and the terminal 100 can reply with a successful reception reply after receiving all the SLC PDU2s. Alternatively, the terminal 100 may not reply. This application embodiment does not limit this.

[0318] S709, Terminal 100 receives one or more SLC PDU2.

[0319] Terminal 100 can receive one or more SLC PDU2.

[0320] In one possible implementation, after the terminal 100 has collected one or more SLC PDU1s, it replies to the Beidou network device 200 that it has collected the one or more SLC PDU2s.

[0321] Furthermore, the BeiDou network device 200 can parse the user ID field in the frame header of each SLC PDU2 at the SLC layer. If the terminal 100 parses the user ID field and finds that the terminal 100's identifier (e.g., mobile phone number 138xxxxxxxx) is the same, the terminal 100 uploads the one or more SLC PDU2s to the MDCP layer for further parsing; if the terminal 100 does not parse the user ID field and finds that the terminal 100's identifier is not the one sent to the terminal 100, the terminal 100 can determine that the SLC PDU2 was not sent to the terminal 100 and can discard the SLC PDU2.

[0322] S710 and Terminal 100 combine one or more SLC PDU2s into a mailbox overview query result message.

[0323] Specifically, terminal 100 can assemble one or more SLC PDU2s into one or more SLC SDUs at the SLC layer. Then, terminal 100 uploads the one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs. Then, terminal 100 can assemble one or more MDCP PDUs into an MDCP SDU at the MDCP layer. Then, terminal 100 can upload the MDCPSDU to the APP layer as a mailbox overview query result message. (See reference here.) Figure 6 The decapsulation process of outgoing data from the BeiDou communication system will not be described here.

[0324] S711, Terminal 100 parses the number of emails sent from the target terminal to Terminal 100 from the mailbox overview query result message.

[0325] Terminal 100 can parse the email count field in the mailbox overview query result message at the APP layer and obtain the number of emails sent by the target terminal to terminal 100 from the email count field.

[0326] S712, Terminal 100 displays the number of messages sent from the target terminal to Terminal 100.

[0327] Terminal 100 may display the number of emails sent to terminal 100 by the target terminal. Terminal 100 may also prompt the user with the number of emails sent to terminal 100 by the target terminal in other ways, such as by the terminal 100 verbally announcing the number of emails sent to terminal 100 by the target terminal. This embodiment of the application does not limit this.

[0328] For example, the number of emails sent to terminal 100 by whitelisted target terminals, non-whitelisted target terminals, and all target terminals can be displayed on the screen as follows: Figures 8A-8C As shown.

[0329] like Figure 8A As shown, when a user queries terminal 100 for the number of emails sent to terminal 100 from a target terminal in the whitelist, such as the number sent by the user's father's terminal, terminal 100 can display user interface 80A. This user interface 80A may include: a status bar 803 and a message notification box 804, wherein:

[0330] The status bar 803 may include a signal strength indicator 801 for mobile communication signals (also known as cellular signals) and a BeiDou communication icon 802. The signal strength indicator 801 for mobile communication signals (also known as cellular signals) is used to indicate that the current terminal 100 has no mobile communication signal, and the BeiDou communication icon 802 is used to indicate that the terminal 100 has enabled the BeiDou communication function.

[0331] The message notification box 804 is used to display the number of messages sent from the target terminal to the terminal 100, such as "Received 1 message from Dad".

[0332] Optionally, the message notification box 804 may also include a control 805, which allows the user to download an email sent by their father by clicking on the control 805.

[0333] like Figure 8B As shown, when a user queries terminal 100 for the number of emails sent to terminal 100 from a target terminal not on the whitelist, such as Xiaoming's terminal, terminal 100 can display user interface 80B. This user interface 80B may include: a status bar 803 and a message notification box 806, wherein:

[0334] For status bar error 803, please refer to the above. Figure 8A The description in the text will not be repeated here.

[0335] The message notification box 806 is used to display the number of messages sent from the target terminal to the terminal 100, such as "Received 16 messages from Xiaoming".

[0336] Optionally, the message notification box 806 may also include a control 807, which allows the user to click on the control 807 to choose to download any one of the 16 emails sent by Xiaoming or all of them.

[0337] In some scenarios, Xiaoming's terminal sends more than 16 emails to terminal 100 (e.g., 24 emails), but the BeiDou network device can only query a maximum of 16 emails. When terminal 100 queries the number of emails Xiaoming's terminal sent to it, the BeiDou network device sends the query result to terminal 100 as 16 emails sent by Xiaoming's terminal. Terminal 100 can then display that it received 16 emails from Xiaoming.

[0338] In one possible implementation, if the user downloads 10 out of the 16 emails, then the next time the user queries the number of emails sent from Xiaoming's terminal to terminal 100, the query result sent by Beidou network device 200 can include the 6 emails that were not downloaded and the 8 emails that were not queried in the previous query. That is, the number of emails sent from Xiaoming's terminal to terminal 100 is 14, and terminal 100 can display that it has received 16 emails from Xiaoming.

[0339] Alternatively, in another possible implementation, if the user does not download any of the 16 emails, then the next time the user queries the number of emails sent from Xiaoming's terminal to terminal 100, the query result sent by the Beidou network device to terminal 100 will show that the number of emails sent from Xiaoming's terminal to terminal 100 is 16. Terminal 100 can then display that it has received 16 emails from Xiaoming.

[0340] like Figure 8C As shown, when a user queries the number of emails sent to terminal 100 by all target terminals, terminal 100 can display user interface 80C. This user interface 80C may include: a status bar 803 and a message notification box 808, wherein:

[0341] For status bar error 803, please refer to the above. Figure 8A The description in the text will not be repeated here.

[0342] The message notification box 808 displays the number of emails sent to terminal 100 from target terminals on the whitelist, as well as the number of emails sent to terminal 100 from all non-whitelisted target terminals. For example, if both the father's and mother's terminals are on terminal 100's whitelist, when a user queries the total number of emails sent to terminal 100 from all target terminals, the Beidou network device 200 finds that the father's terminal sent 3 emails, the mother's terminal sent 4 emails, and the total number of emails sent to terminal 100 from all non-whitelisted target terminals is 16. The Beidou network device 200 sends the query results to terminal 100, which can then display the results. For example, the message notification box 808 might display "Received 3 emails from father," "Received 4 emails from mother," and "Received 16 other emails."

[0343] Understandably, since the identifier of the father's terminal in the whitelist corresponds to the sequence number 1 and the identifier of the mother's terminal corresponds to the sequence number 2, terminal 100 displays the number of emails sent by the father's terminal as the first one in the message queue of the message notification box 808.

[0344] Optionally, the message notification box 808 may also include controls 809, 810, or 811. Control 809 is used to download any one or all of the three letters from Dad. Control 810 is used to download any one or all of the four letters from Mom. Control 811 is used to download any one or all of the other 16 letters.

[0345] It is understandable that when the user uses controls 807, 809, 810, or 811, terminal 100 can also display an option box (not shown in the figure) for the user to select which email to download. Figure 8A , Figure 8B , Figure 8C The user interface shown may contain more or less interface content (e.g., application icons, controls, etc.), and this application embodiment does not limit this. This application embodiment also does not limit the specific form of the user interface displaying the number of letters.

[0346] Thus, through the mailbox overview query method in a satellite communication system provided in this application embodiment, even when terminal 100 is on the BeiDou network and not camped on the cellular network, it can still query the number of letters sent to terminal 100 by other terminals.

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

[0348] Figure 8DThis is a schematic diagram of the structure of the terminal 100 provided in the embodiments of this application.

[0349] 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.

[0350] 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.

[0351] 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.

[0352] 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.

[0353] 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.

[0354] 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.

[0355] 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.

[0356] 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.

[0357] 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.

[0358] 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.

[0359] 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.

[0360] 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 shooting function of the terminal 100. The processor 110 and the display screen 194 communicate via the DSI interface to enable the display function of the terminal 100.

[0361] 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.

[0362] 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.

[0363] 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.

[0364] 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.

[0365] 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.

[0366] 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.

[0367] 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.

[0368] 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.

[0369] 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.

[0370] 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 an audio device (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.

[0371] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal 100, including wireless local area networks (WLAN) (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.

[0372] 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.

[0373] 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, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0374] 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.

[0375] 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.

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

[0377] 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 skin tone. 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.

[0378] 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.

[0379] 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.

[0380] 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.

[0381] 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.

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

[0383] 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.

[0384] Non-volatile memory can include disk storage devices and flash memory.

[0385] 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.

[0386] 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.

[0387] 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.

[0388] 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.

[0389] 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.

[0390] 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.

[0391] 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.

[0392] 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.

[0393] 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.

[0394] 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.

[0395] 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.

[0396] 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.

[0397] 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.

[0398] 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.

[0399] 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.

[0400] 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.

[0401] 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.

[0402] 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.

[0403] 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.

[0404] 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.

[0405] 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.

[0406] 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 correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on 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.

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

[0408] 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.

[0409] 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.

[0410] 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.

[0411] The following will combine Figures 9 to 12 The communication device of the present application embodiment is described in detail.

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

[0413] In one design, the transceiver unit 910 can be used to send a mailbox information query request message to the Beidou network device 200;

[0414] Optionally, the transceiver unit 910 can also be used to receive mailbox overview query result messages.

[0415] The processing unit 920 can be used to send mailbox overview query request messages to the MDCP layer, and can segment the mailbox overview query request messages into one or more MDCP PDUs at the MDCP layer.

[0416] Optionally, the processing unit 920 can also be used to send one or more MDCP PDUs to the SLC layer, and each MDCP PDU can be segmented into one or more SLC PDUs1 in the SLC layer.

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

[0418] Optionally, the processing unit 920 can also be used to perform the above. Figure 7 The method embodiment shown illustrates the functional steps performed by terminal 100 related to protocol parsing, encapsulation, and computation determination.

[0419] It should be understood that the communication device 900 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.

[0420] In the case of using integrated units, see Figure 10 , Figure 10 This is a schematic diagram of the structure of the communication device 1000 provided in this application embodiment. The communication device 1000 can be the BeiDou network device 200 in the above embodiments. Optionally, the communication device 1000 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 receiving station 31, BeiDou ground transmitting station 35, signal receiving and processing equipment 32, signal processing center 33, signal transmitting and processing equipment 36, operation control center 37, and BeiDou short message fusion communication platform 34. Figure 10 As shown, the communication device 1000 may include a transceiver unit 1010 and a processing unit 1020.

[0421] In one design, the transceiver unit 1010 can be used to receive mailbox overview query request messages.

[0422] The transceiver unit 1010 can also be used to send mailbox overview query result messages.

[0423] The processing unit 1020 can be used to assemble one or more SLC PDU1s into a mailbox information query request message.

[0424] The processing unit 1020 can also be used to assemble one or more SLC PDU1s into one or more SLCSDUs at the SLC layer, upload one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer; assemble one or more MDCP PDUs into MDCP SDUs at the MDCP layer; and then upload the MDCP SDUs to the APP layer as mailbox overview query request messages.

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

[0426] Optionally, the processing unit 1020 can also be used to perform the above. Figure 7 The method embodiment shown illustrates the functional steps of protocol parsing, encapsulation, and computation determination performed by the BeiDou network device 200.

[0427] It should be understood that the communication device 1000 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.

[0428] 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 9 Any product of the aforementioned terminal 100 functions, as long as it possesses the above-mentioned features. Figure 10 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.

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

[0430] See Figure 11 , Figure 11 This is a schematic diagram of the structure of the communication device 1100 provided in an embodiment of this application. The communication device 1100 may be a terminal 100, or a device thereof. Figure 11As shown, the communication device 1100 includes a processor 1101 and a transceiver 1102 internally connected and communicating with the processor. The processor 1101 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 the computer programs. The transceiver 1102, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1102 can 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 1100 may also include an antenna 1103 and / or a radio frequency unit (not shown in the figure). The antenna 1103 and / or radio frequency unit may be located inside the communication device 1100 or separate from the communication device 1100, that is, the antenna 1103 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

[0432] The processor 1101, transceiver 1102, and memory 1104 can be connected via a communication bus.

[0433] In one design, the communication device 1100 can be used to perform the functions of the terminal 100 in the aforementioned embodiments; the processor 1101 can be used to perform the aforementioned... Figure 3 and Figure 5 as well as Figure 7 In the illustrated embodiment, 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; transceiver 1102 can be used to perform the above-mentioned... Figure 3 and Figure 5 as well as Figure 7 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.

[0434] In any of the above designs, the processor 1101 may include a transceiver for implementing receiving and transmitting 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 receiving and transmitting 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.

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

[0436] In one implementation, the communication device 1100 may include circuitry capable of performing the functions 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-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0437] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 11 The communication device 1100 may be a standalone device or part of a larger device. For example, the communication device 1100 may be:

[0438] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0439] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0440] (3) ASIC, such as modem;

[0441] (4) Modules that can be embedded in other devices;

[0442] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0443] (6) Others, etc.

[0444] As a possible product form, any network element in the BeiDou network equipment 200 described in this application embodiment (e.g., BeiDou ground receiving station 31, BeiDou ground transmitting station 35, signal receiving and processing equipment 32, signal processing center 33, signal transmitting and processing equipment 36, operation control center 37, and BeiDou short message fusion communication platform 34) can be implemented by a general bus architecture.

[0445] See Figure 12 , Figure 12 This is a schematic diagram of the structure of the communication device 1200 provided in an embodiment of this application. The communication device 1200 may be a BeiDou network device 200, or a device thereof. Figure 12 As shown, the communication device 1200 includes a processor 1201 and a transceiver 1202 internally connected and communicating with the processor. The processor 1201 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 1202, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1202 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 1200 may also include an antenna 1203 and / or a radio frequency unit (not shown in the figure). The antenna 1203 and / or radio frequency unit may be located inside the communication device 1200 or separate from the communication device 1200, that is, the antenna 1203 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

[0447] The processor 1201, transceiver 1202, and memory 1204 can be connected via a communication bus.

[0448] In one design, the communication device 1200 can be used to perform the functions of the Beidou network device 200 in the aforementioned embodiments: the processor 1201 can be used to perform the above-mentioned functions. Figure 7 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 1202 can be used to perform the above. Figure 4 , Figure 6 and Figure 7 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.

[0449] In any of the above designs, the processor 1201 may include a transceiver for implementing receiving and transmitting 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 receiving and transmitting 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.

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

[0451] 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.

[0452] 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.

[0453] 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.

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

[0455] 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.

[0456] 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.

[0457] 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)".

[0458] 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.

[0459] 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 method of mailbox profiling in a satellite communication system, characterized by, include: A first terminal sends a mailbox overview query request message to a satellite network device. This message is used to query the number of emails sent to the first terminal by one or more second terminals. The message includes a message ID field, a receipt indication field, and a service type field. The message ID field indicates the ID of the first email successfully received by the first terminal. The ID of the first email instructs the satellite network device to delete the first email. When the receipt indication field is an eighth value, it indicates that the satellite network device needs to reply with an application-layer receipt to the first terminal. When the receipt indication field is a ninth value, it indicates that the satellite network device does not need to reply with the application-layer receipt. The application-layer receipt indicates that the satellite network device successfully received the mailbox overview query request message. The message may indicate that the satellite network device has not successfully received the mailbox overview request message. If the service type field is a first value, the service type field indicates that the mailbox overview query request message is used to query the number of emails sent by a second terminal within the whitelist to the first terminal. If the service type field is a second value, the service type field indicates that the mailbox overview query request message is used to query the number of emails sent by a second terminal not within the whitelist to the first terminal. If the service type field is a third value, the service type field indicates that the mailbox overview query request message is used to query the number of emails sent by all second terminals to the first terminal. The first terminal has the whitelist configured, and the whitelist stores the identifier of the second terminal associated with the first terminal and the sequence number of the second terminal associated with the first terminal. The first terminal receives a mailbox overview query result message sent by the satellite network device; The mailbox overview query result message includes a message count field; the message count field is used to indicate the number of messages sent by the one or more second terminals to the first terminal, and the number of messages sent by the one or more second terminals to the first terminal does not include the number of the first messages.

2. The method according to claim 1, characterized in that, When the service type field is the first value, the mailbox overview query request message also includes a sender ID field, the sender ID field is a whitelist bitmap, and the first bit of the whitelist bitmap is used to indicate the identifier of the second terminal with the first sequence number in the whitelist; When the service type field is the second value, the mailbox overview query request message also includes a sender ID field, which is used to indicate the mobile phone number of the second terminal that is not in the whitelist.

3. The method of claim 2, wherein, The mailbox overview query result message also includes a whitelist indication field. When the whitelist indication field is the fourth value, the whitelist indication field is used to indicate the number of letters sent to the first terminal by a second terminal that is not on the whitelist in the letter quantity field. When the whitelist indication field is the fifth value, the whitelist indication field is used to indicate the number of letters sent from the second terminal within the whitelist to the first terminal, or the total number of letters sent from all second terminals to the first terminal.

4. The method of claim 3, wherein, The mailbox overview query result message also includes a message type indicator field. When the message type indicator field is the sixth value, the message type indicator field is used to indicate the number of letters sent by the one or more second terminals to the first terminal. When the message type indicator field is the seventh value, the message type indicator field is used to indicate that the mailbox overview query result message is used to download the content of the emails sent by the one or more second terminals to the first terminal.

5. The method of claim 4, wherein, When the service type in the mailbox overview query request message is the second value, the whitelist indication field in the mailbox overview query result message is the fourth value, and the message type indication field in the mailbox overview query result message is the sixth value; When the service type in the mailbox overview query request message is the first value or the third value, the whitelist indication field in the mailbox overview query result message is the fifth value, and the message type indication field in the mailbox overview query result message is the sixth value.

6. The method according to any one of claims 1 to 5, characterized in that, Before the first terminal sends a mailbox information query request message to the satellite network device, the method further includes: The first terminal detects the first operation and generates a mailbox overview query request message based on the first operation.

7. The method of claim 6, wherein, The first terminal sends a mailbox information query request message to the satellite network equipment, specifically including: The first terminal sends the mailbox overview query request message to the message data aggregation MDCP layer of the first terminal at the application APP layer, as the MDCP service data unit SDU of the MDCP layer; After adding padding data and redundancy length indication fields to the MDCP SDU, the first terminal splits it into one or more MDCP Protocol Data Units (PDUs); the one or more MDCP PDUs include a first MDCP PDU; The first terminal sends the first MDCP PDU to the Satellite Link Control (SLC) layer as the SLC layer's SLCSDU; The first terminal splits the SLC SDU into one or more SLC PDUs; The first terminal sends the one or more SLC PDUs to the satellite network device.

8. The method of claim 7, wherein, The first terminal receives a mailbox overview query result message sent by the satellite network device, specifically including: The first terminal receives P SLC PDUs sent by the satellite network device; where P is a positive integer. The first terminal assembles the P SLC PDUs into Q SLC SDUs at the SLC layer; where Q is a positive integer and is less than or equal to P. The first terminal uploads the Q SLC SDUs to the MDCP layer as Q MDCP PDUs of the MDCP layer; The first terminal assembles the Q MDCP PDUs into an MDCP SDU at the MDCP layer; After the first terminal removes the padding data and redundant length indication field from the MDCP SDU at the MDCP layer, it uploads it to the APP layer as a mailbox overview query result message.

9. The method of claim 8, wherein, After the first terminal receives the mailbox overview query result message sent by the satellite network device, the method further includes: The first terminal parses the number of letters sent by one or more second terminals to the first terminal from the letter number field in the mailbox overview query result message; The first terminal displays on its screen the number of messages sent by the one or more second terminals to the first terminal.

10. A method for querying mailbox information in a satellite communication system, characterized in that, include: The satellite network device receives a mailbox overview query request message sent by a first terminal. This message is used to query the number of emails sent to the first terminal by one or more second terminals. The message includes a message ID field, a receipt indication field, and a service type field. The message ID field indicates the ID of the first email successfully received by the first terminal. The ID of the first email instructs the satellite network device to delete the first email. If the receipt indication field is an eighth value, it indicates that the satellite network device needs to reply with an application-layer receipt to the first terminal. If the receipt indication field is a ninth value, it indicates that the satellite network device does not need to reply with the application-layer receipt to the first terminal. The application-layer receipt indicates that the satellite network device has successfully received the mailbox. The mailbox overview request message, or an indication that the satellite network device has not successfully received the mailbox overview request message, is used to indicate that the mailbox overview query request message is used to query the number of emails sent by a second terminal in the whitelist to the first terminal when the service type field is a first value; when the service type field is a second value when the service type field is a second value when the service type field is a third ... Based on the mailbox overview query request message, the satellite network device generates a mailbox overview query result message, which includes a message quantity field. The message quantity field is used to indicate the number of messages sent by the one or more second terminals to the first terminal, and the number of messages sent by the one or more second terminals to the first terminal does not include the number of the first message. The satellite network device sends a mailbox overview query result message to the first terminal.

11. The method according to claim 10, characterized in that, When the service type field is the first value, the mailbox overview query request message also includes a sender ID field, the sender ID field is a whitelist bitmap, and the first bit of the whitelist bitmap is used to indicate the identifier of the second terminal with the first sequence number in the whitelist; When the service type field is the second value, the mailbox overview query request message also includes a sender ID field, which is used to indicate the mobile phone number of the second terminal that is not in the whitelist.

12. The method according to claim 11, characterized in that, The mailbox overview query result message also includes a whitelist indication field. When the whitelist indication field is the fourth value, the whitelist indication field is used to indicate the number of letters sent to the first terminal by a second terminal that is not on the whitelist in the letter quantity field. When the whitelist indication field is the fifth value, the whitelist indication field is used to indicate the number of letters sent from the second terminal within the whitelist to the first terminal, or the total number of letters sent from all second terminals to the first terminal.

13. The method according to claim 12, characterized in that, The mailbox overview query result message also includes a message type indicator field. When the message type indicator field is the sixth value, the message type indicator field is used to indicate the number of letters sent by the one or more second terminals to the first terminal. When the message type indicator field is the seventh value, the message type indicator field is used to indicate that the mailbox overview query result message is used to download the content of the emails sent by the one or more second terminals to the first terminal.

14. The method according to claim 13, characterized in that, When the service type in the mailbox overview query request message is the second value, the whitelist indication field in the mailbox overview query result message is the fourth value, and the message type indication field in the mailbox overview query result message is the sixth value; When the service type in the mailbox overview query request message is the first value or the third value, the whitelist indication field in the mailbox overview query result message is the fifth value, and the message type indication field in the mailbox overview query result message is the sixth value.

15. The method according to any one of claims 10-14, characterized in that, The satellite network device receives a mailbox information query request message sent by the first terminal, including: The satellite network device receives X SLC PDUs sent by the first terminal; where X is a positive integer. The satellite network device combines the X SLC PDUs into Y SLC SDUs at the SLC layer; where Y is a positive integer, and Y is less than or equal to X. The satellite network device uploads the Y SLC SDUs to the MDCP layer as Y MDCPPDUs of the MDCP layer; The satellite network equipment combines the Y MDCP PDUs into an MDCP SDU at the MDCP layer; The satellite network device removes padding data and redundant length indication fields from the MDCP SDU at the MDCP layer and uploads it to the APP layer as a mailbox overview query request message.

16. The method according to claim 15, characterized in that, Based on the mailbox profile query request message, the satellite network device generates a mailbox profile query result message, including: The satellite network device queries the number of messages sent by the one or more second terminals to the first terminal in the short message center based on the mailbox overview query request message; The satellite network device generates a mailbox overview query result message based on the number of emails sent from one or more second terminals to the first terminal.

17. The method according to claim 16, characterized in that, The satellite network device sends a mailbox overview query result message to the first terminal, including: The satellite network device sends the mailbox overview query result message to the message data aggregation MDCP layer of the satellite network device at the application (APP) layer, as the MDCP service data unit (SDU) of the MDCP layer; The satellite network equipment adds padding data and redundancy length indication fields to the MDCP SDU, and then splits it into one or more MDCP Protocol Data Units (PDUs); the one or more MDCP PDUs include a second MDCP PDU. The satellite network equipment sends the second MDCP PDU to the Satellite Link Control (SLC) layer as the SLC SDU of the SLC layer. The satellite network equipment splits the SLC SDU into one or more SLC PDUs; The satellite network device sends the one or more SLC PDUs to the first terminal.

18. A satellite communication system, characterized in that, Includes the first terminal and satellite network equipment; among which: The first terminal sends a mailbox overview query request message to the satellite network device. The mailbox overview query request message is used to query the number of emails sent to the first terminal by one or more second terminals. The mailbox overview query request message includes a message ID field, a receipt indication field, and a service type field. The message ID field indicates the ID of the first email successfully received by the first terminal. The ID of the first email instructs the satellite network device to delete the first email. When the receipt indication field is an eighth value, it indicates that the satellite network device needs to reply with an application layer receipt to the first terminal. When the receipt indication field is a ninth value, it indicates that the satellite network device does not need to reply with the application layer receipt to the first terminal. The application layer receipt indicates that the satellite network device has successfully received the email. The mailbox overview request message, or an indication that the satellite network device has not successfully received the mailbox overview request message, is used to indicate that the mailbox overview query request message is used to query the number of emails sent by a second terminal within the whitelist to the first terminal when the service type field is a first value; when the service type field is a second value when the service type field is a second value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value when the service type field is a third value; the first terminal has the whitelist set up, and the whitelist is used to store the identifier of the second terminal associated with the first terminal and the sequence number of the second terminal associated with the first terminal; The satellite network equipment is used to receive the mailbox information query request message; The satellite network device is used to generate a mailbox overview query result message based on the mailbox overview query request message. The mailbox overview query result message includes a letter count field. The letter count field is used to indicate the number of letters sent to the first terminal by the one or more second terminals after the sending time of the first letter. The number of letters sent to the first terminal by the one or more second terminals does not include the number of the first letter. The satellite network device is used to send the mailbox overview query result message to the first terminal; The first terminal is used to receive the mailbox overview query result message.

19. 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 1-9.

20. The communication device according to claim 19, characterized in that, The communication device is a terminal.

21. 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, and the one or more memories are 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 10-17.

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

23. 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-9.

24. 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 10-17.

25. A chip system applied 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-9.

Images