Processing method, communication device, and storage medium

Abstract

The application discloses a processing method, a communication device and a storage medium. The processing method comprises: enabling or disabling uplink cancellation resources by a terminal device based on first information and second information. Through the technical scheme, in the SBFD gNB-to-gNB CLI scenario, the processing mechanism of the uplink cancellation resources is improved, and the uplink transmission performance is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a processing method, communication device, and storage medium. Background Technology

[0002] In the existing protocol, in the SBFD (Subband Full-Duplex) gNB-to-gNB CLI (gNB-to-gNBCross Link Interference) scenario, uplink resource muting can only be statically enabled or disabled through RRC (Radio Resource Control).

[0003] In conceiving and implementing this application, the inventors discovered at least the following problems: if uplink cancellation resources are statically enabled continuously, they will collide with the DMRS (Demodulation Reference Signal), and / or, uplink resource cancellation will occur unnecessarily, leading to a decrease in uplink transmission performance. Therefore, it is necessary to improve the enabling or disabling mechanism of uplink cancellation resources.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a processing method, communication device and storage medium that improves the enabling or disabling mechanism of uplink elimination resources in the SBFDgNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0006] This application provides a processing method applicable to terminal devices (such as mobile phones), comprising the following steps:

[0007] S2: Enable or disable uplink resource elimination based on the first and second information.

[0008] Optionally, the method further includes at least one of the following:

[0009] The first message is used to instruct the uplink to disable or de-enable resources;

[0010] The second piece of information is used to configure uplink elimination resources;

[0011] The first piece of information is contained in the downlink control information;

[0012] The first information is configured by RRC signaling;

[0013] The first information includes the first instruction and / or time-domain resource allocation information;

[0014] The second information is carried in the RRC signaling;

[0015] The second information includes time-domain symbol indexes and / or frequency-domain rasters.

[0016] Optionally, step S2 includes at least one of the following:

[0017] If the first information indicates that uplink elimination resources are enabled, then uplink resource elimination is performed on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0018] If the first information indicates to enable uplink resource elimination, then uplink resource elimination will not be performed on the currently scheduled PUSCH.

[0019] Optionally, the method further includes at least one of the following:

[0020] The first instruction is used to instruct the upstream to disable or de-enable resources;

[0021] Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH;

[0022] The first indication is represented by a first parameter and / or by a field of downlink control information;

[0023] The first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information;

[0024] The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

[0025] This application also provides a processing method applicable to network devices (such as base stations or satellites), comprising the following steps:

[0026] S1: Send first information and second information to enable or disable uplink elimination resources based on the first information and second information.

[0027] Optionally, the method further includes at least one of the following:

[0028] The first message is used to instruct the uplink to disable or de-enable resources;

[0029] The second piece of information is used to configure uplink elimination resources;

[0030] The first piece of information is contained in the downlink control information;

[0031] The first information is configured by RRC signaling;

[0032] The first information includes the first instruction and / or time-domain resource allocation information;

[0033] The second information is carried in the RRC signaling;

[0034] The second information includes time-domain symbol indexes and / or frequency-domain rasters.

[0035] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information, including at least one of the following:

[0036] If the first information indicates that uplink elimination resources are enabled, then uplink resource elimination is performed on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0037] If the first information indicates to enable uplink resource elimination, then uplink resource elimination will not be performed on the currently scheduled PUSCH.

[0038] Optionally, the method further includes at least one of the following:

[0039] The first instruction is used to instruct the upstream to disable or de-enable resources;

[0040] Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH;

[0041] The first indication is represented by a first parameter and / or by a field of downlink control information;

[0042] The first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information;

[0043] The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

[0044] This application also provides a processing apparatus, the apparatus comprising:

[0045] The processing module is used to enable or disable uplink elimination resources based on the first and second information.

[0046] This application also provides a processing apparatus, the apparatus comprising:

[0047] The sending module is used to send first information and second information so that the terminal device can enable or disable uplink elimination resources based on the first information and second information.

[0048] This application also provides a communication device, including: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the steps of any of the processing methods described above.

[0049] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a network device (such as a base station or satellite), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified in the context.

[0050] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of any of the processing methods described above.

[0051] The technical solution of this application embodiment enables or disables uplink elimination resources based on first information and second information. In the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the enhancement of uplink transmission performance. Attached Figure Description

[0052] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. 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, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0053] Figure 1 A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application;

[0054] Figure 2 A communication network system architecture diagram provided in this application embodiment;

[0055] Figure 3 A schematic diagram of the hardware structure of a controller 140 provided in this application;

[0056] Figure 4 A schematic diagram of the hardware structure of a network node 150 provided in this application;

[0057] Figure 5 This is a schematic flowchart illustrating the processing method of the first embodiment of this application;

[0058] Figure 6 This is a schematic flowchart illustrating the processing method of the fifth embodiment of this application;

[0059] Figure 7 This is a schematic diagram illustrating the interaction flow between a network device and a terminal device in the sixth embodiment of this application, showing the processing method.

[0060] Figure 8 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 ;

[0061] Figure 9 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 ;

[0062] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0063] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0064] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0065] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element, and / or, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0066] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0067] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0068] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0069] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0070] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0071] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0072] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a network device (such as a base station or satellite), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

[0073] Terminal devices can be implemented in various forms. For example, the terminal devices described in this application may include smart terminal devices such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0074] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminal devices.

[0075] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0076] The following is combined with Figure 1 A detailed introduction to each component of the mobile terminal:

[0077] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. And / or, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.

[0078] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0079] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0080] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0081] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0082] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0083] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands from processor 110. And / or, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0084] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0085] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0086] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). And / or, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0087] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0088] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0089] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0090] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0091] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is a New Radio (NR) system based on general mobile communication technology. The NR system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0092] Optionally, UE201 can be the aforementioned terminal device 100, which will not be described in detail here.

[0093] E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. Optionally, eNodeB2021 can connect to other eNodeB2022 via backhaul (e.g., X2 interface), and eNodeB2021 connects to EPC203, providing access from UE201 to EPC203.

[0094] EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gateway) 2034, a PGW (Packet Data Network Gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0095] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0096] Although the above description uses the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation.

[0097] Figure 3 This is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0098] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0099] Figure 4 This application provides a schematic diagram of the hardware structure of a network node 150. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0100] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0101] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0102] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.

[0103] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0104] Technical terms used in this embodiment:

[0105] PDSCH: Physical Downlink Shared Channel;

[0106] PDCCH: Physical Downlink Control Channel;

[0107] UL resource muting: UpLink resource muting, the process of eliminating resources along the uplink.

[0108] PRB: Physical Resource Block;

[0109] SBFD: Subband Full-Duplex.

[0110] First Embodiment

[0111] Reference Figure 5 , Figure 5This is a flowchart illustrating the processing method of the first embodiment of this application. The processing method of this embodiment can be applied to a terminal device (such as a mobile phone) and includes the following steps:

[0112] S2: The terminal device enables or disables uplink resource elimination based on the first and second information.

[0113] This embodiment takes into account that in the existing protocol in the SBFD (subband full-duplex) gNB-to-gNB CLI (inter-base station cross-link interference) scenario, uplink cancellation resources can only be statically enabled or disabled through RRC (Radio Resource Control). If uplink cancellation resources are statically enabled all the time, uplink cancellation resources will collide with DMRS (Demodulation Reference Signal), and / or uplink resource cancellation will be performed where it is unnecessary, which will lead to a reduction in uplink transmission performance.

[0114] Therefore, this embodiment proposes a technical solution whereby the terminal device enables or disables uplink elimination resources based on the first and second information. This can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0115] Optionally, the first and second information are provided by network devices.

[0116] Alternatively, network equipment may be base stations or satellites, etc.

[0117] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0118] Optionally, the second information is used to configure uplink elimination resources.

[0119] Optionally, the first information is carried in the downlink control information.

[0120] Optionally, the first information is configured by RRC signaling.

[0121] Optionally, the second information is carried in RRC signaling.

[0122] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0123] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0124] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0125] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information, including at least one of the following:

[0126] If the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0127] If the first information indicates to enable uplink resource removal, the terminal device will not perform uplink resource removal for the currently scheduled PUSCH.

[0128] Therefore, by enabling or disabling uplink elimination resources based on the first and second information, the terminal device can improve the enabling or disabling mechanism of uplink elimination resources in the SBFDgNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

[0129] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0130] Optionally, the first indication is represented by the first parameter.

[0131] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation.

[0132] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation-r16.

[0133] Optionally, the first parameter is located in PUSCH-Allocation-r16.

[0134] Optionally, the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation can be set to 32.

[0135] Optionally, the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 can be set to 128.

[0136] Optionally, the first indication is represented by a field of downlink control information.

[0137] Optionally, the first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information.

[0138] Optionally, the first bit is the highest bit and / or an additional bit in the time-domain resource allocation domain.

[0139] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0140] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0141] Optionally, downlink control information (DCI) schedules a single PUSCH on a single cell.

[0142] Optionally, downlink control information can schedule multiple PUSCHs on a single cell.

[0143] Optionally, downlink control information schedules multiple PUSCHs on multiple cells, with a single PUSCH scheduled on each cell.

[0144] Through the technical solution of this embodiment, the terminal device enables or disables uplink elimination resources based on the first and second information. In the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the enhancement of uplink transmission performance.

[0145] Second Embodiment

[0146] Based on the first embodiment of this application, this embodiment further describes the method of enabling or disabling uplink resource elimination by the terminal device based on the first information and the second information, combined with the scenario.

[0147] This embodiment proposes a technical solution whereby the terminal device enables or disables uplink elimination resources based on the first and second information. This can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0148] Optionally, the first and second information are provided by network devices.

[0149] Alternatively, network equipment may be base stations or satellites, etc.

[0150] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0151] Optionally, the second information is used to configure uplink elimination resources.

[0152] Optionally, the first information is carried in the downlink control information.

[0153] Optionally, the first information is configured by RRC signaling.

[0154] Optionally, the second information is carried in RRC signaling.

[0155] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0156] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information.

[0157] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0158] Optionally, if the first information indicates to enable uplink resource elimination, the terminal device will not perform uplink resource elimination for the currently scheduled PUSCH.

[0159] Optionally, the terminal device determines the uplink cancellation resource based on the indication of the first information.

[0160] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0161] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0162] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0163] Optionally, the first indication is used to instruct the upstream to disable or de-enable resources.

[0164] Optionally, the first indication is represented by the first parameter.

[0165] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0166] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0167] Optionally, DCI (Downlink Control Information) schedules a single PUSCH on a single cell.

[0168] Optionally, a single DCI can schedule multiple cells, with each cell scheduling a single PUSCH.

[0169] Optionally, the TimeDomainResourceAssignment (TDRA) field in the DCI (format 0_0, 0_1, 0_2) of the scheduling uplink data channel PUSCH is used to indicate a row in the time domain resource allocation table.

[0170] Optionally, the time-domain resource allocation table can be configured via RRC public signaling or user-specific signaling.

[0171] Optionally, if the time domain resource allocation table is not configured for initial access, the default time domain resource allocation table shall be used.

[0172] Optionally, one row of the time-domain resource allocation table contains information such as the mapping type of the PUSCH scheduled by the DCI, the time slot interval of the offset between the DCI and the scheduled PUSCH, the starting symbol position S of the PUSCH scheduled by the DCI, and the duration (i.e., the duration symbol length) L, which determines the time-domain resource position of the PUSCH indicated by the DCI.

[0173] Optionally, mapping types A and B are also typically referred to as slot-based scheduling, mini-slot-based scheduling, non-slot-based scheduling, or symbol-based scheduling, respectively. Optionally, the time-domain resource allocation table for RRC signaling configuration is shown in Table 1. Optionally, the start symbol position S and the duration symbol length L are jointly determined by the SLIV value indicated by startSymbolAndLength.

[0174] Table 1. Time Domain Resource Allocation Table

[0175]

[0176] Optionally, a first parameter (ULmutingsymbol) is added to PUSCH-TimeDomainResourceAllocation to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH.

[0177] For example, if the first parameter indicates that uplink cancellation is enabled, then uplink cancellation is performed on the currently scheduled PUSCH according to the uplink cancellation pattern configured by the second information; and / or, if it indicates that uplink cancellation is disabled or this parameter is not configured, then uplink cancellation is not required for the currently scheduled PUSCH.

[0178] Optionally, the parameter maxNrofUL-Allocations is increased to 32, thus ensuring that, apart from the first parameter, PUSCH-TimeDomainResourceAllocation has 16 combinations.

[0179] Optionally, uplink pattern cancellation is configured via RRC signaling.

[0180] Optionally, uplink pattern cancellation is configured or activated by MAC CE signaling.

[0181] Optionally, the temporal domain of the uplink elimination pattern is the symbol index.

[0182] Optionally, the symbol index includes one or both of symbol index 1 and symbol index 2.

[0183] Optionally, the frequency domain of the uplink elimination pattern is a grid, and optionally, the grid has one elimination resource element for every two resource elements or for every four resource elements.

[0184] Through the technical solution of this embodiment, the terminal device enables or disables uplink elimination resources based on the first information and the second information. For example, if the first information indicates that the uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured by the second information; and / or, if the first information indicates that the uplink elimination resources are disabled, the terminal device does not perform uplink resource elimination on the currently scheduled PUSCH. Thus, in the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance.

[0185] Third Embodiment

[0186] Based on any of the above embodiments of this application, this embodiment further describes the method of enabling or disabling uplink resource elimination by a terminal device based on first information and second information, combined with specific scenarios.

[0187] This embodiment proposes a technical solution whereby the terminal device enables or disables uplink elimination resources based on the first and second information. This can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0188] Optionally, the first and second information are provided by network devices.

[0189] Alternatively, network equipment may be base stations or satellites, etc.

[0190] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0191] Optionally, the second information is used to configure uplink elimination resources.

[0192] Optionally, the first information is carried in the downlink control information.

[0193] Optionally, the first information is configured by RRC signaling.

[0194] Optionally, the second information is carried in RRC signaling.

[0195] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0196] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information.

[0197] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0198] Alternatively, if a DCI schedules multiple PUSCHes, uplink resource elimination can be determined using the following method:

[0199] Optionally, if the first information indicates that uplink cancellation resources are enabled, the terminal device performs uplink resource cancellation on the first PUSCH of the current DCI scheduling according to the uplink cancellation resources configured in the second information.

[0200] Optionally, if the first information indicates that uplink cancellation resources are enabled, the terminal device performs uplink resource cancellation on a PUSCH currently scheduled by the DCI according to the uplink cancellation resources configured by the second information. Optionally, the location of the PUSCH in the time domain is determined by higher-layer signaling.

[0201] Optionally, if the first information indicates that uplink cancellation resources are enabled, the terminal device performs uplink resource cancellation on all PUSCHs currently scheduled by the DCI according to the uplink cancellation resources configured in the second information.

[0202] Optionally, if the first information indicates to enable uplink resource elimination, the terminal device will not perform uplink resource elimination for the currently scheduled PUSCH.

[0203] Optionally, if the first information indicates that uplink resource elimination is disabled, the terminal device will not perform uplink resource elimination for all PUSCHs currently scheduled by the DCI.

[0204] Optionally, the terminal device determines the uplink cancellation resource based on the indication of the first information.

[0205] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0206] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0207] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0208] Optionally, the first indication is used to instruct the upstream to disable or de-enable resources.

[0209] Optionally, the first indication is represented by the first parameter.

[0210] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0211] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0212] Optionally, DCI (Downlink Control Information) schedules multiple PUSCHs on a single cell.

[0213] Optionally, in the DCI format 0_1 ​​of the scheduled PUSCH, the Time Domain Resource Assignment field indicates a row in the table pusch-TimeDomainAllocationListForMultiPUSCH of the RRC configuration.

[0214] Optionally, the time-domain resource allocation table configured by RRC is shown in Table 2. Optionally, each row contains time-domain resource allocation information for up to 8 PUSCHs.

[0215] Optionally, the time-domain resource allocation information of each PUSCH includes the mapping type of the PUSCH scheduled by DCI, the starting symbol position S of the PUSCH scheduled by DCI, and the duration symbol length L, which determines the time-domain resource position of the PUSCH indicated by DCI.

[0216] Optionally, mapping types A and B are also commonly referred to as time-slot-based scheduling, micro-time-slot-based scheduling, or non-time-slot or symbol-based scheduling, respectively.

[0217] Optionally, the time-domain resource allocation table for RRC signaling configuration is shown in Table 2. Optionally, the start symbol position S and the duration symbol length L are jointly determined by the SLIV value indicated by startSymbolAndLength.

[0218] Optionally, a first parameter (ULmutingsymbol) is added to PUSCH-TimeDomainResourceAllocation-r16 to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH.

[0219] For example, if the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on the currently scheduled PUSCH according to the configured uplink cancellation pattern; and / or, if it indicates that uplink cancellation is disabled, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

[0220] Optionally, the parameter maxNrofUL-Allocations-r16 is increased to 128, thus ensuring that, apart from the first parameter, PUSCH-TimeDomainResourceAllocation-r16 has 16 possible combinations.

[0221] Optionally, a first parameter (ULmutingsymbol) is added to PUSCH-Allocation-r16 to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH.

[0222] For example, if the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on the currently scheduled PUSCH according to the configured uplink cancellation pattern; and / or, if it indicates that uplink cancellation is disabled or that this parameter is not configured, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

[0223] Optionally, if the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on all PUSCHs currently scheduled by the DCI according to the configured uplink cancellation pattern.

[0224] Optionally, if the first information indicates that uplink resource cancellation is enabled, the terminal device performs uplink resource cancellation on the first PUSCH of the current DCI scheduling according to the configured uplink cancellation pattern.

[0225] Optionally, if the first information indicates that uplink resource cancellation is enabled, the terminal device performs uplink resource cancellation on a PUSCH currently scheduled by the DCI according to the configured uplink cancellation pattern. Optionally, the location of the PUSCH in the time domain is determined by higher-layer signaling.

[0226] Alternatively, if the instruction is to enable uplink cancellation or not configure this parameter, the terminal device does not need to perform uplink cancellation on all PUSCHs currently scheduled by the DCI.

[0227] Table 2. Time-domain resource allocation table for RRC configuration

[0228]

[0229] Optionally, uplink pattern cancellation is configured via RRC signaling.

[0230] Optionally, uplink pattern cancellation is configured or activated by MAC CE signaling.

[0231] Optionally, the temporal domain of the uplink elimination pattern is the symbol index.

[0232] Optionally, the symbol index includes one or both of symbol index 1 and symbol index 2.

[0233] Optionally, the frequency domain of the uplink elimination pattern is a grid, and optionally, the grid has one elimination resource element for every two resource elements or for every four resource elements.

[0234] Optionally, a first parameter (ULmutingsymbol) is added to PUSCH-Allocation-r16 to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH.

[0235] For example, if the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on the currently scheduled PUSCH according to the uplink cancellation pattern configured in the time domain resource allocation table of the RRC configuration shown in Table 3; and / or, if it indicates that uplink cancellation is disabled or this parameter is not configured, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

[0236] Table 3. Time-domain resource allocation table for RRC configuration

[0237]

[0238] Through the technical solution of this embodiment, the terminal device enables or disables uplink elimination resources based on the first information and the second information. For example, if the first information indicates that the uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured by the second information; and / or, if the first information indicates that the uplink elimination resources are disabled, the terminal device does not perform uplink resource elimination on the currently scheduled PUSCH. Thus, in the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance.

[0239] Fourth embodiment

[0240] Based on any of the above embodiments of this application, this embodiment further describes the method of enabling or disabling uplink resource elimination by a terminal device based on first information and second information, combined with specific scenarios.

[0241] This embodiment proposes a technical solution whereby the terminal device enables or disables uplink elimination resources based on the first and second information. This can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0242] Optionally, the first and second information are provided by network devices.

[0243] Alternatively, network equipment may be base stations or satellites, etc.

[0244] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0245] Optionally, the second information is used to configure uplink elimination resources.

[0246] Optionally, the first information is carried in the downlink control information.

[0247] Optionally, the first information is configured by RRC signaling.

[0248] Optionally, the second information is carried in RRC signaling.

[0249] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0250] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information.

[0251] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0252] Optionally, if the first information indicates to enable uplink resource elimination, the terminal device will not perform uplink resource elimination for the currently scheduled PUSCH.

[0253] Optionally, the terminal device determines the uplink cancellation resource based on the indication of the first information.

[0254] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0255] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0256] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0257] Optionally, the first indication is used to instruct the upstream to disable or de-enable resources.

[0258] Optionally, the first indication is represented by a field of downlink control information.

[0259] Optionally, the first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information.

[0260] Optionally, the first bit is the highest bit and / or an additional bit in the time-domain resource allocation domain.

[0261] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0262] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0263] Optionally, downlink control information schedules multiple PUSCHs on multiple cells, with a single PUSCH scheduled on each cell.

[0264] Optionally, the TimeDomainResource Assignment field in the DCI (format 0_0, 0_1, 0_2) of the scheduling uplink data channel PUSCH is used to indicate a row in the time domain resource allocation table.

[0265] Optionally, the time-domain resource allocation table can be configured via RRC public signaling or user-specific signaling.

[0266] Optionally, if the time domain resource allocation table is not configured for initial access, the default time domain resource allocation table shall be used.

[0267] Optionally, one row of the time-domain resource allocation table contains information such as the mapping type of the PUSCH scheduled by the DCI, the time slot interval of the offset between the DCI and the scheduled PUSCH, the starting symbol position S of the PUSCH scheduled by the DCI, and the duration symbol length L, which determines the time-domain resource position of the PUSCH indicated by the DCI.

[0268] Optionally, mapping types A and B are also typically referred to as slot-based scheduling, micro-slot-based scheduling, or non-slot-based or symbol-based scheduling, respectively. Optionally, the time-domain resource allocation for RRC signaling configuration is shown in Table 1. Optionally, the start symbol position S and the duration symbol length L are jointly determined by the SLIV value indicated by startSymbolAndLength.

[0269] Optionally, one bit in the Time Domain Resource Assignment field of the DCI (format 0_0,0_1,0_2) can be used to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH.

[0270] For example, if the TDRA field in the DCI indicates that uplink cancellation is enabled, then uplink cancellation is performed on the currently scheduled PUSCH according to the configured uplink cancellation pattern. If the TDRA field in the DCI indicates that uplink cancellation is disabled or is not configured, then uplink cancellation is not required for the currently scheduled PUSCH.

[0271] Optionally, the 1 bit is the highest bit in the TDRA field.

[0272] Optionally, the bits other than the highest bit in the Time Domain Resource Assignment field are used to indicate the time domain information for scheduling PUSCH.

[0273] Optionally, the 1 bit is the least significant bit in the TDRA field.

[0274] Optionally, the bits other than the least significant bit in the Time Domain Resource Assignment field are used to indicate the time domain information for scheduling PUSCH.

[0275] Optionally, the 1 bit is a newly added 1 bit.

[0276] Optionally, if the 1 bit is a newly added 1 bit, then the TDRA field is bits, where I TDRA Configure the number of rows in the time domain resource allocation table for RRC public signaling or user-specific signaling.

[0277] Optionally, the terminal device determines whether to enable or disable uplink cancellation based on the SLIV value and the threshold value.

[0278] Optionally, if the SLIV value is less than a first threshold, the terminal device can perform uplink cancellation.

[0279] Optionally, if the SLIV value is greater than or equal to the first threshold, the terminal device disables uplink cancellation.

[0280] Optionally, if the SLIV value is greater than the second threshold, the terminal device enables uplink cancellation.

[0281] Optionally, if the SLIV value is less than or equal to the second threshold, the terminal device disables uplink cancellation.

[0282] Optionally, the values ​​of the first threshold and / or the second threshold are configured by RRC signaling.

[0283] Optionally, the SLIV value is configured by RRC signaling and indicated by the TDRA field in the DCI.

[0284] Optionally, uplink pattern cancellation is configured via RRC signaling.

[0285] Optionally, uplink pattern cancellation is configured or activated by MAC CE signaling.

[0286] Optionally, the temporal domain of the uplink elimination pattern is the symbol index.

[0287] Optionally, the symbol index includes one or both of symbol index 1 and symbol index 2.

[0288] Optionally, the frequency domain of the uplink elimination pattern is a grid, and optionally, the grid has one elimination resource element for every two resource elements or for every four resource elements.

[0289] Through the technical solution of this embodiment, the terminal device enables or disables uplink elimination resources based on the first information and the second information. For example, if the first information indicates that the uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured by the second information; and / or, if the first information indicates that the uplink elimination resources are disabled, the terminal device does not perform uplink resource elimination on the currently scheduled PUSCH. Thus, in the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance.

[0290] Fifth Embodiment

[0291] Reference Figure 6 , Figure 6 This is a flowchart illustrating the processing method of the fifth embodiment of this application. The processing method of this embodiment can be applied to network devices (such as base stations) and includes the following steps:

[0292] S1: The network device sends first information and second information to enable or disable uplink elimination resources based on the first information and second information.

[0293] This embodiment proposes a technical solution that can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0294] Optionally, the first and second information are provided by network devices.

[0295] Alternatively, network equipment may be base stations or satellites, etc.

[0296] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0297] Optionally, the second information is used to configure uplink elimination resources.

[0298] Optionally, the first information is carried in the downlink control information.

[0299] Optionally, the first information is configured by RRC signaling.

[0300] Optionally, the second information is carried in RRC signaling.

[0301] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0302] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0303] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0304] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information, including at least one of the following:

[0305] If the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0306] If the first information indicates to enable uplink resource removal, the terminal device will not perform uplink resource removal for the currently scheduled PUSCH.

[0307] Therefore, by enabling or disabling uplink elimination resources based on the first and second information, the terminal device can improve the enabling or disabling mechanism of uplink elimination resources in the SBFDgNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

[0308] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0309] Optionally, the first indication is represented by the first parameter.

[0310] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation.

[0311] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation-r16.

[0312] Optionally, the first parameter is located in PUSCH-Allocation-r16.

[0313] Optionally, the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation can be set to 32.

[0314] Optionally, the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 can be set to 128.

[0315] Optionally, the first indication is represented by a field of downlink control information.

[0316] Optionally, the first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information.

[0317] Optionally, the first bit is the highest bit and / or a newly added bit in the time-domain resource allocation domain.

[0318] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0319] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0320] Optionally, downlink control information (DCI) schedules a single PUSCH on a single cell.

[0321] Optionally, downlink control information can schedule multiple PUSCHs on a single cell.

[0322] Optionally, downlink control information schedules multiple PUSCHs on multiple cells, with a single PUSCH scheduled on each cell.

[0323] Through the technical solution of this embodiment, the network device sends first information and second information so that the terminal device can enable or disable uplink elimination resources based on the first information and second information. In the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance.

[0324] Sixth Embodiment

[0325] Reference Figure 7 , Figure 7 This application provides a processing method according to the sixth embodiment, which includes the following steps: (The sixth embodiment is a schematic diagram of the interaction process between a network device and a terminal device.)

[0326] S1: The network device sends first information and second information to enable or disable uplink resource elimination based on the first information and second information;

[0327] S2: The terminal device enables or disables uplink resource elimination based on the first and second information.

[0328] This embodiment proposes a technical solution whereby the terminal device enables or disables uplink elimination resources based on the first and second information. This can improve the enabling or disabling mechanism of uplink elimination resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0329] Optionally, the first and second information are provided by network devices.

[0330] Alternatively, network equipment may be base stations or satellites, etc.

[0331] Optionally, the first information is used to instruct the uplink to disable or de-enable the resource.

[0332] Optionally, the second information is used to configure uplink elimination resources.

[0333] Optionally, the first information is carried in the downlink control information.

[0334] Optionally, the first information is configured by RRC signaling.

[0335] Optionally, the second information is carried in RRC signaling.

[0336] Optionally, the second information includes a time-domain symbol index and / or a frequency-domain raster.

[0337] Optionally, the terminal device determines uplink cancellation resource enable based on the indication of the first information.

[0338] Optionally, the terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0339] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information, including at least one of the following:

[0340] If the first information indicates that uplink elimination resources are enabled, the terminal device performs uplink resource elimination on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0341] If the first information indicates to enable uplink resource removal, the terminal device will not perform uplink resource removal for the currently scheduled PUSCH.

[0342] Therefore, by enabling or disabling uplink elimination resources based on the first and second information, the terminal device can improve the enabling or disabling mechanism of uplink elimination resources in the SBFDgNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

[0343] Optionally, the first information includes a first instruction and / or time-domain resource allocation information.

[0344] Optionally, the first indication is represented by the first parameter.

[0345] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation.

[0346] Optionally, the first parameter is located in PUSCH-TimeDomainResourceAllocation-r16.

[0347] Optionally, the first parameter is located in PUSCH-Allocation-r16.

[0348] Optionally, the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation can be set to 32.

[0349] Optionally, the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 can be set to 128.

[0350] Optionally, the first indication is represented by a field of downlink control information.

[0351] Optionally, the first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information.

[0352] Optionally, the first bit is the highest bit and / or an additional bit in the time-domain resource allocation domain.

[0353] Optionally, time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH.

[0354] Optionally, the time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by the downlink control information, the time slot interval of the offset between the downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by the downlink control information, and the duration.

[0355] Optionally, downlink control information (DCI) schedules a single PUSCH on a single cell.

[0356] Optionally, downlink control information can schedule multiple PUSCHs on a single cell.

[0357] Optionally, downlink control information schedules multiple PUSCHs on multiple cells, with a single PUSCH scheduled on each cell.

[0358] Through the technical solution of this embodiment, the network device sends first information and second information, and the terminal device enables or disables uplink elimination resources based on the first information and second information. In the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance.

[0359] Seventh Embodiment

[0360] Please see Figure 8 , Figure 8 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 1 This device can be mounted on or is the terminal device in the above method embodiments, such as... Figure 8 As shown, the processing device 160 includes:

[0361] Processing module 1601 is used to enable or disable uplink elimination resources based on first information and second information.

[0362] Optionally, the device further includes at least one of the following:

[0363] The first message is used to instruct the uplink to disable or de-enable resources;

[0364] The second piece of information is used to configure uplink elimination resources;

[0365] The first piece of information is contained in the downlink control information;

[0366] The first information is configured by RRC signaling;

[0367] The first information includes the first instruction and / or time-domain resource allocation information;

[0368] The second information is carried in the RRC signaling;

[0369] The second information includes time-domain symbol indexes and / or frequency-domain rasters.

[0370] Optionally, enabling or disabling uplink elimination resources based on the first and second information includes at least one of the following:

[0371] If the first information indicates that uplink elimination resources are enabled, then uplink resource elimination is performed on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0372] If the first information indicates to enable uplink resource elimination, then uplink resource elimination will not be performed on the currently scheduled PUSCH.

[0373] Optionally, the device further includes at least one of the following:

[0374] The first instruction is used to instruct the upstream to disable or de-enable resources;

[0375] Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH;

[0376] The first indication is represented by a first parameter and / or by a field of downlink control information;

[0377] The first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information;

[0378] The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

[0379] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0380] Eighth embodiment

[0381] Please see Figure 9 , Figure 9 Schematic diagram of the processing apparatus provided in the embodiments of this application Figure 2 This device can be mounted on or is the network device described in the above method embodiments, such as... Figure 9 As shown, the device 170 includes:

[0382] The sending module 1701 is used to send first information and second information so that the terminal device can enable or disable uplink elimination resources based on the first information and second information.

[0383] Optionally, the device further includes at least one of the following:

[0384] The first message is used to instruct the uplink to disable or de-enable resources;

[0385] The second piece of information is used to configure uplink elimination resources;

[0386] The first piece of information is contained in the downlink control information;

[0387] The first information is configured by RRC signaling;

[0388] The first information includes the first instruction and / or time-domain resource allocation information;

[0389] The second information is carried in the RRC signaling;

[0390] The second information includes time-domain symbol indexes and / or frequency-domain rasters.

[0391] Optionally, the terminal device enables or disables uplink elimination resources based on the first and second information, including at least one of the following:

[0392] If the first information indicates that uplink elimination resources are enabled, then uplink resource elimination is performed on the currently scheduled PUSCH according to the uplink elimination resources configured in the second information.

[0393] If the first information indicates to enable uplink resource elimination, then uplink resource elimination will not be performed on the currently scheduled PUSCH.

[0394] Optionally, the device further includes at least one of the following:

[0395] The first instruction is used to instruct the upstream to disable or de-enable resources;

[0396] Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH;

[0397] The first indication is represented by a first parameter and / or by a field of downlink control information;

[0398] The first indication is represented by the first bit in the time-domain resource allocation field of the downlink control information;

[0399] The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

[0400] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0401] See Figure 10 , Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 10 As shown, the communication device 180 described in this embodiment can be a terminal device (or a component that can be used in a terminal device) or a network device (or a component that can be used in a network device) mentioned in the foregoing method embodiments. The communication device 180 can be used to implement the methods corresponding to the terminal device or network device described in the above method embodiments, as detailed in the descriptions in the above method embodiments.

[0402] The communication device 180 may include one or more processors 1801, which may also be referred to as processing units, and can perform certain control or processing functions. The processor 1801 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0403] Optionally, the processor 1801 may also store instructions 1803 or data (e.g., intermediate data). Optionally, instructions 1803 may be executed by the processor 1801, causing the communication device 180 to perform the methods described in the above method embodiments corresponding to the terminal device or network device.

[0404] Optionally, the communication device 180 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[0405] Optionally, the communication device 180 may include one or more memories 1802, which may store instructions 1804 that can be executed on the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments.

[0406] Alternatively, the memory 1802 may also store data. The processor 1801 and the memory 1802 can be configured separately or integrated together.

[0407] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801, which may be referred to as a processing unit, controls the communication device 180 (terminal device, core network device, or wireless access network device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transceiver functions of the communication device 180.

[0408] Optionally, if the communication device 180 is used to implement the operation corresponding to the terminal device in the above embodiments, for example, the transceiver 1805 may receive the first information and the second information; and the processor 1801 may enable or disable uplink elimination resources based on the first information and the second information.

[0409] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0410] Optionally, if the communication device 180 is used to implement the operation corresponding to the network device in the above embodiments, for example, the transceiver 1805 can send the first information and the second information.

[0411] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0412] The processor 1801 and transceiver 1805 described in this application can be implemented in ICs (Integrated Circuits), analog integrated circuits, RFICs (Radio Frequency Integrated Circuits), mixed-signal integrated circuits, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N Metal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0413] In this application, the communication device can be a terminal device (such as a mobile phone) or a network device (such as a base station), depending on the context. Furthermore, the terminal device can be implemented in various forms. For example, the terminal devices described in this application can include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0414] Although the communication devices described above are exemplified as terminal devices or network devices, the scope of the communication devices described in this application is not limited to the aforementioned terminal devices or network devices, and the structure of the communication devices may vary. Figure 10 There are limitations. Communication equipment can be a standalone device or part of a larger device.

[0415] This application also provides a communication system, including: a terminal device as described in any of the above embodiments; and a network device as described in any of the above embodiments.

[0416] This application also provides a communication device, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the steps of the processing method in any of the above embodiments.

[0417] The communication equipment mentioned in this application may be a terminal device (such as a mobile phone), a network device (such as a base station or satellite), or a chip (such as a SOC or a baseband chip with communication functions). The specific meaning needs to be clarified according to the context.

[0418] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of the processing method in any of the above embodiments.

[0419] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described processing method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.

[0420] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0421] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0422] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0423] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0424] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0425] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0426] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0427] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0429] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the methods of each embodiment of this application.

[0430] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0431] The above are merely preferred embodiments of this application and do 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 processing method, characterized in that, Applied to terminal devices, including the following steps: S2: Enable or disable uplink resource elimination based on the first and second information; The first information includes the time domain resource allocation domain of the first instruction and downlink control information; The first instruction is represented by the first parameter; The first parameter is included in PUSCH-Allocation-r16; The first parameter is used to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH. If the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on the currently scheduled PUSCH according to the uplink cancellation pattern configured in the second information. If the first parameter indicates that uplink cancellation is disabled or the first parameter is not configured, the terminal device does not perform uplink cancellation on the currently scheduled PUSCH. The temporal domain of the upward elimination pattern is the symbol index; The PUSCH-Allocation-r16 corresponding to the currently scheduled PUSCH is indicated by the time-domain resource allocation field of the downlink control information.

2. The method according to claim 1, characterized in that, It also includes at least one of the following: The first parameter is ULmutingsymbol; The first information also includes time-domain resource allocation information; The second information is carried in the RRC signaling; The second information includes time-domain symbol indexes and / or frequency-domain rasters.

3. The method according to claim 2, characterized in that, It also includes at least one of the following: Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH; The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

4. A processing method, characterized in that, Applied to network devices, including the following steps: S1: Send first information and second information to enable or disable uplink resource elimination based on the first information and second information; The first information includes the time domain resource allocation domain of the first instruction and downlink control information; The first instruction is represented by the first parameter; The first parameter is included in PUSCH-Allocation-r16; The first parameter is used to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH. If the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on the currently scheduled PUSCH according to the uplink cancellation pattern configured in the second information. If the first parameter indicates that uplink cancellation is disabled or the first parameter is not configured, the terminal device does not perform uplink cancellation on the currently scheduled PUSCH. The temporal domain of the upward elimination pattern is the symbol index; The PUSCH-Allocation-r16 corresponding to the currently scheduled PUSCH is indicated by the time-domain resource allocation field of the downlink control information.

5. The method according to claim 4, characterized in that, It also includes at least one of the following: The first parameter is ULmutingsymbol; The first information also includes time-domain resource allocation information; The second information is carried in the RRC signaling; The second information includes time-domain symbol indexes and / or frequency-domain rasters.

6. The method according to claim 5, characterized in that, It also includes at least one of the following: Time-domain resource allocation information is used to indicate the time-domain resource allocation of PUSCH; The time-domain resource allocation information includes at least one of the following: the mapping type of the PUSCH scheduled by downlink control information, the time slot interval of the offset between downlink control information and the scheduled PUSCH, the start symbol of the PUSCH scheduled by downlink control information, and the duration.

7. A communication device, characterized in that, include: A memory and a processor, wherein the memory stores a processing program, and the processing program, when executed by the processor, implements the processing method as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the processing method as described in any one of claims 1 to 6.

Images