Task arrangement information issuing method, device and equipment, non-instantaneous computer readable storage medium and computer program product

Abstract

The invention provides a task arrangement information issuing method, device and equipment, a non-instantaneous computer readable storage medium and a computer program product, and the method comprises the steps: receiving task arrangement information issued by a cloud platform through a satellite network at user equipment, the task arrangement information comprises group information of all user equipment in a group where the user equipment is located; in response to the received task arrangement information, monitoring peripheral user equipment located at the periphery of the user equipment, and determining whether the peripheral user equipment belongs to a group in which the user equipment is located and whether the peripheral user equipment receives the task arrangement information; and in response to determining that the peripheral user equipment belongs to the group in which the user equipment is located and the peripheral user equipment does not receive the task arrangement information, at least synchronizing the group information to the peripheral user equipment. Through the synchronization mechanism of the equipment in the group, the success rate of issuing the equipment marshalling task by the cloud platform is greatly improved, the reliability of the whole system is enhanced, and the stable operation of the system in a complex network environment is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of satellite network communications, and in particular to a method, apparatus, device, non-transitory computer-readable storage medium, and computer program product for sending task scheduling information. Background Art

[0002] With the continuous development of satellite communication technology, satellite networks are playing an increasingly important role in remote communications and device access in remote areas. In many practical application scenarios, multiple devices on the ground need to access backend servers via satellite networks for centralized management and task scheduling. For example, in scenarios such as field geological exploration, ocean monitoring, and remote environmental monitoring, a large number of monitoring devices are distributed over a vast area. Satellite networks have become the primary means of communication for data transmission and command exchange between these devices and backend servers.

[0003] Currently, in a satellite network environment, a common solution for a backend server to group multiple access devices and arrange group tasks before issuing them is: after completing the group arrangement, the server directly sends the tasks of each device to the corresponding device via the satellite network.

[0004] However, due to the poor stability of satellite network bandwidth and weak network, this method is prone to failure in sending tasks. Summary of the Invention

[0005] It would be advantageous to provide a mechanism that alleviates, mitigates, or eliminates at least one of the problems described above.

[0006] In a first aspect, a method for delivering task scheduling information is provided, comprising:

[0007] At the user device:

[0008] Receiving task scheduling information sent by a cloud platform via a satellite network, the task scheduling information including group information for all user devices in the group where the user device is located;

[0009] In response to receiving the task scheduling information, monitoring surrounding user devices located around the user device to determine whether the surrounding user devices belong to the group to which the user device belongs and whether the surrounding user devices have received the task scheduling information;

[0010] In response to determining that the surrounding user device belongs to the group to which the user device belongs and the surrounding user device has not yet received the task scheduling information, at least the group information is synchronized to the surrounding user device.

[0011] In a second aspect, a task scheduling information delivery device is provided, comprising:

[0012] At the user device:

[0013] a receiving unit, configured to receive task scheduling information sent by a cloud platform via a satellite network, wherein the task scheduling information includes group information for all user devices in the group where the user device is located;

[0014] a monitoring unit, configured to monitor surrounding user devices located around the user device in response to receiving the task scheduling information, to determine whether the surrounding user devices belong to the group to which the user device belongs and whether the surrounding user devices have received the task scheduling information;

[0015] The synchronization unit is configured to synchronize at least the group information to the surrounding user devices in response to determining that the surrounding user devices belong to the group to which the user devices belong and the surrounding user devices have not received the task scheduling information.

[0016] In a third aspect, a task scheduling information delivery device is provided, including:

[0017] one or more processors; and

[0018] One or more memories coupled to the one or more processors and storing instructions thereon, when the instructions are executed individually or collectively by the one or more processors, enable the task scheduling information issuing device to execute any one of the aforementioned methods.

[0019] In a fourth aspect, a non-transitory computer-readable storage medium storing machine-executable instructions is provided. When the machine-executable instructions are executed individually or collectively by one or more processors in a task scheduling information sending device, the task scheduling information sending device is caused to perform any of the aforementioned methods.

[0020] In a fifth aspect, a computer program product comprising machine-executable instructions is provided. When the machine-executable instructions are executed individually or collectively by one or more processors in a task scheduling information delivery device, the task scheduling information delivery device is caused to execute any of the aforementioned methods.

[0021] According to an exemplary embodiment of the present disclosure, when the satellite network may have unstable bandwidth, weak network, etc., resulting in unsuccessful task delivery, the user device that has successfully received the task scheduling information can act as a "relay node" to synchronize the task information to the surrounding devices in the same group that have not received the information. This method effectively makes up for the shortcomings of the satellite network in the task delivery process and greatly improves the success rate of the cloud platform's delivery of device grouping tasks. Even if some user devices fail to receive the cloud platform's task scheduling information in the first time due to satellite network problems, the synchronization mechanism of the surrounding devices can ensure that the task information can eventually be delivered to all target devices. This information transmission method enhances the reliability of the entire system, reduces system operation anomalies caused by task delivery failures, ensures the stable operation of the system in a complex network environment, and improves the efficiency of task execution.

[0022] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0024] Figure 1 The figure shows a schematic diagram of the process of sending group tasks based on a satellite network in the prior art;

[0025] Figure 2 A schematic diagram of a process for delivering a group task based on a satellite network in an embodiment of the present disclosure is shown;

[0026] Figure 3 A schematic diagram showing a process of a method for issuing task scheduling information in an embodiment of the present disclosure is shown;

[0027] Figure 4 A schematic diagram of a task scheduling and delivery process based on a satellite network in an embodiment of the present disclosure is shown;

[0028] Figure 5 A schematic diagram showing the structure of a device for issuing task scheduling information in an embodiment of the present disclosure is shown; and

[0029] Figure 6 A simplified block diagram of a task scheduling information delivery device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0030] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that the description of these embodiments is merely for illustrative purposes and helps those skilled in the art to understand and implement the present disclosure without placing any restriction on the scope of the present disclosure. The disclosure described herein can be implemented in a manner different from that described below.

[0031] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0032] References in this disclosure to "one embodiment," "an embodiment," "an exemplary embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an exemplary embodiment, whether or not explicitly described, those skilled in the art will recognize that such feature, structure, or characteristic may be combined with other embodiments.

[0033] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the listed terms.

[0034] The terms used herein are intended only to describe specific embodiments and are not intended to limit exemplary embodiments. As used herein, the singular forms "a," "an," and "the" also include the plural forms, unless the context clearly indicates otherwise. As used herein, "a group of elements" or "a set of elements" is intended to include one or more elements. It should also be understood that the terms "comprise," "include," "have," "have," "include," and / or "comprising," when used herein, specify the presence of the features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0035] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0036] (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits)

[0037] (b) a combination of hardware circuitry and software, such as (where applicable):

[0038] (i) a combination of analog and / or digital hardware circuitry and software / firmware; and

[0039] (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions, and

[0040] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) to operate, but where software is not required for operation, the software may not be present.

[0041] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also includes an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing network device, if applicable to the particular claimed element.

[0042] As used herein, the term "communication network" refers to a network that complies with any appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), Non-Terrestrial Network (NTN), etc. Furthermore, communications between terminal devices and network devices in a communication network may be performed according to any appropriate generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), future sixth generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of the present disclosure may be applied to satellite communication systems. Given the rapid developments in communications, future generations of communication technologies and systems will undoubtedly exist, and the present disclosure may be implemented with such technologies and systems. The scope of the present disclosure should not be considered limited to the aforementioned systems.

[0043] As used herein, the term "satellite network equipment" refers to a node located on a satellite or in the ground segment of a satellite communications network. Terminal devices access the network and receive services through this node. Depending on the terminology and technology used, satellite network equipment can refer to a base station (BS) or access point (AP) as a satellite payload, such as a NodeB (NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), or a relay node. An example of a relay node is an integrated access and backhaul (IAB) node. The distributed unit (DU) portion of an IAB node can perform the functions of a "satellite network equipment" and therefore operate as a network device. In the following description, the terms "satellite network equipment," "BS," and "node" are used interchangeably.

[0044] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback device, an in-vehicle wireless terminal device, a wireless endpoint, a mobile station, a notebook embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless user equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), consumer electronic devices, relay nodes, devices operating on commercial and / or industrial wireless networks, and the like. The mobile terminal (MT) portion of the IAB node can perform the functions of a "terminal device" and can therefore operate as a terminal device. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" can be used interchangeably.

[0045] While the functionality described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functionality may be implemented in a user equipment device (such as a cell phone, tablet computer, laptop computer, desktop computer, mobile IoT device, or fixed IoT device). For example, the user equipment device may appropriately have the corresponding capabilities described in connection with fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device, such as a chipset or processor, configured to control the user device when installed therein. Examples of these functions include boot server functionality and / or home subscriber server functionality, which may be implemented in the user equipment device by providing the user equipment device with software configured to cause the user equipment device to perform from the perspective of these functions / nodes.

[0046] like Figure 1 As shown in FIG, a flow chart of the prior art for sending group tasks based on a satellite network is provided. The cloud platform sends the group information of each device to each device in a point-to-point manner via the satellite network.

[0047] Due to the unique characteristics of satellite networks, poor bandwidth stability and weak network conditions are key factors affecting the success rate of mission dispatch. Satellite communication signals travel long distances and are subject to interference from various factors, such as atmospheric influences and solar activity. These factors can cause signal attenuation and distortion, which in turn affects network bandwidth stability. Furthermore, due to the significant transmission latency of satellite communications, weak network conditions, such as slow transmission speeds and packet loss, can easily occur in situations of network congestion or poor signal quality.

[0048] In existing mission delivery solutions, due to the poor stability of satellite network bandwidth and weak network conditions, packet loss and transmission interruptions can occur during the mission delivery process, resulting in unsuccessful mission delivery. Once a mission delivery fails, the server must re-initiate the mission delivery request, which not only increases server load but also prolongs the time it takes for devices to obtain the mission, impacting the overall system efficiency and timely execution of the mission. In applications where time-sensitive mission execution is crucial, unsuccessful mission delivery can have serious consequences.

[0049] Therefore, the existing method of directly sending equipment tasks through the satellite network is subject to the network environment of the satellite network, and there is a problem of unsuccessful task sending. A new technical solution is needed to improve the success rate of the cloud platform sending equipment grouping tasks, ensure that the equipment can obtain task instructions in a timely and accurate manner, thereby improving the reliability and operation efficiency of the entire system.

[0050] Based on this, the embodiment of the present disclosure proposes a solution for sending task scheduling information, such as Figure 2 As shown, a schematic diagram of the process of sending group tasks based on the satellite network in the embodiment of the present disclosure is provided. Figure 2 The principles and implementations of the present disclosure are described in detail.

[0051] The disclosed embodiments provide a method, apparatus, device, non-transitory computer-readable storage medium, and computer program product for sending task scheduling information. Figure 3 As shown, a flow chart of a method 300 for sending task scheduling information in an embodiment of the present disclosure is provided. The method 300 for sending task scheduling information at least includes the following steps S310 to S330:

[0052] At the user device:

[0053] Step S310: Receive task scheduling information sent by the cloud platform via a satellite network, where the task scheduling information includes group information for all user equipment in the group where the user equipment is located.

[0054] On the user device side, the device continuously listens for communication signals from the cloud platform. After the cloud platform completes device grouping and task scheduling, it transmits task scheduling information, including group information for all user devices within the user device's group, via the satellite network. The user device receives this task scheduling information from the cloud platform, which may include key information such as the group identifier, a list of devices within the group, and a summary of the tasks for each device. This information helps the user device understand its position within the group and the overall task plan for the group.

[0055] Step S320 : In response to receiving the task scheduling information, monitoring surrounding user devices located around the user device to determine whether the surrounding user devices belong to the group where the user device is located and whether the surrounding user devices have received the task scheduling information.

[0056] Once a user device successfully receives the task scheduling information from the cloud platform, it immediately activates a monitoring mechanism for surrounding user devices. For example, it can utilize short-range communication technology to broadcast and scan within a certain range around it to locate other nearby user devices. For discovered nearby user devices, authentication and information exchange are performed through specific communication protocols to determine whether these nearby user devices belong to the user's group and further confirm whether these nearby user devices have received the task scheduling information from the cloud platform. This process requires the user device to possess certain device identification and information exchange capabilities, enabling it to accurately determine the group affiliation and information reception status of surrounding devices.

[0057] Step S330 : In response to determining that the surrounding user device belongs to the group to which the user device belongs and the surrounding user device has not received the task scheduling information, at least synchronize the group information to the surrounding user device.

[0058] If, after determining in step S320, the user device determines that the surrounding user device belongs to its group and has not yet received the task scheduling information, the user device will perform the corresponding synchronization operation. At least the group information will be synchronized with these surrounding user devices to ensure that the surrounding user devices are aware of their group environment and the relevant task schedule. In actual applications, in addition to group information, some task details can also be synchronized so that the surrounding user devices can quickly understand the task requirements and prepare for execution. The synchronization process can be completed quickly and stably using short-range communication technology, for example, to ensure timely information transmission.

[0059] In the event that a satellite network fails to deliver a task due to unstable bandwidth or weak network conditions, user devices that have successfully received the task scheduling information can act as "relay nodes" to synchronize the task information with surrounding devices that have not received the information. This approach effectively compensates for the shortcomings of the satellite network during task delivery and greatly improves the success rate of device grouping tasks delivered by the cloud platform. Even if some user devices fail to receive the cloud platform's task scheduling information immediately due to satellite network issues, the synchronization mechanism of surrounding devices can ensure that the task information is ultimately delivered to all target devices. This information transmission method enhances the reliability of the entire system, reduces system operation anomalies caused by task delivery failures, ensures the stable operation of the system in complex network environments, and improves task execution efficiency.

[0060] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group where the user device is located, and monitoring surrounding user devices located around the user device includes: receiving device information broadcast by the surrounding user devices, the device information of the surrounding user devices including the device identity information of the surrounding user devices and indication information indicating whether the surrounding user devices have received the task scheduling information; determining whether the surrounding user devices belong to the group where the user device is located based on the device identity information of the other user devices and the device identity information of the surrounding user devices; and determining whether the surrounding user devices have received the task scheduling information based on the indication information indicating whether the surrounding user devices have received the task scheduling information.

[0061] When the cloud platform generates task scheduling information, it includes not only the group information for all user devices in the user device's group, but also the device identity information of other user devices in the group. This device identity information is primarily used to uniquely identify each device in the group, such as the device's serial number or specific device number, so that subsequent devices can accurately identify whether they belong to the same group.

[0062] The surrounding user devices will broadcast operations according to certain rules and frequencies. During the broadcast process, the surrounding user devices will send broadcast signals containing their own device information. These device information mainly includes two parts: one is the device identity information of the surrounding user devices, which is used to indicate their own identity; the other is the indication information indicating whether the surrounding user devices have received the task scheduling information. For example, the indication information can be the hash value of the most recently received task scheduling information. The hash value is a fixed-length string obtained by calculating the data using a specific algorithm. It is unique and irreversible and can effectively identify a piece of data. Of course, those skilled in the art can process and characterize the task scheduling information through other algorithms, which are not specifically limited here.

[0063] After receiving device information broadcast by nearby devices, a user device first compares the device identity information of other devices contained in the task scheduling information issued by the cloud platform with the received device identity information of the nearby device. If the two match, it means that the nearby device belongs to the same group as the user device; if not, it means that they do not belong to the same group.

[0064] The user device determines whether the surrounding user device has received the current task scheduling information based on the indicator information (such as a hash value) broadcast by the surrounding user device. The user device compares the hash value broadcast by the surrounding user device with the hash value of the task scheduling information it has currently received. If the two match, it indicates that the surrounding user device has received the same task scheduling information as the current user device. If they do not match, it indicates that the surrounding user device has not yet received the current task scheduling information.

[0065] By including the device identity information of other user devices in the group and the device identity information broadcast by surrounding user devices in the task scheduling information, the user device can accurately determine whether the surrounding user devices belong to the group it is in, avoiding the erroneous transmission of information between devices in different groups, ensuring that task information is only synchronized and shared within the relevant group, and improving the accuracy and security of information transmission.

[0066] By processing task scheduling information using algorithms such as hash values, the task reception status of surrounding user devices can be determined in a short period of time. Compared with directly transmitting the entire task scheduling information for comparison, this significantly reduces data transmission and computational complexity, improving system efficiency.

[0067] Combining group device identification and task reception status judgment, short-range communication technology can be used more effectively to synchronize task information, making up for possible failures of the satellite network during task delivery, further improving the success rate of device grouping tasks delivered by the cloud platform, and enhancing the reliability and stability of the entire system.

[0068] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group where the user device is located, and monitoring surrounding user devices located around the user device includes: broadcasting the device information of the user device to the surrounding area of the user device, the device information of the user device includes indication information indicating that the user device has received the task scheduling information, and the indication information enables surrounding user devices located around the user device and not yet received the task scheduling information to initiate a request to obtain the task scheduling information; receiving the device information broadcast by the surrounding user devices, the device information of the surrounding user devices includes the device identity information of the surrounding user devices and the request to obtain the task scheduling information; determining whether the surrounding user device belongs to the group where the user device is located based on the device identity information of the other user devices and the device identity information of the surrounding user devices; and determining that the surrounding user devices have not yet received the task scheduling information based on the request to obtain the task scheduling information.

[0069] As another implementation method corresponding to the aforementioned embodiment, the user device can broadcast its own information. After receiving the task scheduling information issued by the cloud platform, the user device will broadcast its own device information to its surroundings. These device information include indication information indicating that the user device has received the task scheduling information, for example, it can be a hash value of the currently received task scheduling information. By broadcasting the indication that the user device has received the task scheduling information, the surrounding devices that have not yet received the information can be informed and trigger them to initiate a request to obtain the task scheduling information.

[0070] Neighboring user devices receive the broadcast information from the user device and retrieve the hash value and other indicative information. The neighboring user device compares the received hash value with the hash value of the task scheduling information it most recently received. If the two match, the neighboring user device has already received the current task scheduling information and does not need to initiate a request to obtain the task scheduling information. If they do not match, the neighboring user device has not yet received the current task scheduling information and needs to initiate a request to obtain the task scheduling information.

[0071] Nearby user devices (that haven't yet received the task schedule information) broadcast their device information, including their device identity and a request for task schedule information. This allows the user device to identify nearby devices that need task schedule information and further determine whether these devices belong to the same group.

[0072] The user device receives device information broadcasted by surrounding user devices, including device identity information and a request for task scheduling information. The user device compares the device identity information of other user devices contained in the task scheduling information issued by the cloud platform with the device identity information of the surrounding user devices received. If the two match, it indicates that the surrounding user device belongs to the same group as the user device; if they do not match, it indicates that they do not belong to the same group. Because the surrounding user device broadcasts a request for task scheduling information, the user device can directly determine that the surrounding user device has not yet received the current task scheduling information.

[0073] When determining the status of their own task reception, surrounding user devices only need to perform a simple hash value comparison, eliminating the need to frequently send large amounts of data to verify receipt of task scheduling information. Only when they are certain they have not received the task scheduling information will they initiate a request, effectively reducing communication overhead and improving system resource utilization.

[0074] In some embodiments, determining whether the surrounding user device belongs to the group to which the user device belongs based on the device identity information of the other user devices and the device identity information of the surrounding user devices includes: comparing the device identity information of the surrounding user device with the device identity information of the other user devices; in response to the comparison indicating that the device identity information of the surrounding user device is consistent with the device identity information of one of the other user devices, determining that the surrounding user device belongs to the group to which the user device belongs; in response to the comparison indicating that the device identity information of the surrounding user device is inconsistent with the device identity information of any of the other user devices, determining that the surrounding user device does not belong to the group to which the user device belongs.

[0075] The user device compares the device identity information of the surrounding user devices with the device identity information of other user devices in the group one by one, for example, the device serial number in the device identity information may be used for comparison.

[0076] If, during the comparison process, it is found that the device identity information of the surrounding user device is exactly the same as the device identity information of any other user device in the group, the user device determines that the surrounding user device belongs to the group it belongs to. If the device identity information of the surrounding user device is inconsistent with the device identity information of any other user device in the group, the user device determines that the surrounding user device does not belong to the group it belongs to.

[0077] Through strict device identity information comparison, it is possible to accurately determine whether surrounding user devices belong to the same group. Only devices belonging to the same group will perform subsequent task orchestration information synchronization and collaborative work, avoiding the erroneous transmission of information between devices in different groups and improving the accuracy and security of information transmission.

[0078] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group to which the user device belongs, and synchronizing at least the group information to the surrounding user devices includes: synchronizing the device identity information and the group information of the other user devices to the surrounding user devices to allow the surrounding user devices to perform the monitoring and synchronization operations.

[0079] After receiving the task schedule from the cloud platform, the user device will synchronize the group information and the device identity information of other user devices in the group with the surrounding user devices in the same group. This synchronization can be achieved using short-range communication technologies such as Bluetooth, WiFi, and ZigBee.

[0080] After receiving the group information and device identity information of other user devices synchronized by the user device, the surrounding user devices can perform monitoring and synchronization operations. For example, the surrounding user devices monitor the surrounding environment to obtain information or status of other relevant devices. Based on the group information and the device identity information of other user devices, they synchronize tasks with other devices. This process is similar to the monitoring and synchronization process for user devices described above and is not further described here.

[0081] By synchronizing group information and device identity information of other user devices to surrounding user devices, surrounding devices can understand the task arrangements of the entire group and the identity information of other devices, thereby better cooperating with other devices.

[0082] In some embodiments, synchronizing at least the group information to the surrounding user devices includes: establishing a data channel with the surrounding user devices through a short-range communication protocol; and sending at least the group information to the surrounding user devices via the data channel.

[0083] After receiving the task orchestration information (including group information) from the cloud platform, the user device's internal communication module begins working, preparing to establish short-range communication connections with nearby user devices. The user device can select an appropriate short-range communication protocol, such as Bluetooth, Wi-Fi, or ZigBee, based on factors such as the surrounding environment, device type, and communication requirements. For example, a user device can send Bluetooth Low Energy (BLE) broadcasts and listen for Bluetooth Low Energy broadcasts from other devices. Bluetooth Low Energy broadcasts carry the device's own device information. Another example is a user device can send CoAP broadcasts to other devices on a Wi-Fi network and listen for CoAP broadcasts from other devices. CoAP broadcasts carry the device's own device information.

[0084] After a user device successfully establishes a data channel with surrounding user devices using a short-range communication protocol, it encapsulates group information (such as device information and task information within the group) according to the communication protocol format and sends it to the surrounding user devices via the data channel. Upon receiving the group information, the surrounding user devices parse and store it.

[0085] Short-range communication protocols typically establish connections quickly, enabling the establishment of data channels in a short period of time, ensuring that group information is promptly transmitted to nearby user devices. Short-range communication protocols offer high stability and reliability when communicating over short distances, ensuring that group information is not lost or damaged during transmission. Short-range communication protocols typically do not require complex network infrastructure, resulting in low communication costs and relatively low power consumption, which can extend device battery life. Short-range communication is not restricted by geographic location or network coverage, allowing user devices to flexibly establish communication connections with nearby user devices based on actual needs, synchronizing group information.

[0086] In some embodiments, sending at least the group information to the surrounding user device via the data channel includes: obtaining the public key of the surrounding user device from the device information of the surrounding user device; encrypting the task scheduling information using the public key to obtain encrypted task scheduling information; and sending the encrypted task scheduling information to the surrounding user device via the data channel.

[0087] After a user device successfully establishes a data channel with a nearby user device via a short-range communication protocol, the two devices begin exchanging device information. The nearby user device sends a message containing its own device information, including the nearby user device's public key. The user device then encrypts the task scheduling information using the nearby user device's public key. The encryption process converts the original task scheduling information into a ciphertext form that can only be decrypted by devices with the corresponding private key.

[0088] The user device sends the encrypted task schedule information to the surrounding user devices through the established data channel. After receiving the encrypted information, the surrounding user devices can use the private key corresponding to the public key stored in their own storage to decrypt the encrypted task schedule information, thereby obtaining the original task schedule information.

[0089] By using the public key of the surrounding user devices to encrypt the task scheduling information, only the surrounding user devices with the corresponding private key can decrypt the information, effectively preventing the leakage of task scheduling information during transmission, thereby ensuring the security of information transmission.

[0090] In some embodiments, before receiving the task scheduling information sent by the cloud platform via the satellite network, the method further includes: generating a pair of public and private keys when accessing the satellite network; uploading the device identity information of the user device and the public key to the cloud platform; and storing the private key locally on the user device.

[0091] Before receiving task orchestration information delivered by the cloud platform via the satellite network, the user device must first connect to the satellite network. This primarily involves the satellite communication module in the user device establishing a connection with the satellite, completing operations such as signal acquisition, tracking, and synchronization. Once the user device successfully connects to the satellite network, its internal security module generates a pair of public and private keys. The key generation algorithm, such as RSA or elliptic curve cryptography, ensures the security and uniqueness of the generated key.

[0092] The user device encapsulates its own device identity information (such as device number, device type, device location, etc.) and the generated public key into a format that complies with the satellite communication protocol, uploads it to the cloud platform via the satellite network, and securely stores the generated private key in the local storage module, so that when it subsequently receives encrypted task scheduling information synchronized from other devices, it can directly use the locally stored private key for decryption.

[0093] After the user device uploads the public key to the cloud platform, the cloud platform can use this public key to encrypt the task scheduling information when sending it to the user device. Only the user device with the corresponding private key can decrypt this information, ensuring the security of information during transmission over the satellite network. Furthermore, because the private key is stored locally on the user device and strictly confidential, only legitimate user devices can use it to correctly perform digital signing and decryption operations. This makes it difficult for malicious devices to impersonate legitimate devices to access the satellite network and cloud platform, thereby improving system security.

[0094] In order to facilitate the understanding of the above embodiments, Figure 4 As shown, a schematic diagram of the task scheduling and delivery process based on the satellite network in an embodiment of the present disclosure is provided. It mainly includes the following steps:

[0095] 1. When a user device connects to the cloud platform, it uploads its device identity information, such as the SN serial number, and generates a pair of public and private keys. The private key is stored locally on the device, and the public key is uploaded to the cloud platform along with the identity information.

[0096] 2. The cloud platform will send the group information of each user device, the device information of other devices in the group, and the public key information of other devices to the corresponding devices (such as device B and device D) via the satellite network.

[0097] 3. Device B (Device D) can send Bluetooth Low Energy (BLE) broadcasts and listen for other devices' Bluetooth Low Energy (BLE) broadcasts. These broadcasts carry the device's own information. Alternatively, Device B (Device D) can send CoAP broadcasts to other devices on a Wi-Fi network and listen for other devices' CoAP broadcasts. These broadcasts carry the device's own information. This allows Device B (Device D) to detect nearby devices via short-range communication methods like Bluetooth Low Energy (BLE) and Wi-Fi.

[0098] 4. After receiving the grouping information sent by the cloud platform, device B (device D) will judge whether the surrounding device is a device in the group information by combining the information of the surrounding devices sensed by short-range methods such as Bluetooth and WIFI in step [3].

[0099] 5. If a nearby user device is found to be part of the current group, data exchange will be carried out via short-range protocols such as Bluetooth Low Energy (BLE) and Wi-Fi. For example, a Bluetooth channel will be established via Bluetooth Low Energy (BLE) or a TCP channel will be established via Wi-Fi to synchronize group information. The data synchronization process is encrypted using the peer's public key to ensure secure data transmission.

[0100] 6. After receiving the group information from the surrounding user devices via short-range mode, the device will continue to discover whether there are other devices in the group information around it, and then perform steps [3]-[5].

[0101] 7. All devices in the group will transmit according to steps [3]-[6] until all user devices in the group have correctly received the group information.

[0102] In combination with actual business scenarios, user devices that need to be orchestrated generally appear in clusters and can discover each other within a short range. The present disclosure improves the success rate of the cloud platform sending device grouping tasks by adding a short-range method of sending grouping tasks. For example, in scenarios where multiple devices such as broadband terminals, narrowband handheld devices, and narrowband Internet of Things devices work together and need to synchronize key data such as access rights to a certain key service, although the broadband bandwidth is good and the success probability is high, the narrowband Internet of Things bandwidth and resources are limited and the success probability is low. Since the current short-range technical solutions and hardware are relatively mature, the solution disclosed in this disclosure can effectively solve the success rate of multiple devices receiving group information sent from the cloud in similar scenarios.

[0103] The disclosed embodiment also provides a task scheduling information sending device 500, such as Figure 5 As shown, a structural diagram of a task scheduling information delivery device 500 according to an embodiment of the present disclosure is provided. The device 500 includes: a receiving unit 510, a monitoring unit 520, and a synchronization unit 530, wherein:

[0104] At the user device:

[0105] A receiving unit 510 is configured to receive task scheduling information sent by a cloud platform via a satellite network, wherein the task scheduling information includes group information for all user devices in the group where the user device is located;

[0106] a monitoring unit 520 configured to monitor surrounding user devices located around the user device in response to receiving the task scheduling information to determine whether the surrounding user devices belong to the group to which the user device belongs and whether the surrounding user devices have received the task scheduling information;

[0107] The synchronization unit 530 is configured to synchronize at least the group information to the surrounding user devices in response to determining that the surrounding user devices belong to the group to which the user devices belong and the surrounding user devices have not received the task scheduling information.

[0108] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group where the user device is located, and the monitoring unit 520 is specifically used to: receive device information broadcast by the surrounding user devices, the device information of the surrounding user devices including the device identity information of the surrounding user devices and indication information indicating whether the surrounding user devices have received the task scheduling information; determine whether the surrounding user devices belong to the group where the user device is located based on the device identity information of the other user devices and the device identity information of the surrounding user devices; determine whether the surrounding user devices have received the task scheduling information based on the indication information indicating whether the surrounding user devices have received the task scheduling information.

[0109] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group where the user device is located, and the monitoring unit 520 is specifically used to: broadcast the device information of the user device to the surrounding area of the user device, the device information of the user device includes indication information indicating that the user device has received the task scheduling information, and the indication information enables the surrounding user devices located in the surrounding area of the user device and not yet received the task scheduling information to initiate a request to obtain the task scheduling information; receive the device information broadcast by the surrounding user devices, the device information of the surrounding user devices includes the device identity information of the surrounding user devices and the request to obtain the task scheduling information; determine whether the surrounding user device belongs to the group where the user device is located based on the device identity information of the other user devices and the device identity information of the surrounding user devices; and determine that the surrounding user devices have not yet received the task scheduling information based on the request to obtain the task scheduling information.

[0110] In some embodiments, the monitoring unit 520 is specifically used to: compare the device identity information of the surrounding user device with the device identity information of the other user devices; in response to the comparison showing that the device identity information of the surrounding user device is consistent with the device identity information of one of the other user devices, determine that the surrounding user device belongs to the group to which the user device belongs; in response to the comparison showing that the device identity information of the surrounding user device is inconsistent with the device identity information of any of the other user devices, determine that the surrounding user device does not belong to the group to which the user device belongs.

[0111] In some embodiments, the task scheduling information also includes device identity information of other user devices in the group to which the user device belongs, and the synchronization unit 530 is specifically used to synchronize the device identity information of the other user devices and the group information to the surrounding user devices to allow the surrounding user devices to perform the monitoring and synchronization operations.

[0112] In some embodiments, the synchronization unit 530 is specifically configured to: establish a data channel with the surrounding user devices via a short-range communication protocol; and send at least the group information to the surrounding user devices via the data channel.

[0113] In some embodiments, the synchronization unit 530 is specifically used to: obtain the public key of the surrounding user device from the device information of the surrounding user device; use the public key to encrypt the task scheduling information to obtain encrypted task scheduling information; and send the encrypted task scheduling information to the surrounding user device via the data channel.

[0114] In some embodiments, the device 500 also includes: a generation unit, used to generate a pair of public keys and private keys when accessing the satellite network before receiving the task scheduling information sent by the cloud platform via the satellite network; an uploading unit, used to upload the device identity information of the user device and the public key to the cloud platform; and save the private key locally on the user device.

[0115] The above-mentioned task scheduling information issuing device can implement each step of the task scheduling information issuing method provided in the above-mentioned embodiment. The relevant explanations about the task scheduling information issuing method are applicable to the task scheduling information issuing device and will not be repeated here.

[0116] While specific functions have been discussed above with reference to specific units, it should be noted that the functionality of the various units discussed herein may be divided into multiple units, and / or at least some of the functionality of multiple units may be combined into a single unit. The specific unit discussed herein performing an action includes the specific unit itself performing the action, or alternatively the specific unit calling or otherwise accessing another component or unit that performs the action (or performs the action in conjunction with the specific unit). Thus, the specific unit that performs an action may include the specific unit itself that performs the action and / or another unit that the specific unit calls or otherwise accesses to perform the action.

[0117] It should also be understood that various techniques may be described herein in the general context of software hardware elements or program units. Figure 5The various units described may be implemented in hardware or in hardware in combination with software and / or firmware. For example, these units may be implemented as computer program code / instructions configured to be executed in one or more processors and stored in a computer-readable storage medium. Alternatively, these units may be implemented as hardware logic / circuits.

[0118] An embodiment of the present disclosure also provides a computer storage medium storing instructions, which, when executed individually or collectively by at least one processor of a computing device, cause the computing device to perform the method of the first aspect.

[0119] An embodiment of the present disclosure further provides a computer program product, comprising instructions, which, when executed individually or collectively by at least one processor of a computing device, enable the computing device to perform the above-mentioned synchronization signal detection method.

[0120] The present disclosure also provides a chip including a circuit system configured to execute the above-mentioned method for delivering task scheduling information. It should be noted that the circuit system may be a dedicated integrated circuit, a general-purpose processor, or a combination thereof.

[0121] An embodiment of the present disclosure also provides a computing device including the above-mentioned chip.

[0122] Figure 6 FIG. 6 is a simplified block diagram of a task scheduling information delivery device 600 suitable for implementing the embodiment of the present disclosure. Figure 6 As shown, the task scheduling information sending device 600 includes one or more processors 610 , one or more memories 620 coupled to the processors 610 , and one or more communication modules 640 coupled to the processors 610 .

[0123] The communication module 640 is used for two-way communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communicating with other network elements.

[0124] Processor 610 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Task orchestration information delivery device 600 may have multiple processors, such as application-specific integrated circuit chips, which are driven in time to a clock that synchronizes the master processor.

[0125] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist across a power outage.

[0126] Computer program 630 includes computer executable instructions for execution by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any appropriate actions and processes by loading program 630 into RAM 622.

[0127] The embodiment of the present disclosure can be implemented by the program 630, so that the task scheduling information issuing device 600 can execute the reference Figure 1 Any process of the disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0128] In some embodiments, program 630 may be tangibly embodied in a computer-readable medium, which may be contained in task scheduling information delivery device 600 (e.g., memory 620) or another storage device accessible to task scheduling information delivery device 600. Task scheduling information delivery device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Program 630 is stored on the computer-readable medium.

[0129] It should be noted that computing devices include but are not limited to terminal devices, base station devices (for example, ground base stations or satellite network devices), and devices that can implement the above-mentioned synchronization signal detection method all fall within the scope of protection of this disclosure.

[0130] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0131] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in program modules, which are executed in a device on a target real or virtual processor. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or separated between program modules as needed. The machine-executable instructions for the program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0132] The program code for carrying out the disclosed method can be written with any combination of one or more programming languages. These program codes can be provided to the processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing equipment so that when the program code is executed by the processor or controller, the function / operation specified in the flow chart and / or the block diagram is realized. The program code can be executed fully on the machine as an independent software package, partly on the machine, partly on the machine, partly on a remote machine, partly on a remote machine, or all on a remote machine or server.

[0133] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0134] A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0135] In addition, although operations are described in a specific order, this should not be understood as requiring that these operations be performed in the specific order or sequence shown, or that all operations shown be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limiting the scope of this disclosure, but rather as describing features specific to a particular embodiment. Some features described in the context of a separate embodiment may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually or in any suitable subcombination in multiple embodiments.

[0136] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0137] It should be understood that the use of personally identifiable information should be subject to privacy policies and practices generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

1. A method for delivering task scheduling information, comprising: At the user device: Receiving task scheduling information sent by a cloud platform via a satellite network, the task scheduling information including group information for all user devices in the group where the user device is located; In response to receiving the task scheduling information, monitoring surrounding user devices located around the user device to determine whether the surrounding user devices belong to the group to which the user device belongs and whether the surrounding user devices have received the task scheduling information; In response to determining that the surrounding user device belongs to the group to which the user device belongs and the surrounding user device has not yet received the task scheduling information, at least the group information is synchronized to the surrounding user device.

2. The method according to claim 1, wherein The task scheduling information further includes device identity information of other user devices in the group to which the user device belongs, and monitoring surrounding user devices located around the user device includes: receiving device information broadcast by the surrounding user devices, where the device information of the surrounding user devices includes device identity information of the surrounding user devices and indication information indicating whether the surrounding user devices have received the task scheduling information; Determining whether the surrounding user device belongs to the group to which the user device belongs based on the device identity information of the other user device and the device identity information of the surrounding user device; Whether the surrounding user equipment has received the task scheduling information is determined according to the indication information indicating whether the surrounding user equipment has received the task scheduling information.

3. The method according to claim 1, wherein The task scheduling information further includes device identity information of other user devices in the group to which the user device belongs, and monitoring surrounding user devices located around the user device includes: Broadcasting device information of the user device to surrounding areas of the user device, wherein the device information of the user device includes indication information indicating that the user device has received the task scheduling information, so that surrounding user devices located around the user device and not having received the task scheduling information initiate a request to obtain the task scheduling information; receiving device information broadcast by the surrounding user devices, where the device information of the surrounding user devices includes device identity information of the surrounding user devices and the request for obtaining the task scheduling information; Determining whether the surrounding user device belongs to the group to which the user device belongs based on the device identity information of the other user devices and the device identity information of the surrounding user devices; According to the request for obtaining the task scheduling information, it is determined that the surrounding user equipment has not received the task scheduling information.

4. The method according to claim 2 or 3, wherein: The determining, based on the device identity information of the other user devices and the device identity information of the surrounding user devices, whether the surrounding user devices belong to the group to which the user devices belong includes: Comparing the device identity information of the surrounding user devices with the device identity information of the other user devices; In response to the comparison indicating that the device identity information of the surrounding user device is consistent with the device identity information of one of the other user devices, determining that the surrounding user device belongs to the group to which the user device belongs; In response to the comparison indicating that the device identity information of the surrounding user device is inconsistent with the device identity information of any of the other user devices, it is determined that the surrounding user device does not belong to the group to which the user device belongs.

5. The method according to claim 2 or 3, wherein: The task scheduling information further includes device identity information of other user devices in the group to which the user device belongs, and synchronizing at least the group information to the surrounding user devices includes: The device identity information and the group information of the other user devices are synchronized with the surrounding user devices, so as to allow the surrounding user devices to perform the monitoring and synchronization operations.

6. The method according to any one of claims 1 to 3, wherein: The step of at least synchronizing the group information to the surrounding user devices includes: Establishing a data channel with the surrounding user equipment through a short-range communication protocol; At least the group information is sent to the surrounding user devices via the data channel.

7. The method according to claim 6, wherein: The sending at least the group information to the surrounding user devices via the data channel includes: Obtaining the public key of the surrounding user device from the device information of the surrounding user device; Encrypting the task scheduling information using the public key to obtain encrypted task scheduling information; The encrypted task scheduling information is sent to the surrounding user devices via the data channel.

8. The method for issuing task scheduling information according to any one of claims 1 to 3, wherein: Before receiving the task scheduling information sent by the cloud platform via the satellite network, the method further includes: When accessing the satellite network, generating a pair of public and private keys; Uploading the device identity information of the user device and the public key to the cloud platform; The private key is stored locally on the user device.

9. A task scheduling information delivery device, comprising: At the user device: a receiving unit, configured to receive task scheduling information sent by a cloud platform via a satellite network, wherein the task scheduling information includes group information for all user devices in the group where the user device is located; a monitoring unit, configured to monitor surrounding user devices located around the user device in response to receiving the task scheduling information, to determine whether the surrounding user devices belong to the group to which the user device belongs and whether the surrounding user devices have received the task scheduling information; The synchronization unit is configured to synchronize at least the group information to the surrounding user devices in response to determining that the surrounding user devices belong to the group to which the user devices belong and the surrounding user devices have not received the task scheduling information.

10. A task scheduling information delivery device, comprising: one or more processors; as well as One or more memories coupled to the one or more processors and storing instructions thereon, which, when the one or more processors execute the instructions individually or collectively, enable the task scheduling information issuing device to execute the method of any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium storing machine-executable instructions, wherein when the machine-executable instructions are executed individually or collectively by one or more processors in a task scheduling information issuing device, the task scheduling information issuing device is caused to execute the method of any one of claims 1 to 8.

12. A computer program product comprising machine-executable instructions, wherein when the machine-executable instructions are executed individually or collectively by one or more processors in a task scheduling information issuing device, the device is caused to execute the method according to any one of claims 1 to 8.

Images