Processing method and device, equipment and readable storage medium
By receiving signaling by the terminal and dynamically adjusting the SBFD configuration, the problem of undetermined transmission processing details when dynamically adjusting SBFD is solved, and dynamic resource matching and service transmission performance are improved.
Patent Information
- Application Number
- CN202311409438.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-26
- Publication Date
- 2025-04-29
AI Technical Summary
When or after dynamically adjusting the full duplex SBFD configuration of subbands, the transmission processing details have not been determined yet, affecting the actual deployment.
The terminal receives signaling from the network-side device, dynamically adjusts the SBFD configuration, and performs processing operations of target uplink transmission or downlink reception according to the signaling.
Ensure the feasibility of dynamic SBFD, enables available resources to dynamically match business needs, and improves service transmission performance.
Smart Images

Figure CN119907115A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a processing method, an apparatus, a device and a readable storage medium. Background Art
[0002] The network side can dynamically adjust the Sub-Band Full Duplex (SBFD) configuration through signaling. The details of transmission processing during or after dynamic adjustment of SBFD (Dynamic SBFD) have not yet been determined, which affects the actual deployment of Dynamic SBFD. Summary of the invention
[0003] The embodiments of the present application provide a processing method, an apparatus, a device, and a readable storage medium, which can solve the problem that the transmission processing details during or after dynamic adjustment of SBFD have not yet been determined.
[0004] In a first aspect, a processing method is provided, comprising:
[0005] The terminal receives a first signaling from a network side device;
[0006] The terminal performs a processing operation of target uplink transmission or a processing operation of target downlink reception according to the first signaling;
[0007] The first signaling is used to dynamically adjust the sub-band full-duplex SBFD configuration.
[0008] In a second aspect, a processing method is provided, comprising:
[0009] The network side device sends a first signaling to the terminal;
[0010] The network side device determines, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal;
[0011] The network side device performs a corresponding receiving operation or sending operation according to a processing operation of a target uplink transmission or a processing operation of a target downlink reception of the terminal;
[0012] The first signaling is used to dynamically adjust the SBFD configuration.
[0013] In a third aspect, a processing device is provided, comprising:
[0014] A first receiving module, used for a terminal to receive a first signaling from a network side device;
[0015] A first execution module, configured for the terminal to execute a processing operation of a target uplink transmission or a processing operation of a target downlink reception according to the first signaling;
[0016] The first signaling is used to dynamically adjust the SBFD configuration.
[0017] In a fourth aspect, a processing device is provided, comprising:
[0018] A sending module, used for a network side device to send a first signaling to a terminal;
[0019] A determination module, configured for the network side device to determine, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal;
[0020] A second execution module, configured for the network side device to perform a corresponding receiving operation or sending operation according to a processing operation of a target uplink transmission or a processing operation of a target downlink reception of the terminal;
[0021] The first signaling is used to dynamically adjust the SBFD configuration.
[0022] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
[0023] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used for the terminal to receive a first signaling from a network side device, and the processor is used for the terminal to perform a processing operation of a target uplink transmission or a processing operation of a target downlink reception according to the first signaling; wherein the first signaling is used to dynamically adjust the SBFD configuration.
[0024] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.
[0025] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used for the network side device to send a first signaling to a terminal, and the processor is used for the network side device to determine, according to the first signaling, a processing operation for a target uplink transmission or a processing operation for a target downlink reception of the terminal; the processor is used for the network side device to perform a corresponding receiving operation or a sending operation according to the processing operation for the target uplink transmission or the processing operation for the target downlink reception of the terminal; wherein the first signaling is used to dynamically adjust the SBFD configuration.
[0026] In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
[0027] In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.
[0028] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
[0029] In the twelfth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.
[0030] In the embodiments of the present application, for transmission processing after Dynamic SBFD is introduced or deployed, the specific processing methods are sorted out to ensure the feasibility of Dynamic SBFD, so that available resources can dynamically match business needs to improve business transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] Figure 1a is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;
[0032] Figure 1b It is a schematic diagram of a flexible duplex mode;
[0033] Figure 2 It is one of the flow charts of the processing method provided in the embodiment of the present application;
[0034] Figure 3a This is one of the application scenario schematic diagrams provided in the embodiments of the present application;
[0035] Figure 3b This is the second schematic diagram of the application scenario provided in the embodiment of the present application;
[0036] Figure 3c This is the third application scenario schematic diagram provided by the embodiment of the present application;
[0037] Figure 3d This is the fourth application scenario schematic diagram provided by the embodiment of the present application;
[0038] Figure 3e This is the fifth application scenario schematic diagram provided by the embodiment of the present application;
[0039] Figure 4 This is the second flow chart of the processing method provided in the embodiment of the present application;
[0040] Figure 5 It is one of the structural schematic diagrams of the processing device provided in the embodiment of the present application;
[0041] Figure 6 This is the second structural diagram of the processing device provided in the embodiment of the present application;
[0042] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;
[0043] Figure 8 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;
[0044] Fig. 9 It is a schematic diagram of the structure of the network side device provided in the embodiment of the present application;
[0045] Fig.10 It is a structural diagram of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0046] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0047] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0048] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0049] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.
[0050] Figure 1aA block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0051] The core network device may include, but is not limited to, at least one of the following: a core network node, a core network function, a mobility management entity (Mobility Management Entity, MME), an access mobility management function (Access and Mobility Management Function, AMF), a session management function (Session Management Function, SMF), a user plane function (User Plane Function, UPF), a policy control function (Policy Control Function, PCF), a policy and charging rules function unit (Policy and Charging Rules Function, PCRF), an edge application service discovery function (Edge Application Server Discovery Function, EASDF), a unified data management (Unified Data Management, UDM), a unified data storage (Unified Data Repository, UDR), a home user server (Home Subscriber Server, HSS), a centralized network configuration (CNC), a network storage function (Network Repository Function, NRF), a network exposure function (Network Exposure Function, NEF), a local NEF (Local NEF, or L-NEF), and a binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.
[0052] In order to better understand the technical solution of this application, the following contents are first introduced:
[0053] Flexibleduplex
[0054] When deploying traditional cellular networks, frequency division duplex (FDD) or time division duplex (TDD) can be used based on the available spectrum and service characteristics. When FDD is used, uplink and downlink transmissions are located at different frequencies, and the two do not interfere with each other and can be carried out simultaneously. When TDD is used, uplink and downlink transmissions are located at the same frequency and are carried out in a staggered manner using time division. Both duplex methods have their own advantages and disadvantages.
[0055] In order to more flexibly utilize limited spectrum resources, dynamically match business needs, improve resource utilization efficiency, and improve uplink coverage, latency and other performance of data transmission, a flexible duplex mode is proposed. A flexible duplex mode based on non-overlapping sub-band full duplex in the frequency domain (SBFD, non-overlapping sub-band full duplex) is:
[0056] Full-duplex on the network side
[0057] From the perspective of the network side, at the same time, uplink transmission and downlink transmission can be carried out simultaneously in different frequency domain sub-bands. To avoid interference between uplink and downlink, a certain guard band can be reserved between the frequency domain sub-bands corresponding to different transmission directions (such as uplink sub-band and downlink sub-band).
[0058] Terminal side half-duplex or full-duplex
[0059] When the terminal side supports half-duplex, only uplink transmission or downlink transmission can be performed at the same time, and both cannot be performed at the same time. It can be understood that in this case, the uplink transmission and downlink transmission at the same time on the network side can only be for different terminals.
[0060] When the terminal side supports full-duplex, similar to the network side, at the same time, uplink transmission and downlink transmission can be performed simultaneously in different frequency domain sub-bands.
[0061] Figure 1b A schematic diagram of the flexible duplex mode is given. In a part of the downlink symbol, the network side semi-statically divides the frequency domain of a single carrier into three sub-bands, where the two sides of the carrier are downlink sub-bands and the center is uplink sub-bands, to reduce interference to adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception respectively.
[0062] Dynamic SBFD
[0063] In Rel-18, SBFD based on full-duplex on the network side and half-duplex on the terminal side was studied. Among them, the focus was on semi-static SBFD, that is, only uplink transmission in the uplink subband configured on the network side, and only downlink transmission in the downlink subband configured on the network side. At the same time, more research has been done on Dynamic SBFD, including: for Semi-static DL symbols configured with ULsubband, downlink transmission is allowed outside the DL subband; for Semi-static flexible symbols configured with ULsubband, downlink transmission is allowed outside the DL subband, and uplink transmission is allowed outside the UL subband. The details are as follows:
[0064] For dynamic SBFD,
[0065] For UEs that are aware of SBFD (i.e., UEs that know that the network side performs SBFD operations within a certain serving cell / carrier / bandwidth portion by obtaining relevant configuration / indication information; optionally, these UEs can further know the time domain / frequency domain location corresponding to the SBFD operation), further study whether DL reception outside the semi-statically configured DL subband is allowed in symbols configured as DL in TDD-UL-DL-ConfigCommon based on the following options:
[0066] Option 1 (semi-static): DL reception is not allowed outside the semi-statically configured DL subbands;
[0067] Option 2: Allow DL reception outside of the semi-statically configured DL subbands.
[0068] For SBFD-aware UEs, further study whether DL reception outside the semi-statically configured DL subbands and UL transmission outside the semi-statically configured UL subbands are allowed in symbols configured as flexible in TDD-UL-DL-ConfigCommon based on the following options:
[0069] Option 1 (semi-static): DL reception is not allowed outside the semi-statically configured DL subbands, and UL transmission is not allowed outside the semi-statically configured UL subbands;
[0070] Option 2: Allow DL reception outside the semi-statically configured DL subbands, but disallow UL transmission outside the semi-statically configured UL subbands;
[0071] Option 3: Allow DL reception outside of the semi-statically configured DL subbands, and allow UL transmission outside of the semi-statically configured UL subbands.
[0072] In addition, some discussion has been made on the signaling method for implementing Dynamic SBFD, including the signaling indication method based on scheduling downlink control information (DCI) / non-scheduling DCI / media access control element (MAC CE), as follows:
[0073] If dynamic SBFD is supported, the following options can be considered:
[0074] Option 1: Dynamic SBFD is achieved by scheduling DCI for scheduling DL reception outside of the semi-statically configured SBFD DL subband and / or UL transmission outside of the semi-statically configured SBFD UL subband.
[0075] Option 2: Dynamic SBFD is implemented through non-scheduled DCI, which indicates whether a symbol is a SBFD symbol.
[0076] Option 3: Dynamic SBFD is implemented by a MAC CE that indicates whether a symbol is a SBFD symbol.
[0077] There is no discussion about the timeline processing of Dynamic SBFD ("Timeline processing" here can be understood as: the determination of the processing timing relationship of uplink transmission and / or downlink reception and related operations and requirements). Therefore, it is necessary to sort out the timeline processing solutions of Dynamic SBFD to ensure the feasibility of Dynamic SBFD.
[0078] The processing method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.
[0079] First, the following concepts involved in the description of this application are explained:
[0080] Based on the TDD pattern configuration information provided by the network side to the UE (for example, tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated provided for a serving cell of the UE), the following symbol types can be distinguished:
[0081] (1)DL symbol;
[0082] (2)UL symbol;
[0083] (3)Flexible symbol;
[0084] When tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated is not provided for a certain Serving cell, it can be considered that each Symbol is a Flexible symbol, or follows the rules corresponding to the Flexible symbol.
[0085] Based on the above TDD pattern configuration information and the SBFD configuration information provided by the network side to the UE, the Symbol types corresponding to (1) and (2) can be further distinguished as follows:
[0086] (1)SBFD symbol
[0087] The network side can configure certain symbols to perform SBFD operation through SBFD configuration information, that is, configure these symbols as SBFD symbols. For example, some or all symbols in a single cycle determined based on the TDD pattern are configured as SBFD symbols. These symbols configured as SBFD symbols can be some or all types of Symbol types distinguished based on the TDD pattern configuration information.
[0088] For a serving cell configured or activated for a UE, the SBFD symbol on the serving cell can be further distinguished into the following symbol types corresponding to (1.1) and (1.2):
[0089] (1.1)SBFD symbol for duplex mode 1
[0090] For Duplex mode 1, the network side supports SBFD operation based on full-duplex; the UE side only supports SBFD operation based on half-duplex, that is, within a single SBFD symbol, the UE can only perform uplink transmission or downlink reception, but cannot perform uplink transmission and downlink reception based on FDM at the same time.
[0091] (1.2)SBFD symbol for duplex mode 2
[0092] For Duplex mode 2, the network side supports SBFD operation based on full duplex; the UE side can support SBFD operation based on full duplex, that is, the UE can simultaneously perform uplink transmission and downlink reception based on FDM within a single SBFD symbol. It can be understood that a UE that supports SBFD operation based on full duplex (i.e., supports Duplex mode 2, or supports SBFD symbol for duplex mode 2) must also support SBFD operation based on half duplex (i.e., supports Duplex mode 1, or supports SBFD symbol for duplex mode 1).
[0093] Optionally, the UE does not expect the SSB symbol to be configured as the SBFD symbol for duplex mode 2 to ensure the performance of SSB-based measurement and other operations. The SSB associated with the SSB symbol here includes at least one of CD-SSB and NCD-SSB.
[0094] Optionally, the UE does not expect the SBFD symbol configured with the PRACH occasion (which can be understood as the PRACH occasion mapped in the UL subband configured in this / these SBFD symbol) to be configured as the SBFD symbol for duplex mode 2 to avoid the impact of self-interference caused by PRACH transmission on potential downlink reception / measurement performance. Alternatively, when the PRACH occasion is configured in the SBFD symbol configured as the SBFD symbol for duplex mode 2, the UE implementation chooses whether to send PRACH or perform downlink reception / measurement. One possible implementation is that when triggered to initiate PRACH transmission (excluding PDCCH order based PRACH), the UE chooses to send PRACH; otherwise, the UE chooses to perform downlink reception / measurement.
[0095] Optionally, for a UE supporting Duplex mode 2 (or a UE supporting both Duplex mode 1 and Duplex mode 2), in the Frequency domain pattern configured / applied for two SBFD symbols in the same carrier (Carrier) / Serving cell / bandwidth part pair (BWP pair), the bandwidth corresponding to the Guardband corresponding to the SBFD symbol for duplex mode 2 is greater than or not less than the bandwidth corresponding to the Guardband corresponding to the SBFD symbol for duplex mode 1, so as to suppress the self-interference caused by the potential UE-side full-duplex operation of Duplex mode 2 (Duplex mode 1 does not involve self-interference). Optionally, the frequency domain range corresponding to the ULsubband / DL subband corresponding to the SBFD symbol for duplex mode 2 is within the frequency domain range corresponding to the ULsubband / DL subband corresponding to the SBFD symbol for duplex mode 1; the frequency domain range corresponding to the Guardband corresponding to the SBFD symbol for duplex mode 1 is within the frequency domain range corresponding to the Guardband corresponding to the SBFD symbol for duplex mode 2. For example, in Figure 3aFor Duplex mode 1, the Frequency domain pattern configured for the UE can be consistent with the frequency domain resources planned by the network side for the SBFD operation; for Duplex mode 2, the single UL subband in the Frequency domain pattern configured for the UE is located within the frequency domain range of the UL subband planned by the network side for the SBFD operation, and each DL subband is located within the frequency domain range of the corresponding DL subband planned by the network side for the SBFD operation. Optionally, in the Frequency domain patterns corresponding to the two Duplex modes, the corresponding DL subbands are completely aligned (i.e., the sizes and positions of the two in the frequency domain are the same), and only the corresponding UL subbands are not aligned (i.e., the sizes or positions of the two in the frequency domain are different); or, the corresponding UL subbands are completely aligned, and only the corresponding DL subbands are not aligned. Optionally, in the Frequency domain patterns corresponding to the two Duplex modes, the center frequencies of the corresponding DL / UL subbands are the same / aligned.
[0096] Optionally, after the introduction of Dynamic SBFD, Duplex mode 2 can be further subdivided into multiple Duplex modes according to different dimensions. Accordingly, the corresponding SBFDsymbol type can be determined for each Duplex mode. For example, based on whether the size and position of the Guardband in the frequency domain are fixed (based on semi-static configuration) or variable (based on dynamic signaling), Duplex mode 2 can be further divided into the following Duplex modes corresponding to (a) to (b):
[0097] (a) Duplex mode 2A: The size and position of the guardband are fixed;
[0098] Accordingly, the sizes and positions of the DL subband and the UL subband are also fixed.
[0099] (b) Duplex mode 2B: The size of the guardband is fixed, but the position can be changed;
[0100] At this time, the Guardband may occupy frequency domain resources corresponding to the DL subband and / or UL subband planned by the network side for the SBFD operation as needed.
[0101] Accordingly, the sizes and positions of the DL subband and the UL subband also change as the position of the Guardband changes.
[0102] (c) Duplex mode 2C: The size and position of the Guardband can be changed;
[0103] Accordingly, the sizes and positions of the DL subband and the UL subband also change as the position of the Guardband changes.
[0104] (d) Duplex mode 2D: The size of the guardband can be changed, but the position is fixed;
[0105] Here, the position of the Guardband is fixed, but its size can vary. This can be understood as follows: the center frequency of the Guardband, or the starting point / end point of the Guardband in the frequency domain is fixed, but the frequency domain width corresponding to the Guardband can vary.
[0106] For the Duplex mode corresponding to (c) or (d) above, the UE can report multiple Guardband sizes and applicable situations / conditions based on its own capabilities. The network side can select one of the Guardband sizes to configure the Frequency domain pattern for the UE as needed. Based on this configured frequency domain pattern, the network side can also use Dynamic SBFD to dynamically change the Guardband size and / or adjust the Guardband position, thereby adjusting the Frequency domain pattern of the actual application.
[0107] Accordingly, the SBFD symbol for duplex mode 2A, the SBFD symbol for duplex mode 2B, the SBFD symbol for duplex mode 2C and the SBFD symbol for duplex mode 2D can be further distinguished.
[0108] Whether the UE supports SBFD and the supported Duplex mode or SBFD symbol type when SBFD is supported may be determined based on the capability report of the UE.
[0109] (2) non-SBFD symbol
[0110] A symbol that is not configured (or instructed) to perform an SBFD operation can be considered a non-SBFDsymbol.
[0111] After the Symbol type corresponding to each Symbol is determined based on the above SBFD configuration information, Dynamic SBFD can be introduced to further dynamically adjust the Symbol type actually applied to some or all Symbols, so that the available resources dynamically match the service requirements to improve the service transmission performance.
[0112] See also Figure 2 , the embodiment of the present application provides a processing method, the execution subject of the method is a terminal, and the method includes:
[0113] Step 201: The terminal receives a first signaling from a network side device;
[0114] Step 202: The terminal performs a processing operation of a target uplink transmission or a processing operation of a target downlink reception according to the first signaling;
[0115] The first signaling is used to dynamically adjust the SBFD configuration.
[0116] The above-mentioned terminal receiving the first signaling to dynamically adjust the SBFD configuration based on the semi-static SBFD configuration may also be referred to as Dynamic overriding;
[0117] It should be noted that the above-mentioned target uplink transmission and target downlink reception refer to the transmission to be performed based on semi-static configuration information and / or indicated information. The processing operation of the target uplink transmission may include a cancellation operation (Cancellation) and a preparation operation (Preparation) of the target uplink transmission, and the processing operation of the target downlink reception may include a cancellation operation and a preparation operation of the target downlink reception.
[0118] For the target uplink transmission that needs to be judged or canceled, it can be understood that, in general, only the uplink transmission that the terminal judged to be actually executable before this Dynamic overriding and the terminal has begun to prepare for is considered. Here, the information based on which the terminal judges that this uplink transmission can be actually executed is the semi-static configuration information and / or indicated information before this Dynamic overriding, and does not include the information corresponding to this Dynamic overriding.
[0119] For the target uplink transmission that needs to be judged or prepared, it can be understood that, in general, only the uplink transmission that meets the following situation 1 or situation 2 is considered: situation 1, based on the semi-static configuration information and / or indicated information before this Dynamic overriding, this uplink transmission does not exist yet; situation 2, based on the semi-static configuration information and / or indicated information before this Dynamic overriding, the terminal has known this uplink transmission, but has not judged this uplink transmission as actually executable. After the terminal learns of this Dynamic overriding, it judges that this uplink transmission is actually executable (that is, the semi-static configuration information and / or indicated information based on which the terminal judges that it can be actually executed must include the information corresponding to this Dynamic overriding), then the terminal judges and prepares this uplink transmission as needed.
[0120] For the target downlink reception that needs to be judged or prepared, it can be understood that, in general, only the downlink reception that meets the following situation 3 or situation 4 is considered: situation 3, based on the semi-static configuration information and / or indicated information before this Dynamic overriding, this downlink reception does not exist; situation 4, based on the semi-static configuration information and / or indicated information before this Dynamic overriding, the terminal is aware of this downlink reception, but has not judged this downlink reception as actually executable. After the terminal learns of this Dynamic overriding, it judges that this downlink reception is actually executable (that is, the semi-static configuration information and / or indicated information based on which the terminal judges that it can be actually executed must include the information corresponding to this Dynamic overriding), then the terminal judges and prepares this downlink reception as needed.
[0121] In the embodiments of the present application, for the subsequent transmission processing when Dynamic SBFD is introduced or deployed, the specific processing methods are sorted out to ensure the feasibility of Dynamic SBFD, so that the available resources can dynamically match the business needs to improve the business transmission performance.
[0122] For a scheduled or configured uplink transmission, the terminal can actually perform the uplink transmission only when at least the following two conditions are met simultaneously:
[0123] Condition 1: (after possible puncturing / rate matching) any frequency domain resource occupied by any symbol can be used for uplink transmission;
[0124] Condition 2: The parameters (or parameter sets) actually in effect in any occupied Symbol match / are compatible with the parameters (or parameter sets) applied during the preparation of this uplink transmission.
[0125] The uplink transmission here may include at least one of the following (1) and (2):
[0126] (1) Physical Uplink Shared Channel (PDSCH) / Physical Uplink Control Channel (PUCCH) / Physical Random Access Channel (PRACH) / Sounding Reference Signal (SRS) transmission configured by high-layer signaling.
[0127] (2) Dynamically scheduled / triggered PUSCH / PUCCH / PRACH / SRS transmission. For uplink Cancellation, the Cancellation of dynamically scheduled / triggered uplink transmission is involved / included in the following cases: allowing the later scheduled / triggered uplink transmission to override / de-prioritize the previously scheduled / triggered uplink transmission (for example, based on the order of scheduling / triggering DCI), or allowing the scheduled / triggered higher priority uplink transmission to override / de-prioritize the scheduled / triggered lower priority uplink transmission (for example, based on PHY priority 0 / 1), or allowing Dynamic overriding based on Group common signaling to override / de-prioritize the previously scheduled / triggered uplink transmission. For uplink Preparation, the dynamically scheduled uplink transmission can be mainly considered while Dynamic overriding.
[0128] When Dynamic SBFD may affect the satisfaction of any of the above conditions, the terminal needs to determine or re-determine whether the uplink transmission can be actually transmitted. When a certain uplink transmission is required / able to be performed based on semi-static configuration information and / or indicated information, the terminal begins to prepare for this uplink transmission. When it is subsequently determined based on Dynamic SBFD that the actual transmission cannot be performed, the terminal may need to perform a Cancellation operation; when a certain uplink transmission is not required based on semi-static configuration information and / or indicated information, the terminal ignores or cancels this uplink transmission. When it is subsequently determined based on Dynamic SBFD that the transmission is actually required, the terminal may need to perform Preparation and sending operations. These judgments / operations require the terminal to spend a certain amount of time to process, so Timeline processing needs to be defined accordingly.
[0129] In a possible implementation manner, the terminal performs a target uplink transmission processing operation according to the first signaling, including any one of the following (1) and (2):
[0130] (1) when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the first condition, performing a cancellation operation of the target uplink transmission;
[0131] (2) when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the second condition, performing a preparation operation for the target uplink transmission;
[0132] The first case includes at least one of the following (1) and (2):
[0133] (1) within the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment;
[0134] (2) In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application;
[0135] The second situation includes at least one of the following (1) to (3):
[0136] (1) within the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment;
[0137] (2) matching or being compatible with the target uplink transmission based on the dynamically adjusted effective parameters within the target time domain unit;
[0138] (3) In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on dynamic adjustment.
[0139] It should be noted that the above-mentioned time domain units can specifically be symbols, time slots, time periods, etc. For the convenience of description, the time domain units are described as symbols in some specific embodiments below. It can be understood that the embodiments of the present application do not limit the types of time domain units.
[0140] Timeline processing for upstream cancellation
[0141] The application scenario of the Timeline processing involved in the uplink Cancellation is: within a given Symbol, at least one frequency domain resource that was available for uplink transmission before a dynamic overriding is dynamically adjusted to be unavailable for (all) uplink transmissions, and / or, the parameters (or parameter sets) dynamically effective based on this dynamic overriding do not match / are incompatible with the (specific) uplink transmission (and the parameters (or parameter sets) effective before the dynamic overriding match / are compatible with the (specific) uplink transmission).
[0142] In a possible implementation manner, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the first condition, the dynamic adjustment includes at least one of the following (1) to (4):
[0143] (1) Dynamically adjust part of the frequency domain range of the target uplink subband within the target time domain unit to be unavailable for uplink transmission;
[0144] Case 1-1: Dynamically adjust part of the frequency domain range of a given UL subband within a given Symbol to be unavailable for (all) uplink transmission;
[0145] Here, "a given UL subband in a given Symbol" can be understood as: a UL subband configured in a given Symbol (for example, a UL subband configured in a Semi-static DL / flexible symbol; the Semi-static DL / flexible symbol here can be understood as a symbol configured as a DL or flexible symbol by RRC parameters tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated related to the time division duplex mode TDD pattern), or, a UL subband that was effective before this Dynamic overriding (for example, the previous Dynamic overriding dynamically adjusted the given Symbol to SBFD symbol for duplex mode 1, then before this Dynamic overriding, there was a valid UL subband in the given Symbol).
[0146] Examples of scenarios for Case 1-1 include at least one of the following (a) and (b):
[0147] (a) The Duplex mode / Symbol type corresponding to a given Symbol switches, resulting in an adjustment to the frequency domain range corresponding to a given UL subband;
[0148] For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 to SBFD symbol for duplex mode 2. Figure 3b In the present invention, when the Frequency domain pattern in a given Symbol is dynamically adjusted from Pattern for duplex mode 1 to Pattern for duplex mode 2, based on the bandwidth requirement of the Guardband of Duplex mode 2, the bandwidth of a given UL subband is narrowed in this Symbol, so that some frequency domain resources on both sides of the given UL subband are adjusted from being usable for uplink transmission to being unusable for uplink transmission (the UL subband after the frequency domain range is narrowed can be called an adjusted UL subband).
[0149] (b) The Duplex mode / Symbol type corresponding to a given Symbol is not changed, and only the frequency domain range corresponding to a given UL subband is adjusted.
[0150] For example, when Duplex mode 2B or Duplex mode 2C is used in a given Symbol, a change in the size and / or position of the Guardband may also cause a change in the frequency domain range corresponding to a given UL subband.
[0151] (2) dynamically adjusting the entire frequency domain range of the target uplink subband within the target time domain unit to be unavailable for uplink transmission;
[0152] Case 1-2: Dynamically adjust the entire frequency domain range of a given UL subband within a given Symbol to be unavailable for (all) uplink transmissions;
[0153] Scenario examples of Case 1-2 include: the Symbol type corresponding to a given Symbol switches. For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 or SBFD symbol forduplex mode 2 to DL non-SBFD symbol (i.e., Full DL symbol). In Figure 3, when the Frequency domain pattern within a given Symbol is dynamically adjusted from Pattern for duplex mode 1 to Pattern for full DL, the frequency domain resources corresponding to the entire given UL subband and Guardband are used for downlink reception, that is, all frequency domain resources within a given UL subband are adjusted from being available for uplink transmission to being unavailable for uplink transmission, or, the given UL subband is disabled or invalid or does not exist within the given Symbol.
[0154] (3) Dynamically adjust part of the frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be unavailable for uplink transmission;
[0155] Case 1-3: Dynamically adjust part of the frequency domain range of the UL BWP in a given Symbol to be unavailable for (all) uplink transmission;
[0156] Examples of scenarios for Case 1-3 include: the Symbol type corresponding to a given Symbol switches. For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from UL non-SBFD symbol (i.e., Full UL symbol) to SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2. At this time, all frequency domain resources in the UL BWP can be used for (all) uplink transmissions, and only the frequency domain resources in the UL subband can be used for (all) uplink transmissions.
[0157] (4) Dynamically adjust the parameters in effect in the target time domain unit to be inconsistent with or incompatible with the parameters of the target uplink transmission.
[0158] Case 1-4: The dynamically effective parameters (or parameter sets) in a given Symbol do not match / are incompatible with (specific) uplink transmission;
[0159] Examples of scenarios for Case 1-4 include: different parameters (or parameter sets) can be configured / applied for different Symbol types, and the switching of Symbol types causes the applied parameters (or parameter sets) to change. The uplink transmission affected here can be understood as the uplink transmission associated with the changed parameters (or parameter sets). "Mismatch / incompatibility" can be understood as when a certain uplink transmission is determined to be able to transmit, or is being prepared, at least one parameter in the parameters (or parameter sets) on which it is based, including time-frequency resource configuration, power configuration, spatial relation / Beam configuration, etc., is different from the corresponding parameter value in the dynamically effective parameters (or parameter sets) in a given Symbol, or is not within the application / effective scope of the corresponding parameter. For example, assuming that corresponding PUCCH-Configs are configured for SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2 respectively, when the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 to SBFD symbol for duplex mode 2, the actually effective PUCCH-Config changes, so that the PUCCH transmission configured in the given Symbol before the dynamic adjustment (the corresponding PUCCH-Resource and related transmission parameters are determined based on the PUCCH-Config corresponding to the SBFD symbol for duplex mode 1) can no longer be transmitted (based on the aforementioned condition 2).
[0160] It can be understood that Case 1-1 / 1-2 / 1-3 corresponds to condition 1, and Case 1-4 corresponds to condition 2.
[0161] For the application scenario of the above-mentioned uplink Cancellation Timeline processing, for a certain uplink transmission that needs to be / can be performed based on the semi-static configuration information and / or the previously indicated information, when the terminal performs Dynamic overriding and this uplink transmission satisfies at least one of the following, the terminal determines that this uplink transmission cannot be actually transmitted and needs to be canceled:
[0162] In a possible implementation manner, the terminal performs a processing operation of target uplink transmission according to the first signaling, including:
[0163] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission meets the first condition, performing a cancellation operation of the target uplink transmission;
[0164] The first condition includes at least one of the following (1) to (4):
[0165] (1) at least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a portion of the frequency domain in which the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0166] For Case 1-1, at least one frequency domain resource occupied by the uplink transmission in a given Symbol is located in a partial frequency domain range of a given UL subband that is dynamically adjusted to be unavailable for (all) uplink transmissions;
[0167] (2) at least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within the entire frequency domain range in which the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0168] For Case 1-2, at least one frequency domain resource occupied by the uplink transmission in a given Symbol is located in the entire frequency domain range of a given UL subband that is dynamically adjusted to be unavailable for (all) uplink transmissions;
[0169] (3) at least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a portion of the frequency domain where the uplink BWP is dynamically adjusted to be unavailable for uplink transmission;
[0170] For Case 1-3, at least one frequency domain resource occupied by the uplink transmission in a given Symbol is located in a partial frequency domain range where the UL BWP is dynamically adjusted to be unavailable for (all) uplink transmissions;
[0171] (4) The parameters of the target uplink transmission do not match or are incompatible with the parameters that are dynamically effective in the target time domain unit.
[0172] For Cases 1-4, the parameters (or parameter sets) based on this upstream transmission do not match / are incompatible with the parameters (or parameter sets) that are dynamically effective in a given Symbol.
[0173] Specifically, see Figure 3c , the figure shows the scenario where the SBFD symbol for duplex mode 1 is rolled back to a Full DL symbol based on PDSCH scheduling.
[0174] In a possible implementation manner, executing the cancel operation of the target uplink transmission includes at least one of the following (1) to (4) (that is, when the terminal determines that a certain uplink transmission needs to be canceled, executing at least one of the following (1) to (4)):
[0175] (1) when the target uplink transmission belongs to the first type of transmission, the terminal does not report the partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is less than the first predefined time from the first time reference point, the target uplink transmission is not cancelled;
[0176] The first type of transmission may allow a partial cancellation operation to be performed based on the partial cancellation capability reported by the terminal, or may only allow a full cancellation operation to be performed. Optionally, the first type of transmission includes at least one of PUSCH transmission, PUCCH transmission and PRACH transmission.
[0177] (2) when the target uplink transmission belongs to the first type of transmission, the terminal does not report the partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is greater than or equal to the first predefined time length from the first time reference point, cancel the target uplink transmission;
[0178] When the uplink transmission is PUSCH / PUCCH / PRACH transmission:
[0179] When the terminal does not indicate the [partialCancellation] capability, the uplink transmission is not canceled when the start time of the uplink transmission is less than a predefined time from the first time reference point; otherwise, the uplink transmission is canceled as a whole, that is, the uplink transmission is ignored as a whole, or not transmitted as a whole.
[0180] (3) when the target uplink transmission belongs to the first type of transmission and the terminal reports a partial cancellation capability for the first type of transmission, canceling the transmission of the target uplink transmission within any time domain unit that is not less than a first predefined time length from the first time reference point;
[0181] When the uplink transmission is PUSCH / PUCCH / PRACH transmission:
[0182] When the terminal indicates the [partialCancellation] capability, the terminal only cancels the transmission of this uplink transmission within the Symbol that is not less than a predefined time length from the first time reference point (including one or more given Symbols that determine that this uplink transmission needs to be canceled, and the occupied Symbol after this / these Symbols (if any)).
[0183] (4) when the target uplink transmission belongs to the second type of transmission, cancel the transmission of the target uplink transmission in the time domain unit that is not less than the first predefined time length from the first time reference point and does not meet the second condition;
[0184] It is assumed here that the terminal can always perform a partial cancellation operation for the second type of transmission. Optionally, the second type of transmission includes SRS transmission.
[0185] When the uplink transmission is SRS transmission:
[0186] The terminal only cancels the transmission within one or more given Symbols whose distance from the first time reference point is not less than a predefined time length and for which it is determined that the uplink transmission needs to be canceled.
[0187] The second condition is that any frequency domain resource occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and the parameters actually effective in the target time domain unit match or are compatible with the parameters applied during preparation of the target uplink transmission;
[0188] The first time reference point includes any one of the following (1) and (2):
[0189] (1) The end time of the first signaling;
[0190] (2) Detecting the end time of the control resource set CORESET or the time domain unit of the first signaling.
[0191] The first time reference point may be: the end time of the DCI indicating dynamic overriding (ie, the end time of the last symbol occupied by the PDCCH carrying the DCI), or the end time of the CORESET / Slot in which the DCI is detected.
[0192] Determining the first predefined duration includes any one of the following (1) to (3):
[0193] (1) determining a first predefined duration based on the first parameter and the first offset;
[0194] (2) determining a first predefined duration based on a second parameter and a second offset; it can be understood that the second offset can be the same as or different from the first offset;
[0195] (3) determining a first predefined duration based on a third parameter;
[0196] Among them, the first parameter is the preset preparation time, the second parameter is the preset number of preparation time domain units, and the third parameter is different from the first parameter and the second parameter.
[0197] The above (1) and (2) are referred to as the predefined duration determination method 1-1, and the above (3) is referred to as the predefined duration determination method 1-2.
[0198] In a possible implementation manner, determining the target offset includes any one of the following (1) to (4):
[0199] (1) The target offset value is a single value specified by the protocol or pre-configured;
[0200] (2) At least one value is specified or preconfigured in the protocol, and the indication information (for example, DCI) carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0201] (3) The protocol specifies or preconfigures at least one first record, and determines a matching first record from the at least one first record, and uses an offset value corresponding to the matching first record as a target offset value, wherein each first record in the at least one first record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0202] When determining a matching record from the at least one first record, for a first record in the at least one first record, if the source time domain unit type corresponding to the first record is the same as the source time domain unit type of the dynamic adjustment, and the target time domain unit type corresponding to the first record is the same as the target time domain unit type of the dynamic adjustment, then the terminal determines that the first record matches the dynamic adjustment, that is, the first record is a matching first record. Optionally, the terminal expects to determine at most one matching first record from the at least one first record. Optionally, the terminal expects to determine at least one matching first record from the at least one first record. Optionally, when the terminal cannot determine any matching first record from the at least one first record, the value of the target offset is a default value.
[0203] (4) the protocol specifies or pre-configures at least one target parameter, and when the value of at least one of the at least one target parameter changes due to dynamic adjustment, the value of the target offset is a predefined value, and when the value of at least one of the target parameters does not change due to dynamic adjustment, the value of the target offset is a default value;
[0204] The target offset is any one of the following: a first offset, a second offset.
[0205] In the embodiment of the present application, the predefined duration is determined in a manner 1-1: in T proc,2 Or introduce a Delta based on N2;
[0206] T proc,2 Or N2 can be determined based on the existing protocol, namely:
[0207] T proc,2 is the PUSCH preparation time corresponding to the terminal processing capability; when determining the PUSCH preparation time here, the following assumptions are adopted: 2,1 =1; μ corresponds to the minimum SCS configuration between the following two: SCS configuration of PDCCH carrying DCI format; SCS configuration of SRS, PUCCH, PUSCH or μ r When PRACH uses 15kHz or higher SCS configuration, μ r is the SCS configuration of PRACH, otherwise μ r =0.
[0208] N2 can be understood as the duration corresponding to N2 Symbols, and the SCS corresponding to the Symbol is the SCS of the UL BWP application.
[0209] For Cancellation of uplink transmission, after the introduction of Dynamic overriding, compared with the situation before the introduction, the terminal may need to perform additional operations while canceling uplink transmission. For example, when different parameters (or parameter sets) are configured / applied for different Symbol types, the terminal may need to switch the corresponding parameters (or parameter sets) according to the target Symbol type of Dynamic overriding, and adjust the Digital filter accordingly based on the changes in available time-frequency resources.
[0210] Delta can be specified by the protocol or configured by high-level signaling according to the terminal capabilities, etc. (hereinafter the same), and can adopt any of the following (1) to (4):
[0211] (1) A single Delta value is specified by the protocol or configured by high-level signaling. During Dynamic overriding, the change of Symbol type is not distinguished and this value is uniformly applied. Optionally, whether to apply this value is indicated in the DCI indicating Dynamic overriding, and 1 bit can be used for indication, for example, a value of 0 indicates that this value is not applied, and a value of 1 indicates that this value is applied. Optionally, different SCSs can be distinguished to determine the corresponding single Delta values, for example, a 30kHz SCS corresponds to one Delta value, a 60kHz SCS corresponds to another Delta value, and so on.
[0212] (2) At least one Delta value is specified by the protocol or configured by high-level signaling, and the DCI indicating Dynamic overriding indicates the application of one of the values. For example, when there are N (>=1) Delta values, the ceiling (log2 (N)) bit can be used for indication, where log2 () is the logarithm of 2 and ceiling () is the rounding operation. When there is no indication bit in the DCI, the Delta default value can be applied, or the Delta value corresponding to the default index value can be applied (for example, the first Delta value is applied, that is, the default index value = 0).
[0213] (3) One or more Delta records are specified by the protocol or configured by high-level signaling. Each Delta record determines the Delta value to be applied when Symbol type 1 is adjusted to Symbol type 2 (assuming that Symbol type 1 is different from Symbol type 2). For Symbol type adjustments not explicitly listed, the terminal does not expect such Symbol type adjustments to occur during Dynamic overriding, or, when such Symbol type adjustments occur during Dynamic overriding, the terminal applies the default Delta value (configured by high-level signaling or specified by the protocol, such as Delta = 0).
[0214] (4) When the value of one or more predefined parameters changes before and after Dynamic overriding, Delta value 1 is applied, otherwise Delta default value is applied. Here, the one or more predefined parameters, as well as Delta value 1 and Delta default value, can be specified by the protocol or configured by high-level signaling. The one or more predefined parameters may include parameters that affect available frequency domain resources, such as Frequency domain pattern related parameters (including corresponding SCS, etc.).
[0215] Optionally, when the Symbol type is dynamically switched, resulting in changes in available time-frequency resources, application configuration parameters (or parameter sets), etc., whether the terminal needs additional switching time or the required additional switching time can be provided to the network side by reporting terminal capability information or auxiliary information. The network side can perform the above-mentioned high-level signaling configuration based on the reported information.
[0216] In a possible implementation manner, determining the first predefined duration based on the third parameter includes any one of the following (1) to (4):
[0217] (1) The first predefined duration is a single duration specified in the protocol or preconfigured;
[0218] (2) At least one duration is specified or preconfigured by the protocol, and one of the at least one durations is indicated by the indication information (for example, DCI) carrying the first signaling as the first predefined duration;
[0219] (3) the protocol specifies or preconfigures at least one second record, and determines a matching second record from the at least one second record, and uses the duration corresponding to the matching second record as the first predefined duration, wherein each second record in the at least one second record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0220] (4) The protocol stipulates or preconfigures at least one target parameter. When the value of at least one of the at least one target parameter changes based on dynamic adjustment, the first predefined duration is the target duration. When the value of at least one of the target parameters does not change based on dynamic adjustment, the first predefined duration is the default duration.
[0221] In the embodiment of the present application, the predefined duration is determined in method 1-2: independent of T proc,2 or N2 is determined;
[0222] It can be specified by the protocol or configured by high-level signaling, using any of the following (1) to (4):
[0223] (1) A single predefined duration is specified by the protocol or configured by high-level signaling. In Dynamic overriding, the duration is applied uniformly regardless of the change of the Symbol type. Optionally, whether to apply this duration is indicated in the DCI indicating Dynamic overriding. One bit can be used for indication. For example, a value of 0 indicates that the existing protocol value T is applied. proc,2, a value of 1 indicates that this duration is applied. Optionally, different SCSs may be distinguished to determine corresponding single predefined durations, for example, a 30kHz SCS corresponds to one predefined duration, a 60kHz SCS corresponds to another predefined duration, and so on.
[0224] (2) At least one predefined duration is specified by the protocol or configured by high-level signaling, and the DCI indicating Dynamic Overriding indicates the application of one of the predefined durations. For example, when there are N (>=1) predefined durations, the ceiling (log2 (N)) bit can be used for indication, where log2 () is the logarithm of 2 and ceiling () is the rounding operation. When there is no indication bit in the DCI, the existing protocol value T can be applied. proc,2 , or, applying the predefined duration corresponding to the default index value (eg, applying the first predefined duration, ie, the default index value = 0).
[0225] (3) One or more predefined duration records are specified by the protocol or configured by high-level signaling, and each predefined duration record determines the corresponding predefined duration when Symbol type 1 is adjusted to Symbol type 2 (assuming that Symbol type 1 is different from Symbol type 2). For Symbol type adjustments not explicitly listed, the terminal does not expect such Symbol type adjustments to occur during Dynamic overriding, or, when such Symbol type adjustments occur during Dynamic overriding, the terminal applies the existing protocol value T proc,2 , or, applying the predefined duration corresponding to the default predefined duration record (for example, applying the predefined duration corresponding to the first predefined duration record).
[0226] (4) When the value of one or more predefined parameters changes before and after Dynamic overriding, the predefined duration 1 is applied, otherwise the predefined duration default value is applied. Here, the predefined one or more parameters, as well as the predefined duration 1 and the predefined duration default value can be specified by the protocol or configured by high-level signaling. For example, the predefined duration default value is the existing protocol value T proc,2 The predefined one or more parameters may include parameters affecting available frequency domain resources, such as Frequencydomain pattern related parameters (including corresponding SCS, etc.).
[0227] Through the above method and related embodiments, it can be ensured that after Dynamic SBFD is introduced or when Dynamic SBFD is deployed, uplink Cancellation-related operations take into account the additional processing time required by the terminal for Dynamic SBFD-related operations, and the processing timing of Dynamic SBFD can be matched with the processing capabilities of different terminals as needed, thereby ensuring the practical feasibility of Dynamic SBFD and reducing the complexity requirements of the terminal.
[0228] Timeline processing involved in uplink preparation
[0229] The application scenarios of the Timeline processing involved in uplink Preparation are: within a given Symbol, at least one frequency domain resource that was not available for uplink transmission before a dynamic overriding is dynamically adjusted to be available for (all) uplink transmissions, and / or, the parameters (or parameter sets) dynamically effective based on this dynamic overriding match / are compatible with (specific) uplink transmissions (and the parameters (or parameter sets) effective before the dynamic overriding do not match / are incompatible with (specific) uplink transmissions), and / or, at least one uplink transmission is newly scheduled / triggered based on this dynamic overriding.
[0230] In a possible implementation manner, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the second condition, the dynamic adjustment includes at least one of the following (1) to (4):
[0231] (1) Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be usable for uplink transmission;
[0232] Case 2-1: Dynamically adjust part of the frequency domain range of a given UL subband within a given Symbol to be available for (all) uplink transmissions;
[0233] Examples of scenarios for Case 2-1 include at least one of the following (a) and (b):
[0234] (a) The Duplex mode / Symbol type corresponding to a given Symbol switches, resulting in an adjustment to the frequency domain range corresponding to a given UL subband
[0235] For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 2 to SBFD symbol for duplex mode 1. In FIG3 , when the Frequency domain pattern in a given Symbol is dynamically adjusted from Pattern for duplex mode 2 to Pattern for duplex mode 1, based on the bandwidth requirement of the Guardband of Duplex mode 1, the bandwidth of a given UL subband is widened in this Symbol, so that some frequency domain resources on both sides of the given UL subband are adjusted from being unavailable for uplink transmission to being available for uplink transmission (the UL subband after the frequency domain range is widened may be referred to as an adjusted UL subband).
[0236] (b) The Duplex mode / Symbol type corresponding to a given Symbol is not changed, and only the frequency domain range corresponding to a given UL subband is adjusted.
[0237] For example, when Duplex mode 2B or Duplex mode 2C is used in a given Symbol, a change in the size and / or position of the Guardband may also cause a change in the frequency domain range corresponding to a given UL subband.
[0238] (2) Dynamically adjust the target time domain unit from a non-existent uplink subband to an existing uplink subband;
[0239] It can be understood that the entire frequency domain range of the target uplink subband existing based on the dynamic adjustment can be used for uplink transmission.
[0240] Case 2-2: The UL subband does not exist in a given symbol and is adjusted to exist, and the entire frequency domain range of the existing UL subband can be used for (all) uplink transmissions;
[0241] The scenario examples of Case 2-2 include: the Symbol type corresponding to the given Symbol switches. For example, the Symbol type corresponding to the given Symbol is dynamically adjusted from DL non-SBFD symbol (i.e., Full DL symbol) to SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2. In Figure 3, when the Frequency domain pattern in the given Symbol is dynamically adjusted from Pattern for full DL to Pattern for duplex mode 1, the given Symbol is adjusted from all frequency domain resources being used for downlink reception to having one UL subband, and the entire frequency domain range of this UL subband can be used for (all) uplink transmissions.
[0242] (3) Dynamically adjust the entire frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be available for uplink transmission;
[0243] Case 2-3: Dynamically adjust the entire frequency domain range of the UL BWP within a given Symbol to be available for (all) uplink transmissions;
[0244] The scenario examples of Case 2-3 include: the Symbol type corresponding to a given Symbol switches. For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2 to UL non-SBFD symbol (i.e., Full UL symbol). At this time, the frequency domain resources in the UL subband are adjusted from being available for (all) uplink transmissions to all frequency domain resources in the UL BWP being available for (all) uplink transmissions.
[0245] (4) Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target uplink transmission.
[0246] Case 2-4: The dynamically effective parameters (or parameter sets) in a given Symbol match / are compatible with (specific) uplink transmission;
[0247] Scenario examples of Case 2-4 include: different parameters (or parameter sets) can be configured / applied for different Symbol types, and the switching of Symbol type causes the applied parameters (or parameter sets) to change. The uplink transmission affected here can be understood as the uplink transmission associated with the changed parameters (or parameter sets). "Matching / compatible" can be understood as that for an uplink transmission that has not started preparation or has been canceled before, all its applicable / applied parameters, including time-frequency resource configuration, power configuration, spatial relation / Beam configuration, etc., are the same as the corresponding parameter values in the dynamically effective parameters (or parameter sets) in the given Symbol, or are within the application / effective range of the corresponding parameters. For example, assuming that corresponding PUCCH-Configs are configured for SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2, respectively, when the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 to SBFD symbol for duplex mode 2, the actually effective PUCCH-Config changes, so that the PUCCH transmission determined based on the PUCCH-Resource and related parameters configured in the actually effective PUCCH-Config (for example, PUCCH transmission for carrying Periodic / Semi-persistent CSI, assuming that the corresponding CSI-ReportConfig is configured to use the PUCCH-Resource and related parameters in the PUCCH-Config corresponding to the SBFD symbol for duplex mode 1 when the reporting time is within the SBFD symbol for duplex mode 1, and is configured to use the PUCCH-Resource and related parameters in the PUCCH-Config corresponding to the SBFD symbol for duplex mode 2 when the reporting time is within the SBFD symbol for duplex mode 2) can be transmitted (based on the aforementioned condition 2).
[0248] It can be understood that Case 2-1 / 2-2 / 2-3 corresponds to condition 1, and Case 2-4 corresponds to condition 2.
[0249] For the application scenario of the above-mentioned uplink Preparation Timeline processing, for a certain uplink transmission that does not need / cannot be performed based on semi-static configuration information and / or previously indicated information, when the terminal performs Dynamic overriding and this uplink transmission at least satisfies conditions 1 and 2 at the same time, the terminal determines that this uplink transmission can be actually transmitted and needs to prepare the corresponding transmission; or, for a certain uplink transmission that is newly scheduled / triggered while Dynamic overriding, it is assumed (or the terminal expects) that this uplink transmission at least satisfies conditions 1 and 2 at the same time, so that the terminal determines that this uplink transmission can be actually transmitted and needs to prepare the corresponding transmission. Optionally, this uplink transmission satisfies at least one of the following:
[0250] In a possible implementation manner, the terminal performs a processing operation of target uplink transmission according to the first signaling, including:
[0251] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission meets the third condition, performing a preparation operation for the target uplink transmission;
[0252] The third condition includes at least one of the following (1) to (5):
[0253] (1) The target uplink transmission is the uplink transmission that is newly scheduled or newly triggered while the SBFD configuration is dynamically adjusted;
[0254] For Case 2-1, this uplink transmission is a newly scheduled / triggered uplink transmission during dynamic overriding;
[0255] (2) All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and at least one occupied frequency domain resource is located within the partial frequency domain range of the target uplink subband that is dynamically adjusted to be available for uplink transmission;
[0256] For Case 2-1, all frequency domain resources occupied by this uplink transmission in a given Symbol can be used for (all) uplink transmission, and at least one occupied frequency domain resource is located in a partial frequency domain range that is dynamically adjusted by a given UL subband to be used for (all) uplink transmission;
[0257] (3) All frequency domain resources occupied by the target uplink transmission in the target time domain unit are available for uplink transmission and are located within the frequency domain range corresponding to the target uplink subband that exists or appears based on the dynamically adjusted SBFD configuration;
[0258] For Case 2-2, all frequency domain resources occupied by this uplink transmission within a given Symbol can be used for (all) uplink transmissions and are located within the frequency domain range corresponding to the UL subband that exists / appears based on dynamic adjustment;
[0259] (4) All frequency domain resources occupied by the target uplink transmission within the target time domain unit can be used for uplink transmission;
[0260] For Case 2-3, all frequency domain resources occupied by this uplink transmission within a given Symbol can be used for (all) uplink transmissions;
[0261] (5) The parameters of the target uplink transmission match or are compatible with the parameters that are dynamically effective in the target time domain unit.
[0262] For Case 2-4, the parameters (or parameter sets) based on this upstream transmission match / are compatible with the parameters (or parameter sets) that are dynamically effective within a given Symbol.
[0263] Specifically, see Figure 3d The figure shows a scenario in which the SBFD symbol for duplex mode 1 is indicated as a Full UL symbol based on the group common DCI Group common DCI.
[0264] When the terminal determines that it needs to prepare for an uplink transmission, it performs the following operations:
[0265] In a possible implementation manner, performing a preparation operation for target uplink transmission includes at least one of the following (1) to (4):
[0266] (1) when the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is less than the second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0267] (2) when the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, prepare the target uplink transmission;
[0268] Optionally, the third type of transmission includes at least one of PUSCH transmission, PUCCH transmission and PRACH transmission.
[0269] When the uplink transmission is PUSCH / PUCCH / PRACH transmission:
[0270] When the starting time of the uplink transmission is less than a predefined time length from the second time reference point, the uplink transmission is not prepared, that is, the uplink transmission is ignored as a whole, or not transmitted as a whole; otherwise, the terminal performs a preparation operation to initiate the uplink transmission.
[0271] (3) when the target uplink transmission belongs to the fourth category of transmission and the start time of at least one time domain unit occupied by the target uplink transmission is greater than or equal to the second predefined time length from the second time reference point, performing a preparation operation for the target uplink transmission in the at least one time domain unit;
[0272] (4) when the target uplink transmission belongs to the fourth type of transmission and the start time of any time domain unit occupied by the target uplink transmission is less than the second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0273] Optionally, the fourth type of transmission includes SRS transmission.
[0274] When the uplink transmission is SRS transmission:
[0275] When the start time of at least one Symbol occupied by this uplink transmission is not less than or greater than a predefined time length from the second time reference point, the terminal performs a preparation operation for the transmission within this at least one Symbol and initiates a corresponding transmission; otherwise, the terminal does not prepare for this uplink transmission, that is, this uplink transmission is ignored as a whole, or not transmitted as a whole.
[0276] Optionally, for dynamically scheduled uplink transmission, and / or, newly scheduled / triggered uplink transmission during dynamic overriding, the terminal expects that the starting time of the uplink transmission is not less than a predefined time length from a second time reference point (or, when the uplink transmission is an SRS transmission, the terminal expects that the starting time of at least one Symbol occupied by the SRS transmission is not less than a predefined time length from the second time reference point), which can be guaranteed by the network side.
[0277] The second time reference point includes any one of the following (1) and (2):
[0278] (1) The end time of the first signaling;
[0279] (2) The end time of the CORESET or time domain unit of the first signaling is detected.
[0280] The second time reference point may be: the end time of the DCI indicating dynamic overriding (ie, the end time of the last symbol occupied by the PDCCH carrying the DCI), or the end time of the CORESET / Slot where the DCI is detected.
[0281] Determining the second predefined duration includes any one of the following (1) to (4):
[0282] (1) determining a second predefined duration based on the fourth parameter and the third offset;
[0283] (2) determining a second predefined duration based on the fifth parameter and the fourth offset;
[0284] (3) determining a second predefined duration based on the sixth parameter;
[0285] (4) determining a second predefined duration based on the type of the target uplink transmission and a predefined rule;
[0286] Among them, the fourth parameter is the preset preparation time, the fifth parameter is the preset number of preparation time domain units, and the sixth parameter is different from the fourth parameter and the fifth parameter.
[0287] The above (1) and (2) are referred to as the predefined duration determination method 2-1, the above (3) is referred to as the predefined duration determination method 2-2, and the above (4) is referred to as the predefined duration determination method 2-3.
[0288] In a possible implementation manner, determining the target offset includes any one of the following (1) to (4):
[0289] (1) The target offset value is a single value specified by the protocol or pre-configured;
[0290] (2) At least one value is specified or preconfigured in the protocol, and the indication information (for example, DCI) carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0291] (3) The protocol specifies or preconfigures at least one third record, and determines a matching third record from the at least one third record, and uses the offset value corresponding to the matching third record as the value of the target offset, wherein each third record in the at least one third record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0292] (4) the protocol specifies or pre-configures at least one target parameter, and when the value of at least one of the at least one target parameter changes due to dynamic adjustment, the value of the target offset is a predefined value, and when the value of at least one of the target parameters does not change due to dynamic adjustment, the value of the target offset is a default value;
[0293] The target offset is any one of the following: the third offset, the fourth offset.
[0294] In the embodiment of the present application, the predefined duration determination method 2-1: in T proc,2 Or N2 introduces a Delta. For details, please refer to the corresponding description of the predefined duration determination method 1-1, and only replace "Cancellation" with "Preparation".
[0295] It can be understood that the predefined duration determination method 2-1 can use the Delta in the predefined duration determination method 1-1, or the Delta in the predefined duration determination method 2-1 and the predefined duration determination method 1-1 are determined independently.
[0296] In a possible implementation manner, determining the second predefined duration based on the sixth parameter includes any one of the following (1) to (4):
[0297] (1) The second predefined duration is a single duration specified in the protocol or preconfigured;
[0298] (2) The protocol specifies or preconfigures at least one duration, and the indication information (for example, DCI) carrying the first signaling indicates one of the at least one duration as the second predefined duration;
[0299] (3) The protocol specifies or preconfigures at least one fourth record, and determines a matching fourth record from the at least one fourth record, and uses the duration corresponding to the matching fourth record as the second predefined duration, wherein each fourth record in the at least one fourth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0300] (4) The protocol stipulates or preconfigures at least one target parameter. When the value of at least one of the at least one target parameter changes based on dynamic adjustment, the second predefined duration is the target duration. When the value of at least one of the target parameters does not change based on dynamic adjustment, the second predefined duration is the default duration.
[0301] In an embodiment of the present application, the predefined duration determination method 2-2 is explicitly specified by the protocol or explicitly configured by high-level signaling. For details, please refer to the corresponding description of the predefined duration determination method 1-2.
[0302] It can be understood that the predefined duration determination method 2-2 can use the predefined duration in the predefined duration determination method 1-2, or the predefined duration determination method 2-2 and the predefined duration determination method 1-2 are determined independently.
[0303] Method 2-3 for determining the predefined duration: implicitly determined based on existing protocol provisions or high-level signaling;
[0304] Different uplink transmissions may have their corresponding predefined durations implicitly determined based on the Timeline constants specified in their respective existing protocols or the Timeline parameters configured by high-level signaling.
[0305] For example, the predefined durations corresponding to various types of uplink transmissions may be determined based on the Timeline constants / parameters that dynamically trigger such uplink transmissions in the current Serving cell / BWP pair. Examples for various types of uplink transmissions are as follows:
[0306] In a possible implementation manner, determining the second predefined duration based on the type of target uplink transmission and a predefined rule includes any one of the following (1) to (5):
[0307] (1) When the target uplink transmission is PUSCH transmission, the second predefined duration is any one of the following: a minimum value or a maximum value of a first scheduling offset configured in a time domain resource allocation table (TDRA table) associated with a predefined downlink control information format DCI format, and a configured first minimum scheduling offset;
[0308] PUSCH transmission
[0309] The predefined duration can be the minimum value (or maximum value) of k2 or k2-r16 or extendedK2-r17 (i.e., the above-mentioned first scheduling offset) configured in the TDRA table associated / applied to the predefined DCI format (e.g., DCI format 0_0 / 0_1 / 0_2, which can be specified by the protocol or configured by high-level signaling), or minimumSchedulingOffsetK2-r16 (i.e., the first minimum scheduling offset configured above), and the unit is the Slot length determined based on the SCS corresponding to the PUSCH transmission. At this time, the starting time (i.e., the second time reference point) of applying the predefined duration can be adjusted accordingly to the PUSCH slot corresponding to the PDCCH slot where the DCI is located (assuming that the SCS of the PDCCH is configured as μ PDCCH , the SCS configuration of PUSCH is μ PUSCH , the terminal detects the DCI indicating Dynamic overriding in PDCCH slot n, and the starting time of the application predefined duration is ), or, the PUSCH slot that overlaps with the end time of the DCI (or the last PUSCH slot that overlaps with the PDCCH transmission where the DCI is located).
[0310] (2) When the target uplink transmission is PUCCH transmission, the second predefined duration is the minimum value or maximum value of the time domain feedback offset configured in the time domain feedback offset set associated with the predefined DCI format;
[0311] PUCCH transmission
[0312] The predefined duration may be the minimum value (or maximum value) of K1 in the K1 set (i.e., the above-mentioned time domain feedback offset set) associated / applied to a predefined DCI format (e.g., DCI format 1_0 / 1_1 / 1_2, which may be specified by the protocol or configured by high-level signaling), and the unit is the length of the Slot or Sub-slot corresponding to the PUCCH transmission. At this time, the starting time (i.e., the second time reference point) of applying the predefined duration may be adjusted accordingly to the last PUCCH slot (Slot / Sub-slot, preferably Slot) overlapping with the PDCCH slot where the DCI is located, or the last PUSCH slot (Slot / Sub-slot, preferably Sub-slot) overlapping with the PDCCH transmission where the DCI is located.
[0313] (3) When the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a non-periodic type, the second predefined duration is a time domain unit offset corresponding to the SRS resource set (e.g., corresponding parameter slotOffset);
[0314] (4) when the target uplink transmission is SRS transmission, and the SRS resource set corresponding to the SRS transmission is configured to adopt a periodic type, the second predefined duration is a time domain unit offset corresponding to the first SRS resource set, wherein the first SRS resource set and the SRS resource set corresponding to the SRS transmission correspond to the same serving cell or the same bandwidth part pair BWP pair, and the first SRS resource set adopts a non-periodic type;
[0315] SRS transmission
[0316] When the SRS-ResourceSet corresponding to the SRS transmission is configured to adopt a non-periodic type, the slotOffset corresponding to this SRS-ResourceSet can be directly applied. Otherwise, the slotOffset corresponding to the SRS-ResourceSet configured for the same Serving cell / BWPpair of this terminal and adopting a non-periodic type can be used; when there are multiple SRS-ResourceSets, the SRS-ResourceSet with the smallest / largest srs-ResourceSetId can be selected from them, or the SRS-ResourceSet with a usage of a specific value (for example, the same as the usage of the SRS-ResourceSet corresponding to the SRS transmission) can be selected; when there is no SRS-ResourceSet adopting a non-periodic type, the default value 0 can be used. At this time, the starting time (i.e., the second time reference point) of applying the predefined duration can be adjusted accordingly to the last UL slot overlapping with the PDCCH slot where the DCI is located, or the last UL slot overlapping with the PDCCH transmission where the DCI is located.
[0317] (5) When the target uplink transmission is a PRACH transmission, the second predefined duration is the minimum duration between the last time domain unit carrying a PDCCH order and the first time domain unit of a first PRACH transmission, wherein the first PRACH transmission corresponds to the PDCCH order.
[0318] PRACH transmission
[0319] The predefined duration can be the shortest time between the last symbol received by the PDCCH command and the first symbol transmitted by the PRACH (specifically N T,2 +Δ BWPSwitching +Δ Delay msec).
[0320] Through the above method and related embodiments, it can be ensured that after Dynamic SBFD is introduced or when Dynamic SBFD is deployed, uplink Preparation related operations take into account the additional processing time required by the terminal for Dynamic SBFD related operations, and the processing timing of Dynamic SBFD can be matched with the processing capabilities of different terminals as needed, thereby ensuring the practical feasibility of Dynamic SBFD and reducing the complexity requirements of the terminal.
[0321] For downstream timeline processing, the main considerations are switching the effective parameters (or parameter sets), switching / adjusting the timelines involved in digital filters, etc.
[0322] For a certain scheduled / configured downlink reception, the terminal can actually perform this downlink reception only when it satisfies at least the following two conditions at the same time:
[0323] Condition 3: (after possible Puncturing / Rate matching) any frequency domain resource occupied by any symbol can be used for downlink reception;
[0324] Condition 4: The parameters (or parameter sets) actually in effect in any occupied Symbol match / are compatible with the parameters (or parameter sets) of this downlink receiving application.
[0325] The downlink reception here may include at least one of the following (1) and (2):
[0326] (1) Physical Downlink Shared Channel (PDSCH) / Physical Downlink Control Channel (PDCCH) / Channel State Information-Reference Signal (CSI-RS) transmission configured by high-layer signaling.
[0327] (2) Dynamically scheduled / triggered PDSCH / CSI-RS transmission: Dynamically scheduled downlink reception while dynamic overriding can be considered.
[0328] When Dynamic SBFD may affect the satisfaction of any of the above conditions, the terminal needs to determine or re-determine whether downlink reception needs to be actually received. When a downlink reception needs to be performed based on semi-static configuration information and / or indicated information, the terminal makes corresponding preparations before the start time of this downlink reception (including applying effective parameters (or parameter sets), switching / adjusting Digital filters, etc.) so that downlink reception can be started from the start time of this downlink reception; when a downlink reception does not need to be performed based on semi-static configuration information and / or indicated information, the terminal ignores or cancels this downlink reception. When it is subsequently determined that reception is actually required based on Dynamic SBFD, the terminal may need to perform corresponding preparations so that downlink reception can be started from the start time of this downlink reception. These judgments / operations require the terminal to spend a certain amount of time to process, so Timeline processing needs to be defined accordingly. For the cancellation of downlink reception, it can be understood that after the terminal decodes the indication information corresponding to DynamicSBFD, if it determines based on the indication information that a downlink reception that has been prepared for reception needs to be ignored or canceled, the terminal can directly and immediately abandon the subsequent receiving operation of this downlink reception (if the moment of this judgment is at or before the start time of this downlink reception, the terminal can directly abandon the receiving operation of this downlink reception; if the moment of this judgment is after the start time of this downlink reception, the terminal can terminate the receiving operation of this downlink reception and discard the previously cached data), without explicitly specifying its Timeline processing or considering the required processing time, or directly specifying the predefined duration corresponding to the cancellation operation of the downlink reception as the default value (for example, directly specifying the predefined duration corresponding to the cancellation operation of the downlink reception as 0; at this time, the cancellation operation based on the predefined duration can refer to or follow the corresponding description of the uplink cancellation operation, for example, the uplink cancellation operation here can be a cancellation operation for the first type of uplink transmission or a cancellation operation for the second type of uplink transmission).
[0329] In a possible implementation manner, the terminal performs a target downlink reception processing operation according to the first signaling, including:
[0330] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, performing a preparation operation for the target downlink reception;
[0331] The third situation includes at least one of the following (1) to (3):
[0332] (1) within the target time domain unit, at least one frequency domain resource that is unavailable for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment;
[0333] (2) matching or being compatible with the target downlink reception based on the dynamically adjusted effective parameters within the target time domain unit;
[0334] (3) In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on dynamic adjustment.
[0335] Timeline processing involved in downlink preparation
[0336] The application scenarios of the Timeline processing involved in downlink Preparation are: within a given Symbol, at least one frequency domain resource that was not available for downlink reception before a dynamic overriding is dynamically adjusted to be available for (all) downlink reception, and / or, the parameters (or parameter sets) dynamically effective based on this dynamic overriding match / are compatible with (specific) downlink reception (and the parameters (or parameter sets) effective before the dynamic overriding do not match / are incompatible with the (specific) downlink reception), and / or, at least one downlink reception is newly scheduled / triggered based on this dynamic overriding.
[0337] In a possible implementation manner, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, the dynamic adjustment includes at least one of the following (1) to (4):
[0338] (1) Dynamically adjust a portion of the frequency domain range of a target downlink subband within a target time domain unit to be usable for downlink reception;
[0339] Case 3-1: Dynamically adjust part of the frequency domain range of a given DL subband within a given Symbol to be available for (all) downlink reception;
[0340] Examples of scenarios for Case 3-1 include at least one of the following (a) and (b):
[0341] (a) The Duplex mode / Symbol type corresponding to a given Symbol is switched, resulting in an adjustment in the frequency domain range corresponding to a given DL subband;
[0342] For example, the Symbol type corresponding to the given Symbol is dynamically adjusted from SBFD symbol for duplex mode 2 to SBFD symbol for duplex mode 1. In FIG3 , when the Frequency domain pattern in the given Symbol is dynamically adjusted from Pattern for duplex mode 2 to Pattern for duplex mode 1, based on the bandwidth requirement of the Guardband of Duplex mode 1, the bandwidth of the given DL subband is widened in the Symbol, so that some frequency domain resources on both sides of the given DL subband are adjusted from being unavailable for downlink reception to being available for downlink reception (the DL subband after the frequency domain range is widened may be referred to as an adjusted DL subband).
[0343] (b) The Duplex mode / Symbol type corresponding to a given Symbol is not changed, and only the frequency domain range corresponding to a given DL subband is adjusted;
[0344] For example, when Duplex mode 2B or Duplex mode 2C is used in a given Symbol, changes in the size and / or position of the Guardband may also cause changes in the frequency domain range corresponding to a given DL subband.
[0345] (2) Dynamically adjust the target time domain unit from a non-existent downlink subband to a downlink subband;
[0346] Case 3-2: A DL subband is adjusted from non-existent to existing in a given symbol, and the entire frequency domain range of any existing DL subband can be used for (all) downlink reception;
[0347] The scenario examples of Case 3-2 include: the Symbol type corresponding to the given Symbol switches. For example, the Symbol type corresponding to the given Symbol is dynamically adjusted from UL non-SBFD symbol (i.e., Full UL symbol) to SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2. In Figure 3, when the Frequency domain pattern in the given Symbol is dynamically adjusted from Pattern for full UL to Pattern for duplex mode 1, the given Symbol is adjusted from all frequency domain resources being used for uplink transmission to having two DL subbands, and the entire frequency domain range of any one of the DL subbands can be used for (all) downlink reception.
[0348] (3) Dynamically adjust the entire frequency domain range of the downlink BWP within the target time domain unit to be available for downlink reception;
[0349] Case 3-3: Dynamically adjust the entire frequency domain range of the DL BWP in a given Symbol to be available for (all) downlink reception;
[0350] The scenario examples of Case 3-3 include: the Symbol type corresponding to a given Symbol is switched. For example, the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 or SBFD symbol for duplex mode 2 to DL non-SBFD symbol (i.e., Full DL symbol). At this time, the frequency domain resources in the DL subband are adjusted from being available for (all) downlink reception to all frequency domain resources in the DL BWP being available for (all) downlink reception.
[0351] (4) Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target downlink transmission.
[0352] Case 3-4: The dynamically effective parameters (or parameter sets) in a given Symbol match / are compatible with (specific) downlink reception;
[0353] Scenario examples of Case 3-4 include: different parameters (or parameter sets) can be configured / applied for different Symbol types, and the switching of Symbol type causes the applied parameters (or parameter sets) to change. The affected downlink reception here can be understood as the downlink reception associated with the changed parameters (or parameter sets). "Matching / compatible" can be understood as that for a downlink reception that has not started preparation or has been canceled before, all applicable / applied parameters, including time-frequency resource configuration, power configuration, TCI state / QCL / Beam configuration, etc., are the same as the corresponding parameter values in the dynamically effective parameters (or parameter sets) in the given Symbol, or are within the application / effective range of the corresponding parameters. For example, assuming that corresponding CSI-ReportConfig (corresponding CSI-RS measurement resources) are configured for SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2, respectively, when the Symbol type corresponding to a given Symbol is dynamically adjusted from SBFD symbol for duplex mode 1 to SBFD symbol for duplex mode 2, the actually effective CSI-ReportConfig (corresponding CSI-RS measurement resources) changes, so that the terminal needs to prepare corresponding reception / measurement operations (based on the aforementioned condition 4) based on the CSI-RS measurement resources and related parameters configured in the actually effective CSI-ReportConfig.
[0354] It can be understood that Case 3-1 / 3-2 / 3-3 corresponds to condition 3, and Case 3-4 corresponds to condition 4.
[0355] For the application scenario of the above-mentioned downlink Preparation Timeline processing, for a downlink reception that does not need / cannot be executed based on semi-static configuration information and / or previously indicated information, when the terminal performs Dynamic overriding and this downlink reception at least satisfies Condition 3 and Condition 4 at the same time, the terminal determines that this downlink reception can be actually received, and considers making corresponding reception preparations before the start time of this downlink reception; or, for a downlink reception that is newly scheduled / triggered while Dynamic overriding, it is assumed (or the terminal expects) that this downlink reception at least satisfies Condition 3 and Condition 4 at the same time, so that the terminal determines that this downlink reception can be actually received, and considers making corresponding reception preparations before the start time of this downlink reception.
[0356] In a possible implementation manner, the terminal performs a processing operation of target uplink transmission according to the first signaling, including:
[0357] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target downlink reception satisfies the fourth condition, performing a preparation operation for the target downlink reception;
[0358] The fourth condition includes at least one of the following (1) to (5):
[0359] (1) The target downlink reception belongs to the downlink reception that is newly scheduled or newly triggered while the SBFD configuration is dynamically adjusted;
[0360] For Case 3-1, this downlink transmission belongs to the downlink reception newly scheduled / triggered while dynamic overriding;
[0361] (2) All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception, and at least one occupied frequency domain resource is located within a portion of the frequency domain range of the downlink subband that is dynamically adjusted to be available for downlink reception;
[0362] For Case 3-1, all frequency domain resources occupied by this downlink reception in a given Symbol can be used for (all) downlink reception, and at least one occupied frequency domain resource is located in a partial frequency domain range in which at least one DL subband is dynamically adjusted to be available for (all) downlink reception;
[0363] (3) All frequency domain resources occupied by the target downlink reception in the target time domain unit are available for downlink reception and are all within the frequency domain range corresponding to the downlink subband that exists or appears based on the dynamic adjustment of the SBFD configuration;
[0364] For Case 3-2, all frequency domain resources occupied by this downlink reception in a given Symbol can be used for (all) downlink reception and are located within the frequency domain range corresponding to at least one DL subband that exists / appears based on dynamic adjustment;
[0365] (4) All frequency domain resources occupied by the target downlink reception within the target time domain unit can be used for downlink reception;
[0366] For Case 3-3, all frequency domain resources occupied by this downlink reception within a given Symbol can be used for (all) downlink reception;
[0367] (5) The parameters received by the target downlink match or are compatible with the parameters that are dynamically effective in the target time domain unit.
[0368] For Case 3-4, the parameters (or parameter sets) based on which this downlink reception is received match / is compatible with the parameters (or parameter sets) that are dynamically effective within a given Symbol.
[0369] Specifically, see Figure 3e , the figure shows the scenario where the SBFD symbol for duplexmode1 is indicated as a Full DL symbol based on Group common DCI.
[0370] In a possible implementation, performing a preparation operation for a target downlink reception includes at least one of the following (1) to (3) (that is, when the terminal determines that a certain downlink reception needs to be prepared, performing at least one of the following (1) to (3)):
[0371] (1) when the start time of the target downlink reception is less than a third predefined time length from the third time reference point, performing the first operation;
[0372] (2) when the start time of the target downlink reception is greater than or equal to a third predefined time length from the third time reference point, performing the second operation;
[0373] (3) the terminal expects the start time of the target downlink reception to be no less than a third predefined time length from the third time reference point;
[0374] The above (1) and (2) can be simply referred to as operation 1, and the above (3) can be simply referred to as operation 2.
[0375] Operation 1: When the starting time of the downlink reception is less than a predefined time distance from the third time reference point, the first operation is performed; otherwise, the second operation is performed;
[0376] When this downlink reception is scheduled / triggered by a DCI indicating Dynamic overriding (for example, Dynamic overriding is explicitly or implicitly indicated by UE-specific scheduling signalling),
[0377] The first operation may be any one of the following (a) to (c):
[0378] (a) in a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling or triggering is invalid and the dynamic adjustment of the SBFD configuration fails;
[0379] The scheduling is invalid and Dynamic overriding fails.
[0380] The terminal discards / cancels this downlink reception and considers that this DCI is invalid / should be ignored, that is, Dynamic overriding fails.
[0381] (b) when the target downlink reception is scheduled or triggered by the first signaling, it is determined that the scheduling is valid, but the dynamic adjustment of the SBFD configuration is not effective;
[0382] Scheduling is effective, no dynamic overriding
[0383] The terminal may prepare for the reception of this downlink reception based on the original Symbol type (before Dynamic overriding) (including the parameters (or parameter set) corresponding to the application, etc.), and consider that Dynamic overriding is not actually performed.
[0384] When at least one frequency domain resource occupied by this downlink reception is not available for (all) downlink reception based on the original Symbol type, the terminal performs Rate matching or Puncturing for these frequency domain resources. Optionally, the terminal expects that any frequency domain resource occupied by this downlink reception can be used for (all) downlink reception based on the original Symbol type (for example, when the original Symboltype is SBFD symbol, the frequency domain resources occupied by this downlink reception are all located in the DL subband, or the original Symboltype is DL non-SBFD symbol (i.e., Full DL symbol)).
[0385] (c) when the target downlink reception is not scheduled or triggered by the first signaling, determining that the dynamic adjustment of SBFD is effective, and discarding or canceling the target downlink reception;
[0386] When this downlink reception is not scheduled / triggered by a DCI indicating Dynamic overriding (for example, Dynamic overriding is indicated by Group common signaling), the first operation may be: Dynamic overriding is always successful / effective, and the terminal discards / cancels this downlink reception.
[0387] The second operation includes:
[0388] Determine that the dynamic adjustment of SBFD is effective and prepare for target downlink reception;
[0389] That is, Dynamic overriding succeeds / takes effect, and the terminal is ready to receive this downlink reception.
[0390] Operation 2: The terminal expects that the starting time of the downlink reception is always no less than a predefined time distance from the third time reference point;
[0391] At this time, Dynamic overriding is always successful / effective, and the terminal is ready to receive this downlink reception.
[0392] Optionally, only for dynamically scheduled downlink reception, and / or newly scheduled / triggered downlink reception at the same time as Dynamic overriding, the terminal expects that the start time of this downlink reception is not less than a predefined duration from the third time reference point. For example, in the case where the downlink scheduling DCI implicitly / explicitly indicates Dynamic overriding while scheduling PDSCH reception, the network side can ensure that the start time of this PDSCH reception is not less than a predefined duration from the third time reference point by configuring / indicating an appropriate K0.
[0393] The third time reference point includes any one of the following (1) and (2):
[0394] (1) The end time of the first signaling;
[0395] (2) The end time of the CORESET or time domain unit of the first signaling is detected.
[0396] The third time reference point may be: the end time of the DCI indicating dynamic overriding (ie, the end time of the last symbol occupied by the PDCCH carrying the DCI), or the end time of the CORESET / Slot where the DCI is detected.
[0397] When the downlink reception is PDSCH reception, it is optional to distinguish whether the PDSCH reception is Unicast PDSCH, Broadcast PDSCH or Multicast PDSCH, and adopt different operations respectively. For example, when it is Unicast PDSCH, the terminal expects that the start time of the PDSCH reception is always not less than the predefined duration from the third time reference point; when it is Broadcast / Multicast PDSCH, because the predefined durations used by different terminals may be different, the operation of "scheduling invalid, dynamic overriding failed" can be adopted at this time.
[0398] Determining the third predefined duration includes any one of the following (1) and (2):
[0399] (1) determining a third predefined duration based on the seventh parameter;
[0400] (2) Determine a third predefined duration based on the type of target downlink reception and predefined rules.
[0401] The above (1) is referred to as the predefined duration determination method 3-1, and the above (2) is referred to as the predefined duration determination method 3-2.
[0402] In a possible implementation manner, determining the third predefined duration based on the seventh parameter includes any one of the following (1) to (4):
[0403] (1) The third predefined duration is a single duration specified in the protocol or preconfigured;
[0404] (2) at least one duration is specified or preconfigured by the protocol, and one of the at least one duration is indicated by the indication information carrying the first signaling as the third predefined duration;
[0405] (3) the protocol specifies or preconfigures at least one fifth record, and determines a matching fifth record from the at least one fifth record, and uses the duration corresponding to the matching fifth record as the third predefined duration, wherein each fifth record in the at least one fifth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0406] (4) The protocol stipulates or preconfigures at least one target parameter. When the value of at least one of the at least one target parameter changes based on dynamic adjustment, the third predefined duration is the target duration. When the value of at least one of the target parameters does not change based on dynamic adjustment, the third predefined duration is the default duration.
[0407] In the embodiment of the present application, the predefined duration is determined in mode 3-1: explicitly specified by the protocol or explicitly configured by high-level signaling;
[0408] Specifically, any one of the following (a) to (d) may be adopted:
[0409] (a) A single predefined duration is specified by the protocol or configured by high-level signaling. In Dynamic overriding, the change of Symbol type is not distinguished, and the duration is uniformly applied. Optionally, whether to apply this duration is indicated in the DCI indicating Dynamic overriding, and 1 bit can be used for indication, for example, a value of 0 indicates the application of the default value 0, and a value of 1 indicates the application of this duration. Optionally, different SCSs can be distinguished to determine the corresponding single predefined durations, for example, a 30kHz SCS corresponds to one predefined duration, a 60kHz SCS corresponds to another predefined duration, and so on.
[0410] (b) At least one predefined duration is specified by the protocol or configured by high-level signaling, and the application of one of the predefined durations is indicated in the DCI indicating Dynamic overriding. For example, when there are N (>=1) predefined durations, the ceiling (log2 (N)) bit can be used for indication, where log2 () is the logarithm of 2 and ceiling () is a rounding operation. When there is no indication bit in the DCI, a default value of 0 can be applied, or a predefined duration corresponding to a default index value can be applied (for example, the first predefined duration is applied, i.e., the default index value = 0).
[0411] (c) One or more predefined duration records are specified by the protocol or configured by high-level signaling, and each predefined duration record determines the predefined duration corresponding to the adjustment from Symbol type 1 to Symbol type 2 (assuming that Symbol type 1 is different from Symbol type 2). For Symbol type adjustments not explicitly listed, the terminal does not expect such Symbol type adjustments to occur during Dynamic overriding, or, when such Symbol type adjustments occur during Dynamic overriding, the terminal applies a default value of 0, or applies the predefined duration corresponding to the default predefined duration record (for example, applying the predefined duration corresponding to the first predefined duration record).
[0412] (d) When the value of one or more predefined parameters changes before and after Dynamic overriding, the predefined duration 1 is applied, otherwise the predefined duration default value is applied. Here, the predefined one or more parameters, as well as the predefined duration 1 and the predefined duration default value, can be specified by the protocol or configured by high-level signaling. For example, the predefined duration default value is the default value 0. The predefined one or more parameters may include parameters that affect available frequency domain resources, such as Frequency domain pattern related parameters (including corresponding SCS, etc.).
[0413] In a possible implementation manner, determining the third predefined duration based on the type of target downlink reception and a predefined rule includes any one of the following (a) to (c):
[0414] (a) When the target downlink reception is PDSCH reception, the duration is any one of the following: the minimum value or the maximum value of the second scheduling offset configured in the TDRA table associated with the predefined DCI format, and the configured second minimum scheduling offset;
[0415] (b) when the target downlink reception is CSI-RS reception and the CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a non-periodic type, the duration is the time domain unit offset corresponding to the CSI-RS resource set;
[0416] (c) when the target downlink reception is CSI-RS reception and the CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a periodic type, the duration is a time domain unit offset corresponding to a first CSI-RS resource set, wherein the first CSI-RS resource set and the CSI-RS resource set corresponding to the CSI-RS transmission correspond to the same serving cell or bandwidth part pair BWP pair, and the first CSI-RS resource set adopts a non-periodic type.
[0417] In the embodiment of the present application, the predefined duration determination method 3-2: implicit determination based on existing protocol provisions or high-level signaling
[0418] Different downlink receptions may implicitly determine their corresponding predefined durations based on the Timeline constants specified in their respective existing protocols or the Timeline parameters configured by high-level signaling.
[0419] For example, the predefined duration corresponding to each type of downlink reception can be determined based on the Timeline constant / parameter that dynamically triggers this type of downlink reception in the current Serving cell / BWP pair. Examples for various downlink receptions are as follows:
[0420] PDSCH Reception
[0421] The predefined duration may be the minimum value (or maximum value) of k0 or k0-r16 or k0-v1710 configured in the TDRA table associated / applied to the predefined DCI format (e.g., DCI format 1_0 / 1_1 / 1_2, which may be specified by the protocol or configured by high-level signaling), or minimumSchedulingOffsetK0-r16, in units of the Slot length determined based on the SCS corresponding to the PDSCH transmission. At this point, the starting time of applying the predefined duration may be adjusted accordingly to the PDSCH slot corresponding to the PDCCH slot where the DCI is located (assuming that the SCS of the PDCCH is configured as μ PDCCH , the SCS configuration of PDSCH is μ PDSCH , the terminal detects the DCI indicating Dynamic overriding in PDCCH slot n, and the starting time of the application predefined duration is ), or, the PDSCH slot that overlaps with the end time of the DCI (or the last PDSCH slot that overlaps with the PDCCH transmission where the DCI is located).
[0422] Non-Zero Power (NZP) CSI-RS Reception
[0423] When the NZP-CSI-RS-ResourceSet corresponding to the NZP CSI-RS reception is configured to adopt a non-periodic type, the aperiodicTriggeringOffset corresponding to this NZP-CSI-RS-ResourceSet can be directly applied. Otherwise, the aperiodicTriggeringOffset corresponding to the NZP-CSI-RS-ResourceSet configured for the same Serving cell / BWP pair of this terminal and adopting a non-periodic type can be used; when there are multiple NZP-CSI-RS-ResourceSets, the NZP-CSI-RS-ResourceSet with the smallest / largest nzp-CSI-ResourceSetId can be selected from them; when there is no NZP-CSI-RS-ResourceSet adopting a non-periodic type, the default value 0 can be used. At this time, the starting time of applying the predefined duration can be adjusted accordingly to the last DL slot overlapping with the PDCCH slot where the DCI is located, or the last DL slot overlapping with the PDCCH transmission where the DCI is located.
[0424] Through the above method and related embodiments, it can be ensured that after Dynamic SBFD is introduced or when Dynamic SBFD is deployed, downlink Preparation-related operations take into account the additional processing time required by the terminal for Dynamic SBFD-related operations, and the processing timing of Dynamic SBFD can be matched with the processing capabilities of different terminals as needed, thereby ensuring the practical feasibility of Dynamic SBFD and reducing the complexity requirements of the terminal.
[0425] It can be understood that when no new uplink transmission / downlink reception is scheduled / triggered during Dynamic overriding (for example, Dynamic overriding is indicated by UE specific non-scheduling DCI or Group common DCI), the above predefined duration can also be understood or described as the effectiveness delay of Dynamic overriding.
[0426] It can be understood that when the Timeline processing corresponding to Dynamic SBFD exists at the same time as other Timeline processing (for example, the Timeline processing corresponding to Intra-UE UCI multiplexing), the terminal can apply the corresponding Timeline processing for different operation aspects (for example, Dynamic SBFD related operations and Intra-UE UCI multiplexing related operations) respectively to meet the corresponding Timeline requirements at the same time.
[0427] In a possible implementation, the method further includes:
[0428] The terminal performs any one of the following (1) to (3):
[0429] (1) For any configured or scheduled PDSCH reception, the corresponding hybrid automatic repeat request response HARQ-ACK is fed back. If the PDSCH reception is not actually received, NACK is fed back for the PDSCH reception;
[0430] For configured or scheduled PDSCH reception, the terminal feeds back corresponding HARQ-ACK information; when a certain PDSCH reception is not actually received, the terminal feeds back NACK for this PDSCH reception.
[0431] (2) For any PDSCH reception for which the terminal determines to perform the preparation operation, the corresponding HARQ-ACK is fed back. If the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception;
[0432] For downlink reception that the terminal determines needs to be prepared (see the description in the previous text for details), the terminal feeds back corresponding HARQ-ACK information; when a certain PDSCH reception is not actually received, the terminal feeds back NACK for this PDSCH reception.
[0433] (3) For any PDSCH reception that the terminal actually receives, the corresponding HARQ-ACK is fed back; for any PDSCH reception that the terminal does not actually receive, the corresponding HARQ-ACK is not fed back.
[0434] For the PDSCH reception actually received by the terminal (including the case where the terminal does not discard / cancel the downlink reception in operation 1, and the corresponding case of operation 2), the terminal feeds back the corresponding HARQ-ACK information, otherwise the terminal does not feed back the corresponding HARQ-ACK information; the terminal determines the corresponding HARQ-ACK value based on the decoding situation of the PDSCH reception actually received, for example: if the PDSCH can be decoded correctly, the fed back HARQ-ACK value is set to ACK, and if the PDSCH can be decoded correctly, the fed back HARQ-ACK value is set to NACK.
[0435] See also Figure 4 , the embodiment of the present application provides a processing method, the execution subject of the method is a network side device, and the method includes:
[0436] Step 401: The network side device sends a first signaling to the terminal;
[0437] Step 402: The network side device determines a processing operation for a target uplink transmission or a processing operation for a target downlink reception of the terminal according to the first signaling;
[0438] Step 403: The network side device performs a corresponding receiving operation or sending operation according to the processing operation of the target uplink transmission or the processing operation of the target downlink reception of the terminal;
[0439] The first signaling is used to dynamically adjust the SBFD configuration.
[0440] It should be noted that the network side device, as the opposite side subject interacting with the terminal, should follow the same determination method and rules as the terminal for the judgment of the transmission processing operation, so as to ensure that the terminal side and the network side have the same understanding, and then ensure that the network side device can correctly perform the receiving operation or sending operation corresponding to the terminal side. Therefore, the content of the following scheme related to the network side device can be understood with reference to the description of the terminal side scheme above, and no further repetition will be given.
[0441] In a possible implementation manner, the network side device determines, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal, including any one of the following:
[0442] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the first condition, determining that the processing operation of the target uplink transmission of the terminal is to cancel the execution of the target uplink transmission;
[0443] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the second condition, determining the processing operation of the target uplink transmission of the terminal is a preparation operation for performing the target uplink transmission;
[0444] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the third condition, determining that the processing operation of the target downlink reception of the terminal is a preparation operation for performing the target downlink reception;
[0445] in,
[0446] The first situation includes at least one of the following:
[0447] In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment;
[0448] In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application;
[0449] The second situation includes at least one of the following:
[0450] In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment;
[0451] In the target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission;
[0452] In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on dynamic adjustment;
[0453] The third situation includes at least one of the following:
[0454] In the target time domain unit, at least one frequency domain resource that is unavailable for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment;
[0455] In the target time domain unit, the parameters that take effect based on dynamic adjustment are matched or compatible with the target downlink reception;
[0456] In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on dynamic adjustment.
[0457] In a possible implementation, the method further includes:
[0458] The network side device ensures that the starting time of the target downlink reception is not less than a third predefined time length from the third time reference point;
[0459] The third time reference point includes any of the following:
[0460] End time of the first signaling;
[0461] The end time of the CORESET or time domain unit of the first signaling is detected;
[0462] The determination of the third predefined duration includes any one of the following:
[0463] determining a third predefined duration based on the seventh parameter;
[0464] The third predefined duration is determined based on the type of target downlink reception and a predefined rule.
[0465] The processing method provided in the embodiment of the present application can be executed by a processing device. In the embodiment of the present application, the processing device provided in the embodiment of the present application is described by taking the processing method executed by the processing device as an example.
[0466] See also Figure 5 , an embodiment of the present application provides a processing device, which can be applied to a terminal, and the device includes:
[0467] The first receiving module 501 is used for the terminal to receive the first signaling from the network side device;
[0468] A first execution module 502, configured for the terminal to execute a processing operation of a target uplink transmission or a processing operation of a target downlink reception according to the first signaling;
[0469] The first signaling is used to dynamically adjust the SBFD configuration.
[0470] Optionally, the first execution module is specifically used for any of the following:
[0471] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies a first condition, performing a cancellation operation of the target uplink transmission;
[0472] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the second condition, performing the preparation operation for the target uplink transmission;
[0473] in,
[0474] The first situation includes at least one of the following:
[0475] In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment;
[0476] In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application;
[0477] The second situation includes at least one of the following:
[0478] In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment;
[0479] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission;
[0480] In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on the dynamic adjustment.
[0481] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the first condition, the dynamic adjustment includes at least one of the following:
[0482] Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be unavailable for uplink transmission;
[0483] Dynamically adjust the entire frequency domain range of the target uplink subband within the target time domain unit to be unavailable for uplink transmission;
[0484] Dynamically adjust part of the frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be unavailable for uplink transmission;
[0485] The parameters effective in the target time domain unit are dynamically adjusted to be incompatible with or incompatible with the parameters of the target uplink transmission.
[0486] Optionally, the first execution module is used to:
[0487] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission meets the first condition, performing a cancellation operation of the target uplink transmission;
[0488] The first condition includes at least one of the following:
[0489] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0490] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within the entire frequency domain range in which the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0491] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the uplink BWP is dynamically adjusted to be unavailable for uplink transmission;
[0492] The target uplink transmission parameters do not match or are incompatible with the dynamically effective parameters in the target time domain unit.
[0493] Optionally, the first execution module is used for at least one of the following:
[0494] When the target uplink transmission belongs to the first type of transmission, the terminal does not have a reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is less than a first predefined duration from a first time reference point, the target uplink transmission is not canceled;
[0495] When the target uplink transmission belongs to the first type of transmission, the terminal has no reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is greater than or equal to a first predefined time length from a first time reference point, cancel the target uplink transmission;
[0496] When the target uplink transmission belongs to the first type of transmission and the terminal reports a partial cancellation capability for the first type of transmission, canceling the transmission of the target uplink transmission within any time domain unit that is not less than a first predefined time length from the first time reference point;
[0497] In the case where the target uplink transmission belongs to the second type of transmission, canceling the transmission of the target uplink transmission within a time domain unit that is not less than a first predefined time length from the first time reference point and does not meet the second condition;
[0498] The second condition is that any frequency domain resource occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and the parameters actually effective in the target time domain unit match or are compatible with the parameters applied by the target uplink transmission during preparation;
[0499] The first time reference point includes any one of the following:
[0500] an end time of the first signaling;
[0501] Detecting an end time of a control resource set CORESET or a time domain unit of the first signaling;
[0502] The determination of the first predefined duration includes any one of the following:
[0503] Determine the first predefined duration based on the first parameter and the first offset;
[0504] Determine the first predefined duration based on a second parameter and a second offset;
[0505] Determining the first predefined duration based on a third parameter;
[0506] Among them, the first parameter is a preset preparation time length, the second parameter is a preset number of preparation time domain units, and the third parameter is different from the first parameter and the second parameter.
[0507] Optionally, determining the target offset includes any one of the following:
[0508] The value of the target offset is a single value specified by the protocol or pre-configured;
[0509] The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0510] The protocol specifies or preconfigures at least one first record, and determines a matching first record from the at least one first record, and uses the offset value corresponding to the matching first record as the value of the target offset, wherein each first record in the at least one first record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0511] The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value;
[0512] The target offset is any one of the following: the first offset, the second offset.
[0513] Optionally, determining the first predefined duration based on a third parameter includes any one of the following:
[0514] The first predefined duration is a single duration specified in the protocol or preconfigured;
[0515] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the first predefined duration;
[0516] The protocol stipulates or preconfigures at least one second record, and determines a matching second record from the at least one second record, and uses the duration corresponding to the matching second record as the first predefined duration, wherein each second record in the at least one second record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0517] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the first predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the first predefined duration is the default duration.
[0518] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the second condition, the dynamic adjustment includes at least one of the following:
[0519] Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be usable for uplink transmission;
[0520] Dynamically adjust the target time domain unit from a non-existent uplink subband to a present uplink subband;
[0521] Dynamically adjust the entire frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be available for uplink transmission;
[0522] Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target uplink transmission.
[0523] Optionally, the first execution module is used to:
[0524] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission satisfies a third condition, performing a preparation operation for the target uplink transmission;
[0525] The third condition includes at least one of the following:
[0526] The target uplink transmission belongs to an uplink transmission that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration;
[0527] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and at least one occupied frequency domain resource is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be usable for uplink transmission;
[0528] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and are located within the frequency domain range corresponding to the target uplink subband that exists or appears based on the dynamic adjustment of the SBFD configuration;
[0529] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission;
[0530] The target uplink transmission parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
[0531] Optionally, the first execution module is used for at least one of the following:
[0532] When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is less than a second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0533] When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, preparing the target uplink transmission;
[0534] When the target uplink transmission belongs to the fourth type of transmission and the start time of at least one time domain unit occupied by the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, performing a preparation operation for the target uplink transmission in the at least one time domain unit;
[0535] When the target uplink transmission belongs to the fourth type of transmission and the start time of any time domain unit occupied by the target uplink transmission is less than the second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0536] The second time reference point includes any one of the following:
[0537] an end time of the first signaling;
[0538] Detecting the end time of the CORESET or time domain unit of the first signaling;
[0539] The determination of the second predefined duration includes any one of the following:
[0540] Determine the second predefined duration based on a fourth parameter and a third offset;
[0541] Determine the second predefined duration based on the fifth parameter and the fourth offset;
[0542] Determining the second predefined duration based on a sixth parameter;
[0543] Determining the second predefined duration based on the type of the target uplink transmission and a predefined rule;
[0544] Among them, the fourth parameter is a preset preparation time length, the fifth parameter is a preset number of preparation time domain units, and the sixth parameter is different from the fourth parameter and the fifth parameter.
[0545] Optionally, determining the target offset includes any one of the following:
[0546] The value of the target offset is a single value specified by the protocol or pre-configured;
[0547] The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0548] The protocol specifies or preconfigures at least one third record, and determines a matching third record from the at least one third record, and uses the offset value corresponding to the matching third record as the value of the target offset, wherein each third record in the at least one third record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0549] The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value;
[0550] The target offset is any one of the following: the third offset, the fourth offset.
[0551] Optionally, the determining the second predefined duration based on the sixth parameter includes any one of the following:
[0552] The second predefined duration is a single duration specified in the protocol or preconfigured;
[0553] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the second predefined duration;
[0554] The protocol stipulates or preconfigures at least one fourth record, and determines a matching fourth record from the at least one fourth record, and uses the duration corresponding to the matching fourth record as the second predefined duration, wherein each fourth record in the at least one fourth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0555] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the second predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the second predefined duration is the default duration.
[0556] Optionally, the determining the second predefined duration based on the type of the target uplink transmission and a predefined rule includes any one of the following:
[0557] In the case where the target uplink transmission is a PUSCH transmission, the second predefined duration is any one of the following: a minimum value or a maximum value of a first scheduling offset configured in a time domain resource allocation table TDRAtable associated with a predefined downlink control information format DCI format, and a configured first minimum scheduling offset;
[0558] In the case where the target uplink transmission is PUCCH transmission, the second predefined duration is the minimum value or maximum value of the time domain feedback offset configured in the time domain feedback offset set associated with the predefined DCI format;
[0559] When the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a non-periodic type, the second predefined duration is a time domain unit offset corresponding to the SRS resource set;
[0560] In a case where the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a periodic type, the second predefined duration is a time domain unit offset corresponding to a first SRS resource set, wherein the first SRS resource set and the SRS resource set corresponding to the SRS transmission correspond to the same serving cell Servingcell or the same bandwidth part pair BWP pair, and the first SRS resource set adopts a non-periodic type;
[0561] In the case where the target uplink transmission is a PRACH transmission, the second predefined duration is the minimum duration between the last time domain unit carrying the PDCCH command and the first time domain unit of the first PRACH transmission, wherein the first PRACH transmission corresponds to the PDCCH command.
[0562] Optionally, the first execution module is used to:
[0563] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, performing the preparation operation for the target downlink reception;
[0564] The third situation includes at least one of the following:
[0565] In the target time domain unit, at least one frequency domain resource that was not available for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment;
[0566] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target downlink reception;
[0567] In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on the dynamic adjustment.
[0568] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the third condition, the dynamic adjustment includes at least one of the following:
[0569] Dynamically adjust a portion of the frequency domain range of a target downlink subband within a target time domain unit to be usable for downlink reception;
[0570] Dynamically adjust the target time domain unit from a non-existent downlink subband to a present downlink subband;
[0571] Dynamically adjust the entire frequency domain range of the downlink BWP in the target time domain unit to be available for downlink reception;
[0572] Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target downlink transmission.
[0573] Optionally, the first execution module is used to:
[0574] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target downlink reception satisfies a fourth condition, performing a preparation operation for the target downlink reception;
[0575] The fourth condition includes at least one of the following:
[0576] The target downlink reception belongs to a downlink reception that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration;
[0577] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception, and at least one occupied frequency domain resource is located within a partial frequency domain range in which a downlink subband is dynamically adjusted to be used for downlink reception;
[0578] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception and are located within the frequency domain range corresponding to the downlink subband that exists or appears based on the dynamic adjustment of the SBFD configuration;
[0579] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception;
[0580] The target downlink received parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
[0581] Optionally, the first execution module is used to:
[0582] When the start time of the target downlink reception is less than a third predefined time length from the third time reference point, performing the first operation;
[0583] When the start time of the target downlink reception is greater than or equal to a third predefined time length from the third time reference point, performing a second operation;
[0584] The terminal expects that the start time of the target downlink reception is not less than a third predefined time length from the third time reference point;
[0585] The first operation includes any one of the following:
[0586] In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling or triggering is invalid, and the dynamic adjustment of the SBFD configuration fails;
[0587] In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling is valid, but the dynamic adjustment of the SBFD configuration is not effective;
[0588] In a case where the target downlink reception is not scheduled or triggered by the first signaling, determining that the dynamic adjustment of SBFD is effective, and discarding or canceling the target downlink reception;
[0589] The second operation includes:
[0590] Determining that the dynamic adjustment of SBFD is effective and preparing the target downlink reception;
[0591] The third time reference point includes any one of the following:
[0592] an end time of the first signaling;
[0593] Detecting the end time of the CORESET or time domain unit of the first signaling;
[0594] The determination of the third predefined duration includes any one of the following:
[0595] Determining the third predefined duration based on a seventh parameter;
[0596] The third predefined duration is determined based on the type of the target downlink reception and a predefined rule.
[0597] Optionally, determining the third predefined duration based on the seventh parameter includes any one of the following:
[0598] The third predefined duration is a single duration specified in the protocol or preconfigured;
[0599] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the third predefined duration;
[0600] The protocol stipulates or preconfigures at least one fifth record, and determines a matching fifth record from the at least one fifth record, and uses the duration corresponding to the matching fifth record as the third predefined duration, wherein each fifth record in the at least one fifth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0601] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the third predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the third predefined duration is the default duration.
[0602] Optionally, the determining the third predefined duration based on the type of the target downlink reception and a predefined rule includes any one of the following:
[0603] In the case where the target downlink reception is PDSCH reception, the duration is any one of the following: a minimum value or a maximum value of a second scheduling offset configured in a TDRA table associated with a predefined DCI format, and a configured second minimum scheduling offset;
[0604] When the target downlink reception is CSI-RS reception and a CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a non-periodic type, the duration is a time domain unit offset corresponding to the CSI-RS resource set;
[0605] When the target downlink reception is CSI-RS reception and the CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a periodic type, the duration is a time domain unit offset corresponding to a first CSI-RS resource set, wherein the first CSI-RS resource set and the CSI-RS resource set corresponding to the CSI-RS transmission correspond to the same serving cell or bandwidth part pair BWP pair, and the first CSI-RS resource set adopts a non-periodic type.
[0606] Optionally, the device further comprises:
[0607] The third execution module is used for the terminal to execute any one of the following:
[0608] For any configured or scheduled PDSCH reception, a corresponding hybrid automatic repeat request response HARQ-ACK is fed back. If the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception;
[0609] For any PDSCH reception determined by the terminal to perform a preparation operation, a corresponding HARQ-ACK is fed back, and if the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception;
[0610] For any PDSCH reception actually received by the terminal, the corresponding HARQ-ACK is fed back, and for any PDSCH reception not actually received by the terminal, the corresponding HARQ-ACK is not fed back.
[0611] See also Figure 6 , an embodiment of the present application provides a processing device, which can be applied to a network side device, and the device includes:
[0612] A sending module 601 is used for a network side device to send a first signaling to a terminal;
[0613] A determination module 602 is used for the network side device to determine a processing operation for a target uplink transmission or a processing operation for a target downlink reception of the terminal according to the first signaling;
[0614] A second execution module 603 is used for the network side device to perform a corresponding receiving operation or sending operation according to the processing operation of the target uplink transmission or the processing operation of the target downlink reception of the terminal;
[0615] The first signaling is used to dynamically adjust the SBFD configuration.
[0616] Optionally, the second execution module is used for any of the following:
[0617] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the first condition, determining that the processing operation of the target uplink transmission of the terminal is to execute a cancellation operation of the target uplink transmission;
[0618] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the second condition, determining that the processing operation of the target uplink transmission of the terminal is a preparation operation for performing the target uplink transmission;
[0619] When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the third condition, determining the processing operation of the target downlink reception of the terminal as a preparation operation for performing the target downlink reception;
[0620] in,
[0621] The first situation includes at least one of the following:
[0622] In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment;
[0623] In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application;
[0624] The second situation includes at least one of the following:
[0625] In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment;
[0626] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission;
[0627] In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on the dynamic adjustment;
[0628] The third situation includes at least one of the following:
[0629] In the target time domain unit, at least one frequency domain resource that was not available for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment;
[0630] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target downlink reception;
[0631] In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on the dynamic adjustment.
[0632] Optionally, the device further comprises:
[0633] A fourth execution module, used for the network side device to ensure that the starting time of the target downlink reception is not less than a third predefined time length from the third time reference point;
[0634] The third time reference point includes any one of the following:
[0635] an end time of the first signaling;
[0636] Detecting the end time of the CORESET or time domain unit of the first signaling;
[0637] The determination of the third predefined duration includes any one of the following:
[0638] Determining the third predefined duration based on a seventh parameter;
[0639] The third predefined duration is determined based on the type of the target downlink reception and a predefined rule.
[0640] The processing device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices other than a terminal. For example, the terminal may include but is not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0641] The processing device provided in the embodiment of the present application can achieve Figures 2 to 4 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0642] like Figure 7 As shown, the embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702, and the memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction is executed by the processor 701 to implement the various steps of the above method embodiment, and can achieve the same technical effect. When the communication device 700 is a network side device, the program or instruction is executed by the processor 701 to implement the various steps of the above method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0643] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the above-mentioned terminal side method embodiment. The terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, Figure 8 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0644] The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of a processor 810.
[0645] Those skilled in the art will appreciate that the terminal 800 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 810 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0646] It should be understood that in the embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0647] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 801 can transmit the data to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network side device. Generally, the radio frequency unit 801 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0648] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 809 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0649] The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 810.
[0650] The radio frequency unit 801 is used for the terminal to receive the first signaling from the network side device;
[0651] Processor 810, configured for the terminal to perform a processing operation of target uplink transmission or a processing operation of target downlink reception according to the first signaling;
[0652] The first signaling is used to dynamically adjust the SBFD configuration.
[0653] Optionally, the processor 810 is configured to perform any of the following:
[0654] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies a first condition, performing a cancellation operation of the target uplink transmission;
[0655] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the second condition, performing the preparation operation for the target uplink transmission;
[0656] in,
[0657] The first situation includes at least one of the following:
[0658] In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment;
[0659] In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application;
[0660] The second situation includes at least one of the following:
[0661] In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment;
[0662] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission;
[0663] In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on the dynamic adjustment.
[0664] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the first condition, the dynamic adjustment includes at least one of the following:
[0665] Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be unavailable for uplink transmission;
[0666] Dynamically adjust the entire frequency domain range of the target uplink subband within the target time domain unit to be unavailable for uplink transmission;
[0667] Dynamically adjust part of the frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be unavailable for uplink transmission;
[0668] The parameters effective in the target time domain unit are dynamically adjusted to be incompatible with or incompatible with the parameters of the target uplink transmission.
[0669] Optionally, the processor 810 is configured to:
[0670] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission meets the first condition, performing a cancellation operation of the target uplink transmission;
[0671] The first condition includes at least one of the following:
[0672] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0673] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within the entire frequency domain range in which the target uplink subband is dynamically adjusted to be unavailable for uplink transmission;
[0674] At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the uplink BWP is dynamically adjusted to be unavailable for uplink transmission;
[0675] The target uplink transmission parameters do not match or are incompatible with the dynamically effective parameters in the target time domain unit.
[0676] Optionally, the processor 810 is configured to perform at least one of the following:
[0677] When the target uplink transmission belongs to the first type of transmission, the terminal does not have a reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is less than a first predefined duration from a first time reference point, the target uplink transmission is not canceled;
[0678] When the target uplink transmission belongs to the first type of transmission, the terminal has no reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is greater than or equal to a first predefined time length from a first time reference point, cancel the target uplink transmission;
[0679] When the target uplink transmission belongs to the first type of transmission and the terminal reports a partial cancellation capability for the first type of transmission, canceling the transmission of the target uplink transmission within any time domain unit that is not less than a first predefined time length from the first time reference point;
[0680] In the case where the target uplink transmission belongs to the second type of transmission, canceling the transmission of the target uplink transmission within a time domain unit that is not less than a first predefined time length from the first time reference point and does not meet the second condition;
[0681] The second condition is that any frequency domain resource occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and the parameters actually effective in the target time domain unit match or are compatible with the parameters applied by the target uplink transmission during preparation;
[0682] The first time reference point includes any one of the following:
[0683] an end time of the first signaling;
[0684] Detecting an end time of a control resource set CORESET or a time domain unit of the first signaling;
[0685] The determination of the first predefined duration includes any one of the following:
[0686] Determine the first predefined duration based on the first parameter and the first offset;
[0687] Determine the first predefined duration based on a second parameter and a second offset;
[0688] Determining the first predefined duration based on a third parameter;
[0689] Among them, the first parameter is a preset preparation time length, the second parameter is a preset number of preparation time domain units, and the third parameter is different from the first parameter and the second parameter.
[0690] Optionally, determining the target offset includes any one of the following:
[0691] The value of the target offset is a single value specified by the protocol or pre-configured;
[0692] The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0693] The protocol specifies or preconfigures at least one first record, and determines a matching first record from the at least one first record, and uses the offset value corresponding to the matching first record as the value of the target offset, wherein each first record in the at least one first record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0694] The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value;
[0695] The target offset is any one of the following: the first offset, the second offset.
[0696] Optionally, determining the first predefined duration based on a third parameter includes any one of the following:
[0697] The first predefined duration is a single duration specified in the protocol or preconfigured;
[0698] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the first predefined duration;
[0699] The protocol stipulates or preconfigures at least one second record, and determines a matching second record from the at least one second record, and uses the duration corresponding to the matching second record as the first predefined duration, wherein each second record in the at least one second record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0700] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the first predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the first predefined duration is the default duration.
[0701] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the second condition, the dynamic adjustment includes at least one of the following:
[0702] Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be usable for uplink transmission;
[0703] Dynamically adjust the target time domain unit from a non-existent uplink subband to a present uplink subband;
[0704] Dynamically adjust the entire frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be available for uplink transmission;
[0705] Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target uplink transmission.
[0706] Optionally, the processor 810 is configured to:
[0707] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission satisfies a third condition, performing a preparation operation for the target uplink transmission;
[0708] The third condition includes at least one of the following:
[0709] The target uplink transmission belongs to an uplink transmission that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration;
[0710] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and at least one occupied frequency domain resource is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be usable for uplink transmission;
[0711] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and are located within the frequency domain range corresponding to the target uplink subband that exists or appears based on the dynamic adjustment of the SBFD configuration;
[0712] All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission;
[0713] The target uplink transmission parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
[0714] Optionally, the processor 810 is configured to perform at least one of the following:
[0715] When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is less than a second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0716] When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, preparing the target uplink transmission;
[0717] When the target uplink transmission belongs to the fourth type of transmission and the start time of at least one time domain unit occupied by the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, performing a preparation operation for the target uplink transmission in the at least one time domain unit;
[0718] When the target uplink transmission belongs to the fourth type of transmission and the start time of any time domain unit occupied by the target uplink transmission is less than the second predefined time length from the second time reference point, the target uplink transmission is not prepared;
[0719] The second time reference point includes any one of the following:
[0720] an end time of the first signaling;
[0721] Detecting the end time of the CORESET or time domain unit of the first signaling;
[0722] The determination of the second predefined duration includes any one of the following:
[0723] Determine the second predefined duration based on a fourth parameter and a third offset;
[0724] Determine the second predefined duration based on the fifth parameter and the fourth offset;
[0725] Determining the second predefined duration based on a sixth parameter;
[0726] Determining the second predefined duration based on the type of the target uplink transmission and a predefined rule;
[0727] Among them, the fourth parameter is a preset preparation time length, the fifth parameter is a preset number of preparation time domain units, and the sixth parameter is different from the fourth parameter and the fifth parameter.
[0728] Optionally, determining the target offset includes any one of the following:
[0729] The value of the target offset is a single value specified by the protocol or pre-configured;
[0730] The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset;
[0731] The protocol specifies or preconfigures at least one third record, and determines a matching third record from the at least one third record, and uses the offset value corresponding to the matching third record as the value of the target offset, wherein each third record in the at least one third record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value;
[0732] The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value;
[0733] The target offset is any one of the following: the third offset, the fourth offset.
[0734] Optionally, the determining the second predefined duration based on the sixth parameter includes any one of the following:
[0735] The second predefined duration is a single duration specified in the protocol or preconfigured;
[0736] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the second predefined duration;
[0737] The protocol stipulates or preconfigures at least one fourth record, and determines a matching fourth record from the at least one fourth record, and uses the duration corresponding to the matching fourth record as the second predefined duration, wherein each fourth record in the at least one fourth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0738] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the second predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the second predefined duration is the default duration.
[0739] Optionally, the determining the second predefined duration based on the type of the target uplink transmission and a predefined rule includes any one of the following:
[0740] In the case where the target uplink transmission is PUSCH transmission, the second predefined duration is any one of the following: a minimum value or a maximum value of a first scheduling offset configured in a time domain resource allocation table TDRA table associated with a predefined downlink control information format DCI format, and a configured first minimum scheduling offset;
[0741] In the case where the target uplink transmission is PUCCH transmission, the second predefined duration is the minimum value or maximum value of the time domain feedback offset configured in the time domain feedback offset set associated with the predefined DCI format;
[0742] When the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a non-periodic type, the second predefined duration is a time domain unit offset corresponding to the SRS resource set;
[0743] In a case where the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a periodic type, the second predefined duration is a time domain unit offset corresponding to a first SRS resource set, wherein the first SRS resource set and the SRS resource set corresponding to the SRS transmission correspond to the same serving cell Servingcell or the same bandwidth part pair BWP pair, and the first SRS resource set adopts a non-periodic type;
[0744] In the case where the target uplink transmission is a PRACH transmission, the second predefined duration is the minimum duration between the last time domain unit carrying the PDCCH command and the first time domain unit of the first PRACH transmission, wherein the first PRACH transmission corresponds to the PDCCH command.
[0745] Optionally, the processor 810 is configured to:
[0746] When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, performing the preparation operation for the target downlink reception;
[0747] The third situation includes at least one of the following:
[0748] In the target time domain unit, at least one frequency domain resource that was not available for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment;
[0749] In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target downlink reception;
[0750] In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on the dynamic adjustment.
[0751] Optionally, when the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the third condition, the dynamic adjustment includes at least one of the following:
[0752] Dynamically adjust a portion of the frequency domain range of a target downlink subband within a target time domain unit to be usable for downlink reception;
[0753] Dynamically adjust the target time domain unit from a non-existent downlink subband to a present downlink subband;
[0754] Dynamically adjust the entire frequency domain range of the downlink BWP in the target time domain unit to be available for downlink reception;
[0755] Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target downlink transmission.
[0756] Optionally, the processor 810 is configured to:
[0757] After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target downlink reception satisfies a fourth condition, performing a preparation operation for the target downlink reception;
[0758] The fourth condition includes at least one of the following:
[0759] The target downlink reception belongs to a downlink reception that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration;
[0760] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception, and at least one occupied frequency domain resource is located within a partial frequency domain range in which a downlink subband is dynamically adjusted to be used for downlink reception;
[0761] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception and are located within the frequency domain range corresponding to the downlink subband that exists or appears based on the dynamic adjustment of the SBFD configuration;
[0762] All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception;
[0763] The target downlink received parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
[0764] Optionally, the processor 810 is configured to:
[0765] When the start time of the target downlink reception is less than a third predefined time length from the third time reference point, performing the first operation;
[0766] When the start time of the target downlink reception is greater than or equal to a third predefined time length from the third time reference point, performing a second operation;
[0767] The terminal expects that the start time of the target downlink reception is not less than a third predefined time length from the third time reference point;
[0768] The first operation includes any one of the following:
[0769] In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling or triggering is invalid, and the dynamic adjustment of the SBFD configuration fails;
[0770] In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling is valid, but the dynamic adjustment of the SBFD configuration is not effective;
[0771] In a case where the target downlink reception is not scheduled or triggered by the first signaling, determining that the dynamic adjustment of SBFD is effective, and discarding or canceling the target downlink reception;
[0772] The second operation includes:
[0773] Determining that the dynamic adjustment of SBFD is effective and preparing the target downlink reception;
[0774] The third time reference point includes any one of the following:
[0775] an end time of the first signaling;
[0776] Detecting the end time of the CORESET or time domain unit of the first signaling;
[0777] The determination of the third predefined duration includes any one of the following:
[0778] Determining the third predefined duration based on a seventh parameter;
[0779] The third predefined duration is determined based on the type of the target downlink reception and a predefined rule.
[0780] Optionally, determining the third predefined duration based on the seventh parameter includes any one of the following:
[0781] The third predefined duration is a single duration specified in the protocol or preconfigured;
[0782] The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the third predefined duration;
[0783] The protocol stipulates or preconfigures at least one fifth record, and determines a matching fifth record from the at least one fifth record, and uses the duration corresponding to the matching fifth record as the third predefined duration, wherein each fifth record in the at least one fifth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration;
[0784] The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the third predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the third predefined duration is the default duration.
[0785] Optionally, the determining the third predefined duration based on the type of the target downlink reception and a predefined rule includes any one of the following:
[0786] In the case where the target downlink reception is PDSCH reception, the duration is any one of the following: a minimum value or a maximum value of a second scheduling offset configured in a TDRA table associated with a predefined DCI format, and a configured second minimum scheduling offset;
[0787] When the target downlink reception is CSI-RS reception and a CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a non-periodic type, the duration is a time domain unit offset corresponding to the CSI-RS resource set;
[0788] When the target downlink reception is CSI-RS reception and the CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a periodic type, the duration is a time domain unit offset corresponding to a first CSI-RS resource set, wherein the first CSI-RS resource set and the CSI-RS resource set corresponding to the CSI-RS transmission correspond to the same serving cell or bandwidth part pair BWP pair, and the first CSI-RS resource set adopts a non-periodic type.
[0789] Optionally, the processor 810 is configured for the terminal to perform any one of the following:
[0790] For any configured or scheduled PDSCH reception, a corresponding hybrid automatic repeat request response HARQ-ACK is fed back. If the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception;
[0791] For any PDSCH reception determined by the terminal to perform a preparation operation, a corresponding HARQ-ACK is fed back, and if the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception;
[0792] For any PDSCH reception actually received by the terminal, the corresponding HARQ-ACK is fed back, and for any PDSCH reception not actually received by the terminal, the corresponding HARQ-ACK is not fed back.
[0793] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.
[0794] The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the above network side method embodiment. The network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.
[0795] Specifically, the embodiment of the present application also provides a network side device. Fig. 9 As shown, the network side device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94 and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92. The radio frequency device 92 processes the received information and sends it out through the antenna 91.
[0796] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93, which includes a baseband processor.
[0797] The baseband device 93 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig. 9 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 to execute the network device operations shown in the above method embodiment.
[0798] The network side device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).
[0799] Specifically, the network side device 900 of the embodiment of the present invention further includes: instructions or programs stored in the memory 95 and executable on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute. Figure 6 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0800] Specifically, the embodiment of the present application also provides a network side device. Fig.10 As shown, the network side device 1000 includes: a processor 1001, a network interface 1002 and a memory 1003. The network interface 1002 is, for example, a common public radio interface (CPRI).
[0801] Specifically, the network side device 1000 of the embodiment of the present invention further includes: an instruction or program stored in the memory 1003 and executable on the processor 1001, and the processor 1001 calls the instruction or program in the memory 1003 to execute Figure 6 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0802] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0803] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.
[0804] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0805] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0806] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described here.
[0807] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the terminal side method described above, and the network side device can be used to execute the steps of the network side method described above.
[0808] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also 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 one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0809] 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 a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.
[0810] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A processing method, characterized in that: include: The terminal receives a first signaling from a network side device; The terminal performs a processing operation of target uplink transmission or a processing operation of target downlink reception according to the first signaling; The first signaling is used to dynamically adjust the sub-band full-duplex SBFD configuration.
2. The method according to claim 1, characterized in that The terminal performs a target uplink transmission processing operation according to the first signaling, including any one of the following: When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies a first condition, performing a cancellation operation of the target uplink transmission; When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the second condition, performing the preparation operation for the target uplink transmission; in, The first situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment; In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application; The second situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment; In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission; In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on the dynamic adjustment.
3. The method according to claim 2, characterized in that When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the first condition, the dynamic adjustment includes at least one of the following: Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be unavailable for uplink transmission; Dynamically adjust the entire frequency domain range of the target uplink subband within the target time domain unit to be unavailable for uplink transmission; Dynamically adjust part of the frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be unavailable for uplink transmission; The parameters effective in the target time domain unit are dynamically adjusted to be incompatible with or incompatible with the parameters of the target uplink transmission.
4. The method according to claim 1, characterized in that The terminal performs a processing operation of target uplink transmission according to the first signaling, including: After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission meets the first condition, performing a cancellation operation of the target uplink transmission; The first condition includes at least one of the following: At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be unavailable for uplink transmission; At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within the entire frequency domain range in which the target uplink subband is dynamically adjusted to be unavailable for uplink transmission; At least one frequency domain resource occupied by the target uplink transmission in the target time domain unit is located within a partial frequency domain range where the uplink BWP is dynamically adjusted to be unavailable for uplink transmission; The target uplink transmission parameters do not match or are incompatible with the dynamically effective parameters in the target time domain unit.
5. The method according to any one of claims 2 to 4, characterized in that: The canceling operation of executing the target uplink transmission includes at least one of the following: When the target uplink transmission belongs to the first type of transmission, the terminal does not have a reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is less than a first predefined duration from a first time reference point, the target uplink transmission is not canceled; When the target uplink transmission belongs to the first type of transmission, the terminal has no reporting partial cancellation capability for the first type of transmission, and the start time of the target uplink transmission is greater than or equal to a first predefined time length from a first time reference point, cancel the target uplink transmission; When the target uplink transmission belongs to the first type of transmission and the terminal reports a partial cancellation capability for the first type of transmission, canceling the transmission of the target uplink transmission within any time domain unit that is not less than a first predefined time length from the first time reference point; In the case where the target uplink transmission belongs to the second type of transmission, canceling the transmission of the target uplink transmission within a time domain unit that is not less than a first predefined time length from the first time reference point and does not meet the second condition; The second condition is that any frequency domain resource occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and the parameters actually effective in the target time domain unit match or are compatible with the parameters applied by the target uplink transmission during preparation; The first time reference point includes any one of the following: an end time of the first signaling; Detecting an end time of a control resource set CORESET or a time domain unit of the first signaling; The determination of the first predefined duration includes any one of the following: Determine the first predefined duration based on the first parameter and the first offset; Determine the first predefined duration based on a second parameter and a second offset; Determining the first predefined duration based on a third parameter; Among them, the first parameter is a preset preparation time length, the second parameter is a preset number of preparation time domain units, and the third parameter is different from the first parameter and the second parameter.
6. The method according to claim 5, characterized in that Determination of the target offset includes any of the following: The value of the target offset is a single value specified by the protocol or pre-configured; The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset; The protocol specifies or preconfigures at least one first record, and determines a matching first record from the at least one first record, and uses the offset value corresponding to the matching first record as the value of the target offset, wherein each first record in the at least one first record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value; The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value; The target offset is any one of the following: the first offset, the second offset.
7. The method according to claim 5, characterized in that The determining the first predefined duration based on the third parameter includes any one of the following: The first predefined duration is a single duration specified in the protocol or preconfigured; The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the first predefined duration; The protocol stipulates or preconfigures at least one second record, and determines a matching second record from the at least one second record, and uses the duration corresponding to the matching second record as the first predefined duration, wherein each second record in the at least one second record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration; The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the first predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the first predefined duration is the default duration.
8. The method according to claim 2, characterized in that: When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling meets the second condition, the dynamic adjustment includes at least one of the following: Dynamically adjust a portion of the frequency domain range of a target uplink subband within a target time domain unit to be usable for uplink transmission; Dynamically adjust the target time domain unit from a non-existent uplink subband to a present uplink subband; Dynamically adjust the entire frequency domain range of the uplink bandwidth part BWP within the target time domain unit to be available for uplink transmission; Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target uplink transmission.
9. The method according to claim 1, characterized in that: The terminal performs a processing operation of target uplink transmission according to the first signaling, including: After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target uplink transmission satisfies a third condition, performing a preparation operation for the target uplink transmission; The third condition includes at least one of the following: The target uplink transmission belongs to an uplink transmission that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration; All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and at least one occupied frequency domain resource is located within a partial frequency domain range where the target uplink subband is dynamically adjusted to be usable for uplink transmission; All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission, and are located within the frequency domain range corresponding to the target uplink subband that exists or appears based on the dynamic adjustment of the SBFD configuration; All frequency domain resources occupied by the target uplink transmission in the target time domain unit can be used for uplink transmission; The target uplink transmission parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
10. The method according to claim 8 or 9, characterized in that: The preparation operation for performing the target uplink transmission includes at least one of the following: When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is less than a second predefined time length from the second time reference point, the target uplink transmission is not prepared; When the target uplink transmission belongs to the third type of transmission and the start time of the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, preparing the target uplink transmission; When the target uplink transmission belongs to the fourth type of transmission and the start time of at least one time domain unit occupied by the target uplink transmission is greater than or equal to a second predefined time length from the second time reference point, performing a preparation operation for the target uplink transmission in the at least one time domain unit; When the target uplink transmission belongs to the fourth type of transmission and the start time of any time domain unit occupied by the target uplink transmission is less than the second predefined time length from the second time reference point, the target uplink transmission is not prepared; The second time reference point includes any one of the following: an end time of the first signaling; Detecting the end time of the CORESET or time domain unit of the first signaling; The determination of the second predefined duration includes any one of the following: Determine the second predefined duration based on a fourth parameter and a third offset; Determine the second predefined duration based on the fifth parameter and the fourth offset; Determining the second predefined duration based on a sixth parameter; Determining the second predefined duration based on the type of the target uplink transmission and a predefined rule; Among them, the fourth parameter is a preset preparation time length, the fifth parameter is a preset number of preparation time domain units, and the sixth parameter is different from the fourth parameter and the fifth parameter.
11. The method according to claim 10, characterized in that Determination of the target offset includes any of the following: The value of the target offset is a single value specified by the protocol or pre-configured; The protocol specifies or preconfigures at least one value, and the indication information carrying the first signaling indicates one of the at least one value as the value of the target offset; The protocol specifies or preconfigures at least one third record, and determines a matching third record from the at least one third record, and uses the offset value corresponding to the matching third record as the value of the target offset, wherein each third record in the at least one third record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to an offset value; The protocol stipulates or preconfigures at least one target parameter, and when the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the value of the target offset is a predefined value, and when the value of the at least one target parameter does not change based on the dynamic adjustment, the value of the target offset is a default value; The target offset is any one of the following: the third offset, the fourth offset.
12. The method according to claim 10, characterized in that The determining the second predefined duration based on the sixth parameter includes any one of the following: The second predefined duration is a single duration specified in the protocol or preconfigured; The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the second predefined duration; The protocol stipulates or preconfigures at least one fourth record, and determines a matching fourth record from the at least one fourth record, and uses the duration corresponding to the matching fourth record as the second predefined duration, wherein each fourth record in the at least one fourth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration; The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the second predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the second predefined duration is the default duration.
13. The method according to claim 10, characterized in that The determining the second predefined duration based on the type of the target uplink transmission and a predefined rule includes any one of the following: In the case where the target uplink transmission is a PUSCH transmission, the second predefined duration is any one of the following: a minimum value or a maximum value of a first scheduling offset configured in a time domain resource allocation table TDRAtable associated with a predefined downlink control information format DCI format, and a configured first minimum scheduling offset; In the case where the target uplink transmission is PUCCH transmission, the second predefined duration is the minimum value or maximum value of the time domain feedback offset configured in the time domain feedback offset set associated with the predefined DCI format; When the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a non-periodic type, the second predefined duration is a time domain unit offset corresponding to the SRS resource set; In a case where the target uplink transmission is SRS transmission and the SRS resource set corresponding to the SRS transmission is configured to adopt a periodic type, the second predefined duration is a time domain unit offset corresponding to a first SRS resource set, wherein the first SRS resource set and the SRS resource set corresponding to the SRS transmission correspond to the same serving cell or the same bandwidth part pair BWP pair, and the first SRS resource set adopts a non-periodic type; In the case where the target uplink transmission is a PRACH transmission, the second predefined duration is the minimum duration between the last time domain unit carrying the PDCCH command and the first time domain unit of the first PRACH transmission, wherein the first PRACH transmission corresponds to the PDCCH command.
14. The method according to claim 1, characterized in that The terminal performs a target downlink reception processing operation according to the first signaling, including: When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, performing the preparation operation for the target downlink reception; The third situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that was not available for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment; In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target downlink reception; In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on the dynamic adjustment.
15. The method according to claim 14, characterized in that When the dynamic adjustment of the SBFD configuration by the terminal according to the first signaling satisfies the third condition, the dynamic adjustment includes at least one of the following: Dynamically adjust a portion of the frequency domain range of a target downlink subband within a target time domain unit to be usable for downlink reception; Dynamically adjust the target time domain unit from a non-existent downlink subband to a present downlink subband; Dynamically adjust the entire frequency domain range of the downlink BWP in the target time domain unit to be available for downlink reception; Dynamically adjust the parameters effective in the target time domain unit to match or be compatible with the parameters of the target downlink transmission.
16. The method according to claim 1, characterized in that The terminal performs a processing operation of target uplink transmission according to the first signaling, including: After the terminal dynamically adjusts the SBFD configuration according to the first signaling, if the target downlink reception satisfies a fourth condition, performing a preparation operation for the target downlink reception; The fourth condition includes at least one of the following: The target downlink reception belongs to a downlink reception that is newly scheduled or newly triggered while dynamically adjusting the SBFD configuration; All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception, and at least one occupied frequency domain resource is located within a partial frequency domain range in which a downlink subband is dynamically adjusted to be used for downlink reception; All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception and are located within the frequency domain range corresponding to the downlink subband that exists or appears based on the dynamic adjustment of the SBFD configuration; All frequency domain resources occupied by the target downlink reception in the target time domain unit can be used for downlink reception; The target downlink received parameters match or are compatible with the dynamically effective parameters in the target time domain unit.
17. The method according to any one of claims 14 to 16, characterized in that The preparation operation for performing the target downlink reception includes at least one of the following: When the start time of the target downlink reception is less than a third predefined time length from the third time reference point, performing the first operation; When the start time of the target downlink reception is greater than or equal to a third predefined time length from the third time reference point, performing a second operation; The terminal expects that the start time of the target downlink reception is not less than a third predefined time length from the third time reference point; The first operation includes any one of the following: In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling or triggering is invalid, and the dynamic adjustment of the SBFD configuration fails; In a case where the target downlink reception is scheduled or triggered by the first signaling, determining that the scheduling is valid, but the dynamic adjustment of the SBFD configuration is not effective; In a case where the target downlink reception is not scheduled or triggered by the first signaling, determining that the dynamic adjustment of SBFD is effective, and discarding or canceling the target downlink reception; The second operation includes: Determining that the dynamic adjustment of SBFD is effective and preparing the target downlink reception; The third time reference point includes any one of the following: an end time of the first signaling; Detecting the end time of the CORESET or time domain unit of the first signaling; The determination of the third predefined duration includes any one of the following: Determining the third predefined duration based on a seventh parameter; The third predefined duration is determined based on the type of the target downlink reception and a predefined rule.
18. The method according to claim 17, characterized in that The determining the third predefined duration based on the seventh parameter includes any one of the following: The third predefined duration is a single duration specified in the protocol or preconfigured; The protocol stipulates or preconfigures at least one duration, and the indication information carrying the first signaling indicates one of the at least one duration as the third predefined duration; The protocol stipulates or preconfigures at least one fifth record, and determines a matching fifth record from the at least one fifth record, and uses the duration corresponding to the matching fifth record as the third predefined duration, wherein each fifth record in the at least one fifth record corresponds to a source time domain unit type and a target time domain unit type, and corresponds to a duration; The protocol stipulates or pre-configures at least one target parameter. When the value of at least one of the at least one target parameter changes based on the dynamic adjustment, the third predefined duration is the target duration. When the value of at least one target parameter does not change based on the dynamic adjustment, the third predefined duration is the default duration.
19. The method according to claim 17, characterized in that The determining the third predefined duration based on the type of the target downlink reception and a predefined rule includes any one of the following: In the case where the target downlink reception is PDSCH reception, the duration is any one of the following: a minimum value or a maximum value of a second scheduling offset configured in a TDRA table associated with a predefined DCIformat, a configured second minimum scheduling offset; When the target downlink reception is CSI-RS reception and a CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a non-periodic type, the duration is a time domain unit offset corresponding to the CSI-RS resource set; When the target downlink reception is CSI-RS reception and the CSI-RS resource set corresponding to the CSI-RS reception is configured to adopt a periodic type, the duration is a time domain unit offset corresponding to a first CSI-RS resource set, wherein the first CSI-RS resource set and the CSI-RS resource set corresponding to the CSI-RS transmission correspond to the same serving cell or bandwidth part pair BWP pair, and the first CSI-RS resource set adopts a non-periodic type.
20. The method according to any one of claims 14 to 19, characterized in that The method further comprises: The terminal performs any of the following: For any configured or scheduled PDSCH reception, a corresponding hybrid automatic repeat request response HARQ-ACK is fed back. If the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception; For any PDSCH reception determined by the terminal to perform a preparation operation, a corresponding HARQ-ACK is fed back, and if the PDSCH reception is not actually received, a NACK is fed back for the PDSCH reception; For any PDSCH reception actually received by the terminal, the corresponding HARQ-ACK is fed back, and for any PDSCH reception not actually received by the terminal, the corresponding HARQ-ACK is not fed back.
21. A processing method, characterized in that: include: The network side device sends a first signaling to the terminal; The network side device determines, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal; The network side device performs a corresponding receiving operation or sending operation according to a processing operation of a target uplink transmission or a processing operation of a target downlink reception of the terminal; The first signaling is used to dynamically adjust the SBFD configuration.
22. The method according to claim 21, characterized in that The network-side device determines, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal, including any one of the following: When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the first condition, determining that the processing operation of the target uplink transmission of the terminal is to execute a cancellation operation of the target uplink transmission; When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the second condition, determining that the processing operation of the target uplink transmission of the terminal is a preparation operation for performing the target uplink transmission; When the dynamic adjustment of the SBFD configuration by the first signaling satisfies the third condition, determining the processing operation of the target downlink reception of the terminal as a preparation operation for performing the target downlink reception; in, The first situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that is available for uplink transmission before the dynamic adjustment is adjusted to be unavailable for uplink transmission based on the dynamic adjustment; In the target time domain unit, the parameters that take effect based on the dynamic adjustment do not match or are incompatible with the parameters of the target uplink transmission application; The second situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that is unavailable for uplink transmission before the dynamic adjustment is adjusted to be available for uplink transmission based on the dynamic adjustment; In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target uplink transmission; In the target time domain unit, at least one uplink transmission is newly scheduled or newly triggered based on the dynamic adjustment; The third situation includes at least one of the following: In the target time domain unit, at least one frequency domain resource that was not available for downlink reception before the dynamic adjustment is adjusted to be available for downlink reception based on the dynamic adjustment; In a target time domain unit, the parameters that take effect based on the dynamic adjustment are matched or compatible with the target downlink reception; In the target time domain unit, at least one downlink reception is newly scheduled or newly triggered based on the dynamic adjustment.
23. The method according to claim 21, characterized in that The method further comprises: The network side device ensures that the starting time of the target downlink reception is not less than a third predefined time length from the third time reference point; The third time reference point includes any one of the following: an end time of the first signaling; Detecting the end time of the CORESET or time domain unit of the first signaling; The determination of the third predefined duration includes any one of the following: Determining the third predefined duration based on a seventh parameter; The third predefined duration is determined based on the type of the target downlink reception and a predefined rule.
24. A processing device, characterized in that include: A first receiving module, used for a terminal to receive a first signaling from a network side device; A first execution module, configured for the terminal to execute a processing operation of a target uplink transmission or a processing operation of a target downlink reception according to the first signaling; The first signaling is used to dynamically adjust the SBFD configuration.
25. A processing device, characterized in that: include: A sending module, used for a network side device to send a first signaling to a terminal; A determination module, configured for the network side device to determine, according to the first signaling, a processing operation for target uplink transmission or a processing operation for target downlink reception of the terminal; A second execution module, configured for the network side device to perform a corresponding receiving operation or sending operation according to a processing operation of a target uplink transmission or a processing operation of a target downlink reception of the terminal; The first signaling is used to dynamically adjust the SBFD configuration.
26. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the processing method according to any one of claims 1 to 20 are implemented.
27. A network side device, characterized in that: It includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the processing method according to any one of claims 21 to 23 are implemented.
28. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the processing method according to any one of claims 1 to 20, or implements the steps of the processing method according to any one of claims 21 to 23.