CN115623562A - A scheduling method, device, equipment, medium and chip - Google Patents

Abstract

The application discloses a scheduling method, a scheduling device, a scheduling apparatus, a scheduling medium and a scheduling chip, wherein the method comprises the following steps: starting a first timer; sending a Scheduling Request (SR) message before the first timer runs out; starting a second timer; and if the second timer finishes running and the first timer finishes running, stopping sending the SR message. By the method, the power consumption of the terminal equipment during scheduling can be reduced.

Description

A scheduling method, device, equipment, medium and chip

technical field

The present application relates to the technical field of communication, and in particular to a scheduling method, device, equipment, medium and chip.

Background technique

In the new air interface (New Radio, NR), the terminal device can send a scheduling request (Scheduling Request, SR) message to the network device to request resources that can be used to send uplink data to the network device, and the terminal device also needs to send the SR message A corresponding SR resource, the SR resource may be configured by a network device. After the terminal device sends the SR message, it can be triggered to enter the state of monitoring the physical downlink control channel (Physical Downlink Control Channel, PDCCH). When the PDCCH is not monitored after a certain period of time, the SR message will be resent.

Currently, a terminal device can send an SR message at any time when there are SR resources, and sending an SR message is not limited by a discontinuous reception (DRX) state. This means that the terminal device may enter the state of monitoring the PDCCH at any time, and the network device may not schedule the terminal device. At this time, the terminal device will repeatedly send the SR message, and has been in the state of monitoring the PDCCH, resulting in the failure of the terminal device. Increased energy consumption.

Contents of the invention

The present application discloses a scheduling method, device, equipment, medium and chip, which reduce the power consumption of terminal equipment during scheduling.

In the first aspect, an embodiment of the present application provides a scheduling method, device, device, medium, and chip, the method including:

start the first timer;

Sending a scheduling request SR message before the end of the first timer;

start the second timer;

If the running of the second timer ends and the running of the first timer ends, the sending of the SR message is stopped.

In an embodiment, the SR message is sent within the scheduling request SR sending window.

In one embodiment, the starting time of the SR sending window is before the running starting time of the first timer or during the running of the first timer.

In one embodiment, if the running of the second timer ends and the running of the first timer has not ended, the SR message is resent.

In one embodiment, the first timer includes one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

In one embodiment, the second timer includes one or more of the following timers:

Scheduling request prohibition timer SR-ProhibitTimer;

Scheduling request transmission timer SR-TransmissionTimer.

In a second aspect, the embodiment of the present application provides a communication device, including:

a processing unit, configured to start a first timer;

A communication unit, configured to send a scheduling request SR message before the end of the first timer;

The processing unit is also used to start a second timer;

The processing unit is further configured to stop sending the SR message if the running of the second timer ends and the running of the first timer ends.

In a third aspect, an embodiment of the present application provides a communication device, including a processor and a memory, the memory is used to store a computer program, the computer program includes program instructions, the processor is configured to call the program instructions, and execute as described in the first aspect scheduling method.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores one or more instructions, and one or more instructions are suitable for being loaded by a processor and executing the scheduling described in the first aspect. method.

In the fifth aspect, the embodiment of the present application provides a chip, the chip is used to implement the scheduling method described in the first aspect.

In a sixth aspect, the embodiment of the present application provides a chip module, the chip module includes a storage device, a chip, and a communication interface, and the chip is used to execute the scheduling method described in the first aspect.

In the embodiment of this application, the terminal device can start the first timer; send a scheduling request SR message before the end of the first timer; start the second timer; if the second timer ends, and the first timer ends , then stop sending SR messages. Through this method, the power consumption of the terminal device during scheduling can be reduced.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application. Ordinary technicians can also obtain other drawings based on these drawings on the premise of not paying creative work.

FIG. 1 is a schematic diagram of a discontinuous reception cycle provided by an embodiment of the present application;

FIG. 2 is a schematic flowchart of a scheduling request method provided in an embodiment of the present application;

FIG. 3 is a schematic flowchart of a scheduling request method provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of sending an SR message within the SR sending window provided by an embodiment of the present application;

FIG. 5 is another schematic diagram of sending an SR message within the SR sending window provided by the embodiment of the present application;

FIG. 6 is a schematic diagram of units of a communication device provided in an embodiment of the present application;

FIG. 7 is a simplified schematic diagram of a physical structure of a communication device provided in an embodiment of the present application;

FIG. 8 is a simplified schematic diagram of a chip module provided by an embodiment of the present application.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element. In addition, different implementations of the present application Components, features, and elements with the same name in the example may have the same meaning, or may have different meanings, and the specific meaning shall be determined based on the explanation in the specific embodiment or further combined with the context in the specific embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination". Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising", "comprising" indicate the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not exclude one or more other features, steps, operations, The existence, occurrence or addition of an element, component, item, species, and/or group. The terms "or" and "and/or" as used herein are to be construed as inclusive, or to mean either one or any combination. Thus, "A, B or C" or "A, B and/or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C" . Exceptions to this definition will only arise when combinations of elements, functions, steps or operations are inherently mutually exclusive in some way.

It should be understood that although the various steps in the flow chart in the embodiment of the present application are displayed sequentially as indicated by the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages, these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order is not necessarily sequential Instead, it may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

It should be noted that in this article, step codes such as 110 and 120 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantive limitation on the order. Those skilled in the art may, during specific implementation, First execute 120 and then execute 110, etc., but these should be within the protection scope of this application.

In the following description, the use of suffixes such as 'module', 'part' or 'unit' for denoting elements is only for facilitating the description of the present application and has no specific meaning by itself. Therefore, 'module', 'part' or 'unit' may be used in combination.

In order to better understand the embodiments of the present application, the following introduces the technical terms involved in the embodiments of the present application:

A scheduling request (Scheduling Request, SR) is a way for a terminal device (User Equipment, UE) to apply for resources from the network side for new data transmission. The SR message sent by the UE is transmitted through a physical uplink control channel (Physical Uplink Control Channel, PUCCH) control channel. After the network side successfully decodes the SR message of a certain UE, it may or may not allocate RB resources to the UE through downlink control information (Downlink Control Information, DCI). In many cases, the UE needs to send SR messages multiple times in order to obtain uplink resources. In the embodiment of the present application, after the UE sends the SR message, the UE may be triggered to enter the wake-up state (also called the active state). A UE in an awake state can monitor a physical downlink control channel (Physical Downlink Control Channel, PDCCH), and the PDCCH can include the above-mentioned DCI, and the DCI can enable the UE to obtain RB resources to send uplink data. After the UE enters the wake-up state, it can start a timer, and wait for the uplink scheduling of the network device during the running of the timer. If the timer expires and has not received the scheduling from the base station, the UE can send the SR message again. In this embodiment of the application, the terminal device can send an SR message when it is in a dormant state. After sending the SR message, it can start a timer and enter the wake-up state to monitor the corresponding PDCCH; when the timer runs overtime, The terminal device can enter the dormant state.

Discontinuous reception (Discontinuous Reception, DRX) is a packet-based data flow that is usually bursty, and there is data transmission for a period of time, but there is no data transmission for a long period of time in the next period. When there is no data transmission, the power consumption can be reduced by stopping receiving the PDCCH (at this time, the PDCCH blind detection will be stopped), thereby improving the battery life. FIG. 1 is a schematic diagram of a discontinuous receiving cycle. The period marked "On Duration" is the period during which the UE monitors the PDCCH, and during this period, the UE is in an awake state. The time marked "Opportunity for DRX" is the DRX sleep time, that is, the time when the UE enters the sleep state and does not monitor the PDCCH in order to save power. It can be seen from Figure 1 that the longer the time for DRX dormancy, the lower the power consumption of the UE, but correspondingly, the delay of service transmission will also increase. It should be noted that the wake-up state may be an On Duration state or a DRX ON state. Among them, the OnDuration state can be controlled by the duration timer (Drx-OnDurationTimer), and the DRX ON state can be Drx-OnDurationTimer, inactivity timer Drx-InactivityTimer, discontinuous reception downlink retransmission timer (Drx-RetransmissionTimerDL) 1. Controlled by one or more timers in the discontinuous reception uplink retransmission timer (Drx-RetransmissionTimerUL).

SR Prohibit Timer (SR-ProhibitTimer) is used to control the frequency of SR messages transmitted in PUCCH. When the timer is running, SR messages cannot be sent. Once the timer expires, UE needs to resend SR messages. . Wherein, the running duration of the SR-ProhibitTimer timer can be configured by Radio Resource Control (RRC).

In order to better understand the embodiment of the present application, the applicable network architecture of the embodiment of the present application will be described below.

Please refer to FIG. 2 . FIG. 2 is a schematic diagram of a wireless communication network architecture provided by an embodiment of the present application. As shown in FIG. 2, the network architecture may include network equipment and terminal equipment, and the terminal equipment establishes a connection with the network equipment through a serving cell. Wherein, the serving cell may include one or more channels as a data transmission medium between the network device and the terminal device, such as a physical downlink control channel (Physical Downlink Control Channel, PDCCH), a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), Physical Uplink Shared Channel (Physical Uplink Control Channel, PUSCH) and so on. The network device can allocate wireless resources to the terminal device for service transmission between the network device and the terminal device.

It should be noted that the technical solution of the present invention is applicable to the 5th generation mobile communication (5th Generation, 5G) communication system, also applicable to 4G, 3G communication systems, and also applicable to various new communication systems in the future, such as 6G , 7G, in-vehicle short-distance communication system, etc. The technical solution of the present invention is also applicable to different network architectures, including but not limited to relay network architecture, dual link architecture, vehicle-to-everything communication architecture, in-vehicle short-distance communication architecture and other architectures.

The network device involved in the embodiment of the present application may also be referred to as an access network device, which is an entity on the network side for transmitting or receiving signals, and can be used to link received air frames with Internet Protocol (Internet Protocol , IP) packets are converted to each other, acting as a router between the terminal device and the rest of the access network, which may include an IP network, etc. Access network devices can also coordinate attribute management for the air interface. For example, the access network device can be an eNB in LTE, or a New Radio Controller (NR controller), a gNB in a 5G system, a centralized network element (Centralized Unit), or a The new wireless base station can be a radio remote module, a micro base station, a relay (Relay), a distributed network element (DistributedUnit), a receiving point (Transmission Reception Point, TRP) or a transmission point (TransmissionPoint , TP), may be a G node in the in-vehicle short-distance communication system or any other wireless access device, but this embodiment of the application is not limited thereto.

A base station (base station, BS) in this embodiment of the present application may also be referred to as a base station device, and is a device deployed in a radio access network (RAN) to provide a wireless communication function. For example, equipment providing base station functions in 2G networks includes base transceiver stations (BTS), equipment providing base station functions in 3G networks includes Node B (NodeB), and equipment providing base station functions in 4G networks includes evolved Node B (evolved NodeB, eNB), in wireless local area networks (wireless local area networks, WLAN), the device that provides the base station function is the access point (access point, AP), in 5G new wireless (New Radio, NR) The device gNB that provides base station functions, and the node B (ng-eNB) that continues to evolve, in which gNB and the terminal use NR technology for communication, and the ng-eNB and the terminal use E-UTRA (Evolved Universal Terrestrial Radio Access) technology For communication, both gNB and ng-eNB can be connected to the 5G core network. The base station in the embodiment of the present application also includes devices that provide base station functions in future new communication systems, and the like.

The terminal in the embodiment of the present application may refer to various forms of user equipment (user equipment, UE), access terminal, user unit, user station, mobile station, mobile station (mobile station, built as MS), remote station, remote terminal , mobile equipment, user terminal, terminal equipment, wireless communication equipment, user agent or user device. The terminal device can also be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the future 5G network or terminals in the future evolution of the Public Land Mobile Network (PLMN) equipment, etc., which are not limited in this embodiment of the present application.

In order to reduce power consumption when a terminal device makes a scheduling request to a network device, an embodiment of the present application provides a scheduling request method and device. The scheduling request method and device provided in the embodiment of the present application will be further introduced in detail below.

Please refer to FIG. 3 . FIG. 3 is a schematic flowchart of a method for scheduling a request according to an embodiment of the present application. The scheduling request method includes the following operations 310 to 340 . The execution subject of the method shown in FIG. 3 may be a terminal device, or a chip in the terminal device. When the terminal device executes the process shown in Figure 3, the following steps may be included:

310. Start the first timer.

Wherein, the first timer may include but not limited to one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

It should be noted that, during the running of the first timer, the terminal device is in the DRX ON state. The running duration of the first timer may be the union of the respective running time periods of the above one or more timers. For example, the first timer includes OnDurationTimer and InactivityTimer, the running time of OnDurationTimer is from the 1st to the 10th second, and the running time of the InactivityTimer is from the 8th to the 12th second, then the running time of the first timer is the first From 1 second to the 12th second, correspondingly, the terminal device is always in the DRX ON state during the period from the 1st second to the 12th second.

In this embodiment of the present application, the network device may periodically configure SR resources for the terminal device, and the terminal device may send an SR message to the access network device through the SR resource. For the terminal device, the SR resource is valid during the running of the first timer.

320. Send a scheduling request SR message before the running of the first timer ends.

Specifically, the terminal device may send the SR message to the network device through the SR resource within the SR sending window. Wherein, within the SR sending window, the SR resource is also valid.

In a possible implementation manner, the starting time of the SR sending window may be before the running starting time of the first timer. FIG. 4 is a schematic diagram of sending an SR message within an SR sending window. As in 4, the SR transmission window is located before the start time of the first timer. At this time, the terminal device is in the DRX OFF state, but the SR resources in the SR transmission window are valid at this time. Therefore, the terminal device can transmit The SR message is sent through the SR resource within the window. Moreover, the terminal device can send the SR message at any time within the SR sending window.

Wherein, in this implementation manner, the SR message is sent before the running start time of the first timer, and the terminal device needs to wait for the first timer to start running before monitoring the PDCCH. In this way, the terminal equipment can monitor the PDCCH only in the DRX ON state, which reduces certain energy consumption of the terminal. In addition, the SR message is sent before the start time of the first timer, and the terminal device may monitor the PDCCH without waiting for the first timer to start running, that is, start monitoring the PDCCH after sending the SR in the sending window. Specifically, whether to monitor the PDCCH after the first timer starts may depend on the configuration of the base station or the agreement in advance.

Optionally, the starting moment of the SR sending window may be during the running of the first timer. FIG. 5 is another schematic diagram of sending an SR message within the SR sending window. In FIG. 5 , the SR sending window is in the running process of the first timer. At this time, the terminal device is in the DRX ON state, and the terminal device can start monitoring the PDCCH immediately after sending the SR message.

330. Start the second timer.

Wherein, the running start time of the second timer is after the time when the terminal device sends the SR message, and the sending of the SR message by the terminal device may trigger the running of the second timer. The second timer may be one or more of the following timers: a scheduling request prohibit timer (SR-ProhibitTimer), and a scheduling request sending timer (SR-TransmissionTimer). The SR-TransmissionTimer may be a newly configured timer. Wherein, whether the second timer needs to run may be configured by the network device through signaling, and during the running of the second timer, the terminal device stops sending the SR message.

340. If the running of the second timer ends and the running of the first timer ends, stop sending the SR message.

In a possible implementation manner, if the second timer ends but the first timer does not end, the terminal device sends the SR message again.

Optionally, for the situation shown in FIG. 4 , the SR sending window is located before the running start time of the first timer, and the terminal device sends an SR message within the SR sending window, thereby triggering the second timer to send an SR message in the SR sending window. The terminal device starts monitoring the PDCCH at the starting time of the first timer running. When the second timer finishes running during the running of the first timer, the terminal device does not monitor the uplink grant in the PDCCH, indicating that the network device has no available resources to allocate to the terminal before the running of the second timer ends equipment. Since the terminal device is still in the DRX ON state at this time, the terminal device can send the SR message again, request the uplink authorization from the network device again, and monitor the PDCCH again. At the same time, sending the SR message again may trigger the start of the second timer again. When the running of the first timer ends, the terminal device also stops monitoring the PDCCH before the running of the second timer ends.

Optionally, for the situation shown in Figure 5, the SR sending window is located during the start of the first timer, and the terminal device sends an SR message within the SR sending window, thereby triggering the second timer to start the SR sending window start within. Since it has entered the DRX ON state at this time, the terminal device can monitor the PDCCH immediately after sending the SR message. When the second timer ends, but the first timer does not end, it means that the network device has no available resources to allocate to the terminal device before the second timer ends, and the terminal device can send the SR message again to request Authorize uplink, and monitor PDCCH again. When the first timer finishes running, the terminal device stops monitoring the PDCCH.

When the second timer finishes running and the first timer also finishes running, the terminal device is already in the DRX OFF state, no longer sends SR messages, and no longer monitors PDCCH, and the terminal device needs to wait for the next SR sending window before sending SR news.

In a possible implementation manner, when the network device configures through signaling that the second timer does not need to be started, the terminal device may start the third timer after sending the SR message. The third timer is different from the second timer. When the third timer is in the running state and the first timer is also in the running state, the terminal device can monitor the PDCCH. When the third timer ends and the first timer is still running, if the terminal device does not hear the uplink grant of the PDCCH, it resends the SR message. When the first timer expires, the terminal device stops monitoring the PDCCH. When both the third timer and the first timer run overtime, the terminal device stops sending the SR message.

In a possible implementation manner, when the terminal device is not configured with an SR sending window, the terminal device may send the SR message during the running of the first timer, that is, in the DRX ON state.

Optionally, after sending the SR message, the terminal device may start the second timer, and since it has entered the DRX ON state at this time, the terminal device may monitor the PDCCH immediately after sending the SR message. When the second timer ends but the first timer ends, the terminal device can send the SR message again and keep monitoring the PDCCH. When the first timer finishes running, the terminal device stops monitoring the PDCCH. When the second timer finishes running and the first timer also finishes running, the terminal device is already in the DRX OFF state, no longer sends SR messages, and no longer monitors PDCCH, and the terminal device needs to wait for the next SR sending window before sending SR message.

Optionally, after sending the SR message, the terminal device may start a third timer, and when the third timer is in the running state and the first timer is also in the running state, the terminal device may monitor the PDCCH. When the third timer ends and the first timer is still running, if the terminal device does not hear the uplink grant of the PDCCH, it resends the SR message. When the first timer expires, the terminal device stops monitoring the PDCCH. When the third timer finishes running and the first timer also finishes running, the terminal device is already in the DRX OFF state, no longer sends SR messages, and no longer monitors PDCCH, and the terminal device needs to wait for the next SR sending window before sending SR news.

Through the embodiment of the present application, the terminal device can send the SR message within the SR sending window, and the SR sending window can be located before the running start time of the first timer, or during the running process of the first timer. After the terminal device sends the SR message, if the first timer is in the running state, it can monitor the uplink grant of the PDCCH. After the terminal device sends the SR message, it may be triggered to start the second timer. When the running of the second timer ends during the running of the first timer, and the terminal device does not listen to the uplink grant of the PDCCH, it means that the network device has no available resources to allocate to the terminal device at this time, so the terminal device can send again SR message to re-request uplink scheduling. And when both the first timer and the second timer run to the end, and the terminal device still does not monitor the uplink scheduling of the PDCCH, the terminal device stops sending the SR message, and needs to wait for the next SR sending window before resending the SR message. In this method, the terminal device can only send the SR message when the first timer is running, and can only monitor the PDCCH during the running of the first timer, instead of sending the SR message and monitoring the PDCCH at any time. Therefore, the method can reduce the power consumption of the terminal device when requesting uplink scheduling from the network device.

Please refer to FIG. 6. FIG. 6 is a schematic diagram of units of a communication device provided in an embodiment of the present application. The communication device shown in FIG. 6 may be used to perform some or all of the functions in the method embodiment described in FIG. 3 above. The device may be a terminal device, or a device in the terminal device, or a device that can be matched with the terminal device.

The logical structure of the device may include: a processing unit 610 and a communication unit 620, wherein, when the device is applied to a terminal device:

a processing unit 610, configured to start a first timer;

A communication unit 620, configured to send a scheduling request SR message before the end of the first timer;

The processing unit 610 is further configured to start a second timer;

The processing unit 610 is further configured to stop sending the SR message if the second timer ends and the first timer ends.

In a possible implementation manner, the communication unit 620 is further configured to send an SR message within a scheduling request SR sending window.

In a possible implementation manner, the starting time of the SR sending window is before the running starting time of the first timer or during the running of the first timer.

In a possible implementation manner, the above-mentioned communication unit 620 is further configured to resend the SR message if the running of the second timer ends and the running of the first timer has not ended.

In a possible implementation manner, the first timer includes one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

In a possible implementation manner, the second timer includes one or more of the following timers:

Scheduling request prohibition timer SR-ProhibitTimer;

Scheduling request transmission timer SR-TransmissionTimer.

Please refer to FIG. 7. FIG. 7 is a simplified schematic diagram of a physical structure of a communication device provided by an embodiment of the present application. The communication device includes a processor 710, a memory 720, and a communication interface 730. The processor 710, the memory 720, and the communication interface 730 Connected via one or more communication buses. The communication device may be a chip, or a chip module or the like.

The processor 710 is configured to support the communication device to execute the corresponding functions of the above method in FIG. 3 . It should be understood that, in the embodiment of the present application, the processor 710 may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP), Application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

The memory 720 is used to store program codes and the like. The memory 720 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DRRAM).

The communication interface 730 is used to send and receive data, information or messages, etc., and may also be described as a transceiver, a transceiver circuit, and the like.

In the embodiment of the present application, when the communication device is a terminal device, the processor 710 calls the program code stored in the memory 720 to perform the following operations:

The processor 710 invokes the program code stored in the memory 720 to start the first timer;

The control communication interface 730 sends a scheduling request SR message before the end of the first timer;

The processor 710 invokes the program code stored in the memory 720 to start the second timer;

The processor 710 calls the program code stored in the memory 720 and stops sending the SR message if the running of the second timer ends and the running of the first timer ends.

In a possible implementation manner, the control communication interface 730 sends the SR message within the scheduling request SR sending window.

In a possible implementation manner, the starting time of the SR sending window is before the running starting time of the first timer or during the running of the first timer.

In a possible implementation manner, the control communication interface 730 resends the SR message if the running of the second timer ends and the running of the first timer has not ended.

In a possible implementation manner, the first timer includes one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

In a possible implementation manner, the second timer includes one or more of the following timers:

Scheduling request prohibition timer SR-ProhibitTimer;

Scheduling request transmission timer SR-TransmissionTimer.

The embodiment of the present application also provides a chip, which may also be included in a chip module, wherein the chip is connected to a transceiver.

When the chip is applied to terminal equipment:

The chip is used to start the first timer;

The chip is also used to control the transceiver to send a scheduling request SR message before the end of the first timer;

The chip is also used to start the second timer;

The chip is also configured to stop sending the SR message if the second timer ends and the first timer ends.

In a possible implementation manner, the chip is further configured to control the transceiver to send the SR message within the scheduling request SR sending window.

In a possible implementation manner, the starting time of the SR sending window is before the running starting time of the first timer or during the running of the first timer.

In a possible implementation manner, the chip is further configured to control the transceiver to resend the SR message if the running of the second timer ends and the running of the first timer has not ended.

In a possible implementation manner, the first timer includes one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

In a possible implementation manner, the second timer includes one or more of the following timers:

Scheduling request prohibition timer SR-ProhibitTimer;

Scheduling request transmission timer SR-TransmissionTimer.

Please refer to FIG. 8. FIG. 8 is a simplified schematic diagram of a chip module provided by an embodiment of the present application. The chip module includes a storage device 810, a chip 820, and a communication interface 830. When the chip module is applied to the second network element when, where:

The chip 820 is used to start the first timer;

The chip 820 is also used to control the communication interface 830 to send a scheduling request SR message before the end of the first timer;

The chip 820 is also used to start the second timer;

The chip 820 is also configured to stop sending the SR message if the running of the second timer ends and the running of the first timer ends.

In a possible implementation manner, the chip 820 is also used to control the communication interface 830 to send the SR message within the scheduling request SR sending window.

In a possible implementation manner, the starting time of the SR sending window is before the running starting time of the first timer or during the running of the first timer.

In a possible implementation manner, the chip 820 is further configured to control the communication interface 830 to resend the SR message if the running of the second timer ends and the running of the first timer has not ended.

In a possible implementation manner, the first timer includes one or more of the following timers:

Duration timer Drx-OnDurationTimer;

Inactive timer Drx-InactivityTimer;

Discontinuous reception downlink retransmission timer Drx-RetransmissionTimerDL;

Discontinuous reception uplink retransmission timer Drx-RetransmissionTimerUL.

In a possible implementation manner, the second timer includes one or more of the following timers:

Scheduling request prohibition timer SR-ProhibitTimer;

Scheduling request transmission timer SR-TransmissionTimer.

It should be noted that, in the foregoing embodiments, descriptions of each embodiment have their own emphases, and for parts that are not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

The steps in the method of the embodiment of the present invention can be adjusted, merged and deleted according to actual needs.

The units in the processing device in the embodiment of the present invention can be combined, divided and deleted according to actual needs.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. A computer can be a general purpose computer, special purpose computer, computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, etc. integrated with one or more available media. Usable media may be magnetic media, (eg, floppy disk, memory disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), among others.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit it; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the application. scope.

Claims (11)

1. A method of scheduling, comprising:

starting a first timer;

sending a Scheduling Request (SR) message before the first timer runs out;

starting a second timer;

and if the second timer runs and the first timer runs, stopping sending the SR message.

2. The method of claim 1, further comprising:

and transmitting the SR message in a Scheduling Request (SR) transmission window.

3. The method of claim 2, wherein a starting time of the SR transmission window is before or during a starting time of the first timer operation.

4. The method according to any one of claims 1 to 3, further comprising:

and if the second timer runs to the end and the first timer runs to the end, retransmitting the SR message.

5. The method of any one of claims 1 to 4, wherein the first timer comprises one or more of:

a duration timer Drx-OnDurationTimer;

an inactivity timer Drx-inactivity timer;

a discontinuous reception downlink retransmission timer Drx-retransmission timerdl;

a Drx-retransmission timer ul is received discontinuously.

6. The method of any of claims 1 to 4, wherein the second timer comprises one or more of the following timers:

a scheduling request forbids a timer SR-ProhibitTimer;

the scheduling request sends a timer SR-TransmissionTimer.

7. A communications apparatus, comprising:

the processing unit is used for starting a first timer;

a communication unit, configured to send a scheduling request, SR, message before the first timer runs out;

the processing unit is further configured to start a second timer;

the processing unit is further configured to stop sending the SR message if the second timer runs end and the first timer runs end.

8. A communications device comprising a processor, a memory for storing a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the scheduling method of any one of claims 1 to 6.

9. A computer-readable storage medium, having stored thereon one or more instructions adapted to be loaded by a processor and to perform the scheduling method of any of claims 1 to 6.

10. A chip for performing the scheduling method of any one of claims 1 to 6.

11. A chip module, characterized in that the chip module comprises a storage device, a chip and a communication interface, wherein the chip is used for executing the scheduling method according to any one of claims 1 to 6.

Images