Processing method, communication device and storage medium

Abstract

The invention discloses a processing method, communication equipment and a storage medium. The processing method comprises the step that terminal equipment enables or de-enables uplink elimination resources based on first information and second information. Through the technical scheme of the invention, in an SBFD gNB-to-gNB CLI scene, a processing mechanism of uplink elimination resources is perfected, and the uplink transmission performance is further supported to be improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a processing method, a communication device and a storage medium. Background Art

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

[0003] In the process of conceiving and implementing the present application, the inventors found that there are at least the following problems: if the uplink cancellation resource is always statically enabled, the uplink cancellation resource will collide with the DMRS (Demodulation Reference Signal), and / or, the uplink resource will be eliminated where it is not necessary, which will lead to a decrease in uplink transmission performance. Therefore, it is necessary to improve the enabling or disabling mechanism of the uplink cancellation resource.

[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, a communication device and a storage medium, which 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] The present application provides a processing method which can be applied to a terminal device (such as a mobile phone), comprising the steps of:

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

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

[0009] The first information is used to indicate whether uplink resource elimination is enabled or disabled;

[0010] The second information is used to configure uplink cancellation resources;

[0011] The first information is carried in the downlink control information;

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

[0013] The first information includes a first indication and / or time domain resource allocation information;

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

[0015] The second information includes a time domain symbol index and / or a frequency domain grid.

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

[0017] If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information;

[0018] If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

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

[0020] The first indication is used to indicate whether uplink resource elimination is enabled or disabled;

[0021] The time domain resource allocation information is used to indicate the time domain resource allocation of the 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 a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

[0025] The present application also provides a processing method, which can be applied to a network device (such as a base station or a satellite), comprising the steps of:

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

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

[0028] The first information is used to indicate whether uplink resource elimination is enabled or disabled;

[0029] The second information is used to configure uplink cancellation resources;

[0030] The first information is carried in the downlink control information;

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

[0032] The first information includes a first indication and / or time domain resource allocation information;

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

[0034] The second information includes a time domain symbol index and / or a frequency domain grid.

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

[0036] If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information;

[0037] If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

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

[0039] The first indication is used to indicate whether uplink resource elimination is enabled or disabled;

[0040] The time domain resource allocation information is used to indicate the time domain resource allocation of the 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 a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

[0044] The present application also provides a processing device, the device comprising:

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

[0046] The present application also provides a processing device, the device comprising:

[0047] A sending module is used to send first information and second information so that the terminal device enables or disables uplink elimination resources based on the first information and the second information.

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

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

[0050] The present application also provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of any of the processing methods described above are implemented.

[0051] According to the technical solution of the embodiment of the present application, the terminal device enables or disables uplink elimination resources based on the first information and the second information. In the SBFD gNB-to-gNB CLI scenario, the enabling or disabling mechanism of the uplink elimination resources is improved, thereby supporting the improvement of uplink transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

[0053] Figure 1 A schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0054] Figure 2 A communication network system architecture diagram provided for an embodiment of the present application;

[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 flow chart of a processing method according to the first embodiment of the present application;

[0058] Figure 6 This is a flowchart of a processing method according to the fifth embodiment of the present application;

[0059] Figure 7 A schematic diagram of the interaction process between a network device and a terminal device showing a processing method in the sixth embodiment of the present application;

[0060] Figure 8 A schematic diagram of the structure of the processing device provided in the embodiment of the present application Figure 1 ;

[0061] Fig. 9 A schematic diagram of the structure of the processing device provided in the embodiment of the present application Figure 2 ;

[0062] Fig.10 A schematic diagram of the structure of a communication device provided in an embodiment of the present application.

[0063] The realization of the purpose, functional features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The above-mentioned drawings have shown clear embodiments of this application, which will be described in more detail later. These drawings and textual descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0064] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0065] It should be noted that, in this article, the terms "comprises", "includes" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element, and / or, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0066] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate that there are the described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or", "and / or", "including at least one of the following" etc. used in this application can be interpreted as inclusive, or mean any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”, and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0067] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0068] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

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

[0070] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0071] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0072] The communication device in this application can be a terminal device (such as a mobile phone), a network device (such as a base station or a satellite), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified based on the context.

[0073] The terminal device may be implemented in various forms. For example, the terminal device described in this application may include intelligent terminal devices such as mobile phones, tablet computers, laptop computers, 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 subsequent description will be made by taking a mobile terminal as an example, and those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the construction according to the embodiments of the present application can also be applied to fixed-type terminal devices.

[0075] See also Figure 1 , which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application, the mobile terminal 100 may include: RF (Radio Frequency, radio frequency) unit 101, WiFi module 102, audio output unit 103, A / V (audio / video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111 and other components. Those skilled in the art can understand that Figure 1 The structure of the mobile terminal shown in the figure does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0076] Combine the following Figure 1 The following is a detailed introduction to the various components of the mobile terminal:

[0077] The radio frequency unit 101 can be used for receiving and sending signals during information transmission or communication. Specifically, after receiving the downlink information of the base station, it is sent to the processor 110 for processing; in addition, the uplink data is sent to the base station. Generally, 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 with the network and other devices through wireless communication. The above-mentioned wireless communications can 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, etc.

[0078] WiFi is a short-range wireless transmission technology. Mobile terminals can help users send and receive emails, browse web pages, and access streaming media through WiFi module 102. It provides users with wireless broadband Internet access. Figure 1 The WiFi module 102 is shown, but it is understandable that it is not an essential component of the mobile terminal and can be omitted as needed without changing the essence of the invention.

[0079] The audio output unit 103 can convert the audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, etc. Moreover, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (for example, a call signal reception sound, a message reception 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 processor (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 106. The image frame processed by the graphics processor 1041 can be stored in the memory 109 (or other storage medium) or sent via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a telephone call mode, a recording mode, a voice recognition mode, and other operating modes, and can process such sound into audio data. The processed audio (voice) data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 can implement various types of noise elimination (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and sending 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 brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can also be configured on the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated 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] The user input unit 107 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1071 or near the touch panel 1071 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 110, and can receive and execute the command sent by the processor 110. And / or, the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, etc., which are not 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. Then, the processor 110 provides corresponding visual output on the display panel 1061 according to the type of touch event. Figure 1 In the figure, the touch panel 1071 and the display panel 1061 are used as two independent components to implement 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 implement the input and output functions of the mobile terminal, which is not limited here.

[0085] The interface unit 108 serves as an interface through which at least one external device can be connected to the 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, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

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

[0087] The processor 110 is the control center of the mobile terminal. It uses various interfaces and lines to connect various parts of the entire mobile terminal. It executes various functions of the mobile terminal and processes data by running or executing software programs and / or modules stored in the memory 109, and calling data stored in the memory 109, so as to monitor the mobile terminal as a whole. 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 processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned 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) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

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

[0090] In order to facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0091] See also Figure 2 , Figure 2 A communication network system architecture diagram is provided for an embodiment of the present application. The communication network system is a NR (New Radio) system of universal 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 an operator's IP service 204, which are connected in sequence.

[0092] Optionally, UE201 may be the above-mentioned terminal device 100, which will not be described in detail here.

[0093] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 , etc. Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface), and eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide UE 201 with access to EPC 203 .

[0094] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, PGW (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, and provides bearer and connection management. HSS 2032 is used to provide some registers to manage functions such as home location register (not shown in the figure), and store some user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, which selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

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

[0096] Although the above introduction takes the LTE system as an example, those skilled in the art should know that the present 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 here.

[0097] Figure 3 The hardware structure diagram of a controller 140 provided in the present application is shown in FIG. 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 executed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar and will not be described in detail 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 The hardware structure diagram of a network node 150 provided in the present application is shown in FIG. 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, and its implementation principle and beneficial effects are similar, which will not be repeated 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 above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the methods of various embodiments of the present application.

[0102] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a storage medium, or transmitted from one storage medium to another storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. 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 includes one or more available media integration. Available media can be magnetic media, (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state hard disk solid state disk, SSD), etc.

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

[0104] Technical terms involved in this embodiment:

[0105] PDSCH: Physical Downlink Shared CHannel, physical downlink shared channel;

[0106] PDCCH: Physical Downlink Control CHannel, physical downlink control channel;

[0107] UL resource muting: UpLink resource muting, uplink resource muting;

[0108] PRB: Physical Resource Block, physical resource block;

[0109] SBFD: SubBand Full-Duplex, sub-band full-duplex.

[0110] First embodiment

[0111] Reference Figure 5 , Figure 5This is a flow chart of a processing method according to the first embodiment of the present application. The processing method according to the embodiment of the present application 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 elimination resources based on the first information and the second information.

[0113] This embodiment takes into account that in the existing protocol, in the SBFD (sub-band full-duplex) gNB-to-gNB CLI (base station cross-link interference) scenario, uplink cancellation resources can only be statically enabled or disabled through RRC (radio resource control). If the uplink cancellation resources are always statically enabled, the uplink cancellation resources will collide with the DMRS (demodulation reference signal) and / or uplink resource elimination will be performed where it is not necessary, which will result in a decrease in uplink transmission performance.

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

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

[0116] Optionally, the network device may be a base station or a satellite, etc.

[0117] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0119] Optionally, the first information is carried in 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 grid.

[0123] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

[0125] Optionally, the terminal device enables or disables uplink cancellation resources based on the first information and the 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 by the second information;

[0127] If the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

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

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

[0130] Optionally, the first indication is represented by a 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 value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0135] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 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 a newly added bit in the time domain resource allocation domain.

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

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

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

[0142] Optionally, the downlink control information schedules multiple PUSCHs on a single cell.

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

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

[0145] Second embodiment

[0146] On the basis of the first embodiment of the present application, this embodiment further describes a method for enabling or disabling uplink elimination resources by a terminal device based on first information and second information in combination with a scenario.

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

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

[0149] Optionally, the network device may be a base station or a satellite, etc.

[0150] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0152] Optionally, the first information is carried in 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 grid.

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

[0157] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device eliminates uplink resources for the currently scheduled PUSCH according to the uplink elimination resources configured by the second information.

[0158] Optionally, if the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

[0159] Optionally, the terminal device determines uplink elimination resources based on an indication of the first information.

[0160] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

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

[0163] Optionally, the first indication is used to indicate uplink resource elimination enabling or disabling.

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

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

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

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

[0168] Optionally, a single DCI schedules multiple cells, and each cell schedules a single PUSCH.

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

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

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

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

[0173] Optionally, mapping types A and B are also generally referred to as slot-based scheduling, mini slot-based scheduling or non slot-based scheduling or symbol scheduling, respectively. Optionally, the time domain resource allocation table configured by RRC signaling is shown in Table 1. Optionally, the start symbol position S and the continuous 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 is added in PUSCH-TimeDomainResourceAllocation, where the first parameter (ULmutingsymbol) is used to indicate whether uplink muting is enabled in the currently scheduled PUSCH.

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

[0178] Optionally, the parameter maxNrofUL-Allocations is increased to 32, thereby ensuring that, in addition to the first parameter, there are 16 combinations of PUSCH-TimeDomainResourceAllocation.

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

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

[0181] Optionally, the time domain of the uplink cancellation pattern is a 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 cancellation pattern is a grid, and optionally, the grid has one cancellation resource element for every 2 resource elements or every 4 resource elements.

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

[0185] Third embodiment

[0186] On the basis of any of the above embodiments of the present application, this embodiment further describes a method for enabling or disabling uplink elimination resources by a terminal device based on first information and second information in combination with a scenario.

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

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

[0189] Optionally, the network device may be a base station or a satellite, etc.

[0190] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0192] Optionally, the first information is carried in 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 grid.

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

[0197] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device eliminates uplink resources for the currently scheduled PUSCH according to the uplink elimination resources configured by the second information.

[0198] Optionally, if one DCI schedules multiple PUSCHs, uplink resource elimination may be determined according to the following method:

[0199] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device eliminates uplink resources for the first PUSCH scheduled by the current DCI according to the uplink elimination resources configured by the second information.

[0200] Optionally, if the first information indicates enabling uplink elimination resources, the terminal device performs uplink resource elimination on a PUSCH currently scheduled by the DCI according to the uplink elimination resources configured by the second information. Optionally, the position of the PUSCH in the time domain is determined by high-level signaling.

[0201] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device eliminates uplink resources for all PUSCHs currently scheduled by the DCI according to the uplink elimination resources configured by the second information.

[0202] Optionally, if the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

[0203] Optionally, if the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for all PUSCHs currently scheduled by the DCI.

[0204] Optionally, the terminal device determines uplink elimination resources based on an indication of the first information.

[0205] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

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

[0208] Optionally, the first indication is used to indicate uplink resource elimination enabling or disabling.

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

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

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

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

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

[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 of up to 8 PUSCHs.

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

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

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

[0218] Optionally, a first parameter is added in PUSCH-TimeDomainResourceAllocation-r16, where the first parameter (ULmutingsymbol) is used to indicate whether uplink muting 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 the indication is 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, thereby ensuring that in addition to the first parameter, there are 16 combinations of PUSCH-TimeDomainResourceAllocation-r16.

[0221] Optionally, a first parameter is added in PUSCH-Allocation-r16, where the first parameter (ULmutingsymbol) is used to indicate whether uplink muting 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 the indication is 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.

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

[0224] Optionally, if the first information indicates enabling uplink resource elimination, the terminal device eliminates uplink resources for the first PUSCH scheduled by the current DCI according to the configured uplink elimination pattern.

[0225] Optionally, if the first information indicates enabling uplink resource elimination, the terminal device eliminates uplink resources for a PUSCH currently scheduled by the DCI according to the configured uplink elimination pattern. Optionally, the position of the PUSCH in the time domain is determined by high-level signaling.

[0226] Optionally, if it is indicated that uplink cancellation is disabled or this parameter is not configured, 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, the uplink cancellation pattern is configured by RRC signaling.

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

[0231] Optionally, the time domain of the uplink cancellation pattern is a 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 cancellation pattern is a grid, and optionally, the grid has one cancellation resource element for every 2 resource elements or every 4 resource elements.

[0234] Optionally, a first parameter is added in PUSCH-Allocation-r16, where the first parameter (ULmutingsymbol) is used to indicate whether uplink muting 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 PUSCH currently scheduled by the DCI according to the uplink cancellation pattern configured by 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 the uplink elimination resource based on the first information and the second information. For example, if the first information indicates to enable the uplink elimination resource, the terminal device eliminates the uplink resources of the currently scheduled PUSCH according to the uplink elimination resource configured by the second information; and / or, if the first information indicates to disable the uplink elimination resource, the terminal device does not eliminate the uplink resources of the currently scheduled PUSCH, thereby improving the enabling or disabling mechanism of the uplink elimination resource in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0239] Fourth embodiment

[0240] On the basis of any of the above embodiments of the present application, this embodiment further describes a method for enabling or disabling uplink elimination resources by a terminal device based on first information and second information in combination with a scenario.

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

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

[0243] Optionally, the network device may be a base station or a satellite, etc.

[0244] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0246] Optionally, the first information is carried in 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 grid.

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

[0251] Optionally, if the first information indicates that uplink elimination resources are enabled, the terminal device eliminates uplink resources for the currently scheduled PUSCH according to the uplink elimination resources configured by the second information.

[0252] Optionally, if the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

[0253] Optionally, the terminal device determines uplink elimination resources based on an indication of the first information.

[0254] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

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

[0257] Optionally, the first indication is used to indicate uplink resource elimination enabling or disabling.

[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 a newly added bit in the time domain resource allocation domain.

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

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

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

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

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

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

[0267] Optionally, a row of the time domain resource allocation table contains information on the mapping type of the DCI-scheduled PUSCH, the offset time slot interval between the DCI and the scheduled PUSCH, the starting symbol position S of the DCI-scheduled PUSCH, and the continuous symbol length L, thereby determining the PUSCH time domain resource position indicated by the DCI.

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

[0269] Optionally, 1 bit in the Time Domain Resource Assignment field in the DCI (format 0_0, 0_1, 0_2) is 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, 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 this field is not configured, uplink cancellation does not need to be performed on the currently scheduled PUSCH.

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

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

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

[0274] Optionally, bits other than the lowest bit in the Time Domain Resource Assignment field are used to indicate 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, the TDRA field is bit, where I TDRA Configure the number of rows in the time domain resource allocation table for RRC common signaling or user-specific signaling.

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

[0278] Optionally, if the SLIV value is less than the first threshold, the terminal device can achieve uplink elimination.

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

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

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

[0282] Optionally, the value of the first threshold and / or the second threshold is 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, the uplink cancellation pattern is configured by RRC signaling.

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

[0286] Optionally, the time domain of the uplink cancellation pattern is a 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 cancellation pattern is a grid, and optionally, the grid has one cancellation resource element for every 2 resource elements or every 4 resource elements.

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

[0290] Fifth embodiment

[0291] Reference Figure 6 , Figure 6 This is a flow chart of a processing method according to a fifth embodiment of the present application. The processing method according to the embodiment of the present application can be applied to a network device (such as a base station), and includes the following steps:

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

[0293] This embodiment proposes a technical solution, which 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 information and the second information are provided by a network device.

[0295] Optionally, the network device may be a base station or a satellite, etc.

[0296] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0298] Optionally, the first information is carried in 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 grid.

[0302] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

[0304] Optionally, the terminal device enables or disables uplink cancellation resources based on the first information and the 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 by the second information;

[0306] If the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

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

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

[0309] Optionally, the first indication is represented by a 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 value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0314] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 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, the time domain resource allocation information is used to indicate the time domain resource allocation of the PUSCH.

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

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

[0321] Optionally, the downlink control information schedules multiple PUSCHs on a single cell.

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

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

[0324] Sixth embodiment

[0325] Reference Figure 7 , Figure 7 The sixth embodiment of the present application provides a processing method according to the sixth embodiment. The sixth embodiment of the present application provides a processing method, including the following steps:

[0326] S1: The network device sends first information and second information, so that the terminal device enables or disables uplink elimination resources based on the first information and the second information;

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

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

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

[0330] Optionally, the network device may be a base station or a satellite, etc.

[0331] Optionally, the first information is used to indicate whether uplink resource elimination is enabled or disabled.

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

[0333] Optionally, the first information is carried in 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 grid.

[0337] Optionally, the terminal device determines whether to enable uplink resource elimination based on an indication of the first information.

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

[0339] Optionally, the terminal device enables or disables uplink cancellation resources based on the first information and the 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 by the second information;

[0341] If the first information indicates to disable uplink resource elimination, the terminal device does not eliminate uplink resources for the currently scheduled PUSCH.

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

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

[0344] Optionally, the first indication is represented by a 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 value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0349] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 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 a newly added bit in the time domain resource allocation domain.

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

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

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

[0356] Optionally, the downlink control information schedules multiple PUSCHs on a single cell.

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

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

[0359] Seventh embodiment

[0360] See also Figure 8 , Figure 8 A schematic diagram of the structure of the processing device provided in the embodiment of the present application Figure 1 The device may be mounted on or be the terminal device in the above method embodiment, such as Figure 8 As shown, the processing device 160 includes:

[0361] The processing module 1601 is configured to enable or disable uplink cancellation resources based on the first information and the second information.

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

[0363] The first information is used to indicate whether uplink resource elimination is enabled or disabled;

[0364] The second information is used to configure uplink cancellation resources;

[0365] The first information is carried in the downlink control information;

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

[0367] The first information includes a first indication and / or time domain resource allocation information;

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

[0369] The second information includes a time domain symbol index and / or a frequency domain grid.

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

[0371] If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information;

[0372] If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

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

[0374] The first indication is used to indicate whether uplink resource elimination is enabled or disabled;

[0375] The time domain resource allocation information is used to indicate the time domain resource allocation of the 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 a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

[0379] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0380] Eighth embodiment

[0381] See also Fig. 9 , Fig. 9 A schematic diagram of the structure of the processing device provided in the embodiment of the present application Figure 2 The device may be mounted on or be the network device in the above method embodiment, such as Fig. 9 As shown, the device 170 includes:

[0382] The sending module 1701 is used to send the first information and the second information so that the terminal device enables or disables the uplink elimination resource based on the first information and the second information.

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

[0384] The first information is used to indicate whether uplink resource elimination is enabled or disabled;

[0385] The second information is used to configure uplink cancellation resources;

[0386] The first information is carried in the downlink control information;

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

[0388] The first information includes a first indication and / or time domain resource allocation information;

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

[0390] The second information includes a time domain symbol index and / or a frequency domain grid.

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

[0392] If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information;

[0393] If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

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

[0395] The first indication is used to indicate whether uplink resource elimination is enabled or disabled;

[0396] The time domain resource allocation information is used to indicate the time domain resource allocation of the 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 a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

[0400] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0401] See also Fig.10 , Fig.10 This is a schematic diagram of the structure of the communication device provided in the embodiment of the present application. Fig.10 As shown, the communication device 180 described in this embodiment can be the terminal device (or a component that can be used for the terminal device) or the network device (or a component that can be used for the network device) mentioned in the above method embodiment. The communication device 180 can be used to implement the method corresponding to the terminal device or the network device described in the above method embodiment, and specifically refer to the description in the above method embodiment.

[0402] The communication device 180 may include one or more processors 1801, which may also be referred to as a processing unit, and may implement certain control or processing functions. The processor 1801 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device, execute the software program, and process the data of the software program.

[0403] Optionally, the processor 1801 may also store instructions 1803 or data (eg, intermediate data). Optionally, the instructions 1803 may be executed by the processor 1801, so that the communication device 180 executes the method corresponding to the terminal device or network device described in the above method embodiment.

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

[0405] Optionally, the communication device 180 may include one or more memories 1802 , on which instructions 1804 may be stored. The instructions may be executed on the processor 1801 , so that the communication device 180 executes the method described in the above method embodiment.

[0406] Optionally, data may also be stored in the memory 1802. The processor 1801 and the memory 1802 may be provided separately or integrated together.

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

[0408] Optionally, if the communication device 180 is used to implement operations corresponding to the terminal device in the above-mentioned embodiments, for example, the transceiver 1805 can receive the first information and the second information; and the processor 1801 can 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 the transceiver 1805 can refer to the relevant description of the above embodiments, which will not be repeated here.

[0410] Optionally, if the communication device 180 is used to implement operations corresponding to the network devices in the above embodiments, for example: the first information and the second information may be sent by the transceiver 1805 .

[0411] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can refer to the relevant description of the above embodiments, which will not be repeated here.

[0412] The processor 1801 and the transceiver 1805 described in the present application can be implemented in an IC (Integrated Circuit), an analog integrated circuit, an RFIC (Radio Frequency Integrated Circuit), a mixed signal integrated circuit, an ASIC (Application Specific Integrated Circuit), a PCB (Printed Circuit Board), an electronic device, etc. The processor 1801 and the 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 may be a terminal device (such as a mobile phone) or a network device (such as a base station), which needs to be determined according to the context. In addition, the terminal device may be implemented in various forms. For example, the terminal device described in this application may include mobile terminals such as mobile phones, tablet computers, laptop computers, 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 in the above embodiments, the communication device is described by taking a terminal device or a network device as an example, the scope of the communication device described in the present application is not limited to the above terminal device or network device, and the structure of the communication device may not be limited to the above terminal device or network device. Fig.10 The communication device may be a stand-alone device or may be part of a larger device.

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

[0416] An embodiment of the present application also provides a communication device, including a memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.

[0417] The communication device in this application can be a terminal device (such as a mobile phone), a network device (such as a base station or a satellite), or a chip (such as a SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified based on the context.

[0418] An embodiment of the present application further provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

[0419] In the embodiments of the communication device and the storage medium provided in the embodiments of the present application, all the technical features of any of the above-mentioned processing method embodiments may be included, and the expansion and explanation content of the specification are basically the same as those of the embodiments of the above-mentioned methods, and will not be repeated here.

[0420] The embodiment of the present application further provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer executes the methods in the above various possible implementation modes.

[0421] An embodiment of the present 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 equipped with the chip executes the methods in various possible implementation modes as described above.

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

[0423] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

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

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

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

[0427] In the present application, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0428] The various technical features of the technical solution of the present application can be arbitrarily combined. In order to make the description concise, not all possible combinations of the various 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 description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as above, including a number of instructions for a terminal device (which can be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the method of each embodiment of the present application.

[0430] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a storage medium, or transmitted from one storage medium to another storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. 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 includes one or more available media integration. Available media can be magnetic media, (e.g., floppy disk, storage disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid-state storage disk Solid State Disk (SSD)), etc.

[0431] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A processing method, characterized in that: Applied to terminal equipment, including the steps of: S2: Enable or disable uplink cancellation resources based on the first information and the second information.

2. The method according to claim 1, characterized in that Also includes at least one of the following: The first information is used to indicate whether uplink resource elimination is enabled or disabled; The second information is used to configure uplink cancellation resources; The first information is carried in the downlink control information; The first information is configured by RRC signaling; The first information includes a first indication and / or time domain resource allocation information; The second information is carried in the RRC signaling; The second information includes a time domain symbol index and / or a frequency domain grid.

3. The method according to claim 2, characterized in that Step S2 includes at least one of the following: If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information; If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

4. The method according to claim 2 or 3, characterized in that: Also includes at least one of the following: The first indication is used to indicate whether uplink resource elimination is enabled or disabled; The time domain resource allocation information is used to indicate the time domain resource allocation of the PUSCH; The first indication is represented by a first parameter and / or by a field of downlink control information; The first indication is represented by the first bit in the time domain resource allocation field of the downlink control information; The time domain resource allocation information includes at least one of a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

5. A processing method, characterized in that: Applied to network equipment, including the steps of: S1: Send first information and second information to enable the terminal device to enable or disable uplink elimination resources based on the first information and the second information.

6. The method according to claim 5, characterized in that Also includes at least one of the following: The first information is used to indicate whether uplink resource elimination is enabled or disabled; The second information is used to configure uplink cancellation resources; The first information is carried in the downlink control information; The first information is configured by RRC signaling; The first information includes a first indication and / or time domain resource allocation information; The second information is carried in the RRC signaling; The second information includes a time domain symbol index and / or a frequency domain grid.

7. The method according to claim 6, characterized in that The terminal device enables or disables uplink cancellation resources based on the first information and the second information, including at least one of the following: If the first information indicates that uplink resource cancellation is enabled, uplink resource cancellation is performed on the currently scheduled PUSCH according to the uplink resource cancellation configured by the second information; If the first information indicates disabling of uplink resource cancellation, uplink resource cancellation is not performed on the currently scheduled PUSCH.

8. The method according to claim 6 or 7, characterized in that: Also includes at least one of the following: The first indication is used to indicate whether uplink resource elimination is enabled or disabled; The time domain resource allocation information is used to indicate the time domain resource allocation of the PUSCH; The first indication is represented by a first parameter and / or by a field of downlink control information; The first indication is represented by the first bit in the time domain resource allocation field of the downlink control information; The time domain resource allocation information includes at least one of a mapping type of a PUSCH scheduled by downlink control information, a time slot interval offset between the downlink control information and the scheduled PUSCH, and a start symbol and duration of the PUSCH scheduled by downlink control information.

9. A communication device, characterized in that: include: A memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the processing method according to any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processing method according to any one of claims 1 to 8 is implemented.

Images