WO2023123777A1 - 配置方法、信道监控方法、通信节点及存储介质 - Google Patents

配置方法、信道监控方法、通信节点及存储介质 Download PDF

Info

Publication number
WO2023123777A1
WO2023123777A1 PCT/CN2022/090048 CN2022090048W WO2023123777A1 WO 2023123777 A1 WO2023123777 A1 WO 2023123777A1 CN 2022090048 W CN2022090048 W CN 2022090048W WO 2023123777 A1 WO2023123777 A1 WO 2023123777A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcch
drx
monitoring
drx cycle
pdcch monitoring
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.)
Ceased
Application number
PCT/CN2022/090048
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP22913073.7A priority Critical patent/EP4459905A4/en
Priority to KR1020247025366A priority patent/KR20240141746A/ko
Publication of WO2023123777A1 publication Critical patent/WO2023123777A1/zh
Priority to US18/757,487 priority patent/US20240349302A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0087—Timing of allocation when data requirements change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/36—Transmission power control [TPC] using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • 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/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the technical field of wireless communication networks, for example, to a configuration method, a channel monitoring method, a communication node and a storage medium.
  • the Configured Grant (CG) resource and semi-persistent scheduling (Semi-Persistent Scheduling, SPS) strategy for energy saving of the terminal (User Equipment, UE) is only applicable to the determination of the transmission opportunity (data packet transmission starts Timing and period are determined) for small-period services (transmission interval is usually less than or equal to 640ms); for services with uncertain data packet transmission timing or long periods, Discontinuous Reception in RRC_CONNECTED state (C-CONNECTED state, C- DRX) mechanism, and in the current C-DRX, the value range of the DRX cycle can only be in ms, and can only take a few discrete values, if the service cycle is not an integer multiple of ms or the cycle is not in the DRX cycle If the value is within the range, the C-DRX mechanism cannot be applied; if the service cycle is large (greater than 10240ms), the C-DRX mechanism cannot be used either.
  • CG Configured Grant
  • SPS
  • the start position of the DRX cycle is fixed in different radio frame periods, but for services whose service period is not an integer factor of 10240ms, the start position of the DRX cycle in different radio frame periods may be different, so the current The DRX mechanism cannot be applied to scenarios where the business cycle is not an integer factor of 10240 ms.
  • the configuration of the PDCCH search space also has a problem similar to that of the C-DRX configuration.
  • the present application provides a configuration method, a channel monitoring method, a communication node and a storage medium.
  • An embodiment of the present application provides a configuration method, including: acquiring service information, the service information including the service period, the start time of the possible arrival of the service, and the end time of the possible arrival of the service; sending a physical downlink control channel (Physical Downlink Control Channel) according to the service information Downlink Control Channel, PDCCH) monitoring related configuration information, the configuration information is used to indicate the monitoring timing of PDCCH.
  • a physical downlink control channel Physical Downlink Control Channel
  • PDCCH Physical Downlink Control Channel
  • the embodiment of the present application also provides a channel monitoring method, including: receiving configuration information related to PDCCH monitoring, where the configuration information is used to indicate a PDCCH monitoring opportunity; and monitoring the PDCCH according to the configuration information.
  • the embodiment of the present application also provides a communication node, including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • a communication node including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor executes the program, the above-mentioned configuration method or channel is implemented. monitoring method.
  • the embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the above configuration method or channel monitoring method is implemented.
  • Fig. 1 is a flowchart of a configuration method provided by an embodiment
  • Fig. 2 is a flow chart of a channel monitoring method provided by an embodiment
  • Fig. 3 is a schematic diagram of acquiring business information provided by an embodiment
  • FIG. 4 is a schematic diagram of a DRX configuration mode provided by an embodiment
  • FIG. 5 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 6 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 7 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 8 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 9 is a schematic diagram of another DRX configuration mode provided by an embodiment.
  • FIG. 10 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 11 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 12 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • FIG. 13 is a schematic diagram of another DRX configuration mode provided by an embodiment
  • Fig. 14 is a schematic structural diagram of a configuration device provided by an embodiment
  • Fig. 15 is a schematic structural diagram of a channel monitoring device provided by an embodiment
  • Fig. 16 is a schematic diagram of a hardware structure of a communication node provided by an embodiment.
  • FIG. 1 is a flow chart of a configuration method provided by an embodiment. As shown in FIG. 1 , the method can be applied to a first communication node, and the first communication node can be a base station side node or a network side node.
  • the method provided in this embodiment includes step 110 and step 120 .
  • step 110 service information is obtained, and the service information includes a service cycle, a start time of possible service arrival, and a possible end time of service arrival.
  • step 120 configuration information related to PDCCH monitoring is sent according to the service information, and the configuration information is used to indicate the timing of PDCCH monitoring.
  • the first communication node acquires service information, where the service information may include the service period, the start time of the possible arrival of the service, and the end time of the possible arrival of the service; on this basis, the first communication node according to the acquired service information Send configuration information related to PDCCH monitoring to the UE side, where the configuration information can be used to indicate the timing of PDCCH monitoring.
  • the monitoring timing of the PDCCH by indicating the monitoring timing of the PDCCH according to the configuration of the service information, it is not limited by the service cycle, and the flexibility of monitoring is improved, and the business with uncertain or long-period data packet transmission timing and the service cycle is not 10240ms are realized.
  • the power saving of the terminal by an integer factor of .
  • the configuration information is DRX configuration information; the configuration information is used to indicate the start time of PDCCH monitoring, the end time of PDCCH monitoring and the length of DRX cycle.
  • the start time of PDCCH monitoring is indicated by a first designated position and a first time offset
  • the first designated position includes a radio resource control (Radio Resource Control, RRC) message of configuration information or a media access Control (Medium Access Control, MAC) Control Element (Control Element, CE) radio frame, subframe and/or time slot for the first transmission, or the first designated position is the designated radio frame, subframe and/or time slot
  • RRC Radio Resource Control
  • MAC Media Access Control
  • Control Element Control Element
  • the first time offset includes the time interval from the first specified position to the start time of PDCCH monitoring
  • the end time of PDCCH monitoring is indicated according to the second specified position and the second time offset, wherein the second specified position includes The first designated position, or the start time of PDCCH monitoring
  • the second time offset includes a time interval from the second designated position to the end time of PDCCH monitoring.
  • the method further includes: within the PDCCH monitoring period, configuring periodic buffer status report (Buffer Status Report, BSR) resources or scheduling request (Scheduling Request, SR) indication resources; or based on the PDCCH monitoring period Determine the effective timing of periodic BSR resources or SR indication resources; or indicate the effective time period of periodic BSR resources or SR indication through configuration information, and the PDCCH monitoring period is a predefined time period after receiving BSR or SR;
  • BSR periodic buffer status report
  • SR scheduling request
  • the method also includes: performing uplink physical uplink shared channel (physical uplink shared channel, PUSCH) resource scheduling for carrying user plane data in the case of receiving the BSR or SR; wherein, the periodic BSR resources or SR indication resources include periodic CG resources, periodic non-contention Physical Random Access Channel (Physiacal Random Access Channel, PRACH) resources and/or an uplink physical signal used to indicate allocation of uplink authorization resources bearing user plane data.
  • uplink physical uplink shared channel physical uplink shared channel, PUSCH
  • PUSCH resource scheduling for carrying user plane data in the case of receiving the BSR or SR
  • the periodic BSR resources or SR indication resources include periodic CG resources, periodic non-contention Physical Random Access Channel (Physiacal Random Access Channel, PRACH) resources and/or an uplink physical signal used to indicate allocation of uplink authorization resources bearing user plane data.
  • PRACH Physical Random Access Channel
  • the method further includes: configuring periodic BSR resources or SR indication resources during the period from the start time of service possible arrival to the end time of service possible arrival; after the second communication node sends BSR or SR, it starts Monitoring the PDCCH; wherein, the periodic BSR resources or SR indication resources include periodic CG resources, periodic non-contention PRACH resources and/or uplink physical signals used to indicate allocation of uplink authorization resources bearing user plane data.
  • the configuration information is used to indicate the start time of PDCCH monitoring and the length of the DRX cycle; the configuration information is also used to indicate the end time of PDCCH monitoring, or the PDCCH monitoring period or DRX inactivation timing information.
  • the configuration information is used to indicate the start time of PDCCH monitoring, DRX inactivation timing information and DRX cycle length.
  • the configuration information includes multiple groups of DRX configurations, each group of DRX configurations includes a DRX cycle length and a corresponding start offset; the timing of PDCCH monitoring is a union of PDCCH monitoring timings in each DRX configuration.
  • the configuration information includes multiple sets of DRX configurations, and each set of DRX configurations includes a start time of PDCCH monitoring, an end time of PDCCH monitoring, and a service period.
  • the configuration information includes the DRX cycle and the configuration information of multiple PDCCH monitoring periods included in the DRX cycle; the configuration information of the multiple PDCCH monitoring periods includes: the length of each PDCCH monitoring period, the number of PDCCH monitoring periods, and /or the starting position of each PDCCH monitoring period.
  • the configuration information includes multiple groups of DRX configurations, and each group of DRX configurations corresponds to a DRX inactivity timer.
  • the configuration information includes a DRX cycle and a PDCCH monitoring period of two lengths.
  • the configuration information includes a DRX cycle, PDCCH monitoring periods of two lengths, and descending steps of the PDCCH monitoring periods.
  • the method further includes: in the case of starting to transmit data, sending a PDCCH channel or a transmission start indication or a PDCCH monitoring start indication or a wake-up signal; in the case of a data transmission stop, sending a transmission end indication or a PDCCH monitoring End indication or hibernation indication.
  • the configuration information is the PDCCH search space configured by the following parameters: the start time of the PDCCH search space, the PDCCH monitoring period, and the period of the PDCCH search space.
  • the configuration information is the PDCCH search space configured by the following parameters: PDCCH monitoring period and period of the PDCCH search space.
  • the start time of the PDCCH search space is the time when the UE sends the BSR or SR, or the time when the UE sends the BSR or SR and moves backward for a predefined time period.
  • obtaining service information includes: obtaining service information according to a quality of service (Quality of Service, QoS) parameter delivered by the core network; or obtaining service according to terminal auxiliary information, uplink RRC message and/or uplink MAC CE structure information.
  • QoS Quality of Service
  • Fig. 2 is a flow chart of a channel monitoring method provided by an embodiment. As shown in Fig. 2, the method may be applied to a second communication node, and the second communication node may be a UE side node. The method provided in this embodiment includes step 210 and step 220 .
  • step 210 configuration information related to PDCCH monitoring is received, and the configuration information is used to indicate the timing of PDCCH monitoring.
  • step 220 monitor the PDCCH according to the configuration information.
  • the UE side receives configuration information related to PDCCH monitoring sent by the base station side, where the configuration information can be used to indicate the timing of PDCCH monitoring; on this basis, the UE side can monitor the PDCCH according to the configuration information.
  • the second communication node can monitor the PDCCH according to the monitoring timing of the PDCCH indicated by the configuration information, which is not limited by the service cycle, improves the flexibility of monitoring, and realizes the uncertain or long-period data packet transmission timing. Energy saving for services and terminals whose service period is not an integer factor of 10240ms.
  • the configuration information is DRX configuration information; the configuration information is used to indicate the start time of PDCCH monitoring, the end time of PDCCH monitoring, and the length of the DRX cycle;
  • Monitor PDCCH according to configuration information, including: in each DRX cycle, monitor PDCCH in a specified time interval or monitor PDCCH according to the first PDCCH search space, do not monitor PDCCH in a non-specified time interval or monitor PDCCH according to the second PDCCH search space or , in each DRX cycle, start monitoring PDCCH after sending BSR or SR;
  • the specified time interval includes from the start time of PDCCH monitoring to the completion of data packet transmission, or from the start time of PDCCH monitoring to the end time of PDCCH monitoring, or from sending BSR or SR to data packet transmission completion, or from sending BSR Or the end time of PDCCH monitoring after SR.
  • the start time of the Nth DRX cycle is one of the following:
  • the configuration information is used to indicate the start time of PDCCH monitoring and the length of the DRX cycle; the configuration information is also used to indicate the end time of PDCCH monitoring, or the PDCCH monitoring period or DRX inactivation timing information.
  • monitoring the PDCCH according to the configuration information includes: in each DRX cycle, starting to monitor the PDCCH from the start time of the PDCCH monitoring, and stopping monitoring the PDCCH until any of the following conditions are met: monitoring after the start time of the PDCCH monitoring to the PDCCH, and start the DRX inactive timer after receiving or feeding back the Hybrid Automatic Repeat reQuest (HARQ) confirmation information (ACKnowledge, ACK); monitor the PDCCH during the DRX inactive timer timing, and Restart the DRX inactive timer after receiving or feeding back the HARQ ACK; the PDCCH is not monitored during the DRX inactive timer timing, and the DRX inactive timer expires; the end time of the PDCCH monitoring expires and the PDCCH is not monitored.
  • HARQ Hybrid Automatic Repeat reQuest
  • the configuration information is used to indicate the start time of PDCCH monitoring, DRX inactivation timing information and DRX cycle length.
  • the method further includes one of the following: in each DRX cycle,
  • the DRX inactive timer is restarted after receiving or feeding back the HARQ ACK;
  • the configuration information includes multiple sets of DRX configurations
  • Monitoring the PDCCH according to the configuration information includes: monitoring the PDCCH at the PDCCH monitoring occasion included in each DRX configuration.
  • the configuration information includes configuration information of the first DRX cycle and configuration information of the second DRX cycle, wherein the first DRX cycle includes multiple second DRX cycles;
  • Monitoring the PDCCH according to the configuration information includes: in each first DRX cycle, for the overlapping area of the PDCCH monitoring period included in the first DRX cycle and the second DRX cycle, from the start timing of the earlier PDCCH monitoring period to Monitor the PDCCH at the end timing of the later PDCCH monitoring period; for non-overlapping areas, monitor the PDCCH according to the PDCCH monitoring period included in the second DRX cycle.
  • the configuration information includes a DRX cycle and a first PDCCH monitoring period and a second PDCCH monitoring period;
  • Monitor PDCCH according to configuration information including:
  • the PDCCH Before receiving a PDCCH channel or a transmission start indication or a PDCCH monitoring start indication or a wake-up signal, monitor the PDCCH on the first PDCCH monitoring period; after receiving a PDCCH channel or a transmission start indication or a PDCCH monitoring start indication or a wake-up signal, until receiving When the transmission end indication or the PDCCH monitoring end indication or dormancy indication is reached, the PDCCH is monitored during the second PDCCH monitoring period;
  • monitor PDCCH according to configuration information including:
  • monitor PDCCH according to configuration information including:
  • monitor PDCCH according to configuration information including:
  • monitor PDCCH according to configuration information including:
  • monitor PDCCH according to configuration information including:
  • the first DRX cycle includes one or more DRX cycles
  • the second DRX cycle includes one or more DRX cycles.
  • the configuration information includes the DRX cycle, the PDCCH monitoring period of two lengths, and the descending step of the PDCCH monitoring period;
  • Monitoring PDCCH according to configuration information including: before receiving PDCCH channel or transmission start indication or PDCCH monitoring start indication or wake-up signal, monitoring PDCCH according to the PDCCH monitoring period with the smaller length of the two lengths; after receiving PDCCH channel or transmission start In the first DRX cycle after the indication or PDCCH monitoring start indication or the wake-up signal, the PDCCH is monitored according to the longer PDCCH monitoring period of the two lengths, and the corresponding PDCCH is used in each DRX cycle except the first DRX cycle.
  • the PDCCH monitoring period of a specified length monitors the PDCCH; if an instruction to stop data transmission is received, the PDCCH is monitored according to the PDCCH monitoring period with a smaller length; wherein, if data is successfully received in any DRX cycle, the next DRX cycle
  • the specified length corresponding to a DRX cycle is the length of the PDCCH monitoring period of the DRX cycle minus the down step;
  • the designated length corresponding to the next DRX cycle is restored to the larger length of the two lengths; wherein, the designated length corresponding to each DRX cycle is greater than or equal to the smaller length of the two lengths.
  • monitoring the PDCCH according to the configuration information includes: within the PDCCH monitoring period in each DRX cycle, monitoring the PDCCH that meets the conditions from the start position of the first PDCCH search space, the PDCCH that meets the conditions includes the search space
  • the start position of the PDCCH falls within the PDCCH monitoring period of the corresponding DRX cycle.
  • the method further includes: determining the PDCCH search space according to the following parameters: the start time of the PDCCH search space, the PDCCH monitoring period, and the period of the PDCCH search space.
  • Fig. 3 is a schematic diagram of acquiring service information provided by an embodiment.
  • Obtaining the service information by the base station may include: obtaining the service information according to the QoS parameters delivered by the core network; or obtaining the service information according to the auxiliary information of the terminal, the uplink RRC message and/or the uplink MAC CE structure.
  • the service information may include a service cycle, a possible start time of service arrival, and a possible end time of service arrival.
  • the service mode of periodic services with uncertain arrival time (large jitter range) is used to illustrate that the core network or UE notifies the base station of the service period (i.e. Period) and the start time of possible arrival of the service (i.e.
  • burst Arrival Start Time ie Burst Arrival End Time
  • the start time of the possible arrival of the business and the end time of the possible arrival of the business can also be determined by the possible arrival time of the business (that is, Burst Arrival Time) and the fluctuation range of the business arrival time (that is, Burst Arrival Time Spread, or Burst Arrival Time Jitter). characterization. for example:
  • the start time of the possible arrival of the business the possible arrival time of the business - the fluctuation range of the business arrival time;
  • End time of possible service arrival possible service arrival time+fluctuation range of service arrival time.
  • the start time of the possible arrival of the business the possible arrival time of the business - the fluctuation range of the business arrival time / 2;
  • End time of possible service arrival possible service arrival time+fluctuation range of service arrival time/2.
  • Fig. 4 is a schematic diagram of a DRX configuration manner provided by an embodiment. As shown in FIG. 4 , based on the service mode shown in FIG. 3 provided by the core network or the UE, the connection mode DRX cycle configured by the base station for the UE is taken as an example.
  • the configuration information is DRX configuration information.
  • the base station configures the UE in RRC connection mode: the start time of PDCCH monitoring (ie PDCCH Monitoring Start Time), the end time of PDCCH monitoring (ie PDCCH Monitoring End Time), and the length of the DRX cycle; UE in a In the DRX cycle, the time interval from the start time of PDCCH monitoring to the completion of uplink/downlink data packet transmission (that is, the specified time interval), or the time interval from the start time of PDCCH monitoring to the end time of PDCCH monitoring (that is, the specified time interval ) (Which one of the times arrives first shall prevail.
  • the start time of PDCCH monitoring ie PDCCH Monitoring Start Time
  • the end time of PDCCH monitoring ie PDCCH Monitoring End Time
  • the length of the DRX cycle UE in a In the DRX cycle, the time interval from the start time of PDCCH monitoring to the completion of uplink/downlink data packet transmission (that is, the specified time interval), or the time interval from the start time of PDC
  • the UE needs to monitor the PDCCH in the specified time interval or monitor the PDCCH according to the first PDCCH search space (with a smaller PDCCH monitoring period); A large PDCCH monitoring period) monitors the PDCCH.
  • the start time of PDCCH monitoring corresponds to the start time of possible service arrival
  • the end time of PDCCH monitoring corresponds to the end time of the possible arrival of the service, which is shifted backward by an amount of time (that is, Time Offset); the amount of time is to consider the retransmission delay of service scheduling and the HARQ ACK/NACK delay, where NACK is non-acknowledgment information (i.e. Non ACKnowledge);
  • the DRX cycle corresponds to the cycle of the service.
  • the DRX cycle configured by the base station for the UE can be in one-to-one correspondence with the service mode of the UE.
  • the value range of the service cycle is completely consistent with the value range of the DRX cycle.
  • the cycle of the DRX cycle is expressed in Hertz (Hz) , frames per second (fps), ms (milliseconds), or us (microseconds), and can be a period represented by any integer value within the value range.
  • the value range of the DRX cycle is not limited by a system frame number (System Frame Number, SFN) cycle (ie 10240ms), that is, it can be greater than one SFN cycle.
  • SFN System Frame Number
  • the UE can use the timer to calculate the start time of the next DRX cycle (the end time of the previous DRX cycle is the start time of the next DRX cycle).
  • the start time of the Nth DRX cycle Floor (the start time of the first DRX cycle + (N-1)*Period), that is, the start time of the Nth DRX cycle is the first The result of rounding down the sum of the start time of each DRX cycle and the sum of N-1 service cycles.
  • Floor can represent the lower integer
  • N can represent the Nth DRX cycle
  • Period can represent the service cycle or the length of the DRX cycle, which should be converted into the basic unit of the DRX cycle length (such as ms, slot or symbol) during calculation.
  • the start time of the Nth DRX cycle can also be calculated as follows:
  • the start time of the Nth DRX cycle Ceil(the start time of the first DRX cycle+(N-1)*Period), that is, the start time of the Nth DRX cycle can be the start time of the first DRX cycle and N-1
  • the start time of the Nth DRX cycle Round(the start time of the first DRX cycle+(N-1)*Period), that is, the start time of the Nth DRX cycle can be the start time of the first DRX cycle and N-1
  • the start time of the Nth DRX cycle the start time of the first DRX cycle + Floor((N-1)*Period), that is, the start time of the Nth DRX cycle can be the start time of the first DRX cycle and the N-1
  • the start time of the Nth DRX cycle the start time of the first DRX cycle + Ceil((N-1)*Period), that is, the start time of the Nth DRX cycle can be the start time of the first DRX cycle and N-1
  • the start time of the Nth DRX cycle the start time of the first DRX cycle + Round((N-1)*Period), that is, the start time of the Nth DRX cycle can be the start time of the first DRX cycle
  • Ceil is rounded up; Round is rounded to the nearest integer.
  • the cycle unit ms of the DRX cycle may also be a frame (frame), a subframe (subframe), a slot (slot), or a symbol (symbol). That is, the service cycle is first converted into the cycle unit of the DRX cycle, and then rounded down, rounded up, or rounded to the start time of the cycle unit of the DRX cycle.
  • the service occurrence frequency is characterized by Hz or fps, it can be converted into the corresponding service period through the reciprocal.
  • the service period corresponding to x Hz is (1/x) seconds, and then it can be converted to ms, symbol or slot on this basis.
  • 1ms 1subframe, so the unit of ms and subframe is equivalent.
  • the related method can also be used in the configuration strategy of CG or SPS.
  • the business cycle may not be an integer multiple of ms.
  • IIoT Industrial Internet of Things
  • XR Extended Reality
  • the frequency of business occurrence is often expressed in Hz
  • the reciprocal of x Hz (1/x Hz) is the corresponding business cycle
  • fps that is, frame per second
  • the reciprocal of x fps (1/x fps) is the corresponding business cycle.
  • 60Hz or 10fps corresponds to a period of 16.667ms
  • 120Hz or 8.333fps corresponds to a period of 8.333ms.
  • Such a non-integer period cannot match the period of CG or SPS.
  • the cycle of CG or SPS can be configured with the actual cycle of the service (Hz, fps or non-integer value).
  • Floor means rounding down
  • Ceil means rounding up
  • Round means rounding up to the nearest integer.
  • N means the Nth DRX cycle
  • Period means the actual cycle of the service, which should be converted to CG or SPS cycle during calculation
  • the basic unit (such as ms, slot or symbol).
  • the start time of PDCCH monitoring can be characterized relative to the first designated position (such as a certain SFN, subframe and/or slot) and the first time offset (such as time offset 2, namely TimeOffset2), specifically: SFN , subframe and/or slot is the radio frame, subframe and/or time slot of the first transmission of the RRC message or MAC CE that configures the C-DRX, or the radio frame specified by the RRC message or MAC CE that configures the C-DRX , subframe and/or time slot.
  • the time offset 2 ie, TimeOffset2 is the time interval from the first designated position to the start time of PDCCH monitoring.
  • the end time of PDCCH monitoring can be characterized relative to a second designated position (such as a certain SFN, subframe and/or slot) and a second time offset (such as time offset 3, namely TimeOffset3), specifically: the first
  • the two designated positions include the first designated position, or the start time of PDCCH monitoring.
  • the time offset 3 (ie, TimeOffset3) is the time interval (ie, On-Duration) from the second designated position to the end time of PDCCH monitoring.
  • the base station configures periodic BSR resources or SR indication resources for the UE so that the UE can request an uplink grant (UpLink Grant, UL Grant); upon receiving the BSR or SR, the base station performs uplink PUSCH resource scheduling for carrying user plane data, reducing uplink transmission delay. That is, the SR indication resource during the On-Duration period is only applicable to the scenario where the message size (Message Size) is fixed. The base station can know the size of the UL Grant resource to be allocated after receiving the SR, without requiring the UE to report the BSR.
  • the periodic BSR resources or SR indication resources may include periodic CG resources, periodic non-contention PRACH resources, or uplink physical signals that can be used to instruct the base station to allocate UL Grant resources.
  • the configuration information includes a periodic BSR resource or a valid time period indicated by an SR, and the PDCCH monitoring period is a predefined time period after receiving the BSR or SR.
  • Fig. 5 is a schematic diagram of another DRX configuration manner provided by an embodiment.
  • the base station configures the connected mode DRX cycle for the UE as an example.
  • Configuration effective timing of periodic BSR or SR, DRX cycle length; UE starts to monitor PDCCH after sending BSR or SR in one DRX cycle.
  • the UE needs to monitor the PDCCH within the specified time interval or monitor according to the first PDCCH search space (with a smaller PDCCH monitoring period).
  • the UE does not need to monitor the PDCCH or monitor the PDCCH according to the second PDCCH search space (with a larger PDCCH monitoring period) in the unspecified time interval.
  • the calculation of the DRX cycle is the same as that in FIG. 4 .
  • the specified time interval may also be from sending the BSR or SR to the completion of data packet transmission, or from sending the BSR or SR to the end time of PDCCH monitoring.
  • the completion of the data packet transmission refers to the completion of the HARQ ACK process of data transmission and/or the completion of the RLC ACK process, and that is, the ACK confirmation of the data packet transmission is received, and there is no subsequent data transmission, or within the current DRX cycle No more data transfer.
  • Fig. 6 is a schematic diagram of another DRX configuration mode provided by an embodiment. As shown in FIG. 6 , the connection mode DRX support of periodic services with uncertain arrival time (large jitter range) and uncertain data packet size is illustrated.
  • the base station configures the start time of PDCCH monitoring and the length of the DRX cycle for the UE, and also configures the end time of PDCCH monitoring or the PDCCH monitoring period (ie On-Duration) or DRX inactivation timing information (ie DRX-Inactivity Timer).
  • UE starts to monitor PDCCH from the start time of PDCCH monitoring until any of the following conditions are met, UE stops PDCCH monitoring until the beginning of the next DRX cycle (the start position of the next DRX cycle is the previous DRX cycle The starting position of (that is, PDCCH Monitoring Start Time) + DRX cycle):
  • the start time of PDCCH monitoring may be the start time of C-DRX, may be a specified timing in C-DRX, or the timing when the C-DRX start time is shifted backward by a predefined time period.
  • the specified timing or the offset of the predefined time period is predefined by the standard or configured by the base station.
  • the PDCCH is not monitored during the timing period of the DRX inactive timer, and the DRX inactive timer expires;
  • the end time of PDCCH monitoring is up and no PDCCH is monitored.
  • Fig. 7 is a schematic diagram of another DRX configuration mode provided by an embodiment. As shown in FIG. 7 , the connection mode DRX support of periodic services with uncertain arrival time (large jitter range) and uncertain data packet size is illustrated.
  • the base station configures the start time of PDCCH monitoring, DRX inactivation timing information and DRX cycle length for the UE (there is no explicit configuration of the end time of PDCCH monitoring).
  • the UE monitors PDCCH in the DRX cycle until it monitors PDCCH:
  • the DRX inactive timer is restarted after receiving or feeding back the HARQ ACK;
  • the PDCCH monitoring will be stopped after the DRX inactive timer expires until the next DRX cycle starts (the start position of the next DRX cycle is the start position of the previous DRX cycle ( That is, PDCCH Monitoring Start Time)+DRX cycle).
  • Figure 7 can be considered as a special case of Figure 6: it is equivalent to not configuring the end time of PDCCH monitoring, and it can also be understood that the end time of PDCCH monitoring overlaps with the end time of the DRX cycle.
  • the existing DRX cycle can only take several discrete values, as follows:
  • DRX short cycle such as ⁇ ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 ⁇ ;
  • DRX long cycle start offset such as ⁇ ms10 INTEGER(0...9),ms20 INTEGER(0...19),ms32 INTEGER(0...31),ms40 INTEGER(0...39),ms60 INTEGER (0...59),ms64 INTEGER(0...63),ms70 INTEGER(0...69),ms80 INTEGER(0...79),ms128 INTEGER(0...127),ms160 INTEGER(0...159),ms256 INTEGER(0 ...255),ms320 INTEGER(0...319),ms512 INTEGER(0...511),ms640 INTEGER(0...639),ms1024 INTEGER(0...1023),ms1280 INTEGER(0...1279),ms2048 INTEGER(0...2047 ), ms2560 INTEGER(0...2559), ms5120 INTEGER(0...5119), ms10
  • the timing for the UE to monitor the PDCCH can be the PDCCH monitoring timing in the multiple DRX configurations
  • Fig. 8 is a schematic diagram of another DRX configuration mode provided by an embodiment. As shown in FIG. 8 , an example is illustrated by using two DRX configurations to map a smaller DRX cycle.
  • the UE monitors the PDCCH at a PDCCH monitoring opportunity included in each DRX configuration.
  • the first On-Duration is the PDCCH monitoring timing of DRX cycle 1;
  • the second On-Duration is the PDCCH monitoring timing of DRX cycle 2;
  • the third On-Duration is the next PDCCH monitoring timing of DRX cycle 1 ;
  • the fourth On-Duration is the next PDCCH monitoring opportunity of DRX cycle 2; and so on.
  • multiple sets of DRX configurations can also be used for DRX configurations with non-integer periods.
  • the service arrival start time is 0hh0mm0ss0ms
  • the arrival end time is 0hh0mm0ss1ms
  • the service mode may be split into C-DRX configurations of multiple integer periods.
  • Table 1 shows a correspondence between C-DRX configuration 1 and C-DRX parameters. As shown in Table 1, configure the following three C-DRX parameters for the UE to map the service mode:
  • Fig. 9 is a schematic diagram of another DRX configuration mode provided by an embodiment. As shown in FIG. 9 , it is described by using one DRX to include multiple On-Duration opportunities to map the DRX whose service cycle is not an integer multiple of 1 ms.
  • the base station configures the configuration information of a DRX cycle and multiple On-Durations (that is, PDCCH monitoring period) contained in a DRX cycle for the UE; multiple On-Durations include: On-Duration length, On-Duration individual Number and/or starting position of each On-Duration.
  • the On-Duration lengths of multiple On-Durations can be the same (multiple On-Durations in one DRX cycle share one On-Duration length), or the On-Duration lengths of multiple On-Durations are different (multiple On-Durations in one DRX cycle On-Duration corresponds to an On-Duration length list).
  • the starting positions of multiple On-Durations in a DRX cycle can be explicitly indicated by the base station, or the first On-Duration starting position can be explicitly indicated, and the remaining On-Duration starting positions can be based on the first On-Duration starting position, etc.
  • the interval is calculated.
  • a DRX cycle contains 3 On-Durations; the start position of the first On-Duration is the start position of the DRX cycle;
  • Fig. 10 is a schematic diagram of another DRX configuration mode provided by an embodiment. As shown in Figure 10, the simultaneous configuration of DRX and Legacy DRX cycles specifying the start timing of the DRX cycle is described.
  • This embodiment shows the case of multiple groups of DRX configurations: each group of DRX configurations corresponds to a DRX inactivation timer, and the DRX inactivation timer corresponding to each group of DRXs is started independently; the monitoring timing of PDCCH monitoring is in multiple groups of DRX A union of PDCCH monitoring opportunities.
  • the base station configures a DRX cycle 1 (that is, the first DRX cycle) and the corresponding PDCCH monitoring start time, On-Duration1 for the UE; the base station configures a DRX cycle 2 (that is, the second DRX cycle) and the corresponding On-Duration2.
  • DRX cycle 1 is longer than DRX cycle 2, and one DRX cycle 1 includes multiple DRX cycles 2.
  • the start timing of DRX cycle 2 is earlier than the start timing of DRX cycle 1 and the start time of PDCC monitoring, and the end timing of DRX cycle 1 is also later than the end timing of DRX cycle 2 .
  • the UE monitors the PDCCH for a time period of: [start timing of DRX cycle 2, end timing of DRX cycle 1].
  • start timing of DRX cycle 2 end timing of DRX cycle 1
  • the UE In the remaining time periods of DRX cycle 1, because there is only On-Duration 2 of DRX cycle 2, the UE only needs to monitor the PDCCH according to On-Duration 2 of DRX cycle 2.
  • Fig. 11 is a schematic diagram of another DRX configuration mode provided by an embodiment.
  • the service mode of the quasi-periodic service with uncertain arrival time (large jitter range) and the corresponding DRX configuration are used for illustration.
  • the network configures the DRX cycle and two lengths of PDCCH monitoring period (On-Duration), such as the first PDCCH monitoring period (DRX-OnDurationTimer1) and the second PDDCH monitoring period (DRX-OnDurationTimer2), the larger On-Duration covers the entire Jitter (Jitter) range.
  • On-Duration two lengths of PDCCH monitoring period
  • the network sends the PDCCH channel or transmission start indication (ie Transmission Start Indication) or PDCCH monitoring start indication (ie PDCCH Monitoring Start Indication) or wake up signal (Wake Up Signal, WUS); if the data transmission stops, it is sent Transmission end indication (ie Transmission End Indication) or PDCCH monitoring end indication (ie PDCCH Monitoring End Indication) or sleep indication (ie Go-to-sleep Indication).
  • transmission start indication ie Transmission Start Indication
  • PDCCH monitoring start indication ie PDCCH Monitoring Start Indication
  • WUS Wake Up Signal
  • the UE Before receiving the PDCCH channel or Transmission Start Indication or PDCCH Monitoring Start Indication or WUS, the UE applies a smaller On-Duration, such as min ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ , and the smaller On-Duration can be, for example, the first PDCCH monitoring period;
  • UE After receiving PDCCH channel or Transmission Start Indication or PDCCH Monitoring Start Indication or WUS until receiving Transmission End Indication, PDCCH Monitoring End Indication or Go-to-sleep Indication, UE applies a larger On-Duration, such as max ⁇ DRX-OnDurationTimer1 , DRX-OnDurationTimer2 ⁇ , the larger On-Duration may be, for example, the first PDCCH monitoring period.
  • a larger On-Duration such as max ⁇ DRX-OnDurationTimer1 , DRX-OnDurationTimer2 ⁇
  • the larger On-Duration may be, for example, the first PDCCH monitoring period.
  • the PDCCH is monitored during the first PDCCH monitoring period. If the PDCCH is detected or the data is successfully received or the PDCCH corresponding to the PDSCH is detected, the PDCCH is monitored during the first PDCCH monitoring period and the second PDCCH monitoring period, or, during the second PDCCH The PDCCH is monitored during the monitoring period.
  • the parameters of the first PDCCH search space are used for PDCCH monitoring (for example, the PDCCH monitoring interval of the first PDCCH search space, and the PDCCH continuous monitoring duration of the first PDCCH search space );
  • the parameters of the second PDCCH search space are used for PDCCH monitoring (such as the PDCCH monitoring interval of the second PDCCH search space and the PDCCH continuous monitoring duration of the second PDCCH search space).
  • FIG. 12 is a schematic diagram of another DRX configuration mode provided by an embodiment.
  • FIG. 12 illustrates the business mode of the quasi-periodic service with uncertain arrival time (large jitter range) and the corresponding DRX configuration, which can be regarded as a modified embodiment of FIG. 11 .
  • the network configures the DRX cycle and two lengths of PDCCH monitoring period (ie On-Duration), such as DRX-OnDurationTimer1 and DRX-OnDurationTimer2, the larger On-Duration covers the entire Jitter range, and the PDCCH monitoring period The descending step size (ie On-Duration Ramping-down Step).
  • the network sends the PDCCH channel or Transmission Start Indication or PDCCH Monitoring Start Indication or WUS; if the data transmission stops, it sends the PDCCH channel or Transmission End Indication or PDCCH Monitoring End Indication or Go-to-sleep Indication.
  • the UE Before receiving the PDCCH channel or Transmission Start Indication or PDCCH Monitoring Start Indication or WUS, the UE applies a smaller On-Duration, such as min ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ .
  • the UE applies a larger On-Duration, such as max ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ ; if successfully received
  • the data will reduce the length of On-Duration in the next DRX cycle according to the configured On-Duration Ramping-down Step, that is, if the data is successfully received in any DRX cycle, the next DRX cycle corresponding to the specified
  • the length is the length of the PDCCH monitoring period of the DRX cycle minus the down step.
  • the longest On-Duration will be resumed in the next DRX cycle, that is, the next DRX of the DRX cycle
  • the specified length corresponding to the period is restored to the larger of the two lengths, such as max ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ .
  • the UE applies a smaller On-Duration, such as min ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ .
  • the UE reduces the On-Duration length according to the configured descending step size, and the minimum length cannot be lower than the configured min ⁇ DRX-OnDurationTimer1, DRX-OnDurationTimer2 ⁇ , that is, the specified length corresponding to each DRX cycle is greater than or equal to the smaller of the two lengths length.
  • the DRX cycle is configured as 16ms, and the two lengths of On-Duration are 2ms and 8ms respectively, wherein 8ms can cover the jitter range, and the On-Duration decrease step is configured as 2ms.
  • This embodiment is a resource configuration for a PDCCH search space with a non-integer period.
  • the UE monitors PDCCH according to the PDCCH search space (ie Search Space).
  • the PDCCH search space can currently use the following parameters. Configuration (similar to the configuration of the DRX cycle), including: monitoring cycle (in slots), the start offset position of the monitoring cycle (in slots), monitoring duration (in slots) and the number of symbols monitored in each slot (in symbol units).
  • monitoring period can only take several discrete integer values.
  • monitoring slot period and offset i.e. Monitoring Slot Periodicity And Offset
  • CHOICE selects sl1280 100, it means that the period of the monitoring time slot is 1280slot, and the value range of the offset of the monitoring time slot is 100.
  • the value of the offset of the PDCCH monitoring time slot is related to the value of the PDCCH monitoring period.
  • the monitoring period can only take several discrete values, such as: sl1, sl2, sl4, sl5, sl8, sl10, sl16..., sl1280, sl2560.
  • the service period is not an integer multiple of the monitoring period (slot)
  • the service period is not within the value range of the PDCCH monitoring period, or the On-Duration length of PDCCH monitoring in the DRX period (that is, the end time of PDCCH monitoring-the start of PDCCH monitoring time) is not an integer multiple of the monitoring period (slot), or when the connected mode DRX is not configured
  • two solutions are two solutions:
  • the UE In the case of connected mode DRX cycle configuration, during the PDCCH monitoring period (ie On-Duration) in the DRX cycle, the UE starts to monitor the PDCCH from the beginning of the first PDCCH search space that appears; and only monitors the PDCCH search The start position of the space falls on the PDCCH during the On-Duration period in the DRX cycle.
  • PDCCH monitoring period ie On-Duration
  • the PDCCH search space does not need to be monitored; if the PDCCH search space The start position of the PDCCH search space falls within the On-Duration, even if the PDCCH monitoring timing of the PDCCH search space falls outside the On-Duration of the DRX cycle, the PDCCH search space needs to be monitored.
  • Fig. 13 is a schematic diagram of another DRX configuration mode provided by an embodiment.
  • the base station configures for the UE: the start time of the PDCCH search space (that is, the PDCCH Search Space Start Time), the duration of the PDCCH monitoring (that is, the PDCCH monitoring period Duration) and the period of the PDCCH search space;
  • the start time of the PDCCH search space can be configured through an absolute timing, or based on a relative time offset (namely Offset) of a certain timing.
  • the start time of the PDCCH search space can be configured through an absolute timing (SFN, subframe and/or slot); or a relative time offset (ie Time Offset) based on an absolute timing (a certain SFN, subframe and/or slot) Characterization, specifically: SFN, subframe and/or slot may be the radio frame, subframe and/or time slot of the first transmission of the RRC message configuring the PDCCH search space.
  • the time offset ie Time Offset is the time interval from the reference SFN, subframe and/or slot to the start time of the PDCCH search space.
  • the period of the PDCCH search space configured by the base station for the UE can be one-to-one corresponding to the service mode of the UE; at this time, the value range of the required service period is completely consistent with the value range of the PDCCH search space period, for example: PDCCH search space period
  • the period of is in units of hertz (Hz), frame per second (Fps), ms, or us, and can be a period represented by any integer value within the value range.
  • the value range of the PDCCH search space period is not constrained by a SFN period (an integer factor of 10240ms).
  • the UE can calculate the start time of the next PDCCH search space period through the timer (the end time of the previous PDCCH search space period is the start time of the next PDCCH search space period).
  • the start position of the Nth PDCCH search space period Floor(the start position of the first PDCCH search space period+(N-1)*Period).
  • Floor represents the lower integer
  • N represents the Nth DRX cycle
  • Period represents the service cycle or the cycle length of the PDCCH search space, which must be converted into the basic unit of the PDCCH search space cycle length (such as ms, slot or symbol) during calculation.
  • the start position of the Nth PDCCH search space period can also be calculated as follows:
  • the start position of the Nth PDCCH search space period Ceil (the start position+(N-1)*Period of the first PDCCH search space period);
  • the start position of the Nth PDCCH search space period Round(the start position+(N-1)*Period of the first PDCCH search space period);
  • Ceil is rounded up; Round is rounded to the nearest integer.
  • the start time of the Nth PDCCH search space the start time of the first DRX cycle + Floor((N-1)*Period), that is, the start time of the Nth PDCCH search space period can be the start time of the first PDCCH search space period The sum after rounding down with the length of N-1 business cycles;
  • the start time of the Nth PDCCH search space period the start time of the first PDCCH search space period + Ceil((N-1)*Period), that is, the start time of the Nth PDCCH search space period can be the first PDCCH search space period The sum of the start time of and the length of N-1 business cycles rounded up.
  • the start time of the Nth PDCCH search space period the start time of the first PDCCH search space period + Round((N-1)*Period), that is, the start time of the Nth PDCCH search space period can be the first PDCCH search space period The sum of the integer periods of the PDCCH search space whose start time is closest to the length of N-1 service periods.
  • the unit of the PDCCH search space period may be: ms, frame, subfrmae, slot, or symbol. That is, the service period is first converted into a unit of the PDCCH search space period, and then rounded down, up, or rounded to the start position of the PDCCH search space period unit.
  • the service occurrence frequency is represented by Hz or fps
  • it is converted into the corresponding PDCCH search space period through the inverse.
  • Fig. 14 is a schematic structural diagram of a configuration device provided by an embodiment.
  • the configuration device includes: a business information acquisition module 310 and a configuration information sending module 320;
  • the business information acquisition module 310 is configured to acquire business information, the business information includes a business cycle, a possible start time of business arrival and an end time of possible business arrival;
  • the configuration information sending module 320 is configured to send configuration information related to PDCCH monitoring according to the service information, and the configuration information is used to indicate the monitoring timing of the physical downlink control channel PDCCH.
  • the configuration device of this embodiment indicates the monitoring timing of the PDCCH according to the configuration of the service information, which can not be limited by the service cycle, improves the flexibility of monitoring, and realizes the business with uncertain or long-period data packet transmission timing and the service cycle Energy saving for terminals that are not integer factors of 10240ms.
  • the configuration information is DRX configuration information; the configuration information is used to indicate the start time of PDCCH monitoring, the end time of PDCCH monitoring and the length of DRX cycle.
  • the start time of PDCCH monitoring is indicated by a first specified position and a first time offset, wherein the first specified position includes a radio frame or a subframe where an RRC message of configuration information or a MAC control element CE is first transmitted And/or time slots, or radio frames, subframes and/or time slots specified by the first designated position; the first time offset includes a time interval from the first designated position to the start time of PDCCH monitoring;
  • the end time of PDCCH monitoring is indicated according to the second specified position and the second time offset, wherein the second specified position includes the first specified position, or the start time of PDCCHPDCCH monitoring; the second time offset is from the second specified position Time interval to end time of PDCCH monitoring.
  • the device also includes:
  • the configuration module is configured to configure periodic BSR resources or SR indication resources within the monitoring period; or determine the effective timing of periodic BSR resources or SR indication resources based on the PDCCH monitoring period; or indicate periodic BSR resources or SR through configuration information
  • the indicated effective time period, the PDCCH monitoring period is a predefined time period after receiving BSR or SR;
  • the scheduling module is configured to perform uplink PUSCH resource scheduling for bearing user plane data when a BSR or SR is received;
  • the periodic BSR resources or SR indication resources include periodic CG resources, periodic non-contention PRACH resources and/or uplink physical signals used to indicate allocation of uplink grant resources.
  • the configuration information is used to indicate the start time of PDCCH monitoring and the length of the DRX cycle; the configuration information is also used to indicate the end time of PDCCH monitoring, or the PDCCH monitoring period or DRX inactivation timing information.
  • the configuration information is used to indicate the start time of PDCCH monitoring, DRX inactivation timing information and DRX cycle length.
  • the configuration information includes multiple groups of DRX configurations, each group of DRX configurations includes a DRX cycle length and a corresponding start offset; the timing of PDCCH monitoring is a union of PDCCH monitoring timings in each DRX configuration.
  • the configuration information includes multiple sets of DRX configurations, and each set of DRX configurations includes a start time of PDCCH monitoring, an end time of PDCCH monitoring, and a service period.
  • the configuration information includes the DRX cycle and the configuration information of multiple PDCCH monitoring periods included in the DRX cycle; the configuration information of the multiple PDCCH monitoring periods includes: the length of each PDCCH monitoring period, the number of PDCCH monitoring periods, and /or the starting position of each PDCCH monitoring period.
  • the configuration information includes multiple groups of DRX configurations, and each group of DRX configurations corresponds to a DRX inactivity timer.
  • the configuration information includes a DRX cycle and a PDCCH monitoring period of two lengths.
  • the configuration information includes a DRX cycle, PDCCH monitoring periods of two lengths, and descending steps of the PDCCH monitoring periods.
  • the device also includes:
  • the first sending module is configured to send a PDCCH channel or a transmission start indication or a PDCCH monitoring start indication or a wake-up signal when starting to transmit data;
  • the second sending module is configured to send a transmission end indication or a PDCCH monitoring end indication or a dormancy indication when the data transmission is stopped.
  • the configuration information is the PDCCH search space configured by the following parameters: the start time of the PDCCH search space, the PDCCH monitoring period, and the period of the PDCCH search space.
  • the business information acquisition module 310 specifically includes:
  • the first obtaining unit is configured to obtain service information according to the QoS parameters transmitted by the core network; or,
  • the second obtaining unit is configured to obtain service information according to the auxiliary information of the terminal, the uplink RRC message and/or the uplink MAC CE structure.
  • Fig. 15 is a schematic structural diagram of a channel monitoring device provided by an embodiment. As shown in FIG. 15 , the channel monitoring device includes: a configuration information receiving module 410 and a monitoring module 420;
  • the configuration information receiving module 410 is configured to receive configuration information related to PDCCH monitoring, where the configuration information is used to indicate the timing of PDCCH monitoring.
  • the monitoring module 420 is configured to monitor the PDCCH according to the configuration information.
  • the channel monitoring device of this embodiment monitors the PDCCH according to the configuration information that can indicate the monitoring timing of the PDCCH, so that it is not limited by the service cycle, improves the flexibility of monitoring, and realizes services with uncertain or long-period data packet transmission timing. , and the energy saving of the terminal whose service period is not an integer factor of 10240ms.
  • the configuration information is DRX configuration information; the configuration information is used to indicate the start time of PDCCH monitoring, the end time of PDCCH monitoring, and the length of the DRX cycle;
  • the monitoring module 420 specifically includes:
  • the first monitoring unit is configured to monitor the PDCCH in a specified time interval or monitor the PDCCH according to the first PDCCH search space in each DRX cycle, and not monitor the PDCCH in a non-specified time interval or monitor the PDCCH according to the second PDCCH search space, or , in each DRX cycle, start monitoring PDCCH after sending BSR or SR; wherein, the specified time interval includes from the start time of PDCCH monitoring to the completion of data packet transmission, or from the start time of PDCCH monitoring to the end time of PDCCH monitoring, Or, the time from sending the BSR or SR to the completion of data packet transmission, or from sending the BSR or SR to the end time of PDCCH monitoring.
  • the start time of the Nth DRX cycle is one of the following:
  • the configuration information is used to indicate the start time of PDCCH monitoring and the length of the DRX cycle; the configuration information is also used to indicate the end time of PDCCH monitoring, or the PDCCH monitoring period or DRX inactivation timing information.
  • the monitoring module 420 specifically further includes:
  • the second monitoring unit is configured to start monitoring the PDCCH from the start time of the PDCCH monitoring in each DRX cycle, and stop monitoring the PDCCH until any of the following conditions is met:
  • the PDCCH is not monitored during the timing of the DRX inactive timer, and the DRX inactive timer expires;
  • the end time of PDCCH monitoring is up and no PDCCH is monitored.
  • the configuration information is used to indicate the start time of PDCCH monitoring, DRX inactivation timing information and DRX cycle length.
  • the device also includes:
  • the start module is set to start the DRX inactivation timer after receiving or feeding back the HARQ ACK if the PDCCH is monitored in each DRX cycle;
  • the restart module is set to monitor the PDCCH during the timing of the DRX inactive timer, then restart the DRX inactive timer after receiving or feeding back the HARQ ACK;
  • the stop module is configured to stop monitoring the PDCCH after the DRX inactive timer expires if no PDCCH is monitored during the timing of the DRX inactive timer.
  • the configuration information includes multiple sets of DRX configurations
  • the monitoring module 420 specifically also includes:
  • the sixth monitoring unit is configured to monitor the PDCCH at the PDCCH monitoring occasion included in each DRX configuration.
  • the configuration information includes configuration information of the first DRX cycle and configuration information of the second DRX cycle, wherein the first DRX cycle includes multiple second DRX cycles;
  • the monitoring module 420 specifically also includes:
  • the seventh monitoring unit is set to, in each first DRX cycle, for the overlapping area of the PDCCH monitoring period included in the first DRX cycle and the second DRX cycle, from the start timing of the earlier PDCCH monitoring period to the end Monitor the PDCCH at the end of the later PDCCH monitoring period;
  • the eighth monitoring unit is configured to monitor the PDCCH according to the PDCCH monitoring period included in the second DRX cycle for the non-overlapping area.
  • the configuration information includes a DRX cycle and a first PDCCH monitoring period and a second PDCCH monitoring period;
  • the monitoring module 420 specifically also includes:
  • the ninth monitoring unit is configured to monitor the PDCCH during the first PDCCH monitoring period before receiving the PDCCH channel or the transmission start indication or the PDCCH monitoring start indication or the wake-up signal;
  • the tenth monitoring unit is configured to monitor the PDCCH in the second PDCCH monitoring period after receiving the PDCCH channel or the transmission start indication or the PDCCH monitoring start indication or the wake-up signal until receiving the transmission end indication or the PDCCH monitoring end indication or the dormancy indication .
  • the monitoring module 420 may be configured to: monitor the PDCCH on the first PDCCH monitoring period before receiving the transmission start indication or the PDCCH monitoring start indication or the wake-up signal, and after receiving the transmission start indication or the PDCCH monitoring start indication or the wake-up signal, monitoring the PDCCH over a first PDCCH monitoring period and a second PDCCH monitoring period;
  • the monitoring module 420 may be configured to: monitor the PDCCH in the first PDCCH monitoring period in the first DRX cycle after receiving the transmission start indication or the PDCCH monitoring start indication or the wake-up signal, and monitor the PDCCH in the first DRX cycle except the first DRX cycle monitor the PDCCH on the second PDCCH monitoring period in each DRX cycle;
  • the monitoring module 420 may be configured to: monitor the PDCCH in the first PDCCH monitoring period in the first DRX cycle, and monitor the PDCCH in the second PDCCH monitoring period in the second DRX cycle;
  • the monitoring module 420 may be configured to: monitor the PDCCH during the first PDCCH monitoring period and the second PDCCH monitoring period, or monitor the PDCCH during the second PDCCH monitoring period if the data is successfully received within a DRX cycle;
  • the monitoring module 420 can be used to: monitor the PDCCH during the first PDCCH monitoring period, if the PDCCH is detected or the data is successfully received or the PDCCH corresponding to the PDSCH is detected, then monitor the PDCCH during the first PDCCH monitoring period and the second PDCCH monitoring period, Or, monitor the PDCCH during the second PDCCH monitoring period;
  • the first DRX cycle includes one or more DRX cycles
  • the second DRX cycle includes one or more DRX cycles.
  • the configuration information includes the DRX cycle, the PDCCH monitoring period of two lengths, and the descending step of the PDCCH monitoring period;
  • the monitoring module 420 specifically also includes:
  • the eleventh monitoring unit is configured to monitor the PDCCH according to the smaller PDCCH monitoring period of the two lengths before receiving the PDCCH channel or the transmission start indication or the PDCCH monitoring start indication or the wake-up signal;
  • the twelfth monitoring unit is configured to monitor the PDCCH according to the longer PDCCH monitoring period of the two lengths in the first DRX cycle after receiving the PDCCH channel or the transmission start indication or the PDCCH monitoring start indication or the wake-up signal, and in In each DRX cycle except the first DRX cycle, use the PDCCH monitoring period of the corresponding specified length to monitor the PDCCH;
  • the thirteenth monitoring unit is configured to monitor the PDCCH according to the PDCCH monitoring period with a smaller length if an indication of data transmission stop is received;
  • the specified length corresponding to the next DRX cycle of the DRX cycle is the length of the PDCCH monitoring period of the DRX cycle minus the down step; After successfully receiving data and not receiving an instruction to stop data transmission, the specified length corresponding to the next DRX cycle of the DRX cycle is restored to the larger length of the two lengths; wherein, the specified length corresponding to each DRX cycle is greater than or equal to The smaller of the two lengths.
  • the monitoring module 420 specifically further includes:
  • the fourteenth monitoring unit is configured to start monitoring the PDCCH that satisfies the conditions from the start position of the first PDCCH search space within the PDCCH monitoring period in each DRX cycle, and the PDCCH that meets the conditions includes the start position of the search space that falls within the corresponding The PDCCH in the PDCCH monitoring period in the DRX cycle.
  • the device also includes:
  • the determining module is configured to determine the PDCCH search space according to the following parameters: the start time of the PDCCH search space, the PDCCH monitoring period and the period of the PDCCH search space.
  • the channel monitoring device proposed in this embodiment and the channel monitoring method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes the channel monitoring method Same beneficial effect.
  • FIG. 16 is a schematic diagram of the hardware structure of a communication node provided in an embodiment.
  • the communication node provided in the present application including a memory 520, a processor 510, and a computer program stored in the memory and operable on the processor.
  • the processor 510 executes the program, the above configuration method or channel monitoring method is implemented.
  • the communication node may also include a memory 520; there may be one or more processors 510 in the communication node, and one processor 510 is taken as an example in FIG. 16; the memory 520 is used to store one or more programs; the one or more The program is executed by the one or more processors 510, so that the one or more processors 510 implement the configuration method or the channel monitoring method as described in the embodiment of the present application.
  • the communication node further includes: a communication device 530 , an input device 540 and an output device 550 .
  • the processor 510, the memory 520, the communication device 530, the input device 540, and the output device 550 in the communication node may be connected through a bus or in other ways. In FIG. 16, connection through a bus is taken as an example.
  • the input device 540 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the communication node.
  • the output device 550 may include a display device such as a display screen.
  • Communications device 530 may include a receiver and a transmitter.
  • the communication device 530 is configured to perform information sending and receiving communication according to the control of the processor 510 .
  • the memory 520 can be configured to store software programs, computer-executable programs and modules, such as the program instructions/modules corresponding to the configuration method described in the embodiment of the present application (for example, the business information acquisition in the configuration device module 310 and configuration information sending module 320); or program instructions/modules corresponding to the channel monitoring method described in the embodiment of the present application (for example, the configuration information receiving module 410 and the monitoring module 420 in the channel monitoring device).
  • the memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the communication node, and the like.
  • the memory 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • memory 520 may further include memory located remotely from processor 510, and these remote memories may be connected to communication nodes through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • An embodiment of the present application further provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the configuration method or the channel monitoring method described in any one of the embodiments of the present application is implemented.
  • the configuration method includes: obtaining service information, the service information including the service period, the start time of the possible arrival of the service, and the end time of the possible arrival of the service; sending configuration information related to PDCCH monitoring according to the service information, and the configuration information is used It is used to indicate the monitoring timing of the PDCCH.
  • the channel monitoring method includes: receiving configuration information related to PDCCH monitoring, where the configuration information is used to indicate the monitoring timing of the PDCCH; and monitoring the PDCCH according to the configuration information.
  • the computer storage medium in the embodiments of the present application may use any combination of one or more computer-readable media.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more conductors, portable computer disks, hard disks, Random Access Memory (RAM), read-only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination of the above .
  • a computer readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • any appropriate medium including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • Computer program codes for performing the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional A procedural programming language, such as the "C" language or similar programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through the Internet using an Internet service provider). connect).
  • LAN local area network
  • WAN wide area network
  • connect such as AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Embodiments of the present application may be realized by a data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.
  • Computer-readable media may include non-transitory storage media.
  • Data processors may be any Types, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic devices (Field-Programmable Gate Array , FPGA) and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种配置方法、信道监控方法、通信节点及存储介质。该方法获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间(110)；根据所述业务信息发送物理下行控制信道PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机(120)。

Description

配置方法、信道监控方法、通信节点及存储介质
相关申请的交叉引用
本申请基于申请号为202111673935.2、申请日为2021年12月31日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及无线通信网络技术领域，例如涉及一种配置方法、信道监控方法、通信节点及存储介质。
背景技术
在无线通信系统中，用于终端(User Equipment，UE)节能的配置授权(Configured Grant，CG)资源和半静态调度(Semi-Persistent Scheduling，SPS)策略只适用于传输时机确定(数据包传输开始时机和周期确定)的小周期业务(传输间隔通常小于或等于640ms)；对于数据包传输时机不确定或大周期的业务，一般采用连接态下的非连续接收(Discontinuous Reception in RRC_CONNECTED state，C-DRX)机制，而目前的C-DRX中，DRX周期的取值范围只能是以ms为单位，且只能取离散的几个值，如果业务周期不是ms的整数倍或者周期不在DRX周期的取值范围内，则C-DRX机制无法适用；如果业务周期较大(大于10240ms)，则C-DRX机制也无法使用。
此外，对于DRX，在不同无线帧周期内，DRX周期的开始位置是固定的，但对于业务周期不是10240ms的整数因子的业务，不同无线帧周期内的DRX周期的开始位置可能不同，因此目前的DRX机制也无法适用于业务周期不是10240ms的整数因子的场景。
PDCCH搜索空间的配置也存在C-DRX配置类似问题。
发明内容
本申请提供一种配置方法、信道监控方法、通信节点及存储介质。
本申请实施例提供一种配置方法，包括：获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间；根据所述业务信息发送物理下行控制信道(Physical Downlink Control Channel，PDCCH)监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。
本申请实施例还提供了一种信道监控方法，包括：接收PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机；根据所述配置信息监控PDCCH。
本申请实施例还提供了一种通信节点，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现上述的配置方法或信道监控方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该程序被处理器执行时实现上述的配置方法或信道监控方法。
附图说明
图1为一实施例提供的一种配置方法的流程图；
图2为一实施例提供的一种信道监控方法的流程图；
图3为一实施例提供的一种获取业务信息的示意图；
图4为一实施例提供的一种DRX配置方式的示意图；
图5为一实施例提供的另一种DRX配置方式的示意图；
图6为一实施例提供的又一种DRX配置方式的示意图；
图7为一实施例提供的又一种DRX配置方式的示意图；
图8为一实施例提供的又一种DRX配置方式的示意图；
图9为一实施例提供的又一种DRX配置方式的示意图；
图10为一实施例提供的又一种DRX配置方式的示意图；
图11为一实施例提供的又一种DRX配置方式的示意图；
图12为一实施例提供的又一种DRX配置方式的示意图；
图13为一实施例提供的又一种DRX配置方式的示意图；
图14为一实施例提供的一种配置装置的结构示意图；
图15为一实施例提供的一种信道监控装置的结构示意图；
图16为一实施例提供的一种通信节点的硬件结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
图1为一实施例提供的一种配置方法的流程图，如图1所示，该方法可应用于第一通信节点，第一通信节点可以为基站侧或网络侧节点。本实施例提供的方法包括步骤110和步骤120。
在步骤110中，获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间。
在步骤120中，根据所述业务信息发送PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。
本实施例中，第一通信节点获取业务信息，其中业务信息可以包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间；在此基础上，第一通信节点根据所获取的业务信息发送PDCCH监控相关的配置信息至UE侧，其中配置信息可以用于指示PDCCH的监控时机。
本实施例中，通过根据业务信息配置来指示PDCCH的监控时机，可以不受业务周期的限制，提高监控的灵活性，实现对于数据包传输时机不确定或大周期的业务、以及业务周期不是10240ms的整数因子的终端的节能。
在一实施例中，配置信息为DRX的配置信息；配置信息用于指示PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度。
在一实施例中，PDCCH监控的开始时间通过第一指定位置和第一时间偏移量指示，其中，第一指定位置包括配置信息的无线资源控制(Radio Resource Control，RRC)消息或媒体接入控制(Medium Access Control，MAC)控制元素(Control Element，CE)首次传输的无线帧、子帧和/或时隙，或者所述第一指定位置为指定的无线帧、子帧和/或时隙；第一时间偏移量包括所述第一指定位置到PDCCH监控的开始时间的时间间隔；PDCCH监控的结束时间根据第二指定位置和第二时间偏移量指示，其中，第二指定位置包括所述第一指定位置，或者PDCCH监控的开始时间；第二时间偏移量包括从第二指定位置到PDCCH监控的结束时间的时间间隔。
在一实施例中，该方法还包括：在PDCCH监控时段内，配置周期性缓冲区状态上报(Buffer Status Report，BSR)资源或者调度请求(Scheduling Request，SR)指示资源；或者基于PDCCH的监控时段确定周期性BSR资源或者SR指示资源的有效时机；或者通过配置信息指示周期性BSR资源或者SR指示的有效时间段，PDCCH监控时段为接收到BSR或者SR后的预定义时间段；
该方法还包括：在接收到BSR或者SR的情况下进行承载用户面数据的上行物理上行共享信道(physical uplink shared channel，PUSCH)资源调度；其中，周期性BSR资源或者SR指示资源包括周期性CG资源、周期性非竞争物理随机接入信道(Physiacal Random Access Channel，PRACH)资源和/或用于指示分配承载用户面数据的上行授权资源的上行物理信号。
在一实施例中，该方法还包括：在业务可能到达的开始时间到业务可能到达的结束时间的时段内，配置周期性BSR资源或者SR指示资源；第二通信节点在发送BSR或者SR后开始监控PDCCH；其中，周期性BSR资源或者SR指示资源包括周期性CG资源、周期性非竞争PRACH资源和/或用于指示分配承载用户面数据的上行授权资源的上行物理信号。
在一实施例中，配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
在一实施例中，配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置包括DRX周期长度以及对应的起始偏移；监控PDCCH的时机为各DRX配置中PDCCH监控时机的并集。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置包括PDCCH监控的开始时间、PDCCH监控的结束时间以及业务周期。
在一实施例中，配置信息包括DRX周期和DRX周期内包含的多个PDCCH监控时段的配置信息；多个PDCCH监控时段的配置信息包括：各PDCCH监控时段的长度、PDCCH监控时段的个数和/或各PDCCH监控时段的起始位置。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置分别对应于一个DRX非激活定时器。
在一实施例中，配置信息包括DRX周期以及两种长度的PDCCH监控时段。
在一实施例中，配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长。
在一实施例中，该方法还包括：在开始传输数据的情况下，发送PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号；在数据传输停止的情况下，发送传输结束指示或者PDCCH监控结束指示或者休眠指示。
在一实施例中，配置信息为通过如下参数配置的PDCCH搜索空间：PDCCH搜索空间的开始时间、PDCCH监控时段和PDCCH搜索空间的周期。
在一实施例中，配置信息为通过如下参数配置的PDCCH搜索空间：PDCCH监控时段和PDCCH搜索空间的周期。其中，PDCCH搜索空间的开始时间为UE发送BSR或SR的时间，或者UE发送BSR或SR并向后推移预定义时间段的时机。
在一实施例中，获取业务信息包括：根据核心网传递的服务质量(Quality of Service，QoS)参数获取业务信息；或者，根据终端的辅助信息、上行RRC消息和/或上行MAC CE结构获取业务信息。
本申请实施例还提供一种信道监控方法。图2为一实施例提供的一种信道监控方法的流程图，如图2所示，该方法可应用于第二通信节点，第二通信节点可以为UE侧节点。本实施例提供的方法包括步骤210和步骤220。
在步骤210中，接收PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。
在步骤220中，根据所述配置信息监控PDCCH。
本实施例中，UE侧接收基站侧所发送的PDCCH监控相关的配置信息，其中该配置信息可以用于指示PDCCH的监控时机；在此基础上，UE侧可根据该配置信息监控PDCCH。
本实施例中，第二通信节点可根据配置信息所指示的PDCCH的监控时机来监控PDCCH，可以不受业务周期的限制，提高监控的灵活性，实现对于数据包传输时机不确定或大周期的业务、以及业务周期不是10240ms的整数因子的终端的节能。
在一实施例中，配置信息为DRX的配置信息；配置信息用于指示PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度；
根据配置信息监控PDCCH，包括：在每个DRX周期内，在指定时间区间内监控PDCCH或按照第一PDCCH搜索空间监控PDCCH，在非指定时间区间不监控PDCCH或按照第二PDCCH搜索空间监控PDCCH或者，在每个DRX周期内，在发送BSR或者SR后开始监控PDCCH；
其中，指定时间区间包括从PDCCH监控的开始时间到数据包传输完成，或者从PDCCH监控的开始时间到PDCCH监控的结束时间，或者，从发送BSR或者SR后到数据包传输完成，或者从发送BSR或者SR后到PDCCH监控的结束时间。
在一实施例中，第N个DRX周期的开始时间为以下之一：
第一个DRX周期的开始时间与N-1个业务周期向下取整的结果之和；
第一个DRX周期的开始时间与N-1个业务周期向上取整的结果之和；
第一个DRX周期的开始时间与最接近于N-1个业务周期的整数之和；
第一个DRX周期的开始时间与N-1个业务周期之和向下取整的结果；
第一个DRX周期的开始时间与N-1个业务周期之和向上取整的结果；
第一个DRX周期的开始时间与N-1个业务周期之和最接近的DRX整数周期位置。
在一实施例中，配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
在一实施例中，根据配置信息监控PDCCH，包括：在每个DRX周期内，从PDCCH监控的开始时间开始监控PDCCH，直至满足以下任一条件，停止监控PDCCH：在PDCCH监控的开始时间之后监控到PDCCH，并在收到或反馈混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)确认信息(ACKnowledge，ACK)后启动DRX非激活定时器；在DRX非激活定时器定时期间监控 到PDCCH，并在收到或反馈HARQ ACK后重新启动DRX非激活定时器；在DRX非激活定时器定时期间未监控到PDCCH，且DRX非激活定时器超时；PDCCH监控的结束时间到时且未监控到PDCCH。
在一实施例中，配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
在一实施例中，该方法还包括以下之一：在每个DRX周期内，
若监控到PDCCH，则在收到或反馈HARQ ACK后启动DRX非激活定时器；
在DRX非激活定时器定时期间监控到PDCCH，则在收到或反馈HARQ ACK后重新启动DRX非激活定时器；
在DRX非激活定时器定时期间未监控到PDCCH，则在DRX非激活定时器超时后停止监控PDCCH。
在一实施例中，配置信息包括多组DRX配置；
根据配置信息监控PDCCH，包括：在各DRX配置中包含的PDCCH监控时机监控PDCCH。
在一实施例中，配置信息包括第一DRX周期的配置信息和第二DRX周期的配置信息，其中，第一DRX周期内包括多个第二DRX周期；
根据配置信息监控PDCCH，包括：在每个第一DRX周期内，对于第一DRX周期和第二DRX周期内包含的PDCCH监控时段的重叠区域，从开始较早的PDCCH监控时段的开始时机，到结束较晚的PDCCH监控时段的结束时机监控PDCCH；对于非重叠区域，按照第二DRX周期内包含的PDCCH监控时段监控PDCCH。
在一实施例中，配置信息包括DRX周期以及第一PDCCH监控时段和第二PDCCH监控时段；
根据配置信息监控PDCCH，包括：
在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH；在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，直至接收到传输结束指示或者PDCCH监控结束指示或者休眠指示，在第二PDCCH监控时段上监控PDCCH；
或者，根据配置信息监控PDCCH，包括：
在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH；在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH；
或者，根据配置信息监控PDCCH，包括：
在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内在第一PDCCH监控时段上监控PDCCH，在除所述第一个DRX周期以外的每个DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，根据配置信息监控PDCCH，包括：
在第一DRX周期内在第一PDCCH监控时段上监控PDCCH，在第二DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，根据配置信息监控PDCCH，包括：
若在一个DRX周期内成功接收数据，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH；
或者，根据配置信息监控PDCCH，包括：
在第一PDCCH监控时段监控PDCCH，若检测到PDCCH或成功接收数据或检测到PDSCH对应的PDCCH，则在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH；
其中，第一DRX周期包括一个或多个DRX周期，第二DRX周期包括一个或多个DRX周期。
在一实施例中，配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长；
根据配置信息监控PDCCH，包括：在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，根据两种长度中长度较小的PDCCH监控时段监控PDCCH；在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内根据两种长度中长度较大的PDCCH监控时段监控PDCCH，并在除第一个DRX周期以外的每个DRX 周期内使用对应的指定长度的PDCCH监控时段监控PDCCH；若接收到数据传输停止的指示，则根据所长度较小的PDCCH监控时段监控PDCCH；其中，若在任意一个DRX周期内成功接收数据，则该DRX周期的下一个DRX周期对应的指定长度为该DRX周期的PDCCH监控时段的长度减去下降步长；若在任意一个DRX周期内未成功接收到数据且没有收到数据传输停止的指示，则该DRX周期的下一个DRX周期对应的指定长度恢复为两种长度中较大的长度；其中，各DRX周期对应的指定长度大于或等于两种长度中较小的长度。
在一实施例中，根据配置信息监控PDCCH，包括：在每个DRX周期内的PDCCH监控时段内，从第一个PDCCH搜索空间的开始位置开始监控满足条件的PDCCH，满足条件的PDCCH包括搜索空间的开始位置落在相应的DRX周期内的PDCCH监控时段内的PDCCH。
在一实施例中，该方法还包括：根据如下参数确定PDCCH搜索空间：PDCCH搜索空间的开始时间、PDCCH监控时段和PDCCH搜索空间的周期。
以下通过不同实施例对上述的配置方法和信道监控方法进行说明。
实施例一
图3为一实施例提供的一种获取业务信息的示意图。基站获取业务信息可以包括：根据核心网传递的QoS参数获取业务信息；或者，根据终端的辅助信息、上行RRC消息和/或上行MAC CE结构获取业务信息。其中业务信息可以包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间。如图3所示，以到达时间不确定(抖动范围较大)的周期性业务的业务模式说明，核心网或UE通知基站业务周期(即Period)、业务可能到达的开始时间(即Burst Arrival Start Time)以及业务可能到达的结束时间(即Burst Arrival End Time)。其中，业务可能到达的开始时间及业务可能到达的结束时间也可以通过业务可能到达的时间(即Burst Arrival Time)和业务到达时间的波动范围(即Burst Arrival Time Spread，或者Burst Arrival Time Jitter)来表征。比如：
业务可能到达的开始时间＝业务可能到达的时间-业务到达时间的波动范围；
业务可能到达的结束时间＝业务可能到达的时间+业务到达时间的波动范围。
或者，
业务可能到达的开始时间＝业务可能到达的时间-业务到达时间的波动范围/2；
业务可能到达的结束时间＝业务可能到达的时间+业务到达时间的波动范围/2。
图4为一实施例提供的一种DRX配置方式的示意图。如图4所示，以基于核心网或UE提供的如图3所示的业务模式，基站给UE配置的连接模式DRX周期为例。配置信息为DRX的配置信息，基站给RRC连接模式的UE配置：PDCCH监控的开始时间(即PDCCH Monitoring Start Time)、PDCCH监控的结束时间(即PDCCH Monitoring End Time)、DRX周期长度；UE在一个DRX周期内，从PDCCH监控的开始时间到上/下行数据包传输完成这个时间区间(即指定时间区间)内，或者从PDCCH监控的开始时间到PDCCH监控的结束时间这个时间区间(即指定时间区间)内(其中哪一个时间先到以哪一个时间为准，如上/下行数据包传输完成时间较PDCCH监控的结束时间先到，就以上/下行数据包传输完成对应的指定时间区间为准)，UE需要在指定时间区间内监控PDCCH或按照第一PDCCH搜索空间(以较小的PDCCH监控周期)监控PDCCH；此外，UE在非指定时间区间内无需监控PDCCH或按照第二PDCCH搜索空间(以较大的PDCCH监控周期)监控PDCCH。
其中：
PDCCH监控的开始时间对应业务可能到达的开始时间；
PDCCH监控的结束时间对应业务可能到达的结束时间向后偏移一个时间量(即Time Offset)；时间量是考虑业务调度的重传时延及HARQ ACK/NACK时延，其中NACK为非确认信息(即Non ACKnowledge)；
DRX周期对应业务的周期。
其中，基站给UE配置的DRX周期可以与UE的业务模式一一对应，此时，需要业务的周期取值范围和DRX周期的取值范围完全一致，比如：DRX周期的周期以赫兹(Hz)、帧每秒(fps)、ms(毫秒)、或者us(微秒)为单位，且可以是取值范围内的任意整数值表征的周期。
考虑到与业务模式匹配，且PDCCH监控的开始时间和结束时间由基站显式配置(而不是计算得到)，DRX周期的取值范围不受一个系统帧号(System Frame Number，SFN)周期(即10240ms)的约束，也就是可以大于一个SFN周期。UE可以通过定时器来计算下一个DRX周期的开始时间(上一个DRX周期的结束时间即为下一个DRX周期的开始时间)。
如果业务周期不是1ms的整数倍，则第N个DRX周期开始时间＝Floor(第一个DRX周期的开 始时间+(N-1)*Period)，即第N个DRX周期的开始时间为第一个DRX周期的开始时间与N-1个业务周期之和向下取整的结果。其中：Floor可表示下取整，N可表示第N个DRX周期，Period可表示业务周期或者DRX周期长度，计算时要转换为DRX周期长度的基本单位(比如ms、slot或者symbol)。
第N个DRX周期开始时间也可以如下计算：
第N个DRX周期开始时间＝Ceil(第一个DRX周期开始时间+(N-1)*Period)，即第N个DRX周期开始时间可以为第一个DRX周期的开始时间与N-1个业务周期之和向上取整的结果；
或者，
第N个DRX周期开始时间＝Round(第一个DRX周期开始时间+(N-1)*Period)，即第N个DRX周期开始时间可以为第一个DRX周期的开始时间与N-1个业务周期之和最接近的DRX整数周期位置。
或者，
第N个DRX周期开始时间＝第一个DRX周期开始时间+Floor((N-1)*Period)，即第N个DRX周期开始时间可以为第一个DRX周期的开始时间与N-1个业务周期长度向下取整后的和；
或者，
第N个DRX周期开始时间＝第一个DRX周期开始时间+Ceil((N-1)*Period)，即第N个DRX周期开始时间可以为第一个DRX周期的开始时间与与N-1个业务周期长度向上取整后的和。
或者，
第N个DRX周期开始时间＝第一个DRX周期开始时间+Round((N-1)*Period)，即第N个DRX周期开始时间可以为第一个DRX周期的开始时间与N-1个业务周期长度最接近的DRX整数周期的和。
其中：Ceil为上取整；Round为四舍五入到最接近的整数。
此处DRX周期的周期单位ms也可以是帧(frame)、子帧(subframe)、时隙(slot)、或符号(symbol)。也就是先把业务周期转换为DRX周期的周期单位，再通过下取整、上取整，或者四舍五入到DRX周期的周期单位的开始时间。
如果业务发生频率用Hz或fps表征，则可通过倒数转换为对应的业务周期。比如x Hz对应的业务周期为(1/x)秒，然后在此基础上可以转换为ms、symbol或者slot。其中1ms＝1subframe，所以ms和subframe做单位是等价的。
相关方法也可以用在CG或SPS的配置策略中。比如在工业物联网(Industrial Internet of Things，IIoT)及扩展现实(Extended Reality，XR)等场景中，业务周期可能不是ms的整数倍。比如在IIoT中，常常以Hz表达业务发生频率，x Hz的倒数(1/x Hz)即为对应的业务周期；在XR等图像处理中，常以fps(即frame per second)表达业务发生频率，x fps的倒数(1/x fps)即为对应的业务周期。60Hz或者10fps对应16.667ms的周期，120Hz或者8.333fps对应8.333ms的周期。这样的非整数周期是无法与CG或SPS的周期匹配的。此时可以以业务的实际周期(Hz、fps或非整数值)配置CG或SPS的周期。如果业务周期不是1ms的整数倍，则第N个CG或SPS的开始时间＝Floor(第一CG或SPS的开始时间+(N-1)*Period)，第N个CG或SPS的开始时间＝Ceil(第一CG或SPS的开始时间+(N-1)*Period)，或者第N个CG或SPS的开始时间＝Round(第一CG或SPS的开始时间+Round((N-1)*period)。其中：Floor表示下取整，Ceil表示上取整，Round表示四舍五入到最接近的整数。N表示第N个DRX周期，Period表示业务的实际周期，计算时要转换为CG或SPS周期的基本单位(比如ms、slot或者symbol)。
PDCCH监控的开始时间可以通过相对于第一指定位置(如某个SFN、subframe和/或slot)和第一时间偏移量(如时间偏移量2，即TimeOffset2)来表征，具体地：SFN、subframe和/或slot为配置该C-DRX的RRC消息或MAC CE的首次传输的无线帧、子帧和/或时隙，或者为配置该C-DRX的RRC消息或MAC CE指定的无线帧、子帧和/或时隙。时间偏移量2(即TimeOffset2)为从第一指定位置到PDCCH监控开始时间的时间间隔。
PDCCH监控的结束时间可以通过相对于第二指定位置(如某个SFN、subframe和/或slot)和第二时间偏移量(如时间偏移量3，即TimeOffset3)来表征，具体地：第二指定位置包括所述第一指定位置，或者PDCCH监控的开始时间。时间偏移量3(即TimeOffset3)为从第二指定位置到PDCCH监控的结束时间的时间间隔(即On-Duration)。
在业务可能到达的开始时间与业务可能到达的结束时间的On-Duration期间(即PDCCH监控时 段)，基站给UE配置周期性BSR资源或者SR指示资源，以便UE及时请求上行授权(UpLink Grant，UL Grant)；基站收到BSR或者SR即进行承载用户面数据的上行PUSCH资源调度，降低上行传输时延。也就是On-Duration期间的SR指示资源只适用于消息大小(即Message Size)固定的场景，基站收到SR即可知道需要分配的UL Grant资源大小，而无需UE再上报BSR。其中，周期性BSR资源或者SR指示资源可以包括周期性CG资源、周期性非竞争PRACH资源、或者可用于指示基站分配UL Grant资源的上行物理信号。
或者，配置信息中包括周期性BSR资源或者SR指示的有效时间段，PDCCH监控时段为接收到BSR或者SR后的预定义时间段。
图5为一实施例提供的另一种DRX配置方式的示意图。如图5所示，以基于核心网或UE提供的如图3所示的业务模式，基站给UE配置的连接模式DRX周期为例，配置信息为DRX的配置信息，基站给RRC连接模式的UE配置：周期性BSR或SR的有效时机、DRX周期长度；UE在一个DRX周期内，从发送BSR或SR后开始监控PDCCH。PDCCH监控的开始时间到上/下行数据包传输完成这个时间区间(即指定时间区间)内，UE需要在指定时间区间内监控PDCCH或按照第一PDCCH搜索空间(以较小的PDCCH监控周期)监控PDCCH；此外，UE在非指定时间区间内无需监控PDCCH或按照第二PDCCH搜索空间(以较大的PDCCH监控周期)监控PDCCH。DRX周期的计算与图4相同。
指定时间区间也可以为从发送BSR或者SR后到数据包传输完成，或者从发送BSR或者SR后到PDCCH监控的结束时间。
所述数据包传输完成指数据传输的HARQ ACK过程完成和/或RLC ACK过程完成，且也即收到了所述数据包传输的ACK确认，且没有紧接着的后续数据传输，或者本DRX周期内没有更多数据传输。
实施例二
图6为一实施例提供的又一种DRX配置方式的示意图。如图6所示，以到达时间不确定(抖动范围较大)，且数据包大小也不确定的周期性业务的连接模式DRX支持说明。基站给UE配置PDCCH监控的开始时间以及DRX周期长度，还配置PDCCH监控的结束时间或PDCCH监控时段(即On-Duration)或DRX非激活定时信息(即DRX-Inactivity Timer)。
在每个DRX周期内，UE从PDCCH监控的开始时间开始监控PDCCH，直至满足如下任一条件，UE停止PDCCH监控，直到下一DRX周期的开始(下一DRX周期的开始位置为上一DRX周期的开始位置(即PDCCH Monitoring Start Time)+DRX周期)：
PDCCH监控的开始时间可以为C-DRX的开始时间，可以为C-DRX内某个指定时机，或者C-DRX开始时间向后偏移预定义时间段的时机。其中：指定时机或预定义时间段偏移由标准预定义或者基站配置。
在PDCCH监控的开始时间之后监控到PDCCH，并在收到或反馈HARQ ACK后启动DRX非激活定时器(即DRX-Inactivity Timer)；
在DRX非激活定时器定时期间内监控到PDCCH，并在收到或反馈HARQ ACK后重新启动DRX非激活定时器；
在DRX非激活定时器定时期间内未监控到PDCCH，且DRX非激活定时器超时；
PDCCH监控的结束时间到时且未监控到PDCCH。
图7为一实施例提供的又一种DRX配置方式的示意图。如图7所示，以到达时间不确定(抖动范围较大)，且数据包大小也不确定的周期性业务的连接模式DRX支持说明。基站给UE配置PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度(其中没有显式的PDCCH监控的结束时间配置)。
UE从PDCCH监控的开始时间开始，在DRX周期内监控PDCCH，直到监控到PDCCH：
如果监控到PDCCH，则在收到或反馈HARQ ACK后启动DRX非激活定时器；
在DRX非激活定时器定时期间内监控到PDCCH，则在收到或反馈HARQ ACK后重新启动DRX非激活定时器；
在DRX非激活定时器定时期间内未监控到PDCCH，则在DRX非激活定时器超时后停止停止PDCCH监控，直到下一DRX周期开始(下一DRX周期的开始位置为上一DRX周期开始位置(即PDCCH Monitoring Start Time)+DRX周期)。
需要说明的是，图7可认为是图6的一个特例：相当于没有配置PDCCH监控的结束时间，也可 以理解为PDCCH监控的结束时间和DRX周期结束时间重叠。
实施例三
现有的DRX周期只能取值为几个离散的值，如下：
DRX短周期(即DRX-ShortCycle)，如{ms2,ms3,ms4,ms5,ms6,ms7,ms8,ms10,ms14,ms16,ms20,ms30,ms32,ms35,ms40,ms64,ms80,ms128,ms160,ms256,ms320,ms512,ms640,spare9,spare8,spare7,spare6,spare5,spare4,spare3,spare2,spare1}；
DRX长周期起始偏移(即DRX-LongCycleStartOffset)，如{ms10 INTEGER(0…9),ms20 INTEGER(0…19),ms32 INTEGER(0…31),ms40 INTEGER(0…39),ms60 INTEGER(0…59),ms64 INTEGER(0…63),ms70 INTEGER(0…69),ms80 INTEGER(0…79),ms128 INTEGER(0…127),ms160 INTEGER(0…159),ms256 INTEGER(0…255),ms320 INTEGER(0…319),ms512 INTEGER(0…511),ms640 INTEGER(0…639),ms1024 INTEGER(0…1023),ms1280 INTEGER(0…1279),ms2048 INTEGER(0…2047),ms2560 INTEGER(0…2559),ms5120 INTEGER(0…5119),ms10240 INTEGER(0…10239)}。其中，INTEGER可表示取整数。
如果想配置DRX周期＝15ms(即DRX周期长度为15ms)的DRX参数，目前的标准无法支持；除了采用实施例一和实施例二所述的方法外，还可以通过多个DRX周期来映射标准不支持的DRX周期取值。
比如：如果希望配置DRX周期＝15ms，对应的起始偏移(即StartOffset)＝1ms的DRX参数，则可以通过如下两个DRX参数配置来实现：
DRX配置1：DRX周期＝30ms，Start Offset＝1ms；
DRX配置2：DRX周期＝30ms，Start Offset＝16ms。
或者也可以通过如下四个DRX参数配置来实现：
DRX配置1：DRX周期＝30ms，Start Offset＝1ms；
DRX配置2：DRX周期＝30ms，Start Offset＝16ms；
DRX配置3：DRX周期＝30ms，Start Offset＝33ms；
DRX配置4：DRX周期＝30ms，Start Offset＝49ms。
需要说明的是，如果给UE配置了多个DRX配置，其中每个DRX配置可以包括DRX周期长度以及对应的起始偏移，则UE监控PDCCH的时机可以为多个DRX配置里的PDCCH监控时机的并集：也就是说只要有一个DRX配置需要监控PDCCH，UE就监控PDCCH。
图8为一实施例提供的又一种DRX配置方式的示意图。如图8所示，以采用两个DRX配置来映射一个较小的DRX周期进行示例说明。在图8中：DRX周期1长度＝DRX周期2长度＝30ms；DRX周期2的开始位置落在DRX周期1的中间位置。在此基础上，采用两个DRX周期长度＝30ms的DRX配置就能映射出一个DRX周期的PDCCH监控时机。
UE在各DRX配置中包含的PDCCH监控时机监控PDCCH。图8中：第一个On-Duration为DRX周期1的PDCCH监控时机；第二个On-Duration为DRX周期2的PDCCH监控时机；第三个On-Duration为DRX周期1的下一PDCCH监控时机；第四个On-Duration为DRX周期2的下一PDCCH监控时机；依此类推。
另外，多组DRX配置也可以用于非整数周期的DRX配置。比如，业务到达开始时间为0hh0mm0ss0ms，到达结束时间为0hh0mm0ss1ms，业务周期为60fps(＝16.667ms)，因为如果DRX周期以ms为单位，则很难将该业务周期映射到一个C-DRX配置上。此时，可以将该业务模式拆分为多个整数周期的C-DRX配置。表1示出了一种C-DRX配置1与C-DRX参数的对应关系，如表1所示，给UE配置如下的3个C-DRX参数来映射该业务模式：
表1 C-DRX配置1与C-DRX参数的对应关系
Figure PCTCN2022090048-appb-000001
图9为一实施例提供的又一种DRX配置方式的示意图。如图9所示，以采用一个DRX包含多个On-Duration时机来映射业务周期不是1ms的整数倍的DRX进行说明。基站给UE配置一个DRX周期和一个DRX周期内包含的多个On-Duration(即也可理解为PDCCH监控时段)的配置信息；多个 On-Duration包括：On-Duration长度、On-Duration的个数和/或各On-Duration的起始位置。
多个On-Duration的On-Duration长度可以相同(一个DRX周期内的多个On-Duration共用一个On-Duration长度)，或者多个On-Duration的On-Duration长度不同(一个DRX周期内地多个On-Duration对应一个On-Duration长度列表)。
一个DRX周期内的多个On-Duration的起始位置可由基站显式指示，或者显式指示第一个On-Duration开始位置，其余On-Duration开始位置可基于第一个On-Duration开始位置等间隔计算得到。
在图9中：一个DRX周期内包含3个On-Duration；第一个On-Duration的开始位置为DRX周期的开始位置；
后续两个On-Duration的开始位置基于第一个On-Duration的开始位置计算得到，比如：第二个On-Duration的开始位置＝第一个On-Duration的开始位置+Floor(DRX周期)/3；第三个On-Duration的开始位置＝第一个On-Duration的开始位置+Floor(DRX周期)*2/3。
图10为一实施例提供的又一种DRX配置方式的示意图。如图10所示，以指定DRX周期开始时机的DRX与Legacy DRX周期同时配置进行说明。本实施例展示了多组DRX配置的情况下：每组DRX配置分别对应于一个DRX非激活定时器，每组DRX对应的DRX非激活定时器独立启动；PDCCH监控的监控时机为多组DRX中PDCCH监控时机的并集。
在图10中：基站给UE配置一个DRX周期1(即第一DRX周期)和对应的PDCCH监控的开始时间、On-Duration1；基站给UE配置一个DRX周期2(即第二DRX周期)和对应的On-Duration2。
DRX周期1比DRX周期2长，一个DRX周期1内包含多个DRX周期2。
DRX周期2的开始时机比DRX周期1的开始时机PDCC监控的开始时间早，DRX周期1的结束时机也比DRX周期2的结束时机晚。则UE在DRX周期1的On-Duration1和DRX周期2的On-Duration2重叠区域，监控PDCCH的时段为：[DRX周期2的开始时机，DRX周期1的结束时机]。而在DRX周期1的其余时间段，因为只有DRX周期2的On-Duration2，UE只需按DRX周期2的On-Duration2监控PDCCH即可。
实施例四
图11为一实施例提供的又一种DRX配置方式的示意图。如图11所示，以到达时间不确定(抖动范围较大)的准周期性业务的业务模式以及对应的DRX配置进行说明。网络配置DRX周期和两种长度的PDCCH监控时段(即On-Duration)，例如第一PDCCH监控时段(DRX-OnDurationTimer1)和第二PDDCH监控时段(DRX-OnDurationTimer2)，较大的On-Duration覆盖整个抖动(即Jitter)的范围。一旦有数据需要UE接收，网络发送PDCCH信道或者传输开始指示(即Transmission Start Indication)或者PDCCH监控开始指示(即PDCCH Monitoring Start Indication)或者唤醒信号(Wake Up Signal，WUS)；若数据传输停止则发送传输结束指示(即Transmission End Indication)或者PDCCH监控结束指示(即PDCCH Monitoring End Indication)或者休眠指示(即Go-to-sleep Indication)。
收到PDCCH信道或者Transmission Start Indication或者PDCCH Monitoring Start Indication或者WUS之前，UE应用较小的On-Duration，例如min{DRX-OnDurationTimer1，DRX-OnDurationTimer2}，较小的On-Duration例如可以为第一PDCCH监控时段；
收到PDCCH信道或者Transmission Start Indication或者PDCCH Monitoring Start Indication或者WUS之后直到收到Transmission End Indication、PDCCH Monitoring End Indication或者Go-to-sleep Indication，UE应用较大的On-Duration，例如max{DRX-OnDurationTimer1，DRX-OnDurationTimer2}，较大的On-Duration例如可以为第一PDCCH监控时段。
或者，在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH，在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH；
或者，在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内在第一PDCCH监控时段上监控PDCCH，在除所述第一个DRX周期以外的每个DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，在第一DRX周期内在第一PDCCH监控时段上监控PDCCH，在第二DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，若在一个DRX周期内成功接收数据，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH；
或者，在第一PDCCH监控时段监控PDCCH，若检测到PDCCH或成功接收数据或检测到PDSCH对应的PDCCH，则在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH。
进一步地：UE在第一PDCCH监控时段上监控PDCCH时，采用第一PDCCH搜索空间的参数进行PDCCH监控(比如采用第一PDCCH搜索空间的PDCCH监控间隔，和第一PDCCH搜索空间的PDCCH连续监控时长)；UE在第二PDCCH监控时段上监控PDCCH时，采用第二PDCCH搜索空间的参数进行PDCCH监控(比如采用第二PDCCH搜索空间的PDCCH监控间隔和第二PDCCH搜索空间的PDCCH连续监控时长)。
图12为一实施例提供的又一种DRX配置方式的示意图。图12是以到达时间不确定(抖动范围较大)的准周期性业务的业务模式以及对应的DRX配置进行说明，可认为是图11的一种变形实施例。如图12所示，网络配置DRX周期和两种长度的PDCCH监控时段(即On-Duration)，例如DRX-OnDurationTimer1和DRX-OnDurationTimer2，较大的On-Duration覆盖整个Jitter的范围，以及PDCCH监控时段的下降步长(即On-Duration Ramping-down Step)。一旦有数据需要UE接收，网络发送PDCCH信道或者Transmission Start Indication或者PDCCH Monitoring Start Indication或者WUS；若数据传输停止则发送PDCCH信道或者Transmission End Indication或者PDCCH Monitoring End Indication或者Go-to-sleep Indication。
收到PDCCH信道或者Transmission Start Indication或者PDCCH Monitoring Start Indication或者WUS之前，UE应用较小的On-Duration，例如min{DRX-OnDurationTimer1，DRX-OnDurationTimer2}。
UE在收到PDCCH信道或者Transmission Start Indication或者PDCCH Monitoring Start Indication或者WUS之后的第一个DRX周期内，UE应用较大的On-Duration，例如max{DRX-OnDurationTimer1，DRX-OnDurationTimer2}；若成功接收数据则在下一个DRX周期按照配置的On-Duration Ramping-down Step下降步长缩减On-Duration的长度，即若在任意一个DRX周期内成功接收数据，则该DRX周期的下一个DRX周期对应的指定长度为该DRX周期的PDCCH监控时段的长度减去下降步长。如果任意一个DRX周期内没有成功接收到数据并且没有收到数据传输停止的指示(即可理解为错过)，则在下一个DRX周期恢复使用最长的On-Duration，即该DRX周期的下一个DRX周期对应的指定长度恢复为两种长度中较大的长度，如max{DRX-OnDurationTimer1，DRX-OnDurationTimer2}。若收到数据传输停止指示则UE应用较小的On-Duration，例如min{DRX-OnDurationTimer1，DRX-OnDurationTimer2}。
其中，UE按照配置的下降步长缩减On-Duration长度，最小长度不能低于配置的min{DRX-OnDurationTimer1，DRX-OnDurationTimer2}，即各DRX周期对应的指定长度大于或等于两种长度中较小的长度。
在一些实施例中，配置DRX周期为16ms，两种长度的On-Duration分别为2ms和8ms，其中8ms能够覆盖抖动范围，On-Duration下降步长配置为2ms。收到数据传输开始指示之后的第一个DRX周期(即DRX周期1)，UE应用On-Duration最大值8ms，成功接收数据则下一个DRX周期(即DRX周期2)，UE应用On-Duration长度为8ms-2ms＝6ms。如果DRX周期2数据接收成功则在下一个DRX周期(即DRX周期3)继续下降步长为8ms-2ms-2ms＝4ms，最低降到配置的On-Duration长度最小值2ms。如果在DRX周期4，On-Duration长度讲到最低值2ms的情况下，UE没有在DRX的On-Duration成功监听到数据则在下一个DRX周期恢复最长的On-Duration监听，在此基础上参考接收成功与否判断下个DRX周期沿用最长的On-Duration还是按照下降步长缩减On-Duration时间直到收到传输结束指示。
实施例五
本实施例是对非整数周期的PDCCH搜索空间的资源配置。
在前述DRX周期内On-Duration或者[PDCCH监控的开始时间，PDCCH监控的结束时间]期间，UE监控PDCCH也是按照PDCCH搜索空间(即Search Space)来监控的，PDCCH搜索空间目前可采用如下参数来配置(类似于DRX周期的配置)，包括：监控周期(以slot为单位)，监控周期的开始偏移位置(以slot)，监控时长(以slot为单位)以及每个slot内监控的符号数(以symbol为单位)。
其中：监控周期(slot)也只能取几个离散的整数值。例如，监控时隙周期和偏移量(即Monitoring Slot Periodicity And Offset)可以从如下选择：CHOICE{
sl1   NULL,
sl2   INTEGER(0..1),
sl4   INTEGER(0..3),
sl5    INTEGER(0..4),
sl8    INTEGER(0..7),
sl10   INTEGER(0..9),
sl16   INTEGER(0..15),
sl20   INTEGER(0..19),
sl40   INTEGER(0..39),
sl80   INTEGER(0..79),
sl160  INTEGER(0..159),
sl320  INTEGER(0..319),
sl640  INTEGER(0..639),
sl1280 INTEGER(0..1279),
sl2560 INTEGER(0..2559)}
比如：CHOICE选择sl1280 100，则表示监控时隙周期是1280slot，监控时隙的偏移量取值范围为100。
也就是PDCCH监控时隙的偏移量取值与PDCCH监控周期取值相关。且监控周期只能取几个离散的值，比如：sl1，sl2，sl4，sl5，sl8，sl10，sl16...，sl1280，sl2560。
这样，当业务周期不是监控周期(slot)的整数倍，业务周期不在PDCCH监控周期的取值范围内，或者DRX周期内PDCCH监控的On-Duration长度(即PDCCH监控的结束时间-PDCCH监控的开始时间)不是监控周期(slot)的整数倍，或者没有配置连接模式DRX时，就需要考虑PDCCH监控周期与DRX周期内PDCCH监控的On-Duration长度或业务周期的匹配关系。比如基于业务周期的长度，希望配置PDCCH监控周期是sl1281是配置不出来的。此时有如下2种解决方案：
(1)当PDCCH搜索空间与DRX周期内On-Duration存在交集时：
在连接模式DRX周期配置的情况下，在DRX周期内的PDCCH监控时段(即On-Duration)期间，UE从出现的第一个PDCCH搜索空间的开始位置，开始监控PDCCH；且只监控该PDCCH搜索空间的开始位置落在DRX周期内的On-Duration期间的PDCCH。也就是：如果PDCCH搜索空间的开始位置落在On-Duration之外，即使该PDCCH搜索空间的PDCCH监控时机落在DRX周期内的On-Duration期间，该PDCCH搜索空间也无需监控；如果PDCCH搜索空间的开始位置落在On-Duration之内，即使该PDCCH搜索空间的PDCCH监控时机落在DRX周期的On-Duration外，该PDCCH搜索空间也需要监控。
(2)重新定义PDCCH搜索空间的配置策略，以适配非整数周期问题。具体参见图13。
图13为一实施例提供的又一种DRX配置方式的示意图。如图13所示，基站给UE配置：PDCCH搜索空间的开始时间(即PDCCH Search Space Start Time)、PDCCH监控持续时长(即PDCCH监控时段Duration)和PDCCH搜索空间的周期；
其中，PDCCH搜索空间的开始时间可以通过绝对时机配置，或者基于某个时机的相对时间偏移(即Offset)来配置。
具体的，PDCCH搜索空间的开始时间可以通过绝对时机(SFN、subframe和/或slot)配置；或者基于绝对时机(某个SFN、subframe和/或slot)的相对时间偏移(即Time Offset)来表征，具体地：SFN、subframe和/或slot可以为配置该PDCCH搜索空间的RRC消息的首次传输的无线帧、子帧和/或时隙。对时间偏移(即Time Offset)为参考SFN、subframe和/或slot到PDCCH搜索空间的开始时间的时间间隔。
其中，基站给UE配置的PDCCH搜索空间的周期可以与UE的业务模式一一对应；此时，需要业务的周期取值范围和PDCCH搜索空间周期的取值范围完全一致，比如：PDCCH搜索空间周期的周期以赫兹(Hz)、帧每秒(Fps)、ms、或者us为单位，且可以是取值范围内的任意整数值表征的周期。
考虑到与业务模式匹配，且PDCCH搜索空间的周期由基站显式配置(而不是计算得到)，PDCCH搜索空间周期的取值范围不受一个SFN周期(10240ms的整数因子)的约束。UE可通过定时器来计算下一个PDCCH搜索空间周期的开始时间(上一个PDCCH搜索空间周期的结束时间即为下一个PDCCH搜索空间周期的开始时间)。
如果业务周期不是PDCCH搜索空间周期基准单位的整数倍，则第N个PDCCH搜索空间周期的开始位置＝Floor(第一个PDCCH搜索空间周期的开始位置+(N-1)*Period)。其中：Floor表示下取整，N表示第N个DRX周期，Period表示业务周期或者PDCCH搜索空间的周期长度，计算时要 转换为PDCCH搜索空间周期长度的基本单位(比如ms、slot或者symbol)。
第N个PDCCH搜索空间周期的开始位置也可以如下计算：
第N个PDCCH搜索空间周期的开始位置＝Ceil(第一个PDCCH搜索空间周期的开始位置+(N-1)*Period)；
或者，
第N个PDCCH搜索空间周期的开始位置＝Round(第一个PDCCH搜索空间周期的开始位置+(N-1)*Period)；
其中：Ceil为上取整；Round为四舍五入到最接近的整数。
或者，
第N个PDCCH搜索空间开始时间＝第一个DRX周期开始时间+Floor((N-1)*Period)，即第N个PDCCH搜索空间周期开始时间可以为第一个PDCCH搜索空间周期的开始时间与N-1个业务周期长度向下取整后的和；
或者，
第N个PDCCH搜索空间周期开始时间＝第一个PDCCH搜索空间周期开始时间+Ceil((N-1)*Period)，即第N个PDCCH搜索空间周期开始时间可以为第一个PDCCH搜索空间周期的开始时间与与N-1个业务周期长度向上取整后的和。
或者，
第N个PDCCH搜索空间周期开始时间＝第一个PDCCH搜索空间周期开始时间+Round((N-1)*Period)，即第N个PDCCH搜索空间周期开始时间可以为第一个PDCCH搜索空间周期的开始时间与N-1个业务周期长度最接近的PDCCH搜索空间整数周期的和。
此处PDCCH搜索空间周期单位可以为：ms、frame、subfrmae、slot、或symbol。也就是先把业务周期转换为PDCCH搜索空间周期的单位，再通过下取整、上取整、或者四舍五入到PDCCH搜索空间周期单位的开始位置。
如果业务发生频率用Hz或fps表征，则通过倒数转换为对应的PDCCH搜索空间周期。比如xHz对应的PDCCH搜索空间周期为(1/x)秒，然后转换为ms、symbol或者slot。1ms＝1subframe，所以ms和subframe做单位是等价的。
本申请实施例还提供一种配置装置。图14为一实施例提供的一种配置装置的结构示意图。如图14所示，所述配置装置包括：业务信息获取模块310和配置信息发送模块320；
业务信息获取模块310，设置为获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间；
配置信息发送模块320，设置为根据所述业务信息发送PDCCH监控相关的配置信息，所述配置信息用于指示物理下行控制信道PDCCH的监控时机。
本实施例的配置装置，通过根据业务信息配置来指示PDCCH的监控时机，可以不受业务周期的限制，提高监控的灵活性，实现对于数据包传输时机不确定或大周期的业务、以及业务周期不是10240ms的整数因子的终端的节能。
在一实施例中，配置信息为DRX的配置信息；配置信息用于指示PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度。
在一实施例中，PDCCH监控的开始时间通过第一指定位置和第一时间偏移量指示，其中，第一指定位置包括配置信息的RRC消息或MAC控制元素CE首次传输的无线帧、子帧和/或时隙，或第一指定位置指定的无线帧、子帧和/或时隙；第一时间偏移量包括从第一指定位置到PDCCH监控的开始时间的时间间隔；
PDCCH监控的结束时间根据第二指定位置和第二时间偏移量指示，其中，第二指定位置包括第一指定位置，或者PDCCHPDCCH监控的开始时间；第二时间偏移量为从第二指定位置到PDCCH监控的结束时间的时间间隔。
在一实施例中，该装置还包括：
配置模块，设置为在监控时段内，配置周期性BSR资源或者SR指示资源；或者基于PDCCH的监控时段确定周期性BSR资源或者SR指示资源的有效时机；或者通过配置信息指示周期性BSR资源或者SR指示的有效时间段，PDCCH监控时段为接收到BSR或者SR后的预定义时间段；
调度模块，设置为在接收到BSR或者SR的情况下进行承载用户面数据的上行PUSCH资源调度；
其中，周期性BSR资源或者SR指示资源包括周期性CG资源、周期性非竞争PRACH资源和/ 或用于指示分配上行授权资源的上行物理信号。
在一实施例中，配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
在一实施例中，配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置包括DRX周期长度以及对应的起始偏移；监控PDCCH的时机为各DRX配置中PDCCH监控时机的并集。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置包括PDCCH监控的开始时间、PDCCH监控的结束时间以及业务周期。
在一实施例中，配置信息包括DRX周期和DRX周期内包含的多个PDCCH监控时段的配置信息；多个PDCCH监控时段的配置信息包括：各PDCCH监控时段的长度、PDCCH监控时段的个数和/或各PDCCH监控时段的起始位置。
在一实施例中，配置信息包括多组DRX配置，每组DRX配置分别对应于一个DRX非激活定时器。
在一实施例中，配置信息包括DRX周期以及两种长度的PDCCH监控时段。
在一实施例中，配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长。
在一实施例中，该装置还包括：
第一发送模块，设置为在开始传输数据的情况下，发送PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号；
第二发送模块，设置为在数据传输停止的情况下，发送传输结束指示或者PDCCH监控结束指示或者休眠指示。
在一实施例中，配置信息为通过如下参数配置的PDCCH搜索空间：PDCCH搜索空间的开始时间、PDCCH监控时段和PDCCH搜索空间的周期。
在一实施例中，业务信息获取模块310，具体包括：
第一获取单元，设置为根据核心网传递的QoS参数获取业务信息；或者，
第二获取单元，设置为根据终端的辅助信息、上行RRC消息和/或上行MAC CE结构获取业务信息。
本实施例提出的配置装置与上述实施例提出的配置方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行配置方法相同的有益效果。
本申请实施例还提供一种信道监控装置。图15为一实施例提供的一种信道监控装置的结构示意图。如图15所示，所述信道监控装置包括：配置信息接收模块410和监控模块420；
配置信息接收模块410，设置为接收PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。
监控模块420，设置为根据所述配置信息监控PDCCH。
本实施例的信道监控装置，通过根据可指示PDCCH的监控时机的配置信息来监控PDCCH，可以不受业务周期的限制，提高监控的灵活性，实现对于数据包传输时机不确定或大周期的业务、以及业务周期不是10240ms的整数因子的终端的节能。
在一实施例中，配置信息为DRX的配置信息；配置信息用于指示PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度；
监控模块420，具体包括：
第一监控单元，设置为在每个DRX周期内，在指定时间区间内监控PDCCH或按照第一PDCCH搜索空间监控PDCCH，在非指定时间区间不监控PDCCH或按照第二PDCCH搜索空间监控PDCCH，或者，在每个DRX周期内，在发送BSR或者SR后开始监控PDCCH；其中，指定时间区间包括从PDCCH监控的开始时间到数据包传输完成，或者从PDCCH监控的开始时间到PDCCH监控的结束时间，或者，从发送BSR或者SR后到数据包传输完成，或者从发送BSR或者SR后到PDCCH监控的结束时间。
在一实施例中，第N个DRX周期的开始时间为以下之一：
第一个DRX周期的开始时间与N-1个业务周期向下取整的结果之和；
第一个DRX周期的开始时间与N-1个业务周期向上取整的结果之和；
第一个DRX周期的开始时间与最接近于N-1个业务周期的整数之和；
第一个DRX周期的开始时间与N-1个业务周期之和向下取整的结果；
第一个DRX周期的开始时间与N-1个业务周期之和向上取整的结果；
第一个DRX周期的开始时间与N-1个业务周期之和最接近的DRX整数周期位置。
在一实施例中，配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
在一实施例中，监控模块420，具体还包括：
第二监控单元，设置为在每个DRX周期内，从PDCCH监控的开始时间开始监控PDCCH，直至满足以下任一条件，停止监控PDCCH：
在PDCCH监控的开始时间之后监控到PDCCH，并在收到或反馈HARQ ACK后启动DRX非激活定时器；
在DRX非激活定时器定时期间监控到PDCCH，并在收到或反馈HARQ ACK后重新启动DRX非激活定时器；
在DRX非激活定时器定时期间未监控到PDCCH，且DRX非激活定时器超时；
PDCCH监控的结束时间到时且未监控到PDCCH。
在一实施例中，配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
在一实施例中，该装置还包括：
启动模块，设置为在每个DRX周期内，若监控到PDCCH，则在收到或反馈HARQ ACK后启动DRX非激活定时器；
重启动模块，设置为在DRX非激活定时器定时期间监控到PDCCH，则在收到或反馈HARQ ACK后重新启动DRX非激活定时器；
停止模块，设置为在DRX非激活定时器定时期间未监控到PDCCH，则在DRX非激活定时器超时后停止监控PDCCH。
在一实施例中，配置信息包括多组DRX配置；
监控模块420，具体还包括：
第六监控单元，设置为在各DRX配置中包含的PDCCH监控时机监控PDCCH。
在一实施例中，配置信息包括第一DRX周期的配置信息和第二DRX周期的配置信息，其中，第一DRX周期内包括多个第二DRX周期；
监控模块420，具体还包括：
第七监控单元，设置为在每个第一DRX周期内，对于第一DRX周期和第二DRX周期内包含的PDCCH监控时段的重叠区域，从开始较早的PDCCH监控时段的开始时机，到结束较晚的PDCCH监控时段的结束时机监控PDCCH；
第八监控单元，设置为对于非重叠区域，按照第二DRX周期内包含的PDCCH监控时段监控PDCCH。
在一实施例中，配置信息包括DRX周期以及第一PDCCH监控时段和第二PDCCH监控时段；
监控模块420，具体还包括：
第九监控单元，设置为在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH；
第十监控单元，设置为在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，直至接收到传输结束指示或者PDCCH监控结束指示或者休眠指示，在第二PDCCH监控时段上监控PDCCH。
或者，监控模块420可用于：在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH，在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH；
或者，监控模块420可用于：在接收到传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内在第一PDCCH监控时段上监控PDCCH，在除所述第一个DRX周期以外的每个DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，监控模块420可用于：在第一DRX周期内在第一PDCCH监控时段上监控PDCCH，在第二DRX周期内在第二PDCCH监控时段上监控PDCCH；
或者，监控模块420可用于：若在一个DRX周期内成功接收数据，在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH；
或者，监控模块420可用于：在第一PDCCH监控时段监控PDCCH，若检测到PDCCH或成功接收数据或检测到PDSCH对应的PDCCH，则在第一PDCCH监控时段和第二PDCCH监控时段上监控PDCCH，或，在第二PDCCH监控时段上监控PDCCH；
其中，所述第一DRX周期包括一个或多个DRX周期，所述第二DRX周期包括一个或多个DRX周期。
在一实施例中，配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长；
监控模块420，具体还包括：
第十一监控单元，设置为在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，根据两种长度中长度较小的PDCCH监控时段监控PDCCH；
第十二监控单元，设置为在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内根据两种长度中长度较大的PDCCH监控时段监控PDCCH，并在除第一个DRX周期以外的每个DRX周期内使用对应的指定长度的PDCCH监控时段监控PDCCH；
第十三监控单元，设置为若接收到数据传输停止的指示，则根据所长度较小的PDCCH监控时段监控PDCCH；
其中，若在任意一个DRX周期内成功接收数据，则该DRX周期的下一个DRX周期对应的指定长度为该DRX周期的PDCCH监控时段的长度减去下降步长；若在任意一个DRX周期内未成功接收到数据且没有收到数据传输停止的指示，则该DRX周期的下一个DRX周期对应的指定长度恢复为两种长度中较大的长度；其中，各DRX周期对应的指定长度大于或等于两种长度中较小的长度。
在一实施例中，监控模块420，具体还包括：
第十四监控单元，设置为在每个DRX周期内的PDCCH监控时段内，从第一个PDCCH搜索空间的开始位置开始监控满足条件的PDCCH，满足条件的PDCCH包括搜索空间的开始位置落在相应的DRX周期内的PDCCH监控时段内的PDCCH。
在一实施例中，该装置还包括：
确定模块，设置为根据如下参数确定PDCCH搜索空间：PDCCH搜索空间的开始时间、PDCCH监控时段和PDCCH搜索空间的周期。
本实施例提出的信道监控装置与上述实施例提出的信道监控方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行信道监控方法相同的有益效果。
本申请实施例还提供了一种通信节点，该通信节点可以是基站或终端，图16为一实施例提供的一种通信节点的硬件结构示意图，如图16所示，本申请提供的通信节点，包括存储器520、处理器510以及存储在存储器上并可在处理器上运行的计算机程序，处理器510执行所述程序时实现上述的配置方法或信道监控方法。
通信节点还可以包括存储器520；该通信节点中的处理器510可以是一个或多个，图16中以一个处理器510为例；存储器520用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器510执行，使得所述一个或多个处理器510实现如本申请实施例中所述的配置方法或信道监控方法。
通信节点还包括：通信装置530、输入装置540和输出装置550。
通信节点中的处理器510、存储器520、通信装置530、输入装置540和输出装置550可以通过总线或其他方式连接，图16中以通过总线连接为例。
输入装置540可用于接收输入的数字或字符信息，以及产生与通信节点的用户设置以及功能控制有关的按键信号输入。输出装置550可包括显示屏等显示设备。
通信装置530可以包括接收器和发送器。通信装置530设置为根据处理器510的控制进行信息收发通信。
存储器520作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述配置方法对应的程序指令/模块(例如，配置装置中的业务信息获取模块310和配置信息发送模块320)；或者如本申请实施例所述信道监控方法对应的程序指令/模块(例如，信 道监控装置中的配置信息接收模块410和监控模块420)。存储器520可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据通信节点的使用所创建的数据等。此外，存储器520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器520可进一步包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的配置方法或信道监控方法。该配置方法，包括：获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间；根据所述业务信息发送PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。该信道监控方法，包括：接收PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机；根据所述配置信息监控PDCCH。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是，但不限于：电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式CD-ROM、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的一些实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory， RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本申请的范围。因此，本申请的恰当范围将根据权利要求确定。

Claims (30)

  1. 一种配置方法，包括：
    获取业务信息，所述业务信息包括业务周期、业务可能到达的开始时间以及业务可能到达的结束时间；
    根据所述业务信息发送物理下行控制信道PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机。
  2. 根据权利要求1所述的方法，其中，所述配置信息为非连续接收DRX的配置信息；所述配置信息用于指示PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度。
  3. 根据权利要求2所述的方法，其中，
    所述PDCCH监控的开始时间通过第一指定位置和第一时间偏移量指示，其中，
    所述第一指定位置包括所述配置信息的无线资源控制RRC消息或媒体接入控制MAC控制元素CE首次传输的无线帧、子帧和/或时隙，或者所述第一指定位置包括指定的无线帧、子帧和/或时隙；
    所述第一时间偏移量包括从所述第一指定位置到所述PDCCH监控的开始时间的时间间隔；
    所述PDCCH监控的结束时间根据第二指定位置和第二时间偏移量指示，其中，
    所述第二指定位置包括所述第一指定位置，或者PDCCH监控的开始时间；
    所述第二时间偏移量包括从所述第二指定位置到所述PDCCH监控的结束时间的时间间隔。
  4. 根据权利要求1所述的方法，还包括：
    在PDCCH监控时段内，配置周期性缓冲区状态上报BSR资源或者调度请求SR指示资源；或者基于所述PDCCH的监控时段确定周期性BSR资源或者SR指示资源的有效时机；或者通过所述配置信息指示周期性BSR资源或者SR指示的有效时间段，所述PDCCH监控时段为接收到BSR或者SR后的预定义时间段；
    所述方法还包括：在接收到BSR或者SR的情况下进行承载用户面数据的上行物理上行共享信道PUSCH资源调度；
    其中，所述周期性BSR资源或者SR指示资源包括周期性配置授权CG资源、周期性非竞争物理随机接入信道PRACH资源和/或用于指示分配上行授权资源的上行物理信号。
  5. 根据权利要求1所述的方法，其中，所述配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；
    所述配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
  6. 根据权利要求1所述的方法，其中，所述配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
  7. 根据权利要求1所述的方法，其中，所述配置信息包括多组DRX配置，每组DRX配置包括DRX周期长度以及对应的起始偏移；
    监控PDCCH的时机为各所述DRX配置中PDCCH监控时机的并集。
  8. 根据权利要求1所述的方法，其中，所述配置信息包括多组DRX配置，每组DRX配置包括PDCCH监控的开始时间、PDCCH监控的结束时间以及业务周期。
  9. 根据权利要求1所述的方法，其中，所述配置信息包括DRX周期和所述DRX周期内包含的多个PDCCH监控时段的配置信息；
    所述多个PDCCH监控时段的配置信息包括：各所述PDCCH监控时段的长度、所述PDCCH监控时段的个数和/或各所述PDCCH监控时段的起始位置。
  10. 根据权利要求1所述的方法，其中，所述配置信息包括多组DRX配置，每组DRX配置分别对应于一个DRX非激活定时器。
  11. 根据权利要求1所述的方法，其中，所述配置信息包括DRX周期以及两种长度的PDCCH监控时段。
  12. 根据权利要求1所述的方法，其中，所述配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长。
  13. 根据权利要求11或12所述的方法，其中，还包括：
    在开始传输数据的情况下，发送PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号；
    在数据传输停止的情况下，发送传输结束指示或者PDCCH监控结束指示或者休眠指示。
  14. 根据权利要求1所述的方法，其中，所述配置信息为通过如下参数配置的PDCCH搜索空间：
    PDCCH搜索空间的开始时间、PDCCH监控时段以及PDCCH搜索空间的周期。
  15. 根据权利要求1所述的方法，其中，所述获取业务信息包括：
    根据核心网传递的服务质量QoS参数获取业务信息；或者，
    根据终端的辅助信息、上行RRC消息和/或上行MAC CE结构获取业务信息。
  16. 一种信道监控方法，包括：
    接收物理下行控制信道PDCCH监控相关的配置信息，所述配置信息用于指示PDCCH的监控时机；
    根据所述配置信息监控PDCCH。
  17. 根据权利要求16所述的方法，其中，所述配置信息为非连续接收DRX的配置信息；所述配置信息用于指示物理下行控制信道PDCCH监控的开始时间、PDCCH监控的结束时间以及DRX周期长度；
    根据所述配置信息监控PDCCH，包括：
    在每个DRX周期内，在指定时间区间内监控PDCCH或按照第一PDCCH搜索空间监控PDCCH，在非指定时间区间不监控PDCCH或按照第二PDCCH搜索空间监控PDCCH；
    或者，在每个DRX周期内，在发送BSR或者SR后开始监控PDCCH；
    其中，所述指定时间区间包括从PDCCH监控的开始时间到数据包传输完成，或者从PDCCH监控的开始时间到PDCCH监控的结束时间，或者，从发送BSR或者SR后到数据包传输完成，或者从发送BSR或者SR后到PDCCH监控的结束时间。
  18. 根据权利要求17所述的方法，其中，第N个DRX周期的开始时间为以下之一：
    第一个DRX周期的开始时间与N-1个业务周期向下取整的结果之和；
    第一个DRX周期的开始时间与N-1个业务周期向上取整的结果之和；
    第一个DRX周期的开始时间与最接近于N-1个业务周期的整数之和；
    第一个DRX周期的开始时间与N-1个业务周期之和向下取整的结果；
    第一个DRX周期的开始时间与N-1个业务周期之和向上取整的结果；
    第一个DRX周期的开始时间与N-1个业务周期之和最接近的DRX整数周期位置。
  19. 根据权利要求16所述的方法，其中，
    所述配置信息用于指示PDCCH监控的开始时间以及DRX周期长度；
    所述配置信息还用于指示PDCCH监控的结束时间、或PDCCH监控时段或DRX非激活定时信息。
  20. 根据权利要求19所述的方法，其中，根据所述配置信息监控PDCCH，包括：
    在每个DRX周期内，从PDCCH监控的开始时间开始监控PDCCH，直至满足以下任一条件，停止监控PDCCH：
    在所述PDCCH监控的开始时间之后监控到PDCCH，并在收到或反馈混合自动重传请求HARQ确认信息ACK后启动DRX非激活定时器；
    在DRX非激活定时器定时期间监控到PDCCH，并在收到或反馈HARQ ACK后重新启动所述DRX非激活定时器；
    在DRX非激活定时器定时期间未监控到PDCCH，且所述DRX非激活定时器超时；
    PDCCH监控的结束时间到时且未监控到PDCCH。
  21. 根据权利要求16所述的方法，其中，所述配置信息用于指示PDCCH监控的开始时间、DRX非激活定时信息以及DRX周期长度。
  22. 根据权利要求21所述的方法，其中，还包括以下之一：在每个DRX周期内，
    若监控到PDCCH，则在收到或反馈HARQ ACK后启动DRX非激活定时器；
    在所述DRX非激活定时器定时期间监控到PDCCH，则在收到或反馈HARQ ACK后重新启动所述DRX非激活定时器；
    在所述DRX非激活定时器定时期间未监控到PDCCH，则在所述DRX非激活定时器超时后停止监控PDCCH。
  23. 根据权利要求16所述的方法，其中，所述配置信息包括多组DRX配置；
    根据所述配置信息监控PDCCH，包括：
    在各所述DRX配置中包含的PDCCH监控时机监控PDCCH。
  24. 根据权利要求16所述的方法，其中，所述配置信息包括第一DRX周期的配置信息和第二 DRX周期的配置信息，其中，所述第一DRX周期内包括多个所述第二DRX周期；
    根据所述配置信息监控PDCCH，包括：在每个第一DRX周期内，
    对于所述第一DRX周期和所述第二DRX周期内包含的PDCCH监控时段的重叠区域，从开始较早的PDCCH监控时段的开始时机，到结束较晚的PDCCH监控时段的结束时机监控PDCCH；
    对于非重叠区域，按照所述第二DRX周期内包含的PDCCH监控时段监控PDCCH。
  25. 根据权利要求16所述的方法，其中，所述配置信息包括DRX周期以及第一PDCCH监控时段和第二PDCCH监控时段；
    根据所述配置信息监控PDCCH，包括：
    在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，在第一PDCCH监控时段上监控PDCCH，在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后，直至接收到传输结束指示或者PDCCH监控结束指示或者休眠指示，在第二PDCCH监控时段上监控PDCCH。
  26. 根据权利要求16所述的方法，其中，所述配置信息包括DRX周期、两种长度的PDCCH监控时段以及PDCCH监控时段的下降步长；
    根据所述配置信息监控PDCCH，包括：在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之前，根据所述两种长度中长度较小的PDCCH监控时段监控PDCCH；
    在接收到PDCCH信道或者传输开始指示或者PDCCH监控开始指示或者唤醒信号之后的第一个DRX周期内根据所述两种长度中长度较大的PDCCH监控时段监控PDCCH，并在除所述第一个DRX周期以外的每个DRX周期内使用对应的指定长度的PDCCH监控时段监控PDCCH；
    若接收到数据传输停止的指示，则根据所述长度较小的PDCCH监控时段监控PDCCH；
    其中，若在任意一个DRX周期内成功接收数据，则该DRX周期的下一个DRX周期对应的指定长度为该DRX周期的PDCCH监控时段的长度减去所述下降步长；
    若在任意一个DRX周期内未成功接收到数据且没有收到数据传输停止的指示，则该DRX周期的下一个DRX周期对应的指定长度恢复为所述两种长度中较大的长度；
    其中，各所述DRX周期对应的指定长度大于或等于所述两种长度中较小的长度。
  27. 根据权利要求16所述的方法，其中，根据所述配置信息监控PDCCH，包括：
    在每个DRX周期内的PDCCH监控时段内，从第一个PDCCH搜索空间的开始位置开始监控满足条件的PDCCH，所述满足条件的PDCCH包括搜索空间的开始位置落在相应的DRX周期内的PDCCH监控时段内的PDCCH。
  28. 根据权利要求16所述的方法，其中，还包括：
    根据如下参数确定PDCCH搜索空间：PDCCH搜索空间的开始时间、PDCCH监控时段和PDCCH搜索空间的周期。
  29. 一种通信节点，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1-15中任一项所述的配置方法或如权利要求16-28中任一项所述的信道监控方法。
  30. 一种计算机可读存储介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如权利要求1-15中任一项所述的配置方法或如权利要求16-28中任一项所述的信道监控方法。
PCT/CN2022/090048 2021-12-31 2022-04-28 配置方法、信道监控方法、通信节点及存储介质 Ceased WO2023123777A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22913073.7A EP4459905A4 (en) 2021-12-31 2022-04-28 Configuration method, channel monitoring method, communication node and storage medium
KR1020247025366A KR20240141746A (ko) 2021-12-31 2022-04-28 구성 방법, 채널 모니터링 방법, 통신 노드 및 저장 매체
US18/757,487 US20240349302A1 (en) 2021-12-31 2024-06-27 Configuration method, channel monitoring method, communication node and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111673935.2A CN115865287A (zh) 2021-12-31 2021-12-31 配置方法、信道监控方法、通信节点及存储介质
CN202111673935.2 2021-12-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/757,487 Continuation US20240349302A1 (en) 2021-12-31 2024-06-27 Configuration method, channel monitoring method, communication node and storage medium

Publications (1)

Publication Number Publication Date
WO2023123777A1 true WO2023123777A1 (zh) 2023-07-06

Family

ID=85652799

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/090048 Ceased WO2023123777A1 (zh) 2021-12-31 2022-04-28 配置方法、信道监控方法、通信节点及存储介质

Country Status (5)

Country Link
US (1) US20240349302A1 (zh)
EP (1) EP4459905A4 (zh)
KR (1) KR20240141746A (zh)
CN (2) CN115865287A (zh)
WO (1) WO2023123777A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022031809A1 (en) * 2020-08-05 2022-02-10 Idac Holdings, Inc. Idle/inactive mobility for small data transmission
CN119485669A (zh) * 2023-08-10 2025-02-18 华为技术有限公司 一种确定harq进程标识的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076552A (zh) * 2018-07-16 2018-12-21 北京小米移动软件有限公司 信道监测方法、装置、系统及存储介质
CN111181686A (zh) * 2018-11-09 2020-05-19 华硕电脑股份有限公司 用于改进物理下行链路控制信道监听模式的方法和设备
US20200236692A1 (en) * 2019-01-23 2020-07-23 Samsung Electronics Co., Ltd. Method and apparatus for managing pdcch processing timelines

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20210138762A (ko) * 2019-03-27 2021-11-19 콘비다 와이어리스, 엘엘씨 뉴 라디오에서의 drx 구성
CN113557768A (zh) * 2019-03-28 2021-10-26 瑞典爱立信有限公司 通过ue的可允许传输间隙辅助

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109076552A (zh) * 2018-07-16 2018-12-21 北京小米移动软件有限公司 信道监测方法、装置、系统及存储介质
CN111181686A (zh) * 2018-11-09 2020-05-19 华硕电脑股份有限公司 用于改进物理下行链路控制信道监听模式的方法和设备
US20200236692A1 (en) * 2019-01-23 2020-07-23 Samsung Electronics Co., Ltd. Method and apparatus for managing pdcch processing timelines

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Discussion on DCI-based power saving adaptation during DRX active time", 3GPP TSG RAN WG1 #103-E, R1-2008966, 24 October 2020 (2020-10-24), XP051946754 *
See also references of EP4459905A4 *

Also Published As

Publication number Publication date
EP4459905A4 (en) 2025-04-16
KR20240141746A (ko) 2024-09-27
CN115865287A (zh) 2023-03-28
CN118740353A (zh) 2024-10-01
US20240349302A1 (en) 2024-10-17
EP4459905A1 (en) 2024-11-06

Similar Documents

Publication Publication Date Title
EP3104650B1 (en) Method and device for performing communication by using unauthorized spectrum
CN113170498B (zh) 用于针对被配置sps和drx的ue启用下行链路调度的方法和网络节点
EP2169871B1 (en) Method and apparatus of handling a timer for triggering buffer status report
EP3764733A1 (en) Communication method and apparatus for discontinuous reception, and communication device and communication system
CN111865536B (zh) 搜索空间的监测、配置方法及装置
CN113812184B (zh) 非连续接收中的唤醒信令处理
CN115087082B (zh) 上行发送处理方法、装置、终端及可读存储介质
CN113994740A (zh) 用于处理pdcch跳过和唤醒信令的机制
CN112312523A (zh) 一种通信方法及装置
JP7690034B2 (ja) 上りリンク伝送の方法、端末及びネットワーク側機器
CN113225791B (zh) 基于唤醒信号的上行链路信息
WO2022222892A1 (zh) 一种非连续接收的配置方法及装置
CN113939036B (zh) 信道监听、传输方法、终端及网络侧设备
CN113767673A (zh) 非连续接收中的定时器控制
US20240349302A1 (en) Configuration method, channel monitoring method, communication node and storage medium
EP3316655A1 (en) Method, terminal and system for reducing power consumption of cluster terminal in broadband cluster system
CN112534916A (zh) 用于进入睡眠模式的交互机制
CN120660396A (zh) 用于小数据传输的设备、方法和装置
CN113365326B (zh) 资源调度方法、装置、设备及存储介质
CN113709852B (zh) 一种通信传输的方法、装置及系统
CN107079422A (zh) 半双工系统下的子帧调度方法、数据收发方法、装置和系统
CN114223159B (zh) 高层ack/nack的传输
JP2025531492A (ja) 通信のためのデバイス、方法、装置およびコンピュータ可読媒体
WO2022206159A1 (zh) 信道发送、接收方法、通信节点及存储介质
CN114760715A (zh) Rrc状态转换报告

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: 22913073

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202417056865

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022913073

Country of ref document: EP

Effective date: 20240731