WO2023103830A1 - 一种卫星多播短消息的方法及相关装置 - Google Patents

一种卫星多播短消息的方法及相关装置 Download PDF

Info

Publication number
WO2023103830A1
WO2023103830A1 PCT/CN2022/134866 CN2022134866W WO2023103830A1 WO 2023103830 A1 WO2023103830 A1 WO 2023103830A1 CN 2022134866 W CN2022134866 W CN 2022134866W WO 2023103830 A1 WO2023103830 A1 WO 2023103830A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
short message
message
terminal
field
Prior art date
Application number
PCT/CN2022/134866
Other languages
English (en)
French (fr)
Inventor
樊亮亮
徐海博
姚楚婷
薛丽霞
甘雯昱
申秋晨
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202210144012.6A external-priority patent/CN116321015A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023103830A1 publication Critical patent/WO2023103830A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present application relates to the technical field of satellite communication, in particular to a method and a related device for multicast short message transmission in a satellite communication system.
  • Satellite navigation system is a major infrastructure integrating positioning, timing and communication.
  • the satellite short message communication service is one of the characteristics of the satellite communication system.
  • the satellite short message communication service is especially suitable for communication in areas where mobile communication is not covered, or cannot be covered, or the communication system is destroyed, such as oceans, deserts, grasslands, and uninhabited areas.
  • the short message system of some satellite communication satellites has upgraded the short message technical system, and opened up some necessary resources of the communication system of the satellite short message service.
  • the characteristics of the communication system of the business design the communication protocol.
  • the satellite communication system does not provide relevant protocol content for the multicast short message transmission used by the terminal.
  • Terminals under the Beidou communication system cannot send multicast short messages to other terminals, nor can they receive multicast short messages sent by other terminals.
  • the embodiment of the present application provides a method, system and related device for multicast short message transmission in a satellite communication system.
  • the terminal can also send messages to other terminals through the satellite communication system Send multicast short messages.
  • the embodiment of the present application provides a method for transmitting a multicast short message in a satellite communication system, the method is applied to a first terminal, and the method may include: the first terminal sends an inbound multicast short message to a satellite network device message message, the inbound multicast short message message can include a first field and a second field, and the first field is used to indicate that the multicast ID of the multicast group corresponding to the inbound multicast short message message is The first multicast ID, the second field is used to indicate that the information content in the inbound multicast short message is the first information content.
  • the first terminal can send multicast short messages to other terminals through the satellite network.
  • the multicast short message indicates the ID of the multicast group corresponding to the multicast short message, so the satellite network equipment can identify the multicast group corresponding to the multicast short message.
  • the inbound multicast short message message further includes a third field, and the third field is used to indicate that the service type of the inbound multicast short message message is general Message service type.
  • the first terminal sends an inbound multicast short message message to the satellite network device, including: the first terminal sends one or more first user frames to the satellite network device,
  • the one or more first user frames include a fourth field, and the fourth field is used to indicate that the frame type of the one or more first user frames is a multicast short message frame type.
  • the satellite network device can determine that the received message is an inbound multicast short message message through one or more first user frames, so that the inbound multicast short message message can be sent to the corresponding Network elements are processed.
  • the inbound multicast short message message further includes a third field, and the third field is used to indicate that the service type of the inbound multicast short message message is inbound Multicast short message type.
  • the satellite network device can directly determine that the received message is an inbound multicast short message message through the inbound multicast short message message, so the lower layer of the protocol does not need to indicate that the message is an inbound multicast short message messages, saving communication resources in satellite network equipment.
  • the first terminal sends an inbound multicast short message message to the satellite network device, including: the first terminal sends one or more first user frames to the satellite network device,
  • the one or more first user frames include a fourth field, where the fourth field is used to indicate that the frame type of the one or more first user frames is a general data frame type.
  • the method further includes: the first terminal receives the first outbound multicast short message message sent by the satellite network device, the first outbound multicast short message message includes a fifth field and a sixth field, the fifth field is used to indicate that the sender ID of the first outbound multicast short message message is the user ID of the second terminal, and the sixth field is used to indicate that the first The information content in the outbound multicast short message message is the second information content; wherein, the first terminal and the second terminal belong to the first multicast group, and the multicast ID of the first multicast group is the first multicast group Broadcast ID.
  • the first terminal after receiving the first outbound multicast short message message, the first terminal can determine the specific sender of the first outbound multicast short message message through the fifth field.
  • the first terminal receiving the first outbound multicast short message message sent by the satellite network device includes: the first terminal receiving one or more second user frames, the The one or more second user frames include a seventh field and an eighth field, the seventh field is used to indicate that the frame type of the one or more second user frames is a multicast user frame type, and the eighth field is used for Indicating that the multicast ID of the multicast group corresponding to the one or more second user frames is the first multicast ID; the first terminal determines that the one or more second user frames are multicast short messages based on the seventh field frame, and parse to obtain the first multicast ID; the first terminal obtains the first outbound multicast short message message based on the one or more second user frames, and parses to obtain the user ID and the second information content of the second terminal ; The first terminal displays the second information content based on the first multicast ID and the user ID of the second terminal.
  • one or more second user frames include the first multicast ID, so the satellite network device can send one or more second user frames once on the air interface, and the terminals in the multicast group corresponding to the first multicast ID The one or more second user frames can all be received, which saves air interface resources for satellite communications.
  • the method further includes: the first terminal sends a multicast short message query request message to the satellite network device, and the multicast short message query request message includes a service type field , the service type field is used to indicate that the service type of the multicast short message query request message is the multicast short message query type; the first terminal receives and displays the multicast short message query result message, and the multicast short message query result The message is generated by the satellite network equipment based on the multicast short message query request message.
  • the first terminal can query the number of unsuccessfully received multicast short message messages through the satellite system.
  • the service type field is used to indicate that the service type of the multicast short message query request message is a multicast short message query type, and the query specifies that the multicast group is sent to the first The quantity of the multicast short message of terminal; Also comprise multicast ID field and multicast short message ID field in the multicast short message inquiry request message, described multicast ID field is used for indicating the multicast ID of designated multicast group , the multicast short message ID field is used to indicate the multicast short message ID of the last multicast short message among the multicast short messages successfully received by the first terminal continuously; the multicast short message query result message includes the multicast short message The number field, the multicast short message number field is used to indicate the number of multicast short messages sent to the first terminal by the specified multicast group.
  • the first terminal can query the number of unsuccessfully received multicast short messages in the designated multicast group through the satellite communication system.
  • the service type field is used to indicate that the service type of the multicast short message query request message is a multicast short message query type, and the query sent to all multicast groups is sent to the first The quantity of the multicast short message of terminal; Also comprise the multicast short message ID field in the multicast short message inquiry request message, the multicast short message ID field is used for indicating the last in the multicast short message that the first terminal receives successfully successively The ID of a multicast short message; The multicast short message quantity field is included in the multicast short message query result message, and the multicast short message quantity field is used to indicate that all multicast groups send to the multicast short message of the first terminal quantity.
  • the first terminal can query the number of unsuccessfully received multicast short messages in all multicast groups through the satellite communication system.
  • the method further includes: the first terminal sends a multicast short message download request message to the satellite network device, the multicast short message download request message includes a service type field, The service type field is used to indicate that the service type of the multicast short message download request message is a multicast short message download type; the first terminal receives and displays the second outbound multicast short message message, and the second outbound multicast short message The message is generated by the satellite network equipment based on the multicast short message download request message.
  • the first terminal can download the information content of the unsuccessfully received multicast short message through the satellite communication system.
  • the service type field is used to indicate that the service type of the multicast short message download request message is a multicast short message download type, and the download specifies that the multicast group is sent to the first The multicast short message of the terminal;
  • the multicast short message download request message also includes a multicast ID field and a multicast short message ID field, and the multicast ID field is used to indicate the multicast ID of the specified multicast group, and the multicast short message
  • the message ID field is used to indicate the multicast short message ID of the last multicast short message in the multicast short messages successfully received by the first terminal continuously;
  • the completion indication field is used to indicate whether there is a multicast short message to be sent to the first terminal in the specified multicast group.
  • the first terminal can download the information content of the unsuccessfully received multicast short messages in the designated multicast group through the satellite system. Further, the first terminal may also determine whether to continue the download.
  • the service type field is used to indicate that the service type of the multicast short message download request message is a multicast short message download type, and download all multicast groups and send them to the first The multicast short message of the terminal;
  • the multicast short message download request message also includes a multicast short message ID field, and the multicast short message ID field is used to indicate that the last multicast short message in the multicast short messages successfully received by the first terminal The multicast short message ID of broadcasting short message;
  • the download completion indication field include the download completion indication field, and the download completion indication field is used to indicate whether all multicast groups subsequently have multicast short message to send to the second a terminal.
  • the first terminal can download the information content of the unsuccessfully received multicast short messages in all multicast groups through the satellite system. Further, the first terminal may also determine whether to continue the download.
  • the embodiment of the present application provides a method for transmitting a multicast short message in a satellite communication system.
  • the method includes: a first terminal sends an inbound multicast short message message to a satellite network device, and the inbound multicast
  • the short message message includes a first field and a second field, and the first field is used to indicate that the multicast ID of the multicast group corresponding to the inbound multicast short message message is the first multicast ID, and the second The field is used to indicate that the information content in the inbound multicast short message message is the first information content;
  • the satellite network equipment receives the inbound multicast short message message, and parses to obtain the first multicast ID and the first information content;
  • the satellite network The device sends a first outbound multicast short message message based on the first information content;
  • the second terminal receives the first outbound multicast short message message, wherein the first terminal and the second terminal belong to the first multicast group,
  • the multicast ID of the first multicast group is the first multicast ID.
  • the first terminal can send a multicast short message to the second terminal belonging to the same multicast group through the satellite network.
  • the multicast short message indicates the ID of the multicast group corresponding to the multicast short message, so the satellite network equipment can identify the multicast group corresponding to the multicast short message.
  • the inbound multicast short message message further includes a third field, and the third field is used to indicate that the service type of the multicast short message message is a general message service type.
  • the first terminal sends an inbound multicast short message message to the satellite network device, including: the first terminal sends one or more first user frames to the satellite network device,
  • the one or more first user frames include a fourth field, and the fourth field is used to indicate that the frame type of the one or more first user frames is a multicast short message frame type.
  • the satellite network device receiving the inbound multicast short message message includes: the satellite network device receives one or more first user frames, and parses to obtain the fourth field; The satellite network device determines that one or more first user frames are multicast short message frames based on the fourth field; the satellite network device obtains the inbound multicast short message message based on the one or more first user frames, and parses to obtain the first A multicast ID and first information content.
  • the satellite network device can determine that the received message is an inbound multicast short message message through one or more first user frames, so that the inbound multicast short message message can be sent to the corresponding Network elements are processed.
  • the inbound multicast short message includes a third field, and the third field is used to indicate that the service type of the multicast short message is an inbound multicast short message. message type.
  • the first terminal sends an inbound multicast short message message to the satellite network device, including: the first terminal sends one or more first user frames to the satellite network device,
  • the one or more first user frames include a fourth field, where the fourth field is used to indicate that the frame type of the one or more first user frames is a general data frame type.
  • the satellite network device receiving the inbound multicast short message message includes: the satellite network device receives one or more first user frames; the satellite network device receives one or more first user frames; The first user frame obtains the inbound multicast short message message, and parses to obtain the third field; the satellite network equipment determines that the service type of the inbound multicast short message message is the inbound multicast short message type based on the third field, and The first multicast ID and the first information content are obtained by parsing.
  • the satellite network device can directly determine that the received message is an inbound multicast short message message through the inbound multicast short message message, so the lower layer of the protocol does not need to indicate that the message is an inbound multicast short message messages, saving communication resources in satellite network equipment.
  • the first outbound multicast short message message includes a sender ID field and a fifth field, and the sender ID field is used to indicate that the first outbound multicast short message
  • the sender ID of the multicast short message message is the user ID of the first terminal
  • the fifth field is used to indicate the first information content of the first outbound multicast short message message.
  • the satellite network device sends the first outbound multicast short message message based on the information content, including: the satellite network device sends one or more second user frames, the One or more second user frames include a sixth field and a seventh field, the sixth field is used to indicate that the frame type of one or more second user frames is a multicast short message frame type, and the seventh field is used for Indicating that the multicast ID of the multicast group corresponding to the one or more second user frames is the first multicast ID.
  • one or more second user frames include the first multicast ID, so the satellite network device can send one or more second user frames once on the air interface, and the terminals in the multicast group corresponding to the first multicast ID The one or more second user frames can all be received, which saves air interface resources for satellite communications.
  • the second terminal receiving the first outbound multicast short message message includes: the second terminal receives one or more second user frames, and parses to obtain the sixth field; The second terminal determines that one or more second user frames are multicast short message frames based on the sixth field, and parses to obtain the first multicast ID; the second terminal obtains the first outbound message frame based on one or more second user frames Broadcast a short message message, and parse to obtain the user ID of the first terminal and the first information content; the second terminal displays the first information content based on the first multicast ID and the user ID of the first terminal.
  • the first terminal after receiving the first outbound multicast short message message, the first terminal can determine the specific sender of the first outbound multicast short message message through the sixth field.
  • the method further includes: the satellite network device determines the first outbound multicast short message The satellite information and beam information of the broadcast short message message.
  • the satellite network device can determine satellite information and beam information before sending the first outbound multicast short message message, which improves the success rate of sending the first outbound multicast short message message.
  • the inbound multicast short message message includes a location information field, and the location information field is used to indicate the location information of the first terminal; the satellite network device determines the first outgoing terminal The satellite information and beam information of the station multicast short message message, including: the satellite network device analyzes the location information field based on the inbound multicast short message message; the satellite network device obtains the first outbound multicast message based on the location information field. The satellite information and beam information of the broadcast short message message.
  • the satellite network equipment can receive the position information of the first terminal, and determine the satellite information and beam information of the first outbound multicast short message message according to the position information of the first terminal, which improves the efficiency of the first outbound multicast short message.
  • the success rate of packet sending is the rate of packet sending.
  • one or more first user frames include an outbound link indication field, and the outbound link indication field is used to indicate that the first outbound multicast short message message satellite information and beam information of the text; before the satellite network equipment sends the first outbound multicast short message message based on the first information content, the method also includes: the satellite network equipment analyzes and obtains the first user frame based on one or multicast An outbound link indication field: the satellite network device obtains satellite information and beam information of the first outbound multicast short message message based on the outbound link indication field.
  • the satellite network equipment can receive the outbound link indication, and determine the satellite information and beam information of the first outbound multicast short message message according to the outbound link indication, which improves the speed of the first outbound multicast short message.
  • the success rate of packet sending is the rate of packet sending.
  • the method further includes: the first terminal sends a multicast short message query request message to the satellite network device, the multicast short message query request message includes a service type field, The service type field is used to indicate that the service type of the multicast short message query request message is the multicast short message query type; the satellite network equipment receives the multicast short message query request message; A multicast short message query result message is generated; the satellite network device sends the multicast short message query result message to the first terminal; the first terminal receives and displays the multicast short message query result message.
  • the first terminal can query the number of unsuccessfully received multicast short message messages through the satellite system.
  • the service type field is used to indicate that the service type of the multicast short message query request message is a multicast short message query type, and the query specifies that the multicast group is sent to the first The quantity of the multicast short message of terminal; Also comprise multicast ID field and multicast short message ID field in the multicast short message inquiry request message, this multicast ID field is used for indicating the multicast ID of designated multicast group, The multicast short message ID field is used to indicate the multicast short message ID of the last multicast short message in the multicast short messages successfully received by the first terminal continuously; the multicast short message query result message includes the multicast short message The number field, the multicast short message number field is used to indicate the number of multicast short messages sent to the first terminal by the specified multicast group.
  • the first terminal can query the number of unsuccessfully received multicast short messages in the designated multicast group through the satellite communication system.
  • the service type field is used to indicate that the service type of the multicast short message query request message is a multicast short message query type, and the query sent to all multicast groups is sent to the first The quantity of the multicast short message of terminal; Also comprise the multicast short message ID field in the multicast short message inquiry request message, this multicast short message ID field is used for indicating that in the multicast short message that the first terminal receives continuously The multicast short message ID of the last multicast short message; the multicast short message quantity field is included in the multicast short message query result message, and the multicast short message quantity field is used to indicate that all multicast groups are sent to the first terminal The number of multicast short messages.
  • the first terminal can query the number of unsuccessfully received multicast short messages in all multicast groups through the satellite communication system.
  • the method further includes: the first terminal sends a multicast short message download request message to the satellite network device, the multicast short message download request message includes a service type field, The service type field is used to indicate that the service type of the multicast short message download request message is the multicast short message download type; the satellite network equipment receives the multicast short message download request message; the satellite network equipment downloads the request message based on the multicast short message , generating a second outbound multicast short message; the satellite network device sends the second outbound multicast short message to the first terminal; the first terminal receives and displays the second outbound multicast short message.
  • the first terminal can download the information content of the unsuccessfully received multicast short message through the satellite communication system.
  • the service type field is used to indicate that the service type of the multicast short message download request message is a multicast short message download type, and the download specifies that the multicast group is sent to the first The multicast short message of the terminal; the multicast ID field and the multicast short message ID field are also included in the multicast short message download request message, and the multicast ID field is used to indicate the multicast ID of the designated multicast group.
  • the broadcast short message ID field is used to indicate the multicast short message ID of the last multicast short message in the multicast short messages successfully received by the first terminal continuously;
  • the second outbound multicast short message message includes the download completion indication field , the download completion indication field is used to indicate whether the specified multicast group will subsequently send a multicast short message to the first terminal.
  • the first terminal can download the information content of the unsuccessfully received multicast short messages in the designated multicast group through the satellite system. Further, the first terminal may also determine whether to continue the download.
  • the service type field is used to indicate that the service type of the multicast short message download request message is a multicast short message download type, and download all multicast groups and send them to the first
  • the multicast short message of the terminal also includes a multicast short message ID field, and the multicast short message ID field is used to indicate that the first terminal has continuously successfully received the multicast short message
  • the multicast short message ID of the last multicast short message includes a download completion indication field, and the download completion indication field is used to indicate whether all multicast groups subsequently have multicast short messages The message is sent to the first terminal.
  • the first terminal can download the information content of the unsuccessfully received multicast short messages in all multicast groups through the satellite system. Further, the first terminal may also determine whether to continue the download.
  • an embodiment of the present application provides a communication device, including one or more processors, one or more memories, and a transceiver; wherein, the transceiver, one or more memories are coupled to one or more processors , one or more memories are used to store computer program codes, the computer program codes include computer instructions, and when one or more processors execute the computer instructions, the communication device executes any one of the possible implementation manners of the first aspect above Methods.
  • the communication device is a terminal.
  • the embodiment of the present application provides a computer-readable storage medium, and instructions are stored in the computer-readable storage medium, and when the instructions are run on the computer, the computer is made to execute any possible implementation of the above-mentioned first aspect. method in .
  • the embodiment of the present application provides a chip or a chip system applied to 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 run the code instructions to execute The method in any possible implementation manner of the first aspect above.
  • FIG. 1 is a schematic structural diagram of a satellite communication system provided by an embodiment of the present application.
  • FIG. 2A is a data inbound transmission process in a satellite communication system provided by an embodiment of the present application.
  • FIG. 2B is a data outbound transmission process in a satellite communication system provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a terminal 100 provided in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a protocol encapsulation architecture of inbound data of a satellite communication system 10 provided in an embodiment of the present application;
  • FIG. 5 is a schematic diagram of a protocol analysis framework for inbound data of a satellite communication system 10 provided in an embodiment of the present application;
  • FIG. 6 is a schematic diagram of a protocol encapsulation framework for outbound data of a satellite communication system 10 provided in an embodiment of the present application;
  • FIG. 7 is a schematic diagram of a protocol analysis framework for outbound data of a satellite communication system 10 provided in an embodiment of the present application.
  • FIGS. 9A-9B are schematic diagrams of another set of interfaces provided in the embodiment of the present application.
  • FIG. 10A is a schematic flow diagram of a multicast short message transmission in a satellite communication system provided in an embodiment of the present application.
  • FIG. 10B is a schematic flow diagram of multicast short message transmission in another satellite communication system provided in the embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of another satellite communication system provided by an embodiment of the present application.
  • FIG. 12A is a schematic flow diagram of multicast short message transmission in another satellite communication system provided in the embodiment of the present application.
  • FIG. 12B is a schematic flow diagram of multicast short message transmission in another satellite communication system provided in the embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another satellite communication system provided by an embodiment of the present application.
  • Fig. 14 is a schematic flow diagram of the method for querying the multicast short message quantity in a kind of satellite communication system provided in the embodiment of the application;
  • FIG. 15 is a schematic flow diagram of a method for downloading a multicast short message in a satellite communication system provided in an embodiment of the present application
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • first and second are used for descriptive purposes only, and cannot be understood as implying or implying relative importance or implicitly specifying the quantity of indicated technical features. Therefore, the features defined as “first” and “second” may explicitly or implicitly include one or more of these features. In the description of the embodiments of the present application, unless otherwise specified, the “multiple” The meaning is two or more.
  • a satellite communication system 10 provided in the embodiment of the present application is introduced below.
  • FIG. 1 shows a schematic structural diagram of a satellite communication system 10 provided in an embodiment of the present application, taking a satellite communication system as an example.
  • the satellite communication system 10 may include a terminal 100 , a short message satellite 21 , a satellite network device 200 , a short message center 25 and a terminal 300 .
  • the satellite communication system 10 may also include an emergency rescue platform 26 and an emergency rescue center 27 .
  • the terminal 100 can send the short message information to the short message satellite 21, and the short message satellite 21 only performs a relay, and directly forwards the short message information sent by the terminal 100 to the satellite network device 200 on the ground.
  • the satellite network device 200 can analyze the short message information forwarded by the satellite according to the satellite communication protocol, and forward the message content of the general message type parsed from the short message information to the short message center (short message service center, SMSC) 25.
  • the short message center 25 can forward the content of the message to the terminal 300 through a traditional cellular communication network.
  • the satellite network device 200 may also send the emergency message sent by the terminal 100 to the emergency rescue center 27 through the emergency rescue platform 26 .
  • the terminal 300 can also send the short message to the short message center 25 through a traditional cellular communication network.
  • the short message center 25 can forward the short message of the terminal 300 to the satellite network device 200 .
  • the satellite network device 200 can relay the short message of the terminal 300 to the terminal 100 through the short message satellite 21 .
  • the terminal 100 may send the location information of the terminal 100 to the location center 28 through the satellite communication system. After receiving the location information sent by the terminal 100, the location center 28 stores the location information of the terminal 100 locally. Wherein, the location information may include longitude information, latitude information and altitude information of the terminal 100 .
  • the location center 28 may be a subscriber home server (Home Subscriber Server, HSS).
  • HSS Home Subscriber Server
  • NR New Radio
  • UDM Unified Data Management
  • the above-mentioned satellite network equipment 200 may include a satellite ground transceiver station 22, a satellite central station 23 and a satellite short message fusion communication platform 24.
  • the satellite ground transceiver station 22 may include one or more devices with a sending function and one or more devices with a receiving function, or may include one or more devices with a sending function and a receiving function, which is not limited herein .
  • the satellite ground transceiver station 22 can be used for the data processing function of the satellite network device 200 at the physical layer (physical layer protocol, PHY).
  • the satellite central station 23 can be used for the data processing function of the satellite network device 200 at the satellite link layer (satellite link control protocol, SLC) layer and the message data convergence protocol (message data convergence protocol, MDCP).
  • the satellite short message fusion communication platform 24 can be used for data processing function at the application layer (Application Protocol, APP).
  • the satellite communication system 10 since the satellite communication system 10 communicates through satellite links, its main characteristics are: time extension (about 270 ms in one direction), and large link loss.
  • the services supported by the current satellite communication system 10 are mainly burst short message services, and do not support connection state management, mobility management, and broadcast control information.
  • the terminal 100 can actively send data to the satellite network device 200 through the short message satellite 21 .
  • the central station on the ground cannot actively page users. Due to the long propagation distance of satellite communication, the satellite communication system 10 requires high transmission power of the terminal 100 . Due to the limitation of the radio frequency device on the current terminal 100, the terminal 100 cannot continuously send signals to the short message satellite 21 for a long time. In order not to damage the radio frequency device on the terminal 100 as much as possible, after the radio frequency device of the terminal 100 continues to work for a period of time in the sending state, it must stop working for a period of time before continuing to switch to the sending state to continue working.
  • the duration of the sending state on the terminal 100 is determined by the underlying hardware capability of the terminal 100 .
  • the terminal 100 in order to ensure that the data received by the terminal 100 and the data sent do not interfere with each other, the terminal 100 does not support sending data and receiving data simultaneously. The terminal 100 needs to wait to receive the data sent by the satellite network device 200 after sending the data.
  • the working mode of the satellite network device 200 may be a duplex mode, and data may be sent and received at the same time, and the satellite network device 200 may send and receive data for a long time.
  • FIG. 2A shows an inbound data transmission process in a satellite communication system provided by an embodiment of the present application.
  • data inbound may refer to the terminal 100 sending data to the satellite network device 200 .
  • terminal 100 may transmit data frames to satellite ground transceiver station 22 .
  • the satellite ground transceiver station 22 can send the data frame to the satellite central station 23 .
  • the satellite central station 23 can aggregate data frames into an application layer message and report it to the satellite short message fusion communication platform 24 .
  • the satellite central station 23 may return an acknowledgment character (acknowledge character, ACK) of the SLC layer to the terminal 100.
  • the ACK can be used to indicate whether the satellite network device 200 has successfully received the data frame sent by the terminal 100 .
  • FIG. 2B shows a data outbound transmission process in a satellite communication system provided by an embodiment of the present application.
  • outbound data may refer to the satellite network device 200 sending data to the terminal 100 .
  • the satellite short message fusion communication platform 24 in the satellite network device 200 can send the application layer message to the satellite central station 23; then the satellite central station 23 can split the application layer message into one or more data frames It is sent to the satellite ground transceiver station 22, and then sent to the terminal 100 after being relayed by the short message satellite 21.
  • the terminal 100 may return an ACK of the SLC layer to the satellite central station 23 after receiving the data frame. The ACK can be used for whether the terminal 100 successfully receives the data frame sent by the satellite network device 200 .
  • FIG. 3 shows a schematic structural diagram of the terminal 100 .
  • the terminal 100 shown in FIG. 3 is only an example, and the terminal 100 may have more or fewer components than those shown in FIG. 3, may combine two or more components, or may have Different component configurations.
  • the various components shown in Figure 3 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.
  • the terminal 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and A subscriber identification module (subscriber identification module, SIM) card interface 195 and the like.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal 100 .
  • the terminal 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit, NPU
  • the controller may be the nerve center and command center of the terminal 100 .
  • the controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.
  • the wireless communication function of the terminal 100 can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in terminal 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the terminal 100 .
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves and radiate them through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the low-frequency baseband signal is passed to the application processor after being processed by the baseband processor.
  • the application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194 .
  • the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent from the processor 110, and be set in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system, etc. (global navigation satellite system, GNSS), satellite communication module, frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.
  • the wireless communication module 160 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.
  • the satellite communication module can be used to communicate with satellite network equipment.
  • the satellite communication module can communicate with Beidou network equipment, and the satellite communication module can support short message transmission with Beidou network equipment.
  • the antenna 1 of the terminal 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR techniques, etc.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • code division multiple access code division multiple access
  • CDMA broadband Code division multiple access
  • WCDMA wideband code division multiple access
  • time division code division multiple access time-division code division multiple access
  • TD-SCDMA time-division code division multiple access
  • LTE long
  • the GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou navigation satellite system (beidou navigation satellite system, BDS), a quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • Beidou navigation satellite system beidou navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the terminal 100 realizes the display function through the GPU, the display screen 194, and the application processor.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
  • the display screen 194 is used to display images, videos and the like.
  • the display screen 194 includes a display panel.
  • the display panel may be a liquid crystal display (LCD).
  • the display panel can also use organic light-emitting diodes (organic light-emitting diodes, OLEDs), active-matrix organic light-emitting diodes or active-matrix organic light-emitting diodes (active-matrix organic light emitting diodes, AMOLEDs), flexible light-emitting diodes ( flex light-emitting diode, FLED), miniled, microLed, micro-oled, quantum dot light emitting diodes (quantum dot light emitting diodes, QLED), etc.
  • the terminal 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.
  • the external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. Such as saving music, video and other files in the external memory card.
  • the internal memory 121 may be used to store computer-executable program codes including instructions.
  • the processor 110 executes various functional applications and data processing of the terminal 100 by executing instructions stored in the internal memory 121 .
  • the internal memory 121 may include an area for storing programs and an area for storing data.
  • the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like.
  • the storage data area can store data created during the use of the terminal 100 (such as audio data, phonebook, etc.) and the like.
  • the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.
  • the terminal 100 may implement an audio function through an audio module 170 , a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor. Such as music playback, recording, etc.
  • the SIM card interface 195 is used for connecting a SIM card.
  • the SIM card can be connected and separated from the terminal 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 .
  • the terminal 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards may be the same or different.
  • 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 implement functions such as calling and data communication.
  • the terminal 100 adopts an eSIM, that is, an embedded SIM card.
  • the eSIM card can be embedded in the terminal 100 and cannot be separated from the terminal 100 .
  • a protocol encapsulation framework for inbound data of the satellite communication system 10 provided in the embodiment of the present application is introduced below.
  • FIG. 4 shows a schematic diagram of a protocol encapsulation architecture of inbound data of a satellite communication system 10 provided in an embodiment of the present application.
  • the satellite short message transmission protocol layer on the terminal 100 can be divided into an application layer (Application Protocol, APP), a message data convergence layer (Message Data Convergence Protocol, MDCP), a satellite link control layer (Satellite Link Control, SLC) and physical layer (Physical, PHY).
  • Application Protocol Application Protocol
  • MDCP message Data Convergence Protocol
  • SLC Satellite Link Control
  • PHY Physical layer
  • the workflow of the satellite short message transmission protocol on the terminal 100 can be as follows:
  • the terminal 100 can compress the original data into compressed data through a compression algorithm, and add a compression indication field in front of the compressed data, wherein the compression indication field can be used to indicate the compression algorithm type of the compressed data. Afterwards, the terminal 100 may encrypt the compressed data to obtain encrypted data, and add an encryption indication field to the header of the encrypted data, where the encryption indication field is used to indicate the encryption algorithm type of the encrypted data. The terminal 100 may encapsulate the encrypted data, the compressed indication field, and the encrypted indication field into an application layer message and send it to the MDCP layer.
  • the application layer message includes a message header and message data.
  • the packet header includes a compression indication field, an encryption indication field, and the like.
  • the message data includes the above-mentioned encrypted data.
  • the terminal 100 may also encrypt the compression indication field and the compressed data together to obtain encrypted data.
  • the terminal 100 can obtain the application layer message sent by the APP layer through the interlayer interface, and use the application layer message as an MDCP SDU (MDCP Service Data Unit, MDCP service data unit). Due to the limitation of the air interface, the terminal 100 can only send a physical frame of a specified length at the physical layer each time, so that the length of the MDCP layer data is restricted to the specified length. Therefore, at the MDCP layer, the terminal 100 can add padding to a specified length at the end of the MDCP SDU, and add a redundant length indication field at the head of the MDCP SDU. The redundant length indication field may be used to indicate the length of the padding data.
  • MDCP SDU MDCP Service Data Unit
  • the terminal 100 can split the padding data and the MDCP SDU after adding the redundant length indication field into one or more fixed-length MDCP segment data (M_segment), and add a follow-up indication to the header of each MDCP segment data Field, get MDCP PDU (MDCP Protocol Data Unit, MDCP protocol data unit), that is, MDCP PDU includes M_segment and successor indication field.
  • MDCP PDU MDCP Protocol Data Unit, MDCP protocol data unit
  • the follow-up indication field can be used to indicate that the current MDCP PDU is the initial MDCP PDU, intermediate MDCP PDU or the last MDCP PDU among multiple MDCP PDUs sent continuously; or, it is an MDCP PDU sent separately.
  • the terminal 100 can obtain the MDCP PDU issued by the MDCP layer through the interlayer interface as an SLC SDU (SLC Service Data Unit, SLC Service Data Unit).
  • SLC SDU SLC Service Data Unit
  • SLC Service Data Unit SLC Service Data Unit
  • the terminal 100 can segment the SLC SDU into one or more (up to 4) fixed-length SLC segment data (S_segment), and add frame header information to each S_segment header to obtain the SLC PDU (SLC Protocol Data Unit, SLC protocol data unit).
  • the terminal 100 can obtain the SLC PDU issued by the SLC layer through the interlayer interface, as a code block (code block) of the PHY layer, and add a synchronization header at the head of the code block, and add a calibration at the end of the code block. Parity field.
  • a cyclic redundancy check (cyclic redundancy check, CRC) may be used to check the coding block, therefore, the check bit field may include a CRC code.
  • the terminal 100 can encode the code block and the parity field (for example, polar encoding) to obtain coded data (coded data), and then insert a pilot into the coded data to obtain pilot coded data (pilot+data).
  • the terminal 100 sequentially modulates the synchronization header and pilot coded data through the underlying hardware to obtain modulated data (modulated data).
  • modulated data modulated data
  • the terminal 100 may perform spectrum spreading on the modulated data to obtain spread spectrum modulated data (spread+modulated data).
  • the terminal 100 can send the spread-spectrum modulated data to the short message satellite 21 , and relay and forward it to the satellite network device 200 via the short message satellite 21 .
  • a protocol analysis framework for inbound data of the satellite communication system 10 provided in the embodiment of the present application is introduced below.
  • FIG. 5 shows a schematic diagram of a protocol analysis architecture of inbound data of a satellite communication system 10 provided in an embodiment of the present application.
  • the satellite short message transmission protocol layer of the satellite network device 200 can be divided into an application layer (Application Protocol, APP), a message data convergence layer (Message Data Convergence Protocol, MDCP), a satellite link control layer (Satellite Link Control, SLC) and physical layer (Physical, PHY).
  • the satellite network device 200 may include a satellite ground transceiver station 22 , a satellite central station 23 and a satellite short message fusion communication platform 24 .
  • the satellite ground transceiver station 22 can be used to be responsible for the protocol processing of the PHY layer.
  • the satellite central station 23 can be used to be responsible for the protocol processing of the SLC layer and the MDCP layer.
  • the satellite short message fusion communication platform 24 can be used to be responsible for the protocol processing of the APP layer.
  • the workflow of the satellite short message transmission protocol layer of the satellite network device 200 can be as follows:
  • the satellite network device 200 can obtain the modulated and spread-spectrum coded pilot data sent by the terminal 100 .
  • the satellite network device 200 may despread the received spread spectrum modulated data (spread+modulated data) to obtain modulated data (modulated data). Then, the satellite network device 200 may demodulate the modulated data to obtain pilot coded data (pilot+data). Next, the satellite network device 200 removes the pilot information in the pilot coded data to obtain coded data (code data). Then, the satellite network device 200 can decode the coded data, and verify the integrity of the code block (code block) through the check data in the check bit field. If it is complete, the satellite network device 200 can extract the code block (code block), and present it to the SLC layer through the interlayer interface as the SLC PDU of the SLC layer.
  • the satellite network device 200 can splice the SLC PDUs belonging to the same SLC SDU into one SLC SDU based on the frame header information of the SLC PDU.
  • the satellite network device 200 can present the SLC SDU to the MDCP layer through the interlayer interface as an MDCP PDU of the MDCP layer.
  • the satellite network device 200 can splice all MDCP PDUs belonging to the same MDCP SDU into one MDCP SDU.
  • the satellite network device 200 can present the MDCP SDU to the APP layer through the interlayer interface, as an application layer message received by the APP layer.
  • the satellite network device 200 can decrypt and decompress the application layer message based on the message header of the application layer message to obtain original data.
  • a protocol encapsulation framework for outbound data of the satellite communication system 10 provided in the embodiment of the present application is introduced below.
  • FIG. 6 shows a schematic diagram of a protocol encapsulation architecture of outbound data of a satellite communication system 10 provided in an embodiment of the present application.
  • the satellite short message transmission protocol layer in the satellite network device 200 can be an application layer (Application Protocol, APP), a message data convergence layer (Message Data Convergence Protocol, MDCP), a satellite link control layer (Satellite Link Control, SLC) and physical layer (Physical, PHY).
  • the satellite network device 200 may include a satellite ground transceiver station 22 , a satellite central station 23 and a satellite short message fusion communication platform 24 .
  • the satellite ground transceiver station 22 can be used to be responsible for the protocol processing of the PHY layer.
  • the satellite central station 23 can be used to be responsible for the protocol processing of the SLC layer and the MDCP layer.
  • the satellite short message fusion communication platform 24 can be used to be responsible for the protocol processing of the APP layer.
  • the workflow of the satellite short message transmission protocol in the satellite network device 200 can be as follows:
  • the satellite network device 200 can compress the original data into compressed data through a compression algorithm, and add a compression indication field in front of the compressed data, wherein the compression indication field can be used to indicate the compression algorithm type of the compressed data. Afterwards, the satellite network device 200 can encrypt the compressed data and the compression indication field together to obtain the encrypted data, and add an encryption algorithm field to the header of the encrypted data, and the encryption algorithm field is used to indicate the encryption of the encrypted data algorithm type. The satellite network device 200 also needs to add a service type field at the head of the encryption algorithm field, and the service type field can be used to indicate the service type of the original data.
  • the satellite network device 200 may encapsulate the encrypted data, the compression indication field, the encryption indication field, and the service type field into an application layer message and send it to the MDCP layer.
  • the application layer message may include a message header and message data.
  • the packet header may include a compression indication field, an encryption indication field, a service type field, and the like.
  • the message data includes the above-mentioned encrypted data.
  • the satellite network device 200 can obtain the application layer message delivered by the APP layer through the interlayer interface, and use the application layer message as an MDCP SDU.
  • the satellite network device 200 can split an MDCP SDU into one or more fixed-length MDCP segment data (M_segement), and add a follow-up indication field to the header of each MDCP segment data to obtain an MDCP PDU , that is, the MDCP PDU includes M_segment and successor indication fields.
  • the follow-up indication field can be used to indicate that the current MDCP PDU is the initial MDCP PDU or the middle MDCP PDU or the last MDCP PDU of multiple MDCP PDUs sent continuously; or it is an MDCP PDU sent separately.
  • the satellite network device 200 can obtain the MDCP PDU sent by the MDCP layer through the interlayer interface as the SLC SDU.
  • the satellite network device 200 can segment the SLC SDU into one or more (up to 4) fixed-length SLC segment data (S_segement), and add frame header information to each S_segment header to obtain the SLC PDU .
  • the satellite network device 200 can obtain the SLC PDU sent by the SLC layer through the interlayer interface.
  • the satellite network device 200 can obtain SLC PDUs of one user or multiple users from the SLC layer.
  • the satellite network device 200 can splice the SLC PDUs of multiple users together, add the header of the physical frame (such as the version number) as the code block (code block) of the PHY layer, and add a check digit at the end of the code block (for example, cyclic redundancy check (cyclic redundancy check, CRC) code), and encode the code block and CRC code (for example, polar encoding), the encoded physical frame plus the reserved segment can form a fixed-length physical time
  • the coded data of the message branch (S2C_d branch) of the slot can form a fixed-length physical time
  • the satellite network device 200 can put multiple SLC PDUs of a user into different physical frames respectively. Then, the satellite network device 200 composes the coded data of the S2C_d branch and the pilot information of the pilot branch (S2C_p branch) into pilot coded data, that is, outbound data. The satellite network device 200 can send the outbound data to the short message satellite 21 , and relay and forward it to the terminal 100 via the short message satellite 21 .
  • the pilot information of the S2C_p branch is related to the satellite beam.
  • the pilot information of the S2C_p branch is also known and does not need to be decoded.
  • the coded data of the S2C_d branch needs to be decoded.
  • a protocol analysis framework for outbound data of the satellite communication system 10 provided in the embodiment of the present application is introduced below.
  • FIG. 7 shows a schematic diagram of a protocol analysis architecture of outbound data of a satellite communication system 10 provided in an embodiment of the present application.
  • the satellite short message transmission protocol layer of terminal 100 can be divided into application layer (Application Protocol, APP), message data convergence layer (Message Data Convergence Protocol, MDCP), satellite link control layer (Satellite Link Control , SLC) and physical layer (Physical, PHY).
  • application layer Application Protocol, APP
  • message data convergence layer Message Data Convergence Protocol, MDCP
  • satellite link control layer Satellite Link Control , SLC
  • Physical layer Physical, PHY
  • the workflow of the satellite short message transmission protocol layer of the terminal 100 can be as follows:
  • the terminal 100 can obtain the modulated and spread-spectrum coded pilot data sent by the satellite network device 200 .
  • the terminal 100 may despread the received spread spectrum modulated data (spread+modulated data) to obtain modulated data (modulated data).
  • the terminal 100 may demodulate the modulated data to obtain pilot coded data (pilot+data).
  • the terminal 100 may remove the pilot information in the pilot coded data to obtain coded data (code data).
  • the terminal 100 can decode the coded data, and verify the integrity of the code block (code block) through the check data in the check bit field. If it is complete, the terminal 100 can extract the code block (code block), and present it to the SLC layer through the interlayer interface as the SLC PDU of the SLC layer.
  • the pilot coded data is the outbound data sent by the above-mentioned satellite network device 200, and the outbound data is composed of coded data of the S2C_d branch and pilot information of the pilot branch (S2C_p branch).
  • the terminal 100 can splice the SLC PDUs belonging to the same SLC SDU into one SLC SDU based on the frame header information of the SLC PDU.
  • the terminal 100 can present the SLC SDU to the MDCP layer through the interlayer interface as the MDCP PDU of the MDCP layer.
  • the terminal 100 can splice all MDCP PDUs belonging to the same MDCP SDU into one MDCP SDU.
  • the terminal 100 can present the MDCP SDU to the APP layer through the interlayer interface as an application layer message received by the APP layer.
  • the terminal 100 may decrypt and decompress the application layer message based on the message header of the application layer message to obtain original data.
  • the terminal 100 cannot use other network resources (for example, a cellular network) other than the satellite network, that is, when there is no signal, for example, when the terminal 100 is in an ocean, desert, grassland, wireless When mobile communication does not cover, or cannot cover, or areas where the communication system is damaged, such as crowded areas.
  • Terminal 100 can communicate with other terminals through a satellite network. Wherein, the terminal 100 joins the first multicast group, and the terminal 100 can send a multicast short message to other terminals in the first multicast group through the satellite network, and can also receive other terminals in the first multicast group through the satellite network. A multicast short message sent by the terminal to the terminal 100. In this way, the user can realize the transmission of multicast short messages under the satellite system through the terminal 100 .
  • network resources for example, a cellular network
  • the terminal 100 may respond to the user's input of sending a multicast short message, and in response to the input, generate an inbound multicast short message based on the text message and the multicast ID input by the user.
  • the terminal 100 may send the inbound multicast short message to the satellite network device 200, the inbound multicast short message includes a first type indication field, a multicast ID field, and the first type indication field is used to indicate the inbound multicast short message Service type, the multicast ID field is used to indicate the multicast group to which the inbound multicast short message belongs.
  • the terminal 100 may display a desktop 801 .
  • the desktop 801 may include multiple application icons, for example, the first communication application icon 803 and so on.
  • the first communication application icon 803 can be used to trigger the display of the interface of the first communication application (such as the first communication application interface 810 shown in FIG. 8B ), wherein the first communication application can be used to receive/send satellite short messages .
  • the first communication application may be short message, unlink and so on.
  • a status bar 802 may also be displayed above the desktop 801, and a prompt icon 802A may be displayed in the status bar 802.
  • the prompt icon 802A is used to indicate that the terminal 100 is disconnected from the cellular network. state.
  • the terminal 100 receives the user's input (for example, click) on the first communication application icon 803 , and in response to the input, the terminal 100 may display the first communication application interface 810 as shown in FIG. 8B .
  • the first communication application interface 810 may include a new control 811, and the new control 811 may be used to trigger the terminal 100 to display a contact selection interface.
  • the first communication application interface 810 can also display a multicast group control 812 and historical contact entries, the historical contact entries can display the information of the historical contacts and the latest message records of the historical contacts, and the historical contact entries can also display It can be used to trigger the terminal 100 to display the letter editing interface of the historical contact.
  • the multicast group control 812 may be used to trigger the terminal 100 to display a multicast group function interface (such as the multicast group function interface 820 shown in FIG. 8C ).
  • the terminal 100 receives a user's input (for example, a single click) on the multicast group control 812 , and in response to the input, the terminal 100 may display a multicast group function interface 820 .
  • the multicast group function interface may include a new control 821 , and the new control 821 may be used to trigger the terminal 100 to display a multicast group selection interface.
  • Historical multicast group entries can also be displayed in the multicast group function interface 820, and historical multicast group information and recent message records of historical multicast groups can be displayed in the historical multicast group entries. The group entry can also be used to trigger the terminal 100 to display the message editing interface of the historical multicast group.
  • the terminal 100 receives the user's input (for example, click) on the new control 821, and in response to the input, the terminal 100 may display a multicast group selection interface 830 as shown in FIG. 8D.
  • the multicast group selection interface 830 can display a multicast group display area 831 .
  • the multicast group display area 831 can display a plurality of multicast group icons, such as the multicast group icon 831A, and the multicast group icon can be used to trigger the display of the multicast group communication information corresponding to the multicast group icon Editing interface.
  • the terminal 100 receives the user's input (such as clicking) on the multicast group icon 831C, and in response to the input, the terminal 100 may display the edited multicast group information of the third group corresponding to the multicast group icon 831C. Interface 840.
  • the multicast group information editing interface 840 may include, but not limited to, an editing column 841 , a sending control 842 and the like.
  • the editing column 841 can be used to display the content of the text message input by the user.
  • the sending control 842 can be used to trigger the terminal 100 to send a multicast short message including the content of the text message displayed in the editing column 841 to the satellite network device 200 .
  • the multicast group information editing interface 840 can also display a keyboard display area 843 and more icons 844, the keyboard display area 843 can be used to input text message content, and the more icons 844 can be used to trigger the display of messages in the multicast group. User member information.
  • the terminal 100 may receive the input from the user on the keyboard display area 843 , and display the content input by the user in the editing column 841 . As shown in FIG. 8E , the terminal 100 can receive and display the text message input by the user in the editing column 841 through the keyboard display area 843 . Wherein, the text message may be "safely arrived at the camp".
  • the terminal 100 may receive user input (for example, click) on the sending control 842, and in response to the input, the terminal 100 may display a multicast group information editing interface 850 as shown in FIG. 8F.
  • the multicast group information editing interface 850 may include a multicast information box 851 .
  • the multicast information box 851 may be used to display the content in the editing column 841 sent by the user.
  • the satellite network device 200 After the satellite network device 200 receives the inbound multicast short message sent by the terminal 100, after the satellite network device 200 recognizes that the message is a multicast short message, it can parse out the multicast ID from the inbound multicast short message, and then According to the multicast ID, the multicast short message is sent to other terminals in the multicast group indicated by the multicast ID.
  • the members in the third group include the terminal 100, the terminal 200 and the terminal 300, and the satellite network device 200 sends the multicast short message to the terminal 200 and terminal 300.
  • terminal 200 or terminal 300 may display the multicast short message.
  • the user interface shown in the embodiment of the present invention does not constitute a specific limitation on the terminal 100 .
  • the terminal 100 may adopt other user interfaces.
  • the terminal 200 may display a receiving information prompt, and the receiving information prompt may be used to prompt the user to receive a multicast short message from the terminal 100 .
  • the terminal 200 may display a desktop 900 as shown in FIG. 9A .
  • the desktop 900 may include multiple application icons, for example, a first communication application icon and so on.
  • the first communication application icon may be used to trigger the display of the interface of the first communication application, wherein the first communication application may be used for receiving/sending satellite short messages.
  • the first communication application may be short message, unlink and so on.
  • a status bar 901 may also be displayed above the desktop 900, and a prompt icon 901A may be displayed in the status bar 901.
  • the prompt icon 901A is used to indicate that the terminal 200 is disconnected from the cellular network. At this time, the terminal 200 is in a state where there is no cellular signal state.
  • a prompt icon 901B may also be displayed in the display status bar 901, and the prompt icon 901B is used to prompt that the terminal 200 is within the coverage of satellite signals and can use the satellite communication system for communication.
  • a receiving information prompt 902 may also be displayed above the multiple application icons.
  • the receiving information prompt 902 may be used to prompt the user to receive a satellite multicast short message from the terminal 100 .
  • the receiving information prompt 902 may include text type prompt information: "a satellite multicast short message from the terminal 100 is received".
  • the information receiving prompt 902 may also include an application identifier 903, which may be used to indicate the application software for displaying the satellite message.
  • the application identifier 903 may be used to instruct the terminal 200 to receive the satellite multicast short message through the first communication application. That is to say, the application identifier 903 may prompt the user to view the satellite message through the first communication application.
  • the terminal 200 may display the content of the received satellite short message through the first communication application in response to the user's input (for example, single click) on receiving the information prompt 902 .
  • the terminal 200 may, after receiving the user's input (for example, click) on the receiving information prompt 902 as shown in FIG. 9A , respond to the input and display an information editing interface 910 as shown in FIG. 9B .
  • the information editing interface 910 may include an information box 911 .
  • the information box 911 may be used to display the content of the text message in the received multicast short message.
  • the information box 911 may also be used to display the sender of the multicast short message, such as the terminal 100 .
  • the information box 911 may also display the time information of sending the multicast short message, which is not shown in FIG. 9B .
  • what is shown in FIG. 9B is the fourth group of the terminal 200, that is, the third group in the terminal 100 corresponds to the fourth group in the terminal 200, which is not limited in this embodiment of the present application.
  • the user interface illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal 200 .
  • the terminal 200 may adopt other user interfaces.
  • FIG. 10A shows a schematic flow diagram of multicast short message transmission in a satellite communication system provided in an embodiment of the present application.
  • the method includes:
  • the terminal 100 generates an inbound multicast short message message based on the text information and the multicast ID.
  • the terminal 100 can use the text message and the multicast ID as original data, and obtain an application layer message based on the original data.
  • the application layer message is an inbound multicast short message message, and the terminal 100 obtains the application layer message based on the original data.
  • FIG. 4 For a detailed description of the message, reference may be made to the embodiment shown in FIG. 4 , which will not be repeated here.
  • the terminal 100 may obtain the text information and the multicast ID after receiving the user's operation as shown in Figure 8E.
  • the text information is the safe arrival at the camp
  • the multicast ID is the multicast ID corresponding to the third group selected by the user.
  • the member terminals in the third group in the terminal 100 may negotiate with the corresponding application server under the cellular network to determine the multicast ID of the third group or group virtual beam information (for example, synchronization header information), which is used to indicate the identity of the third group in the satellite communication system.
  • group virtual beam information For example, synchronization header information
  • the terminal device can identify the received physical layer data as a multicast short message message by using group virtual beam information at the physical layer.
  • the format of the inbound multicast short message message may be as shown in Table 1 below.
  • the inbound multicast short message message may include a receipt indication field, a service type field, an encryption indication field, a compression indication field, an application layer authentication code field, a multicast ID field, and a text message field.
  • the specific fields contained in the inbound multicast short message message and the sequence of the fields are not limited. For example, when an inbound multicast short message message does not require an application layer receipt by default, the inbound multicast short message message may not include a receipt indication field.
  • the receipt indication field may be used to indicate whether the receiving device (for example, the satellite network device 200 ) of the inbound multicast short message needs to reply to the terminal 200 with an application layer receipt.
  • the application layer receipt can be used to indicate whether the receiving device has successfully received the inbound multicast short message message.
  • the length of the receipt indication field may be 1 bit.
  • the return receipt indication field is a value D1 (for example, 0)
  • D2 for example, 1
  • D1 for example, 0
  • D2 for example, 1
  • the service type field may be used to indicate the service type of the inbound multicast short message message.
  • the service types of the message may include general message, multicast and multi-message query, multicast short message download and so on.
  • the length of the service type field may be 4 bits. It can be understood that, the embodiment of the present application does not limit the length of the service type field. When there are more and more types of business types, the length of the field of the business type can be longer and longer. In this embodiment of the present application, the length of the service type field is 4 bits as an example for illustration. When the service type field is 0000, it indicates that the application layer message is a general message. The meanings of other values of the service type indication field can be referred to in Table 2, and will not be repeated here. It should be noted that, in the embodiment of the present application, the service type of the inbound multicast short message message is a general message service type.
  • the encryption indication field may be used to indicate whether the inbound multicast short message is encrypted.
  • the length of the encryption indication field may be 2 bits.
  • D3 for example, 00
  • the compression indication field may be used to indicate whether the inbound multicast short message packet is compressed.
  • the length of the compression indication field may be 2 bits.
  • D4 for example, 00
  • the multicast ID field may be used to indicate the identifier of the multicast group corresponding to the inbound multicast short message.
  • the length of the multicast ID field may be 10 bits. It can be understood that, the embodiment of the present application does not limit the length of the multicast ID field.
  • the text message field can be used to indicate the content of the inbound multicast short message.
  • the length of the text message field may be Nbit. It can be understood that, the embodiment of the present application does not limit the length of the text message field.
  • the inbound multicast short message message may also include a location information field, which may be used to indicate information about the current location of the terminal 100, and the location information may include information about the current location of the terminal 100. longitude and latitude.
  • the terminal 100 may acquire the current location information of the terminal 100 based on a satellite navigation system, for example, a global navigation satellite system (global navigation satellite system, GNSS), a Beidou satellite navigation system (beidou navigation satellite system, BDS), etc.
  • the terminal 100 generates one or more first user frames based on the inbound multicast short message.
  • the terminal 100 may deliver the inbound multicast short message message to the MDCP layer through the interlayer interface.
  • the terminal 100 can segment the inbound multicast short message message into one or more MDCP PDUs at the MDCP layer.
  • the terminal 100 sends one or more MDCP PDUs to the SLC layer.
  • the terminal 100 may segment each MDCP PDU into one or more first user frames at the SLC layer.
  • the terminal 100 may fill in the identifier of the terminal 100 (for example, the mobile phone number of the terminal 100 ) in the user ID field in the frame header of each first user frame.
  • the identifier of the terminal 100 for example, the mobile phone number of the terminal 100
  • the format of the first user frame may be as shown in Table 3 below.
  • the first user frame may include a version number field, a frame type indication field, a user ID field, an outbound link indication field, an AM-Enable field, an NDI (New Data Indicator) field, a total number of frames field, a frame Serial number field, user information field and so on. It can be understood that, in the embodiment of the present application, the specific fields contained in the first user frame and the sequence of the fields are not limited.
  • the version number field is used to indicate the version of the currently used satellite communication protocol.
  • the data length of the version number field may be 3 bits. It can be understood that, the embodiment of the present application does not limit the length of the version number field. In some embodiments, the version number field may not be included in the first user frame.
  • the frame type field may be used to indicate the frame type of the first user frame.
  • the data length of the frame type field may be 3 bits.
  • the frame types may include general data frames (or information message frames), ACK frames, return receipt frames, location report frames, emergency rescue frames, multicast short message frames, and so on. It should be noted that, in the embodiment of the present application, the frame type of the first user frame is a multicast short message frame type.
  • the user ID field can be used to indicate the device identity of the terminal 100 .
  • the data length of the user ID field may be 34 bits. It can be understood that, in this embodiment of the present application, the length of the user ID field is not limited.
  • the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message.
  • the data length of the outbound link indication field may be 16 bits. It can be understood that the embodiment of the present application does not limit the length of the outbound link indication field. In some embodiments, the outbound link indication field may not be included in the first user frame.
  • the AM-Enable field is used to indicate whether the receiver needs to feed back confirmation information for the first user frame.
  • the data length of the AM-Enable field may be 1 bit.
  • the AM-Enable field is a value A1 (for example, 0)
  • A2 for example, 1
  • the AM-Enable field may not be included in the first user frame.
  • the NDI field is used to indicate whether the first user frame is a retransmission user frame.
  • the data length of the NDI field may be 1 bit. Specifically, when the NDI is reversed, it indicates that the first user frame is not a retransmission user frame. It can be understood that, the embodiment of the present application does not limit the length of the NDI field. In some embodiments, the NDI field may not be included in the first user frame.
  • the total number of frames field can be used to indicate the total number of user frames included in the SLC SDU where the first user frame is located.
  • the length of the frame total number field may be 2 bits.
  • one SLC SDU can include up to 4 position reporting frames. It can be understood that, the embodiment of the present application does not limit the length of the total number of frames field.
  • the frame sequence number field can be used to indicate the sequence of the multicast short message frame in an SLC SDU.
  • the length of the frame sequence number field may be 2 bits.
  • the user information field may be used to indicate the data content of the first user frame.
  • the data content of the first user frame is all or part of the SLC SDU. It can be understood that the embodiment of the present application does not limit the length of the user information field.
  • the frame type indication field of the first user frame is obtained by the terminal 100 at the SLC layer based on the packet service type indication sent by the APP layer, for example, the APP layer sends an inbound multicast short message through an interlayer interface message, indicating that the service type of the inbound multicast short message message is the inbound multicast short message type, then the terminal 100 sets the frame type to the multicast short message frame type at the SLC layer.
  • the terminal 100 sends one or more first user frames to the satellite network device 200.
  • the terminal 100 may send one or more first user frames to the satellite network device 200 .
  • the terminal 100 may send one or more first user frames to the satellite network device 200 .
  • the terminal 100 may generate and send the one or more first user frames to the satellite network device 200 in response to the first input.
  • the first input is not limited to single click, double click, long press, slide, voice command input and the like.
  • the first input may be the input for the send control 842 shown in FIG. 8E above.
  • the satellite network device 200 determines that the first user frame is a multicast short message frame, and obtains a multicast ID and text information based on one or more first user frames.
  • the satellite network device 200 can determine that the first user frame is a multicast short message frame based on the frame type field at the SLC layer, determine the sender ID based on the user ID field, and based on One or more first user frames get the multicast ID and text information.
  • the sender ID may be the mobile phone number of the terminal 100 .
  • the satellite network device 200 assembles one or more first user frames sent by the terminal 100 into one or more SLC SDUs at the SLC layer. Then, the satellite network device 200 uploads the one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the satellite network device 200 can assemble one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the satellite network device 200 can upload the MDCP SDU to the APP layer as an inbound multicast short message message.
  • the inbound multicast short message message includes location information
  • the satellite network device 200 can obtain the location information based on the MDCP SDU at the APP layer.
  • the first user frame includes an outbound link indication field, and the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message, and the satellite network device 200 may be based on the first A user frame gets outbound link indication information.
  • the satellite network equipment 200 includes a satellite central station 23 and a satellite short message fusion communication platform 24, and the satellite central station 23 is based on the frame type field at the SLC layer
  • the MDCP SDU is obtained based on one or more first user frames at the MDCP layer.
  • the satellite central station 23 sends the frame type of the MDCP SDU and the first user frame to the satellite short message fusion communication platform 24.
  • the satellite short message fusion communication platform 24 obtains text information and multicast ID based on the MDCP SDU at the APP layer.
  • the inbound multicast short message message includes location information
  • the satellite short message fusion communication platform 24 can also obtain the location information based on the MDCP SDU at the APP layer.
  • the first user frame includes an outbound link indication field, and the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message, and the satellite central station 23 also sends the satellite short message The converged communication platform 24 sends outbound link indication information.
  • the MDCP SDU is obtained based on one or more first user frames at the MDCP layer.
  • the satellite central station 23 sends the frame type of the MDCP SDU and the first user frame to the broadcast multicast center 29.
  • the broadcast multicast center 29 obtains the text information and the multicast ID based on the MDCP SDU at the APP layer.
  • the inbound multicast short message message includes location information, and the broadcast multicast center 29 can also obtain location information based on the MDCP SDU at the APP layer.
  • an outbound link indication field is included in the first user frame, and the outbound link indication field is used to indicate satellite information and beam information of the outbound multicast short message, and the satellite central station 23 also broadcasts to the broadcast multicast center 29 Send outbound link indication information.
  • the broadcast multicast center 29 and the location center 28 can communicate with each other.
  • the broadcast multicast center 29 can communicate with the short message center 25, and the short message center 25 can communicate with the location center 28, which is not shown in FIG. 11 .
  • the embodiment of the present application does not limit the specific connection mode.
  • the satellite network device 200 determines the target user ID based on the multicast ID in the inbound short message message, and determines satellite information and beam information of the outbound multicast short message.
  • the satellite network device 200 can obtain the multicast ID field and text information from the inbound multicast short message message.
  • the satellite network device 200 may determine the target user ID of the text message based on the multicast ID field. For example, when the satellite network device 200 determines that the multicast group corresponding to the multicast ID is the third group based on the multicast ID field, and the member information in the third group is queried as terminal 100, terminal 200 and terminal 300, then The satellite network device 200 determines that the target user ID of the text information is the user ID of the terminal 200 and the user ID of the terminal 300 .
  • the satellite network device 200 may query the location center 28 for the member terminal information of the multicast group corresponding to the multicast ID, and the location center 28 may send the member terminal information of the multicast group to the satellite network device 200 based on the multicast ID .
  • the first user frame includes an outbound link indication field
  • the satellite network device 200 determines satellite information and beam information of the outbound multicast short message based on the outbound link indication field at the SLC layer.
  • the inbound multicast short message includes location information, where the location information is the location of the terminal 100 .
  • the satellite network device 200 determines satellite information and beam information of the outbound multicast short message based on the location information. Specifically, the satellite network device 200 may generate a circle with the location of the terminal 100 as the center and the first length as the radius, and the satellites and beams within the circle are determined as the satellite information and beam information of the outbound multicast short message.
  • the first length may be 10 kilometers, and this embodiment of the present application does not limit the specific value of the first length.
  • the satellite network device 200 may request the location center 28 for the location information of the terminal 100 .
  • the satellite network device 200 can send the user ID information of the terminal 100 to the location center 28, and the location center 28 sends the location information of the terminal 100 to the satellite network device 200 after querying the location information of the terminal 100 according to the user ID of the terminal 100.
  • the satellite network device 200 determines satellite information and beam information of the outbound multicast short message based on the location information. For a specific determination manner, reference may be made to the description of the foregoing embodiments, and details are not repeated here.
  • the satellite network device 200 may request the location information of the terminal 100 from the location center 28 in response to receiving the inbound multicast short message.
  • the satellite network device 200 may periodically request the location center 28 for the location information of the terminal 100, and store the obtained location information of the terminal 100 locally.
  • the satellite network device 200 requests the location center 28 for the location information of the terminal 100, and instructs the location center 28 to send the location information of the terminal 100 to the satellite network device 200 when the location of the terminal 100 changes.
  • the satellite network device 200 saves the obtained location information of the terminal 100 locally.
  • the satellite network equipment 200 includes a satellite central station 23 and a satellite short message fusion communication platform 24, and the satellite short message fusion communication platform 24 receives the satellite After the MDCP SDU and the frame type of the first user frame sent by the central station 23, the satellite short message fusion communication platform 24 obtains the multicast ID field and text information based on the MDCP SDU at the APP layer.
  • the satellite short message fusion communication platform 24 can determine the target user ID of the text message based on the multicast ID field. For a specific determination manner, reference may be made to the description of the foregoing embodiments, and details are not repeated here.
  • the first user frame includes an outbound link indication field
  • the satellite central station 23 obtains the outbound link indication field based on the first user frame at the SLC layer, and sends the outbound link indication field to the satellite Short message fusion communication platform24.
  • the satellite short message fusion communication platform 24 determines satellite information and beam information of the outbound multicast short message based on the outbound link indication field.
  • the satellite central station 23 obtains the outbound link indication field based on the first user frame at the SLC layer, and determines the satellite information and the outbound multicast short message based on the outbound link indication field. beam information.
  • the satellite central station 23 sends the satellite information and beam information to the satellite short message fusion communication platform 24 .
  • the inbound multicast short message includes location information
  • the satellite short message fusion communication platform 24 obtains the location information based on the MDCP SDU at the APP layer.
  • the satellite short message fusion communication platform 24 determines the satellite information and beam information of the outbound multicast short message based on the location information.
  • the satellite short message fusion communication platform 24 may send a location query request to the location center 28 through the short message center 25, and the location query request is used to query the location information of the terminal 100.
  • the satellite short message fusion communication platform 24 can send the user ID information of the terminal 100 to the location center 28.
  • the location center 28 inquires the position information of the terminal 100 according to the user ID of the terminal 100, it sends the terminal to the satellite short message fusion communication platform 24. 100's of location information.
  • the satellite short message fusion communication platform 24 determines the satellite information and beam information of the outbound multicast short message based on the location information.
  • For a specific manner of determining satellite information and beam information reference may be made to the description of the foregoing embodiments, and details are not repeated here.
  • a specific location request manner reference may be made to the description of the foregoing embodiments, which will not be repeated here.
  • the satellite network equipment 200 includes a satellite central station 23, a satellite short message fusion communication platform 24 and a broadcast multicast center 29, and the broadcast multicast center 29
  • the broadcast multicast center 29 After receiving the MDCP SDU sent by the satellite central station 23 and the frame type of the first user frame, the broadcast multicast center 29 obtains the multicast ID field and text information based on the MDCP SDU at the APP layer.
  • the broadcast multicast center 29 may determine the target user ID of the text message based on the multicast ID field. For a specific determination manner, reference may be made to the description of the foregoing embodiments, and details are not repeated here.
  • the first user frame includes an outbound link indication field
  • the satellite central station 23 obtains the outbound link indication field based on the first user frame at the SLC layer, and sends the outbound link indication field to the broadcast Multicast Center 29.
  • the broadcast multicast center 29 determines satellite information and beam information of the outbound multicast short message based on the outbound link indication field.
  • the satellite central station 23 obtains the outbound link indication field based on the first user frame at the SLC layer, and determines the satellite information and the outbound multicast short message based on the outbound link indication field. beam information.
  • the satellite central station 23 sends the satellite information and beam information to the broadcast multicast center 29 .
  • the inbound multicast short message includes location information
  • the broadcast multicast center 29 obtains the location information based on the MDCP SDU at the APP layer.
  • the broadcast multicast center 29 determines satellite information and beam information of the outbound multicast short message based on the location information.
  • the broadcast multicast center 29 may request the location center 28 for the location information of the terminal 100 .
  • the broadcast multicast center 29 can send the user ID information of the terminal 100 to the location center 28, and the location center 28 sends the location information of the terminal 100 to the broadcast multicast center 29 after inquiring the location information of the terminal 100 according to the user ID of the terminal 100.
  • the broadcast multicast center 29 determines satellite information and beam information of the outbound multicast short message based on the location information. For a specific manner of determining satellite information and beam information, reference may be made to the description of the foregoing embodiments, and details are not repeated here. For a specific location request manner, reference may be made to the description of the foregoing embodiments, which will not be repeated here.
  • the satellite network device 200 generates an outbound multicast short message message based on the text information and the multicast ID.
  • the satellite network device 200 may use the text information, the sender ID and the multicast ID as original data, and obtain an application layer message based on the original data, and the application layer message is an outbound multicast short message message.
  • the satellite network equipment 200 includes a satellite central station 23 and a satellite short message fusion communication platform 24, and the satellite short message fusion communication platform 24 is at the APP layer
  • the text message, the sender's user ID and the multicast ID are used as original data, and an application layer message is obtained based on the original data, and the application layer message is an outbound multicast short message message.
  • the satellite network equipment 200 includes a satellite central station 23, a satellite short message fusion communication platform 24 and a broadcast multicast center 29, and the broadcast multicast center 29
  • the text message, the user ID of the sender and the multicast ID are used as original data, and an application layer message is obtained based on the original data, and the application layer message is an outbound multicast short message message.
  • the format of the outbound multicast short message message is shown in Table 5.
  • the multicast short message message may include a message type indication field, a multicast short message download completion indication field, an encryption indication field, a compression indication field, an application layer authentication code field, a multicast group number field, Multicast ID field, sender ID field, message original sending time field, multicast short message content field, multicast short message ID field.
  • the specific fields contained in the multicast short message message and the sequence of the fields are not limited. For example, if the multicast short message is not encrypted, the multicast short message may not include an encryption indication field.
  • Table 6 exemplarily shows the lengths corresponding to the fields in Table 5 and specific descriptions.
  • the message type indication field may be used to indicate the message type of the outbound multicast short message message.
  • the message type of the message may include mailbox overview, letter message, multicast short message query result, multicast short message and so on.
  • the length of the message type indication field may be 2 bits. It can be understood that the embodiment of the present application does not limit the length of the message type indication field. When there are more and more types of message types, the length of the message type indication field may be longer and longer. In this embodiment of the present application, the length of the message type indication field is 2 bits as an example for illustration. When the message type indication field is 00, it indicates that the application layer message is a message summary message. The meanings of other values of the message type indication field can be referred to in Table 6, and will not be repeated here. It should be noted that, in the embodiment of the present application, the message type of the outbound multicast short message is a multicast short message type.
  • the multicast short message download completion indication field may be used to indicate whether there is a multicast short message to be sent to the terminal 200 subsequently.
  • the length of the multicast short message download completion indication field may be 1 bit.
  • M1 for example, 1
  • M2 for example, 0
  • M2 for example, 0
  • the embodiment of the present application does not limit the length and specific value of the download completion indication field of the multicast short message. It should be noted that the outbound multicast short message message may not include the download completion indication field of the multicast short message.
  • the multicast ID may be used to indicate the ID of the multicast group corresponding to the multicast short message message.
  • the data length of the multicast ID may be 10 bits. It can be understood that, in this embodiment of the present application, the length of the multicast ID field is not limited.
  • the sender ID field may be used to indicate the identity of the target terminal sending the multicast short message.
  • the sender ID field may be a 34-bit identifier of the target terminal (such as a mobile phone number). It can be understood that, in this embodiment of the present application, the length of the sender ID field and the specific value of the sender ID field are not limited.
  • the original sending time field of the multicast short message is used to indicate the original sending time of the multicast short message, that is, the time when the target terminal sends the multicast short message.
  • the length of the original sending time field of the multicast short message may be 7 bits. It can be understood that the embodiment of the present application does not limit the length of the original sending time field of the multicast short message.
  • the multicast short message ID field is used to indicate the ID of the multicast short message.
  • the length of the ID field of the multicast short message may be 4 bits. It can be understood that the embodiment of the present application does not limit the length of the ID field of the multicast short message.
  • the content field of the multicast short message may be used to indicate the content of the multicast short message sent to the terminal 200 by the target multicast group.
  • the length of the content field of the multicast short message may be Nbit. It can be understood that, in this embodiment of the present application, the length of the content field of the multicast short message is not limited.
  • the subscribing service may be provided by the application server, and in this case, the execution starts directly from S1006.
  • the application server may send the text information and the multicast ID to the satellite network device 200 .
  • the sender ID field may not be included in the outbound multicast short message message.
  • the satellite network device 200 segments the outbound multicast short message into one or more second user frames.
  • the satellite network device 200 may deliver the outbound multicast short message message and the target user ID to the MDCP layer.
  • the satellite network device 200 can segment the outbound multicast short message message into one or more MDCP PDUs at the MDCP layer.
  • the satellite network device 200 sends one or more MDCP PDUs to the SLC layer as SLC SDUs of the SLC layer, and sends the target user ID to the SLC layer.
  • Satellite network device 200 may segment each SLC SDU into one or more second user frames at the SLC layer.
  • the satellite network device 200 may fill in the target user ID in the user ID field of each second user frame.
  • the frame type of the one or more second user frames is a general data frame type.
  • the satellite network equipment 200 includes a satellite central station 23 and a satellite short message fusion communication platform 24, and the satellite short message fusion communication platform 24 can send out
  • the station multicasts the short message message and the target user ID and sends it to the satellite central station 23.
  • the satellite central station 23 segments the outbound multicast short message into one or more second user frames.
  • the satellite network equipment 200 includes a satellite central station 23, a satellite short message fusion communication platform 24 and a broadcast multicast center 29, and the broadcast multicast center 29 Send the outbound multicast short message message and the target user ID to the satellite central station 23.
  • the satellite central station 23 segments the outbound multicast short message into one or more second user frames.
  • the satellite network device 200 sends one or more second user frames to the target user.
  • the satellite network device 200 may use the satellite information and beam information determined in S1005 to send one or more second user frames to the target user. Specifically, the satellite network device 200 may send a second user frame, and then send a second second user frame to the target user after receiving a reply from the target user that the second user frame has been successfully received. Optionally, the satellite network device 200 may also sequentially send one or more second user frames to the target user, and the target user replies to the satellite network device 200 after receiving all the second user frames and successfully receives the second user frame. frame. Alternatively, the target user may not reply. This embodiment of the present application does not limit it.
  • the outbound multicast short message message is an outbound multicast short message message sent to a specific target terminal.
  • the satellite network device 200 cyclically executes S1007 and S1008 N times.
  • the group described in the multicast ID is the third group, and the third group includes terminal 100, terminal 200 and terminal 300
  • the satellite network device 200 takes terminal 200 and terminal 300 as target users to perform S1007 and S1008 respectively .
  • the target user is the terminal 200 as an example for description.
  • the terminal 200 receives one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • reference may be made to the description of the embodiment shown in FIG. 7 , which will not be repeated here.
  • the terminal 200 After the terminal 200 has received all the one or more second user frames, it replies to the satellite network device 200 that the one or more second user frames have been received.
  • the terminal 200 may parse out the user ID field in the frame header of each second user frame at the SLC layer. If the user ID parsed by the terminal 200 from the user ID field is the same as the identifier of the terminal 200, the terminal 200 uploads the one or more second user frames to the MDCP layer for further analysis. If the user ID parsed by the terminal 200 from the user ID field is different from the identifier of the terminal 200, the terminal 200 may determine that the second user frame is not sent to the terminal 200, and the terminal 200 may discard the second user frame.
  • the terminal 200 assembles one or more second user frames into an outbound multicast short message message.
  • the terminal 200 may assemble one or more second user frames into one or more SLC SDUs at the SLC layer. Then, the terminal 200 uploads one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the terminal 200 can combine one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the terminal 200 can upload the MDCP SDU to the APP layer as an outbound multicast short message message.
  • the terminal 200 parses the content of the multicast short message sent by the terminal 100 to the terminal 200 in the outbound multicast short message message.
  • the terminal 200 can obtain the multicast ID field, the sender ID field, the multicast short message content field, etc. based on the multicast short message message at the APP layer, so as to determine the multicast group and sender corresponding to the multicast short message.
  • the terminal 200 displays the content of the multicast short message sent by the terminal 100 to the terminal 200.
  • the terminal 200 may display the content of the multicast short message sent to the terminal 200 by the target multicast group on the display screen.
  • the sender ID is the user ID of the terminal 100
  • the multicast group indicated by the multicast ID is the fourth group in the terminal 200
  • the terminal 100 will use the first communication application to display in the fourth group
  • the sender of the content of the letter is the terminal 100 , as shown in FIG. 9B .
  • the terminal 200 may also prompt the user in other forms for the content of the short message sent to the terminal 200 by the target multicast group.
  • the terminal 200 voice broadcasts the content of the letter sent to the terminal 200 by the target multicast group.
  • the display form of is not limited.
  • the terminal 100 is under the satellite network and does not reside in the cellular network, and can also broadcast to other members of the target multicast group through the satellite network.
  • the terminal sends a multicast short message.
  • FIG. 12A shows a schematic flow diagram of multicast short message transmission in another satellite communication system provided in the embodiment of the present application.
  • the method includes:
  • the terminal 100 generates an inbound multicast short message message based on the text information and the multicast ID.
  • the format of the inbound multicast short message message can refer to Table 1, and will not be repeated here.
  • the value of the service type field in the inbound multicast short message message may be 1011, which is used to indicate that the service type of the inbound multicast short message message message is multiple
  • the broadcast short message type that is, in the embodiment of the present application, the service type indication field is used to indicate that the application layer message is an inbound multicast short message message.
  • the terminal 100 generates one or more first user frames based on the inbound multicast short message.
  • the format of the first user frame may refer to Table 3, which will not be repeated here.
  • the value of the frame type field of the first user frame is 0000, which is used to indicate that the first user frame is a general data frame.
  • the terminal 100 sends one or more first user frames to the satellite network device 200.
  • the satellite network device 200 determines, based on the service type indication field, that the received application layer message is an inbound multicast short message.
  • the satellite network device 200 can obtain the MDCP SDU based on one or more first user frames at the SLC layer and the MDCP layer.
  • the satellite network device 200 can upload the MDCP SDU to the APP layer, and use it as an application layer message of the APP layer, that is, an inbound multicast short message message.
  • the inbound multicast short message message includes a service type indication field, and the satellite network device 200 determines that the application layer message is an inbound multicast short message message based on the type indication field.
  • the inbound multicast short message message includes location information, and the satellite network device 200 can obtain the location information based on the MDCP SDU at the APP layer.
  • the first user frame includes an outbound link indication field, and the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message, and the satellite network device 200 may be based on the first A user frame gets outbound link indication information.
  • the satellite network equipment 200 includes a satellite central station 23 and a satellite short message fusion communication platform 24, and the satellite central station 23 is based on the SLC layer and the MDCP layer One or more first user frames get MDCP SDUs.
  • the satellite central station 23 sends the MDCP SDU to the satellite short message fusion communication platform 24 as an application layer message.
  • the satellite short message fusion communication platform 24 obtains the service type indication field, text information and multicast ID based on the application layer message at the APP layer.
  • the satellite short message fusion communication platform 24 determines that the application layer message is an inbound multicast short message message based on the service type indication field.
  • the inbound multicast short message message includes location information
  • the satellite short message fusion communication platform 24 can also obtain the location information based on the MDCP SDU at the APP layer.
  • the first user frame includes an outbound link indication field, and the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message, and the satellite central station 23 also sends the satellite short message The converged communication platform 24 sends outbound link indication information.
  • the SLC layer and the MDCP layer obtain the MDCP SDU based on one or more first user frames.
  • the satellite central station 23 sends the MDCP SDU to the satellite short message fusion communication platform 24 as an application layer message.
  • the satellite short message fusion communication platform 24 obtains the service type indication field, text information and multicast ID based on the application layer message at the APP layer.
  • the satellite short message fusion communication platform 24 determines that the application layer message is an inbound multicast short message message based on the service type indication field, and sends the service type indication field, text information and multicast ID to the broadcast multicast center 29.
  • the inbound multicast short message message includes location information
  • the satellite short message fusion communication platform 24 can also obtain the location information based on the MDCP SDU at the APP layer, and sends the location information to the broadcast and multicast center 29.
  • the broadcast multicast center 29 and the location center 28 can communicate with each other.
  • the broadcast multicast center 29 can communicate with the short message center 25, and the short message center 25 can communicate with the location center 28, which is not shown in FIG. 13 .
  • the embodiment of the present application does not limit the specific connection mode.
  • the satellite short message fusion communication platform 24 determines that the application layer message is an inbound multicast short message message based on the service type indication field, and can send the MDCP SDU to the broadcast multicast center 29.
  • the broadcast multicast center 29 obtains the service type indication field, text information and multicast ID at the APP layer based on the application layer message.
  • the inbound multicast short message message includes location information, and the broadcast multicast center 29 can obtain the location information based on the application layer message at the APP layer.
  • the first user frame includes an outbound link indication field, and the outbound link indication field is used to indicate the satellite information and beam information of the outbound multicast short message, and the satellite central station 23 also sends the satellite short message
  • the converged communication platform 24 sends the outbound link indication information, and the satellite short message converged communication platform 24 sends the outbound link indication information to the broadcast multicast center 29 .
  • the satellite network device 200 determines the target user ID based on the multicast ID in the inbound short message message, and determines satellite information and beam information of the outbound multicast short message.
  • the satellite network device 200 generates an outbound multicast short message message based on the text information and the multicast ID.
  • the subscription service when the multicast ID indicates the multicast group of the subscription service, the subscription service may be provided by the application server, and in this case, the execution starts from S1206 directly.
  • the application server may send the text information and the multicast ID to the satellite network device 200 .
  • the satellite network device 200 segments the outbound multicast short message into one or more second user frames.
  • the satellite network device 200 sends one or more second user frames to the target user.
  • the target user is the terminal 200 as an example for description.
  • the terminal 200 receives one or more second user frames.
  • the terminal 200 assembles one or more second user frames into an outbound multicast short message message.
  • the terminal 200 parses the content of the multicast short message sent from the terminal 100 to the terminal 200 in the outbound multicast short message message.
  • the terminal 200 displays the content of the multicast short message sent by the terminal 100 to the terminal 200.
  • the multicast group has agreed in advance the time point for sending outbound multicast short messages, and the satellite short message fusion communication platform 24 or the broadcast multicast center 29 and the member terminals in the multicast group have all saved Time point information for sending the outbound multicast short message.
  • S1006 and S1206 in the embodiment of the present application may be replaced with S1006A.
  • S1009A is also included.
  • the satellite network device 200 generates an outbound multicast short message message based on the text information and the multicast ID according to the time point information for sending the outbound multicast short message.
  • the satellite network device 200 obtains the time point information of the outbound multi-message transmission agreed in advance by the corresponding multicast group according to the multicast ID.
  • the multicast group corresponding to the multicast ID is the third group in the terminal 100
  • the time point for sending the outbound multicast short message agreed in advance by the third group in the terminal 100 is the hour, such as 13:00 etc.
  • the satellite network device 200 may generate an outbound multicast short message message based on the text information and the multicast ID at time 13:00.
  • the specific generation process of the outbound multicast short message message reference may be made to the description of the above embodiment, and details are not repeated here.
  • the terminal 200 performs a satellite alignment operation according to the time point information sent by the outbound multicast short message, and completes the acquisition of satellite signals to realize synchronization with the satellite system.
  • the terminal 200 may start the satellite alignment operation at a time that is the first duration before the sending time of the outbound multicast short message.
  • the multicast group corresponding to the multicast ID is the third group in the terminal 100, and the time point for sending outbound multi-messages agreed in advance by the third group in the terminal 100 is the hour, such as 13:00, etc. wait.
  • the terminal 200 may start the satellite alignment operation at 12:55.
  • the terminal 200 may receive notification information at 12:55, and the user performs a satellite alignment operation according to the notification information.
  • the notification information includes text notification information or voice notification information, which is not limited in this embodiment of the present application.
  • the multicast group has agreed on the time point (comprising the sending time point and the receiving time point) of the multicast short message transmission in advance, and the satellite short message fusion communication platform 24 or the broadcast multicast center 29 and the multicast group
  • the member terminals in the group all save the time point information of the multicast short message transmission.
  • S1001 and S1201 can be replaced with S1001A.
  • S1006 and S1206 in the embodiment of the present application may be replaced with S1006B.
  • S1009B is also included.
  • the terminal 100 generates an inbound multicast short message message based on the text information and the multicast ID according to the time point information of the multicast short message transmission.
  • the terminal 100 obtains the time point information of the multicast short message transmission agreed in advance by the corresponding multicast group according to the multicast ID.
  • the multicast group corresponding to the multicast ID is the third group in the terminal 100, and the time point for the transmission of the multicast short message agreed in advance by the third group in the terminal 100 is the hour, such as 13:00, etc. wait.
  • the terminal 100 may generate an inbound multicast short message message based on the text information and the multicast ID at the time point 13:00.
  • the terminal 100 may cache the multicast short message after receiving the user's multicast short message sending operation, and automatically generate the inbound multicast short message at the agreed time point of multicast short message transmission. message message.
  • the terminal 100 may start the satellite alignment operation at a time that is a first duration away from the multicast short message transmission time point.
  • the multicast group corresponding to the multicast ID is the third group in the terminal 100, and the multicast short message transmission time agreed in advance by the third group in the terminal 100 is the hour, such as 13:00, etc. .
  • the terminal 100 may start the satellite alignment operation at 12:55.
  • the terminal 100 may receive notification information at 12:55, and the user performs a satellite alignment operation according to the notification information.
  • the notification information includes text notification information or voice notification information, which is not limited in this embodiment of the present application.
  • the satellite network device 200 generates an outbound multicast short message message based on the text information and the multicast ID according to the time point information of the multicast short message transmission.
  • the terminal 200 performs a satellite alignment operation according to the time point information transmitted by the multicast short message, and completes the acquisition of satellite signals to realize synchronization with the satellite system.
  • the terminal 200 may actively query to obtain the time point information of the outbound multicast short message transmission or the time point information of the multicast short message transmission. Specifically, the terminal 200 may send a multicast period query request message to the satellite network device 200, where the multicast period query request message carries the multicast ID information. The satellite network device 200 generates a multicast period query result message based on the multicast ID, and sends the multicast period query result message to the terminal 200 .
  • the second user frame is a multicast user frame
  • the multicast ID corresponding to the second user frame may be indicated in the second user frame.
  • S1006 and S1206 can be replaced with S1006C.
  • S1007 and S1207 can be replaced with S1007A.
  • S1009 and S1209 can be replaced with S1009C.
  • S1010 and S1210 can be replaced with S1010A.
  • S1011 and S1211 can be replaced with S1011A.
  • the specific process can refer to FIG. 10B and FIG. 12B.
  • the satellite network device 200 generates an outbound multicast short message message based on the text information.
  • the satellite network device 200 may use the text information and the sender ID as original data, and obtain an application layer message based on the original data, where the application layer message is an outbound multicast short message message.
  • the format of the outbound multicast short message message is as shown in Table 5 above, and the specific description of each field can refer to the description of S1006, which will not be repeated here.
  • the outbound multicast short message message may not include a message type indication field.
  • the outbound multicast short message message may include a message type indication field, and the message type indication field may take a value of 11, which is used to indicate that the application layer message is an outbound multicast short message message. This embodiment of the present application does not limit it.
  • the outbound multicast short message message may not include a multicast ID field.
  • the satellite network device 200 segments the outbound multicast short message into one or more second user frames.
  • the satellite network device 200 may deliver the outbound multicast short message message and the multicast ID to the MDCP layer, and indicate that the type of the outbound multicast short message message is an outbound multicast short message type.
  • the satellite network device 200 can segment the outbound multicast short message message into one or more MDCP PDUs at the MDCP layer. Then, the satellite network device 200 sends one or more MDCP PDUs to the SLC layer as the SLC SDU of the SLC layer, and sends the multicast ID and the type of the outbound multicast short message message to the SLC layer.
  • Satellite network device 200 may segment each SLC SDU into one or more second user frames at the SLC layer.
  • the satellite network device 200 may fill in the frame type of the multicast short message in the frame type indication field of each second user frame, and fill in the multicast ID in the multicast ID field.
  • the process of the satellite network device 200 segmenting the outbound multicast short message into one or more second user frames reference may be made to the specific description in FIG. 6 , which will not be repeated here.
  • the format of the second user frame is shown in Table 7.
  • the second user frame may include a frame type field, a frame length field, a multicast ID field, a frame total number field, a frame sequence number field, a user information field, and the like.
  • the second user frame further includes an AM-Enable field.
  • the frame type field may be used to indicate the frame type of the second user frame.
  • the data length of the frame type field may be 2 bits.
  • Frame types may include general data frames (or information message frames), ACK frames, receipt frames, multicast short message frames, and so on.
  • the frame type of the second user frame is a multicast short message frame type. It can be understood that, the embodiment of the present application does not limit the length of the frame type field.
  • the frame length field may be used to indicate the data length of the user information in the second user frame.
  • the data length of the frame length field may be 8 bits or 9 bits. It can be understood that the embodiment of the present application does not limit the length of the frame length field.
  • the multicast ID field is used to indicate the ID of the multicast group corresponding to the second user frame.
  • the data length of the multicast ID field may be 10 bits. It can be understood that, in this embodiment of the present application, the length of the multicast ID field is not limited.
  • the total number of frames field can be used to indicate the total number of user frames included in the SLC SDU where the second user frame is located.
  • the length of the frame total number field may be 2 bits.
  • one SLC SDU can include up to 4 position reporting frames. It can be understood that, the embodiment of the present application does not limit the length of the total number of frames field.
  • the frame sequence number field can be used to indicate the sequence of the multicast short message frame in an SLC SDU.
  • the length of the frame sequence number field may be 2 bits.
  • the user information field may be used to indicate the data content of the second user frame. It can be understood that the embodiment of the present application does not limit the length of the user information field.
  • the format of the second user frame is shown in Table 9.
  • the second user frame may include a frame type field, a frame length field, a broadcast multicast indication field, a multicast ID field, a total number of frames field, a frame sequence number field, a user information field, and the like.
  • each field in the second user frame shown in Table 9 may be as shown in Table 8 above. It should be noted that, when the value of the frame type field is 11, it indicates that the second user frame is a broadcast-multicast user frame.
  • the second user frame also includes a broadcast multicast indication field and a broadcast multicast ID field.
  • the length of the broadcast-multicast indication field may be 1 bit.
  • the broadcast and multicast indication field is a value C1 (for example, 0), it can be used to indicate that the second user frame is a multicast short message frame, and the broadcast and multicast ID field is used to indicate the multicast ID information; when the When the broadcast-multicast indication field is a value C2 (for example, 1), it can be used to indicate that the second user frame is a broadcast short message frame, and at this time, the broadcast-multicast ID field is used to indicate broadcast ID information.
  • the terminal 200 receives one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • reference may be made to the description of the embodiment shown in FIG. 7 , which will not be repeated here.
  • the terminal 200 determines that the second user frame is a multicast short message frame based on the frame type field, and determines the ID of the multicast group corresponding to the second user frame based on the multicast ID field.
  • the terminal 200 determines that the second user frame is a broadcast multicast short message frame based on the frame type field. Further, the terminal 200 determines that the second user frame is a multicast short message frame based on the broadcast multicast indication field.
  • the terminal 200 may determine whether the second user frame is sent to the terminal 200 based on the multicast ID field. If it is determined that the ID of the multicast group belongs to the multicast group of the terminal 200, it can be determined that the second user frame is sent to the terminal 200, and the terminal 200 uploads the one or more second user frames to the MDCP layer to continue Analysis; if it is determined that the ID of the multicast group does not belong to the multicast group of the terminal 200, it can be determined that the second user frame is not sent to the terminal 200, and the terminal 200 can discard the second user frame.
  • the terminal 200 assembles one or more second user frames into an outbound multicast short message message.
  • the terminal 200 may assemble one or more second user frames into one or more SLC SDUs at the SLC layer. Then, the terminal 200 uploads one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer, and sends the multicast ID to the MDCP layer. Then, the terminal 200 can combine one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the terminal 200 can upload the MDCP SDU to the APP layer as an outbound multicast short message message, and send the multicast ID to the APP layer.
  • the terminal 200 parses the content of the multicast short message sent by the terminal 100 to the terminal 200 in the outbound multicast short message message.
  • the terminal 200 can obtain the sender ID field and the multicast short message content field, etc. based on the multicast short message message at the APP layer, and obtain the multicast ID from the MDCP layer, thereby determining the multicast group corresponding to the multicast short message and sender.
  • the satellite network device 200 may indicate in the second user frame that the second user frame is a multicast user frame, and indicate a multicast ID in the second user frame. In this way, the satellite network device 200 only needs to send the outbound multicast short message once, and all member terminals in the multicast group can receive the outbound multicast short message.
  • the terminal 100 may also receive one or more second user frames, and the second user frames do not include a user ID field.
  • the terminal 100 cannot determine whether one or more second user frames are sent to the terminal 100 through the user ID field.
  • the terminal 100 may obtain the outbound multicast short message message based on one or more second user frames, and obtain the sender ID field based on the outbound multicast short message message. Based on the fact that the user ID indicated by the sender ID field is the same as the user ID of the terminal 100, the terminal 100 may discard the outbound multicast short message message.
  • the multicast group to which the outbound multicast short message message belongs is a multicast group of a subscription service, and the subscription service may be provided by an application server.
  • the execution starts directly from S1006C.
  • the application server can send the text information and the multicast ID to the satellite network device 200 . It should be noted that the sender ID field may not be included in the outbound multicast short message message.
  • the outbound multicast short message message can be deleted immediately, without Waiting for other multicast members in the multicast group to feed back confirmation messages for receiving outbound multicast short message messages.
  • the outbound multicast short message message sent by the satellite short message fusion communication platform 24 or the broadcast multicast center 29 to the satellite central station 23 carries a return receipt indication field.
  • the return receipt indication field is used to instruct other multicast members in the multicast group to reply a confirmation message to the satellite short message fusion communication platform 24 or the broadcast multicast center 29 when they successfully receive the outbound multicast short message.
  • the outbound multicast short message message can be deleted, otherwise it needs to continue Cache the outbound multicast short message message.
  • the multicast members in the multicast group can query or download cached unreceived multicast short messages from the satellite short message fusion communication platform 24 or the broadcast multicast center 29 .
  • Fig. 14 shows a schematic flowchart of a method for querying the number of multicast short messages in a satellite communication system provided in an embodiment of the present application.
  • the embodiment of the present application takes the terminal 200 to query the number of multicast messages as an example.
  • the method for querying the number of multicast short messages in a satellite communication system provided by the embodiment of the present application may include the following steps:
  • the terminal 200 generates a multicast short message query request message based on user operations, and the user of the multicast short message query request message queries the number of multicast short messages sent to the terminal 200 by a specified multicast group or all multicast groups .
  • the terminal 200 is under the satellite network, that is, the terminal 200 is in a scenario without a cellular network and a wireless local area network, and the terminal 200 is not camped on the cellular network.
  • the terminal 200 can query the designated multicast group or all multicast groups through the satellite network to send The number of multicast short messages to the terminal 200.
  • control 1 can be used to query the number of multicast short messages sent to the terminal 200 by a specified multicast group.
  • Control 2 can be used to query the number of multicast short messages sent to the terminal 200 by all multicast groups.
  • the format of the multicast short message query request message may be as shown in Table 10 below.
  • the multicast short message query request message may include a return receipt indication field, a business type field, an encryption indication field, a compression indication field, an application layer authentication code field, a multicast ID field, and a multicast short message ID field .
  • the specific fields contained in the multicast short message query request message and the sequence of the fields are not limited.
  • the multicast short message query request message may not include a receipt indication field.
  • the return receipt indication field may be used to indicate whether the receiving device (such as the satellite network device 200 ) of the multicast short message query request message needs to reply to the terminal 200 with an application layer return receipt.
  • the application layer receipt can be used to indicate whether the receiving device has successfully received the multicast short message query request message.
  • the length of the receipt indication field may be 1 bit.
  • the return receipt indication field is a value D1 (for example, 0), it can be used to indicate that the receiving device of the multicast short message query request message does not need to return an application layer return receipt to the terminal 200 .
  • the return receipt indication field is a value D2 (for example, 1), it can be used to indicate that the receiving device of the multicast short message query request message needs to reply an application layer return receipt to the terminal 200 . It can be understood that the embodiment of the present application does not limit the length of the return receipt indication field and the specific value of the return receipt indication field.
  • the service type field may be used to indicate the service type of the multicast short message query request message.
  • the service types of the message may include general message, multicast and multi-message query, multicast short message download and so on.
  • the length of the service type field may be 4 bits. It can be understood that, the embodiment of the present application does not limit the length of the service type field. When there are more and more types of business types, the length of the field of the business type can be longer and longer. In this embodiment of the present application, the length of the service type field is 4 bits as an example for illustration. When the service type field is 0000, it indicates that the service type of the application layer message is a general message.
  • the service type field When the service type field is 0111, it indicates that the application layer message is a multicast short message query request message, and what the multicast short message query request message queries is the multicast short message sent by the designated multicast group quantity.
  • the service type field When the service type field is 1000, it indicates that the application layer message is a multicast short message query request message, and what the multicast short message query request message queries is the information of the multicast short messages sent by all multicast groups. quantity.
  • the service type field When the service type field is 1001, it indicates that the application layer message is a multicast short message download request message, and what the multicast short message download request message downloads is the multicast short message sent by the designated multicast group quantity.
  • the service type field When the service type field is 1010, it indicates that the application layer message is a multicast short message download request message, and the download of the multicast short message download request message is the multicast short message sent by all multicast groups quantity.
  • the meanings of other values of the service type indication field can be referred to in Table 2, and will not be repeated here.
  • the encryption indication field may be used to indicate whether the multicast short message query request message is encrypted.
  • the length of the encryption indication field may be 2 bits.
  • D3 for example, 00
  • the compression indication field may be used to indicate whether the multicast short message query request message is compressed.
  • the length of the compression indication field may be 2 bits.
  • D4 for example, 00
  • the multicast ID field may be used to indicate the identification of the specified multicast group for the number of multicast short messages sent to the terminal 200 to be queried or downloaded by the terminal 200 .
  • the length of the multicast ID field may be 10 bits. It can be understood that, the embodiment of the present application does not limit the length of the multicast ID field.
  • the service type field is 0111
  • what the multicast short message query request message inquires is the quantity of the multicast short messages sent by the specified multicast group, therefore, in the multicast short message query request message, Include this multicast ID field;
  • the business type field is 1000
  • what this multicast short message inquiry request message inquired about is the quantity of the multicast short message that all multicast groups send, so this multicast short message download request report
  • the text may not include the multicast ID field, or may include the multicast ID field, which is not limited in this embodiment of the present application.
  • the multicast short message ID field may be used to indicate the ID of the last multicast short message among the multicast short messages successively and successfully received by the terminal 200 .
  • the ID of the multicast short message successfully received by the terminal 200 is 1, 2, 3, 5, then the multicast short message ID field is filled with 3 .
  • the multicast short message query request message queries the number of multicast short messages sent by all multicast groups, the multicast short message query request message may not include the multicast short message ID field.
  • the terminal 200 segments the multicast short message query request packet into one or more first user frames.
  • the terminal 200 may send the multicast short message query request message to the MDCP layer through the interlayer interface.
  • the terminal 200 can segment the multicast short message query request message into one or more MDCP PDUs at the MDCP layer.
  • the terminal 200 sends one or more MDCP PDUs to the SLC layer.
  • the terminal 200 may segment each MDCP PDU into one or more first user frames at the SLC layer.
  • the terminal 200 may fill in the identifier of the terminal 200 (for example, the mobile phone number of the terminal 200 ) in the user ID field in the frame header of each first user frame.
  • the identifier of the terminal 200 for example, the mobile phone number of the terminal 200
  • the terminal 200 sends one or more first user frames to the satellite network device 200.
  • the terminal 200 may send one or more first user frames to the satellite network device 200 .
  • the terminal 200 may send one or more first user frames to the satellite network device 200 .
  • the satellite network device 200 assembles one or more first user frames into a multicast short message query request message.
  • the satellite network device 200 assembles one or more first user frames sent by the terminal 200 into one or more SLC SDUs at the SLC layer. Then, the satellite network device 200 uploads the one or more first user frames to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the satellite network device 200 can assemble one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the satellite network device 200 can upload the MDCP SDU to the APP layer as a multicast short message query request message.
  • the satellite network device 200 generates a multicast short message query result message based on the multicast short message query request message.
  • the satellite network device 200 can query the quantity of the multicast short message sent to the terminal 200 based on the multicast short message query request message. Then, the satellite network device 200 may generate a multicast short message query result message from the query result, and the multicast short message query result message is used to indicate the number of multicast short messages sent to the terminal 200 by the target multicast group.
  • the broadcast short message query request message is used to query the number of multicast short messages sent to the terminal 200. Then, the satellite short message fusion communication platform 24 can generate a multicast short message query result message from the query result, and the multicast short message query result message is used to indicate the multicast short message sent to the terminal 200 by the target multicast group. The number of messages.
  • the satellite network equipment 200 includes a satellite central station 23, a satellite short message fusion communication platform 24 and a broadcast multicast center 29, and the broadcast multicast
  • the broadcast center 29 may query the number of multicast short messages sent to the terminal 200 based on the multicast short message query request message. Then, the broadcast and multicast center 29 can generate a multicast short message query result message with the result of the query, and the multicast short message query result message is used to indicate the number of multicast short messages sent to the terminal 200 by the target multicast group .
  • the satellite central station 23 can according to the The identification of the terminal 200 (for example, the mobile phone number 138xxxxxxxx of the terminal 200) analyzed in a user frame, and the identification of the terminal 200 is sent to the satellite short message fusion communication platform 24 or the broadcast and multicast center 29.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can resolve the multicast short message received by the terminal 200 last time according to the identification of the terminal 200 and the multicast short message ID field in the multicast short message query request message.
  • the ID of the message (such as "a1") queries the number of multicast short messages sent to the terminal 200 by all target multicast groups after the time of sending the multicast short message whose ID is a1.
  • the satellite central station 23 may according to The identification of terminal 200 (for example, the mobile phone number 138xxxxxxxx of terminal 200) parsed from the first user frame, and the identification of terminal 200 is sent to satellite short message fusion communication platform 24 or broadcast multicast center 29.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can analyze the multicast ID and the multicast short message query request message according to the identification of the terminal 200 and the multicast ID field in the multicast short message query request message.
  • the multicast short message ID field resolve the ID (for example " a1 ") of the multicast short message that the terminal 200 received last time. After the multicast short message sending time of the multicast short message whose ID is a1, specify the target The number of multicast short messages sent to the terminal 200 by the multicast group.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can store the number of multicast short messages sent to the terminal 200 by different multicast groups.
  • the format of the number of multicast short messages sent to the terminal 200 by different multicast groups stored in the satellite short message fusion communication platform 24 or the broadcast multicast center 29 may be shown in Table 12 below.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can store the multicast ID, the sender ID of the multicast short message received by the multicast ID, and the sending time of the multicast short message.
  • the multicast group whose multicast ID is 1 is the first multicast group of the terminal 200, and the sender ID of two multicast short messages and the sending time of the multicast short message are stored in the first multicast group .
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 also stores the multicast short message ID.
  • the multicast short message IDs are numbered according to the order of sending time of all the multicast short messages received by the terminal 200 .
  • the terminal 200 receives 4 multicast short messages in total. If the multicast short message successfully received by the terminal 200 last time is the multicast short message sent by the sender "13xxxxxxxx0" in the multicast ID 1, and the multicast short message ID is 1, then the terminal 200 is querying the multicast ID 1 When the number of multicast short messages sent is 1, the number of multicast short messages replied by the satellite network device 200 is 1. If the multicast short message successfully received by the terminal 200 last time is the multicast short message sent by the sender "13xxxxxxxx0" in the multicast ID 1, and the multicast short message ID is 1, then the terminal 200 is inquiring about all multicast short messages. When the number of multicast short messages sent by the group is large, the number of multicast short messages replied by the satellite network device 200 is 3.
  • the multicast short message IDs may be numbered according to the order of sending time of the multicast short messages received in the terminal 200 under different multicast IDs.
  • the multicast group indicated by the multicast ID 1 receives two multicast short messages, wherein, the multicast short message ID of the multicast short message sent by the sender "13xxxxxxxx0" is 1.
  • the multicast short message ID of the multicast short message sent by the sender "13xxxxxxxx1" is 2; the multicast group indicated by the multicast ID 2 received two multicast short messages, among which the sender "158xxxxxxx0" sent The multicast short message ID of the multicast short message is 1, and the multicast short message ID of the multicast short message sent by the sender "158xxxxxxx1" is 2.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can also store the specific content of the multicast short message. It can be understood that the above Table 12 is only an example, and the embodiment of the present application does not limit the format for storing the multicast short message.
  • the format of the multicast short message query result message may be as shown in Table 13 below.
  • the multicast short message query result message may include message type indication field, encryption indication field, compression indication field, application layer authentication code field, multicast group number, multicast ID field, multicast short message Message Quantity field. It can be understood that the specific fields contained in the multicast short message query result message in the embodiment of the present application and the arrangement order of the fields are not limited. For example, if the satellite network device 200 does not encrypt the multicast short message query result message, the multicast short message query result message may not include an encryption indication field.
  • Table 14 exemplarily shows the lengths corresponding to the fields in Table 13 and specific descriptions.
  • the encryption indication field may be used to indicate whether the multicast short message query result message is encrypted.
  • the length of the encryption indication field may be 2 bits.
  • M1 for example, 00
  • the compression indication field may be used to indicate whether the multicast short message query result packet is compressed.
  • the length of the compression indication field may be 2 bits.
  • M2 for example, 00
  • the application layer authentication code field can be used for application layer authentication.
  • the length of the application layer authentication code field may be 16 bits. It can be understood that, the embodiment of the present application does not limit the length of the application layer authentication code field.
  • the number of multicast groups field may be used to indicate the number of all multicast groups in the terminal 200 .
  • the optional multicast group quantity field can also be used to indicate the cycle times of the multicast ID field and the multicast short message quantity field in the multicast short message query result message.
  • the length of the multicast group number field may be 4 bits. It can be understood that the embodiment of the present application does not limit the length of the multicast group quantity field.
  • the multicast ID field is used to indicate the ID of the target multicast group.
  • the length of the multicast ID field may be 10 bits. It can be understood that, in this embodiment of the present application, the length of the multicast ID field is not limited.
  • the number of multicast short messages field is used to indicate the number of multicast short messages sent by the target multicast group.
  • the number field of the multicast short message may be 4 bits. It can be understood that the embodiment of the present application does not limit the length of the multicast short message quantity field.
  • the multicast ID field and the multicast short message quantity field appear multiple times in the multicast short message query result message.
  • the satellite short message fusion communication platform 24 or the broadcast and multicast center 29 can generate different target The multicast short message query result message of the multicast group. Therefore, the multicast short message query result message may not include the multicast group number field.
  • the multicast short message query result message may not include the multicast group quantity field and the multicast ID field.
  • the number of multicast short messages field is used to indicate the total number of multicast short messages of all multicast groups in the terminal 200 .
  • the satellite network device 200 segments the multicast short message query result packet into one or more second user frames.
  • the satellite network device 200 sends one or more second user frames to the terminal 200.
  • the terminal 200 receives one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • reference may be made to the description of the embodiment shown in FIG. 7 , which will not be repeated here.
  • the terminal 200 After the terminal 200 has received the one or more second user frames, it replies to the satellite network device 200 that the one or more second user frames have been received.
  • the terminal 200 may parse out the user ID field in the frame header of each second user frame at the SLC layer. If the user ID parsed by the terminal 200 from the user ID field is the same as the identifier of the terminal 200, the terminal 200 uploads the one or more second user frames to the MDCP layer for further analysis. If the user ID parsed by the terminal 200 from the user ID field is different from the identifier of the terminal 200, the terminal 200 may determine that the second user frame is not sent to the terminal 200, and the terminal 200 may discard the second user frame.
  • the terminal 200 assembles one or more second user frames into a multicast short message query result message.
  • the terminal 200 can combine one or more second user frames into one or more SLC SDUs at the SLC layer. Then, the terminal 200 uploads one or more second user frames to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the terminal 200 can combine one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the terminal 200 can upload the MDCP SDU to the APP layer as a multicast short message query result message.
  • the terminal 200 analyzes the number of multicast short messages sent to the terminal 200 by the target multicast group based on the multicast short message query result message.
  • the terminal 200 can obtain the multicast group quantity field, the multicast ID field and the multicast short message quantity field based on the multicast short message query result message at the APP layer, and know the target multicast group sending message from the multicast short message quantity field. The number of multicast short messages to the terminal 200.
  • the terminal 200 displays the number of multicast short messages sent to the terminal 200 by the target multicast group.
  • the terminal 200 may display the number of multicast short messages sent to the terminal 200 by the target multicast group.
  • the terminal 200 may also prompt the user in other forms for the number of short messages sent by the target multicast group to the terminal 200, for example, the terminal 200 voice broadcasts the number of letters sent by the target multicast group to the terminal 200, the embodiment of the present application Not limited.
  • the terminal 200 can also query the multiple messages sent to the terminal 200 by the target group when it is under the satellite network and does not reside in the cellular network.
  • the number of broadcast short messages can also query the multiple messages sent to the terminal 200 by the target group when it is under the satellite network and does not reside in the cellular network.
  • Fig. 15 shows a schematic flowchart of a method for downloading a multicast short message in a satellite communication system provided in an embodiment of the present application.
  • the embodiment of the present application takes terminal 200 downloading a multicast message as an example for illustration. Downloading a multicast short message in a satellite communication system provided by the embodiment of the present application may include the following steps:
  • the terminal 200 generates a multicast short message download request message based on user operations, and the multicast short message download request message is used to download the content of the multicast short message sent to the terminal 200 by one or more target multicast groups.
  • the terminal 200 is under the satellite network, that is, the terminal 200 is in a scenario without a cellular network and a wireless local area network, the terminal 200 is not camped on the cellular network, and the satellite communication module in the terminal 200 is turned on.
  • the terminal 200 can communicate with the satellite network device 200 through the satellite communication module.
  • the terminal 200 may acquire the content of the multicast short message sent to the terminal 200 by one or more target multicast groups through the satellite network.
  • control 3 and the control 4 may exist in the terminal 200 .
  • control 3 can be used to request to download the content of the multicast short message sent to the terminal 200 by the designated target multicast group.
  • control 4 can be used to request to download the contents of the multicast short messages sent to the terminal 200 by all multicast groups.
  • the format of the multicast short message download request message may be as shown in Table 15 below.
  • the terminal 200 segments the multicast short message download request packet into one or more first user frames.
  • the terminal 200 may send the multicast short message download request message to the MDCP layer through the interlayer interface.
  • the terminal 200 can segment the multicast short message download request message into one or more MDCP PDUs at the MDCP layer.
  • the terminal 200 sends one or more MDCP PDUs to the SLC layer.
  • the terminal 200 may segment each MDCP PDU into one or more first user frames at the SLC layer.
  • the terminal 200 may fill in the identifier of the terminal 200 (for example, the mobile phone number of the terminal 200 ) in the user ID field in the frame header of each first user frame.
  • the identifier of the terminal 200 for example, the mobile phone number of the terminal 200
  • the terminal 200 sends one or more first user frames to the satellite network device 200.
  • the terminal 200 may send one or more first user frames to the satellite network device 200 .
  • the terminal 200 may send one or more first user frames to the satellite network device 200 .
  • the satellite network device 200 assembles one or more first user frames into a multicast short message download request message.
  • the satellite network device 200 assembles one or more first user frames sent by the terminal 200 into one or more SLC SDUs at the SLC layer. Then, the satellite network device 200 uploads the one or more first user frames to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the satellite network device 200 can combine one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the satellite network device 200 can upload the MDCP SDU to the APP layer as a multicast short message download request message.
  • the satellite network device 200 generates an outbound multicast short message message based on the multicast short message download request message, and the outbound multicast short message message is used to indicate the multicast message sent to the terminal 200 by the target multicast group The content of the short message.
  • the satellite network device 200 may query the multicast short message sent to the terminal 200 based on the multicast short message download request message. Then, the satellite network device 200 can generate an outbound multicast short message message from the queried multicast short message, and the outbound multicast short message message is used to indicate the multicast short message sent to the terminal 200 by the target multicast group. The content of the message.
  • the satellite short message fusion communication platform 24 can generate an outbound multicast short message message with the inquired multicast short message, and the outbound multicast short message message is used to indicate the target multicast group and send it to the terminal 200 content of the multicast short message.
  • the satellite network equipment 200 includes a satellite central station 23, a satellite short message fusion communication platform 24 and a broadcast multicast center 29, and the broadcast multicast
  • the broadcast center 29 may query the multicast short message sent to the terminal 200 based on the multicast short message download request message. Then, the broadcast and multicast center 29 can generate an outbound multicast short message message from the inquired multicast short message, and the outbound multicast short message message is used to indicate the multicast message sent to the terminal 200 by the target multicast group. The content of the short message.
  • the satellite central station 23 can download the content of the multicast short message from the first
  • the identification of the terminal 200 for example, the mobile phone number 138xxxxxxxx of the terminal 200
  • the satellite short message fusion communication platform 24 or the broadcast and multicast center 29 can resolve the multicast short message received by the terminal 200 last time according to the identification of the terminal 200 and the multicast short message ID field in the multicast short message download request message.
  • the ID of the message (such as "a1") queries the contents of the multicast short messages sent to the terminal 200 by all target multicast groups after the time of sending the multicast short message whose ID is a1.
  • the satellite central station 23 may According to the terminal 200 identification (for example, the mobile phone number 138xxxxxxxx of terminal 200) analyzed from the first user frame, and the identification of terminal 200 is sent to satellite short message fusion communication platform 24 or broadcast multicast center 29.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can analyze the multicast ID and the multicast short message download request message according to the identification of the terminal 200 and the multicast ID field in the multicast short message download request message.
  • the multicast short message ID field resolve the ID (for example " a1 ") of the multicast short message that the terminal 200 received last time. After the multicast short message sending time of the multicast short message whose ID is a1, specify the target The content of the multicast short message sent to the terminal 200 by the multicast group.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 can store the contents of multicast short messages sent to the terminal 200 by different multicast groups.
  • the specific storage manner of the content of the multicast short message reference may be made to the description of S1405, which will not be repeated here.
  • the satellite short message fusion communication platform 24 or the broadcast multicast center 29 inquire about the content of the multicast short message sent to the terminal 200 by the target multicast group in the multicast short message download request message, the satellite short message fusion communication The platform 24 or the broadcast multicast center 29 can generate an outbound multicast short message message based on the content of the multicast short message.
  • the format of the outbound multicast short message message is as shown in Table 5, and the specific description of each field in the outbound multicast short message message can refer to the description of S1006, which will not be repeated here. repeat. It can be understood that, in the embodiment of the present application, the outbound multicast short message message is an outbound multicast short message message sent to a specific target terminal. For example, the outbound multicast short message message is an outbound multicast short message message sent to the terminal 200 .
  • the satellite network device 200 segments the outbound multicast short message into one or more second user frames.
  • the satellite network device 200 sends one or more second user frames to the terminal 200.
  • the terminal 200 receives one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • the terminal 200 may receive one or more second user frames.
  • reference may be made to the description of the embodiment shown in FIG. 7 , which will not be repeated here.
  • the terminal 200 After the terminal 200 has received the one or more second user frames, it replies to the satellite network device 200 that the one or more second user frames have been received.
  • the terminal 200 may parse out the user ID field in the frame header of each second user frame at the SLC layer. If the user ID parsed by the terminal 200 from the user ID field is the same as the identifier of the terminal 200, the terminal 200 uploads the one or more second user frames to the MDCP layer for further analysis. If the user ID parsed by the terminal 200 from the user ID field is different from the identifier of the terminal 200, the terminal 200 may determine that the second user frame is not sent to the terminal 200, and the terminal 200 may discard the second user frame.
  • the terminal 200 assembles one or more second user frames into an outbound multicast short message message.
  • the terminal 200 can combine one or more second user frames into one or more SLC SDUs at the SLC layer. Then, the terminal 200 uploads one or more second user frames to the MDCP layer as one or more MDCP PDUs of the MDCP layer. Then, the terminal 200 can combine one or more MDCP PDUs into MDCP SDUs at the MDCP layer. Then, the terminal 200 can upload the MDCP SDU to the APP layer as an outbound multicast short message message.
  • the terminal 200 parses out the content of the multicast short message sent to the terminal 200 by the target multicast group based on the outbound multicast short message message.
  • the terminal 200 can obtain the multicast ID field, the sender ID field, the multicast short message content field, etc. based on the outbound multicast short message message at the APP layer, thereby determining the corresponding multicast group and sender of the multicast short message. square.
  • the terminal 200 displays the content of the multicast short message sent to the terminal 200 by the target multicast group.
  • the terminal 200 may display the content of the multicast short message sent to the terminal 200 by the target multicast group on the display screen.
  • the terminal 200 can also prompt the user in other forms for the content of the short message sent to the terminal 200 by the target multicast group.
  • the terminal 200 voice broadcasts the content of the letter sent to the terminal 200 by the target multicast group. Not limited.
  • the multicast short message download completion indication field in the outbound multicast short message message indicates that there will be a multicast short message to be sent to the terminal 200, and the terminal 200 can display a notification message to the user.
  • the notification message uses It is used to prompt the user whether to continue to download the subsequent multicast short message.
  • the user of the terminal 200 may query the multicast short message first. That is, query the number of multicast short messages sent to the terminal 200 by the target multicast group. After the satellite network device 200 sends the terminal 200 the number sent by the target multicast group to the terminal 200, the terminal 200 can select the multicast short message to be downloaded to download the multicast short message.
  • the terminal 200 can also download the multicast short message sent to the terminal 200 by the target group when it is under the satellite network and does not reside in the cellular network.
  • the number of short messages is not limited to the number of short messages.
  • the above content elaborates the method provided by the present application in detail.
  • the embodiments of the present application also provide corresponding devices or equipment.
  • the embodiment of the present application can divide the functional modules of the terminal 100, the terminal 200 and the satellite network device 200 according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one in a processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 16 is a schematic structural diagram of a communication device 1600 provided in an embodiment of the present application.
  • the communication device 1600 may be the terminal 100 or the terminal 200 in the foregoing embodiments.
  • the communication device 1600 may be a chip/chip system, for example, a satellite communication chip.
  • the communication device 1600 may include a transceiver unit 1610 and a processing unit 1620 .
  • the transceiver unit 1610 can be used to send an inbound multicast short message message to the satellite network device 200;
  • the transceiver unit 1610 may also be configured to receive an outbound multicast short message message.
  • the processing unit 1620 can be used to send the inbound multicast short message message to the MDCP layer, and can segment the inbound multicast short message message into one or more MDCP PDUs at the MDCP layer.
  • processing unit 1620 can also be used to segment the inbound multicast short message message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each An MDCP PDU is segmented into one or more first user frames.
  • the processing unit 1620 may also be configured to assemble one or more first user frames into one or more SLC SDUs, send one or more SLC SDUs to the MDCP layer, and send one or more SLC SDUs to the MDCP layer.
  • a MDCP PDU is assembled into an MDCP SDU, and the MDCP SDU can be sent to the APP layer as an outbound multicast short message message.
  • the transceiver unit 1610 can be used to send a multicast short message query request message to the satellite network device 200;
  • the transceiver unit 1610 may also be configured to receive a multicast short message query result message.
  • processing unit 1620 can also be used to segment the multicast short message query request message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each An MDCP PDU is segmented into one or more first user frames.
  • the processing unit 1620 may also be configured to assemble one or more first user frames into one or more SLC SDUs, send one or more SLC SDUs to the MDCP layer, and send one or more SLC SDUs to the MDCP layer.
  • a MDCP PDU is assembled into an MDCP SDU, and the MDCP SDU can be sent to the APP layer as a multicast short message query result message.
  • the transceiver unit 1610 can be used to send a multicast short message download request message to the satellite network device 200;
  • the transceiver unit 1610 may also be configured to receive an outbound multicast short message message.
  • processing unit 1620 can also be used to segment the multicast short message download request message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each An MDCP PDU is segmented into one or more first user frames.
  • the processing unit 1620 may also be configured to assemble one or more first user frames into one or more SLC SDUs, send one or more SLC SDUs to the MDCP layer, and send one or more SLC SDUs to the MDCP layer.
  • a MDCP PDU is assembled into an MDCP SDU, and the MDCP SDU can be sent to the APP layer as an outbound multicast short message message.
  • the transceiver unit 1610 can also be used to perform the functional steps related to sending and receiving performed by the terminal 100 or terminal 200 in the method embodiment shown in FIG. 10A, FIG. 10B, FIG. 12A or FIG. The functional steps related to sending and receiving performed by the terminal 200 in the method embodiment shown in FIG. 14 or FIG. 15 .
  • the processing unit 1620 may also be configured to execute functional steps related to protocol parsing and encapsulation and calculation determination performed by the terminal 100 or terminal 200 in the method embodiments shown in FIG. 10A, FIG. 10B, FIG. 12A or FIG. 12B, and It can be used to execute the functional steps related to protocol parsing and encapsulation and calculation determination performed by the terminal 200 in the method embodiment shown in FIG. 14 or FIG. 15 .
  • the communication device 1600 in this design can correspondingly perform the method steps performed by the terminal 100 or the terminal 200 in the foregoing embodiments, and details are not repeated here for brevity.
  • FIG. 17 is a schematic structural diagram of a communication device 1700 provided in an embodiment of the present application.
  • the communication apparatus 1700 may be the satellite network device 200 in the foregoing embodiments.
  • the communication device 1700 may be a specific network element in the satellite network equipment 200, for example, one or more network elements in the satellite ground transceiver station 22, the satellite central station 23, and the satellite short message fusion communication platform 24 The combination.
  • the communication device 1700 may include a transceiver unit 1710 and a processing unit 1720 .
  • the transceiver unit 1710 can be used to receive an inbound multicast short message message.
  • the transceiver unit 1710 may also be configured to send an outbound multicast short message message.
  • the processing unit 1720 can also be used to assemble one or more first user frames into one or more SLC SDUs at the SLC layer, and upload one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer ; Assemble one or more MDCP PDUs into MDCP SDU at the MDCP layer; then, it can be used to upload the MDCP SDU to the APP layer as an inbound multicast short message message.
  • processing unit 1720 can also be used to segment the outbound multicast short message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each One MDCP PDU is segmented into one or more second user frames.
  • the transceiver unit 1710 may be configured to receive a multicast short message query request message.
  • the transceiver unit 1710 may also be configured to send a multicast short message result message.
  • the processing unit 1720 can also be used to assemble one or more first user frames into one or more SLC SDUs at the SLC layer, and upload one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer ; Assemble one or more MDCP PDUs into MDCP SDUs at the MDCP layer; then, it can be used to upload the MDCP SDUs to the APP layer as a multicast short message query request message.
  • processing unit 1720 can also be used to segment the multicast short message result message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each The MDCP PDU is segmented into one or more second user frames.
  • the transceiver unit 1710 may be configured to receive a multicast short message download request message.
  • the transceiver unit 1710 may also be configured to send an outbound multicast short message message.
  • the processing unit 1720 can also be used to assemble one or more first user frames into one or more SLC SDUs at the SLC layer, and upload one or more SLC SDUs to the MDCP layer as one or more MDCP PDUs of the MDCP layer ; Assemble one or more MDCP PDUs into MDCP SDUs at the MDCP layer; then, it can be used to upload the MDCP SDUs to the APP layer as a multicast short message download request message.
  • processing unit 1720 can also be used to segment the outbound multicast short message into one or more MDCP PDUs, one or more MDCP PDUs can be sent to the SLC layer, and each One MDCP PDU is segmented into one or more second user frames.
  • the transceiver unit 1710 may also be configured to perform the sending and receiving functional steps performed by the satellite network device 200 in the method embodiment shown in FIG. 10A, FIG. 10B, FIG. 12A, FIG. 12B, FIG. 14 or FIG. 15.
  • the processing unit 1720 may also be configured to execute the protocol parsing and encapsulation and calculation determination performed by the satellite network device 200 in the method embodiment shown in FIG. 10A, FIG. 10B, FIG. 12A, FIG. 12B, FIG. 14 or FIG. 15 functional steps.
  • the communication device 1700 in this design can correspondingly perform the method steps performed by the satellite network device 200 in the foregoing embodiments, and for the sake of brevity, details are not repeated here.
  • the terminal 100, the terminal 200 and the satellite network device 200 of the embodiment of the present application have been introduced above. It should be understood that any product in any form that has the functions of the terminal 100 or terminal 200 described in FIG. Products of any form with the functions of the satellite network device 200 fall within the scope of protection of the embodiments of the present application.
  • the terminal 100 or the terminal 200 described in the embodiment of the present application may be implemented by a general bus architecture.
  • FIG. 18 is a schematic structural diagram of a communication device 1800 provided by an embodiment of the present application.
  • the communication device 1800 may be the terminal 100 or the terminal 200, or a device therein.
  • the communication device 1800 includes a processor 1801 and a transceiver 1802 internally connected and communicating with the processor.
  • the processor 1801 is a general purpose processor or a special purpose processor or the like.
  • it may be a baseband processor or a central processing unit for satellite communications.
  • the baseband processor of satellite communication can be used to process satellite communication protocols and satellite communication data
  • the central processing unit can be used to control communication devices (such as baseband chips, terminals, terminal chips, etc.), execute computer programs, and process computer Program data.
  • the transceiver 1802 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1802 may include a receiver and a transmitter, and the receiver may be called a receiver or a receiving circuit, etc., for realizing a receiving function; the transmitter may be called a transmitter or a sending circuit, for realizing a sending function.
  • the communication device 1800 may further include an antenna 1803 and/or a radio frequency unit (not shown in the figure).
  • the antenna 1803 and/or the radio frequency unit may be located inside the communication device 1800, or may be separated from the communication device 1800, that is, the antenna 1803 and/or the radio frequency unit may be remote or distributed.
  • the communication device 1800 may include one or more memories 1804, on which instructions may be stored, the instructions may be computer programs, and the computer programs may be run on the communication device 1800, so that the communication device 1800 executes the above-mentioned Methods described in the Examples.
  • data may also be stored in the memory 1804 .
  • the communication device 1800 and the memory 1804 can be set separately or integrated together.
  • the processor 1801, the transceiver 1802, and the memory 1804 may be connected through a communication bus.
  • the communication device 1800 can be used to execute the functions of the terminal 100 or the terminal 200 in the foregoing embodiments: the processor 1801 can be used to execute the above-mentioned functions described in FIG. 10A, FIG. 10B, FIG. 12A, FIG. 12B, FIG. 14 and FIG.
  • the terminal 100 or the terminal 200 performs functional steps related to protocol parsing and encapsulation and calculation determination and/or other processes for the technology described herein;
  • the transceiver 1502 can be used to execute the above-mentioned FIG. 12A, FIG. 12B, FIG. 14 and FIG. 15 show the functional steps related to protocol parsing and encapsulation and operation determination performed by terminal 100 or terminal 200 and/or other processes for the technology described herein.
  • the processor 1801 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits for realizing the functions of receiving and sending can be separated or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit may be used for signal transmission or transmission.
  • the processor 1801 may store instructions, the instructions may be computer programs, and the computer programs run on the processor 1801 to enable the communication device 1800 to execute the method steps performed by the terminal 100 in the above method embodiments.
  • the computer program may be fixed in the processor 1801, and in this case, the processor 1801 may be implemented by hardware.
  • the communication device 1800 may include a circuit, and the circuit may implement the function of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this application can be implemented in integrated circuits (integrated circuits, ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be fabricated using various IC process technologies such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • Communications apparatus 1800 may be a stand-alone device or may be part of a larger device.
  • the communication device 1800 may be:
  • a set of one or more ICs may also include storage components for storing data and computer programs;
  • ASIC such as modem (Modem);
  • any network element for example, the satellite ground transceiver station 22, the satellite central station 23 and the satellite short message fusion communication platform 24
  • any network element in the satellite network equipment 200 described in the embodiment of the application can be composed of Generic bus architecture to achieve.
  • FIG. 19 is a schematic structural diagram of a communication device 1900 provided by an embodiment of the present application.
  • the communication device 1900 may be the satellite network device 200, or a device therein.
  • the communication device 1900 includes a processor 1901 and a transceiver 1902 internally connected and communicating with the processor.
  • the processor 1901 is a general purpose processor or a special purpose processor or the like.
  • it may be a baseband processor or a central processing unit for satellite communications.
  • the baseband processor of the satellite communication can be used to process the satellite communication protocol and satellite communication data
  • the central processing unit can be used to control the communication device (eg, baseband chip, etc.), execute the computer program, and process the data of the computer program.
  • the transceiver 1902 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1902 may include a receiver and a transmitter, and the receiver may be called a receiver or a receiving circuit, etc., for realizing a receiving function; the transmitter may be called a transmitter or a sending circuit, for realizing a sending function.
  • the communication device 1900 may further include an antenna 1903 and/or a radio frequency unit (not shown in the figure).
  • the antenna 1903 and/or the radio frequency unit may be located inside the communication device 1900, or may be separated from the communication device 1900, that is, the antenna 1903 and/or the radio frequency unit may be remote or distributed.
  • the communication device 1900 may include one or more memories 1904, on which instructions may be stored, the instructions may be computer programs, and the computer programs may be run on the communication device 1900, so that the communication device 1900 executes the above-mentioned Methods described in the Methods Examples.
  • data may also be stored in the memory 1904 .
  • the communication device 1900 and the memory 1904 can be set separately or integrated together.
  • the processor 1901, the transceiver 1902, and the memory 1904 may be connected through a communication bus.
  • the communication device 1900 can be used to execute the functions of the satellite network equipment 200 in the foregoing embodiments: the processor 1901 can be used to execute the above-mentioned functions shown in FIG. 10A, FIG. 10B, FIG. 12A, FIG. 12B, FIG. 14 and FIG.
  • the satellite network device 200 executes the functional steps related to protocol parsing and encapsulation and calculation determination and/or other processes for the technology described herein;
  • the transceiver 1902 can be used to execute the above-mentioned FIG. 10A, FIG. 10B, and FIG. 12A 12B, FIG. 14 and FIG. 15, satellite network equipment 200 in the embodiment shown in the protocol parsing and encapsulation and operation to determine the functional steps and / or other processes used in the technology described herein.
  • the processor 1901 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits for realizing the functions of receiving and sending can be separated or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit may be used for signal transmission or transmission.
  • the processor 1901 may store instructions, the instructions may be computer programs, and the computer programs run on the processor 1901 to enable the communication device 1900 to execute the method performed by the satellite network device 200 in the above method embodiments step.
  • the computer program may be fixed in the processor 1901, and in this case, the processor 1901 may be implemented by hardware.
  • the embodiment of the present application also provides a computer-readable storage medium, where computer program code is stored in the computer-readable storage medium, and when the above-mentioned processor executes the computer program code, the communication device executes the method in any of the above-mentioned embodiments .
  • An embodiment of the present application further provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute the method in any one of the preceding embodiments.
  • the embodiment of the present application also provides a communication device, which can exist in the product form of a chip.
  • the structure of 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 performs the aforementioned The method in any of the examples.
  • the embodiment of the present application also provides a satellite communication system, including the terminal 100 and/or the terminal 200 and the satellite network device 200, and the terminal 100 and/or the terminal 200 and the satellite network device 200 can execute the method in any of the foregoing embodiments.
  • This application fully introduces the communication function of short messages in the satellite communication system. It can be understood that the Beidou satellite communication system supports the communication function of short messages, and the method introduced in this application is applicable to the Beidou satellite communication system.
  • the term “when” may be interpreted to mean “if” or “after” or “in response to determining" or “in response to detecting".
  • the phrase “in determining” or “if detected (a stated condition or event)” may be interpreted to mean “if determining" or “in response to determining" or “on detecting (a stated condition or event)” or “in response to detecting (a stated condition or event)”.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, DSL) or wireless (eg, infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state hard disk), etc.
  • the processes can be completed by computer programs to instruct related hardware.
  • the programs can be stored in computer-readable storage media.
  • When the programs are executed may include the processes of the foregoing method embodiments.
  • the aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Radio Relay Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种卫星通信系统中多播短消息传输的方法、系统及相关装置。该方法可以应用于第一终端，该方法可以包括：第一终端向卫星网络设备发送入站多播短消息报文，入站多播短消息报文可以包括第一字段和第二字段，该第一字段用于指示该入站多播短消息报文所对应的多播群组的多播ID为第一多播ID，第二字段用于指示该入站多播短消息报文中的信息内容为第一信息内容。这样，当第一终端所在的环境中没有蜂窝网络、或者无线局域网络的情况下，第一终端可以通过卫星网络向其他的终端发送多播短消息。其中，该多播短消息中指示了多播短消息所对应的多播群组的多播ID，因此卫星网络设备可以识别该多播短消息所对应的多播群组。

Description

一种卫星多播短消息的方法及相关装置
本申请要求在2021年12月6日提交中国国家知识产权局、申请号为202111511376.5的中国专利申请的优先权，发明名称为“一种卫星短消息下行接收的方法”的中国专利申请的优先权，要求在2022年2月17日提交中国国家知识产权局、申请号为202210144012.6的中国专利申请的优先权，发明名称为“一种卫星多播短消息的方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及卫星通信技术领域，尤其涉及一种卫星通信系统中多播短消息传输的方法及相关装置。
背景技术
卫星导航系统是集定位、授时、通信于一体的重大基础设施。卫星短报文通信业务是卫星通信系统中的特色之一。卫星短报文通信业务特别适用于在海洋、沙漠、草原、无人区等移动通信未覆盖、或覆盖不了、或通信系统被破坏的区域进行通信。目前一些卫星通信卫星的短报文系统对短报文技术体制进行了升级，将卫星短报文业务的通信系统一些必要的资源开放使用，针对消费者业务和设备特性，需要依据卫星短报文业务的通信系统的特性设计通信协议。
其中，由于卫星通信系统中没有提供给终端使用的多播短消息传输的相关协议内容。北斗通信系统下的终端无法向其他终端发送多播短消息，也无法接收其他终端发送的多播短消息。
因此，如何在卫星通信系统中实现多播短消息的传输成为亟待解决的问题。
发明内容
本申请实施例提供了一种卫星通信系统中多播短消息传输的方法、系统及相关装置。通过本申请实施例提供的一种卫星通信系统中多播短消息传输的方法，当终端所在的环境中没有蜂窝网络、或者无线局域网络的情况下，终端也可以通过卫星通信系统向其他的终端发送多播短消息。
第一方面，本申请实施例提供了一种卫星通信系统中多播短消息传输的方法，该方法应用于第一终端，该方法可以包括：第一终端向卫星网络设备发送入站多播短消息报文，入站多播短消息报文可以包括第一字段和第二字段，该第一字段用于指示该入站多播短消息报文所对应的多播群组的多播ID为第一多播ID，第二字段用于指示该入站多播短消息报文中的信息内容为第一信息内容。
这样，当第一终端所在的环境中没有蜂窝网络、或者无线局域网络的情况下，第一终端可以通过卫星网络向其他的终端发送多播短消息。其中，该多播短消息中指示了多播短消息所对应的多播群组的ID，因此卫星网络设备可以识别该多播短消息所对应的多播群组。
结合第一方面，在一种可能的实现方式中，入站多播短消息报文中还包括第三字段，该第三字段用于指示该入站多播短消息报文的业务类型为通用报文业务类型。
结合第一方面，在一种可能的实现方式中，第一终端向卫星网络设备发送入站多播短消息报文，包括：第一终端向卫星网络设备发送一个或多个第一用户帧，该一个或多个第一用户帧中包括第四字段，该第四字段用于指示该一个或多个第一用户帧的帧类型为多播短消息帧类型。
这样，卫星网络设备可以通过一个或多个第一用户帧确定接收到的报文为入站多播短消息报文，因此可以实现在协议下层将入站多播短消息报文发送到对应的网元进行处理。
结合第一方面，在一种可能的实现方式中，入站多播短消息报文中还包括第三字段，第三字段用于指示该入站多播短消息报文的业务类型为入站多播短消息类型。
这样，卫星网络设备可以直接通过入站多播短消息报文确定接收到的报文为入站多播短消息报文，因此，不需要协议下层来指示该报文为入站多播短消息报文，节省了卫星网络设备中的通信资源。
结合第一方面，在一种可能的实现方式中，第一终端向卫星网络设备发送入站多播短消息报文，包括：第一终端向卫星网络设备发送一个或多个第一用户帧，该一个或多个第一用户帧中包括第四字段，该第四字段用于指示该一个或多个第一用户帧的帧类型为通用数据帧类型。
结合第一方面，在一种可能的实现方式中，该方法还包括：第一终端接收卫星网络设备发送的第一出站多播短消息报文，该第一出站多播短消息报文中包括第五字段和第六字段，该第五字段用于指示该第一出站多播短消息报文的发送方ID为第二终端的用户ID，该第六字段用于指示该第一出站多播短消息报文中的信息内容为第二信息内容；其中，第一终端和第二终端属于第一多播群组，该第一多播群组的多播ID为第一多播ID。
这样，第一终端在接收到第一出站多播短消息报文后，可以通过第五字段确定该第一出站多播短消息报文的具体发送方。
结合第一方面，在一种可能的实现方式中，第一终端接收卫星网络设备发送的第一出站多播短消息报文，包括：第一终端接收一个或多个第二用户帧，该一个或多个第二用户帧中包括第七字段和第八字段，该第七字段用于指示该一个或多个第二用户帧的帧类型为多播用户帧类型，该第八字段用于指示该一个或多个第二用户帧所对应的多播群组的多播ID为第一多播ID；第一终端基于第七字段确定该一个或多个第二用户帧为多播短消息帧，并解析得到第一多播ID；第一终端基于该一个或多个第二用户帧得到第一出站多播短消息报文，并解析得到第二终端的用户ID和第二信息内容；第一终端基于第一多播ID和第二终端的用户ID显示第二信息内容。
这样，一个或多个第二用户帧中包括第一多播ID，因此卫星网络设备可以在空口发送一次一个或多个第二用户帧，第一多播ID对应的多播群组中的终端都能接收到该一个或多个第二用户帧，节省了卫星通信的空口资源。
结合第一方面，在一种可能的实现方式中，该方法还包括：第一终端向卫星网络设备发送多播短消息查询请求报文，该多播短消息查询请求报文中包括业务类型字段，该业务类型字段用于指示该多播短消息查询请求报文的业务类型为多播短消息查询类型；第一终端接收并显示多播短消息查询结果报文，该多播短消息查询结果报文为卫星网络设备基于多播短消 息查询请求报文生成的。
这样，第一终端可以通过卫星系统查询未成功接收的多播短消息报文的数量。
结合第一方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询指定多播群组发送给第一终端的多播短消息的数量；多播短消息查询请求报文中还包括多播ID字段和多播短消息ID字段，所述多播ID字段用于指示指定多播群组的多播ID，多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；多播短消息查询结果报文中包括多播短消息数量字段，多播短消息数量字段用于指示指定多播群组发送给第一终端的多播短消息的数量。
这样，第一终端可以通过卫星通信系统查询指定多播群组中未成功接收到的多播短消息的数量。
结合第一方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询所有多播群组发送给第一终端的多播短消息的数量；多播短消息查询请求报文中还包括多播短消息ID字段，多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的ID；多播短消息查询结果报文中包括多播短消息数量字段，多播短消息数量字段用于指示所有多播群组发送给第一终端的多播短消息的数量。
这样，第一终端可以通过卫星通信系统查询所有多播群组中未成功接收到的多播短消息的数量。
结合第一方面，在一种可能的实现方式中，该方法还包括：第一终端向卫星网络设备发送多播短消息下载请求报文，多播短消息下载请求报文中包括业务类型字段，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型；第一终端接收并显示第二出站多播短消息报文，第二出站多播短消息报文为卫星网络设备基于多播短消息下载请求报文生成的。
这样，第一终端可以通过卫星通信系统下载未成功接收到的多播短消息的信息内容。
结合第一方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载指定多播群组发送给第一终端的多播短消息；多播短消息下载请求报文中还包括多播ID字段和多播短消息ID字段，多播ID字段用于指示指定多播群组的多播ID，多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；第二出站多播短消息报文中包括下载完成指示字段，下载完成指示字段用于指示指定多播群组后续是否还有多播短消息发送给第一终端。
这样，第一终端可以通过卫星系统下载指定多播群组中未成功接收到的多播短消息的信息内容。进一步的，第一终端还可以确定是否继续下载。
结合第一方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载所有多播群组发送给第一终端的多播短消息；多播短消息下载请求报文中还包括多播短消息ID字段，多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；第二出站多播短消息报文中包括下载完成指示字段，下载完成指示字段用于指示所有多播群组后续是否还有多播短消息发送给第一终端。
这样，第一终端可以通过卫星系统下载所有多播群组中未成功接收到的多播短消息的信息内容。进一步的，第一终端还可以确定是否继续下载。
第二方面，本申请实施例提供了一种卫星通信系统中多播短消息传输的方法，该方法包括：第一终端向卫星网络设备发送入站多播短消息报文，该入站多播短消息报文中包括第一字段和第二字段，该第一字段用于指示入站多播短消息报文所对应的多播群组的多播ID为第一多播ID，该第二字段用于指示入站多播短消息报文中的信息内容为第一信息内容；卫星网络设备接收入站多播短消息报文，解析得到第一多播ID和第一信息内容；卫星网络设备基于第一信息内容发送第一出站多播短消息报文；第二终端接收第一出站多播短消息报文，其中，第一终端和第二终端属于第一多播群组，第一多播群组的多播ID为第一多播ID。
这样，当第一终端所在的环境中没有蜂窝网络、或者无线局域网络的情况下，第一终端可以通过卫星网络向属于同一个多播群组中的第二终端发送多播短消息。其中，该多播短消息中指示了多播短消息所对应的多播群组的ID，因此卫星网络设备可以识别该多播短消息所对应的多播群组。
结合第二方面，在一种可能的实现方式中，入站多播短消息报文中还包括第三字段，该第三字段用于指示多播短消息报文的业务类型为通用报文业务类型。
结合第二方面，在一种可能的实现方式中，第一终端向卫星网络设备发送入站多播短消息报文，包括：第一终端向卫星网络设备发送一个或多个第一用户帧，该一个或多个第一用户帧中包括第四字段，该第四字段用于指示所述一个或多个第一用户帧的帧类型为多播短消息帧类型。
结合第二方面，在一种可能的实现方式中，卫星网络设备接收所述入站多播短消息报文，包括：卫星网络设备接收一个或多个第一用户帧，解析得到第四字段；卫星网络设备基于第四字段确定一个或多个第一用户帧为多播短消息帧；卫星网络设备基于一个或多个第一用户帧得到入站多播短消息报文，并解析得到第一多播ID和第一信息内容。
这样，卫星网络设备可以通过一个或多个第一用户帧确定接收到的报文为入站多播短消息报文，因此可以实现在协议下层将入站多播短消息报文发送到对应的网元进行处理。
结合第二方面，在一种可能的实现方式中，入站多播短消息报文中包括第三字段，该第三字段用于指示多播短消息报文的业务类型为入站多播短消息类型。
结合第二方面，在一种可能的实现方式中，第一终端向卫星网络设备发送入站多播短消息报文，包括：第一终端向卫星网络设备发送一个或多个第一用户帧，该一个或多个第一用户帧中包括第四字段，该第四字段用于指示该一个或多个第一用户帧的帧类型为通用数据帧类型。
结合第二方面，在一种可能的实现方式中，卫星网络设备接收入站多播短消息报文，包括：卫星网络设备接收一个或多个第一用户帧；卫星网络设备基于一个或多个第一用户帧得到入站多播短消息报文，解析得到第三字段；卫星网络设备基于该第三字段确定入站多播短消息报文的业务类型为入站多播短消息类型，并解析得到第一多播ID和第一信息内容。
这样，卫星网络设备可以直接通过入站多播短消息报文确定接收到的报文为入站多播短消息报文，因此，不需要协议下层来指示该报文为入站多播短消息报文，节省了卫星网络设备中的通信资源。
结合第二方面，在一种可能的实现方式中，第一出站多播短消息报文中包括发送方ID字段和第五字段，所述发送方ID字段用于指示所述第一出站多播短消息报文的发送方ID为所述第一终端的用户ID，所述第五字段用于指示所述第一出站多播短消息报文的信息内容所述第一信息内容。
结合第二方面，在一种可能的实现方式中，卫星网络设备基于所述信息内容发送第一出站多播短消息报文，包括：卫星网络设备发送一个或多个第二用户帧，该一个或多个第二用户帧中包括第六字段和第七字段，该第六字段用于指示一个或多个第二用户帧的帧类型为多播短消息帧类型，该第七字段用于指示一个或多个第二用户帧所对应的多播群组的多播ID为第一多播ID。
这样，一个或多个第二用户帧中包括第一多播ID，因此卫星网络设备可以在空口发送一次一个或多个第二用户帧，第一多播ID对应的多播群组中的终端都能接收到该一个或多个第二用户帧，节省了卫星通信的空口资源。
结合第二方面，在一种可能的实现方式中，第二终端接收第一出站多播短消息报文，包括：第二终端接收一个或多个第二用户帧，解析得到第六字段；第二终端基于第六字段确定一个或多个第二用户帧为多播短消息帧，并解析得到第一多播ID；第二终端基于一个或多个第二用户帧得到第一出站多播短消息报文，并解析得到第一终端的用户ID和所述第一信息内容；第二终端基于第一多播ID和第一终端的用户ID显示所述第一信息内容。
这样，第一终端在接收到第一出站多播短消息报文后，可以通过第六字段确定该第一出站多播短消息报文的具体发送方。
结合第二方面，在一种可能的实现方式中，在卫星网络设备基于第一信息内容发送第一出站多播短消息报文之前，该方法还包括：卫星网络设备确定第一出站多播短消息报文的卫星信息和波束信息。
这样，卫星网络设备可以在发送第一出站多播短消息报文前确定卫星信息和波束信息，提高了第一出站多播短消息报文发送的成功率。
结合第二方面，在一种可能的实现方式中，入站多播短消息报文中包括位置信息字段，所述位置信息字段用于指示第一终端的位置信息；卫星网络设备确定第一出站多播短消息报文的卫星信息和波束信息，包括：卫星网络设备基于入站多播短消息报文，解析得到位置信息字段；卫星网路设备基于位置信息字段，得到第一出站多播短消息报文的卫星信息和波束信息。
这样，卫星网络设备可以接收第一终端的位置信息，并根据第一终端的位置信息确定第一出站多播短消息报文的卫星信息和波束信息，提高了第一出站多播短消息报文发送的成功率。
结合第二方面，在一种可能的实现方式中，一个或多个第一用户帧中包括出站链路指示字段，该出站链路指示字段用于指示第一出站多播短消息报文的卫星信息和波束信息；在卫星网络设备基于第一信息内容发送第一出站多播短消息报文之前，该方法还包括：卫星网络设备基于一个或多播第一用户帧，解析得到出站链路指示字段；卫星网络设备基于出站链路指示字段，得到第一出站多播短消息报文的卫星信息和波束信息。
这样，卫星网络设备可以接收到出站链路指示，并根据该出站链路指示确定第一出站多播短消息报文的卫星信息和波束信息，提高了第一出站多播短消息报文发送的成功率。
结合第二方面，在一种可能的实现方式中，该方法还包括：第一终端向卫星网络设备发送多播短消息查询请求报文，多播短消息查询请求报文中包括业务类型字段，该业务类型字段用于指示多播短消息查询请求报文的业务类型为多播短消息查询类型；卫星网络设备接收多播短消息查询请求报文；卫星网络设备基于多播短消息查询请求报文，生成多播短消息查询结果报文；卫星网络设备向第一终端发送多播短消息查询结果报文；第一终端接收并显示所述多播短消息查询结果报文。
这样，第一终端可以通过卫星系统查询未成功接收的多播短消息报文的数量。
结合第二方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询指定多播群组发送给第一终端的多播短消息的数量；多播短消息查询请求报文中还包括多播ID字段和多播短消息ID字段，该多播ID字段用于指示指定多播群组的多播ID，该多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；多播短消息查询结果报文中包括多播短消息数量字段，多播短消息数量字段用于指示指定多播群组发送给第一终端的多播短消息的数量。
这样，第一终端可以通过卫星通信系统查询指定多播群组中未成功接收到的多播短消息的数量。
结合第二方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询所有多播群组发送给第一终端的多播短消息的数量；多播短消息查询请求报文中还包括多播短消息ID字段，该多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；多播短消息查询结果报文中包括多播短消息数量字段，该多播短消息数量字段用于指示所有多播群组发送给第一终端的多播短消息的数量。
这样，第一终端可以通过卫星通信系统查询所有多播群组中未成功接收到的多播短消息的数量。
结合第二方面，在一种可能的实现方式中，该方法还包括：第一终端向卫星网络设备发送多播短消息下载请求报文，多播短消息下载请求报文中包括业务类型字段，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型；卫星网络设备接收多播短消息下载请求报文；卫星网络设备基于多播短消息下载请求报文，生成第二出站多播短消息报文；卫星网络设备向第一终端发送第二出站多播短消息报文；第一终端接收并显示第二出站多播短消息报文。
这样，第一终端可以通过卫星通信系统下载未成功接收到的多播短消息的信息内容。
结合第二方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载指定多播群组发送给第一终端的多播短消息；多播短消息下载请求报文中还包括多播ID字段和多播短消息ID字段，该多播ID字段用于指示指定多播群组的多播ID，该多播短消息ID字段用于指示第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；第二出站多播短消息报文中包括下载完成指示字段，该下载完成指示字段用于指示指定多播群组后续是否还有多播短消息发送给第一终端。
这样，第一终端可以通过卫星系统下载指定多播群组中未成功接收到的多播短消息的信 息内容。进一步的，第一终端还可以确定是否继续下载。
结合第二方面，在一种可能的实现方式中，业务类型字段用于指示多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载所有多播群组发送给第一终端的多播短消息；多播短消息下载请求报文中还包括多播短消息ID字段，该多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；第二出站多播短消息报文中包括下载完成指示字段，该下载完成指示字段用于指示所有多播群组后续是否还有多播短消息发送给第一终端。
这样，第一终端可以通过卫星系统下载所有多播群组中未成功接收到的多播短消息的信息内容。进一步的，第一终端还可以确定是否继续下载。
第三方面，本申请实施例提供了一种通信装置，包括一个或多个处理器、一个或多个存储器和收发器；其中，收发器、一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器在执行计算机指令时，使得该通信装置执行上述第一方面任一项可能的实现方式中的方法。
结合第三方面，在一种可能的实现方式中，通信装置为终端。
第四方面，本申请实施例提供了一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第一方面任一项可能的实现方式中的方法。
第五方面，本申请实施例提供了一种芯片或芯片系统，应用于终端，包括处理电路和接口电路，接口电路用于接收代码指令并传输至处理电路，处理电路用于运行代码指令以执行上述第一方面任一项可能的实现方式中的方法。
附图说明
图1为本申请实施例提供的一种卫星通信系统的架构示意图；
图2A为本申请实施例提供的一种卫星通信系统中数据入站的传输过程；
图2B为本申请实施例提供的一种卫星通信系统中数据出站的传输过程；
图3为本申请实施例提供的终端100的结构示意图；
图4为本申请实施例中提供的一种卫星通信系统10的入站数据的协议封装架构示意图；
图5为本申请实施例中提供的一种卫星通信系统10的入站数据的协议解析架构示意图；
图6为本申请实施例中提供的一种卫星通信系统10的出站数据的协议封装架构示意图；
图7为本申请实施例中提供的一种卫星通信系统10的出站数据的协议解析架构示意图；
图8A-8F为本申请实施例中提供的一组界面示意图；
图9A-9B为本申请实施例中提供的另一组界面示意图；
图10A本申请实施例中提供的一种卫星通信系统中多播短消息传输的流程示意图；
图10B本申请实施例中提供的另一种卫星通信系统中多播短消息传输的流程示意图；
图11为本申请实施例提供的另一种卫星通信系统的架构示意图；
图12A本申请实施例中提供的另一种卫星通信系统中多播短消息传输的流程示意图；
图12B本申请实施例中提供的另一种卫星通信系统中多播短消息传输的流程示意图；
图13为本申请实施例提供的另一种卫星通信系统的架构示意图；
图14为本申请实施例中提供的一种卫星通信系统中查询多播短消息数量的方法的流程 示意图；
图15为本申请实施例中提供的一种卫星通信系统中下载多播短消息的方法的流程示意图；
图16为本申请实施例提供的一种通信装置的结构示意图；
图17为本申请实施例提供的另一种通信装置的结构示意图；
图18为本申请实施例提供的另一种通信装置的结构示意图；
图19为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
下面将结合附图对本申请实施例中的技术方案进行清楚、详尽地描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；文本中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为暗示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征，在本申请实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
下面介绍本申请实施例中提供的一种卫星通信系统10。
图1示出了本申请实施例中提供的一种卫星通信系统10的架构示意图，以卫星通信系统为例。
如上图1所示，卫星通信系统10可以包括终端100、短报文卫星21、卫星网络设备200、短消息中心25和终端300。可选的，该卫星通信系统10还可以包括紧急救援平台26、紧急救援中心27。
其中，终端100可以发送短报文信息给短报文卫星21，短报文卫星21只进行中继，直接将终端100发送的短报文信息转发给地面的卫星网络设备200。卫星网络设备200可以根据卫星通信协议解析卫星转发的短报文信息，并将从短报文信息中解析出的通用报文类型的报文内容转发给短消息中心(short message service center，SMSC)25。短消息中心25可以通过传统的蜂窝通信网络，将报文内容转发给终端300。卫星网络设备200也可以将终端100发送的紧急求救类型的报文，通过紧急救援平台26发送给紧急救援中心27。
终端300也可以通过传统的蜂窝通信网络，将短消息发送给短消息中心25。短消息中心25可以将终端300的短消息转发给卫星网络设备200。卫星网络设备200可以将终端300的短消息通过短报文卫星21中继发送给终端100。
终端100可以通过卫星通信系统将终端100的位置信息发送给位置中心28。位置中心28接收到终端100发送个位置信息后，将终端100的位置信息存储在本地。其中，位置信息可以包括终端100的经度信息、纬度信息和高度信息。在长期演进(Long Term Evolution，LTE)网络中，位置中心28可以是用户归属地服务器(Home Subscriber Server，HSS)。在新空口(New Radio，NR)网络中，位置中心28可以是统一数据管理功能(Unified Data Management，UDM)网元。位置中心28也存储了蜂窝网络下的终端300的位置信息。
其中，上述卫星网络设备200可以包括卫星地面收发站22、卫星中心站23和卫星短报 文融合通信平台24。其中，卫星地面收发站22可以包括分别具有发送功能的一个或多个设备和具有接收功能的一个或多个设备，或者可以包括具有发送功能和接收功能的一个或多个设备，此处不作限定。卫星地面收发站22可用于卫星网络设备200在物理层(physical layer protocol，PHY)对数据的处理功能。卫星中心站23可用于卫星网络设备200在卫星链路层(satellite link control protocol，SLC)层和消息数据汇聚层(message data convergence protocol，MDCP)对数据的处理功能。卫星短报文融合通信平台24可用于在应用层(Application Protocol，APP)对数据的处理功能。
其中，由于卫星通信系统10是通过卫星链路进行通信，其主要特性是：时延长(单向约270ms)，链路损耗大。当前卫星通信系统10支持的业务主要是突发短消息业务，不支持连接状态管理、移动性管理和广播控制信息等。
终端100可以主动通过短报文卫星21给卫星网络设备200发送数据。但是，由于没有空口信令，地面的中心站无法主动寻呼用户。由于卫星通信传播距离远，卫星通信系统10中对终端100的发送功率要求高。受限当前终端100上射频器件的限制，终端100无法向短报文卫星21长时间持续发送信号。为了尽量不损坏终端100上射频器件，终端100的射频器件在发送状态持续工作一段时间后，必须停止工作一段时间后才能继续切换到发送状态继续工作。其中，终端100上发送状态的持续时长由终端100的底层硬件能力所决定。在上述卫星通信系统10中，为了保证终端100接收到的数据和发送的数据互不干扰，终端100不支持发送数据和接收数据同时发生。终端100需要在发送数据后，再等待接收卫星网络设备200发送的数据。
其中，卫星网络设备200的工作模式可以是双工模式，可以同时收发数据，且卫星网络设备200可以长时间发送和接收数据。
图2A示出了本申请实施例提供的一种卫星通信系统中数据入站的传输过程。
如图2A所示，数据入站可以指终端100将数据发送给卫星网络设备200。例如，终端100可以向卫星地面收发站22发送数据帧。卫星地面收发站22可以将数据帧发送给卫星中心站23。卫星中心站23可以将数据帧汇聚成应用层报文上报给卫星短报文融合通信平台24。卫星中心站23可以在接收到终端100发送的数据帧后，向终端100返回SLC层的确认字符(acknowledge character，ACK)。该ACK可用于指示卫星网络设备200是否成功收到终端100发送的数据帧。
图2B示出了本申请实施例提供的一种卫星通信系统中数据出站的传输过程。
如图2B所示，数据出站可以指卫星网络设备200将数据发送给终端100。例如，卫星网络设备200中的卫星短报文融合通信平台24可以将应用层报文发送给卫星中心站23；然后卫星中心站23可以将该应用层报文拆分成一个或多个数据帧发送给卫星地面收发站22，由短报文卫星21中继后发送给终端100。可选的，终端100接收到数据帧后可以向卫星中心站23返回SLC层的ACK。该ACK可用于终端100是否成功接收到卫星网络设备200发送的数据帧。
图3示出了终端100的结构示意图。
下面以终端100为例对实施例进行具体说明。应该理解的是，图3所示终端100仅是一个范例，并且终端100可以具有比图3中所示的更多的或者更少的部件，可以组合两个或多个的部件，或者可以具有不同的部件配置。图3中所示出的各种部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件、或硬件和软件的组合中实现。
终端100可以包括：处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本发明实施例示意的结构并不构成对终端100的具体限定。在本申请另一些实施例中，终端100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是终端100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
终端100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在终端100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(不限于扬声器170A，受话器170B等)输出声音信 号，或通过显示屏194显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以提供应用在终端100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，卫星通信模块，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
其中，卫星通信模块可用于与卫星网络设备进行通信，例如在北斗通信系统中，卫星通信模块可以与北斗网络设备通信，卫星通信模块的可支持与北斗网络设备之间的短报文传输。
在一些实施例中，终端100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得终端100可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯系统(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，和/或IR技术等。所述GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
终端100通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏194用于显示图像，视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)。显示面板还可以采用有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，miniled，microLed，micro-oled，量子点发光二极管(quantum dot light emitting diodes，QLED)等制造。在一些实施例中，终端100可以包括1个或N个显示屏194，N为大于1的正整数。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行终端100的各种功能应用以及数据处理。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操 作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
终端100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
SIM卡接口195用于连接SIM卡。SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现和终端100的接触和分离。终端100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口195可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口195可以同时插入多张卡。所述多张卡的类型可以相同，也可以不同。SIM卡接口195也可以兼容不同类型的SIM卡。SIM卡接口195也可以兼容外部存储卡。终端100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，终端100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在终端100中，不能和终端100分离。
下面介绍本申请实施例中提供的一种卫星通信系统10的入站数据的协议封装架构。
图4示出了本申请实施例中提供的一种卫星通信系统10的入站数据的协议封装架构示意图。
如图4所示，终端100上的卫星短报文传输协议层可以分为应用层(Application Protocol,APP)、消息数据汇聚层(Message Data Convergence Protocol，MDCP)、卫星链路控制层(Satellite Link Control，SLC)和物理层(Physical，PHY)。
终端100发送数据给卫星网络设备200时，终端100上的卫星短报文传输协议的工作流程可以如下：
在APP层，终端100可以将原始数据通过压缩算法，压缩成压缩数据，并在压缩数据前面添加压缩指示字段，其中，压缩指示字段可用于表示该压缩数据的压缩算法类型。之后，终端100可以将压缩数据加密，得到加密后数据，并在加密后数据的头部添加加密指示字段，该加密指示字段用于表示该加密后的数据的加密算法类型。终端100可以将加密后数据、压缩指示字段、加密指示字段封装成应用层报文下发给MDCP层。其中，该应用层报文包括报文头和报文数据。该报文头中包括压缩指示字段、加密指示字段等等。该报文数据包括上述加密后数据。
可选的，终端100也可以将压缩指示字段和压缩数据一起进行加密，得到加密后数据。
在MDCP层，终端100可以通过层间接口获取到APP层下发的应用层报文，并将应用层报文作为一个MDCP SDU(MDCP Service Data Unit，MDCP服务数据单元)。由于受空口的限制，终端100每次只能在物理层发送的指定长度的物理帧，这样，约束了MDCP层数据的长度为指定长度。因此，在MDCP层，终端100可以在MDCP SDU的尾部添加填充数据(padding)至指定长度，并在MDCP SDU的头部添加冗余长度指示字段。该冗余长度指示字段可用于表示该填充数据的长度。终端100可以将填充数据以及增加冗余长度指示字段之后的MDCP SDU，拆分成一个或多个固定长度的MDCP分段数据(M_segment)，并在每个MDCP分段数据的头部添加后继指示字段，得到MDCP PDU(MDCP Protocol Data Unit，MDCP协议数据单元)，即MDCP PDU包括M_segment和后继指示字段。其中，后继指示字段可用 于表示当前的MDCP PDU是连续发送的多个MDCP PDU中的起始MDCP PDU、中间MDCP PDU或最后一个MDCP PDU；或者，是单独发送的一个MDCP PDU。
在SLC层，终端100可以通过层间接口获取到MDCP层下发的MDCP PDU，作为SLC SDU(SLC Service Data Unit，SLC服务数据单元)。在SLC层，终端100可以将SLC SDU分段成一个或多个(最多4个)固定长度的SLC分段数据(S_segment)，并在每个S_segment头部添加帧头信息，得到SLC PDU(SLC Protocol Data Unit，SLC协议数据单元)。
在PHY层，终端100可以通过层间接口获取到SLC层下发的SLC PDU，作为PHY层的编码块(code block)，并在code block的头部添加同步头，在code block的尾部添加校验位字段。其中，在上述卫星通信系统10中，可以采用循环冗余校验(cyclic redundancy check，CRC)对编码块进行校验，因此，该校验位字段中可以包括CRC码。终端100可以对code block和校验位字段进行编码(例如polar编码)，得到编码数据(coded data)，再在coded data中插入导频，得到导频编码数据(pilot+data)。然后，终端100通过底层硬件对同步头和导频编码数据依次进行调制得到调制数据(modulated data)。终端100可以对调制数据进行扩频，得到扩频调制数据(spread+modulated data)。终端100可以将扩频调制数据发送给短报文卫星21，经由短报文卫星21中继转发给卫星网络设备200。
下面介绍本申请实施例中提供的一种卫星通信系统10的入站数据的协议解析架构。
图5示出了本申请实施例中提供的一种卫星通信系统10的入站数据的协议解析架构示意图。
如图5所示，卫星网络设备200的卫星短报文传输协议层可以分为应用层(Application Protocol,APP)、消息数据汇聚层(Message Data Convergence Protocol，MDCP)、卫星链路控制层(Satellite Link Control，SLC)和物理层(Physical，PHY)。其中，卫星网络设备200可以包括卫星地面收发站22、卫星中心站23和卫星短报文融合通信平台24。卫星地面收发站22可用于负责PHY层的协议处理。卫星中心站23可用于负责SLC层和MDCP层的协议处理。卫星短报文融合通信平台24可用于负责APP层的协议处理。
卫星网络设备200在接收到终端100发送的数据时，卫星网络设备200的卫星短报文传输协议层的工作流程可以如下：
在PHY层，卫星网络设备200可以获取到终端100发送的经过调制和扩频后的导频编码数据。卫星网络设备200可以对接收到的扩频调制数据(spread+modulated data)进行解扩频，得到调制数据(modulated data)。然后，卫星网络设备200可以对调制数据进行解调，得到导频编码数据(pilot+data)。接着，卫星网络设备200去除导频编码数据中的导频信息，得到编码数据(code data)。然后，卫星网络设备200可以对编码数据进行解码，并通过校验位字段中的校验数据验证编码块(code block)的完整性。若完整，则卫星网络设备200可以提取出编码块(code block)，通过层间接口呈递给SLC层，作为SLC层的SLC PDU。
在SLC层，卫星网络设备200可以基于SLC PDU的帧头信息，将属于同一个SLC SDU的SLC PDU拼接成一个SLC SDU。卫星网络设备200可以将SLC SDU通过层间接口呈递给MDCP层，作为MDCP层的MDCP PDU。
在MDCP层，卫星网络设备200可以将属于同一个MDCP SDU的所有MDCP PDU拼接成一个MDCP SDU。卫星网络设备200可以将MDCP SDU通过层间接口呈递到APP层，作 为APP层接收到的应用层报文。
在APP层，卫星网络设备200可以基于应用层报文的报文头，对应用层报文进行解密、解压缩，得到原始数据。
本申请实施例中，上述协议处理过程仅为示例说明，本申请对协议处理的具体操作不作限定。
下面介绍本申请实施例中提供的一种卫星通信系统10的出站数据的协议封装架构。
图6示出了本申请实施例中提供的一种卫星通信系统10的出站数据的协议封装架构示意图。
如图6所示，卫星网络设备200中的卫星短报文传输协议层可以应用层(Application Protocol,APP)、消息数据汇聚层(Message Data Convergence Protocol，MDCP)、卫星链路控制层(Satellite Link Control，SLC)和物理层(Physical，PHY)。其中，卫星网络设备200可以包括卫星地面收发站22、卫星中心站23和卫星短报文融合通信平台24。卫星地面收发站22可用于负责PHY层的协议处理。卫星中心站23可用于负责SLC层和MDCP层的协议处理。卫星短报文融合通信平台24可用于负责APP层的协议处理。
卫星网络设备200发送数据给终端100时，卫星网络设备200中的卫星短报文传输协议的工作流程可以如下：
在APP层，卫星网络设备200可以将原始数据通过压缩算法，压缩成压缩数据，并在压缩数据前面添加压缩指示字段，其中，压缩指示字段可用于表示该压缩数据的压缩算法类型。之后，卫星网络设备200可以将压缩数据以及压缩指示字段一并加密，得到加密后数据，并在加密后数据的头部添加加密算法字段，该加密算法字段用于表示该加密后的数据的加密算法类型。卫星网络设备200还需在加密算法字段的头部添加业务类型字段，该业务类型字段可用于表示该原始数据的业务类型。卫星网络设备200可以将加密后数据、压缩指示字段、加密指示字段、业务类型字段封装成应用层报文下发给MDCP层。其中，该应用层报文可以包括报文头和报文数据。该报文头中可以包括压缩指示字段、加密指示字段和业务类型字段等等。该报文数据包括上述加密后数据。
在MDCP层，卫星网络设备200可以通过层间接口获取到APP层下发的应用层报文，并将应用层报文作为一个MDCP SDU。在MDCP层，卫星网络设备200可以将一个MDCP SDU拆分成一个或多个固定长度的MDCP分段数据(M_segement)，并在每个MDCP分段数据的头部添加后继指示字段，得到MDCP PDU，即MDCP PDU包括M_segement和后继指示字段。其中，后继指示字段可用于表示当前的MDCP PDU是连续发送的多个MDCP PDU的起始MDCP PDU或中间MDCP PDU或最后一个MDCP PDU；或者是单独发送的一个MDCP PDU。
在SLC层，卫星网络设备200可以通过层间接口获取到MDCP层下发的MDCP PDU，作为SLC SDU。在SLC层，卫星网络设备200可以将SLC SDU分段成一个或多个(最多4个)固定长度的SLC分段数据(S_segement)，并在每个S_segement头部添加帧头信息，得到SLC PDU。
在PHY层，卫星网络设备200可以通过层间接口获取到SLC层下发的SLC PDU。卫星网络设备200可以从SLC层获取到一个用户或多个用户的SLC PDU。卫星网络设备200可 以将多个用户的SLC PDU拼接在一起，再加上物理帧的帧头(例如版本号)作为PHY层的编码块(code block)，并在code block的尾部添加校验位(例如，循环冗余校验(cyclic redundancy check，CRC)码)，并对code block和CRC码进行编码(例如polar编码)，编码后的物理帧加上保留段可以组成一个固定长度的物理时隙的电文支路(S2C_d支路)的编码数据。其中，卫星网络设备200可以将一个用户的多个SLC PDU分别放到不同的物理帧中。然后，卫星网络设备200将S2C_d支路的编码数据和导频支路(S2C_p支路)的导频信息组成导频编码数据，即出站数据。卫星网络设备200可以将出站数据发送给短报文卫星21，经由短报文卫星21中继转发给终端100。
可以理解的是，S2C_p支路的导频信息与卫星波束相关。当卫星波束号是已知信息时，S2C_p支路的导频信息也是已知的，无需解码的。而S2C_d支路的编码数据是需要解码的。
下面介绍本申请实施例中提供的一种卫星通信系统10的出站数据的协议解析架构。
图7示出了本申请实施例中提供的一种卫星通信系统10的出站数据的协议解析架构示意图。
如图7所示，终端100的卫星短报文传输协议层可以分为应用层(Application Protocol,APP)、消息数据汇聚层(Message Data Convergence Protocol，MDCP)、卫星链路控制层(Satellite Link Control，SLC)和物理层(Physical，PHY)。
终端100在接收到卫星网络设备发送的数据时，终端100的卫星短报文传输协议层的工作流程可以如下：
在PHY层，终端100可以获取到卫星网络设备200发送的经过调制和扩频后的导频编码数据。终端100可以对接收到的扩频调制数据(spread+modulated data)进行解扩频，得到调制数据(modulated data)。然后，终端100可以对调制数据进行解调，得到导频编码数据(pilot+data)。接着，终端100可以去除导频编码数据中的导频信息，得到编码数据(code data)。然后，终端100可以对编码数据进行解码，并通过校验位字段中的校验数据验证编码块(code block)的完整性。若完整，则终端100可以提取出编码块(code block)，通过层间接口呈递给SLC层，作为SLC层的SLC PDU。
这里，该导频编码数据即为上述卫星网络设备200发送的出站数据，该出站数据由S2C_d支路的编码数据和导频支路(S2C_p支路)的导频信息组成。
在SLC层，终端100可以基于SLC PDU的帧头信息，将属于同一个SLC SDU的SLC PDU拼接成一个SLC SDU。终端100可以将SLC SDU通过层间接口呈递给MDCP层，作为MDCP层的MDCP PDU。
在MDCP层，终端100可以将属于同一个MDCP SDU的所有MDCP PDU拼接成一个MDCP SDU。终端100可以将MDCP SDU通过层间接口呈递到APP层，作为APP层接收到的应用层报文。
在APP层，终端100可以基于应用层报文的报文头，对应用层报文进行解密、解压缩，得到原始数据。
本申请实施例中，上述协议处理过程仅为示例说明，本申请对协议处理的具体操作不作限定。
在一种可能的实现方式中，终端100无法使用除了卫星网络以外的其他网络资源(例如，蜂窝网络)，即，处于无信号的状态时，例如，当终端100处于海洋、沙漠、草原、无人区等移动通信未覆盖、或覆盖不了、或通信系统被破坏的区域时。终端100可以通过卫星网络与其他终端通信。其中，终端100加入第一多播群组，终端100可以通过卫星网络发送多播短消息给第一多播群组中的其他终端，也可以通过卫星网络接收第一多播群组中的其他终端发送给终端100的多播短消息。这样，用户可以通过终端100实现卫星系统下的多播短消息的传输。
具体的，终端100可以响应于用户发送多播短消息的输入，响应于该输入，基于用户输入的文本消息和多播ID生成入站多播短消息。终端100可以向卫星网络设备200发送该入站多播短消息，入站多播短消息包括第一类型指示字段，多播ID字段，第一类型指示字段用于指示入站多播短消息的业务类型，多播ID字段用于指示该入站多播短消息所属的多播群组。
接下来介绍本申请实施例提供的一组界面示意图。
示例性的，如图8A所示，终端100可以显示桌面801。其中，桌面801可以包括多个应用图标，例如，第一通讯应用图标803等等。其中，该第一通讯应用图标803可以用于触发显示第一通讯应用的界面(如图8B所示的第一通讯应用界面810)，其中，第一通讯应用可以用于接收/发送卫星短消息。例如，第一通讯应用可以为短信、畅联等等。其中，桌面801的上方还可以显示状态栏802，该状态栏802中可以显示提示图标802A，提示图标802A用于指示终端100与蜂窝网络断开通信连接，此时，终端100处于无蜂窝信号的状态。
终端100接收到用户针对第一通讯应用图标803的输入(例如单击)，响应于该输入，终端100可以显示如图8B所述的第一通讯应用界面810。
如图8B所示，第一通讯应用界面810可以包括新建控件811，新建控件811可以用于触发终端100显示联系人选择界面。第一通讯应用界面810中还可以显示有多播群组控件812和历史联系人条目，历史联系人条目中可以显示有历史联系人的信息和历史联系人的最近消息记录，历史联系人条目还可以用于触发终端100显示和该历史联系人的信件编辑界面。多播群组控件812可以用于触发终端100显示多播群组功能界面(如图8C所示的多播群组功能界面820)。
终端100接收用户针对多播群组控件812的输入(例如单击)，响应于该输入，终端100可以显示多播群组功能界面820。如图8C所示，多播群组功能界面可以包括新建控件821，该新建控件821可以用于触发终端100显示多播群组选择界面。多播群组功能界面820中还可以显示有历史多播群组条目，历史多播群组条目中可以显示有历史多播群组的信息和历史多播群组的最近消息记录，历史多播群组条目还可以用于触发终端100显示和该历史多播群组的信件编辑界面。
终端100接收到用户针对新建控件821的输入(例如单击)，响应于该输入，终端100可以显示如图8D所示的多播群组选择界面830。该多播群组选择界面830可以显示有多播群组显示区域831。多播群组显示区域831可以显示多个多播群组图标，例如多播群组图标831A，多播群组图标可用于触发显示和该多播群组图标对应的多播群组通信的信息编辑界面。
终端100接收到用户针对多播群组图标831C的输入(例如单击)，响应于该输入，终端100可以显示与该多播群组图标831C对应的第三群组的多播群组信息编辑界面840。
如图8E所示，多播群组信息编辑界面840可以包括但不限于编辑栏841和发送控件842 等等。其中编辑栏841可以用于显示用户输入的文本消息内容。发送控件842可以用于触发终端100将包括有编辑栏841中显示的文本消息内容的多播短消息发送至卫星网络设备200。多播群组信息编辑界面840还可以显示有键盘显示区域843和更多图标844，键盘显示区域843可以用于输入文本消息内容，更多图标844可以用于触发显示该多播群组中的用户成员信息。
终端100可以接收到用户针对键盘显示区域843的输入，并将用户输入的内容显示在编辑栏841中。如图8E所示，终端100可以通过键盘显示区域843接收并在编辑栏841中显示用户输入的文本消息。其中，该文本消息可以为“安全到达营地”。
终端100可以接收用户针对发送控件842的输入(例如单击)，响应于该输入，终端100可以显示如图8F所示的多播群组信息编辑界面850。多播群组信息编辑界面850可以包括多播信息框851。其中，多播信息框851可以用于显示用户发送的编辑栏841中的内容。
卫星网络设备200接收到终端100发送的入站多播短消息后，卫星网络设备200识别出该消息为多播短消息后，可以从该入站多播短消息中解析出多播ID，然后根据该多播ID将该多播短消息发送给该多播ID指示的多播群组中的其他终端。以该多播ID指示的多播群组为第三群组为例，第三群组中的成员包括终端100、终端200和终端300，卫星网络设备200将该多播短消息发送给终端200和终端300。终端200或终端300可以在接收到该多播短消息后，可以显示该多播短消息。
可以理解的是，本发明实施例示意的用户界面并不构成对终端100的具体限定。在本申请另一些实施例中，终端100可以采用其他的用户界面。
接下来介绍本申请实施例提供的另一组界面示意图。
在一种可能的实现方式中，终端200在接收到多播短消息后，可以显示接收信息提示，接收信息提示可以用于提示用户收到一条来自终端100的多播短消息。
示例性的，终端200可以显示如图9A所示的桌面900。其中，桌面900可以包括多个应用图标，例如，第一通讯应用图标等等。其中，该第一通讯应用图标可以用于触发显示第一通讯应用的界面，其中，第一通讯应用可以用于接收/发送卫星短消息。例如，第一通讯应用可以为短信、畅联等等。
其中，桌面900的上方还可以显示状态栏901，该状态栏901中可以显示提示图标901A，提示图标901A用于指示终端200与蜂窝网络断开通信连接，此时，终端200处于无蜂窝信号的状态。显示状态栏901中还可以显示提示图标901B，提示图标901B用于提示终端200处于卫星信号覆盖范围内，可以使用卫星通信系统进行通信。
其中，多个应用图标的上方还可以显示接收信息提示902。接收信息提示902可以用于提示用户接收到一条来自终端100的卫星多播短消息。例如，接收信息提示902可以包括文字类提示信息：“接收到来自终端100的一条卫星多播短消息”。接收信息提示902还可以包括应用标识903，应用标识903可以用于指示显示卫星消息的应用软件。例如，应用标识903可以用于指示终端200通过第一通讯应用接收该卫星多播短消息。也就是说，应用标识903可以提示用户可以通过第一通讯应用查看该卫星消息。终端200可以在接收到用户针对接收信息提示902的输入(例如单击)后，响应于该输入，通过第一通讯应用显示接收到的卫星短消息的内容。
终端200可以在接收到用户针对如图9A所示的接收信息提示902的输入(例如单击) 后，响应于该输入，显示如图9B所示的信息编辑界面910。
示例性的，如图9B所示，信息编辑界面910可以包括信息框911。其中，信息框911可以用于显示接收到的多播短消息中的文本消息的内容。可选的，信息框911中还可以用于显示该多播短消息的发送方，例如终端100。可选的，信息框911还可以显示该多播短消息发送的时间信息，图9B中未示出。其中，图9B中示出的为终端200的第四群组，即终端100中的第三群组对应着终端200中的第四群组，本申请实施例对此不作限定。
可以理解的是，本发明实施例示意的用户界面并不构成对终端200的具体限定。在本申请另一些实施例中，终端200可以采用其他的用户界面。
图10A示出了本申请实施例中提供的一种卫星通信系统中多播短消息传输的流程示意图。
如图10A所示，该方法包括：
S1001，终端100基于文本信息和多播ID生成入站多播短消息报文。
具体的，终端100可以将文本消息和多播ID作为原始数据，并基于原始数据得到应用层报文，该应用层报文为入站多播短消息报文，终端100基于原始数据得到应用层报文的详细描述可以参见图4所示的实施例，在此不再赘述。
在一些实施例中，终端100可以接收到用户如图8E的操作后，得到文本信息和多播ID。其中文本信息为安全到达营地，多播ID为用户选择的第三群组对应的多播ID。
在一种可能的实施方式中，终端100中的第三群组中的成员终端可以在蜂窝网络下，与对应的应用服务器协商，确定第三群组的多播ID或者群组虚拟波束信息(例如同步头信息)，用于指示第三群组在卫星通信系统中的标识。其中，终端设备可以在物理层通过群组虚拟波束信息来识别接收到的物理层数据为多播短消息报文。
在一种可能的实现方式中，入站多播短消息报文的格式可以如下表1所示。
表1
Figure PCTCN2022134866-appb-000001
如上表1所示，入站多播短消息报文中可以包括回执指示字段、业务类型字段、加密指示字段、压缩指示字段、应用层鉴权码字段、多播ID字段，文本消息字段。可以理解的是，本申请实施例中的入站多播短消息报文中包含具体字段以及字段的排列顺序不作限定。例如，当入站多播短消息报文默认不需要应用层回执时，该入站多播短消息报文中可以不包含回执指示字段。
表1中示出的入站多播短消息报文中各个字段的具体说明可以如下表2所示。
表2
Figure PCTCN2022134866-appb-000002
Figure PCTCN2022134866-appb-000003
如表2所示，回执指示字段可以用于指示该入站多播短消息报文的接收设备(例如卫星网络设备200)是否需要向终端200回复应用层回执。应用层回执可以用于指示接收设备是否成功接收该入站多播短消息报文。回执指示字段的长度可以是1bit。当该回执指示字段为数值D1(例如，0)时，可以用于指示该入站多播短消息报文的接收设备不需要向终端200回复应用层回执。当该回执指示字段为数值D2(例如，1)时，可以用于指示该入站多播短消息报文的接收设备需要向终端200回复应用层回执。可以理解的是，本申请实施例对回执指示字段的长度以及回执指示字段的具体取值不作限定。
如表2所示，业务类型字段可以用于指示该入站多播短消息报文的业务类型。在卫星短报文通信中，报文的业务类型可以包括通用报文，多播多消息查询和多播短消息下载等等。该业务类型字段的长度可以是4bit。可以理解的是，本申请实施例对该业务类型字段的长度不作限定。当业务类型的种类越来越多时，该业务类型的字段的长度可以越来越长。本申请实施例以业务类型字段的长度为4bit为例进行举例说明。当该业务类型字段为0000时，指示该应用层报文为通用报文。该业务类型指示字段其他取值的含义可以参见表2所示，在此不再一一赘述。需要说明的是，在本申请实施例中，入站多播短消息报文的业务类型为通用报文业务类型。
如表2所示，加密指示字段可以用于指示该入站多播短消息报文是否加密。示例性地，加密指示字段的长度可以是2bit。当加密指示字段为数值D3(例如，00)时，指示该入站多播短消息报文未加密。可以理解的是，本申请实施例对该加密指示字段的长度和加密指示字段的具体取值不作限定。
如表2所示，压缩指示字段可以用于指示该入站多播短消息报文是否压缩。示例性地，压缩指示字段的长度可以是2bit。当压缩指示字段为数值D4(例如，00)时，指示该入站多 播短消息报文未压缩。可以理解的是，本申请实施例对该压缩指示字段的长度和压缩指示字段的具体取值不作限定。
如表2所示，多播ID字段可以用于指示该入站多播短消息对应的多播群组的标识。该多播ID字段的长度可以是10bit。可以理解的是，本申请实施例对该多播ID字段的长度不作限定。
如表2所示，文本消息字段可以用于指示该入站多播短消息的内容。该文本消息字段的长度可以是Nbit。可以理解的是，本申请实施例对该文本消息字段的长度不作限定。
可选的，入站多播短消息报文中还可以包括位置信息字段，该位置信息字段可用于指示终端100当前所处的位置的信息，该位置信息中可以包括终端100当前所处位置的经度和维度。其中，终端100可以基于卫星导航系统获取终端100当前位置信息，例如，全球导航卫星系统(global navigation satellite system，GNSS)、北斗卫星导航系统(beidou navigation satellite system，BDS)等等。
S1002，终端100基于入站多播短消息生成一个或多个第一用户帧。
具体的，终端100可以通过层间接口将入站多播短消息报文下发至MDCP层。终端100可以在MDCP层将入站多播短消息报文分段成一个或多个MDCP PDU。然后，终端100再将一个或多个MDCP PDU下发至SLC层。终端100可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。在SLC层，终端100可以在每个第一用户帧的帧头中的用户ID字段中填入终端100的标识(例如，终端100的手机号码)。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
在一种可能的实现方式中，第一用户帧的格式可以如下表3所示。
表3
Figure PCTCN2022134866-appb-000004
如表3所示，第一用户帧可以包括版本号字段、帧类型指示字段、用户ID字段、出站链路指示字段、AM-Enable字段、NDI(New Data Indicator)字段、帧总数字段、帧序号字段、用户信息字段等等。可以理解的是，本申请实施例中的第一用户帧中包含具体字段以及字段的排列顺序不作限定。
表3中示出的第一用户帧中各个字段的具体说明可以如下表4所示。
表4
Figure PCTCN2022134866-appb-000005
Figure PCTCN2022134866-appb-000006
如表4所示，版本号字段用于指示当前使用的卫星通信协议的版本。其中，该版本号字段的数据长度可以为3bit。可以理解的是，本申请实施例对版本号字段的长度不作限定。在一些实施例中，第一用户帧中可以不包括版本号字段。
如表4所示，帧类型字段可用于指示第一用户帧的帧类型。其中，帧类型字段的数据长度可以为3bit。帧类型可以包括通用数据帧(或者可称为信息报文帧)、ACK帧、回执帧、位置上报帧、应急救援帧、多播短消息帧等等。需要说明的是，在本申请实施例中，第一用户帧的帧类型为多播短消息帧类型。
如表4所示，用户ID字段可用于指示终端100的设备标识。其中，该用户ID字段的数据长度可以为34bit。可以理解的是，本申请实施例对用户ID字段的长度不作限定。
如表4所示，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息。其中，该出站链路指示字段的数据长度可以为16bit。可以理解的是，本申请实施例对出站链路指示字段的长度不作限定。在一些实施例中，第一用户帧中可以不包括出站链路指示字段。
如表4所示，AM-Enable字段用于指示是否需要接收方对第一用户帧反馈确认信息。其中，该AM-Enable字段的数据长度可以为1bit。当该AM-Enable字段为数值A1(例如，0)时，可以用于指示该第一用户帧不需要接收方反馈确认信息；当该AM-Enable字段为数值A2(例如，1)时，可以用于指示该第一用户帧需要接收方反馈确认信息。可以理解的是，本申请实施例对AM-Enable字段的长度不作限定。在一些实施例中，第一用户帧中可以不包括AM-Enable字段。
如表4所示，NDI字段用于指示第一用户帧是否为重传用户帧。其中，该NDI字段的数据长度可以为1bit。具体的，当NDI发生翻转时，指示第一用户帧不是重传用户帧。可以理解的是，本申请实施例对NDI字段的长度不作限定。在一些实施例中，第一用户帧中可以不包括NDI字段。
如表4所示，帧总数字段可用于表示该第一用户帧所在的SLC SDU中包括的用户帧的总数量。其中，该帧总数字段的长度可以是2bit。当帧总数字段的长度为2bit时，一个SLC SDU中最多可包括4个位置上报帧。可以理解的是，本申请实施例对帧总数字段的长度不作限定。
如表4所示，帧序号字段可用于指示该多播短消息帧在一个SLC SDU中的顺序。该帧序号字段的长度可以是2bit。
如表4所示，用户信息字段可用于指示第一用户帧的数据内容。具体的，第一用户帧的数据内容为SLC SDU的全部或一部分。可以理解的是，本申请实施例对用户信息字段的长度不作限定。
可以理解的是，第一用户帧的帧类型指示字段为终端100在SLC层基于APP层下发的报文业务类型指示得到的，例如，APP层通过层间接口下发入站多播短消息报文时，指示该 入站多播短消息报文的业务类型为入站多播短消息类型，则终端100在SLC层将帧类型设置为多播短消息帧类型。
S1003，终端100将一个或多个第一用户帧发送至卫星网络设备200。
终端100可以将一个或多个第一用户帧发送给卫星网络设备200。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
在一些实施例中，终端100可以在接收到用户的第一输入后，响应于该第一输入，生成并向卫星网络设备200发送该一个或多个第一用户帧。其中，第一输入不限于单击、双击、长按、滑动、语音指令输入等等。例如，第一输入可以为上述图8E所示的针对发送控件842的输入。
S1004，卫星网络设备200确定第一用户帧为多播短消息帧，并基于一个或多个第一用户帧得到多播ID和文本信息。
卫星网络设备200在接收到该一个或多个第一用户帧后，可以在SLC层基于帧类型字段确定出第一用户帧为多播短消息帧，基于用户ID字段确定发送方ID，并基于一个或多个第一用户帧得到多播ID和文本信息。示例性的，发送方ID可以为终端100的手机号码。
具体的，卫星网络设备200将终端100发送的一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU。然后，卫星网络设备200将该一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，卫星网络设备200可以在MDCP层将一个或多个MDCP PDU组装成MDCP SDU。然后，卫星网络设备200可以将MDCP SDU上传至APP层作为入站多播短消息报文。这里可以参考图4中卫星通信系统的入站数据的解封装过程的描述，此处不再赘述。
可选的，入站多播短消息报文包括有位置信息，卫星网络设备200可以在APP层基于该MDCP SDU得到位置信息。
可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星网络设备200可以在SLC层基于第一用户帧得到出站链路指示信息。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星中心站23在SLC层基于帧类型字段确定出第一用户帧为多播短消息帧后，在MDCP层基于一个或多个第一用户帧得到MDCP SDU。卫星中心站23向卫星短报文融合通信平台24发送MDCP SDU和第一用户帧的帧类型。卫星短报文融合通信平台24在APP层基于该MDCP SDU得到文本信息和多播ID。可选的，入站多播短消息报文包括有位置信息，卫星短报文融合通信平台24在APP层基于该MDCP SDU还可以得到位置信息。可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星中心站23还向卫星短报文融合通信平台24发送出站链路指示信息。
在一些实施例中，如图11所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，卫星中心站23在SLC层基于帧类型字段确定出第一用户帧为多播短消息帧后，在MDCP层基于一个或多个第一用户帧得 到MDCP SDU。卫星中心站23向广播多播中心29发送MDCP SDU和第一用户帧的帧类型。广播多播中心29在APP层基于该MDCP SDU得到文本信息和多播ID。可选的，入站多播短消息报文包括有位置信息，广播多播中心29在APP层基于该MDCP SDU还可以得到位置信息。可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星中心站23还向广播多播中心29发送出站链路指示信息。
需要说明的是，在图11所示的卫星通信系统的架构图中，广播多播中心29和位置中心28可以相互通信。可选的，广播多播中心29可以和短消息中心25之间可以相互通信，短消息中心25可以和位置中心28之间相互通信，图11中未示出。本申请实施例对具体的连接方式不作限定。
S1005，卫星网络设备200基于入站短消息报文中的多播ID确定目标用户ID，并确定出站多播短消息的卫星信息和波束信息。
卫星网络设备200可以从入站多播短消息报文中得到多播ID字段和文本信息。卫星网络设备200可以基于多播ID字段确定该文本信息的目标用户ID。例如，当卫星网络设备200基于多播ID字段确定出多播ID对应的多播群组为第三群组时，查询第三群组中的成员信息为终端100、终端200和终端300，那么卫星网络设备200确定该文本信息的目标用户ID为终端200的用户ID和终端300的用户ID。可选的，卫星网络设备200可以向位置中心28查询多播ID对应的多播群组的成员终端信息，位置中心28可以基于多播ID向卫星网络设备200发送多播群组的成员终端信息。
可选的，第一用户帧包括有出站链路指示字段，卫星网络设备200在SLC层基于该出站链路指示字段确定出站多播短消息的卫星信息和波束信息。
可选的，入站多播短消息报文中包括有位置信息，该位置信息为终端100所在的位置。卫星网络设备200基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的，卫星网络设备200可以以终端100所在的位置为中心，以第一长度为半径生成一个圆，该圆范围内的卫星和波束确定为出站多播短消息的卫星信息和波束信息。其中，第一长度可以是10千米，本申请实施例对第一长度的具体取值不作限定。
可选的，卫星网络设备200可以向位置中心28请求终端100的位置信息。卫星网络设备200可以向位置中心28发送终端100的用户ID信息，位置中心28根据终端100的用户ID查询到终端100的位置信息后，向卫星网络设备200发送终端100的位置信息。卫星网络设备200基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的确定方式可以参考上述实施例的描述，在此不再赘述。
在一些实施例中，卫星网络设备200可以响应于接收到入站多播短消息，向位置中心28请求终端100的位置信息。
在一些实施例中，卫星网络设备200可以周期性的向位置中心28请求终端100的位置信息，并将得到的终端100的位置信息保存在本地。
在一些实施例中，卫星网络设备200向位置中心28请求终端100的位置信息，并指示位置中心28在终端100的位置发生变化时向卫星网络设备200发送终端100的位置信息。卫星网络设备200将得到的终端100的位置信息保存在本地。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星短报文融合通信平台24接收到卫星中心站23发送的MDCP SDU和第一用户帧的帧类型后，卫星短报文融合通信平台24在APP层基于该MDCP SDU得到多播ID字段和文本信息。卫星短报文融合通信平台24可以基于多播ID字段确定该文本信息的目标用户ID。具体的确定方式可以参考上述实施例的描述，在此不再赘述。
可选的，第一用户帧包括有出站链路指示字段，卫星中心站23在SLC层基于第一用户帧得到该出站链路指示字段，并将该出站链路指示字段发送给卫星短报文融合通信平台24。卫星短报文融合通信平台24基于该出站链路指示字段确定出站多播短消息的卫星信息和波束信息。在一种可能的实现方式中，卫星中心站23在SLC层基于第一用户帧得到该出站链路指示字段，并基于该出站链路指示字段确定出站多播短消息的卫星信息和波束信息。卫星中心站23将该卫星信息和波束信息发送给卫星短报文融合通信平台24。
可选的，入站多播短消息报文中包括有位置信息，卫星短报文融合通信平台24在APP层基于该MDCP SDU得到该位置信息。卫星短报文融合通信平台24基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的确定方式可以参考上述实施例的描述，在此不再赘述。
可选的，卫星短报文融合通信平台24可以通过短消息中心25向位置中心28发送位置查询请求，该位置查询请求用于请求查询终端100的位置信息。卫星短报文融合通信平台24可以向位置中心28发送终端100的用户ID信息，位置中心28根据终端100的用户ID查询到终端100的位置信息后，向卫星短报文融合通信平台24发送终端100的位置信息。卫星短报文融合通信平台24基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的卫星信息和波束信息的确定方式可以参考上述实施例的描述，在此不再赘述。具体的位置请求方式可以参考上述实施例的描述，在此不再赘述。
在一些实施例中，如图11所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，广播多播中心29接收到卫星中心站23发送的MDCP SDU和第一用户帧的帧类型后，广播多播中心29在APP层基于该MDCP SDU得到多播ID字段和文本信息。广播多播中心29可以基于多播ID字段确定该文本信息的目标用户ID。具体的确定方式可以参考上述实施例的描述，在此不再赘述。
可选的，第一用户帧包括有出站链路指示字段，卫星中心站23在SLC层基于第一用户帧得到该出站链路指示字段，并将该出站链路指示字段发送给广播多播中心29。广播多播中心29基于该出站链路指示字段确定出站多播短消息的卫星信息和波束信息。在一种可能的实现方式中，卫星中心站23在SLC层基于第一用户帧得到该出站链路指示字段，并基于该出站链路指示字段确定出站多播短消息的卫星信息和波束信息。卫星中心站23将该卫星信息和波束信息发送给广播多播中心29。
可选的，入站多播短消息报文中包括有位置信息，广播多播中心29在APP层基于该MDCP SDU得到该位置信息。广播多播中心29基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的确定方式可以参考上述实施例的描述，在此不再赘述。
可选的，广播多播中心29可以向位置中心28请求终端100的位置信息。广播多播中心29可以向位置中心28发送终端100的用户ID信息，位置中心28根据终端100的用户ID查 询到终端100的位置信息后，向广播多播中心29发送终端100的位置信息。广播多播中心29基于位置信息确定出站多播短消息的卫星信息和波束信息。具体的卫星信息和波束信息的确定方式可以参考上述实施例的描述，在此不再赘述。具体的位置请求方式可以参考上述实施例的描述，在此不再赘述。
S1006，卫星网络设备200基于文本信息和多播ID生成出站多播短消息报文。
具体的，卫星网络设备200可以将文本信息、发送方ID和多播ID作为原始数据，并基于原始数据得到应用层报文，该应用层报文为出站多播短消息报文。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星短报文融合通信平台24在APP层将文本消息、发送方的用户ID和多播ID作为原始数据，并基于原始数据得到应用层报文，该应用层报文为出站多播短消息报文。
在一些实施例中，如图11所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，广播多播中心29在APP层将文本消息、发送方的用户ID和多播ID作为原始数据，并基于原始数据得到应用层报文，该应用层报文为出站多播短消息报文。
在一种可能的实现方式中，出站多播短消息报文的格式如表5所示。
表5
Figure PCTCN2022134866-appb-000007
如上表5所示，多播短消息报文可以包括消息类型指示字段、多播短消息下载完成指示字段、加密指示字段、压缩指示字段、应用层鉴权码字段、多播群组数量字段、多播ID字段、发送方ID字段、消息原始发送时间字段、多播短消息内容字段、多播短消息ID字段。可以理解的是，本申请实施例中的多播短消息报文中包含具体字段以及字段的排列顺序不作限定。例如，若对多播短消息报文未进行加密，多播短消息报文中也可以不包括加密指示字段。
表5中示出的出站多播短消息报文中各个字段的具体说明可以如下表6所示。表6示例性地示出了表5中各个字段对应的长度以及具体说明。
表6
Figure PCTCN2022134866-appb-000008
Figure PCTCN2022134866-appb-000009
如表6所示，消息类型指示字段可以用于指示该出站多播短消息报文的消息类型。在卫星短报文通信中，报文的消息类型可以包括信箱概况、信件消息、多播短消息查询结果和多播短消息等等。该消息类型指示字段的长度可以是2bit。可以理解的是，本申请实施例对该消息类型指示字段的长度不作限定。当消息类型的种类越来越多时，该消息类型指示字段的长度可以越来越长。本申请实施例以消息类型指示字段的长度为2bit为例进行举例说明。当该消息类型指示字段为00时，指示该应用层报文为消息概况报文。该消息类型指示字段其他取值的含义可以参见表6所示，在此不再一一赘述。需要说明的是，在本申请实施例中，出站多播短消息的消息类型为多播短消息类型。
其中，表6中的加密指示字段、压缩指示字段和应用层鉴权码字段的具体说明可以参考S1001的描述，在此不再赘述。
如表6所示，多播短消息下载完成指示字段可以用于指示后续是否还有多播短消息发送给终端200。该多播短消息下载完成指示字段的长度可以是1bit。当多播短消息下载完成指示字段为数值M1(例如1)时，可以用于指示后续还有多播短消息发送给终端200。当多播短消息下载完成指示字段为数值M2(例如0)时，可以用于指示后续没有多播短消息发送给终端200。可以理解的是，本申请实施例对该多播短消息下载完成指示字段的长度和具体取值不作限定。需要说明的是，出站多播短消息报文中可以不包括该多播短消息下载完成指示字段。
如表6所示，多播ID可以用于指示该多播短消息报文对应的多播群组的ID。示例性的，多播ID的数据长度可以是10bit。可以理解的是，本申请实施例对多播ID字段的长度不作限定。
如表6所示，发送方ID字段可以用于指示发送该多播短消息的目标终端的标识。示例性地，发送方ID字段中可以为34bit的目标终端的标识(例如手机号码)。可以理解的是，本申请实施例对发送方ID字段的长度和发送方ID字段的具体取值不作限度。
如表6所示，多播短消息原始发送时间字段用于指示多播短消息的原始发送时间，即目标终端发送该多播短消息的时间。示例性地，多播短消息原始发送时间字段的长度可以是7bit。可以理解的是，本申请实施例对多播短消息原始发送时间字段的长度不作限定。
如表6所示，多播短消息ID字段用于指示多播短消息的ID。示例性地，多播短消息ID字段的长度可以是4bit。可以理解的是，本申请实施例对多播短消息ID字段的长度不作限定。
如表6所示，多播短消息内容字段可以用于指示目标多播群组发送给终端200的多播短消息的内容。示例性地，多播短消息内容字段的长度可以是Nbit。可以理解的是，本申请实施例对多播短消息内容字段的长度不作限定。
在一些实施例中，当多播ID指示的是订阅服务的多播群组，订阅服务可以由应用服务器 提供，此时直接从S1006开始执行。其中，应用服务器可以将文本信息和多播ID发送给卫星网络设备200。需要说明的是，出站多播短消息报文中可以不包括发送方ID字段。
S1007，卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧。
具体的，卫星网络设备200可以将出站多播短消息报文和目标用户ID下发至MDCP层。卫星网络设备200可以在MDCP层将出站多播短消息报文分段成一个或多个MDCP PDU。然后，卫星网络设备200再将一个或多个MDCP PDU至SLC层，作为SLC层的SLC SDU，并将目标用户ID下发至SLC层。卫星网络设备200可以在SLC层将每一个SLC SDU分段成一个或多个第二用户帧。在SLC层，卫星网络设备200可以在每一个第二用户帧的用户ID字段中填入目标用户ID。卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。需要说明的是，在本申请实施例中，一个或多个第二用户帧的帧类型为通用数据帧类型。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星短报文融合通信平台24可以将出站多播短消息报文和目标用户ID发送给卫星中心站23。卫星中心站23将出站多播短消息报文分段成一个或多个第二用户帧。
在一些实施例中，如图11所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，广播多播中心29将出站多播短消息报文和目标用户ID发送给卫星中心站23。卫星中心站23将出站多播短消息报文分段成一个或多个第二用户帧。
S1008，卫星网络设备200向目标用户发送一个或多个第二用户帧。
卫星网络设备200可以使用在S1005中确定的卫星信息和波束信息，将一个或多个第二用户帧发送给目标用户。具体的，卫星网络设备200可以发送完一个第二用户帧，收到目标用户回复的成功接收该第二用户帧后，再向目标用户发送第二个第二用户帧。可选的，卫星网络设备200也可以依次地将一个或多个第二用户帧发送给目标用户，目标用户在接收完全部的第二用户帧后再向卫星网络设备200回复成功接收第二用户帧。或者，目标用户也可以不回复。本申请实施例对此不作限定。
可以理解的是，在本申请实施例中，出站多播短消息报文是发送给特定的目标终端的出站多播短消息报文。当多播ID所属群组中存在N个目标用户时，卫星网络设备200循环执行N次S1007和S1008。例如，当多播ID所述群组为第三群组，第三群组中包括终端100、终端200和终端300时，卫星网络设备200分别将终端200和终端300作为目标用户执行S1007和S1008。
在本申请实施例中，以目标用户是终端200为例进行说明。
S1009，终端200接收一个或多个第二用户帧。
终端200可以接收到一个或多个第二用户帧。具体的接收过程可以参考图7所示实施例的描述，在此不再赘述。
在一种可能的实现方式中，当终端200收齐一个或多个第二用户帧后，向卫星网络设备 200回复已收齐一个或多个第二用户帧。
进一步地，终端200可以在SLC层解析出每个第二用户帧的帧头中的用户ID字段。若终端200从用户ID字段中解析出的用户ID和终端200的标识相同，则终端200将该一个或多个第二用户帧上传至MDCP层继续解析。若终端200从用户ID字段中解析出的用户ID和终端200的标识不同，则终端200可以确定该第二用户帧不是发送给终端200的，终端200可以丢弃该第二用户帧。
S1010，终端200将一个或多个第二用户帧组装成出站多播短消息报文。
具体的，终端200可以将一个或多个第二用户帧在SLC层组装一个或多个SLC SDU。然后，终端200将一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，终端200可以在MDCP层将一个或多个MDCP PDU拼成MDCP SDU。然后，终端200可以将MDCP SDU上传至APP层作为出站多播短消息报文。这里可以参考图7中卫星通信系统的出站数据的解封装过程的描述，此处不再赘述。
S1011，终端200解析出出站多播短消息报文中终端100发送给终端200的多播短消息的内容。
终端200可以在APP层基于多播短消息报文得到多播ID字段、发送方ID字段以及多播短消息内容字段等等，从而确定该多播短消息对应的多播群组和发送方。
S1012，终端200显示终端100发送给终端200的多播短消息的内容。
终端200可以在显示屏中显示目标多播群组发送给终端200的多播短消息的内容。示例性地，发送方ID为终端100的用户ID，多播ID所指示的多播群组为终端200中的第四群组，那么终端100将使用第一通讯应用在第四群组中显示该信件内容，该信件内容的发送方为终端100，可以参考图9B所示。终端200也可以以其他形式提示用户目标多播群组发送给终端200的短消息的内容，例如，终端200语音播报目标多播群组发送给终端200的信件的内容，本申请实施例对具体的显示形式不作限定。
这样，通过本申请实施例提供的一种卫星通信系统中多播短消息传输的方法，终端100在卫星网络下，未驻留蜂窝网络，也可以通过卫星网络向目标多播群组中其他的终端发送多播短消息。
图12A示出了本申请实施例中提供的另一种卫星通信系统中多播短消息传输的流程示意图。
如图12A所示，该方法包括：
S1201，终端100基于文本信息和多播ID生成入站多播短消息报文。
终端100基于文本信息和多播ID生成入站多播短消息报文的具体过程可以参见S1001的具体描述，在此不再赘述。
其中，入站多播短消息报文的格式可以参考表1所示，在此不再赘述。
需要说明的是，在本申请实施例中，该入站多播短消息报文中的业务类型字段的取值可以为1011，用于指示该入站多播短消息报文的业务类型为多播短消息类型，即本申请实施例 中通过该业务类型指示字段来指示该应用层报文为入站多播短消息报文。
S1202，终端100基于入站多播短消息生成一个或多个第一用户帧。
终端100基于入站多播短消息生成一个或多个第一用户帧的具体过程可以参见S1002的具体描述，在此不再赘述。
其中，第一用户帧的格式可以参考表3所示，在此不再赘述。
需要说明的是，在本申请实施例中，第一用户帧的帧类型字段取值为0000，用于指示该第一用户帧为通用数据帧。
S1203，终端100将一个或多个第一用户帧发送至卫星网络设备200。
终端100将一个或多个第一用户帧发送至卫星网络设备200的具体过程可以参见S1003的具体描述，在此不再赘述。
S1204，卫星网络设备200基于业务类型指示字段确定接收到的应用层报文为入站多播短消息。
卫星网络设备200可以在SLC层和MDCP层基于一个或多个第一用户帧得到MDCP SDU。卫星网络设备200可以将MDCP SDU上传至APP层，将其作为APP层的应用层报文，即入站多播短消息报文。入站多播短消息报文中包括业务类型指示字段，卫星网络设备200基于该类型指示字段确定该应用层报文为入站多播短消息报文。可选的，入站多播短消息报文包括有位置信息，卫星网络设备200可以在APP层基于该MDCP SDU得到位置信息。可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星网络设备200可以在SLC层基于第一用户帧得到出站链路指示信息。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星中心站23在SLC层和MDCP层基于一个或多个第一用户帧得到MDCP SDU。卫星中心站23向卫星短报文融合通信平台24发送MDCP SDU，作为应用层报文。卫星短报文融合通信平台24在APP层基于该应用层报文得到业务类型指示字段、文本信息和多播ID。卫星短报文融合通信平台24基于业务类型指示字段确定该应用层报文为入站多播短消息报文。可选的，入站多播短消息报文包括有位置信息，卫星短报文融合通信平台24在APP层基于该MDCP SDU还可以得到位置信息。可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星中心站23还向卫星短报文融合通信平台24发送出站链路指示信息。
在一些实施例中，如图11所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，卫星中心站23在SLC层和MDCP层基于一个或多个第一用户帧得到MDCP SDU。卫星中心站23向卫星短报文融合通信平台24发送MDCP SDU，作为应用层报文。卫星短报文融合通信平台24在APP层基于该应用层报文得到业务类型指示字段、文本信息和多播ID。卫星短报文融合通信平台24基于业务类型指示字段确定该应用层报文为入站多播短消息报文，向广播多播中心29发送业务类型指示字段、文本信息和多播ID。可选的，入站多播短消息报文包括有位置信息，卫星短报文融合通信平台24在APP层基于该MDCP SDU还可以得到位置信息，并将位置信息发送给广播多 播中心29。
需要说明的是，在图11所示的卫星通信系统的架构图中，广播多播中心29和位置中心28可以相互通信。可选的，广播多播中心29可以和短消息中心25之间可以相互通信，短消息中心25可以和位置中心28之间相互通信，图13中未示出。本申请实施例对具体的连接方式不作限定。
在一种可能的实现方式中，卫星短报文融合通信平台24基于业务类型指示字段确定该应用层报文为入站多播短消息报文，可以向广播多播中心29发送该MDCP SDU。广播多播中心29在APP层基于该应用层报文得到业务类型指示字段、文本信息和多播ID。可选的，入站多播短消息报文包括有位置信息，广播多播中心29在APP层可以基于该应用层报文得到位置信息。
可选的，第一用户帧中包括有出站链路指示字段，出站链路指示字段用于指示出站多播短消息的卫星信息和波束信息，卫星中心站23还向卫星短报文融合通信平台24发送出站链路指示信息，卫星短报文融合通信平台24向广播多播中心29发送出站链路指示信息。
S1205，卫星网络设备200基于入站短消息报文中的多播ID确定目标用户ID，并确定出站多播短消息的卫星信息和波束信息。
S1206，卫星网络设备200基于文本信息和多播ID生成出站多播短消息报文。
在一些实施例中，当多播ID指示的是订阅服务的多播群组，订阅服务可以由应用服务器提供，此时直接从S1206开始执行。其中，应用服务器可以将文本信息和多播ID发送给卫星网络设备200。
S1207，卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧。
S1208，卫星网络设备200向目标用户发送一个或多个第二用户帧。
在本申请实施例中，以目标用户是终端200为例进行说明。
S1209，终端200接收一个或多个第二用户帧。
S1210，终端200将一个或多个第二用户帧组装成出站多播短消息报文。
S1211，终端200解析出出站多播短消息报文中终端100发送给终端200的多播短消息的内容。
S1212，终端200显示终端100发送给终端200的多播短消息的内容。
在图12A中，S1205-S1212的过程和图10A中S1005-S1012的过程类似，为简洁描述在此不再赘述。
在一些实施例中，多播群组提前约定了出站多播短消息发送的时间点，卫星短报文融合通信平台24或广播多播中心29以及多播群组中的成员终端均保存了该出站多播短消息发送的时间点信息。本申请实施例中的S1006和S1206可以替换为S1006A。在本申请实施例中的S1009和S1209前，还包括S1009A。
S1006A：卫星网络设备200根据出站多播短消息发送的时间点信息，基于文本信息和多播ID生成出站多播短消息报文。
具体的，卫星网络设备200根据多播ID得到对应的多播群组提前约定的出站多消息发送的时间点信息。例如，多播ID对应的多播群组为终端100中第三群组，终端100中的第三群 组提前约定的出站多播短消息发送的时间点为整点时刻，如13:00等等。那么卫星网络设备200可以在时间点13:00基于文本信息和多播ID生成出站多播短消息报文。具体的出站多播短消息报文的生成过程可以参见上述实施例的描述，在此不再赘述。
S1009A，终端200根据出站多播短消息发送的时间点信息，进行对星操作，完成卫星信号的捕获以实现与卫星系统保持同步。
在一些场景中，在未完成对星操作之前，终端200无法接收到短报文卫星发送的出站多播短消息。因此，终端200在准备接收出站多播短消息之前要完成对星操作。具体的，终端200可以在距离出站多播短消息的发送时间点第一时长的时刻开始进行对星操作。例如，多播ID对应的多播群组为终端100中的第三群组，终端100中的第三群组提前约定的出站多消息发送的时间点为整点时刻，如13:00等等。在一种可能的实现方式中，终端200可以在12:55时开始进行对星操作。在另一种可能的实现方式中，终端200可以在12:55时收到通知信息，用户根据该通知信息进行对星操作。通知信息包括文本通知信息或语音通知信息，本申请实施例不做限定。
在一些实施例中，多播群组提前约定了多播短消息传输的时间点(包括发送时间点和接收时间点)，卫星短报文融合通信平台24或广播多播中心29以及多播群组中的成员终端均保存了该多播短消息传输的时间点信息。本申请实施例中S1001和S1201可以替换为S1001A。本申请实施例中的S1006和S1206可以替换为S1006B。在本申请实施例中的S1009和S1209前，还包括S1009B。
S1001A，终端100根据多播短消息传输的时间点信息，基于文本信息和多播ID生成入站多播短消息报文。
具体的，终端100根据多播ID得到对应的多播群组提前约定的多播短消息传输的时间点信息。例如，多播ID对应的多播群组为终端100中的第三群组，终端100中的第三群组提前约定的多播短消息传输的时间点为整点时刻，如13:00等等。那么，终端100可以在时间点13:00基于文本信息和多播ID生成入站多播短消息报文。具体的入站多播短消息报文的生成过程可以参见上述实施例的描述，在此不再赘述。在一种可能的实现方式中，终端100可以在接收用户的多播短消息发送操作后，将多播短消息缓存下来，在约定的多播短消息传输的时间点自动生成入站多播短消息报文。
在一些场景中，在未完成对星操作之前，终端100无法向卫星网络设备200发送入站多播短消息。因此，终端100在准备向卫星网络设备200发送入站多播短消息前要进行对星操作。具体的，终端100可以在距离多播短消息传输时间点的第一时长的时刻开始进行对星操作。例如，多播ID对应的多播群组为终端100中的第三群组，终端100中的第三群组提前约定的多播短消息传输时间点为整点时刻，如13:00等等。在一种可能的实现方式中，终端100可以在12:55时开始进行对星操作。在另一种可能的实现方式中，终端100可以在12:55时收到通知信息，用户根据该通知信息进行对星操作。通知信息包括文本通知信息或语音通知信息，本申请实施例不做限定。
S1006B，卫星网络设备200根据多播短消息传输的时间点信息，基于文本信息和多播ID生成出站多播短消息报文。
具体的，可以参考S1006A的描述，在此不再赘述。
S1009B，终端200根据多播短消息传输的时间点信息，进行对星操作，完成卫星信号的捕获以实现与卫星系统保持同步。
具体的，可以参考S1009A的描述，在此不再赘述。
在一些实施例中，终端200可以采用主动查询的方式得到出站多播短消息发送的时间点信息或多播短消息传输的时间点信息。具体的，终端200可以向卫星网络设备200发送多播周期查询请求消息，多播周期查询请求消息中携带有多播ID信息。卫星网络设备200基于多播ID生成多播周期查询结果报文，并将多播周期查询结果报文发送给终端200。
在一些实施例中，可以在第二用户帧中指示该第二用户帧为多播用户帧，并且在第二用户帧中指示该第二用户帧所对应的多播ID。本申请实施例中S1006和S1206可以替换为S1006C。本申请实施例中S1007和S1207可以替换为S1007A。本申请实施例中S1009和S1209可以替换为S1009C。本申请实施例中S1010和S1210可以替换为S1010A。本申请实施例中S1011和S1211可以替换为S1011A。具体的流程可以参考图10B和图12B。
S1006C，卫星网络设备200基于文本信息生成出站多播短消息报文。
具体的，卫星网络设备200可以将文本信息、发送方ID作为原始数据，并基于原始数据得到应用层报文，该应用层报文为出站多播短消息报文。
在一种可能的实现方式中，出站多播短消息报文的格式如上表5所示，其中各个字段的具体说明可以参考S1006的描述，在此不再赘述。
在一种可能的实现方式中，在本申请实施例中，出站多播短消息报文可以不包括消息类型指示字段。可选的，出站多播短消息报文可以包括消息类型指示字段，该消息类型指示字段可以取值为11，用于指示该应用层报文为出站多播短消息报文。本申请实施例对此不作限定。
在一种可能的实现方式中，出站多播短消息报文可以不包括多播ID字段。
S1007A，卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧。
具体的，卫星网络设备200可以将出站多播短消息报文、多播ID下发至MDCP层，并指示该出站多播短消息报文的类型为出站多播短消息类型。卫星网络设备200可以在MDCP层将出站多播短消息报文分段成一个或多个MDCP PDU。然后，卫星网络设备200再将一个或多个MDCP PDU至SLC层，作为SLC层的SLC SDU，并将多播ID和出站多播短消息报文的类型下发至SLC层。卫星网络设备200可以在SLC层将每一个SLC SDU分段成一个或多个第二用户帧。在SLC层，卫星网络设备200可以在每一个第二用户帧的帧类型指示字段中填入多播短消息帧类型，在多播ID字段中填入多播ID。卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。
在一种可能的实现方式中，第二用户帧的格式如表7所示。
表7
Figure PCTCN2022134866-appb-000010
如表7所示，第二用户帧可以包括帧类型字段、帧长字段、多播ID字段、帧总数字段、帧序号字段、用户信息字段等等。可选地，第二用户帧中还包括AM-Enable字段。
表7中示出的第二用户帧中各个字段的具体说明可以如下表8所示。
表8
Figure PCTCN2022134866-appb-000011
如表8所示，帧类型字段可用于指示第二用户帧的帧类型。其中，帧类型字段的数据长度可以为2bit。帧类型可以包括通用数据帧(或者可称为信息报文帧)、ACK帧、回执帧、多播短消息帧等等。其中，在本申请实施例中，第二用户帧的帧类型为多播短消息帧类型。可以理解的是，本申请实施例对该帧类型字段的长度不作限定。
如表8所示，帧长字段可用于指示第二用户帧中用户信息的数据长度。其中，帧长字段的数据长度可以是8bit或9bit。可以理解的是，本申请实施例对该帧长字段的长度不作限定。
如表8所示，多播ID字段用于指示该第二用户帧对应的多播群组的ID。其中，该多播ID字段的数据长度可以为10bit。可以理解的是，本申请实施例对多播ID字段的长度不作限定。
如表8所示，帧总数字段可用于表示该第二用户帧所在的SLC SDU中包括的用户帧的总数量。其中，该帧总数字段的长度可以是2bit。当帧总数字段的长度为2bit时，一个SLC SDU中最多可包括4个位置上报帧。可以理解的是，本申请实施例对帧总数字段的长度不作限定。
如表8所示，帧序号字段可用于指示该多播短消息帧在一个SLC SDU中的顺序。该帧序号字段的长度可以是2bit。
如表8所示，用户信息字段可用于指示第二用户帧的数据内容。可以理解的是，本申请实施例对用户信息字段的长度不作限定。
在另一种可能的实现方式中，第二用户帧的格式如表9所示。
表9
Figure PCTCN2022134866-appb-000012
如表9所示，第二用户帧可以包括帧类型字段、帧长字段、广播多播指示字段、多播ID字段、帧总数字段、帧序号字段、用户信息字段等等。
表9中示出的第二用户帧中各个字段的具体说明可以如上表8所示。需要说明的是，其中当帧类型字段取值为11时，指示第二用户帧为广播多播用户帧。第二用户帧还包括广播多播指示字段和广播多播ID字段。广播多播指示字段的长度可以是1bit。当该广播多播指示字段为数值C1(例如，0)时，可以用于指示该第二用户帧为多播短消息帧，此时广播多播ID字段用于指示多播ID信息；当该广播多播指示字段为数值C2(例如，1)时，可以用于指示该第二用户帧为广播短消息帧，此时广播多播ID字段用于指示广播ID信息。
S1009C，终端200接收一个或多个第二用户帧。
终端200可以接收到一个或多个第二用户帧。具体的接收过程可以参考图7所示实施例的描述，在此不再赘述。
在一种可能的实现方式中，终端200基于帧类型字段确定该第二用户帧为多播短消息帧，基于多播ID字段确定该第二用户帧所对应的多播群组的ID。
在一种可能的实现方式中，终端200基于帧类型字段确定该第二用户帧为广播多播短消息帧。进一步的，终端200基于广播多播指示字段确定该第二用户帧为多播短消息帧。
终端200可以基于多播ID字段确定该第二用户帧是否是发送给终端200的。如果确定该多播群组的ID属于终端200的多播群组，则可以确定该第二用户帧是发送给终端200的，终端200将该一个或多个第二用户帧上传至MDCP层继续解析；如果确定该多播群组的ID不属于终端200的多播群组，则可以确定该第二用户帧不是发送给终端200的，终端200可以丢弃该第二用户帧。
S1010A，终端200将一个或多个第二用户帧组装成出站多播短消息报文。
具体的，终端200可以将一个或多个第二用户帧在SLC层组装一个或多个SLC SDU。然后，终端200将一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU，并将多播ID发送给MDCP层。然后，终端200可以在MDCP层将一个或多个MDCP PDU拼成MDCP SDU。然后，终端200可以将MDCP SDU上传至APP层作为出站多播短消息报文，并将多播ID发送给APP层。这里可以参考图7中卫星通信系统的出站数据的解封装过程的描述，此处不再赘述。
S1011A，终端200解析出出站多播短消息报文中终端100发送给终端200的多播短消息的内容。
终端200可以在APP层基于多播短消息报文得到发送方ID字段以及多播短消息内容字段等等，并从MDCP层得到多播ID，从而确定该多播短消息对应的多播群组和发送方。
在本申请实施例中，卫星网络设备200可以在第二用户帧中指示该第二用户帧为多播用户帧，并在第二用户帧中指示多播ID。这样，卫星网络设备200只需发送一次出站多播短消息报文，多播群组中的所有成员终端都可以接收到该出站多播短消息报文。
需要说明的是，在本申请实施例中，终端100也可以接收到一个或多个第二用户帧，第二用户帧中不包括用户ID字段。终端100无法通过用户ID字段确定一个或多个第二用户帧是否是发送给终端100的。终端100可以基于一个或多个第二用户帧得到出站多播短消息报文，并基于出站多播短消息报文得到发送方ID字段。终端100基于发送方ID字段指示的用户ID和终端100的用户ID相同，终端100可以丢弃该出站多播短消息报文。
在一些实施例中，出站多播短消息报文所属的多播群组为订阅服务的多播群组，订阅服务可以由应用服务器提供，此时直接从S1006C开始执行。其中应用服务器可以将文本信息和多播ID发送给卫星网络设备200。需要说明的是，出站多播短消息报文中可以不包括发送方ID字段。
在一些实施例中，卫星短报文融合通信平台24或广播多播中心29将出站多播短消息报文发送给卫星中心站23后，可以立即删除出站多播短消息报文，无需等待多播群组中其他多播成员反馈接收出站多播短消息报文的确认消息。
在一些实施例中，卫星短报文融合通信平台24或广播多播中心29向卫星中心站23发送 的出站多播短消息报文中携带有回执指示字段。回执指示字段用于指示多播群组中其他多播成员在成功接收到出站多播短消息时，向卫星短报文融合通信平台24或广播多播中心29回复确认消息。当卫星短报文融合通信平台24或广播多播中心29接收到所有多播群组中其他的所有的多播成员发送的确认消息后，可以删除出站多播短消息报文，否则需要继续缓存该出站多播短消息报文。
在一些实施例中，多播群组中的多播成员可以向卫星短报文融合通信平台24或广播多播中心29查询或下载缓存的未接收到的多播短消息。
图14示出了本申请实施例中提供的一种卫星通信系统中查询多播短消息数量的方法的流程示意图。本申请实施例以终端200查询多播消息数量为例进行说明，本申请实施例提供的一种卫星通信系统中查询多播短消息数量的方法可以包括如下步骤：
S1401，终端200基于用户操作，生成多播短消息查询请求报文，多播短消息查询请求报文用户查询指定多播群组或者所有多播群组发送给终端200的多播短消息的数量。
终端200处于卫星网络下，即终端200处于无蜂窝网络和无线局域网络的场景下，终端200未驻留到蜂窝网络，终端200可以通过卫星网络查询指定多播群组或者所有多播群组发送给终端200的多播短消息的数量。
进一步地，终端200中可以存在控件1、控件2。其中，控件1可以用于查询指定多播群组发送给终端200的多播短消息的数量。控件2可以用于查询所有多播群组发送给终端200的多播短消息的数量。
在一种可能的实现方式中，多播短消息查询请求报文的格式可以如下表10所示。
表10
Figure PCTCN2022134866-appb-000013
如上表10所示，多播短消息查询请求报文可以包括回执指示字段、业务类型字段、加密指示字段、压缩指示字段、应用层鉴权码字段、多播ID字段、多播短消息ID字段。可以理解的是，本申请实施例中的多播短消息查询请求报文中包含具体字段以及字段的排列顺序不作限定。例如，当多播短消息查询请求报文默认不需要应用层回执时，该多播短消息查询请求报文中可以不包含回执指示字段。
表10中示出的多播短消息查询请求报文中各个字段的具体说明可以如下表11所示。
表11
Figure PCTCN2022134866-appb-000014
Figure PCTCN2022134866-appb-000015
如表11所示，回执指示字段可以用于指示该多播短消息查询请求报文的接收设备(例如卫星网络设备200)是否需要向终端200回复应用层回执。应用层回执可以用于指示接收设备是否成功接收该多播短消息查询请求报文。回执指示字段的长度可以是1bit。当该回执指示字段为数值D1(例如，0)时，可以用于指示该多播短消息查询请求报文的接收设备不需要向终端200回复应用层回执。当该回执指示字段为数值D2(例如，1)时，可以用于指示该多播短消息查询请求报文的接收设备需要向终端200回复应用层回执。可以理解的是，本申请实施例对回执指示字段的长度以及回执指示字段的具体取值不作限定。
业务类型字段可以用于指示该多播短消息查询请求报文的业务类型。在卫星短报文通信中，报文的业务类型可以包括通用报文、多播多消息查询和多播短消息下载等等。该业务类型字段的长度可以是4bit。可以理解的是，本申请实施例对该业务类型字段的长度不作限定。当业务类型的种类越来越多时，该业务类型的字段的长度可以越来越长。本申请实施例以业务类型字段的长度为4bit为例进行举例说明。当该业务类型字段为0000时，指示该应用层报文的业务类型为通用报文。当该业务类型字段为0111时，指示该应用层报文为多播短消息查询请求报文，且该多播短消息查询请求报文查询的是指定多播群组发送的多播短消息的数量。当该业务类型字段为1000时，指示该应用层报文为多播短消息查询请求报文，且该多播短消息查询请求报文查询的是所有多播群组发送的多播短消息的数量。当该业务类型字段为1001时，指示该应用层报文为多播短消息下载请求报文，且该多播短消息下载请求报文下载的是指定多播群组发送的多播短消息的数量。当该业务类型字段为1010时，指示该应用层报文为多播短消息下载请求报文，且该多播短消息下载请求报文下载的是所有多播群组发送的多播短消息的数量。该业务类型指示字段其他取值的含义可以参见表2所示，在此不再一一赘述。
加密指示字段可以用于指示该多播短消息查询请求报文是否加密。示例性地，加密指示字段的长度可以是2bit。当加密指示字段为数值D3(例如，00)时，指示该多播短消息查询请求报文未加密。可以理解的是，本申请实施例对该加密指示字段的长度和加密指示字段的具体取值不作限定。
压缩指示字段可以用于指示该多播短消息查询请求报文是否压缩。示例性地，压缩指示字段的长度可以是2bit。当压缩指示字段为数值D4(例如，00)时，指示该多播短消息查询请求报文未压缩。可以理解的是，本申请实施例对该压缩指示字段的长度和压缩指示字段的具体取值不作限定。
多播ID字段可以用于指示终端200要查询或者下载的发送给终端200多播短消息数量的指定多播群组的标识。该多播ID字段的长度可以是10bit。可以理解的是，本申请实施例对该多播ID字段的长度不作限定。需要说明的是，当业务类型字段为0111，该多播短消息查询请求报文查询的是指定多播群组发送的多播短消息的数量，因此，该多播短消息查询请求报文中包括该多播ID字段；当业务类型字段为1000时，该多播短消息查询请求报文查询的是所有多播群组发送的多播短消息的数量，因此该多播短消息下载请求报文中可以不包括该多播ID字段，也可以包括该多播ID字段，本申请实施例不做限定。
多播短消息ID字段可以用于指示终端200连续成功接收到的多播短消息中最后一个多播短消息的ID。示例性的，终端200点击用于查询多播短消息的控件之前，终端200成功接收到的多播短消息的ID为1、2、3、5，那么该多播短消息ID字段填写为3。在一些实施例中，当该多播短消息查询请求报文查询的是所有多播群组发送的多播短消息的数量时，多播短消息查询请求报文中可以不包括多播短消息ID字段。
S1402，终端200将多播短消息查询请求报文分段成一个或多个第一用户帧。
具体的，终端200可以通过层间接口将多播短消息查询请求报文下发至MDCP层。终端200可以在MDCP层将多播短消息查询请求报文分段成一个或多个MDCP PDU。然后，终端200再将一个或多个MDCP PDU下发至SLC层。终端200可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。在SLC层，终端200可以在每个第一用户帧的帧头中的用户ID字段中填入终端200的标识(例如，终端200的手机号码)。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
S1403，终端200向卫星网络设备200发送一个或多个第一用户帧。
终端200可以将一个或多个第一用户帧发送给卫星网络设备200。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
S1404，卫星网络设备200将一个或多个第一用户帧组装成多播短消息查询请求报文。
具体的，卫星网络设备200将终端200发送的一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU。然后，卫星网络设备200将该一个或多个第一用户帧上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，卫星网络设备200可以在MDCP层将一个或多个MDCP PDU组装成MDCP SDU。然后，卫星网络设备200可以将MDCP SDU上传至APP层作为多播短消息查询请求报文。这里可以参考图4中卫星通信系统的入站数据的解封装过程的描述，此处不再赘述。
S1405，卫星网络设备200基于多播短消息查询请求报文，生成多播短消息查询结果报文。
卫星网络设备200可以基于多播短消息查询请求报文，查询发送给终端200的多播短消 息的数量。然后，卫星网络设备200可以将查询的结果生成多播短消息查询结果报文，该多播短消息查询结果报文用于指示目标多播群组发送给终端200的多播短消息的数量。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星短报文融合通信平台24可以基于多播短消息查询请求报文，查询发送给终端200的多播短消息的数量。然后，卫星短报文融合通信平台24可以将查询的结果生成多播短消息查询结果报文，该多播短消息查询结果报文用于指示目标多播群组发送给终端200的多播短消息的数量。
在一些实施例中，如图11或图13所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，广播多播中心29可以基于多播短消息查询请求报文，查询发送给终端200的多播短消息的数量。然后，广播多播中心29可以将查询的结果生成多播短消息查询结果报文，该多播短消息查询结果报文用于指示目标多播群组发送给终端200的多播短消息的数量。
具体的，在一种可能的实现方式中，当多播短消息查询请求报文指示查询所有目标多播群组发送给终端200的多播短消息的数量时，卫星中心站23可以根据从第一用户帧中解析出的终端200的标识(例如，终端200的手机号码138xxxxxxxx)，并将终端200的标识发送给卫星短报文融合通信平台24或广播多播中心29。卫星短报文融合通信平台24或广播多播中心29可以根据终端200的标识和多播短消息查询请求报文中的多播短消息ID字段中解析出终端200上一次接收到的多播短消息的ID(例如“a1”)查询在多播短消息的ID为a1的多播短消息发送时间之后，所有目标多播群组发送给终端200的多播短消息的数量。
可选的，在另一种可能的实现方式中，当多播短消息查询请求报文指示查询指定目标多播群组发送给终端200的多播短消息的数量时，卫星中心站23可以根据从第一用户帧中解析出的终端200的标识(例如，终端200的手机号码138xxxxxxxx)，并将终端200的标识发送给卫星短报文融合通信平台24或广播多播中心29。卫星短报文融合通信平台24或广播多播中心29可以根据终端200的标识和多播短消息查询请求报文中多播ID字段解析出来的多播ID以及多播短消息查询请求报文中的多播短消息ID字段中解析出终端200上一次接收到的多播短消息的ID(例如“a1”)查询在多播短消息的ID为a1的多播短消息发送时间之后，指定目标多播群组发送给终端200的多播短消息的数量。
可以理解的是，卫星短报文融合通信平台24或广播多播中心29可以存储不同多播群组发送给终端200的多播短消息的数量。示例性的，卫星短报文融合通信平台24或广播多播中心29中存储的不同多播群组发送给终端200的多播短消息的数量的格式可以如下表12所示。
表12
Figure PCTCN2022134866-appb-000016
如表12所示，卫星短报文融合通信平台24或广播多播中心29可以存储多播ID、多播ID接收到的多播短消息的发送方ID以及多播短消息的发送时间。例如，多播ID为1的多播 群组为终端200的第一多播群组，第一多播群组中存储有两个多播短消息的发送方ID以及多播短消息的发送时间。卫星短报文融合通信平台24或广播多播中心29还存储了多播短消息ID。其中，多播短消息ID是按照终端200接收到的所有的多播短消息的发送时间的先后顺序进行编号的。
在一些场景下，如表12所示，终端200一共接收到4个多播短消息。若终端200上一次成功接收到的多播短消息为多播ID 1中发送方“13xxxxxxxx0”发送的多播短消息，该多播短消息ID为1，那么等终端200在查询多播ID 1发送的多播短消息数量时，卫星网络设备200回复的多播短消息数量为1。若终端200上一次成功接收到的多播短消息为多播ID 1中发送方“13xxxxxxxx0”发送的多播短消息，该多播短消息ID为1，那么等终端200在查询所有的多播群组发送的多播短消息数量时，卫星网络设备200回复的多播短消息数量为3。
可选的，多播短消息ID可以是按照终端200中不同的多播ID下接收到的多播短消息的发送时间的先后顺序进行编号的。示例性的，如表12所示，多播ID 1所指示的多播群组接收到两条多播短消息，其中，发送方“13xxxxxxxx0”发送的多播短消息的多播短消息ID为1，发送方“13xxxxxxxx1”发送的多播短消息的多播短消息ID为2；多播ID 2所指示的多播群组接收到两条多播短消息，其中，发送方“158xxxxxxx0”发送的多播短消息的多播短消息ID为1，发送方“158xxxxxxx1”发送的多播短消息的多播短消息ID为2。
可选的，卫星短报文融合通信平台24或广播多播中心29还可以存储多播短消息的具体内容。可以理解的是，上述表12仅为示例，本申请实施例对多播短消息存储的格式不作限定。
在一种实现的方式中，多播短消息查询结果报文的格式可以如下表13所示。
表13
Figure PCTCN2022134866-appb-000017
如上表13所示，多播短消息查询结果报文可以包括消息类型指示字段、加密指示字段、压缩指示字段、应用层鉴权码字段、多播群组数量、多播ID字段、多播短消息数量字段。可以理解的是，本申请实施例中的多播短消息查询结果报文中包含具体字段以及字段的排列顺序不作限定。例如，若卫星网络设备200未对多播短消息查询结果报文进行加密，多播短消息查询结果报文中也可以不包括加密指示字段。
表13中示出的多播短消息查询结果报文中各个字段的具体说明可以如下表14所示。表14示例性示出了表13中各个字段对应的长度以及具体说明。
表14
Figure PCTCN2022134866-appb-000018
Figure PCTCN2022134866-appb-000019
如表14所示，加密指示字段可以用于指示该多播短消息查询结果报文是否加密。示例性地，加密指示字段的长度可以是2bit。当加密指示字段为数值M1(例如，00)时，指示该多播短消息查询结果报文未加密。可以理解的是，本申请实施例对该加密指示字段的长度和加密指示字段的具体取值不作限定。
如表14所示，压缩指示字段可以用于指示该多播短消息查询结果报文是否压缩。示例性地，压缩指示字段的长度可以是2bit。当压缩指示字段为数值M2(例如，00)时，指示该多播短消息查询结果报文未压缩。可以理解的是，本申请实施例对该压缩指示字段的长度和压缩指示字段的具体取值不作限定。
如表14所示，应用层鉴权码字段可以用于应用层的鉴权。示例性地，该应用层鉴权码字段的长度可以是16bit。可以理解的是，本申请实施例对该应用层鉴权码字段的长度不作限定。
如表14所示，多播群组数量字段可以用于指示终端200中所有的多播群组的个数。可选的多播群组数量字段也可以用于指示多播短消息查询结果报文中多播ID字段和多播短消息数量字段循环的次数。示例性地，该多播群组数量字段的长度可以是4bit。可以理解的是，本申请实施例对多播群组数量字段的长度不作限定。
如表14所示，多播ID字段用于指示目标多播群组的ID。示例性地，该多播ID字段的长度可以是10bit。可以理解的是，本申请实施例对多播ID字段的长度不作限定。
如表14所示，多播短消息数量字段用于指示目标多播群组发送的多播短消息的数量。示例性地，该多播短消息数量字段可以为4bit。可以理解的是，本申请实施例对多播短消息数量字段的长度不作限定。
需要说明的是，当多播群组数量字段指示的多播群组数量为N个时，则多播ID字段和多播短消息数量字段在多播短消息查询结果报文中出现多次。
在一种可能的实现方式中，当终端200查询的是所有目标多播群组发送的多播短消息的数量时，卫星短报文融合通信平台24或广播多播中心29可以生成不同的目标多播群组的多播短消息查询结果报文。因此，多播短消息查询结果报文中可以不包括多播群组数量字段。
在一种可能的实现方式中，多播短消息查询结果报文中可以不包括多播群组数量字段和多播ID字段。此时，多播短消息数量字段用于指示终端200中所有多播群组的多播短消息数量的总数量。
S1406，卫星网络设备200将多播短消息查询结果报文分段成一个或多个第二用户帧。
卫星网络设备200将多播短消息查询结果报文分段成一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。
S1407，卫星网络设备200向终端200发送一个或多个第二用户帧。
卫星网络设备200向终端200发送一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。
S1408，终端200接收一个或多个第二用户帧。
终端200可以接收到一个或多个第二用户帧。具体的接收过程可以参考图7所示实施例的描述，在此不再赘述。
在一种可能的实现方式中，当终端200收齐一个或多个第二用户帧后，向卫星网络设备200回复已收齐一个或多个第二用户帧。
进一步地，终端200可以在SLC层解析出每个第二用户帧的帧头中的用户ID字段。若终端200从用户ID字段中解析出的用户ID和终端200的标识相同，则终端200将该一个或多个第二用户帧上传至MDCP层继续解析。若终端200从用户ID字段中解析出的用户ID和终端200的标识不同，则终端200可以确定该第二用户帧不是发送给终端200的，终端200可以丢弃该第二用户帧。
S1409，终端200将一个或多个第二用户帧组装成多播短消息查询结果报文。
具体地，终端200将可以将一个或多个第二用户帧在SLC层拼成一个或多个SLC SDU。然后，终端200将一个或多个第二用户帧上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，终端200可以在MDCP层将一个或多个MDCP PDU拼成MDCP SDU。然后，终端200可以将MDCP SDU上传至APP层作为多播短消息查询结果报文。这里可以参考图7中卫星通信系统的出站数据的解封装过程的描述，此处不再赘述。
S1410，终端200基于多播短消息查询结果报文解析出目标多播群组发送给终端200的多播短消息的数量。
终端200可以在APP层基于多播短消息查询结果报文得到多播群组数量字段、多播ID字段和多播短消息数量字段，从多播短消息数量字段中获知目标多播群组发送给终端200的多播短消息的数量。
S1411，终端200显示目标多播群组发送给终端200的多播短消息的数量。
终端200可以在显示目标多播群组发送给终端200的多播短消息的数量。终端200也可以以其他形式提示用户目标多播群组发送给终端200的短消息的数量，例如，终端200语音播报目标多播群组发送给终端200的信件的数量，本申请实施例对此不作限定。
这样，通过本申请实施例提供的一种卫星通信系统中查询多播短消息数量的方法，终端200在卫星网络下，未驻留蜂窝网络，也可以查询到目标群组发送给终端200的多播短消息的数量。
图15示出了本申请实施例中提供的一种卫星通信系统中下载多播短消息的方法的流程示意图。本申请实施例以终端200下载多播消息为例进行说明，本申请实施例提供的一种卫星通信系统中下载多播短消息可以包括如下步骤：
S1501，终端200基于用户操作，生成多播短消息下载请求报文，多播短消息下载请求报文用于下载一个或多个目标多播群组发送给终端200的多播短消息的内容。
终端200处于卫星网络下，即终端200处于无蜂窝网络和无线局域网络的场景下，终端200未驻留到蜂窝网络，终端200中的卫星通信模块开启。终端200可以通过该卫星通信模块与卫星网络设备200通信。终端200可以通过卫星网络获取一个或多个目标多播群组发送给终端200的多播短消息的内容。
进一步地，终端200中可以存在控件3、控件4。其中控件3可以用于请求下载指定目标 多播群组发送给终端200的多播短消息的内容。控件4可以用于请求下载所有多播群组发送给终端200的多播短消息的内容。
在一种可能的实现方式中，多播短消息下载请求报文的格式可以如下表15所示。
表15
Figure PCTCN2022134866-appb-000020
其中，表15中的字段的具体含义可以参考S1401中的描述，在此不再赘述。需要说明的是，在多播短消息下载请求报文中，当业务类型指示字段取值为1001时，指示该多播短消息下载请求报文请求下载指定多播群组发送给终端200的多播短消息；当业务类型指示字段取值为1010时，指示该多播短消息下载请求报文请求下载所有多播群组发送给终端200的多播短消息，此时多播短消息下载请求报文中可以不包括多播ID字段。
S1502，终端200将多播短消息下载请求报文分段成一个或多个第一用户帧。
具体的，终端200可以通过层间接口将多播短消息下载请求报文下发至MDCP层。终端200可以在MDCP层将多播短消息下载请求报文分段成一个或多个MDCP PDU。然后，终端200再将一个或多个MDCP PDU下发至SLC层。终端200可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。在SLC层，终端200可以在每个第一用户帧的帧头中的用户ID字段中填入终端200的标识(例如，终端200的手机号码)。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
S1503，终端200向卫星网络设备200发送一个或多个第一用户帧。
终端200可以将一个或多个第一用户帧发送给卫星网络设备200。这里具体可以参考图4中卫星通信系统10中入站数据封装过程的描述，此处不再赘述。
S1504，卫星网络设备200将一个或多个第一用户帧组装成多播短消息下载请求报文。
具体的，卫星网络设备200将终端200发送的一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU。然后，卫星网络设备200将该一个或多个第一用户帧上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，卫星网络设备200可以在MDCP层将一个或多个MDCP PDU拼成MDCP SDU。然后，卫星网络设备200可以将MDCP SDU上传至APP层作为多播短消息下载请求报文。这里可以参考图4中卫星通信系统的入站数据的解封装过程的描述，此处不再赘述。
S1505，卫星网络设备200基于多播短消息下载请求报文，生成出站多播短消息报文，该出站多播短消息报文用于指示目标多播群组发送给终端200的多播短消息的内容。
卫星网络设备200可以基于多播短消息下载请求报文，查询发送给终端200的多播短消息。然后，卫星网络设备200可以将查询到的多播短消息生成出站多播短消息报文，该出站多播短消息报文用于指示目标多播群组发送给终端200的多播短消息的内容。
在一些实施例中，如图1所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23和卫星短报文融合通信平台24，卫星短报文融合通信平台24可以基于多播短消息 下载请求报文，查询发送给终端200的多播短消息。然后，卫星短报文融合通信平台24可以将查询到的多播短消息生成出站多播短消息报文，该出站多播短消息报文用于指示目标多播群组发送给终端200的多播短消息的内容。
在一些实施例中，如图11或图13所示的卫星通信系统的架构图中，卫星网络设备200包括卫星中心站23、卫星短报文融合通信平台24和广播多播中心29，广播多播中心29可以基于多播短消息下载请求报文，查询发送给终端200的多播短消息。然后，广播多播中心29可以将查询到的多播短消息生成出站多播短消息报文，该出站多播短消息报文用于指示目标多播群组发送给终端200的多播短消息的内容。
具体的，在一种可能的实现方式中，当多播短消息下载请求报文指示下载所有目标多播群组发送给终端200的多播短消息的内容时，卫星中心站23可以根据从第一用户帧中解析出的终端200的标识(例如，终端200的手机号码138xxxxxxxx)，并将终端200的标识发送给卫星短报文融合通信平台24或广播多播中心29。卫星短报文融合通信平台24或广播多播中心29可以根据终端200的标识和多播短消息下载请求报文中的多播短消息ID字段中解析出终端200上一次接收到的多播短消息的ID(例如“a1”)查询在多播短消息的ID为a1的多播短消息发送时间之后，所有目标多播群组发送给终端200的多播短消息的内容。
可选的，在另一种可能的实现方式中，当多播短消息下载请求报文指示请求下载指定目标多播群组发送给终端200的多播短消息的内容时，卫星中心站23可以根据从第一用户帧中解析出的终端200的标识(例如，终端200的手机号码138xxxxxxxx)，并将终端200的标识发送给卫星短报文融合通信平台24或广播多播中心29。卫星短报文融合通信平台24或广播多播中心29可以根据终端200的标识和多播短消息下载请求报文中多播ID字段解析出来的多播ID以及多播短消息下载请求报文中的多播短消息ID字段中解析出终端200上一次接收到的多播短消息的ID(例如“a1”)查询在多播短消息的ID为a1的多播短消息发送时间之后，指定目标多播群组发送给终端200的多播短消息的内容。
可以理解的是，卫星短报文融合通信平台24或广播多播中心29可以存储不同多播群组发送给终端200的多播短消息的内容。多播短消息的内容的具体存储方式可以参考S1405的描述，在此不再赘述。
当卫星短报文融合通信平台24或广播多播中心29查询到多播短消息下载请求报文中目标多播群组发送给终端200的多播短消息的内容之后，卫星短报文融合通信平台24或广播多播中心29可以基于该多播短消息的内容，生成出站多播短消息报文。
在一种可能的实现方式中，出站多播短消息报文的格式如表5所示，出站多播短消息报文中的各个字段的具体说明可以参考S1006的描述，在此不再赘述。可以理解的是，在本申请实施例中，出站多播短消息报文是发送给特定的目标终端的出站多播短消息报文。例如，该出站多播短消息报文是发送给终端200的出站多播短消息报文。
S1506，卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧。
卫星网络设备200将出站多播短消息报文分段成一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。
S1507，卫星网络设备200向终端200发送一个或多个第二用户帧。
卫星网络设备200向终端200发送一个或多个第二用户帧的过程可以参考图6的具体的描述，在此不再赘述。
S1508，终端200接收一个或多个第二用户帧。
终端200可以接收到一个或多个第二用户帧。具体的接收过程可以参考图7所示实施例的描述，在此不再赘述。
在一种可能的实现方式中，当终端200收齐一个或多个第二用户帧后，向卫星网络设备200回复已收齐一个或多个第二用户帧。
进一步地，终端200可以在SLC层解析出每个第二用户帧的帧头中的用户ID字段。若终端200从用户ID字段中解析出的用户ID和终端200的标识相同，则终端200将该一个或多个第二用户帧上传至MDCP层继续解析。若终端200从用户ID字段中解析出的用户ID和终端200的标识不同，则终端200可以确定该第二用户帧不是发送给终端200的，终端200可以丢弃该第二用户帧。
S1509，终端200将一个或多个第二用户帧组装成出站多播短消息报文。
具体地，终端200将可以将一个或多个第二用户帧在SLC层拼成一个或多个SLC SDU。然后，终端200将一个或多个第二用户帧上传至MDCP层作为MDCP层的一个或多个MDCP PDU。然后，终端200可以在MDCP层将一个或多个MDCP PDU拼成MDCP SDU。然后，终端200可以将MDCP SDU上传至APP层作为出站多播短消息报文。这里可以参考图7中卫星通信系统的出站数据的解封装过程的描述，此处不再赘述。
S1510，终端200基于出站多播短消息报文解析出目标多播群组发送给终端200的多播短消息的内容。
终端200可以在APP层基于出站多播短消息报文得到多播ID字段、发送方ID字段以及多播短消息内容字段等等，从而确定该多播短消息对应的多播群组和发送方。
S1511，终端200显示目标多播群组发送给终端200的多播短消息的内容。
终端200可以在显示屏中显示目标多播群组发送给终端200的多播短消息的内容。终端200也可以以其他形式提示用户目标多播群组发送给终端200的短消息的内容，例如，终端200语音播报目标多播群组发送给终端200的信件的内容，本申请实施例对此不作限定。
在一些实施例中，出站多播短消息报文中的多播短消息下载完成指示字段指示后续还有多播短消息发送给终端200，终端200可以显示通知消息给用户，该通知消息用于提示用户是否继续下载后续的多播短消息。
可选的，终端200的用户在进行多播短消息的下载之前，可以先进行多播短消息的查询。即查询目标多播群组发送给终端200的多播短消息的数量。当卫星网络设备200向终端200发送目标多播群组发送给终端200的数量后，终端200可以选择想要下载的多播短消息进行多播短消息的下载。
这样，通过本申请实施例提供的一种卫星通信系统中下载多播短消息的方法，终端200在卫星网络下，未驻留蜂窝网络，也可以下载到目标群组发送给终端200的多播短消息的数量。
上述内容详细阐述了本申请提供的方法，为了便于更好地实施本申请实施例的上述方案，本申请实施例还提供了相应的装置或设备。
本申请实施例可以根据上述方法示例对终端100、终端200和卫星网络设备200进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
下面将结合图16至图19详细描述本申请实施例的通信装置。
在采用集成的单元的情况下，参见图16，图16是本申请实施例提供的通信装置1600的结构示意图。该通信装置1600可以为上述实施例中的终端100或终端200。可选的，通信装置1600可以为一种芯片/芯片系统，例如，卫星通信芯片。如图16所示，该通信装置1600可以包括收发单元1610和处理单元1620。
一种设计中，收发单元1610，可用于向卫星网络设备200发送入站多播短消息报文；
可选地，收发单元1610，还可以用于接收出站多播短消息报文。
处理单元1620，可用于将入站多播短消息报文下发至MDCP层，可以在MDCP层将入站多播短消息报文分段成一个或多个MDCP PDU。
可选地，处理单元1620，还可用于将入站多播短消息报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。
可选地，处理单元1620，还可用于将一个或多个第一用户帧组装成一个或多个SLC SDU，可以将一个或多个SLC SDU发送给MDCP层，可以在MDCP层将一个或多个MDCP PDU组装成MDCP SDU，可以将MDCP SDU发送给APP层作为出站多播短消息报文。
一种设计中，收发单元1610，可用于向卫星网络设备200发送多播短消息查询请求报文；
可选地，收发单元1610，还可以用于接收多播短消息查询结果报文。
可选地，处理单元1620，还可用于将多播短消息查询请求报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。
可选地，处理单元1620，还可用于将一个或多个第一用户帧组装成一个或多个SLC SDU，可以将一个或多个SLC SDU发送给MDCP层，可以在MDCP层将一个或多个MDCP PDU组装成MDCP SDU，可以将MDCP SDU发送给APP层作为多播短消息查询结果报文。
一种设计中，收发单元1610，可用于向卫星网络设备200发送多播短消息下载请求报文；
可选地，收发单元1610，还可以用于接收出站多播短消息报文。
可选地，处理单元1620，还可用于将多播短消息下载请求报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成一个或多个第一用户帧。
可选地，处理单元1620，还可用于将一个或多个第一用户帧组装成一个或多个SLC SDU，可以将一个或多个SLC SDU发送给MDCP层，可以在MDCP层将一个或多个MDCP PDU组装成MDCP SDU，可以将MDCP SDU发送给APP层作为出站多播短消息报文。
可选的，收发单元1610，还可用于执行上述图10A、图10B、图12A或图12B所示方法实施例中终端100或终端200执行的有关发送和接收的功能步骤，还可以用于上述图14或图 15所示方法实施例中终端200执行的有关发送和接收的功能步骤。
可选的，处理单元1620，还可用于执行上述图10A、图10B、图12A或图12B所示方法实施例中终端100或终端200执行的有关协议解析与封装以及运算确定的功能步骤，还可用于执行上述图14或图15所示方法实施例中终端200执行的有关协议解析与封装以及运算确定的功能步骤。
应理解，该种设计中的通信装置1600可对应执行前述实施例中终端100或终端200执行的方法步骤，为了简洁，在此不再赘述。
在采用集成的单元的情况下，参见图17，图17是本申请实施例提供的通信装置1700的结构示意图。该通信装置1700可以为上述实施例中的卫星网络设备200。可选的，通信装置1700可以为卫星网络设备200中的具体网元，例如，卫星地面收发站22、卫星中心站23和卫星短报文融合通信平台24中的一个网元或多个网元的组合。如图17所示，该通信装置1700可以包括收发单元1710和处理单元1720。
一种设计中，收发单元1710，可用于接收入站多播短消息报文。
可选地，收发单元1710，还可用于发送出站多播短消息报文。
处理单元1720，还可以用于将一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU，将一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU；在MDCP层将一个或多个MDCP PDU组装成MDCP SDU；然后，可以用于将MDCP SDU上传至APP层作为入站多播短消息报文。
可选地，处理单元1720，还可用于将出站多播短消息报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成一个或多个第二用户帧。
一种设计中，收发单元1710，可用于接收多播短消息查询请求报文。
可选地，收发单元1710，还可用于发送多播短消息结果报文。
处理单元1720，还可以用于将一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU，将一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU；在MDCP层将一个或多个MDCP PDU组装成MDCP SDU；然后，可以用于将MDCP SDU上传至APP层作为多播短消息查询请求报文。
可选地，处理单元1720，还可用于将多播短消息结果报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成一个或多个第二用户帧。
一种设计中，收发单元1710，可用于接收多播短消息下载请求报文。
可选地，收发单元1710，还可用于发送出站多播短消息报文。
处理单元1720，还可以用于将一个或多个第一用户帧在SLC层组装成一个或多个SLC SDU，将一个或多个SLC SDU上传至MDCP层作为MDCP层的一个或多个MDCP PDU；在MDCP层将一个或多个MDCP PDU组装成MDCP SDU；然后，可以用于将MDCP SDU上传至APP层作为多播短消息下载请求报文。
可选地，处理单元1720，还可用于将出站多播短消息报文分段为一个或多个MDCP PDU，可以将一个或多个MDCP PDU下发至SLC层，可以在SLC层将每一个MDCP PDU分段成 一个或多个第二用户帧。
可选的，收发单元1710，还可用于执行上述图10A、图10B、图12A、图12B、图14或图15所示方法实施例中卫星网络设备200执行的有关发送和接收的功能步骤。
可选的，处理单元1720，还可用于执行上述图10A、图10B、图12A、图12B、图14或图15所示方法实施例中卫星网络设备200执行的有关协议解析与封装以及运算确定的功能步骤。
应理解，该种设计中的通信装置1700可对应执行前述实施例中卫星网络设备200执行的方法步骤，为了简洁，在此不再赘述。
以上介绍了本申请实施例的终端100、终端200和卫星网络设备200，应理解，但凡具备上述图16所述的终端100或终端200的功能的任何形态的产品，但凡具备上述图17所述的卫星网络设备200的功能的任何形态的产品，都落入本申请实施例的保护范围。
作为一种可能的产品形态，本申请实施例所述的终端100或终端200，可以由一般性的总线体系结构来实现。
参见图18，图18是本申请实施例提供的通信装置1800的结构示意图。该通信装置1800可以是终端100或终端200，或其中的装置。如图18所示，该通信装置1800包括处理器1801和与所述处理器内部连接通信的收发器1802。其中，处理器1801是通用处理器或者专用处理器等。例如可以是卫星通信的基带处理器或中央处理器。卫星通信的基带处理器可以用于对卫星通信协议以及卫星通信数据进行处理，中央处理器可以用于对通信装置(如，基带芯片，终端、终端芯片等)进行控制，执行计算机程序，处理计算机程序的数据。收发器1802可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1802可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。可选的，通信装置1800还可以包括天线1803和/或射频单元(图未示意)。所述天线1803和/或射频单元可以位于所述通信装置1800内部，也可以与所述通信装置1800分离，即所述天线1803和/或射频单元可以是拉远或分布式部署的。
可选的，通信装置1800中可以包括一个或多个存储器1804，其上可以存有指令，该指令可为计算机程序，所述计算机程序可在通信装置1800上被运行，使得通信装置1800执行上述方法实施例中描述的方法。可选的，所述存储器1804中还可以存储有数据。通信装置1800和存储器1804可以单独设置，也可以集成在一起。
其中，处理器1801、收发器1802、以及存储器1804可以通过通信总线连接。
一种设计中，通信装置1800可以用于执行前述实施例中终端100或终端200的功能：处理器1801可以用于执行上述图10A、图10B、图12A、图12B、图14以及图15所示实施例中终端100或终端200执行的有关协议解析与封装以及运算确定的功能步骤和/或用于本文所描述的技术的其它过程；收发器1502可以用于执行上述图10A、图10B、图12A、图12B、图14以及图15所示实施例中终端100或终端200执行的有关协议解析与封装以及运算确定的功能步骤和/或用于本文所描述的技术的其它过程。
在上述任一种设计中，处理器1801中可以包括用于实现接收和发送功能的收发器。例如 该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在上述任一种设计中，处理器1801可以存有指令，该指令可为计算机程序，计算机程序在处理器1801上运行，可使得通信装置1800执行上述方法实施例中终端100执行的方法步骤。计算机程序可能固化在处理器1801中，该种情况下，处理器1801可能由硬件实现。
在一种实现方式中，通信装置1800可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图18的限制。通信装置1800可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置1800可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端、智能终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
作为一种可能的产品形态，本申请实施例所述的卫星网络设备200中的任一网元(例如、卫星地面收发站22、卫星中心站23和卫星短报文融合通信平台24，可以由一般性的总线体系结构来实现。
参见图19，图19是本申请实施例提供的通信装置1900的结构示意图。该通信装置1900可以是卫星网络设备200，或其中的装置。如图19所示，该通信装置1900包括处理器1901和与所述处理器内部连接通信的收发器1902。其中，处理器1901是通用处理器或者专用处理器等。例如可以是卫星通信的基带处理器或中央处理器。卫星通信的基带处理器可以用于对卫星通信协议以及卫星通信数据进行处理，中央处理器可以用于对通信装置(如，基带芯片等)进行控制，执行计算机程序，处理计算机程序的数据。收发器1902可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1902可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等， 用于实现发送功能。可选的，通信装置1900还可以包括天线1903和/或射频单元(图未示意)。所述天线1903和/或射频单元可以位于所述通信装置1900内部，也可以与所述通信装置1900分离，即所述天线1903和/或射频单元可以是拉远或分布式部署的。
可选的，通信装置1900中可以包括一个或多个存储器1904，其上可以存有指令，该指令可为计算机程序，所述计算机程序可在通信装置1900上被运行，使得通信装置1900执行上述方法实施例中描述的方法。可选的，所述存储器1904中还可以存储有数据。通信装置1900和存储器1904可以单独设置，也可以集成在一起。
其中，处理器1901、收发器1902、以及存储器1904可以通过通信总线连接。
一种设计中，通信装置1900可以用于执行前述实施例中卫星网络设备200的功能：处理器1901可以用于执行上述图10A、图10B、图12A、图12B、图14以及图15所示实施例中卫星网络设备200执行的有关协议解析与封装以及运算确定的功能步骤和/或用于本文所描述的技术的其它过程；收发器1902可以用于执行上述图10A、图10B、图12A、图12B、图14以及图15所示实施例中卫星网络设备200执行的有关协议解析与封装以及运算确定的功能步骤和/或用于本文所描述的技术的其它过程。
在上述任一种设计中，处理器1901中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在上述任一种设计中，处理器1901可以存有指令，该指令可为计算机程序，计算机程序在处理器1901上运行，可使得通信装置1900执行上述方法实施例中卫星网络设备200执行的方法步骤。计算机程序可能固化在处理器1901中，该种情况下，处理器1901可能由硬件实现。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序代码，当上述处理器执行该计算机程序代码时，使得通信装置执行前述任一实施例中的方法。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行前述任一实施例中的方法。
本申请实施例还提供一种通信装置，该装置可以以芯片的产品形态存在，该装置的结构中包括处理器和接口电路，该处理器用于通过接收电路与其它装置通信，使得该装置执行前述任一实施例中的方法。
本申请实施例还提供一种卫星通信系统，包括终端100和/或终端200和卫星网络设备200，该终端100和/或终端200和卫星网络设备200可以执行前述任一实施例中的方法。
本申请全文介绍了卫星通信系统中短报文的通信功能，可以理解的是，北斗卫星通信系统支持短报文的通信功能，本申请中介绍的方法，适用于该北斗卫星通信系统。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实 施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。
上述实施例中所用，根据上下文，术语“当…时”可以被解释为意思是“如果…”或“在…后”或“响应于确定…”或“响应于检测到…”。类似地，根据上下文，短语“在确定…时”或“如果检测到(所陈述的条件或事件)”可以被解释为意思是“如果确定…”或“响应于确定…”或“在检测到(所陈述的条件或事件)时”或“响应于检测到(所陈述的条件或事件)”。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如DVD)、或者半导体介质(例如固态硬盘)等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (37)

  1. 一种卫星通信系统中的多播短消息传输的方法，所述方法应用于第一终端，所述方法包括：
    所述第一终端向卫星网络设备发送入站多播短消息报文，所述入站多播短消息报文中包括第一字段和第二字段，所述第一字段用于指示所述入站多播短消息报文所对应的多播群组的多播ID为第一多播ID，所述第二字段用于指示所述入站多播短消息报文中的信息内容为第一信息内容。
  2. 根据权利要求1所述的方法，其特征在于，所述入站多播短消息报文中还包括第三字段，所述第三字段用于指示所述入站多播短消息报文的业务类型为通用报文业务类型。
  3. 根据权利要求2所述的方法，其特征在于，所述第一终端向卫星网络设备发送入站多播短消息报文，包括：
    所述第一终端向所述卫星网络设备发送一个或多个第一用户帧，所述一个或多个第一用户帧中包括第四字段，所述第四字段用于指示所述一个或多个第一用户帧的帧类型为多播短消息帧类型。
  4. 根据权利要求1所述的方法，其特征在于，所述入站多播短消息报文中还包括第三字段，所述第三字段用于指示所述入站多播短消息报文的业务类型为入站多播短消息类型。
  5. 根据权利要求4所述的方法，其特征在于，所述第一终端向卫星网络设备发送入站多播短消息报文，包括：
    所述第一终端向所述卫星网络设备发送一个或多个第一用户帧，所述一个或多个第一用户帧中包括第四字段，所述第四字段用于指示所述一个或多个第一用户帧的帧类型为通用数据帧类型。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一终端接收所述卫星网络设备发送的第一出站多播短消息报文，所述第一出站多播短消息报文中包括第五字段和第六字段，所述第五字段用于指示所述第一出站多播短消息报文的发送方ID为第二终端的用户ID，所述第六字段用于指示所述第一出站多播短消息报文中的信息内容为第二信息内容；
    其中，所述第一终端和所述第二终端属于第一多播群组，所述第一多播群组的多播ID为所述第一多播ID。
  7. 根据权利要求6所述的方法，其特征在于，所述第一终端接收所述卫星网络设备发送的第一出站多播短消息报文，包括：
    所述第一终端接收一个或多个第二用户帧，所述一个或多个第二用户帧中包括第七字段和第八字段，所述第七字段用于指示所述一个或多个第二用户帧的帧类型为多播用户帧类型，所述第八字段用于指示所述一个或多个第二用户帧所对应的多播群组的多播ID为所述第一 多播ID；
    所述第一终端基于所述第七字段确定所述一个或多个第二用户帧为多播短消息帧，并解析得到所述第一多播ID；
    所述第一终端基于所述一个或多个第二用户帧得到所述第一出站多播短消息报文，并解析得到所述第二终端的用户ID和所述第二信息内容；
    所述第一终端基于所述第一多播ID和所述第二终端的用户ID显示所述第二信息内容。
  8. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一终端向所述卫星网络设备发送多播短消息查询请求报文，所述多播短消息查询请求报文中包括业务类型字段，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型；
    所述第一终端接收并显示多播短消息查询结果报文，所述多播短消息查询结果报文为所述卫星网络设备基于所述多播短消息查询请求报文生成的。
  9. 根据权利要求8所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询指定多播群组发送给所述第一终端的多播短消息的数量；
    所述多播短消息查询请求报文中还包括多播ID字段和多播短消息ID字段，所述多播ID字段用于指示所述指定多播群组的多播ID，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述多播短消息查询结果报文中包括多播短消息数量字段，所述多播短消息数量字段用于指示所述指定多播群组发送给所述第一终端的多播短消息的数量。
  10. 根据权利要求8所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询所有多播群组发送给所述第一终端的多播短消息的数量；
    所述多播短消息查询请求报文中还包括多播短消息ID字段，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的ID；
    所述多播短消息查询结果报文中包括多播短消息数量字段，所述多播短消息数量字段用于指示所述所有多播群组发送给所述第一终端的多播短消息的数量。
  11. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一终端向所述卫星网络设备发送多播短消息下载请求报文，所述多播短消息下载请求报文中包括业务类型字段，所述业务类型字段用于指示所述多播短消息下载请求报文的业务类型为多播短消息下载类型；
    所述第一终端接收并显示第二出站多播短消息报文，所述第二出站多播短消息报文为所述卫星网络设备基于所述多播短消息下载请求报文生成的。
  12. 根据权利要求11所述的方法，其特征在于，所述业务类型字段用于指示所述多播短 消息下载请求报文的业务类型为多播短消息下载类型，且下载指定多播群组发送给所述第一终端的多播短消息；
    所述多播短消息下载请求报文中还包括多播ID字段和多播短消息ID字段，所述多播ID字段用于指示所述指定多播群组的多播ID，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述第二出站多播短消息报文中包括下载完成指示字段，所述下载完成指示字段用于指示所述指定多播群组后续是否还有多播短消息发送给所述第一终端。
  13. 根据权利要求11所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载所有多播群组发送给所述第一终端的多播短消息；
    所述多播短消息下载请求报文中还包括多播短消息ID字段，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；所述第二出站多播短消息报文中包括下载完成指示字段，所述下载完成指示字段用于指示所述所有多播群组后续是否还有多播短消息发送给所述第一终端。
  14. 一种卫星通信系统中的多播短消息传输的方法，其特征在于，包括：
    第一终端向卫星网络设备发送入站多播短消息报文，所述入站多播短消息报文中包括第一字段和第二字段，所述第一字段用于指示所述入站多播短消息报文所对应的多播群组的多播ID为第一多播ID，所述第二字段用于指示所述入站多播短消息报文中的信息内容为第一信息内容；
    所述卫星网络设备接收所述入站多播短消息报文，解析得到所述第一多播ID和所述第一信息内容；
    所述卫星网络设备基于所述第一信息内容发送第一出站多播短消息报文；
    第二终端接收所述第一出站多播短消息报文，其中，所述第一终端和所述第二终端属于第一多播群组，所述第一多播群组的多播ID为所述第一多播ID。
  15. 根据权利要求14所述的方法，其特征在于，所述入站多播短消息报文中还包括第三字段，所述第三字段用于指示所述多播短消息报文的业务类型为通用报文业务类型。
  16. 根据权利要求15所述的方法，其特征在于，所述第一终端向卫星网络设备发送入站多播短消息报文，包括：
    所述第一终端向所述卫星网络设备发送一个或多个第一用户帧，所述一个或多个第一用户帧中包括第四字段，所述第四字段用于指示所述一个或多个第一用户帧的帧类型为多播短消息帧类型。
  17. 根据权利要求15或16所述的方法，其特征在于，所述卫星网络设备接收所述入站多播短消息报文，包括：
    所述卫星网络设备接收所述一个或多个第一用户帧，解析得到所述第四字段；
    所述卫星网络设备基于所述第四字段确定所述一个或多个第一用户帧为多播短消息帧；
    所述卫星网络设备基于所述一个或多个第一用户帧得到所述入站多播短消息报文，并解析得到所述第一多播ID和所述第一信息内容。
  18. 根据权利要求14所述的方法，其特征在于，所述入站多播短消息报文中包括第三字段，所述第三字段用于指示所述多播短消息报文的业务类型为入站多播短消息类型。
  19. 根据权利要求18所述的方法，其特征在于，所述第一终端向卫星网络设备发送入站多播短消息报文包括：
    所述第一终端向所述卫星网络设备发送所述一个或多个第一用户帧，所述一个或多个第一用户帧中包括第四字段，所述第四字段用于指示所述一个或多个第一用户帧的帧类型为通用数据帧类型。
  20. 根据权利要求18或19所述的方法，其特征在于，所述卫星网络设备接收所述入站多播短消息报文，包括：
    所述卫星网络设备接收所述一个或多个第一用户帧；
    所述卫星网络设备基于所述一个或多个第一用户帧得到所述入站多播短消息报文，解析得到所述第三字段；
    所述卫星网络设备基于所述第三字段确定所述入站多播短消息报文的业务类型为入站多播短消息类型，并解析得到所述第一多播ID和所述第一信息内容。
  21. 根据权利要求15-20中任一项所述的方法，其特征在于，所述第一出站多播短消息报文中包括发送方ID字段和第五字段，所述发送方ID字段用于指示所述第一出站多播短消息报文的发送方ID为所述第一终端的用户ID，所述第五字段用于指示所述第一出站多播短消息报文的信息内容所述第一信息内容。
  22. 根据权利要求21所述的方法，其特征在于，所述卫星网络设备基于所述第一信息内容发送第一出站多播短消息报文，包括：
    所述卫星网络设备发送一个或多个第二用户帧，所述一个或多个第二用户帧中包括第六字段和第七字段，所述第六字段用于指示所述一个或多个第二用户帧的帧类型为多播短消息帧类型，所述第七字段用于指示所述一个或多个第二用户帧所对应的多播群组的多播ID为所述第一多播ID。
  23. 根据权利要求22所述的方法，其特征在于，所述第二终端接收所述第一出站多播短消息报文，包括：
    所述第二终端接收所述一个或多个第二用户帧，解析得到所述第六字段；
    所述第二终端基于所述第六字段确定所述一个或多个第二用户帧为多播短消息帧，并解析得到所述第一多播ID；
    所述第二终端基于所述一个或多个第二用户帧得到所述第一出站多播短消息报文，并解 析得到所述第一终端的用户ID和所述第一信息内容；
    所述第二终端基于所述第一多播ID和所述第一终端的用户ID显示所述第一信息内容。
  24. 根据权利要求14所述的方法，其特征在于，在所述卫星网络设备基于所述第一信息内容发送所述第一出站多播短消息报文之前，所述方法还包括：
    所述卫星网络设备确定所述第一出站多播短消息报文的卫星信息和波束信息。
  25. 根据权利要求24所述的方法，其特征在于，所述入站多播短消息报文中包括位置信息字段，所述位置信息字段用于指示所述第一终端的位置信息；
    所述卫星网络设备确定所述第一出站多播短消息报文的卫星信息和波束信息，包括：
    所述卫星网络设备基于所述入站多播短消息报文，解析得到所述位置信息字段；
    所述卫星网路设备基于所述位置信息字段，得到所述第一出站多播短消息报文的卫星信息和波束信息。
  26. 根据权利要求16所述的方法，其特征在于，所述一个或多个第一用户帧中包括出站链路指示字段，所述出站链路指示字段用于指示所述第一出站多播短消息报文的卫星信息和波束信息；
    在所述卫星网络设备基于所述第一信息内容发送所述第一出站多播短消息报文之前，所述方法还包括：
    所述卫星网络设备基于所述一个或多播第一用户帧，解析得到所述出站链路指示字段；
    所述卫星网络设备基于所述出站链路指示字段，得到所述第一出站多播短消息报文的卫星信息和波束信息。
  27. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第一终端向所述卫星网络设备发送多播短消息查询请求报文，所述多播短消息查询请求报文中包括业务类型字段，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型；
    所述卫星网络设备接收所述多播短消息查询请求报文；
    所述卫星网络设备基于所述多播短消息查询请求报文，生成多播短消息查询结果报文；
    所述卫星网络设备向所述第一终端发送所述多播短消息查询结果报文；
    所述第一终端接收并显示所述多播短消息查询结果报文。
  28. 根据权利要求27所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询指定多播群组发送给所述第一终端的多播短消息的数量；
    所述多播短消息查询请求报文中还包括多播ID字段和多播短消息ID字段，所述多播ID字段用于指示所述指定多播群组的多播ID，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述多播短消息查询结果报文中包括多播短消息数量字段，所述多播短消息数量字段用 于指示所述指定多播群组发送给所述第一终端的多播短消息的数量。
  29. 根据权利要求27所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息查询请求报文的业务类型为多播短消息查询类型，且查询所有多播群组发送给所述第一终端的多播短消息的数量；
    所述多播短消息查询请求报文中还包括多播短消息ID字段，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述多播短消息查询结果报文中包括多播短消息数量字段，所述多播短消息数量字段用于指示所述所有多播群组发送给所述第一终端的多播短消息的数量。
  30. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第一终端向所述卫星网络设备发送多播短消息下载请求报文，所述多播短消息下载请求报文中包括业务类型字段，所述业务类型字段用于指示所述多播短消息下载请求报文的业务类型为多播短消息下载类型；
    所述卫星网络设备接收所述多播短消息下载请求报文；
    所述卫星网络设备基于所述多播短消息下载请求报文，生成第二出站多播短消息报文；
    所述卫星网络设备向所述第一终端发送所述第二出站多播短消息报文；
    所述第一终端接收并显示所述第二出站多播短消息报文。
  31. 根据权利要求30所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载指定多播群组发送给所述第一终端的多播短消息；
    所述多播短消息下载请求报文中还包括多播ID字段和多播短消息ID字段，所述多播ID字段用于指示所述指定多播群组的多播ID，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述第二出站多播短消息报文中包括下载完成指示字段，所述下载完成指示字段用于指示所述指定多播群组后续是否还有多播短消息发送给所述第一终端。
  32. 根据权利要求30所述的方法，其特征在于，所述业务类型字段用于指示所述多播短消息下载请求报文的业务类型为多播短消息下载类型，且下载所有多播群组发送给所述第一终端的多播短消息；
    所述多播短消息下载请求报文中还包括多播短消息ID字段，所述多播短消息ID字段用于指示所述第一终端连续成功接收到的多播短消息中最后一个多播短消息的多播短消息ID；
    所述第二出站多播短消息报文中包括下载完成指示字段，所述下载完成指示字段用于指示所述所有多播群组后续是否还有多播短消息发送给所述第一终端。
  33. 根据权利要求14所述的方法，其特征在于，所述第二终端为一个或多个终端。
  34. 一种通信装置，其特征在于，包括一个或多个处理器、一个或多个存储器和收发器； 其中，所述收发器、所述一个或多个存储器与所述一个或多个处理器耦合，所述一个或多个存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当一个或多个处理器在执行所述计算机指令时，使得所述通信装置执行如权利要求1-13中任一项所述的方法。
  35. 根据权利要求34所述的通信装置，其特征在于，所述通信装置为终端。
  36. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-13中任一项所述的方法。
  37. 一种芯片或芯片系统，应用于终端，其特征在于，包括处理电路和接口电路，所述接口电路用于接收代码指令并传输至所述处理电路，所述处理电路用于运行所述代码指令以执行如权利要求1-13中任一项所述的方法。
PCT/CN2022/134866 2021-12-06 2022-11-29 一种卫星多播短消息的方法及相关装置 WO2023103830A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202111511376.5 2021-12-06
CN202111511376 2021-12-06
CN202210144012.6A CN116321015A (zh) 2021-12-06 2022-02-17 一种卫星多播短消息的方法及相关装置
CN202210144012.6 2022-02-17

Publications (1)

Publication Number Publication Date
WO2023103830A1 true WO2023103830A1 (zh) 2023-06-15

Family

ID=86729610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/134866 WO2023103830A1 (zh) 2021-12-06 2022-11-29 一种卫星多播短消息的方法及相关装置

Country Status (1)

Country Link
WO (1) WO2023103830A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117278949A (zh) * 2023-11-17 2023-12-22 中国人民解放军国防科技大学 一种针对低功耗用户终端的北斗短报文通信方法和系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080146219A1 (en) * 2006-12-14 2008-06-19 General Motors Corporation Satellite radio file broadcast method
US20110092158A1 (en) * 2009-10-08 2011-04-21 Gerald Plamondon Portable satellite data communication device and related method
CN104333850A (zh) * 2014-09-25 2015-02-04 北京华力创通科技股份有限公司 基于北斗通讯的短报文读取方法
CN104661184A (zh) * 2013-11-20 2015-05-27 电信科学技术研究院 一种进行卫星通信的方法和设备
CN111083865A (zh) * 2019-11-21 2020-04-28 北京天海达科技有限公司 一种基于北斗短报文卫星通信的路灯控制系统及方法
CN111505680A (zh) * 2020-04-21 2020-08-07 中国人民解放军陆军勤务学院 一种后勤保障车辆监控和指挥系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080146219A1 (en) * 2006-12-14 2008-06-19 General Motors Corporation Satellite radio file broadcast method
US20110092158A1 (en) * 2009-10-08 2011-04-21 Gerald Plamondon Portable satellite data communication device and related method
CN104661184A (zh) * 2013-11-20 2015-05-27 电信科学技术研究院 一种进行卫星通信的方法和设备
CN104333850A (zh) * 2014-09-25 2015-02-04 北京华力创通科技股份有限公司 基于北斗通讯的短报文读取方法
CN111083865A (zh) * 2019-11-21 2020-04-28 北京天海达科技有限公司 一种基于北斗短报文卫星通信的路灯控制系统及方法
CN111505680A (zh) * 2020-04-21 2020-08-07 中国人民解放军陆军勤务学院 一种后勤保障车辆监控和指挥系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117278949A (zh) * 2023-11-17 2023-12-22 中国人民解放军国防科技大学 一种针对低功耗用户终端的北斗短报文通信方法和系统
CN117278949B (zh) * 2023-11-17 2024-01-30 中国人民解放军国防科技大学 一种针对低功耗用户终端的北斗短报文通信方法和系统

Similar Documents

Publication Publication Date Title
US7580005B1 (en) Display change between mobile terminal display and external device display
US9591524B2 (en) Method and apparatus for transmitting data in network system, and data transmission system
WO2017096637A1 (zh) Mimo卫星服务终端
CN102201846B (zh) 基于soft AP技术的无线数据传输系统及其方法
CN102821057A (zh) 文件传送方法、装置和系统
CN104205667A (zh) 用于触发多个无线设备的技术和配置
US10574397B2 (en) Information processing apparatus, communication system, information processing method and program
CN112073922B (zh) 窄带与宽带通信的中转设备、服务器、融合系统及方法
WO2023103830A1 (zh) 一种卫星多播短消息的方法及相关装置
US20230353234A1 (en) Transmission latency compensation method, apparatus, communication device and storage medium
WO2023030152A1 (zh) 一种切换网络的方法及相关装置
WO2023011362A1 (zh) 一种北斗通信系统中出站传输控制方法、系统及相关装置
CN107231604B (zh) 一种数字通信方法及系统
WO2019201127A1 (zh) 数据传输方法及装置
CN102237925B (zh) 基于北斗卫星移动通信系统实现数据广播的方法及系统
WO2023011605A1 (zh) 北斗通信系统中的信件下载查询方法、系统及相关装置
Chen et al. Cellular based machine to machine communication with un-peer2peer protocol stack
US20220338288A1 (en) Communication method and apparatus
CN116321015A (zh) 一种卫星多播短消息的方法及相关装置
CN112214425B (zh) 数据发送方法、装置、计算机设备以及存储介质
CN115842799A (zh) 北斗通信系统中的信箱概况查询方法、系统及相关装置
CN115842800B (zh) 北斗通信系统中的信件下载查询方法、系统及相关装置
CN115250453A (zh) 一种数据传输方法及设备
WO2023088206A1 (zh) 一种传输方法、系统及相关装置
WO2023011594A1 (zh) 北斗通信系统中的信箱概况查询方法、系统及相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22903252

Country of ref document: EP

Kind code of ref document: A1