Methods, apparatus, equipment and media for blind detection of downlink control channels of multiple terminals

Abstract

This application discloses a method, apparatus, computer device, and storage medium for blind detection of downlink control channels (CCEs) across multiple terminals. The method records the occupancy status of CCE resource blocks among multiple terminals using a global resource occupancy table, enabling the sharing of CCE resource block occupancy status among multiple terminals to avoid wasting computing resources due to repeated blind detection. Before subsequent terminals perform blind detection, a pruning and filtering mechanism is added. First, the occupancy status of each CCE resource block is queried from the global resource occupancy table, and CCE resource blocks that are already occupied are filtered out. This achieves a hierarchical and decreasing number of blind detections, reducing the amount of resources involved in repeated blind detection and improving blind detection efficiency.

Description

Technical Field

[0001] This application relates to the field of communication testing technology, and in particular to a method, apparatus, computer device, and computer-readable storage medium for blind detection of downlink control channels of multiple terminals. Background Technology

[0002] When performing blind detection of the Physical Downlink Control Channel (PDC), the multi-terminal simulator mainly adopts a fully hardware-based blind detection architecture based on FPGA, and achieves concurrent blind detection of multiple terminals by parallel replication of the single-terminal blind detection module. However, this blind detection method involves a large amount of invalid blind detection calculations. Therefore, how to improve the efficiency of concurrent blind detection of multiple terminals has become an urgent problem to be solved. Summary of the Invention

[0003] This application provides a method, apparatus, computer device, and storage medium for blind detection of downlink control channels for multiple terminals, so as to improve the efficiency of concurrent blind detection of multiple terminals.

[0004] In a first aspect, this application provides a method for blind detection of downlink control channels for multiple terminals, the method comprising:

[0005] Obtain the first candidate set of physical downlink control channel (PDCCH) to be detected for the first terminal. The PDCCH candidate set includes at least one control channel element (CCE) resource block.

[0006] Based on the preset global resource occupancy table, the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected is obtained;

[0007] From the first PDCCH candidate set to be detected, remove the CCE resource blocks whose occupation status is occupied to obtain the target PDCCH candidate set, so as to perform pruning filtering on the first PDCCH candidate set to be detected;

[0008] The first terminal is controlled to perform blind PDCCH checks on each CCE resource block in the target PDCCH candidate set.

[0009] Secondly, this application also provides a downlink control channel blind detection device for multiple terminals, the device comprising:

[0010] The data caching module is used to obtain the first physical downlink control channel (PDCCH) candidate set of the first terminal to be detected. The PDCCH candidate set includes at least one control channel element (CCE) resource block.

[0011] The pruning and filtering module is used to obtain the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected based on a preset global resource occupancy table.

[0012] The pruning and filtering module is further configured to remove the CCE resource blocks whose occupancy status is occupied from the first PDCCH candidate set to be detected, so as to obtain the target PDCCH candidate set and perform pruning and filtering on the first PDCCH candidate set to be detected.

[0013] The blind detection decoding module is used to control the first terminal to perform blind PDCCH detection on each CCE resource block in the target PDCCH candidate set.

[0014] Thirdly, this application also provides a computer device, the computer device including a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program and, when executing the computer program, implement the downlink control channel blind detection method for multiple terminals as described above.

[0015] Fourthly, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the downlink control channel blind detection method for multiple terminals as described above.

[0016] This application discloses a method, apparatus, computer device, and storage medium for blind detection of downlink control channels (PDCCHs) across multiple terminals. The method involves: acquiring a first candidate set of physical downlink control channels (PDCCHs) to be detected from a first terminal, where the PDCCH candidate set includes at least one control channel element (CCE) resource block; obtaining the occupancy status of each CCE resource block in the first candidate set based on a preset global resource occupancy table; removing CCE resource blocks whose occupancy status is "occupied" from the first candidate set to obtain a target candidate set for pruning and filtering; and controlling the first terminal to perform blind PDCCH detection on each CCE resource block in the target candidate set. Through this method, this application records the occupancy status of CCE resource blocks among multiple terminals using a global resource occupancy table, achieving sharing of CCE resource block occupancy status among multiple terminals and avoiding wasted computing resources caused by repeated blind detection. Before subsequent blind checks are performed on the terminal, a pruning and filtering mechanism is added. First, the occupancy status of each CCE resource block is queried from the global resource occupancy table, and CCE resource blocks that are already in an occupied state are filtered out. This achieves a hierarchical and progressively decreasing number of blind checks, reducing the number of resources for repeated blind checks and improving the efficiency of blind checks. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic flowchart of the first embodiment of a blind detection method for downlink control channels of multiple terminals provided in this application.

[0019] Figure 2 This is a schematic flowchart of a second embodiment of a multi-terminal downlink control channel blind detection method provided by the embodiments of this application.

[0020] Figure 3 This is a schematic flowchart of a third embodiment of a multi-terminal downlink control channel blind detection method provided by the embodiments of this application.

[0021] Figure 4 This is a schematic block diagram of a downlink control channel blind detection device for multiple terminals provided in an embodiment of this application.

[0022] Figure 5 A schematic block diagram of the structure of a computer device provided for an embodiment of this application. Detailed Implementation

[0023] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0025] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0026] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0027] Embodiments of this application provide a method, apparatus, computer device, and storage medium for blind detection of downlink control channels for multiple terminals. The downlink control channel blind detection method for multiple terminals can be applied to servers.

[0028] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0029] Please see Figure 1 , Figure 1 This is a schematic flowchart illustrating a multi-terminal downlink control channel blind detection method provided in an embodiment of this application. This multi-terminal downlink control channel blind detection method can be applied to servers.

[0030] like Figure 1 As shown, the downlink control channel blind detection method for multiple terminals specifically includes steps S101 to S104.

[0031] S101. Obtain the first physical downlink control channel (PDCCH) candidate set of the first terminal to be detected. The PDCCH candidate set includes at least one control channel element (CCE) resource block.

[0032] For example, before S101, the method further includes:

[0033] Obtain the protocol configuration parameters corresponding to the first terminal, wherein the protocol configuration parameters include an wireless network temporary identifier and / or downlink control information;

[0034] Based on the protocol configuration parameters, the search space of the first terminal is calculated, the search space includes at least one candidate position, and the candidate position corresponds to at least one CCE resource block;

[0035] Based on each candidate location and its corresponding CCE resource block, the first PDCCH candidate set to be detected is generated.

[0036] In this embodiment, the multi-terminal simulator currently employs a fully hardware-based blind detection architecture based on FPGA when performing blind detection of the Physical Downlink Control Channel (PDCCH), and achieves concurrent blind detection of multiple terminals through parallel replication of a single-terminal blind detection module. However, in this blind detection method, each terminal independently performs blind detection within the same search space. If a CCE (Control Channel Element) resource has already been successfully blind-detected and decoded into a valid DCI (Downlink Control Information) by a preceding terminal and occupied, subsequent terminals will still repeatedly perform blind detection on the already occupied resource, resulting in a large amount of invalid computation.

[0037] To address the aforementioned issues, this embodiment constructs a global resource occupancy table GROT, which is used to share and perform parallel reading and writing of CCE resource occupancy status among multiple terminals to avoid redundant blind detection of resources. A pruning and filtering mechanism is also introduced, whereby GROT is queried before subsequent terminals perform blind detection to filter out CCE resources that have already been occupied, thereby achieving a hierarchical reduction in the number of blind detections.

[0038] Specifically, before the first terminal performs blind detection, the potential control channel locations that need to be detected should be determined for the first terminal. This includes:

[0039] 1. Protocol Parameter Configuration: First, configure the unique protocol parameters for the first terminal. Protocol parameters typically include, but are not limited to: the terminal's Radio Network Temporary Identifier (RNTI), used to identify its identity at the physical layer; and the downlink control information (DCI) format that needs to be monitored (such as DCI format 0_0, 1_0, etc.), which defines the length and structure of the control information.

[0040] 2. Search Space Calculation: Based on the aforementioned protocol parameters and the rules defined in 3GPP TS 38.213 and other protocol specifications, the PDCCH search space of the first terminal within the current slot is calculated using hardware logic or embedded software. The search space is a set of candidate positions determined by the protocol algorithm. Each candidate position corresponds to a specific Control Channel Unit (CCE) index or a resource block composed of multiple consecutive CCEs (the number of which is determined by the aggregation level and can be 1, 2, 4, 8, or 16).

[0041] 3. Candidate Set Generation: All calculated candidate positions and their corresponding CCE resource block indices are organized into an ordered list or bitmap, thus generating the first PDCCH candidate set to be detected. This candidate set is used to define all possible positions where the first terminal needs to perform blind detection within this time slot.

[0042] S102. Based on the preset global resource occupancy table, obtain the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected;

[0043] In this embodiment, the global resource occupancy table GROT serves as a central database shared by all terminals, used to record the occupancy status of each CCE resource. When a terminal successfully decodes the DCI and occupies a CCE resource, GROT is immediately updated, marking the corresponding CCE as occupied. Specifically, this includes:

[0044] 1. Accessing the Global Resource Occupancy Table GROT: A global resource occupancy table GROT is pre-established in the FPGA Block RAM (BRAM) or a mapping table in shared memory. This table uses the CCE resource block index as the key to store the current occupancy status of each CCE resource block (e.g., represented by 1 bit, '0' represents free, '1' represents occupied), and can selectively record the terminal identifier occupying the resource.

[0045] 2. Batch Query Status: The indexes of all CCE resource blocks contained in the first candidate PDCCH to be detected are used as input for the query request. The GROT is queried in parallel or serially through one or more read ports.

[0046] 3. Obtain Status Data: Receive the occupancy status data returned by GROT corresponding to each queried index. Obtain the occupancy status vector corresponding to the first candidate PDECH to be detected, where each bit identifies whether the corresponding CCE resource block has been occupied by another terminal.

[0047] S103. Remove the CCE resource blocks whose occupation status is occupied from the first PDCCH candidate set to be detected, and obtain the target PDCCH candidate set, so as to perform pruning and filtering on the first PDCCH candidate set to be detected.

[0048] In this embodiment, a pruning and filtering mechanism is used to achieve resource sharing via GROT. Before any terminal begins its PDCCH blind detection process, it first queries GROT. If GROT shows that a certain CCE resource is already occupied by another terminal, the terminal will directly skip the blind detection of that CCE, thereby avoiding duplicate calculations and achieving a hierarchical decrease in the number of blind detections, reducing the waste of computing resources. Specifically, this includes:

[0049] 1. State Comparison and Filtering Decision: The occupied state vector is compared item by item with the first set of PDCCH candidate blocks to be detected. For each CCE resource block in the candidate set, it is determined whether its state in GROT is "occupied".

[0050] 2. Perform the removal operation: Based on the comparison results, generate a filter mask. Logically remove or mark all CCE resource blocks with a status of "occupied" from the inspection list. The removal or marking operation can be implemented through a hardware selector or multiplexer.

[0051] 3. Generating the target candidate set: After the elimination operation, the remaining CCE resource blocks with the status of "idle" constitute a new set, namely the target PDCCH candidate set. This candidate set is a subset of the original candidate set, thereby avoiding subsequent blind checks on occupied resources.

[0052] S104. Control the first terminal to perform blind PDCCH checks on each CCE resource block in the target PDCCH candidate set.

[0053] In this embodiment, blind checking is performed on the filtered and pruned resource set. Specifically, this includes:

[0054] 1. Schedule blind detection resources: Submit the target PDCCH candidate set to the blind detection processing engine corresponding to the first terminal. This engine can be a dedicated hardware pipeline implemented based on FPGA.

[0055] 2. Execute the blind detection process: Control the blind detection processing engine to sequentially execute the standard PDCCH blind detection process for each CCE resource block (or combination thereof) according to the order of the candidate set. This process includes: channel estimation, demodulation, rate matching, Polar code decoding, and CRC verification using the first terminal's own RNTI.

[0056] 3. Output blind detection results: The blind detection engine outputs the results of the decoding attempts. If the CRC check on a CCE resource block is successful and the RNTI matches, a valid DCI is output; otherwise, the next candidate position is tried.

[0057] In this embodiment, based on the global resource occupancy table, the occupancy status of CCE resource blocks among multiple terminals is recorded, realizing the sharing of CCE resource block occupancy status among multiple terminals. This provides a check-before-test mechanism, and before subsequent terminals perform blind detection, a pruning and filtering mechanism is added, realizing the pruning and filtering of the PDCCH blind detection process in a multi-terminal environment, which significantly improves the computational efficiency and blind detection efficiency.

[0058] Please see Figure 2 , Figure 2 This is a schematic flowchart of a multi-terminal downlink control channel blind detection method provided in an embodiment of this application.

[0059] like Figure 2As shown, the downlink control channel blind detection method for multiple terminals further includes step S105 after step S104, specifically steps S1051 to S1054.

[0060] S1051. When a blind detection request from the second terminal is detected, the priority of the second terminal and the second candidate set of PDCCH to be detected are obtained.

[0061] This embodiment further provides a priority arbitration mechanism. Specifically, it includes:

[0062] 1. Blind Test Request Detection: Blind test requests from various terminals are continuously monitored. When the second terminal (e.g., the terminal carrying URLLC services) is ready to perform a PDCCH blind test, it first sends a blind test request to the arbitration module. This request can be detected as a hardware interrupt signal or a specific instruction in the message queue.

[0063] 2. Priority Information Acquisition: Each terminal is assigned a priority level during initialization. This level is typically pre-defined based on its service type (eMBB, URLLC, mMTC) and stored in the configuration register. Upon detecting a request from a second terminal, the arbitration module immediately queries or receives the priority identifier (e.g., a numerical value, where a higher value indicates a higher priority) attached to the second terminal from the configuration table.

[0064] 3. Candidate Set Acquisition: Acquire the second candidate set of PDCCH to be detected generated for the second terminal. The generation method of this candidate set is the same as that of the first terminal, and it is calculated based on the potential search space of the second terminal's protocol parameters such as RNTI and DCI format.

[0065] S1052. Based on the global resource occupancy table, determine the CCE resource blocks that need to be preempted in the second PDCCH candidate set to be detected, and obtain the priority of the terminal occupying the CCE resource blocks that need to be preempted. The CCE resource blocks that need to be preempted are the CCE resource blocks whose occupancy status is occupied.

[0066] In this embodiment, the user performs the stage of identifying and comparing conflicting resources. Specifically, this includes:

[0067] 1. Query resource status: Submit the second set of PDCCH candidates to be detected to the global resource occupancy table GROT for querying, and obtain the current occupancy status of each CCE resource block.

[0068] 2. Identify Resources to be Preempted: Compare the query results with the second candidate set. Filter out CCE resource blocks in the second candidate set that are currently occupied in the GROT, and define these resource blocks as CCE resource blocks to be preempted. These resource blocks are the direct objects causing priority conflicts.

[0069] 3. Obtain the priority of the occupying party: For each CCE resource block that needs to be preempted, the arbitration module queries the occupying terminal identifier recorded in GROT, and then obtains the priority information of the terminal currently occupying the resource (i.e., the occupying terminal) from the system configuration.

[0070] S1053. When the priority of the second terminal is greater than the priority of the occupying terminal, a preemption instruction is generated, and the occupying terminal corresponding to the CCE resource block to be preempted in the global resource occupation table is updated to the second terminal.

[0071] In this embodiment, arbitration decisions and status changes are performed. Specifically, this includes:

[0072] 1. Priority Comparison and Decision: The arbitration module compares the priority of the second terminal with the priority of the occupying terminal. If the priority of the second terminal is indeed greater than the priority of the occupying terminal, the arbitration module makes a preemption decision.

[0073] 2. Generate a preemption command: Based on the preemption decision, the arbitration module generates a preemption command. This command includes, but is not limited to: the target CCE resource block index, the original occupying terminal identifier, and the new occupying terminal (second terminal) identifier.

[0074] 3. Forced Update GROT: The arbitration module performs a forced write operation on GROT. Based on the preemption instruction, the occupying terminal identifier field corresponding to the CCE resource block to be preempted is updated from the original occupying terminal to the second terminal. This update is mandatory and does not require the original occupying terminal to actively release it. At this point, the resource block is logically immediately allocated to the second terminal.

[0075] S1054. According to the preemption instruction, forcibly release the CCE resource block that needs to be preempted, and control the second terminal to perform a blind PDCCH check on the CCE resource block that needs to be preempted.

[0076] In this embodiment, the arbitration result is executed. Specifically, it includes:

[0077] 1. Resource Release Notification: The preemption command will also be sent to the processing unit related to the original occupying terminal, notifying it to forcibly release the occupation and related processing of the CCE resource block. This can cause it to suspend any ongoing subsequent operations related to the resource.

[0078] 2. Trigger blind detection of the second terminal: The arbitration module sends a permission signal to the blind detection processing engine of the second terminal, instructing it to perform a blind PDCCH detection on the preempted CCE resource block (which now belongs to it).

[0079] 3. Perform blind check: Control the blind check engine of the second terminal to initiate a blind check process for the CCE resource block to be preempted (which is already in its target candidate set and its status is available to it). After the blind check is successful, the second terminal will update GROT according to the process, at which time the occupant information will be confirmed as the second terminal.

[0080] By employing the methods described above, this embodiment further resolves resource conflicts between multiple terminals by ensuring the resources available for high-priority services. When a resource conflict occurs between a high-priority terminal and a low-priority terminal (i.e., when a high-priority terminal needs to perform a blind check on a CCE resource, but that resource is already occupied or being processed by a low-priority terminal), the arbitration module allows the high-priority terminal to preempt the resource and notifies the low-priority terminal to release or suspend its occupation of the resource. This forces a resource reallocation, ensuring that blind check requests for high-priority services are processed first, thereby meeting their requirements for low latency and high reliability. This resolves the cross-terminal resource conflict problem and improves service adaptability.

[0081] Please see Figure 3 , Figure 3 This is a schematic flowchart of a multi-terminal downlink control channel blind detection method provided in an embodiment of this application.

[0082] like Figure 3 As shown, after step S103, there are also steps S106 and S107:

[0083] S106, when there is a first downlink control information that is successfully blind-decoded and valid in the target PDCCH candidate set, the occupancy status of the first CCE resource block corresponding to the first downlink control information is updated to occupied in the global resource occupancy table, and the occupancy terminal identifier of the first CCE resource block is recorded according to the first terminal identifier.

[0084] In this embodiment, the user implements updating the global resource usage status after a successful blind detection, specifically including:

[0085] 1. Blind test result verification and valid DCI determination

[0086] 1.1 Blind Detection Decoding Execution: Control the first terminal to perform blind PDCCH detection on each CCE resource block (or combination thereof) in the target PDCCH candidate set. The blind detection processing engine decodes each candidate position in the candidate set in sequence. This process includes a series of physical layer signal processing operations such as demodulation, derate matching, and Polar decoding.

[0087] 1.2 CRC Check and RNTI Verification: Cyclic redundancy check is performed on the downlink control information (DCI) obtained from blind detection decoding. First, the received CRC checksum is descrambled using the Radio Network Temporary Identifier (RNTI) of the first terminal. Then, the local CRC value of the DCI data is calculated. If the descrambled CRC code is completely consistent with the locally calculated CRC value, the CRC check is considered successful, and the RNTI match is considered successful.

[0088] 1.3 Valid DCI Confirmation: The system confirms that the current decoding is successful only when the CRC check passes and the RNTI matches, determines that the DCI is a valid downlink control information, and records the specific CCE resource block location where the decoding was successful.

[0089] 2. Determine the physical resource location corresponding to the valid DCI.

[0090] 2.1 Resource Block Index Acquisition: The system records the specific CCE resource block index where a valid DCI is successfully decoded. For cases where the aggregation level is greater than 1, it is necessary to record the starting index and length of the set of consecutive CCE resource blocks occupied by the DCI.

[0091] 2.2 First CCE Resource Block Identifier: The CCE resource block (or set of resource blocks) carrying the valid downlink control information is identified as the first CCE resource block. This identifier has a one-to-one correspondence with the physical resource location.

[0092] 2.3 Terminal Identity Confirmation: Simultaneously confirm the terminal identity of the valid DCI decoder, i.e., the first terminal identifier, which is usually the terminal's logical number or hardware instance identifier.

[0093] 3. Update the global resource usage table

[0094] 3.1 Occupancy Status Update: Initiate a write operation to the global resource occupancy table GROT to update the occupancy status of the first CCE resource block from idle to occupied. This update operation is achieved by setting the status bit of the corresponding CCE resource block index in GROT.

[0095] 3.2 Occupying Terminal Identifier Record: Write the first terminal identifier into the record item corresponding to the first CCE resource block in GROT. This identifier is stored as metadata and used for subsequent priority arbitration and conflict resolution.

[0096] 3.3 Atomicity Guarantee: The update operation is executed as an atomic transaction, ensuring the integrity and consistency of resource state changes in a multi-terminal concurrent access environment. In FPGA implementation, the atomicity of the update can be guaranteed through hardware mutual exclusion mechanisms or write locks.

[0097] Therefore, this embodiment achieves real-time updates of resource occupancy status, providing other terminals with the latest resource availability information. By establishing a precise mapping between DCI and physical CCE resource blocks, the accuracy of the updates is ensured. The identifier of the occupying terminal is recorded, providing necessary information for subsequent priority arbitration and conflict resolution. This effectively avoids repeated blind checks of the same CCE resource by multiple terminals, improving blind check efficiency and resource utilization, while providing a reliable data foundation for resource preemption by high-priority services.

[0098] Step S1071: Perform false detection verification on the first downlink control information through the upper-layer protocol stack;

[0099] In this embodiment, this step is a crucial verification stage for false detection identification, used to discover logical errors that the physical layer CRC check cannot recognize. Specifically, it includes:

[0100] 1. DCI Content Parsing: Parse the first downlink control information that the physical layer has determined to be valid and successfully decoded according to the format specified in the protocol, and extract each information field, including but not limited to: resource allocation indication, modulation and coding scheme, hybrid automatic repeat request process number, new data indication bit, power control command, etc.

[0101] 2. Protocol Rule Compliance Check: The upper-layer protocol stack (such as the MAC layer or RRC layer) verifies the protocol rule compliance of the parsed DCI content. The check includes:

[0102] Resource validity verification: Verify whether the frequency domain resource allocation indicated in the DCI is within the valid range of the current carrier bandwidth.

[0103] Parameter validity verification: Verify whether the values ​​of parameters such as modulation and coding scheme and antenna port are valid values ​​defined by the protocol.

[0104] State consistency verification: Combine the current state of the terminal (such as RRC connection state, active bandwidth portion) to verify whether the DCI command is valid in this state.

[0105] 3. Business logic rationality judgment: In addition to protocol rules, business logic rationality judgment may also be performed. For example, in specific test scenarios, certain extreme scheduling instructions (such as allocating extremely large or extremely small resource blocks) may be judged as not conforming to the expected business logic flow.

[0106] Step S1072: When the first downlink control information does not conform to the protocol rules and / or business logic of the upper-layer protocol stack, the first downlink control information is determined to be a false detection, and a rollback instruction is generated.

[0107] In this embodiment, this step is the stage of making decisions based on the verification results. Specifically, it includes:

[0108] 1. Verification Result Evaluation: Based on the combined results of the checks in step S1071, if the DCI content fully complies with all protocol rules and the business logic is reasonable, then the DCI is confirmed to be authentic and valid.

[0109] 2. False Detection: If any aspect of the DCI content is found to be inconsistent with protocol rules (such as resource index out of bounds) or significantly deviates from business logic, the successful decoding at the physical layer is determined to be a false detection. Such false detections are usually caused by coincidental CRC matches (i.e., false positives) due to factors such as channel noise and interference.

[0110] 3. Generate rollback instruction: Once a false detection is determined, the upper-layer protocol stack immediately generates a rollback instruction. This instruction is either a hardware interrupt signal or a message, which contains at least the following key information: the CCE resource block index corresponding to the falsely detected DCI, and the identifier of the first terminal currently erroneously occupying that resource.

[0111] Step S1073: According to the rollback instruction, in the global resource occupancy table, the occupancy status of the CCE resource block is rolled back from occupied to idle, and the occupancy terminal identifier of the first CCE resource block is cleared.

[0112] In this embodiment, this step is the execution phase for correcting errors and restoring resource availability. Specifically, it includes:

[0113] 1. Locating the target resource: The false detection rollback module receives the rollback instruction and, based on the CCE resource block index carried in the instruction, accurately locates the record item that needs to be corrected in the global resource occupancy table (GROT), namely the first CCE resource block.

[0114] 2. Status Rollback: Perform a write operation on GROT to change the occupancy status of the first CCE resource block located from occupied to free. This operation clears the erroneous occupancy markers caused by false detections.

[0115] 3. Clear the occupation identifier: At the same time, clear the occupation terminal identifier (i.e., the first terminal identifier) ​​associated with the first CCE resource block to ensure that the resource is unbound from any terminal.

[0116] 4. Atomicity operation: The entire rollback operation (state rollback and flag clearing) is designed as an atomic operation to ensure the correct recovery of resource state in a multi-terminal concurrent access environment and avoid intermediate states with inconsistent states.

[0117] This ensures that if a terminal incorrectly marks a CCE resource as valid and updates it to GROT due to a CRC check error (e.g., a false positive) during blind detection, the conflict rollback module will be triggered after detecting the false detection. This module is used to clear the erroneous resource occupancy mark in GROT, making the resource available again. This prevents subsequent terminals from continuously skipping the resource due to the erroneous mark, thus preventing the risk of missed detection.

[0118] To further prevent missed detections, this embodiment addresses the issue of a terminal incorrectly marking a CCE resource as valid due to a CRC false positive, which would lead to subsequent terminals continuously skipping that resource. A conflict rollback module is added to quickly clear erroneous resource occupancy marks caused by false detections (such as CRC false positives), further improving the accuracy of blind detection. Specifically, the closed-loop mechanism consisting of the three steps in S107 effectively compensates for the inherent defects of physical layer blind detection. It not only detects and corrects deep logical errors that physical layer CRC checks cannot identify, preventing the continued existence of erroneous resource occupancy states, but also enables rapid rollback operations (typically at the nanosecond level) to promptly release incorrectly occupied resources, reducing the risk of missed detections by subsequent terminals due to false detections. Furthermore, it maintains state consistency, ensuring that the resource status reflected in the global resource occupancy table matches the actual network status, thereby maintaining the reliable operation of the entire multi-terminal collaborative blind detection system.

[0119] The following is a further example for illustration:

[0120] Assume a multi-terminal concurrent 5G communication test scenario where terminal 1 (eMBB service, priority 2), terminal 2 (eMBB service, priority 1), and terminal 5 (URLLC service, priority 7) simultaneously perform PDCCH blind detection.

[0121] 1. Terminal 1 completes blind detection and occupies resources (pruning filtering mechanism and GROT application):

[0122] Terminal 1 (eMBB, priority 2) initiates blind detection.

[0123] After blind testing, terminal 1 successfully solved a valid DCI, which occupied CCE0-7 (aggregation degree 8).

[0124] Terminal 1 writes the occupancy information of CCE0-7 into the global resource occupancy table (GROT) through the write port of GROT and marks it as "occupied".

[0125] II. Terminal 2 performs pruning and filtering (application of pruning and filtering mechanism):

[0126] Terminal 2 (eMBB, priority 1) begins preprocessing in preparation for blind detection.

[0127] Before the actual blind test, the pruning and filtering module of terminal 2 will query GROT.

[0128] The GROT message indicates that CCE0-7 is already in use by terminal 1.

[0129] Based on the query results of GROT, the pruning and filtering module of terminal 2 generates a "skip blind detection" signal, which directly skips the blind detection of the CCE0-7 combination, thereby reducing the search space, avoiding repeated calculations, and saving computing power.

[0130] III. Terminal 5 performs priority preemption (application of hardware-based priority arbitration module):

[0131] Terminal 5 (URLLC, priority 7), as a high-priority service, has also begun preprocessing.

[0132] Terminal 5 needs to perform blind inspection on CCE resources, which include CCE8-11. Assume that CCE8-11 is currently occupied or being processed by the low-priority terminal 2.

[0133] The hardware-based priority arbitration module detected a priority conflict between terminal 5 (priority 7) and terminal 2 (priority 1).

[0134] Because terminal 5 has a higher priority, the arbitration module generates a "preemption enable" signal, allowing terminal 5 to preempt CCE8-11 resources.

[0135] Terminal 5 successfully preempted the resource and performed a blind check, while updating the occupied flag of CCE8-11 in GROT.

[0136] IV. Resource rollback after false detection in terminal 1 (application of conflict rollback module):

[0137] Suppose that at some point, the DCI (occupied CCE0-7) previously decoded by terminal 1 is further verified by the upper-layer protocol stack and its CRC check result is found to be a false positive.

[0138] At this point, the conflict rollback module is triggered.

[0139] The conflict rollback module will immediately clear the erroneous occupancy markers for terminal 1 to CCE0-7 in GROT.

[0140] Through the above rollback operation, the CCE0-7 resource is remarked as available without affecting the normal blind test process of other terminals. This prevents subsequent terminals from continuously skipping the resource due to incorrect marking, thereby preventing the risk of missed detection.

[0141] The above embodiments enable the coordinated operation of GROT, pruning filtering, priority arbitration, and conflict rollback, solving the problems of resource waste, latency, conflict, and false detection in multi-terminal concurrent blind detection.

[0142] In one embodiment, before step S102, the method further includes:

[0143] A. Generate a global resource occupancy table containing the indexes of each CCE resource block, and initialize the occupancy status of each CCE resource block in the global resource occupancy table to an idle state;

[0144] This embodiment includes the generation, initialization, and dynamic updating of the global resource usage table GROT, specifically including:

[0145] 1. Generation and initialization of the global resource occupancy table (GROT)

[0146] 1.1 Determining Resource Scope and Establishing Indexes: Based on the communication system's configuration parameters (such as carrier bandwidth and the configuration of the control resource set CORESET), determine all available control channel element (CCE) resource blocks that can be used for PDCCH transmission in the current cell or simulated environment. Assign a unique index number to each CCE resource block, which typically corresponds to its physical location order in the time-frequency resource grid.

[0147] 1.2 Creating the Global Resource Occupancy Table (GROT) Data Structure: In the shared storage medium (such as the Block RAM of an FPGA), create a mapping table named Global Resource Occupancy Table (GROT). The core data area of ​​this table uses the CCE resource block index as the key field. Each record corresponding to the index contains at least two data fields: an occupancy status bit (which can be represented by 1 bit) and an occupancy terminal identifier (used to record the terminal ID occupying the resource, the bit width of which is determined by the maximum number of terminals supported by the system).

[0148] 1.3 Initialization Operation: At the start of each blind detection cycle (e.g., at the beginning of each time slot) or system startup, the GROT initialization process is executed. All records in GROT are traversed, and the occupancy status bit of each record is uniformly set to a predefined value representing an idle state (e.g., logic '0'), while simultaneously clearing its occupancy terminal identifier field or setting it to a special null value indicating "unoccupied". This operation ensures that all CCE resources are available at the start of the cycle, providing an initial environment for subsequent resource allocation.

[0149] 2. Dynamic updates based on valid blind test results

[0150] 2.1 Valid Downlink Control Information (DCI) Detection: The system continuously monitors the output of the blind detection processing engine of all terminals. When the blind detection engine of any terminal (taking the first terminal as an example) reports successful decoding, and the DCI is confirmed as valid downlink control information through CRC verification and RNTI matching, the GROT update process is triggered.

[0151] 2.2 Locating the Detected CCE Resource Block: Based on the information carried in the successful blind test report, accurately determine the physical resource location carrying this valid DCI, i.e., the index of the detected CCE resource block. For DCIs with an aggregation level greater than 1, it is necessary to determine the starting index and number of consecutive CCE resource blocks they occupy.

[0152] 2.3 Update Occupancy Status and Record Occupancy Terminal: Initiate a write operation to GROT. The target address of this operation is the index record corresponding to the inspected CCE resource block. The specific update content is as follows:

[0153] Update the occupancy status bit of the record from a value representing "free" (e.g., '0') to a value representing "occupied" (e.g., '1').

[0154] Write the terminal identifier field of the record into the unique identifier of the terminal that successfully decoded the valid DCI (i.e., the first terminal).

[0155] 2.4 Atomicity Guarantee and Concurrency Control: This update operation is designed to be atomic. In a multi-terminal concurrent environment, hardware mutex mechanisms or the atomic write operation characteristics of memory are used to prevent read-write conflicts during the update process, ensuring the consistency of resource states in the GROT. This update makes the state of the CCE resource block visible to all terminals sharing this GROT.

[0156] By employing the above methods, a global resource state center was established and maintained, ensuring that the system starts working from a known and definite initial state in each processing cycle. This allows any successful blind detection from a terminal to be instantly converted into globally shared state information, enabling real-time collaboration between terminals, thereby avoiding duplicate resource detection and improving blind detection efficiency. Atomic operations and precise resource location ensure the accuracy and integrity of GROT data, providing a data foundation for subsequent pruning filtering and priority arbitration.

[0157] B. When a terminal detects and decodes valid downlink control information, the occupancy status of the detected CCE resource block corresponding to the valid downlink control information is updated from idle to occupied in the global resource occupancy table, and the occupancy terminal identifier of the detected CCE resource block is recorded.

[0158] In this embodiment, after detecting valid downlink control information (DCI), the global resource occupancy table is updated to convert the successful blind detection result of the terminal into globally shared resource status information in real time and accurately. Specifically, this includes:

[0159] 1. Detection and triggering of effective downlink control information (DCI)

[0160] 1.1 Monitoring Blind Detection Result Output: The system's resource management module continuously monitors the output status registers or message queues of all terminal blind detection processing engines. When the blind detection engine of any terminal (e.g., the first terminal) completes the blind detection decoding of a candidate control channel element (CCE) resource block or a combination thereof, it outputs a blind detection result report. This report contains the decoded data bit stream, the cyclic redundancy check (CRC) result, and the Radio Network Temporary Identifier (RNTI) information used for verification.

[0161] 1.2 Validity Determination: The resource management module reads the result report and determines its validity. The determination criteria are: CRC check passes (indicating that no errors occurred during data transmission) and RNTI matches successfully (indicating that the DCI was indeed sent from the network to this terminal). Only when both of these conditions are met simultaneously is a valid downlink control information (DCI) confirmed to have been detected, and the subsequent global resource occupancy table (GROT) update process is immediately triggered.

[0162] 2. Determine the physical resource location corresponding to the valid DCI.

[0163] 2.1 Parsing the blind detection context: The resource management module obtains the specific CCE resource block index corresponding to this successful blind detection from the blind detection result report that triggered the update, or by querying the context status of the blind detection engine.

[0164] 2.2 Identify Checked CCE Resource Blocks: Explicitly identify the physical resource pointed to by this index as a checked CCE resource block. If the aggregation level of the valid DCI is greater than 1, i.e. it is carried by multiple consecutive CCEs, then the starting index and length of the CCE resource block combination must be identified.

[0165] 2.3 Confirm the identity of the occupying terminal: At the same time, identify the source of this valid blind test result, namely the first terminal, and obtain its unique terminal identifier.

[0166] 3. Perform an update operation on the global resource usage table (GROT).

[0167] 3.1 Preparing Updated Data: The resource management module prepares the data packet to be written to GROT. This data packet contains:

[0168] 3.2 Target address: i.e., the index of the detected CCE resource block determined in the above embodiments.

[0169] 3.3 Update content: Set the occupancy status bit to a value indicating "occupied" (e.g., logic '1'), and fill the identifier of the first terminal into the occupancy terminal identifier field.

[0170] 3.4 Initiating an Atomic Write Operation: The resource management module initiates a write operation to GROT via a dedicated write port or write bus. This operation is designed to be atomic, ensuring that in a multi-terminal concurrent access environment, the update either completes entirely or is not executed at all, avoiding intermediate states such as data corruption or inconsistencies. In FPGA implementations, this can be guaranteed through hardware mutexes or atomic write instructions within the memory itself.

[0171] 3.5 Confirmation of Update Completion: After the write operation is completed, the optional confirmation mechanism will return a success signal. At this point, the status of the checked CCE resource block in GROT has been successfully updated from idle to occupied, and its occupant has been recorded as the first terminal.

[0172] In this embodiment, terminal-level blind detection success events are transformed into system-level global state changes, enabling other terminals to perceive resource usage. By binding a valid DCI to its underlying physical resource (CCE index), it ensures that each update targets the correct objective, avoiding incorrect labeling. Through a dynamic update mechanism, a collaborative strategy of "query first, then blind detection" is implemented, fundamentally preventing multiple terminals from performing duplicate invalid detections on the same resource, thus improving the overall blind detection efficiency of the multi-terminal simulator.

[0173] For example, before detecting that the terminal has blindly decoded valid downlink control information, the method further includes:

[0174] Cyclic redundancy check is performed on the downlink control information decoded by the terminal blind detection.

[0175] The downlink control information decoded by the terminal in the blind detection is determined to be valid downlink control information by passing the cyclic redundancy check.

[0176] In this embodiment, the Cyclic Redundancy Check (CRC) verification includes: using the Radio Network Temporary Identifier (RNTI) of the first terminal to descramble the received CRC checksum, and verifying whether the descrambled CRC code is consistent with the local CRC code calculated based on the DCI data; if they are consistent, the DCI is determined to be a valid DCI.

[0177] Cyclic Redundancy Check (CRC) is performed on the downlink control information (DCI) obtained by blind detection decoding. If the CRC check result of the DCI passes and the RNTI used for verification is consistent with the RNTI of the first terminal, then the DCI is determined to be a valid DCI.

[0178] Understandably, the base station simultaneously sends PDCCH commands to numerous terminals within the cell. These commands are broadcast over the air interface, and all terminals can receive them. To distinguish which command is sent to which terminal, the base station uses a unique RNTI for each terminal as an "identity tag." This tag is appended to the DCI using a CRC mask. Through RNTI scrambling, even if two terminals have identical DCI content, their final CRC checksums will be completely different due to the different RNTIs. This allows terminals to clearly distinguish commands and avoid erroneous reception.

[0179] In one embodiment, after a CRC check has been passed and the result is determined to be "valid", the upper-layer protocol stack may further parse the result and find that the content violates the protocol or logic, thus determining it to be a false detection.

[0180] If the CRC check result of the DCI passes and its CRC mask matches the Wireless Network Temporary Identifier (RNTI) of the first terminal, the DCI is determined to be a valid physical layer DCI, and the global resource occupancy table is updated accordingly. When the valid physical layer DCI is subsequently parsed by the upper-layer protocol stack, if it is confirmed that its content does not conform to the protocol rules or business logic, a false detection by the higher layer is determined to have occurred, and a rollback instruction is generated.

[0181] Furthermore, a hierarchical search space reservation and active pruning module is introduced to manage high-priority terminal search space resources. Specifically, this includes:

[0182] 1. Enhanced Global Resource Occupancy Table (GROT_E): This expands upon the GROT table by adding a "Reserved Status" bit to each CCE resource. In addition to the existing "Occupied" status, it can also be marked as "High Priority Reserved".

[0183] 2. Hierarchical Search Space Reservation and Active Pruning Module (HSSPRM): Works closely with GROT_E, the pruning and filtering module, and the priority arbitration module.

[0184] 3. Modified pruning and filtering module: When querying GROT_E, it not only filters the CCEs that are already in use, but also further filters the CCEs reserved by high-priority terminals.

[0185] 4. Modified Priority Arbitration Module: Works in conjunction with HSSPRM to handle potential conflicts during the reservation phase and supports forced clearing commands initiated by HSSPRM.

[0186] For example, the global resource occupancy table also records the reservation status of each CCE resource block;

[0187] The step of obtaining the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected based on a preset global resource occupancy table specifically includes:

[0188] Obtain the occupancy and reservation status of each CCE resource block in the first PDCCH candidate set to be detected;

[0189] The step of removing CCE resource blocks with an occupied status from the first PDCCH candidate set to be detected, to obtain the target PDCCH candidate set, specifically includes:

[0190] From the first set of PDCCH candidates to be detected, remove the CCE resource blocks whose occupancy status is occupied or whose reservation status is reserved to obtain the target PDCCH candidate set.

[0191] The above embodiment provides a scheme where a low-priority terminal occupies resources first, then a high-priority terminal needs those resources, triggering arbitration for preemption. However, high-priority services still need to wait for the preemption process to complete, causing delays. To further reduce latency, this embodiment provides a mechanism from reactive preemption to proactive reservation. That is, before a high-priority terminal begins blind detection, the resources it might need are reserved in advance, thereby avoiding conflicts with low-priority services from the outset.

[0192] Specifically, in the Global Resource Occupancy Table (GROT), in addition to the two states of Idle and Occupied, a third state has been added: High-Priority Reserved. This includes:

[0193] 1. Enhanced Global Resource Consumption Table (GROT_E)

[0194] Based on the original GROT, a reservation status bit has been added to each CCE resource block. Therefore, the status of each CCE resource can be: 00: Idle; 01: High priority reserved; 10: Occupied.

[0195] The global resource occupancy table serves as a central database, recording both the current resource occupancy status and future reservation status.

[0196] 2. Hierarchical Search Space Reservation and Active Pruning Module (HSSPRM)

[0197] The control module enables proactive management. When a high-priority terminal (such as a URLLC service) prepares for blind detection, HSSPRM receives its complete potential search space information (i.e., the set of all CCEs that may need to be detected) before the terminal itself. Specifically, this includes:

[0198] Query and Reservation: HSSPRM immediately queries GROT_E. For all CCEs in the search space with a status of "Idle", HSSPRM will attempt to change their status to "High Priority Reservation".

[0199] Pre-clearing (forced clearing): If a CCE resource is found to be in a "being processed by a low-priority terminal" state (this state can be provided by the arbitration module or the extended status bit of GROT_E), HSSPRM will immediately send a "forced clearing instruction" to the low-priority terminal through the modified priority arbitration module, requesting it to stop processing and release the resource. This is a proactive intervention before a conflict occurs.

[0200] 3. Modified pruning and filtering module

[0201] The optimization strategy execution unit, when any terminal (especially a low-priority terminal) queries GROT_E before blind detection, filters out CCE resource blocks in the state of being occupied, and further filters out CCE resource blocks in the state of being reserved for high priority, thereby avoiding conflicts at the source.

[0202] 4. Modified priority arbitration module

[0203] Receives and executes the forced clear command sent by HSSPRM. When HSSPRM needs to pre-clear resources, the arbitration module uses its hardware priority arbitration logic to force low-priority terminals to abort their operations on the target resource.

[0204] The following is a further specific embodiment for illustration:

[0205] This embodiment maintains a global resource occupancy table (GROT), enabling multiple terminals to collaboratively share channel resource occupancy status during blind detection of the Physical Downlink Control Channel (PDCCH). This avoids repeated blind detection of already occupied resources and achieves priority-based resource arbitration and false detection recovery. The method mainly includes key steps such as resource state initialization, candidate set pruning and filtering, blind detection execution and verification, priority preemption, and false detection rollback. These steps form a data interaction closed loop through the GROT, ensuring system state consistency. Specifically, it includes:

[0206] 1. Resource state initialization and candidate set generation

[0207] First, resource initialization is required when the system is running or at the start of a new blind detection cycle. Specifically, a global resource occupancy table (GROT) is generated, which is indexed to all available control channel element (CCE) resource blocks, and the occupancy status of each CCE resource block is initialized to an idle state (step S301).

[0208] Subsequently, a PDCCH candidate set to be detected is generated for each terminal initiating blind detection (taking the first terminal as an example). This process includes: obtaining the protocol configuration parameters corresponding to the first terminal, such as its Radio Network Temporary Identifier (RNTI) and the downlink control information (DCI) format to be monitored; calculating the search space of the first terminal in the current time slot based on the protocol configuration parameters and 3GPP protocol rules, which consists of multiple candidate positions, each candidate position corresponding to one or more consecutive CCE resource blocks (i.e., a specific aggregation level); finally, generating the first PDCCH candidate set to be detected for the first terminal based on all candidate positions and their corresponding CCE resource block indices (step S701).

[0209] 2. Pruning and filtering based on global resource state

[0210] After obtaining the first set of candidate PDCCHs to be detected, instead of immediately performing a computationally intensive blind detection operation, pruning and filtering are first performed to improve efficiency. Specifically, the global resource occupancy table (GROT) is queried to obtain the current occupancy status of each CCE resource block in the first set of candidate PDCCHs to be detected (step S101).

[0211] Next, the occupancy status obtained from the query is compared with the candidate set, and all CCE resource blocks with an occupancy status of "occupied" are removed from the first PDCCH candidate set to be detected. This step ensures that subsequent blind detection is only performed on currently unoccupied resources, avoiding invalid calculations. After the removal operation, a target PDCCH candidate set with a significantly reduced size is obtained (step S102).

[0212] 3. Blind inspection execution and resource status update

[0213] The first terminal is controlled to perform blind PDCCH checks on each remaining CCE resource block (or combination thereof) in the target PDCCH candidate set (step S103). The blind check process includes conventional operations such as demodulation, decoding, and CRC verification.

[0214] The downlink control information (DCI) obtained by blind detection decoding needs to be validated. First, a cyclic redundancy check (CRC) is performed on it. If the check passes and the CRC mask used for the check matches the RNTI of the first terminal, then a valid DCI is determined to have been successfully decoded (step S501).

[0215] Once a valid DCI is determined to be decoded, the Global Resource Occupancy Table (GROT) is immediately updated. The occupancy status of the specific CCE resource block (or combination thereof) carrying the valid DCI is changed from idle to occupied, and the identifier of the first terminal is recorded as the occupying terminal (step S502). This update operation is crucial for providing other terminals with the latest resource status.

[0216] 4. Priority Conflict Arbitration Mechanism

[0217] To support the quality of service for multiple services, this invention introduces a priority arbitration mechanism. When the system detects that a second terminal with a higher priority (e.g., a terminal carrying URLLC services) initiates a blind inspection request, and the CCE resource block to be inspected (the CCE resource block to be preempted) has been occupied by a lower priority terminal, the arbitration process is triggered (step S201).

[0218] The arbitration module obtains the priority of the second terminal and the priority of the terminal currently occupying the CCE resource block to be preempted (the occupying terminal). If the comparison confirms that the priority of the second terminal is higher, a preemption instruction is generated (step S202). Subsequently, according to the instruction, the CCE resource block to be preempted is forcibly released, and the identifier of the occupying terminal in GROT is updated to the second terminal (step S203). Finally, the second terminal is controlled to perform a blind PDCCH check on the preempted CCE resource block, thereby ensuring the low latency requirements of high-priority services (step S204).

[0219] 5. False alarm detection and status rollback

[0220] To handle logical errors that physical layer verification cannot identify, this invention also sets up a false detection rollback mechanism. After the valid DCI is reported to the upper-layer protocol stack (such as the MAC layer or RRC layer), the protocol stack will further parse its content to verify whether it conforms to the protocol rules or business logic (step S601).

[0221] If the verification finds that the DCI content contains errors or contradictions (e.g., the scheduled resource index is invalid), then the successful decoding is determined to be a false positive, and a rollback instruction is generated (step S602).

[0222] According to the rollback instruction, the system will locate the CCE resource block recorded in GROT that was occupied by the falsely detected DCI, roll back its occupation status from occupied to idle, and clear the relevant occupation terminal identifier (step S603). This mechanism effectively prevents permanent resource locking and subsequent terminal missed detection problems caused by false detection, ensuring the robustness of the system.

[0223] In summary, this invention constructs an efficient and reliable multi-terminal PDCCH blind detection collaborative processing flow through the aforementioned interconnected steps. The Global Resource Occupancy Table (GROT), serving as a shared state center, connects modules such as pruning filtering, priority arbitration, and false detection rollback, enabling multiple terminals to intelligently avoid conflicts, safeguard critical business operations, and recover from erroneous states, significantly improving the overall system's resource utilization efficiency and reliability.

[0224] Please see Figure 4 , Figure 4 This application provides a schematic block diagram of a downlink control channel blind detection device for multiple terminals, which is used to execute the aforementioned downlink control channel blind detection method for multiple terminals. The downlink control channel blind detection device for multiple terminals can be configured on a server.

[0225] like Figure 4 As shown, the downlink control channel blind detection device 400 for the multi-terminal includes:

[0226] Data caching module 410 is used to obtain the first physical downlink control channel (PDCCH) candidate set of the first terminal, the PDCCH candidate set including at least one control channel element (CCE) resource block;

[0227] The pruning and filtering module 420 is used to obtain the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected based on a preset global resource occupancy table.

[0228] The pruning and filtering module is further configured to remove the CCE resource blocks whose occupancy status is occupied from the first PDCCH candidate set to be detected, so as to obtain the target PDCCH candidate set and perform pruning and filtering on the first PDCCH candidate set to be detected.

[0229] The blind detection decoding module 430 is used to control the first terminal to perform blind PDCCH detection on each CCE resource block in the target PDCCH candidate set.

[0230] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the above-described apparatus and modules can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0231] The aforementioned device can be implemented as a computer program, which can be used in, for example... Figure 5 It runs on the computer device shown.

[0232] Please see Figure 5 , Figure 5This is a schematic block diagram illustrating the structure of a computer device according to an embodiment of this application. The computer device may be a server.

[0233] See Figure 5 The computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include non-volatile storage media and internal memory.

[0234] The non-volatile storage medium can store an operating system and a computer program. This computer program includes program instructions that, when executed, cause the processor to perform any multi-terminal downlink control channel blind detection method.

[0235] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0236] Internal memory provides an environment for the execution of computer programs stored in non-volatile storage media. When executed by a processor, the computer program enables the processor to perform any type of blind detection method for downlink control channels across multiple terminals.

[0237] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0238] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0239] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps:

[0240] Obtain the first candidate set of physical downlink control channel (PDCCH) to be detected for the first terminal. The PDCCH candidate set includes at least one control channel element (CCE) resource block.

[0241] Based on the preset global resource occupancy table, the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected is obtained;

[0242] From the first PDCCH candidate set to be detected, remove the CCE resource blocks whose occupation status is occupied to obtain the target PDCCH candidate set, so as to perform pruning filtering on the first PDCCH candidate set to be detected;

[0243] The first terminal is controlled to perform blind PDCCH checks on each CCE resource block in the target PDCCH candidate set.

[0244] In one embodiment, the processor is further configured to implement:

[0245] When a blind detection request from a second terminal is detected, the priority of the second terminal and the second set of PDCCH candidates to be detected are obtained.

[0246] Based on the global resource occupancy table, the CCE resource blocks that need to be preempted in the second PDCCH candidate set to be detected are determined, and the priority of the terminal occupying the CCE resource block that needs to be preempted is obtained. The CCE resource blocks that need to be preempted are the CCE resource blocks whose occupancy status is occupied.

[0247] When the priority of the second terminal is greater than the priority of the occupying terminal, a preemption instruction is generated, and the occupying terminal corresponding to the CCE resource block to be preempted in the global resource occupancy table is updated to the second terminal;

[0248] According to the preemption command, the preemptible CCE resource block is forcibly released, and the second terminal is controlled to perform a blind PDCCH check on the preemptible CCE resource block.

[0249] In one embodiment, the processor is further configured to implement:

[0250] Generate a global resource occupancy table containing the indexes of each CCE resource block, and initialize the occupancy status of each CCE resource block in the global resource occupancy table to an idle state;

[0251] When a terminal detects and decodes valid downlink control information, the occupancy status of the detected CCE resource block corresponding to the valid downlink control information is updated from idle to occupied in the global resource occupancy table, and the occupancy terminal identifier of the detected CCE resource block is recorded.

[0252] In one embodiment, the processor is further configured to implement:

[0253] Cyclic redundancy check is performed on the downlink control information decoded by the terminal blind detection.

[0254] The downlink control information decoded by the terminal in the blind detection is determined to be valid downlink control information by passing the cyclic redundancy check.

[0255] In one embodiment, the processor is further configured to implement:

[0256] When the target PDCCH candidate set contains first downlink control information that has been successfully decoded by blind detection and is valid, the occupancy status of the first CCE resource block corresponding to the first downlink control information is updated to occupied in the global resource occupancy table, and the occupancy terminal identifier of the first CCE resource block is recorded according to the first terminal identifier.

[0257] In one embodiment, the processor is further configured to implement:

[0258] The first downlink control information is checked for false positives using the upper-layer protocol stack.

[0259] If the first downlink control information does not conform to the protocol rules and / or business logic of the upper-layer protocol stack, the first downlink control information is determined to be a false detection, and a rollback instruction is generated.

[0260] According to the rollback instruction, in the global resource occupancy table, the occupancy status of the CCE resource block is rolled back from occupied to idle, and the occupancy terminal identifier of the first CCE resource block is cleared.

[0261] In one embodiment, the processor is further configured to: obtain protocol configuration parameters corresponding to the first terminal, wherein the protocol configuration parameters include an wireless network temporary identifier and / or downlink control information;

[0262] Based on the protocol configuration parameters, the search space of the first terminal is calculated, the search space includes at least one candidate position, and the candidate position corresponds to at least one CCE resource block;

[0263] Based on each candidate location and its corresponding CCE resource block, the first PDCCH candidate set to be detected is generated.

[0264] The embodiments of this application also provide a computer-readable storage medium storing a computer program, the computer program including program instructions, and the processor executing the program instructions to implement any of the downlink control channel blind detection methods for multiple terminals provided in the embodiments of this application.

[0265] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.

[0266] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for blind detection of downlink control channels in multiple terminals, characterized in that, include: Obtain the protocol configuration parameters corresponding to the first terminal, wherein the protocol configuration parameters include an wireless network temporary identifier and / or downlink control information; Based on the protocol configuration parameters, the search space of the first terminal is calculated, the search space includes at least one candidate position, and the candidate position corresponds to at least one CCE resource block; Based on each candidate location and its corresponding CCE resource block, a first set of PDCCH candidates to be detected is generated. Obtain the first candidate set of physical downlink control channel (PDCCH) to be detected for the first terminal. The PDCCH candidate set includes at least one control channel element (CCE) resource block. Based on the preset global resource occupancy table, the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected is obtained; From the first PDCCH candidate set to be detected, remove the CCE resource blocks whose occupation status is occupied to obtain the target PDCCH candidate set, so as to perform pruning filtering on the first PDCCH candidate set to be detected; Control the first terminal to perform blind PDCCH checks on each CCE resource block in the target PDCCH candidate set; When a blind detection request from a second terminal is detected, the priority of the second terminal and the second set of PDCCH candidates to be detected are obtained. Based on the global resource occupancy table, the CCE resource blocks that need to be preempted in the second PDCCH candidate set to be detected are determined, and the priority of the terminal occupying the CCE resource block that needs to be preempted is obtained. The CCE resource blocks that need to be preempted are the CCE resource blocks whose occupancy status is occupied. When the priority of the second terminal is greater than the priority of the occupying terminal, a preemption instruction is generated, and the occupying terminal corresponding to the CCE resource block to be preempted in the global resource occupancy table is updated to the second terminal; According to the preemption command, the preemptible CCE resource block is forcibly released, and the second terminal is controlled to perform a blind PDCCH check on the preemptible CCE resource block.

2. The downlink control channel blind detection method for multiple terminals according to claim 1, characterized in that, Before obtaining the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected based on a preset global resource occupancy table, the method further includes: Generate a global resource occupancy table containing the indexes of each CCE resource block, and initialize the occupancy status of each CCE resource block in the global resource occupancy table to an idle state; When a terminal detects and decodes valid downlink control information, the occupancy status of the detected CCE resource block corresponding to the valid downlink control information is updated from idle to occupied in the global resource occupancy table, and the occupancy terminal identifier of the detected CCE resource block is recorded.

3. The downlink control channel blind detection method for multiple terminals according to claim 2, characterized in that, Before detecting that the terminal has blindly decoded valid downlink control information, the process also includes: Cyclic redundancy check is performed on the downlink control information decoded by the terminal blind detection. The downlink control information decoded by the terminal in the blind detection is determined to be valid downlink control information by passing the cyclic redundancy check.

4. The downlink control channel blind detection method for multiple terminals according to claim 1, characterized in that, After controlling the first terminal to perform blind PDCCH checks on each CCE resource block in the target PDCCH candidate set, the method further includes: When the target PDCCH candidate set contains first downlink control information that has been successfully decoded by blind detection and is valid, the occupancy status of the first CCE resource block corresponding to the first downlink control information is updated to occupied in the global resource occupancy table, and the occupancy terminal identifier of the first CCE resource block is recorded according to the first terminal identifier.

5. The downlink control channel blind detection method for multiple terminals according to claim 4, characterized in that, The method further includes: The first downlink control information is checked for false positives using the upper-layer protocol stack. If the first downlink control information does not conform to the protocol rules and / or business logic of the upper-layer protocol stack, the first downlink control information is determined to be a false detection, and a rollback instruction is generated. According to the rollback instruction, in the global resource occupancy table, the occupancy status of the CCE resource block is rolled back from occupied to idle, and the occupancy terminal identifier of the first CCE resource block is cleared.

6. A downlink control channel blind detection device for multiple terminals, characterized in that, include: The data caching module is used to obtain the first physical downlink control channel (PDCCH) candidate set of the first terminal to be detected. The PDCCH candidate set includes at least one control channel element (CCE) resource block. The pruning and filtering module is used to obtain the occupancy status of each CCE resource block in the first PDCCH candidate set to be detected based on a preset global resource occupancy table. The pruning and filtering module is further configured to remove the CCE resource blocks whose occupancy status is occupied from the first PDCCH candidate set to be detected, so as to obtain the target PDCCH candidate set and perform pruning and filtering on the first PDCCH candidate set to be detected. The blind detection decoding module is used to control the first terminal to perform blind PDCCH detection on each CCE resource block in the target PDCCH candidate set; The device is also used for: When a blind detection request from a second terminal is detected, the priority of the second terminal and the second set of PDCCH candidates to be detected are obtained. Based on the global resource occupancy table, the CCE resource blocks that need to be preempted in the second PDCCH candidate set to be detected are determined, and the priority of the terminal occupying the CCE resource block that needs to be preempted is obtained. The CCE resource blocks that need to be preempted are the CCE resource blocks whose occupancy status is occupied. When the priority of the second terminal is greater than the priority of the occupying terminal, a preemption instruction is generated, and the occupying terminal corresponding to the CCE resource block to be preempted in the global resource occupancy table is updated to the second terminal; According to the preemption command, the CCE resource block to be preempted is forcibly released, and the second terminal is controlled to perform a blind PDCCH check on the CCE resource block to be preempted. Before acquiring the first candidate set of Physical Downlink Control Channel (PDCCH) to be detected for the first terminal, wherein the PDCCH candidate set includes at least one CCE resource block, the apparatus is further configured to: Obtain the protocol configuration parameters corresponding to the first terminal, wherein the protocol configuration parameters include an wireless network temporary identifier and / or downlink control information; Based on the protocol configuration parameters, the search space of the first terminal is calculated, the search space includes at least one candidate position, and the candidate position corresponds to at least one CCE resource block; Based on each candidate location and its corresponding CCE resource block, a first set of PDCCH candidates to be detected is generated.

7. A computer device, characterized in that, The computer device includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the computer program and, when executing the computer program, implement the downlink control channel blind detection method for multiple terminals as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to implement the downlink control channel blind detection method for multiple terminals as described in any one of claims 1 to 5.

Images