Resource allocation method, satellite flash communication system and computer readable storage medium

Abstract

The application provides a resource allocation method, a star flash communication system and a computer readable storage medium. A terminal node reports a downlink data processing capability parameter, and the downlink data processing capability parameter supports a negative value; the terminal node reports an uplink feedback capability parameter, and the uplink feedback capability parameter supports a continuously configurable time delay range; after obtaining a channel occupation time, whether to allocate a downlink data transmission resource to the terminal node before GCI is determined based on the downlink data processing capability parameter, and an uplink feedback time delay is configured for the terminal node based on the uplink feedback capability parameter; if it is determined that the downlink data transmission resource is allocated to the terminal node before GCI, a scheduling instruction is carried in GCI, so that the terminal node receives downlink data before GCI and feeds back after the uplink feedback time delay according to the scheduling instruction. The problem of low resource utilization caused by limited uplink and downlink time delay capability representation in the star flash SLB system is solved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a resource allocation method, a star-flash communication system, and a computer-readable storage medium. Background Technology

[0002] The StarLight SLB system is a short-range wireless communication technology. While it possesses advanced features such as centralized scheduling, flexible frame structure, and Polar codes, achieving ultra-low latency and high reliability, its resource utilization and scheduling flexibility are still limited by inherent defects in the communication protocol. Dynamic downlink data can only be sent after GCI, leaving resources idle before GCI; the uplink ACK feedback latency is fixed and uniform, unable to adapt to differentiated service requirements, and the coordination of uplink and downlink capabilities is limited, resulting in low resource utilization and poor scheduling flexibility, making it difficult to meet the needs of low-latency, highly dynamic application scenarios. Summary of the Invention

[0003] The main objective of this application is to provide a resource allocation method, a StarSignal communication system, and a computer-readable storage medium to at least solve the problem of low resource utilization caused by limited uplink and downlink latency representation in existing StarSignal SLB systems.

[0004] To achieve the above objectives, according to one aspect of this application, a resource allocation method is provided, applied to a StarScan communication system including terminal nodes and management nodes. The method includes: receiving downlink data processing capability parameters reported by the terminal nodes, the downlink data processing capability parameters supporting negative values; receiving uplink feedback capability parameters reported by the terminal nodes, the uplink feedback capability parameters supporting a continuously configurable delay range; after obtaining channel occupancy time, determining, based on the downlink data processing capability parameters, whether to allocate downlink data transmission resources to the terminal nodes before the GCI, and configuring an uplink feedback delay for the terminal nodes based on the uplink feedback capability parameters; if it is determined that the downlink data transmission resources should be allocated to the terminal nodes before the GCI, then carrying a scheduling instruction in the GCI, such that the terminal nodes receive downlink data before the GCI and provide feedback after the uplink feedback delay according to the scheduling instruction, the scheduling instruction including location information of the downlink data transmission resources and the uplink feedback delay.

[0005] Optionally, after obtaining the channel occupancy time, determining whether to allocate downlink data transmission resources to the terminal node before the GCI based on the downlink data processing capability parameters includes: after obtaining the channel occupancy time, obtaining the symbol length, where the symbol length is the duration of one OFDM symbol; determining the symbol offset based on the downlink data processing capability parameters and the symbol length; and if the symbol offset is negative, determining to allocate the downlink data transmission resources to the terminal node before the GCI.

[0006] Optionally, allocating downlink data transmission resources to the terminal before the GCI includes: reserving a front-end dynamic resource pool before the GCI, and adjusting the number of OFDM symbols in the front-end dynamic resource pool according to the non-periodic service load, wherein the front-end dynamic resource pool is a time-frequency resource block composed of a consecutive plurality of OFDM symbols located before the GCI; sorting the terminal nodes according to the symbol offset order based on the downlink data processing capability parameters reported by the plurality of terminal nodes, and obtaining a sorting result; and allocating GCI positions and downlink data transmission resource positions to each terminal node in sequence according to the sorting result, wherein the GCI position is located within the pre-configured GCI blind detection area of ​​the terminal node, and the downlink data transmission resource position is located before the last symbol of the GCI position.

[0007] Optionally, adjusting the number of OFDM symbols in the front-end dynamic resource pool according to the non-periodic service load includes: increasing the number of OFDM symbols in the front-end dynamic resource pool through physical layer control signaling when there is a high-priority service and at least one of the terminal nodes supports negative downlink data processing capability; and setting the number of OFDM symbols in the front-end dynamic resource pool to zero or a minimum reserved symbol when there is no high-priority service or when none of the terminal nodes support the negative downlink data processing capability.

[0008] Optionally, based on the downlink data processing capability parameters reported by multiple terminal nodes, the terminal nodes are sorted in order of the symbol offset to obtain a sorting result, including: determining the terminal nodes that support self-scheduling as candidate nodes within the scheduling period corresponding to the current channel occupancy time; and sorting each terminal node in ascending order of the symbol offset based on the downlink data processing capability parameters reported by the candidate nodes to obtain the sorting result.

[0009] Optionally, according to the sorting result, GCI position and downlink data transmission resource position are allocated to each of the terminal nodes in sequence, including: determining the downlink data start position corresponding to the candidate with the smallest symbol offset in the sorting result as the starting point of resource allocation; based on the starting point of resource allocation, the GCI position and downlink data transmission resource position are allocated to each of the candidate nodes in sequence until all candidate nodes have completed resource allocation.

[0010] Optionally, after reserving a front-end dynamic resource pool before the GCI, the method further includes: confirming the data transmission status to the terminal node in the GCI through a front-end dynamic data indication field, wherein the front-end dynamic data indication field includes a node identifier, resource location, and ACK resource identifier.

[0011] Optionally, after confirming the data transmission status to the terminal node through the pre-dynamic data indication field in the GCI, the method further includes: carrying the ACK resource identifier corresponding to the downlink data indicated by the pre-dynamic data indication field in the GCI; determining the retransmission mode based on the ACK resource identifier, the retransmission mode including synchronous HARQ retransmission mode or asynchronous HARQ retransmission mode; determining the location of the uplink feedback channel where the terminal node sends ACK / NACK according to the retransmission mode and the uplink feedback delay, and receiving HARQ confirmation information in the uplink feedback channel.

[0012] According to another aspect of this application, a StarFlash communication system is provided, including a management node and at least one terminal node, wherein the management node is used to execute any of the resource allocation methods described above.

[0013] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform any of the described resource allocation methods.

[0014] Applying the technical solution of this application, the system receives downlink data processing capability parameters reported by the terminal node, which support negative values; it also receives uplink feedback capability parameters reported by the terminal node, which support continuously configurable delay ranges. After obtaining the channel occupancy time, based on the downlink data processing capability parameters, it determines whether to allocate downlink data transmission resources to the terminal node before the GCI, and configures an uplink feedback delay for the terminal node based on the uplink feedback capability parameters. If it is determined that downlink data transmission resources should be allocated to the terminal node before the GCI, a scheduling instruction is carried in the GCI so that the terminal node receives downlink data before the GCI and provides feedback after the uplink feedback delay, according to the scheduling instruction. The scheduling instruction includes the location information of the downlink data transmission resources and the uplink feedback delay. In this scheme, by expanding the downlink data processing capability parameters and uplink feedback capability parameters of terminal nodes, the management node can accurately identify terminals with GCI preprocessing capabilities during the channel occupancy time and schedule downlink data to time resources before GCI, while dynamically configuring the uplink feedback timing to match its service latency requirements. By uniformly carrying resource location and feedback latency information in GCI, a non-serial transmission mechanism of sending data first and then controlling is realized, breaking through the constraint that control signaling must precede data in traditional StarSignal SLB protocols and Wi-Fi systems. This solves the problem of low resource utilization caused by limited uplink and downlink latency capabilities in existing StarSignal SLB systems. Attached Figure Description

[0015] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0016] Figure 1 A flowchart illustrating a resource allocation method according to an embodiment of this application is shown;

[0017] Figure 2 A flowchart of a specific resource allocation method provided according to an embodiment of this application is shown. Detailed Implementation

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0019] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0020] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0021] As described in the background section, the resource utilization and scheduling flexibility of the existing StarSignal SLB system are limited by the inherent defects of traditional communication protocols. In order to solve the problem of low resource utilization caused by the limited uplink and downlink latency in the StarSignal SLB system, the embodiments of this application provide a resource allocation method, a StarSignal communication system, and a computer-readable storage medium.

[0022] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0023] SparkLink is a short-range wireless communication technology that employs the Synchronous Low Latency Broadband (SLB) communication protocol. In this protocol, the management node (G node) acts as a centralized scheduling center, responsible for unified management of channel resources and generating scheduling signaling, i.e., G-Link Control Information (GCI). Terminal nodes (T nodes), as lightweight devices being scheduled, transmit and receive data according to the instructions from the G node. However, existing wireless communication technologies suffer from common problems in dynamic resource allocation, stemming from limitations in capability representation methods, which restrict resource utilization and flexibility in the SparkLink SLB mode.

[0024] Figure 1 This is a flowchart illustrating a resource allocation method according to an embodiment of this application. Figure 1As shown, the method includes the following steps:

[0025] Step S101: Receive downlink data processing capability parameters reported by the terminal node. The downlink data processing capability parameters support negative values.

[0026] Specifically, the StarSpark protocol defines the parameter `minGlinkDataDelay`, which is the downlink data processing capability parameter, representing the delay from when a node parses the GCI to when it can successfully process the first G-link data. This parameter is limited to a positive number (1~1000 microseconds), failing to reflect that some nodes with advanced processing capabilities can begin processing downlink data before the GCI (e.g., through pre-decoding or pre-configuration). This lack of capability representation prevents the scheduler from utilizing the capabilities of these nodes to send data before the GCI, resulting in idle resources before the GCI and the inability to carry any dynamic data. This application, however, allows the downlink data processing capability parameter to be negative, enabling terminal nodes to pre-process data, such as through hardware acceleration, cache preloading, and parallel decoding, to receive and pre-process downlink data before the GCI arrives. For example, when a terminal node reports a negative value of -30μs, it is actually indicating to the management node that it has the capability to begin processing downlink data 30μs before the GCI. After the terminal node reports, the management node will utilize the terminal node's preprocessing capabilities to map downlink data that would otherwise have to wait for GCI to be sent to idle time-frequency resources before GCI within the Channel Occupancy Time (COT). This breaks through the constraint that control signaling must precede data in traditional Starlight SLB protocols and Wi-Fi systems, enabling quasi-parallel transmission of control and data, and improving resource utilization and low-latency performance.

[0027] Step S102: Receive the uplink feedback capability parameters reported by the aforementioned terminal node. The uplink feedback capability parameters support a continuously configurable latency range.

[0028] Specifically, in the StarSignal protocol, the ACK feedback delay is typically defined using an enumeration method to specify a limited number of feedback opportunities (such as 1, 2, 3, or 4 symbols or across radio frames). This fixed enumeration representation cannot adapt to the differentiated requirements for feedback delay in scenarios such as industrial control and vehicle-to-everything (V2X) communication, and it also limits the system's adaptive scheduling capability in complex channel environments. The rigidity of uplink feedback delay capability prevents management nodes from finely adjusting the HARQ process according to service requirements and channel quality, affecting retransmission efficiency and resource reuse. In this application, the uplink feedback capability parameter supports a continuously configurable delay range, changing the limitation of the rigid enumeration of ACK / NACK feedback opportunities in traditional protocols. In existing StarSignal SLB or Wi-Fi systems, the feedback delay is a predefined discrete option, and the scheduler cannot finely match it according to service requirements, channel status, or HARQ process, resulting in retransmission waiting redundancy and low resource reuse rate. This application allows terminals to report their supported continuous microsecond-level feedback capability range (e.g., 1~16384μs) to the management node during the access or reconfiguration phase. This means that the terminal's feedback capability has expanded from a few enumerated symbols to a range that can flexibly cover multiple symbols and multiple radio frames following the data transmission. Based on this reported information, the management node can dynamically and independently configure precise latency values ​​for each downlink data stream. Specifically, it can flexibly allocate any symbol within a constrained time for high-reliability, low-latency services, and allocate other uplink resources for high-throughput, latency-insensitive services, increasing the flexibility of uplink resource utilization and fully utilizing contention-based time-frequency resources. For example, it can allocate the minimum feedback latency for ultra-high-reliability, ultra-low-latency short packet services to achieve fast retransmission, allocate 200μs for high-throughput audiovisual entertainment services to match their buffering rhythm, and even configure 800μs for cross-frame collaborative scenarios to avoid resource conflicts. This mechanism makes uplink feedback no longer a passive response, but can be coordinated with downlink scheduling, improving HARQ efficiency, resource reuse rate, and system throughput.

[0029] Step S103: After obtaining the channel occupancy time, based on the downlink data processing capability parameters, determine whether to allocate downlink data transmission resources to the terminal node before GCI, and configure uplink feedback delay for the terminal node based on the uplink feedback capability parameters.

[0030] Specifically, after obtaining the Channel Occupancy Time (COT), the management node no longer adopts the traditional serial scheduling mode where control precedes data. Instead, it implements scheduling based on the extended capability parameters actively reported by the terminal nodes. First, the management node reads the downlink data processing capability parameters reported by each terminal node. If a terminal supports negative latency, such as -20μs, it indicates that it can store data in advance. After GCI parsing is completed, it can quickly complete data decoding. The management node then reserves pre-transmission resources for it in the time-frequency resources before GCI, sending downlink data in advance, thereby completely releasing the channel window that has been idle for a long time before GCI. At the same time, the management node reads the uplink feedback capability parameters reported by the terminal node. Combining the downlink data HARQ process, service priority, and the remaining COT resources, the management node dynamically configures the feedback timing for the terminal node with precision down to the microsecond level, ensuring that ACK / NACK returns at the optimal time, avoiding wasted waiting or conflicts with subsequent scheduling.

[0031] Step S104: If it is determined that the downlink data transmission resources are allocated to the terminal node before the GCI, a scheduling instruction is carried in the GCI so that the terminal node receives downlink data before the GCI and provides feedback after the uplink feedback delay according to the scheduling instruction. The scheduling instruction includes the location information of the downlink data transmission resources and the uplink feedback delay.

[0032] Specifically, if the management node determines to allocate downlink data transmission resources to the terminal node before GCI, the management node carries a corresponding resource index value in the subsequent GCI. This index value is the resource pool information pre-configured in the dedicate configuration by the management node based on the feedback capability information reported by the terminal. This resource pool information contains multiple resource information, covering multiple symbol positions after the data information. After receiving the GCI, the terminal node looks up the corresponding uplink resource position in its locally cached feedback resource pool according to this index value and sends ACK / NACK accordingly. This mechanism does not introduce additional control signaling overhead and realizes static pre-configuration and dynamic index binding of downlink data and uplink feedback resources before GCI. This allows the terminal to autonomously execute subsequent actions without waiting for real-time feedback instructions, fully activating idle resources before GCI without increasing the signaling burden and improving system resource utilization efficiency.

[0033] This embodiment expands the downlink data processing capability parameters (supporting negative values) and uplink feedback capability parameters (supporting continuously configurable delays) of terminal nodes, enabling management nodes to accurately identify terminals with GCI preprocessing capabilities during channel occupancy time and schedule downlink data to time resources prior to GCI. Simultaneously, it dynamically configures uplink feedback timing to match service delay requirements. By uniformly carrying resource location and feedback delay information in GCI, a non-serial transmission mechanism of sending data before control is achieved. This overcomes the constraint in traditional StarSignal SLB protocols and Wi-Fi systems that control signaling must precede data, improving the utilization rate of time and frequency resources within the COT. This solves the problem of low resource utilization in existing StarSignal SLB systems due to limited uplink and downlink delay capabilities.

[0034] In the specific implementation process, after obtaining the channel occupancy time, based on the aforementioned downlink data processing capability parameters, it is determined whether to allocate downlink data transmission resources to the aforementioned terminal node before the aforementioned GCI, including: after obtaining the aforementioned channel occupancy time, obtaining the symbol length, wherein the symbol length is the duration of one OFDM symbol; determining the symbol offset based on the aforementioned downlink data processing capability parameters and the aforementioned symbol length; and if the aforementioned symbol offset is negative, determining whether to allocate the aforementioned downlink data transmission resources to the aforementioned terminal node before the aforementioned GCI.

[0035] Specifically, after obtaining the Channel Occupancy Time (COT), the management node first acquires the fixed duration of an OFDM symbol in the current communication system as the minimum time granularity benchmark for resource scheduling. In StarLight SLB, the fixed duration of an OFDM symbol is typically 8.3 µs, and the OFDM symbol is chosen as the calculation standard. Based on the downlink data processing capability parameters reported by the terminal nodes, combined with the symbol length, a formula is used... The symbol offset is calculated, where N is the symbol offset, minGlinkDataDelay is the downlink data processing capability parameter, and symbol_len is the fixed duration of an OFDM symbol. This symbol offset is used to quantify the time lead required by the terminal node relative to the GCI. If the symbol offset is negative, it indicates that the terminal has the capability to complete downlink data reception and decoding before the GCI arrives. In this case, the management node determines that it supports data reception before the GCI, thereby triggering a scheduling decision to reserve downlink transmission resources for it in the time-frequency resources before the GCI.

[0036] The calculation process of the symbol offset realizes the quantitative mapping of the terminal's processing capabilities, transforming the originally abstract pre-processing capabilities into discrete time-domain offset values ​​that can be directly used by the scheduler, ensuring that resource allocation is executable and consistent at the symbol-level precision. The judgment condition of the negative offset is the core criterion of this application. Its essence is to transform the terminal's capability attributes into scheduling conditions. Without changing the basic frame structure of the protocol, it achieves the timing decoupling of control and data with minimal changes, providing accurate and quantifiable decision-making basis for subsequent pre-allocation of resources, post-indication mechanisms, and uplink-downlink coordinated scheduling, thereby improving the automation level of resource scheduling and system flexibility.

[0037] By quantifying the downlink data processing capability parameters reported by the terminal and the OFDM symbol length, the symbol offset is obtained. Whether the offset is negative is used as the basis for judging whether the terminal has the ability to receive data before GCI, thus realizing symbol-level scheduling decision on the terminal's processing capability. This mechanism transforms the originally abstract pre-processing capability into a clear quantitative criterion, and can dynamically allocate resources before GCI without changing the protocol frame structure. It effectively breaks through the timing limitations of traditional serial transmission and significantly improves the channel resource utilization without increasing signaling overhead.

[0038] Further, allocating downlink data transmission resources to the terminals before the GCI includes: reserving a front-end dynamic resource pool before the GCI, and adjusting the number of OFDM symbols in the front-end dynamic resource pool according to the non-periodic service load. The front-end dynamic resource pool is a time-frequency resource block composed of multiple consecutive OFDM symbols located before the GCI. Based on the downlink data processing capability parameters reported by multiple terminal nodes, the terminal nodes are sorted according to the size of the symbol offset to obtain a sorting result. Based on the sorting result, a GCI position and a downlink data transmission resource position are allocated to each terminal node in sequence. The GCI position is located within the pre-configured GCI blind detection area of ​​the terminal node, and the downlink data transmission resource position is located before the last symbol of the GCI position.

[0039] Specifically, after determining that a terminal supports GCI-pre-data reception, the management node further reserves a front-end dynamic resource pool before GCI. This pool consists of multiple consecutive OFDM symbols that do not overlap with GCI, forming a time-frequency resource block. The size of this resource pool is not fixed but is adaptively adjusted according to the load of non-periodic services (such as bursty data requiring rapid feedback for ultra-low latency) in the current network. This achieves elastic scaling of resources and avoids resource waste in low-load scenarios or resource shortages in high-load scenarios. Based on this, the management node integrates the downlink data processing capability parameters reported by all terminals, calculates their respective symbol offsets, and sorts the terminal nodes according to the size of their symbol offsets.

[0040] Furthermore, based on the downlink data processing capability parameters reported by the multiple terminal nodes, the terminal nodes are sorted in order of the symbol offset to obtain the sorting result, including: within the scheduling period corresponding to the current channel occupancy time, the terminal nodes that support self-scheduling are identified as candidate nodes; based on the downlink data processing capability parameters reported by the candidate nodes, the terminal nodes are sorted in ascending order of the symbol offset to obtain the sorting result.

[0041] Specifically, when the management node performs pre-schedule resource ordering for multiple terminal nodes, it calculates the symbol offset based on the downlink data processing capability parameters reported by each terminal node and arranges them in ascending order of symbol offset from smallest to largest, thus forming a clear scheduling priority sequence. This ordering rule is essentially based on the earliest time that the terminal can receive data, from earliest to latest. That is, the smaller the symbol offset (the larger the negative value), the stronger its processing capability and the earlier the data reception time it can support, and therefore obtains a higher scheduling priority.

[0042] In this embodiment, the management node independently executes downlink resource scheduling decisions within the scheduling period (TTI) corresponding to each Channel Occupancy Time (COT), without relying on the resource status already allocated in the previous TTI. Specifically, within the current TTI, the management node first selects only terminal nodes that report self-scheduling (selfTTIscheduling=True) as scheduling candidate nodes; for non-self-scheduling nodes or nodes that have not reported this capability, the management node does not include them in this scheduling to avoid data reception failure due to insufficient processing capacity.

[0043] The management node sorts the symbol offsets of each candidate node from smallest to largest based on the downlink data processing capability parameters reported by each node. Negative symbol offsets are allowed, indicating that the terminal has the capability to pre-decode or pre-process downlink data before GCI (Global Interpreter Interface). The symbol offsets N of all candidate nodes are sorted from smallest to largest, with negative offsets (e.g., N=-3) taking precedence over zero offsets (N=0) and positive offsets (N=+2). Specifically, the sorting order is: N=-3 takes precedence over N=-1, N=-1 takes precedence over N=0, and N=0 takes precedence over N=+2. This sorting rule directly reflects the order in which terminals receive downlink data on the timeline: terminals with smaller (more negative) offsets have earlier reception capabilities and should be allocated resources more preferentially.

[0044] This sorting mechanism provides the management node with a sequence of candidate nodes arranged in ascending order of receiving capacity, serving as a basis for decision-making in allocating GCI and downlink data resources sequentially, starting with the node with the smallest offset. This process is completed entirely within the current TTI, without relying on historical scheduling records, effectively releasing the resource potential of idle time slots before GCI and overcoming the inherent limitation in traditional protocols that control signaling must precede data transmission.

[0045] Furthermore, based on the above sorting results, GCI positions and downlink data transmission resource positions are allocated to each of the above terminal nodes in sequence, including: determining the downlink data start position corresponding to the candidate with the smallest symbol offset in the above sorting results as the starting point of resource allocation; based on the starting point of resource allocation, the above GCI positions and downlink data transmission resource positions are allocated to each of the above candidate nodes in sequence, until all the above candidate nodes have completed resource allocation.

[0046] Specifically, based on the sorting results, a joint allocation of downlink resources is performed. This allocation process uses the downlink data start position corresponding to the candidate node with the smallest symbol offset after sorting as the physical starting point. When the symbol offset N = -3, it indicates that the terminal node has the capability to receive and process downlink data at the time-frequency resource positions three symbols before the GCI symbol. Therefore, the management node can allocate the downlink data resources of this node to the third symbol before the GCI symbol. The management node then allocates the downlink data transmission resource positions and corresponding GCI positions to each candidate node sequentially according to the aforementioned sorting results (i.e., symbol offset N from smallest to largest, with negative values ​​taking priority). Each GCI is allocated to a blind detection region, arranged sequentially from the starting position, and data is mapped sequentially from the dynamic resource symbol. The GCI and data can be in any relative position that satisfies the capabilities of the terminal node. This joint allocation mechanism of GCI and data enables quasi-parallel control signaling and data transmission in time, breaking through the serial constraint of control first and data second in traditional protocols.

[0047] The allocation process proceeds forward along the time axis. Resource allocation is limited by the availability of the preceding dynamic resource pool, meaning allocation only occurs within the time-frequency resources preceding the GCI symbol, until the resource pool is exhausted or all candidate nodes have successfully allocated their GCI and data resources. When a node with a positive offset (N>0) is scheduled, its data location is after the GCI. At this point, it no longer occupies the preceding resource pool, but allocation continues according to the sorting order to achieve efficient utilization of all time-domain resources within the COT.

[0048] By reserving a dynamically adjustable front-end resource pool and allocating resources before GCI according to the order of symbol offsets reported by terminals from smallest to largest (i.e., from strongest to weakest capability), adaptive and collaborative utilization of idle resources before GCI is achieved. This mechanism not only elastically expands or shrinks the resource pool size according to the burst load of non-periodic services to avoid resource waste, but also ensures that the terminal with the strongest processing capability occupies the frontmost symbol resources first through a capability-driven reverse scheduling strategy, maximizing the release of its early reception capability gain. This enables two-dimensional efficient reuse of time and frequency resources within COT in multi-terminal concurrent scenarios, significantly improving system throughput and deterministic guarantee capability for low-latency services without increasing signaling overhead.

[0049] Furthermore, after reserving a front-end dynamic resource pool before the aforementioned GCI, the method further includes: confirming the data transmission status to the aforementioned terminal node through a front-end dynamic data indication field in the aforementioned GCI, wherein the front-end dynamic data indication field includes node identifier, resource location, and ACK resource identifier.

[0050] Specifically, after reserving a pre-positioned dynamic resource pool before the GCI, the management node notifies the terminal node via the control channel using the dynamic data indication field and ACK feedback indication field indicated in the GCI. The dynamic data indication field includes the symbol start index, symbol length, and frequency domain information of the dynamic data in the time domain. The symbol start index can be located before the GCI control area, while the frequency domain information must avoid occupying frequency domain resources by the GCI. The ACK feedback field indicates the ACK feedback time domain location information and frequency domain resource information. The time domain location information can flexibly cover multiple symbol positions after the data. This method expands the coverage area of ​​downlink data and ACK feedback resources. GCI control information and scheduling data can be sent synchronously in the air interface time, overcoming the limitation of dynamic data lagging behind control signaling in traditional protocols. Simultaneously, the ACK can flexibly cover multiple symbol areas, improving resource utilization.

[0051] Furthermore, after confirming the data transmission status to the terminal node through the preceding dynamic data indication field in the aforementioned GCI, the method further includes: carrying an ACK resource identifier corresponding to the downlink data indicated by the preceding dynamic data indication field in the aforementioned GCI; determining a retransmission mode based on the aforementioned ACK resource identifier, wherein the retransmission mode includes a synchronous HARQ retransmission mode or an asynchronous HARQ retransmission mode; determining the location of the uplink feedback channel in which the terminal node sends ACK / NACK according to the aforementioned retransmission mode and the aforementioned uplink feedback delay, and receiving HARQ confirmation information in the aforementioned uplink feedback channel.

[0052] Specifically, by explicitly carrying the ACK resource identifier for the preceding downlink data in the GCI and linking it with the uplink feedback delay configuration, flexible decision-making on retransmission modes and precise positioning of the uplink feedback channel are achieved. This mechanism expands the ACK feedback location area, allowing for flexible use of idle resources within the TTI and improving uplink resource utilization.

[0053] By carrying the ACK resource identifier of the preceding downlink data in the GCI and linking it with the dynamically configured retransmission mode (synchronous / asynchronous) and uplink feedback latency, efficient and adaptive ACK feedback management of the GCI-pre-transmitted data is achieved, solving the problem of unbased retransmission scheduling in scenarios where data is sent first and then indicated. Without sacrificing flexibility, a reliable and low-overhead preceding data retransmission mechanism is constructed, improving the retransmission efficiency and end-to-end transmission reliability of the StarSpark SLB system under dynamic resource scheduling.

[0054] In some embodiments of this application, adjusting the number of OFDM symbols in the aforementioned front-end dynamic resource pool according to the non-periodic service load includes: increasing the number of OFDM symbols in the aforementioned front-end dynamic resource pool through physical layer control signaling when there is a high-priority service and at least one of the aforementioned terminal nodes supports negative downlink data processing capability; and setting the number of OFDM symbols in the aforementioned front-end dynamic resource pool to zero or a minimum reserved symbol when there is no such high-priority service or when none of the aforementioned terminal nodes support the such negative downlink data processing capability.

[0055] Specifically, when a high-priority service (such as ultra-low latency burst data requiring rapid feedback) is detected, and at least one terminal node has negative downlink processing capability (i.e., can receive data before the GCI), the management node immediately expands the number of OFDM symbols in the front-end resource pool through physical layer signaling, proactively releasing idle time-frequency resources before the GCI, and pre-scheduling critical service data. This compresses end-to-end latency, seizes the transmission window, and maximizes the deterministic guarantee of low-latency services. Conversely, when there is no high-priority service or all terminals do not support negative latency capability, the front-end resource pool is shrunk to zero or only a minimum number of symbols are retained for compatibility or simplified control signaling, avoiding resource idleness and ensuring that the remaining resources within the COT can be efficiently used for regular data transmission or uplink scheduling. This mechanism enables automatic switching of resource modes under different loads and heterogeneous terminal environments, maximizing overall resource utilization while ensuring the performance of critical services.

[0056] By employing a dual-condition dynamic decision-making mechanism based on the existence of high-priority services and the negative latency capability of terminals, the on-demand adjustment of the front-end dynamic resource pool is achieved, improving the intelligence and energy efficiency of system resource utilization. When high-priority services and terminals with pre-processing capabilities coexist, the number of OFDM symbols before GCI is dynamically expanded through physical layer signaling, precisely releasing idle resources to carry low-latency data. Conversely, when there are no high-priority services or the terminal does not support negative latency, the resource pool shrinks to zero or retains only the minimum number of symbols, completely eliminating invalid resource occupation and ensuring that all other resources within the COT are used for regular scheduling. This mechanism balances the performance guarantee of low-latency services with the overall resource efficiency of the system.

[0057] This application innovates the traditional serial mode of control frames and data frames through two core capability extensions: downlink data latency extension and uplink ACK feedback latency extension.

[0058] Downlink data delay capability extension: The minGlinkDataDelay parameter is expanded from supporting only positive values ​​to allowing negative values, indicating that nodes have the ability to receive and process downlink data before the GCI symbol. Based on this capability, after obtaining the COT, the management node can pre-map dynamically scheduled downlink data to time-frequency resources before the GCI. This capability extension completely changes the serial mode in traditional communication systems where control signaling must be sent before data, realizing quasi-parallel transmission of control and data, and eliminating idle resources before the GCI.

[0059] Uplink ACK feedback delay capability expansion: The ACK feedback delay capability parameter is expanded from an enumeration type to an integer range (1~16384 microseconds), supporting microsecond-level granularity delay configuration, enabling nodes to report all supported feedback opportunities. Management nodes can dynamically configure specific feedback delay values ​​for terminal nodes based on service type, channel quality, and resource scheduling, allowing uplink feedback to flexibly match ACK resources and avoiding resource waiting or waste due to fixed feedback opportunities.

[0060] The two capability extensions work together to form a complete dynamic resource allocation framework for uplink and downlink: downlink data is sent in advance through negative latency capability, making full use of idle resources before GCI and shortening the time between data arrival and feedback. Uplink ACK, through fine-grained latency configuration, can be fed back at a more appropriate time (such as immediately after downlink data or across frames), reducing idle waiting time in the HARQ process and improving retransmission efficiency. The management node centrally schedules uplink and downlink resources, dynamically adjusting the downlink data transmission position and uplink feedback timing according to service priority, channel conditions, and extended capability parameters, maximizing the effective data transmission time within the COT.

[0061] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the resource allocation method of this application will be described in detail below with reference to specific embodiments.

[0062] This embodiment relates to a specific resource allocation method, such as... Figure 2 As shown, it includes the following steps:

[0063] Step S1: Capability Reporting and Negotiation (Manifestation of Capability Expansion): During access or reconfiguration, the terminal node (T node) reports its expanded uplink ACK feedback latency capability range (maximum value within 1~16384μs) and expanded downlink data latency capability (minGlinkDataDelay, negative values ​​are allowed) to the management node (G node). The management node records the expanded capabilities of each terminal node for subsequent scheduling decisions.

[0064] Step S2: Downlink Data Scheduling and Transmission (Utilizing Extended Negative Latency Capability): After the management node acquires the COT (Content Target), it calculates the symbol offset based on the downlink data latency capability and service requirements of each terminal node. For terminal nodes supporting negative latency (N is negative), the management node reserves a pre-configured dynamic resource pool before the GCI (Global Interpreter Query) and allocates downlink data resources within this pool. Dynamically scheduled data is transmitted using a resource pre-reservation and post-indication method: Terminal nodes transmit data on pre-configured resources, and the management node confirms the data and HARQ information in the subsequent GCI by adding a pre-configured dynamic data indication field, completely resolving the contradiction of data being transmitted but not indicated. For terminal nodes that do not support negative latency, data is scheduled after the GCI.

[0065] Step S3: Uplink ACK Feedback Configuration and Execution (Utilizing Extended Integer Range Capability): The management node allocates a specific ACK feedback delay value (1~16384μs) for each downlink data based on the downlink data's HARQ process requirements, the remaining time of the current COT, and the terminal node's extended feedback capability. The terminal node sends ACK / NACK after the specified delay. If the delay exceeds the remaining time of the current radio frame, it is automatically postponed to the next radio frame. The management node decides whether to retransmit based on the feedback result. Retransmission can continue to utilize preceding or following resources. The integer range is 1 to 16384, supporting feedback within the current radio frame and feedback within the next radio frame. The duration of a single radio frame is 125μs. When the ACK feedback delay value is ≤4, it indicates that the feedback delay does not exceed the corresponding number of OFDM symbol times; when the ACK feedback delay value is >4, it indicates that the feedback delay can be greater than 4 symbols, supporting cross-radio frame feedback.

[0066] Step S4: Multi-node Collaboration and Adaptive Adjustment: In multi-node scenarios, the management node employs a time-reverse scheduling algorithm, allocating uplink resources backward from GCI, prioritizing nodes with larger absolute negative latency values. The management node dynamically monitors service load and adjusts the size of the uplink dynamic resource pool to adapt to sudden demands from non-periodic services. Uplink ACK feedback latency can also be dynamically adjusted based on service priority; for example, higher-priority services are configured with shorter feedback latency.

[0067] The above method is used in Star Flash SLB mode, where the integer range above supports 1~16384μs.

[0068] This application overcomes the limitations caused by insufficient capability representation in the Wi-Fi serial frame structure and StarScan protocol by extending the downlink data latency capability and the uplink ACK feedback latency range, achieving the following beneficial effects:

[0069] The increased flexibility brought by capacity expansion: Downlink data latency capability has been expanded from positive to negative values, enabling management nodes to perceive and utilize the node's ability to process data before GCI, extending the downlink data transmission window to the entire COT and improving resource utilization. Uplink ACK feedback latency has been expanded from a fixed enumerated value to an integer range (1~16384μs), allowing management nodes to finely adjust the HARQ process according to service requirements and channel conditions, avoiding resource waste or retransmission delays caused by insufficient capacity representation.

[0070] Overcoming the limitation of not being able to transmit dynamic data before the control frame: Compared with the serial mode of Wi-Fi's RTS / CTS, this application enables dynamic scheduling data to be sent before the GCI through negative latency capability and a post-indication mechanism, realizing quasi-parallel transmission of control signaling and data frames and eliminating channel idle waiting time. Compared with existing star-flash protocols, this application makes full use of idle resources before the GCI, especially in short COT scenarios.

[0071] Uplink and downlink coordination optimization maximizes COT utilization: The combination of advance downlink data transmission and flexible uplink feedback configuration maximizes the effective data transmission time within each COT, seamlessly connects uplink and downlink resources, and improves the overall system throughput.

[0072] Enhanced low-latency service support capabilities: Burst traffic can be pre-transmitted with negative latency, combined with short feedback latency, achieving end-to-end microsecond-level latency to meet the stringent requirements of industrial control, vehicle collaboration, and other applications. Full utilization of centralized scheduling advantages: Management nodes possess global uplink and downlink information and expanded capability parameters, enabling cross-layer optimization and achieving efficient two-dimensional resource reuse in time and frequency. Compatibility and smooth evolution: Retaining the original enumeration semantics, backward compatibility is achieved through numerical range expansion; negative latency capability is an optional feature and does not affect the operation of traditional nodes. Broad prospects for standardization and adaptation: This application can be included in subsequent standards of the StarLight Consortium, providing core technical support for StarLight applications in industrial, automotive, and consumer electronics fields.

[0073] Example 1: Downlink data latency capability extension (negative latency reporting and application).

[0074] The terminal node (T node) reports its downlink data processing capability parameter minGlinkDataDelay=-20μs to the management node (G node), indicating that it has the extended capability to start processing downlink data 20μs before GCI. Assuming the duration of a single symbol in the StarSpark SLB system is 10μs, the calculated symbol offset N=-2, indicating that the T node can start effectively receiving data two symbols before the GCI symbol (symbol #0). After obtaining the Channel Occupancy Time (COT), the G node, combined with the negative latency capability reported by the T node, reserves a pre-emptive dynamic resource pool in the time-frequency resources before GCI, and allocates dedicated downlink data resources for the T node in symbols #-2 and #-1 (i.e., the two symbols before GCI) to carry high-priority service data. This downlink data has been scheduled and transmitted by the G node before GCI transmission. Subsequently, the G node adds a pre-processing dynamic data indication field to the GCI symbol (symbol #0). This field contains the following key information: the target T node identifier, the time-frequency resource location occupied by the downlink data (symbols #-2 to #-1), and the corresponding ACK resource identifier (HARQ Process ID=3). The purpose of this indication field is to confirm the data afterward: although the data has been sent before the GCI, the T node can only legally decode and process the data after it is explicitly indicated in the GCI. This process breaks through the limitation of the original protocol that the capability representation is limited to positive numbers, and realizes data transmission before the GCI.

[0075] Example 2: Uplink ACK feedback latency capability extension (integer range configuration).

[0076] The G node dynamically configures the uplink ACK / NACK feedback delay parameter for the T node via RRC (Radio Resource Control) signaling. This parameter is defined in the protocol as an extended integer range:

[0077] asn1;

[0078] ACKDelay::=INTEGER(1..16384);

[0079] The unit is microseconds (μs), representing the maximum time interval that node T can support between receiving downlink data and sending the corresponding ACK / NACK feedback. The introduction of this parameter completely replaces the rigid feedback timing configuration mechanism of the original Star-Spot SLB protocol, which only supports enumerated values ​​(such as 1, 2, 3, 4 symbols or "across frames"), achieving fine-grained feedback delay control at the microsecond level. When ACKDelay is ≤4, since the period of a single OFDM symbol in SLB mode is approximately 0.434μs, this value is equivalent to a feedback delay of no more than 4 symbols (i.e., a maximum of approximately 1.736μs), suitable for services extremely sensitive to latency. For example, in this embodiment, node G configures ACKDelay=1μs for ultra-low latency burst data requiring rapid feedback, enabling node T to send acknowledgment feedback within approximately 1μs after receiving data, greatly shortening the HARQ retransmission cycle. When ACKDelay is greater than 4, it supports feedback delays spanning multiple symbols or even multiple radio frames (a single radio frame is approximately 20.833 μs long). For example, configuring ACKDelay=100 μs for data with high latency tolerance allows the T node to delay feedback to a suitable time in the next radio frame, thereby avoiding conflicts with uplink scheduling, reducing resource contention overhead, and adapting to the scheduling flexibility requirements of low-priority, high-throughput services. The G node dynamically configures this value for the T node according to service requirements. For example, configuring 1 μs for ultra-low latency burst data requiring fast feedback and configuring 100 μs for data with high latency tolerance breaks through the original protocol's enumeration limitation of only supporting 1, 2, 3, 4 symbols or multiple frames.

[0080] Example 3: Uplink and downlink capability coordinated scheduling (short COT scenario, compared with Wi-Fi serial mode).

[0081] COT duration: 5 symbols, GCI occupies symbol #0 (similar to control frames in Wi-Fi).

[0082] Node A (T): Reports extended downlink latency capability of -20μs, requires sending downlink data with ultra-low latency constraints and ACK feedback to be completed in a very short time.

[0083] T-node B: Only supports positive latency of 20μs, and needs to send downlink data with high tolerance for feedback latency and no strict time limit requirements.

[0084] Scheduling process:

[0085] 1. Node G utilizes the expansion capability of A to allocate forward downlink resources for A in symbols #-2 to #-1, and sends data with extremely short feedback delay constraints (equivalent to data being sent before the control frame, while Wi-Fi needs to wait for RTS / CTS exchange before sending data).

[0086] 2. In symbol #0, GCI indicates the preceding data of A (HARQ ID=1) and configures the uplink ACK feedback delay of A to 1μs (utilizing the extended integer range capability), while allocating the following downlink resources (symbols #2~#3) for B.

[0087] 3. A sends an ACK at symbol #1, and G node does not retransmit after confirming the success.

[0088] 4. B receives data at symbol #3, and the G node configures the ACK feedback delay for it to be 20μs (spanning to the next COT).

[0089] In this process, the expanded uplink and downlink capabilities tightly integrate data advance transmission with rapid feedback, and there are no idle symbols in the COT, which greatly improves efficiency compared to the serial mode of Wi-Fi (control + data + ACK serial).

[0090] Example 4: Time-reverse scheduling based on scalability in multi-node scenarios.

[0091] Three nodes: A (-30μs, with strong preprocessing capabilities), B (-10μs, with medium preprocessing capabilities), and C (20μs, can only receive data after GCI).

[0092] GCI is located at symbol #4, and the initial size of the front resource pool is 2 symbols (symbols #2~#3).

[0093] Based on the downlink latency capabilities of each node, node G uses reverse time scheduling: A occupies symbols #2~#3, and B has no preceding resources available.

[0094] The G node detected a large number of bursty data packets that needed to be transmitted and acknowledged within a very short feedback delay. It expanded the front-end resource pool to 3 symbols (symbols #1 to #3) and updated it via RRC signaling.

[0095] In subsequent scheduling, both A and B obtained the preceding resources, and their end-to-end acknowledgment latency for data packets was significantly reduced.

[0096] This invention provides a StarFlash communication system, including a management node and at least one terminal node, wherein the management node is used to execute any of the above-described resource allocation methods.

[0097] The management node (G node) includes a capability management module, a scheduling module, and a signaling generation module. The capability management module receives the extended uplink ACK feedback delay capability range and extended downlink data delay capability parameters reported by the terminal nodes (T nodes). The downlink data delay capability parameters can be negative. The scheduling module, after obtaining the COT, calculates the symbol offset based on the downlink data delay capability parameters. If the offset is negative, it allocates downlink data resources before the GCI and configures specific ACK feedback delay values ​​for the T nodes according to service requirements. The signaling generation module generates a GCI containing a pre-processed dynamic data indication field, and RRC or physical layer signaling containing ACK feedback delay configuration.

[0098] The T-node comprises a capability reporting module, a downlink receiving module, and an uplink feedback module. The capability reporting module reports its extended uplink ACK feedback delay capability range and extended downlink data delay capability parameters to the G-node; these downlink data delay capability parameters are allowed to be negative. The downlink receiving module receives G-link data before or after the GCI, based on the symbol offset allocated by the G-node. The uplink feedback module sends ACK / NACK at specified times, based on the ACK feedback delay value configured by the G-node.

[0099] This invention provides a computer-readable storage medium including a stored program, wherein the program, when running, controls the device where the computer-readable storage medium is located to execute the resource allocation method.

[0100] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0101] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0102] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0103] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0104] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0105] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0106] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0107] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0108] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0109] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0110] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A resource allocation method, said method being applied to a StarFlash communication system including terminal nodes and management nodes, characterized in that, The method includes: Receive downlink data processing capability parameters reported by the terminal node, wherein the downlink data processing capability parameters support negative values; Receive uplink feedback capability parameters reported by the terminal node, wherein the uplink feedback capability parameters support a continuously configurable latency range; After obtaining the channel occupancy time, based on the downlink data processing capability parameters, it is determined whether to allocate downlink data transmission resources to the terminal node before GCI, and based on the uplink feedback capability parameters, uplink feedback delay is configured for the terminal node. If it is determined that the downlink data transmission resources are allocated to the terminal node before the GCI, then the GCI carries a scheduling instruction so that the terminal node receives downlink data before the GCI and provides feedback after the uplink feedback delay, according to the scheduling instruction. The scheduling instruction includes the location information of the downlink data transmission resources and the uplink feedback delay.

2. The method according to claim 1, characterized in that, After obtaining the channel occupancy time, based on the downlink data processing capability parameters, determine whether to allocate downlink data transmission resources to the terminal node before the GCI, including: After obtaining the channel occupancy time, the symbol length is obtained, which is the duration of one OFDM symbol; The symbol offset is determined based on the downlink data processing capability parameters and the symbol length; If the symbol offset is negative, determine that the downlink data transmission resources are allocated to the terminal node before the GCI.

3. The method according to claim 2, characterized in that, Allocating downlink data transmission resources to the terminal prior to the GCI includes: A front-end dynamic resource pool is reserved before the GCI, and the number of OFDM symbols in the front-end dynamic resource pool is adjusted according to the non-periodic service load. The front-end dynamic resource pool is a time-frequency resource block composed of a continuous number of OFDM symbols located before the GCI. Based on the downlink data processing capability parameters reported by the multiple terminal nodes, the terminal nodes are sorted according to the size of the symbol offset to obtain a sorting result; Based on the sorting results, GCI positions and downlink data transmission resource positions are allocated to each terminal node in sequence. The GCI position is located within the pre-configured GCI blind detection area of ​​the terminal node, and the downlink data transmission resource position is located before the last symbol of the GCI position.

4. The method according to claim 3, characterized in that, Adjusting the number of OFDM symbols in the front-end dynamic resource pool according to non-periodic service load includes: In the presence of high-priority services and at least one of the terminal nodes supporting negative downlink data processing capability, the number of OFDM symbols in the front-end dynamic resource pool is increased through physical layer control signaling. In the absence of the high-priority service, or if all the terminal nodes do not support the negative downlink data processing capability, the number of OFDM symbols in the front-end dynamic resource pool is set to zero or a minimum reserved symbol.

5. The method according to claim 3, characterized in that, Based on the downlink data processing capability parameters reported by multiple terminal nodes, the terminal nodes are sorted according to the magnitude of the symbol offset to obtain a sorting result, including: Within the scheduling period corresponding to the current channel occupancy time, the terminal nodes that support self-scheduling are identified as candidate nodes; Based on the downlink data processing capability parameters reported by the candidate nodes, the terminal nodes are sorted in ascending order of symbol offset to obtain the sorting result.

6. The method according to claim 5, characterized in that, Based on the sorting results, GCI locations and downlink data transmission resource locations are allocated to each terminal node in sequence, including: The starting position of the downlink data corresponding to the candidate with the smallest symbol offset in the sorting results is determined as the starting point of resource allocation; Based on the starting point of the resource allocation, the GCI position and the downlink data transmission resource position are allocated to each candidate node in sequence until all candidate nodes have completed resource allocation.

7. The method according to claim 3, characterized in that, After reserving a front-end dynamic resource pool before the GCI, the method further includes: In the GCI, the data transmission status is confirmed to the terminal node through the front-end dynamic data indication field, which includes node identifier, resource location, and ACK resource identifier.

8. The method according to claim 7, characterized in that, After confirming the data transmission status to the terminal node via the pre-processed dynamic data indication field in the GCI, the method further includes: The GCI carries the ACK resource identifier corresponding to the downlink data indicated by the preceding dynamic data indication field; Based on the ACK resource identifier, the retransmission mode is determined, including synchronous HARQ retransmission mode or asynchronous HARQ retransmission mode. Based on the retransmission mode and the uplink feedback delay, the location of the uplink feedback channel for the terminal node to send ACK / NACK is determined, and HARQ acknowledgment information is received in the uplink feedback channel.

9. A star-flash communication system, characterized in that, It includes a management node and at least one terminal node, wherein the management node is used to execute the resource allocation method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the resource allocation method according to any one of claims 1 to 8.

Images