WO2025031246A1 - 调整传输限制的方法、装置、设备及可读存储介质 - Google Patents

调整传输限制的方法、装置、设备及可读存储介质 Download PDF

Info

Publication number
WO2025031246A1
WO2025031246A1 PCT/CN2024/109071 CN2024109071W WO2025031246A1 WO 2025031246 A1 WO2025031246 A1 WO 2025031246A1 CN 2024109071 W CN2024109071 W CN 2024109071W WO 2025031246 A1 WO2025031246 A1 WO 2025031246A1
Authority
WO
WIPO (PCT)
Prior art keywords
predefined
time
predefined operation
scheduling
terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/109071
Other languages
English (en)
French (fr)
Inventor
曾超君
潘学明
李娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2025031246A1 publication Critical patent/WO2025031246A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/11—Semi-persistent scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/563—Allocation or scheduling criteria for wireless resources based on priority criteria of the wireless resources

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a method, device, equipment and readable storage medium for adjusting transmission restrictions.
  • the New Radio introduces a variety of gap mechanisms and corresponding data transmission and reception restrictions.
  • Radio Link Management RLM
  • BFD Beam Failure Detection
  • many regulations for scheduling availability/restrictions are introduced.
  • the above-mentioned gap mechanism and its corresponding transmission and reception restrictions, as well as the scheduling restrictions corresponding to the scheduling availability/restrictions regulations, will increase data transmission delay, reduce service capacity, etc., affecting communication performance.
  • the embodiments of the present application provide a method, apparatus, device and readable storage medium for adjusting transmission restrictions, which can reasonably relax the transmission and reception restrictions brought about by the Gap mechanism and the scheduling restrictions corresponding to the scheduling availability/restrictions, so as to ensure the transmission performance of high data rate and low latency services.
  • a method for adjusting a transmission restriction comprising:
  • the terminal determines that there is a scheduling restriction or a valid target interval timing in the first serving cell
  • the terminal performs a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a method for adjusting a transmission restriction comprising:
  • the network side device determines that there is a scheduling restriction or a valid target interval timing in the first serving cell
  • the network side device performs a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a device for adjusting transmission restriction including:
  • a first determining module is used to determine whether there is a scheduling restriction or a valid target interval timing in the first serving cell; a first executing module is used to execute a predefined operation according to a preset rule;
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a device for adjusting transmission restriction including:
  • a second determination module is used to determine whether there is a scheduling restriction or a valid target interval timing in the first serving cell;
  • a second execution module is used to execute a predefined operation according to a preset rule;
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a terminal 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.
  • a terminal including a processor and a communication interface, wherein the processor is configured to:
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a network side device 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.
  • a network side device including a processor and a communication interface, wherein the processor is used to:
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • a readable storage medium wherein a program or instruction is stored on the readable storage medium, wherein the program Or when the instructions are executed by the 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.
  • a wireless communication system 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.
  • a chip 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.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer 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.
  • the terminal side and the network side relax the scheduling restriction or disable the scheduling restriction in the first time domain unit set according to the preset rules associated with any one of the reporting information related to the channel quality of the Serving cell, the reporting information related to the uplink BSR or SR, and the uplink and downlink scheduling related information, or skip or disable at least one interval timing of the target interval timing, or adjust the interval pattern parameters corresponding to at least one interval timing of the target interval timing, and release the scheduling restriction or interval timing as much as possible to reduce data delay, improve service capacity, and ensure timely or as timely as possible data transmission without affecting measurement requirements or reducing the impact on measurement performance, thereby ensuring the transmission performance of the service.
  • FIG1a is a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • Figure 1b is a schematic diagram of the parameters of NCSG
  • FIG2 is a schematic diagram of a method for adjusting transmission restrictions according to an embodiment of the present application.
  • FIG3 is a schematic diagram of a scenario in which a predefined operation is started based on L3 measurement reporting or L1 CSI reporting of a Serving cell;
  • FIG4 is a second flow chart of a method for adjusting transmission restrictions provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of a structure of a device for adjusting transmission restrictions according to an embodiment of the present application.
  • FIG6 is a second schematic diagram of the structure of the device for adjusting transmission restrictions provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of a structure of a network side device according to an embodiment of the present application.
  • FIG. 10 is a second schematic diagram of the structure of the network side device provided in an embodiment of the present application.
  • 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.
  • “or” in the present application represents at least one of the connected objects.
  • “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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • FIG1a shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may 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 user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal
  • 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.
  • vehicle-mounted equipment can also be called vehicle-mounted terminals, vehicle-mounted controllers, vehicle-mounted modules, vehicle-mounted components, vehicle-mounted chips or vehicle-mounted units, etc. Need to say It is clear 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 (RAN) device, a radio access network function or a radio access network unit.
  • RAN radio access network
  • the access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.
  • 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 (home evolved Node B), a Transmission Reception Point (TRP) or other appropriate terms in the relevant field.
  • the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example
  • the core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery ...
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • Policy Control Function Policy Control Function
  • PCRF Policy and Charging Rules Function
  • edge application service discovery function Edge Application Server Discovery ...
  • Extended reality refers to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. It includes representative forms such as augmented reality (AR), mixed reality (MR), virtual reality (VR), and their intersections. The level of virtual world ranges from partial sensory input to fully immersive virtual reality.
  • AR augmented reality
  • MR mixed reality
  • VR virtual reality
  • AR virtual reality
  • a key aspect of XR is the expansion of human experience, especially the experience related to presence (represented by VR) and cognitive acquisition (represented by AR).
  • the uplink is mainly based on the transmission of relatively dense small data packets. These small data packets can carry information such as gestures and controls, and serve as input and reference for downlink presentation data.
  • the downlink is mainly based on the transmission of multimedia data such as video and audio. Through the timely reception and presentation of these multimedia data, users can be provided with an immersive experience.
  • video data can be modeled as video frames based on frames per second (FPS) (frame rate).
  • FPS frames per second
  • the typical value of FPS is 60 or 120. These video frames arrive periodically or quasi-periodically based on the period determined by FPS (1/FPS second), and the size of the video frame changes dynamically.
  • Each video frame is generally required to be successfully transmitted within 10ms on the air interface, and the transmission success rate is required to be no less than 99% or even 99.9%.
  • downlink video data generally requires a very high data rate, generally up to tens or even hundreds of Mbps (typical value is 30/45Mbps)
  • uplink may also transmit multimedia data such as video, audio, scene images, etc.
  • multimedia data such as video, audio, scene images, etc.
  • Its service characteristics are similar to those of downlink.
  • the data rate is relatively low, for example, at most tens of Mbps (typical value is 10/20Mbps), and the time limit for air interface transmission can also be relaxed.
  • each video frame is generally required to be successfully transmitted within 30ms.
  • the downlink data transmission characteristics are basically consistent with VR services.
  • Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) cells If the UE requires measurement intervals to identify and measure intra-frequency cells and/or inter-frequency cells and/or inter-Radio Access Technology (RAT) Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) cells:
  • RAT inter-Radio Access Technology
  • the network must provide a single per-UE measurement gap pattern to concurrently monitor all frequency layers.
  • the network must provide: a per-FR measurement gap mode for each frequency range (where the UE requires a frequency range level measurement gap to concurrently monitor all its frequency layers for each frequency range independently), or a single UE level measurement gap mode to concurrently monitor all frequency layers for all frequency ranges.
  • the UE During a per-UE measurement gap, the UE:
  • E-UTRA-NR Evolved Universal Terrestrial Radio Access - New Radio
  • RRM Radio resource management
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • PCell primary cell
  • SCell Evolved Universal Terrestrial Radio Access Network
  • NR serving cell Evolved Universal Terrestrial Radio Access Network
  • SA Standalone Architecture
  • CA carrier aggregation
  • the UE During the per-FR measurement gap, the UE:
  • NR further introduces the following derivative or enhanced mechanisms:
  • Measurement gap sharing for per-UE measurement gap or per-FR measurement gap corresponding to FR is applied:
  • the UE is configured to measure positioning frequency layers.
  • Measurement gap sharing is controlled by the network configuration Radio Resource Control (RRC) parameter MeasGapSharingScheme.
  • RRC Radio Resource Control
  • the activation/deactivation mechanism can be further divided into the following two mechanisms:
  • the UE may autonomously change the Pre-MG state from activated to deactivated, or vice versa, based on any one or any combination of the triggering conditions.
  • the UE determines whether a Pre-configured MG is Activated or Deactivated based on the RRC parameter preConfGapStatus configured on the network side.
  • the network can configure up to two per-UE MG types (patterns) for the UE; when the UE supports configuration of per-FR MG, the network can configure a combination of MG types (Combination of MG patterns) for the UE.
  • Determination of Collision of MG occasions When a Collision is determined to exist, the process is performed based on the priority configured for the Measurement gap: the MG occasion corresponding to the higher priority is applied (valid), and the MG occasion corresponding to the lower priority is discarded (invalid). It is required that any two MG occasions that are determined to have a Collision have corresponding priorities, and the corresponding priorities are different.
  • NCSG Network controlled small gap
  • NCSG When NCSG is configured, other MGs cannot be configured at the same time.
  • VIL Visible interruption length
  • VIL1 is the visible interruption length before the measurement length (ML)
  • VIL2 is the visible interruption length after the ML.
  • the UE does not expect to send or receive any data.
  • ML is the measured length
  • whether the UE is expected to send and receive data on the corresponding serving carrier depends on the scheduling restriction requirements.
  • VIRP is the Visible Interruption Repetition Period.
  • the NCSG Configurations table is different from the Measurement gap configuration table.
  • Multi-USIM (MUSIM) gap
  • MUSIM gap is used for MUSIM operation, such as cell identification and measurement of the target cell in the target network, paging Monitoring, System Information Block (SIB) acquisition and/or on-demand System Information (SI) request.
  • SIB System Information Block
  • SI System Information
  • the MUSIM Gap Pattern Configurations table is different from the Measurement gap configuration table.
  • Uplink (UL) gap is used for Tx power management
  • UL gap is used for Tx power management of NR FR2, and there are limitations on some uplink transmissions in the following scenarios.
  • the UE When the UL gap overlaps with uplink transmissions in the NR serving cell in a FR2 single CC scenario, an intra-FR2 CA scenario, or an inter-FR2 CA scenario where the UE does not support tx-Support-UL-GapFR2-r17, the UE does not need to perform any uplink transmissions other than the listed specified uplink transmissions on the NR serving cell during the UL gap.
  • the UL Gap Pattern Configurations table is different from the configuration table for Measurement gap.
  • Restrictions on scheduling availability are further introduced in the time period (or a subset of symbols therein) when the UE (may) perform RRM operations.
  • the following cases are all concerned with the scheduling restrictions (Scheduling restrictions) when the UE is not in the Measurement gap period (some cases marked with with NCSG are for the Scheduling restrictions of the UE during the ML period of NCSG, when the UE is not allowed to configure other MGs at the same time).
  • UE does not expect to send Physical Uplink Control Channel (PUCCH)/Physical Uplink Shared Channel (PUSCH)/Sounding Reference Signal (SRS);
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • SRS Sounding Reference Signal
  • Case 1 NR based on SSB without MG (or using NCSG) co-frequency measurement;
  • SSB symbols within the SMTC window duration SSB symbols within the SMTC window duration
  • RSSI Received Signal Strength Indication
  • Case 2 NR based on SSB without MG (or using NCSG) inter-frequency measurement;
  • SSB symbols within the SMTC window duration SSB symbols within the SMTC window duration
  • RSSI measurement symbols only applicable to SS-RSRQ measurement
  • some data symbols before/after the aforementioned symbols SSB symbols within the SMTC window duration
  • OFDM symbols where CLI measurements are performed and some data symbols before these OFDM symbols;
  • Symbols of interest configured CSI-RS resource symbols and some data symbols before/after these symbols;
  • the scheduling restrictions for a given service cell should also be applied to all other service cells in the same frequency band, and apply to symbols in other service cells that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions.
  • the scheduling restrictions for a given serving cell should also be applied to serving cells in other frequency bands, and to symbols in this serving cell that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions, if the UE does not have the capability to support simultaneousRxTxInterBandCA for the frequency band pair consisting of the frequency band in which the given serving cell is located and this other frequency band.
  • the UE does not expect to send PUCCH/PUSCH/SRS or receive PDCCH/physical downlink shared channel (PDSCH)/CSI-RS for tracking (TRS)/CSI-RS for channel quality indicator (CQI).
  • PDSCH physical downlink shared channel
  • TRS tracking
  • CQI channel quality indicator
  • simultaneousRxDataSSB-DiffNumerology Simultaneous reception of data and SSB with different subcarrier spacing (SCS)) capability is not supported (this capability involves same-frequency measurement (including cases where MG is not required or NCSG is used), Layer 1 reference signal received power (Layer 1reference signal received power, L1-RSRP) measurement (including L1-RSRP reporting or L1-RSRP is used for candidate beam detection), Layer 1 signal-to-noise and interference ratio (Layer 1signal-to-noise and interference ratio, L1-SINR) measurement, radio link monitoring, beam failure detection, etc.) or simultaneousRxDataSSB-DiffNumerology-Inter-r16 (simultaneous reception of different frequencies) is not supported UE with SCS different data on the same segment and SSB) capability (this capability involves inter-frequency measurement), operation based on SSB;
  • SCS subcarrier spacing
  • Case I UE performs measurements in FR1 using a subcarrier spacing different from that of PDSCH/PDCCH (this case is not applicable to CSI-RS);
  • SSB symbols within the SMTC window duration and some data symbols before/after the SSB symbols;
  • Symbols involved in Scheduling restrictions Symbols corresponding to the SSB index configured for L1-RSRP measurement;
  • CASE II UE performs radio link monitoring on FR1 using a subcarrier spacing different from that of PDSCH/PDCCH. Symbols involved in Scheduling restrictions: SSB symbols measured for radio link monitoring;
  • Case III UE performs beam failure detection on FR1 using a different subcarrier spacing than PDSCH/PDCCH
  • SSB symbols measured for beam failure detection
  • the scheduling restrictions for a given service cell should also be applied to all other service cells in the same frequency band, and to symbols in other service cells that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions.
  • inter-FR1 frequency band carrier aggregation when inter-FR1 frequency band carrier aggregation is configured, for other FR1 frequency bands other than the frequency band where the service cell with scheduling restrictions is located, there is no scheduling restriction for the FR1 service cells in these other FR1 frequency bands.
  • the UE does not expect to send PUCCH/PUSCH/SRS or receive PDCCH/PDSCH(/TRS)(/CSI-RS for tracking)/CSI-RS for CQI.
  • PUCCH/PUSCH/SRS or receive PDCCH/PDSCH(/TRS)(/CSI-RS for tracking)/CSI-RS for CQI.
  • the above bracketed items are only effective for the following cases.
  • CASE I UE performs measurements in FR2;
  • SSB symbols within the SMTC window duration and some data symbols before/after the SSB symbols
  • Scheduling restrictions involve symbols: symbols corresponding to the SSB index or periodic/semi-persistent/aperiodic CSI-RS resources configured for L1-RSRP measurement, and (for the case of FR2-2 and 480/960kHz SCS reference symbols, and for HST scenarios) some data symbols before/after these symbols;
  • Scheduling restrictions involve symbols: symbols used to measure L1-SINR, and (for FR2 power level 6 UE configured with highSpeedMeasFlagFR2-r17) some data symbols before/after these symbols;
  • Scheduling restrictions involve symbols: CSI-RS symbols configured in the configured time slot for the CSI-RS resources used for measurement;
  • RLM-RS symbols measured for radio link monitoring, and (for FR2-2 and RLM-RS using 480/960kHz SCS) some data symbols before/after the RLM-RS symbols;
  • CASE III UE performs beam failure detection on FR2
  • Scheduling restrictions involve symbols: reference symbols used for candidate beam detection, and (for FR2-2 and the case of RLM-RS using 480/960kHz SCS) some data symbols before/after the reference symbol;
  • the scheduling restrictions for a given service cell should also be applied to all other service cells in the same frequency band, and to symbols in other service cells that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions.
  • the UE configures different SCSs for SSB on one FR2 band and data on another FR2 band, there will be no scheduling restriction, assuming that the UE configures IBM operation for the band pair consisting of the two FR2 bands.
  • the scheduling restrictions for a given serving cell should also be applied to serving cells in other frequency bands, and to symbols in this serving cell that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions, if the UE does not have the capability to support simultaneousRxTxInterBandCA for the frequency band pair consisting of the frequency band in which the given serving cell is located and this other frequency band.
  • Case A For the frequency band pair consisting of the target measurement frequency band and the frequency band where the serving cell is located, the UE supports neither IBM nor simultaneousRxTxInterBandCA;
  • Case B For the frequency band pair consisting of the target measurement frequency band and the frequency band where the serving cell is located, the UE does not support IBM but supports simultaneousRxTxInterBandCA;
  • Case C For the frequency band pair consisting of the target measurement frequency band and the frequency band where the serving cell is located, the UE supports IBM but does not support simultaneousRxTxInterBandCA;
  • Case D For the frequency band pair consisting of the target measurement frequency band and the frequency band where the serving cell is located, the UE supports both IBM and simultaneousRxTxInterBandCA: At this time, there is no scheduling restriction for the serving cell.
  • UE does not expect to receive PDCCH/PDSCH/CSI-RS for tracking/CSI-RS for CQI.
  • Case I UE performs CLI measurement and DL reception in frequency division multiplexing (FDM)
  • the symbols involved in scheduling restrictions are: for SRS-RSRP measurement, the orthogonal frequency division multiplexing (OFDM) symbols for SRS-RSRP measurement, and some data symbols before these OFDM symbols; for CLI-RSSI measurement, the OFDM symbols for CLI-RSSI measurement, and some data symbols before these OFDM symbols.
  • OFDM orthogonal frequency division multiplexing
  • the scheduling restrictions for the service cell performing CLI measurements are also applied to all other service cells in the same frequency band, and apply to symbols in other service cells that fully or partially overlap with the symbols involved in the aforementioned Scheduling restrictions.
  • the present application provides a method for adjusting transmission restrictions, the method is performed by a terminal, and the method includes:
  • Step 201 The terminal determines that there is a scheduling restriction or a valid target interval timing in the first serving cell
  • Step 202 The terminal performs a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • a preset rule is associated with any of the following:
  • the first reporting information related to the channel quality of the serving cell which may be referred to as mode 1;
  • mode 2 (2) second reporting information related to an uplink buffer status report (BSR) or a scheduling request (SR); referred to as mode 2;
  • mode 3 Scheduling information related to uplink and downlink scheduling
  • the predefined operations include at least one of the following:
  • the terminal side and the network side execute predefined operations according to preset rules associated with any one of the reporting information related to the channel quality of the Serving cell, the reporting information related to the uplink BSR or SR, and the uplink and downlink scheduling related information, to implement a scheme for adjusting transmission restrictions based on rules, and reasonably relax the transmission and reception restrictions brought by the Gap mechanism, and the scheduling restrictions corresponding to the scheduling availability/restrictions, by ensuring that the measurement requirements are not affected or the impact on the measurement performance is reduced, ensuring timely or as timely as possible data transmission, etc., so as to ensure the transmission performance of high data rate and low latency services.
  • predefined operations may also be referred to as predefined behaviors.
  • the time domain unit may correspond to a unit divided in a predefined manner in the time domain, such as a time slot or a symbol. In the following, the time domain unit is described as a symbol, and the first time domain unit set is described as a set of symbols. Relaxing or disabling scheduling restrictions is Relax/disable scheduling restrictions.
  • a set of symbols can correspond to a set of symbols of Scheduling restrictions within one or more Windows or Window groups, or within a time period/time sub-segment, or within the duration or extended duration corresponding to the transmission corresponding to/triggered by the scheduled DCI.
  • the set of symbols of Scheduling restrictions please refer to the corresponding description in the previous text.
  • the Window here can be ML.
  • the Relax/disable scheduling restrictions here can be understood as closing/removing the Scheduling restrictions corresponding to the symbol set, so that the channels/signals that were not allowed to be sent or received before the closing/removal are allowed to be sent or received within this symbol set, or partially closing/removing the Scheduling restrictions corresponding to the symbol set, so that the channels/signals that were not allowed to be sent or received before the closing/removal are allowed to be sent or received within this symbol set and meet one or more pre-set conditions (for the specific description of the conditions, see below), thereby ensuring more timely data scheduling and transmission, so as to ensure or improve the transmission performance of high data rate and low latency services.
  • Gap occasion can be understood as the (e.g. single) Gap window corresponding to a certain Gap mechanism in NR after configuration/activation.
  • the Gap occasion here can be a Window composed of VIL1, ML and VIL2, or only the time portion corresponding to VIL1 and VIL2.
  • Skip/disable here can be understood as closing/removing the transmission and reception restrictions within the Gap occasion (i.e., treating this Gap occasion as invalid, or as not existing), or closing/removing the transmission and reception restrictions within the Gap occasion for reception/transmission that meets the predefined conditions (i.e., only treating this Gap occasion as invalid, or as not existing for reception/transmission that meets the predefined conditions).
  • data (or data that meets one or more pre-set conditions (see below for a specific description of the conditions)) may be allowed to be scheduled and transmitted during the Gap occasion, or data (or data that meets one or more pre-set conditions (see below for a specific description of the conditions)) may be allowed to overlap with the Gap occasion in the time domain, thereby ensuring more timely data scheduling and transmission to ensure or improve the transmission performance of high data rate and low latency services.
  • the gap pattern parameters are gap pattern parameters
  • Adjusting the Gap pattern parameters includes adjusting (e.g., extending/shortening) the Gap cycle length (e.g., the value of the parameter mgrp), the Gap offset (e.g., the value of the parameter gapOffset), the Gap length (e.g., the value of the parameter mgl), etc.
  • the Gap cycle length e.g., the value of the parameter mgrp
  • the Gap offset e.g., the value of the parameter gapOffset
  • the Gap length e.g., the value of the parameter mgl
  • the adjustment here can be understood as adjusting the corresponding parameters for the target Gap occasion(s) or the Gap occasion(s) within the target time period/time sub-segment.
  • the Gap period length can be extended or shortened to control the frequency or probability of the transceiver restriction corresponding to the Gap occasion in the time domain, so as to reduce the impact of the transceiver restriction on data scheduling and transmission, thereby ensuring or improving the transmission performance of high data rate and low latency services.
  • the first serving cell has a target interval opportunity in effect can be understood as the first serving cell is included in the serving cell set where the target interval opportunity is in effect or applied.
  • the serving cell set where the target interval opportunity is in effect or applied is generally based on the protocol provisions, the serving cell or the serving cell set where the gap occasion or scheduling restrictions are applied, for details, see the corresponding description below.
  • the serving cell set where the target interval opportunity is in effect or applied can be configured by high-level signaling.
  • the scope of the target Serving cell of the above predefined operations is, by default, the Serving cell or the set of Serving cells to which the Gap occasion or Scheduling restrictions apply based on the protocol provisions.
  • the target Serving cell can be understood as all serving cells configured by the UE, including NR serving cells or E-UTRAN serving cells;
  • the target Serving cell can be understood as all serving cells configured by the UE in the corresponding FR (FR1 or FR2), including NR serving cells or E-UTRAN serving cells.
  • the target Serving cell corresponding to the predefined operation can be determined based on other rules for different methods.
  • the applied Serving cell is the Serving cell corresponding to the channel quality
  • the applied Serving cell is the Serving cell corresponding to the channel quality
  • the target Serving cell or target Serving cell list/set can be explicitly configured by high-level signaling.
  • the target Serving cell of the above predefined operation must include the first serving cell.
  • the above-mentioned preset rules can be understood as continuing to use the semi-static/dynamic signaling and processes in the relevant technology, without introducing/adding new semi-static configuration/dynamic indication information to explicitly indicate whether the UE performs a predefined operation (which specific method to adopt, and the relevant parameters involved when a certain method is adopted, can be specified by the protocol or configured by high-level signaling), but introducing new rules so that both parties can reach an agreement on the above-mentioned determination of the operation (including start and end time).
  • Method 1 Based on the channel quality related reporting information of the Serving cell (corresponding to the measurement requirements).
  • the preset rule is associated with the reporting information related to the channel quality of the serving cell.
  • the terminal performs predefined operations according to preset rules, including:
  • the terminal When the channel quality of the Serving cell is higher than or equal to the first threshold, the terminal performs predefined operations based on the reporting information related to the channel quality of the Serving cell.
  • the better the channel quality of the Serving cell the less necessary it is for the UE to perform neighboring cell measurements and prepare for handover and other mobility processes, the less the need to introduce scheduling restrictions for measurements, etc., the fewer situations where scheduling restrictions are actually needed, or the situation can be more sparse in the time domain. Accordingly, scheduling restrictions can be relaxed or disabled in some situations or at some times to ensure the latency, capacity and other performance of data transmission as much as possible while avoiding or reducing the performance related to Scheduling restrictions such as measurements.
  • the channel quality of the Serving cell is higher than or not lower than the predefined threshold (i.e., the first threshold mentioned above), both sides can consider that they can temporarily lift scheduling restrictions or close the Measuremeng gap, etc., that is, perform predefined operations.
  • the terminal when the channel quality of the Serving cell is higher than or equal to the first threshold, and the occupied interval is used to perform measurements of non-serving cells, or the scheduling restriction is introduced to perform detection of non-serving cells, the terminal performs predefined operations based on the reporting information related to the channel quality of the Serving cell.
  • the Gap is occupied or scheduling restrictions are introduced for measuring the Serving cell, for example, the Gap is occupied to measure the SSB of the Serving cell outside the Active Bandwidth Part (Active BWP), or scheduling restrictions are introduced to perform RLM/BFD of SSB based on SCS different from PDSCH/Physical downlink control channel (PDCCH) in FR1 or RLM/BFD in FR2, then the predefined operation cannot be performed when the channel quality of the Serving cell is good enough. Therefore, "performing the predefined operation when the channel quality of the Serving cell is good enough" is only applicable to some scenarios, that is, occupying the Gap or introducing scheduling restrictions is to perform measurement or detection on non-serving cells.
  • Active BWP Active Bandwidth Part
  • the Serving cell here may be only a special cell (SpCell), or only an SCell, or any Serving cell. It is understandable that there is an association relationship between the Serving cell here and the first serving cell.
  • the Serving cell here is the first serving cell.
  • the Serving cell here and the first serving cell are different serving cells; optionally, the two are located in the same frequency domain range (FR1 or FR2), or in the same Cell group, or in a Serving cell group or list specified by the protocol or configured by high-level signaling.
  • the terminal performs a predefined operation according to the channel quality related reporting information of the serving cell, including any one of the following:
  • Mode 1-1 The terminal performs predefined operations based on the layer 3 (L3) measurement reporting information of the serving cell;
  • Method 1-2 The terminal performs predefined operations based on the channel state information (CSI) reported by the serving cell.
  • CSI channel state information
  • the channel quality of the serving cell can be determined by L3 measurement reporting or layer 1 (L1) CSI reporting in the related art, for example, see the scenario shown in FIG3. Accordingly, the terminal performs a predefined operation according to the L3 measurement reporting or L1 CSI reporting.
  • L1 CSI reporting layer 1
  • method 1-1 is as follows:
  • the first reporting information includes a measurement report based on L3 measurement, and the terminal performs a predefined operation according to the first reporting information, including any one of the following:
  • Mode 1-1-1 When sending a measurement report based on L3 measurement, the terminal performs a predefined operation, and the measurement report based on L3 measurement is triggered based on a measurement reporting event;
  • Method 1-1-2 The terminal performs a predefined operation based on the channel quality information in the measurement report of L3 measurement.
  • the terminal performs a predefined operation according to the measurement reporting event, including:
  • the terminal After the terminal sends a measurement report based on L3 measurement based on the first event, the terminal performs a predefined operation starting from a first predefined time;
  • the first predefined time is determined based on the transmission time of the measurement report of the layer 3 measurement sent by the first event
  • the second predefined time is determined based on the transmission time of the measurement report of the layer 3 measurement sent by the second event.
  • both sides may consider that the UE does not need or needs to perform intra-frequency/inter-frequency/inter-RAT measurements, and thus executes or stops executing predefined operations.
  • the first predefined time is determined based on the transmission time of the measurement report of the layer 3 measurement sent by the first event
  • the second predefined time is determined based on the transmission time of the measurement report of the second event, which can be specifically as follows:
  • the first predefined moment is the hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback moment corresponding to the transmission block (Transport Block, TB) where the response (Acknowledgement, ACK) corresponding to the radio link control service data unit (Radio Link Control Service Data Unit, RLC SDU) carrying the measurement report of the layer 3 measurement sent by the first event is located plus the first time interval
  • the HARQ-ACK feedback moment is the start moment or end moment of the physical uplink control channel PUCCH transmission carrying the HARQ-ACK information (generally, it can be required to be the HARQ-ACK information corresponding to the transmission block and the value is ACK), or the HARQ-ACK feedback moment is the start moment or end moment of the time unit (for example, Slot or sub-slot) where the PUCCH transmission carrying the HARQ-ACK information is located, and the first time interval is specified by the protocol or configured by high-level signaling; by determining the first predefined moment, the terminal and the network can have a consistent understanding of the moment of starting to execute the pre
  • the second predefined moment is the HARQ-ACK feedback moment corresponding to the TB where the ACK corresponding to the RLC SDU carrying the measurement report of the second event is located plus the second time interval
  • the HARQ-ACK feedback moment is the start moment or end moment of the PUCCH transmission carrying the HARQ-ACK information (generally, it can be required to be the HARQ-ACK information corresponding to the transmission block and the value of which is ACK)
  • the HARQ-ACK feedback moment is the start moment or end moment of the time unit (such as Slot or Sub-slot) where the PUCCH transmission carrying the HARQ-ACK information is located, and the second time interval is specified by the protocol or configured by high-level signaling; by determining the second predefined moment, the terminal and the network can have a consistent understanding of the moment to stop executing the predefined operation, and stop executing the predefined operation as early as possible to avoid affecting the measurement performance.
  • both sides may consider that the UE performs a predefined operation starting from predefined time 1 (for example, the HARQ-ACK feedback time corresponding to the TB (downlink direction) where the ACK corresponding to the RLC SDU carrying the (uplink) measurement report (Measurement report) is located + delta1; the HARQ-ACK feedback time may be the start/end time of the PUCCH transmission carrying the HARQ-ACK information, or the start/end time of the Slot where the PUCCH transmission is located; delta1 may be specified by the protocol or configured by high-level signaling).
  • predefined time 1 for example, the HARQ-ACK feedback time corresponding to the TB (downlink direction) where the ACK corresponding to the RLC SDU carrying the (uplink) measurement report (Measurement report) is located + delta1
  • the HARQ-ACK feedback time may be the start/end time of the PUCCH transmission carrying the HARQ-ACK information, or the start/end time of the Slot where the PUCCH transmission is located
  • the terminal performs a predefined operation according to the channel quality information in the measurement report, including:
  • the terminal performs the predefined operation starting from the third predefined time
  • the terminal stops performing the predefined operation at a fourth predefined time
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report.
  • the L3 measurement and channel quality information here can be the cell-level reference signal received power (RSRP)/reference signal received quality (RSRQ)/signal to interference plus noise ratio (SINR) corresponding to the serving cell, or the RSRP/RSRQ/SINR of the strongest beam or one or more predefined beams.
  • RSRP cell-level reference signal received power
  • RSRQ reference signal received quality
  • SINR signal to interference plus noise ratio
  • whether to execute or stop executing the predefined operation is determined based on the RSRP/RSRQ/SINR reported for one or more specific Serving cells in the Measurement report. For example, when the RSRP/RSRQ/SINR corresponding to one or more Serving cells is higher than or not lower than the predefined threshold, both sides may consider that the UE (starts or continues) to execute the predefined operation; when the RSRP/RSRQ/SINR corresponding to one or more Serving cells is lower than or not higher than the predefined threshold, both sides may consider that the UE stops/no longer executes the predefined operation.
  • the Measurement report here can be a Measurement report that includes all Serving cells or at least one or N Serving cells in the above-mentioned one or more specific Serving cells.
  • the report type (reportType) corresponding to the Measurement report is required to be periodic (periodical) and/or event-triggered (eventTriggered).
  • the effective time of RSRP/RSRQ/SINR contained in it can refer to the above method.
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report, which may be specifically as follows:
  • the third predefined moment is the HARQ-ACK feedback moment corresponding to the TB where the ACK corresponding to the RLC SDU carrying the first measurement report is located plus the third time interval
  • the HARQ-ACK feedback moment is the start moment or end moment of the PUCCH transmission carrying the HARQ-ACK information (generally, it may be required to be the HARQ-ACK information corresponding to the transmission block and having the value of ACK)
  • the HARQ-ACK feedback moment is the start moment or end moment of the time unit (such as Slot or Sub-slot) where the PUCCH transmission carrying the HARQ-ACK information is located, and the third time interval is specified by the protocol or configured by high-level signaling; by determining the third predefined moment, the terminal and the network can have a consistent understanding of the moment when the predefined operation is started, and can start executing the predefined operation as early as possible to ensure or improve the performance of data transmission;
  • the fourth predefined moment is the HARQ-ACK feedback moment corresponding to the TB where the ACK corresponding to the RLC SDU carrying the second measurement report is located plus the fourth time interval
  • the HARQ-ACK feedback moment is the start moment or end moment of the PUCCH transmission carrying the HARQ-ACK information (generally, it may be required to be the HARQ-ACK information corresponding to the transmission block and having the value of ACK)
  • the HARQ-ACK feedback moment is the start moment or end moment of the time unit (such as Slot or Sub-slot) where the PUCCH transmission carrying the HARQ-ACK information is located, and the fourth time interval is specified by the protocol or configured by high-level signaling; by determining the fourth predefined moment, the terminal and the network can have a consistent understanding of the moment to stop executing the predefined operation, and can stop executing the predefined operation as early as possible to avoid affecting the measurement performance.
  • method 1-2 is as follows:
  • the terminal performs a predefined operation according to the CSI reporting information of the serving cell, including any one of the following:
  • the terminal performs the predefined operation starting from the fifth predefined time
  • the terminal stops performing the predefined operation at a sixth predefined time;
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report.
  • the predefined operation can be determined whether to execute or stop executing the predefined operation based on the reported information in the CSI report, such as L1-RSRP/L1-SINR or Channel Quality Indicator (CQI). For example, when the reported information is higher than or not lower than the predefined threshold, both sides can consider that the UE executes the predefined operation (starts or continues) for the Serving cell corresponding to the CSI report; when the reported information is lower than or not higher than the predefined threshold, both sides can consider that the UE stops/no longer executes the predefined operation for this Serving cell.
  • the reported information in the CSI report such as L1-RSRP/L1-SINR or Channel Quality Indicator (CQI).
  • CQI Channel Quality Indicator
  • the CSI report here can introduce certain restrictions for its corresponding CSI-ReportConfig.
  • restrict its reportConfigType to one or more of the following:
  • Aperiodic (Aperiodic CSI on PUSCH);
  • the reported amount must include L1-RSRP and/or L1-SINR and/or CQI;
  • the measurement bandwidth for example, the percentage of the measurement frequency domain resources corresponding to the csi-ReportingBand relative to the DL active BWP or the Serving cell bandwidth is higher than or not lower than a predefined threshold.
  • the CQI in the CSI report When determined based on the CQI in the CSI report, it can be based only on the CQI in the single codeword CSI report; or, for a single codeword CSI report, based on the CQI of this single codeword, for a dual codeword CSI report, based on the CQI of a predefined codeword (e.g., the first codeword/the second codeword/the codeword with a larger CQI/the codeword with a smaller CQI) or the average CQI of the two codewords.
  • the CQI here can be a wideband CQI, and/or one or more subband CQIs with the minimum/maximum values.
  • the effective time of the reporting information contained therein (that is, the start time that can be used to determine whether to execute or stop executing a predefined operation) can be the end time + delta2 of the PUCCH/PUSCH carrying this CSI report; delta2 can be specified by the protocol or configured by high-level signaling, mainly considering the decoding delay of the CSI report.
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report, which may be specifically as follows:
  • the fifth predefined time is the end time of the PUCCH or PUSCH carrying the first CSI reporting information plus the fifth time interval, and the fifth time interval is specified by the protocol or configured by high-level signaling; by determining the fifth predefined time, the terminal and the network can have a consistent understanding of the time when the predefined operation starts to be executed, and the predefined operation can be executed as early as possible to ensure or improve the performance of data transmission;
  • the sixth predefined moment is the end moment of the PUCCH or PUSCH carrying the second CSI reporting information plus the sixth time interval, and the sixth time interval is specified by the protocol or configured by high-level signaling; by determining the sixth predefined moment, the terminal and the network can have a consistent understanding of the moment to stop executing the predefined operation, and stop executing the predefined operation as soon as possible to avoid affecting measurement performance.
  • Method 2 Based on uplink BSR/SR related reporting information (corresponding to uplink data transmission requirements).
  • the terminal when the preset rule is associated with the reporting information related to the uplink BSR or SR, the terminal performs a predefined operation according to a preset rule, including at least one of the following:
  • Processing criterion 1 When the reporting information of the target logical channel or the target logical channel group in the uplink BSR reporting information meets the first condition, the terminal performs a predefined operation on the target serving cell;
  • Processing criterion 2 When the SR reporting information or uplink BSR reporting information of the target logical channel or target logical channel group meets the second condition, the terminal performs a predefined operation on the target serving cell;
  • the first condition includes at least one of the following:
  • the waiting time of the data to be transmitted on the target logical channel or target logical channel group is longer than or equal to the sixth threshold; that is, the data to be transmitted in the uplink direction of the specific logical channel (Logical channel)/Logical Channel Group (LCG) has been waiting for a long time;
  • the remaining packet delay budget (PDB) of the data to be transmitted on the target logical channel or target logical channel group is shorter than or equal to the seventh threshold; that is, the data to be transmitted in the uplink direction of the specific Logical channel/LCG is about to time out or is likely to be discarded, which is more urgent;
  • the amount of data to be transmitted on the target logical channel or target logical channel group is greater than or equal to the eighth threshold; that is, the amount of data to be transmitted in the uplink direction of the specific Logical channel/LCG is relatively large;
  • the second condition includes at least one of the following:
  • the terminal triggers and actually sends the SR PUCCH for the target logical channel or at least one logical channel in the target logical channel group;
  • the uplink BSR reporting information indicates that there is an amount of data to be transmitted for the target logical channel or the target logical channel group.
  • Gap or scheduling restrictions can be temporarily ignored to prioritize data transmission demands, that is, data transmission demands have a higher priority than measurement.
  • This processing principle only sacrifices RAN4 performance such as RRM measurement when necessary, and has relatively little impact on RAN4 performance.
  • both sides may determine that the UE performs a predefined operation (start or continue) for all Serving cells (or, all Serving cells of FR1/FR2, or, all Serving cells of MCG/SCG, or, the Serving cells specified by the protocol or configured by the high-level signaling, or each Serving cell in the Serving cell list):
  • the waiting time of the data to be transmitted here may be the maximum value/minimum value/average value of the waiting time of all the data to be transmitted.
  • the Remaining PDB of the data to be transmitted here may be a maximum value/minimum value/average value of the Remaining PDB of all the data to be transmitted.
  • the above-mentioned specific Logical channel/LCG corresponds to at least one Logical channel/LCG, which can be determined in any of the following ways:
  • a specific Logical channel/LCG may be a Logical channel/LCG corresponding to an RB mapped with a specific service type or a Quality of Service (QoS) flow with specific attributes (for example, XR service, or a video stream of an XR service, or an I Frame of a Video stream of an XR service), or the configuration of the Logical channel/LCG or its mapped resource block (RB) meets predefined requirements (for example, a discard timer configured for the RB is shorter than or not longer than a predefined threshold).
  • QoS Quality of Service
  • the terminal when the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the first condition, the terminal performs a predefined operation on the target Serving cell, including:
  • the terminal starts or continues to perform the predefined operation on the target Serving cell from the seventh predefined time;
  • the UE continues to execute the predefined operation.
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information.
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information, and may be specifically as follows:
  • the seventh predefined time is any one of the following:
  • the start/end time of the first PUSCH transmission of the TB carrying the above uplink buffer reporting information + delta3; delta3 can be specified by the protocol or configured by high-level signaling, mainly considering the delay of HARQ transmission, decoding and decapsulation of the TB.
  • the start time or end time of the PDCCH transmission corresponding to the uplink grant (UL grant) received by the terminal indicating the new transmission plus the eighth time interval which is specified by the protocol or configured by high-level signaling
  • the UE receives the start/end time + delta4 of the PDCCH transmission corresponding to the newly transmitted UL grant; delta4 can be specified by the protocol or configured by high-level signaling, mainly considering the PDCCH decoding delay.
  • the terminal and the network can have a consistent understanding of the time to start executing the predefined operation, and can start executing the predefined operation as early as possible to ensure or improve data transmission performance.
  • the terminal when the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the first condition, performs a predefined operation for the target Serving cell, further comprising:
  • the terminal stops executing the predefined operation
  • the third condition includes any of the following:
  • both sides may determine that the UE (or, all Serving cells of FR1/FR2, or, all Serving cells of MCG/SCG, or, each Serving cell in the Serving cell list or the Serving cell specified by the protocol or configured by high-level signaling) (start or continue) performing a predefined operation:
  • the UE triggers and actually sends an SR PUCCH for a specific Logical channel or at least one Logical channel in a specific LCG
  • an associated SR Config can be configured for it.
  • the LCG where this specific Logical channel is located, or this specific LCG triggers a Regular BSR
  • the UE does not have available uplink shared channel (UL-SCH) initial transmission resources the corresponding SR PUCCH can be sent based on this associated SR Config.
  • UL-SCH uplink shared channel
  • Uplink Buffer reporting information indicates that there is a certain amount of data to be transmitted for a specific Logical channel/LCG (or, the amount of data to be transmitted > 0)
  • the terminal when the SR reporting information or uplink BSR reporting information of the target logical channel or the target logical channel group meets the second condition, the terminal performs a predefined operation on the target Serving cell, including:
  • the terminal starts or continues to perform the predefined operation on the target Serving cell from the eighth predefined time;
  • the eighth predefined time is determined based on the transmission time of the SR reporting information or the uplink BSR reporting information.
  • the eighth predefined time is any one of the following:
  • the terminal adds the ninth time interval to the start time or end time of the first SR PUCCH transmission after triggering the SR.
  • the ninth time interval is specified by the protocol or configured by high-level signaling.
  • the start time or end time of the PDCCH transmission corresponding to the uplink authorization UL grant received by the terminal indicating the new transmission plus the eleventh time interval is specified by the protocol or configured by high-level signaling.
  • the time for determining (starting or continuing) to execute the predefined operation may be any one of the above items.
  • the above-mentioned time for determining (starting or continuing) executing the predefined operation can be: the start/end time of the first SR PUCCH transmission of the UE after triggering SR + delta5; wherein delta5 can be specified by the protocol or configured by high-level signaling, mainly considering possible delays such as multiple SR PUCCH transmissions and decoding.
  • the terminal and the network can have a consistent understanding of the time for starting to execute the predefined operation, and can start executing the predefined operation as early as possible to ensure or improve data transmission performance.
  • the terminal when the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the second condition, performs a predefined operation on the target Serving cell, further comprising:
  • the terminal stops executing the predefined operation
  • the fourth condition includes any of the following:
  • the uplink BSR reporting information indicates that the amount of data to be transmitted for the target logical channel or the target logical channel group is zero.
  • both sides determine to execute the predefined operation for all or specific Serving cells (start or continue), they can determine to stop executing the predefined operation based on any of the following (i.e., the fourth condition above):
  • both sides determine to stop executing the predefined operation.
  • Mode 3 Based on uplink and downlink scheduling information or scheduling conditions (corresponding to uplink and downlink data transmission requirements).
  • the terminal when the preset rule is associated with the uplink and downlink scheduling related information, the terminal performs a predefined operation according to the preset rule, including:
  • Mode 3-1 The terminal performs a predefined operation according to the transmission position of the physical downlink shared channel (PDSCH), channel state information reference signal (CSI-RS), physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH) or sounding reference signal (SRS) corresponding to the scheduling downlink control information (DCI);
  • PDSCH physical downlink shared channel
  • CSI-RS channel state information reference signal
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • SRS sounding reference signal
  • Mode 3-2 The terminal performs a predefined operation according to the transmission attribute information indicated in the scheduling DCI, where the transmission attribute information is related to the size of the TB or the physical layer priority;
  • Method 3-3 The terminal performs predefined operations based on data scheduling related information.
  • method 3-1 is as follows:
  • the terminal performs a predefined operation according to a location of a PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI, including:
  • the terminal performs a predefined operation for the interval opportunity or the first window; wherein the first window is a predefined window with scheduling restrictions;
  • both sides consider that a predefined operation should be performed on this Gap occasion or Window with scheduling restrictions, such as disabling this Gap occasion, or disabling the Scheduling restrictions in this Window with scheduling restrictions.
  • the terminal performs a predefined operation for the area of time domain overlap
  • the terminal when the time domain interval between the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the time domain unit occupied by the interval opportunity or the first window is less than or equal to the tenth threshold, the terminal performs a predefined operation for the area of extended time domain overlap, and the area of extended time domain overlap is determined based on the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the tenth threshold;
  • the terminal performs a predefined operation for all time domain units with scheduling restrictions within a first time period, where the first time period is determined by the transmission of a PDSCH, CSI-RS, PUSCH, PUCCH or SRS corresponding to the scheduling DCI;
  • this period of time is the time period corresponding to the specified duration starting from the earliest corresponding/triggered PDSCH/CSI-RS or PUSCH/PUCCH/SRS transmission or the start time of the Slot where the transmission is located (or the duration/number of symbols corresponding to the predefined threshold).
  • the specified duration here can be specified by the protocol or configured by high-level signaling, or directly indicated in the scheduling DCI.
  • the terminal performs a predefined operation for all time domain units that have time domain overlap or extended time domain overlap with the second time period and have scheduling restrictions, and the second time period is determined by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI.
  • Predefined operations are performed only for all Symbols that have time domain overlap with PDSCH/CSI-RS or PUSCH/PUCCH/SRS transmission corresponding to/triggered by scheduling DCI, or extended time domain overlap (based on extended duration, see the corresponding description in the previous text for details), and have Scheduling restrictions.
  • the priority of the PUCCH/PUSCH scheduled by the DCI meets predefined requirements, such as a high priority, or the priority of the HARQ-ACK corresponding to the PDSCH scheduled by the DCI meets predefined requirements, such as a high priority.
  • the priority of the PDSCH scheduled by the DCI meets predefined requirements, such as a high priority.
  • method 3-2 is as follows:
  • the terminal performs a predefined operation according to the transmission attribute information indicated in the scheduling DCI, including:
  • the terminal When the terminal detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction meets the fifth condition, the terminal performs a predefined operation on the target Serving cell, where N is specified by the protocol or configured by high-level signaling;
  • the fifth condition includes at least one of the following:
  • the size of TB is greater than or equal to the eleventh threshold
  • the physical layer priority is a predefined priority.
  • both sides may determine that the UE performs a predefined operation (start or continue) for all Serving cells (or, all Serving cells of FR1/FR2, or, all Serving cells of MCG/SCG, or, the Serving cells specified by the protocol or configured by high-level signaling, or each Serving cell in the Serving cell list):
  • PHY priority is a predefined priority, such as a higher priority
  • PHY priority is only supported in the uplink direction.
  • PHY priority can also be introduced in the downlink direction as needed.
  • the PHY priority corresponding to the scheduled PDSCH is indicated in the DCI to distinguish the priority of the data carried by the PDSCH (which can be independently indicated with the priority of the HARQ-ACK corresponding to the scheduled PDSCH in the relevant technology).
  • the terminal when the terminal detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction satisfies the fifth condition, the terminal performs a predefined operation on the target Serving cell, including:
  • the terminal When the terminal detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction meets the fifth condition, the terminal starts or continues to perform the predefined operation for the target Serving cell from the ninth predefined time;
  • the ninth predefined time is determined based on the transmission time of N consecutive scheduled DCIs.
  • the ninth predefined time is determined based on the transmission time of N consecutive scheduled DCIs, and may be specifically as follows:
  • the ninth predefined time is the latest start time or the latest end time of the PDCCH transmission corresponding to N consecutive scheduled DCIs plus a twelfth time interval, and the twelfth time interval is specified by the protocol or configured by high-level signaling.
  • the above-mentioned time for determining (starting or continuing) executing the predefined operation can be: the latest start/end time of PDCCH transmission corresponding to N consecutive (newly transmitted) scheduled DCIs + delta6; wherein delta6 can be specified by the protocol or configured by high-level signaling, mainly considering the PDCCH decoding delay.
  • the terminal and the network can have a consistent understanding of the time to start executing the predefined operation, and can start executing the predefined operation as early as possible to ensure or improve data transmission performance.
  • the terminal performs a predefined operation according to the transmission attribute information indicated in the scheduling DCI, further comprising:
  • the terminal stops executing the predefined operation
  • the sixth condition includes any of the following:
  • the terminal detects in the target transmission direction that the transmission attribute information indicated by at least one scheduling DCI in N consecutive scheduling DCIs does not meet the fifth condition.
  • both sides determine to execute the predefined operation for all or specific Serving cells (start or continue), they can determine to stop executing the predefined operation based on any of the following (i.e., the sixth condition above):
  • method 3-3 is as follows:
  • the terminal performs a predefined operation according to the data scheduling related information, including:
  • the terminal execute predefined operations
  • the third time period is specified by a protocol or configured by high-level signaling.
  • both sides can determine that the UE (or, all Serving cells of FR1/FR2, or, all Serving cells of MCG/SCG, or, the Serving cells specified by the protocol or configured by high-level signaling or each Serving cell in the Serving cell list) (start or continue) perform the predefined operation.
  • the above duration may be specified by the protocol or configured by high-level signaling.
  • the amount of data scheduled above can be considered as the sum of the TB Sizes indicated by the (new transmission) scheduling DCI detected by the UE for the specified transmission direction within the above time period.
  • the amount of data actually scheduled for the specific RB/Logical channel mentioned above can be directly determined based on the data assembly in the Media Access Control (MAC) Protocol Data Unit (PDU) (based on the Logical Channel Identity (LCID) field in the MAC subheader corresponding to each MAC SDU, the corresponding Logical channel can be identified).
  • the specific RB/Logical channel here can be a RB/Logical channel that maps a QoS flow corresponding to a specific service type or having specific attributes (such as XR service, or Video stream of XR service, or I Frame of Video stream of XR service), or the configuration of the RB/Logical channel meets predefined requirements (for example, the Discard Timer configured for the RB is shorter than or not longer than a predefined threshold).
  • the above-mentioned most recent duration can be determined by a sliding window method, and its end time can be the start/end time of the PDCCH transmission corresponding to the scheduling DCI of the specified transmission direction received by the UE; its start time can be implicitly determined based on the end time and duration.
  • the terminal performs a predefined operation on the target Serving cell, including:
  • the terminal starts or continues to perform the predefined operation on the target Serving cell from the tenth predefined time;
  • the tenth predefined time is the end time of the third time period plus a preset time interval, and the preset time interval is specified by the protocol or configured by high-level signaling.
  • the above-mentioned time for determining (starting or continuing) executing the predefined operation can be: the end time of the most recent period + delta7; wherein delta7 can be specified by the protocol or configured by high-level signaling, mainly considering the delays of TB's HARQ transmission, decoding and decapsulation.
  • the terminal and the network can have a consistent understanding of the time to start executing the predefined operation, and can start executing the predefined operation as early as possible to ensure or improve data transmission performance.
  • the terminal performs a predefined operation according to the data scheduling related information, further comprising:
  • the terminal stops executing the predefined operation
  • the seventh condition includes any of the following:
  • the amount of data scheduled by the terminal in the third time period of the specified transmission direction or the amount of data actually scheduled for the target logical channel or the target logical channel group is less than the eleventh threshold.
  • both sides determine to execute the predefined operation for all or specific Serving cells (start or continue), they can determine to stop executing the predefined operation based on any of the following (i.e., the seventh condition above):
  • the first object targeted by the predefined operation satisfies a predefined condition
  • the first object includes a first time domain unit set or interval opportunity.
  • method 1/2/3 it is determined to execute a predefined operation, or it is determined that the Window (such as Gap occasion or SMTC window, etc.) or Symbol with scheduling restrictions that can execute the predefined operation requires to meet the predefined conditions.
  • the predefined conditions include at least one of the following:
  • the first object is applied to a scenario other than a first scenario, where the first scenario is specified by a protocol or configured by high-level signaling;
  • Window/Symbol with scheduling restrictions is not used for predefined purposes or scenarios1, such as Radio Link Monitoring (RLM) and/or Beam Failure Detection (BFD).
  • RLM Radio Link Monitoring
  • BFD Beam Failure Detection
  • the first object is only applied to the second scenario, and the second scenario is specified by the protocol or configured by high-level signaling;
  • Window/Symbol with scheduling restrictions is only used for predefined purposes or scenarios 2, such as intra/inter-frequency measurement, and/or Positioning, etc.
  • the predefined purposes or scenarios 2 here can be specified by the protocol or configured by high-level signaling.
  • the priority corresponding to the Window meets predefined requirements, including absolute value requirements and/or relative requirements.
  • predefined requirements including absolute value requirements and/or relative requirements.
  • the corresponding priority is required to be lower or not higher than a predefined threshold, or the gapPriority-r17 corresponding to the GapConfig-r17 corresponding to the Gap occasion is required to be greater than or not less than a predefined threshold.
  • the predefined threshold here can be specified by the protocol or configured by high-level signaling.
  • the corresponding priority is the lowest or one of the lowest N priorities among all configured GapConfig-r17s (or, the corresponding gapPriority-r17 is the largest or one of the largest N priorities among all configured GapConfig-r17s), or, the corresponding priority is the lowest or one of the lowest M priorities among the GapConfig-r17 corresponding to the Gap occasion that exists within a period of time (given by the period of time for determining whether to perform the predefined operation in each specific method) (or, the corresponding gapPriority-r17 is the largest or one of the largest M priorities among the GapConfig-r17 corresponding to the Gap occasion that exists within this period of time).
  • the period or length of the Window meets predefined requirements, for example, the period is not longer than a predefined threshold, and/or the length is not shorter than a predefined threshold.
  • the predefined threshold here can be specified by the protocol or configured by high-level signaling.
  • the predefined operation when the predefined operation is to relax scheduling restrictions or disable scheduling restrictions within a first symbol time domain unit set, or to skip gap opportunities or disable gap opportunities, the predefined operation is performed, that is, for one or more of the above methods (methods 1/2/3), when it is determined to perform a predefined operation on a certain Window or Symbol with scheduling restrictions, if the predefined operation is Relax/disable scheduling restrictions during a set of symbols or Skip/disable Gap occasion(s), any of the following is performed:
  • the terminal expects to be scheduled, and the priorities of uplink transmission or downlink reception within the time range corresponding to the first object meet the specified priority requirements;
  • the UE expects to be scheduled only for uplink transmission/downlink reception whose priority meets specific requirements within the Window or Symbol with scheduling restrictions (including the situation that the scheduled uplink transmission/downlink reception is partially or completely within the Window or Symbol with scheduling restrictions; when the scheduled uplink transmission/downlink reception is only partially within the Window or Symbol with scheduling restrictions, it can also be understood that the scheduled uplink transmission/downlink reception overlaps with the Window or Symbol with scheduling restrictions in the time domain), such as high-priority PUSCH/PUCCH/SRS transmission, or the corresponding HARQ-ACK is a high-priority PDSCH reception, or a high-priority PDSCH reception.
  • scheduling restrictions including the situation that the scheduled uplink transmission/downlink reception is partially or completely within the Window or Symbol with scheduling restrictions; when the scheduled uplink transmission/downlink reception is only partially within the Window or Symbol with scheduling restrictions, it can also be understood that the scheduled uplink transmission/downlink reception overlaps with the Window or Symbol with scheduling restrictions in the time domain), such
  • the terminal does not expect to be scheduled, and the priorities corresponding to the uplink transmission or downlink reception that overlaps with the time range corresponding to the first object do not meet the specified priority requirements.
  • the UE does not expect to be scheduled only for uplink transmission/downlink reception whose priority does not meet specific requirements within the Window or Symbol with scheduling restrictions (including the situation that the scheduled uplink transmission/downlink reception is partially or completely within the Window or Symbol with scheduling restrictions; when the scheduled uplink transmission/downlink reception is only partially within the Window or Symbol with scheduling restrictions, it can also be understood that the scheduled uplink transmission/downlink reception overlaps with the Window or Symbol with scheduling restrictions in the time domain), such as high-priority PUSCH/PUCCH/SRS transmission, or the corresponding HARQ-ACK is a high-priority PDSCH reception, or high-priority PDSCH reception.
  • the UE expects to be scheduled for at least one uplink transmission or downlink reception whose priority meets specific requirements within the Window or Symbol with scheduling restrictions, and at this time, scheduling of other uplink transmissions or downlink receptions whose priorities do not meet specific requirements is also allowed (or without restriction).
  • an embodiment of the present application provides a method for adjusting transmission restrictions, the execution subject of the method is a network side device, and the method includes:
  • Step 401 The network side device determines that there is a scheduling restriction or an effective target interval timing in the first serving cell;
  • Step 402 The network side device performs a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • a preset rule is associated with any of the following:
  • the predefined operations include at least one of the following:
  • the relevant content in the network side method can be directly understood by referring to the relevant content in the terminal side method.
  • the terminal side and the network side perform predefined operations based on the same preset rules, so that the terminal side and the network side have a consistent understanding.
  • the terminal side and the network side execute predefined operations according to preset rules associated with any one of the reporting information related to the channel quality of the Serving cell, the reporting information related to the uplink BSR or SR, and the uplink and downlink scheduling related information, to implement a scheme for adjusting transmission restrictions based on rules, and reasonably relax the transmission and reception restrictions brought by the Gap mechanism, and the scheduling restrictions corresponding to the scheduling availability/restrictions, by ensuring that the measurement requirements are not affected or the impact on the measurement performance is reduced, ensuring timely or as timely as possible data transmission, etc., so as to ensure the transmission performance of high data rate and low latency services.
  • the network side device when the preset rule is associated with the reporting information related to the channel quality of the serving cell, the network side device performs a predefined operation according to the preset rule, including:
  • the network-side device When the channel quality of the Serving cell is higher than or equal to the first threshold, the network-side device performs predefined operations based on the reported information related to the channel quality of the Serving cell.
  • the first reporting information includes a measurement report based on layer 3 measurement
  • the network side device performs a predefined operation according to the first reporting information, including any one of the following:
  • the network side device In case of receiving a measurement report based on L3 measurement, the network side device performs a predefined operation, and the measurement report based on L3 measurement is triggered based on a measurement reporting event;
  • the network side device performs a predefined operation according to the channel quality information in the measurement report of the layer 3 measurement.
  • the network side device performs a predefined operation according to the measurement reporting event, including:
  • the network side device After the network side device receives the measurement report based on the L3 measurement reported based on the first event, the network side device performs the predefined operation from the first predefined time;
  • the network side device After the network side device receives the measurement report based on the L3 measurement reported based on the second event, the network side device 2. Stop executing predefined operations at predefined times;
  • the first predefined time is determined based on the transmission time of the measurement report of the layer 3 measurement reported by the first event
  • the second predefined time is determined based on the transmission time of the measurement report of the layer 3 measurement reported by the second event.
  • the network side device performs a predefined operation according to the channel quality information in the measurement report, including:
  • the network side device When the channel quality information in the first measurement report is higher than or equal to the second threshold, the network side device performs the predefined operation from a third predefined time;
  • the network side device stops performing the predefined operation at a fourth predefined time
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report.
  • the network side device performs a predefined operation according to the CSI reporting information of the serving cell, including any of the following:
  • the network side device When the channel quality information in the first CSI report is higher than or equal to the fourth threshold, the network side device performs the predefined operation from the fifth predefined time;
  • the network side device stops performing the predefined operation at a sixth predefined time
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report.
  • the network side device when the preset rule is associated with the relevant reporting information of the uplink BSR or SR, the network side device performs the predefined operation according to the preset rule, including at least one of the following:
  • the network side device When the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the first condition, the network side device performs a predefined operation on the target Serving cell;
  • the network side device When the SR reporting information or uplink BSR reporting information of the target logical channel or target logical channel group meets the second condition, the network side device performs a predefined operation on the target Serving cell;
  • the first condition includes at least one of the following:
  • the waiting time of the data to be transmitted of the target logical channel or the target logical channel group is longer than or equal to the sixth threshold
  • the remaining packet delay budget PDB of the to-be-transmitted data of the target logical channel or the target logical channel group is shorter than or equal to the seventh threshold
  • the amount of data to be transmitted on the target logical channel or the target logical channel group is greater than or equal to an eighth threshold
  • the second condition includes at least one of the following:
  • the network side device actually receives the SR PUCCH for the target logical channel or at least one logical channel in the target logical channel group;
  • the uplink BSR reporting information indicates that there is an amount of data to be transmitted for the target logical channel or the target logical channel group.
  • the network side device performs a predefined operation on the target serving cell, including:
  • the network-side device starts or continues to perform the predefined operation for the target Serving cell from the seventh predefined time;
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information.
  • the network side device when the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the first condition, performs a predefined operation on the target Serving cell, further comprising:
  • the network side device stops executing the predefined operation
  • the third condition includes any of the following:
  • a first preset time length is reached
  • the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information does not meet the first condition.
  • the network side device when the SR reporting information or uplink BSR reporting information of the target logical channel or the target logical channel group meets the second condition, performs a predefined operation on the target Serving cell, including:
  • the network-side device starts or continues to perform the predefined operation for the target Serving cell from the eighth predefined time;
  • the eighth predefined time is determined based on the transmission time of the SR reporting information or the uplink BSR reporting information.
  • the network side device when the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information meets the second condition, performs a predefined operation on the target Serving cell, further comprising:
  • the network side device stops executing the predefined operation
  • the fourth condition includes any of the following:
  • a second preset time period is reached
  • the uplink BSR reporting information indicates that the amount of data to be transmitted for the target logical channel or the target logical channel group is zero.
  • the network side device when the preset rule is associated with the uplink and downlink scheduling related information, the network side device performs a predefined operation according to the preset rule, including:
  • the network side device performs a predefined operation according to the location of the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduled DCI;
  • the network side device performs the predefined operation according to the transmission attribute information indicated in the scheduling DCI;
  • the network side device performs predefined operations based on the data scheduling related information.
  • the network side device performs a predefined operation according to the location of the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI, including any one of the following:
  • the network side device When the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI overlaps with the interval opportunity or the first window in the time domain, or the time domain interval between the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the time domain unit occupied by the interval opportunity or the first window is less than or equal to the ninth threshold, the network side device performs a predefined operation for the interval opportunity or the first window; wherein, the first window is a predefined window with scheduling constraints;
  • the network side device When the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI overlaps with the interval opportunity or the first window, the network side device performs a predefined operation on the area of time domain overlap;
  • the network side device When the time domain interval between the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the time domain unit occupied by the interval opportunity or the first window is less than or equal to the tenth threshold, the network side device performs a predefined operation on the area of extended time domain overlap, and the area of extended time domain overlap is determined based on the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the tenth threshold;
  • the network side device performs a predefined operation for all time domain units with scheduling restrictions within a first time period, where the first time period is determined by the transmission of a PDSCH, CSI-RS, PUSCH, PUCCH or SRS corresponding to the scheduling DCI;
  • the network side device performs predefined operations for all time domain units that have time domain overlap or extended time domain overlap with the second time period and have scheduling restrictions.
  • the second time period is determined by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI.
  • the network side device performs a predefined operation according to the transmission attribute information indicated in the scheduling DCI, including:
  • the network side device When the network side device detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction meets the fifth condition, the network side device performs a predefined operation on the target Serving cell, where N is specified by the protocol or configured by high-level signaling;
  • the fifth condition includes at least one of the following:
  • the size of TB is greater than or equal to the eleventh threshold
  • the physical layer priority is a predefined priority.
  • the network side device when the network side device detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction meets the fifth condition, the network side device performs a predefined operation on the target Serving cell, including:
  • the network side device When the network side device detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction meets the fifth condition, the network side device starts or continues to perform the predefined operation for the target Serving cell from the ninth predefined time;
  • the ninth predefined time is determined based on the transmission time of N consecutive scheduled DCIs.
  • the network side device performs a predefined operation according to the transmission attribute information indicated in the scheduling DCI, further comprising:
  • the network side device stops executing the predefined operation
  • the sixth condition includes any of the following:
  • a third preset time period is reached
  • the network side device detects in the target transmission direction that the transmission attribute information indicated by at least one scheduling DCI in N consecutive scheduling DCIs does not meet the fifth condition.
  • the network side device performs a predefined operation according to the data scheduling related information, including:
  • the network side device When the amount of data scheduled by the network side device in the third time period in the specified transmission direction or the amount of data actually scheduled for the target logical channel or the target logical channel group is greater than or equal to the eleventh threshold, the network side device performs a predefined operation on the target Serving cell;
  • the third time period is specified by a protocol or configured by high-level signaling.
  • the network-side device performs a predefined operation on the target Serving cell, including:
  • the network-side device starts or continues to perform the predefined operation for the target Serving cell from the tenth predefined time;
  • the tenth predefined time is the end time of the third time period plus a preset time interval, and the preset time interval is specified by the protocol or configured by high-level signaling.
  • the network side device performs a predefined operation according to the data scheduling related information, further comprising:
  • the network side device stops executing the predefined operation
  • the seventh condition includes any of the following:
  • a fourth preset time length is reached;
  • the amount of data scheduled by the network side device in the third time period of the specified transmission direction, or the amount of data actually scheduled for the target logical channel or the target logical channel group, is less than the eleventh threshold.
  • the first object targeted by the predefined operation satisfies a predefined condition
  • the first object includes a first time domain unit set or an interval opportunity, and the predefined condition includes at least one of the following:
  • the first object is applied to a scenario other than a first scenario, where the first scenario is specified by a protocol or configured by a high-level signaling;
  • the first object is only applied to the second scenario, where the second scenario is specified by the protocol or configured by high-level signaling;
  • the priority of the first object meets the predefined priority requirement
  • the period or length of the first object meets predefined requirements.
  • performing the predefined operation includes any one of the following:
  • the network side device ensures that the priorities of the uplink transmission or downlink reception within the time range corresponding to the first object meet the specified priority requirements for the terminal scheduling;
  • the network side device ensures that the priorities corresponding to the uplink transmission or downlink reception that overlaps with the time range corresponding to the first object for the terminal scheduling meet the specified priority requirements;
  • the network side device ensures that the terminal is scheduled, and the priority corresponding to at least one of the uplink transmission or downlink reception within the time range corresponding to the first object meets the specified priority requirement;
  • the network side device ensures that the terminal is scheduled, and at least one of the uplink transmissions or downlink receptions that overlaps with the time range corresponding to the first object has a priority level that meets the specified priority requirement.
  • the terminal does not expect the scheduled uplink transmission or downlink reception to occur in the following situation: the priorities of the uplink transmission or downlink reception within the time range corresponding to the first object do not meet the specified priority requirements, or the uplink transmission or downlink reception overlapping the time range corresponding to the first object does not meet the specified priority requirements.
  • the uplink transmission or downlink reception scheduled by the network side device for the terminal requires that: among the uplink transmission or downlink reception within the time range corresponding to the first object, at least one of the uplink transmissions or downlink receptions has a priority that meets the specified priority requirement, or among the uplink transmissions or downlink receptions that overlap with the time range corresponding to the first object, at least one of the uplink transmissions or downlink receptions has a priority that meets the specified priority requirement.
  • the method for adjusting transmission restrictions provided in the embodiment of the present application can be executed by a device for adjusting transmission restrictions.
  • the device for adjusting transmission restrictions provided in the embodiment of the present application is described by taking the method for adjusting transmission restrictions performed by the device for adjusting transmission restrictions as an example.
  • an embodiment of the present application provides a device for adjusting transmission restriction, which can be applied to a terminal, and includes:
  • a first determining module 501 is used to determine whether there is a scheduling restriction or a valid target interval timing in the first serving cell
  • a first execution module 502 configured to execute a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • the first execution module is specifically configured to:
  • the predefined operation is performed according to the reporting information related to the channel quality of the serving cell.
  • the first reporting information includes a measurement report based on layer 3 measurement
  • the first execution module is specifically used for any of the following:
  • the predefined operation is performed according to the channel quality information in the measurement report of the layer 3 measurement.
  • the first execution module is specifically configured to:
  • the first predefined time is determined based on a transmission time of a measurement report of layer 3 measurement sent by the first event
  • the second predefined time is determined based on a transmission time of a measurement report of layer 3 measurement sent by the second event.
  • the first execution module is specifically configured to:
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report.
  • the first reporting information includes a channel state information CSI report
  • the first execution module is specifically used for any one of the following:
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report.
  • the first execution module is specifically used for at least one of the following:
  • the first condition includes at least one of the following:
  • the waiting time of the data to be transmitted of the target logical channel or the target logical channel group is longer than or equal to the sixth threshold
  • the remaining packet delay budget PDB of the to-be-transmitted data of the target logical channel or the target logical channel group is shorter than or equal to the seventh threshold
  • the amount of data to be transmitted on the target logical channel or target logical channel group is higher than or equal to an eighth threshold
  • the second condition includes at least one of the following:
  • the terminal triggers and actually sends an SR PUCCH for the target logical channel or at least one logical channel in the target logical channel group;
  • the uplink BSR reporting information indicates that there is an amount of data to be transmitted for the target logical channel or the target logical channel group.
  • the first execution module when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a first condition, is specifically configured to:
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information.
  • the first execution module when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a first condition, is specifically configured to:
  • the third condition includes any one of the following:
  • a first preset time length is reached
  • the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information does not meet the first condition.
  • the first execution module is specifically used to:
  • the eighth predefined time is determined based on the transmission time of the SR reporting information or the uplink BSR reporting information.
  • the first execution module when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a second condition, is specifically configured to:
  • the fourth condition includes any one of the following:
  • a second preset time period is reached
  • the uplink BSR reporting information indicates that the amount of data to be transmitted for the target logical channel or the target logical channel group is zero.
  • the first execution module is specifically configured to:
  • the first execution module is specifically used for any of the following:
  • the predefined operation is performed for the interval opportunity or the first window; wherein the first window is a predefined window with the scheduling restriction;
  • the predefined operation is performed on the area of extended time domain overlap, and the area of extended time domain overlap is determined based on the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the tenth threshold;
  • the predefined operation for all time domain units within the scheduling restriction within a first time period where the first time period is determined by the transmission of a PDSCH, a CSI-RS, a PUSCH, a PUCCH or an SRS corresponding to the scheduling DCI;
  • Predefined operations are performed for all time domain units that have time domain overlap or extended time domain overlap with the second time period and have the scheduling restriction, and the second time period is determined by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI.
  • the first execution module is specifically configured to:
  • the terminal When the terminal detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction all meets the fifth condition, performing the predefined operation on the target serving cell, where N is specified by the protocol or configured by high-level signaling;
  • the fifth condition includes at least one of the following:
  • the size of TB is greater than or equal to the eleventh threshold
  • the physical layer priority is a predefined priority.
  • the first execution module is specifically configured to:
  • the N is specified by a protocol or configured by high-level signaling, and the ninth predefined time is determined based on the transmission time of the N consecutive scheduled DCIs.
  • the first execution module is specifically configured to:
  • the sixth condition includes any one of the following:
  • a third preset time period is reached;
  • the terminal detects in the target transmission direction that transmission attribute information indicated by at least one scheduling DCI in N consecutive scheduling DCIs does not satisfy the fifth condition.
  • the first execution module is specifically configured to:
  • the third time period is specified by a protocol or configured by high-level signaling.
  • the first execution module is specifically configured to:
  • the tenth predefined time is the end time of the third time period plus a preset time interval, and the preset time interval is specified by a protocol or configured by high-level signaling.
  • the first execution module is specifically configured to:
  • the seventh condition includes any one of the following:
  • a fourth preset time length is reached;
  • the amount of data scheduled by the terminal in a third time period in a specified transmission direction, or the amount of data actually scheduled for a target logical channel or a target logical channel group, is less than an eleventh threshold.
  • the first object targeted by the predefined operation satisfies a predefined condition
  • the first object includes the first time domain unit set or the interval opportunity, and the predefined condition includes at least one of the following:
  • the first object is applied to a scenario other than a first scenario, where the first scenario is specified by a protocol or configured by high-layer signaling;
  • the first object is only applied to a second scenario, where the second scenario is specified by a protocol or configured by high-level signaling;
  • the priority of the first object meets a predefined priority requirement
  • the period or length of the first object meets a predefined requirement.
  • the first execution module is specifically used for any one of the following:
  • the terminal expects to be scheduled, and the priorities corresponding to uplink transmission or downlink reception within the time range corresponding to the first object meet the specified priority requirements;
  • the terminal expects to be scheduled, and the priorities corresponding to uplink transmission or downlink reception overlapping with the time range corresponding to the first object meet the specified priority requirements;
  • the terminal does not expect to be scheduled, and the priorities corresponding to uplink transmission or downlink reception within the time range corresponding to the first object do not meet the specified priority requirement;
  • the terminal does not expect to be scheduled, and the priorities corresponding to uplink transmission or downlink reception overlapping with the time range corresponding to the first object do not meet the specified priority requirements.
  • an embodiment of the present application provides a device for adjusting transmission restrictions, the device being applied to a network side device, and the device comprising:
  • the second determination module 601 is used to determine whether there is a scheduling restriction in the target serving cell or whether there is a sending and receiving restriction corresponding to the target interval timing;
  • the second execution module 602 is used to execute a predefined operation according to a preset rule
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • the second execution module is configured to:
  • the predefined operation is performed according to the reporting information related to the channel quality of the serving cell.
  • the first reporting information includes a measurement report based on layer 3 measurement
  • the first execution module is specifically used for any of the following:
  • the first execution module is specifically configured to:
  • the network side device After the network side device receives the measurement report based on the L3 measurement reported based on the first event, performing the predefined operation from a first predefined time;
  • the network side device After the network side device receives the measurement report based on the L3 measurement reported based on the second event, stopping executing the predefined operation at a second predefined time;
  • the first predefined time is determined based on a transmission time of a measurement report of layer 3 measurement reported by the first event
  • the second predefined time is determined based on a transmission time of a measurement report of layer 3 measurement reported by the second event.
  • the second execution module is used to:
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report.
  • the first reporting information includes a channel state information CSI report
  • the second execution module is used for any one of the following:
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report.
  • the second execution module is configured to perform at least one of the following:
  • the first condition includes at least one of the following:
  • the waiting time of the data to be transmitted of the target logical channel or the target logical channel group is longer than or equal to the sixth threshold
  • the remaining packet delay budget PDB of the to-be-transmitted data of the target logical channel or the target logical channel group is shorter than or equal to the seventh threshold
  • the amount of data to be transmitted on the target logical channel or target logical channel group is higher than or equal to an eighth threshold
  • the second condition includes at least one of the following:
  • the network side device actually receives the SR PUCCH for the target logical channel or at least one logical channel in the target logical channel group;
  • the uplink BSR reporting information indicates that there is an amount of data to be transmitted for the target logical channel or the target logical channel group.
  • the second execution module is used to:
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information.
  • the second execution module is used to:
  • the third condition includes any one of the following:
  • a first preset time length is reached
  • the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information does not meet the first condition.
  • the second execution module is used to:
  • the eighth predefined time is determined based on the transmission time of the SR reporting information or the uplink BSR reporting information.
  • the second execution module is configured to:
  • the fourth condition includes any one of the following:
  • a second preset time length is reached
  • the uplink BSR reporting information indicates that the amount of data to be transmitted for the target logical channel or the target logical channel group is zero.
  • the second execution module is configured to:
  • the second execution module is used for any of the following:
  • the predefined operation is performed for the interval opportunity or the first window; wherein the first window is a predefined window with the scheduling restriction;
  • the time domain interval between the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the time domain unit occupied by the interval opportunity or the first window is less than or equal to the tenth threshold, performing the predefined operation on the area of extended time domain overlap, and the area of extended time domain overlap is determined based on the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the tenth threshold;
  • the predefined operation for all time domain units within the scheduling restriction within a first time period where the first time period is determined by the transmission of a PDSCH, a CSI-RS, a PUSCH, a PUCCH or an SRS corresponding to the scheduling DCI;
  • Predefined operations are performed for all time domain units that have time domain overlap or extended time domain overlap with the second time period and have the scheduling restriction, and the second time period is determined by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI.
  • the second execution module is used to:
  • the predefined operation is performed on the target Serving cell, where N is specified by the protocol or configured by high-level signaling;
  • the fifth condition includes at least one of the following:
  • the size of TB is greater than or equal to the eleventh threshold
  • the physical layer priority is a predefined priority.
  • the network side device detects the transmission attributes indicated in N consecutive scheduling DCIs in the target transmission direction.
  • the second execution module is used to:
  • the predefined operation is started or continued to be performed for the target Serving cell from a ninth predefined time;
  • the ninth predefined time is determined based on the transmission time of the N consecutive scheduled DCIs.
  • the second execution module is used to:
  • the sixth condition includes any one of the following:
  • a third preset time length is reached
  • the network side device detects in the target transmission direction that the transmission attribute information indicated by at least one scheduling DCI in N consecutive scheduling DCIs does not meet the fifth condition.
  • the second execution module is used to:
  • the predefined operation is performed on the target Serving cell;
  • the third time period is specified by a protocol or configured by high-level signaling.
  • the second execution module is used to:
  • the tenth predefined time is the end time of the third time period plus a preset time interval, and the preset time interval is specified by a protocol or configured by high-level signaling.
  • the second execution module is used to:
  • the seventh condition includes any one of the following:
  • a fourth preset time length is reached;
  • the amount of data scheduled by the network side device in the third time period of the specified transmission direction, or the amount of data actually scheduled for the target logical channel or the target logical channel group, is less than the eleventh threshold.
  • the first object targeted by the predefined operation satisfies a predefined condition
  • the first object includes the first time domain unit set or the interval opportunity, and the predefined condition includes at least one of the following:
  • the first object is applied to a scenario other than a first scenario, where the first scenario is specified by a protocol or configured by high-layer signaling;
  • the first object is only applied to a second scenario, where the second scenario is specified by a protocol or configured by high-level signaling;
  • the priority of the first object meets a predefined priority requirement
  • the period or length of the first object meets a predefined requirement.
  • the second execution module is used for any one of the following:
  • the device for adjusting the transmission restriction 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 the 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.
  • the terminal may include but is not limited to the types of terminal 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.
  • the device for adjusting transmission restrictions provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702, wherein the memory 702 stores a program or instruction that can be run on the processor 701.
  • 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.
  • 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.
  • the embodiment of the present application also provides a terminal, 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 in the 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.
  • Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • 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.
  • the terminal 800 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 810 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the terminal structure shown in FIG8 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042.
  • 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 unit 806 may include a display panel 8061, which 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, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the radio frequency unit 801 after receiving downlink data from the network side device, 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.
  • 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.
  • 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.
  • the memory 809 may include a volatile memory or a non-volatile memory.
  • 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).
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct memory bus random access memory
  • 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.
  • the processor 810 is configured to determine whether there is a scheduling restriction or a valid target interval timing in the first serving cell;
  • the processor 810 is used to execute a predefined operation according to a preset rule
  • the first serving cell is any serving cell configured by the terminal
  • the preset rule is associated with any of the following:
  • the predefined operation includes at least one of the following:
  • An interval pattern parameter corresponding to at least one interval opportunity among the target interval opportunities is adjusted.
  • the processor 810 is specifically configured to:
  • the predefined operation is performed according to the reporting information related to the channel quality of the serving cell.
  • the first reporting information includes a measurement report based on layer 3 measurement
  • the processor 810 is specifically configured to perform any of the following:
  • the predefined operation is performed according to the channel quality information in the measurement report of the layer 3 measurement.
  • the processor 810 is specifically configured to:
  • the first predefined time is determined based on a transmission time of a measurement report of layer 3 measurement sent by the first event
  • the second predefined time is determined based on a transmission time of a measurement report of layer 3 measurement sent by the second event.
  • the processor 810 is specifically configured to:
  • the third predefined time is determined based on the transmission time of the first measurement report, and the fourth predefined time is determined based on the transmission time of the second measurement report.
  • the first reporting information includes a channel state information CSI report
  • the processor 810 is specifically configured to do any one of the following:
  • the fifth predefined time is determined based on the transmission time of the first CSI report
  • the sixth predefined time is determined based on the transmission time of the second CSI report.
  • the processor 810 is specifically configured to do at least one of the following:
  • the reporting information for the target logical channel or target logical channel group in the uplink BSR reporting information meets the first condition In the case of, performing the predefined operation on the target serving cell;
  • the first condition includes at least one of the following:
  • the waiting time of the data to be transmitted of the target logical channel or the target logical channel group is longer than or equal to the sixth threshold
  • the remaining packet delay budget PDB of the to-be-transmitted data of the target logical channel or the target logical channel group is shorter than or equal to the seventh threshold
  • the amount of data to be transmitted on the target logical channel or target logical channel group is higher than or equal to an eighth threshold
  • the second condition includes at least one of the following:
  • the terminal triggers and actually sends an SR PUCCH for the target logical channel or at least one logical channel in the target logical channel group;
  • the uplink BSR reporting information indicates that there is an amount of data to be transmitted for the target logical channel or the target logical channel group.
  • the processor 810 when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a first condition, is specifically configured to:
  • the seventh predefined time is determined based on the transmission time of the uplink BSR reporting information.
  • the processor 810 when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a first condition, is specifically configured to:
  • the third condition includes any one of the following:
  • a first preset time length is reached
  • the reporting information for the target logical channel or the target logical channel group in the uplink BSR reporting information does not meet the first condition.
  • the processor 810 is specifically configured to:
  • the eighth predefined time is determined based on the transmission time of the SR reporting information or the uplink BSR reporting information.
  • the processor 810 when reporting information for a target logical channel or a target logical channel group in the uplink BSR reporting information satisfies a second condition, the processor 810 is specifically configured to:
  • the fourth condition includes any one of the following:
  • a second preset time length is reached
  • the uplink BSR reporting information indicates that the amount of data to be transmitted for the target logical channel or the target logical channel group is zero.
  • the processor 810 is specifically configured to:
  • processor 810 is specifically configured to perform any of the following:
  • the predefined operation is performed for the interval opportunity or the first window; wherein the first window is a predefined window with the scheduling restriction;
  • the time domain interval between the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the time domain unit occupied by the interval opportunity or the first window is less than or equal to the tenth threshold, performing the predefined operation on the area of extended time domain overlap, and the area of extended time domain overlap is determined based on the time domain unit occupied by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI and the tenth threshold;
  • the predefined operation for all time domain units within the scheduling restriction within a first time period where the first time period is determined by the transmission of a PDSCH, a CSI-RS, a PUSCH, a PUCCH or an SRS corresponding to the scheduling DCI;
  • Predefined operations are performed for all time domain units that have time domain overlap or extended time domain overlap with the second time period and have the scheduling restriction, and the second time period is determined by the PDSCH, CSI-RS, PUSCH, PUCCH or SRS transmission corresponding to the scheduling DCI.
  • the processor 810 is specifically configured to:
  • the terminal When the terminal detects that the transmission attribute information indicated in N consecutive scheduling DCIs in the target transmission direction all meets the fifth condition, performing the predefined operation on the target serving cell, where N is specified by the protocol or configured by high-level signaling;
  • the fifth condition includes at least one of the following:
  • the size of TB is greater than or equal to the eleventh threshold
  • the physical layer priority is a predefined priority.
  • the processor 810 is specifically configured to:
  • the N is specified by a protocol or configured by high-level signaling, and the ninth predefined time is determined based on the transmission time of the N consecutive scheduled DCIs.
  • the processor 810 is specifically configured to:
  • the sixth condition includes any one of the following:
  • a third preset time period is reached;
  • the terminal detects in the target transmission direction that transmission attribute information indicated by at least one scheduling DCI in N consecutive scheduling DCIs does not satisfy the fifth condition.
  • the processor 810 is specifically configured to:
  • the third time period is specified by a protocol or configured by high-level signaling.
  • the processor 810 is specifically configured to:
  • the tenth predefined time is the end time of the third time period plus a preset time interval, and the preset time interval is specified by a protocol or configured by high-level signaling.
  • the processor 810 is specifically configured to:
  • the seventh condition includes any one of the following:
  • a fourth preset time length is reached;
  • the amount of data scheduled by the terminal in a third time period in a specified transmission direction, or the amount of data actually scheduled for a target logical channel or a target logical channel group, is less than an eleventh threshold.
  • the first object targeted by the predefined operation satisfies a predefined condition
  • the first object includes the first time domain unit set or the interval opportunity, and the predefined condition includes at least one of the following:
  • the first object is applied to a scenario other than a first scenario, where the first scenario is specified by a protocol or configured by high-layer signaling;
  • the first object is only applied to a second scenario, where the second scenario is specified by a protocol or configured by high-level signaling;
  • the priority of the first object meets a predefined priority requirement
  • the period or length of the first object meets a predefined requirement.
  • the processor 810 is specifically configured to do any one of the following:
  • the priority corresponding to the uplink transmission or downlink reception that is expected to be scheduled and overlaps with the time range corresponding to the first object The priority levels all meet the specified priority requirements;
  • the priorities of uplink transmission or downlink reception that are not expected to be scheduled and overlap with the time range corresponding to the first object do not meet the specified priority requirements.
  • 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 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.
  • the embodiment of the present application also provides a network side device.
  • 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.
  • the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing.
  • 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.
  • 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.
  • the baseband device 93 may include, for example, at least one baseband board, on which a plurality of chips are arranged, as shown in FIG. 9 , wherein one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call a program in the memory 95 and execute the network device operations shown in the above method embodiment.
  • the network side device may also include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and executable on the processor 94.
  • the processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by the modules shown in Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a network side device.
  • 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).
  • CPRI common public radio interface
  • the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1003 and executable on the processor 1001.
  • the processor 1001 calls the instructions or programs in the memory 1003 to execute the method executed by each module shown in Figure 6 and achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • each process of the above-mentioned method embodiment for adjusting the transmission restriction is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • 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.
  • the readable storage medium may be a non-transient readable storage medium.
  • 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 for adjusting the transmission restriction, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • 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.
  • 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 embodiment for adjusting the transmission restriction, and can achieve the same technical effect. To avoid repetition, it will not be described here.
  • 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 as described above, and the network side device can be used to execute the steps of the network side method as described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种调整传输限制的方法、装置、设备及可读存储介质，属于通信技术领域，方法包括：终端与网络侧设备确定第一服务小区中存在调度限制或存在生效的目标间隔时机，终端与网络侧设备根据预设规则，执行预定义操作；其中，第一服务小区为终端配置的任意一个服务小区；预设规则与以下任意一项相关联：与服务小区的信道质量相关的第一上报信息；与上行缓冲状态报告BSR或调度请求SR相关的第二上报信息；与上下行调度相关的调度信息；预定义操作包括以下至少一项：在第一时域单元集内放松调度限制或禁用调度限制；跳过或禁用目标间隔时机中的至少一个间隔时机；调整目标间隔时机中的至少一个间隔时机对应的间隔图样参数。

Description

调整传输限制的方法、装置、设备及可读存储介质
相关申请的交叉引用
本申请主张在2023年08月07日提交的中国专利申请No.202310990766.8的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种调整传输限制的方法、装置、设备及可读存储介质。
背景技术
新空口(New Radio，NR)中为了支持无线资源管理测量(Radio Resource Management measurements，RRM measurements)、定位(Positioning)、小区全球识别码报告(Cell Global Identity reporting，CGI reporting)、多通用用户身份模块操作(multi universal subscriber identity module operation，MUSIM operation)、传输功率管理(Tx power management)等，引入了多种间隔(Gap)机制，以及对应的数据收发限制。同时，为了保障RRM measurements、无线链路管理(Radio Link Management，RLM)、波束失败检测(Beam Failure Detection，BFD)等的性能，引入了调度可用性/限制(scheduling availability/restrictions)的诸多规定。而上述Gap机制及其对应的收发限制，以及scheduling availability/restrictions规定对应的调度限制，会增大数据传输时延、降低业务容量等，影响通信性能。
发明内容
本申请实施例提供一种调整传输限制的方法、装置、设备及可读存储介质，能够实现合理地放松Gap机制带来的收发限制，以及scheduling availability/restrictions规定对应的调度限制，以保障高数据速率低时延业务的传输性能。
第一方面，提供了一种调整传输限制的方法，包括：
终端确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
所述终端根据预设规则，执行预定义操作；
其中，所述第一服务小区为所述终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行缓冲状态报告BSR或调度请求SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第二方面，提供了一种调整传输限制的方法，包括：
网络侧设备确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
所述网络侧设备根据预设规则，执行预定义操作；
其中，所述第一服务小区为终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第三方面，提供了一种调整传输限制的装置，包括：
第一确定模块，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；第一执行模块，用于根据预设规则，执行预定义操作；
其中，所述第一服务小区为所述终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第四方面，提供了一种调整传输限制的装置，包括：
第二确定模块，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；第二执行模块，用于根据预设规则，执行预定义操作；
其中，所述第一服务小区为终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关上报信息；
与上行BSR或SR相关的第一上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于：
确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
根据预设规则，执行预定义操作；
其中，所述第一服务小区为所述终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行缓冲状态报告BSR或调度请求SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于：
确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
根据预设规则，执行预定义操作；
其中，所述第一服务小区为终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序 或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法，或实现如第二方面所述的方法。
在本申请实施例中，终端侧和网络侧根据与Serving cell的信道质量相关上报信息、上行BSR或SR的相关上报信息和上下行调度相关信息中任意一项相关联预设规则，在第一时域单元集内放松所述调度限制或禁用所述调度限制，或，跳过或禁用所述目标间隔时机中的至少一个间隔时机，或，调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数，尽可能释放调度限制或间隔时机，以减小数据时延，提高业务容量，在不影响测量需求或降低对测量性能的影响的前提下，保证及时或尽量及时的数据传输，从而保障业务的传输性能。
附图说明
图1a是本申请实施例可应用的一种无线通信系统的框图；
图1b是NCSG的参数示意图；
图2是本申请实施例提供的调整传输限制的方法流程示意图之一；
图3是基于Serving cell的L3测量上报或L1 CSI上报确定开始执行预定义操作的场景示意图；
图4是本申请实施例提供的调整传输限制的方法流程示意图之二；
图5是本申请实施例提供的调整传输限制的装置结构示意图之一；
图6是本申请实施例提供的调整传输限制的装置结构示意图之二；
图7是本申请实施例提供的通信设备的结构示意图；
图8是本申请实施例提供的终端的结构示意图；
图9是本申请实施例提供的网络侧设备的结构示意图之一；
图10是本申请实施例提供的网络侧设备的结构示意图之二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本 领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1a示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说 明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)、统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)、网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
为了更好地理解本申请的技术方案，首先对以下内容进行介绍：
扩展现实(eXtended reality，XR)是指由计算机技术和可穿戴设备产生的所有真实与虚拟的组合环境和人机交互。它包括增强现实(Augmented Reality，AR)、混合现实(Mixed Reality，MR)、虚拟现实(Virtual Reality，VR)等代表性形式，以及它们之间的交叉领域。虚拟世界的级别从部分感官输入到完全沉浸式虚拟现实。XR的一个关键方面是人类经验的扩展，尤其是与存在感(以VR为代表)和认知习得(以AR为代表)相关的经验。
对于VR业务，上行以较为密集的小数据包传输为主，这些小数据包可承载手势、控制等信息，作为下行呈现数据的输入和参考；下行以视频和音频等多媒体数据传输为主，通过这些多媒体数据的及时接收以及呈现，向用户提供沉浸式的感受。以下行视频数据为例，视频数据可以建模为基于每秒帧数(Frames Per Second，FPS)(帧率)的视频帧(Video frame)， FPS的典型值为60或120。这些Video frame基于FPS确定的周期(为1/FPS秒)周期性或准周期性到达，并且Video frame的大小动态变化。每个Video frame在空口一般要求在10ms内成功传输，并且传输成功率要求不低于99％甚至99.9％。此外，下行视频数据一般要求很高的数据速率，一般可达几十甚至上百Mbps(典型值为30/45Mbps)
对于AR业务，上行除了上述密集小数据包传输之外，也可能传输视频和音频、场景画面等多媒体数据，其业务特性和下行类似，通常数据速率相对较低，例如最多几十Mbps(典型值为10/20Mbps)，空口传输的时间限也可以放宽，例如每个Video frame一般要求在30ms内成功传输；下行数据传输特性基本与VR业务一致。
NR中的Gap机制
基本测量间隔(Measurement gap，MG)的配置：
如果UE需要测量间隔来识别和测量频率内小区和/或频率间小区和/或者无线接入技术(Radio Access Technology，RAT)间演进的陆地无线接入网(Evolved UMTS Terrestrial Radio Access Network，E-UTRAN)小区：
(1)如果UE不支持不同频率范围的独立测量间隔模式，则网络必须提供单个UE级测量间隔模式(per-UE measurement gap pattern)以并发监测所有频率层。
(2)如果UE支持针对不同频率范围的独立测量间隔模式，则网络必须提供：针对频率范围的频率范围(Frequency Range，FR)级(per-FR；)测量间隔模式(其中UE需要频率范围级测量间隔以独立地针对每个频率范围并发监测其所有频率层)，或者单个UE级测量间隔模式以并发监测所有频率范围的所有频率层。
配置了Measurement gap时的UE行为：
在UE级测量间隔(per-UE measurement gap)期间，UE：
(1)对于演进的UMTS地面无线接入-新空口(Evolved Universal Terrestrial Radio Access-New Radio，E-UTRA-NR)双连接，除了用于无线资源管理(Radio resource management，RRM)测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应的演进的UMTS陆地无线接入网络(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)主小区(Primary cell，PCell)、E-UTRAN辅小区(Secondary Cell，SCell)和NR服务小区进行接收/发送。
(2)对于独立组网(Standalone Architecture，SA)(配置单载波或载波聚合(carrier aggregation，CA))，除了用于RRM测量、定位参考信号(Positioning Reference Signal，PRS)测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应的NR服务小区进行接收/发送。
(3)对于NR-E-UTRA双连接，除了用于RRM测量、PRS测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应PCell、SCell和E-UTRAN服务小区进行接收/发送。
(4)对于NR-DC，除了用于RRM测量、PRS测量的信号的接收，以及用于随机接入 过程的信号之外，不需要从相应的NR服务小区进行接收/向相应的NR服务小区进行发送。
在FR级测量间隔(per-FR measurement gap)期间，UE：
(1)对于E-UTRA-NR双连接，在对应的频率范围内，除了用于RRM测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应的E-UTRAN PCell、E-UTRAN SCell和NR服务小区进行接收/发送。
(2)对于SA(配置了单载波或CA)，在对应的频率范围内，除了用于RRM测量、PRS测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应的NR服务小区进行接收/发送。
(3)对于NR-E-UTRA双连接，在对应的频率范围内，除了用于RRM测量、PRS测量的信号的接收，以及用于随机接入过程的信号之外，不需要从/向相应PCell、SCell和E-UTRAN服务小区进行接收/发送。
(4)对于NR-DC，在对应的频率范围内，除了用于RRM测量、PRS测量的信号的接收，以及用于随机接入过程的信号之外，不需要从相应的NR服务小区进行接收/向相应的NR服务小区进行发送。
基于Measurement gap的衍生/增强机制：
在上述per-UE measurement gap或per-FR measurement gap的配置及UE行为的基础上，NR中进一步引入了如下衍生或增强机制：
测量间隔共享(Measurement gap sharing)
当频率内测量(Intra-frequency measurement)和频率间测量(Inter-frequency measurement)中的任一个都需要占用Measurement gap，或者，影响Measurement gap的使用(例如，基于同步信号块(Synchronization Signal Block，SSB)的测量对应的SSB测量定时配置(SSB Measurement Timing Configuration，SMTC)窗口(window)与Measurement gap完全交叠)时，需要考虑Measurement gap在Intra-frequency measurement和Inter-frequency measurement之间的共享。
具体地，当基于UE粒度或FR粒度同时满足以下各个条件时，应用针对per-UE measurement gap或与FR对应的per-FR measurement gap的Measurement gap sharing：
条件1：intra-frequency measurement需要占用Measurement gap，或者影响Measurement gap的使用；
条件2：inter-frequency/RAT measurement需要占用Measurement gap，或者inter-frequency measurement不需要占用Measurement gap但影响Measurement gap的使用；
条件3：UE被配置测量定位频率层(positioning frequency layers)。
对于Measurement gap sharing，通过网络配置无线资源控制(Radio Resource Control，RRC)参数MeasGapSharingScheme进行控制。
预配置的测量间隔(Pre-configured measurement gap):
相对于基本的Measurement gap，进一步引入了激活(Activation)/去激活(Deactivation) 机制。当某个配置的Pre-configured measurement gap被激活之后，其操作与基本的Measurement gap完全相同。
对于Activation/Deactivation机制，可以进一步区分如下两种机制：
(1)自主激活/去激活机制(Autonomous activation/deactivation mechanism)
UE可以基于触发条件中的任何一个或任意组合自主地将Pre-MG状态从激活改变为去激活，反之亦然。
(2)网络控制的激活/去激活机制(Network-controlled activation/deactivation mechanism)
UE基于网络侧配置的RRC参数preConfGapStatus确定某个Pre-configured MG为Activated或Deactivated。
并发测量间隔(Concurrent measurement gaps):
相对于基本的Measurement gap，允许为UE配置存在MG时机的碰撞(Collision of MG occasions)的间隔组合(Gap combination)。
当UE不支持配置per-FR MG时，网络可为UE配置最多两个per-UE MG类型(pattern)；当UE支持配置per-FR MG时，网络可为UE配置MG类型的组合(Combination of MG patterns)。
Collision of MG occasions的判断:当判断存在Collision时，基于为Measurement gap配置的优先级(Priority)进行处理：应用对应高优先级(Higher priority)的MG occasion(生效)，并丢弃(drop)对应低优先级(Lower priority)的MG occasion(不生效)。要求任意两个被判断存在Collision的MG occasion都存在对应的Priority，并且对应的Priority不同。
其它(独立于Measurement gap的)Gap机制：
在NR中，进一步引入了如下Gap机制：
(1)网络控制小间隔(Network controlled small gap，NCSG)
当配置采用NCSG时，不允许同时配置其它MG。
NCSG各参数的示意图参见图1b。
(a)可见中断长度(visible interruption length，VIL)1and VIL2
VIL1是测量长度(measurement length，ML)之前的可见中断长度，VIL2是ML之后的可见中断长度。在VIL1和VIL2期间，UE不期望发送和接收任何数据。
(b)测量长度(measurement length，ML)
ML是测量长度。
在ML期间，UE是否期望在相应的服务载波上发送和接收数据取决于调度限制要求。
(c)可见中断重复周期(Visible interruption Repetition Period，VIRP)
VIRP是可见中断重复周期。
NCSG配置(Configurations)表格与Measurement gap的配置表格不同。
多通用用户身份模块(Multi-USIM，MUSIM)gap：
MUSIM gap用于MUSIM operation，例如目标网络中目标小区的小区识别和测量、寻呼 监控、系统消息块(System Information Block，SIB)获取和/或按需系统信息(System Information，SI)请求。
目前理解UE在MUSIM gap中的数据收发限制为沿用与Measurement gap相同的限制。
MUSIM Gap Pattern Configurations表格与Measurement gap的配置表格不同。
上行(Uplink，UL)gap用于Tx功率管理(power management)
UL gap用于NR FR2的Tx power management，在下述场景中对于部分上行传输存在限制。
当在FR2单CC场景、FR2频段内CA场景，或者UE不支持tx-Support-UL-GapFR2-r17的FR2频段间CA场景中，UL间隔与NR服务小区中的上行传输交叠时，在UL间隔期间，UE在NR服务小区上除了列出的指定上行传输之外，不需要进行其它任何上行传输。UL Gap Pattern Configurations表格与Measurement gap的配置表格不同。
NR中的对调度可用性的限制(Restrictions on scheduling availability)规定
考虑到UE侧的RRM操作，在前述Gap机制的UE侧数据收发限制之外，在UE(可能)执行RRM操作的时间段(或其中的符号子集)还进一步引入了Restrictions on scheduling availability相关规定。其中，下述列出的情况(Case)都是关注UE未处于Measurement gap期间的调度限制(Scheduling restrictions)(部分带with NCSG标注的Case是针对UE在NCSG的ML期间的Scheduling restrictions，此时UE不允许同时配置其它MG)。
在UE(可能)执行RRM操作的时间段引入Restrictions on scheduling availability的考虑因素大致包括：
因素1：上下行传输方向之间的切换
(1)影响(Impacts)
此时只影响上行传输：UE不期望发送物理上行控制信道(Physical Uplink Control Channel，PUCCH)/物理上行共享信道(Physical Uplink Shared Channel，PUSCH)/探测参考信号(Sounding Reference Signal，SRS)；
(2)涉及的情况(Involved cases)
情况(CASE)I:UE在时分双工(Time Division Duplexing，TDD)频段执行测量(在FR1上(注11))
Case 1:NR基于SSB无需MG(或使用NCSG)的同频测量；
Scheduling restrictions涉及的符号：SMTC窗口持续时间内的SSB符号、接收信号强度指示(Received Signal Strength Indication，RSSI)测量符号(仅适用于SS-RSRQ测量)以及前述符号之前/之后的一些数据符号；
扩展到其他服务小区：注12；注13；
Case 2:NR基于SSB无需MG(或使用NCSG)的异频测量；
Scheduling restrictions涉及的符号：SMTC窗口持续时间内的SSB符号、RSSI测量符号(仅适用于SS-RSRQ测量)以及前述符号之前/之后的一些数据符号；
扩展到其他服务小区：注12；注13(仅适用于使用NCSG的情况)；
Case 3:FR1/FR2上的跨链路干扰(Cross Link Interference，CLI)(SRS-RSRP/CLI-RSSI)测量(总是不需要MG)；
Scheduling restrictions涉及的符号：执行CLI测量的OFDM符号以及这些OFDM符号之前的一些数据符号；
扩展到其他服务小区：注12；
Case 4:NR基于CSI-RS的同频测量(总是不需要MG)；
关注的符号：配置的CSI-RS资源符号以及这些符号之前/之后的一些数据符号；
扩展到其他服务小区：注12；
注11:对于Case3和Case4，不限于FR1
注12：Scheduling restrictions适用于同一频段内的其他服务小区(可以理解的是，注12同时适用于上述Case 1/2/3/4)
具体地，当执行TDD频段内载波聚合时，针对某个给定服务小区的调度限制也应当应用到同一频段中的所有其他服务小区，并适用于其他服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号。
注13：当针对某一其他频段，UE针对当前频段与此其他频段构成的频段对不支持simultaneousRxTxInterBandCA(频段间CA同时收发)时，Scheduling restrictions适用于此其他频段内的服务小区
具体地，当执行TDD频段间载波聚合时，针对某个给定服务小区的调度限制也应当应用到其他频段中的服务小区，并适用于此服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号，如果UE针对给定服务小区所在的频段和此其他频段构成的频段对不具备支持simultaneousRxTxInterBandCA的能力的话。
因素2：FR1不同DL SCS之间的切换
(1)Impacts
此时同时影响上行传输和下行接收：UE不期望发送PUCCH/PUSCH/SRS或接收PDCCH/物理下行共享信道(Physical downlink shared channel，PDSCH)/用于跟踪的CSI-RS(CSI-RS for tracking，TRS)/用于信道质量指示(Channel quality indicator，CQI)的CSI-RS。上述带括号的项仅针对下述部分Case生效。
(2)涉及的情况(Involved cases)
针对不支持simultaneousRxDataSSB-DiffNumerology(同时接收子载波间隔(Subcarrier Spacing，SCS)不同的数据和SSB)能力(此能力涉及同频测量(包括不需要MG或使用NCSG的情况)，层1参考信号接收功率(Layer 1reference signal received power，L1-RSRP)测量(包括L1-RSRP上报或L1-RSRP用于候选波束检测的情况)，层1信号与干扰加噪声比(Layer 1signal-to-noise and interference ratio，L1-SINR)测量，无线链路监测，波束失败检测等情况)或不支持simultaneousRxDataSSB-DiffNumerology-Inter-r16(同时接收不同频 段上SCS不同的数据和SSB)能力(此能力涉及异频测量)的UE，基于SSB的操作；
CASE I:UE在FR1使用与PDSCH/PDCCH不同的子载波间隔执行测量(此CASE不适用于CSI-RS)；
Case 1:NR基于SSB无需MG(或使用NCSG)的同频测量
Scheduling restrictions涉及的符号：如果开启了deriveSSB_IndexFromCell，则为SMTC窗口持续时间内的SSB符号和SSB符号之前/之后的一些数据符号；如果未开启deriveSSB_IndexFromCell，则为SMTC窗口持续时间内的所有符号；
扩展到其他服务小区：注21；
Case 2:NR基于SSB无需MG(或使用NCSG)的异频测量
Scheduling restrictions涉及的符号：SMTC窗口持续时间内的SSB符号和SSB符号之前/之后的一些数据符号；
扩展到其他服务小区：注21；
Case 3:NR基于SSB用于上报(或用于候选波束检测)的L1-RSRP测量(总是不需要MG)
Scheduling restrictions涉及的符号：为L1-RSRP测量配置的SSB索引对应的符号；
扩展到其他服务小区：注21；注22；
Case 4:NR基于SSB的L1-SINR测量(总是不需要MG)
Scheduling restrictions涉及的符号：L1-SINR测量要测量的SSB符号；
扩展到其他服务小区：注21；注22；
CASE II:UE在FR1上使用与PDSCH/PDCCH不同的子载波间隔执行无线链路监测Scheduling restrictions涉及的符号：为无线链路监测而测量的SSB符号；
扩展到其他服务小区：注21；注22；
CASE III:UE在FR1上使用与PDSCH/PDCCH不同的子载波间隔执行波束失败检测
Scheduling restrictions涉及的符号：为波束失败检测而测量的SSB符号；
扩展到其他服务小区：注21；注22；
注21：Scheduling restrictions适用于同一频段内的其他服务小区(可以理解的是，注21同时适用于上述所有Case)
具体地，当执行频段内载波聚合时，针对某个给定服务小区的调度限制也应当应用到同一频段中的所有其他服务小区，并适用于其他服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号。
注22：Scheduling restrictions不适用于其他频段内的服务小区
具体地，当配置了FR1频段间载波聚合时，对于存在调度限制的服务小区所在频段之外的其它FR1频段，这些其它FR1频段内的FR1服务小区不存在调度限制。
因素3：FR2不同模拟波束(Beam management)之间的切换
(1)影响(Impacts)
此时同时影响上行传输和下行接收：UE不期望发送PUCCH/PUSCH/SRS或接收PDCCH/PDSCH(/TRS)(/CSI-RS for tracking)/CSI-RS for CQI。上述带括号的项仅针对下述部分Case生效。
(2)涉及的情况(Involved cases)
CASE I:UE在FR2上执行测量；
Case 1:NR基于SSB无需MG(或使用NCSG)的同频测量
Scheduling restrictions涉及的符号：如果开启了deriveSSB_IndexFromCell，则为SMTC窗口持续时间内的SSB符号和SSB符号之前/之后的一些数据符号；如果未开启deriveSSB_IndexFromCell，则为SMTC窗口持续时间内的所有符号；
扩展到其他服务小区：注31；注32；注33；注释34；
Case 2:NR基于SSB无需MG(或使用NCSG)的异频测量
Scheduling restrictions涉及的符号：SMTC窗口持续时间内的SSB符号和SSB符号之前/之后的一些数据符号
扩展到其他服务小区：注31；注35(仅适用于使用NCSG的情况)；
Case 3:NR基于CSI-RS/SSB用于上报(或用于候选波束检测)的L1-RSRP测量(总是不需要MG)
Scheduling restrictions涉及的符号：与为L1-RSRP测量配置的SSB索引或周期/半持续/非周期CSI-RS资源对应的符号，以及(对于FR2-2和480/960kHz SCS参考符号的情况，及对于HST场景)这些符号之前/之后的一些数据符号；
扩展到其他服务小区：注31；注32；注33；
Case 4:NR基于CSI-RS/SSB的L1-SINR测量(总是不需要MG)
Scheduling restrictions涉及的符号：用于测量L1-SINR的符号，以及(对于配置了highSpeedMeasFlagFR2-r17的FR2功率等级6UE)这些符号之前/之后的一些数据符号；
扩展到其他服务小区：注31；
Case 5:NR基于CSI-RS的同频测量(总是不需要MG)
Scheduling restrictions涉及的符号：用于测量的CSI-RS资源在配置的时隙内配置的CSI-RS符号；
扩展到其他服务小区：注31；注32；
CASE II:UE对FR2进行无线链路监测
Scheduling restrictions涉及的符号：为了无线链路监测而测量的RLM-RS符号，以及(对于FR2-2及使用480/960kHz SCS的RLM-RS的情况)RLM-RS符号之前/之后的一些数据符号；
扩展到其他服务小区：注31；注32；注33；
CASE III:UE对FR2进行波束失败检测
Scheduling restrictions涉及的符号：用于候选波束检测的参考符号，以及(对于FR2-2 及使用480/960kHz SCS的RLM-RS的情况)参考符号之前/之后的一些数据符号；
扩展到其他服务小区：注31；注32；注33；
注31：Scheduling restrictions适用于同一频段内的其他服务小区(可以理解的是，注31同时适用于上述所有Case)
具体地，当执行FR2的频段内载波聚合时，针对某个给定服务小区的调度限制也应当应用到同一频段中的所有其他服务小区，并适用于其他服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号。
注32：Scheduling restrictions不适用于其他频段内的服务小区
具体地，当执行FR2的频段间载波聚合时，不会因其它不同FR2频段内FR2服务小区的调度限制，导致当前FR2频段内的FR2服务小区存在调度限制，这里假设UE针对由其它不同FR2频段和当前FR2频段构成的频段对，能够执行独立的波束管理。
注33：Scheduling restrictions不适用于一个FR2频段的SSB与另一个FR2频段的数据的SCS不同的频段间情况，假设针对由这两个FR2频段构成的频段对支持独立波束管理(Independent beam management，IBM)操作
具体地，如果UE在一个FR2频段上的SSB与另一个FR2频段上的数据配置了不同的SCS时，不会存在调度限制，假设UE针对由这两个FR2频段构成的频段对配置了IBM操作。
注34：当针对某一其他频段，UE针对当前频段与此其他频段构成的频段对不支持simultaneousRxTxInterBandCA(频段间CA同时收发)时，Scheduling restrictions适用于此其他频段内的服务小区
具体地，当执行FR2频段间载波聚合时，针对某个给定服务小区的调度限制也应当应用到其他频段中的服务小区，并适用于此服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号，如果UE针对给定服务小区所在的频段和此其他频段构成的频段对不具备支持simultaneousRxTxInterBandCA的能力的话。
注35：对于频段间情况，IBM能力和同时收发能力的各种组合下，Scheduling restrictions的适用性
具体地，可区分如下情况A/B/C/D分别进行规定：
情况A：对于目标测量频段和服务小区所在频段构成的频段对，UE既不支持IBM，也不支持simultaneousRxTxInterBandCA；
情况B：对于目标测量频段和服务小区所在频段构成的频段对，UE不支持IBM，但支持simultaneousRxTxInterBandCA；
情况C：对于目标测量频段和服务小区所在频段构成的频段对，UE支持IBM，但不支持simultaneousRxTxInterBandCA；
情况D：对于目标测量频段和服务小区所在频段构成的频段对，UE既支持IBM，也支持simultaneousRxTxInterBandCA：此时对于服务小区不存在调度限制。
因素4：不同的下行FDMed测量和接收UE能力
(1)影响(Impacts)
此时只影响下行接收：UE不期望接收PDCCH/PDSCH/CSI-RS for tracking/CSI-RS for CQI。
(2)涉及的情况(Involved cases)
CASE I:UE以频分复用(frequency division multiplex，FDM)的方式执行CLI测量和DL接收
Case 1:FR1/FR2上的CLI(SRS-RSRP/CLI-RSSI)测量(总是不需要MG)
Scheduling restrictions涉及的符号：对于SRS-RSRP测量，为执行SRS-RSRP测量的正交频分复用(Orthogonal frequency division multiplex，OFDM)符号，以及这些OFDM符号之前的一些数据符号；对于CLI-RSSI测量，为执行CLI-RSSI测量的OFDM符号，以及这些OFDM符号之前的一些数据符号。
扩展到其他服务小区：注41；
注41：Scheduling restrictions适用于同一频段内的其他服务小区(可以理解的是，注41同时适用于上述所有Case)
具体地，当配置了TDD频段内载波聚合时，针对执行CLI测量的服务小区的调度限制也应用到同一频段中的所有其他服务小区，并适用于其他服务小区中与前述Scheduling restrictions涉及的符号完全或部分重叠的符号。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的调整传输限制的方法进行详细地说明。
参见图2，本申请实施提供一种调整传输限制的方法，该方法的执行主体为终端，方法包括：
步骤201：终端确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
步骤202：终端根据预设规则，执行预定义操作；
其中，第一服务小区为终端配置的任意一个服务小区；
预设规则与以下任意一项相关联：
(1)与服务小区(Serving cell)的信道质量相关的第一上报信息；可简称为方式1；
(2)与上行缓冲状态报告(Buffer Status Report，BSR)或调度请求(Scheduling Request，SR)相关的第二上报信息；可简称为方式2；
(3)与上下行调度相关的调度信息；可简称为方式3；
预定义操作包括以下至少一项：
(1)在第一时域单元集内放松调度限制或禁用调度限制；
(2)跳过或禁用目标间隔时机中的至少一个间隔时机；
(3)调整目标间隔时机中的至少一个间隔时机对应的间隔图样参数；
可以理解的是，这里的“禁用”也可以理解为“去使能(disable)”。
在本申请实施例中，终端侧和网络侧根据与Serving cell的信道质量相关上报信息、上行BSR或SR的相关上报信息和上下行调度相关信息中任意一项相关联预设规则，执行预定义操作，实现基于规则调整传输限制的方案，通过保证不影响测量需求或降低对测量性能的影响、保证及时或尽量及时的数据传输等，以合理地放松Gap机制带来的收发限制，以及scheduling availability/restrictions规定对应的调度限制，从而保障高数据速率低时延业务的传输性能。
可选地，上述预定义操作也可以称之为预定义行为。
针对上述预定义操作：
(1)在第一时域单元集内放松调度限制或禁用调度限制，时域单元可对应时隙(Slot)、符号(Symbol)等在时域上以预定义方式切分的单元，在下文中时域单元以符号为例，第一时域单元集以一组符号(a set of symbols)为例进行描述；放松调度限制或禁用调度限制为Relax/disable scheduling restrictions；
这里a set of symbols可以对应一到多个Window或Window group内，或者，一个时间段/时间子段内，或者，调度DCI对应/触发的传输对应的持续时间或扩展持续时间内，存在Scheduling restrictions的符号集合。存在Scheduling restrictions的符号集合，可参见前文中的相应描述。对于NCSG机制，这里的Window可以为ML。
这里的Relax/disable scheduling restrictions，可以理解为关闭/去除符号集合对应的Scheduling restrictions，使此符号集合内允许收发在关闭/去除之前不允许收发的信道/信号，或者，部分关闭/去除符号集合对应的Scheduling restrictions，使此符号集合内允许收发在关闭/去除之前不允许收发，并且满足预先设定的一到多个条件(针对条件的具体描述可参见下文)的信道/信号，从而可以保证更及时的数据调度和传输，以保证或提升高数据速率低时延业务的传输性能。
(2)跳过间隔时机或禁用间隔时机，其中间隔时机为Gap occasion；
Gap occasion可以理解为NR中某种Gap机制在配置/激活之后对应的(例如单个)Gap window。对于NCSG机制，这里的Gap occasion可以为由VIL1、ML和VIL2构成的Window，或者，仅包含VIL1和VIL2对应的时间部分。这里的Skip/disable，可以理解为关闭/去除Gap occasion内的收发限制(即将此Gap occasion作失效处理，或者当作不存在)，或者，关闭/去除Gap occasion内针对满足预定义条件的接收/发送的收发限制(即仅对于满足预定义条件的接收/发送，将此Gap occasion作失效处理，或者当作不存在)。相应地，在关闭/去除上述收发限制之后，可以允许在Gap occasion期间调度和传输数据(或者满足预先设定的一到多个条件(针对条件的具体描述可参见下文)的数据)，或者，允许调度和传输的数据(或者满足预先设定的一到多个条件(针对条件的具体描述可参见下文)的数据)与Gap occasion在时域交叠，从而可以保证更及时的数据调度和传输，以保证或提升高数据速率低时延业务的传输性能。
(3)调整间隔时机对应的间隔图样参数，其中间隔图样参数为Gap pattern参数；
调整Gap pattern参数包括，调整(例如延长/缩短)Gap周期长度(例如参数mgrp的取值)，Gap偏移(例如参数gapOffset的取值)，Gap长度(例如参数mgl的取值)等。
这里的调整，可以理解为针对目标Gap occasion(s)或目标时间段/时间子段内的Gap occasion(s)调整对应的参数。例如，可以通过延长Gap周期长度，或缩短Gap长度，从而控制Gap occasion对应的收发限制在时域出现的频次或概率，以减轻收发限制对数据调度和传输的影响，从而保证或提升高数据速率低时延业务的传输性能。
“第一服务小区中存在生效的目标间隔时机”，可以理解为，目标间隔时机生效或应用的Serving cell集合中，包含第一服务小区。目标间隔时机生效或应用的Serving cell集合，一般是基于协议规定，Gap occasion或Scheduling restrictions应用的Serving cell或Serving cell集合，具体参见下文中的相应描述。可选地，可以由高层信令配置目标间隔时机生效或应用的Serving cell集合。
需要说明的是，上述预定义操作的目标Serving cell的范围，默认是基于协议规定，Gap occasion或Scheduling restrictions应用的Serving cell或Serving cell集合。例如，对于UE级测量间隔(per-UE measurement gap)对应的Gap occasion，其目标Serving cell可以理解成为UE配置的所有服务小区，包括NR服务小区或E-UTRAN服务小区；对于FR级测量间隔(per-FR measurement gap)对应的Gap occasion，其目标Serving cell可以理解成为UE在对应FR(FR1或FR2)内配置的所有服务小区，包括NR服务小区或E-UTRAN服务小区。又例如，对于Scheduling restrictions，除了基于RRM测量、CLI测量、L1-RSRP测量、L1-SINR测量、RLM、BFD等行为直接引入Scheduling restrictions的Serving cell，还包括基于位于同一频段、或位于其它频段但UE不支持对应频段对的同时收发或IBM等能力而扩展确定的其它同频段或异频段Serving cell(具体扩展规则参见前文中的相应描述)。可选地，可以针对不同的方式基于其它规则分别确定预定义操作对应的目标Serving cell。例如，对于方式1：基于Serving cell的信道质量相关上报信息，应用的Serving cell即信道质量对应的Serving cell；对于方式3：基于上下行调度相关信息，分基于各个Serving cell的上下行调度相关信息分别确定每个Serving cell是否执行预定义操作，以及当执行预定义操作时目标Serving cell即为此Serving cell。可选地，各方式当确定执行预定义操作时，目标Serving cell或目标Serving cell列表/集合可以由高层信令显式配置。
可以理解的是，上述预定义操作的目标Serving cell中必然包含第一服务小区。
需要说明的是，上述预设规则可以理解为，沿用相关技术中的半静态/动态信令和过程，不引入/新增半静态配置/动态指示信息以显式指示UE是否执行预定义操作(具体采用哪种方式，以及当采用某种方式时涉及的相关参数，可以由协议规定或由高层信令配置)，但引入新的规则，以便两侧对于上述确定操作(包括起止时间)达成一致。
下面针对上述预设规则对本申请的技术方案做具体描述：
方式1：基于Serving cell的信道质量相关上报信息(对应测量需求)。
在一种可能的实施方式中，在预设规则与Serving cell的信道质量相关上报信息相关联 的情况下，终端根据预设规则，执行预定义操作，包括：
在Serving cell的信道质量高于或等于第一门限的情况下，终端根据Serving cell的信道质量相关上报信息，执行预定义操作。
可以理解为，Serving cell的信道质量越好，UE作邻区测量并准备切换等移动性过程的必要性越小，从而占用Gap作测量等的需求越小，实际占用的Gap可以更少，或者在时域可以更稀疏。相应地，配置的Gap无需全部使用，可以根据需要跳过或禁用一部分间隔时机，或者根据需要调整Gap参数以降低间隔时机在时域出现的频次或缩短每个间隔时机的时域长度等，以在避免或降低对测量等与Gap占用相关的性能的前提下，尽量保证数据传输的时延、容量等性能。同理，Serving cell的信道质量越好，UE作邻区测量并准备切换等移动性过程的必要性越小，引入scheduling restrictions作测量等的需求越小，实际需要限制调度的情况可以更少，或者在时域可以更稀疏，相应地可以在一些情况下或在一些时刻放松或禁用scheduling restrictions，以在避免或降低对测量等与Scheduling restrictions相关的性能的前提下，尽量保证数据传输的时延、容量等性能。当Serving cell的信道质量高于或不低于预定义门限(即上述第一门限)时，两侧可认为能暂时解除scheduling restrictions或关闭Measuremeng gap等，即执行预定义操作。
可选地，在满足在Serving cell的信道质量高于或等于第一门限的同时，还需满足占用间隔是用于执行非服务小区(non-serving cell)的测量，或者，引入调度限制是用于执行non-serving cell的检测的情况下，终端根据Serving cell的信道质量相关上报信息，执行预定义操作。
可以理解的是，如果占用Gap或引入scheduling restrictions是为了测量Serving cell，例如占用Gap测量Serving cell位于活跃带宽部分(Active Bandwidth Part，Active BWP)之外的SSB，或者，引入scheduling restrictions以执行FR1基于与PDSCH/物理下行控制信道(Physical downlink control channel，PDCCH)不同SCS的SSB的RLM/BFD或FR2的RLM/BFD，则在Serving cell的信道质量足够好时，仍不能执行预定义操作。因此，“在Serving cell的信道质量足够好时执行预定义操作”只适用于部分场景，即占用Gap或引入scheduling restrictions是为了执行针对non-serving cell的测量或检测。
这里的Serving cell，可以仅为特殊小区(Special Cell，SpCell)，也可以仅为SCell，或者，可以为任意Serving cell。可以理解的是，这里的Serving cell，与所述第一服务小区之间存在关联关系。在一些实施例中，这里的Serving cell即为所述第一服务小区。在另一些实施例中，这里的Serving cell与所述第一服务小区为不同的服务小区；可选地，两者位于相同的频域范围(FR1或FR2)、或者位于相同的Cell group、或者协议规定或高层信令配置的Serving cell组或列表中。
具体地，上述方式1具体为：
在一种可能的实施方式中，终端根据Serving cell的信道质量相关上报信息，执行预定义操作，包括以下任意一项：
方式1-1：终端根据Serving cell的层3(Layer 3，L3)测量上报信息，执行预定义操作；
方式1-2：终端根据Serving cell的信道状态信息(Channel State Information，CSI)上报信息，执行预定义操作。
即，Serving cell的信道质量可以通过相关技术中的L3测量上报或层1(L1)CSI上报来判断，例如参见图3所示场景。相应地，终端根据L3测量上报或L1 CSI上报执行预定义操作。
具体地，方式1-1具体为：
在一种可能的实施方式中，第一上报信息包括基于L3测量的测量报告，终端根据第一上报信息，执行预定义操作包括以下任意一项：
方式1-1-1：在发送基于L3测量的测量报告的情况下，终端执行预定义操作，基于L3测量的测量报告是基于测量上报事件触发的；
方式1-1-2：终端根据L3测量的测量报告中的信道质量信息，执行预定义操作。
针对上述方式1-1-1，在一种可能的实施方式中，终端根据测量上报事件，执行预定义操作，包括：
(1)在终端基于第一事件发送基于L3测量的测量报告之后，终端从第一预定义时刻开始执行预定义操作；
(2)在终端基于第二事件发送基于L3测量的测量报告之后，终端在第二预定义时刻停止执行预定义操作；
其中，第一预定义时刻基于第一事件发送的层3测量的测量报告的传输时刻确定，第二预定义时刻基于第二事件发送的层3测量的测量报告的传输时刻确定。
在本申请实施例中，在UE针对特定的一到多个Serving cell上报针对特定事件的测量报告之后，两侧可认为UE无需或需要执行intra-frequency/inter-frequency/inter-RAT measurements，从而执行或停止执行预定义操作。
上述第一预定义时刻基于第一事件发送的层3测量的测量报告的传输时刻确定，第二预定义时刻基于第二事件的测量报告的传输时刻确定，具体可以如下：
第一预定义时刻为承载第一事件发送的层3测量的测量报告的无线链路控制业务数据单元(Radio Link Control Service Data Unit，RLC SDU)对应的应答(Acknowledgement，ACK)所在传输块(Transport Block，TB)对应的混合自动重传请求应答(Hybrid automatic repeat request acknowledgement，HARQ-ACK)反馈时刻加第一时间间隔，HARQ-ACK反馈时刻为承载HARQ-ACK信息(一般地，可要求是与所述传输块对应且取值为ACK的HARQ-ACK信息)的物理上行控制信道PUCCH传输的开始时刻或结束时刻，或者HARQ-ACK反馈时刻为承载HARQ-ACK信息的PUCCH传输所在时间单元(例如Slot或子时隙(Sub-slot))的开始时刻或结束时刻，第一时间间隔由协议规定或高层信令配置；通过确定第一预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能；
第二预定义时刻为承载第二事件的测量报告的RLC SDU对应的ACK所在TB对应的HARQ-ACK反馈时刻加第二时间间隔，HARQ-ACK反馈时刻为承载HARQ-ACK信息(一般地，可要求是与所述传输块对应且取值为ACK的HARQ-ACK信息)的PUCCH传输的开始时刻或结束时刻，或者HARQ-ACK反馈时刻为承载HARQ-ACK信息的PUCCH传输所在时间单元(例如Slot或Sub-slot)的开始时刻或结束时刻，第二时间间隔由协议规定或高层信令配置；通过确定第二预定义时刻，可使得终端和网络两侧对于停止执行预定义操作的时刻理解一致，并且尽早停止执行预定义操作以避免影响测量等性能。
例如：在UE针对SpCell上报A1事件测量报告之后，两侧可认为从预定义时刻1(例如，承载(上行方向)测量报告(Measurement report)的RLC SDU对应的ACK所在(下行方向)TB对应的HARQ-ACK反馈时刻+delta1；HARQ-ACK反馈时刻可以为承载HARQ-ACK信息的PUCCH传输的开始/结束时刻，或者，PUCCH传输所在Slot的开始/结束时刻；其中delta1可以由协议规定或高层信令配置)开始UE执行预定义操作；在UE针对SpCell上报A2事件测量报告之后，两侧可认为从预定义时刻2(其定义参见预定义时刻1，仅参考的Measurement report不同)开始UE停止执行预定义操作。
针对上述方式1-1-2，在一种可能的实施方式中，终端根据测量报告中的信道质量信息，执行预定义操作，包括：
(1)在第一测量报告中的信道质量信息高于或等于第二门限的情况下，终端从第三预定义时刻开始执行预定义操作；
(2)在第二测量报告中的信道质量信息低于或等于第三门限的情况下，终端在第四预定义时刻停止执行预定义操作；
其中，第三预定义时刻基于第一测量报告的传输时刻确定，第四预定义时刻基于第二测量报告的传输时刻确定。
这里的L3测量，以及信道质量信息可以为Serving cell对应的小区级参考信号接收功率(Reference Signal Receiving Power，RSRP)/参考信号接收质量(Reference Signal Received Quality，RSRQ)/信号与干扰加噪声比(Signal to Interference plus Noise Ratio，SINR)，或者，最强的波束(Beam)或预定义的一到多个Beam的RSRP/RSRQ/SINR。
具体地，基于Measurement report中针对特定的一到多个Serving cell上报的RSRP/RSRQ/SINR确定是否执行或停止执行预定义操作。例如，当这一到多个Serving cell对应的RSRP/RSRQ/SINR高于或不低于预定义门限时，两侧可认为UE(开始或继续)执行预定义操作；当这一到多个Serving cell对应的RSRP/RSRQ/SINR低于或不高于预定义门限时，两侧可认为UE停止/不再执行预定义操作。
这里的Measurement report，可以为包含上述特定的一到多个Serving cell中所有Serving cell或至少一个或N个Serving cell的Measurement report。可选地，Measurement report对应的报告类型(reportType)要求为周期性的(periodical)和/或事件触发的(eventTriggered)。
对于某个Measurement report，其中包含的RSRP/RSRQ/SINR的生效时刻可参考上述方 式1-1-1中针对预定义时刻1/2的定义。
上述第三预定义时刻基于第一测量报告的传输时刻确定，第四预定义时刻基于第二测量报告的传输时刻确定，具体可以如下：
第三预定义时刻为承载第一测量报告的RLC SDU对应的ACK所在TB对应的HARQ-ACK反馈时刻加第三时间间隔，HARQ-ACK反馈时刻为承载HARQ-ACK信息(一般地，可要求是与所述传输块对应且取值为ACK的HARQ-ACK信息)的PUCCH传输的开始时刻或结束时刻，或者HARQ-ACK反馈时刻为承载HARQ-ACK信息的PUCCH传输所在时间单元(例如Slot或Sub-slot)的开始时刻或结束时刻，第三时间间隔由协议规定或高层信令配置；通过确定第三预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能；
第四预定义时刻为承载第二测量报告的RLC SDU对应的ACK所在TB对应的HARQ-ACK反馈时刻加第四时间间隔，HARQ-ACK反馈时刻为承载HARQ-ACK信息(一般地，可要求是与所述传输块对应且取值为ACK的HARQ-ACK信息)的PUCCH传输的开始时刻或结束时刻，或者HARQ-ACK反馈时刻为承载HARQ-ACK信息的PUCCH传输所在时间单元(例如Slot或Sub-slot)的开始时刻或结束时刻，第四时间间隔由协议规定或高层信令配置；通过确定第四预定义时刻，可使得终端和网络两侧对于停止执行预定义操作的时刻理解一致，并且尽早停止执行预定义操作以避免影响测量等性能。
具体地，方式1-2具体为：
在一种可能的实施方式中，终端根据Serving cell的CSI上报信息，执行预定义操作，包括以下任意一项：
(1)在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，终端从第五预定义时刻开始执行预定义操作；
(2)在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，终端在第六预定义时刻停止执行预定义操作；
其中，第五预定义时刻基于第一CSI报告的传输时刻确定，第六预定义时刻基于第二CSI报告的传输时刻确定。
具体地，可以基于CSI report中的上报信息，例如L1-RSRP/L1-SINR或信道质量指示(Channel Quality Indicator，CQI)，确定是否执行或停止执行预定义操作。例如，当上报信息高于或不低于预定义门限时，两侧可认为UE针对CSI report对应的Serving cell(开始或继续)执行预定义操作；当上报信息低于或不高于预定义门限时，两侧可认为UE针对此Serving cell停止/不再执行预定义操作。
可选地，这里的CSI report，针对其对应的CSI-ReportConfig可引入一定的限制。例如，限制其reportConfigType，必须为以下一种或几种：
周期的(periodic)(PUCCH上的周期性CSI(Periodic CSI on PUCCH))；
semiPersistentOnPUCCH(PUCCH上的半持续性CSI(Semi-persistent CSI on  PUCCH))；
semiPersistentOnPUSCH(Semi-persistent CSI on PUSCH)；
非周期的(aperiodic)(PUSCH上的非周期性CSI(Aperiodic CSI on PUSCH))；
或必须经由PUCCH或PUSCH上报；
和/或，限制其reportQuantity，必须为以下一种或几种：
cri-RI-PMI-CQI；
cri-RI-i1-CQI；
cri-RI-CQI；
cri-RSRP；
ssb-Index-RSRP；
cri-RI-LI-PMI-CQI；
或上报量中必须包含L1-RSRP和/或L1-SINR和/或CQI；
和/或，限制其频率粒度(Frequency granularity)，例如必须为宽带频率粒度(Wideband frequency-granularity)，或者，上报量中必须包含宽带CQI；
和/或，限制其测量带宽，例如csi-ReportingBand对应的测量频域资源相对于DL active BWP或Serving cell带宽的百分比高于或不低于预定义门限。
当基于CSI report中的CQI确定时，可以仅基于单码字CSI report中的CQI；或者，对于单码字CSI report，基于此单一码字的CQI，对于双码字CSI report，基于预定义码字(例如，第一个码字/第二个码字/CQI较大的码字/CQI较小的码字)的CQI或两个码字的CQI平均值。这里的CQI，可以为宽带CQI，和/或，取值最小/最大的一到多个子带CQI。
对于某个CSI report，其中包含的上报信息的生效时刻(即可用于确定是否执行或停止执行预定义操作的开始时刻)可以为承载此CSI report的PUCCH/PUSCH的结束时刻+delta2；其中delta2可以由协议规定或高层信令配置，主要考虑CSI report的解码时延。
上述第五预定义时刻基于第一CSI报告的传输时刻确定，第六预定义时刻基于第二CSI报告的传输时刻确定，具体可以如下：
第五预定义时刻为承载第一CSI上报信息的PUCCH或PUSCH的结束时刻加第五时间间隔，第五时间间隔由协议规定或高层信令配置；通过确定第五预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能；
第六预定义时刻为承载第二CSI上报信息的PUCCH或PUSCH的结束时刻加第六时间间隔，第六时间间隔由协议规定或高层信令配置；通过确定第六预定义时刻，可使得终端和网络两侧对于停止执行预定义操作的时刻理解一致，并且尽早停止执行预定义操作以避免影响测量等性能。
方式2：基于上行BSR/SR相关上报信息(对应上行数据传输需求)。
在一种可能的实施方式中，在预设规则与上行BSR或SR的相关上报信息相关联的情 况下，终端根据预设规则，执行预定义操作，包括以下至少一项：
处理准则1：在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，终端针对目标Serving cell执行预定义操作；
处理准则2：针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，终端针对目标Serving cell执行预定义操作；
其中，第一条件包括以下至少一项：
(1)目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；即在特定逻辑信道(Logical channel)/逻辑信道组(Logical Channel Group，LCG)的上行方向的待传数据已等候较长时间；
(2)目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算(Packet Delay Budget，PDB)短于或等于第七门限；即在特定Logical channel/LCG的上行方向的待传数据即将或很有可能超时被丢弃，较为紧急；
(3)目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；即在特定Logical channel/LCG的上行方向的待传数据量比较多；
第二条件包括以下至少一项：
(1)终端针对目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道触发和实际发送了SR PUCCH；
(2)上行BSR上报信息指示针对目标逻辑信道或目标逻辑信道组存在待传数据量。
针对上述处理准则1：
当特定Logical channel/LCG的上行方向存在较多/较集中/较紧急的数据传输需求时，可以暂时忽略Gap或scheduling restrictions，优先保证数据传输需求，即数据传输需求的优先级高于测量的优先级。这种处理准则仅在必要时牺牲RRM测量等RAN4性能，对RAN4性能影响相对较小。
具体地，当上行Buffer上报信息(例如，BSR上报或增强的BSR上报中的信息)中针对特定Logical channel/LCG的上报信息满足以下至少一项(即上述第一条件)时，两侧可确定UE针对所有Serving cell(或者，FR1/FR2的所有Serving cell，或，MCG/SCG的所有Serving cell，或，协议规定或高层信令配置的Serving cell或Serving cell列表中的各个Serving cell)(开始或继续)执行预定义操作：
(a)特定Logical channel/LCG的待传数据量高于或不低于预定义门限
(b)特定Logical channel/LCG的待传数据的等待时间长于或不短于预定义门限
这里待传数据的等待时间，可以为所有待传数据的等待时间的最大值/最小值/平均值。
(c)特定Logical channel/LCG的待传数据的剩余(Remaining)PDB短于或不长于预定义门限
这里待传数据的Remaining PDB，可以为所有待传数据的Remaining PDB的最大值/最小值/平均值。
上述特定Logical channel/LCG对应至少一个Logical channel/LCG，其确定可以采用以下任一方式：
(a)基于规则隐式确定(协议规定)
特定Logical channel/LCG可以为映射了对应特定业务类型或具备特定属性的服务质量(Quality of Service，QoS)流(flow)(例如XR业务，或者XR业务的视频流(Video stream)，或者XR业务的Video stream的I Frame)的RB对应的Logical channel/LCG，或者，Logical channel/LCG或其映射的资源块(Resource block，RB)的配置满足预定义要求(例如，为RB配置的丢弃计时器(Discard Timer)短于或不长于预定义门限)。
(b)由高层信令显式配置
例如，采用UE特定RRC信令(UE specific RRC signalling)显式配置。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，终端针对目标Serving cell执行预定义操作，包括：
终端针对目标Serving cell从第七预定义时刻开始或继续执行预定义操作；
需要说明的是，如果当前UE已经开始执行所述预定义操作，则基于本次上行BSR上报信息，UE继续执行所述预定义操作。
其中，第七预定义时刻基于上行BSR上报信息的传输时刻确定。
上述第七预定义时刻基于上行BSR上报信息的传输时刻确定，具体可以如下：
第七预定义时刻为以下任意一项：
(1)承载上行BSR上报信息的TB的第一次PUSCH传输的开始时刻或结束时刻加第七时间间隔，第七时间间隔由协议规定或高层信令配置；
承载上述上行Buffer上报信息的TB的第一次PUSCH传输的开始/结束时刻+delta3；其中delta3可以由协议规定或高层信令配置，主要考虑TB的HARQ传输、解码和解封装等时延。
(2)针对承载上行BSR上报信息的TB传输占用的HARQ进程，终端接收到的指示新传的上行授权(UL grant)对应的PDCCH传输的开始时刻或结束时刻加第八时间间隔，第八时间间隔由协议规定或高层信令配置
针对承载上述上行Buffer上报信息的TB传输占用的HARQ进程，UE接收到的指示新传的UL grant对应的PDCCH传输的开始/结束时刻+delta4；其中delta4可以由协议规定或高层信令配置，主要考虑PDCCH解码时延。
通过上述确定第七预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，终端针对目标Serving cell执行预定义操作，还包括：
在满足第三条件的情况下，终端停止执行预定义操作；
其中，第三条件包括以下任意一项：
(1)从终端确定开始或继续执行预定义操作开始，达到第一预设时长；
(2)上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足第一条件。
在两侧确定针对所有或特定Serving cell(开始或继续)执行预定义操作之后，可以基于以下任一项确定停止执行预定义操作：
(a)在每次确定(开始或继续)执行预定义操作时，启动或重启一个Timer，当Timer超时时，两侧确定停止执行预定义操作，即通过Timer确定是否达到第一预设时长。
(b)当上行Buffer上报信息中针对特定Logical channel/LCG的上报信息不再满足上述指定项(即确定针对所有或特定Serving cell(开始或继续)执行预定义操作时满足的一到多项)或任一项时，两侧确定停止执行预定义操作。
针对上述处理准则2：
只要特定Logical channel/LCG的上行方向存在数据传输需求，就考虑暂时忽略Gap或scheduling restrictions，优先保证数据传输需求。这种处理准则可以理解为特定Logical channel/LCG的上行数据传输需求绝对优先，对RAN4性能影响相对较大。
具体地，当满足如下情况中的至少一项(即上述第二条件)时，两侧可确定UE针对所有Serving cell(或者，FR1/FR2的所有Serving cell，或，MCG/SCG的所有Serving cell，或，协议规定或高层信令配置的Serving cell或Serving cell列表中的各个Serving cell)(开始或继续)执行预定义操作：
(a)UE针对特定Logical channel或者特定LCG中的至少一个Logical channel触发和实际发送了SR PUCCH
这里考虑了对于特定Logical channel，或者特定LCG中的某个Logical channel，可以为其配置关联的SR Config。当此特定Logical channel所在的LCG，或者此特定LCG，触发了Regular BSR时，当UE不存在可用的上行共享信道(Uplink Shared Channel，UL-SCH)初传资源时，可以基于此关联的SR Config发送对应的SR PUCCH。
(b)上行Buffer上报信息指示针对特定Logical channel/LCG存在待传数据量(或者，待传数据量>0)
特定Logical channel/LCG的确定参照处理准则1中相关描述。
在一种可能的实施方式中，针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，终端针对目标Serving cell执行预定义操作，包括：
终端针对目标Serving cell从第八预定义时刻开始或继续执行预定义操作；
其中，第八预定义时刻基于SR上报信息或上行BSR上报信息的传输时刻确定。
上述第八预定义时刻为以下任意一项：
(1)终端在触发SR之后的第一次SR PUCCH传输的开始时刻或结束时刻加第九时间间隔，第九时间间隔由协议规定或高层信令配置；
(2)承载上行BSR上报信息的TB的第一次PUSCH传输的开始时刻或结束时刻加第 十时间间隔，第十时间间隔由协议规定或高层信令配置；
(3)针对承载上行BSR上报信息的TB传输占用的HARQ进程，终端接收到的指示新传的上行授权UL grant对应的PDCCH传输的开始时刻或结束时刻加第十一时间间隔，第十一时间间隔由协议规定或高层信令配置。
当基于上行Buffer上报信息时，上述确定(开始或继续)执行预定义操作的时刻可以为上述任一项。
当基于SR PUCCH传输时，上述确定(开始或继续)执行预定义操作的时刻可以为：UE在触发SR之后的第一次SR PUCCH传输的开始/结束时刻+delta5；其中delta5可以由协议规定或高层信令配置，主要考虑可能的多次SR PUCCH传输、解码等时延。
通过上述确定第八预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，终端针对目标Serving cell执行预定义操作，还包括：
在满足第四条件的情况下，终端停止执行预定义操作；
其中，第四条件包括以下任意一项：
(1)从终端确定开始或继续执行预定义操作开始，达到第二预设时长；
(2)上行BSR上报信息指示针对目标逻辑信道或目标逻辑信道组的待传数据量为0。
在两侧确定针对所有或特定Serving cell(开始或继续)执行预定义操作之后，可以基于以下任一项(即上述第四条件)确定停止执行预定义操作：
(a)在每次确定(开始或继续)执行预定义操作时，启动或重启一个Timer，当Timer超时时，两侧确定停止执行预定义操作。即通过Timer确定是否达到第二预设时长。
(b)当针对特定Logical channel/LCG的待传数据量为0时(例如，上行Buffer上报信息指示特定Logical channel/LCG的待传数据量为0，或者，UE上报视频帧结束(End of video frame)指示(可以由物理层动态信令指示，或者通过MAC CE指示))，两侧确定停止执行预定义操作。
方式3：基于上下行调度信息或调度情况(对应上下行数据传输需求)。
在一种可能的实施方式中，在预设规则与上下行调度相关信息相关联的情况下，终端根据预设规则，执行预定义操作，包括：
方式3-1：终端根据调度下行控制信息(Downlink Control Information，DCI)对应的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)、信道状态信息参考信号(Channel State Information-Reference Signal，CSI-RS)、物理上行共享信道(Physical Uplink Shared Channel，PUSCH)、物理上行控制信道(Physical Uplink Control Channel，PUCCH)或探测参考信号(Sounding Reference Signal，SRS)传输的位置，执行预定义操作；
方式3-2：终端根据调度DCI中指示的传输属性信息，执行预定义操作，传输属性信息与TB的大小或物理层优先级相关；
方式3-3：终端根据数据调度相关信息，执行预定义操作。
具体地，方式3-1具体为：
在一种可能的实施方式中，终端根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作，包括：
假设对于与间隔时机(Gap occasion(s))或具有调度限制的符号(Symbols with scheduling restrictions)存在交叠的控制资源集(Control resource set，CORESET)实例(instance)，UE不作PDCCH检测。
对于某个Gap occasion或具有调度限制的窗口(Window with scheduling restrictions)(可以理解为配置的Window内包含的部分或所有Symbol存在Scheduling restrictions，例如SMTC window)，可以采用以下任一方式：
(1)在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与间隔时机或第一窗口存在时域交叠，或者，调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与间隔时机或第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，终端针对间隔时机或第一窗口执行预定义操作；其中，第一窗口为存在调度限制的预定义窗口；
当调度DCI对应/触发的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输，与此Gap occasion或Window with scheduling restrictions(即第一窗口)存在时域交叠，或者两者占用的任意Symbol之间的时域间隔小于或不大于预定义门限时，两侧认为针对此Gap occasion或Window with scheduling restrictions执行预定义操作，例如disable此Gap occasion，或者disable此Window with scheduling restrictions内的Scheduling restrictions。
(2)在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与间隔时机或第一窗口存在时域交叠，终端针对时域交叠的区域执行预定义操作；
(3)在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与间隔时机或第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，终端针对扩展时域交叠的区域执行预定义操作，扩展时域交叠的区域基于调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和第十门限确定；
当调度DCI对应/触发的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输，与此Gap occasion或Window with scheduling restrictions存在时域交叠，或者两者占用的任意Symbol之间的时域间隔小于或不大于预定义门限(可以理解为，此调度DCI对应/触发的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输占用的任意Symbol对应的持续时间，以及此Symbol之前和之后预定义门限时长构成的持续时间，所形成的并集对应的扩展持续时间，与此Gap occasion或Window with scheduling restrictions存在时域交叠，可以称之为“扩展时域交叠”)时，两侧认为仅针对此Gap occasion或Window with scheduling restrictions的时域交叠区域，或者扩展时域交叠区域执行预定义操作，例如解除此Gap occasion的时域交叠区域/扩展时域交叠区域内的数据收发限制，或者解除此Window with scheduling restrictions的时域交叠区域/扩 展时域交叠区域内的Scheduling restrictions。
类似地，当存在Scheduling restrictions的Symbol不对应任何Window，或不以Window的方式进一步组织时，可以采用以下任一方式：
(4)终端针对第一时间段内存在调度限制的所有时域单元执行预定义操作，第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
针对由调度DCI对应/触发的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输确定的一段时间内存在Scheduling restrictions的所有Symbol执行预定义操作。例如，这段时间为从对应/触发的最早的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输或传输所在Slot的起始时刻(或再往前推预定义门限对应的时长/符号数)开始，指定时长对应的时间段。这里的指定时长可以由协议规定或由高层信令配置，或者在调度DCI中直接指示。
(5)终端针对与第二时间段存在时域交叠或扩展时域交叠，且存在调度限制的所有时域单元执行预定义操作，第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
仅针对与由调度DCI对应/触发的PDSCH/CSI-RS或PUSCH/PUCCH/SRS传输存在时域交叠，或存在扩展时域交叠(基于扩展持续时间，具体参见前文中的相应描述)，且存在Scheduling restrictions的所有Symbol执行预定义操作。
可选地，上述DCI调度的PUCCH/PUSCH的优先级满足预定义要求，例如为高优先级，或者，上述DCI调度的PDSCH对应的HARQ-ACK的优先级满足预定义要求，例如为高优先级。当下行方向进一步引入PHY priority时，可选地，上述DCI调度的PDSCH的优先级满足预定义要求，例如为高优先级。
具体地，方式3-2具体为：
在一种可能的实施方式中，终端根据调度DCI中指示的传输属性信息，执行预定义操作，包括：
在终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，终端针对目标Serving cell执行预定义操作，N由协议规定或高层信令配置；
其中，第五条件包括以下至少一项：
(1)TB的大小大于或等于第十一门限；
(2)物理层优先级为预定义优先级。
具体地，当UE在指定传输方向(下行或上行)最近检测到的连续N(N>＝1)个(新传)调度DCI中指示的传输属性信息满足以下至少一项(即上述第五条件)时，两侧可确定UE针对所有Serving cell(或者，FR1/FR2的所有Serving cell，或，MCG/SCG的所有Serving cell，或，协议规定或高层信令配置的Serving cell或Serving cell列表中的各个Serving cell)(开始或继续)执行预定义操作：
(a)TB Size大于或不小于预定义门限；
(b)PHY priority为预定义优先级，例如较高优先级；
基于相关协议规定，仅上行方向支持PHY priority。实际上，下行方向根据需要也可以引入PHY priority，例如，在DCI中指示调度的PDSCH对应的PHY priority，用于区分PDSCH承载的数据的优先级(可以与相关技术中针对调度的PDSCH对应的HARQ-ACK的优先级独立指示)。
在一种可能的实施方式中，在终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，终端针对目标Serving cell执行预定义操作，包括：
在终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，终端针对目标Serving cell从第九预定义时刻开始或继续执行预定义操作；
其中，第九预定义时刻基于连续N个调度DCI的传输时刻确定。
上述第九预定义时刻基于连续N个调度DCI的传输时刻确定，具体可以如下：
第九预定义时刻为连续N个调度DCI对应的PDCCH传输的最晚开始时刻或最晚结束时刻加第十二时间间隔，第十二时间间隔由协议规定或高层信令配置。
上述确定(开始或继续)执行预定义操作的时刻可以为：连续N个(新传)调度DCI对应的PDCCH传输的最晚开始/结束时刻+delta6；其中delta6可以由协议规定或高层信令配置，主要考虑PDCCH解码时延。
通过上述确定第九预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能。
在一种可能的实施方式中，终端根据调度DCI中指示的传输属性信息，执行预定义操作，还包括：
在满足第六条件的情况下，终端停止执行预定义操作；
其中，第六条件包括以下任意一项：
(1)从终端确定开始或继续执行预定义操作开始，达到第三预设时长；
(2)终端在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
在两侧确定针对所有或特定Serving cell(开始或继续)执行预定义操作之后，可以基于以下任一项(即上述第六条件)确定停止执行预定义操作：
(a)在每次确定(开始或继续)执行预定义操作时，启动或重启一个Timer，当Timer超时时，两侧确定停止执行预定义操作。即通过Timer确定是否达到第三预设时长。
(b)当UE在指定传输方向最近检测到的连续N个(新传)调度DCI中指示的信息不再满足上述指定项(即确定针对所有或特定Serving cell(开始或继续)执行预定义操作时满足的一到多项)或任一项时，两侧确定停止执行预定义操作。
具体地，方式3-3具体为：
在一种可能的实施方式中，终端根据数据调度相关信息，执行预定义操作，包括：
在终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，终端针对目标Serving cell 执行预定义操作；
其中，第三时间段由协议规定或高层信令配置。
具体地，可根据指定UE在指定传输方向(下行或上行)最近一段时长内调度的数据量，或者针对特定RB/Logical channel实际调度的数据量确定是否(开始或继续)执行预定义操作。例如，当上述数据量大于或不小于预定义门限时，两侧可确定UE针对所有Serving cell(或者，FR1/FR2的所有Serving cell，或，MCG/SCG的所有Serving cell，或，协议规定或高层信令配置的Serving cell或Serving cell列表中的各个Serving cell)(开始或继续)执行预定义操作。
上述时长可以由协议规定或高层信令配置。
上述调度的数据量可考虑上述时长内UE针对指定传输方向检测到的(新传)调度DCI指示的TB Size之和。
上述针对特定RB/Logical channel实际调度的数据量，可直接基于媒体接入控制(Medium Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)中的数据组装情况确定(基于每个MAC SDU对应的MAC子头(subheader)中的逻辑信道标识(Logical Channel Identity，LCID)字段，便可识别对应Logical channel)。这里特定RB/Logical channel，可以为映射了对应特定业务类型或具备特定属性的QoS flow(例如XR业务，或者XR业务的Video stream，或者XR业务的Video stream的I Frame)的RB/Logical channel，或者，RB/Logical channel的配置满足预定义要求(例如，为RB配置的Discard Timer短于或不长于预定义门限)。
上述最近一段时长可以采用滑动窗的方式确定，其结束时刻可以为UE收到指定传输方向的调度DCI对应的PDCCH传输的开始/结束时刻；其开始时刻可以基于结束时刻和时长隐式确定。
在一种可能的实施方式中，终端针对目标Serving cell执行预定义操作，包括：
终端针对目标Serving cell从第十预定义时刻开始或继续执行预定义操作；
其中，第十预定义时刻为第三时间段的结束时刻加预设时间间隔，预设时间间隔由协议规定或高层信令配置。
上述确定(开始或继续)执行预定义操作的时刻可以为：最近一段时长的结束时刻+delta7；其中delta7可以由协议规定或高层信令配置，主要考虑TB的HARQ传输、解码和解封装等时延。
通过上述确定第十预定义时刻，可使得终端和网络两侧对于开始执行预定义操作的时刻理解一致，并且尽早开始执行预定义操作以保障或提升数据传输的性能。
在一种可能的实施方式中，终端根据数据调度相关信息，执行预定义操作，还包括：
在满足第七条件的情况下，终端停止执行预定义操作；
其中，第七条件包括以下任意一项：
(1)从终端确定开始执行或继续预定义操作开始，达到第四预设时长；
(2)终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
在两侧确定针对所有或特定Serving cell(开始或继续)执行预定义操作之后，可以基于以下任一项(即上述第七条件)确定停止执行预定义操作：
(a)在每次确定(开始或继续)执行预定义操作时，启动或重启一个Timer，当Timer超时时，两侧确定停止执行预定义操作。
(b)当UE在指定传输方向最近检测到的连续N个(新传)调度DCI中指示的信息不再满足上述指定项(即确定针对所有或特定Serving cell(开始或继续)执行预定义操作时满足的一到多项)或任一项时，两侧确定停止执行预定义操作。
在一种可能的实施方式中，预定义操作针对的第一对象满足预定义条件；
其中，第一对象包括第一时域单元集或间隔时机，对于上述某种或多种方式(方式1/2/3)，确定执行预定义操作，或者确定可执行预定义操作的Window(例如Gap occasion或SMTC window等)或Symbol with scheduling restrictions要求满足预定义条件。
预定义条件包括以下至少一项：
(1)第一对象应用于第一场景以外的场景，第一场景由协议规定或高层信令配置；
Window/Symbol with scheduling restrictions不用于预定义用途或场景1，例如无线连接监测(Radio Link Monitoring，RLM)，和/或，波束失效检测(Beam Failure Detection，BFD)等。
(2)第一对象仅应用于第二场景，第二场景由协议规定或高层信令配置；
Window/Symbol with scheduling restrictions仅用于预定义用途或场景2，例如intra/inter-frequency measurement，和/或，Positioning等，这里的预定义用途或场景2可以由协议规定或高层信令配置。
(3)第一对象的优先级满足预定义优先级要求；
Window对应的优先级满足预定义要求，包括绝对值要求，和/或，相对要求，这里认为优先级较低或足够低的Window才允许执行预定义操作，以尽量避免对于较高优先级或较重要的功能使用Window造成影响。
对于绝对值要求，例如，要求对应的优先级低于或不高于预定义门限，或者，要求Gap occasion对应的GapConfig-r17对应的gapPriority-r17大于或不小于预定义门限。这里的预定义门限可以由协议规定或高层信令配置。
对于相对要求，例如，对应的优先级在所有配置的GapConfig-r17中最低或属于最低的N个优先级之一(或者，对应的gapPriority-r17在所有配置的GapConfig-r17中最大或属于最大的N个优先级之一)，或者，对应的优先级在一段时长(由各具体方式中确定是否执行预定义操作的时长给定)内存在的Gap occasion对应的GapConfig-r17中最低或属于最低的M个优先级之一(或者，对应的gapPriority-r17在此段时长内存在的Gap occasion对应的GapConfig-r17中最大或属于最大的M个优先级之一)。
目前认为Symbol with scheduling restrictions不存在优先级的概念。
(4)第一对象的周期或长度满足预定义要求。
Window的周期或长度满足预定义要求，例如周期不长于预定义门限，和/或，长度不短于预定义门限，这里的预定义门限可以由协议规定或高层信令配置。
目前认为Symbol with scheduling restrictions不涉及周期和长度等概念。
在一种可能的实施方式中，在预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，执行预定义操作，即对于上述某种或多种方式(方式1/2/3)，当确定针对某个Window或Symbol with scheduling restrictions执行预定义操作时，如果预定义操作为Relax/disable scheduling restrictions during a set of symbols或者Skip/disable Gap occasion(s)，执行以下任一项：
(1)终端期望被调度，且位于第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
(2)终端期望被调度，且与第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
针对上述(1)和(2)，UE期望在所述Window或Symbol with scheduling restrictions内(包括调度的上行传输/下行接收部分或全部位于所述Window或Symbol with scheduling restrictions内的情况；当调度的上行传输/下行接收仅部分位于所述Window或Symbol with scheduling restrictions内时，也可以理解为调度的上行传输/下行接收与所述Window或Symbol with scheduling restrictions在时域交叠)仅被调度优先级满足特定要求的上行传输/下行接收，例如高优先级的PUSCH/PUCCH/SRS传输，或者，对应的HARQ-ACK为高优先级的PDSCH接收，或者，高优先级的PDSCH接收。
(3)终端不期望被调度，且位于第一对象对应的时间范围内的上行传输或下行接收对应的优先级都不满足指定优先级要求；
(4)终端不期望被调度，且与第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都不满足指定优先级要求。
针对上述(3)和(4)，UE不期望在所述Window或Symbol with scheduling restrictions内(包括调度的上行传输/下行接收部分或全部位于所述Window或Symbol with scheduling restrictions内的情况；当调度的上行传输/下行接收仅部分位于所述Window或Symbol with scheduling restrictions内时，也可以理解为调度的上行传输/下行接收与所述Window或Symbol with scheduling restrictions在时域交叠)仅被调度优先级不满足特定要求的上行传输/下行接收，例如高优先级的PUSCH/PUCCH/SRS传输，或者，对应的HARQ-ACK为高优先级的PDSCH接收，或者，高优先级的PDSCH接收。可以理解为，UE期望在所述Window或Symbol with scheduling restrictions内被调度至少一个优先级满足特定要求的上行传输或下行接收，此时还允许调度其它优先级不满足特定要求的上行传输或下行接收(或者不作限制)。
参见图4，本申请实施例提供一种调整传输限制的方法，该方法的执行主体为网络侧设备，方法包括：
步骤401：网络侧设备确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
步骤402：网络侧设备根据预设规则，执行预定义操作；
其中，第一服务小区为终端配置的任意一个服务小区；
预设规则与以下任意一项相关联：
(1)与Serving cell的信道质量相关的第一上报信息；
(2)与上行BSR或SR相关的第二上报信息；
(3)与上下行调度相关的调度信息；
预定义操作包括以下至少一项：
(1)在第一时域单元集内放松调度限制或禁用调度限制；
(2)跳过或禁用目标间隔时机中的至少一个间隔时机；
(3)调整目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
需要说明的是，网络侧方法中的相关内容可以直接参照终端侧方法中的相关内容进行理解，本申请提供的调整传输限制的方法中，终端侧与网络侧基于相同的预设规则执行预定义操作，使得终端侧和网络侧理解一致。
在本申请实施例中，终端侧和网络侧根据与Serving cell的信道质量相关上报信息、上行BSR或SR的相关上报信息和上下行调度相关信息中任意一项相关联预设规则，执行预定义操作，实现基于规则调整传输限制的方案，通过保证不影响测量需求或降低对测量性能的影响、保证及时或尽量及时的数据传输等，以合理地放松Gap机制带来的收发限制，以及scheduling availability/restrictions规定对应的调度限制，从而保障高数据速率低时延业务的传输性能。
在一种可能的实施方式中，在预设规则与Serving cell的信道质量相关上报信息相关联的情况下，网络侧设备根据预设规则，执行预定义操作，包括：
在Serving cell的信道质量高于或等于第一门限的情况下，网络侧设备根据Serving cell的信道质量相关上报信息，执行预定义操作。
在一种可能的实施方式中，第一上报信息包括基于层3测量的测量报告，网络侧设备根据第一上报信息，执行预定义操作包括以下任意一项：
在接收基于L3测量的测量报告的情况下，网络侧设备执行预定义操作，基于L3测量的测量报告是基于测量上报事件触发的；
网络侧设备根据层3测量的测量报告中的信道质量信息，执行预定义操作。
在一种可能的实施方式中，网络侧设备根据测量上报事件，执行预定义操作，包括：
在网络侧设备接收基于第一事件上报的基于L3测量的测量报告之后，网络侧设备从第一预定义时刻开始执行预定义操作；
在网络侧设备接收基于第二事件上报的基于L3测量的测量报告之后，网络侧设备在第 二预定义时刻停止执行预定义操作；
其中，第一预定义时刻基于第一事件上报的层3测量的测量报告的传输时刻确定，第二预定义时刻基于第二事件上报的层3测量的测量报告的传输时刻确定。
在一种可能的实施方式中，网络侧设备根据测量报告中的信道质量信息，执行预定义操作，包括：
在第一测量报告中的信道质量信息高于或等于第二门限的情况下，网络侧设备从第三预定义时刻开始执行预定义操作；
在第二测量报告中的信道质量信息低于或等于第三门限的情况下，网络侧设备在第四预定义时刻停止执行预定义操作；
其中，第三预定义时刻基于第一测量报告的传输时刻确定，第四预定义时刻基于第二测量报告的传输时刻确定。
在一种可能的实施方式中，网络侧设备根据Serving cell的CSI上报信息，执行预定义操作，包括以下任意一项：
在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，网络侧设备从第五预定义时刻开始执行预定义操作；
在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，网络侧设备在第六预定义时刻停止执行预定义操作；
其中，第五预定义时刻基于第一CSI报告的传输时刻确定，第六预定义时刻基于第二CSI报告的传输时刻确定。
在一种可能的实施方式中，在预设规则与上行BSR或SR的相关上报信息相关联的情况下，网络侧设备根据预设规则，执行预定义操作，包括以下至少一项：
在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，网络侧设备针对目标Serving cell执行预定义操作；
针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，网络侧设备针对目标Serving cell执行预定义操作；
其中，第一条件包括以下至少一项：
目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
第二条件包括以下至少一项：
网络侧设备针对目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道实际接收了SR PUCCH；
上行BSR上报信息指示针对目标逻辑信道或目标逻辑信道组存在待传数据量。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道 组的上报信息满足第一条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，包括：
网络侧设备针对目标Serving cell从第七预定义时刻开始或继续执行预定义操作；
其中，第七预定义时刻基于上行BSR上报信息的传输时刻确定。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，还包括：
在满足第三条件的情况下，网络侧设备停止执行预定义操作；
其中，第三条件包括以下任意一项：
从网络侧设备确定开始或继续执行预定义操作开始，达到第一预设时长；
上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足第一条件。
在一种可能的实施方式中，针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，包括：
网络侧设备针对目标Serving cell从第八预定义时刻开始或继续执行预定义操作；
其中，第八预定义时刻基于SR上报信息或上行BSR上报信息的传输时刻确定。
在一种可能的实施方式中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，还包括：
在满足第四条件的情况下，网络侧设备停止执行预定义操作；
其中，第四条件包括以下任意一项：
从网络侧设备确定开始或继续执行预定义操作开始，达到第二预设时长；
上行BSR上报信息指示针对目标逻辑信道或目标逻辑信道组的待传数据量为0。
在一种可能的实施方式中，在预设规则与上下行调度相关信息相关联的情况下，网络侧设备根据预设规则，执行预定义操作，包括：
网络侧设备根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作；
网络侧设备根据调度DCI中指示的传输属性信息，执行预定义操作；
网络侧设备根据数据调度相关信息，执行预定义操作。
在一种可能的实施方式中，网络侧设备根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作，包括以下任意一项：
在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与间隔时机或第一窗口存在时域交叠，或者，调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与间隔时机或第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，网络侧设备针对间隔时机或第一窗口执行预定义操作；其中，第一窗口 为存在调度限制的预定义窗口；
在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与间隔时机或第一窗口存在时域交叠，网络侧设备针对时域交叠的区域执行预定义操作；
在调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与间隔时机或第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，网络侧设备针对扩展时域交叠的区域执行预定义操作，扩展时域交叠的区域基于调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和第十门限确定；
网络侧设备针对第一时间段内存在调度限制的所有时域单元执行预定义操作，第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
网络侧设备针对与第二时间段存在时域交叠或扩展时域交叠，且存在调度限制的所有时域单元执行预定义操作，第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
在一种可能的实施方式中，网络侧设备根据调度DCI中指示的传输属性信息，执行预定义操作，包括：
在网络侧设备在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，N由协议规定或高层信令配置；
其中，第五条件包括以下至少一项：
TB的大小大于或等于第十一门限；
物理层优先级为预定义优先级。
在一种可能的实施方式中，在网络侧设备在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，网络侧设备针对目标Serving cell执行预定义操作，包括：
在网络侧设备在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，网络侧设备针对目标Serving cell从第九预定义时刻开始或继续执行预定义操作；
其中，第九预定义时刻基于连续N个调度DCI的传输时刻确定。
在一种可能的实施方式中，网络侧设备根据调度DCI中指示的传输属性信息，执行预定义操作，还包括：
在满足第六条件的情况下，网络侧设备停止执行预定义操作；
其中，第六条件包括以下任意一项：
从网络侧设备确定开始或继续执行预定义操作开始，达到第三预设时长；
网络侧设备在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
在一种可能的实施方式中，网络侧设备根据数据调度相关信息，执行预定义操作，包括：
在网络侧设备在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，网络侧设备针对目标Serving cell执行预定义操作；
其中，第三时间段由协议规定或高层信令配置。
在一种可能的实施方式中，网络侧设备针对目标Serving cell执行预定义操作，包括：
网络侧设备针对目标Serving cell从第十预定义时刻开始或继续执行预定义操作；
其中，第十预定义时刻为第三时间段的结束时刻加预设时间间隔，预设时间间隔由协议规定或高层信令配置。
在一种可能的实施方式中，网络侧设备根据数据调度相关信息，执行预定义操作，还包括：
在满足第七条件的情况下，网络侧设备停止执行预定义操作；
其中，第七条件包括以下任意一项：
从网络侧设备确定开始执行或继续预定义操作开始，达到第四预设时长；
网络侧设备在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
在一种可能的实施方式中，预定义操作针对的第一对象满足预定义条件；
其中，第一对象包括第一时域单元集或间隔时机，预定义条件包括以下至少一项：
第一对象应用于第一场景以外的场景，第一场景由协议规定或高层信令配置；
第一对象仅应用于第二场景，第二场景由协议规定或高层信令配置；
第一对象的优先级满足预定义优先级要求；
第一对象的周期或长度满足预定义要求。
在一种可能的实施方式中，在预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，执行预定义操作，包括以下任意一项：
(1)网络侧设备保证为终端调度，且位于第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
(2)网络侧设备保证为终端调度，且与第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
(3)网络侧设备保证为终端调度，且位于第一对象对应的时间范围内的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求；
(4)网络侧设备保证为终端调度，且与第一对象对应的时间范围交叠的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求。
针对上述(3)和(4)，可以理解的是，对应于终端侧，终端不期望被调度的上行传输或下行接收出现下述情况一：位于第一对象对应的时间范围内的上行传输或下行接收对应的优先级都不满足指定优先级要求，或者与第一对象对应的时间范围交叠的上行传输或下 行接收对应的优先级都不满足指定优先级要求。因此对网络侧，网络侧设备为终端调度的上行传输或下行接收要求满足：位于第一对象对应的时间范围内的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求，或者与第一对象对应的时间范围交叠的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求。
本申请实施例提供的调整传输限制的方法，执行主体可以为调整传输限制的装置。本申请实施例中以调整传输限制的装置执行调整传输限制的方法为例，说明本申请实施例提供的调整传输限制的装置。
参见图5，本申请实施例提供一种调整传输限制的装置，该装置可以应用于终端，该装置包括：
第一确定模块501，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
第一执行模块502，用于根据预设规则，执行预定义操作；
其中，所述第一服务小区为所述终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
可选地，在所述预设规则与服务小区的信道质量相关的第一上报信息相关联的情况下，第一执行模块，具体用于：
在所述服务小区的信道质量高于或等于第一门限的情况下，根据服务小区的信道质量相关上报信息，执行所述预定义操作。
可选地，所述第一上报信息包括基于层3测量的测量报告，所述第一执行模块，具体用于以下任意一项：
在发送基于L3测量的测量报告的情况下，执行所述预定义操作，所述基于L3测量的测量报告是基于测量上报事件触发的；
根据层3测量的测量报告中的信道质量信息，执行所述预定义操作。
可选地，所述第一执行模块，具体用于：
在所述终端基于第一事件发送基于L3测量的测量报告之后，从第一预定义时刻开始执行所述预定义操作；
在所述终端基于第二事件发送基于L3测量的测量报告之后，在第二预定义时刻停止执行所述预定义操作；
其中，所述第一预定义时刻基于所述第一事件发送的层3测量的测量报告的传输时刻确定，所述第二预定义时刻基于所述第二事件发送的层3测量的测量报告的传输时刻确定。
可选地，所述第一执行模块，具体用于：
在第一测量报告中的信道质量信息高于或等于第二门限的情况下，从第三预定义时刻开始执行所述预定义操作；
在第二测量报告中的信道质量信息低于或等于第三门限的情况下，在第四预定义时刻停止执行所述预定义操作；
其中，所述第三预定义时刻基于所述第一测量报告的传输时刻确定，所述第四预定义时刻基于所述第二测量报告的传输时刻确定。
可选地，所述第一上报信息包括信道状态信息CSI报告，所述第一执行模块，具体用于以下任意一项：
在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，从第五预定义时刻开始执行所述预定义操作；
在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，在第六预定义时刻停止执行所述预定义操作；
其中，所述第五预定义时刻基于所述第一CSI报告的传输时刻确定，所述第六预定义时刻基于所述第二CSI报告的传输时刻确定。
可选地，在所述预设规则与上行BSR或SR相关的第二上报信息相关联的情况下，所述第一执行模块，具体用于以下至少一项：
在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，针对目标服务小区执行所述预定义操作；
针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，针对目标服务小区执行所述预定义操作；
其中，所述第一条件包括以下至少一项：
所述目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
所述目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
所述目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
所述第二条件包括以下至少一项：
所述终端针对所述目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道触发和实际发送了SR PUCCH；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组存在待传数据量。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述第一执行模块，具体用于：
针对所述目标服务小区从第七预定义时刻开始或继续执行所述预定义操作；
其中，所述第七预定义时刻基于所述上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述第一执行模块，具体用于：
在满足第三条件的情况下，停止执行所述预定义操作；
其中，所述第三条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第一预设时长；
所述上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足所述第一条件。
可选地，针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，所述第一执行模块，具体用于：
针对所述目标服务小区从第八预定义时刻开始或继续执行所述预定义操作；
其中，所述第八预定义时刻基于所述SR上报信息或上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，所述第一执行模块，具体用于：
在满足第四条件的情况下，停止执行所述预定义操作；
其中，所述第四条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第二预设时长；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组的待传数据量为0。
可选地，在所述预设规则与上下行调度相关信息相关联的情况下，所述第一执行模块，具体用于：
根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作；
根据调度DCI中指示的传输属性信息，执行预定义操作；
根据数据调度相关信息，执行预定义操作。
可选地，所述第一执行模块，具体用于以下任意一项：
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或第一窗口存在时域交叠，或者，所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，针对所述间隔时机或所述第一窗口执行所述预定义操作；其中，所述第一窗口为存在所述调度限制的预定义窗口；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或所述第一窗口存在时域交叠，针对所述时域交叠的区域执行所述预定义操作；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单 元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，针对扩展时域交叠的区域执行所述预定义操作，所述扩展时域交叠的区域基于所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和所述第十门限确定；
针对第一时间段内存在所述调度限制的所有时域单元执行所述预定义操作，所述第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
针对与第二时间段存在时域交叠或扩展时域交叠，且存在所述调度限制的所有时域单元执行预定义操作，所述第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
可选地，所述第一执行模块，具体用于：
在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，针对目标服务小区执行所述预定义操作，所述N由协议规定或高层信令配置；
其中，所述第五条件包括以下至少一项：
TB的大小大于或等于第十一门限；
物理层优先级为预定义优先级。
可选地，在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，所述第一执行模块，具体用于：
在所述终端在所述目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，针对所述目标服务小区从第九预定义时刻开始或继续执行所述预定义操作；
其中，所述N由协议规定或高层信令配置，所述第九预定义时刻基于所述连续N个调度DCI的传输时刻确定。
可选地，所述第一执行模块，具体用于：
在满足第六条件的情况下，停止执行所述预定义操作；
其中，所述第六条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第三预设时长；
所述终端在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
可选地，所述第一执行模块，具体用于：
在所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，针对目标服务小区执行所述预定义操作；
其中，所述第三时间段由协议规定或高层信令配置。
可选地，所述第一执行模块，具体用于：
针对目标服务小区从第十预定义时刻开始或继续执行所述预定义操作；
其中，所述第十预定义时刻为所述第三时间段的结束时刻加预设时间间隔，所述预设时间间隔由协议规定或高层信令配置。
可选地，所述第一执行模块，具体用于：
在满足第七条件的情况下，停止执行所述预定义操作；
其中，所述第七条件包括以下任意一项：
从所述终端确定开始执行或继续所述预定义操作开始，达到第四预设时长；
所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
可选地，所述预定义操作针对的第一对象满足预定义条件；
其中，所述第一对象包括所述第一时域单元集或所述间隔时机，所述预定义条件包括以下至少一项：
所述第一对象应用于第一场景以外的场景，所述第一场景由协议规定或高层信令配置；
所述第一对象仅应用于第二场景，所述第二场景由协议规定或高层信令配置；
所述第一对象的优先级满足预定义优先级要求；
所述第一对象的周期或长度满足预定义要求。
可选地，在所述预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，所述第一执行模块，具体用于以下任意一项：
所述终端期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
所述终端期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
所述终端不期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都不满足指定优先级要求；
所述终端不期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都不满足指定优先级要求。
参见图6，本申请实施例提供一种调整传输限制的装置，该装置应用于网络侧设备，该装置包括：
第二确定模块601，用于确定目标服务小区中存在调度限制或目标间隔时机对应有收发限制；
第二执行模块602，用于根据预设规则，执行预定义操作；
其中，所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机或禁用间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
可选地，在所述预设规则与服务小区的信道质量相关上报信息相关联的情况下，所述第二执行模块，用于：
在所述服务小区的信道质量高于或等于第一门限的情况下，根据服务小区的信道质量相关上报信息，执行所述预定义操作。
可选地，所述第一上报信息包括基于层3测量的测量报告，所述第一执行模块，具体用于以下任意一项：
在发送基于L3测量的测量报告的情况下，执行所述预定义操作，所述基于L3测量的测量报告是基于测量上报事件触发的；
根据层3测量的测量报告中的信道质量信息，执行所述预定义操作。
可选地，所述第一执行模块，具体用于：
在所述网络侧设备接收基于第一事件上报的基于L3测量的测量报告之后，从第一预定义时刻开始执行所述预定义操作；
在所述网络侧设备接收基于第二事件上报的基于L3测量的测量报告之后，在第二预定义时刻停止执行所述预定义操作；
其中，所述第一预定义时刻基于所述第一事件上报的层3测量的测量报告的传输时刻确定，所述第二预定义时刻基于所述第二事件上报的层3测量的测量报告的传输时刻确定。
可选地，所述第二执行模块，用于：
在第一测量报告中的信道质量信息高于或等于第二门限的情况下，从第三预定义时刻开始执行所述预定义操作；
在第二测量报告中的信道质量信息低于或等于第三门限的情况下，在第四预定义时刻停止执行所述预定义操作；
其中，所述第三预定义时刻基于所述第一测量报告的传输时刻确定，所述第四预定义时刻基于所述第二测量报告的传输时刻确定。
可选地，所述第一上报信息包括信道状态信息CSI报告，所述第二执行模块，用于以下任意一项：
在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，从第五预定义时刻开始执行所述预定义操作；
在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，在第六预定义时刻停止执行所述预定义操作；
其中，所述第五预定义时刻基于所述第一CSI报告的传输时刻确定，所述第六预定义时刻基于所述第二CSI报告的传输时刻确定。
可选地，在所述预设规则与上行BSR或SR的相关上报信息相关联的情况下，所述第二执行模块，用于以下至少一项：
在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，针对目标服务小区执行所述预定义操作；
针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，针对目标服务小区执行所述预定义操作；
其中，所述第一条件包括以下至少一项：
所述目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
所述目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
所述目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
所述第二条件包括以下至少一项：
所述网络侧设备针对所述目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道实际接收了SR PUCCH；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组存在待传数据量。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述第二执行模块，用于：
针对所述目标服务小区从第七预定义时刻开始或继续执行所述预定义操作；
其中，所述第七预定义时刻基于所述上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述第二执行模块，用于：
在满足第三条件的情况下，停止执行所述预定义操作；
其中，所述第三条件包括以下任意一项：
从所述网络侧设备确定开始或继续执行所述预定义操作开始，达到第一预设时长；
所述上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足所述第一条件。
可选地，针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，所述第二执行模块，用于：
针对所述目标服务小区从第八预定义时刻开始或继续执行所述预定义操作；
其中，所述第八预定义时刻基于所述SR上报信息或上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，所述第二执行模块，用于：
在满足第四条件的情况下，停止执行所述预定义操作；
其中，所述第四条件包括以下任意一项：
从所述网络侧设备确定开始或继续执行所述预定义操作开始，达到第二预设时长；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组的待传数据量为0。
可选地，在所述预设规则与上下行调度相关信息相关联的情况下，所述第二执行模块，用于：
根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作；
根据调度DCI中指示的传输属性信息，执行预定义操作；
根据数据调度相关信息，执行预定义操作。
可选地，所述第二执行模块，用于以下任意一项：
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或第一窗口存在时域交叠，或者，所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，针对所述间隔时机或所述第一窗口执行所述预定义操作；其中，所述第一窗口为存在所述调度限制的预定义窗口；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或所述第一窗口存在时域交叠，针对所述时域交叠的区域执行所述预定义操作；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，针对扩展时域交叠的区域执行所述预定义操作，所述扩展时域交叠的区域基于所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和所述第十门限确定；
针对第一时间段内存在所述调度限制的所有时域单元执行所述预定义操作，所述第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
针对与第二时间段存在时域交叠或扩展时域交叠，且存在所述调度限制的所有时域单元执行预定义操作，所述第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
可选地，所述第二执行模块，用于：
在所述网络侧设备在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，针对目标Serving cell执行所述预定义操作，所述N由协议规定或高层信令配置；
其中，所述第五条件包括以下至少一项：
TB的大小大于或等于第十一门限；
物理层优先级为预定义优先级。
可选地，在所述网络侧设备在目标传输方向检测到连续N个调度DCI中指示的传输属 性信息满足第五条件的情况下，所述第二执行模块，用于：
在所述网络侧设备在所述目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，针对所述目标Serving cell从第九预定义时刻开始或继续执行所述预定义操作；
其中，所述第九预定义时刻基于所述连续N个调度DCI的传输时刻确定。
可选地，所述第二执行模块，用于：
在满足第六条件的情况下，停止执行所述预定义操作；
其中，所述第六条件包括以下任意一项：
从所述网络侧设备确定开始或继续执行所述预定义操作开始，达到第三预设时长；
所述网络侧设备在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
可选地，所述第二执行模块，用于：
在所述网络侧设备在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，针对目标Serving cell执行所述预定义操作；
其中，所述第三时间段由协议规定或高层信令配置。
可选地，所述第二执行模块，用于：
针对目标Serving cell从第十预定义时刻开始或继续执行所述预定义操作；
其中，所述第十预定义时刻为所述第三时间段的结束时刻加预设时间间隔，所述预设时间间隔由协议规定或高层信令配置。
可选地，所述第二执行模块，用于：
在满足第七条件的情况下，停止执行所述预定义操作；
其中，所述第七条件包括以下任意一项：
从所述网络侧设备确定开始执行或继续所述预定义操作开始，达到第四预设时长；
所述网络侧设备在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
可选地，所述预定义操作针对的第一对象满足预定义条件；
其中，所述第一对象包括所述第一时域单元集或所述间隔时机，所述预定义条件包括以下至少一项：
所述第一对象应用于第一场景以外的场景，所述第一场景由协议规定或高层信令配置；
所述第一对象仅应用于第二场景，所述第二场景由协议规定或高层信令配置；
所述第一对象的优先级满足预定义优先级要求；
所述第一对象的周期或长度满足预定义要求。
可选地，在所述预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，所述第二执行模块，用于以下任意一项：
保证为所述终端调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
保证为所述终端调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
保证为所述终端调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求；
保证为所述终端调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求。
本申请实施例中的调整传输限制的装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的调整传输限制的装置能够实现图2至图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图7所示，本申请实施例还提供一种通信设备700，包括处理器701和存储器702，存储器702上存储有可在所述处理器701上运行的程序或指令，例如，该通信设备700为终端时，该程序或指令被处理器701执行时实现上述方法实施例的各个步骤，且能达到相同的技术效果。该通信设备700为网络侧设备时，该程序或指令被处理器701执行时实现上述方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现终端侧方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图8为实现本申请实施例的一种终端的硬件结构示意图。
该终端800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809以及处理器810等中的至少部分部件。
本领域技术人员可以理解，终端800还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元804可以包括图形处理器(Graphics Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示 单元806可包括显示面板8061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板8061。用户输入单元807包括触控面板8071以及其他输入设备8072中的至少一种。触控面板8071，也称为触摸屏。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元801接收来自网络侧设备的下行数据后，可以传输给处理器810进行处理；另外，射频单元801可以向网络侧设备发送上行数据。通常，射频单元801包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器809可用于存储软件程序或指令以及各种数据。存储器809可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器809可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器809包括但不限于这些和任意其它适合类型的存储器。
处理器810可包括一个或多个处理单元；可选的，处理器810集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，处理器810，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
处理器810，用于根据预设规则，执行预定义操作；
其中，所述第一服务小区为所述终端配置的任意一个服务小区；
所述预设规则与以下任意一项相关联：
与服务小区的信道质量相关的第一上报信息；
与上行BSR或SR相关的第二上报信息；
与上下行调度相关的调度信息；
所述预定义操作包括以下至少一项：
在第一时域单元集内放松所述调度限制或禁用所述调度限制；
跳过或禁用所述目标间隔时机中的至少一个间隔时机；
调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
可选地，在所述预设规则与服务小区的信道质量相关的第一上报信息相关联的情况下，处理器810，具体用于：
在所述服务小区的信道质量高于或等于第一门限的情况下，根据服务小区的信道质量相关上报信息，执行所述预定义操作。
可选地，所述第一上报信息包括基于层3测量的测量报告，所述处理器810，具体用于以下任意一项：
在发送基于L3测量的测量报告的情况下，执行所述预定义操作，所述基于L3测量的测量报告是基于测量上报事件触发的；
根据层3测量的测量报告中的信道质量信息，执行所述预定义操作。
可选地，所述处理器810，具体用于：
在所述终端基于第一事件发送基于L3测量的测量报告之后，从第一预定义时刻开始执行所述预定义操作；
在所述终端基于第二事件发送基于L3测量的测量报告之后，在第二预定义时刻停止执行所述预定义操作；
其中，所述第一预定义时刻基于所述第一事件发送的层3测量的测量报告的传输时刻确定，所述第二预定义时刻基于所述第二事件发送的层3测量的测量报告的传输时刻确定。
可选地，所述处理器810，具体用于：
在第一测量报告中的信道质量信息高于或等于第二门限的情况下，从第三预定义时刻开始执行所述预定义操作；
在第二测量报告中的信道质量信息低于或等于第三门限的情况下，在第四预定义时刻停止执行所述预定义操作；
其中，所述第三预定义时刻基于所述第一测量报告的传输时刻确定，所述第四预定义时刻基于所述第二测量报告的传输时刻确定。
可选地，所述第一上报信息包括信道状态信息CSI报告，所述处理器810，具体用于以下任意一项：
在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，从第五预定义时刻开始执行所述预定义操作；
在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，在第六预定义时刻停止执行所述预定义操作；
其中，所述第五预定义时刻基于所述第一CSI报告的传输时刻确定，所述第六预定义时刻基于所述第二CSI报告的传输时刻确定。
可选地，在所述预设规则与上行BSR或SR相关的第二上报信息相关联的情况下，所述处理器810，具体用于以下至少一项：
在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件 的情况下，针对目标服务小区执行所述预定义操作；
针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，针对目标服务小区执行所述预定义操作；
其中，所述第一条件包括以下至少一项：
所述目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
所述目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
所述目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
所述第二条件包括以下至少一项：
所述终端针对所述目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道触发和实际发送了SR PUCCH；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组存在待传数据量。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述处理器810，具体用于：
针对所述目标服务小区从第七预定义时刻开始或继续执行所述预定义操作；
其中，所述第七预定义时刻基于所述上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述处理器810，具体用于：
在满足第三条件的情况下，停止执行所述预定义操作；
其中，所述第三条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第一预设时长；
所述上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足所述第一条件。
可选地，针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，所述处理器810，具体用于：
针对所述目标服务小区从第八预定义时刻开始或继续执行所述预定义操作；
其中，所述第八预定义时刻基于所述SR上报信息或上行BSR上报信息的传输时刻确定。
可选地，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，所述处理器810，具体用于：
在满足第四条件的情况下，停止执行所述预定义操作；
其中，所述第四条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第二预设时长；
所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组的待传数据量为0。
可选地，在所述预设规则与上下行调度相关信息相关联的情况下，所述处理器810，具体用于：
根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作；
根据调度DCI中指示的传输属性信息，执行预定义操作；
根据数据调度相关信息，执行预定义操作。
可选地，所述处理器810，具体用于以下任意一项：
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或第一窗口存在时域交叠，或者，所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，针对所述间隔时机或所述第一窗口执行所述预定义操作；其中，所述第一窗口为存在所述调度限制的预定义窗口；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或所述第一窗口存在时域交叠，针对所述时域交叠的区域执行所述预定义操作；
在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，针对扩展时域交叠的区域执行所述预定义操作，所述扩展时域交叠的区域基于所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和所述第十门限确定；
针对第一时间段内存在所述调度限制的所有时域单元执行所述预定义操作，所述第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
针对与第二时间段存在时域交叠或扩展时域交叠，且存在所述调度限制的所有时域单元执行预定义操作，所述第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
可选地，所述处理器810，具体用于：
在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，针对目标服务小区执行所述预定义操作，所述N由协议规定或高层信令配置；
其中，所述第五条件包括以下至少一项：
TB的大小大于或等于第十一门限；
物理层优先级为预定义优先级。
可选地，所述处理器810，具体用于：
在所述终端在所述目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，针对所述目标服务小区从第九预定义时刻开始或继续执行所述预定义操作；
其中，所述N由协议规定或高层信令配置，所述第九预定义时刻基于所述连续N个调度DCI的传输时刻确定。
可选地，所述处理器810，具体用于：
在满足第六条件的情况下，停止执行所述预定义操作；
其中，所述第六条件包括以下任意一项：
从所述终端确定开始或继续执行所述预定义操作开始，达到第三预设时长；
所述终端在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
可选地，所述处理器810，具体用于：
在所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，针对目标服务小区执行所述预定义操作；
其中，所述第三时间段由协议规定或高层信令配置。
可选地，所述处理器810，具体用于：
针对目标服务小区从第十预定义时刻开始或继续执行所述预定义操作；
其中，所述第十预定义时刻为所述第三时间段的结束时刻加预设时间间隔，所述预设时间间隔由协议规定或高层信令配置。
可选地，所述处理器810，具体用于：
在满足第七条件的情况下，停止执行所述预定义操作；
其中，所述第七条件包括以下任意一项：
从所述终端确定开始执行或继续所述预定义操作开始，达到第四预设时长；
所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
可选地，所述预定义操作针对的第一对象满足预定义条件；
其中，所述第一对象包括所述第一时域单元集或所述间隔时机，所述预定义条件包括以下至少一项：
所述第一对象应用于第一场景以外的场景，所述第一场景由协议规定或高层信令配置；
所述第一对象仅应用于第二场景，所述第二场景由协议规定或高层信令配置；
所述第一对象的优先级满足预定义优先级要求；
所述第一对象的周期或长度满足预定义要求。
可选地，在所述预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，所述处理器810，具体用于以下任意一项：
期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优 先级都满足指定优先级要求；
不期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都不满足指定优先级要求；
不期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都不满足指定优先级要求。
可以理解，本实施例中提及的各实现方式的实现过程可以参照方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如网络侧方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图9所示，该网络侧设备900包括：天线91、射频装置92、基带装置93、处理器94和存储器95。天线91与射频装置92连接。在上行方向上，射频装置92通过天线91接收信息，将接收的信息发送给基带装置93进行处理。在下行方向上，基带装置93对要发送的信息进行处理，并发送给射频装置92，射频装置92对收到的信息进行处理后经过天线91发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置93中实现，该基带装置93包括基带处理器。
基带装置93例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为基带处理器，通过总线接口与存储器95连接，以调用存储器95中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口96，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备900还包括：存储在存储器95上并可在处理器94上运行的指令或程序，处理器94调用存储器95中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图10所示，该网络侧设备1000包括：处理器1001、网络接口1002和存储器1003。其中，网络接口1002例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的网络侧设备1000还包括：存储在存储器1003上并可在处理器1001上运行的指令或程序，处理器1001调用存储器1003中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述调整传输限制的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述调整传输限制的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述调整传输限制的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的终端侧方法的步骤，所述网络侧设备可用于执行如上所述的网络侧方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (34)

  1. 一种调整传输限制的方法，包括：
    终端确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
    所述终端根据预设规则，执行预定义操作；
    其中，所述第一服务小区为所述终端配置的任意一个服务小区；
    所述预设规则与以下任意一项相关联：
    与服务小区的信道质量相关的第一上报信息；
    与上行缓冲状态报告BSR或调度请求SR相关的第二上报信息；
    与上下行调度相关的调度信息；
    所述预定义操作包括以下至少一项：
    在第一时域单元集内放松所述调度限制或禁用所述调度限制；
    跳过或禁用所述目标间隔时机中的至少一个间隔时机；
    调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
  2. 根据权利要求1所述的方法，其中，在所述预设规则与服务小区的信道质量相关的第一上报信息相关联的情况下，所述终端根据预设规则，执行预定义操作，包括：
    在所述服务小区的信道质量高于或等于第一门限的情况下，所述终端根据所述第一上报信息，执行所述预定义操作。
  3. 根据权利要求2所述的方法，其中，所述第一上报信息包括基于层3测量的测量报告，所述终端根据所述第一上报信息，执行所述预定义操作包括以下任意一项：
    在发送基于层3测量的测量报告的情况下，所述终端执行所述预定义操作，所述基于层3测量的测量报告是基于测量上报事件触发的；
    所述终端根据基于层3测量的测量报告中的信道质量信息，执行所述预定义操作。
  4. 根据权利要求3所述的方法，其中，所述在发送基于层3测量的测量报告的情况下，所述终端执行所述预定义操作包括：
    在所述终端基于第一事件发送基于层3测量的测量报告之后，所述终端从第一预定义时刻开始执行所述预定义操作；
    在所述终端基于第二事件发送基于层3测量的测量报告之后，所述终端在第二预定义时刻停止执行所述预定义操作；
    其中，所述第一预定义时刻基于所述第一事件发送的层3测量的测量报告的传输时刻确定，所述第二预定义时刻基于所述第二事件发送的层3测量的测量报告的传输时刻确定。
  5. 根据权利要求3所述的方法，其中，所述终端根据基于层3测量的测量报告中的信道质量信息，执行所述预定义操作，包括：
    在第一测量报告中的信道质量信息高于或等于第二门限的情况下，所述终端从第三预定义时刻开始执行所述预定义操作；
    在第二测量报告中的信道质量信息低于或等于第三门限的情况下，所述终端在第四预定义时刻停止执行所述预定义操作；
    其中，所述第三预定义时刻基于所述第一测量报告的传输时刻确定，所述第四预定义时刻基于所述第二测量报告的传输时刻确定。
  6. 根据权利要求2所述的方法，其中，所述第一上报信息包括信道状态信息CSI报告，所述终端根据所述第一上报信息，执行所述预定义操作，包括以下任意一项：
    在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，所述终端从第五预定义时刻开始执行所述预定义操作；
    在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，所述终端在第六预定义时刻停止执行所述预定义操作；
    其中，所述第五预定义时刻基于所述第一CSI报告的传输时刻确定，所述第六预定义时刻基于所述第二CSI报告的传输时刻确定。
  7. 根据权利要求1所述的方法，其中，在所述预设规则与上行BSR或SR相关的第二上报信息相关联的情况下，所述终端根据预设规则，执行预定义操作，包括以下至少一项：
    在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，终端针对目标服务小区执行所述预定义操作；
    针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，终端针对目标服务小区执行所述预定义操作；
    其中，所述第一条件包括以下至少一项：
    所述目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
    所述目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
    所述目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
    所述第二条件包括以下至少一项：
    所述终端针对所述目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道触发或实际发送了SR物理上行控制信道PUCCH；
    所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组存在待传数据量。
  8. 根据权利要求7所述的方法，其中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述终端针对目标服务小区执行所述预定义操作，包括：
    所述终端针对所述目标服务小区从第七预定义时刻开始或继续执行所述预定义操作；
    其中，所述第七预定义时刻基于所述上行BSR上报信息的传输时刻确定。
  9. 根据权利要求8所述的方法，其中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，所述终端针对所述目标服务小区开始或继续执行所述预定义操作之后，还包括：
    在满足第三条件的情况下，所述终端停止执行所述预定义操作；
    其中，所述第三条件包括以下任意一项：
    从所述终端确定开始或继续执行所述预定义操作开始，达到第一预设时长；
    所述上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息不满足所述第一条件。
  10. 根据权利要求7所述的方法，其中，
    针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，所述终端针对目标服务小区执行所述预定义操作，包括：
    所述终端针对所述目标服务小区从第八预定义时刻开始或继续执行所述预定义操作；
    其中，所述第八预定义时刻基于所述SR上报信息或上行BSR上报信息的传输时刻确定。
  11. 根据权利要求10所述的方法，其中，在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第二条件的情况下，所述终端针对所述目标服务小区开始或继续执行所述预定义操作之后，还包括：
    在满足第四条件的情况下，所述终端停止执行所述预定义操作；
    其中，所述第四条件包括以下任意一项：
    从所述终端确定开始或继续执行所述预定义操作开始，达到第二预设时长；
    所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组的待传数据量为0。
  12. 根据权利要求1所述的方法，其中，在所述预设规则与上下行调度相关信息相关联的情况下，所述终端根据预设规则，执行预定义操作，包括：
    所述终端根据调度下行控制信息DCI对应的物理下行共享信道PDSCH、信道状态信息参考信号CSI-RS、物理上行共享信道PUSCH、PUCCH或探测参考信号SRS传输的位置，执行预定义操作；
    所述终端根据调度DCI中指示的传输属性信息，执行预定义操作，所述传输属性信息与传输块TB的大小或物理层优先级相关；
    所述终端根据数据调度相关信息，执行预定义操作。
  13. 根据权利要求12所述的方法，其中，所述终端根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作，包括以下任意一项：
    在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或第一窗口存在时域交叠，或者，所述调度DCI对应的PDSCH、CSI-RS、PUSCH、 PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第九门限的情况下，所述终端针对所述间隔时机或所述第一窗口执行所述预定义操作；其中，所述第一窗口为存在所述调度限制的预定义窗口；
    在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输，与所述间隔时机或所述第一窗口存在时域交叠，所述终端针对所述时域交叠的区域执行所述预定义操作；
    在所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元，与所述间隔时机或所述第一窗口占用的时域单元之间的时域间隔小于或等于第十门限的情况下，所述终端针对扩展时域交叠的区域执行所述预定义操作，所述扩展时域交叠的区域基于所述调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输占用的时域单元和所述第十门限确定；
    所述终端针对第一时间段内存在所述调度限制的所有时域单元执行所述预定义操作，所述第一时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定；
    所述终端针对与第二时间段存在时域交叠或扩展时域交叠，且存在所述调度限制的所有时域单元执行预定义操作，所述第二时间段由调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输确定。
  14. 根据权利要求12所述的方法，其中，所述终端根据调度DCI中指示的传输属性信息，执行预定义操作，包括：
    在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息都满足第五条件的情况下，所述终端针对目标服务小区执行所述预定义操作，所述N由协议规定或高层信令配置；
    其中，所述第五条件包括以下至少一项：
    TB的大小大于或等于第十一门限；
    物理层优先级为预定义优先级。
  15. 根据权利要求14所述的方法，其中，在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，所述终端针对目标服务小区执行所述预定义操作，包括：
    在所述终端在所述目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，所述终端针对所述目标服务小区从第九预定义时刻开始或继续执行所述预定义操作；
    其中，所述N由协议规定或高层信令配置，所述第九预定义时刻基于所述连续N个调度DCI的传输时刻确定。
  16. 根据权利要求15所述的方法，其中，在所述终端在目标传输方向检测到连续N个调度DCI中指示的传输属性信息满足第五条件的情况下，所述终端针对目标服务小区开始或继续执行所述预定义操作之后，还包括：
    在满足第六条件的情况下，所述终端停止执行所述预定义操作；
    其中，所述第六条件包括以下任意一项：
    从所述终端确定开始或继续执行所述预定义操作开始，达到第三预设时长；
    所述终端在目标传输方向检测到连续N个调度DCI中至少一个调度DCI指示的传输属性信息不满足第五条件。
  17. 根据权利要求12所述的方法，其中，所述终端根据数据调度相关信息，执行预定义操作，包括：
    在所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，所述终端针对目标服务小区执行所述预定义操作；
    其中，所述第三时间段由协议规定或高层信令配置。
  18. 根据权利要求17所述的方法，其中，在所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，所述终端针对目标服务小区执行所述预定义操作，包括：
    所述终端针对目标服务小区从第十预定义时刻开始或继续执行所述预定义操作；
    其中，所述第十预定义时刻为所述第三时间段的结束时刻加预设时间间隔，所述预设时间间隔由协议规定或高层信令配置。
  19. 根据权利要求18所述的方法，其中，在所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，大于或等于第十一门限的情况下，所述终端针对目标服务小区开始或继续执行所述预定义操作之后，还包括：
    在满足第七条件的情况下，所述终端停止执行所述预定义操作；
    其中，所述第七条件包括以下任意一项：
    从所述终端确定开始执行或继续所述预定义操作开始，达到第四预设时长；
    所述终端在指定传输方向的第三时间段内，调度的数据量或者针对目标逻辑信道或目标逻辑信道组实际调度的数据量，小于第十一门限。
  20. 根据权利要求1所述的方法，其中，
    所述预定义操作针对的第一对象满足预定义条件；
    其中，所述第一对象包括所述第一时域单元集或所述间隔时机，所述预定义条件包括以下至少一项：
    所述第一对象应用于第一场景以外的场景，所述第一场景由协议规定或高层信令配置；
    所述第一对象仅应用于第二场景，所述第二场景由协议规定或高层信令配置；
    所述第一对象的优先级满足预定义优先级要求；
    所述第一对象的周期或长度满足预定义要求。
  21. 根据权利要求20所述的方法，其中，在所述预定义操作为在第一符号时域单元集 内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，所述执行预定义操作，包括以下任意一项：
    所述终端期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
    所述终端期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
    所述终端不期望被调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都不满足指定优先级要求；
    所述终端不期望被调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都不满足指定优先级要求。
  22. 一种调整传输限制的方法，包括：
    网络侧设备确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
    所述网络侧设备根据预设规则，执行预定义操作；
    其中，所述第一服务小区为终端配置的任意一个服务小区；
    所述预设规则与以下任意一项相关联：
    与服务小区的信道质量相关的第一上报信息；
    与上行BSR或SR相关的第二上报信息；
    与上下行调度相关的调度信息；
    所述预定义操作包括以下至少一项：
    在第一时域单元集内放松所述调度限制或禁用所述调度限制；
    跳过或禁用所述目标间隔时机中的至少一个间隔时机；
    调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
  23. 根据权利要求22所述的方法，其中，在所述预设规则与服务小区的信道质量相关上报信息相关联的情况下，所述网络侧设备根据预设规则，执行预定义操作，包括：
    在所述服务小区的信道质量高于或等于第一门限的情况下，所述网络侧设备根据所述第一上报信息，执行所述预定义操作。
  24. 根据权利要求23所述的方法，其中，所述第一上报信息包括基于层3测量的测量报告，所述网络侧设备根据所述第一上报信息，执行所述预定义操作包括以下任意一项：
    在发送基于层3测量的测量报告的情况下，所述网络侧设备执行所述预定义操作，所述基于层3测量的测量报告是基于测量上报事件触发的；
    所述网络侧设备根据层3测量的测量报告中的信道质量信息，执行所述预定义操作。
  25. 根据权利要求23所述的方法，其中，所述第一上报信息包括CSI报告，所述网络侧设备根据所述第一上报信息，执行所述预定义操作，包括以下任意一项：
    在第一CSI报告中的信道质量信息高于或等于第四门限的情况下，所述网络侧设备从第五预定义时刻开始执行所述预定义操作；
    在第二CSI报告中的信道质量信息低于或等于第五门限的情况下，所述网络侧设备在第六预定义时刻停止执行所述预定义操作；
    其中，所述第五预定义时刻基于所述第一CSI报告的传输时刻确定，所述第六预定义时刻基于所述第二CSI报告的传输时刻确定。
  26. 根据权利要求22所述的方法，其中，在所述预设规则与上行BSR或SR相关的第二上报信息相关联的情况下，所述网络侧设备根据预设规则，执行预定义操作，包括以下至少一项：
    在上行BSR上报信息中针对目标逻辑信道或目标逻辑信道组的上报信息满足第一条件的情况下，网络侧设备针对目标服务小区执行所述预定义操作；
    针对目标逻辑信道或目标逻辑信道组的SR上报信息或上行BSR上报信息满足第二条件的情况下，网络侧设备针对目标服务小区执行所述预定义操作；
    其中，所述第一条件包括以下至少一项：
    所述目标逻辑信道或目标逻辑信道组的待传数据的等待时间长于或等于第六门限；
    所述目标逻辑信道或目标逻辑信道组的待传数据的剩余包延迟预算PDB短于或等于第七门限；
    所述目标逻辑信道或目标逻辑信道组的待传数据量高于或等于第八门限；
    所述第二条件包括以下至少一项：
    所述网络侧设备针对所述目标逻辑信道或目标逻辑信道组中的至少一个逻辑信道实际接收了SR PUCCH；
    所述上行BSR上报信息指示针对所述目标逻辑信道或目标逻辑信道组存在待传数据量。
  27. 根据权利要求22所述的方法，其中，在所述预设规则与上下行调度相关信息相关联的情况下，所述网络侧设备根据预设规则，执行预定义操作，包括：
    所述网络侧设备根据调度DCI对应的PDSCH、CSI-RS、PUSCH、PUCCH或SRS传输的位置，执行预定义操作；
    所述网络侧设备根据调度DCI中指示的传输属性信息，执行预定义操作，所述传输属性信息与TB的大小或物理层优先级相关；
    所述网络侧设备根据数据调度相关信息，执行预定义操作。
  28. 根据权利要求22所述的方法，其中，
    所述预定义操作针对的第一对象满足预定义条件；
    其中，所述第一对象包括所述第一时域单元集或所述间隔时机，所述预定义条件包括以下至少一项：
    所述第一对象应用于第一场景以外的场景，所述第一场景由协议规定或高层信令配置；
    所述第一对象仅应用于第二场景，所述第二场景由协议规定或高层信令配置；
    所述第一对象的优先级满足预定义优先级要求；
    所述第一对象的周期或长度满足预定义要求。
  29. 根据权利要求28所述的方法，其中，在所述预定义操作为在第一符号时域单元集内放松调度限制或禁用调度限制，或跳过间隔时机或禁用间隔时机的情况下，所述执行预定义操作，包括以下任意一项：
    所述网络侧设备保证为所述终端调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收对应的优先级都满足指定优先级要求；
    所述网络侧设备保证为所述终端调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收对应的优先级都满足指定优先级要求；
    所述网络侧设备保证为所述终端调度，且位于所述第一对象对应的时间范围内的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求；
    所述网络侧设备保证为所述终端调度，且与所述第一对象对应的时间范围交叠的上行传输或下行接收中至少有一个上行传输或下行接收对应的优先级满足指定优先级要求。
  30. 一种调整传输限制的装置，包括：
    第一确定模块，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
    第一执行模块，用于根据预设规则，执行预定义操作；
    其中，所述第一服务小区为终端配置的任意一个服务小区；
    所述预设规则与以下任意一项相关联：
    与服务小区的信道质量相关的第一上报信息；
    与上行BSR或SR相关的第二上报信息；
    与上下行调度相关的调度信息；
    所述预定义操作包括以下至少一项：
    在第一时域单元集内放松所述调度限制或禁用所述调度限制；
    跳过或禁用所述目标间隔时机中的至少一个间隔时机；
    调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
  31. 一种调整传输限制的装置，包括：
    第二确定模块，用于确定第一服务小区中存在调度限制或存在生效的目标间隔时机；
    第二执行模块，用于根据预设规则，执行预定义操作；
    其中，所述第一服务小区为终端配置的任意一个服务小区；
    所述预设规则与以下任意一项相关联：
    与服务小区的信道质量相关上报信息；
    与上行BSR或SR相关的第一上报信息；
    与上下行调度相关的调度信息；
    所述预定义操作包括以下至少一项：
    在第一时域单元集内放松所述调度限制或禁用所述调度限制；
    跳过或禁用所述目标间隔时机中的至少一个间隔时机；
    调整所述目标间隔时机中的至少一个间隔时机对应的间隔图样参数。
  32. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至22任一项所述的调整传输限制的方法的步骤。
  33. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求23至29任一项所述的调整传输限制的方法的步骤。
  34. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至22任一项所述的调整传输限制的方法的步骤，或者实现如权利要求23至29任一项所述的调整传输限制的方法的步骤。
PCT/CN2024/109071 2023-08-07 2024-08-01 调整传输限制的方法、装置、设备及可读存储介质 Pending WO2025031246A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310990766.8 2023-08-07
CN202310990766.8A CN119450768A (zh) 2023-08-07 2023-08-07 调整传输限制的方法、装置、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2025031246A1 true WO2025031246A1 (zh) 2025-02-13

Family

ID=94525732

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/109071 Pending WO2025031246A1 (zh) 2023-08-07 2024-08-01 调整传输限制的方法、装置、设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN119450768A (zh)
WO (1) WO2025031246A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111918327A (zh) * 2019-05-10 2020-11-10 华为技术有限公司 一种通信方法及装置
CN115087082A (zh) * 2021-03-15 2022-09-20 维沃移动通信有限公司 上行发送处理方法、装置、终端及可读存储介质
US20230199648A1 (en) * 2020-09-25 2023-06-22 Vivo Mobile Communication Co., Ltd. Channel monitoring method and apparatus, and user equipment
US20230217430A1 (en) * 2022-01-04 2023-07-06 Qualcomm Incorporated Techniques for skipping scheduling requests

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111918327A (zh) * 2019-05-10 2020-11-10 华为技术有限公司 一种通信方法及装置
US20230199648A1 (en) * 2020-09-25 2023-06-22 Vivo Mobile Communication Co., Ltd. Channel monitoring method and apparatus, and user equipment
CN115087082A (zh) * 2021-03-15 2022-09-20 维沃移动通信有限公司 上行发送处理方法、装置、终端及可读存储介质
US20230217430A1 (en) * 2022-01-04 2023-07-06 Qualcomm Incorporated Techniques for skipping scheduling requests

Also Published As

Publication number Publication date
CN119450768A (zh) 2025-02-14

Similar Documents

Publication Publication Date Title
US10993277B2 (en) Enhanced PDCP duplication handling and RLC failure handling
JP7039495B2 (ja) サウンディング基準信号（ｓｒｓ）切替えのための複数のアンテナおよび中断時間値
KR102090417B1 (ko) 캐리어 스위칭에 기인한 중단을 위한 핸들링 및 캐리어 스위칭 능력 표시
KR102080982B1 (ko) 비면허 무선 주파수 대역에서의 시분할 lte 전송을 위한 방법 및 장치
JP6559688B2 (ja) キャリアアグリゲーションによるカバレージ拡張
KR102078492B1 (ko) 공유 무선 주파수 스펙트럼 대역에서 사운딩 레퍼런스 신호의 송신을 위한 기법들
KR20250161661A (ko) 채널화 및 bwp
US20150326377A1 (en) Method and apparatus for coexistence among wireless transmit/receive units (wtrus) operating in the same spectrum
JP7681733B2 (ja) 基準信号の伝送方法及び機器
CN117014930A (zh) 测量和上报方法、装置、设备、系统及存储介质
US20250039901A1 (en) Information receiving method, information transmitting method, and device
US20240406981A1 (en) Methods and apparatuses of selecting a carrier for a sidelink multi-carrier operation
CN120880575A (zh) Cli的测量和上报方法、装置、终端、网络侧设备及介质
WO2025031246A1 (zh) 调整传输限制的方法、装置、设备及可读存储介质
WO2025209267A1 (zh) 信息上报、接收方法、装置、设备、可读存储介质及计算机程序产品
WO2025031245A1 (zh) 调整传输限制的方法、装置、设备及可读存储介质
WO2025026316A1 (zh) 传输限制调整方法、装置、终端、网络侧设备及介质
CN121771999A (zh) 资源配置方法、装置、终端及网络侧设备
WO2025026150A1 (zh) 传输控制方法、传输调度方法、传输配置方法及相关设备
CN119450780A (zh) 链路传输处理方法、装置及终端
CN119316955A (zh) 波束处理方法、装置、终端及网络侧设备
WO2026035692A1 (en) Enabling data transmissions during scheduling gaps
CN120034958A (zh) 上行传输资源选择方法、装置、终端及可读存储介质
CN120935551A (zh) 终端能力上报方法、装置、终端及网络侧设备
WO2026032141A1 (zh) 测量处理方法、装置及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24850891

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE