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

Abstract

Provided are a task arrangement information issuing method and device, equipment, non-transient computer readable storage medium and computer program product, the method comprising: at a user equipment: receiving task arrangement information issued by a cloud platform through a satellite network, the task arrangement information comprising group information for all user equipment in a group in which the user equipment is located; in response to receiving the task arrangement information, listening to peripheral user equipment located around the user equipment, and determining whether the peripheral user equipment belongs to the group in which the user equipment is located and whether the peripheral user equipment has received the task arrangement information; in response to determining that the peripheral user equipment belongs to the group in which the user equipment is located and that the peripheral user equipment has not received the task arrangement information, synchronizing at least the group information to the peripheral user equipment. Through the synchronization mechanism of the equipment in the group, the disclosure greatly improves the success rate of the cloud platform issuing the equipment grouping task, enhances the reliability of the entire system, and guarantees the stable operation of the system in a complex network environment.

Description

Technical Field

[0001] This disclosure relates to the field of satellite network communication, and specifically to a method, apparatus, device, non-transient computer-readable storage medium, and computer program product for distributing task scheduling information. Background Technology

[0002] With the continuous development of satellite communication technology, satellite networks are playing an increasingly important role in areas such as long-distance communication and equipment access in remote areas. In many practical applications, multiple devices on the ground need to connect to a backend server via satellite network so that the server can centrally manage these devices and schedule tasks. For example, in scenarios such as field geological exploration, marine monitoring, and environmental monitoring in remote areas, a large number of monitoring devices are distributed over a wide area, and satellite networks have become the main communication means for data transmission and command exchange between these devices and the backend server.

[0003] Currently, in a satellite network environment, the common approach for a backend server to manage multiple access devices in groups and assign tasks to these groups is as follows: after completing the group assignment, the server directly sends the tasks for each device to the corresponding device via the satellite network.

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

[0005] Providing a mechanism to alleviate, reduce or eliminate at least one of the above problems would be beneficial.

[0006] In the first aspect, a method for distributing task orchestration information is provided, including:

[0007] At the user equipment:

[0008] Receive task orchestration information sent by the cloud platform via satellite network, the task orchestration information including group information for all user devices in the group to which the user device is located;

[0009] In response to receiving the task orchestration information, the system monitors nearby user devices located around the user device to determine whether the nearby user devices belong to the group to which the user device belongs and whether the nearby user devices have received the task orchestration information.

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

[0011] In a second aspect, a task orchestration information distribution device is provided, comprising:

[0012] At the user equipment:

[0013] The receiving unit is used to receive task scheduling information sent by the cloud platform through the satellite network. The task scheduling information includes group information for all user devices in the group to which the user device is located.

[0014] A listening unit is configured to, in response to receiving the task orchestration information, listen to 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 orchestration information.

[0015] A synchronization unit is configured to, in response to determining that the surrounding user equipment belongs to the group to which the user equipment belongs and that the surrounding user equipment has not yet received the task orchestration information, at least synchronize the group information to the surrounding user equipment.

[0016] In a third aspect, a task orchestration information distribution 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, wherein the task orchestration information delivery device performs any of the foregoing methods when the instructions are executed individually or jointly by the one or more processors.

[0019] In a fourth aspect, a non-transitory computer-readable storage medium storing machine-executable instructions is provided, which, when executed individually or jointly by one or more processors in a task orchestration information delivery device, cause the task orchestration information delivery device to perform any of the foregoing methods.

[0020] In a fifth aspect, a computer program product including machine-executable instructions is provided, which, when executed individually or jointly by one or more processors in a task orchestration information delivery device, cause the task orchestration information delivery device to perform any of the methods described above.

[0021] According to an exemplary embodiment of this disclosure, in cases where satellite networks may experience bandwidth instability or weak networks leading to unsuccessful task delivery, user devices that have successfully received task orchestration information can act as "relay nodes," synchronizing the task information with surrounding devices within the same group that have not yet received the information. This approach effectively compensates for the shortcomings of satellite networks in the task delivery process, significantly improving the success rate of cloud platform-delivered device grouping tasks. Even if some user devices fail to receive the cloud platform's task orchestration information immediately due to satellite network issues, the synchronization mechanism of surrounding devices ensures that the task information is ultimately delivered to all target devices. This information transmission method enhances the reliability of the entire system, reduces system malfunctions caused by task delivery failures, ensures stable system operation in complex network environments, and improves task execution efficiency.

[0022] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

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

[0024] Figure 1 A schematic diagram of the process for issuing group tasks based on satellite networks in the prior art is shown;

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

[0026] Figure 3 A flowchart illustrating the task orchestration information distribution method in an embodiment of this disclosure is shown.

[0027] Figure 4 This illustration shows a schematic diagram of the task orchestration and distribution process based on a satellite network in an embodiment of this disclosure;

[0028] Figure 5 A schematic diagram of the structure of the task orchestration information distribution device in an embodiment of this disclosure is shown; and

[0029] Figure 6 A simplified block diagram of a task orchestration information distribution device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0030] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein may be implemented in ways other than those described below.

[0031] In the following description and claims, unless otherwise defined, 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 pertains.

[0032] References to "an embodiment," "embodiment," "exemplary embodiment," etc., in this disclosure indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment needs to include specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an exemplary embodiment, whether explicitly described or not, those skilled in the art will recognize that such a feature, structure, or characteristic affects its connection to other embodiments.

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

[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein also include the plural forms unless the context clearly indicates otherwise. The terms “a group of elements” or “a collection of elements” as used herein are intended to include one or more elements. It should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “including,” and / or “comprising,” when used herein, specify the presence of the stated 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 "circuit" may refer to one or more 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 (if applicable):

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

[0039] (ii) Any part of a hardware processor (including a digital signal processor), 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 circuitry and / or processors, such as microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when software is not required to operate.

[0041] The definition of "circuit" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit" also includes implementations of hardware circuitry or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware. The term "circuit" also includes, for example, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing network devices, if applicable to a particular claim element.

[0042] As used herein, the term "communication network" refers to a network that conforms to any suitable 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, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, 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), and future sixth-generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to satellite communication systems. Given the rapid development in communications, future types of communication technologies and systems will naturally exist, and this disclosure can be implemented using these technologies and systems. The scope of this disclosure should not be considered limited to the aforementioned systems.

[0043] As used herein, the term "satellite network device" refers to a node located on a satellite or ground segment within a satellite communication network. Terminal devices access the network and receive services through this node. Depending on the terminology and technology applied, a satellite network device can refer to a base station (BS) or access point (AP) that serves as a satellite payload, such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), or a relay node. An example of a relay node can be an Integrated Access and Backhaul (IAB) node. The Distributed Unit (DU) portion of an IAB node can perform the functions of a "satellite network device" and therefore can operate as a network device. In the following description, the terms "satellite network device," "BS," and "node" are used interchangeably.

[0044] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a 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). This terminal device may include, but is not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop installed devices (LMEs), USB dongles, smart devices, wireless subscriber equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, relay nodes, devices operating on commercial and / or industrial wireless networks, etc. The mobile terminal (MT) portion of an IAB node can perform the functions of a "terminal device" and therefore can operate as a terminal device. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0045] While the functions described herein may be implemented in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, they may be implemented in user equipment devices (such as cellular phones, tablet computers, laptop computers, desktop computers, mobile IoT devices, or fixed IoT devices). For example, the user equipment device may suitably have the corresponding capabilities described in relation to fixed and / or wireless network nodes. The user equipment device may be user equipment and / or control devices, such as chipsets or processors, configured to control the user equipment when it is installed therein. Examples of these functions include boot server functions and / or home subscriber servers, 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 The diagram illustrates the workflow for distributing group tasks via satellite networks in existing technologies. The cloud platform transmits group information for 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 delivery. Satellite communication signals travel long distances, and during transmission, they are subject to interference from various factors, such as atmospheric effects and solar activity. These factors lead to signal attenuation and distortion, thus affecting network bandwidth stability. Simultaneously, because satellite communication has significant transmission delays, weak network conditions are easily encountered under network congestion or poor signal quality, resulting in slower network transmission speeds and data packet loss.

[0048] In existing task delivery schemes, due to the poor stability of satellite network bandwidth and weak network conditions, issues such as data packet loss and transmission interruptions may occur during task delivery, leading to unsuccessful task delivery. Once task delivery fails, the server needs to re-initiate the task delivery request, which not only increases the server load but also prolongs the time for devices to acquire tasks, impacting the overall system efficiency and timely task execution. Especially in application scenarios with high time sensitivity to task execution, unsuccessful task delivery can lead to serious consequences.

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

[0050] Based on this, embodiments of this disclosure propose a solution for distributing task orchestration information, such as... Figure 2 The diagram illustrates a process for distributing group tasks based on a satellite network, as shown in this embodiment of the present disclosure. The following will be based on... Figure 2 The principles and implementation of this 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 distributing task orchestration information. For example... Figure 3 The diagram shows a flowchart of a task orchestration information distribution method 300 in this embodiment of the present disclosure. The task orchestration information distribution method 300 includes at least the following steps S310 to S330:

[0052] At the user equipment:

[0053] Step S310: Receive task scheduling information sent by the cloud platform via the satellite network. The task scheduling information includes group information for all user devices in the group to which the user device is located.

[0054] On the user device side, the device continuously listens for communication signals from the cloud platform. After completing the grouping and task orchestration of the devices, the cloud platform transmits task orchestration information, which includes group information for all user devices within the group to which the user device belongs, via satellite network. The user device receives this task orchestration information from the cloud platform. This information may include key content such as the group identifier, a list of devices within the group, and a summary of the tasks for each device, so that the user device can clearly understand its position in the group and the overall task plan of the group.

[0055] Step S320: In response to receiving the task orchestration information, monitor the 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 orchestration information.

[0056] Once a user device successfully receives the task orchestration information from the cloud platform, it immediately initiates a nearby user device monitoring mechanism. For example, short-range communication technology can be used to broadcast and scan within a certain radius to locate other nearby user devices. For discovered nearby user devices, authentication and information exchange are performed through a specific communication protocol to determine if these devices belong to the user's own group and further confirm whether they have received the task orchestration information from the cloud platform. This process requires the user device to possess certain device identification and information exchange capabilities, accurately determining the group affiliation and information reception status of nearby devices.

[0057] Step S330: In response to determining that the surrounding user equipment belongs to the group to which the user equipment belongs and that the surrounding user equipment has not yet received the task orchestration information, at least the group information is synchronized to the surrounding user equipment.

[0058] If, after step S320, it is determined that the surrounding user devices belong to their own group and have not yet received task scheduling information, the user devices will take corresponding synchronization actions. At a minimum, group information will be synchronized to these surrounding user devices to ensure they are aware of their group environment and relevant task arrangements. In practical applications, in addition to group information, some task details can also be synchronized so that surrounding user devices can quickly understand the task requirements and prepare for execution. The synchronization process can be completed quickly and stably, for example, using short-range communication technology to ensure timely information transmission.

[0059] In situations where satellite networks may experience bandwidth instability or weak networks, leading to unsuccessful task delivery, user devices that have successfully received task orchestration information can act as "relay nodes," synchronizing the task information to surrounding devices that have not yet received the information. This approach effectively compensates for the shortcomings of satellite networks in the task delivery process, significantly improving the success rate of cloud platform-delivered task orchestration. Even if some user devices fail to receive the cloud platform's task orchestration information immediately due to satellite network issues, the synchronization mechanism of surrounding devices ensures that the task information is ultimately transmitted to all target devices. This information transmission method enhances the reliability of the entire system, reduces system malfunctions caused by task delivery failures, ensures stable system operation in complex network environments, and improves task execution efficiency.

[0060] In some embodiments, the task orchestration information further includes device identity information of other user devices within the group to which the user device belongs. Monitoring surrounding user devices located near the user device includes: receiving device information broadcast by the surrounding user devices, the device information including device identity information and indication information indicating whether the surrounding user devices have received the task orchestration information; determining whether the surrounding user devices belong 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; and determining whether the surrounding user devices have received the task orchestration information based on the indication information indicating whether the surrounding user devices have received the task orchestration information.

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

[0062] Nearby user equipment (UFOs) broadcast according to certain rules and frequencies. During the broadcast, UFOs send broadcast signals containing their own device information. This device information mainly includes two parts: first, the device identification information of the nearby UFO, used to identify itself; and second, an indication of whether the nearby UFO has received the task orchestration information. For example, the indication information could be the hash value of the most recently received task orchestration information. A hash value is a fixed-length string calculated by a specific algorithm on data, possessing uniqueness and irreversibility, and effectively identifying a piece of data. Of course, those skilled in the art can process and characterize task orchestration information using other algorithms, which are not specifically limited here.

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

[0064] User equipment (UE) determines whether a neighboring UE has received the current task orchestration information based on indications (such as hash values) broadcast by neighboring UEs. The UE compares the received hash value from the neighboring UE's broadcast with the hash value of its own currently received task orchestration information. If they match, it indicates that the neighboring UE has received the same task orchestration information as the current UE; if they do not match, it means that the neighboring UE has not yet received the current task orchestration information.

[0065] By including the device identity information of other user devices in the group in the task orchestration information, as well as the device identity information broadcast by surrounding user devices, user devices can accurately determine whether surrounding user devices belong to their own group. This avoids the erroneous transmission of information between devices in different groups, ensures that task information is only synchronized and shared within the relevant groups, and improves the accuracy and security of information transmission.

[0066] By employing algorithms such as hash values ​​to process task orchestration information, the system can quickly determine the task reception status of surrounding user devices. Compared to directly transmitting the entire task orchestration information for comparison, this significantly reduces data transmission volume and computational complexity, thereby improving system operating efficiency.

[0067] By 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 in the satellite network during task distribution, further improving the success rate of cloud platform-distributed device grouping tasks, and enhancing the reliability and stability of the entire system.

[0068] In some embodiments, the task orchestration information further includes device identity information of other user devices within the group to which the user device belongs. Monitoring surrounding user devices located near the user device includes: broadcasting device information of the user device to the surrounding area of ​​the user device, the device information including indication information indicating that the user device has received the task orchestration information, the indication information causing surrounding user devices located near the user device that have not yet received the task orchestration information to initiate a request to obtain the task orchestration information; receiving the device information broadcast by the surrounding user devices, the device information including the device identity information of the surrounding user devices and the request to obtain the task orchestration information; determining whether the surrounding user devices belong 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; and determining, based on the request to obtain the task orchestration information, that the surrounding user devices have not yet received the task orchestration information.

[0069] As an alternative implementation to the aforementioned embodiments, the user equipment can broadcast its own information. After receiving task orchestration information from the cloud platform, the user equipment broadcasts its own device information to its surroundings. This device information includes indications that the user equipment has received the task orchestration information, such as the hash value of the currently received task orchestration information. By broadcasting the indication that it has received the task orchestration information, surrounding devices that have not yet received the information can be notified and are triggered to initiate requests to obtain the task orchestration information.

[0070] Nearby user equipment (UE) receives broadcast information from other UE and retrieves indicative information such as hash values. The UE compares the received hash value with the hash value of its most recently received task orchestration information. If they match, it means the UE has already received the current task orchestration information and does not need to initiate a request to retrieve it. If they do not match, it means the UE has not yet received the current task orchestration information and needs to initiate a request to retrieve it.

[0071] Nearby user devices (that have not yet received task orchestration information) will broadcast their own device information, including their device identity information and a request to obtain task orchestration information. This allows user devices to identify nearby devices that need to obtain task orchestration information and further determine whether these devices belong to the same group.

[0072] The user equipment (UE) receives device information broadcast by nearby UEs, including device identity information and requests for task orchestration information. The UE compares the device identity information of other UEs, contained in the task orchestration information distributed by the cloud platform, with the received device identity information of the nearby UEs. If they match, it means the nearby UE belongs to the same group as the UE; otherwise, it does not belong to the same group. Because the nearby UEs broadcast requests for task orchestration information, the UE can directly determine that the nearby UEs have not yet received the current task orchestration information.

[0073] When determining their own task reception status, surrounding user equipment only needs to perform a simple hash value comparison operation, without frequently sending large amounts of data to the user equipment to prove whether they have received the task orchestration information. A retrieval request is only initiated when it is determined that the information has not been received, thereby effectively reducing communication overhead and improving system resource utilization.

[0074] In some embodiments, determining whether a nearby user device belongs to the user device's group 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 matches the device identity information of one of the other user devices, determining that the surrounding user device belongs to the user device's group; and in response to the comparison indicating that the device identity information of the surrounding user device does not match the device identity information of any of the other user devices, determining that the surrounding user device does not belong to the user device's group.

[0075] The user device compares the device identity information of 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 can be used for comparison.

[0076] If, during the comparison process, the device identity information of a nearby user device is found to be completely consistent with the device identity information of any other user device in the group, then the user device determines that the nearby user device belongs to its own group. If the device identity information of a nearby user device is inconsistent with the device identity information of any other user device in the group, then the user device determines that the nearby user device does not belong to its own group.

[0077] By strictly comparing device identity information, 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 orchestration information further includes device identity information of other user devices within the group to which the user device is located, and synchronizing the group information to the surrounding user devices includes synchronizing 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 listening and synchronization operations.

[0079] After receiving task orchestration information from the cloud platform, the user device will synchronize the group information and device identity information of other user devices in the group to nearby user devices within the same group. Synchronization can be achieved using short-range communication technologies such as Bluetooth, WiFi, or ZigBee.

[0080] After receiving group information and device identity information from other user devices synchronized by nearby user devices, the surrounding user devices can perform listening and synchronization operations. For example, by listening to the surrounding environment to obtain information or status of other relevant devices, the surrounding user devices can synchronize tasks with other devices based on the group information and device identity information of other user devices. This process is the same as the listening and synchronization process of the user devices described above, and will not be elaborated here.

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

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

[0083] After receiving task orchestration information (including group information) from the cloud platform, the user equipment's internal communication module begins operation, preparing to establish short-range communication connections with surrounding user equipment. The user equipment can select a suitable 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, the user equipment can send Bluetooth BLE broadcasts and listen for Bluetooth BLE broadcasts sent by other devices; the Bluetooth BLE broadcasts will carry the device's own device information. As another example, under a Wi-Fi network, the user equipment can send COAP broadcasts to other devices on the Wi-Fi network and listen for COAP broadcasts sent by other devices; the COAP broadcasts will carry the device's own device information.

[0084] After a user equipment (UE) successfully establishes a data channel with surrounding UEs via a short-range communication protocol, the UE encapsulates group information (such as device information and task information within the group) according to the communication protocol format and then sends it to the surrounding UEs via the data channel. The surrounding UEs receive the group information, parse it, and store it.

[0085] Short-range communication protocols typically feature rapid connection establishment, enabling the rapid creation of data channels and ensuring timely transmission of group information to nearby user devices. They offer high stability and reliability in short-range communication, guaranteeing that group information is not lost or corrupted during transmission. Short-range communication protocols generally do not require complex network infrastructure, resulting in lower communication costs and relatively lower power consumption, thus extending device battery life. Furthermore, short-range communication is not limited by geographical location or network coverage, allowing user devices to flexibly establish communication connections with nearby user devices based on actual needs, achieving synchronization of group information.

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

[0087] After a user equipment (UE) successfully establishes a data channel with nearby UEs via a short-range communication protocol, the two sides will exchange device information. Nearby UEs will send a message containing their own device information, including their public key. The UE then uses the nearby UE's public key to encrypt the task orchestration information. The encryption process transforms the original task orchestration information into a ciphertext format that can only be decrypted by devices possessing the corresponding private key.

[0088] User equipment (UE) sends encrypted task orchestration information to surrounding UEs via the established data channel. Upon receiving the encrypted information, the surrounding UEs can use their stored private key corresponding to the public key to decrypt the encrypted task orchestration information, thereby obtaining the original task orchestration information.

[0089] By encrypting task orchestration information using the public key of the surrounding user devices, only the surrounding user devices with the corresponding private key can decrypt the information, effectively preventing the leakage of task orchestration information during transmission and thus ensuring the security of information transmission.

[0090] In some embodiments, before receiving task orchestration information sent by the cloud platform via the satellite network, the method further includes: generating a public key and a private key pair 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 from the cloud platform via the satellite network, user equipment (UE) needs to connect to the satellite network. This mainly involves the satellite communication module within the UE establishing a connection with the satellite and completing operations such as signal acquisition, tracking, and synchronization. Once the UE successfully connects to the satellite network, its internal security module generates a public and private key pair. Key generation algorithms, such as RSA or elliptic curve cryptography, can be used to ensure the generated key has sufficient security and uniqueness.

[0092] User equipment encapsulates its own device identity information (such as device number, device type, device location, etc.) and the generated public key into a format that conforms to the satellite communication protocol, uploads it to the cloud platform through the satellite network, and securely stores the generated private key in the local storage module so that when it receives encrypted task orchestration information synchronized from other devices, it can directly use the locally stored private key to decrypt it.

[0093] After the user equipment uploads its public key to the cloud platform, the cloud platform can use this public key to encrypt the information when issuing task orchestration information to the user equipment. Only user equipment with the corresponding private key can decrypt this information, thus ensuring the security of information during transmission over the satellite network. Furthermore, because the private key is stored locally on the user equipment and kept strictly confidential, only legitimate user equipment can use the private key to perform correct digital signature and decoding operations. This makes it difficult for malicious devices to impersonate legitimate devices to access the satellite network and cloud platform, improving system security.

[0094] For ease of understanding of the above embodiments, as Figure 4 The diagram illustrates a task orchestration and deployment process based on a satellite network, as shown in this embodiment. It mainly includes the following steps:

[0095] 1. When a user device connects to the cloud platform, it will upload its device identity information, such as the serial number (SN), and generate a public-private key pair. The private key is stored locally on the device, while the public key is uploaded to the cloud platform along with the identity information.

[0096] 2. The cloud platform will use the satellite network to send the group information of each user device, as well as 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).

[0097] 3. Device B (Device D) can send Bluetooth BLE broadcasts and listen to Bluetooth BLE broadcasts sent by other devices. The Bluetooth BLE broadcasts will carry the device's own device information. Alternatively, Device B (Device D) can send COAP broadcasts to other devices on a Wi-Fi network and listen to COAP broadcasts sent by other devices. The COAP broadcasts will carry the device's own device information. In this way, Device B (Device D) can perceive which devices are present in the vicinity through short-range communication methods such as Bluetooth BLE and Wi-Fi.

[0098] 4. After receiving the grouping information from the cloud platform, Device B (D) will combine the information of surrounding devices sensed through short-range methods such as Bluetooth and WIFI in step [3] to determine whether the surrounding devices are devices within the group information.

[0099] 5. If a nearby user device is detected to be another device within the current group, data exchange will occur via short-range protocols such as Bluetooth BLE or Wi-Fi. For example, a Bluetooth channel will be established via Bluetooth BLE, or a TCP data channel will be established via Wi-Fi to synchronize the group information. The data synchronization process uses the peer's public key for encryption to ensure the security of data transmission.

[0100] 6. After receiving group information from nearby user devices via short-range communication, the device will continue to detect whether there are other devices in the group information in its vicinity, and then perform the operations in steps [3]-[5].

[0101] 7. Devices within the group will transmit the information in the manner described in steps [3]-[6] until all user devices within the group have correctly received the group information.

[0102] In practical business scenarios, user devices requiring orchestration typically appear in clusters, capable of discovering each other within a short range. This disclosure improves the success rate of cloud platform-deployed device grouping tasks by increasing the short-range deployment of grouping tasks. For example, in scenarios where multiple devices, such as broadband terminals, narrowband handheld devices, and narrowband IoT devices, collaborate and need to synchronize critical data (e.g., access permissions to a key service), while broadband bandwidth offers good performance and a higher success rate, narrowband IoT has limited bandwidth and resources, resulting in a lower success rate. Since short-range technologies and hardware are relatively mature, the solution disclosed in this disclosure effectively addresses the success rate of multiple devices receiving cloud-deployed group information in such scenarios.

[0103] The disclosed embodiments also provide a task orchestration information distribution device 500, such as... Figure 5 The diagram shows a schematic representation of a task orchestration information distribution device 500 in this embodiment of the present disclosure. The device 500 includes a receiving unit 510, a listening unit 520, and a synchronization unit 530, wherein:

[0104] At the user equipment:

[0105] The receiving unit 510 is used to receive task scheduling information sent by the cloud platform through the satellite network. The task scheduling information includes group information for all user devices in the group to which the user device is located.

[0106] The listening unit 520 is configured to, in response to receiving the task orchestration information, listen to the 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 orchestration information.

[0107] Synchronization unit 530 is configured to, in response to determining that the surrounding user equipment belongs to the group to which the user equipment belongs and that the surrounding user equipment has not yet received the task orchestration information, at least synchronize the group information to the surrounding user equipment.

[0108] In some embodiments, the task orchestration information further includes device identity information of other user devices within the group to which the user device belongs. The monitoring unit 520 is specifically configured to: receive device information broadcast by the surrounding user devices, wherein 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 orchestration information; determine whether the surrounding user devices belong 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; and determine whether the surrounding user devices have received the task orchestration information based on the indication information indicating whether the surrounding user devices have received the task orchestration information.

[0109] In some embodiments, the task orchestration information further includes device identity information of other user devices within the group to which the user device belongs. The monitoring unit 520 is specifically configured to: broadcast device information of the user device to the vicinity of the user device, the device information including indication information indicating that the user device has received the task orchestration information, the indication information causing nearby user devices located near the user device that have not yet received the task orchestration information to initiate a request to obtain the task orchestration information; receive the device information broadcast by the nearby user devices, the device information including the device identity information of the nearby user devices and the request to obtain the task orchestration information; determine whether the nearby user devices belong 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 nearby user devices; and determine that the nearby user devices have not yet received the task orchestration information based on the request to obtain the task orchestration information.

[0110] In some embodiments, the monitoring unit 520 is specifically configured to: compare the device identity information of the surrounding user device with the device identity information of 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, determine 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, determine that the surrounding user device does not belong to the group to which the user device belongs.

[0111] In some embodiments, the task orchestration information further includes device identity information of other user devices in the group to which the user device is located. 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, so as to allow the surrounding user devices to perform the listening and synchronization operations.

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

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

[0114] In some embodiments, the apparatus 500 further includes: a generation unit, configured to generate a public key and a private key pair when accessing the satellite network before receiving task orchestration information issued by the cloud platform via the satellite network; an upload unit, configured to upload the device identity information of the user device and the public key to the cloud platform; and to store the private key locally on the user device.

[0115] The task orchestration information distribution device described above can implement each step of the task orchestration information distribution method provided in the foregoing embodiments. The relevant explanations of the task orchestration information distribution method are applicable to the task orchestration information distribution 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 functions of the units discussed herein may be divided into multiple units, and / or at least some functions of multiple units may be combined into a single unit. The specific unit performing an action discussed herein 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). Therefore, a specific unit performing an action may include the specific unit performing the action itself and / or another unit that performs the action, called or otherwise accessed by the specific unit.

[0117] It should also be understood that this article can describe various technologies in the general context of software and hardware components or program units. The above regarding... Figure 5The described units can be implemented in hardware or in hardware in combination with software and / or firmware. For example, these units can be implemented as computer program code / instructions configured to execute in one or more processors and stored in a computer-readable storage medium. Alternatively, these units can be implemented as hardware logic / circuit.

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

[0119] This disclosure also provides a computer program product, including instructions that, when executed individually or jointly by at least one processor of a computing device, cause the computing device to perform the above-described synchronization signal detection method.

[0120] This disclosure also provides a chip, which includes a circuit system configured to perform the above-described task orchestration information distribution method. It should be noted that the circuit system may be an application-specific integrated circuit (ASIC), a general-purpose processor, or a combination thereof.

[0121] This disclosure also provides a computing device including the chip described above.

[0122] Figure 6 This is a simplified block diagram of a task orchestration information distribution device 600 suitable for implementing embodiments of the present disclosure. (See diagram below.) Figure 6 As shown, the task orchestration information distribution 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] Communication module 640 is used for bidirectional communication. Communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0124] Processor 610 can be of any type suitable for the local technology network, and as a non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Task orchestration information distribution device 600 can have multiple processors, such as application-specific integrated circuit (ASIC) chips, which are timely driven to a clock that synchronizes with the main 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 disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist during power-off periods.

[0126] Computer program 630 includes computer-executable instructions that are executed by a 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 embodiments of this disclosure can be implemented via program 630, enabling the task orchestration information distribution device 600 to execute reference... Figure 1 Any process disclosed herein. Embodiments of this disclosure may also be implemented in hardware or by a combination of software and hardware.

[0128] In some embodiments, program 630 may be tangibly contained in a computer-readable medium, which may be contained in a task scheduling information delivery device 600 (e.g., memory 620) or other 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 and base station devices (e.g., ground base stations or satellite network devices). Devices capable of implementing the above-mentioned synchronization signal detection method are all within the scope of protection of this disclosure.

[0130] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others 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 this disclosure are shown and described as block diagrams, flowcharts, or other graphical representations, 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 circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0131] This 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 included in program modules, which execute 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 as needed among program modules. The machine-executable instructions for the program modules can execute within a local or distributed device. In a distributed device, the program modules can reside in both local and remote storage media.

[0132] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, partially on a remote machine, partially on a remote machine, or entirely on a remote machine or server as a standalone software package.

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

[0134] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0135] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that these operations be performed in the specific order or sequence shown, or that all of the operations shown be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

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

[0137] It should be fully understood that the use of personally identifiable information should comply with privacy policies and practices generally considered to meet or exceed industry or governmental requirements for protecting user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

Claims

1. A method for task orchestration information delivery, comprising: at a user device: receiving task orchestration information delivered by a cloud platform through a satellite network, the task orchestration information comprising group information for all user devices in a group in which the user device is located; in response to receiving the task orchestration information, listening to peripheral user devices located in a periphery of the user device to determine whether the peripheral user devices belong to the group in which the user device is located and whether the peripheral user devices have received the task orchestration information; in response to determining that the peripheral user devices belong to the group in which the user device is located and that the peripheral user devices have not received the task orchestration information, synchronizing at least the group information to the peripheral user devices.

2. The method of claim 1, wherein, the task orchestration information further comprises device identity information of other user devices in the group in which the user device is located, and the listening to peripheral user devices located in a periphery of the user device comprises: receiving device information broadcast by the peripheral user devices, the device information of the peripheral user devices comprising device identity information of the peripheral user devices and indication information indicating whether the peripheral user devices have received the task orchestration information; determining whether the peripheral user devices belong to the group in which the user device is located according to the device identity information of the other user devices and the device identity information of the peripheral user devices; determining whether the peripheral user devices have received the task orchestration information according to the indication information indicating whether the peripheral user devices have received the task orchestration information.

3. The method of claim 1, wherein, the task orchestration information further comprises device identity information of other user devices in the group in which the user device is located, and the listening to peripheral user devices located in a periphery of the user device comprises: broadcasting device information of the user device to a periphery of the user device, the device information of the user device comprising indication information indicating that the user device has received the task orchestration information, the indication information causing peripheral user devices located in the periphery of the user device and having not received the task orchestration information to initiate a request for obtaining the task orchestration information; receiving device information broadcast by the peripheral user devices, the device information of the peripheral user devices comprising device identity information of the peripheral user devices and the request for obtaining the task orchestration information; determining whether the peripheral user devices belong to the group in which the user device is located according to the device identity information of the other user devices and the device identity information of the peripheral user devices; determining that the peripheral user devices have not received the task orchestration information according to the request for obtaining the task orchestration information.

4. The method of claim 2 or 3, wherein, the determining whether the peripheral user devices belong to the group in which the user device is located according to the device identity information of the other user devices and the device identity information of the peripheral user devices comprises: comparing the device identity information of the peripheral 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 peripheral user device is consistent with the device identity information of a user device among the other user devices, determining that the peripheral user device belongs to the group in which the user device is located; in response to the comparison indicating that the device identity information of the peripheral user device is inconsistent with the device identity information of any user device among the other user devices, determining that the peripheral user device does not belong to the group in which the user device is located.

5. The method of claim 2 or 3, wherein, The task orchestration information further includes device identity information of the other user devices within the group in which the user device is located, and the at least synchronizing the group information to the peripheral user device includes: synchronizing the device identity information of the other user devices and the group information to the peripheral user device to allow the peripheral user device to perform the listening and the synchronizing operations.

6. The method of any one of claims 1 to 3, wherein, The at least synchronizing the group information to the peripheral user device includes: establishing a data channel with the peripheral user device through a short-range communication protocol; sending at least the group information to the peripheral user device via the data channel.

7. The method of claim 6, wherein, The sending at least the group information to the peripheral user device via the data channel includes: obtaining a public key of the peripheral user device from device information of the peripheral user device; encrypting the task orchestration information using the public key to obtain encrypted task orchestration information; sending the encrypted task orchestration information to the peripheral user device via the data channel.

8. The task scheduling information issuing method according to any one of claims 1 to 3, wherein, Before receiving the task orchestration information issued by the cloud platform through the satellite network, the method further includes: generating a pair of public and private keys when accessing the satellite network; uploading device identity information of the user device and the public key to the cloud platform; storing the private key locally on the user device.

9. A task orchestration information issuing apparatus, comprising: At a user device: a receiving unit configured to receive task orchestration information issued by a cloud platform through a satellite network, the task orchestration information including group information for all user devices within a group in which the user device is located; a listening unit configured to, in response to receiving the task orchestration information, listen to peripheral user devices located in a periphery of the user device to determine whether the peripheral user devices belong to the group in which the user device is located and whether the peripheral user devices have received the task orchestration information; a synchronizing unit configured to, in response to determining that the peripheral user devices belong to the group in which the user device is located and that the peripheral user devices have not received the task orchestration information, at least synchronize the group information to the peripheral user devices.

10. A task orchestration information issuing device, comprising: one or more processors; and one or more memories coupled to the one or more processors and storing instructions thereon that, when executed by the one or more processors alone or collectively, cause the task orchestration information issuing device to perform the method of any one of claims 1-8.

11. A non-transitory computer-readable storage medium storing machine-executable instructions that, when executed by one or more processors in a task orchestration information issuance device, alone or in combination, cause the task orchestration information issuance device to perform the method of any of claims 1-8.

12. A computer program product comprising machine-executable instructions that, when executed by one or more processors in a task orchestration information issuance device, alone or in combination, cause the task orchestration information issuance device to perform the method of any of claims 1-8.

Images