Resource preemption processing method, communication device, and readable storage medium

Abstract

The application discloses a hybrid automatic repeat request feedback method, which is applied to a base station side, and comprises the following steps: acquiring information of an ultra-reliable low-latency communication (URLLC) burst service; and determining radio resources allocated for the URLLC burst service by skipping radio resources allocated for a first user equipment, wherein the first user equipment is not allowed to occupy the radio resources by the URLLC burst service. The application further discloses a communication device and a readable storage medium.

Description

[Technical Field]

[0001] This application relates to the field of communications, and in particular to a resource preemption processing method, a communication device, and a readable storage medium. [Background Technology]

[0002] Currently, wireless communication systems utilize Frequency Division Duplex (FDD) or Time Division Duplex (TDD) for data transmission between base stations and User Equipment (UE). For example... Figure 1 As shown, in an FDD wireless communication system, different frequency channels are used for the uplink and downlink, allowing user equipment to transmit data simultaneously on both channels. In a TDD wireless communication system, the same frequency channel is used for both the uplink and downlink, thus dividing the transmission timeline into uplink and downlink transmission times. FDD duplexing can be further divided into full-duplex FDD and half-duplex FDD (HD-FDD). HD-FDD combines the characteristics of both FDD and TDD, meaning that the uplink and downlink use different frequency channels, but their transmission times are staggered.

[0003] The fifth-generation mobile communication system (5G NR) includes three major application scenarios: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC). URLLC has two fundamental characteristics: high reliability and low latency, for example, 10 -5 Or 10 -6It offers order-of-magnitude BLER performance with an air interface transmission latency of 0.5ms or 1ms. As specified in 3GPP R15, URLLC will provide services to latency-0 sensitive devices, which can be referred to as URLLC devices. To improve system resource utilization, URLLC devices and non-URLLC devices can coexist. When a URLLC device bursts URLLC service while a non-URLLC device is already occupying radio resources for transmission, R15 specifies a downlink preemption mechanism for URLLC. Correspondingly, the downlink preemption indication (PI) mechanism is used to notify user equipment of the location of preempted resources. Specifically, the base station sends a PI indication (post-indication method) to notify user equipment of the location of preempted resources. User equipment can then receive the PI indication and remove the preempted resources from the received data, thus eliminating the impact of preempted resources and achieving successful decoding.

[0004] like Figure 2 As shown, PUCCH is the Physical uplink control channel, and PDSCH is the Physical downlink share channel. Some resources in PDSCH are preempted by URLLC UEs. Therefore, after PDSCH, the PI indication needs to be transmitted to the corresponding UE with the preempted resources through PUCCH so that the UE with the preempted resources can remove the resources at the preempted positions according to the PI indication, thereby achieving successful decoding.

[0005] However, half-duplex user equipment (HD-FDDUE) can only receive or send messages at any given time and cannot do so in parallel. Therefore, it is possible that the HD-FDDUE receives data that has been punctured (resources preempted), but then the HD-FDDUE switches to the uplink (UL) and cannot listen to the PI indication sent by the base station. As a result, it cannot know that the resources have been occupied and the location of the occupied resources. At this time, the HD-FDDUE has already received the data on the time-frequency resources together and then decoded them. Since the received data contains URLLC user data, decoding errors occur, which leads to retransmission. Furthermore, because its HARQ (Hybrid Automatic Repeat Request) buffer is polluted by URLLC user data, even if multiple HARQ retransmissions are performed and different redundant versions are soft-merged, decoding errors may still occur, affecting the reliability of non-URLLCUE data transmission and wasting resources. [Summary of the Invention]

[0006] The main technical problem addressed by this application is to provide a resource preemption processing method, communication equipment, and readable storage medium, which can solve the problems of low reliability and resource waste in data transmission of user equipment in the prior art.

[0007] To address the aforementioned technical problems, the first aspect of this application provides a resource preemption processing method. This method is applied to the base station side and includes: acquiring information about Ultra Reliable Low Latency Communication (URLLC) burst services; skipping the radio resources allocated to a first user equipment that are determined to be preempted for the URLLC burst service, and the first user equipment not allowing the resources to be occupied by the URLLC burst service.

[0008] To address the aforementioned technical problems, a second aspect of this application provides a resource preemption processing method. This method is applied to the user equipment side and includes: sending user equipment information to the base station, wherein the user equipment information is used to instruct the user equipment not to allow resources to be occupied by URLLC burst services.

[0009] To address the aforementioned technical problems, a third aspect of this application provides a communication device comprising a processor, a memory, and a communication circuit, wherein the processor is connected to the communication circuit; the memory stores instructions, and the processor executes the instructions to implement the resource preemption processing method provided in the first aspect of this application.

[0010] To address the aforementioned technical problems, a fourth aspect of this application provides a communication device comprising a processor, a memory, and a communication circuit, wherein the processor is connected to the communication circuit; the memory stores instructions, and the processor executes the instructions to implement the resource preemption processing method provided in the second aspect of this application.

[0011] To address the aforementioned technical problems, this application provides a readable storage medium storing instructions that, when executed by a processor, implement the aforementioned resource preemption processing method.

[0012] The beneficial effects of this application are: the base station obtains information about ultra-reliable low-latency communication (URLLC) burst services; it skips the radio resources allocated to the first user equipment and determines the radio resources to be preempted for the URLLC burst services. In this case, by setting the first user equipment to not allow resources to be occupied by the URLLC burst services, the radio resources allocated to the first user equipment can be stopped from being allocated to the URLLC burst services. This avoids decoding errors caused by the mixing of URLLC burst service data into the data of the first user equipment, and thus eliminates the need for HARQ retransmission, or even multiple HARQ retransmissions. This ensures the reliability of the data transmission of the first user equipment while reducing resource waste. [Attached Image Description]

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

[0014] Figure 1 This is a schematic diagram of FDD, HD-FDD and FDD in the prior art;

[0015] Figure 2 This is a schematic diagram of a post-preemption instruction mechanism in the prior art;

[0016] Figure 3 This is a schematic diagram of one embodiment of the wireless communication system or network of this application;

[0017] Figure 4 This is a flowchart illustrating the first embodiment of the resource preemption processing method of this application;

[0018] Figure 5 This is a flowchart illustrating the second embodiment of the resource preemption processing method of this application;

[0019] Figure 6 This is a flowchart illustrating the third embodiment of the resource preemption processing method of this application;

[0020] Figure 7 This is a schematic diagram of the first embodiment of the multi-terminal interaction of the resource preemption processing method of this application;

[0021] Figure 8 This is a flowchart illustrating the fourth embodiment of the resource preemption processing method of this application;

[0022] Figure 9 This is a flowchart illustrating the fifth embodiment of the resource preemption processing method of this application;

[0023] Figure 10 This is a schematic diagram of a downlink preemption instruction;

[0024] Figure 11 This is a schematic diagram showing the correspondence between the bits of the preemption instruction and the symbol;

[0025] Figure 12 This is a flowchart illustrating the sixth embodiment of the resource preemption processing method of this application;

[0026] Figure 13 This is a schematic diagram of the second embodiment of the multi-terminal interaction of the resource preemption processing method of this application;

[0027] Figure 14 This is a flowchart illustrating the seventh embodiment of the resource preemption processing method of this application;

[0028] Figure 15 This is a flowchart illustrating the eighth embodiment of the resource preemption processing method of this application;

[0029] Figure 16 This is a schematic diagram of the MACCE in this application;

[0030] Figure 17 This is a flowchart illustrating the eighth embodiment of the resource preemption processing method of this application;

[0031] Figure 18 This is a schematic diagram of the third embodiment of the multi-terminal interaction of the resource preemption processing method of this application;

[0032] Figure 19 This is a schematic diagram of the structure of the first embodiment of the communication device of this application;

[0033] Figure 20 This is a schematic diagram of the structure of the second embodiment of the communication device of this application;

[0034] Figure 21 This is a schematic diagram of the structure of an embodiment of the readable storage medium of this application.

Detailed Implementation Methods

[0035] The technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. The following embodiments can be combined with each other if they do not conflict. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0036] The term "user equipment" in this application may include or represent any portable computing device used for communication. Examples of user equipment that may be used in some embodiments of the described devices, methods, and systems may be wired or wireless devices, such as mobile devices, mobile phones, user equipment, smartphones, portable computing devices such as laptops, handheld devices, tablets, tablet computers, netbooks, personal digital assistants, music players, and other computing devices capable of wired or wireless communication. Additionally, user equipment may also be a reduced-capability user equipment.

[0037] Please see Figure 3 , Figure 3This is a schematic diagram of a wireless communication system or network 100, including a core network 102 (or telecommunications infrastructure) and multiple network nodes 104a-104m (e.g., base station gNBs) serving multiple wireless communication units 108a-108e (e.g., UEs). The multiple network nodes 104a-104m are connected to the core network 102 via links. These links can be wired or wireless (e.g., radio communication links, fiber optics, etc.). The core network 102 may include multiple core network nodes, network entities, application servers, or any other network or computing device that can communicate with one or more wireless access networks including the multiple network nodes 104a-104m.

[0038] In this example, network nodes 104a-104m are illustrated as base stations, such as, but not limited to, gNBs in a 5G network. Each of the multiple network nodes 104a-104m (e.g., base stations) has a footprint, which, for simplicity and for example, but not limited to, is... Figure 3 The diagram schematically represents corresponding circular cells 106a-106m used to serve one or more UEs 108a-108e. UEs 108a-108e are able to receive services from wireless communication system 100, such as voice, video, audio, or other communication services.

[0039] The wireless communication system or network 100 may include or represent any one or more communication networks for communication between UE 108a-108e and other devices, content sources, or servers connected to the wireless communication system or network 100. The core network 102 may also include or represent one or more communication networks, one or more network nodes, entities, elements, application servers, servers, base stations, or other network devices linked, coupled, or connected to form the wireless communication system or network 100. Links or couplings between network nodes may be wired or wireless (e.g., radio communication links, fiber optics, etc.). The wireless communication system or network 100 and the core network 102 may include any suitable combination of a core network and a wireless access network containing network nodes or entities, base stations, access points, etc., enabling communication between UE 108a-108e, network nodes 104a-104m of the wireless communication system 100 and core network 102, content sources, and / or other devices connected to the system or network 100.

[0040] Examples of wireless communication networks 100 that may be used in some embodiments of the described devices, methods, and systems may be at least one communication network or a combination thereof, including but not limited to, one or more wired and / or wireless telecommunication networks, one or more core networks, one or more wireless access networks, one or more computer networks, one or more data communication networks, the Internet, telephone networks, wireless networks such as WiMAX, WLAN, and / or Wi-Fi networks based on the IEEE 802.11 standard (by way of example only), or Internet Protocol (IP) networks, packet-switched networks or enhanced packet-switched networks, IP Multimedia Subsystem (IMS) networks, or communication networks based on wireless, cellular, or satellite technologies, such as mobile networks, Global System for Mobile Communications (GSM), GPRS networks, Wideband Code Division Multiple Access (W-CDMA), CDMA2000, or LTE / Advanced LTE communication networks, or any second-generation, third-generation, fourth-generation, or fifth-generation and beyond-generation communication networks, etc.

[0041] exist Figure 3 In the example, the wireless communication system 100 may be, by way of example only but not limited to, a 5G communication network using cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) technology for downlink and uplink channels. The downlink may include one or more communication channels for transmitting data from one or more gNBs 104a-104m to one or more UEs 108a-108e. Typically, the downlink channel is a communication channel used for transmitting data, for example, from gNB 104a to UE 108a.

[0042] Both uplink and downlink in 5G networks are divided into radio frames (e.g., each frame can be 10 ms long), and each frame can be further divided into multiple subframes. For example, each frame may include 10 subframes of equal length, where each subframe consists of multiple time slots (e.g., 2 time slots) for transmitting data. In addition to time slots, subframes may include several additional special fields or OFDM symbols, which may include, by way of example only, downlink synchronization symbols, broadcast symbols, and / or uplink reference symbols.

[0043] Please see Figure 4 , Figure 4This is a flowchart illustrating the first embodiment of the resource preemption processing method of this application.

[0044] Specifically, the first embodiment of the resource preemption handling method includes:

[0045] Step S11: Obtain information on bursty URLLC services.

[0046] This embodiment applies to the base station side. The main characteristics of URLLC low-latency scenarios are high burstiness but small data volume. Therefore, NR supports URLLC using a preemptive approach to occupy channel resources. For example, when the base station allocates physical resources to eMBB services, it also allocates eMBB service resources to URLLC services simultaneously. When URLLC preempts physical resources, the NR notifies the UE of the preemption result to ensure the low-latency requirements of URLLC. The user equipment corresponding to the bursty URLLC service is called the URLLCUE.

[0047] When a base station obtains information about a burst of Ultra Reliable Low Latency Communication (URLLC) service, it needs to allocate radio resources for the burst service. The allocated radio resources can be radio resources that are not occupied by user equipment or radio resources that have been occupied by user equipment.

[0048] Step S12: Skip the radio resources allocated to the first user equipment and determine the radio resources to be preempted for URLLC burst service allocation. The first user equipment shall not allow the resources to be occupied by URLLC burst service.

[0049] In this embodiment, the first user equipment (UE) is not allowed to have its resources occupied by URLLC burst services. When the base station needs to allocate preempted radio resources for URLLC burst services, the base station skips the radio resources allocated to the UE and determines them as the preempted radio resources allocated to the URLLC burst services, thereby ensuring the integrity of the radio resources allocated to the UE. Since the radio resources allocated to the UE are not occupied by URLLC burst services, decoding errors caused by interference data (URLLC service data) mixed into the UE's user data are avoided. Therefore, HARQ retransmissions, or even multiple HARQ retransmissions, are unnecessary, ensuring the reliability of the UE's data transmission while avoiding resource waste.

[0050] Optionally, the first user equipment can be a half-duplex user equipment, such as a security sensor (security switch, security light curtain, security door system). Half-duplex user equipment (HD-FDD UE) operates in HD-FDD mode, meaning it can only receive or send messages at a time and cannot do so concurrently. Therefore, although the system has a downlink preemption indication mechanism, the PI indication is a post-indication method (e.g., ...). Figure 2As shown, this means that the PI indication is sent after the resource is occupied. This is referred to as the post-PI indication. When the base station sends the PI indication, if the user equipment is in the uplink state, that is, it can only send messages, the user equipment cannot receive the PI indication. This may affect the reliability of data transmission of half-duplex user equipment. Therefore, for half-duplex user equipment and other such equipment, by setting it to not allow resources to be occupied by URLLC burst services, the impact of URLLC burst services can be avoided, and the reliability of data transmission of half-duplex user equipment can be guaranteed.

[0051] In some implementations, the first user equipment can be a reduced-capability user equipment, abbreviated as RedCap UE. RedCap UE can include three main categories of devices: industrial wireless sensors, video surveillance equipment in smart cities, and wearable devices. Specifically, industrial wireless sensors include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc.; video surveillance equipment in smart cities includes access control devices, traffic video surveillance equipment, etc.; wearable devices include smartwatches, wristbands, rings, electronic health-related devices, medical monitoring devices, etc. Compared to URLLC / eMBB devices, RedCap UEs are relatively smaller in size and have lower requirements for bandwidth and peak data rates. Optionally, RedCap UEs can adopt HD-FDD operating mode; a RedCap UE operating in HD-FDD mode is also known as an HD-FDD UE.

[0052] In some implementations, the first user equipment may specifically disallow uplink and / or downlink resources from being occupied by URLLC burst services. Specifically, the first user equipment may disallow uplink resources from being occupied by URLLC burst services, or the first user equipment may disallow downlink resources from being occupied by URLLC burst services, or the first user equipment may disallow both uplink and downlink resources from being occupied by URLLC burst services. It is understood that the resource preemption processing method provided in this application can be applied not only to the downlink preemption mechanism in URLLC services, but also to the uplink cancellation mechanism in URLLC services, meaning that the URLLC device cannot preempt the uplink resources of the first user equipment.

[0053] In this embodiment, the base station obtains information about Ultra-Reliable Low-Latency Communication (URLLC) burst services; it skips the radio resources allocated to the first user equipment and determines the radio resources to be preempted for the URLLC burst services. By setting the first user equipment to not allow resources to be occupied by the URLLC burst services, the radio resources allocated to the first user equipment can be stopped from being allocated to the URLLC burst services. This avoids decoding errors caused by the mixing of URLLC burst service data into the data of the first user equipment, and thus eliminates the need for HARQ retransmission, or even multiple HARQ retransmissions. This ensures the reliability of the data transmission of the first user equipment while reducing resource waste.

[0054] Please see Figure 5 , Figure 5 This is a flowchart illustrating the second embodiment of the resource preemption processing method of this application.

[0055] Specifically, the second embodiment of the resource preemption handling method includes:

[0056] Step S21: Obtain information on bursty URLLC services.

[0057] For details, please refer to the description of the first embodiment of the resource preemption processing method in this application, which will not be repeated here.

[0058] Step S22: Obtain information about the first user device.

[0059] Step S23: Determine, based on the information of the first user equipment, that the first user equipment does not allow resources to be occupied by URLLC burst services.

[0060] Steps S22-S23 and S21 do not have a fixed order. In this embodiment, steps S22-S23 can be executed after step S21. In other embodiments, steps S22-S23 can be executed before or simultaneously with step S21. No limitation is made here.

[0061] In some implementations, the information of the first user equipment may include the first user equipment's capability information (UEcapability). This capability information may include an identifier indicating that the first user equipment does not allow resources to be occupied by URLLC burst services.

[0062] In one implementation, the capability information of the first user equipment (User Equipment) must include an identifier indicating that the first User Equipment does not allow resources to be occupied by URLLC burst services. Therefore, when the base station obtains the capability information of the first User Equipment, it can directly determine that the first User Equipment does not allow resources to be occupied by URLLC burst services. In another implementation, the capability information of the first User Equipment may include an identifier indicating that the first User Equipment does not allow resources to be occupied by URLLC burst services. In this case, after obtaining the information of the first User Equipment, the base station needs to confirm that it includes an identifier indicating that the first User Equipment does not allow resources to be occupied by URLLC burst services before it can determine that the first User Equipment does not allow resources to be occupied by URLLC burst services.

[0063] Information about the first user equipment can be carried by Radio Access Control (RRC) messages, or it can be transmitted using special resources during random processes, such as MSG1 / MSGA. Specifically, it can be at least one of the following in MSG1 / MSGA: a separate initial UL BWP, a separate preamble, and a separate Prach occasion. RRC messages can include messages such as RRCSetupComplete, RRCReconfigurationComplete, RRCReestablishmentComplete, and UEcapabilityInformation.

[0064] Optionally, the first user equipment (UE) may proactively report capability information. The base station receives the capability information proactively reported by the UE and determines whether the capability information includes an identifier indicating that the UE is not allowed to have its resources occupied by URLLC burst services. If it does, then the UE is not allowed to have its resources occupied by URLLC burst services; if it does not, then the UE is allowed to have its resources occupied by URLLC burst services. Alternatively, the base station may proactively acquire the capability information of the UE.

[0065] Specifically, the information of the first user equipment may include a capability type identifier and / or a device type identifier, which can be used to indicate that the first user equipment does not allow resources to be bursty served by URLLC. The capability type identifier may include radio access-related capabilities and core network-related capabilities, specifically the capability types included in the UE capability information.

[0066] In one application scenario, the device type identifier may include, but is not limited to, half-duplex user equipment identifiers (such as HD-FDD UE) and full-duplex user equipment identifiers (such as FDD UE). HD-FDD UE indicates that the first user equipment does not allow resources to be occupied by URLLC burst services, while FDD UE indicates that the first user equipment allows resources to be occupied by URLLC burst services. When the device type identifier reported by the first user equipment is HD-FDD UE, the base station can determine, based on HD-FDD UE, that the first user equipment does not allow resources to be occupied by URLLC burst services.

[0067] In one application scenario, the device type identifier may include, but is not limited to, Redcap UE and regular NR UE. Redcap UE indicates that the first user equipment (UE) does not allow resources to be occupied by URLLC burst services, while regular NR UE indicates that the first UE allows resources to be occupied by URLLC burst services. When the device type identifier reported by the first UE is Redcap UE, the base station can determine, based on Redcap UE, that the first UE does not allow resources to be occupied by URLLC burst services. In other application scenarios, Redcap UE may also include multiple sub-device type identifiers, such as wireless sensor identifiers, video surveillance device identifiers, and wearable device identifiers.

[0068] In some implementations, not all Redcap UEs have high performance requirements. For some Redcap UEs with low performance requirements, resources can be used for URLLC burst services, while for others, resources may not be used for URLLC burst services. For example, a device type identified as Redcap UE-1 represents a UE with low performance requirements (such as a smart bracelet), and this UE can allow resources to be used for URLLC burst services; a device type identified as Redcap UE-2 represents a UE with high performance requirements (such as a security sensor or high-end video surveillance equipment), and this UE may not allow resources to be used for URLLC burst services.

[0069] In other embodiments, the information of the first user equipment includes a dedicated identifier indicating that the first user equipment does not allow resources to be occupied by URLLC burst services. This dedicated identifier may be carried by a Radio Access Control (RRC) message. The dedicated identifier can be selected based on actual circumstances and is not limited here, as long as it can be used to indicate that the first user equipment does not allow resources to be occupied by URLLC burst services.

[0070] Step S24: Skip the radio resources allocated to the first user equipment and determine the radio resources to be preempted for URLLC burst service allocation.

[0071] If the base station determines that the first user equipment does not allow resources to be occupied by URLLC burst services, it can skip the radio resources allocated to the first user equipment and determine the radio resources to be preempted by the URLLC burst service, that is, it will not allocate the radio resources allocated to the first user equipment to the URLLC burst service; if the base station determines that the first user equipment allows resources to be occupied by URLLC burst services, it can determine the radio resources allocated to the first user equipment and determine the radio resources to be preempted by the URLLC burst service.

[0072] In this embodiment, the base station obtains information about the first user equipment and determines, based on the information about the first user equipment, that the first user equipment is not allowed to have its resources occupied by URLLC burst services. Therefore, when obtaining information about ultra-reliable low-latency communication (URLLC) burst services, the base station can skip the radio resources allocated to the first user equipment and determine the radio resources to be preempted by the URLLC burst services. The information about the first user equipment can determine whether the resources of the first user equipment can be occupied by the URLLC burst services without affecting the reliability of data transmission. If not, it can be determined that the first user equipment is not allowed to have its resources occupied by the URLLC burst services, thereby ensuring the reliability of data transmission of the first user equipment.

[0073] Please see Figure 6 , Figure 6 This is a flowchart illustrating the third embodiment of the resource preemption processing method of this application.

[0074] Specifically, the third embodiment of the resource preemption handling method includes:

[0075] Step S31: Send user equipment information to the base station. The user equipment information is used to instruct the user equipment not to allow resources to be occupied by URLLC burst services.

[0076] This embodiment applies to the user equipment side. The user equipment sends user equipment information to the base station. The user equipment information is used to indicate that the user equipment does not allow resources to be occupied by URLLC burst services, so that the base station determines that the user equipment does not allow resources to be occupied by URLLC burst services based on the user equipment information, thereby skipping the radio resources allocated to the user equipment and determining the radio resources to be preempted for URLLC burst services.

[0077] In some implementations, the user equipment can be a half-duplex user equipment and / or a capability-reduced user equipment.

[0078] In some implementations, user equipment does not allow uplink and / or downlink resources to be occupied by URLLC burst services.

[0079] In some implementations, the user equipment information may include the user equipment's capability information, which may include an identifier indicating that the user equipment does not allow resources to be occupied by URLLC burst services.

[0080] In some implementations, the user equipment information may include a dedicated identifier indicating that the user equipment does not allow resources to be occupied by URLLC burst services. This dedicated identifier may be carried by a Radio Access Control (RRC) message.

[0081] It is understood that the user equipment in this embodiment is similar to the first user equipment in the previous embodiment. For details, please refer to the description in the first and second embodiments of the resource preemption processing method of this application, which will not be repeated here.

[0082] In this embodiment, the user equipment sends user equipment information to the base station. This user equipment information is used to instruct the user equipment not to allow resources to be occupied by URLLC burst services. This enables the base station to determine, based on the user equipment information, that the user equipment should not allow resources to be occupied by URLLC burst services, and to skip the radio resources allocated to the user equipment that are determined to be preempted by the URLLC burst services. This avoids decoding errors caused by the mixing of URLLC burst service data into the data of the first user equipment, and eliminates the need for HARQ retransmission, or even multiple HARQ retransmissions. This ensures the reliability of the data transmission of the first user equipment while reducing resource waste.

[0083] Please see Figure 7 , Figure 7 This is a schematic diagram of the first embodiment of the resource preemption processing method of this application with multi-terminal interaction.

[0084] The first embodiment of the resource preemption handling method with multi-terminal interaction may include:

[0085] 1) The base station (gNB) obtains information about bursty ultra-reliable low-latency communication (URLLC) services.

[0086] 2) The first user equipment (UE1) sends information about the first user equipment to the base station.

[0087] 3) The base station receives information from the first user equipment.

[0088] 4) The base station determines, based on the information of the first user equipment, that the first user equipment is not allowed to have its resources occupied by URLLC burst services.

[0089] 5) The radio resources that the base station skips to allocate to the first user equipment are determined to be radio resources preempted by URLLC burst service allocation. The first user equipment shall not allow the resources to be occupied by URLLC burst service.

[0090] For an explanation of the above content, please refer to the corresponding section in the foregoing embodiments; it will not be repeated here.

[0091] Please see Figure 8 , Figure 8 This is a flowchart illustrating the fourth embodiment of the resource preemption processing method of this application.

[0092] Specifically, the fourth embodiment of the resource preemption handling method includes:

[0093] Step S41: Determine that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0094] This embodiment applies to the base station side. The user equipment can be a half-duplex user equipment and / or a reduced-capacity user equipment.

[0095] In this embodiment, the time unit can be a slot, and the second time unit can be the previous slot of the first time unit, or the first N slots of the first time unit, where N is a positive integer.

[0096] Specifically, at least a portion of the downlink resources allocated to user equipment in the first time unit may be preempted by URLLC burst services of URLLC UEs. The URLLC UE preempts the downlink resources of the HD-FDD UE, and the preemption occurs before at least one control resource set (CORESET) time domain period corresponding to the preempted resource has started. Using the pre-PI scheme of this embodiment can resolve the abnormal situation where a large proportion of HD-FDD UEs cannot receive PI instructions.

[0097] Step S42: Send a preemption indication to the user equipment in the second time unit, which is prior to the first time unit. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0098] When the base station determines that a URLLC burst service has preempted at least a portion of the downlink resources allocated to the HD-FDD UE in the first time unit, it sends a preemption indication (pre-PI indication) to the user equipment in the second time unit prior to the first time unit to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted, and to indicate the location of the preempted downlink resources, so that the user equipment can eliminate the impact of the preempted resources.

[0099] In some implementations, the base station may not distinguish between user equipment (UEs), that is, it may send a preemption instruction to all UEs in the second time unit. In other implementations, the base station may distinguish between UEs, and send a preemption instruction to only UEs that cannot receive the post-PI instruction, such as half-duplex UEs, in the second time unit.

[0100] This embodiment, by placing the PI indication at the beginning and enabling the user equipment to receive the pre-placed PI indication, ensures that regardless of whether the user equipment is in an uplink state in the time unit following the first time unit, it can successfully receive the PI indication in the second time unit and know that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted. This avoids decoding errors caused by preempted resources being mixed into the user equipment's data, thus eliminating the need for HARQ retransmissions, or even multiple HARQ retransmissions, ensuring the reliability of the first user equipment's data transmission while reducing resource waste.

[0101] Please see Figures 9 to 10 , Figure 9 This is a flowchart illustrating the fifth embodiment of the resource preemption processing method of this application. Figure 10 This is a schematic diagram of a downlink preemption instruction. Figure 11 This is a schematic diagram showing the correspondence between the bits and symbols of the preemption indicator.

[0102] Specifically, the fifth embodiment of the resource preemption handling method includes:

[0103] Step S51: Determine that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0104] For details, please refer to the description of the fourth embodiment of the resource preemption processing method in this application, which will not be repeated here.

[0105] Step S52: Determine whether the user equipment is in the uplink state in the third time unit, which is after the first time unit.

[0106] If yes, proceed to step S53; otherwise, proceed to step S54.

[0107] In this embodiment, step S52 and step S51 are not necessarily ordered. In this embodiment, step S52 can be executed after step S51. In other embodiments, step S52 can be executed before or at the same time as step S51. No limitation is made here.

[0108] In this embodiment, the time unit can be a slot. The third time unit can be the next slot after the first time unit, or it can be the last N slots of the first time unit, where N is a positive integer.

[0109] The base station can determine whether the user equipment can receive the PI instruction before switching to the uplink state based on the uplink and downlink time allocation of the user equipment, and then determine whether the pre-PI instruction is needed based on the result.

[0110] Specifically, the base station determines whether the user equipment is in the uplink state in the third time unit. If so, it means that the user equipment cannot successfully receive the post-PI indication in the third time unit, so it needs to send a preemption indication to the user equipment in the second time unit in advance so that the user equipment can successfully receive the PI indication. If not, it means that the user equipment can successfully receive the post-PI indication in the third time unit, so it is not necessary to pre-position the PI indication, and it can still send a preemption indication to the user equipment in the third time unit.

[0111] Step S53: Send a preemption instruction to the user equipment in the second time unit.

[0112] Step S54: Send a preemption instruction in the third time unit instead of the second time unit.

[0113] The second time unit precedes the first time unit, and the preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0114] In this embodiment, the preemption indication may include a first indicator, which indicates whether the preemption indication is before or after the first time unit. Optionally, the size of the first indicator may be 1 bit or more bits. For example, the first indicator is Pre-Ind (1 bit), with a size of 1 bit, where a value of 1 indicates a pre-PI indication and a value of 0 indicates a post-PI indication.

[0115] In some implementations, the base station sends a preemption indication to the user equipment. The user equipment receives the preemption indication and determines whether it includes a first indicator. If the first indicator is included, it is determined that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted. If the first indicator is not included, it is determined that at least a portion of the downlink resources allocated to the user equipment in the first time unit have not been preempted.

[0116] In other embodiments, after step S53, the method may further include: sending a preemption indication to the user equipment in a third time unit, which is after the first time unit. In existing designs, the downlink preemption indication is placed later, while in this embodiment, to resolve the conflict between half-duplex user equipment and URLLC services, the PI indication is placed earlier. However, considering the compatibility with other normal user equipment, the base station can still send the preemption indication to the user equipment in the third time unit.

[0117] In some implementations, the preemption indication can be included in a dedicated format of Downlink Control Information (DCI), specifically DCI format 2_1. Specifically, when the user equipment is in the uplink state in the third time unit, the base station can schedule DCI format 2_1 and other normally scheduled DCIs. Multiple DCIs can reside in different search spaces within the same core set; or they can reside in different core sets.

[0118] Specifically, such as Figure 10 As shown, the base station can send a PI indication to the user equipment via multicast. The PI indication is carried in DCI format 2_1, notifying the user equipment of resources preempted within a Reference DL Region (RDR). DCI format 2_1 is a Group-common DCI with a maximum payload size of 126 bits. Each 14-bit segment corresponds to one UE PI, scrambled by INT_RNTI. The preemption indication / configuration is in DownlinkPreemption. To ensure reliability, URLLC services occupy a large amount of bandwidth in the frequency domain. Therefore, the data of one URLLC user may occupy the time-frequency resources of multiple non-URLLC UEs. To save overhead, the PI indication can be carried in a Group-common DCI format to notify a group of user equipment of resources preempted by the URLLC service, which is more efficient.

[0119] In some implementations, the preemption indication can be included in the DCI used to control user equipment. This involves extending the existing DCI by adding a PI indicator (14 bits). Specifically, this can be done by adding a leading PI indicator bit (e.g., DCI 0_x, 1_x) and the PI indicator (14 bits) to the DCI used to control user equipment. It is understood that the PI indicator is optional and not all user equipment requires configuration. When a user equipment's resources are preempted, the PI indicator in the DCI used to control the user equipment can be set according to the location of the preempted resource. Alternatively, the PI indicator can be set only when it is determined that the user equipment cannot receive the PI indicator in a timely manner, thus indicating the preempted resource information.

[0120] In one application scenario, the user equipment determines the DCI to be detected based on its own equipment type, 0_x. 1_x requires the addition of a downlink preemption indication, thereby adding an indication bit to the pre-indicator PI. Subsequently, the DCI is detected according to the extended DCI format. When the base station determines that the downlink resources have been preempted, it sets the PI indication in the extended DCI. The user equipment detects the DCI according to the known extended DCI format, thereby obtaining the PI indication from the DCI.

[0121] This section briefly explains the correspondence between the bits and symbols in the PI indicator, dividing it into two cases: In the first case, when timeFrequencySet is configured to 0, the frequency domain represents the entire frequency domain BWP, while the time domain is divided into 14 groups. Each of the 14 bits indicates whether a time / frequency position in one group is occupied by URLLC data. For example... Figure 11 As shown in the left figure, the 14 Symbols are divided into 14 groups, with each symbol corresponding to a bit in the PI indicator. A value of 1 indicates that it is occupied by the URLLC UE. Another scenario is when timeFrequencySet is configured to 1, the frequency domain is divided into upper and lower parts, and several symbols in the time domain are grouped together, using one bit to indicate each group. Similarly, 14 bits can represent 14 groups. Figure 11 As shown in the right figure, the 14 Symbols are divided into 14 groups. Each symbol corresponds to a bit in the PI indicator. A value of 1 indicates that it is occupied by the URLLC UE.

[0122] In this embodiment, the base station determines that at least some downlink resources allocated to the user equipment in the first time unit have been preempted, and then determines whether the user equipment is in the uplink state in the third time unit. The third time unit is after the first time unit. If so, a preemption indication is sent to the user equipment in the second time unit; otherwise, a preemption indication is sent in the third time unit instead of the second time unit. Specifically, whether the user equipment is in the uplink state in the third time unit is determined in advance before allocating resources for the preemption indication, so that the PI indication is only brought forward when it is determined that the user equipment is in the uplink state in the third time unit.

[0123] Please see Figure 12 , Figure 12 This is a flowchart illustrating the sixth embodiment of the resource preemption processing method of this application.

[0124] Specifically, the sixth embodiment of the resource preemption handling method includes:

[0125] Step S61: Receive a preemption indication from the base station in the second time unit. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted. The second time unit is prior to the first time unit.

[0126] This embodiment applies to the user equipment side. The user equipment can be a half-duplex user equipment and / or a reduced-capacity user equipment.

[0127] In some implementations, the preemption indication may include a first indicator, which may be used to indicate that the preemption indication is before or after a first time unit. The preemption indication may be included in a dedicated format downlink control information (DCI). The dedicated format DCI may be DCI format 2_1.

[0128] In some implementations, the preemption instruction may be included in the DCI used to control the user equipment.

[0129] Step S62: Receive downlink transmissions using the allocated downlink resources in the first time unit.

[0130] Step S63: Decode the data after removing the portion of the downlink transmission that uses preempted downlink resources.

[0131] The user equipment receives a preemption indication from the base station in the second time unit, and then uses the allocated downlink resources to receive downlink transmission in the first time unit. Based on the preemption indication, the user equipment can determine at least a portion of the downlink resources allocated to the user equipment in the first time unit that have been preempted, so that the portion of downlink resources can be removed and then decoded to ensure the reliability of the user equipment's data transmission.

[0132] In some implementations, after receiving the preemption instruction from the base station in the second time unit, the user equipment can also receive the preemption instruction from the base station in the third time unit. The third time unit is after the first time unit to take into account the compatibility of other normal user equipment and ensure the normal operation of other normal user equipment.

[0133] It is understood that the specific content of this embodiment can be referred to the description in the above embodiment of the resource preemption processing method of this application, and will not be repeated here.

[0134] In this embodiment, the user equipment can successfully receive the preemption instruction from the base station in the second time unit, and then use the allocated downlink resources to receive downlink transmission in the first time unit. After removing the part of the downlink transmission that uses the preempted downlink resources according to the preemption instruction, it performs decoding. This can avoid decoding errors caused by the preempted resources being mixed into the user equipment's data, and thus eliminate the need for HARQ retransmission, or even multiple HARQ retransmissions. This ensures the reliability of the first user equipment's data transmission while reducing resource waste.

[0135] Please see Figure 13 , Figure 13This is a schematic diagram of the second embodiment of the multi-terminal interaction of the resource preemption processing method of this application.

[0136] The second embodiment of the resource preemption handling method with multi-terminal interaction may include:

[0137] 1) The base station (gNB) determines that at least a portion of the downlink resources allocated to the duplex user equipment in the first time unit have been preempted (the base station determines that the URLLC UE preempted at least a portion of the resources of the HD-FDD UE in the first time unit).

[0138] 2) The base station sends a preemption indication to the dual-half-duplex user equipment in the second time unit, which is before the first time unit. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the dual-half-duplex user equipment in the first time unit have been preempted (PDCCH (DCI format 2_1 + other DCI)).

[0139] 3) The base station sends the PDCCH to the URLLC device in the second time unit.

[0140] 4) The HD-FDD UE receives a preemption indication from the base station in the second time unit (DCI format 2_1 is detected).

[0141] 5) Duplex user equipment uses the allocated downlink resources to receive downlink transmissions in the first time unit (PDSCH (at least some downlink resources are preempted)).

[0142] 6) Duplex user equipment decodes the data after removing the portion of the downlink transmission that was preempted using downlink resources, according to DCI format 2_1.

[0143] 7) The URLLC device receives the PDCCH sent by the base station and decodes it successfully.

[0144] For an explanation of the above content, please refer to the corresponding section in the foregoing embodiments; it will not be repeated here.

[0145] Please see Figure 14 , Figure 14 This is a flowchart illustrating the seventh embodiment of the resource preemption processing method of this application. This embodiment is applied to the base station side. Specifically, the seventh embodiment of the resource preemption processing method includes:

[0146] Step S71: Determine that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0147] Step S72: Send a Media Access Control (MAC) Protocol Data Unit (PDU) containing a preemption indication to the User Equipment. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the User Equipment in the first time unit have been preempted.

[0148] The Media Access Control (MAC) Protocol Data Unit (PDU) is abbreviated as MAC PDU. A MAC PDU may consist of a MAC header, a MAC CE, and a MAC SDU. The MAC header can be composed of multiple MAC sub-headers, each corresponding to a MAC CE and a MAC SDU, indicating the name (LCID field in the MAC sub-header represents the name of the corresponding MAC CE and MAC SDU), length, and other information. The MAC CE carries control information related to radio resource management. The MAC SDU carries data or signaling; a MAC PDU may contain zero or more MAC SDUs. In this embodiment, the preemption indication can be one of the MAC control elements (CE), i.e., the MAC CE. Optionally, a new MAC CE can be constructed to carry the preemption indication.

[0149] In some implementations, the LCID of the PI indicator can be defined as shown in Table 1 below. In one example, field 46 can be used to represent the MAC PDU containing the preemption indicator, specifically the name of the MAC CE.

[0150] Table 1: Values ​​of LCID for DL-SCH

[0151]

[0152] In this embodiment, when the base station determines that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted, it sends a Media Access Control (MAC) Protocol Data Unit (PDU) containing a preemption indication to the user equipment. The preemption indication is carried by the MAC PDU, enabling the user equipment to receive the preemption indication in a timely manner. This allows the user equipment to determine the preempted portion of the downlink resources allocated to the user equipment in the first time unit, thereby avoiding decoding errors caused by URLLC burst service data mixed into the data of the first user equipment. Consequently, HARQ retransmissions are no longer necessary, or even multiple HARQ retransmissions, ensuring the reliability of data transmission of the first user equipment while reducing resource waste.

[0153] Please see Figures 15 to 16 , Figure 15 This is a flowchart illustrating the eighth embodiment of the resource preemption processing method of this application. Figure 16 This is a schematic diagram of the MACCE in this application.

[0154] Specifically, the eighth embodiment of the resource preemption handling method includes:

[0155] Step S81: Determine that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0156] This embodiment applies to the base station side. The user equipment is a half-duplex user equipment and / or a reduced-capacity user equipment.

[0157] Step S82: Determine whether the user equipment is in the uplink state in the second time unit, which is after the first time unit.

[0158] If yes, proceed to step S83; otherwise, proceed to step S84.

[0159] Unlike the above embodiments, in this embodiment the second time unit is after the first time unit.

[0160] If the user equipment is not in the uplink state in the second time unit, it means that the user equipment can receive the preemption instruction in the downlink control information in time, and thus can send the preemption instruction to the user equipment using the downlink control information in the second time unit; if the user equipment is in the uplink state in the second time unit, it means that the user equipment cannot receive the preemption instruction in the downlink control information in time, and thus needs to send the preemption instruction through the MAC PDU so that the user equipment can receive the preemption instruction in time.

[0161] In other embodiments, the base station can also obtain user equipment information and determine whether the user equipment can receive the preemption indication in the downlink control information in a timely manner based on the user equipment information. The user equipment information may include a capability type identifier and / or a device type identifier, the details of which are described in the above embodiments and will not be repeated here. For example, if the device type identifier obtained by the base station is HD-FDD UE, it indicates that the user equipment cannot receive the preemption indication in the downlink control information in a timely manner. Therefore, a preemption indication can be sent using a MAC PDU to ensure the reliability of user equipment data transmission.

[0162] Step S83: Send a MAC PDU containing a preemption instruction.

[0163] The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0164] Step S84: In the second time unit, a preemption instruction is sent to the user equipment using downlink control information.

[0165] The Media Access Control (MAC) Protocol Data Unit (PDU) includes a preemption indication.

[0166] In some implementations, the base station may send a preemption indication to the user equipment using downlink control information (DCI) in a second time unit. In other implementations, the base station may send a MAC PDU containing the preemption indication using unpreempted downlink resources in a first time unit.

[0167] The preemption indication includes a first indicator, which indicates that the preemption indication occurs before or after the preempted downlink resources. Thus, when at least a portion of the downlink resources allocated to the user equipment are preempted, the preemption indication can be sent to the user equipment before (after) the first time unit. The user equipment can determine from the first indicator that the preemption indication is used to indicate that the downlink resources in the later (earlier) time unit are preempted.

[0168] like Figure 16 The diagram shown illustrates a MACCE scenario, including two cases: case 1 (oct1) is a preemption indication containing a first indicator (Pre-Ind), and case 2 (oct2) is a preemption indication without a first indicator. The Preemption Indication is 14 bits, and each bit... Figure 11 The symbols in the code correspond to each other, specifically starting from the highest bit or starting from the lowest bit.

[0169] Optionally, the size of the first indicator can be 1 bit or more bits. In some implementations, the first indicator is Pre-Ind (1 bit), with a value of 1 bit indicating a pre-PI indicator and a value of 0 indicating a post-PI indicator. In other implementations, it can be determined by checking if there is a MACCE containing a PI indicator; if so, it is determined to be a pre-PI indicator; otherwise, it is determined to be a post-PI indicator.

[0170] In some implementations, after determining that at least some of the downlink resources allocated to the user equipment in the first time unit have been preempted, a preemption instruction can be sent to the user equipment using downlink control information in the second time unit. The second time unit follows the first time unit to take into account the compatibility of other normal user equipment and ensure the normal operation of other normal user equipment.

[0171] Please see Figure 17 , Figure 17 This is a flowchart illustrating the eighth embodiment of the resource preemption processing method of this application.

[0172] Specifically, the eighth embodiment of the resource preemption handling method includes:

[0173] Step S91: Receive a MACPDU containing a preemption indication from the base station. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0174] This embodiment applies to the user equipment side. The user equipment can be a half-duplex user equipment and / or a reduced-capacity user equipment.

[0175] Step S92: After removing the portion of the downlink transmission received by the first time unit that uses preempted downlink resources, perform decoding.

[0176] After receiving a MACPDU containing a preemption indication from the base station, the user equipment can decode the MACPDU to obtain the downlink preemption indication information of the first time unit. Based on the downlink preemption indication information, the part of the downlink transmission received in the first time unit that uses the preempted downlink resources is removed, and then the decoding is performed.

[0177] In some implementations, the user equipment may receive a preemption instruction contained in downlink control information from the base station in a second time unit, which is after the first time unit.

[0178] In some implementations, the preemption instruction may include a first indicator, which may be used to indicate that the preemption instruction occurs before or after the preempted downlink resource.

[0179] In some implementations, the transmission resources used by the MAC PDU containing the preemption indication can be downlink resources that were not preempted within the first time unit.

[0180] In some implementations, the preemption instruction can be a MAC CE in a MAC PDU.

[0181] It is understood that the specific content of this embodiment can be referred to the description in the above embodiment of the resource preemption processing method of this application, and will not be repeated here.

[0182] Please see Figure 18 , Figure 18 This is a schematic diagram of the third embodiment of the resource preemption processing method of this application with multi-terminal interaction.

[0183] The third embodiment of the resource preemption handling method with multi-terminal interaction may include:

[0184] 1) The base station (gNB) determines that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted, and constructs MACUE (determines that the URLLC UE has preempted at least a portion of the resources of the HD-FDD UE in the first time unit, and constructs MAC CE).

[0185] 2) The base station simultaneously sends a Media Access Control (MAC) Protocol Data Unit (PDU) containing a preemption indication to both the half-duplex user equipment and the URLLC equipment. The preemption indication is used to indicate that at least a portion of the downlink resources allocated to the user equipment in the first time unit have been preempted.

[0186] 3) Half-duplex user equipment (HD-FDD UE) receives a MACPDU containing a preemption indication from the base station.

[0187] 4) The half-duplex user equipment decodes the MAC CE, and then decodes it after removing the part of the downlink transmission that was preempted in the downlink transmission received in the first time unit according to the decoded PI indication.

[0188] 5) At the same time, the URLLC device can also perform decoding, and the decoding is successful.

[0189] For an explanation of the above content, please refer to the corresponding section in the foregoing embodiments; it will not be repeated here.

[0190] Please see Figure 19 , Figure 19 This is a schematic diagram of the structure of the first embodiment of the communication device of this application.

[0191] like Figure 19 As shown, the first embodiment of the communication device of this application includes: a processor 110, a memory 120 and a communication circuit 130.

[0192] Processor 110 controls the operation of the communication device. Processor 110 can also be referred to as a CPU (Central Processing Unit). Processor 110 may be an integrated circuit chip with signal sequence processing capabilities. Processor 110 can also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor.

[0193] The memory 120 stores the instructions and data required for the processor 110 to operate.

[0194] The processor 110 is used to execute instructions to implement the methods provided by the above embodiments and possible combinations of the resource preemption processing method applied to the base station side in this application.

[0195] Please see Figure 20 , Figure 20 This is a schematic diagram of the structure of the second embodiment of the communication device of this application.

[0196] like Figure 20As shown, the second embodiment of the communication device of this application includes: a processor 210, a memory 220, and a communication circuit 230.

[0197] Processor 210 controls the operation of the communication device. Processor 210 can also be called a CPU (Central Processing Unit). Processor 210 may be an integrated circuit chip with signal sequence processing capabilities. Processor 210 can also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor.

[0198] The memory 220 stores the instructions and data required for the processor 210 to operate.

[0199] The processor 210 is used to execute instructions to implement the methods provided by the above embodiments and possible combinations of the resource preemption processing method applied to the user equipment side of this application.

[0200] Please see Figure 21 , Figure 21 This is a schematic diagram of the structure of an embodiment of the readable storage medium of this application.

[0201] like Figure 21 As shown, the present application has a readable storage medium storing instructions 310, which, when executed by a processor, implement the resource preemption processing method provided by the embodiments and possible combinations thereof.

[0202] Readable storage media can include read-only memory (ROM), random access memory (RAM), flash memory, hard disk, optical disk, etc.

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

[0204] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0205] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0206] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0207] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A resource preemption processing method, wherein the method is applied to the base station side, characterized in that, The method includes: acquiring information about bursty ultra-reliable low-latency communication (URLLC) services; Determine whether the first user equipment is in an uplink state in a time unit after the time unit corresponding to the URLLC burst service, wherein the first user equipment is a half-duplex user equipment; When it is determined that the first user equipment is in an uplink state in a time unit following the time unit corresponding to the URLLC burst service, a preemption indication is sent to the first user equipment before the time unit corresponding to the URLLC burst service, wherein the preemption indication is used to indicate that at least a portion of the downlink resources in the time unit corresponding to the URLLC burst service are preempted; and The radio resources allocated to the first user equipment are skipped and the radio resources preempted for the URLLC burst service are determined. The first user equipment does not allow the resources to be occupied by the URLLC burst service.

2. The method according to claim 1, characterized in that, The first user equipment shall not allow uplink and / or downlink resources to be occupied by URLLC burst services.

3. The method according to claim 1, characterized in that, Before determining the radio resources to be preempted by the URLLC burst service, the step of skipping the radio resources allocated to the first user equipment further includes: obtaining information about the first user equipment; and determining, based on the information about the first user equipment, that the first user equipment does not allow resources to be occupied by the URLLC burst service.

4. The method according to claim 3, characterized in that, The information of the first user equipment includes the capability information of the first user equipment, which includes an identifier indicating that the first user equipment does not allow resources to be occupied by URLLC burst services.

5. The method according to claim 3, characterized in that, The information of the first user equipment includes a special identifier indicating that the first user equipment does not allow resources to be occupied by URLLC burst services.

6. The method according to claim 5, characterized in that, The dedicated identifier is carried by the Radio Access Control (RRC) message.

7. A communication device, characterized in that, include: A processor, a memory, and a communication circuit, wherein the processor is connected to the communication circuit; The memory stores instructions, and the processor executes the instructions to implement the method as described in any one of claims 1-6.

8. A readable storage medium storing instructions, characterized in that, When the instructions are executed by the processor, they implement the method as described in any one of claims 1-6.

Images