Processing method, communication device, and storage medium

Abstract

Disclosed in the present application are a processing method, a communication device, and a storage medium. The method comprises: a terminal device determining a time-domain position of an uplink channel repetition transmission on the basis of first information. The technical solution of the present application can optimize a transmission mechanism for a PUSCH repetition transmission type B.

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, there is only one configuration for repeated transmission type B of a PUSCH (Physical Uplink Shared Channel) within a cell.

[0003] During the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] In SBFD (Subband Full-Duplex) scenarios, the receive antenna configuration of network devices (such as gNBs) may differ between SBFD and non-SBFD symbols, and / or the interference experienced by the received signals may differ. Transmitting PUSCH repetition type B in both SBFD and non-SBFD symbols will degrade the reception performance of network devices. Therefore, it is necessary to optimize the transmission mechanism for PUSCH repetition type B.

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

[0006] The main purpose of this application is to provide a processing method, a communication device and a storage medium, aiming to optimize the transmission mechanism of PUSCH repeated transmission type B.

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

[0008] S2: Determine a time domain position for repeated transmission of the uplink channel based on the first information.

[0009] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

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

[0011] The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel;

[0012] The number of repetitions is used to indicate the number of repetitions of uplink channel transmission;

[0013] The symbol type includes at least one of the following:

[0014] Sub-band full-duplex symbol;

[0015] Non-subband full-duplex symbols;

[0016] downlink symbol;

[0017] Uplink symbols;

[0018] Flexible symbols.

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

[0020] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0021] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0022] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0023] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0024] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0025] If an uplink channel nominal retransmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule;

[0026] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0027] If the symbol mapped first in an uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped later is an SBFD symbol, the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0028] If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission;

[0029] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0030] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols.

[0031] Optionally, the first rule includes at least one of the following:

[0032] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0033] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0034] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0035] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0036] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0037] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0038] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0039] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

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

[0041] The actual repetition transmission supports transmission on both SBFD and non-SBFD symbols:

[0042] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0043] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0044] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0045] The actual repeated transmission uses the transmission power of the SBFD part;

[0046] The actual retransmission uses the uplink spatial domain filter of the SBFD part;

[0047] During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

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

[0049] S1, sending first information so that the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0050] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

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

[0052] The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel;

[0053] The number of repetitions is used to indicate the number of repetitions of uplink channel transmission;

[0054] The symbol type includes at least one of the following:

[0055] Sub-band full-duplex symbol;

[0056] Non-subband full-duplex symbols;

[0057] downlink symbol;

[0058] Uplink symbols;

[0059] Flexible symbols.

[0060] Optionally, the terminal device determines, according to the first information, a time domain position for repeated transmission of the uplink channel, including at least one of the following:

[0061] The terminal device determines the time domain position of a nominal repetition transmission of the uplink channel according to the time domain indication information and the number of repetitions;

[0062] The terminal device determines the time domain position of the actual repeated transmission based on the time domain position of the nominal repeated transmission of the uplink channel, as well as the valid symbols and / or invalid symbols.

[0063] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0064] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0065] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0066] If an uplink channel nominal retransmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule;

[0067] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0068] If the symbol mapped first in an uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped later is an SBFD symbol, the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0069] If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission;

[0070] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0071] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols.

[0072] Optionally, the first rule includes at least one of the following:

[0073] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0074] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0075] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0076] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0077] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0078] Optionally, the terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols, including at least one of the following:

[0079] The terminal device determines the time domain position of the actual repeated transmission within a time slot according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols;

[0080] The terminal device determines a continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols within a time slot, and determines a time domain position of an actual repeated transmission based on the continuous set.

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

[0082] The actual repetition transmission supports transmission on both SBFD and non-SBFD symbols:

[0083] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0084] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0085] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0086] The actual repeated transmission uses the transmission power of the SBFD part;

[0087] The actual retransmission uses the uplink spatial domain filter of the SBFD part;

[0088] During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

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

[0090] The determination module is configured to determine a time domain position for repeated transmission of an uplink channel based on the first information.

[0091] The present application also provides a processing device, wherein the device comprises:

[0092] The sending module is used to send the first information so that the terminal device determines the time domain position of the repeated transmission of the uplink channel based on the first information.

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

[0094] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified in the context.

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

[0096] In the technical solution of the present application, the terminal device determines the time domain position of the uplink channel repeated transmission based on the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0103] FIG6 is a schematic diagram of PUSCH repetition type B transmission according to the third embodiment of the present application;

[0104] FIG7 is a schematic diagram of PUSCH repetition type B transmission according to the fourth embodiment of the present application;

[0105] FIG8 is a schematic flow chart of a processing method according to a sixth embodiment of the present application;

[0106] FIG9 is a schematic diagram of the interaction flow between a network device and a terminal device according to a processing method according to a seventh embodiment of the present application;

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

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

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

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

[0111] Implementation Methods of the Application

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

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

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

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

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

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

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

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

[0120] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified based on the context.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0142] 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).

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

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

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

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

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

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

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

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

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

[0152] Technical terms involved in this embodiment:

[0153] PUSCH: Physical Uplink Shared Channel, physical uplink shared channel;

[0154] SBFD: Subband Full-Duplex, subband full-duplex;

[0155] non-SBFD: non-sub-band full-duplex;

[0156] PUSCH repetition type B: Physical uplink shared channel repetition type B.

[0157] First embodiment

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

[0159] S2: The terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0160] This embodiment is primarily targeted at SBFD (Sub-Band Full Duplex) scenarios. This embodiment takes into account that the receive antenna configurations of network devices (such as gNBs) may differ between SBFD and non-SBFD symbols, and / or the interference experienced by the received signals may differ. Therefore, if PUSCH repetition transmission type B is transmitted in both SBFD and non-SBFD symbols, the reception performance of the network device will be affected.

[0161] Therefore, this embodiment proposes a solution to optimize the transmission mechanism of PUSCH repetition transmission type B, clarify the effective time domain position of PUSCH repetition transmission type B, and improve the receiving performance of network devices.

[0162] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0163] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0164] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0165] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0166] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0167] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value of m indicates row m+1 of the resource allocation table. Optionally, the resource allocation table includes at least one of a time slot offset Ks, a starting position and length indicator SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, a number of time slots for determining a TBS, and a repetition count.

[0168] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0169] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0170] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0171] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0172] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0173] Optionally, the symbol type includes at least one of a subband full duplex (SBFD) symbol, a non-subband full duplex (non-SBFD) symbol, a downlink (DL) symbol, an uplink (UL) symbol, and a flexible (FL) symbol.

[0174] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0175] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0176] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0177] Optionally, the sub-band full-duplex symbols and the non-sub-band full-duplex symbols are indicated by RRC signaling.

[0178] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0179] Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0180] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0181] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0182] Optionally, as a first implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0183] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0184] Determining valid symbols and / or invalid symbols according to a time domain position and symbol type of a nominal repeated transmission of an uplink channel;

[0185] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0186] Optionally, as a second implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0187] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0188] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0189] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0190] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0191] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0192] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0193] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0194] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0195] Optionally, if the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, determining one type of symbol as an invalid symbol and determining the other type of symbol as a valid symbol includes at least one of the following:

[0196] Optionally, if one uplink channel nominal repeated transmission includes SBFD symbols and non-SBFD symbols, the symbols corresponding to the symbol type mapped previously are valid symbols, and the symbols corresponding to the symbol type mapped later are invalid symbols.

[0197] Optionally, if the symbol mapped first in one uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0198] Optionally, if the symbol mapped first in one uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped second is a SBFD symbol, then the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0199] Optionally, if one uplink channel nominal repeated transmission includes SBFD symbols and non-SBFD symbols, the symbols corresponding to the symbol type mapped previously are invalid symbols, and the symbols corresponding to the symbol type mapped later are valid symbols.

[0200] Optionally, if the symbol mapped first in one uplink channel nominal repeated transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, the SBFD symbol is an invalid symbol and the non-SBFD symbol is a valid symbol.

[0201] Optionally, if the symbol mapped first in one uplink channel nominal repeated transmission is a non-SBFD symbol and the symbol mapped later is a SBFD symbol, the non-SBFD symbol is an invalid symbol and the SBFD symbol is a valid symbol.

[0202] Optionally, if an uplink channel nominal retransmission includes SBFD symbols and non-SBFD symbols respectively, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols contained in the transmission, and the remaining symbols of the uplink channel nominal retransmission are valid symbols.

[0203] Optionally, if an uplink channel nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, and the number of SBFD symbols contained in an uplink channel nominal repetition transmission is greater than or equal to the number of non-SBFD symbols contained in an uplink channel nominal repetition transmission, then the non-SBFD symbols are invalid symbols and the SBFD symbols are valid symbols.

[0204] Optionally, if an uplink channel nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, and the number of SBFD symbols included in an uplink channel nominal repetition transmission is less than the number of non-SBFD symbols included in an uplink channel nominal repetition transmission, then the SBFD symbols are invalid symbols and the non-SBFD symbols are valid symbols.

[0205] Optionally, if an uplink channel nominal retransmission includes SBFD symbols and non-SBFD symbols respectively, one type of symbol is determined to be an invalid symbol based on the larger of the number of SBFD symbols and the number of non-SBFD symbols contained in the transmission, and the remaining symbols of the uplink channel nominal retransmission are valid symbols.

[0206] Optionally, if an uplink channel nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, and the number of SBFD symbols contained in an uplink channel nominal repetition transmission is greater than or equal to the number of non-SBFD symbols contained in an uplink channel nominal repetition transmission, then the SBFD symbols are invalid symbols and the non-SBFD symbols are valid symbols.

[0207] Optionally, if an uplink channel nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, and the number of SBFD symbols included in an uplink channel nominal repetition transmission is less than the number of non-SBFD symbols included in an uplink channel nominal repetition transmission, then the non-SBFD symbols are invalid symbols and the SBFD symbols are valid symbols.

[0208] Optionally, the first rule includes at least one of the following:

[0209] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0210] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0211] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0212] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0213] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0214] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0215] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0216] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

[0217] Through the technical solution of this embodiment, the terminal device determines the time domain position of the uplink channel repeated transmission according to the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0218] Second embodiment

[0219] Based on the first embodiment of the present application, a second embodiment of the present application is proposed. This embodiment mainly explains how to select a processing method for configuration parameters if PUSCH repetition transmission type B is transmitted on SBFD symbols and non-SBFD symbols respectively.

[0220] Optionally, in this embodiment, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0221] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0222] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0223] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0224] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0225] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value m indicates row m+1 of the resource allocation table.

[0226] Optionally, the resource allocation table includes at least one of a time slot offset Ks, a starting position and length indication SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, and a number of time slots for determining a TBS, a number of repetitions, and the like.

[0227] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0228] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0229] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0230] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0231] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0232] Optionally, the symbol type includes at least one of: a sub-band full-duplex symbol, a non-sub-band full-duplex symbol, a downlink symbol, an uplink symbol, and a flexible symbol.

[0233] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0234] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0235] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0236] Optionally, the sub-band full-duplex symbol and the non-sub-band full-duplex symbol are indicated by RRC signaling. Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0237] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0238] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0239] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0240] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include at least one of the following:

[0241] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0242] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0243] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0244] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0245] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

[0246] Optionally, the actual retransmission is PUSCH retransmission type B.

[0247] Optionally, PUSCH repetition transmission type B is transmitted on SBFD symbols and non-SBFD symbols respectively.

[0248] Optionally, if PUSCH repetition transmission type B is transmitted on SBFD symbols and non-SBFD symbols respectively, at least one of the following configuration parameters is selected:

[0249] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0250] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0251] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0252] The actual repeated transmission uses the frequency resources of the SBFD part;

[0253] The actual repeated transmission uses the transmission power of the SBFD part;

[0254] The actual retransmission uses the uplink spatial domain filter of the SBFD part.

[0255] Optionally, the actual repetitive transmission is not stopped during the transition period or gap between SBFD symbols and non-SBFD symbols.

[0256] Optionally, the SBFD part of the actual repeated transmission refers to a part of the actual repeated transmission mapped onto the SBFD symbol.

[0257] Optionally, the non-SBFD part of the actual repeated transmission refers to a part of the actual repeated transmission mapped to a non-SBFD symbol.

[0258] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resource parameters, where the frequency resource parameters include frequency domain position, number of resource blocks, frequency hopping parameters, and the like.

[0259] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmission power parameters, where the uplink transmission power parameters include open-loop power parameters, closed-loop power parameters, and the like.

[0260] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter, and the uplink spatial domain filter is indicated by a reference signal.

[0261] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the transmission power of the SBFD part.

[0262] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the frequency resources of the SBFD part.

[0263] Optionally, the SBFD part and the non-SBFD part that are actually repeatedly transmitted use an uplink spatial domain filter of the SBFD part.

[0264] Through the technical solution of this embodiment, the terminal device determines the time domain position of the uplink channel repeated transmission based on the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B. Among them, if the actual repeated transmission is transmitted on SBFD symbols and non-SBFD symbols respectively, the terminal device selects the corresponding configuration parameters to avoid affecting the receiving performance of the network device.

[0265] Third embodiment

[0266] Based on any of the above embodiments of the present application, a third embodiment of the present application is proposed. This embodiment mainly describes a processing method for the case where PUSCH repeated transmission does not support simultaneous transmission on SBFD symbols and non-SBFD symbols.

[0267] This embodiment mainly targets SBFD (sub-band full duplex) scenarios, optimizes the transmission mechanism of PUSCH repeated transmission type B, clarifies the effective time domain position of PUSCH repeated transmission type B, and improves the receiving performance of network devices.

[0268] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0269] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0270] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0271] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0272] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0273] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value m indicates row m+1 of the resource allocation table.

[0274] Optionally, the resource allocation table includes at least one of a time slot offset Ks, a starting position and length indication SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, and a number of time slots for determining a TBS, a number of repetitions, and the like.

[0275] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0276] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0277] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0278] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0279] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0280] Optionally, the symbol type includes at least one of a subband full duplex (SBFD) symbol, a non-subband full duplex (non-SBFD) symbol, a downlink (DL) symbol, an uplink (UL) symbol, and a flexible (FL) symbol.

[0281] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0282] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0283] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0284] Optionally, the sub-band full-duplex symbol and the non-sub-band full-duplex symbol are indicated by RRC signaling. Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0285] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0286] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0287] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0288] Optionally, the terminal device determining the time domain position of repeated transmission of the uplink channel based on the first information may include:

[0289] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0290] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0291] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0292] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0293] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0294] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0295] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0296] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0297] Optionally, the first rule includes at least one of the following:

[0298] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0299] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0300] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0301] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0302] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0303] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0304] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

[0305] The following describes the solution of this embodiment in combination with the following scenarios:

[0306] Optionally, for PUSCH repetition type B transmission, the number of nominal repetition transmissions is determined by a parameter numberOfRepetitions, where for the nth nominal repetition transmission, n=0, ..., numberOfRepetitions-1.

[0307] Optionally, the time slot at which the nth PUSCH nominal retransmission starts is The starting symbol is the symbol of this time slot

[0308] Optionally, the time slot at which the nth PUSCH nominal retransmission ends is The ending symbol is the symbol of this time slot

[0309] Optionally, K s is the time slot where PUSCH transmission starts, is the number of symbols contained in a time slot. S is the symbol at which PUSCH transmission starts in the time slot, and L is the number of consecutively allocated symbols, starting from symbol S.

[0310] Optionally, if a PUSCH nominal retransmission includes only non-SBFD symbols, whether it is an invalid symbol is determined according to the following rules:

[0311] Symbols denoted as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in PUSCH repetition type B transmission;

[0312] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in PUSCH repetition type B transmission;

[0313] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in PUSCH repetition type B transmission;

[0314] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, then in PUSCH repetition type B transmission, in each group of consecutive symbols of all symbols represented as downlink in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are considered invalid symbols.

[0315] Optionally, the symbols given by numberOfInvalidSymbolsForDL-UL-Switching are defined using the reference SCS configuration referenceSubcarrierSpacing provided in tdd-UL-DL-ConfigurationCommon.

[0316] Optionally, if a PUSCH nominal retransmission includes only SBFD symbols, these symbols are considered as valid symbols.

[0317] Optionally, if a PUSCH nominal repetition transmission includes only SBFD symbols, and the PUSCH nominal repetition falls into an uplink subband in the frequency domain, these symbols are considered to be valid symbols.

[0318] Optionally, if a PUSCH nominal repetition transmission includes only SBFD symbols, and the PUSCH nominal repetition falls outside the uplink subband in the frequency domain, these symbols are considered as invalid symbols.

[0319] Optionally, if a PUSCH nominal retransmission includes SBFD symbols and non-SBFD symbols, one type of symbol is considered as an invalid symbol, for example, the symbol type sent first is considered as a valid symbol, and the symbol type sent later is considered as an invalid symbol.

[0320] Optionally, in a PUSCH nominal repetition transmission, the symbol mapped first is an SBFD symbol and the symbol mapped later is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol.

[0321] Optionally, in a PUSCH nominal repetition transmission, the symbols mapped first are non-SBFD symbols and the symbols mapped later are SBFD symbols, then the non-SBFD symbols are valid symbols and the SBFD symbols are invalid symbols.

[0322] Optionally, if a PUSCH nominal retransmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is considered as an invalid symbol, for example, the symbol type sent later is considered as a valid symbol, and the symbol type sent earlier is considered as an invalid symbol.

[0323] Optionally, in a PUSCH nominal repetition transmission, the symbol mapped first is an SBFD symbol and the symbol mapped later is a non-SBFD symbol, then the SBFD symbol is an invalid symbol and the non-SBFD symbol is a valid symbol.

[0324] Optionally, in a PUSCH nominal repetition transmission, the symbol mapped first is a non-SBFD symbol and the symbol mapped later is a SBFD symbol, then the non-SBFD symbol is an invalid symbol and the SBFD symbol is a valid symbol.

[0325] Optionally, if a PUSCH nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, one type of symbol is determined as an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols contained in the transmission, and the remaining symbols are valid symbols.

[0326] Optionally, if the number of SBFD symbols included in the transmission is greater than or equal to the number of non-SBFD symbols, the non-SBFD symbols are invalid symbols and the SBFD symbols are valid symbols.

[0327] Optionally, if the number of SBFD symbols included in the transmission is less than the number of non-SBFD symbols, the SBFD symbols are invalid symbols and the non-SBFD symbols are valid symbols.

[0328] Optionally, if a PUSCH nominal repetition transmission includes SBFD symbols and non-SBFD symbols respectively, one type of symbol is determined as an invalid symbol based on the larger of the number of SBFD symbols and the number of non-SBFD symbols contained in the transmission, and the remaining symbols are valid symbols.

[0329] Optionally, if the number of SBFD symbols included in the transmission is greater than or equal to the number of non-SBFD symbols, the non-SBFD symbols are valid symbols and the SBFD symbols are invalid symbols.

[0330] Optionally, if the number of SBFD symbols included in the transmission is less than the number of non-SBFD symbols, the SBFD symbols are valid symbols and the non-SBFD symbols are invalid symbols.

[0331] Optionally, for PUSCH repetition type B transmission, after determining invalid symbols for PUSCH repetition type B transmission for each of the K nominal repetition transmissions, the remaining symbols are considered as potential valid symbols for PUSCH repetition type B transmission.

[0332] Optionally, if the number of potentially valid symbols for PUSCH repetition type B transmission in one nominal repetition transmission is greater than zero, then one nominal repetition transmission consists of one or more actual repetition transmissions, and optionally, each actual repetition transmission consists of a contiguous set of all potentially valid symbols that can be used for PUSCH repetition type B transmission in one time slot. Except for the case of L=1, actual repetitions with a single symbol are omitted.

[0333] Optionally, the terminal device should repeat the transmission block (TB) in the actual repeated transmission.

[0334] Optionally, the redundancy version to be applied to the nth actual repetition (the count includes omitted actual repetitions) is determined according to Table 1 below (where N=1).

[0335] Table 1: Redundancy version for PUSCH transmission

[0336] Optionally, PUSCH repetition type B transmission may be as shown in FIG6 .

[0337] Through the technical solution of this embodiment, the terminal device determines the time domain position of the uplink channel repeated transmission according to the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0338] Fourth embodiment

[0339] Based on any of the above embodiments, the fourth embodiment of the present application is proposed. This embodiment mainly describes the processing method for PUSCH repeated transmission that does not support simultaneous transmission on SBFD symbols and non-SBFD symbols (the actual repeated transmission only includes one symbol type).

[0340] This embodiment mainly targets SBFD (sub-band full duplex) scenarios, optimizes the transmission mechanism of PUSCH repeated transmission type B, clarifies the effective time domain position of PUSCH repeated transmission type B, and improves the receiving performance of network devices.

[0341] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0342] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0343] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0344] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0345] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0346] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value of m indicates row m+1 of the resource allocation table. The resource allocation table includes at least one of a time slot offset Ks, a starting position and length indicator SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, a time slot number for determining a TBS, and a repetition count.

[0347] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0348] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0349] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0350] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0351] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0352] Optionally, the symbol type includes at least one of a subband full duplex (SBFD) symbol, a non-subband full duplex (non-SBFD) symbol, a downlink (DL) symbol, an uplink (UL) symbol, and a flexible (FL) symbol.

[0353] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0354] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0355] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0356] Optionally, the sub-band full-duplex symbol and the non-sub-band full-duplex symbol are indicated by RRC signaling. Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0357] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0358] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0359] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0360] Optionally, the terminal device determining the time domain position of repeated transmission of the uplink channel based on the first information may include:

[0361] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0362] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0363] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0364] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0365] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0366] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0367] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0368] Optionally, the first rule includes at least one of the following:

[0369] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0370] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0371] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0372] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0373] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0374] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0375] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

[0376] The following describes the solution of this embodiment in combination with the following scenarios:

[0377] Optionally, the actual repeated transmission includes only one symbol type.

[0378] Optionally, a PUSCH repetition transmission does not support transmission on SBFD symbols and non-SBFD symbols respectively.

[0379] Optionally, for PUSCH repetition type B transmission, the number of nominal repetition transmissions is determined by a parameter numberOfRepetitions, where for the nth nominal repetition transmission, n=0, ..., numberOfRepetitions-1.

[0380] Optionally, the time slot at which the nth PUSCH nominal retransmission starts is The starting symbol is the symbol of this time slot

[0381] Optionally, the time slot at which the nth PUSCH nominal retransmission ends is The ending symbol is the symbol of this time slot

[0382] Optionally, K s is the time slot where PUSCH transmission starts, is the number of symbols contained in a time slot. S is the symbol at which PUSCH transmission starts in the time slot, and L is the number of consecutively allocated symbols, starting from symbol S.

[0383] Optionally, determine whether it is an invalid symbol according to the following rules:

[0384] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in PUSCH repetition type B transmissions;

[0385] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in PUSCH repetition type B transmission;

[0386] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in PUSCH repetition type B transmission;

[0387] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, then in PUSCH repetition type B transmission, in each group of consecutive symbols of all symbols represented as downlink in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are considered invalid symbols.

[0388] Optionally, the symbols given by numberOfInvalidSymbolsForDL-UL-Switching are defined using the reference SCS configuration referenceSubcarrierSpacing provided in tdd-UL-DL-ConfigurationCommon.

[0389] Optionally, for PUSCH repetition type B transmission, after determining invalid symbols for PUSCH repetition type B transmission for each of the K nominal repetition transmissions, the remaining symbols are considered as potential valid symbols for PUSCH repetition type B transmission.

[0390] Optionally, if the number of potentially valid symbols for PUSCH repetition type B transmission in a nominal repetition transmission is greater than zero, then a nominal repetition transmission consists of one or more actual repetition transmissions, where an actual repetition transmission is limited to symbols of the same type. Optionally, each actual repetition transmission consists of a contiguous set of all potentially valid symbols of the same type that can be used for PUSCH repetition type B transmission in a time slot. Except for the case where L = 1, actual repetitions with a single symbol are omitted.

[0391] Optionally, if a nominal repetition transmission includes SBFD symbols and non-SBFD symbols, then the nominal repetition transmission can be divided into m actual repetition transmissions, where each actual repetition transmission is continuous in the time domain, i.e., mapped to continuous symbols. Optionally, each actual repetition transmission does not cross a time slot boundary in the time domain, i.e., the symbols included in the actual repetition transmission belong to the same time slot.

[0392] Optionally, each actual repetition transmission includes only one symbol type, that is, one actual repetition transmission is mapped to consecutive SBFD symbols, or one actual repetition transmission is mapped to consecutive non-SBFD symbols.

[0393] Optionally, the terminal device should repeat the transport block (TB) in the actual repeated transmission. The redundancy version to be applied to the nth actual repetition (the count includes omitted actual repetitions) is determined according to Table 1 above (where N=1).

[0394] Optionally, PUSCH repetition type B transmission may be as shown in FIG. 7 .

[0395] Through the technical solution of this embodiment, the terminal device determines the time domain position of the uplink channel repeated transmission according to the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0396] Fifth embodiment

[0397] Based on any of the above embodiments, the fifth embodiment of the present application is proposed. This embodiment mainly describes a processing method for PUSCH repeated transmission supporting simultaneous transmission on SBFD symbols and non-SBFD symbols.

[0398] This embodiment mainly targets SBFD (sub-band full duplex) scenarios, optimizes the transmission mechanism of PUSCH repeated transmission type B, clarifies the effective time domain position of PUSCH repeated transmission type B, and improves the receiving performance of network devices.

[0399] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0400] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0401] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0402] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0403] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0404] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value of m indicates row m+1 of the resource allocation table. The resource allocation table includes at least one of a time slot offset Ks, a starting position and length indicator SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, a time slot number for determining a TBS, and a repetition count.

[0405] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0406] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0407] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0408] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0409] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0410] Optionally, the symbol type includes at least one of a subband full duplex (SBFD) symbol, a non-subband full duplex (non-SBFD) symbol, a downlink (DL) symbol, an uplink (UL) symbol, and a flexible (FL) symbol.

[0411] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0412] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0413] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0414] Optionally, the sub-band full-duplex symbol and the non-sub-band full-duplex symbol are indicated by RRC signaling. Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0415] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0416] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0417] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0418] Optionally, the terminal device determining the time domain position of repeated transmission of the uplink channel based on the first information may include:

[0419] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0420] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0421] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0422] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0423] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0424] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0425] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0426] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0427] Optionally, the first rule includes at least one of the following:

[0428] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0429] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0430] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0431] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0432] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0433] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0434] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0435] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

[0436] The following describes the solution of this embodiment in combination with the following scenarios:

[0437] Optionally, PUSCH repetition transmission supports simultaneous transmission on SBFD symbols and non-SBFD symbols.

[0438] Optionally, for PUSCH repetition type B transmission, the number of nominal repetition transmissions is determined by a parameter numberOfRepetitions, where for the nth nominal repetition transmission, n=0, ..., numberOfRepetitions-1.

[0439] Optionally, the time slot at which the nth PUSCH nominal retransmission starts is The starting symbol is the symbol of this time slot

[0440] Optionally, the time slot at which the nth PUSCH nominal retransmission ends is The ending symbol is the symbol of this time slot

[0441] Optionally, K s is the time slot where PUSCH transmission starts, is the number of symbols contained in a time slot. S is the symbol at which PUSCH transmission starts in the time slot, and L is the number of consecutively allocated symbols, starting from symbol S.

[0442] Optionally, determine whether it is an invalid symbol according to the following rules:

[0443] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in PUSCH repetition type B transmissions;

[0444] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in PUSCH repetition type B transmission;

[0445] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in PUSCH repetition type B transmission;

[0446] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, then in PUSCH repetition type B transmission, in each group of consecutive symbols of all symbols represented as downlink in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are considered invalid symbols.

[0447] The symbols given by numberOfInvalidSymbolsForDL-UL-Switching are defined using the reference SCS configuration referenceSubcarrierSpacing provided in tdd-UL-DL-ConfigurationCommon.

[0448] Optionally, for PUSCH repetition type B transmission, after determining invalid symbols for PUSCH repetition type B transmission for each of the K nominal repetition transmissions, the remaining symbols are considered as potential valid symbols for PUSCH repetition type B transmission.

[0449] Optionally, if the number of potentially valid symbols for PUSCH repetition type B transmission in one nominal repetition transmission is greater than zero, then one nominal repetition transmission consists of one or more actual repetition transmissions, and optionally, each actual repetition transmission consists of a contiguous set of all potentially valid symbols that can be used for PUSCH repetition type B transmission in one time slot. Except for the case of L=1, actual repetitions with a single symbol are omitted.

[0450] Optionally, the terminal device should repeat the TB in the actual repeated transmission. The redundancy version to be applied to the nth actual repetition (the count includes omitted actual repetitions) is determined according to Table 1 above (where N=1).

[0451] Optionally, if PUSCH repetition transmission type B is transmitted simultaneously in SBFD symbols and non-SBFD symbols, at least one of the following configuration parameters is selected:

[0452] The SBFD part and the non-SBFD part of the PUSCH actual repeated transmission use the same frequency resources;

[0453] The actual repeated transmission of PUSCH uses the frequency resources of the SBFD part;

[0454] The SBFD part and the non-SBFD part of the PUSCH actual repeated transmission use the same uplink transmit power;

[0455] The actual repeated transmission of PUSCH uses the transmit power of the SBFD part;

[0456] The SBFD part and the non-SBFD part of the PUSCH actual repeated transmission use the same uplink spatial domain filter;

[0457] The actual repeated transmission of PUSCH uses the uplink spatial domain filter of the SBFD part.

[0458] Optionally, the actual repetitive transmission is not stopped during the transition period or gap between SBFD symbols and non-SBFD symbols.

[0459] Optionally, the SBFD part of the actual repeated transmission refers to a part of the actual repeated transmission mapped onto the SBFD symbol.

[0460] Optionally, the non-SBFD part of the actual repeated transmission refers to a part of the actual repeated transmission mapped to a non-SBFD symbol.

[0461] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resource parameters, where the frequency resource parameters include frequency domain position, number of resource blocks, frequency hopping parameters, and the like.

[0462] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmission power parameters, where the uplink transmission power parameters include open-loop power parameters, closed-loop power parameters, and the like.

[0463] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter, and the uplink spatial domain filter is indicated by a reference signal.

[0464] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the transmission power of the SBFD part.

[0465] Optionally, the SBFD part and the non-SBFD part of the actual repeated transmission use the frequency resources of the SBFD part.

[0466] Optionally, the SBFD part and the non-SBFD part that are actually repeatedly transmitted use an uplink spatial domain filter of the SBFD part.

[0467] Through the technical solution of this embodiment, the terminal device determines the time domain position of the uplink channel repeated transmission according to the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0468] Sixth embodiment

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

[0470] S1: The network device sends first information so that the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0471] This embodiment is primarily targeted at SBFD (Sub-Band Full Duplex) scenarios. This embodiment takes into account that the receive antenna configurations of network devices (such as gNBs) may differ between SBFD and non-SBFD symbols, and / or the interference experienced by the received signals may differ. Therefore, if PUSCH repetition transmission type B is transmitted in both SBFD and non-SBFD symbols, the reception performance of the network device will be affected.

[0472] Therefore, this embodiment proposes a solution to optimize the transmission mechanism of PUSCH repetition transmission type B, clarify the effective time domain position of PUSCH repetition transmission type B, and improve the receiving performance of network devices.

[0473] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0474] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0475] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0476] Optionally, the time domain information is carried in downlink control information (DCI). For example, the time domain information is a "Time domain resource assignment" field in the downlink control information.

[0477] Optionally, the time domain information is used to indicate the time slot offset Ks, the starting position and length indication SLIV, the start symbol S and the allocation length L, the PUSCH mapping type, and is used to determine at least one of the number of time slots of the TBS, the number of repetitions, etc.

[0478] Optionally, the time domain information is used to indicate a resource allocation table. For example, a time domain information value of m indicates row m+1 of the resource allocation table. The resource allocation table includes at least one of a time slot offset Ks, a starting position and length indicator SLIV, a start symbol S and an allocation length L, a PUSCH mapping type, a time slot number for determining a TBS, and a repetition count.

[0479] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0480] Optionally, the number of repetitions is indicated by a higher-level parameter, which is RRC signaling, for example, the higher-level parameter is "numberOfRepetitions".

[0481] Optionally, the number of repetitions is indicated by a higher-level parameter, which is a MAC CE.

[0482] Optionally, the number of repetitions is indicated by control information, and the control information is downlink control information (DCI).

[0483] Optionally, the number of repetitions is predefined and indicated by some elements in the resource allocation table.

[0484] Optionally, the symbol type includes at least one of a subband full duplex (SBFD) symbol, a non-subband full duplex (non-SBFD) symbol, a downlink (DL) symbol, an uplink (UL) symbol, and a flexible (FL) symbol.

[0485] Optionally, the symbol type is indicated by a higher-level parameter, and the higher-level parameter is RRC signaling.

[0486] Optionally, the downlink symbols, uplink symbols, and flexible symbols are indicated by RRC signaling "tdd-UL-DL-ConfigurationCommon" and / or "tdd-UL-DL-ConfigurationDedicated".

[0487] Optionally, downlink symbols, uplink symbols, and flexible symbols are indicated by downlink control information DCI 2_0.

[0488] Optionally, the sub-band full-duplex symbols and the non-sub-band full-duplex symbols are indicated by RRC signaling.

[0489] Optionally, the symbol where the sub-band full-duplex symbol is located is a downlink symbol and / or a flexible symbol.

[0490] Optionally, the sub-band full-duplex symbol is a periodic symbol.

[0491] Optionally, the downlink symbols and / or flexible symbols configured as sub-band full-duplex symbols include uplink sub-bands in the frequency domain, and the uplink sub-bands can be used for the terminal to transmit uplink channels and / or uplink signals.

[0492] Optionally, the non-subband full-duplex symbol is defined relative to the sub-band full-duplex symbol, that is, the non-subband full-duplex symbol is at least one of a downlink symbol, an uplink symbol, and a flexible symbol.

[0493] Optionally, as a first implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0494] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0495] Determining valid symbols and / or invalid symbols according to a time domain position and symbol type of a nominal repeated transmission of an uplink channel;

[0496] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0497] Optionally, as a second implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0498] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0499] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0500] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0501] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0502] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0503] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0504] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0505] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0506] Optionally, if the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, determining one type of symbol as an invalid symbol and determining the other type of symbol as a valid symbol includes at least one of the following:

[0507] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0508] Optionally, if the symbol mapped first in one uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped second is a SBFD symbol, then the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0509] Optionally, if an uplink channel nominal repeated transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission.

[0510] Optionally, the first rule includes at least one of the following:

[0511] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0512] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0513] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0514] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0515] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0516] Optionally, the terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols, including at least one of the following:

[0517] The terminal device determines the time domain position of the actual repeated transmission within a time slot according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols;

[0518] The terminal device determines a continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols within a time slot, and determines a time domain position of an actual repeated transmission based on the continuous set.

[0519] Optionally, the actual retransmission is PUSCH retransmission type B.

[0520] Optionally, PUSCH repetition transmission type B is transmitted simultaneously in SBFD symbols and non-SBFD symbols.

[0521] Optionally, if PUSCH repetition transmission type B is transmitted simultaneously in SBFD symbols and non-SBFD symbols, the terminal device adopts at least one of the following selection configuration parameters:

[0522] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0523] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0524] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0525] The actual repeated transmission uses the transmission power of the SBFD part;

[0526] The actual retransmission uses the uplink spatial domain filter of the SBFD part.

[0527] Optionally, the terminal device does not stop the actual repetitive transmission during the transition period or gap between the SBFD symbols and the non-SBFD symbols.

[0528] Through the technical solution of this embodiment, the network device sends the first information so that the terminal device determines the time domain position of the uplink channel repeated transmission according to the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0529] Seventh embodiment

[0530] 9 , 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 seventh embodiment, the seventh embodiment of the present application proposes a processing method, comprising the steps of:

[0531] S1: The network device sends first information so that the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information;

[0532] S2: The terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0533] This embodiment is primarily targeted at SBFD (Sub-Band Full Duplex) scenarios. This embodiment takes into account that the receive antenna configurations of network devices (such as gNBs) may differ between SBFD and non-SBFD symbols, and / or the interference experienced by the received signals may differ. Therefore, if PUSCH repetition transmission type B is transmitted in both SBFD and non-SBFD symbols, the reception performance of the network device will be affected.

[0534] Therefore, this embodiment proposes a solution to optimize the transmission mechanism of PUSCH repetition transmission type B, clarify the effective time domain position of PUSCH repetition transmission type B, and improve the receiving performance of network devices.

[0535] Optionally, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0536] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

[0537] Optionally, the time domain indication information is used to indicate a time domain position of repeated transmission of the uplink channel.

[0538] Optionally, the number of repetitions is used to indicate the number of repetitions of repeated transmission of the uplink channel.

[0539] Optionally, the symbol type includes at least one of: a sub-band full-duplex symbol, a non-sub-band full-duplex symbol, a downlink symbol, an uplink symbol, and a flexible symbol.

[0540] Optionally, as a first implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0541] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0542] Determining valid symbols and / or invalid symbols according to a time domain position and symbol type of a nominal repeated transmission of an uplink channel;

[0543] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0544] Optionally, as a second implementation solution, the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information, which may include:

[0545] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0546] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0547] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0548] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0549] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0550] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0551] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols;

[0552] If one uplink channel nominal retransmission includes only non-SBFD symbols, it is determined whether the non-SBFD symbols are invalid symbols according to the first rule.

[0553] Optionally, if the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, determining one type of symbol as an invalid symbol and determining the other type of symbol as a valid symbol includes at least one of the following:

[0554] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0555] Optionally, if the symbol mapped first in one uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped second is a SBFD symbol, then the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0556] Optionally, if an uplink channel nominal repeated transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission.

[0557] Optionally, the first rule includes at least one of the following:

[0558] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0559] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0560] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0561] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0562] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0563] Optionally, the terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols, including at least one of the following:

[0564] The terminal device determines the time domain position of the actual repeated transmission within a time slot according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols;

[0565] The terminal device determines a continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols within a time slot, and determines a time domain position of an actual repeated transmission based on the continuous set.

[0566] Optionally, the actual retransmission is PUSCH retransmission type B.

[0567] Optionally, PUSCH repetition transmission type B is transmitted simultaneously in SBFD symbols and non-SBFD symbols.

[0568] Optionally, if PUSCH repetition transmission type B is transmitted simultaneously in SBFD symbols and non-SBFD symbols, the terminal device adopts at least one of the following selection configuration parameters:

[0569] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0570] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0571] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0572] The actual repeated transmission uses the transmission power of the SBFD part;

[0573] The actual retransmission uses the uplink spatial domain filter of the SBFD part.

[0574] Optionally, the terminal device does not stop the actual repetitive transmission during the transition period or gap between the SBFD symbols and the non-SBFD symbols.

[0575] Through the technical solution of this embodiment, the network device sends the first information, and the terminal device determines the time domain position of the uplink channel repeated transmission based on the first information, thereby optimizing the transmission mechanism of PUSCH repeated transmission type B.

[0576] Eighth embodiment

[0577] Please refer to Figure 10, which is a schematic diagram of the structure of the processing device provided in the embodiment of the present application. The device can be installed in or is the terminal device in the above method embodiment. As shown in Figure 10, the processing device 160 includes:

[0578] The determination module 1601 is configured to determine a time domain position for repeated transmission of an uplink channel based on the first information.

[0579] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

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

[0581] The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel;

[0582] The number of repetitions is used to indicate the number of repetitions of uplink channel transmission;

[0583] The symbol type includes at least one of the following:

[0584] Sub-band full-duplex symbol;

[0585] Non-subband full-duplex symbols;

[0586] downlink symbol;

[0587] Uplink symbols;

[0588] Flexible symbols.

[0589] Optionally, determining a time domain position for repeated transmission of an uplink channel based on the first information includes at least one of the following:

[0590] Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions;

[0591] The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

[0592] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0593] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0594] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0595] If an uplink channel nominal retransmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule;

[0596] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0597] If the symbol mapped first in an uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped later is an SBFD symbol, the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0598] If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission;

[0599] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0600] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols.

[0601] Optionally, the first rule includes at least one of the following:

[0602] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0603] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0604] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0605] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0606] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0607] Optionally, determining the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols includes at least one of the following:

[0608] Determining the time domain position of actual repeated transmission within a time slot according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols;

[0609] A continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols in a time slot is determined, and a time domain position of an actual repeated transmission is determined according to the continuous set.

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

[0611] The actual repetition transmission supports transmission on both SBFD and non-SBFD symbols:

[0612] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0613] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0614] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0615] The actual repeated transmission uses the transmission power of the SBFD part;

[0616] The actual retransmission uses the uplink spatial domain filter of the SBFD part;

[0617] During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

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

[0619] Please refer to Figure 11, which is a second structural diagram of a processing device provided in an embodiment of the present application. The device can be installed in or be the network device in the above method embodiment. As shown in Figure 11, the device 170 includes:

[0620] The sending module 1701 is used to send first information so that the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

[0621] Optionally, the first information includes: at least one of time domain indication information, number of repetitions and symbol type.

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

[0623] The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel;

[0624] The number of repetitions is used to indicate the number of repetitions of uplink channel transmission;

[0625] The symbol type includes at least one of the following:

[0626] Sub-band full-duplex symbol;

[0627] Non-subband full-duplex symbols;

[0628] downlink symbol;

[0629] Uplink symbols;

[0630] Flexible symbols.

[0631] Optionally, the terminal device determines, according to the first information, a time domain position for repeated transmission of the uplink channel, including at least one of the following:

[0632] The terminal device determines the time domain position of a nominal repetition transmission of the uplink channel according to the time domain indication information and the number of repetitions;

[0633] The terminal device determines the time domain position of the actual repeated transmission based on the time domain position of the nominal repeated transmission of the uplink channel, as well as the valid symbols and / or invalid symbols.

[0634] Optionally, a method for determining a valid symbol and / or an invalid symbol includes at least one of the following:

[0635] If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol;

[0636] If an uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols;

[0637] If an uplink channel nominal retransmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule;

[0638] If the symbol mapped first in an uplink channel nominal repetition transmission is an SBFD symbol and the symbol mapped second is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol;

[0639] If the symbol mapped first in an uplink channel nominal repetition transmission is a non-SBFD symbol and the symbol mapped later is an SBFD symbol, the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol;

[0640] If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission;

[0641] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink sub-band in the frequency domain, the SBFD symbols are determined to be valid symbols;

[0642] If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined to be invalid symbols.

[0643] Optionally, the first rule includes at least one of the following:

[0644] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission;

[0645] Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission;

[0646] For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission;

[0647] For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in uplink channel repetition type B transmission;

[0648] For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

[0649] Optionally, the terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols, including at least one of the following:

[0650] The terminal device determines the time domain position of the actual repeated transmission within a time slot according to the time domain position of the nominal repeated transmission of the uplink channel and the valid symbols and / or invalid symbols;

[0651] The terminal device determines a continuous set of all potential valid symbols belonging to nominal repeated transmission and the same type of symbols within a time slot, and determines a time domain position of an actual repeated transmission based on the continuous set.

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

[0653] The actual repetition transmission supports transmission on both SBFD and non-SBFD symbols:

[0654] The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources;

[0655] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmit power;

[0656] The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter;

[0657] The actual repeated transmission uses the transmission power of the SBFD part;

[0658] The actual retransmission uses the uplink spatial domain filter of the SBFD part;

[0659] During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

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

[0661] Refer to Figure 12, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 12, 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.

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

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

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

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

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

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

[0668] 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 determine the time domain position of the uplink channel repeated transmission based on the first information.

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

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

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

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

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

[0674] 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 12. The communication device may be an independent device or may be part of a larger device.

[0675] An embodiment of the present application further 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.

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

[0677] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified based on the context.

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

[0679] 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 expansion and explanation content of the specification are basically the same as those of the embodiments of the above-mentioned methods, and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

[0690] 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)).

[0691] 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: Determine the time domain position of repeated transmission of the uplink channel based on the first information.

2. The method according to claim 1, wherein: The first information includes at least one of the following: Time domain indication information; Number of repetitions; The symbol type.

3. The method according to claim 2, wherein: Also includes at least one of the following: The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel; The number of repetitions is used to indicate the number of repetitions of uplink channel retransmission; The symbol type includes at least one of the following: Sub-band full-duplex symbol; Non-subband full-duplex symbol; Downlink symbol; Uplink symbol; Flexible symbols.

4. The method according to claim 2, wherein: Step S2 includes at least one of the following: Determine a time domain position of a nominal repetition transmission of an uplink channel according to the time domain indication information and the number of repetitions; The time domain position of the actual repeated transmission is determined according to the time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols.

5. The method according to claim 4, wherein: The method for determining valid symbols and / or invalid symbols includes at least one of the following: If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol; If one uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols; If an uplink channel nominal repetition transmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule; If the symbol mapped before the nominal repetition transmission of an uplink channel is an SBFD symbol and the symbol mapped after is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol; If the symbol mapped before the nominal repetition transmission of an uplink channel is a non-SBFD symbol and the symbol mapped after is a SBFD symbol, then the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol; If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission; If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink subband in the frequency domain, the SBFD symbol is determined as a valid symbol; If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined as invalid symbols.

6. The method according to claim 5, wherein: The first rule includes at least one of the following: Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission; Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission; For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission; For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in the uplink channel repetition type B transmission; For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

7. The method according to claim 4, wherein: Determining the time domain position of actual repeated transmission according to a time domain position of a nominal repeated transmission of an uplink channel and valid symbols and / or invalid symbols includes at least one of the following: The time domain position of an actual repeated transmission in a time slot is determined based on the time domain position of a nominal repeated transmission of an uplink channel, as well as valid symbols and / or invalid symbols; a continuous set of all potential valid symbols belonging to the nominal repeated transmission and belonging to the same type of symbols in a time slot is determined, and the time domain position of an actual repeated transmission is determined based on the continuous set.

8. The method according to claim 4, wherein: Also includes at least one of the following: The actual repetitive transmission supports transmission on both SBFD symbols and non-SBFD symbols at the same time: The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources; The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmission power; The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter; The actual repeated transmission uses the transmission power of the SBFD part; The actual repetitive transmission uses the uplink spatial domain filter of the SBFD part; During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

9. A processing method, wherein: Applied to network equipment, including the steps of: S1: Send first information so that the terminal device determines the time domain position of repeated transmission of the uplink channel based on the first information.

10. The method according to claim 9, wherein: The first information includes at least one of the following: Time domain indication information; Number of repetitions; The symbol type.

11. The method according to claim 10, wherein: Also includes at least one of the following: The time domain indication information is used to indicate the time domain position of repeated transmission of the uplink channel; The number of repetitions is used to indicate the number of repetitions of uplink channel retransmission; The symbol type includes at least one of the following: Sub-band full-duplex symbol; Non-subband full-duplex symbol; Downlink symbol; Uplink symbol; Flexible symbols.

12. The method according to claim 10, wherein: The terminal device determines the time domain position of repeated transmission of the uplink channel according to the first information, including at least one of the following: The terminal device determines the time domain position of a nominal repetition transmission of the uplink channel according to the time domain indication information and the number of repetitions; The terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of an uplink channel, and the valid symbols and / or invalid symbols.

13. The method according to claim 12, wherein: The method for determining valid symbols and / or invalid symbols includes at least one of the following: If the time domain position of a nominal repetitive transmission of an uplink channel includes SBFD symbols and non-SBFD symbols, one type of symbol is determined as an invalid symbol, and the other type of symbol is determined as a valid symbol; If one uplink channel nominal repetition transmission includes only SBFD symbols, the SBFD symbols are determined as valid symbols; If an uplink channel nominal repetition transmission includes only non-SBFD symbols, determining whether the non-SBFD symbols are invalid symbols according to the first rule; If the symbol mapped before the nominal repetition transmission of an uplink channel is an SBFD symbol and the symbol mapped after is a non-SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol; If the symbol mapped before the nominal repetition transmission of an uplink channel is a non-SBFD symbol and the symbol mapped after is a SBFD symbol, then the non-SBFD symbol is a valid symbol and the SBFD symbol is an invalid symbol; If an uplink channel nominal repetitive transmission includes both SBFD symbols and non-SBFD symbols, one type of symbol is determined to be an invalid symbol based on the smaller of the number of SBFD symbols and the number of non-SBFD symbols included in the transmission; If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls into an uplink subband in the frequency domain, the SBFD symbol is determined as a valid symbol; If an uplink channel nominal repetition transmission includes only SBFD symbols, and the uplink channel nominal repetition falls outside the uplink sub-band in the frequency domain, the SBFD symbols are determined as invalid symbols.

14. The method according to claim 13, wherein: The first rule includes at least one of the following: Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols in uplink channel repetition type B transmission; Symbols indicated as downlink using tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and not configured as SBFD are considered invalid symbols in uplink channel repetition type B transmission; For the TDD band, the symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigurationCommon for receiving SS / PBCH blocks are considered invalid symbols in uplink channel repetition type B transmission; For the TDD band, the symbols indicated by the CORESET for Type0-PDCCH CSS set in the MIB pdcch-ConfigSIB1 are considered invalid symbols in the uplink channel repetition type B transmission; For the TDD band, if numberOfInvalidSymbolsForDL-UL-Switching is configured, when the uplink channel repeats type B transmission, in each group of consecutive symbols represented by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as all downlink symbols, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the last symbol are regarded as invalid symbols.

15. The method according to claim 12, wherein: The terminal device determines the time domain position of the actual repeated transmission according to the time domain position of the nominal repeated transmission of the uplink channel, and the valid symbol and / or the invalid symbol, including at least one of the following: The terminal equipment determines the time domain position of the actual repeated transmission within a time slot according to the time domain position of the nominal repeated transmission of an uplink channel, and the valid symbol and / or invalid symbol; The terminal device determines a continuous set of all potential valid symbols belonging to the same type of symbols and belonging to nominal repeated transmission within a time slot, and determines a time domain position of an actual repeated transmission according to the continuous set.

16. The method according to claim 12, wherein: Also includes at least one of the following: The actual repetitive transmission supports transmission on both SBFD symbols and non-SBFD symbols at the same time: The SBFD part and the non-SBFD part of the actual repeated transmission use the same frequency resources; The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink transmission power; The SBFD part and the non-SBFD part of the actual repeated transmission use the same uplink spatial domain filter; The actual repeated transmission uses the transmission power of the SBFD part; The actual repetitive transmission uses the uplink spatial domain filter of the SBFD part; During the transition period or gap between SBFD symbols and non-SBFD symbols, the actual repetitive transmission is not stopped.

17. A communication device, wherein: include: A memory and a processor, wherein a processing program is stored in the memory, and the processing program is executed by the processor to implement the processing method according to claim 1 or 9.

18. A computer-readable storage medium, wherein: The computer-readable storage medium stores a processing program, and the processing program is executed by a processor to implement the processing method according to claim 1 or 9.

Images