A transmission method, system and related apparatus

Abstract

This application discloses a transmission method, system, and related apparatus. This application relates to the field of satellite communications. A first satellite network device generates a first data packet and transmits the first data packet to at least one first terminal device via a second satellite network device within a specified time period. The specified time period is negotiated between the first satellite network device and the at least one first terminal device.

Description

Technical Field

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

[0002] Satellite communication services can be used for positioning and communication in areas where mobile communication is unavailable, poorly covered, or where communication systems are damaged, such as oceans, deserts, grasslands, and uninhabited areas. Currently, only terminals connected to cellular networks can receive broadcast or multicast messages. However, terminals connected to satellite networks cannot receive broadcast or multicast messages. Therefore, how terminals connected to satellite networks can receive broadcast or multicast messages is a pressing issue that needs to be addressed in satellite communication systems. Summary of the Invention

[0003] This application provides a transmission method, system, and related apparatus. Relating to the field of satellite communication, a first satellite network device generates a first data packet and transmits it to at least one first terminal device via a second satellite network device within a specified time period. The specified time period is negotiated between the first satellite network device and the at least one first terminal device. Alternatively, the first satellite network device determines the specified time period based on broadcast time information sent by the first network device. In this way, the terminal can not only receive broadcast data under the satellite network, but also receive the first data packet at the same time it was sent, since the terminal stores the transmission time of the first data packet. This reduces the power consumption of the terminal when receiving satellite data and improves the success rate of receiving the first data packet.

[0004] In a first aspect, this application provides a transmission method, comprising: a first satellite network device generating a first data packet; the first satellite network device sending the first data packet to a second satellite network device within a specified time period; wherein the first data packet is used by the second satellite network device to generate a second data packet and send it to at least one first terminal device; the specified time period is negotiated between the first satellite network device and at least one first terminal device, or the first satellite network device determines the specified time period based on broadcast time information sent by the first network device.

[0005] It should be noted that the first satellite network device can be a converged communication platform 24 or a broadcast multicast service center 17. At least one first terminal device may include terminal 100. At least one first terminal device may also include terminal 300.

[0006] In one possible implementation, the method further includes: a first satellite network device sending information to a second satellite network device instructing the second satellite network device to broadcast the first data packet to at least one first terminal device. Alternatively, the first satellite network device sending information to the second satellite network device instructing the second satellite network device to multicast the first data packet to at least one first terminal device. In some embodiments, the information instructing the second satellite network device to broadcast the first data packet to at least one first terminal device and the information instructing the second satellite network device to multicast the first data packet to at least one first terminal device are broadcast instruction information. In some embodiments, the second satellite network device may be a ground center station 19.

[0007] In one possible implementation, the method further includes: a first satellite network device sending one or more of the following information to a second satellite network device: an identifier of a first data packet, broadcast time information of the first data packet, and broadcast area information of the first data packet. The identifier is used to indicate the service type of the first data packet. The identifier of the first data packet can be a broadcast source identifier of the broadcast data in the first data packet.

[0008] In one possible implementation, the first data packet includes information indicating the time for the first satellite network device to send the next M first data packets, where M is a positive integer.

[0009] In one possible implementation, before the first satellite network device sends the first data packet to the second satellite network device, the method further includes: the first satellite network device sending a first message to a first terminal device through the second satellite network device, the first message including time information indicating the transmission time of the first data packet. Alternatively, the first satellite network device sends time information or the first message to a third satellite network device. Wherein, when the first satellite network device is a broadcast multicast service center 17, the third satellite network device is a converged communication platform 18. In some embodiments, the first satellite network device generates the first message based on the time information; in other embodiments, the first satellite network device sends the time information to the second satellite network device, and the second satellite network device generates the first message based on the time information. The first message may be a broadcast time response.

[0010] In one possible implementation, before the first satellite network device sends the first message to the first terminal device via the second satellite network device, the method further includes: the first satellite network device receiving a second message sent by the first terminal device via the second satellite network device. The second message instructs the first satellite network device to send the first message to the first terminal device. In some embodiments, the second message is a broadcast time request.

[0011] In one possible implementation, before the first satellite network device sends the first time information or the first message to the third satellite network device, the method further includes: the first satellite network device receiving a time request or a second message sent by the third satellite network device. The time request instructs the first satellite network device to send time information to the third satellite network device, and the second message instructs the first satellite network device to send the first message to the first terminal device. Here, the first satellite network device is a broadcast multicast service center 17, and the third satellite network device is a converged communication platform 18. The first satellite network device receiving the time request sent by the third satellite network device can be understood as the third satellite network device obtaining time information from the first satellite network device. In some embodiments, the second message is a broadcast time request.

[0012] In one possible implementation, after the first satellite network device sends the first data packet to the second satellite network device, the method further includes: the first satellite network device receiving information sent by the second satellite network device indicating the reception status of the first terminal device for the first data packet. In this way, the first satellite network device can determine the result of the first terminal device parsing the first data packet. Furthermore, the first satellite network device can also perform further operations based on the result of parsing the first data packet, such as retransmitting the first data packet.

[0013] In one possible implementation, before the first satellite network device sends the first data packet to the second satellite network device, the method further includes: the first satellite network device receiving the content of the first data packet sent by the first network device. The first satellite network device receives one or more of the following information sent by the first network device: an identifier of the first data packet, broadcast time information, and broadcast area information. The content of the first data packet includes broadcast data, which may include at least one of multicast data and broadcast data. In some embodiments, the first network device is a server 15 or an emergency rescue platform 26.

[0014] Secondly, this application provides a transmission method, comprising: a second satellite network device receiving a first data packet sent by a first satellite network device; the second satellite network device generating a second data packet based on the first data packet; and the second satellite network device sending the second data packet to at least one first terminal device. Thus, the second satellite network device can broadcast (multicast) the second data packet to at least one first terminal device. The first terminal device can receive broadcast messages (multicast messages) under the satellite network. In some embodiments, the second satellite network device is a ground central station 19. In other embodiments, the second satellite network device may include a ground transceiver station and a central station.

[0015] In one possible implementation, before the second satellite network device generates the second data packet based on the first data packet, the method further includes: the second satellite network device receiving information instructing the second satellite network device to generate a broadcast-type second data packet based on the first data packet. Alternatively, the second satellite network device receiving information instructing the second satellite network device to generate a multicast-type second data packet based on the first data packet. In some embodiments, the information instructing the second satellite network device to broadcast the first data packet to at least one first terminal device and the information instructing the second satellite network device to multicast the first data packet to at least one first terminal device are broadcast instruction information.

[0016] In one possible implementation, the second satellite network device generates a second data packet based on the first data packet, specifically including: the second satellite network device generating the second data packet based on information for instructing the second satellite network device to generate a broadcast-type second data packet based on the first data packet or information for instructing the second satellite network device to generate a multicast-type second data packet based on the first data packet.

[0017] In one possible implementation, the second satellite network device sends the second data packet to at least one first terminal device, specifically including: the second satellite network device sending the second data packet to at least one first terminal device via a first beam. Alternatively, the second satellite network device sends the second data packet to at least one first terminal device, the second data packet including a first version number, the first version number indicating whether the second data packet is a broadcast data packet or a multicast data packet. Alternatively, the second satellite network device sends the second data packet to at least one first terminal device, the second data packet including first information and a second version number, the first information indicating whether the second data packet is a broadcast data packet and / or a multicast data packet, and the second version number indicating the protocol version used by the second satellite network device to generate the second data packet. Here, the first beam is a beam used to transmit broadcast data, and its subcode is different from the waveform used to transmit unicast data, so that the terminal can determine that the received data includes broadcast data through the first beam. It should also be noted that the first version number and the second version number are different. In some embodiments, the first information is a user ID field. The value of the user ID field can be used to identify the broadcast source or terminal. In some embodiments, the first information is a frame type indication field, the value of which can be used to indicate that the second data packet is a broadcast data packet. In some embodiments, the first information is a frame type indication field, the value of which can be used to indicate that the second data packet is a broadcast data packet or a multicast data packet. In some embodiments, the first information is a broadcast type indication field, which can be used to indicate that the second data packet is a broadcast data packet or a multicast data packet. Thus, when the terminal receives the second data packet, it can determine that the second data packet is a broadcast data packet based on the first beam, the first version number, or the first information.

[0018] In one possible implementation, when the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet further includes information indicating the broadcast source of the second data packet. Alternatively, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet further includes information indicating the multicast source of the second data packet. In some embodiments, the first information may be a frame type indication field or a broadcast type indication field indicating that the second data packet is either a broadcast data packet or a multicast data packet. The information indicating the broadcast source of the second data packet is a broadcast source identifier, for example, the broadcast source identifier may be the broadcast ID of the broadcast source or the name, code, etc., of the broadcast source. The information indicating the multicast source of the second data packet is a multicast source identifier, for example, the multicast source identifier may be the broadcast ID of the multicast source or the name, code, etc., of the multicast source. In this way, the terminal can determine whether to receive the second data packet based on the broadcast source identifier.

[0019] In one possible implementation, the method further includes: a second satellite network device receiving one or more of the following information: an identifier of a first data packet, broadcast time information of the first data packet, and broadcast area information of the first data packet. The identifier indicates the service type of the first data packet. The second satellite network device determines a first beam, or a first version number, or first information based on the information. Alternatively, the second satellite network device receives information instructing it to generate a second data packet of broadcast type based on the first data packet, or information instructing it to generate a second data packet of multicast type based on the first data packet. The second satellite network device determines the first beam, or the first version number, or the first information based on the information instructing it to generate a second data packet of broadcast type based on the first data packet or the information instructing it to generate a second data packet of multicast type based on the first data packet.

[0020] When the second satellite network device receives one or more of the following information: the identifier of the first data packet, the broadcast time information of the first data packet, and the broadcast area information of the first data packet, the second satellite network device can determine that the first data packet contains broadcast data based on the identifier, since the identifier of the first data packet can be used to indicate the broadcast source. The second satellite network device can determine the value of the user ID field or the broadcast ID field based on the identifier of the first data packet. Since the broadcast area information of the first data packet can be used to indicate the area where the second satellite network device broadcasts or multicasts the first data packet, the second satellite network device can also determine that the first data packet is a broadcast data packet based on the broadcast area information, as unicast data packets do not require broadcast area division. Since the broadcast time information of the first data packet can be used to indicate the time period during which the second satellite network device broadcasts or multicasts the first data packet, the second satellite network device only sends unicast data packets to the first terminal device when it receives a download message request from the first terminal device. Therefore, since unicast data packets do not require a specified sending time, the second satellite network device can also determine that the first data packet is a broadcast data packet based on the broadcast time information.

[0021] The first information determined based on the information used to instruct the second satellite network device to generate a second data packet of broadcast type based on the first data packet or the information used to instruct the second satellite network device to generate a second data packet of multicast type based on the first data packet can be a frame type indication field or a broadcast type indication field.

[0022] In one possible implementation, before the second satellite network device receives the first data packet sent by the first satellite network device, the method further includes: the second satellite network device receiving a first message sent by the first satellite network device, or the second satellite network device receiving a first message sent by a third satellite network device. The first message includes time information indicating the transmission time of the first data packet. The second satellite network device then sends the first message to the first terminal device.

[0023] In one possible implementation, before the second satellite network device receives the first message sent by the first satellite network device, or before the second satellite network device receives the first message sent by the third satellite network device, the method further includes: the second satellite network device receiving the second message sent by the first terminal device.

[0024] The second satellite network device sends the second message to the first satellite network device, or the second satellite network device sends the second message to the third satellite network device, and the second message is used to obtain the first message.

[0025] In one possible implementation, after the second satellite network device sends the second data packet to at least one first terminal device, the method further includes: the second satellite network device receiving information sent by the first terminal device indicating the reception status of the first terminal device for the first data packet. The second satellite network device then sends the information indicating the reception status of the first terminal device for the first data packet to the first satellite network device.

[0026] Thirdly, this application provides a transmission method, comprising: a first terminal device receiving a second data packet sent by a second satellite network device within a specified time period. The first terminal device determines whether the second data packet is a broadcast data packet or a multicast data packet. Based on the second data packet, the first terminal device obtains a first data packet, wherein the first data packet is a data packet sent by the first satellite network device to the second satellite network device, and the specified time period is negotiated by the first satellite network device and at least one first terminal device, or the first terminal determines the specified time period based on a received first message.

[0027] In one possible implementation, the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet, specifically including: the second data packet includes a first version number, and the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on the first version number.

[0028] Alternatively, the second data packet may include the first information, and the first terminal device may determine the second data packet as a broadcast data packet or a multicast data packet based on the first information.

[0029] Alternatively, the first terminal device can determine whether the second data packet is a broadcast or multicast data packet based on the first beam received from the second data packet. In this way, when the terminal determines the type of the received second data packet, it can determine the structure of the second data packet. For example, the terminal can determine the broadcast ID field in the second data packet based on its type, and then determine whether to receive the second data packet based on the broadcast ID field. When any of the broadcast source identifiers stored in the terminal matches the broadcast source identifier indicated by the broadcast ID field, the terminal receives the second data packet. This also avoids the terminal 100 receiving spam messages (e.g., advertising messages).

[0030] In one possible implementation, when the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet also includes information indicating the broadcast source of the second data packet. Alternatively, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet also includes information indicating the multicast source of the second data packet.

[0031] In one possible implementation, the first data packet includes information indicating the reception time of the next M first data packets sent by the first satellite network device, where M is a positive integer. This avoids the terminal being unable to determine the transmission time of subsequent data packets if a second data packet is missed.

[0032] In one possible implementation, before the first terminal device receives the second data packet sent by the second satellite network device, the method further includes: the first terminal device sending a second message to the second satellite network device, the second message being used to instruct the first satellite network device to send the transmission time information of the first data packet to the first terminal device.

[0033] In one possible implementation, after the first terminal device sends a second message to the second satellite network device, the method further includes: the first terminal device receiving a first message, the first message including transmission time information for indicating the time when the first satellite network device sends the first data packet.

[0034] In one possible implementation, the first terminal device sends a second message to the second satellite network device, specifically including: the first terminal device receiving input from a user querying the transmission time of the next first data packet. In response to the input, the first terminal device sends the second message to the second satellite network device. In this way, the user can actively query the transmission time of the first data packet.

[0035] In one possible implementation, after the first terminal device receives the first message, the method further includes: the first terminal device displaying the transmission time of the first data packet. This allows the user to determine the transmission time of the next first data packet based on the time displayed by the first terminal device. The user can then perform a satellite pairing operation on the first terminal device at that transmission time, improving the success rate of receiving the first data packet.

[0036] In one possible implementation, before the first terminal device receives the first data packet sent by the second satellite network device, the method further includes: the first terminal device receiving input from a user querying the transmission time of the next first data packet. In response to the input, the first terminal device displays a transmission time indicating to the first satellite network device to transmit the first data packet, the transmission time being negotiated between the first satellite network device and at least one first terminal device.

[0037] Fourthly, this application provides a transmission method, comprising: a third satellite network device receiving a first message sent by a first satellite network device; or, the third satellite network device receiving first time information sent by the first satellite network device and generating a first message based on the first time information.

[0038] The third satellite network device sends a first message to the first terminal device. The first message includes first time information, which is used to indicate the time when the first data packet was sent.

[0039] In some embodiments, the third satellite network device may be a converged communication platform 18, which is used to process unicast data.

[0040] In one possible implementation, before the third satellite network device receives the first message sent by the first satellite network device, the method further includes: the third satellite network device receiving a second message sent by the second satellite network device.

[0041] The third satellite network device sends a second message to the first satellite network device, and the second message is used to instruct the first satellite network device to send a first message to the third satellite network device.

[0042] In one possible implementation, before the third satellite network device sends the first message to the first terminal device, the method further includes: the third satellite network device receiving a second message sent by the second satellite network device, the second message being used to instruct the third satellite network device to generate the first message and send the first message to the second satellite network device.

[0043] In one possible implementation, before the third satellite network device receives the first time information sent by the first satellite network device, the method further includes: the third satellite network device sending a first time information request to the first satellite network device, the first time information request being used to instruct the first satellite network device to send the first time information to the third satellite network device.

[0044] Fifthly, this application provides a transmission method, comprising: a first device generating a second data packet; the first device sending the second data packet to at least one first terminal device within a specified time period, the specified time period being negotiated by a first satellite network device and at least one first terminal device, or the first satellite network device determining the specified time period based on broadcast time information sent by the first network device. Optionally, the first device may determine the specified time period based on the amount of broadcast data sent by the first network device. In some embodiments, the first device may include a ground central station 19 and a converged communication platform 24. In other embodiments, the first device may include a ground central station 19, a converged communication platform 18, and a broadcast multicast service center 17.

[0045] In one possible implementation, the method further includes: the first device receiving the content of a second data packet sent by a first network device. The first device receives one or more of the following information sent by the first network device: an identifier of the second data packet, broadcast time information, and broadcast area information.

[0046] In one possible implementation, the first device sends the first data packet to at least one first terminal device within a specified time period, specifically including:

[0047] The first device sends the second data packet to at least one first terminal device via the first beam.

[0048] Alternatively, the first device may send a second data packet to at least one first terminal device, the second data packet including a first version number, the first version number being used to indicate whether the second data packet is a broadcast data packet or a multicast data packet.

[0049] Alternatively, the first device may send a second data packet to at least one first terminal device. The second data packet includes first information and a second version number. The first information indicates that the second data packet is a broadcast data packet and / or a multicast data packet, and the second version number indicates the protocol version used by the second satellite network device to generate the second data packet.

[0050] In one possible implementation, when the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet also includes information indicating the broadcast source of the second data packet. Alternatively, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet also includes information indicating the multicast source of the second data packet.

[0051] In one possible implementation, the method further includes: the first device determining a first beam, or determining a first version number, or determining first information based on the identifier of the second data packet.

[0052] In one possible implementation, before the first device sends the second data packet to at least one first terminal device within a specified time period, the method further includes:

[0053] The first device sends a first message to the first terminal device, the first message including time information indicating the time of transmission of the second data packet.

[0054] In one possible implementation, before the first device sends the first message to the first terminal device, the method further includes: the first device receiving a second message sent by the first terminal device, the second message being used to instruct the first device to send the first message to the first terminal device.

[0055] In one possible implementation, after the first device sends the second data packet to at least one first terminal device, the method further includes: the first device receiving information sent by the first terminal device indicating the reception status of the second data packet by the first terminal device.

[0056] In one possible implementation, the first device generates the second data packet, specifically including: the first device generating the first data packet at the application layer (AP); the first device forwarding the first data packet from the AP layer to the message data aggregation (MDCP) layer and / or the satellite link control (SLC) layer; and the first device processing the first data packet into the second data packet at the MDCP layer and / or the SLC layer.

[0057] In one possible implementation, the second data packet includes a time for instructing the first device to send the next second data packet.

[0058] Sixthly, this application provides a transmission method, comprising: a first terminal device receiving a second data packet from a first device within a specified time period; the first terminal device determining that the second data packet is a broadcast data packet or a multicast data packet; and the first terminal device obtaining a first data packet based on the second data packet, wherein the specified time period is negotiated by a first satellite network device and at least one first terminal device, or the first terminal determines the specified time period based on a received first message.

[0059] In one possible implementation, the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet, specifically including: the second data packet includes a first version number, and the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on the first version number. Alternatively, the second data packet includes first information, and the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on the first information. Alternatively, the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on a first beam that receives the second data packet.

[0060] In one possible implementation, when the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet also includes information indicating the broadcast source of the second data packet. Alternatively, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet also includes information indicating the multicast source of the second data packet.

[0061] In one possible implementation, the first data packet includes information indicating the reception time for the first terminal device to receive the next first data packet sent by the first satellite network device.

[0062] In one possible implementation, before the first terminal device receives the second data packet from the first device within a specified time period, the method further includes:

[0063] The first terminal device sends a second message to the first device, the second message being used to instruct the first satellite device to send the transmission time information of the first data packet to the first terminal device.

[0064] In one possible implementation, after the first terminal device sends a second message to the first device, the method further includes: the first terminal device receiving a first message sent by the first device, the first message including time information indicating the transmission time of the first data packet.

[0065] In one possible implementation, the first terminal device sends a second message to the first device, specifically including: the first terminal device receiving input from a user querying the sending time of the next second data packet. In response to the input, the first terminal device sends the second message to the first device.

[0066] In one possible implementation, after the first terminal device receives the first message, the method further includes: the first terminal device displaying the sending time of the first data packet.

[0067] In one possible implementation, before the first terminal device receives the second data packet sent by the first device, the method further includes: the first terminal device receiving input from a user querying the transmission time of the next second data packet. In response to the input, the first terminal device displays an indication of the time for receiving the second data packet, the transmission time being negotiated between the first device and at least one other first terminal device.

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

[0069] The communication device can be a satellite network device, or any network element or a combination of multiple network elements within a satellite network device. For example, the satellite network device can be a BeiDou satellite network device.

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

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

[0072] Ninthly, this application provides a computer storage medium including computer instructions that, when executed on a computer, cause the computer to perform the method in any of the possible implementations of the first, second, fourth, or fifth aspects described above.

[0073] In a tenth aspect, this application provides a computer storage medium including computer instructions that, when executed on a computer, cause the computer to perform the method in any of the possible implementations of the third or sixth aspect described above.

[0074] In one aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the first, second, fourth, or fifth aspects described above.

[0075] In a twelfth aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the third or sixth aspect described above.

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

[0077] Figure 1 A schematic diagram of a satellite communication system provided in an embodiment of this application;

[0078] Figure 2A A schematic diagram of another satellite communication system provided in the embodiments of this application;

[0079] Figure 2B A schematic diagram of another satellite communication system provided in the embodiments of this application;

[0080] Figure 3 A schematic diagram of another satellite communication system provided in the embodiments of this application;

[0081] Figure 4A This application provides a schematic diagram of an outbound protocol architecture.

[0082] Figure 4B A schematic diagram of the protocol encapsulation architecture for outbound data of a satellite communication system provided in this application embodiment;

[0083] Figure 4C A schematic diagram of the protocol parsing architecture for outbound data of a satellite communication system provided in this application embodiment;

[0084] Figure 5A A schematic flowchart illustrating a transmission method provided in an embodiment of this application;

[0085] Figure 5B A schematic diagram illustrating a data packet broadcasting format provided in an embodiment of this application;

[0086] Figure 6A A flowchart illustrating another transmission method provided in an embodiment of this application;

[0087] Figure 6B A schematic diagram illustrating another format for broadcasting data packets provided in an embodiment of this application;

[0088] Figure 7A A flowchart illustrating another transmission method provided in an embodiment of this application;

[0089] Figure 7B A schematic diagram illustrating another format for broadcasting data packets provided in an embodiment of this application;

[0090] Figure 8A A flowchart illustrating another transmission method provided in an embodiment of this application;

[0091] Figure 8B A schematic diagram illustrating another format for broadcasting data packets provided in an embodiment of this application;

[0092] Figure 9 A schematic diagram of another satellite communication system provided in the embodiments of this application;

[0093] Figure 10 This is a schematic diagram of another outbound protocol architecture provided in an embodiment of this application;

[0094] Figure 11 A schematic diagram illustrating a default broadcast cycle provided in an embodiment of this application;

[0095] Figures 12A-12E A set of interface schematic diagrams provided for embodiments of this application;

[0096] Figure 13 A schematic diagram illustrating an additional broadcast time provided in an embodiment of this application;

[0097] Figure 14 A schematic diagram illustrating another format for broadcasting data packets provided in an embodiment of this application;

[0098] Figures 15A-15B Another set of interface schematic diagrams provided for embodiments of this application;

[0099] Figure 16 A schematic diagram illustrating a modification cycle provided in an embodiment of this application;

[0100] Figure 17 A flowchart illustrating a method for querying the sending time of a first data packet, provided in an embodiment of this application;

[0101] Figure 18 A schematic diagram illustrating another process for querying the sending time of the first data packet, provided in an embodiment of this application;

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

[0103] Figure 20 This application provides a schematic diagram of a terminal sending receipt information.

[0104] Figure 21This is a schematic diagram illustrating another process for sending receipt information by a terminal, provided in an embodiment of this application.

[0105] Figure 22 This is a schematic diagram of a hardware structure provided for an embodiment of this application. Detailed Implementation

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

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

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

[0109] like Figure 1 As shown, the satellite communication system 10 may include, but is not limited to, terminal 100, satellite 21, satellite network equipment 200, server 15, etc.

[0110] In this system, terminal 100 of the satellite network can send data packets to server 15 via satellite network device 200. Specifically, terminal 100 can first send data packets to satellite 21, which then relays the packets directly to the ground-based satellite network device 200. Satellite network device 200 can then parse the data packets forwarded by satellite 21 according to the satellite communication protocol and forward the parsed data to server 15. Optionally, satellite network device 200 can forward the parsed content from the data packets to server 15 via a traditional cellular communication network (referred to as a cellular network) or via the Internet.

[0111] Server 15 can also send data packets to terminal 100 of the satellite network. Server 15 can send data to satellite network device 200, which can encapsulate the data sent by server 15 into data packets according to the satellite communication protocol. Satellite network device 200 can then send the data packets to satellite 21. Satellite 21 can then send the data packets to terminal 100 of the satellite network.

[0112] During unicast, satellite network device 200 stores data sent from server 15 to terminal 100. When satellite network device 200 receives a download request from terminal 100, it encapsulates the data sent from server 15 to terminal 100 into a data packet based on the download request and sends the data packet to terminal 100 via satellite 21. The download request can be used to instruct satellite network device 200 to send the data sent from server 15 to terminal 100.

[0113] During broadcasting or multicasting, satellite network device 200 can encapsulate the data received from server 15 into a data packet and broadcast the data packet to multiple terminals under the satellite network via satellite 21, including terminal 100.

[0114] Optionally, the satellite communication system 10 may also include an emergency rescue platform 26 and an emergency rescue center 27. The satellite network device 200 can transmit emergency rescue frames sent by the terminal 100 to the emergency rescue center 27 via the emergency rescue platform 26. The emergency rescue center 27 can also broadcast data (e.g., rescue information) to multiple devices within the satellite network via the emergency rescue platform 26, the satellite network device 200, and the satellite 21.

[0115] The satellite network equipment 200 may include, but is not limited to, a ground center station 19 and a converged communication platform 24. The ground center station 19 may include one or more devices with transmitting and receiving functions, or it may include one or more devices with both transmitting and receiving functions; this is not limited here. The ground center station 19 can be used by the satellite network equipment 200 for data processing at the physical layer (PHY), satellite link control layer (SLC), and message data convergence layer (MDCP). The converged communication platform 24 can be used for data processing at the application layer (AP). The process of a terminal 100 in the satellite network sending data to the satellite network equipment 200 can be called an inbound process, and the process of the satellite network equipment 200 sending data to a terminal 100 in the satellite network can be called an outbound process.

[0116] Optionally, the satellite network equipment 200 may include, but is not limited to, a ground transceiver station 22 (not shown in the figure), a central station 23 (not shown in the figure), and a converged communication platform 24. The ground transceiver station 22 may include one or more devices with transmitting capabilities and one or more devices with receiving capabilities, or may include one or more devices with both transmitting and receiving capabilities; this is not limited here. The ground transceiver station 22 can be used by the satellite network equipment 200 for data processing at the physical layer. The central station 23 can be used by the satellite network equipment 200 for data processing at the satellite link control layer and message data aggregation layer.

[0117] In some potential application scenarios, server 15 can be an Internet of Things (IoT) server. Server 15 can notify one or more terminals to perform specific operations, such as locking or unlocking. These terminals can be electronic devices that provide services to users when unlocked, such as shared bicycles or lockers. Server 15 can be configured by the operator providing these terminals, which include terminal 300. When terminal 100 receives an unlocking request from a user, it can send an unlock request (including the identification information of terminal 300) to server 15 via a cellular network. After receiving the unlock request, server 15 can send an unlock command to terminal 300 via the cellular network. Upon receiving the unlock command, terminal 300 performs the unlocking operation.

[0118] Alternatively, when terminal 100 receives an unlock operation from the user to unlock terminal 300, it can establish a communication connection with terminal 300 (e.g., a Bluetooth connection). Terminal 100 can receive the identification information of terminal 300 through the communication connection. Terminal 100 can send an unlock request (including the identification information of terminal 300) to server 15 via a cellular network. After receiving the unlock request, server 15 can send an unlock command to terminal 100 via the cellular network. After receiving the unlock command, terminal 100 can send the unlock command to terminal 300 via the communication connection, and terminal 300 can perform an unlock operation based on the unlock command.

[0119] However, when the terminal 100 is in an area with poor mobile communication signal or a damaged communication system (such as a land network outage caused by a natural disaster), taking unlocking as an example, if the terminal 100 cannot send an unlocking request to the server 15 through the cellular network, the user cannot unlock the terminal 300.

[0120] Therefore, in one possible implementation, after receiving a request operation (e.g., an unlocking operation) from user terminal 300 (e.g., unlocking terminal 300), terminal 100 can send a request (e.g., an unlocking request) to server 15 via satellite 21 and satellite network device 200. When server 15 receives the request, it can send an information instruction (e.g., an unlocking instruction) to satellite network device 200, which includes the identifier of terminal 300. Terminal 100 can also instruct terminal 300 to send a download request to satellite network device 200, which instructs satellite network device 200 to transmit the instruction (e.g., the unlocking instruction) sent by server 15 to terminal 300 via satellite 21. Upon receiving this instruction, terminal 300 can perform a corresponding operation (e.g., an unlocking operation), such as... Figure 2A As shown. In this way, terminal 100 can, when cellular networks are unavailable, use... Figure 2A The satellite communication system 20 shown performs corresponding operations on the terminal 300 (e.g., unlocking the terminal 300).

[0121] In another possible implementation, after receiving a request operation (e.g., an unlocking operation) from user terminal 300 (e.g., to unlock terminal 300), terminal 100 can establish a communication connection (e.g., Bluetooth connection) with terminal 300 and obtain the identification information of terminal 300. Terminal 100 can send a request (e.g., an unlocking request) (including the identification information of terminal 300) to server 15 via satellite 21 and satellite network device 200. When server 15 receives the request, it can send an information instruction (e.g., an unlocking instruction) to satellite network device 200. After sending a request (e.g., an unlocking request) to server 15, terminal 100 can also send a download request to satellite network device 200, which instructs satellite network device 200 to transmit the information instruction (e.g., an unlocking instruction) sent by server 15 to terminal 100 via satellite 21. After receiving the instruction, terminal 100 can send the instruction to terminal 300. After receiving the information instruction (e.g., an unlocking instruction), terminal 300 can perform a corresponding operation (e.g., an unlocking operation), such as... Figure 2B As shown. In this way, terminal 100 can use [the cellular network] when it is unavailable. Figure 2B The satellite communication system 30 shown performs corresponding operations on the terminal 300 (e.g., unlocking the terminal 300).

[0122] In another possible implementation, server 15 can send an operation command (e.g., an unlock command) to satellite network device 200. This operation command could be one received by server 15 from an operator (e.g., an unlock operation), or it could be generated by server 15 itself. Satellite network device 200 can broadcast this command to multiple terminals (including terminal 300) within the satellite network via satellite 21. Upon receiving the command, these terminals can perform corresponding operations (e.g., unlocking operations), such as... Figure 3 As shown. Thus, when cellular networks are unavailable, the operator providing the terminal 300 can... Figure 3 The satellite communication system 40 shown performs group operations on multiple terminals 300 in a specific area, avoiding the waste of transmission resources caused by sending the same instructions to each of the multiple terminals 300 individually. For example, it can unlock terminals 300 to facilitate use by users in the area.

[0123] It should be noted that since satellite 21 includes one or more satellites, and the coverage areas of different beams of each of these satellites are different, satellite network equipment 200 can send data to equipment in the area corresponding to the beam through different beams of different satellites.

[0124] Optionally, server 15 may send broadcast area information of the data to satellite network device 200 when sending data to satellite network device 200. Satellite network device 200 can determine the beam for broadcasting the data based on the broadcast area information. In this way, satellite network device 200 can broadcast data within the area indicated by the broadcast area information using the determined beam.

[0125] Optionally, server 15 may send broadcast time information of the data to satellite network device 200 when sending data to satellite network device 200. Satellite network device 200 may determine the time period for sending data to one or more terminals based on the broadcast time information.

[0126] This application provides a transmission method in which a satellite network device 200 can generate a second data packet based on broadcast data sent by a server 15. The satellite network device 200 can then send the second data packet to at least one terminal. In this way, terminals within the satellite network can directly receive broadcast data from the server 15 without needing to send a download request to the satellite network device 200.

[0127] Specifically, the converged communication platform 24 can receive broadcast data sent by the server 15. The converged communication platform 24 can generate a first data packet based on the broadcast data and send the first data packet to the ground central station 19. The ground central station 19 can obtain a second data packet based on the first data packet and send the second data packet to one or more terminals. For example, the ground central station 19 can send the second data packet to terminal 100 and terminal 300.

[0128] In one possible implementation, the broadcast data is broadcast data. Server 15 can send the broadcast data to all terminals within the broadcast range. For example, when the ground center station 19 sends the second data packet to other terminals through a designated beam, all terminals within the coverage area of ​​that designated beam can receive the second data packet, and after receiving it, can parse the second data packet to obtain the broadcast data.

[0129] In one possible implementation, the broadcast data is broadcast data. Server 15 can send multicast data of the broadcast group to one or more designated terminals. For example, when the ground center station 19 sends a second data packet containing multicast data to other terminals through a designated beam, all terminals within the coverage area of ​​the designated beam can receive the second data packet. However, only some of the terminals that receive the second data packet can parse it and obtain the multicast data. These terminals store the broadcast source identifier of the broadcast group from server 15.

[0130] It should be noted that the satellite network device 200 can provide one or more broadcast groups, each with a different identifier (also known as a broadcast source identifier). A broadcast group can include one or more terminals. The satellite network device 200 can provide broadcast groups to other servers, such as weather servers and marine information servers. Servers can send the broadcast source identifier of a broadcast group to terminals that have subscribed to the services provided by that server (for example, a weather server can send the broadcast source identifier of its broadcast group to terminals that have subscribed to weather forecast services). Servers can also send service data to terminals that have subscribed to their services based on the broadcast source identifier. For example, a weather server can send real-time weather data to terminals that have subscribed to weather forecast services through the satellite network device 200. When the satellite network device 200 receives data from a weather server sent to a broadcast group, it can encapsulate the data and the broadcast source identifier of the broadcast group into a data packet and send the data packet to the terminal of the broadcast group. The terminal can store the broadcast source identifier of the server's broadcast group and, based on the broadcast source identifier in a first or second data packet, determine that the multicast data comes from the server indicated by the stored broadcast source identifier. In this way, the server can send multicast data to some terminals, and some terminals can also parse and obtain the multicast data.

[0131] Optionally, the server can set different keys, encryption algorithms, etc., for different broadcast groups, and send the keys and decryption algorithms to the terminals when sending the broadcast source identifier. In this way, only the terminals of the broadcast group can parse and obtain the multicast data sent by the server to that broadcast group.

[0132] In one possible implementation, the broadcast data can be either broadcast data or multicast data. Server 15 can send the broadcast data and a broadcast source identifier together to satellite network device 200. Satellite network device 200 can obtain a second data packet based on the broadcast data and the broadcast source identifier. The terminal can determine whether the broadcast data in the data packet is broadcast data or multicast data based on the broadcast source identifier, and determine the source of the broadcast data (e.g., server 15, a broadcast group of server 15, etc.).

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

[0134] Figure 4A A schematic diagram of the outbound protocol architecture provided in an embodiment of this application is shown. Figure 4A As shown, terminal 100 can be used to process data transmitted by satellite network device 200 at the physical layer, satellite link control layer, message data aggregation layer, and application layer. The converged communication platform 24 can be used to process data sent to the terminal (e.g., terminal 100) at the application layer. Ground center station 19 may include one or more devices with transmitting capabilities and one or more devices with receiving capabilities, or may include one or more devices with both transmitting and receiving capabilities, without limitation herein. Ground center station 19 can be used to process data sent to the terminal (e.g., terminal 100) at the physical layer, satellite link control layer, and message data aggregation layer. The converged communication platform 24 and ground center station 19 can be collectively referred to as satellite network device 200.

[0135] Figure 4B This diagram illustrates a protocol encapsulation architecture for outbound data provided in an embodiment of this application. For example... Figure 4B As shown, the data transmission protocol layer on satellite network device 200 can be divided into application layer, message data aggregation layer, satellite link control layer, and physical layer. When satellite network device 200 sends data to terminal 100, the workflow of the data transmission protocol on satellite network device 200 can be as follows:

[0136] At the AP layer, satellite network device 200 can add header information to the broadcast data to obtain the first data packet. The broadcast data may include, but is not limited to, data, text, semaphores, voice, images, and animations sent by third-party servers (e.g., server 15, emergency rescue platform 26).

[0137] Optionally, the packet header information may include, but is not limited to, a compression indication field, an encryption indication field, etc. The compression indication field can be used to indicate whether the satellite network device 200 has performed compression. The encryption indication field is used to indicate whether the satellite network device 200 has performed encryption.

[0138] Optionally, the satellite network device 200 may encode and compress broadcast data, and after obtaining the compressed data, add a compression indication field before the compressed data. The compression indication field is used to indicate the type of encoding and compression algorithm used by the satellite network device 200.

[0139] Optionally, the satellite network device 200 can use a key to encrypt and broadcast data to obtain encrypted data. An encryption indication field can be added before the encrypted data. The encryption indication field is used to indicate the type of encryption algorithm used by the satellite network device 200.

[0140] Optionally, the satellite network device 200 can perform encoding and compression operations on the broadcast data to obtain compressed data. The satellite network device 200 can then encrypt the compressed data to obtain encrypted data. A header information is added before the encrypted data to obtain the first data packet. The header information may include, but is not limited to, a compression indication field and an encryption indication field. The compression indication field indicates the type of encoding and compression algorithm used by the satellite network device 200 to compress the data. The encryption indication field indicates the type of encryption algorithm used by the satellite network device 200 to encrypt the data.

[0141] Optionally, the satellite network device 200 can also receive broadcast source identification information sent by a third-party server. This broadcast source identification information can be used to indicate the source of the broadcast data, such as server 15 or a broadcast group of server 15. That is, the terminal receiving the first data packet can determine whether to receive the broadcast data in the first data packet based on the broadcast source identification information. For example, terminal 100 can store one or more broadcast source identification information entries. Terminal 100 can determine whether the broadcast source identification information in the first data packet is the same as one of the one or more broadcast source identification information entries stored by terminal 100. When terminal 100 determines that the broadcast source identification information in the first data packet is the same as one of the one or more broadcast source identification information entries stored by terminal 100, it obtains the broadcast data in the first data packet.

[0142] Furthermore, the satellite network device 200 can determine the encryption algorithm type of the broadcast data based on the broadcast source identification information. Thus, the terminal receiving the first data packet can decrypt the first data packet based on the broadcast source identification information, for example, by using a key agreed upon with the broadcast source or obtained through prior negotiation with the broadcast source, to obtain the broadcast data.

[0143] At the MDCP layer, the satellite network device 200 can obtain application layer packets sent from the AP layer through the inter-layer interface and treat each application layer packet as an MDCP SDU. The satellite network device 200 can split the MDCP SDU into one or more fixed-length MDCP segments (M_segment) and add a successor indication field to the header of each MDCP segment to obtain an MDCP PDU. That is, an MDCP PDU includes an M_segment and a successor indication field. The successor indication field can be used to indicate the order of the current MDCPPDU within the same MDCPSDU.

[0144] At the SLC layer, the satellite network device 200 can obtain the MDCPPDU issued by the MDCP layer through the inter-layer interface, which serves as the SLC SDU. The satellite network device 200 can segment the SLC SDU into one or more (e.g., four) fixed-length SLC segment data (S_segment), and add frame header information to the header of each S_segment to obtain the SLC PDU. The frame header information may include, but is not limited to, a total frame count field and a frame sequence number field. The total frame count field indicates the total number of SLC PDUs included in the SLC SDU to which this SLC PDU belongs. The frame sequence number field indicates the sequence number of this SLC PDU within its respective SLC SDU.

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

[0146] Figure 4C This illustration shows a schematic diagram of a protocol parsing architecture for outbound data provided in an embodiment of this application. For example... Figure 4CAs shown, the transport protocol layer on the terminal receiving the first data packet (e.g., terminal 100) can be divided into the application layer, message data aggregation layer, satellite link control layer, and physical layer. When terminal 100 receives data sent by satellite network device 200, the data transmission protocol workflow on terminal 100 can be as follows:

[0147] At the PHY layer, terminal 100 can capture the encoded data of the S2C-d tributary based on the subcode of the S2C-p tributary sent by satellite network equipment 200. After capturing the encoded data of the S2C-d tributary, terminal 100 can perform physical layer processing (e.g., despreading, demodulation, depiloting, decoding, etc.) on the encoded data of the S2C-d tributary to obtain physical frames. Terminal 100 can extract user frames belonging to terminal 100 from the physical frames. Terminal 100 can then present the user frames to the SLC layer through the inter-layer interface as SLC PDUs for the SLC layer.

[0148] At the SLC layer, when the user frame received by terminal 100 is a general data frame, terminal 100 can concatenate SLC PDUs belonging to the same SLC SDU into a single SLC SDU. Terminal 100 can then present the SLC SDU to the MDCP layer through the inter-layer interface, serving as the MDCP PDU for the MDCP layer.

[0149] At the MDCP layer, terminal 100 can process an MDCP PDU into an MDCPSDU or concatenate multiple MDCP PDUs into an MDCP SDU. Terminal 100 can then present the MDCP SDU to the AP layer through the inter-layer interface as the first data packet received by the AP layer.

[0150] At the AP layer, terminal 100 can obtain broadcast data from the first data packet.

[0151] Optionally, when the first data packet includes an encryption indication field and a compression indication field, the terminal 100 can decrypt the first data packet according to the indication to obtain compressed data. The terminal 100 then decompresses and decodes the compressed data according to the indication to obtain broadcast data.

[0152] Optionally, the first data packet may include broadcast source identification information. The terminal 100 can determine whether to receive broadcast data in the first data packet based on the broadcast source identification information. For example, the terminal 100 may store one or more broadcast source identification information entries. The terminal 100 can determine whether the broadcast source identification information in the first data packet is the same as one of the one or more broadcast source identification information entries stored by the terminal 100. When the terminal 100 determines that the broadcast source identification information in the first data packet is the same as one of the one or more broadcast source identification information entries stored by the terminal 100, it obtains the broadcast data in the first data packet. Furthermore, the terminal 100 can determine the encryption algorithm type of the broadcast data or determine whether encryption is required based on the broadcast source identification information. For example, if it is broadcast information, since the satellite network device 200 may not encrypt the data, the terminal 100 can determine that decryption is unnecessary. Thus, the terminal 100 can decrypt the first data packet based on the broadcast source identification information to obtain the broadcast data.

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

[0154] In one possible implementation, the converged communication platform 24 can receive broadcast data and a broadcast source identifier sent by the server 15, wherein the broadcast data is broadcast data or multicast data. The converged communication platform 24 can encapsulate the received broadcast data to obtain a first data packet. The converged communication platform 24 can send the first data packet and the broadcast source identifier to the ground center station 19. The ground center station 19 can obtain a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes the first data packet and a user identity (ID) field. The ground center station 19 can determine the value of the user ID field based on the broadcast source identifier; that is, the user ID field can be used to indicate the broadcast source of the broadcast data. It is understood that the user ID field can also be used to indicate whether the second data packet is a broadcast data packet or a multicast data packet. The ground center station 19 can send the second data packet to at least one terminal (e.g., terminal 100). After receiving the second data packet, the terminal 100 can determine the type of the second data packet and the broadcast source of the broadcast data based on the user ID field in the second data packet. Terminal 100 can determine whether to receive the second data packet based on its broadcast source. Once terminal 100 determines that it has received the second data packet, it can parse the packet based on its type to obtain the broadcast data. Here, the second data packet is an SLCPDU or a physical frame. In this way, terminals in a satellite network (such as terminal 100) can receive broadcast or multicast data.

[0155] Figure 5AA schematic flowchart of a transmission method provided in an embodiment of this application is shown.

[0156] like Figure 5A As shown, the transmission method includes the following steps:

[0157] S501. Server 15 sends the broadcast data and broadcast source identifier to the converged communication platform 24.

[0158] Server 15 can send broadcast data and a broadcast source identifier to the converged communication platform 24. The broadcast source identifier can be a broadcast ID set by the converged communication platform 24 for server 15 or a broadcast group of server 15. Alternatively, the broadcast source identifier can be identification information (e.g., name) for server 15 or a broadcast group of server 15.

[0159] S502. The converged communication platform 24 generates the first data packet based on the broadcast data.

[0160] The converged communication platform 24 can encapsulate broadcast data to obtain a first data packet. For a detailed description of how the converged communication platform generates the first data packet based on the broadcast data, please refer to the above. Figure 4B The embodiments shown are not described in detail here.

[0161] S503. The converged communication platform 24 sends the first data packet and the broadcast source identifier to the ground center station 19.

[0162] The converged communication platform 24 can send a first data packet containing broadcast data and a broadcast source identifier to the ground center station 19.

[0163] Optionally, when the broadcast source identifier is the identifier of server 15 or a broadcast group of server 15, the converged communication platform 24 can determine the broadcast ID of the broadcast source (i.e., server 15 or a broadcast group of server 15) based on the broadcast source identifier, and send the first data packet and the broadcast ID to the ground center station 19. The broadcast ID can be used to indicate the broadcast source. Specifically, the converged communication platform 24 stores the correspondence between the identifier information of server 15 or a broadcast group of server 15 and the broadcast ID. The converged communication platform 24 can determine the broadcast ID of the broadcast source identifier based on the broadcast source identifier sent by server 15.

[0164] S504. Ground center station 19 obtains a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes a user ID field, which is used to indicate the broadcast source of the second data packet and the type of the second data packet.

[0165] like Figure 5BAs shown, after receiving the first data packet and the broadcast source identifier, the ground center station 19 can process the first data packet through the MDCP layer and the SLC layer to obtain one or more fixed-length SLC segment data. For a detailed description of how the ground center station 19 obtains SLC segment data based on the first data packet, please refer to the above. Figure 4B The illustrated embodiment will not be described in detail here. The ground center station 19 can add frame header information to the header of each S_segment to obtain an SLC PDU (also known as a user frame). The frame header information may include, but is not limited to, a frame length field, a frame type field, and a user identity (ID) field.

[0166] The frame length field can be used to identify the type or length of a user frame.

[0167] The frame type field can be used to identify the type of user frame. For example, the frame type field can be 2 bits long. When the frame type field value is 00, the current user frame can be identified as a general data frame. General data frames can be used to transmit unicast or broadcast data. When the frame type field value is 01, the current user frame can be identified as an ACK frame. ACK frames can be used to confirm the transmission status of SLCPDUs at the SLC layer. When the frame type field value is 10, the current user frame can be identified as an acknowledgment frame. Acknowledgment frames can be used to confirm the parsing status of the first data packet at the application layer. Here, the following embodiments will use the example of general data frames being used to transmit unicast or broadcast data. That is, when broadcast data is sent via a general data frame, the frame type field value is 00. Using this method, it can be ensured that terminals already on the network that do not support broadcast / multicast functions can normally receive data packets from satellite network equipment. Terminals that support broadcast and multicast functions (such as terminal 100) will support the reception of data from multiple user IDs (such as a unicast ID, one or more broadcast source IDs or multicast source IDs). After receiving a data packet sent by satellite network device 200, the terminal will identify whether the IDs included in the data packet are multiple user IDs supported by terminal 100.

[0168] Alternatively, when the frame type field value is 00, the current user frame can be identified as a general data frame. General data frames can be used to transmit unicast data. When the frame type field value is 11, the current user frame can be identified as a broadcast frame (also known as a broadcast data packet). Broadcast frames can be used to transmit broadcast data.

[0169] For example, the frame type field can be 3 bits long. A value of 000 indicates the current user frame is a general data frame. A value of 001 indicates an ACK frame. A value of 010 indicates an acknowledgment frame. A value of 011 indicates a broadcast frame (also known as a broadcast data packet). Broadcast frames can be used to transmit broadcast data. A value of 100 indicates a multicast frame (also known as a multicast data packet). Multicast frames can be used to transmit multicast data.

[0170] The user ID field can be used to identify the broadcast source, helping the terminal determine whether it is data that needs to be received. Terminal 100 can retrieve user frames from the outbound data based on the value of the user ID field. Here, the value of the user ID field is the broadcast ID of the broadcast source. Terminal 100 stores the broadcast IDs of the preset broadcast sources. It should be noted that, since the number of broadcast sources and multicast sources differs, the lengths of the broadcast IDs of broadcast sources and multicast sources can be different.

[0171] It should also be noted that when the user frame is a general data frame used to transmit unicast data, the user ID field can be used to identify the receiving device, such as terminal 100. In this case, the value of the user ID field is the identifier of terminal 100 (e.g., the mobile phone number of terminal 100). To allow the user frame to transmit both unicast and broadcast data, the length of the user ID field is the maximum of the lengths of the identifier of terminal 100 and the broadcast ID. That is, terminal 100 can determine whether the data in the user frame is unicast, broadcast, or multicast data based on the value of the user ID field. For example, the broadcast ID (also known as broadcast ID) of a broadcast source can be 3 bits long, the broadcast ID (also known as multicast ID) of a multicast source can be 10 bits long, and the user ID of terminal 100 can be 34 bits long; therefore, the length of the user ID field is 34 bits. Alternatively, the user ID of terminal 100 can be 37 bits; therefore, the length of the user ID field is 37 bits. Furthermore, to enable terminal 100 to identify the broadcast source more quickly, the value of the user ID field can be assigned to the broadcast source, multicast source, and device identifier in ascending order. For example, a user ID field value of 0-7 indicates broadcast, while a user ID field value of 8-1023 indicates multicast.

[0172] Subsequently, ground station 19 can concatenate the broadcast frame with other user frames and add a version number field to the header of multiple user frames. The version number field can be used to indicate the version of the satellite communication system protocol. Ground station 19 can also add a checksum (e.g., cyclic redundancy check (CRC) code) to the tail of multiple user frames to obtain a physical frame. Ground station 19 can also perform physical layer processing on the physical frame (e.g., encoding, pilot insertion, modulation, spreading, etc.) and add a reserved segment to the physical frame to form the encoded data of the S2C-d branch, which is a fixed-length physical time slot. Then, ground station 19 can synchronously transmit the encoded data of the S2C-d branch and the subcode of the S2C-p branch to satellite 21, which relays it to one or more terminals (including terminal 100).

[0173] In this embodiment of the application, the above-described broadcast frame processing mechanism is only an example, and the application does not limit the specific operation of the broadcast frame processing mechanism.

[0174] S505. Ground center station 19 sends the second data packet to terminal 100.

[0175] The ground control station 19 can send the second data packet to the terminal 100 through the operation shown in step S504. The second data packet can be a user frame.

[0176] S506. When the value of the user ID field in the second data packet is a preset value, the first data packet is obtained based on the second data packet, and the first data packet is parsed. The preset value can be understood as a value obtained by the terminal 100 before communicating with the converged communication platform 24 or the ground center station 19 via the satellite communication link. For example, before communicating via the satellite communication link, the terminal 100 may communicate via cellular or other means, and the value may be configured by the converged communication platform for the terminal 100 or negotiated between the terminal 100 and the converged communication platform.

[0177] Terminal 100 can capture the encoded data of the S2C-d tributary based on the subcode of the S2C-p tributary transmitted by ground center station 19. After capturing the encoded data of the S2C-d tributary, terminal 100 can perform physical layer processing on the encoded data of the S2C-d tributary (e.g., despreading, demodulation, depiloting, decoding, etc.) to obtain physical frames. Then, it extracts user frames from the physical frames whose user ID field values ​​are preset values. Here, the preset values ​​may include, but are not limited to, the broadcast ID stored by terminal 100, the user ID of terminal 100, etc.

[0178] Afterwards, terminal 100 can obtain the first data packet based on the retrieved user frame. For details, please refer to... Figure 4CThe illustrated embodiment will not be described in detail here. Terminal 100 can parse the first data packet to obtain the broadcast data. Terminal 100 can also display the parsed broadcast data.

[0179] Optionally, server 15 may send broadcast area information of the broadcast data to converged communication platform 24 when sending broadcast data. Converged communication platform 24 can then determine the beam used for transmitting the broadcast data based on the broadcast area information. Alternatively, converged communication platform 24 may send the broadcast area information to ground center station 19, which can then determine the beam used for transmitting the broadcast data based on the broadcast area information. In this way, satellite network equipment 200 can broadcast data within the area indicated by the broadcast area information using the determined beam. It should be noted that the coverage area of ​​the beam used for transmitting broadcast data includes the area indicated by the broadcast area information.

[0180] Optionally, when sending broadcast data to the converged communication platform 24, the server 15 may send the broadcast time information of the broadcast data to the converged communication platform 24. The converged communication platform 24 may determine the time period for sending broadcast data to one or more terminals based on the broadcast time information.

[0181] It should be noted that, not limited to server 15, the converged communication platform 24 can also receive broadcast data from other broadcast sources (e.g., emergency rescue platform 26, a broadcast group of emergency rescue platform 26, etc.). It should also be noted that the converged communication platform 24 and the ground center station 19 can be collectively referred to as satellite network equipment 200.

[0182] In one possible implementation, the converged communication platform 24 can receive broadcast data and a broadcast source identifier sent by the server 15. The converged communication platform 24 can encapsulate the received broadcast data to obtain a first data packet. The converged communication platform 24 can send the first data packet and the broadcast source identifier to the ground center station 19. The ground center station 19 can obtain a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes the first data packet, a frame type indication field, and a broadcast ID field. The ground center station 19 can determine the value of the frame type indication field based on the broadcast source identifier. Here, the frame type indication field in the second data packet can be used to indicate that the second data packet is a broadcast data packet, or it can be used to indicate that the second data packet is a multicast data packet. The ground center station 19 can also determine the value of the broadcast ID field based on the broadcast source identifier; that is, the broadcast ID field can be used to indicate the broadcast source of the broadcast data. The ground center station 19 can send the second data packet to at least one terminal (e.g., terminal 100). After receiving the second data packet, the terminal 100 can determine the type of the second data packet based on the frame type indication field in the second data packet. Terminal 100 can determine whether to receive the second data packet based on the broadcast ID field of the second data packet. Once terminal 100 determines that it has received the second data packet, it can parse the second data packet based on its type to obtain the broadcast data. Here, the second data packet is an SLCPDU. In this way, terminals in a satellite network (such as terminal 100) can receive broadcast or multicast data.

[0183] The frame type indicator field can be used to identify the type of the second data packet generated by the ground center station 19. For example, the frame type field can be 3 bits long. When the frame type field value is 000, it indicates that the current second data packet is a general data frame. General data frames can be used to transmit unicast data. When the frame type field value is 001, it indicates that the current second data packet is an ACK frame. When the frame type field value is 010, it indicates that the current second data packet is an acknowledgment frame. When the frame type field value is 011, it indicates that the current second data packet is a broadcast frame (also known as a broadcast data packet). Broadcast frames can be used to transmit broadcast data. When the frame type field value is 100, it indicates that the current second data packet is a multicast frame (also known as a multicast data packet). Multicast frames can be used to transmit multicast data. Here, the user frame sent by the satellite network device 200 to the terminal 100 is a broadcast frame, and the frame type field value can be 011. Alternatively, the user frame sent by the satellite network device 200 to the terminal 100 is a multicast frame, and the frame type field value can be 100. Since the broadcast ID field of a broadcast frame and the broadcast ID field of a multicast frame have different lengths, the terminal 100 can determine the position and length of the broadcast ID field in the user frame based on the value of the frame type field, and thus obtain the broadcast ID field.

[0184] Optionally, the first data packet includes broadcast data and a broadcast source identifier that the converged communication platform 24 can receive from the server 15. The converged communication platform 24 can encapsulate the received broadcast data and broadcast source identifier to obtain the first data packet. The first data packet includes broadcast data and a broadcast ID field or a multicast ID field. The converged communication platform 24 can send the first data packet and broadcast indication information to the ground center station 19, wherein the broadcast indication information can be used to indicate that the first data packet is a broadcast data packet, or it can be used to indicate that the first data packet is a multicast data packet. In this way, the ground center station 19 can directly determine the value of the frame type indication field based on the broadcast indication information. The ground center station 19 can send a second data packet to at least one terminal.

[0185] In another possible implementation, the ground center station 19 can obtain the second data packet based on the first data packet and the broadcast source identifier. The second data packet includes the first data packet, a frame type indicator field, a broadcast type indicator field, and a broadcast ID field. The ground center station 19 can determine the value of the frame type indicator field based on the broadcast source identifier; that is, the frame type indicator field can be used to indicate that the second data packet is a data packet containing broadcast data (also known as a broadcast data packet). The ground center station 19 can also determine the value of the broadcast type indicator field based on the broadcast source identifier. When the value of the broadcast type indicator field is a first preset value, the broadcast type indicator field can be used to indicate that the second data packet is a broadcast data packet. When the value of the broadcast type indicator field is a second preset value, the broadcast type indicator field can be used to indicate that the second data packet is a multicast data packet. The ground center station 19 can also determine the value of the broadcast ID field based on the broadcast source identifier; the broadcast ID field can be used to indicate the broadcast source of the broadcast data. It should be noted that, because the number of multicast sources and broadcast sources differs, the length of the broadcast ID field used to indicate the broadcast source in broadcast packets and multicast packets differs. In other words, the broadcast type indicator field can be used to indicate the length of the broadcast ID field. Ground center station 19 can send the second data packet to at least one terminal (e.g., terminal 100).

[0186] After receiving the second data packet, terminal 100 can determine that the second data packet is a broadcast data packet based on the frame type indication field in the second data packet. Terminal 100 can also determine whether the second data packet is a broadcast or multicast data packet based on the broadcast type indication field, i.e., determine the broadcast ID field in the second data packet. Terminal 100 can then determine whether to receive the second data packet based on the broadcast ID field. Once terminal 100 determines that it has received the second data packet, it can parse the second data packet to obtain the broadcast data. Here, the second data packet is an SLCPDU. In this way, terminals in the satellite network (e.g., terminal 100) can receive broadcast or multicast data. Using this method, the type of broadcast and the broadcast type indication can indicate whether it is a multicast or broadcast. For broadcasts, since the amount of broadcast source data is smaller, the broadcast ID length can be shorter, thus saving outbound transmission resources.

[0187] Figure 6A A schematic flowchart of a transmission method provided in an embodiment of this application is shown.

[0188] like Figure 6A As shown, the transmission method includes the following steps:

[0189] S601. Server 15 sends the broadcast data and broadcast source identifier to the converged communication platform 24.

[0190] S602. The converged communication platform 24 generates the first data packet based on the broadcast data.

[0191] S603. The converged communication platform 24 sends the first data packet and the broadcast source identifier to the ground center station 19.

[0192] For a detailed description of steps S601-S603, please refer to the above. Figure 5A The embodiments shown are not described in detail here.

[0193] S604. Ground center station 19 obtains a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes a frame type indication field, which is used to indicate the type of the second data packet.

[0194] like Figure 6B As shown, after receiving the first data packet and the broadcast source identifier, the ground center station 19 can process the first data packet through the MDCP layer and the SLC layer to obtain one or more fixed-length SLC segment data. For a detailed description of how the ground center station 19 obtains SLC segment data based on the first data packet, please refer to the above. Figure 4B The illustrated embodiment will not be described in detail here. The ground center station 19 can add frame header information to the header of each S_segment to obtain an SLC PDU (also known as a user frame). The frame header information may include, but is not limited to, a frame length field, a frame type field, a broadcast type indicator field, and a broadcast ID field.

[0195] The frame length field can be used to identify the length of a user frame.

[0196] The frame type field is used to identify the type of user frame. For example, the frame type field can be 2 bits long. When the frame type field value is 00, it indicates that the current user frame is a general data frame, which can be used to transmit unicast data. When the frame type field value is 01, it indicates that the current user frame is an ACK frame. When the frame type field value is 10, it indicates that the current user frame is an acknowledgment frame. When the frame type field value is 11, it indicates that the current user frame is a broadcast frame (also known as a broadcast data packet), which can be used to transmit broadcast data. Here, the user frame is a broadcast frame, so the frame type field value is 11. It should be noted that the user frame only includes the broadcast type indicator field and the broadcast ID field when it is a broadcast frame.

[0197] The broadcast type indicator field can be used to indicate whether a user frame is a broadcast data packet or a multicast data packet. Specifically, when the value of the broadcast type indicator field is a first preset value, it indicates that the second data packet is a broadcast data packet. When the value of the broadcast type indicator field is a second preset value, it indicates that the second data packet is a multicast data packet. For example, the length of the broadcast type indicator field can be 1 bit. When the broadcast type indicator field is 0, it indicates that the current user frame is a broadcast frame. When the broadcast type indicator field is 1, it indicates that the current user frame is a multicast frame.

[0198] The broadcast ID field can be used to identify the broadcast source. Terminal 100 can retrieve broadcast frames from the preset broadcast source from the outbound data based on the value of the broadcast ID field. Here, the value of the broadcast ID field is the broadcast ID of the broadcast source. Terminal 100 stores the broadcast IDs of the preset broadcast sources.

[0199] It should be noted that because the number of broadcast sources and multicast sources differs, the broadcast IDs of broadcast sources and multicast sources have different lengths. When the broadcast type indicator field indicates that the user frame is a broadcast frame, the broadcast ID field is the same as the broadcast ID field, for example, the broadcast ID field has a length of 3 bits. When the broadcast type indicator field indicates that the user frame is a multicast frame, the broadcast ID field is the same as the multicast ID field, for example, the multicast ID field has a length of 10 bits. In this way, terminal 100 can determine the length of the broadcast ID field based on the value of the broadcast type indicator field, thereby saving outbound transmission resources.

[0200] Subsequently, ground control station 19 can obtain the encoded data of the S2C-d tributary based on the user frame, and then relay the encoded data of the S2C-d tributary and the subcode of the S2C-p tributary to one or more terminals (including terminal 100) via satellite 21. For details, please refer to the above. Figure 5A The embodiments shown are not described in detail here.

[0201] S605. Ground center station 19 sends the second data packet to terminal 100.

[0202] The ground control station 19 can send the second data packet to the terminal 100 through the operation shown in step S604. The second data packet can be a user frame.

[0203] S606. Terminal 100 determines the type of the second data packet based on the frame type indication field of the second data packet.

[0204] Terminal 100 can capture the encoded data of the S2C-d tributary based on the subcode of the S2C-p tributary sent by ground central station 19. After capturing the encoded data of the S2C-d tributary, terminal 100 can perform physical layer processing on the encoded data of the S2C-d tributary (e.g., despreading, demodulation, depiloting, decoding, etc.) to obtain physical frames.

[0205] Terminal 100 can determine the type of the user frame, i.e., the type of the second data packet, based on the frame type indicator field of the user frame in the physical frame. When terminal 100 determines that the second data packet is a broadcast data packet based on the value of the frame type indicator field, terminal 100 can obtain the broadcast type indicator field of the second data packet.

[0206] S607. Terminal 100 determines the broadcast ID field in the second data packet based on the broadcast type indication field of the second data packet.

[0207] Terminal 100 can determine whether the second data packet is a broadcast data packet or a multicast data packet based on the broadcast type indication field of the second data packet. Terminal 100 can also determine the broadcast ID field based on the broadcast type indication field.

[0208] S608. When the value of the broadcast ID field is a preset value, the terminal 100 obtains the first data packet based on the second data packet and parses the first data packet.

[0209] Terminal 100 can retrieve user frames from physical frames whose broadcast ID field value is a preset value. Here, the preset value may include, but is not limited to, the broadcast ID stored by terminal 100. Terminal 100 can also obtain the first data packet based on the user frame; for details, please refer to... Figure 4C The illustrated embodiment will not be described in detail here. Terminal 100 can parse the first data packet to obtain the broadcast data. Terminal 100 can also display the parsed broadcast data.

[0210] Optionally, server 15 may send broadcast area information of the broadcast data to converged communication platform 24 when sending broadcast data. Converged communication platform 24 can then determine the beam used for transmitting the broadcast data based on the broadcast area information. Alternatively, converged communication platform 24 may send the broadcast area information to ground center station 19, which can then determine the beam used for transmitting the broadcast data based on the broadcast area information. In this way, satellite network equipment 200 can broadcast data within the area indicated by the broadcast area information using the determined beam. It should be noted that the coverage area of ​​the beam used for transmitting broadcast data includes the area indicated by the broadcast area information.

[0211] Optionally, when sending broadcast data to the converged communication platform 24, the server 15 may send the broadcast time information of the broadcast data to the converged communication platform 24. The converged communication platform 24 may determine the time period for sending broadcast data to one or more terminals based on the broadcast time information.

[0212] It should be noted that, not limited to server 15, the converged communication platform 24 can also receive broadcast data from other broadcast sources (e.g., emergency rescue platform 26, a broadcast group of emergency rescue platform 26, etc.). It should also be noted that the converged communication platform 24 and the ground center station 19 can be collectively referred to as satellite network equipment 200.

[0213] In another possible implementation, the converged communication platform 24 can receive broadcast data and a broadcast source identifier sent by the server 15. Based on the received broadcast data and broadcast source identifier, the converged communication platform 24 can encapsulate a first data packet. The first data packet includes broadcast data and a broadcast source identifier field (used to indicate the broadcast source of the broadcast data). The converged communication platform 24 can send the first data packet and broadcast indication information to the ground center station 19, wherein the broadcast indication information can be used to indicate that the first data packet is a broadcast data packet, or it can be used to indicate that the first data packet is a multicast data packet. In this way, the ground center station 19 can directly determine the value of the frame type indication field based on the broadcast indication information. The ground center station 19 can send a second data packet to at least one terminal. Optionally, the first data packet includes broadcast data, a broadcast type indication field, and a broadcast ID field.

[0214] In one possible implementation, the converged communication platform 24 can receive broadcast data and a broadcast source identifier sent by the server 15, wherein the broadcast data is broadcast data or multicast data. The converged communication platform 24 can encapsulate the received broadcast data to obtain a first data packet. The converged communication platform 24 can send the first data packet and the broadcast source identifier to the ground center station 19. The ground center station 19 can obtain a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes the first data packet and a first version number. The ground center station 19 can determine a broadcast type indication field, a broadcast ID field, and the first version number based on the broadcast source identifier. The first version number can be used to indicate that the second data packet is a data packet containing broadcast data (i.e., a broadcast data packet). Additionally, the second data packet may also include a broadcast type indication field and a broadcast ID field. The ground center station 19 can determine the broadcast type indication field and the broadcast ID field based on the broadcast source identifier. The broadcast type indication field can be used to indicate whether the second data packet is a broadcast data packet or a multicast data packet. The broadcast ID field can be used to indicate the broadcast source of the broadcast data. Ground center station 19 can send the second data packet to at least one terminal (e.g., terminal 100).

[0215] After determining that the second data packet is a broadcast data packet based on the first version number in the received second data packet, terminal 100 can parse the second data packet to obtain the broadcast data. When the second data packet includes a broadcast type indication field and a broadcast ID field, terminal 100 can determine whether the second data packet is a broadcast data packet or a multicast data packet based on the broadcast type indication field, that is, determine the length of the broadcast ID field. Terminal 100 can then determine whether to receive the second data packet based on the broadcast ID field. After terminal 100 determines that it has received the second data packet, it can parse the second data packet to obtain the broadcast data. Here, the second data packet is a physical frame. In this way, terminals in the satellite network (such as terminal 100) can receive broadcast data or multicast data.

[0216] Figure 7A A schematic flowchart of a transmission method provided in an embodiment of this application is shown.

[0217] like Figure 7A As shown, the transmission method includes the following steps:

[0218] S701. Server 15 sends the broadcast data and broadcast source identifier to the converged communication platform 24.

[0219] S702. The converged communication platform 24 generates the first data packet based on the broadcast data.

[0220] S703. The converged communication platform 24 sends the first data packet and the broadcast source identifier to the ground center station 19.

[0221] Specifically, the detailed descriptions of steps S701-S703 can be found above. Figure 5A The embodiments shown are not described in detail here.

[0222] S704. Ground center station 19 obtains a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes a first version number and the first data packet. The first version number is used to indicate the type of the second data packet.

[0223] like Figure 7B As shown, after receiving the first data packet and the broadcast source identifier, the ground center station 19 can process the first data packet through the MDCP layer and the SLC layer to obtain an SLC PDU (also known as a user frame). For a detailed description of how the ground center station 19 obtains the user frame based on the first data packet, please refer to the above. Figure 4B The illustrated embodiment will not be described in detail here. The frame header information may include, but is not limited to, a frame length field, a broadcast type indicator field, and a broadcast ID field. For a description of the frame header information, please refer to the above. Figure 6B The embodiments shown are not described in detail here.

[0224] Ground center station 19 can determine that a user frame is a broadcast data frame based on the broadcast source identifier, that is, determine the first version number. Ground center station 19 can concatenate user frames containing broadcast data with other user frames containing broadcast data, and add the first version number to the header of multiple user frames. The first version number can be used to indicate that these user frames are broadcast frames. It is understood that when concatenating user frames that do not contain broadcast data (e.g., receipt frames) with other user frames that do not contain broadcast data, ground center station 19 can add a second version number to the header of multiple user frames. The second version number is different from the first version number. That is, the first version number can be understood as a version number field with a first value, and the second version number can be understood as a version number field with a second value. In this way, terminal 100 can determine whether the received frame is a broadcast frame based on the version number. Distinguishing by version number helps ensure system compatibility, ensuring that older versions of terminals are not affected, and newer versions of terminals can add more extended functions.

[0225] Ground station 19 can also add check codes (e.g., cyclic redundancy check (CRC) codes) to the end of multiple user frames to obtain physical frames. Ground station 19 can also perform physical layer processing on the physical frames (e.g., encoding, pilot insertion, modulation, spreading, etc.) and add reserved segments to the physical frames to form coded data of the S2C-d branch with a fixed length of physical time slot. Then, ground station 19 can synchronously transmit the coded data of the S2C-d branch and the subcode of the S2C-p branch to satellite 21, which will then relay the data to one or more terminals (including terminal 100).

[0226] S705. Ground center station 19 sends the second data packet to terminal 100.

[0227] The ground control station 19 can send the second data packet to the terminal 100 through the operation shown in step S704. The second data packet can be a physical frame.

[0228] S706. Terminal 100 determines the type of the second data packet based on the first version number.

[0229] Terminal 100 can capture the encoded data of the S2C-d tributary based on the subcode of the S2C-p tributary sent by ground central station 19. After capturing the encoded data of the S2C-d tributary, terminal 100 can perform physical layer processing on the encoded data of the S2C-d tributary (e.g., despreading, demodulation, depiloting, decoding, etc.) to obtain physical frames.

[0230] When terminal 100 determines that the version number field of the physical frame is the first version number, it can determine that the physical frame is a physical frame that includes the broadcast frame.

[0231] S707. Terminal 100 determines the broadcast ID field in the second data packet based on the broadcast type indication field in the second data packet.

[0232] Terminal 100 can determine the broadcast ID field of each user frame based on the broadcast type indication field of each user frame in the second data packet.

[0233] S708. When the value of the broadcast ID field is a preset value, the terminal 100 obtains the first data packet based on the second data packet and parses the first data packet.

[0234] Specifically, when terminal 100 determines that the value of the broadcast ID field of a user frame is a preset value, it retrieves the user frame and obtains the first data packet based on the user frame. For a detailed description of how terminal 100 obtains the first data packet based on the user frame, please refer to the above. Figure 4C The embodiments shown are not described in detail here.

[0235] It should be noted that a physical frame may include one or more user frames whose broadcast ID field values ​​are preset values. Terminal 100 can obtain a first data packet containing broadcast data sent by the broadcast source indicated by the broadcast ID field, based on one or more user frames with the same broadcast ID field value.

[0236] Optionally, when sending broadcast data to the converged communication platform 24, the server 15 may send the broadcast area information of the broadcast data to the converged communication platform 24. The converged communication platform 24 may then determine the beam used for transmitting the broadcast data based on the broadcast area information. Alternatively, the converged communication platform 24 may send the broadcast area information to the ground center station 19, which may then determine the beam used for transmitting the broadcast data based on the broadcast area information.

[0237] Optionally, when sending broadcast data to the converged communication platform 24, the server 15 may send the broadcast time information of the broadcast data to the converged communication platform 24. The converged communication platform 24 may determine the time period for sending broadcast data to one or more terminals based on the broadcast time information.

[0238] It should be noted that, not limited to server 15, the converged communication platform 24 can also receive broadcast data from other broadcast sources (e.g., emergency rescue platform 26, a broadcast group of emergency rescue platform 26, etc.). It should also be noted that the converged communication platform 24 and the ground center station 19 can be collectively referred to as satellite network equipment 200.

[0239] In another possible implementation, the converged communication platform 24 can encapsulate a first data packet based on the received broadcast data and broadcast source identifier. The first data packet includes broadcast data and a broadcast source identifier field (used to indicate the broadcast source of the broadcast data). The converged communication platform 24 can send the first data packet and broadcast indication information to the ground center station 19, wherein the broadcast indication information can be used to indicate that the first data packet is a broadcast data packet, or, the broadcast indication information can be used to indicate that the first data packet is a multicast data packet, or the broadcast indication information can be used to indicate that the first data packet is a broadcast data packet. The ground center station 19 can directly determine the first version number based on the broadcast indication information. The second data packet includes the first data packet and the first version number. The ground center station 19 can send the second data packet to at least one terminal. Optionally, the first data packet may include broadcast data, a broadcast type indication field, and a broadcast ID field, wherein the descriptions of the broadcast type indication field and the broadcast ID field can be found in [reference needed]. Figure 7B The illustrated embodiment will not be described in detail here. Optionally, the first data packet may include broadcast data and one of a broadcast ID field and a multicast ID field, and the second data packet includes a broadcast type field.

[0240] In one possible implementation, the converged communication platform 24 can receive broadcast data and a broadcast source identifier sent by the server 15, wherein the broadcast data is broadcast data or multicast data. The converged communication platform 24 can encapsulate the received broadcast data to obtain a first data packet. The converged communication platform 24 can send the first data packet and the broadcast source identifier to the ground center station 19. The ground center station 19 can obtain a second data packet based on the first data packet and the broadcast source identifier. The second data packet includes the first data packet. The ground center station 19 can determine a first beam based on the broadcast source identifier. The first beam can be used to transmit the second data packet including the broadcast data. Additionally, the second data packet may also include a broadcast type indication field and a broadcast ID field. The ground center station 19 can determine the broadcast type indication field and the broadcast ID field based on the broadcast source identifier. The broadcast type indication field can be used to indicate whether the second data packet is a broadcast data packet or a multicast data packet. The broadcast ID field can be used to indicate the broadcast source of the broadcast data. The ground center station 19 can send the second data packet to at least one terminal (e.g., terminal 100) on the first beam.

[0241] The second data packet received by terminal 100 on the first beam can be identified as a broadcast data packet based on the first beam. Terminal 100 can further determine whether the second data packet is a broadcast or multicast data packet based on the broadcast type indication field, i.e., by determining the length of the broadcast ID field. Terminal 100 can then determine whether to receive the second data packet based on the broadcast ID field. Once terminal 100 determines that it has received the second data packet, it can parse the second data packet to obtain the broadcast data. Here, the second data packet is an SLCPDU or a physical frame. In this way, terminals in a satellite network (such as terminal 100) can receive broadcast or multicast data.

[0242] Figure 8A A schematic flowchart of a transmission method provided in an embodiment of this application is shown.

[0243] like Figure 8A As shown, the transmission method includes the following steps:

[0244] S801. Server 15 sends the broadcast data and broadcast source identifier to the converged communication platform 24.

[0245] S802. The converged communication platform 24 generates the first data packet based on the broadcast data.

[0246] S803. The converged communication platform 24 sends the first data packet and the broadcast source identifier to the ground center station 19.

[0247] For a detailed description of steps S801-S803, please refer to the above. Figure 5A The embodiments shown are not described in detail here.

[0248] S804. Ground center station 19 obtains the second data packet based on the first data packet and the broadcast source identifier.

[0249] S805. Ground center station 19 determines the first beam based on the broadcast source identifier.

[0250] like Figure 7B As shown, after receiving the first data packet and the broadcast source identifier, the ground center station 19 can process the first data packet through the MDCP layer and the SLC layer to obtain an SLC PDU (also known as a user frame). For a detailed description of how the ground center station 19 obtains the user frame based on the first data packet, please refer to the above. Figure 4B The illustrated embodiment will not be described in detail here. The frame header information may include, but is not limited to, a frame length field, a broadcast type indicator field, and a broadcast ID field. For a description of the frame header information, please refer to the above. Figure 6B The illustrated embodiment will not be described in detail here. It should be noted that the user frames obtained by the ground center station 19 are broadcast frames.

[0251] Ground center station 19 can concatenate broadcast frames (also known as broadcast data packets) together, add a version number and a check bit to obtain a physical frame. The version number can be used to indicate the version of the communication protocol of the satellite communication system. Satellite network equipment 200 can perform physical layer processing on the physical frame (e.g., encoding, pilot insertion, modulation, spread spectrum, etc.) to obtain the encoded data of the S2C-d tributary.

[0252] The ground control station 19 can also determine the secondary code of the S2C-p tributary, i.e., determine the first beam, based on the broadcast source identifier. It should be noted that the secondary code used by the ground control station 19 to send unicast data packets is different from the secondary code used to send broadcast data packets. The terminal can determine whether the encoded data of the S2C-d tributary includes broadcast data packets based on the secondary code.

[0253] In some embodiments, all beams used to transmit broadcast data packets (also known as broadcast beams) have the same subcode. For example, when satellite 21 includes a total of 9 beams (also known as unicast beams) for broadcasting unicast data, satellite 21 also includes 9 broadcast beams, and these 9 broadcast beams have the same subcode. That is, among the 9 unicast beams, each unicast beam has a broadcast beam with the same coverage area, and the subcode of each unicast beam is different from the subcode of the broadcast beam.

[0254] In other embodiments, to avoid interference between broadcast beams with overlapping coverage areas, the secondary codes of the beams used to transmit unicast data (also called unicast beams) and the broadcast beams with the same coverage area are different, and the secondary codes of different broadcast beams are also different. For example, when satellite 21 includes a total of 9 unicast beams, satellite 21 also includes 9 broadcast beams, and the secondary codes of these 9 broadcast beams are different. That is, among the 9 unicast beams, any one unicast beam has a broadcast beam with the same coverage area, and the secondary codes of any two broadcast beams are different.

[0255] Ground center station 19 can combine the coded data of S2C-d branch and the subcode of S2C-p branch to form pilot coded data, i.e. outgoing data (also known as the first beam), and relay it to terminal 100 via satellite 21.

[0256] S806. Ground center station 19 sends the second data packet to terminal 100 on the first beam.

[0257] The second data packet can be a broadcast frame or a physical frame including a broadcast frame. A description of the ground center station 19 sending the second data packet to the terminal 100 on the first beam can be found above. Figure 8B The embodiments shown are not described in detail here.

[0258] S807. Terminal 100 determines the type of the second data packet based on the first beam.

[0259] Terminal 100 stores the subcodes of the broadcast beam and the unicast beam. When terminal 100 receives outbound data, it can determine whether the subcode of the S2C-p tributary in the outbound data is the same as the stored subcode based on the stored subcode. When terminal 100 determines that the subcode in the outbound data is the same as the stored subcode of the broadcast beam, it determines that the encoded data includes the broadcast data packet.

[0260] In one possible implementation, terminal 100 can sequentially determine whether the received subcode and the stored subcode are the same according to the order in which the subcodes are stored.

[0261] In another possible implementation, terminal 100 can obtain the secondary code of the beam that intersects the coverage area and the current location based on its current location. It first determines whether the received secondary code is the same as the stored secondary code. This allows for a faster determination of whether the received outgoing data includes unicast or broadcast data. For example, terminal 100 can store the correspondence between secondary codes of different beams and coverage areas, and use this correspondence to determine the secondary code of the beam that intersects the coverage area and the current location.

[0262] Optionally, terminal 100 can store the identifiers or subcodes of beams received at different locations. Based on the stored correspondence between location and beam identifiers (or subcodes), terminal 100 can determine the subcode of the beam received at the location closest to the current location. Terminal 100 can first determine whether the received subcode is the same as the subcode of the beam received at the location closest to the current location; this allows for a faster determination of whether the received outgoing data includes unicast or broadcast data.

[0263] It should be noted that the methods described above for determining whether the stored subcode and the received subcode are the same can be used in combination. For example, when terminal 100 can acquire the subcode of the beam intersecting the coverage area and the current location, it can first determine whether the received subcode and the acquired subcode are the same. When terminal 100 cannot acquire the subcode of the beam intersecting the coverage area and the current location, it can sequentially determine whether the received subcode and the stored subcode are the same according to the order in which the subcodes were stored. It should also be noted that the methods described above are not limited to the above methods; other methods can also be used to determine whether the subcodes are the same. For example, terminal 100 can randomly select a stored subcode and compare it with the received subcode.

[0264] S808. Terminal 100 determines the broadcast ID field in the second data packet based on the broadcast type indication field in the second data packet.

[0265] When terminal 100 determines that the type of the second data packet is a data packet including broadcast data based on the first beam, it can obtain the broadcast type indication field of each user frame in the physical frame, and determine whether the user frame is a broadcast frame or a multicast frame based on the broadcast type indication field, that is, determine the broadcast ID field of the user frame.

[0266] S809. When the value of the broadcast ID field is a preset value, the terminal 100 obtains the first data packet based on the second data packet and parses the first data packet.

[0267] For a detailed description of step S808, please refer to the above. Figure 7A The description of step S708 shown will not be repeated here.

[0268] In another possible implementation, the converged communication platform 24 can encapsulate a first data packet based on the received broadcast data and broadcast source identifier. The first data packet includes broadcast data and a broadcast source identifier field (used to indicate the broadcast source of the broadcast data). The converged communication platform 24 can send the first data packet and broadcast indication information to the ground center station 19, wherein the broadcast indication information can be used to indicate that the first data packet is a broadcast data packet, or the broadcast indication information can be used to indicate that the first data packet is a multicast data packet. The ground center station 19 can directly determine the first beam based on the broadcast indication information. The ground center station 19 can send a second data packet to at least one terminal on the first beam. Optionally, the first data packet may include broadcast data, a broadcast type indication field, and a broadcast ID field. Optionally, the first data packet may include broadcast data and one of a broadcast ID field and a multicast ID field, and the second data packet includes a broadcast type field.

[0269] The following describes a satellite communication system 50 provided in an embodiment of this application.

[0270] like Figure 9 As shown, the satellite communication system 50 may include, but is not limited to, terminal 100, satellite 21, ground center station 19, converged communication platform 18, broadcast multicast service center 17, server 15, etc.

[0271] In this system, the satellite network terminal 100 can send data packets to the server 15 via the satellite network device 200. For details, please refer to... Figure 1 The embodiments shown will not be described in detail here. The satellite network equipment 200 may include, but is not limited to, the ground central station 19 and the converged communication platform 18.

[0272] The server 15 can send data packets to the terminal 100 via the satellite network device 200. The satellite network device 200 may include, but is not limited to, a ground center station 19, a converged communication platform 18, and a broadcast / multicast service center 17.

[0273] During unicast, the converged communication platform 18 stores the data sent by server 15 to terminal 100. When satellite network device 200 receives a download request from terminal 100, it encapsulates the data sent by server 15 to terminal 100 into a data packet based on the download request and sends the data packet to terminal 100 via satellite 21. The download request can be used to instruct the converged communication platform 18 to send the data sent by server 15 to terminal 100.

[0274] During broadcasting or multicasting, after receiving data from server 15, broadcast multicast service center 17 can send the data to multiple terminals under the satellite network via satellite 21, including terminal 100.

[0275] Optionally, the satellite communication system 10 may also include an emergency rescue platform 26 and an emergency rescue center 27. The satellite network device 200 can transmit emergency rescue frames sent by the terminal 100 to the emergency rescue center 27 via the emergency rescue platform 26. The emergency rescue center 27 can also broadcast data (e.g., rescue information) to multiple devices within the satellite network via the emergency rescue platform 26, the satellite network device 200, and the satellite 21.

[0276] The description of ground center station 19 can be found above. Figure 1 The illustrated embodiment will not be described in detail here. The converged communication platform 18 can be used to process unicast data at the application layer. The unicast data is the data sent to the terminal by the satellite network device 200 after receiving a download request from the terminal. The broadcast / multicast service center 17 can be used to process broadcast data at the application layer, obtaining a first data packet containing the broadcast data. The broadcast / multicast service center 17 can also be used to prompt the server 15 with the broadcast group and the corresponding broadcast source identifier. In this way, the broadcast / multicast service center 17 can send broadcast data or multicast data to multiple terminals.

[0277] Figure 10 A schematic diagram of the outbound protocol architecture provided in an embodiment of this application is shown.

[0278] like Figure 10As shown, during broadcast or multicast, terminal 100 can be used to process data transmitted by satellite network device 200 at the physical layer, satellite link control layer, message data aggregation layer, and application layer. Broadcast / multicast service center 17 can be used to process data sent to terminals (e.g., terminal 100) at the application layer. Ground center station 19 may include one or more devices with transmitting and receiving functions, or may include one or more devices with both transmitting and receiving functions, without limitation herein. Ground center station 19 can be used to process data sent to terminals (e.g., terminal 100) at the physical layer, satellite link control layer, and message data aggregation layer. Broadcast / multicast service center 17, converged communication platform 18, and ground center station 19 can be collectively referred to as satellite network device 200.

[0279] It should be noted that when the broadcast multicast service center 17 is used to process broadcast data, the operations performed by the broadcast multicast service center 17 can be found in the above description. Figures 4A-8B The operations performed by the converged communication platform 24 in the illustrated embodiment will not be described in detail here.

[0280] In one possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can negotiate with at least one terminal (including terminal 100) to determine a default broadcast period. The default broadcast period is the period during which the converged communication platform 24 or the broadcast multicast service center 17 sends a first data packet containing broadcast data to at least one terminal.

[0281] like Figure 11 As shown, a default broadcast cycle includes a default broadcast time and a default broadcast interval. The default broadcast time is a period of time (e.g., 20 seconds) starting from the default broadcast moment (e.g., t1, t2). During the default broadcast time, the converged communication platform 24 or the broadcast multicast service center 17 can send a first data packet to at least one terminal. The converged communication platform 24 or the broadcast multicast service center 17 can select a portion of the data packets transmitted during the default broadcast time to send broadcast data; that is, during the broadcast time, the converged communication platform 24 or the broadcast multicast service center 17 may send multiple data packets, only a portion of which are broadcast data packets. Terminal devices expecting to receive the broadcast data will receive the data during the broadcast time.

[0282] The default broadcast interval is the time interval between the default broadcast time in one default broadcast cycle and the default broadcast time in the next default broadcast cycle. During the default broadcast interval, the converged communication platform 24 or the broadcast multicast service center 17 will not send the first data packet to at least one terminal.

[0283] Here, the default broadcast duration is T1, and the default broadcast interval duration is T2. The default broadcast cycle is T1 + T2. The default broadcast time can be obtained from the default broadcast cycle.

[0284] Optionally, during the default broadcast time, the converged communication platform 24 or the broadcast multicast service center 17 can send a first data packet to at least one terminal every preset time interval (e.g., 5ms). This allows the converged communication platform 24 or the broadcast multicast service center 17 to broadcast the first data packet multiple times, improving the success rate of the terminal receiving the first data packet.

[0285] Optionally, the default broadcast cycle can be determined through negotiation between the converged communication platform 24 or the broadcast multicast service center 17 and other servers (e.g., server 15) used to send broadcast data. Alternatively, the default broadcast cycle can be determined by the operators of the converged communication platform 24 or the broadcast multicast service center 17. The terminal 100 stores the default broadcast cycle.

[0286] The following section presents a set of interface diagrams provided in the embodiments of this application.

[0287] When terminal 100 is connected to a satellite network, it can display the broadcast time of the next first data packet, i.e., the default broadcast time. This allows users to receive the first data packet at the default broadcast time, improving the success rate of receiving the first data packet.

[0288] For example, such as Figure 12A As shown, terminal 100 can display desktop 1401. Desktop 1401 can include multiple application icons, such as a communication application icon 1403, etc. The communication application icon 1403 can be used to trigger the display of the communication application interface (e.g., the screen below). Figure 12B The communication application interface 1411 shown can be used to receive / send satellite data. For example, the communication application can be SMS, mobile internet, etc. A status bar 1402 can also be displayed at the top of the desktop 1401. The status bar 1402 can display a signal indicator icon 1402A, which is used to indicate that the terminal 100 has lost communication with the cellular network. At this time, the terminal 100 is in a state without cellular signal.

[0289] Terminal 100 can receive user input for the communication application icon 1403, and in response to the input, display as shown below. Figure 12B The communication application interface 1411 shown is shown.

[0290] like Figure 12BAs shown, the communication application interface 1411 may include, but is not limited to, the broadcast / multicast message option 1412. The broadcast / multicast message option 1412 can be used to trigger the terminal 100 to display the broadcast message option 1413 and the multicast message option 1414. Here, the broadcast / multicast message option 1412 is selected, so the communication application interface 1411 also includes the broadcast message option 1413 and the multicast message option. The broadcast message option 1413 can be used to trigger the terminal 100 to display the broadcast message interface 1421. The multicast message option can be used to trigger the terminal 100 to display the multicast message interface. The multicast message interface can be used to display the multicast source option, which can be used to trigger the terminal 100 to display the broadcast data sent by the multicast source.

[0291] Terminal 100 can receive user input for broadcast message option 1413, and in response to the input, display as shown below. Figure 12C The broadcast message interface 1421 shown is shown.

[0292] like Figure 12C As shown, the broadcast message interface 1421 may include, but is not limited to, one or more broadcast source options. These one or more broadcast source options can be used to trigger the terminal 100 to display broadcast data sent by the broadcast source indicated by the broadcast source option. Here, the one or more broadcast source options include broadcast source option 1422. Broadcast source option 1422 can be used to trigger the terminal 100 to display the broadcast details interface 1431. Optionally, the broadcast source option may also display the name of the broadcast source and some broadcast data. For example, broadcast source option 1422 displays the broadcast source name: "XX Satellite Broadcast," and some broadcast data: "Weather Broadcast…."

[0293] The broadcast message interface 1421 may also include a broadcast time bar 1423. The broadcast time bar 1423 can be used to display the transmission time of the next broadcast data packet, that is, the reception time of the next broadcast data packet that the terminal 100 can receive. The broadcast time displayed in the broadcast time bar 1423 can be obtained based on the default broadcast cycle and the current time. For example, when the default broadcast cycle is 20 minutes, that is, the default broadcast times each day are 00:00, 00:20, 00:40, ..., 23:20, 23:40. The terminal 100 can calculate the nearest default broadcast time after the current time based on the current time and display the value of that default broadcast time in the broadcast time bar 1423. Here, the current time displayed by the terminal 100 is 08:10, and the next broadcast time displayed in the broadcast time bar 1423 of the terminal 100 is "08:20". In this way, the broadcast time bar 1423 can remind the user of the time when the next broadcast data packet will be received. If a user wants to improve the success rate of receiving the next broadcast data packet, they can perform satellite alignment on terminal 100 at the time indicated by broadcast time bar 1423, or move to an area without obstructions, to enhance the satellite signal strength received by terminal 100 and improve the success rate of receiving broadcast data packets. It should be noted that the broadcast time of broadcast data packets sent within the default broadcast time can be considered the default broadcast time of that default broadcast time. Furthermore, since more than one broadcast data packet can be sent within a default broadcast time, the transmission time of the next broadcast data packet is the default broadcast time of the first data packet in the next default broadcast cycle.

[0294] Terminal 100 can receive user input regarding broadcast source option 1422, and in response to that input, display as shown below. Figure 12D The broadcast details interface shown is 1431.

[0295] like Figure 12D As shown, the broadcast details interface 1431 may include, but is not limited to, a broadcast message box 1432 and reception time information 1433. The broadcast message box 1432 can be used to display received broadcast data. The reception time information 1433 can be used to indicate the reception time of the broadcast data in the broadcast message box 1432. It is understood that due to potential delays in the terminal 100's reception of satellite data, the time value displayed in the reception time information may be later than the default broadcast time. Optionally, the broadcast details interface 1431 may also display a broadcast time bar 1423.

[0296] Subsequently, at the next broadcast data packet transmission time indicated by the broadcast time bar 1423, terminal 100 can receive the broadcast data packet sent by the converged communication platform 24 or the broadcast multicast service center 17, and parse the broadcast data packet to obtain the broadcast data. Specifically, a detailed description of the broadcast data packet transmission by the converged communication platform 24 or the broadcast multicast service center 17, and the reception and parsing of the broadcast data packet by terminal 100, can be found in the above embodiments, and will not be repeated here.

[0297] like Figure 12E As shown, after parsing the broadcast data, the terminal 100 can display a broadcast message box 1441 and a reception time information 1442. The broadcast message box 1441 can be used to display the broadcast data received by the terminal 100. The reception time information 1442 can be used to indicate the reception time of the broadcast data displayed in the broadcast message box 1441. Here, the value of the reception time information 1442 is "08:20".

[0298] Understandably, when terminal 100 receives input from the user returning to the broadcast message interface 1421, it can display the broadcast message interface 1421 in response to this input. The broadcast time bar 1423 in the broadcast message interface 1421 displays the updated next broadcast time; here, the content displayed in the broadcast time bar 1423 can be "Next broadcast time: 08:40". In this way, terminal 100 can prompt the user to receive broadcast data packets by displaying the next broadcast time.

[0299] Optionally, terminal 100 can display the default broadcast time, that is, display the above. Figure 11 The default broadcast time T1 is shown. In this way, the user can determine the time range for receiving broadcast data packets by using the displayed default broadcast time, and receive broadcast data packets within the default broadcast time starting from the default broadcast time.

[0300] In one possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can add new broadcast times within the default broadcast cycle, and send a first data packet including broadcast data to at least one terminal within the time period indicated by the new broadcast time. Terminal devices expecting to receive the broadcast data will receive the data during both the default broadcast time and the new broadcast time.

[0301] For example, such as Figure 13As shown, the default broadcast cycle can also include a default broadcast time, a new broadcast time, and a new broadcast interval. The new broadcast time is the period outside the default broadcast time within the default broadcast cycle when the converged communication platform 24 or the broadcast multicast service center 17 sends broadcast data packets. The new broadcast time is a period starting from the new broadcast time. For example, the converged communication platform 24 or the broadcast multicast service center 17 sends a broadcast data packet at the default broadcast time t1 of the first default broadcast cycle, and then sends another broadcast data packet at the new broadcast time t3 after a new broadcast interval T3. Then, after a new broadcast interval T4, the second default broadcast cycle begins. The new broadcast interval T4 and the new broadcast interval T5 can be the same or different.

[0302] In another possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can extend the default broadcast time, increasing the time for sending broadcast data. For example, the converged communication platform 24 or the broadcast multicast service center 17 can extend the default broadcast time of the first default broadcast cycle from T1 to T1', and shorten the default broadcast interval T2 to T2'. Wherein, T1'+T2'=T1+T2.

[0303] In some application scenarios, when the converged communication platform 24 or the broadcast multicast service center 17 receives emergency broadcast data from other servers, such as a disaster warning message sent by the emergency rescue platform 26, the converged communication platform 24 or the broadcast multicast service center 17 can add a new broadcast time to the default broadcast cycle and send the emergency broadcast data to at least one terminal during the new broadcast time. Alternatively, it can extend the broadcast time within each cycle and send the emergency broadcast data to at least one terminal during the extended broadcast time.

[0304] In other application scenarios, when the converged communication platform 24 or the broadcast multicast service center 17 receives broadcast data sent by other servers (e.g., server 15), it can also receive broadcast time information sent by those other servers. The broadcast time information can be used to instruct the converged communication platform 24 or the broadcast multicast service center 17 to send the broadcast data at the time indicated by the broadcast time information. Here, the time indicated by the broadcast time information is either the newly added broadcast moment of the newly added broadcast time or the extended broadcast time length.

[0305] Furthermore, to enable terminal 100 to receive the first data packet at the newly added broadcast time, the converged communication platform 24 or the broadcast multicast service center 17 can add a broadcast time indication field to the first data packet. This field can indicate the transmission time of the next or subsequent first data packet, or the transmission time range for the next or subsequent first data packet. Specifically, the transmission time of the next or subsequent first data packet is the next newly added broadcast time or the default broadcast time. The transmission time range for the next or subsequent first data packet is the default broadcast time within the current broadcast cycle, or the newly added broadcast time within the current default broadcast cycle, or the default broadcast time within the next default broadcast cycle.

[0306] like Figure 14 As shown, the converged communication platform 24 or the broadcast multicast service center 17 can obtain a first data packet based on the received broadcast data. The first data packet includes header information. The header information includes a broadcast time indication field. The broadcast time indication field can be used to indicate the transmission time of the next or subsequent first data packet, that is, the next newly added broadcast time or the default broadcast time.

[0307] For example, the broadcast time indicator field can be 2 bits long. When the broadcast time indicator field is 00, it indicates that the next broadcast time is 1 minute after the previous broadcast start time. When the broadcast time indicator field is 01, it indicates that the next broadcast time is 5 minutes after the previous broadcast start time. When the broadcast time indicator field is 10, it indicates that the next broadcast time is 10 minutes after the previous broadcast start time. When the broadcast time indicator field is 11, it indicates that the next broadcast time is 20 minutes after the previous broadcast start time. A 20-minute interval can be used as the default interval. By adjusting the broadcast time indicator field, new broadcast times can be added, and the broadcast time can be adjusted. The broadcast start time includes both the default broadcast time and newly added broadcast times.

[0308] For example, the broadcast time indicator field can be 2 bits long. When the broadcast time indicator field is 00, it indicates that the next broadcast time is 30 seconds. When the broadcast time indicator field is 01, it indicates that the next broadcast time is 1 minute. When the broadcast time indicator field is 10, it indicates that the next broadcast time is 2 minutes. When the broadcast time indicator field is 11, it indicates that the next broadcast time is 4 minutes. 30 seconds can be set as the default, and the broadcast time can be extended by adjusting the broadcast time indicator field.

[0309] In one possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can adjust the new broadcast time for sending broadcast data packets based on the amount of broadcast data or the current time. For example, when the size of the broadcast data received by the converged communication platform 24 or the broadcast multicast service center 17 is greater than a first threshold (e.g., 1kB), broadcast data packets can be sent every minute, in which case the value of the broadcast time indicator field can be 00. As another example, the converged communication platform 24 or the broadcast multicast service center 17 can divide a day into multiple time periods, for example, the first time period is 9:00-12:00 and 14:00-21:00, during which broadcast data packets can be sent every minute; the second time period is 7:00-9:00 and 21:00-22:00, during which broadcast data packets can be sent every 5 minutes, and so on.

[0310] In one possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can determine the time to send the next broadcast data packet based on the broadcast time sent by other servers. Specifically, when the converged communication platform 24 or the broadcast multicast service center 17 receives broadcast data 1 from other servers with a broadcast time of N minutes later, and when the converged communication platform 24 or the broadcast multicast service center 17 has already sent broadcast data packet 1 indicating a transmission time of less than N minutes for broadcast data packet 2 to terminal 100, the converged communication platform 24 or the broadcast multicast service center 17 can set the value of the broadcast time indication field in broadcast data packet 2 to indicate that broadcast data packet 3 will be sent less than N minutes later, and so on, until the next broadcast data packet indicated by the broadcast data packet sent by the converged communication platform 24 or the broadcast multicast service center 17 has a transmission time of N minutes after receiving broadcast data 1. When the converged communication platform 24 or the broadcast multicast service center 17 receives broadcast data 1 from another server with a broadcast time of N minutes later, and when the converged communication platform 24 or the broadcast multicast service center 17 has already sent broadcast data packet 1 indicating a broadcast data packet 2 with a transmission time greater than or equal to N minutes to the terminal 100, the converged communication platform 24 or the broadcast multicast service center 17 can send broadcast data 1 and broadcast data 2 from broadcast data packet 2 together to the terminal 100. When the converged communication platform 24 or the broadcast multicast service center 17 has not yet sent broadcast data packet 1 indicating the transmission time of broadcast data packet 2 to the terminal 100, the converged communication platform 24 or the broadcast multicast service center 17 can determine the value of the broadcast time indication field of broadcast data packet 1 to a value indicating that the transmission time of broadcast data packet 2 is P minutes later. Here, P is the time that the converged communication platform 24 or the broadcast multicast service center 17 can set for the next broadcast data packet transmission time to be closest to N minutes.

[0311] Optionally, the length of the broadcast time indicator field can be the logarithm of the default broadcast period length (in minutes) rounded up. This allows the broadcast time indicator field to indicate any minute within the broadcast period. For example, when the default broadcast period length is 8 minutes, the broadcast time indicator field is 3 bits long. A broadcast time indicator field of 000 indicates that the next broadcast time is 1 minute after the broadcast time of the previous data packet. A broadcast time indicator field of 001 indicates that the next broadcast time is 2 minutes after the broadcast time of the previous data packet, and so on.

[0312] In this way, the converged communication platform 24 or the broadcast multicast service center 17 can flexibly set the broadcast time. Furthermore, when the terminal 100 does not receive the broadcast data packet sent at the newly added broadcast time, it can also determine the sending time of the next broadcast data packet based on the data packet sent at the default broadcast time.

[0313] Optionally, the converged communication platform 24 or the broadcast multicast service center 17 may send a first data packet including broadcast data to at least one terminal, the first data packet including a broadcast time indication field for indicating the time of transmission of the next first data packet.

[0314] The following section presents a set of interface diagrams provided in the embodiments of this application.

[0315] After receiving a broadcast data packet from the converged communication platform 24 or the broadcast multicast service center 17, the terminal 100 can determine the time when the converged communication platform 24 or the broadcast multicast service center 17 will send the next broadcast data packet based on the value of the broadcast time indication field in the broadcast data packet. The terminal 100 can display the time when the converged communication platform 24 or the broadcast multicast service center 17 will send the next broadcast data packet. This can improve the success rate of the terminal 100 receiving broadcast data packets.

[0316] For example, terminal 100 receives data including, as shown in the example... Figure 12E When the broadcast data packet in the broadcast message box 1441 shown is received, the terminal 100 can determine, based on the value of the broadcast time indication field in the data packet, that the converged communication platform 24 or the broadcast multicast service center 17 will send the next broadcast data packet in 10 minutes.

[0317] When terminal 100 receives user's request Figure 12E When returning to the broadcast details interface 1431 as shown, the terminal 100 can display the following: Figure 15A The broadcast message interface 1451 shown is shown.

[0318] like Figure 15AAs shown, the broadcast message interface 1451 includes a broadcast source option 1452 and a broadcast time bar 1453. The broadcast time bar 1453 can be used to display the transmission time of the next broadcast data packet determined by the terminal 100, that is, the reception time of the next broadcast data packet that the terminal 100 can receive. The broadcast time displayed in the broadcast time bar 1453 can be obtained based on the broadcast time indication field, the default broadcast period, and the current time. For example, the terminal 100 can determine the transmission time of the next data packet based on the broadcast time indication field and display that transmission time on the broadcast time bar. When the terminal 100 has not received a data packet within the previous default broadcast period (for example, if the terminal 100 is on a satellite network after the default broadcast time, and the terminal 100 cannot determine the new broadcast time of the default broadcast period), the terminal 100 can obtain the next default broadcast time based on the default broadcast period and the current time and display it on the broadcast time bar. Here, terminal 100 has determined, based on the broadcast time indication field of the most recently received broadcast data packet, that the next broadcast data packet will be sent in 10 minutes. Terminal 100 can display the next broadcast time as "08:30" on the broadcast time bar 1453. The descriptions of the broadcast message interface 1451 and the broadcast source option 1452 can be found above. Figure 12C The embodiments shown are not described in detail here.

[0319] Terminal 100 can receive user input regarding broadcast source option 1452, and in response to that input, display as shown below. Figure 12E The broadcast details interface shown is 1431.

[0320] Subsequently, at the next broadcast data packet transmission time indicated by the broadcast time bar 1453, terminal 100 can receive the broadcast data packet sent by the converged communication platform 24 or the broadcast multicast service center 17, and parse the broadcast data packet to obtain the broadcast data. Specifically, a detailed description of the broadcast data packet transmission by the converged communication platform 24 or the broadcast multicast service center 17, and the reception and parsing of the broadcast data packet by terminal 100, can be found in the above embodiments, and will not be repeated here.

[0321] like Figure 15B As shown, after parsing the broadcast data, the terminal 100 can display a broadcast message box 1461 and a reception time information 1462. The broadcast message box 1461 can be used to display the broadcast data received by the terminal 100. The reception time information 1462 can be used to indicate the reception time of the broadcast data displayed in the broadcast message box 1461. Here, the value of the reception time information 1462 is "08:30".

[0322] In one possible implementation, the converged communication platform 24 or the broadcast multicast service center 17 can be configured with a modification period. Within a modification period, the time interval between the converged communication platform 24 or the broadcast multicast service center 17 sending broadcast data packets remains unchanged. Thus, when the terminal 100 receives any data packet, it can determine the broadcast time of the remaining data packets within that modification period based on the broadcast time indication field in the data packet. That is, the first data packet includes information indicating the transmission time of the next M first data packets.

[0323] For example, such as Figure 16 As shown, the modification period can be one or more default broadcast periods. Within a modification period, the time intervals between broadcast times (which may include default broadcast times and newly added broadcast times) are the same. For example, when a modification period includes two default broadcast periods, the converged communication platform 24 or the broadcast multicast service center 17 sends a broadcast data packet at the default broadcast time t1 of the first default broadcast period in the first modification period, and then sends a broadcast data packet at the newly added broadcast time t4 after an additional broadcast interval T5. After another newly added broadcast interval T5, the second default broadcast period begins. The broadcast intervals of the two default broadcast periods in the modification period are the same, both being T5. In the second modification period, the broadcast intervals of the two default broadcast periods are the same, both being T6. It should be noted that the broadcast intervals of the first and second modification periods are independent and can be different (e.g., Figure 16 Alternatively, the same principle can be applied. By keeping the broadcast pattern (fixed broadcast time interval) unchanged during the modification period, the terminal can determine the broadcast pattern within the current modification period as soon as it receives a broadcast data packet with time information within a modification period, thus enabling it to receive broadcast data packets quickly, accurately, and energy-efficiently.

[0324] In one possible implementation, terminal 100 can send a broadcast time request to the converged communication platform 24 or the broadcast multicast service center 17. The broadcast time request can instruct the converged communication platform 24 or the broadcast multicast service center 17 to send a broadcast time response to terminal 100. The broadcast time response can include the transmission time information of the first data packet, which can indicate the time when the converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet. In this way, terminal 100 can receive the first data packet within the time period indicated by the broadcast time response, improving the reception success rate.

[0325] In some embodiments, terminal 100 may generate a broadcast time request. This broadcast time request includes frame header information. The frame header information may include, but is not limited to, a frame type indicator field. The frame type indicator field can be used to identify the broadcast time request at the SLC layer. After receiving the data packet sent by terminal 100, ground center station 19 can determine at the SLC layer, based on the frame type indicator field, that the data packet includes a broadcast time request. Ground center station 19 can send the broadcast time request to converged communication platform 24 or broadcast multicast service center 17. After receiving the broadcast time request, converged communication platform 24 or broadcast multicast service center 17 can generate a broadcast time response based on the time the broadcast data packet was sent, and send the broadcast time response to terminal 100 through ground center station 19.

[0326] like Figure 17 As shown, the process of terminal 100 querying the sending time of the first data packet includes the following steps:

[0327] S1701. Terminal 100 sends a broadcast time request to ground center station 19.

[0328] Terminal 100 can use a specific string (e.g., 0) as raw data and encapsulate it to obtain a broadcast time request. It can also include multicast source ID information or broadcast source ID information as raw data and encapsulate it to obtain a broadcast time request. At the AP layer, this specific string, multicast source ID, or broadcast source ID can be used to indicate the transmission time when the converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to terminal 100. Alternatively, terminal 100 may not need to encapsulate data at the AP layer, or may only carry an authentication code at the AP layer, the authentication code being generated based on the agreed data content.

[0329] The broadcast time request also includes a frame type (or SLCPDU type) indication field to indicate that the data packet is for querying the transmission time of the first data packet. This frame type field can be used to identify the type of user frame. For example, the frame type field can be 3 bits long. When the frame type field value is 000, it can identify the current user frame as a message information PDU (general data frame). A message information PDU (general data frame) can be used to transmit unicast data and can also be used to request satellite messages sent to terminal 100 by other terminals or servers from the converged communication platform 24 or the broadcast multicast service center 17. When the frame type field value is 001, it can identify the current user frame as an ACK report PDU (ACK frame). When the frame type field value is 010, it can identify the current user frame as an application layer acknowledgment PDU (acknowledgment frame). When the frame type field value is 011, it can identify the current user frame as a location reporting PDU (location reporting frame). When the frame type field value is 100, it can identify the current user frame as an emergency rescue PDU (emergency rescue frame). Currently, broadcast time request PDUs can be identified using fields different from those in existing frame type indicators. For example, when the frame type field is 101, it can indicate that the current user frame is a broadcast time request frame, which can be used to query the broadcast / multicast service center 17 or the converged communication platform 24 for the transmission time of broadcast data packets. Alternatively, existing frame type indicator fields can be used to indicate the destination to which the data packet needs to be sent. For example, when the frame type field is 110, it can indicate that the data packet needs to be sent to the broadcast / multicast service center 17 instead of the converged communication platform 18.

[0330] The broadcast time request may also include user ID information, which indicates the terminal that sent the broadcast time request. The ground center station 19 can identify the requesting user based on the user ID information.

[0331] The broadcast time request may also include multicast source ID information or broadcast source ID information, or a bit map, to indicate whether terminal 100 requests multiple subscribed broadcast or multicast messages, for example, included in packets at the SLC layer.

[0332] In this application, terminal 100 can receive a user's input requesting the broadcast time of the first data packet, and in response to the input, generate and send a broadcast time request to ground center station 19. Alternatively, terminal 100 can also generate and send broadcast time requests to ground center station 19 at preset intervals (e.g., 30 minutes), which is not limited in this application.

[0333] Terminal 100 can forward the broadcast time request to ground center station 19 via satellite 21.

[0334] S1702. Ground center station 19 sends the broadcast time request to broadcast multicast service center 17 or converged communication platform 24.

[0335] Specifically, after receiving the data packet sent by the terminal 100, if the frame type of the data packet is a broadcast time request frame, the ground center station 19 can parse the data packet and send a message to the broadcast multicast service center 17 or the converged communication platform 24.

[0336] In one possible implementation, when the broadcast multicast service center 17 carries broadcast multicast services, after the ground center station 19 receives a data packet sent by the terminal 100, if the frame type of the data packet is a broadcast time request frame, the ground center station 19 can send a broadcast time information request to the broadcast multicast service center 17 according to the frame type of the data packet. The request content includes the broadcast source ID information or multicast source ID information requested by the terminal, used to request the broadcast multicast service center 17 to send broadcast time information for a specific broadcast source or multicast source. In another possible implementation, when the broadcast multicast service center 17 carries broadcast multicast services, after the ground center station 19 receives a data packet sent by the terminal 100, if the frame type of the data packet indicates that it is sent to the broadcast multicast service center 17, the ground center station 19 can send the data packet to the broadcast multicast service center 17 according to the frame type of the data packet. The data packet includes the broadcast source ID information or multicast source ID information requested by the terminal, used to request the broadcast multicast service center 17 to send broadcast time information for a specific broadcast source or multicast source.

[0337] In another possible implementation, when the converged communication platform 24 carries broadcast and multicast services, after the ground center station 19 receives the data packet sent by the terminal 100, if the frame type of the data packet is a broadcast time request frame, the ground center station 19 can send a broadcast time information request to the converged communication platform 24 according to the frame type of the data packet. The request content includes the broadcast source ID information or multicast source ID information requested by the terminal, which is used to request the converged communication platform 24 to send broadcast time information for a specific broadcast source or multicast source.

[0338] S1703. The converged communication platform 24 or the broadcast multicast service center 17 generates a broadcast time response, which includes the transmission time information of the first data packet.

[0339] After receiving a specific string used to query the transmission time of a broadcast data packet, or a query message sent by the ground center station 19, the converged communication platform 24 or the broadcast multicast service center 17 generates a broadcast time response. The broadcast time response includes the transmission time information of the first data packet sent by the converged communication platform 24 or the broadcast multicast service center 17. Specifically, the converged communication platform 24 or the broadcast multicast service center 17 can use the transmission time information of the first data packet (e.g., the start time of the first data packet's broadcast) as raw data and perform AP layer processing on this raw data. The processed AP layer data packet is then sent to the ground center station 19. A description of how the converged communication platform 24 or the broadcast multicast service center 17 obtains the AP layer data packet including the transmission time information of the first data packet can be found in [link to relevant documentation]. Figure 4B The embodiments shown are not described in detail here.

[0340] S1704. The converged communication platform 24 or the broadcast multicast service center 17 sends a broadcast time response to the ground center station 19.

[0341] Specifically, the converged communication platform 24 or the broadcast multicast service center 17 can send a data packet including the transmission time information of the first data packet to the ground center station 19. The ground center station 19 receives the transmission time information.

[0342] S1705. Ground center station 19 sends broadcast time response to terminal 100.

[0343] Specifically, after receiving a data packet containing the transmission time information of the first data packet from the converged communication platform 24 or the broadcast multicast service center 17, the ground center station 19 can obtain a broadcast response message to be sent to the terminal 100 based on the data packet. Furthermore, it can determine the frame type to be sent based on the obtained data packet.

[0344] If the frame is sent to the requesting user via unicast, a new frame type indicator can be used to specify the user's frame type, such as introducing a new frame type field. Alternatively, a generic data frame can be used. If the frame is sent to multiple users via broadcast or multicast, the user's frame type can be a multicast or broadcast frame. Frame type indication can be found in [link to documentation]. Figure 6B , Figure 7B , Figure 8BThe illustrated embodiment will not be described in detail here. The frame type indicator field of the user frame can be used to indicate the transmission time of the broadcast data packet included in the user frame. For example, the length of the frame type field can be 3 bits. When the value of the frame type field is 000, it can identify the current user frame as a general data frame. When the value of the frame type field is 001, it can identify the current user frame as an ACK frame. When the value of the frame type field is 010, it can identify the current user frame as an acknowledgment frame. When the value of the frame type field is 011, it can identify the current user frame as a broadcast frame. When the value of the frame type field is 100, it can identify the current user frame as a multicast frame. When the value of the frame type field is 101, it can identify the current user frame as a broadcast time response frame. The broadcast time response frame can be used to send the transmission time of the broadcast data packet to the terminal 100. The description of how the ground center station 19 obtains the broadcast time response can be found in [reference needed]. Figure 4B The embodiments shown are not described in detail here.

[0345] The ground center station 19 can determine the user ID information or transmission beam of the broadcast response sent by the ground center station 19 to the terminal 100 based on the user ID or receiving beam provided by the converged communication platform 24 or the broadcast multicast service center 17, or the broadcast time request information recorded by the ground center station 19.

[0346] For example, if the user ID sent in the broadcast time request in S1701 is 13100000000, then after the ground center station 19 obtains the broadcast time information from the converged communication platform 24 or the broadcast multicast service center 17, the broadcast time response message sent in S1705 carries the user ID 13100000000. Since this user frame is a unicast frame sent separately to the requesting user, its frame type field value is 00, indicating general data information.

[0347] For example, if the user ID sending the broadcast time request in S1701 is 13100000000, and the requested broadcast source information is broadcast source 110, then after the ground center station 19 obtains the broadcast time information from the converged communication platform 24 or the broadcast multicast service center 17, the broadcast time response message sent in S1705 carries the broadcast ID 110. Since this user frame is a broadcast frame sent to the requesting user via broadcast, its frame type field value can be 11, indicating a multicast broadcast message. Other terminals that did not send a request message can also quickly learn the broadcast mode information of the current broadcast source 110 when they receive this message.

[0348] For example, if the user sending the broadcast time request in S1701 sends the request information through beam 1, then after the ground center station 19 obtains the broadcast time information from the converged communication platform 24 or the broadcast multicast service center 17, the broadcast time response message in S1705 should be sent through beam 1.

[0349] Since the converged communication platform 24 or the broadcast multicast service center may send broadcast time information outside of broadcast times when the terminal requests it, in order to enable the terminal to obtain the broadcast time information more quickly, the terminal 100 can guide the user to receive broadcast information once when the user triggers the broadcast reception. If it is not received, the user is then instructed to receive it within the default broadcast time or within the requested broadcast time information.

[0350] Optionally, after receiving the broadcast time request sent by the terminal 100, the ground center station 19 can obtain the transmission time information of the first data packet from the converged communication platform 24 or the broadcast multicast service center 17, encapsulate the information as an MDCPSDU to obtain outbound data, and send the outbound data to the terminal 100.

[0351] It should be noted that the ground center station 19 can send the transmission time information of the first data packet to the terminal 100 as broadcast data. The broadcast time response includes a broadcast ID field, which is used to indicate the broadcast source. In this way, other terminals besides terminal 100 can also receive this time information. Alternatively, the ground center station 19 can send the transmission time information of the first data packet to the terminal 100 as unicast data. The broadcast time response includes a user ID field, which is used to indicate the user source to the terminal 100.

[0352] S1706. Terminal 100 determines the transmission time of the first data packet based on the broadcast time response.

[0353] After receiving the data packet sent by the satellite network device 200, the terminal 100 can obtain the transmission time of the first data packet at the AP layer after determining that the data packet is a broadcast time response frame based on the frame type indication field at the SLC layer.

[0354] S1707. Terminal 100 displays the sending time of the first data packet.

[0355] Terminal 100 can display the transmission time of the first data packet received.

[0356] S1708. The converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to the terminal 100 at the time indicated by the sending time information.

[0357] Specifically, a detailed description of how the converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to the terminal 100 at the time indicated by the sending time information can be found in the above embodiments, and will not be repeated here.

[0358] S1709. Terminal 100 receives the first data packet during the transmission time.

[0359] Terminal 100 receives the first data packet at the time indicated by the broadcast time response. Specifically, the description of terminal 100 receiving the first data packet can be found in the above embodiment, and will not be repeated here.

[0360] In other embodiments, terminal 100 may generate a broadcast time request. This broadcast time request includes packet header information. The packet header information may include, but is not limited to, a broadcast time request indication field. The broadcast time request indication field can be used to identify the broadcast time request at the AP layer. After receiving the broadcast time request, the converged communication platform 24 can determine at the AP layer the transmission time of the data packet sent by terminal 100 for querying the first data packet. The converged communication platform 24 can generate a broadcast time response based on the time the broadcast data packet was sent and send the broadcast time response to terminal 100 via ground center station 19.

[0361] In other embodiments, terminal 100 can generate a broadcast time request. This broadcast time request includes header information. The header information may include, but is not limited to, a broadcast time request indication field. The broadcast time request indication field can be used to identify the broadcast time request at the AP layer. After receiving the data packet sent by terminal 100, the converged communication platform 18 can determine at the AP layer the transmission time of the data packet sent by terminal 100 for querying the first data packet. The converged communication platform 18 can send the broadcast time request to the broadcast multicast service center 17. The broadcast multicast service center 17 can generate a broadcast time response based on the time of sending the broadcast data packet and send the broadcast time response to terminal 100 through the ground center station 19.

[0362] like Figure 18 As shown, the process of terminal 100 querying the sending time of the first data packet includes the following steps:

[0363] S1801. Terminal 100 sends a broadcast time request to ground center station 19.

[0364] Terminal 100 can generate a data packet that includes a broadcast time request indication field, i.e., a broadcast time request. This broadcast time request indication field is located in the packet header information, and the value of the broadcast time request indication field is determined by terminal 100 at the AP layer.

[0365] The broadcast time request indication field can be used to indicate whether the broadcast / multicast service center 17 should send the first data packet to the terminal 100 at the specified time. For example, the length of the broadcast time request indication field can be 1 bit. When the value of the broadcast time request indication field is 0, it indicates that the terminal 100 does not query the sending time of the first data packet. When the value of the broadcast time request indication field is 1, it can be used to indicate the sending time of the first data packet from the broadcast / multicast service center 17 to the terminal 100.

[0366] In this application, terminal 100 can receive a user's input requesting the broadcast time of the first data packet, and in response to the input, generate and send a broadcast time request to ground center station 19. Alternatively, terminal 100 can also generate and send broadcast time requests to ground center station 19 at preset intervals (e.g., 30 minutes), which is not limited in this application.

[0367] Terminal 100 can relay the broadcast time request to ground center station 19 via satellite 21.

[0368] S1802. Ground center station 19 sends the broadcast time request to converged communication platform 18.

[0369] Specifically, after receiving the data packet sent by the terminal 100, the ground center station 19 processes it through the PHY layer, SLC layer and MDCP layer before uploading it to the converged communication platform 18.

[0370] S1803. The converged communication platform 18 sends the broadcast time request to the broadcast multicast service center 17.

[0371] The converged communication platform 18 can determine whether to send the broadcast time request to the broadcast multicast service center 17 based on the broadcast time request indication field in the broadcast time request. When the converged communication platform 18 determines that the terminal 100 is querying the sending time of the first data packet based on the broadcast time request indication field in the broadcast time request, it sends the broadcast time request to the broadcast multicast service center 17.

[0372] Optionally, when the converged communication platform 18 receives the broadcast time request sent by the terminal 100 and determines the sending time of the first data packet from the broadcast multicast service center 17 based on the broadcast time request indication field in the broadcast time request, it can encapsulate the first data packet into an AP layer data packet and send the data packet to the terminal 100.

[0373] S1804. Broadcast multicast service center 17 generates a broadcast time response including the transmission time information of the first data packet.

[0374] After receiving a broadcast time request, the broadcast / multicast service center 17 can generate a broadcast time response, which includes the transmission time information of the first data packet. The broadcast time response also includes a broadcast time response indication field. This field indicates that the data packet generated by the broadcast / multicast service center 17 includes the transmission time information of the first data packet. For example, the length of the broadcast time response indication field can be 1 bit. When the value of the broadcast time response indication field is 0, it indicates that the data packet does not include the transmission time of the first data packet. When the value of the broadcast time response indication field is 1, it indicates that the data packet includes the transmission time of the first data packet.

[0375] Specifically, the broadcast multicast service center 17 can determine whether to generate a broadcast time response based on the broadcast time request indication field in the broadcast time request. When the broadcast multicast service center 17 determines that the terminal 100 is querying the transmission time of the first data packet based on the broadcast time request indication field in the broadcast time request, it generates a broadcast time response. Specifically, the broadcast multicast service center 17 can use the transmission time information of the first data packet as raw data and perform AP layer processing on this raw data. The processed AP layer data packet is then sent to the converged communication platform 18. A description of how the broadcast multicast service center 17 obtains the AP layer data packet including the transmission time information of the first data packet can be found in [reference needed]. Figure 4B The embodiments shown are not described in detail here.

[0376] S1805. The broadcast multicast service center 17 sends a broadcast time response to the converged communication platform 18.

[0377] S1806. The converged communication platform 18 sends a broadcast time response to the ground center station 19.

[0378] After receiving the broadcast time response, the converged communication platform 18 relays it to the ground center station 19.

[0379] S1807. Ground center station 19 sends broadcast time response to terminal 100.

[0380] Specifically, after receiving the data packet containing the transmission time information of the first data packet sent by the converged communication platform 18, the ground center station 19 can obtain the outbound data based on the data packet and send the outbound data to the terminal 100. A description of how the terminal 100 obtains the outbound data can be found in [link to relevant documentation]. Figure 4B The illustrated embodiment and S1705 will not be described again here.

[0381] It should be noted that the ground center station 19 can send the transmission time information of the first data packet to the terminal 100 as broadcast data. The broadcast time response includes a broadcast ID field, which is used to indicate the broadcast source. In this way, other terminals besides terminal 100 can also receive this time information. Alternatively, the ground center station 19 can send the transmission time information of the first data packet to the terminal 100 as unicast data. The broadcast time response includes a user ID field, which is used to indicate the user source to the terminal 100.

[0382] S1808. Terminal 100 determines the transmission time of the first data packet based on the broadcast time response.

[0383] After receiving the data packet sent by the satellite network device 200, the terminal 100 can obtain the transmission time of the first data packet at the AP layer after determining that the data packet includes the transmission time of the first data packet based on the broadcast time response indication field.

[0384] S1809. Terminal 100 displays the sending time of the first data packet.

[0385] Terminal 100 can display the transmission time of the first data packet received.

[0386] S1810. The converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to the terminal 100 at the time indicated by the sending time information.

[0387] Specifically, a detailed description of how the converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to the terminal 100 at the time indicated by the sending time information can be found in the above embodiments, and will not be repeated here.

[0388] S1811. Terminal 100 receives the first data packet during the transmission time.

[0389] Terminal 100 receives the first data packet at the time indicated by the broadcast time response. Specifically, the description of terminal 100 receiving the first data packet can be found in the above embodiment, and will not be repeated here.

[0390] In one possible implementation, terminal 100 can receive user input for a query control and, in response to the input, send a broadcast time request to the converged communication platform 24 or the broadcast multicast service center 17. Upon receiving the broadcast time request, the converged communication platform 24 or the broadcast multicast service center 17 can send a broadcast time response to terminal 100. After receiving the broadcast time response, terminal 100 can display the transmission time of the first data packet.

[0391] The following section presents a set of interface diagrams provided in the embodiments of this application.

[0392] For example, terminal 100 can receive user input for communication application icon 1403, and in response to the input, display as shown below. Figure 19A The communication application interface 1471 shown is included. The communication application interface 1471 may include, but is not limited to, a query control 1474. The query control 1474 can be used to trigger the terminal 100 to send a broadcast time request to the converged communication platform 24 or the broadcast / multicast service center 17. The communication application interface 1471 may also include a broadcast time bar 1473 and a broadcast source option 1472. A detailed description of the terminal 100 sending a broadcast time request to the converged communication platform 24 or the broadcast / multicast service center 17 can be found in... Figures 17-18 For a detailed description of the communication application interface 1471 in the illustrated embodiment, please refer to [link / reference needed]. Figure 12B The illustrated embodiment will not be described in detail here. Here, the current time displayed on terminal 100 is 08:10, and the next broadcast time displayed in the broadcast time bar 1473 of terminal 100 is "08:20".

[0393] Terminal 100 can receive user input for query control 1474, and in response to the input, display as shown below. Figure 19B The broadcast message interface shown is 1471.

[0394] like Figure 19B As shown, after the terminal 100 receives the broadcast time response from the converged communication platform 24 or the broadcast multicast service center 17, it can display the updated broadcast time bar 1473. The content displayed in the broadcast time bar 1473 is the updated next broadcast time. Here, the content displayed in the broadcast time bar 1473 can be "Next broadcast time: 08:15". In this way, the terminal 100 can prompt the user to receive broadcast data packets by displaying the next broadcast time.

[0395] Subsequently, at the next broadcast data packet transmission time indicated by the broadcast time bar 1473, terminal 100 can receive the broadcast data packet sent by the converged communication platform 24 or the broadcast multicast service center 17, and parse the broadcast data packet to obtain the broadcast data. Specifically, a detailed description of the broadcast data packet transmission by the converged communication platform 24 or the broadcast multicast service center 17, and the reception and parsing of the broadcast data packet by terminal 100, can be found in the above embodiments, and will not be repeated here.

[0396] Subsequently, after receiving user input regarding broadcast source option 1422, terminal 100 can respond to that input by displaying, as shown below. Figure 19C The broadcast details interface shown is 1491.

[0397] like Figure 19CAs shown, after parsing the broadcast data, the terminal 100 can display a broadcast message box 1492 and a reception time information 1493. The broadcast message box 1492 can be used to display the broadcast data received by the terminal 100. The reception time information 1493 can be used to indicate the reception time of the broadcast data displayed in the broadcast message box 1492. Here, the value of the reception time information 1493 is "08:15".

[0398] It should be noted that the terminal 100 can display the sending time of the first data packet not only in the form of a broadcast time bar, but also through pop-ups, SMS messages, etc., and this application does not limit this.

[0399] In one possible implementation, terminal 100 receives user input for a query control (e.g., Figure 19A The time of sending the next broadcast data packet, i.e., the time of receiving the next broadcast data packet, is displayed only after the input of the query control 1474 shown. This time can be obtained through negotiation between the terminal 100 and the satellite network device 200, or it can be determined by the satellite network device 200 based on broadcast time information sent by other servers (e.g., server 15), the amount of broadcast data received, etc.

[0400] In one possible implementation, after parsing the first data packet, terminal 100 can generate receipt information based on the result of parsing the first data packet and send the receipt information to the converged communication platform 24 or the broadcast multicast service center 17. In this way, the converged communication platform 24 or the broadcast multicast service center 17 can determine the result of terminal 100 parsing the first data packet based on the receipt information.

[0401] Furthermore, when the receipt information is used to indicate that the terminal 100 failed to parse the first data packet, the converged communication platform 24 or the broadcast multicast service center 17 can resend the first data packet to at least one terminal.

[0402] In some embodiments, terminal 100 may generate receipt information. This receipt information includes frame header information. The frame header information may include, but is not limited to, a frame type indicator field. The frame type indicator field can be used to identify the receipt information at the SLC layer. After receiving the data packet sent by terminal 100, ground center station 19 can determine at the SLC layer, based on the frame type indicator field, that the data packet includes receipt information. Ground center station 19 can send the receipt information to converged communication platform 24 or broadcast multicast service center 17. After receiving the receipt information, converged communication platform 24 or broadcast multicast service center 17 can determine the result of terminal 100 parsing the first data packet based on the receipt information.

[0403] like Figure 20As shown, the steps for terminal 100 to send receipt information include the following:

[0404] S2001. The converged communication platform 24 or the broadcast multicast service center 17 sends the first data packet to the ground center station 19.

[0405] S2002. Ground center station 19 sends a second data packet to terminal 100.

[0406] S2003. Terminal 100 obtains the first data packet based on the second data packet.

[0407] For a detailed description of steps S2001-S2003, please refer to the above embodiments, and they will not be repeated here.

[0408] S2004. Terminal 100 parses the first data packet and generates a receipt based on the result of parsing the first data packet.

[0409] For example, the receipt information may include an error code. The error code can be 1 bit long. When the error code value is 0, it indicates that terminal 100 failed to parse and broadcast the data packet. When the error code value is 1, it indicates that terminal 100 successfully parsed and broadcast the data packet. It should be noted that the error code values ​​and their meanings here are for illustrative purposes only.

[0410] For example, the error code length can be 4 bits. An error code value of 0000 indicates that terminal 100 successfully parsed and broadcast the data packet. An error code value of 0001 indicates that terminal 100 failed to parse and broadcast the data packet, and the reason for the failure is a decryption error. An error code value of 0010 indicates that terminal 100 failed to parse and broadcast the data packet, and the reason for the failure is a decoding error. And so on.

[0411] It should be noted that if terminal 100 cannot decrypt the encrypted data to obtain the compressed data, terminal 100 can determine that the result of parsing the broadcast data packet is a decryption error. If terminal 100 cannot decompress and decode the compressed data to obtain the original data, terminal 100 can determine that the result of parsing the broadcast data packet is a decoding error. If terminal 100 successfully parses the broadcast data packet to obtain the original data, terminal 100 determines that the result of parsing the broadcast data packet is a successful parsing.

[0412] The receipt information includes a frame type indicator field, which can be used to indicate that the receipt information includes the result of the terminal 100 parsing the first data packet. For example, this frame type field can be used to identify the type of user frame. For example, the length of the frame type field can be 2 bits. When the value of the frame type field is 00, it can identify the current user frame as a general data frame. When the value of the frame type field is 01, it can identify the current user frame as an ACK frame. When the value of the frame type field is 10, it can identify the current user frame as a receipt frame. When the value of the frame type field is 11, it can identify the current user frame as a broadcast receipt frame. The broadcast receipt frame can be used to transmit the result of the terminal 100 parsing the broadcast data packet.

[0413] Alternatively, the frame type indicator field is used to indicate that the acknowledgment information includes the result of the terminal 100 parsing the data packets sent by the satellite network device 200. For example, this frame type field can be used to identify the type of user frame. For example, the frame type field can be 2 bits long. When the value of the frame type field is 00, it can indicate that the current user frame is a general data frame. When the value of the frame type field is 01, it can indicate that the current user frame is an ACK frame. When the value of the frame type field is 10, it can indicate that the current user frame is an acknowledgment frame. The acknowledgment frame can be used to transmit the result of the terminal 100 parsing the data packets. In order to determine at the SLC layer whether the acknowledgment information is used to indicate the parsing result of broadcast data packets or unicast data packets, the acknowledgment frame also includes a broadcast indicator field. The broadcast indicator field can be used to identify whether the acknowledgment frame is an acknowledgment frame for broadcast data packets or an acknowledgment frame for unicast data packets.

[0414] Optionally, the receipt information may also include an identifier for terminal 100. For example, the receipt information may include a user ID field, which can be used to identify terminal 100; for example, the value of the user ID field could be the mobile phone number of terminal 100. The user ID field can be located in the packet header information of the AP layer or in the frame header information of the SLC layer. In this way, the converged communication platform 24 or the broadcast multicast service center 17 can record information about terminals 100 that have not received the correct data. Furthermore, if retransmission is supported, only the first data packet can be retransmitted to terminal 100, reducing retransmission overhead.

[0415] S2005. Terminal 100 sends a receipt to ground center station 19.

[0416] Terminal 100 sends a receipt to ground control station 19 via satellite 21.

[0417] S2006. Ground center station 19 determines that the receipt information is the receipt information of the first data packet.

[0418] Ground center station 19 can determine that the acknowledgment information is the acknowledgment information of the first data packet based on the frame type indication field. Alternatively, ground center station 19 can determine that the acknowledgment information is the acknowledgment information of the first data packet based on the frame type indication field and the broadcast indication field.

[0419] S2007. Ground center station 19 sends a receipt to converged communication platform 24 or broadcast multicast service center 17.

[0420] Ground center station 19 can send the receipt information to converged communication platform 24 or broadcast multicast service center 17.

[0421] Optionally, when the frame header information of the receipt information includes a user ID field, the ground center station 19 can send the user ID and the receipt information together to the converged communication platform 24 or the broadcast multicast service center 17.

[0422] In one possible implementation, when the ground center station 19 obtains the result of the terminal 100 parsing the first data packet from the user frame based on the frame type field in the frame header information, the ground center station 19 can upload the error code in the user frame to the converged communication platform 24 or the broadcast multicast service center 17 through the inter-layer interface at the SLC layer. The converged communication platform 24 or the broadcast multicast service center 17 can obtain the result of the terminal 100 parsing the first data packet based on the error code in the user information.

[0423] Furthermore, the converged communication platform 24 or the broadcast / multicast service center 17 can perform corresponding operations based on different results. For example, after receiving the receipt information, the converged communication platform 24 or the broadcast / multicast service center 17 can also perform corresponding operations based on the error code in the receipt information. If the error code indicates that the terminal 100 successfully parses the broadcast data packet, the converged communication platform 24 or the broadcast / multicast service center 17 can end the transmission operation. If the error code indicates that the terminal 100 fails to parse the broadcast data packet and the reason for the failure is a decryption error, when the broadcast source is a broadcast source, the converged communication platform 24 or the broadcast / multicast service center 17 can determine that the reason for the terminal 100's decryption error is that the key information of the converged communication platform 24 or the broadcast / multicast service center 17 is different from the key information of the terminal 100. After receiving the receipt information, the converged communication platform 24 or the broadcast / multicast service center 17 can negotiate with the terminal 100 to update the key information (including the key and password book). When the broadcast source is a multicast source, the converged communication platform 24 or the broadcast multicast service center 17 can negotiate with the multicast source to obtain key information (including the key and password book) after receiving the acknowledgment information. After updating the key information, the converged communication platform 24 or the broadcast multicast service center 17 can use the updated key to encrypt the broadcast data, obtain the broadcast data packet, and resend the broadcast data packet to the terminal 100.

[0424] In other embodiments, terminal 100 may generate receipt information. This receipt information includes packet header information. The packet header information may include, but is not limited to, a broadcast receipt indication field. The broadcast receipt indication field can be used to identify the receipt information at the AP layer. After receiving the data packet sent by terminal 100, the converged communication platform 24 can determine at the AP layer that the data packet sent by terminal 100 includes receipt information. The converged communication platform 24 can determine the result of terminal 100 parsing the first data packet based on the receipt information.

[0425] In other embodiments, terminal 100 may generate receipt information. This receipt information includes packet header information. The packet header information may include, but is not limited to, a broadcast receipt indication field. The broadcast receipt indication field can be used to identify the receipt information at the AP layer. After receiving the data packet sent by terminal 100, the converged communication platform 18 can determine at the AP layer that the data packet sent by terminal 100 includes receipt information. The converged communication platform 18 can send the receipt to the broadcast multicast service center 17, and the broadcast multicast service center 17 can determine the result of terminal 100 parsing the first data packet based on the receipt information.

[0426] like Figure 21 As shown, the steps for terminal 100 to send receipt information include the following:

[0427] S2101. Broadcast multicast service center 17 sends the first data packet to ground center station 19.

[0428] S2102. Ground center station 19 sends a second data packet to terminal 100.

[0429] S2103. Terminal 100 obtains the first data packet based on the second data packet.

[0430] For a detailed description of steps S2101-S2103, please refer to the above embodiments, and they will not be repeated here.

[0431] S2104. Terminal 100 parses the first data packet and generates a receipt based on the result of parsing the first data packet.

[0432] The receipt information may include error codes. A detailed description of the error codes can be found in step S2004 above, and will not be repeated here.

[0433] The receipt information includes a broadcast receipt indication field. This field indicates whether the data packet contains the result of terminal 100 parsing the first data packet.

[0434] For example, the length of the broadcast receipt indication field can be 1 bit. When the value of the broadcast receipt indication field is 0, it indicates that the data packet does not include the result of terminal 100 parsing the first data packet. When the value of the broadcast receipt indication field is 1, it can be used to indicate that the data packet includes the result of terminal 100 parsing the first data packet.

[0435] Optionally, the receipt information may also include an identifier for terminal 100. For example, the receipt information may include a user ID field, which can be used to identify terminal 100; for example, the value of the user ID field could be the mobile phone number of terminal 100. The user ID field can be located in the packet header information of the AP layer or in the frame header information of the SLC layer. In this way, the converged communication platform 24 or the broadcast multicast service center 17 can record information about terminals 100 that have not received the correct data. Furthermore, if retransmission is supported, only the first data packet can be retransmitted to terminal 100, reducing retransmission overhead.

[0436] S2105. Terminal 100 sends a receipt to ground center station 19.

[0437] Terminal 100 sends a receipt to ground control station 19 via satellite 21.

[0438] S2106. Ground center station 19 sends a receipt to converged communication platform 18.

[0439] Specifically, after receiving the data packet sent by the terminal 100, the ground center station 19 processes it through the PHY layer, SLC layer and MDCP layer before uploading it to the converged communication platform 18.

[0440] Optionally, when the frame header information of the receipt information includes a user ID field, the ground center station 19 can send the user ID and the receipt information together to the converged communication platform 18.

[0441] S2107. The converged communication platform 18 determines that the receipt information is the receipt information of the first data packet.

[0442] The converged communication platform 18 can determine whether the receipt information includes the parsing result of the first data packet based on the value of the broadcast receipt indication field. When the converged communication platform 18 determines that the receipt information is the receipt information of the first data packet based on the value of the broadcast receipt indication field, it sends the receipt information to the broadcast multicast service center 17.

[0443] S2108. The converged communication platform 18 sends a receipt to the broadcast multicast service center 17.

[0444] The converged communication platform 18 can send receipt information to the broadcast multicast service center 17.

[0445] Optionally, when the converged communication platform 18 receives the user ID sent by the ground center station 19, it can send the user ID and receipt information together to the broadcast multicast service center 17.

[0446] Furthermore, the converged communication platform 24 or the broadcast multicast service center 17 can perform corresponding operations based on the result of the terminal 100 parsing the first data packet. For details, please refer to the above. Figure 20 The embodiments shown are not described in detail here.

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

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

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

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

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

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

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

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

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

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

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

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

[0459] The satellite communication module can be used to communicate with satellite network equipment. In the satellite communication system, the satellite communication module can communicate with satellite network equipment 200, and the satellite communication module can support data packet transmission between the two devices. For example, when the satellite communication system is a BeiDou communication system, and satellite network equipment 200 is a BeiDou network device, the satellite communication module can communicate with the BeiDou network device, and the satellite communication module can support the transmission of BeiDou short messages (i.e., data packets in the BeiDou communication system) between the two devices.

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

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

[0462] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. In some embodiments, terminal 100 may include one or N displays screens 194, where N is a positive integer greater than 1. Pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194. Touch sensor 180K, also called a "touch panel," is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194.

[0463] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the terminal 100. The terminal 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the terminal 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal 100 and cannot be separated from the terminal 100.

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

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

Claims

1. A transmission method, characterized in that, include: The first satellite network device receives the second message sent by the first terminal device; The first satellite network device sends a first message to the first terminal device based on the second message, the first message being used to indicate a specified time period; The first satellite network device generates a first data packet; wherein the first data packet includes broadcast data, and the broadcast data includes at least one of multicast data and broadcast data; The first satellite network device sends the first data packet to the second satellite network device within the specified time period; wherein, the first data packet is used by the second satellite network device to generate a second data packet and send it to at least one first terminal device, and the specified time period is obtained by negotiation between the first satellite network device and the at least one first terminal device, or the first satellite network device determines the specified time period based on the broadcast time information sent by the first network device.

2. The method according to claim 1, characterized in that, The method further includes: The first satellite network device sends information to the second satellite network device, instructing the second satellite network device to broadcast the first data packet to at least one first terminal device; Alternatively, the first satellite network device may send information to the second satellite network device instructing the second satellite network device to multicast the first data packet to the at least one first terminal device.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The first satellite network device sends one or more of the following information to the second satellite network device: the identifier of the first data packet, the broadcast time information of the first data packet, and the broadcast area information of the first data packet; wherein the identifier is used to indicate the service type of the first data packet.

4. The method according to claim 1, characterized in that, The first data packet includes information indicating the time for the first satellite network device to send the next M first data packets, where M is a positive integer.

5. The method according to any one of claims 1, 2, or 4, characterized in that, Sending the first message to the first terminal device specifically includes: The first satellite network device sends the first message to the first terminal device through the second satellite network device. The first message includes time information indicating the transmission time of the first data packet. Alternatively, the first satellite network device may send the time information or the first message to the third satellite network device, and the third satellite network device may send the first message to the first terminal device based on the time information.

6. The method according to claim 5, characterized in that, The first satellite network device receives a second message sent by the first terminal device, specifically including: The first satellite network device receives a second message sent by the first terminal device through the second satellite network device; wherein the second message is used to instruct the first satellite network device to send the first message to the first terminal device.

7. The method according to claim 5, characterized in that, The first satellite network device receives a second message sent by the first terminal device, specifically including: The first satellite network device receives a second message sent by the third satellite network device, the second message being used to instruct the first satellite network device to send the first message to the first terminal device.

8. The method according to any one of claims 1, 2, or 4, characterized in that, After the first satellite network device sends the first data packet to the second satellite network device, the method further includes: The first satellite network device receives information sent by the second satellite network device to indicate the reception status of the first terminal device for the first data packet.

9. The method according to any one of claims 1, 2, or 4, characterized in that, Before the first satellite network device sends the first data packet to the second satellite network device, the method further includes: The first satellite network device receives the content of the first data packet sent by the first network device; The first satellite network device receives one or more of the following information sent by the first network device: the identifier of the first data packet, broadcast time information, and broadcast area information.

10. A transmission method, characterized in that, include: The second satellite network device receives the second message sent by the first terminal device; The second satellite network device sends the second message to the first satellite network device, or the second satellite network device sends the second message to the third satellite network device, wherein the second message is used to obtain the first message; The second satellite network device receives a first message sent by the first satellite network device, or the second satellite network device receives the first message sent by the third satellite network device; wherein the first message is used to indicate a specified time period, the specified time period being negotiated by the first satellite network device and at least one first terminal device, or determined by broadcast time information sent by the first network device; The second satellite network device sends the first message to the first terminal device; The second satellite network device receives a first data packet sent by the first satellite network device; wherein the first data packet includes broadcast data, and the broadcast data includes at least one of multicast data and broadcast data; The second satellite network device generates a second data packet based on the first data packet; The second satellite network device sends the second data packet to at least one first terminal device within a specified time period.

11. The method according to claim 10, characterized in that, Before the second satellite network device generates the second data packet based on the first data packet, the method further includes: The second satellite network device receives information instructing it to generate a second broadcast-type data packet based on the first data packet; or, The second satellite network device receives information instructing the second satellite network device to generate a second data packet of the multicast type based on the first data packet.

12. The method according to claim 11, characterized in that, The second satellite network device generates a second data packet based on the first data packet, specifically including: The second satellite network device generates the second data packet based on the information indicating that the second satellite network device generates a broadcast-type second data packet based on the first data packet or the information indicating that the second satellite network device generates a multicast-type second data packet based on the first data packet.

13. The method according to any one of claims 11-12, characterized in that, The second satellite network device sends the second data packet to at least one first terminal device, specifically including: The second satellite network device transmits the second data packet to at least one first terminal device via the first beam; Alternatively, the second satellite network device sends the second data packet to at least one first terminal device, the second data packet including a first version number, the first version number being used to indicate whether the second data packet is a broadcast data packet or a multicast data packet; Alternatively, the second satellite network device may send the second data packet to at least one first terminal device. The second data packet includes first information and a second version number. The first information indicates that the second data packet is a broadcast data packet and / or a multicast data packet, and the second version number indicates that the second satellite network device generated the protocol version of the second data packet.

14. The method according to claim 13, characterized in that, When the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet further includes information for indicating the broadcast source of the second data packet; or, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet further includes information for indicating the multicast source of the second data packet.

15. The method according to claim 13, characterized in that, The method further includes: The second satellite network device receives one or more of the following information: the identifier of the first data packet, the broadcast time information of the first data packet, and the broadcast area information of the first data packet; wherein the identifier is used to indicate the service type of the first data packet. The second satellite network device determines the first beam, or the first version number, or the first information based on the information. Alternatively, the second satellite network device receives the information instructing the second satellite network device to generate a second data packet of broadcast type based on the first data packet, or the information instructing the second satellite network device to generate a second data packet of multicast type based on the first data packet; The second satellite network device determines the first beam, or determines the first version number, or determines the first information based on the information used to instruct the second satellite network device to generate a second data packet of broadcast type based on the first data packet or the information used to instruct the second satellite network device to generate a second data packet of multicast type based on the first data packet.

16. The method according to any one of claims 11-15, characterized in that, After the second satellite network device sends the second data packet to at least one first terminal device, the method further includes: The second satellite network device receives information sent by the first terminal device indicating the reception status of the first terminal device for the first data packet; The second satellite network device sends the information indicating the reception status of the first terminal device for the first data packet to the first satellite network device.

17. A transmission method, characterized in that, include: The first terminal device sends a second message to the second satellite network device, the second message being used to obtain the first message; The first terminal device receives a first message sent by the second satellite network device. The first message is used to indicate a specified time period, which is obtained by negotiation between the first satellite network device and at least one first terminal device, or determined by broadcast time information sent by the first network device. The first terminal device receives a second data packet sent by the second satellite network device within the specified time period; The first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet; The first terminal device obtains a first data packet based on the second data packet, and the first data packet is a data packet sent by the first satellite network device to the second satellite network device.

18. The method according to claim 17, characterized in that, The first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet, specifically including: The second data packet includes a first version number, and the first terminal device determines whether the second data packet is a broadcast data packet or a multicast data packet based on the first version number; Alternatively, the second data packet includes first information, and the first terminal device determines the second data packet as a broadcast data packet or a multicast data packet based on the first information; Alternatively, the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on the first beam that receives the second data packet.

19. The method according to claim 18, characterized in that, When the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet further includes information for indicating the broadcast source of the second data packet; or, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet further includes information for indicating the multicast source of the second data packet.

20. The method according to any one of claims 17-19, characterized in that, The first data packet includes information for instructing the first satellite network device on the reception time of the next M first data packets, where M is a positive integer.

21. The method according to claim 17, characterized in that, The first terminal device sends a second message to the second satellite network device, specifically including: The first terminal device receives an input from the user querying the sending time of the next first data packet; In response to the input, the first terminal device sends the second message to the second satellite network device.

22. The method according to claim 17 or 21, characterized in that, After the first terminal device receives the first message, the method further includes: The first terminal device displays the sending time of the first data packet.

23. The method according to any one of claims 17-19, characterized in that, The method further includes: The first terminal device receives an input from the user querying the sending time of the next first data packet; In response to the input, the first terminal device displays a transmission time for instructing the first satellite network device to send the first data packet, the transmission time being negotiated between the first satellite network device and at least one first terminal device.

24. A transmission method, characterized in that, include: The third satellite network device receives the second message sent by the second satellite network device; The third satellite network device sends the second message to the first satellite network device, the second message being used to instruct the first satellite network device to send the first message to the third satellite network device; or... The third satellite network device sends a first time information request to the first satellite network device based on the second message. The first time information request is used to instruct the first satellite network device to send the first time information to the third satellite network device. The third satellite network device receives the first message sent by the first satellite network device; or... The third satellite network device receives the first time information sent by the first satellite network device and generates the first message based on the first time information; The third satellite network device sends the first message to the first terminal device. The first message includes the first time information, which is used to indicate the transmission time of the first data packet. The first data packet includes broadcast data, which includes at least one of multicast data and broadcast data. The first message is used to instruct the first terminal device to receive the first data packet at the transmission time. The transmission time of the first data packet is negotiated by the first satellite network device and at least one first terminal device, or determined by the broadcast time information sent by the first network device.

25. A transmission method, characterized in that, include: The first device receives the second message sent by the first terminal device; Based on the second message, the first device sends a first message to the first terminal device. The first message is used to indicate a specified time period, which is obtained by negotiation between the first satellite network device and at least one first terminal device, or determined by broadcast time information sent by the first network device. The first device generates a second data packet; wherein the second data packet is a broadcast data packet or a multicast data packet, and the second data packet is used to generate the first data packet; The first device sends the second data packet to at least one first terminal device within a specified time period.

26. The method according to claim 25, characterized in that, The method further includes: The first device receives the content of the second data packet sent by the first network device; The first device receives one or more of the following information sent by the first network device: the identifier of the second data packet, broadcast time information, and broadcast area information.

27. The method according to claim 25 or 26, characterized in that, The first device sends the second data packet to at least one first terminal device within a specified time period, specifically including: The first device transmits the second data packet to at least one first terminal device via the first beam; Alternatively, the first device sends the second data packet to at least one first terminal device, the second data packet including a first version number, the first version number being used to indicate whether the second data packet is a broadcast data packet or a multicast data packet; Alternatively, the first device may send the second data packet to at least one first terminal device. The second data packet includes first information and a second version number. The first information indicates that the second data packet is a broadcast data packet and / or a multicast data packet, and the second version number indicates that the second satellite network device generates the protocol version of the second data packet.

28. The method according to claim 27, characterized in that, When the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet further includes information for indicating the broadcast source of the second data packet; or, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet further includes information for indicating the multicast source of the second data packet.

29. The method according to claim 27, characterized in that, The method further includes: The first device determines the first beam, or determines the first version number, or determines the first information based on the identifier of the second data packet.

30. The method according to claim 25 or 26, characterized in that, After the first device sends the second data packet to at least one first terminal device, the method further includes: The first device receives information sent by the first terminal device indicating the reception status of the second data packet by the first terminal device.

31. The method according to claim 25 or 26, characterized in that, The first device generates a second data packet, specifically including: The first device generates the first data packet at the application layer (AP). The first device sends the first data packet from the AP layer to the Message Data Convergence (MDCP) layer and / or the Satellite Link Control (SLC) layer; The first device processes the first data packet into the second data packet at the MDCP layer and / or the SLC layer.

32. The method according to claim 25 or 26, characterized in that, The second data packet includes a time for instructing the first device to send the next second data packet.

33. A transmission method, characterized in that, include: The first terminal device sends a second message to the first device, the second message being used to obtain the first message; The first terminal device receives a first message sent by the first device, the first message being used to indicate a specified time period, the specified time period being negotiated by the first satellite network device and at least one first terminal device, or being determined by broadcast time information sent by the first network device; The first terminal device receives a second data packet from the first device within the specified time period; The first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet; The first terminal device obtains the first data packet based on the second data packet.

34. The method according to claim 33, characterized in that, The first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet, specifically including: The second data packet includes a first version number, and the first terminal device determines whether the second data packet is a broadcast data packet or a multicast data packet based on the first version number; Alternatively, the second data packet includes first information, and the first terminal device determines the second data packet as a broadcast data packet or a multicast data packet based on the first information; Alternatively, the first terminal device determines that the second data packet is a broadcast data packet or a multicast data packet based on the first beam that receives the second data packet.

35. The method according to claim 34, characterized in that, When the first information is used to indicate that the second data packet is a broadcast data packet, the second data packet further includes information for indicating the broadcast source of the second data packet; or, when the first information is used to indicate that the second data packet is a multicast data packet, the second data packet further includes information for indicating the multicast source of the second data packet.

36. The method according to any one of claims 33-35, characterized in that, The first data packet includes information indicating the reception time for the first terminal device to receive the next first data packet sent by the first satellite network device.

37. The method according to claim 33, characterized in that, The first terminal device sends a second message to the first device, specifically including: The first terminal device receives an input from the user querying the sending time of the next second data packet; In response to the input, the first terminal device sends the second message to the first device.

38. The method according to claim 33 or 37, characterized in that, After the first terminal device receives the first message, the method further includes: The first terminal device displays the sending time of the first data packet.

39. The method according to any one of claims 33-35, characterized in that, The method further includes: The first terminal device receives an input from the user querying the sending time of the next second data packet; In response to the input, the first terminal device displays a time indicating when the first terminal device receives the second data packet, the time being negotiated between the first device and at least one first terminal device.

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

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

Images