A whitelist control method and related device in a satellite communication system

Abstract

The application discloses a whitelist control method in a satellite communication system and related devices. The application relates to the field of satellite communication. After a Beidou network device receives a first short message sent by a second terminal to a first terminal under a Beidou network, whether the identity of the second terminal is included in the whitelist of the first terminal can be determined based on the stored whitelist of the first terminal. When the Beidou network device determines that the identity of the second terminal is included in the whitelist of the first terminal, the Beidou network device stores the first short message. When the Beidou network device determines that the identity of the second terminal is not included in the whitelist of the first terminal, the Beidou network device discards the first short message. In this way, the Beidou network device can only receive and forward short messages sent by terminals in the whitelist, thereby saving storage space and air interface transmission resources of the Beidou communication system and reducing the power consumption of the first terminal for receiving the short messages.

Description

Technical Field

[0001] This application relates to the field of satellite communications, and in particular to a whitelist control method and related apparatus in a satellite communication system. Background Technology

[0002] The BeiDou short message service is one of the distinctive features of the BeiDou Navigation Satellite System compared to other global positioning and navigation systems such as the US Global Positioning System (GPS) and Russia's Global Navigation Satellite System (GLONASS). It is particularly suitable for positioning and communication in areas such as oceans, deserts, grasslands, and uninhabited areas where mobile communication is unavailable, lacks coverage, or where communication systems are damaged. The BeiDou short message service communication system requires an upgraded technical architecture, and the communication protocol needs to be designed specifically for civilian services and equipment characteristics.

[0003] Currently, when a BeiDou network device receives a short message from a second terminal to a first terminal within the BeiDou network, it will forward the message to the first terminal. However, the BeiDou network device will also forward some unimportant short messages (such as advertising messages) to the first terminal. This consumes air interface transmission resources in the BeiDou communication system and increases the power consumption of the first terminal receiving short messages. Summary of the Invention

[0004] This application provides a whitelist control method and related apparatus in a BeiDou communication system. This application relates to the field of satellite communication. After receiving a first short message from a second terminal to a first terminal under the BeiDou network, the BeiDou network device can determine whether the whitelist of the first terminal includes the identifier of the second terminal, based on the stored whitelist of the first terminal. If the BeiDou network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the BeiDou network device stores the first short message. If the BeiDou network device determines that the whitelist of the first terminal does not include the identifier of the second terminal, the BeiDou network device discards the first short message. In this way, the BeiDou network device can only receive and forward short messages sent by terminals in the whitelist, saving storage space and air interface transmission resources of the BeiDou communication system, and reducing the power consumption of the first terminal receiving short messages.

[0005] In a first aspect, this application provides a whitelist control method in a BeiDou communication system, comprising: a BeiDou network device receiving a first short message sent from a second terminal to a first terminal via a cellular network device; when the BeiDou network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the BeiDou network device stores the first short message; when the BeiDou network device determines that the whitelist of the first terminal does not include the identifier of the second terminal, the BeiDou network device discards the first short message.

[0006] The method provided in this application saves storage space in BeiDou network equipment, reduces the occupation of air interface transmission resources in the BeiDou communication system, and lowers the power consumption of the first terminal receiving BeiDou short messages from BeiDou network equipment.

[0007] In one possible implementation, when the BeiDou network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the BeiDou network device stores the first short message. The method further includes: the BeiDou network device sending a confirmation message to the cellular network device, the confirmation message being used to instruct the cellular network device to delete the first short message.

[0008] In one possible implementation, after the BeiDou network device receives a first short message sent from a second terminal to a first terminal via a cellular network device, the method further includes: the BeiDou network device receiving a first request from the first terminal; the first request being used to obtain short messages sent from one or more terminals to the first terminal, the one or more terminals including the second terminal; when the first terminal's whitelist includes the second terminal, the BeiDou network device sending the first short message to the first terminal; when the first terminal's whitelist does not include the second terminal, the BeiDou network device sending first indication information to the first terminal, the first indication information being used to indicate that the BeiDou network device does not store short messages sent from the second terminal to the first terminal.

[0009] In one possible implementation, after the BeiDou network device receives the first request from the first terminal, the method further includes: when the first terminal's whitelist does not include the second terminal, the BeiDou network device adds the identifier of the second terminal to the first terminal's whitelist.

[0010] In one possible implementation, the BeiDou network device adds the second terminal to the whitelist of the first terminal. Specifically, when the number of terminal identifiers already stored in the whitelist of the first terminal in the BeiDou network device is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the BeiDou network device replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

[0011] In one possible implementation, the first request includes a service type field, which indicates the service type of the first request; wherein, the service type of the first request includes downloading SMS services sent by specified terminals within the whitelist, downloading SMS services sent by all terminals, and downloading SMS services sent by specified terminals not on the whitelist.

[0012] In one possible implementation, when the service type of the first request is to download short messages sent by a specified terminal in the whitelist, the first request also includes a whitelist unit map field, which is used to indicate the sequence number of the second terminal in the whitelist of the first terminal.

[0013] In one possible implementation, when the service type of the first request is to download a short message sent by a specified terminal that is not on the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal.

[0014] Secondly, this application provides a whitelist control method in a BeiDou communication system, comprising: a first terminal sending a first request to a BeiDou network device, the first request being used to obtain short messages sent to the first terminal by one or more terminals, the one or more terminals including a second terminal; when the whitelist of the first terminal includes the identifier of the second terminal, the first terminal receives a first short message from the second terminal sent by the BeiDou network device; when the whitelist of the first terminal does not include the identifier of the second terminal, the first terminal receives a first indication information sent by the BeiDou network device, the first indication information being used to indicate that the BeiDou network device does not store short messages sent to the first terminal by the second terminal.

[0015] In one possible implementation, after the first terminal sends a first request to the BeiDou network device, the method further includes: when the service type of the first request is to download a short message service sent by a specified terminal that is not in the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal; the first terminal adds the identifier of the second terminal to the whitelist of the first terminal.

[0016] In one possible implementation, the first terminal adds the identifier of the second terminal to the whitelist of the first terminal. Specifically, when the number of terminal identifiers already stored in the whitelist of the first terminal is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the first terminal replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

[0017] In one possible implementation, the first terminal adjusts its whitelist through the BeiDou operation server.

[0018] Thirdly, this application provides a BeiDou communication system, including: a first terminal and BeiDou network equipment.

[0019] Beidou network equipment is used to receive the first short message sent from the second terminal to the first terminal;

[0020] The BeiDou network equipment is also used to store the first short message when the whitelist of the first terminal includes the identifier of the second terminal; and to discard the first short message when the whitelist of the first terminal does not include the identifier of the second terminal.

[0021] The first terminal is used to send a first request to the BeiDou network equipment. The first request is used to obtain short messages sent to the first terminal by one or more terminals, including the second terminal.

[0022] The first terminal is also used to receive a first short message from the second terminal sent by the Beidou network device when the whitelist of the first terminal includes the identifier of the second terminal; and to receive a first indication message sent by the Beidou network device when the whitelist of the first terminal does not include the identifier of the second terminal, wherein the first indication message is used to indicate that the Beidou network device does not store the short message sent by the second terminal to the first terminal.

[0023] 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 second aspect described above.

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

[0025] 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 first aspect described above.

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

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

[0028] 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 first aspect described above.

[0029] 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 second aspect above.

[0030] 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 first aspect described above.

[0031] 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 second aspect above. Attached Figure Description

[0032] Figure 1 This application provides a schematic diagram of the architecture of a BeiDou communication system.

[0033] Figure 2A A schematic diagram of the protocol encapsulation architecture for inbound data of a Beidou communication system provided in this application embodiment;

[0034] Figure 2B A schematic diagram of the protocol parsing architecture for inbound data of a Beidou communication system is provided for embodiments of this application;

[0035] Figure 3A A schematic diagram of the protocol encapsulation architecture for outbound data of a Beidou communication system provided in this application embodiment;

[0036] Figure 3B A schematic diagram of the protocol parsing architecture for outbound data of a Beidou communication system provided in this application embodiment;

[0037] Figure 4 A schematic diagram of a message request process in a Beidou communication system provided for an embodiment of this application;

[0038] Figure 5 A flowchart illustrating a whitelist control method in a BeiDou communication system, provided as an embodiment of this application;

[0039] Figures 6A-6G A set of interface schematic diagrams provided for embodiments of this application;

[0040] Figures 7A-7G Another set of interface schematic diagrams provided for embodiments of this application;

[0041] Figures 8A-8C Another set of interface schematic diagrams provided for embodiments of this application;

[0042] Figure 9 A flowchart illustrating another whitelist control method in a BeiDou communication system provided in this application embodiment;

[0043] Figure 10 A flowchart illustrating another whitelist control method in a BeiDou communication system provided in this application embodiment;

[0044] Figure 11 A schematic diagram of a hardware structure provided for an embodiment of this application;

[0045] Figure 12 A flowchart illustrating a whitelist control method in a BeiDou communication system, provided as an embodiment of this application;

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

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

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

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

[0050] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone.

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

[0052] In some embodiments, when the first terminal is under the BeiDou network, it can send a mailbox overview query request (also known as an overview request) to the BeiDou network device. This overview request can be used to instruct the BeiDou network device to send query results to the first terminal. The query results include the number of short messages sent to the first terminal by other terminals. For example, the first terminal can query whether there are short messages from a second terminal, and the returned query result is the number of short messages sent by the second terminal. The first terminal can also send a message download request (also known as a message request) to the BeiDou network device. This message request can be used to instruct the BeiDou network device to send download results to the first terminal. The download results include the content of short messages sent to the first terminal by other terminals. In this way, even if the first terminal is under the BeiDou network but not registered with a cellular network, for example, if the first terminal is in an area without cellular network coverage, the first terminal can still query whether other terminals under the cellular network have sent messages to the first terminal, and can know the number and content of messages sent to the first terminal by other terminals under the cellular network. Here, the first terminal being under the BeiDou network means that the BeiDou communication module in the first terminal is turned on, and the first terminal is not registered with a cellular network.

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

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

[0055] like Figure 1 As shown, in the BeiDou communication system 10, the BeiDou communication system 10 may include, but is not limited to, terminal 100, BeiDou short message satellite 21, BeiDou network equipment 200, cellular network equipment 400, terminal 300, etc.

[0056] Among them, terminal 100 is under the BeiDou network, and terminal 100 can query one or more terminals residing in the cellular network through BeiDou network equipment 200 (e.g., Figure 1 The number of short messages sent by terminal 300 to terminal 100 as shown in the diagram. Terminal 100 can also download the message content of short messages sent to terminal 100 by one or more terminals (e.g., terminal 300) residing in the cellular network via BeiDou network device 200.

[0057] Specifically, terminal 100 can send a mailbox overview query request (also known as an overview request) to BeiDou network device 200. After receiving the overview request, BeiDou network device 200 can obtain the number of emails sent to terminal 100 by other terminals based on the overview request. Then, BeiDou network device 200 can reply to terminal 100 with the query result, that is, the number of emails received by terminal 100.

[0058] Terminal 100 can send a message download request (also known as a message request) to BeiDou network device 200. After receiving the message request, BeiDou network device 200 can obtain the content of messages sent to terminal 100 by other terminals based on the message request. Then, BeiDou network device 200 can reply to terminal 100 with the download result, that is, the content of the message received by terminal 100.

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

[0060] The cellular network equipment 400 may include, but is not limited to, a short message service center (SMSC) 25 and a home location register (HLR) / home subscriber server (HSS) 28. The SMSC 25 can be used to store and forward short messages; that is, the SMSC 25 can forward data sent by terminals under the BeiDou network via the BeiDou network equipment 200 to terminals under the cellular network, and can also be used to send data sent by terminals under the cellular network to terminals under the BeiDou network via the BeiDou network equipment 200. The HLR / HSS 28 can be used to record the network where the terminal resides (e.g., the BeiDou network, the cellular network).

[0061] In some embodiments, a BeiDou network terminal 100 can send BeiDou short messages to a cellular network terminal 300. Specifically, terminal 100 can first send a BeiDou short message to BeiDou short message satellite 21. BeiDou short message satellite 21 only acts as a relay and can directly forward the BeiDou short message sent by terminal 100 to the ground-based BeiDou network device 200. BeiDou network device 200 can parse the BeiDou short message forwarded by the satellite according to the BeiDou communication protocol and forward the message content parsed from the BeiDou short message to cellular network device 400. Cellular network device 400 can forward the message content to terminal 300 through a traditional cellular communication network.

[0062] Cellular network terminal 300 can also send short messages to BeiDou network terminal 100. Specifically, terminal 300 can send short messages to short message center 25 via traditional cellular communication networks. Short message center 25 can forward the short message from terminal 300 to BeiDou network device 200. BeiDou network device 200 can encapsulate the content of the short message from terminal 300 into a BeiDou short message and relay it to terminal 100 via BeiDou short message satellite 21.

[0063] Optionally, the BeiDou communication system 10 may also include a national emergency rescue platform and a national emergency rescue center. The BeiDou network equipment 200 can transmit emergency rescue messages sent by the terminal 100 to the national emergency rescue center through the national emergency rescue platform.

[0064] It should be noted that in the BeiDou communication system, the process of terminal 100 sending data to BeiDou network device 200 is called inbound transmission. The process of BeiDou network device 200 sending data to terminal 100 is called outbound transmission. In this embodiment, the data sent to terminal 100, such as messages, short messages, SMS, emails, etc., can be referred to as letters.

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

[0066] Figure 2A 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.

[0067] like Figure 2A As shown, the BeiDou message transmission protocol layer on terminal 100 can be divided into application layer, message data aggregation layer, satellite link control layer and physical layer.

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

[0069] At the APP layer, terminal 100 can generate application layer messages based on raw data. Specifically, terminal 100 can add message header information before the raw data to obtain the application layer message. The message header information may include, but is not limited to, a service type field. The service type field can be used to indicate the service type of the application layer message generated by terminal 100, such as message communication service (also known as general data service), mailbox overview query service, email message download service, etc.

[0070] It should be noted that when the service type field indicates that the application layer message is a message communication service, the raw data of the application layer message may include, but is not limited to, user-input text information, voice, images, animations, receiver IDs, etc. Terminal 100 can send BeiDou short messages to the terminal indicated by the receiver ID through the application layer message of the message communication service.

[0071] When the service type field indicates that the service of the application layer message is mailbox overview query service / mail message download service, the application layer message may not include the original data. After receiving the mailbox overview query service application layer message (i.e., the aforementioned overview request), the BeiDou network device 200 can send the query result to the terminal 100. After receiving the new message download service application layer message (i.e., the aforementioned mail request), the BeiDou network device 200 can send the download result to the terminal 100.

[0072] Optionally, the summary request and message request may include raw data, which may include a message ID. The message ID can be used to indicate the most recently received BeiDou short message by terminal 100. In this way, BeiDou network device 200 can determine the most recently sent BeiDou short message to terminal 100 based on the message ID, facilitating the BeiDou network device 200 to send BeiDou short messages that terminal 100 has not yet received. When terminal 100 has not yet started receiving BeiDou short messages, the message ID value can be set to a preset initial value.

[0073] Optionally, terminal 100 can encrypt the original data and add an encryption indicator field to the message header. This encryption indicator field can be used to indicate the encryption algorithm used by terminal 100 to encrypt the data. Optionally, before encrypting the original data, terminal 100 can compress the original data. It is understood that the message header can also include a compression indicator field. This compression indicator field can be used to indicate the type of compression algorithm used by terminal 100 to compress the data. Further optionally, terminal 100 can compress the original data to obtain compressed data. Terminal 100 can add the aforementioned compression indicator field before the compressed data. Then, it uses a key to encrypt the compressed data with the added compression indicator field to obtain the encrypted data.

[0074] It should also be noted that when the value of the encryption indicator field is a specified value (e.g., 0), it can be used to indicate that the terminal 100 has not encrypted the original data. When the value of the compression indicator field is a specified value (e.g., 0), it can be used to indicate that the terminal 100 has not compressed the original data.

[0075] At the MDCP layer, terminal 100 can obtain application layer messages sent by the APP layer through the inter-layer interface and treat the application layer messages as an MDCP SDU. At the MDCP layer, terminal 100 can add padding data to the end of the MDCPSDU to a specified length and add a redundancy length indicator field to the MDCP SDU. This redundancy length indicator field can be used to indicate the length of the padding data. Terminal 100 can split the padding data and the MDCPSDU with the added redundancy length indicator field into one or more fixed-length MDCP segments (M_segment), and add a successor indicator field to the header of each MDCP segment to obtain an MDCP PDU. That is, an MDCP PDU includes an M_segment and a successor indicator field. The successor indicator field can be used to indicate the order of the current MDCPPDU among multiple MDCPPDUs in the same MDCPSDU, or that the current MDCPPDU is the only MDCPPDU.

[0076] At the SLC layer, terminal 100 can obtain the MDCPPDU issued by the MDCP layer through the inter-layer interface, which serves as the SLC SDU. At the SLC layer, terminal 100 can segment the SLC SDU into one or more (e.g., four) fixed-length SLC segment data (S_segment), and add frame header information (also known as frame format indication information) to the header of each S_segment to obtain the SLCPDU. The frame header information may include, but is not limited to, a user ID field, a total frame count field, and a frame sequence number field. The user ID field can be used to indicate the terminal (e.g., terminal 100) that generated the SLC PDU. The total frame count field can be used to indicate the total number of SLC PDUs included in the SLC SDU to which this SLC PDU belongs. The frame sequence number field can be used to indicate the sequence number of this SLC PDU within its respective SLC SDU.

[0077] At the PHY layer, terminal 100 can obtain the SLC PDU issued by the SLC layer through the inter-layer interface. Terminal 100 can perform inbound physical layer processing on it (e.g., coding, modulation, spreading, etc.) to obtain inbound data. Then, terminal 100 can send the inbound data to BeiDou short message satellite 21, which will relay it to BeiDou network equipment 200.

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

[0079] like Figure 2B As shown, the BeiDou message transmission protocol layer on the BeiDou network device 200 can be divided into the application layer, message data aggregation layer, satellite link control layer, and physical layer. The BeiDou network device 200 may include, but is not limited to, the BeiDou ground transceiver station 22, the BeiDou central station 23, and the BeiDou short message fusion communication platform 24. The BeiDou ground transceiver station 22 can be used to handle the protocol processing of the PHY layer. The BeiDou central station 23 can be used to handle the protocol processing of the SLC layer and MDCP layer. The BeiDou short message fusion communication platform 24 can be used to handle the protocol processing of the APP layer.

[0080] When the BeiDou network device 200 receives data sent by the terminal 100, the workflow of the BeiDou message transmission protocol on the BeiDou network device 200 can be as follows:

[0081] At the PHY layer, the BeiDou network device 200 can acquire the inbound data sent by the terminal 100. After performing inbound physical layer processing on the inbound data (e.g., despreading, demodulation, decoding, etc.), the BeiDou network device 200 can present it to the SLC layer through the inter-layer interface as the SLC PDU of the SLC layer.

[0082] At the SLC layer, the BeiDou network device 200 can combine SLC PDUs belonging to the same terminal 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.

[0083] At the MDCP layer, the BeiDou network device 200 can concatenate all MDCP PDUs belonging to the same MDCP SDU according to their reception time, and remove the padding data and redundancy length indicator field from the concatenated MDCPPDU to obtain the MDCPSDU. The BeiDou network device 200 can then present the MDCP SDU to the APP layer through the inter-layer interface, serving as the application layer message received by the APP layer. Optionally, when receiving the first MDCPPDU of the MDCPSDU, the BeiDou network device 200 can use the time of receipt of that first MDCPPDU as the reception time and upload that time to the APP layer.

[0084] At the APP layer, the BeiDou network device 200 can determine whether to decrypt based on the encryption indication field in the application layer message header. The BeiDou network device 200 can also determine the type of the application layer message based on the service type field.

[0085] When the service type of the application layer message is message communication, the BeiDou network device 200 can send the content of the application layer message to the terminal indicated by the receiver ID. Optionally, the BeiDou network device 200 can decrypt the encrypted data to obtain compressed data. After decompressing the compressed data, the BeiDou network device 200 obtains the authentication code and the original data.

[0086] When the service type of the application layer message is a mailbox overview query service (i.e., the application layer message is the aforementioned overview request), the BeiDou network device 200 can determine the number of short messages sent to terminal 100 by different terminals based on the short messages sent to terminal 100 by other terminals. The BeiDou network device 200 can generate a query result based on the identifier of other terminals and the number of short messages sent by other terminals, and send the query result to terminal 100. The query result is a BeiDou short message that includes the identifier of other terminals and the number of short messages sent to terminal 100 by other terminals. The terminal identifier can be the terminal's user ID, such as the terminal's mobile phone number, login number, International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identification Number (IMSI), Mobile Subscriber International Integrated Service Digital Network Number (MSISDN), etc. The following explanation uses a mobile phone number as the terminal identifier.

[0087] When the service type of the application layer message is a letter message download service (i.e., the application layer message is the aforementioned letter request), the BeiDou network device 200 can generate a download result based on the short message sent to terminal 100 by other terminals, and send the download result to terminal 100. The download result is a BeiDou short message that includes the identifier of the other terminal and the content of the short message sent to terminal 100 by the other terminal.

[0088] Optionally, the application layer message received by the BeiDou network device 200 may include a message ID field, which can be used to indicate the value of the message ID of the most recently received BeiDou short message by the terminal 100. The BeiDou network device 200 can determine the BeiDou short messages already sent to the terminal 100 based on the message ID field and send the content of any unsent short messages to the terminal 100. Optionally, the BeiDou network device 200 can delete the BeiDou short message indicated by the message ID.

[0089] Optionally, the short message in the BeiDou network device 200 may also include the original message sending time information. The original message sending time information can be used to indicate the time when other terminals sent the short message to the BeiDou network device 200.

[0090] Optionally, the application layer message may include encrypted data. The BeiDou network device 200 can decrypt the encrypted data based on the encryption indication field. Optionally, the application layer message may include compressed data, and the BeiDou network device 100 can decompress the compressed data based on the compression indication field to obtain the original data.

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

[0092] The following describes a protocol architecture for outbound data of a Beidou communication system 10 provided in this application embodiment.

[0093] Figure 3A 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.

[0094] like Figure 3A As shown, the BeiDou message transmission protocol layer on the BeiDou network equipment 200 can be divided into the application layer, message data aggregation layer, satellite link control layer, and physical layer.

[0095] When BeiDou network device 200 sends data to terminal 100, the workflow of the BeiDou message transmission protocol on BeiDou network device 200 can be as follows:

[0096] At the APP layer, the BeiDou network device 200 can generate application layer messages based on raw data. Specifically, the BeiDou network device 200 can add message header information before the raw data to obtain the application layer message. The message header information may include, but is not limited to, a message type indicator field. The message type indicator field can be used to indicate the service type of the application layer message generated by the BeiDou network device 200, such as mailbox overview query service, email message download service, etc.

[0097] Specifically, when the service type of the application layer message is mailbox overview query service, the raw data of the application layer message may include, but is not limited to, the number of short messages sent to terminal 100 by other terminals, and the identifiers of other terminals. Here, the application layer message generated by Beidou network device 200 with the service type of mailbox overview query service can be called the query result.

[0098] When the service type of the application layer message is a letter message download service, the raw data of the application layer message may include, but is not limited to, the message content of short messages sent by other terminals to terminal 100 (e.g., message text, semaphore, voice, images, animations, etc.), and the identifiers of other terminals. Here, the application layer message generated by the Beidou network device 200 with the service type of letter message download service can be referred to as the download result.

[0099] Optionally, the application layer message may also include a message ID field. The message ID field can be used to indicate the application layer message.

[0100] Optionally, the BeiDou network device 200 can encrypt the original data and add an encryption indicator field to the message header. This encryption indicator field can be used to indicate the encryption algorithm used by the BeiDou network device 200 to encrypt the data. Optionally, the BeiDou network device 200 can compress the original data before encrypting it. It is understood that the message header can also include a compression indicator field. This compression indicator field can be used to indicate the type of compression algorithm used by the BeiDou network device 200 to compress the data. Further, optionally, the BeiDou network device 200 can compress the original data to obtain compressed data. The BeiDou network device 200 can add the aforementioned compression indicator field before the compressed data, and then encrypt the compressed data with the added compression indicator field using a key to obtain encrypted data. It should also be noted that when the value of the encryption indicator field is a specified value (e.g., 0), it can be used to indicate that the BeiDou network device 200 has not encrypted the original data. When the value of the compression indicator field is a specified value (e.g., 0), it can be used to indicate that the BeiDou network device 200 has not compressed the original data.

[0101] At the MDCP layer, the BeiDou network device 200 can obtain application layer packets sent from the APP layer through the inter-layer interface and treat each application layer packet as an MDCP SDU. The BeiDou network device 200 can split the MDCP SDU into one or more fixed-length MDCP segments (M_segment) 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_segment and a successor indication field. The successor indication field can be used to indicate the order of the current MDCPPDU within the same MDCPSDU.

[0102] At the SLC layer, the BeiDou network device 200 can obtain the MDCPPDU issued by the MDCP layer through the inter-layer interface, which serves as the SLC SDU. The BeiDou network device 200 can segment the SLC SDU into one or more (e.g., four) fixed-length SLC segment data (S_segment), and add frame header information to the header of each S_segment to obtain the SLC PDU. The frame header information may include, but is not limited to, a user ID field, a total frame count field, and a frame sequence number field. The user ID field can be used to identify the receiving device (e.g., terminal 100), and its value is the ID number of the receiving device. For a detailed description of the total frame count field and the frame sequence number field, please refer to the embodiment described in 3A above, which will not be repeated here.

[0103] At the PHY layer, the BeiDou network device 200 can obtain the SLC PDU issued by the SLC layer through the inter-layer interface, which serves as the user frame. The BeiDou network device 200 can concatenate multiple user frames or a single user's user frames (also known as data frames), adding a frame header (e.g., version number) and a checksum to obtain the physical frame. The BeiDou network device 200 can then perform encoding, modulation, and spreading operations on the physical frame to obtain the encoded data for the message branch (S2C-d branch). The BeiDou network device 200 can combine the encoded data from the S2C-d branch with the pilot data (also known as the subcode) from the pilot branch (S2C-p branch) to form pilot encoded data, i.e., outgoing data. This outgoing data is then sent to the BeiDou short message satellite 21, which relays it to one or more terminals. It is understood that the pilot data of the S2C-p branch is related to the satellite beam. When the satellite beam information is known, the pilot data of the S2C-p branch is also known and does not require decoding. The encoded data of the S2C-d branch needs to be decoded.

[0104] Figure 3B 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.

[0105] like Figure 3B As shown, the BeiDou message transmission protocol layer on terminal 100 can be divided into application layer, message data aggregation layer, satellite link control layer and physical layer.

[0106] At the PHY layer, terminal 100 can capture the encoded data of the S2C-d tributary based on the subcode of the S2C-p tributary sent by Beidou network device 200. After capturing the encoded data of the S2C-d tributary, terminal 100 can perform operations such as despreading, demodulation, and decoding on the encoded data of the S2C-d tributary to obtain physical frames. Terminal 100 can extract user frames belonging to terminal 100 from the physical frames. Terminal 100 can then present the user frames to the SLC layer through the inter-layer interface as SLC PDUs for the SLC layer.

[0107] At the SLC layer, when the user frame received by terminal 100 is a general data frame, terminal 100 can concatenate SLC PDUs belonging to the same SLC SDU into a single SLC SDU. 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. When the user frame received by terminal 100 is an ACK frame, terminal 100 can retransmit data or send the next SLC SDU based on the value of the bitmap field.

[0108] At the MDCP layer, terminal 100 can concatenate one or more MDCP PDUs into an MDCP SDU. 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.

[0109] At the APP layer, when terminal 100 determines that the application layer message is a query result based on the message type indication field in the received application layer message, terminal 100 can display message summary information. The message summary information includes the contact name indicated by the identifier of other terminals in the query result, and the number of short messages sent by that contact. For example, if the query result includes the identifier "13xxxxxxxx9" and the corresponding message count is 2, and the identifier indicates the contact "Lily," then the message summary information can indicate to the user that there are two messages from contact "Lily" waiting to be received.

[0110] When terminal 100 determines that an application layer message is a download result based on the message type indication field in the received application layer message, terminal 100 can display a receiving prompt message. This receiving prompt message can be used to notify the user that a short message sent to terminal 100 by a contact indicated by the identifier of another terminal in the download result has been received. For example, the download result includes an identifier "13xxxxxxxx9" and the corresponding short message content. If the identifier indicates the contact "Lily", then the receiving prompt message can notify the user that a message has been received from the contact "Lily". In some embodiments, terminal 100 can display the short message content in the download result in response to the user's input regarding the receiving prompt message. Optionally, the receiving prompt message of terminal 100 may also include the number of short messages sent by the contact. Optionally, terminal 100 can directly display the contact name and the content of the short message sent by that contact.

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

[0112] The following is a flowchart illustrating a letter request process in a BeiDou communication system, as provided in an embodiment of this application.

[0113] For example, such as Figure 4 As shown, the method includes:

[0114] S401, Terminal 100 reports its presence on the BeiDou network.

[0115] When terminal 100 enters the BeiDou network, it can report its entry to cellular network device 400. For example, when leaving the cellular network (i.e., when no cellular network signal is detected), terminal 100 can proactively send a reporting message to BeiDou network device 200 to indicate that it has entered the BeiDou network. Upon receiving this reporting message, BeiDou network device 200 can notify cellular network device 400 that terminal 100 is camped on the BeiDou network. As another example, if cellular network device 400 does not detect any interactive signaling sent by terminal 100 within a preset time (e.g., 1 minute), it can confirm that terminal 100 is under the BeiDou network. Yet another example, upon receiving input from a user to send a BeiDou short message to BeiDou network device 200, terminal 100 can respond to this input by sending a BeiDou short message to BeiDou network device 200. Upon receiving this BeiDou short message, BeiDou network device 200 can confirm that terminal 100 is under the BeiDou network and notify cellular network device 400 that terminal 100 is camped on the BeiDou network. For example, after receiving input from a user to enable the BeiDou communication function (e.g., input from the user to the BeiDou communication function control), terminal 100 can, in response to this input, send a reporting message to BeiDou network device 200 to instruct terminal 100 to enter the BeiDou network. Upon receiving this reporting message, BeiDou network device 200 can notify cellular network device 400 that terminal 100 is camped on the BeiDou network. The above illustrates various possible implementations of terminal 100 reporting its camping on the BeiDou network, and is not limited to the examples described above. Terminal 100 can also report its camping on the BeiDou network through other methods.

[0116] S402, Terminal 300 sends the first short message to Short Message Center 25.

[0117] Terminal 300 can receive input from a user indicating that they want to send a short message to a user of terminal 100, and in response to this input, send the first short message to the short message center 25. The first short message includes an identifier of terminal 100 (e.g., the user ID of terminal 100), which can be used by the short message center 25 to identify terminal 100.

[0118] S403, the short message center 25 queries the Home Location Register / Home Subscriber Server 28 for the network where terminal 100 is located.

[0119] After receiving the first short message sent to terminal 100, the short message center 25 can send query information to the Home Location Register / Home Subscriber Server 28. The query information includes the identifier of terminal 100 and can be used to query the network where terminal 100 is located.

[0120] S404, Home Location Register / Home Subscriber Server 28 reports to the Short Message Service Center that Terminal 100 is residing in the BeiDou network.

[0121] The Home Location Register / Home Subscriber Server 28 stores information such as the network where the terminal with activated cellular network service is registered. After receiving a query from the Short Message Service Center 25, the Home Location Register / Home Subscriber Server 28 can send the terminal 100's network registration information (e.g., registered on a cellular network, registered on a BeiDou network, etc.) to the Short Message Service Center 25 based on the stored terminal 100's network registration information.

[0122] Here, the Home Location Register / Home Subscriber Server 28 sends a notification to the Short Message Service Center 25 that Terminal 100 is residing in the BeiDou network.

[0123] S405, the short message center 25 sends a BeiDou prompt message to the terminal 300.

[0124] When the short message center 25 determines that the receiving device terminal 100 of the first short message is under the BeiDou network, it can send a BeiDou prompt message to the terminal 300. The BeiDou prompt message can be used to remind the user of the terminal 300 that the first short message is a satellite message.

[0125] S406, Terminal 300 sends a confirmation message to Short Message Center 25.

[0126] After receiving a BeiDou notification, terminal 300 can display the notification. Terminal 300 can display the notification in text, image, or voice format. For example, the BeiDou notification displayed by terminal 300 could be a text message: "The recipient of your short message is on the BeiDou network. Do you confirm sending this satellite message?". When displaying the BeiDou notification, terminal 300 can also display a confirmation control and a cancellation control. The confirmation control can trigger terminal 300 to send a confirmation message to short message center 25, instructing short message center 25 to send the first short message to terminal 100. The cancellation control can trigger terminal 300 to send a cancellation message to short message center 25, instructing short message center 25 to cancel sending the first short message. The following description focuses on the scenario where terminal 300 sends a confirmation message to short message center 25.

[0127] S407, Short Message Center 25 sends the first short message to Beidou Network Equipment 200.

[0128] After receiving the confirmation message, the short message center 25 can send a first short message to the BeiDou network device 200. The BeiDou network device 200 can then store the first short message.

[0129] Optionally, the short message center 25 may choose not to send the aforementioned BeiDou notification information to the terminal 300, but instead directly send the first short message to the BeiDou network device 200.

[0130] S408, Terminal 100 sends a message request to Beidou network device 200.

[0131] Terminal 100 can send a message request to BeiDou network device 200 in response to receiving input from a user indicating that they want to download BeiDou SMS messages. Alternatively, terminal 100 can send message requests to BeiDou network device 200 at preset intervals (e.g., 30 minutes). For example, the user's input to download BeiDou SMS messages can be input to the function controls provided by terminal 100 for receiving BeiDou SMS messages, or a voice command instructing terminal 100 to download BeiDou SMS messages, etc.

[0132] S409, Beidou network equipment 200 sends the first Beidou short message (including the message content of the first short message) to terminal 100.

[0133] After receiving a message request from terminal 100, BeiDou network device 200 can generate a first BeiDou short message based on the first short message. This first BeiDou short message includes the message content input by the user at terminal 300, the identifier of terminal 300, and the identifier of terminal 100. BeiDou network device 200 can use the message content of the first short message as raw data to obtain the first BeiDou short message; for details, please refer to the above description. Figure 3A The embodiments described herein will not be repeated here.

[0134] It is understandable that when terminal 100 sends an overview request to Beidou network device 200, Beidou network device 200 can obtain the query results based on the stored short messages sent to terminal 100 and send them to terminal 100.

[0135] In one possible implementation, the Short Message Service (SMS) center 25 can store short messages (e.g., the first short message) sent to terminals under the BeiDou network. When the BeiDou network device 200 receives a message request from the terminal 100, it can retrieve the short message from the terminal 100 from the SMS center 25 and send it to the terminal 100. This saves storage space for the BeiDou network device 200. It is understood that when the terminal 100 sends an overview request to the BeiDou network device 200, the BeiDou network device 200 can obtain the identifier and quantity information of the short messages sent to the terminal 100 from the SMS center 25, obtain the query results, and send them to the terminal 100.

[0136] Understandably, after receiving the first BeiDou short message, terminal 100 can display a receiving notification message, which can be used to inform the user that short messages have been sent to terminal 100 from other terminals. In some embodiments, terminal 100 can respond to the user's input regarding the receiving notification message and display the content of the short message in the download results. Optionally, the receiving notification message of terminal 100 may also include the number of short messages sent by the contact. Optionally, terminal 100 can directly display the contact's name and the content of the short message sent by that contact.

[0137] It should be noted that "first Beidou short message" is just a metaphor. After receiving a message request, Beidou network device 200 can encapsulate the message content of short messages sent by other terminals to terminal 100 into Beidou short messages and send them to terminal 100. There is no limit to the number of Beidou short messages.

[0138] In this way, terminal 100 under the BeiDou network can receive short messages sent by other terminals. However, terminal 100 downloads all other short messages sent by all other terminals through email requests. For some unimportant short messages (such as advertising text messages, etc.), downloading these unimportant short messages not only occupies the transmission air interface resources of the BeiDou communication system, but also consumes the terminal 100's power.

[0139] This application provides a whitelist control method in a BeiDou communication system. A whitelist can be configured in terminal 100, including the identifiers of N terminals associated with terminal 100 and their sequence numbers in the whitelist. The identifiers of the N terminals can be the user IDs (e.g., mobile phone numbers) of each of the N terminals. The BeiDou network device 200 (e.g., the BeiDou short message fusion communication platform 24) can store the whitelist configured in terminal 100. When BeiDou network device 200 receives a message request from terminal 100, it can determine the short messages sent by terminals in the whitelist based on the stored whitelist of terminal 100, and send the short messages sent by terminals in the whitelist to terminal 100. In this way, terminal 100 can only receive short messages sent by terminals in the whitelist. It is understood that after receiving a summary request from terminal 100, BeiDou network device 200 can send a query result to terminal 100, which includes information on the number of short messages sent to terminal 100 by terminals in the whitelist. Optionally, the query results may also include information on the number of short messages sent from terminals not on the whitelist to terminal 100.

[0140] The following is a flowchart illustrating a whitelist control method in a BeiDou communication system provided in an embodiment of this application.

[0141] For example, such as Figure 5 As shown, the method includes:

[0142] S501, Terminal 100 reports its presence on the BeiDou network.

[0143] When terminal 100 enters the BeiDou network, it can report its entry into the BeiDou network to cellular network device 400 (e.g., Home Location Register / Home Subscriber Server 28).

[0144] S502, Terminal 300 sends the first short message to Short Message Center 25.

[0145] Terminal 300 can receive input from a user indicating that they want to send a short message to a user of terminal 100, and in response to this input, send the first short message to the short message center 25. The first short message includes an identifier of terminal 100 (e.g., the user ID of terminal 100), which can be used by the short message center 25 to identify terminal 100.

[0146] It should be noted that the first short message also includes the identifier of terminal 300, i.e., the user ID.

[0147] S503, the short message center 25 queries the Home Location Register / Home Subscriber Server 28 for the network where terminal 100 is based.

[0148] S504, Home Location Register / Home Subscriber Server 28 reports to Short Message Service 25 that Terminal 100 is residing in the BeiDou network.

[0149] S505, the short message center 25 sends a Beidou prompt message to the terminal 300.

[0150] S506, Terminal 300 sends a confirmation message to Short Message Center 25.

[0151] S507, the short message center 25 sends the first short message to the Beidou network device 200.

[0152] After receiving the confirmation message, the short message center 25 can send a first short message to the BeiDou network device 200. The BeiDou network device 200 can then store the first short message.

[0153] Optionally, the short message center 25 may choose not to send the aforementioned BeiDou notification information to the terminal 300, but instead directly send the first short message to the BeiDou network device 200.

[0154] S508, Terminal 100 sends a message request to Beidou network device 200.

[0155] Terminal 100 can send a message request to BeiDou network device 200 in response to a user's input to download BeiDou SMS. Alternatively, terminal 100 can send message requests to BeiDou network device 200 at preset intervals (e.g., 30 minutes).

[0156] For a detailed description of steps S501-S508, please refer to the above. Figure 4 The embodiments shown are not described in detail here.

[0157] S509, Beidou network equipment 200 determines whether the whitelist of terminal 100 includes the user ID of terminal 300.

[0158] After receiving the email request from the terminal 100, the Beidou network device 200 can determine whether the whitelist includes the user ID of the terminal 300. If the whitelist includes the user ID of the terminal 300, the Beidou network device 200 can execute step S510; if the whitelist does not include the user ID of the terminal 300, the Beidou network device 200 can execute step S511.

[0159] It should be noted that the terminal 300 described here is only an example. After receiving the message request, the Beidou network device 200 will determine whether all other short messages sent to the terminal 100 are short messages sent by terminals in the whitelist, and will send all short messages sent by terminals in the whitelist to the terminal 100.

[0160] S510, Beidou network equipment 200 sends the first Beidou short message (including the message content of the first short message) to terminal 100.

[0161] After receiving a message request from terminal 100, BeiDou network device 200 can generate a first BeiDou short message based on the first short message. This first BeiDou short message includes the message content input by the user at terminal 300, the identifier of terminal 300, and the identifier of terminal 100. BeiDou network device 200 can use the message content of the first short message as raw data to obtain the first BeiDou short message; for details, please refer to the above description. Figure 3A The embodiments described herein will not be repeated here.

[0162] S511, Beidou network equipment 200 sends a second Beidou short message to terminal 100.

[0163] The BeiDou network device 200 determines that the ID number of terminal 300 is not included in the whitelist, and the second BeiDou short message generated by the BeiDou network device 200 does not include the first short message sent by terminal 300. However, if the BeiDou network device 200 also includes short messages sent to terminal 100 by terminals on the whitelist, the second BeiDou short message may include the message content of those short messages. If the BeiDou network device does not include short messages sent to terminal 100 by terminals on the whitelist, the second BeiDou short message can be used to indicate that terminal 100 has no available BeiDou short messages to receive.

[0164] Optionally, after receiving a second BeiDou short message indicating that there are no BeiDou short messages to receive, the terminal 100 may display a no-message message, which can be used to inform the user that there are no short messages sent by other terminals.

[0165] In one possible implementation, the BeiDou network device 200 only stores short messages sent by whitelisted users.

[0166] In some embodiments, after receiving a short message from another terminal sent to a terminal (e.g., terminal 100) under the BeiDou network, the short message center 25 can forward it to the BeiDou network device 200. The BeiDou network device 200 can determine a whitelist of recipients (e.g., terminal 100) based on the recipient identifier in the short message and store short messages sent by terminals indicated by the whitelist. The BeiDou network device 200 can reply with a confirmation message, which can be used to indicate the stored short message. The short message center 25 can delete the short message indicated by the confirmation message.

[0167] In other embodiments, the short message center 25 stores whitelists set by each terminal. The short message center 25 can determine the whitelist of recipients (e.g., terminal 100) based on the recipient identifier in the short message, and send short messages sent by terminals in the whitelist to the BeiDou network device 200.

[0168] The following section introduces examples of whitelists provided in the embodiments of this application.

[0169] In one possible implementation, the whitelist contains the identifiers of N target terminals, and the length of the whitelist bitmap can be N bits. For example, if the whitelist contains the identifiers of 10 target terminals, 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. 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., ...). Figure 1The present application embodiment does not limit the scope of the SMS center 25 shown in the figure.

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

[0171] Table 1

[0172]

[0173] As shown in Table 1, 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 embodiments of this application do not limit the identifiers and serial numbers of the specific terminals in the whitelist.

[0174] In one possible implementation, terminal 100 can set / update the whitelist through the cellular network service operator. For example, terminal 100 can set / update the whitelist in the following way:

[0175] Method 1: Terminal 100 can set / update the whitelist via SMS.

[0176] Specifically, terminal 100 can receive input from a user via SMS to adjust the whitelist, and in response to this input, sends an SMS in a specified format to the operator server providing BeiDou communication services (referred to as the BeiDou operation server). The BeiDou operation server can store the adjusted whitelist and send it to BeiDou network equipment 200.

[0177] Optionally, the BeiDou operation server can also send the adjusted whitelist to terminal 100, and terminal 100 stores the adjusted whitelist.

[0178] In some embodiments, the BeiDou operation server can be the aforementioned Home Location Register / Home Subscriber Server 28 or Short Message Center 25.

[0179] For example, such as Figure 6A As shown, terminal 100 displays a desktop 601. Desktop 601 may include multiple application icons, such as an information application icon 602, a dialer application icon 603, and a BeiDou settings application icon 604, etc. The information application icon 602 can be used to trigger the display of the information application interface (e.g., below). Figure 6B The information application interface 610 shown. The dialer application icon 603 can be used to trigger the display of the dialer application interface (e.g., below). Figure 7A The dialing application interface 701 shown is shown. The BeiDou settings application icon 604 can be used to trigger the display of the BeiDou settings application interface (e.g., below). Figure 8AThe BeiDou settings application interface shown is 801.

[0180] Terminal 100 receives input from the user regarding the information application icon 602 (e.g., a click), and in response to this input, terminal 100 can display, as shown below. Figure 6B The information application interface 610 shown is shown.

[0181] like Figure 6B As shown, the information application interface 610 may include a new control 611, which can be used to trigger the terminal 100 to display a contact selection interface (e.g., below). Figure 6C The contact selection interface 620 shown. The information application interface 610 can also display historical contact entries, which can display information about historical contacts and their recent message records. Historical contact entries can also be used to trigger the terminal 100 to display the email editing interface for that historical contact.

[0182] Terminal 100 receives user input (e.g., a click) for the newly created control 611. In response to this input, terminal 100 can display, as shown below: Figure 6C The contact selection interface 620 shown is a contact display area 621. The contact display area 621 can display multiple contact icons, such as contact icon 621A. These contact icons can be used to trigger the display of the information editing interface for the contact corresponding to that icon (e.g., below). Figure 6D The information editing interface 630 shown is shown. Among them, the contact icon 621A corresponds to the operator that provides Beidou communication services (e.g., China Mobile, China Unicom, China Telecom).

[0183] Terminal 100 can receive input from the user on the contact icon 621A (e.g., clicking), and in response to the input, terminal 100 can display the information editing interface 630.

[0184] like Figure 6D As shown, the information editing interface 630 may include, but is not limited to, an editing bar 631 and a sending control 632. The editing bar 631 can be used to display the content of a text message entered by the user. The sending control 632 can be used to trigger the terminal 100 to send the text message content displayed in the editing bar 631 to the BeiDou operation server. The information editing interface 630 may also display a keyboard display area 633, which can be used to input text message content. Here, the terminal 100 can receive user input to the keyboard display area 633. Figure 6DThe edit bar 631 shown displays user-inputted display instructions (e.g., "whitelist"). These instructions can be used to trigger the BeiDou operation server to return whitelist information to terminal 100.

[0185] Terminal 100 can receive user input (e.g., a click) to the send control 632, and in response to this input, terminal 100 can display, for example... Figure 6E The information box 641 shown. The information box 641 can be used to display the content sent by the user in the edit bar 631.

[0186] After receiving the instruction information sent by terminal 100, the BeiDou operator server can send the whitelist information of terminal 100 to terminal 100 based on the instruction information. Terminal 100 can then display, for example... Figure 6E The information box 642 shown above displays the whitelist information for terminal 100. The whitelist includes 10 whitelist slots, of which whitelist slots 1 through 9 already have corresponding terminal identifiers set, while whitelist slot 10 does not yet have a corresponding terminal identifier set. Optionally, the terminal identifier can be represented by the name of the user corresponding to the terminal identifier in terminal 100; for example, terminal identifier 1 could be represented by "Dad".

[0187] The BeiDou operator server can also send adjustment prompts to terminal 100. These prompts can be used to instruct users of terminal 100 to adjust the whitelist. The adjustment prompts may include, but are not limited to, add, delete, and replace commands. In other words, the prompts can instruct users to add / update terminal identifiers in the whitelist using the add command; delete terminal identifiers from the whitelist using the delete command; and replace the serial numbers of two terminal identifiers in the whitelist using the replace command.

[0188] In some embodiments, the information box 642 may also display adjustment prompts. For example, the terminal 100 can add / update identifiers in the whitelist via SMS in the format '1 + whitelist number + mobile number to be added', delete identifiers in the whitelist via SMS in the format '2 + whitelist number', and replace the serial numbers of two whitelist identifiers via SMS in the format '3 + previous serial number + next serial number'. For example, the adjustment prompts could be: "Add / replace whitelist: Please send '1 + whitelist number + mobile number to be added'; Delete whitelist: Please send; Adjust whitelist order: Please send '3 + previous serial number + next serial number'."

[0189] Terminal 100 can receive user input on the keyboard display area 633 and display an add command in the edit bar 651. The add command can instruct the BeiDou operation server to adjust the terminal identifier of a specified serial number in the whitelist of terminal 100. Here, the add command can be: "1+9+13xxxxxxxx9". This add command can be used to adjust the terminal corresponding to whitelist slot number 9.

[0190] Terminal 100 can receive user requests for... Figure 6F The input to the sending control 632, as shown, responds to the input and sends the add command displayed in the edit bar 651 to the Beidou operation server. The terminal 100 can also display... Figure 6G The information box 661 shown contains an add command. The information box 661 can be used to prompt the user terminal 100 that it has sent the add command to the Beidou operation server.

[0191] After receiving an add command, the BeiDou operation server can update the whitelist of terminal 100 based on the serial number and terminal identifier in the add command. After adjusting the whitelist of terminal 100, the BeiDou operation server can also send an adjustment notification message to terminal 100. This notification message can be used to inform the user that the whitelist adjustment of terminal 100 is complete. The BeiDou operation server can also send the adjusted whitelist of terminal 100 to BeiDou network device 200.

[0192] Terminal 100 can display the adjustment prompt information, such as... Figure 6G As shown in the information box 662, information box 662 can display adjustment prompt information received by terminal 100. For example, the adjustment prompt information can be "Whitelist configured successfully".

[0193] In some embodiments, after receiving a deletion instruction, the BeiDou operation server can delete the terminal identifier corresponding to the sequence number in the deletion instruction from the whitelist of terminal 100. For example, after receiving a deletion instruction of "2+9", the BeiDou operation server can delete the terminal identifier corresponding to whitelist number 9 in the whitelist of terminal 100. Optionally, when terminal 100 queries the whitelist information from the BeiDou operation server again, the identifier corresponding to whitelist number 9 in the whitelist information received by terminal 100 will be "unassigned".

[0194] In other embodiments, after receiving a replacement instruction, the BeiDou operation server can change the terminal identifiers corresponding to two serial numbers in the whitelist of terminal 100 based on the serial numbers in the replacement instruction. For example, after receiving a replacement instruction of "3+2+9", the BeiDou operation server can swap the terminal identifiers corresponding to whitelist number 2 and whitelist number 9 in the whitelist of terminal 100. That is, after receiving the replacement instruction of "3+2+9", the BeiDou operation server modifies the terminal identifier corresponding to whitelist number 2 to "13xxxxxxxx8" and modifies the terminal identifier corresponding to whitelist number 9 to "13xxxxxxxx1".

[0195] In one possible implementation, when the terminal identifier in the addition instruction received by the BeiDou operation server already exists in the whitelist of terminal 100, the BeiDou operation server can send a duplicate prompt message to terminal 100. This duplicate prompt message can remind the user that the terminal identifier already exists and cannot be added again.

[0196] Method 2: Terminal 100 can set / update the whitelist via telephone.

[0197] For example, when establishing a call connection with the BeiDou operation server, terminal 100 can prompt the user to input corresponding commands to adjust the whitelist of terminal 100 through voice prompts. For instance, terminal 100 can add / update identifiers in the whitelist through add commands, delete identifiers in the whitelist through delete commands, and swap identifiers corresponding to two serial numbers in the whitelist through replace commands.

[0198] For example, terminal 100 can receive user requests for... Figure 6A The input of the dialer application icon 603 shown above, in response to the input, displays as follows: Figure 7A The dialing application interface 701 shown is included. The dialing application interface 701 may include a dial pad 702, which can be used to receive user input and trigger the terminal 100 to display the contact number entered by the user via the dial pad 702. The dialing application interface 701 may also include a dial control 703, which can be used to send a call request to the electronic device (e.g., a BeiDou operation server) corresponding to the specified contact number. The dialing application interface 701 may also display call records between the terminal 100 and other terminals.

[0199] Terminal 100 can receive user requests for... Figure 7A After inputting into the dial pad 702 as shown, the following will be displayed: Figure 7BThe contact information 711 shown may include, but is not limited to, a contact name and a contact number. Here, the contact information 711 includes the customer service number of the operator providing BeiDou communication services (e.g., “1xxxx”) and the service name (e.g., “BeiDou Communication”).

[0200] Terminal 100 can receive user requests for... Figure 7B The input to the dial control 703 shown triggers a call request to the BeiDou operation server. Upon receiving the call request from terminal 100, the BeiDou operation server can grant the request and establish a call connection with terminal 100.

[0201] After the terminal 100 establishes a communication connection with the Beidou operation server, it can display the following: Figure 7C The call interface 720 is shown. The call interface 720 may display a dial pad control 721. The dial pad control 721 can be used to trigger the terminal 100 to display the dial pad. Optionally, the call interface 720 may also display the real-time call time between the terminal 100 and the BeiDou operation server.

[0202] After establishing a communication connection between terminal 100 and the BeiDou operation server, the BeiDou operation server can send a first voice prompt message to terminal 100. This first voice prompt message can be used to inform the user about the services provided by the BeiDou operation server. Upon receiving the first voice prompt message, terminal 100 can broadcast it via voice. For example, the first voice prompt message may include: "Press '9' to set the whitelist."

[0203] Terminal 100 can receive user input to the dial pad control 721, and in response to the input, display as shown below. Figure 7D The dial pad 731 is shown. Terminal 100 can receive user input for key "9" on the dial pad 731, and in response to this input, display as shown... Figure 7E The instruction information 741 shown is the content entered by the user via the dial pad 731. Terminal 100 can also send instruction information 741 to the BeiDou operation server.

[0204] Upon receiving instruction information 741, the BeiDou operation server can send a second voice command to terminal 100. This second voice command can prompt the user to select a method for adjusting the whitelist. For example, the second voice command could be: "Press '1' to add or update the whitelist, press '2' to delete the whitelist, and press '3' to change the whitelist order." When the BeiDou operation server receives an instruction from terminal 100 to add or update the whitelist, it can send a voice command to terminal 100 explaining how to add or update terminal identifiers in the whitelist (i.e., a voice command with the format of the add command). When the BeiDou operation server receives an instruction from terminal 100 to delete a terminal identifier from the whitelist, it can send a voice command to terminal 100 explaining how to delete the whitelist (i.e., a voice command with the format of the delete command). When the BeiDou operation server receives an instruction from terminal 100 to replace the whitelist, it can send a voice command to terminal 100 explaining how to replace the terminal identifiers in the whitelist (i.e., a voice command with the format of the replace command).

[0205] Optionally, the second voice command may also include detailed information about the whitelist of terminal 100, such as the serial number in the whitelist and the corresponding user ID of the terminal. Optionally, the second voice command may also include all the entries in the whitelist of terminal 100; for example, the whitelist entries from serial number 01 to serial number 10 can be changed. Terminal 100 can broadcast this second voice prompt information via voice.

[0206] Terminal 100 can receive user input for key "1" on dial pad 731, and in response to the input, display as shown below. Figure 7F The instruction information 751 is shown. Instruction information 751 includes the content entered by the user via dial keypad 731 after the terminal 100 broadcasts the second voice command, namely, "1". The terminal 100 can also send instruction information 751 to the BeiDou operation server.

[0207] After receiving instruction information 751, the BeiDou operation server can send a third voice command to terminal 100. This third voice command can prompt the user on how to add or update the whitelist (the third voice command includes the format for adding instructions). For example, the third voice command could be: "When adding or updating the whitelist, please first enter the whitelist number to be adjusted, then enter the set mobile phone number, and press the '#' key after entering the information."

[0208] Terminal 100 can receive user input on the dial pad 731 and, in response to the input, display as shown below. Figure 7GThe instruction information 761 is shown. Instruction information 761 includes the content entered by the user via dial pad 731 after the terminal 100 broadcasts the third voice command, namely, "10xxxxxxxx9#". The terminal 100 can also send instruction information 761 to the BeiDou operation server. Instruction information 761 can be used to instruct the BeiDou operation server to add or update terminal identifiers with specified serial numbers in the whitelist of the terminal 100. For example, when instruction information 751 is "101xxxxxxxx9#", the BeiDou operation server can modify the 10th identifier in the whitelist to "1xxxxxxxx9".

[0209] Optionally, after the BeiDou operation server adjusts the whitelist of terminal 100, it can also send a fourth voice prompt message to terminal 100. The fourth voice prompt message can be used to notify the user that the whitelist adjustment is complete.

[0210] In some embodiments, when a call connection is established with the BeiDou operation server, the terminal 100 can send voice commands input by the user to the BeiDou operation server. The BeiDou operation server can then adjust the whitelist of the terminal 100 based on the voice commands. For example, the voice command could be: "Add number 13xxxxxxxx9 to the whitelist."

[0211] Understandably, when the BeiDou operation server receives an instruction from terminal 100 to delete a terminal identifier from the whitelist, it can send a voice command to terminal 100 explaining how to delete the identifier. Terminal 100 can then delete the terminal identifier with the specified serial number using the deletion command. Similarly, when the BeiDou operation server receives an instruction from terminal 100 to replace a terminal identifier in the whitelist, it can send a voice command to terminal 100 explaining how to replace the terminal identifiers in the whitelist. Terminal 100 can then replace the terminal identifiers corresponding to two specified serial numbers using the replacement command.

[0212] In one possible implementation, when the terminal identifier in the addition instruction received by the BeiDou operation server already exists in the whitelist of terminal 100, the BeiDou operation server can send a duplicate notification message to terminal 100. This message informs the user that the terminal identifier already exists and cannot be added again. After receiving the duplicate notification message, terminal 100 can verbally announce the message.

[0213] Method 3: Terminal 100 can set / update the whitelist through the application provided by the operator that provides Beidou communication services.

[0214] For example, terminal 100 can receive user requests for... Figure 6A The input of the BeiDou settings application icon 604, as shown, responds to the input and displays as follows: Figure 8A The BeiDou settings application interface shown is 801.

[0215] like Figure 8A As shown, the BeiDou settings application interface 801 includes multiple functional controls provided by the BeiDou settings application (e.g., whitelist setting control 802, bill query control, etc.). These functional controls can be used to trigger the terminal 100 to send the corresponding instruction to the BeiDou operation server. For example, the bill query control can trigger the terminal 100 to query the terminal 100's bill information from the BeiDou operation server, and the terminal 100 can also receive and display the bill information. The whitelist setting control 802 can be used to trigger the terminal 100 to display the whitelist setting interface, which can be used to adjust the whitelist.

[0216] Terminal 100 can receive user input regarding the whitelist setting control 802, and in response to this input, display as shown below. Figure 8B The whitelist setting interface 810 is shown. The whitelist setting interface 810 may include a whitelist display area. The whitelist display area may display one or more (e.g., 10) whitelist entries. Each whitelist entry may include its serial number and the user ID of the terminal set in the whitelist. It should be noted that when no terminal identifier is set in a whitelist entry, only the serial number in the whitelist is displayed. For example, whitelist entry 812 may include serial number 812A and a terminal identifier field 812B. Serial number 812A indicates that the terminal identifier is the 3rd in the whitelist. The terminal identifier field 812B displays the terminal identifier, indicating the corresponding terminal. Whitelist entry 813 may include serial number 813A and a terminal identifier field 813B. Serial number 813A indicates that the terminal identifier is the 10th in the whitelist. The terminal identifier field 813B does not display a terminal identifier, meaning that the whitelist entry has not yet been configured with a corresponding terminal. Optionally, the whitelist setting interface 810 may also include a save control 815, which can be used to save the adjusted whitelist of the terminal 100 and to send the adjusted whitelist of the terminal 100 to the Beidou operation server.

[0217] Terminal 100 can receive user input for the terminal identification bar 813B and display the keyboard display area. Terminal 100 can receive the terminal identifier typed by the user through the keyboard display area and display the user-input terminal identifier in the terminal identification bar 813B. For example, the terminal identification bar 813B can display something like... Figure 8C The terminal identifier shown is "13xxxxxxxx9". Terminal 100 can respond to user requests... Figure 8C The input of the save control 815 shown will send the adjusted whitelist of terminal 100 to the Beidou operation server and save the adjusted whitelist.

[0218] In one possible implementation, after receiving user input for the save control 815, terminal 100 can detect whether the whitelist identifiers in the adjusted whitelist are duplicates. If terminal 100 detects that the adjusted whitelist includes a duplicate terminal identifier, terminal 100 can display a duplicate prompt message, which can indicate to the user that the terminal identifier already exists and cannot be added again. If terminal 100 detects that the adjusted whitelist does not contain duplicate terminal identifiers, terminal 100 can send the adjusted whitelist to the BeiDou operation server and save the adjusted whitelist.

[0219] Of course, Terminal 100 can also set / update the whitelist in other ways (for example, users can activate Beidou communication services and set up a whitelist at the operator's service center). It should be noted that the above methods for setting / updating the whitelist are only examples and should not constitute specific limitations.

[0220] This application provides another whitelist control method in a BeiDou communication system. A whitelist can be configured in terminal 100, including the identifiers of N terminals associated with terminal 100 and their sequence numbers in the whitelist. The BeiDou network device 200 (e.g., the BeiDou short message fusion communication platform 24) can store the whitelist configured in terminal 100. BeiDou network device 200 can receive message requests sent by terminal 100, which may include a sender ID field (e.g., a whitelist bitmap field, a target terminal ID field). BeiDou network device 200 can determine the short message sent by the specified terminal based on the stored whitelist of terminal 100 and the sender ID field in the message request, and send the short message sent by the specified terminal to terminal 100. In this way, terminal 100 can download the short message from the specified terminal. Understandably, the overview request may also include a sender ID field. The Beidou network device 200 can send the query result to the terminal 100, and the query result includes the number of short messages of the terminal indicated by the sender ID field.

[0221] The following is a structural example of an inbound application layer message provided by an embodiment of this application.

[0222] Table 2

[0223]

[0224] As shown in Table 2 above, the inbound application layer message for a letter request or overview request may include, but is not limited to, a service type field, an encryption indication field, a compression indication field, a sender ID field, a message ID field, etc. It is understood that the specific fields and their order in the overview request / letter request in this embodiment are merely examples, and this application does not limit them. The specific descriptions of each field in the inbound application message shown in Table 2 are illustrated in Table 3 below. Table 3 exemplarily shows the length and specific description of each field in Table 2.

[0225] Table 3

[0226]

[0227] As shown in Table 3 above, the "Service Type" field indicates whether the service type of the inbound application layer message is SMS download or mailbox overview query. SMS download includes downloading SMS messages from specified terminals within the whitelist, downloading SMS messages from all terminals, and downloading SMS messages from specified terminals not within the whitelist. Mailbox overview query includes querying the number of SMS messages from specified terminals within the whitelist, querying the number of SMS messages from all terminals, and querying the number of SMS messages from specified terminals not within the whitelist. The identifiers of terminals within the whitelist are present in the whitelist, while the identifiers of terminals not within the whitelist are not present in the whitelist.

[0228] For example, the length of the service type field can be 3 bits. When the service type field is 000, it indicates that the service type of the inbound application layer message is a general data message. It should be noted that when the service type field indicates that the service type of the inbound application layer message is a general data message, the fields of the inbound application layer message are different from those of the aforementioned letter request / summary request inbound application layer message; for example, it includes a text message with user input but does not include a message ID field.

[0229] When the service type field is 001, it indicates that the service type of the inbound application layer message is mailbox overview query service, and the inbound application layer message only queries the number of short messages sent to terminal 100 by terminals within the whitelist. When the service type field is 010, it indicates that the service type of the inbound application layer message is mailbox overview query service within the mailbox service, specifically querying the number of short messages sent to terminal 100 by all terminals (including terminals within the whitelist and terminals outside the whitelist). When the service type field is 011, it indicates that the service type of the inbound application layer message is mailbox overview query service, specifically querying the number of short messages sent to terminal 100 by a single target terminal outside the whitelist.

[0230] When the service type field is 100, it indicates that the service type of the inbound application layer message is SMS message download service (also known as SMS download service), which specifically means downloading short messages sent to this terminal by terminals within the specified whitelist. When the service type field is 101, it indicates that the service type of the inbound application layer message is SMS message download service, which specifically means downloading short messages sent to this terminal user by all terminals (including terminals within the whitelist and those outside the whitelist). When the service type field is 110, it indicates that the service type of the inbound application layer message is SMS message download service, which specifically means downloading short messages sent to this terminal user by a single non-whitelisted user.

[0231] The value 111 in the "Business Type" field is a reserved field. The mailbox overview query service and the mail message download service can be collectively referred to as mailbox services.

[0232] In one possible implementation, the service types of inbound application layer messages include, but are not limited to, message download service and mailbox overview query service. Message download service includes downloading SMS messages from terminals within the whitelist, downloading SMS messages from all terminals within the whitelist, and downloading SMS messages from specified terminals not within the whitelist. Mailbox overview query service includes querying the number of SMS messages from specified terminals within the whitelist, querying the number of SMS messages from all terminals within the whitelist, and querying the number of SMS messages from specified terminals not within the whitelist. For example, when the service type field is 010, it indicates that the inbound application layer message is querying the number of SMS messages sent to terminal 100 by all terminals within the whitelist. When the service type field is 101, it indicates that the inbound application layer message is downloading SMS messages sent to terminal 100 by all terminals within the whitelist.

[0233] The encryption indicator field indicates whether the inbound application layer message is encrypted and the encryption algorithm used. The compression indicator field also indicates whether the inbound application layer message is encrypted and the encryption algorithm used. The message ID field indicates the most recently successfully received BeiDou short message by terminal 100. The message ID field can be 4 bits long.

[0234] The sender ID field can be used to indicate the identifier of the terminal that the terminal 100 wants to obtain, which sent the short message or the number of short messages to the terminal 100. If the terminal specified by the terminal 100 (also known as the target terminal) is in the whitelist configured by the terminal 100, then the sender ID field is a whitelist bitmap field, which indicates the whitelist sequence number of the target terminal. If the target terminal is not in the whitelist configured by the terminal 100, then the sender ID field is a target terminal identifier field, which includes the identifier of the target terminal (e.g., mobile phone number).

[0235] For example, taking the whitelist shown in Table 1 as an example, the whitelist in the inbound application layer message can be displayed in the form of a whitelist unit graph field, as shown in Table 4 or Table 5 below.

[0236] Table 4

[0237]

[0238] As shown in Table 4, the whitelist bitmap field can be 10 bits long, with each target terminal's sequence number occupying 1 bit. In one possible implementation, the sequence number of target terminal 1 in the whitelist can occupy the most significant bit (MSB), i.e., bit 9. Then, the sequence number of target terminal 10 in the whitelist can occupy the least significant bit (LSB), i.e., bit 0. The sequence number of target terminal 2 in the whitelist can occupy bit 8. And so on, the sequence number of target terminal 8 in the whitelist can occupy bit 2. The sequence number of target terminal 9 in the whitelist can occupy bit 1. For example, if a user wants to query the number of emails sent to terminal 100 by target terminal 1 in the whitelist, then the value of the whitelist bitmap entered by terminal 100 in the sender ID field could be "1000000000". It is understandable that when the Beidou network device 200 can determine the serial number of the target terminal based on the whitelist field, it can then identify the target terminal corresponding to the serial number from the whitelist of the stored terminal 100.

[0239] Table 5

[0240]

[0241] In some embodiments, as shown in Table 5, the sequence number of the target terminal with sequence number 10 in the whitelist can occupy the MSB (bit 9) of the 10-bit whitelist. Then, the sequence number of the target terminal with sequence number 1 in the whitelist can occupy the LSB (bit 0) of the 10-bit whitelist. The sequence number of the target terminal with sequence number 9 in the whitelist can occupy bit 8 of the 10-bit whitelist. The sequence number of the target terminal with sequence number 8 in the whitelist can occupy bit 7 of the 10-bit whitelist. And so on, the sequence number of the target terminal with sequence number 3 in the whitelist can occupy bit 2 of the 10-bit whitelist. The sequence number of the target terminal with sequence number 2 in the whitelist can occupy bit 1 of the 10-bit whitelist. 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 value of the whitelist bitmap entered by terminal 100 in the sender ID field can be "0000000001".

[0242] The target terminal identifier field can be used to indicate the identifier of a terminal that is not on the whitelist. The length of this target terminal identifier field can be 44 bits or 34 bits, without limitation. For example, when the identifier of the target terminal is a mobile phone number, if the target terminal's mobile phone number is "13xxxxxxxx9" and the target terminal is not on terminal 100's whitelist, then terminal 100 can encode the target terminal's mobile phone number "13xxxxxxxx9" into 44 bits of binary data and fill it into the target terminal identifier field. Alternatively, terminal 100 can also compress the target terminal's mobile phone number "13xxxxxxxx9" and encode it into 34 bits of binary data before filling it into the target terminal identifier field.

[0243] For example, when the value of the service type field is 000 or 100 as shown in Table 3 above, the sender ID field in the inbound application layer message is the whitelisted unit map field. When the value of the service type field is 010 or 101 as shown in Table 3 above, the sender ID field in the inbound application layer message is the whitelisted unit map field and the target terminal identifier field. When the value of the service type field is 011 or 110 as shown in Table 3 above, the sender ID field in the inbound application layer message is the target terminal identifier field.

[0244] In one possible implementation, when the inbound application layer message is for retrieving all short messages or the number of short messages sent to terminal 100 by other terminals, the inbound application layer message may not include the sender ID field. For example, if the value of the service type field is 010 or 101 as shown in Table 3 above, the inbound application layer message may not include the sender ID field.

[0245] It should be noted that the above-mentioned correspondence between the length of the business type field, its specific value, and the business is only an example. The correspondence between the length of the business type field, the business type, and the value of the business type field can also take other forms. For example, the length of the business type can be more or fewer bits. For another example, when the value of the business type field is 000, it can indicate that the business type of the application layer message is the short message service for downloading all terminals, etc. This application does not constitute a specific limitation in this regard.

[0246] Based on the aforementioned inbound application layer messages, in one possible implementation, terminal 100 can not only set / update the whitelist through the BeiDou operation server as described in Table 1 above, but also set / update the whitelist within the BeiDou network. Thus, terminal 100 can also update / set the whitelist within the BeiDou network. For example, terminal 100 can set / update the whitelist within the BeiDou network in the following ways:

[0247] Method 1: When the Beidou network device 200 receives a letter request from the terminal 100 to download SMS messages from a designated terminal that is not on the whitelist, or a request to query the overview of the number of SMS messages from a designated terminal that is not on the whitelist, it can add the identifier of the designated terminal to the whitelist.

[0248] Method 2: When the BeiDou network device 200 receives a BeiDou short message sent by the terminal 100 to a terminal under the cellular network that is not on the whitelist, it can add the identifier of the terminal under the cellular network to the whitelist.

[0249] It is understandable that terminal 100 can synchronize and adjust the stored whitelist with Beidou network equipment 200. Since the number of entries in the whitelist is limited, terminal 100 can, for example, replace terminals in the whitelist using the following methods.

[0250] (1) Beidou network equipment 200 can replace the terminal identifier with the first serial number.

[0251] Specifically, BeiDou network device 200 and terminal 100 can delete the terminal identifier with serial number 0 and move subsequent terminal identifiers forward. That is, they can write the terminal identifier with serial number 2 to serial number 1, then write the terminal identifier with serial number 3 to serial number 2, and so on. For example, when the whitelist of terminal 100 is the whitelist shown in Table 1, if terminal 100 sends a download request to BeiDou network device 200 to download a short message sent by target terminal 11, since terminal 11 is not included in the whitelist, terminal 100 and BeiDou network device 200 can delete the identifier of target terminal 1, move the identifiers of other target terminals forward, and then add the identifier of target terminal 11 to serial number 10.

[0252] (2) The Beidou network equipment 200 can replace the terminal identifier with the last serial number.

[0253] Specifically, BeiDou network device 200 and terminal 100 can delete the terminal identifier with serial number 10 and move the previous terminal identifiers to the right. That is, they can write the terminal identifier with serial number 9 into the position with serial number 10, then write the terminal identifier with serial number 8 into the position with serial number 9, and so on. For example, when the whitelist of terminal 100 is the whitelist shown in Table 1, if terminal 100 sends a download request to BeiDou network device 200 to download a short message sent by target terminal 11, since terminal 11 is not included in the whitelist, terminal 100 and BeiDou network device 200 can delete the identifier of target terminal 10, move the identifiers of other target terminals to the right, and then add the identifier of target terminal 11 to the position with serial number 1.

[0254] (3) The Beidou network device 200 can set the last N terminal identifiers in the whitelist to be replaceable, where N is a positive integer.

[0255] For example, BeiDou network device 200 and terminal 100 can be configured to replace the slots numbered 8 to 10 in the whitelist, while keeping the remaining slots unchanged. When adjusting the whitelist, BeiDou network device 200 and terminal 100 can adjust the terminal identifiers of signals 8 to 10 according to the embodiments described in (1) and (2) above. For example, when the whitelist of terminal 100 is the whitelist shown in Table 1, if terminal 100 sends a download request to BeiDou network device 200 for downloading a short message sent by target terminal 11, since terminal 11 is not included in the whitelist, when terminal 100 and BeiDou network device 200 replace the terminal identifier with the first number, terminal 100 and BeiDou network device 200 can delete the identifier of target terminal 8, move the identifiers of other target terminals forward, and then add the identifier of target terminal 11 to the slot 10.

[0256] It should be noted that the methods for setting / updating the whitelist are not limited to those described above. The BeiDou network device 200 and terminal 100 can also replace the identifier of the recently set target terminal, etc., and this application embodiment does not limit this. In one possible implementation, the whitelist set by terminal 100 includes emergency rescue numbers by default.

[0257] Next, based on the inbound application layer messages shown in Table 2 above, we will introduce a flowchart of another whitelist control method in the BeiDou communication system provided in this application embodiment.

[0258] For example, such as Figure 9 As shown, the method includes:

[0259] S901, Terminal 100 reports its presence on the BeiDou network.

[0260] When terminal 100 enters the BeiDou network, it can report its entry into the BeiDou network to cellular network device 400 (e.g., Home Location Register / Home Subscriber Server 28).

[0261] S902, terminal 300 sends the first short message to short message center 25.

[0262] Terminal 300 can receive input from a user indicating that they want to send a short message to a user of terminal 100, and in response to this input, send the first short message to the short message center 25. The first short message includes an identifier of terminal 100 (e.g., the user ID of terminal 100), which can be used by the short message center 25 to identify terminal 100.

[0263] It should be noted that the first short message also includes the identifier of terminal 300, i.e., the user ID.

[0264] S903, the short message center 25 queries the Home Location Register / Home Subscriber Server 28 for the network where terminal 100 is located.

[0265] S904, Home Location Register / Home Subscriber Server 28 reports to Short Message Service 25 that Terminal 100 is residing in the BeiDou network.

[0266] S905, the short message center 25 sends a Beidou prompt message to the terminal 300.

[0267] S906, Terminal 300 sends a confirmation message to Short Message Center 25.

[0268] S907, the short message center 25 sends the first short message to the Beidou network equipment 200.

[0269] After receiving the confirmation message, the short message center 25 can send a first short message to the BeiDou network device 200. Upon receiving the first short message, the BeiDou network device 200 can store it.

[0270] Optionally, the short message center 25 may choose not to send the aforementioned BeiDou notification information to the terminal 300, but instead directly send the first short message to the BeiDou network device 200.

[0271] For a detailed description of steps S901-S907, please refer to the above. Figure 4 The embodiments shown are not described in detail here.

[0272] S908, Terminal 100 sends a message request to Beidou network equipment 200 to download short messages from all terminals.

[0273] Terminal 100 can receive an input from a user requesting the download of BeiDou short messages from all terminals, and in response, send a message request to BeiDou network device 200. The service type field of this message request indicates that the service type is short message service for downloading all terminals.

[0274] S909, the BeiDou network device 200 sends the first BeiDou short message to the terminal 100. The first BeiDou short message includes the content of the first short message.

[0275] The BeiDou network device 200 stores short messages sent by all other terminals to terminals under the BeiDou network. When the BeiDou network device 200 receives a request from terminal 100 to download all short messages, it can send all the short messages sent by all other terminals to terminal 100 (including the first short message) to terminal 100. In other words, the BeiDou network device 200 can generate a first BeiDou short message based on the message content of the first short message and send the first BeiDou short message to terminal 100.

[0276] Understandably, when BeiDou network device 200 receives a message request from terminal 100 whose service type is to download a terminal specified in the whitelist, if terminal 300 is a terminal specified in the whitelist of terminal 100, BeiDou network device 200 can send the first short message to terminal 100; if terminal 300 is not a terminal specified in the whitelist of terminal 100 (i.e., terminal 300 is a terminal in the whitelist of terminal 100, but the whitelist unit map field in the message request does not indicate the serial number of terminal 300), BeiDou network device 200 can send the short message of the terminal specified in the whitelist of terminal 100 to terminal 100.

[0277] When the BeiDou network device 200 receives a message request from terminal 100 whose service type is a message request to download a terminal not specified in the whitelist, if the target terminal identifier field in the message request indicates the identifier of terminal 300, the BeiDou network device 200 can send the first short message to terminal 100.

[0278] In one possible implementation, the service type of the message request sent by terminal 100 includes downloading SMS messages from specified terminals within the whitelist, downloading SMS messages from all terminals within the whitelist, and downloading SMS messages from specified terminals not on the whitelist.

[0279] When BeiDou network device 200 receives a message request from terminal 100 requesting to download short messages from all terminals in the whitelist, it can send all short messages sent by terminals in the whitelist to terminal 100. For example, if terminal 100's whitelist includes the identifier (message ID) of terminal 300, BeiDou network device 200 can send a first short message to terminal 100. Specifically, BeiDou network device 200 can generate a first BeiDou short message based on the message content of the first short message and send the first BeiDou short message containing the message content of the first short message to terminal 100. As another example, if terminal 100's whitelist does not include the identifier (message ID) of terminal 300, and if BeiDou network device 200 also includes short messages sent to terminal 100 by terminals in the whitelist, BeiDou network device 200 can generate and send a second BeiDou short message to terminal 100, the second BeiDou short message not containing the message content of the first short message.

[0280] It is understandable that when the BeiDou network device 200 receives a message from terminal 100, the service type is either downloading SMS services from a specified terminal within the whitelist or downloading SMS services from a specified terminal not on the whitelist. For details, please refer to the above description. Figure 9 The embodiments shown are not described in detail here.

[0281] In one possible implementation, if the BeiDou network device 200 has not received any short messages from one or more terminals (whitelisted or unwhitelisted) specified in the message request before receiving the message request, the BeiDou network device 200 may send a first indication message to the terminal 100. This first indication message indicates that the BeiDou network device 200 has not stored any short messages from the one or more terminals specified in the message request. It is understood that the first indication message includes the identifier of the one or more terminals. Optionally, after receiving the first indication message, the terminal 100 may display a no-message notification message, which indicates to the user that there are no short messages from the terminals specified in the first indication message. Optionally, the BeiDou network device 200 may not reply to the terminal 100 with any message.

[0282] Similarly, the scenario where BeiDou network device 200 receives a summary request from terminal 100 can be found in the above description. Figure 9 The example of the letter request shown will not be described again here.

[0283] In one possible implementation, the BeiDou network device 200 only stores short messages sent by whitelisted users.

[0284] In some embodiments, after receiving a short message from another terminal to a terminal (e.g., terminal 100) under the BeiDou network, the short message center 25 can forward it to the BeiDou network device 200. The BeiDou network device 200 can determine a whitelist of recipients (e.g., terminal 100) based on the recipient identifier in the short message and store short messages sent by terminals indicated by the whitelist. Optionally, the BeiDou network device 200 can reply with a confirmation message to the short message center 25, which can be used to indicate a stored short message. The short message center 25 can delete the short message indicated by the confirmation message.

[0285] In other words, this application provides a whitelist control method in a BeiDou communication system. After receiving a first short message from a second terminal to a first terminal within the BeiDou network, the BeiDou network device can determine whether the first terminal's whitelist contains the identifier of the second terminal. If the BeiDou network device determines that the first terminal's whitelist contains the identifier of the second terminal, it stores the first short message. If the BeiDou network device determines that the first terminal's whitelist does not contain the identifier of the second terminal, it discards the first short message. In this way, the BeiDou network device can only receive and forward short messages sent by terminals in the whitelist, saving storage space and air interface transmission resources of the BeiDou communication system, and reducing the power consumption of the first terminal receiving short messages. The first terminal can be terminal 100, and the second terminal can be terminal 300.

[0286] Next, based on the inbound application layer messages shown in Table 2 above, we will introduce a flowchart of another whitelist control method in the BeiDou communication system provided in this application embodiment.

[0287] For example, such as Figure 10 As shown, the method includes:

[0288] S1001, Terminal 100 reports its presence on the BeiDou network.

[0289] When terminal 100 enters the BeiDou network, it can report its entry into the BeiDou network to cellular network device 400 (e.g., Home Location Register / Home Subscriber Server 28).

[0290] S1002, terminal 300 sends the first short message to short message center 25.

[0291] Terminal 300 can receive input from a user indicating that they want to send a short message to a user of terminal 100, and in response to this input, send the first short message to the short message center 25. The first short message includes an identifier of terminal 100 (e.g., the user ID of terminal 100), which can be used by the short message center 25 to identify terminal 100.

[0292] It should be noted that the first short message also includes the identifier of terminal 300 (user ID).

[0293] S1003, the short message center 25 queries the home location register / home subscriber server 28 for the network where terminal 100 is located.

[0294] S1004, Home Location Register / Home Subscriber Server 28 sends feedback to Short Message Service 25 that Terminal 100 is residing in the BeiDou network.

[0295] S1005, the short message center 25 sends a Beidou prompt message to the terminal 300.

[0296] S1006, Terminal 300 sends a confirmation message to Short Message Center 25.

[0297] S1007, the short message center 25 sends the first short message to the Beidou network device 200.

[0298] After receiving the confirmation message, the short message center 25 can send a first short message to the BeiDou network device 200. Upon receiving the first short message, the BeiDou network device 200 can store it.

[0299] Optionally, the short message center 25 may choose not to send the aforementioned BeiDou notification information to the terminal 300, but instead directly send the first short message to the BeiDou network device 200.

[0300] For a detailed description of steps S1001-S1007, please refer to the above. Figure 4 The embodiments shown are not described in detail here.

[0301] S1008, Beidou network equipment 200 determines whether the whitelist of terminal 100 includes the user ID of terminal 300.

[0302] When the BeiDou network device 200 determines that the whitelist of terminal 100 includes the user ID of terminal 300, step S1009 can be executed; when the BeiDou network device 200 determines that the whitelist of terminal 100 does not include the user ID of terminal 300, the first short message can be left unstored.

[0303] S1009, Beidou network equipment 200 stores the first short message.

[0304] Specifically, the BeiDou network device 200 can determine the whitelist of the receiving terminal 100 based on the recipient identifier in the short message, and after determining that the sending terminal 300 of the first short message is in the whitelist of the terminal 100, it stores the first short message sent by the terminal 300.

[0305] Optionally, the Beidou network device 200 can also perform step S1010.

[0306] S1010, Beidou network equipment 200 sends a confirmation message to short message center 25.

[0307] The BeiDou network device 200 can send a confirmation message to the short message center 25. This confirmation message can be used to indicate to the short message center 25 that the BeiDou network device 200 has stored short messages. The short message center 25 can delete the short message indicated by the confirmation message.

[0308] S1011, Terminal 100 sends a message request to Beidou network device 200 for downloading short messages from all terminals.

[0309] Terminal 100, upon receiving input from a user requesting to download all BeiDou short messages from all terminals, can send a message request to BeiDou network device 200 in response. The service type of this message request is the "Download all terminal short messages" service. For example, a message request with a service type field value of 101. It is understood that since BeiDou network device 200 only stores short messages sent by terminals within terminal 100's whitelist, the "Download all terminals" message request is a message request to download short messages from all terminals within the whitelist.

[0310] S1012, Beidou network device 200 sends the first Beidou short message to terminal 100.

[0311] After receiving a message request from terminal 100, BeiDou network device 200 can send the message content of all short messages sent by terminals in the whitelist to terminal 100. Since terminal 100's whitelist includes the identifier (message ID) of terminal 300, BeiDou network device 200 can generate a first BeiDou short message based on the first short message. For a detailed description of how BeiDou network device 200 sends the first BeiDou short message to terminal 100, please refer to the above. Figure 3A The embodiments described herein will not be repeated here.

[0312] It should be noted that the terminal 300 described here is only an example. After receiving the message request, the Beidou network device 200 will determine whether all other short messages sent to terminal 100 are short messages sent by terminals in the whitelist, and will send all short messages sent by terminals in the whitelist to terminal 100.

[0313] It should be noted that if the user ID of terminal 300 is not included in the whitelist of terminal 100, after receiving the email request from terminal 100 to download short messages from all terminals, if BeiDou network device 200 also contains short messages sent to terminal 100 by terminals within the whitelist, BeiDou network device 200 can send the message content of all short messages sent by terminals within the whitelist to terminal 100. Specifically, BeiDou network device 200 can use the message content of short messages sent by terminals within the whitelist as raw data, obtain a second BeiDou short message based on the raw data, and send the second BeiDou short message to terminal 100. Since the identifier (message ID) of terminal 300 is not included in the whitelist of terminal 100, the second BeiDou short message generated by BeiDou network device 200 does not include the message content of the first short message.

[0314] Furthermore, if the BeiDou network device 200 does not contain short messages sent to terminal 100 by one or more terminals that have indicated a message request from terminal 100, the BeiDou network device 200 can send a first indication message to terminal 100. This first indication message indicates that the BeiDou network device 200 does not store short messages from those one or more terminals. The first indication message includes the identifier of those one or more terminals. It is understood that when the BeiDou network device 200 only stores short messages from some of the terminals that have indicated a message request, the BeiDou network device 200 can send the aforementioned second BeiDou short message and the aforementioned first indication message to terminal 100.

[0315] Optionally, after receiving the first instruction information, terminal 100 may display a no-message notification message. The no-message notification message can be used to inform the user that there are no short messages sent by the terminal.

[0316] It is understandable that when terminal 300 is included in the whitelist of terminal 100, after receiving a letter request from terminal 100 to download the short message of the specified terminal 300 in the whitelist (indicating the download of the short message of terminal 300 through the whitelist unit graph field), Beidou network device 200 can also send the message content of the first short message to terminal 100.

[0317] It should be noted that, since the BeiDou network device 200 does not store short messages sent to terminal 100 by terminals not on the whitelist, when terminal 300 is not on terminal 100's whitelist, after receiving a message request from terminal 100 to download short messages from the specified terminal 300 (indicating the need to download short messages from terminal 300 via the target terminal identifier field), the BeiDou network device 200 will return a second BeiDou short message to indicate that terminal 100 has no BeiDou short messages available to receive.

[0318] Optionally, when terminal 100 adjusts its whitelist under the BeiDou network, and BeiDou network device 200 receives a request from terminal 100 to download short messages from terminal 300 that is not on the whitelist, it can add the identifier of terminal 300 to terminal 100's whitelist. After BeiDou network device 200 adjusts terminal 100's whitelist, and receives another short message from terminal 300 to terminal 100 sent by short message center 25, it can store the short message sent by terminal 300 in BeiDou network device 200. When terminal 100 again requests to download short messages from terminal 300, BeiDou network device 200 can send the short message sent by terminal 300 to terminal 100.

[0319] Optionally, the BeiDou network device 200 may not store short messages sent to terminal 100 by terminals not on the whitelist. When terminal 300 is not on the whitelist of terminal 100, after receiving a message request from terminal 100 to download a short message from the specified terminal 300 (indicating the short message to download from terminal 300 via the target terminal identifier field), the BeiDou network device 200 may retrieve the short message from terminal 300 from the short message center 25 and then send the message content to terminal 100.

[0320] Similarly, the scenario where BeiDou network device 200 receives a summary request from terminal 100 can be found in the above description. Figure 10 The example of the letter request shown will not be described again here.

[0321] In other embodiments, the short message center 25 stores whitelists set by each terminal. The short message center 25 can determine the whitelist of recipients (e.g., terminal 100) based on the recipient identifier in the short message, and send short messages sent by terminals in the whitelist to the BeiDou network device 200.

[0322] In one possible implementation, the Short Message Service (SMS) center 25 stores short messages sent to terminal 100 by other terminals. Upon receiving a message request, the BeiDou network device 200 retrieves short messages from the SMS center 25 based on the message request and a whitelist. Upon receiving a summary request, the BeiDou network device 200 retrieves the quantity information of short messages from the SMS center 25 based on the summary request and the whitelist. For example, if the BeiDou network device 200 receives a short message from terminal 100 downloading a message from terminal 10 in the whitelist, the BeiDou network device 200 can send the identifier of the target terminal 10 and the identifier of terminal 100 to the SMS center 25. The SMS center 25 then sends the short message from the target terminal 10 to terminal 100 back to the BeiDou network device 200 based on the identifier of the target terminal 10. The BeiDou network device 200 then sends the message content of the short message from the target terminal 10 to terminal 100 back to terminal 100.

[0323] Understandably, when a BeiDou network device (e.g., BeiDou network device 200) receives a BeiDou short message sent from a third terminal (e.g., terminal 100) within the BeiDou network to a first terminal within the BeiDou network, the BeiDou network device can determine whether the first terminal's whitelist includes the third terminal's identifier. If the first terminal's whitelist includes the third terminal's identifier, the BeiDou network device can store the BeiDou short message. If the first terminal's whitelist does not include the third terminal's identifier, the BeiDou network device can send the BeiDou short message to the short message center 25. When the first terminal returns to the cellular network, the short message center 25 can send the BeiDou short message back to the first terminal. In this way, the BeiDou network device can only store short messages sent by terminals within the whitelist, saving storage space. Furthermore, the BeiDou network device can only send short messages from terminals within the whitelist to terminals within the BeiDou network, saving air interface transmission resources.

[0324] Optionally, the BeiDou network device can send BeiDou short messages sent by a third terminal under the BeiDou network to the short message center 25. After receiving the BeiDou short message, the short message center 25 can determine whether the whitelist of the first terminal includes the identifier of the third terminal. If the whitelist of the first terminal includes the identifier of the third terminal, the short message center 25 can discard the BeiDou short message. If the whitelist of the first terminal does not include the identifier of the third terminal, the short message center 25 can store the BeiDou short message and send a non-whitelist indication message to the BeiDou network device. The non-whitelist indication message is used to indicate that the terminal sending the BeiDou short message is not a terminal in the whitelist. After receiving the non-whitelist indication message, the BeiDou network device can delete the BeiDou short message.

[0325] The terminal 100 provided in the embodiments of this application is described below.

[0326] Terminal 100 may be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device and / or smart city device. The specific type of electronic device is not particularly limited in the embodiments of this application.

[0327] Figure 11 A schematic diagram of a hardware structure provided in an embodiment of this application is shown.

[0328] The following description uses terminal 100 as an example to illustrate the embodiment. It should be understood that... Figure 11 The terminal 100 shown is merely an example, and terminal 100 can have more than... Figure 11 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 11 The various components shown 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.

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

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

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

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

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

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

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

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

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

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

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

[0340] The GPIO interface is configurable 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.

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

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

[0343] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the terminal 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0344] The power management module 141 connects 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, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

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

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

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

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

[0349] 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), satellite communication modules, frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. 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.

[0350] Among them, the satellite communication module can be used to communicate with satellite network equipment. For example, in the BeiDou communication system, the satellite communication module can communicate with BeiDou network equipment 200, and the satellite communication module can support short message transmission between BeiDou network equipment 200.

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

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

[0353] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may 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 miniature LED, a microLED, 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.

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

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

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

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

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

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

[0360] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0361] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of terminal 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of terminal 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0379] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can parse the voice signals based on the vibration signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 180M to realize voice functionality. The application processor can parse heart rate information based on the blood pressure signals acquired by the bone conduction sensor 180M to realize heart rate detection functionality.

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

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

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

[0383] 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, SIM cards, etc. 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. In some embodiments, the terminal 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal 100 and cannot be separated from the terminal 100.

[0384] The following describes a whitelist control method in a BeiDou communication system provided in the embodiments of this application.

[0385] Figure 12 A flowchart illustrating a whitelist control method in a BeiDou communication system provided in an embodiment of this application is shown.

[0386] like Figure 12 As shown, the whitelist control method in this BeiDou communication system includes the following steps:

[0387] S1201, Terminal 300 sends a first short message to Beidou network device 200, the first short message including the identifier of Terminal 100.

[0388] S1202, Beidou network equipment 200 determines whether the whitelist of terminal 100 includes the identifier of terminal 300.

[0389] When BeiDou network device 200 determines that the whitelist of terminal 100 includes the identifier of terminal 300, BeiDou network device 200 can execute step S1203; when BeiDou network device 200 determines that the whitelist of terminal 100 does not include the identifier of terminal 300, BeiDou network device 200 can discard the first short message.

[0390] S1203, Beidou network equipment 200 stores the first short message.

[0391] Specifically, regarding terminal 300, the sending of the first short message can be referred to the aforementioned embodiments, and will not be repeated here.

[0392] For specific operations involving BeiDou network equipment 200, such as determining whitelisted terminals, please refer to the aforementioned embodiments, which will not be repeated here.

[0393] For a detailed description of the result of the BeiDou network device 200 receiving the email request from the terminal 100 and sending the email request to the terminal 100 based on the email request, please refer to the aforementioned embodiments, which will not be repeated here.

[0394] The following describes some possible implementation methods for the BeiDou network equipment 200.

[0395] In one possible implementation, when the BeiDou network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the BeiDou network device stores the first short message. The method further includes:

[0396] The BeiDou network device sends a confirmation message to the cellular network device, which instructs the cellular network device to delete the first short message.

[0397] For details, please refer to the above. Figure 10 The embodiment described above.

[0398] In one possible implementation, after the BeiDou network device receives the first short message sent from the second terminal to the first terminal through the cellular network device, the method further includes: the BeiDou network device receiving a first request from the first terminal; the first request is used to obtain short messages sent from one or more terminals to the first terminal, the one or more terminals including the second terminal;

[0399] When the whitelist of the first terminal includes the second terminal, the Beidou network equipment will send the first short message to the first terminal.

[0400] When the whitelist of the first terminal does not include the second terminal, the Beidou network device sends a first indication message to the first terminal. The first indication message is used to indicate that the Beidou network device does not store the short message sent by the second terminal to the first terminal.

[0401] For details, please refer to the above. Figure 10 The embodiment described above.

[0402] In one possible implementation, after the BeiDou network device receives the first request from the first terminal, the method further includes: when the first terminal's whitelist does not include the second terminal, the BeiDou network device adds the identifier of the second terminal to the first terminal's whitelist.

[0403] Specifically, please refer to the above-described example of setting / updating a whitelist under the BeiDou network.

[0404] In one possible implementation, the BeiDou network device adds the second terminal to the whitelist of the first terminal. Specifically, when the number of terminal identifiers already stored in the whitelist of the first terminal in the BeiDou network device is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the BeiDou network device replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

[0405] Specifically, please refer to the above-described example of setting / updating a whitelist under the BeiDou network.

[0406] In one possible implementation, the first request includes a service type field, which indicates the service type of the first request; wherein, the service type of the first request includes downloading SMS services sent by specified terminals within the whitelist, downloading SMS services sent by all terminals, and downloading SMS services sent by specified terminals not on the whitelist.

[0407] For specific examples, please refer to the embodiments described in Table 3 above.

[0408] In one possible implementation, when the service type of the first request is to download short messages sent by a specified terminal in the whitelist, the first request also includes a whitelist unit map field, which is used to indicate the sequence number of the second terminal in the whitelist of the first terminal.

[0409] For specific examples, please refer to the embodiments described in Table 3 above.

[0410] In one possible implementation, when the service type of the first request is to download a short message sent by a specified terminal that is not on the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal.

[0411] For specific examples, please refer to the embodiments described in Table 3 above.

[0412] The following describes some possible implementation methods for execution by terminal 100.

[0413] In one possible implementation, the first terminal sends a first request to the BeiDou network device. The first request is used to obtain short messages sent to the first terminal by one or more terminals, including the second terminal.

[0414] When the whitelist of the first terminal includes the identifier of the second terminal, the first terminal receives the first short message from the second terminal sent by the Beidou network device.

[0415] When the whitelist of the first terminal does not include the identifier of the second terminal, the first terminal receives a first indication message sent by the Beidou network device. The first indication message indicates that the Beidou network device does not store the short message sent by the second terminal to the first terminal.

[0416] For details, please refer to the above. Figure 10 The embodiment described above.

[0417] In one possible implementation, after the first terminal sends a first request to the BeiDou network device, the method further includes: when the service type of the first request is to download a short message service sent by a specified terminal that is not in the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal; the first terminal adds the identifier of the second terminal to the whitelist of the first terminal.

[0418] Specifically, please refer to the above-described example of setting / updating a whitelist under the BeiDou network.

[0419] In one possible implementation, the first terminal adds the identifier of the second terminal to the whitelist of the first terminal. Specifically, when the number of terminal identifiers already stored in the whitelist of the first terminal is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the first terminal replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

[0420] Specifically, please refer to the above-described example of setting / updating a whitelist under the BeiDou network.

[0421] In one possible implementation, the first terminal adjusts its whitelist through the BeiDou operation server.

[0422] For specific examples, please refer to the embodiments described in Table 1 above.

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

[0424] This application embodiment can divide the terminal 100 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.

[0425] The following will combine Figures 13 to 16 The communication device of the embodiments of this application is described in detail.

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

[0427] In one design, the processing unit 1320 can be used to generate a letter request.

[0428] The transceiver unit 1310 can be used to send the message request to the Beidou network device 200.

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

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

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

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

[0433] In one design, the transceiver unit 1410 can be used to receive a first short message sent by the terminal 300.

[0434] The transceiver unit 1410 is also used to receive email requests sent by the terminal 100.

[0435] The processing unit 1420 can be used to determine whether the whitelist of terminal 100 includes the identifier of terminal 300.

[0436] The processing unit 1420 is also used to generate a first BeiDou short message and / or a first indication message based on the letter request.

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

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

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

[0440] 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 13 Any product of the aforementioned terminal 100 functions, as long as it possesses the above-mentioned features. Figure 14 Any form of product that incorporates the functions of the Beidou network device 200 falls within the protection scope of this application's embodiments.

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

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

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

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

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

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

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

[0448] In one implementation, the communication device 1500 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), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

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

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

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

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

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

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

[0455] (6) Others, etc.

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

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

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

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

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

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

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

[0463] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the method in any of the foregoing embodiments.

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

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

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

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

[0468] The steps of the methods or algorithms described in this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0469] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

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

Claims

1. A whitelist control method in a satellite communication system, characterized in that, include: The satellite network device receives a first short message sent from the second terminal to the first terminal through the cellular network device. The first terminal is a terminal that has reported to the cellular network device or the satellite network device that it is residing on the satellite network. When the satellite network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the satellite network device stores the first short message; When the satellite network device determines that the identifier of the second terminal is not included in the whitelist of the first terminal, the satellite network device discards the first short message.

2. The method according to claim 1, characterized in that, When the satellite network device determines that the whitelist of the first terminal includes the identifier of the second terminal, the satellite network device stores the first short message. The method further includes: The satellite network device sends a confirmation message to the cellular network device, the confirmation message being used to instruct the cellular network device to delete the first short message.

3. The method according to claim 1 or 2, characterized in that, After the satellite network device receives the first short message sent from the second terminal to the first terminal via the cellular network device, the method further includes: The satellite network device receives a first request from the first terminal; the first request is used to obtain short messages sent to the first terminal by one or more terminals, including the second terminal; When the second terminal is included in the whitelist of the first terminal, the satellite network device sends the first short message to the first terminal; When the second terminal is not included in the whitelist of the first terminal, the satellite network device sends a first indication message to the first terminal, the first indication message indicating that the satellite network device does not store the short message sent by the second terminal to the first terminal.

4. The method according to claim 3, characterized in that, After the satellite network device receives the first request from the first terminal, the method further includes: When the second terminal is not included in the whitelist of the first terminal, the satellite network device adds the identifier of the second terminal to the whitelist of the first terminal.

5. The method according to claim 4, characterized in that, The satellite network device adds the identifier of the second terminal to the whitelist of the first terminal, specifically including: When the number of terminal identifiers already stored in the whitelist of the first terminal in the satellite network device is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the satellite network device replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

6. The method according to claim 3, characterized in that, The first request includes a service type field, which indicates the service type of the first request; wherein, the service type of the first request includes downloading SMS services sent by specified terminals within the whitelist, downloading SMS services sent by all terminals, and downloading SMS services sent by specified terminals not within the whitelist.

7. The method according to claim 6, characterized in that, When the service type of the first request is a short message service sent by a specified terminal in the download whitelist, the first request also includes a whitelist unit graph field, which is used to indicate the sequence number of the second terminal in the whitelist of the first terminal.

8. The method according to claim 6, characterized in that, When the service type of the first request is the download of a short message service sent by a specified terminal that is not in the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal.

9. A whitelist control method in a satellite communication system, characterized in that, include: When the first terminal cannot detect a cellular network signal, or receives input from the user to enable satellite communication, or sends a satellite SMS, it reports to the satellite network where it is residing. The first terminal sends a first request to the satellite network device. The first request is used to obtain short messages sent to the first terminal by one or more terminals, including a second terminal. When the whitelist of the first terminal includes the identifier of the second terminal, the first terminal receives a first short message from the satellite network device sent by the second terminal. When the whitelist of the first terminal does not include the identifier of the second terminal, the first terminal receives a first indication message sent by the satellite network device. The first indication message indicates that the satellite network device does not store the short message sent by the second terminal to the first terminal.

10. The method according to claim 9, characterized in that, After the first terminal sends a first request to the satellite network device, the method further includes: When the service type of the first request is to download a short message sent by a specified terminal that is not in the whitelist, the first request also includes a target terminal identifier field, which is used to indicate the identifier of the second terminal; the first terminal adds the identifier of the second terminal to the whitelist of the first terminal.

11. The method according to claim 10, characterized in that, The first terminal adds the identifier of the second terminal to its whitelist, specifically including: When the number of terminal identifiers already stored in the whitelist of the first terminal is the same as the maximum number of terminal identifiers stored in the whitelist of the first terminal, the first terminal replaces the identifier of the third terminal in the whitelist with the identifier of the second terminal.

12. The method according to claim 9, characterized in that, The first terminal adjusts its whitelist through the satellite operation server.

13. 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 9-12.

14. The communication device according to claim 13, characterized in that, The communication device is a terminal.

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

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

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

18. 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 9-12.

19. A chip system applied in a terminal, characterized in that, It includes a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processing circuit, the processing circuit being used to execute the code instructions to perform the method as described in any one of claims 9-12.

Images