A communication method and communication device

Abstract

This application provides a communication method and a communication device. For example, the method is applicable to fixed-point collaborative monitoring scenarios. In this method, a first terminal device within a first area sends first status information to a network device. The first status information indicates whether the first terminal device has an upload task and whether it has upload capability within the current control window. Subsequently, the network device sends first permission information to the first terminal device. The first permission information indicates the upload permissions for the first area and the target device within the first area. The upload permissions and the target device are determined based on the first status information. The target device is a terminal device that has an upload task within the current control window and is allowed to execute the upload task. This method can filter devices executing upload tasks by setting upload permissions and target devices, thereby reducing resource contention among terminal devices and improving task completion rate.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and communication device. Background Technology

[0002] In wide-area infrastructure scenarios such as bridges, highway corridors, wind farms, and pipelines, a large number of widely distributed ultra-low-power terminals (such as passive terminals) are often used to perform environmental sensing tasks in order to monitor the environment of the corresponding scenarios. These environmental sensing tasks may include collecting and reporting environmental information such as temperature, wind speed, and humidity.

[0003] In related technologies, ultra-low power terminals collect environmental information and then upload it to nearby base stations. However, the process of each terminal uploading environmental information is independent, which can easily lead to resource contention and thus affect the efficiency of information transmission. Summary of the Invention

[0004] This application provides a communication method and a communication device for controlling whether a terminal device uploads information from a regional perspective, which can avoid multiple terminal devices competing for resources and improve the efficiency of information transmission.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions: Firstly, this application provides a communication method, which can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example.

[0006] The method includes: a network device receiving first status information sent by a first terminal device within a first area; wherein the first status information is used to indicate whether the first terminal device has an upload task and whether it has upload capability within the current control window, and the first area includes one or more first terminal devices.

[0007] The network device sends first permission information to the first terminal device. The first permission information includes a first target device set, which includes target devices within a first area. The target devices are associated with first status information. The target devices are terminal devices that have upload tasks in the current control window and are allowed to execute upload tasks.

[0008] In this application, the network device can perceive whether the first terminal device has an upload task and whether it has upload capability within the current control window based on the first status information reported by the first terminal device. It can then further filter out terminal devices (i.e., target terminals) that can upload tasks from among the first terminal devices. This avoids multiple terminal devices blindly competing for resources within the same control window, improves the success rate of task uploads, and reduces energy waste caused by repeated transmissions. Furthermore, the upload permission for the first area is actually the upload permission for terminal devices within the first area. That is, the network device can determine the upload permission of terminal devices based on the area dimension. This avoids terminal devices uploading critical / minor information simultaneously competing for resources, thereby reducing resource contention.

[0009] Secondly, a communication method is provided, which can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this method. The following description uses a terminal device (such as a base station) as an example.

[0010] The method includes: a first terminal device can send first status information to a network device, the first status information being used to indicate whether the first terminal device has an upload task and whether it has upload capability in the current control window.

[0011] Subsequently, the first terminal device receives first permission information from the network device. This first permission information is used to indicate the upload permission of the first area and the target device within the first area. The upload permission and the target device are determined based on the first status information. The target device is a terminal device that has an upload task in the current control window and is allowed to execute the upload task.

[0012] Thirdly, a communication device is provided. The communication device includes a processing module and a transceiver module. The transceiver module is used to receive first status information sent by a first terminal device, wherein the first status information indicates whether the first terminal device has an upload task and whether it has upload capability within the current control window, and the first terminal device is a terminal device located within a first area.

[0013] This processing module is used to determine the first license information based on the first status information.

[0014] The transceiver module is also used to send first permission information to the first terminal device. The first permission information indicates the upload permissions for the first area and the target device within the first area. The upload permissions and the target device are determined based on first status information, whereby the target device is a terminal device that has an upload task within the current control window and is permitted to execute the upload task.

[0015] Fourthly, a communication device is provided. The communication device includes a processing module and a transceiver module.

[0016] This processing module is used to determine the first status information. The first status information indicates whether the first terminal device has an upload task and whether it has upload capability within the current control window; the first terminal device is a terminal device located within a first area. The transceiver module is used to send first status information to the network device and to receive first permission information from the network device; wherein the first permission information is used to indicate the upload permission of the first area and the target device in the first area, the upload permission and the target device are determined according to the first status information, and the target device is a terminal device that has an upload task in the current control window and is allowed to execute the upload task.

[0017] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0018] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0019] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0020] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0021] In one implementation, the communication interface can be a transceiver, or an input / output interface.

[0022] In another implementation, the communication device is a chip configured in a base station. When the communication device is a chip configured in a base station, the communication interface can be an input / output interface.

[0023] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and to transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0024] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0025] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0026] Optionally, the processor may be one or more, and the memory may be one or more.

[0027] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0028] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.

[0029] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0030] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0031] In a twelfth aspect, a communication system is provided, including the aforementioned first terminal device and network device. Optionally, the communication system may further include other devices that communicate with the first terminal device and / or the network device.

[0032] It is understood that any of the communication devices, communication systems, chip systems, processors, computer-readable storage media or computer program products provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the communication methods provided in the first aspect, and will not be repeated here. Attached Figure Description

[0033] Figure 1 A scenario diagram provided for an embodiment of this application; Figure 2 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application. Figure 3 One of the flowcharts of a communication method provided in this application embodiment; Figure 4 A second schematic flowchart illustrating a communication method provided in an embodiment of this application; Figure 5 A third schematic flowchart illustrating a communication method provided in an embodiment of this application; Figure 6 A schematic diagram of the structure of a communication device provided in this application embodiment. Figure 1 ; Figure 7 A schematic diagram of the structure of a communication device provided in this application embodiment. Figure 2 . Detailed Implementation

[0034] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0035] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0036] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0037] In wide-area infrastructure scenarios such as bridges, highway corridors, wind farms, and pipelines, a large number of widely distributed and fixed-location ultra-low-power terminals (such as passive terminals) are often used to perform environmental perception tasks in order to monitor the environment of the corresponding scenarios.

[0038] The communication system will be introduced below using a bridge monitoring scenario as an example. Figure 1 As shown, in a bridge monitoring scenario, passive terminal 101 can communicate with base station 103, and passive terminal 102 can communicate with base station 103 through collaborative node 104. Passive terminal 101 is deployed in the bridge monitoring area, such as on bridge piers. Passive terminal 102 is deployed in the pipeline monitoring area, such as beneath pipelines. Passive terminals 101 and 102 can specifically be passive sensor tags.

[0039] Passive terminals 101 and 102 can be used to collect environmental information such as temperature, humidity, and wind speed, and upload the environmental information to base station 103 when there is sufficient energy.

[0040] However, the energy of passive terminals 101 and 102 depends on environmental data collection and is unstable, causing upload capabilities to fluctuate over time. For example, during the day when sunlight is strong, more energy can be collected, sufficient to upload environmental information. In the evening when light is weak, less energy can be collected, insufficient to upload environmental information. This can easily lead to situations where the terminal has an upload need but its energy does not support the upload, making it difficult to guarantee timely and reliable information uploads. Furthermore, due to energy instability, the upload process may be interrupted, potentially causing information loss and duplicate transmissions.

[0041] Furthermore, the processes by which passive terminal 101 and passive terminal 102 upload environmental information to base station 103 are independent of each other. When wireless resources are limited, resource competition and retransmission of environmental information in the event of information failure may occur, thereby affecting the information transmission efficiency.

[0042] To at least address the aforementioned issues, this application provides a communication method that can both avoid resource contention among multiple terminal devices and improve information transmission efficiency, and enable ultra-low power terminals to continuously and reliably upload data under unstable energy conditions.

[0043] This communication method can be applied to fixed-point collaborative monitoring scenarios. Fixed-point collaborative monitoring scenarios include bridge monitoring, pipeline monitoring, wind farm monitoring, fixed roadside terminal monitoring, forest safety monitoring, lake environment monitoring, hazardous chemical plant monitoring, urban utility tunnel monitoring, and power line monitoring. These scenarios all suffer from problems such as wide terminal distribution, unstable terminal energy supply, and fluctuating terminal upload capabilities over time.

[0044] The communication method provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 5th Generation (5G), 6th Generation (6G), or New Radio Access Technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networks. The technical solution provided in this application can also be applied to future communication systems, and this application does not limit its application in this regard.

[0045] Figure 2 This is a schematic diagram of a communication system 100 used in an embodiment of this application. The communication system 100 may include network devices, such as... Figure 2 The network device 110 is shown. The communication system 100 may also include terminal devices, such as... Figure 2 The terminal device 120 shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0046] Optionally, when the power of the terminal device 120 is insufficient to support communication with the network device 110, the terminal device 120 can also communicate with the network device 110 through the cooperating node 130. For example, in Figure 1 In the scenario shown, the passive terminal 102, due to its location at the lower end of the pipeline, collects insufficient energy and can communicate with the base station 103 through the cooperative node 104. The cooperative node 130 can be a controller area network (CAN) device, which is a device supporting the CAN bus protocol.

[0047] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G or 6G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, and base stations in future mobile communication systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be macro base stations, micro base stations, or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network devices. In this application, access network devices are referred to simply as network devices.

[0048] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0049] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. A wireless terminal device can refer to a device with data acquisition and wireless communication functions. Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, aircraft, hot air balloons, ships, robots, robotic arms, smart home devices, or ultra-low power terminals (e.g., passive terminals), etc. The embodiments of this application do not limit the form of the terminal device.

[0050] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0051] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on airplanes or balloons. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios. For example, access network devices and terminal devices can be deployed simultaneously on land; or, access network devices can be deployed on land and terminal devices can be deployed on water, etc., and so on.

[0052] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0053] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0054] Figure 3 This is a schematic diagram illustrating a communication method according to an embodiment of this application. It can be understood that... Figure 3 The first terminal device in the process can be Figure 2 The term 120 can refer to any terminal device 120, or it can refer to a device within a terminal device (such as a processor, chip, or chip system). Network devices can be... Figure 2 The term 110 can refer to any network device, or it can refer to a component (such as a processor, chip, or chip system) within an access network device. For example... Figure 3 As shown, the method includes the following steps: S301, the network device sends task configuration information to the first terminal device.

[0055] The first terminal device is located within the first area. It should be noted that, considering the possibility that some terminal devices within the first area may be unable to communicate with the network device due to insufficient power, the first terminal device can be any terminal device within the first area that is capable of communicating with the network device. Thus, the first area can include one or more first terminal devices. In other words, regardless of whether the first area includes one or more first terminal devices, the network device can send task configuration information to each first terminal device within the first area. Correspondingly, each first terminal device within the first area can receive this task configuration information.

[0056] In this embodiment, the terminal device is used to monitor environmental parameters at fixed locations such as bridges, pipelines, fixed wind turbines, and fixed roadside structures; the location of the terminal device remains unchanged. Based on this, the network device can pre-establish a correspondence between regions and terminal devices, facilitating subsequent management of terminal devices at the region level.

[0057] During the installation and deployment of terminal equipment, the terminal equipment can send its own location information, such as its Global Navigation Satellite System (GNSS) location, to the network equipment. In this way, the network equipment can establish a correspondence between the region and the terminal equipment based on the terminal equipment's location information and preset regional boundaries.

[0058] by Figure 1 Taking the scenario shown as an example, the network device can store the area boundaries of the bridge detection area and the pipeline detection area. After receiving GNSS position 1 from passive terminal 101, the network device can determine that GNSS position 1 is located within the bridge detection area, and thus establish a correspondence between passive terminal 101 and the bridge detection area. After receiving GNSS position 2 from passive terminal 102, the network device can determine that GNSS position 2 is located within the pipeline detection area, and thus establish a correspondence between passive terminal 102 and the pipeline detection area.

[0059] To facilitate management and retrieval of this correspondence, the relationship between the aforementioned regions and terminal devices can be presented in the form of "Region ID - Terminal ID". The Region ID is the region identifier, used to uniquely identify the region. The Terminal ID is the terminal identifier, used to uniquely identify the terminal device.

[0060] It should be noted that the embodiments in this application are only illustrated using the first region as an example. In reality, the network device can also send task configuration information to terminal devices in other regions (such as the second region).

[0061] Correspondingly, the first terminal device receives the task configuration information. This task configuration information may include a task template, control window period, and control window parameters. Optionally, the task configuration information may be encapsulated as radio resource control (RRC) signaling and sent to the first terminal device in the form of RRC signaling.

[0062] Task templates can be used to indicate the parameters that the terminal device needs to collect, the method of collecting the parameters, and the sleep strategy, etc.

[0063] The control window cycle refers to the time interval between two adjacent control windows, which determines how often the terminal device can report data, such as the status codes mentioned later.

[0064] In this embodiment, the control window, also known as the task control cycle, refers to the logical time unit in which a network device completes one closed-loop control cycle. In one closed-loop control cycle, the network device must at least undergo the processes of state collection, permission generation, effective execution, and feedback update.

[0065] Control window parameters can include window length, control window period, and window offset. Window length refers to the duration of each control window. Window offset refers to the time slot delay of the control window relative to the system frame or time slot boundary. Setting the window offset ensures that all terminal devices enter the control window at the same boundary.

[0066] Taking a window length of T and a window offset of t0 as an example, the k-th control window can be represented as W(k) = [t0 + KT, t0 + (K+1)T].

[0067] S302, the first terminal device sends status information to the network device.

[0068] The status information indicates whether the terminal device has an upload task within the current control window, and whether it has the capability to upload within the current control window. The upload task instructs the terminal device to send task information to the network device; this task information may include information collected by the terminal device, such as temperature, humidity, and wind speed. Optionally, the status information sent by the first terminal device can also be referred to as first status information.

[0069] In one implementation, to reduce the bandwidth and energy used to transmit status information, the first terminal device can lightweight the status information into status codes. The status codes include an upload task identifier and an upload capability identifier. The upload task identifier indicates whether an upload task exists within the current control window, and the upload capability identifier indicates the terminal device's upload capability within the current control window.

[0070] Based on the content indicated by the status information, the status code can be defined as: S t (k) = (E) t (k), C t (k)). Among them, E t (k) is the upload capability identifier, representing the upload capability level of terminal device t in the k-th control window. C t (k) is the upload task identifier, indicating whether there is an upload task in the kth control window of the terminal device t.

[0071] Specifically, the task configuration information mentioned above may include status code rules, which the terminal device can use to generate status codes. The status code rules are as follows: If terminal device t does not have an upload task in the k-th control window, then C t (k) = 0; if terminal device t has an upload task in the k-th control window, then C t (k) = 1.

[0072] If terminal device t does not have upload capability in the k-th control window, then E t(k) = 0; if terminal device t has upload capability in the kth control window, then E t (k)≥1 (e.g., 1, 2, 3), and the stronger the upload capability of terminal device t in the k-th control window, the better E t The larger (k) is.

[0073] The upload capability of a terminal device can be correlated with its remaining energy; the more remaining energy a terminal device has, the stronger its upload capability. Conversely, a terminal device lacking upload capability means that its remaining energy is insufficient to support the sending of task information to the network device.

[0074] For example, if the first terminal device does not have upload capability in the current control window and there is no upload task, then the status code sent by the first terminal device is (0,0).

[0075] Conversely, network devices can also determine whether a terminal device has an upload task and whether it has upload capability within the current control window based on the status code. For example, if the status code sent by the first terminal device is (1,2), it indicates that the first terminal device has upload capability and an upload task exists within the current control window.

[0076] Furthermore, based on status codes, network devices can classify terminal devices into the following categories: (1) No-task device: A terminal device that currently has no upload task, i.e., meets the condition C. t Terminal devices with (k) = 0.

[0077] (2) Devices to be restored: Terminal devices that currently have upload tasks but do not have stable upload capabilities within the current control window, i.e., those that meet the criteria C. t (k) = 1 and E t Terminal devices with (k) = 0.

[0078] (3) Candidate devices: Terminal devices that currently have an upload task and have stable upload capabilities within the current control window, i.e., those that meet C t (k) = 1 and E t (k) ≥ 1 terminal device.

[0079] Among them, the devices to be restored and the candidate devices can also be collectively referred to as devices with tasks.

[0080] In this embodiment of the application, the aforementioned status code can be encapsulated as a medium access control (MAC) layer control element (CE) signaling and reported to the network device via the physical uplink shared channel (PUSCH) or the physical uplink control channel (PUCCH).

[0081] S303, the network device determines the upload permission parameters of the first area based on the status information of the first terminal device. The upload permission parameters of the first area are used to indicate the upload permissions of the first area.

[0082] Optionally, the upload permission parameters for the first region can also be called the first upload permission parameters. The upload permissions for the first region can also be understood as the upload permissions for all terminal devices within the first region, used to indicate whether a terminal device can upload task information and the content allowed to be uploaded from the task information.

[0083] Upload permissions can be categorized into three types: uploading only critical information, allowing uploading secondary information, and being ready to respond.

[0084] Understandably, task information can be categorized by content, including key information and secondary information. Key information is typically what is needed to ensure task execution, while secondary information is used to further refine the results.

[0085] The distinction between critical and secondary information depends on the specific application scenario. For example, in forest fire risk monitoring, temperature sensor data can be classified as critical information, while humidity, wind speed, and other auxiliary environmental information can be classified as secondary information. Similarly, in urban environmental monitoring, PM2.5 can be classified as critical information, while oxygen content, temperature, humidity, atmospheric pressure, and other information can be classified as secondary information.

[0086] If a terminal device has upload permissions that only allow uploading critical information, then the terminal device can upload the critical information to the network device.

[0087] If the terminal device has the permission to upload secondary information, then the terminal device can first upload the key information to the network device, and then upload the secondary information to the network device after all the key information has been uploaded.

[0088] If the terminal device has upload permissions for sensing and waiting, the terminal device cannot send task information to the network device.

[0089] Optionally, the upload permission parameters for the first area are also used to indicate the resource configuration guarantee and the maximum number of available devices in the first area. The resource configuration guarantee may include the available uplink rate and maximum retransmission count of the terminal devices. The maximum number of available devices refers to the number of terminal devices within the area that are allowed to upload task information to the network devices.

[0090] Considering that network devices will need to send the upload permission parameter to terminal devices in the future, network devices can reduce the upload permission parameter to an upload permission level.

[0091] Specifically, the task configuration information mentioned above may also include upload permission level information. This upload permission level information stores multiple upload permission levels and their corresponding upload permissions, resource configuration guarantees, and the maximum number of available devices. Thus, after receiving the upload permission level, the terminal device can query its own upload permissions, resource configuration guarantees, and the maximum number of available devices based on the upload permission level information.

[0092] Thus, network devices can enable terminal devices to determine their own upload permissions, resource configuration guarantees, and the maximum number of available devices while reducing the resources required to transmit upload permission parameters.

[0093] For example, upload permission level information can be presented in the table shown in Table 1: Table 1

[0094] As shown in Table 1, the upload permission level information includes three levels: C0, C1, and C2. Level C0 indicates that the upload permission is for uploading only critical information, with an available uplink speed of V1, a maximum retransmission count of M1, and a maximum number of available devices of N1. Level C1 indicates that the upload permission is for uploading secondary information, with an available uplink speed of V2, a maximum retransmission count of M2, and a maximum number of available devices of N2. Level C2 indicates that the upload permission is in a state of alert and standby, with an available uplink speed of V3, a maximum retransmission count of M3, and a maximum number of available devices of N3. Where V1 > V2 > V3, M1 > M2 > M3, and N1 < N2 < N3.

[0095] It should be noted that Table 1 is just an example. The upload permission level information can include more content than Table 1, and can also be presented in other ways besides tables. No specific restrictions are imposed here.

[0096] In this embodiment, the first upload permission parameter can be determined based on the upload pressure of the first region, and the upload pressure of the first region can be determined based on the status information of the first terminal device.

[0097] The higher the upload pressure in the first region, the stricter the upload permissions indicated by the first upload permission parameter.

[0098] For example, when the upload pressure in the first region is the first upload pressure, the first upload permission parameter indicates that the first region has the permission to upload critical information; when the upload pressure in the first region is the second upload pressure, the first upload permission parameter indicates that the first region has the permission to upload both critical and minor information; when the upload pressure in the first region is the third upload pressure, the first upload permission parameter indicates that the first region does not have the permission to upload information; wherein, the first upload pressure is greater than the second upload pressure, and the second upload pressure is greater than the third upload pressure.

[0099] In addition, the higher the upload pressure in the first region, the greater the available uplink rate and the maximum number of retransmissions indicated by the first upload permission parameter, and the smaller the maximum number of available devices.

[0100] The following is combined with Figure 4 Explain the process by which network devices determine the upload permission parameters for the first area. For example... Figure 4 As shown, S303 includes at least S3031 to S3033.

[0101] S3031, the network device calculates the pending upload ratio and blocked upload ratio of the first area.

[0102] The pending upload ratio indicates the percentage of terminals with upload tasks within a region, reflecting the workload within that region. A higher pending upload ratio indicates greater workload for that region.

[0103] Specifically, the required upload ratio can be calculated using formula 1: Equation 1; in, This indicates the upload ratio of region r in the k-th control window. This indicates the number of terminal devices within region r. This indicates the number of terminal devices with upload tasks within region r in the k-th control window.

[0104] In other words, for any given area (such as the first area mentioned above), the network device can count the number of all terminal devices within that area and obtain a count of 1. The network device can also count the number of devices within that area that satisfy C... t The number of terminal devices with (k) = 1 is obtained as quantity 2, which is the number of devices with tasks. Then, the ratio of quantity 2 to quantity 1 is used as the upload ratio for that area. Optionally, quantity 1 can also be called the third quantity, and quantity 2 can also be called the second quantity.

[0105] The blocked upload ratio represents the proportion of terminal devices within a region that have upload tasks but lack stable upload capabilities among all terminal devices with upload tasks. It reflects the degree of upload obstruction in the region. A higher blocked upload ratio indicates a greater degree of upload obstruction in the region.

[0106] Specifically, the blocked upload ratio can be calculated using formula 2: Equation 2; in, This represents the blocked upload ratio of region r in the k-th control window. This represents the number of terminal devices in region r that have upload tasks but lack upload capabilities within the k-th control window.

[0107] In other words, for any given area, network devices can also statistically analyze the conditions within that area that satisfy C. t (k) = 1 and E t The number of terminal devices with (k) = 0 is calculated to be 3, which is the number of devices to be restored. Then, the ratio of 3 to 2 is used as the blocked upload ratio for that area. Optionally, 3 can also be referred to as the first quantity.

[0108] S3032, the network device determines the upload pressure level of the first area based on the ratio of pending uploads and the ratio of blocked uploads in the first area.

[0109] Among them, network devices can first determine the upload pressure of the first area based on the ratio of pending uploads and the ratio of blocked uploads in the first area.

[0110] Among them, the ratio of pending uploads, the ratio of blocked uploads, and the upload pressure satisfy equation 3: Equation 3; in, For the upload pressure of region r in the k-th control window, The first weighting coefficient is set in advance. The second weighting coefficient is set in advance, and Optionally, .

[0111] Understandably, upload pressure The larger the value, the more concentrated the upload tasks are in region r during the k-th control window, and the more severe the situation where tasks cannot be sent out. Therefore, stronger collaborative control and higher upload security are required.

[0112] Then, the network device can determine the upload pressure level based on the range of upload pressure. The correspondence between upload pressure and upload pressure level satisfies equation 4: Equation 4; in, Let L0 be the upload pressure level of region r in the k-th control window, L1 be the preset first upload pressure level, L2 be the preset third upload pressure level, and L3 be the preset fourth upload pressure level, with the upload pressure corresponding to L0~L3 decreasing sequentially. For the preset first pressure threshold, For the pre-set second pressure threshold The third pressure threshold is set in advance, and .

[0113] S3033, the network device determines the upload permission level of the first area based on the upload pressure level of the first area.

[0114] In this embodiment, the upload pressure level and upload permission level satisfy equation 5: Equation 5; in, This indicates the upload permission level used by region r within the k-th control window. This function represents the mapping from upload pressure level to upload permission level.

[0115] In one implementation, the mapping relationship between upload pressure level and upload permission level is as follows: When the upload pressure level of region r is L0, it means that region r has a lot of upload tasks and a serious situation where tasks cannot be sent. In other words, the upload pressure of region r is high. Therefore, the network device can determine the upload permission level to C0, so that the terminal devices in region r can only upload critical information to perform more upload tasks and alleviate the region pressure.

[0116] When the upload pressure level is L1 or L2, it means that there are a small number of upload tasks in region r, or that the situation of having tasks but not being able to send them is not serious. In other words, the upload pressure in region r is average. Therefore, the network device can determine the upload permission level as C1, so that the terminal devices in region r can upload more information.

[0117] With an upload pressure level of L3, it means that the upload pressure in region r is relatively low. Therefore, the network device can determine the upload permission level as C2, so that the terminal devices in region r can only be aware of and stand by, in order to avoid competing for resources with terminal devices in other regions with high upload pressure.

[0118] It should be noted that the above mapping relationship can also be other, as long as it satisfies the requirement that the higher the upload pressure in a region, the less information the terminal devices in that region can upload (i.e., only important information is uploaded).

[0119] It should also be noted that the network device can receive status information from terminal devices within the second area and determine the upload permission level for that second area based on this information. In essence, when the network device receives status information from terminal devices in multiple areas, it can first determine the area to which the terminal belongs based on its terminal ID, and then use the method described above to determine the upload permission level for each area.

[0120] S304, The network device determines the target device in the first area based on the status information of the first terminal device.

[0121] The target device is a terminal device that is allowed to perform upload tasks, that is, a terminal device that can upload task information to the network device. It should be noted that in each area, only the target device in that area can upload task information to the network device. Other devices remain silent, meaning they cannot upload information to the network device, to reduce resource contention.

[0122] In one implementation, for region r, the target device for region r is the terminal device among all candidate devices in region r that satisfies the following two conditions: Condition 1: On-time arrival. On-time arrival means that the task information can reach the network device before the deadline.

[0123] Condition 2: The probability that the task information arrives at the network device on time (denoted as the on-time arrival probability) is greater than or equal to the target success probability.

[0124] Regarding condition 1 above, the network device can estimate the deadline and the expected arrival time of the task information. The expected arrival time refers to the time when the task information arrives at the network device, and the network device can determine whether condition 1 is met based on the deadline and the expected arrival time.

[0125] Taking the example of terminal device u generating or reporting task m in the kth control window, the deadline for task m can be calculated using formula 6: Equation 6; in, Let m be the deadline for task m. Let m be the base time corresponding to task m. This represents the maximum allowable delay for task m.

[0126] In this embodiment, the network device can configure a corresponding base time for task m of terminal device u based on the task type. The reference time can be one of the following three types of moments: the triggering time of task m, the moment when terminal device u reports status information, and the start time of the kth control window.

[0127] For example, for urgent tasks such as safety alarms, fault alarms, and equipment anomaly reports, the base time can be the trigger time of the task.

[0128] For example, for periodic tasks that are uniformly scheduled and processed in batches on the network side, such as periodic environmental monitoring tasks, the reference time can control the start time of the window or the time when the terminal device reports status information.

[0129] In addition, network devices can determine the maximum allowable latency based on task type, upload load level, Quality of Service (QoS) requirements, or task template. .

[0130] For example, urgent tasks correspond to smaller... Periodic tasks correspond to larger .

[0131] After determining the deadline for task m, the network device can further estimate the estimated arrival time of the task information based on current scheduling resources, the size of the task information, the upload capability level of terminal device m, the modulation and coding scheme (MCS), the maximum number of retransmissions, processing latency, the time reserved for each retransmission, and whether it is forwarded through a cooperating node. The estimated arrival time can be calculated using formula 7: Equation 7; in, For the estimated arrival time, For the current moment, The time to wait for the kth control window to schedule resources to take effect. For the estimated uplink transmission time, To handle latency, Allow time for retransmission.

[0132] Understandably, the expected uplink transmission time The time required for terminal device u to transmit task information to network device can be calculated based on the size of the task information and the available uplink rate of the kth control window. The available uplink rate of the kth control window can be associated with the upload capability level and MCS of terminal device m.

[0133] The processing latency mentioned above refers to the time required for the network device to receive and decode the information to be processed. Optionally, if the terminal device u needs to forward task information through a cooperating node, the processing latency also includes the time required for the cooperating node to receive and forward the task information.

[0134] The retransmission reservation time mentioned above can be determined based on the maximum number of retransmissions and the single retransmission reservation time, specifically it can be the product of the maximum number of retransmissions and the single retransmission reservation time.

[0135] Based on this, if If the estimated arrival time is less than or equal to the deadline, it means that the task information can reach the network device before the deadline, i.e., the terminal device meets condition 1.

[0136] like If the estimated arrival time is greater than the deadline, it means that the task information cannot reach the network device before the deadline, i.e., the terminal device does not meet condition 1.

[0137] Regarding condition 2 above, network devices can determine the success probability of the target based on the task type, the upload pressure level of the region where the terminal device is located, or pre-configured upload permission parameters. For example, the more urgent the task and the higher the upload pressure level of the region where the terminal device is located, the higher the success probability of the target should be.

[0138] Furthermore, network devices can also predict the probability of on-time arrival by combining factors such as current link quality, the upload capability level of the terminal device, historical reception success rate, available resources, maximum retransmission count, and whether forwarding occurs through cooperating nodes. Among these factors, the stronger the current link quality, the higher the upload capability level of the terminal device, the higher the historical reception success rate, the more available resources, the greater the maximum retransmission count, or the higher the probability of on-time arrival if forwarding occurs through cooperating nodes.

[0139] Then, the network device can compare the probability of on-time arrival with the probability of target success. If the probability of on-time arrival is greater than or equal to the probability of target success, the terminal device satisfies condition 2; if the probability of on-time arrival is less than the probability of target success, the terminal device does not satisfy condition 2.

[0140] In another implementation, for region r, the target device in region r can be the terminal device that meets conditions 1 and 2 and ranks in the top N in terms of comprehensive score among all candidate devices in region r. The comprehensive score reflects the probability of the terminal device's task information arriving on time and the urgency of the information uploaded by the terminal device.

[0141] In the process of determining the target device, the network device can first select all terminal devices that meet conditions 1 and 2 from all candidate devices in region r, and record them as backup devices.

[0142] Then, the network device can determine the overall score of the backup device based on its on-time arrival probability and the type of task information. A higher on-time arrival probability indicates a higher probability of the terminal device successfully uploading information, resulting in a higher overall score. If the task information includes important information, it indicates a higher urgency of the information being uploaded by the terminal device, further increasing the overall score.

[0143] Finally, the network device can sort the standby devices by their overall scores and select the top N terminal devices as the target devices for region r. N can be determined based on the upload permission level corresponding to region r and Table 1 above.

[0144] S305, the network device sends first permission information to the first terminal device. The first permission information includes upload permission parameters for the first area and a target device set, which includes target devices.

[0145] Considering that the network device can also determine the upload permission parameters of the second area and the target devices within the second area, the network device can generate a license information set and send the license information set to the first terminal device and the terminal devices within the second area. The license information set includes license information from multiple areas, such as the license information for the first area (i.e., the aforementioned first license information), and the license information for the second area. The license information for the second area may include the upload permission parameters for the second area and the set of target devices for the second area.

[0146] In one implementation, the first grant information can be encapsulated as downlink control information (DCI) signaling or configured grant (CG) signaling.

[0147] S306, the first terminal device determines the target upload permission based on the first license information.

[0148] Specifically, after receiving the first permission information, the first terminal device can determine whether it belongs to the target device set of its own region (i.e., the first region). If the first terminal device does not belong to the target device set of the first region, the target upload permission is set to "aware and ready".

[0149] If the first terminal device belongs to the target device set of the first region, the first terminal device can further determine the upload permission level of the first region (denoted as the target upload permission level), and then determine the upload permission corresponding to the target upload permission level as the target upload permission.

[0150] For example, if the upload permission level of the first area is C0, then the target upload permission is to upload only critical information.

[0151] For example, if the upload permission level of the first area is C1, then the target upload permission is to allow the upload of secondary information.

[0152] For example, if the upload permission level of the first area is C2, then the upload permission of the target is "aware and ready".

[0153] S307, the first terminal device sends first task information to the network device based on the target upload permission. The first task information is the task information for the first upload task, which is the upload task of the first terminal device.

[0154] When the target upload permission is set to upload only critical information, the first terminal device can send critical information to the network device within the current control window. However, if the first task information does not include critical information, the first terminal device will not send task information to the network device.

[0155] If the target upload permission allows uploading secondary information, the first terminal device can first send the key information to the network device within the current control window, and then send the secondary information to the network device. However, if the first task information does not include key information, the first terminal device can directly send the secondary information to the network device.

[0156] When the target upload permission is set to "Aware Standby", the first terminal device does not send task information to the network device within the current control window.

[0157] Understandably, while sending the first task information to the network device, the first terminal device can also simultaneously send its terminal ID and the area ID of the first area.

[0158] In one implementation, the first terminal device and the network device can confirm or deny whether the information transmitted in the current control window has been successfully decoded through a hybrid automatic repeat request.

[0159] Since terminal devices always prioritize uploading critical information, they may be unable to upload secondary information to network devices when terminal power is unstable or resources are limited. In this case, secondary information can be uploaded to network devices gradually according to the network device's permission and budget in subsequent control windows. Based on this, the communication method provided in this application may also include S308~S309.

[0160] S308, the network device determines the actual completion rate of the first upload task. The actual completion rate is the proportion of information that has reached the network device in the first upload task in the first task information.

[0161] S309, when the task completion rate is less than or equal to the target completion rate, the network device adds a gap information identifier to the first terminal device, which indicates that there is a gap task in the first terminal device.

[0162] Understandably, if the task completion rate is less than or equal to the target completion rate, it means that the first upload task has not yet reached the target completion state. Therefore, the network device can add a gap information identifier to the first terminal device.

[0163] In this embodiment, whether the terminal device has a gap information identifier can also affect the terminal device's overall score. Specifically, if the terminal device has a gap information identifier, it indicates that the device has an incomplete upload task within a control window, and the overall score is higher. Therefore, the probability that the terminal device will be identified as the target device in the next control window is greater, and the probability that the terminal device will continue to upload task information to the network device is also greater.

[0164] Optionally, the gap information identifier is also used to indicate the type, quantity, or summary of the incomplete uploaded information (also known as gap information) in the first task information. The gap information summary is, for example, a content summary of the gap information. Thus, the network device can determine the secondary information that can be re-uploaded in subsequent control windows based on the gap information identifier, the upload capacity of the terminal device, and the resource budget of the subsequent control window.

[0165] Meanwhile, to prevent the same task from consuming too many resources, the network device can continuously monitor the task completion rate of the first task across multiple control windows. If the task completion rate of the first task is less than or equal to the target completion rate across multiple consecutive control windows, and the number of control windows exceeds a first threshold, the network device can clear the missing information marker on the first terminal device. This avoids the problem of the first terminal device consuming excessive resources due to prolonged information uploading.

[0166] Understandably, S301~S302 can be understood as the process of network devices collecting status, S303~S304 can be understood as the process of network devices generating licenses, and S305~S309 can be understood as the process of license taking effect, execution, and feedback updates.

[0167] Considering that in real-world applications, there may be scenarios where terminal devices cannot directly connect to network devices. For example, a terminal device may be unable to collect sufficient energy due to a poor location, thus preventing a direct connection to the network device. Therefore, embodiments of this application may also introduce a cooperative node to forward information between the network device and the terminal device.

[0168] The following example uses a network device as a base station to illustrate the process of the base station controlling terminal device 1 and terminal device 2 to upload task information. Terminal device 1 is a terminal device in area 1 that can directly connect to the base station, while terminal device 2 is a terminal device in area 1 that cannot directly connect to the base station. Figure 5 As shown, the communication method provided in this application includes: S501, the base station sends task configuration information to terminal device 1 and terminal device 2.

[0169] S501 is the same as S301 mentioned above, and will not be described again here.

[0170] S502, the base station sends collaborative configuration information to the collaborative node.

[0171] The collaborative configuration information may include the correspondence between regions and terminal devices, caching / aggregation rules, secondary information gap grouping rules, and secondary information budgeting rules.

[0172] The correspondence between regions and terminal devices facilitates the base station in summarizing and abstracting the status codes of terminal devices within the same region.

[0173] Caching / aggregation rules are used to constrain the behavior of coordinating nodes in receiving, caching, aggregating, and forwarding information sent by nearby terminal devices. For example, caching / aggregation rules instruct coordinating nodes, upon receiving status codes, critical information, minor information, or gap information sent by terminal devices, to perform caching, deduplication, validity management, and digest generation according to the terminal device's identifier, task identifier, region identifier, and control window.

[0174] Taking status codes as an example, after receiving a status code sent by a terminal device, the coordinating node can perform statistical analysis based on the status code to obtain regional status information for at least one area. This regional status information includes the number of devices with tasks, the number of devices awaiting recovery, the number of candidate devices, and the device identifiers of the candidate devices in that area. Specifically, the number of devices awaiting recovery refers to the number of devices among the terminal devices that sent the status code to the coordinating node that are awaiting recovery; the number of candidate devices refers to the number of candidate devices among the terminal devices that sent the status code to the coordinating node; and the number of devices with tasks refers to the number of devices awaiting recovery and candidate devices among the terminal devices that sent the status code to the coordinating node.

[0175] Taking secondary information as an example, after receiving secondary information sent by a terminal device, the cooperating node can perform deduplication on the secondary information in the region to which the terminal device belongs, and count the number of secondary information to be sent in the region to which the terminal device belongs.

[0176] The minor information gap grouping rule is used to instruct collaborative nodes to divide the minor information that has not been uploaded into different gap groups according to information type, task type, importance, or order of completion.

[0177] Secondary information budget rules are used to limit the amount of resources, data, number of tasks, completion order, and stopping conditions that collaborative nodes can use to forward secondary information within one or more control windows, so that collaborative nodes can complete secondary information in a controlled manner while prioritizing the protection of critical information.

[0178] S503, Terminal device 1 sends status code 1 to the base station.

[0179] S504, Terminal device 2 sends status code 2 to the cooperating node.

[0180] S505, the cooperating node sends the region summary information of region 1 to the base station.

[0181] The details regarding the regional summary information are provided above and will not be repeated here.

[0182] It should be noted that the cooperating node can also receive status codes sent by other terminal devices. These other terminal devices may or may not belong to the same region as Terminal Device 2. When the cooperating node receives status codes from terminal devices belonging to different regions, the cooperating node can send region summary information for each region to the base station.

[0183] Taking the case where the cooperating node also receives the status code sent by the terminal device in region 2 as an example, the cooperating node can also generate and send the region summary information of region 2 to the base station.

[0184] S506, the base station determines the upload permission level 1 of region 1 based on the region summary information of region 1 and status code 1.

[0185] Understandably, terminal devices within the same area can send status codes directly to the base station or to cooperating nodes. Therefore, the base station needs to count the terminal devices that communicate directly with it, as well as those that report their status through cooperating nodes, in order to fully cover all terminal devices within the area and accurately assess the upload pressure in the area.

[0186] Therefore, when counting the number of task-bound devices within the statistical region r, the base station can use status code 1 to count the number of devices within the statistical region r that satisfy C. t The number of terminal devices (i.e., devices with tasks) with (k) = 1 is denoted as quantity 1. Additionally, the base station can obtain the number of devices with tasks in region r from the region summary information of region r. Thus, the sum of quantity 1 and the number of devices with tasks is the total number of all devices with tasks in region r, which is the second quantity mentioned above.

[0187] When determining the number of devices to be restored within the statistical region r, the base station can use status code 1 to count the number of devices within the statistical region r that satisfy C. t (k) = 1 and E tThe number of terminal devices (k) = 0 (i.e., devices to be restored) is denoted as quantity 2. The base station can obtain the number of devices to be restored in region r from the region summary information corresponding to region r. Thus, the sum of quantity 2 and the number of devices to be restored is the total number of all devices to be restored in region r, which is the third quantity mentioned above.

[0188] Finally, the base station can calculate the upload ratio and blocked upload ratio of region r based on the first quantity and the aforementioned second and third quantities, and further determine the upload pressure level of region r based on the upload ratio and blocked upload ratio of region r, and finally determine the upload permission level of region r based on the upload pressure level of region r.

[0189] S507, the base station determines the target device set 1 of region 1 based on the region summary information of region 1 and status code 1.

[0190] S507 is similar to S304, except that in this example, additional statistical region summary information is required to indicate the candidate devices.

[0191] First, the base station can determine candidate devices in terminal device 1 based on status code 1 to obtain candidate device set 1, the process of which is described in S304 and will not be repeated here. Next, the base station can also determine candidate devices in terminal device 2 based on area summary information to obtain candidate device set 2. Then, the base station can merge candidate device set 1 and candidate device set 2 in the same area to determine all candidate devices in that area. Finally, the base station can use the relevant information based on S304 to determine target device set 1 in area 1.

[0192] S508, the base station sends permission information 1 to the cooperating node and terminal device 1. Permission information 1 includes upload permission level 1 and target device set 1.

[0193] S509, the cooperating node sends the target upload permission level 1 to the terminal device 2. The target upload permission level 1 is determined based on the upload permission level 1 and whether the target device set 1 includes the terminal device 2.

[0194] After receiving permission information 1, the collaborating node can determine whether target device set 1 includes terminal device 2. If target device set 1 includes terminal device 2, it means that terminal device 2 is a target device in region 1, so the collaborating node can use upload permission level 1 as the target upload permission level for terminal device 2. If target device set 1 does not include terminal device 2, it means that terminal device 2 is not a target device in region 1, so the collaborating node can determine that the target upload permission level for terminal device 2 is C2.

[0195] It should be noted that the cooperating node can also receive permission information from other regions. S510, terminal device 2 sends task information 1 to the cooperating node based on target upload permission 1, and target upload permission level 1 corresponds to target upload permission 1.

[0196] Among them, terminal device 2 can query the target upload permission level 1 to obtain the target upload permission 1, and then send task information 1 to the cooperating node based on the target upload permission 1.

[0197] Optionally, if the terminal device 2 has sufficient power to support direct communication with the base station, the terminal device 2 can also directly send task information 1 to the base station based on the target upload permission 1.

[0198] S511, the cooperating node sends task information 1 to the base station.

[0199] S512, Terminal device 1 determines the target upload permission 2 based on license information 1.

[0200] Understandably, if the target device set 1 does not simultaneously include terminal device 1 and terminal device 2, the target upload permission 2 and the target upload permission 1 can be different.

[0201] S513, Terminal device 1 sends task information 2 to the base station based on target upload permission 2.

[0202] Understandably, by introducing collaborative nodes, information can be uploaded even when the uplink capability of terminal devices is insufficient, thereby improving the task completion rate within the region.

[0203] The following example, using a forest fire risk monitoring scenario, illustrates the communication method provided in this application. In the forest fire risk monitoring scenario, key information includes temperature information, and secondary information includes humidity information and wind speed information.

[0204] Step 1: Terminal device 3 reports a status code to the network device, indicating that terminal device 3 belongs to region 2.

[0205] Step 2: The network device determines that the upload permission level of area 2 in the current control window is C0, and the target device set 2 of area 2 includes terminal device 3.

[0206] Step 3: The network device sends license information 2 to the terminal device 3. License information 2 includes upload permission level C0 and target device set 2.

[0207] Step 4: Based on the target device set 2 including terminal device 3, terminal device 3 sends temperature information (critical information) to the network device within the current control window.

[0208] Step 5: The network device performs fire hazard warning processing based on temperature information.

[0209] Step 6: The network device determines that secondary information is still needed for fire hazard warning processing, and adds a gap information identifier to terminal device 3 so that terminal device 3 can continue to upload secondary information in the next control window.

[0210] Ultra-low power terminals typically rely on environmental energy harvesting or limited energy storage for operation, and their available energy fluctuates randomly over time, easily leading to insufficient current energy and unstable transmission. Related technologies employ an energy-neutral operation approach, dynamically adjusting sampling frequency, reporting frequency, transmission power, or retransmission count based on the terminal device's current energy harvesting amount, remaining energy, or long-term energy budget. This ensures that the terminal's long-term energy consumption does not exceed the harvested energy, thereby reducing the probability of communication failures due to insufficient energy.

[0211] This application introduces a status code reporting mechanism, enabling the network side to jointly perceive whether a terminal device has an upload task and whether it has the ability to upload. This allows the network device to distinguish between terminals without tasks, terminals awaiting recovery, and candidate terminals, and further select the terminal device (i.e., the target terminal) that should perform the upload task within the current control window from the candidate terminals. This achieves precise control, which can reduce the probability of communication failure due to insufficient energy, reduce ineffective scheduling and ineffective transmission, and reduce the air interface interaction overhead of ultra-low power terminals.

[0212] Furthermore, when faced with the problem of insufficient power or limited resources on terminal devices preventing the upload of task information, related technologies allow terminal devices to temporarily store the task information to be uploaded in a local cache and retry sending it when power is restored or the link becomes available. However, this method relies on the terminal device's own cache and subsequent retries, lacking unified aggregation and scheduling control of terminal status within the region on the network side. When multiple terminal devices simultaneously restore their upload capabilities at later times, issues such as concurrent contention, invalid retries, and insufficient protection for critical tasks may still occur. Additionally, such solutions typically do not distinguish between critical and secondary information, making it difficult to guarantee that critical information is uploaded on time with priority.

[0213] In this application, the network side can assess the upload pressure of a region, identify which regions have high task concentration and high upload obstruction levels, and thus configure stricter upload permission controls and stronger resource guarantees for those regions. In other words, this application achieves an improvement from single-terminal energy control to region-level task collaborative control, which can improve the upload success rate in regions with high upload pressure.

[0214] Furthermore, this application transforms the random and independent upload behavior of terminal devices into controlled uploads based on the control window, upload permissions, and permissions by using a control window, upload permission parameters, and target device set. That is, only terminal devices within the target device set are allowed to upload according to their upload permissions, while other terminal devices remain silent. This avoids multiple terminal devices blindly competing for resources in the same control window, improves the success rate of critical task uploads, and reduces energy waste caused by repeated transmissions.

[0215] Finally, this application further divides task information into critical information and secondary information, with terminal devices prioritizing the uploading of critical information. This ensures that even when terminal power is unstable or resources are limited, network devices can still obtain critical information and perform actions such as issuing alarms based on it. Additionally, secondary information can be uploaded with permission in subsequent control windows, reducing the probability of missing information and minimizing invalid duplicate transmissions.

[0216] In addition, in ultra-low power or energy harvesting terminal scenarios, related technologies also provide a hybrid communication mode that combines backscatter communication with active transmission. Specifically, when the terminal has insufficient energy, backscatter communication is used to upload a small amount of information with a lower energy threshold; when the terminal has sufficient energy, it switches to active transmission to improve data rate and transmission reliability.

[0217] This type of solution can adapt to terminal energy fluctuations to some extent and improve upload capabilities through communication mode switching. However, its focus is usually on terminal communication mode selection, and it has not formed a region-oriented window-based permission / silence control mechanism, nor has it solved the task-level control problem of "which terminals upload, which terminals remain silent, and whether to upload critical or secondary information" under resource-constrained conditions.

[0218] To address the issues of weak coverage, unstable link quality, or low reception success rate in low-power terminals, relevant technologies can employ reliability enhancement methods such as line coding, forward error correction (FEC), cyclic redundancy check (CRC), repetition, diversity, multipath, or network coding. These methods increase coding redundancy or the number of retransmissions to improve the probability of successful reception.

[0219] While such solutions can improve the reliability of reception at the physical or data link layers and reduce the probability of single transmission failures, they primarily address the issue of "how to reliably receive data that has already been sent," without resolving task-level control issues such as "whether the terminal currently has an upload task, whether it has the capability to upload, and whether the current control window allows uploading." Blindly adding duplication or redundancy without considering terminal energy status, task priority, and regional upload pressure may lead to additional energy consumption, which is detrimental to the long-term operation of ultra-low-power terminals.

[0220] Since ultra-low power terminals may experience power outages, power failures, or transmission interruptions, related technologies can also enable the computing or transmission process to continue after an interruption through checkpoints, breakpoint resume, state maintenance, or task continuation, avoiding starting from scratch after each interruption.

[0221] This type of solution can improve the effective completion rate of terminal devices under intermittent power supply conditions and reduce redundant calculations or transmissions. However, this solution focuses more on the breakpoint recovery process of a single terminal and lacks a continuous control mechanism for multiple terminals within a region. It also does not clearly define task-level gap management for incomplete content. Especially within multiple control windows, the existing solution struggles to gradually fill in and terminate secondary information based on network-side permissions, budget, and whether the terminal device has gap information identification.

[0222] In summary, this invention utilizes lightweight terminal status reporting, eliminating the need for terminals to frequently upload complete energy information, cached information, or complex link status. Terminals only need to report whether an upload task exists and whether the current window has upload capability. The network side can then determine the regional upload level based on the terminal status within the area and uniformly decide which terminals upload, which terminals remain silent, and what content to upload. This approach reduces the computational burden on the terminal side and the overhead of air interface interaction, making the overall system process more efficient and clear.

[0223] Furthermore, by employing window-based upload permissions and silent control, this invention avoids a large number of terminals competing for uplink resources simultaneously, reducing invalid retries and duplicate transmissions. On the other hand, through a mechanism that prioritizes the upload of critical information and gradually completes secondary information, this invention ensures the timely upload of important information such as critical alarms and core sensing results, while gradually supplementing secondary information in subsequent control windows. Therefore, this invention can improve the reliability of critical sensing tasks and the overall system convergence efficiency under conditions of unstable terminal energy.

[0224] It should be understood that Figures 1 to 5 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 5 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0225] The above text combined Figures 1 to 5 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 6 to 7 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0226] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0227] Figure 6 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 6 As shown, the communication device 600 may include a communication module 620. The communication module 620 can implement corresponding communication functions, which can be internal communication functions of the communication device 600 or communication functions between the communication device 600 and other devices. Optionally, the communication module 620 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 600 also includes a processing module 610. The processing module 610 can implement corresponding processing functions.

[0228] Optionally, the communication device 600 further includes a storage module, which can be used to store instructions and / or data; the processing module 610 can read the instructions and / or data in the storage module so that the communication device 600 can implement the aforementioned method embodiments.

[0229] In one possible design, the communication device 600 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 600 can be used to perform the steps or processes performed by the terminal device in any of the above method embodiments.

[0230] For example, the communication module 620 is used to: receive first status information of a first terminal device within a first area. The first status information indicates whether the first terminal device has an upload task and whether it has upload capability within the current control window. The first area includes one or more first terminal devices.

[0231] The processing module 610 is used to: determine first permission information based on first status information. The first permission information is used to indicate the upload permission of the first area and the target device in the first area. The upload permission and the target device are determined based on the first status information. The target device is a terminal device that is allowed to perform the upload task.

[0232] The communication module 620 is also used to: send first license information to the first terminal device.

[0233] In one possible design, the first permission information includes a first upload permission parameter, which indicates the upload permission of the first area. The greater the upload pressure in the first area, the stricter the upload permission in the first area.

[0234] In one possible design approach, the greater the upload pressure on the first area, the stricter the upload permissions for the first area, including: When the upload pressure in the first region is the first upload pressure, the first upload permission parameter indicates that the first region has the permission to upload critical information; When the upload pressure in the first region is the second upload pressure, the first upload permission parameter indicates that the first region has the permission to upload critical information and secondary information; When the upload pressure in the first region is the third upload pressure, the first upload permission parameter indicates that the first region does not have the permission to upload information; wherein, the first upload pressure is greater than the second upload pressure, and the second upload pressure is greater than the third upload pressure.

[0235] In one possible design, the upload pressure of the first area is related to a first quantity and a second quantity. The first quantity is the number of devices to be restored in the first area, and the second quantity is the number of devices with tasks in the first area. Devices to be restored are terminal devices with upload tasks but no upload capability, and devices with tasks are terminal devices with upload tasks.

[0236] In one possible design, the upload pressure of the first area is positively correlated with the upload ratio of the first area and the blocked upload ratio of the first area. The upload ratio of the first area is the ratio of the second quantity to the third quantity, and the blocked upload ratio of the first area is the ratio of the first quantity to the second quantity. The third quantity is the number of all terminal devices in the first area.

[0237] In one possible design, the first license information includes a first target device set, which includes target devices within a first area. The target devices are determined based on first status information, whether the first task information can arrive at the network device on time, and the probability of the first task information arriving on time. The first task information is the information to be uploaded by the first upload task, the first upload task is the upload task of the first terminal device, and the probability of arriving on time is the probability that the first task information arrives at the network device on time.

[0238] In one possible design, before sending the first license information to the first terminal device, the processing module 610 is further configured to: determine candidate devices in the first region, wherein the candidate devices are terminal devices that have upload tasks and upload capabilities; From the candidate devices in the first region, terminal devices that meet the first condition and the second condition are selected to obtain the first target device set; wherein, the first condition indicates that the task information arrives at the network device before the deadline, and the second condition indicates that the on-time arrival probability of the task information is greater than or equal to the target success probability.

[0239] In one possible design, before sending the first license information to the first terminal device, the processing module 610 is further configured to: determine candidate devices for the first region based on the first status information, wherein the candidate devices are terminal devices that have upload tasks and upload capabilities; Terminal devices that meet both the first and second conditions are selected from the candidate devices in the first region to obtain backup devices for the first region; wherein, the first condition indicates that the task information arrives at the network device before the deadline, and the second condition indicates that the on-time arrival probability of the task information is greater than or equal to the target success probability. Determine the overall score of the backup device; the overall score is associated with the on-time arrival probability of the first task information, whether the first task information includes key information, and whether the backup device has a gap information identifier. The gap information identifier indicates that the backup device has a gap task, which is an upload task that is not completed within a control window. The top N backup devices with the highest overall scores in the first region are selected to obtain the first target device set.

[0240] In one possible design approach, the overall score is positively correlated with the probability of the backup equipment arriving on time.

[0241] In one possible design approach, where the first task information includes key information, the overall score of the backup equipment is the first overall score. If the first task information does not include critical information, the overall score of the backup equipment is the second overall score, and the first overall score is higher than the second overall score.

[0242] In one possible design approach, when the backup equipment has a gap information identifier, the overall score of the backup equipment is the third overall score. If the backup equipment does not have a gap information identifier, the overall score of the backup equipment is the fourth overall score, and the third overall score is higher than the fourth overall score.

[0243] In one possible design approach, N is inversely proportional to the upload pressure of the first region.

[0244] In one possible design, the target device in the first area includes a first terminal device, the first terminal device includes a first upload task, the first upload task instructs the first terminal device to upload first task information, the first task information includes first key information and first request information.

[0245] The communication module 620 is also used to: receive the first key information sent by the first terminal device in the current control window when the first permission information indicates that the first area has the permission to upload key information; When the first permission information indicates that the first area has the permission to upload key information and secondary information, the first key information and the first secondary information are received sequentially from the first terminal device in the current control window.

[0246] In one possible design, the processing module 610 is further configured to: determine the actual completion rate of the first upload task when the current control window ends, wherein the actual completion rate is the proportion of information in the first upload task that has reached the network device in the first task information; If the actual completion rate is less than or equal to the target completion rate, a gap information identifier is added to the first terminal device, indicating that there are gap tasks in the first terminal device.

[0247] In one possible design, the processing module 610 is further configured to: clear the gap information identifier of the first terminal device when the actual completion rate is less than or equal to the target completion rate in multiple consecutive control windows and the number of multiple control windows is greater than a first threshold.

[0248] In one possible design approach, the first status information is a status code, which includes an upload task identifier and an upload capability identifier. The upload task identifier is used to indicate whether there is an upload task in the current control window of the terminal device, and the upload capability identifier is used to indicate the upload capability of the terminal device in the current control window.

[0249] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0250] Figure 7 This is another schematic block diagram of the communication device provided in the embodiments of this application. The communication device 700 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The communication device 700 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0251] like Figure 7As shown, the communication device 700 may include one or more processors 710, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 710 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 700 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0252] In an alternative design, the processor 710 may also store instructions and / or data, which can be executed by the processor 710 to cause the communication device 700 to perform the methods described in the above method embodiments.

[0253] In another alternative design, the communication device 700 may include a communication interface 720 for implementing receiving and transmitting functions. For example, the communication interface 720 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0254] Optionally, the communication device 700 may include one or more memories 730, which may store instructions that can be executed on the processor 710, causing the communication device 700 to perform the methods described in the above method embodiments. Optionally, the memories 730 may also store data. Optionally, the processor 710 may also store instructions and / or data. The processor 710 and the memories 730 may be provided separately or integrated together.

[0255] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0256] In one implementation, the communication device 700 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0257] In another implementation, the communication device 700 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0258] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0259] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0260] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0261] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0262] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device. The network device may include a first network device. Optionally, the network device may further include a second network device.

[0263] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0264] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0265] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0266] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0267] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0268] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0269] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0270] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to network devices, the method includes: Receive first status information sent by a first terminal device within a first area; wherein, the first status information is used to indicate whether the first terminal device has an upload task and whether it has upload capability within the current control window, and the first area includes one or more of the first terminal devices; Send first permission information to the first terminal device. The first permission information is used to indicate the upload permission of the first area and the target device in the first area. The upload permission and the target device are determined according to the first status information. The target device is a terminal device that has an upload task in the current control window and is allowed to execute the upload task.

2. The method according to claim 1, characterized in that, The first permission information includes a first upload permission parameter, which indicates the upload permission of the first area. The greater the upload pressure in the first area, the stricter the upload permission in the first area.

3. The method according to claim 2, characterized in that, The greater the upload pressure in the first region, the stricter the upload permissions in the first region, including: When the upload pressure in the first region is the first upload pressure, the first upload permission parameter indicates that the first region has the permission to upload key information; When the upload pressure in the first region is the second upload pressure, the first upload permission parameter indicates that the first region has the permission to upload key information and secondary information. When the upload pressure in the first region is the third upload pressure, the first upload permission parameter indicates that the first region does not have the permission to upload information; wherein, the first upload pressure is greater than the second upload pressure, and the second upload pressure is greater than the third upload pressure.

4. The method according to claim 2 or 3, characterized in that, The upload pressure in the first region is related to the first quantity and the second quantity. The first quantity is the number of devices to be restored in the first region, and the second quantity is the number of devices with tasks in the first region. The devices to be restored are terminal devices with upload tasks but no upload capability, and the devices with tasks are terminal devices with upload tasks.

5. The method according to claim 4, characterized in that, The upload pressure in the first region is positively correlated with the ratio of devices to be uploaded and the ratio of blocked uploads in the first region. The ratio of devices to be uploaded in the first region is the ratio of the second quantity to the third quantity, and the ratio of blocked uploads in the first region is the ratio of the first quantity to the second quantity. The third quantity is the number of all terminal devices in the first region.

6. The method according to claim 1, characterized in that, The first license information includes a first target device set, which includes target devices within the first area. The target devices are determined based on the first status information, whether the first task information can arrive at the network device on time, and the on-time arrival probability of the first task information. The first task information is information to be uploaded by a first upload task, the first upload task is an upload task of the first terminal device, and the on-time arrival probability is the probability that the first task information arrives at the network device on time.

7. The method according to claim 6, characterized in that, Before sending the first license information to the first terminal device, the method further includes: Determine candidate devices in the first region, wherein the candidate devices are terminal devices that have upload tasks and upload capabilities; Terminal devices that meet the first and second conditions are selected from the candidate devices in the first region to obtain the first target device set; wherein, the first condition indicates that the task information arrives at the network device before the deadline, and the second condition indicates that the on-time arrival probability of the task information is greater than or equal to the target success probability.

8. The method according to claim 7, characterized in that, Before sending the first license information to the first terminal device, the method further includes: Candidate devices for the first region are determined based on the first status information. The candidate devices are terminal devices that have upload tasks and upload capabilities. Terminal devices that meet the first and second conditions are selected from the candidate devices in the first region to obtain backup devices for the first region; wherein, the first condition indicates that the task information arrives at the network device before the deadline, and the second condition indicates that the on-time arrival probability of the task information is greater than or equal to the target success probability. Determine the overall score of the backup device; wherein the overall score is associated with the on-time arrival probability of the first task information, whether the first task information includes key information, and whether the backup device has a gap information identifier, wherein the gap information identifier indicates that the backup device has a gap task, and the gap task is an upload task that does not end within a control window; The top N backup devices with the highest overall scores in the first region are selected to obtain the first target device set.

9. The method according to claim 8, characterized in that, The overall score is positively correlated with the probability of the backup equipment arriving on time.

10. The method according to claim 8, characterized in that, If the first task information includes key information, the overall score of the backup equipment is the first overall score; If the first task information does not include key information, the overall score of the backup equipment is the second overall score, and the first overall score is higher than the second overall score.

11. The method according to claim 8, characterized in that, If the backup equipment has a gap information identifier, the overall score of the backup equipment is the third overall score; If the backup equipment does not have a gap information identifier, the overall score of the backup equipment is the fourth overall score, and the third overall score is higher than the fourth overall score.

12. The method according to any one of claims 8-11, characterized in that, The value of N is inversely proportional to the upload pressure of the first region.

13. The method according to any one of claims 1-3 and 5-11, characterized in that, The target device within the first area includes the first terminal device, the first terminal device includes a first upload task, the first upload task instructs the first terminal device to upload first task information, the first task information includes first key information and first request information, and the method further includes: When the first permission information indicates that the first area has the permission to upload key information, the first key information sent by the first terminal device in the current control window is received; When the first permission information indicates that the first area has the permission to upload key information and secondary information, the first terminal device receives the first key information and the first secondary information sent sequentially in the current control window.

14. The method according to claim 13, characterized in that, The method further includes: When the current control window ends, the actual completion rate of the first upload task is determined. The actual completion rate is the proportion of information in the first upload task that has reached the network device in the first task information. If the actual completion rate is less than or equal to the target completion rate, a gap information identifier is added to the first terminal device, indicating that there are gap tasks on the first terminal device.

15. The method according to claim 14, characterized in that, The method further includes: If the actual completion rate is less than or equal to the target completion rate in multiple consecutive control windows, and the number of multiple control windows is greater than a first threshold, the gap information identifier of the first terminal device is cleared.

16. The method according to any one of claims 1-3 and 5-11, characterized in that, The first status information is a status code, which includes an upload task identifier and an upload capability identifier. The upload task identifier is used to indicate whether there is an upload task in the current control window of the terminal device, and the upload capability identifier is used to indicate the upload capability of the terminal device in the current control window.

17. A communication device, characterized in that, include: At least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 1-16 via logic circuits or execution code instructions.

18. A computer-readable storage medium, characterized in that, It includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-16.

Images