Processing method, communication device, and storage medium

Abstract

This application describes a processing method, a communication device, and a storage medium. The method includes: a terminal device processes the deactivation of uplink resources based on an indication from initial information. The technical solution described in this application, in a gNB-to-gNB CLI scenario with SBFD, refines the processing mechanism for deactivating uplink resources and facilitates a further improvement in uplink transmission performance.

Description

Processing method, communication device and storage medium Technical Field

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

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

[0003] During the process of conceiving and implementing the present application, the inventors discovered that there are at least the following problems: if uplink cancellation resources are always statically enabled, the uplink cancellation resources will collide with the DMRS (Demodulation Reference Signal), and / or uplink resource cancellation will be performed where it is not necessary, which will lead to a decrease in uplink transmission performance. Therefore, the processing mechanism of the existing protocol for uplink cancellation resources is not perfect enough.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical Solutions

[0005] The main purpose of this application is to provide a processing method, communication device, and storage medium to improve the processing mechanism of uplink resource cancellation in the SBFD gNB-to-gNB CLI scenario, thereby supporting improved uplink transmission performance.

[0006] This application provides a processing method that can be applied to a terminal device (such as a mobile phone), comprising the steps of:

[0007] S2: Process uplink cancellation resources based on the instruction of the first information.

[0008] Optionally, the first information is carried in downlink control information or configured by RRC signaling, or includes a first indication and / or time domain resource allocation information.

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

[0010] Determining uplink resource cancellation enabling based on an indication of the first information;

[0011] Determining whether to disable uplink cancellation resources is based on an indication of the first information.

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

[0013] The first indication is used to indicate whether to enable or disable uplink resource cancellation;

[0014] The time domain resource allocation information is used to indicate the time domain resource allocation of PUSCH;

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

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

[0017] 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.

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

[0019] The first bit is the highest bit and / or a newly added bit in the time domain resource allocation field;

[0020] The first parameter is located in PUSCH-TimeDomainResourceAllocation;

[0021] The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16;

[0022] The first parameter is located in PUSCH-Allocation-r16.

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

[0024] The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32;

[0025] The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128;

[0026] DCI schedules a single PUSCH on a single cell;

[0027] DCI schedules multiple PUSCHs on a single cell;

[0028] DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

[0029] 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:

[0030] S1: Send the first information so that the terminal device processes the uplink elimination resources based on the instruction of the first information.

[0031] Optionally, the first information is carried in downlink control information or configured by RRC signaling, or includes a first indication and / or time domain resource allocation information; and / or the terminal device processes uplink elimination resources based on the indication of the first information, including at least one of the following:

[0032] The terminal device determines, based on an indication of the first information, whether uplink resource cancellation is enabled;

[0033] The terminal device determines to disable uplink elimination resources based on the indication of the first information.

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

[0035] The first indication is used to indicate whether to enable or disable uplink resource cancellation;

[0036] The time domain resource allocation information is used to indicate the time domain resource allocation of PUSCH;

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

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

[0039] 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.

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

[0041] The first bit is the highest bit and / or a newly added bit in the time domain resource allocation field;

[0042] The first parameter is located in PUSCH-TimeDomainResourceAllocation;

[0043] The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16;

[0044] The first parameter is located in PUSCH-Allocation-r16.

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

[0046] The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32;

[0047] The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128;

[0048] DCI schedules a single PUSCH on a single cell;

[0049] DCI schedules multiple PUSCHs on a single cell;

[0050] DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

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

[0052] A processing module is used to process uplink cancellation resources based on the indication of the first information.

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

[0054] The sending module is used to send the first information so that the terminal device processes the uplink elimination resources based on the indication of the first information.

[0055] 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 above-described processing methods when executed by the processor.

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

[0057] 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.

[0058] In the technical solution of the present application, the terminal device determines the uplink cancellation resources based on the indication of the first information, thereby improving the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used 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 following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0060] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0061] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0062] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0063] FIG4 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0064] FIG5 is a schematic flow chart of a processing method according to the first embodiment of the present application;

[0065] FIG6 is a schematic flow chart of a processing method according to a fifth embodiment of the present application;

[0066] FIG7 is a schematic diagram of the interaction flow between a network device and a terminal device illustrating a processing method according to a sixth embodiment of the present application;

[0067] FIG8 is a first structural diagram of a processing device provided in an embodiment of the present application;

[0068] FIG9 is a second structural diagram of a processing device provided in an embodiment of the present application;

[0069] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.

[0070] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0071] Implementation Methods of the Application

[0072] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0073] It should be noted that, in this document, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also 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 presence of other identical elements in the process, method, article or device comprising 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.

[0074] It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning 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 occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0075] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple 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 at least a portion of other steps or sub-steps or stages of other steps.

[0076] 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 the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0077] 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 restriction 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.

[0078] 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.

[0079] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0080] 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 chip (such as an SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified according to the context.

[0081] 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, and other fixed terminal devices such as digital TVs and desktop computers.

[0082] The subsequent description will be made using a mobile terminal as an example. Those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminal devices.

[0083] Please refer to 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 components such as an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0084] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0085] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and / or other components. Furthermore, the RF unit 101 can communicate with the network and other devices via 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.

[0086] WiFi is a short-range wireless transmission technology. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0087] The audio output unit 103 can convert 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, or the like. Furthermore, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.

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

[0089] 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 recognize 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 be configured in the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described here.

[0090] 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.

[0091] The user input unit 107 can be used to receive input digital or character information and generate key signal input related to 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 user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any other suitable object or accessory on or near the touch panel 1071) and drive corresponding connected devices 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 direction and detects the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 110. It can also receive and execute commands sent by the processor 110. And / or, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may 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, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0092] Optionally, the touch panel 1071 may overlay 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. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0093] 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.

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

[0095] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0096] 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 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0097] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0098] 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.

[0099] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an NR (New Radio) system of universal mobile communication technology. The NR system includes UE (User Equipment) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core) 203 and the operator's IP service 204, which are connected in sequence.

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

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

[0102] EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. MME 2031 is optionally a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management. HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores 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, and it selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

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

[0104] Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but can also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., which are not limited here.

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

[0106] 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.

[0107] Figure 4 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0108] 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.

[0109] The integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0110] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, 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 the computer program instructions are loaded and executed 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 device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. 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 integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive solid state disk, SSD), etc.

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

[0112] Technical terms involved in this embodiment:

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

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

[0115] UL resource muting: Uplink resource muting, uplink resource elimination;

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

[0117] SBFD: SubBand Full-Duplex.

[0118] First embodiment

[0119] 5 , which is a flow chart of a processing method according to a 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:

[0120] S2: The terminal device processes uplink elimination resources based on the instruction of the first information.

[0121] This embodiment takes into account that in existing protocols, uplink cancellation resources can only be statically enabled or disabled through RRC (Radio Resource Control) in SBFD (Sub-Band Full Duplex) gNB-to-gNB CLI (Base Station Cross-Link Interference) scenarios. If uplink cancellation resources are statically enabled, they may collide with DMRS (Demodulation Reference Signal) signals and / or cause unnecessary uplink resource cancellation, which can degrade uplink transmission performance.

[0122] Therefore, this embodiment proposes a technical solution, in which the terminal device processes uplink cancellation resources based on the indication of the first information, which can improve the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0123] Optionally, the first information is provided by a network device.

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

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

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

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

[0128] Optionally, the terminal device determines or processes the uplink cancellation resource based on an indication of the first information, including at least one of the following:

[0129] The terminal device determines, based on an indication of the first information, whether uplink resource cancellation is enabled;

[0130] The terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0131] Therefore, the terminal device determines the uplink elimination resource enabling and / or disabling based on the indication of the first information, and can improve the uplink elimination resource processing mechanism in the SBFD gNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

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

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

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

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

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

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

[0138] Optionally, the value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0139] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128.

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

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

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

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

[0144] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

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

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

[0148] Through the technical solution of this embodiment, the terminal device determines the uplink cancellation resources based on the indication of the first information, thereby improving the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0149] Second embodiment

[0150] On the basis of the first embodiment of the present application, this embodiment further describes a method for a terminal device to process uplink elimination resources based on an indication of the first information in combination with a scenario.

[0151] This embodiment proposes a technical solution in which the terminal device processes uplink cancellation resources based on the indication of the first information. This can improve the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting improved uplink transmission performance.

[0152] Optionally, the first information is provided by a network device.

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

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

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

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

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

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

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

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

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

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

[0163] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

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

[0166] Optionally, a Time Domain Resource Assignment (TDRA) field in the 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.

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

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

[0169] 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.

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

[0171] Optionally, the time domain resource allocation table configured by RRC signaling is shown in Table 1. Optionally, the start symbol position S and the continuation symbol length L are jointly determined by the SLIV (Start and Length Indicator Value) value indicated by startSymbolAndLength.

[0172] Table 1. Time domain resource allocation table

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

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

[0175] 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.

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

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

[0178] Optionally, the time domain of the uplink cancellation pattern is a symbol index.

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

[0180] Optionally, the frequency domain of the uplink cancellation pattern is a grid, and optionally, the grid has one cancellation resource element every 2 resource elements or every 4 resource elements.

[0181] Through the technical solution of this embodiment, the terminal device determines the uplink cancellation resource based on the indication of the first information. For example, a first parameter is added to the PUSCH-TimeDomainResourceAllocation to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH. This improves the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, clearly indicates how to dynamically enable or disable uplink cancellation resources, and thus supports improving uplink transmission performance.

[0182] Third embodiment

[0183] On the basis of any of the above embodiments of the present application, this embodiment further describes a method for a terminal device to process uplink elimination resources based on an indication of the first information in combination with a scenario.

[0184] This embodiment proposes a technical solution in which the terminal device processes uplink cancellation resources based on the indication of the first information. This can improve the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting improved uplink transmission performance.

[0185] Optionally, the first information is provided by a network device.

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

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

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

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

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

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

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

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

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

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

[0196] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

[0198] 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.

[0199] 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.

[0200] 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 PUSCH time domain resource position indicated by the DCI.

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

[0202] Optionally, as shown in the time domain resource allocation table of the RRC signaling configuration 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.

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

[0204] 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 to disable uplink cancellation, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

[0205] 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.

[0206] 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. If the indication is to disable uplink cancellation or this parameter is not configured, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

[0207] Optionally, if the first parameter indicates that uplink cancellation is enabled, the terminal device performs uplink cancellation on all PUSCHs currently scheduled by the DCI according to the configured uplink cancellation pattern; and / or, if the indication indicates 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.

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

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

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

[0211] Optionally, the time domain of the uplink cancellation pattern is a symbol index.

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

[0213] Optionally, the frequency domain of the uplink cancellation pattern is a grid, and optionally, the grid has one cancellation resource element every 2 resource elements or every 4 resource elements.

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

[0215] 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 in the time domain resource allocation table of the RRC configuration shown in Table 3; and / or, if the indication is to disable uplink cancellation or this parameter is not configured, the terminal device does not need to perform uplink cancellation on the currently scheduled PUSCH.

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

[0217] Through the technical solution of this embodiment, the terminal device determines the uplink cancellation resource based on the indication of the first information. For example, a first parameter is added to PUSCH-TimeDomainResourceAllocation-r16 to indicate whether uplink cancellation is enabled in the currently scheduled PUSCH. This improves the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, clearly indicates how to dynamically enable or disable uplink cancellation resources, and thus supports improving uplink transmission performance.

[0218] Fourth embodiment

[0219] On the basis of any of the above embodiments of the present application, this embodiment further describes a method for a terminal device to process uplink elimination resources based on an indication of the first information in combination with a scenario.

[0220] This embodiment proposes a technical solution in which the terminal device processes uplink cancellation resources based on the indication of the first information. This can improve the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting improved uplink transmission performance.

[0221] Optionally, the first information is provided by a network device.

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

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

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

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

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

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

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

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

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

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

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

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

[0234] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

[0236] Optionally, the Time Domain Resource 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.

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

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

[0239] Optionally, a row of the time domain resource allocation table contains information on the mapping type of the DCI-scheduled PUSCH, the time slot interval offset 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.

[0240] Optionally, mapping types A and B are also commonly referred to as slot-based scheduling, mini-slot-based or non-slot-based 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 continuation symbol length L are jointly determined by the SLIV value indicated by startSymbolAndLength.

[0241] Optionally, one 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.

[0242] 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; and / or, 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.

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

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

[0245] Optionally, the 1 bit is the least significant bit in the Time Domain Resource Assignment field.

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

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

[0248] Optionally, if the 1 bit is a newly added 1 bit, the Time Domain Resource Assignment field is bits, where I TDRAConfigure the number of rows in the time domain resource allocation table for RRC common signaling or user-specific signaling.

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

[0250] Optionally, if the SLIV value is less than the first threshold, the terminal device enables uplink elimination.

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

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

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

[0254] Optionally, the value of the first threshold and / or the second threshold is configured by RRC signaling.

[0255] Optionally, the SLIV value is configured by RRC signaling. Optionally, the SLIV value is indicated by the Time Domain Resource Assignment field in the DCI.

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

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

[0258] Optionally, the time domain of the uplink cancellation pattern is a symbol index.

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

[0260] Optionally, the frequency domain of the uplink cancellation pattern is a grid, and optionally, the grid has one cancellation resource element every 2 resource elements or every 4 resource elements.

[0261] Through the technical solution of this embodiment, the terminal device determines the uplink cancellation resource based on the indication of the first information, and indicates whether uplink cancellation is enabled in the currently scheduled PUSCH through one bit in the Time Domain Resource Assignment field in the DCI (format 0_0, 0_1, 0_2). Therefore, in the SBFD gNB-to-gNB CLI scenario, the processing mechanism of uplink cancellation resources is improved, and it is clearly indicated how to dynamically enable or disable uplink cancellation resources, thereby supporting the improvement of uplink transmission performance.

[0262] Fifth embodiment

[0263] 6 , which is a flowchart 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:

[0264] S1: The network device sends a first message so that the terminal device processes uplink elimination resources based on an instruction of the first message.

[0265] This embodiment proposes a technical solution to improve the processing mechanism of uplink cancellation resources, thereby supporting the improvement of uplink transmission performance.

[0266] Optionally, the first information is provided by a network device.

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

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

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

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

[0271] Optionally, the terminal device determines or processes the uplink cancellation resource based on an indication of the first information, including at least one of the following:

[0272] The terminal device determines, based on an indication of the first information, whether uplink resource cancellation is enabled;

[0273] The terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0274] Therefore, the terminal device determines the uplink elimination resource enabling and / or disabling based on the indication of the first information, and can improve the uplink elimination resource processing mechanism in the SBFD gNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

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

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

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

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

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

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

[0281] Optionally, the value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0282] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128.

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

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

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

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

[0287] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

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

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

[0291] Through the technical solution of this embodiment, the network device sends the first information so that the terminal device determines the uplink cancellation resource based on the indication of the first information, thereby improving the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0292] Sixth embodiment

[0293] 7 , which is a schematic diagram of an interaction flow between a network device and a terminal device according to a processing method according to a sixth embodiment, the sixth embodiment of the present application proposes a processing method, comprising the steps of:

[0294] S1: The network device sends first information so that the terminal device determines uplink cancellation resources based on an indication of the first information;

[0295] S2: The terminal device determines the uplink cancellation resource based on the indication of the first information.

[0296] This embodiment proposes a technical solution in which the terminal device processes uplink cancellation resources based on the indication of the first information. This can improve the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting improved uplink transmission performance.

[0297] Optionally, the first information is provided by a network device.

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

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

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

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

[0302] Optionally, the terminal device determines or processes the uplink cancellation resource based on an indication of the first information, including at least one of the following:

[0303] The terminal device determines, based on an indication of the first information, whether uplink resource cancellation is enabled;

[0304] The terminal device determines to disable uplink elimination resources based on the indication of the first information.

[0305] Therefore, the terminal device determines the uplink elimination resource enabling and / or disabling based on the indication of the first information, and can improve the uplink elimination resource processing mechanism in the SBFD gNB-to-gNB CLI scenario, realize the dynamic enabling or disabling of uplink elimination resources, and thus support the improvement of uplink transmission performance.

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

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

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

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

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

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

[0312] Optionally, the value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32.

[0313] Optionally, the value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128.

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

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

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

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

[0318] Optionally, the time domain resource allocation information includes at least one of a mapping type of the PUSCH scheduled by the 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 the downlink control information.

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

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

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

[0322] Through the technical solution of this embodiment, the network device sends the first information, and the terminal device determines the uplink cancellation resource based on the indication of the first information, thereby improving the processing mechanism of uplink cancellation resources in the SBFD gNB-to-gNB CLI scenario, thereby supporting the improvement of uplink transmission performance.

[0323] Seventh embodiment

[0324] Please refer to FIG8 , which is a structural diagram of a processing device according to an embodiment of the present application. The device may be mounted on or be the terminal device in the above method embodiment. As shown in FIG8 , the processing device 160 includes:

[0325] The processing module 1601 is configured to process uplink cancellation resources based on an instruction of the first information.

[0326] Optionally, the first information is carried in downlink control information or configured by RRC signaling, or includes a first indication and / or time domain resource allocation information.

[0327] Optionally, processing uplink cancellation resources based on an instruction of the first information includes at least one of the following:

[0328] Determining uplink resource cancellation enabling based on an indication of the first information;

[0329] Determining whether to disable uplink cancellation resources is based on an indication of the first information.

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

[0331] The first indication is used to indicate whether to enable or disable uplink resource cancellation;

[0332] The time domain resource allocation information is used to indicate the time domain resource allocation of PUSCH;

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

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

[0335] 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.

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

[0337] The first bit is the highest bit and / or a newly added bit in the time domain resource allocation field;

[0338] The first parameter is located in PUSCH-TimeDomainResourceAllocation;

[0339] The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16;

[0340] The first parameter is located in PUSCH-Allocation-r16.

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

[0342] The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32;

[0343] The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128;

[0344] DCI schedules a single PUSCH on a single cell;

[0345] DCI schedules multiple PUSCHs on a single cell;

[0346] DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

[0347] 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.

[0348] Eighth embodiment

[0349] Please refer to FIG. 9 , which is a second structural diagram of a processing device provided in an embodiment of the present application. The device may be mounted on or be the network device in the above method embodiment. As shown in FIG. 9 , the device 170 includes:

[0350] The sending module 1701 is used to send the first information so that the terminal device processes the uplink elimination resources based on the indication of the first information.

[0351] Optionally, the first information is carried in downlink control information or configured by RRC signaling, or includes a first indication and / or time domain resource allocation information.

[0352] Optionally, the terminal device processes uplink cancellation resources based on an instruction of the first information, including at least one of the following:

[0353] The terminal device determines, based on an indication of the first information, whether uplink resource cancellation is enabled;

[0354] The terminal device determines to disable uplink elimination resources based on the indication of the first information.

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

[0356] The first indication is used to indicate whether to enable or disable uplink resource cancellation;

[0357] The time domain resource allocation information is used to indicate the time domain resource allocation of PUSCH;

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

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

[0360] 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.

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

[0362] The first bit is the highest bit and / or a newly added bit in the time domain resource allocation field;

[0363] The first parameter is located in PUSCH-TimeDomainResourceAllocation;

[0364] The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16;

[0365] The first parameter is located in PUSCH-Allocation-r16.

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

[0367] The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32;

[0368] The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128;

[0369] DCI schedules a single PUSCH on a single cell;

[0370] DCI schedules multiple PUSCHs on a single cell;

[0371] DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

[0372] 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.

[0373] Refer to Figure 10, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 10, the communication device 180 described in this embodiment can be the terminal device (or component that can be used for a terminal device) or network device (or component that can be used for a network device) mentioned in the aforementioned method embodiment. The communication device 180 can be used to implement the methods corresponding to the terminal device or network device described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

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

[0375] 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.

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

[0377] 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 performs the method described in the above method embodiment.

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

[0379] 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, core network device, or wireless access network device). The transceiver 1805 may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, and is used to implement the transceiver functions of the communication device 180.

[0380] Optionally, if the communication device 180 is used to implement operations corresponding to the terminal device in the above embodiments, for example, the transceiver 1805 can receive the first information; and the processor 1801 can process the uplink elimination resources based on the indication of the first information.

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

[0382] 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 may be sent by the transceiver 1805 .

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

[0384] The processor 1801 and transceiver 1805 described in this application can be implemented on 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 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.

[0385] In this application, a communication device may be a terminal device (such as a mobile phone) or a network device (such as a base station), and the specific definition needs to be determined based on the context. In addition, the terminal device can be implemented in various forms. For example, the terminal devices 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.

[0386] Although the communication device is described above by taking a terminal device or a network device as an example, the scope of the communication device described in this application is not limited to the above-mentioned terminal device or network device, and the structure of the communication device may not be limited to Figure 10. The communication device may be an independent device or may be part of a larger device.

[0387] 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.

[0388] 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.

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

[0390] 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.

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

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

[0393] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

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

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

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

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

[0398] In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail 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 this application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous relevant detailed descriptions.

[0399] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0400] The various technical features of the technical solution of this application can be combined arbitrarily. 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 this application.

[0401] 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 the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially 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, magnetic disk, optical disk) as above, and includes a number of instructions for enabling 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.

[0402] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, 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 the computer program instructions are loaded and executed 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 device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0403] The above are only preferred embodiments of the present application and do not 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, wherein: Applied to terminal equipment, including the steps of: S2: Process uplink elimination resources based on the instruction of the first information.

2. The method according to claim 1, wherein: The first information is carried in the downlink control information or configured by RRC signaling, or includes the first indication and / or time domain resource allocation information; and / or, step S2 includes at least one of the following: Determine uplink resource cancellation enabling based on the indication of the first information; Determine whether to disable uplink cancellation resources based on an indication of the first information.

3. The method according to claim 2, wherein: 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.

4. The method according to claim 3, wherein: Also includes at least one of the following: The first bit is the highest bit and / or the newly added bit in the time domain resource allocation domain; The first parameter is located in PUSCH-TimeDomainResourceAllocation; The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16; The first parameter is located in PUSCH-Allocation-r16.

5. The method according to claim 4, wherein: Also includes at least one of the following: The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32; The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128; DCI schedules a single PUSCH on a single cell; DCI schedules multiple PUSCHs on a single cell; DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

6. A processing method, wherein: Applied to network equipment, including the steps of: S1: Send the first information so that the terminal device processes the uplink elimination resources based on the instruction of the first information.

7. The method according to claim 6, wherein: The first information is carried in the downlink control information or configured by RRC signaling, or includes the first indication and / or time domain resource allocation information; and / or the terminal device processes the uplink elimination resource based on the indication of the first information, including at least one of the following: The terminal device determines, based on the indication of the first information, whether uplink resource cancellation is enabled; The terminal device determines to disable uplink elimination resources based on the indication of the first information.

8. The method according to claim 7, wherein: 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. The method according to claim 8, wherein: Also includes at least one of the following: The first bit is the highest bit and / or the newly added bit in the time domain resource allocation domain; The first parameter is located in PUSCH-TimeDomainResourceAllocation; The first parameter is located in PUSCH-TimeDomainResourceAllocation-r16; The first parameter is located in PUSCH-Allocation-r16.

10. The method according to claim 9, wherein: Also includes at least one of the following: The value of the parameter maxNrofUL-Allocations in PUSCH-TimeDomainResourceAllocation is 32; The value of the parameter maxNrofUL-Allocations-r16 in PUSCH-TimeDomainResourceAllocation-r16 is 128; DCI schedules a single PUSCH on a single cell; DCI schedules multiple PUSCHs on a single cell; DCI schedules multiple PUSCHs on multiple cells, and each cell schedules a single PUSCH.

11. A communication device, wherein: 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 claim 1 or 6 is implemented.

12. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processing method according to claim 1 or 6 is implemented.