A satellite terminal software system upgrade method

Abstract

The present invention discloses a method for upgrading a satellite terminal software system. A ground base station transmits new software version data via a specific multicast bearer, and a transmission identifier is provided for the ground base station that is transmitting the new version data. A satellite terminal that has completed network access at the ground base station that transmits the new version data receives the new version data via the specific multicast bearer and performs a software system upgrade. A satellite terminal that is unable to access the network selects a corresponding ground base station frequency to reside on based on the transmission identifier, so as to receive the new version data via the specific multicast bearer and complete the software system upgrade. This method solves the problem in traditional technologies that satellite terminals must access the network before software system upgrades can be performed. By transmitting the new version data via the specific multicast bearer, satellite terminals that are unable to access the network can also be upgraded online via the network.

Description

Technical Field

[0001] The present invention relates to the technical field of satellite communications, and in particular to a satellite terminal software system upgrading method. Background Art

[0002] Satellite networks are currently experiencing rapid development. The continuous application of new technologies, the continued advancement of satellite operational network construction, and the desire of satellite network operators to provide users with more value-added services are all likely to cause satellite operational networks to undergo a period of continuous evolution. Some satellite terminal users, particularly those in specific industries, may not use their devices for extended periods or even experience network access issues due to software issues. These factors all contribute to the irregular updating of legacy terminal software. Existing update technologies require satellite terminals to be online, and the update mechanism is tightly coupled with the protocol stack.

[0003] According to existing technologies, some users who have not turned on their devices for a long time may not be able to access the network due to certain reasons such as protocol compatibility issues. Such users will not be able to perform online software updates; the update mechanism and the protocol stack are tightly coupled, which does not conform to the software engineering design concept. Subsequent changes in requirements may lead to more aspects to be considered in protocol iteration, and may even cause compatibility issues between previous and subsequent versions, resulting in some users being unable to recognize the new upgrade protocol and unable to upgrade. Summary of the Invention

[0004] In view of this, the present invention provides a satellite terminal software system upgrade method, which can complete the satellite terminal software system upgrade without the satellite terminal interacting with a ground base station.

[0005] The specific technical solution adopted in the present invention is as follows:

[0006] A satellite terminal software system upgrade method, comprising:

[0007] The ground base station sends the new version data through a specific multicast bearer, and identifies the ground base station that is sending the new version data;

[0008] The satellite terminal that has completed network access at the ground base station that sends the new version data receives the new version data through the specific multicast bearer and performs the software system upgrade; the satellite terminal that cannot access the network selects the corresponding ground base station frequency to reside according to the sending identifier, so as to receive the new version data through the specific multicast bearer and complete the software system upgrade.

[0009] Furthermore, before the ground base station sends the new version data through the specific multicast bearer, the method further includes:

[0010] A specific multicast bearer is established, wherein the ground base station and the ground core network establish the specific multicast bearer according to default parameters, and the satellite terminal establishes the specific multicast bearer according to the default parameters of the ground core network.

[0011] Furthermore, when establishing the specific multicast bearer, a low scheduling priority is configured for the specific multicast bearer.

[0012] Furthermore, before the ground base station sends the new version data through the specific multicast bearer, the method further includes:

[0013] The version management server of the satellite routing terminal periodically sends new version data to the ground core network;

[0014] The terrestrial core network sends the new version data to the specific multicast bearer;

[0015] The ground base station receives the new version data from the specific multicast bearer.

[0016] Furthermore, the version management server periodically sends new version data to the ground core network, including:

[0017] The version service manager periodically sends the new version data to the terrestrial core network in a multicast manner;

[0018] Alternatively, the version service manager periodically sends the new version data to the terrestrial core network in a broadcast manner.

[0019] Furthermore, the ground base station sends the new version data through a specific multicast bearer, and identifies the ground base station that is sending the new version data, including:

[0020] The scheduling system of the ground base station sends the new version data in a specific multicast bearer of the air interface, and the ground base station completes the sending identification by notifying itself in a system message that it is sending the new version data.

[0021] Furthermore, before executing the software system upgrade, it is first determined whether the new version data is newer than the version data currently running on the satellite terminal. If so, the software system upgrade is executed; if not, the software system upgrade is not executed.

[0022] Beneficial effects:

[0023] (1) A method for upgrading a satellite terminal software system. The satellite terminal receives new version data via a specific multicast bearer and performs a software system upgrade. The satellite terminal does not need to interact with a ground base station. This solves the problem that in traditional technologies, a satellite terminal must be connected to the network to perform a software system upgrade. By transmitting the new version data via a specific multicast bearer, a satellite terminal that cannot be connected to the network can also perform an online upgrade.

[0024] (2) Configuring a low scheduling priority for a specific multicast bearer can ensure that other normal services are not affected while the software system is upgraded.

[0025] (3) The software system upgrade is completed by using specific multicast communication, which realizes the loose coupling between the upgrade mechanism and the air interface protocol stack during the upgrade process, so as to achieve the effect of not affecting the subsequent evolution of the air interface protocol stack. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a flow chart of a satellite terminal software system upgrading method of the present invention;

[0027] Figure 2 The present invention is a communication architecture diagram of a satellite terminal software system upgrade method. DETAILED DESCRIPTION

[0028] The present invention provides a method for upgrading a satellite terminal software system. A ground base station transmits new version data via a specific multicast bearer and identifies the ground base station that is transmitting the new version data. Satellite terminals that have completed network access at the ground base station that transmitted the version data receive the new version data via the specific multicast bearer and perform a software system upgrade. Satellite terminals that are unable to access the network select a corresponding ground base station frequency to reside on based on the transmission identifier, thereby receiving the new version data via the specific multicast bearer and completing the software system upgrade. This method solves the problem in conventional technologies that satellite terminals must be networked for software system upgrades. By transmitting the new version data via the specific multicast bearer, satellite terminals that are unable to access the network can also be upgraded online.

[0029] The present invention is described in detail below with reference to the accompanying drawings and embodiments.

[0030] An embodiment of the present invention provides a satellite terminal software system upgrade method, comprising:

[0031] Step S102: The ground base station sends the new version data via a specific multicast bearer, and identifies the ground base station that is sending the new version data.

[0032] Step S104: The satellite terminal that has completed network access at the ground base station that sends the new version data receives the new version data through a specific multicast bearer and performs a software system upgrade; the satellite terminal that cannot access the network selects the corresponding ground base station frequency to reside on according to the sending identifier, so as to receive the new version data through a specific multicast bearer and complete the software system upgrade.

[0033] In one specific embodiment, before step S102, the method further includes establishing a specific multicast bearer, wherein the ground base station and the ground core network establish the specific multicast bearer according to default parameters, and the satellite terminal establishes the specific multicast bearer according to the default parameters of the ground core network. When establishing the specific multicast bearer, a low scheduling priority is configured for the specific multicast bearer.

[0034] The version management server of the satellite routing terminal periodically sends new version data to the terrestrial core network. The terrestrial core network sends the new version data to a specific multicast bearer, and the ground base station receives the new version data from the specific multicast bearer. The version management server can periodically send the new version data to the terrestrial core network by multicast or broadcast.

[0035] Figure 1 This is a flow chart of a satellite terminal software system upgrade method of the present invention, such as Figure 1 As shown, the satellite terminal software system upgrade method provided by the present invention includes:

[0036] Step 1: Establishing a specific multicast bearer, wherein the ground base station and the ground core network establish a specific multicast bearer according to default parameters, and the satellite terminal establishes a specific multicast bearer according to the default parameters of the ground core network;

[0037] Figure 2 This is a communication architecture diagram of a satellite terminal software system upgrade method of the present invention. In actual implementation, the software version management server may not be set up in the gateway station, but may be an independent operating module or system. High-throughput satellites can also interact with multiple gateway stations. Figure 2 Only one is shown for illustration, and no specific number is limited.

[0038] In specific implementations, current satellite communication system protocols should support multicast communications. When a ground base station establishes a connection with the terrestrial core network, a dedicated multicast bearer for upgrades is established using default parameters and assigned a low scheduling priority. When the satellite terminal is powered on, a dedicated multicast bearer for upgrades is also established by default, using the same parameters as the terrestrial core network's dedicated multicast bearer, and listening to the agreed multicast address and port.

[0039] Step 2: The version service manager of the satellite routing terminal periodically sends new version data to the ground core network, which sends the new version data to a specific multicast bearer, and the ground base station receives the new version data from the specific multicast bearer;

[0040] In the specific implementation process, the version management server of the satellite routing terminal periodically sends new version data, the ground core network recognizes the new version data and forwards it to a specific multicast bearer. The ground base station receives the new version data on the specific multicast bearer.

[0041] Step 3: The ground base station sends the new version data through a specific multicast bearer, and identifies the ground base station that is sending the new version data;

[0042] The scheduling system of the ground base station sends the new version data in a specific multicast bearer of the air interface, and the ground base station completes the sending identification by notifying itself in a system message that it is sending the new version data.

[0043] During the specific implementation process, the scheduling system of the ground base station schedules the sending of the new version data on the wireless specific multicast bearer of the air interface. At the same time, the ground base station sending the new version data notifies itself in the system message that it is sending the new version data.

[0044] Step 4: The satellite terminal that has completed network access at the ground base station that sends the new version data receives the new version data through a specific multicast bearer and performs a software system upgrade; the satellite terminal that cannot access the network selects the corresponding ground base station frequency to reside on according to the sending identifier to receive the new version data through a specific multicast bearer and complete the software system upgrade.

[0045] Before executing the software system upgrade, it is first determined whether the new version data is newer than the version data currently running on the satellite terminal. If so, the software system upgrade is executed; if not, the software system upgrade is not executed.

[0046] During implementation, all satellite terminals operating on the same frequency as the ground base station will receive the new version data over a specific multicast bearer. If the received version is newer than the currently running version, the upgrade will be executed. Terminals unable to access the network can, based on the version transmission identifier in the ground base station's system message, select the frequency of the ground base station currently transmitting the version data and reside there. This will allow them to receive the new version data over a specific multicast bearer and then choose to upgrade.

[0047] In summary, the present invention provides a method for upgrading the satellite terminal software system. According to the characteristics of the DVB channel, the multicast communication mechanism is used to upgrade the online terminals at the same time. The upgrade mechanism does not need to introduce a new design in the protocol stack, and is loosely coupled with the protocol stack, which also saves air interface traffic. The overall solution for online upgrade provided by the present invention is that the satellite terminal does not need to interact with the base station to establish a specific multicast bearer for upgrading data transmission. The upgraded data is transmitted through the specific multicast bearer, and terminals that cannot access the network can also be upgraded online. The upgrade mechanism is loosely coupled with the air interface protocol stack, which does not affect the subsequent evolution of the air interface protocol stack, and the upgraded multicast bearer is given a low priority and does not affect normal business.

[0048] The above specific embodiments merely illustrate the design principles of the present invention. The shapes and names of the components described herein may vary and are not limiting. Therefore, those skilled in the art may modify or substitute equivalents for the technical solutions described in the above embodiments. Such modifications and substitutions, without departing from the inventive spirit and technical solutions of the present invention, shall fall within the scope of protection of the present invention.

Claims

1. A satellite terminal software system upgrade method, characterized in that: include: The ground base station sends the new version data through a specific multicast bearer, and identifies the ground base station that is sending the new version data; The satellite terminal that has successfully accessed the network at the ground base station that sent the new version data receives the new version data via the specific multicast bearer and performs the software system upgrade; the satellite terminal that cannot access the network selects the corresponding ground base station frequency to reside on according to the sending identifier, so as to receive the new version data via the specific multicast bearer and complete the software system upgrade; Before the ground base station sends the new version data through the specific multicast bearer, the method further includes: Establishing a specific multicast bearer, wherein the ground base station and the ground core network establish the specific multicast bearer according to default parameters, and the satellite terminal establishes the specific multicast bearer according to the default parameters of the ground core network; Before the ground base station sends the new version data through the specific multicast bearer, the method further includes: The version management server of the satellite routing terminal periodically sends new version data to the ground core network; The terrestrial core network sends the new version data to the specific multicast bearer; The ground base station receives the new version data from the specific multicast bearer.

2. The method according to claim 1, wherein When establishing the specific multicast bearer, a low scheduling priority is configured for the specific multicast bearer.

3. The method according to claim 1, wherein The version management server periodically sends new version data to the ground core network, including: The version management server periodically sends the new version data to the terrestrial core network in a multicast manner; Alternatively, the version management server periodically sends the new version data to the terrestrial core network in a broadcasting manner.

4. The method according to claim 1, wherein The ground base station sends the new version data through a specific multicast bearer, and identifies the ground base station that is sending the new version data, including: The scheduling system of the ground base station sends the new version data in a specific multicast bearer of the air interface, and the ground base station completes the sending identification by notifying itself in a system message that it is sending the new version data.

5. The method according to claim 1, wherein Before executing the software system upgrade, it is first determined whether the new version data is newer than the version data currently running on the satellite terminal. If so, the software system upgrade is executed; if not, the software system upgrade is not executed.

Images