Wireless communication method and terminal equipment

Abstract

The invention provides a wireless communication method and terminal equipment. The method comprises the following steps that: if a first condition is met, terminal equipment performs physical downlink control channel (PDCCH) monitoring or skips PDCCH monitoring; wherein the first condition is associated with one or more of the following conditions: the terminal device receives indication information used for indicating the terminal device to skip PDCCH (Physical Downlink Control Channel) monitoring; ending the first window, wherein the first window is a response window corresponding to the first random access process; and cancelling the first scheduling request (SR). In the embodiments of the present application, it is stipulated that a terminal device performs PDCCH monitoring or skips PDCCH monitoring when a first condition is satisfied. According to the invention, the rationality of the specified terminal equipment for carrying out PDCCH monitoring or skipping the PDCCH monitoring is improved, that is, the power consumption of the terminal equipment is reduced on the premise of improving the possibility of receiving the PDCCH by the terminal equipment.

Description

Wireless communication method and terminal device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method and terminal equipment. Background Art

[0002] At present, the communication protocol has reached a consensus on the physical downlink control channel (PDCCH) skipping mechanism in the random access process and the scheduling request (SR) process. However, the behavior of the terminal device after the introduction of the PDCCH skipping mechanism in other communication processes has not been discussed. If, after the PDCCH skipping mechanism is introduced in other communication processes, the terminal device follows the instructions of the network device and skips PDCCH monitoring during the PDCCH skipping period, the terminal device may not be able to receive the PDCCH sent by the network device, resulting in communication failure. On the contrary, if, after the PDCCH skipping mechanism is introduced in other communication processes, the terminal device does not follow the instructions of the network device and continues to monitor the PDCCH during the PDCCH skipping period, it may cause the terminal device to consume more power.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and terminal device. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a wireless communication method is provided, including: if a first condition is met, the terminal device performs physical downlink control channel PDCCH monitoring or skips PDCCH monitoring; wherein, the first condition is associated with one or more of the following: the terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; the first window ends, the first window is a response window corresponding to the first random access process; and the first scheduling request SR is canceled.

[0006] According to a second aspect, a terminal device is provided, comprising: a processing unit, configured to perform physical downlink control channel PDCCH monitoring or skip PDCCH monitoring if a first condition is met; wherein the first condition is associated with one or more of the following: the terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; the first window ends, the first window being a response window corresponding to the first random access process; and the first scheduling request SR is canceled.

[0007] In a third aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0008] In a fourth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device. In another possible design, the system may also include other devices that interact with the terminal device in the solution provided in the embodiment of the present application.

[0009] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal device) to execute some or all of the steps in the methods of the above aspects.

[0010] In a sixth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0011] In the seventh aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0012] In an embodiment of the present application, it is specified that a terminal device performs PDCCH monitoring or skips PDCCH monitoring when a first condition is met, where the first condition is associated with one or more of the following: the terminal device receives instruction information for instructing the terminal device to skip PDCCH monitoring; the first window ends; and the first SR is canceled. This helps to improve the rationality of specifying that the terminal device performs PDCCH monitoring or skips PDCCH monitoring, that is, to reduce the power consumption of the terminal device while increasing the possibility of the terminal device receiving the PDCCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG1 is a wireless communication system 100 used in an embodiment of the present application.

[0014] FIG2 is a flow chart of a contention-based random access method.

[0015] FIG3 is a flow chart of a non-contention-based random access method.

[0016] FIG4 is a flow chart of a two-step random access method.

[0017] FIG5 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0018] FIG6 is a schematic diagram of a terminal device performing PDCCH monitoring in an embodiment of the present application.

[0019] FIG7 is a schematic diagram of a terminal device performing PDCCH monitoring in another embodiment of the present application.

[0020] FIG8 is a schematic diagram of a terminal device skipping PDCCH monitoring in an embodiment of the present application.

[0021] FIG9 is a schematic diagram of a terminal device performing PDCCH monitoring in another embodiment of the present application.

[0022] FIG10 is a schematic diagram of a terminal device skipping PDCCH monitoring in another embodiment of the present application.

[0023] FIG11 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0024] FIG12 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] The technical solution of the present application will be described below with reference to the accompanying drawings. For ease of understanding, the communication process involved in the embodiment of the present application will be described below with reference to Figures 1 to 4.

[0026] Figure 1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0027] FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0028] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0029] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0030] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0031] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0032] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0033] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0034] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0035] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0036] Discontinuous reception (DRX)

[0037] To reduce power consumption in terminal devices, both LTE and NR systems have introduced the DRX mechanism. This allows terminal devices to enter a discontinuous reception state instead of keeping their receivers powered on when not receiving data, thereby saving power. The DRX mechanism configures a DRX cycle for terminal devices in a radio resource control (RRC) connected state. A DRX cycle consists of an "on duration" and an "opportunity for DRX." During the on duration, the terminal device monitors and receives downlink channels and signals, including the PDCCH. During the inactive duration, the terminal device does not receive downlink channels and signals, such as the PDCCH, to reduce power consumption.

[0038] In 5G NR, network equipment can configure DRX configuration for each MAC entity of a terminal device. In some implementations, the DRX configuration may include one or more parameters described below.

[0039] The DRX activation period timer (drx-onDurationTimer) is used to determine the duration of the terminal device waking up at the beginning of a DRX cycle.

[0040] DRX slot offset (drx-SlotOffset) is used to determine the delay for the terminal device to start the DRX activation period timer.

[0041] The DRX inactivity timer (drx-InactivityTimer) is used to determine the duration for which the terminal device can continue to monitor the PDCCH after receiving a PDCCH indicating an uplink initial transmission or a downlink initial transmission.

[0042] The DRX downlink retransmission timer (drx-RetransmissionTimerDL) is used to determine the maximum duration that a terminal device monitors the PDCCH indicating downlink retransmission scheduling. Typically, each downlink hybrid automatic repeat request (HARQ) process, except the broadcast HARQ process, corresponds to a DRX downlink retransmission timer.

[0043] The DRX uplink retransmission timer (drx-RetransmissionTimerUL) is used to determine the maximum duration that a terminal device monitors the PDCCH indicating uplink retransmission scheduling. Typically, each uplink HARQ process corresponds to a DRX uplink retransmission timer.

[0044] The DRX long cycle start offset (drx-LongCycleStartOffset) is used to configure the DRX long cycle and the subframe offsets at which the DRX long cycle and DRX short cycle start.

[0045] The DRX short cycle start offset (drx-ShortCycle) is used to configure the DRX short cycle and is usually an optional configuration.

[0046] The DRX short cycle timer (drx-ShortCycleTimer) is used to determine the duration of the terminal device in the DRX short cycle (and not receiving any PDCCH). Generally, it is an optional configuration.

[0047] The DRX-HARQ-downlink round trip time (RTT) timer (drx-HARQ-RTT-TimerDL) is used to determine the minimum waiting time required for a terminal device to receive a PDCCH indicating downlink scheduling. Typically, each downlink HARQ process other than the broadcast HARQ process can correspond to a DRX-HARQ-downlink round trip time timer.

[0048] The DRX-HARQ-Uplink Round Trip Time (drx-HARQ-RTT-TimerUL) is used to determine the minimum waiting time required for a terminal device to receive a PDCCH indicating uplink scheduling. Typically, each uplink HARQ process corresponds to one DRX-HARQ-Uplink Round Trip Time timer.

[0049] In some scenarios, if a terminal device is configured with DRX, the terminal device needs to monitor the PDCCH during the DRX activation period. In some implementations, the DRX activation period includes the following situations:

[0050] In case 1, any one of the five timers, namely, the DRX active period timer, the DRX inactive period timer, the DRX uplink retransmission timer, the DRX uplink retransmission timer, and the random access contention resolution timer (ra-ContentionResolutionTimer), is running.

[0051] Case 2: An SR is sent on the physical uplink control channel (PUSCH) and is in a pending state, or in other words, there is an SR ready to be sent on the PUSCH.

[0052] Case 3: In a contention-based random access process, the terminal device has not received an initial transmission indicated by a PDCCH scrambled by a cell radio network temporary identifier (C-RNTI) after successfully receiving a random access response.

[0053] Random access process

[0054] Currently, there are two types of random access methods: contention-based random access and non-contention-based random access. These two random access methods are described below with reference to FIG2 and FIG3 .

[0055] FIG2 is a flowchart of a contention-based random access method, which includes steps S210 to S240.

[0056] In step S210, the terminal device sends a message 1 (Msg1) in a random access process, also known as a "random access request," to the network device. The message 1 includes a preamble.

[0057] The terminal device can select a random access channel (RACH) resource and a preamble, and send the selected preamble on the selected resource. The RACH resource may also be referred to as a physical random access channel (PRACH) resource.

[0058] The network device may send RACH configuration information to the terminal device in the form of broadcast. The RACH configuration information may include configuration information of RACH time-frequency resources and configuration information of the initial preamble root sequence.

[0059] The configuration information of the RACH time domain resources can be indicated by a RACH configuration index. The RACH configuration index may include at least one of the repetition period of the RACH resources, the number of RACH occasions (RO) contained in a RACH resource repetition period, and the duration of each RO. The configuration information of the RACH frequency domain resources may include a RACH starting frequency domain resource index and the number of RACH resources that can be frequency-division multiplexed at the same time (i.e., the number of continuous RACH frequency domain resources). A continuous frequency domain resource segment can be determined by the configuration information of the RACH frequency domain resources. The starting preamble root sequence can be broadcast by the cell, and each cell can broadcast one preamble root sequence. Based on the configured starting preamble root sequence, the preamble set available in the cell can be obtained by cyclic shift.

[0060] The configuration information of RACH can be carried in the system message, that is, the network device can send the configuration information of RACH through the system message. The system message may include a synchronization signal block (SSB), and the network device may broadcast the SSB to the terminal device. The SSB may be a CD-SSB. The SSB may include the master information block MIB and the system information block of the resident cell. The system information block may include SIB1 and other SIBs. SIB1 may indicate the relevant configuration information of the initial BWP for the initial access of the terminal device. The configuration information may include the initial uplink BWP and the initial downlink BWP. In the initial uplink BWP, the network device can configure random access resources for the terminal device for initial access. There is a corresponding relationship between the random access resource and the SSB. For example, the network device can control the terminal device's selection of random access resources by configuring a reference signal receiving power (RSRP) threshold. When the random access process is triggered, the terminal device can select an SSB whose RSRP measurement value meets the RSRP threshold, and select the corresponding random access resource to send the preamble code according to the corresponding relationship between the SSB and the random access resource.

[0061] In step S220, the network device sends Msg2 to the terminal device, which may also be called a random access response (RAR). The Msg2 may be carried by the PDCCH.

[0062] After sending Msg1, the terminal device may open a random access response time window (also known as a RAR window) and monitor the PDCCH scrambled by the random access-radio network temporary identifier (RA-RNTI) within the RAR window.

[0063] Typically, the RA-RNTI is related to the time-frequency resources of the RACH used by the terminal device to send Msg 1. After receiving the PDCCH, the terminal device can use the RA-RNTI to decode the PDCCH.

[0064] Msg2 may also include a preamble sent by the terminal device. If the terminal device receives a PDCCH scrambled with RA-RNTI and Msg2 contains the preamble sent by itself, the terminal device may consider that the random access response has been successfully received.

[0065] After the terminal device successfully receives the PDCCH, the terminal device can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH, wherein the PDSCH contains the RAR. The RAR can contain multiple information. For example, the subheader of the RAR can contain a backoff indicator (BI), which can be used to indicate the backoff time for retransmitting Msg1; the random access preamble identification (RAPID) in the RAR indicates the preamble index to which the network device responds to the received data; the payload in the RAR can contain a timing advance group (TAG), which can be used to adjust the uplink timing; the RAR can also include an uplink grant (UL grant) for scheduling the uplink resource indication of Msg3; the RAR can also include a temporary cell-radio network temporary identifier (C-RNTI). For a terminal device that is initially accessing, the terminal device can use the temporary C-RNTI to decode the PDCCH of Msg4.

[0066] Step S230: The terminal device sends Msg3 to the network device. The terminal device may send Msg3 on the uplink grant scheduled by the network device. The Msg3 may also be called a radio resource control (RRC) connection establishment request message.

[0067] The Msg3 is mainly used to inform the network device of the event that triggered the random access process. For example, if it is an initial random access process, the terminal device can carry the UE identity (ID) and establishment cause in the Msg3. If it is an RRC reestablishment, the terminal device can carry the connected UE identity and establishment cause in the Msg3.

[0068] Step S240: The network device sends Msg4 to the terminal device.

[0069] The Msg4 has two functions, one is for contention conflict resolution, and the other is to send an RRC configuration message to the terminal device. If the terminal device carries C-RNTI in Msg3, Msg4 is scheduled using the PDCCH scrambled by the C-RNTI. Accordingly, the terminal device can use the C-RNTI in Msg3 to decode the PDCCH to obtain Msg4. If the terminal device does not carry C-RNTI in Msg3, such as initial access, Msg4 can be scheduled using the PDCCH scrambled by a temporary C-RNTI. Accordingly, the terminal device can use the temporary C-RNTI in Msg2 to decode the PDCCH to obtain Msg4. After successfully decoding the PDCCH, the terminal device obtains the PDSCH carrying Msg4. The terminal device can compare the common control channel (CCCH) service data unit (SDU) in the PDSCH with the CCCH SDU in Msg3. If the two are the same, it means that the contention resolution is successful.

[0070] Figure 3 is a flow chart of a non-contention-based random access method, which includes steps S310 to S330.

[0071] In step S310, the network device sends preamble configuration information to the terminal device, where the configuration information includes the preamble and RACH resources required in the random access process.

[0072] In step S320, the terminal device may send Msg1 to the network device according to the preamble configuration information, that is, the terminal device may send the preamble to the network device on the RACH resource.

[0073] In step S330, the network device sends Msg2 to the terminal device, and the Msg2 may include RAR. After the terminal device receives the RAR, it indicates that the random access process is completed.

[0074] The random access process described above demonstrates that its primary purpose is to achieve uplink synchronization between the terminal and the network. During random access, the network receives the RACH time-frequency resources used by the terminal to transmit the preamble. This information allows the network to determine the terminal's initial time advance (TA) based on the preamble's transmission and reception times, and communicates this information to the terminal via Msg2.

[0075] Later, based on the contention-based four-step random access, NR further introduced a contention-based two-step random access process, which only includes two signaling interactions.

[0076] As shown in Figure 4, in step S410, the first message sent by the terminal device to the network device is called message A (MsgA). In some implementations, message A includes a preamble transmitted on a random access resource and load information transmitted on a PUSCH, which may correspond to messages 1 and 3 in the contention-based four-step random access process.

[0077] In step S420, the network device sends a message B (MsgB) to the terminal device. In some implementations, the message B may correspond to Msg2 and Msg4 in the contention-based four-step random access process.

[0078] Typically, after a terminal device sends message A, it may run a message B response window, where the message B response window is used to detect message B.

[0079] SR process

[0080] The terminal device requests uplink resources from the network device through the SR. The network device does not know when the terminal device needs to send uplink data, that is, it does not know when the terminal device will send the SR. Therefore, the network device can allocate PUCCH resources for the terminal device to transmit SR periodically, and then detect whether there is an SR report on the allocated SR resource.

[0081] For the SR process triggered by the buffer status report (BSR), the SR can be used by the terminal device to request the network device for uplink resources for transmitting the BSR. Correspondingly, the BSR is used by the terminal device to request the network device for uplink resources for transmitting uplink data to be transmitted.

[0082] Currently, there are many triggering conditions for SR. For example, SR may be triggered by a logical channel (for example, the arrival of logical channel data triggers a BSR, and the BSR has no uplink resources). For another example, SR may be triggered by beam failure recovery (BFR). For another example, SR may be triggered by consistent listen before talk (LBT) failure recovery. For another example, SR may be triggered by a positioning measurement gap activation / deactivation request. For another example, SR may be triggered by TA reporting in a non-terrestrial network (NTN) system.

[0083] Typically, once triggered, an SR is in a pending state, which can be called a "pending SR, or pending SR," until the pending SR is canceled or sent. For ease of understanding, the following describes a case where a pending SR is canceled.

[0084] In some scenarios, before the assembly of a medium access control (MAC) protocol data unit (PDU), all pending SRs triggered according to the BSR procedure (communication protocol clause 5.4.5) shall be canceled and each corresponding SR-prohibit timer shall be stopped when a MAC PDU is transmitted that includes a long or short BSR MAC control element (CE) containing the buffer status up to and including the last event that triggered a BSR (see clause 5.4.5) before the assembly of the MAC PDU. All pending SRs triggered according to the BSR procedure (communication protocol clause 5.4.5) shall be canceled and each SR-prohibit timer shall be stopped when the UL grant can accommodate all pending transmittable data.

[0085] In other scenarios, the MAC entity shall, for each pending SR that is not triggered for the serving cell according to the BSR procedure (Section 5.4.5 of the Communication Protocol), cancel the SR and stop the corresponding SR prohibit timer (if running) when the SR meets the following conditions.

[0086] Condition 1: If the SR is triggered by the Preemptive BSR procedure (see clause 5.4.7) before the MAC PDU component and the MAC PDU containing the relevant Preemptive BSR is transmitted.

[0087] Condition 2: If the SR is triggered by beam failure recovery of a secondary cell (see clause 5.17) and a MAC PDU is transmitted, which includes a MAC CE for BFR containing the beam failure recovery information of the cell.

[0088] Condition 3: If the SR is triggered by beam failure recovery of the BFD-reference signal (RS) set of the serving cell (see Section 5.17), and a MAC PDU is sent, the PDU includes an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE containing the beam failure recovery information of the BFD-RS set of the serving cell.

[0089] Condition 4: If the SR is triggered by beam failure recovery of an SCell (see Section 5.17), and the secondary cell (SCell) is deactivated (see Section 5.9).

[0090] Condition 5: If the SR is triggered by beam failure recovery of a BFD-RS group of an SCell (see Section 5.17), and the SCell is deactivated (see Section 5.9).

[0091] Condition 6: If the SR is triggered by beam failure recovery of a BFD-RS group of an SCell (see Section 5.17), and the SCell is deactivated (see Section 5.9).

[0092] Condition 7: If this SR is triggered by consistent LBT failure recovery of an SCell (see Section 5.21), and a MAC PDU is transmitted, and the MAC PDU contains an LBT failure MAC CE, indicating consistent LBT failure of the SCell.

[0093] Condition 8: If this SR is triggered by a consistent LBT failure recovery of an SCell (see Section 5.21), and all triggered consistent LBT failures of this SCell are canceled.

[0094] PDCCH skipping

[0095] Currently, a PDCCH skipping mechanism has been introduced in communication protocols (e.g., the NR energy saving project of 3GPP Rel-17), whereby a network device can instruct a terminal device to skip PDCCH monitoring during a PDCCH skipping duration by sending an indication message (also known as a "PDCCH skipping indication"). In other words, when a terminal device receives a PDCCH skipping indication, the terminal device should follow the PDCCH skipping indication, i.e., skip PDCCH monitoring during the subsequent PDCCH skipping duration, even if the terminal device is in a DRX activation period during the PDCCH skipping duration.

[0096] Currently, the communication protocol has reached a consensus on the PDCCH skipping mechanism in the random access process and the SR process. In the random access process, if the PDCCH skipping duration indicated by the network device includes the first window (for example, the RAR window and / or the message B response window), the terminal device ignores skipping PDCCH monitoring within the first window, that is, the terminal device needs to monitor the PDCCH within the first window. In the SR process, if the PDCCH skipping duration indicated by the network device includes the PDCCH monitoring period after the terminal device sends the SR, the terminal device monitors the PDCCH during the PDCCH monitoring period.

[0097] As mentioned above, the current communication protocol has reached a consensus on the PDCCH skipping mechanism in the random access process and the SR process. However, the behavior of the terminal device after the introduction of the PDCCH skipping mechanism in other communication processes has not been discussed. If the PDCCH skipping mechanism is introduced in other communication processes, and the terminal device follows the instructions of the network device and skips PDCCH monitoring during the PDCCH skipping period, the terminal device may not be able to receive the PDCCH sent by the network device, resulting in communication failure. Conversely, if the PDCCH skipping mechanism is introduced in other communication processes, and the terminal device does not follow the instructions of the network device and continues to monitor the PDCCH during the PDCCH skipping period, it may cause the terminal device to consume more power.

[0098] Therefore, an embodiment of the present application provides a wireless communication method to specify whether a terminal device skips PDCCH monitoring during other communication processes (e.g., when the first condition described below is met). The following is a schematic flowchart of the wireless communication method according to an embodiment of the present application, described in conjunction with FIG5 . The method shown in FIG5 includes step S510.

[0099] In step S510, if the first condition is met, the terminal device performs PDCCH monitoring or skips PDCCH monitoring.

[0100] In some implementations, the first condition is associated with one or more of the following: the terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; the first window ends; and the first SR is canceled.

[0101] Taking the first condition including the terminal device receiving indication information as an example, the indication information may be, for example, the PDCCH skip indication introduced above. In some implementations, the indication information may instruct the terminal device to skip PDCCH monitoring during the PDCCH skip duration.

[0102] Taking the example of the first condition including the end of the first window, the end of the first window can be understood as the terminal device stopping the running first window. The embodiments of the present application do not limit the triggering conditions for the terminal device to stop running the first window. For example, it can be a triggering condition specified in a known communication protocol or a future communication protocol. This will be described below in Example 1 and is not limited here for the sake of brevity.

[0103] The first window may include a response window corresponding to the first random access process, for example, a random access response window and / or a message B response window. Of course, in the embodiment of the present application, the first window may also be other response windows in the first random access process, and the embodiment of the present application is not limited to this.

[0104] Taking the first condition including the cancellation of the first SR as an example, the embodiment of the present application does not limit the situation in which the first SR is canceled. The situation in which the first SR is canceled can be referred to the above introduction. Of course, in the embodiment of the present application, the situation in which the first SR is canceled can also be any one specified in the future communication protocol.

[0105] As described above, the first condition can be associated with one or more of the situations described above. For ease of understanding, the following describes a scheme in which the first condition includes a combination of multiple situations in conjunction with Example 1 and Example 2. Example 1 describes an example in which the first condition includes the terminal device receiving the above-mentioned indication information in conjunction with the end of the first window. Example 2 describes an example in which the first condition includes the terminal device receiving the above-mentioned indication information in conjunction with the cancellation of the first SR.

[0106] In embodiment 1, the first condition includes that the terminal device receives the indication information and the first window ends, or in other words, the first condition includes that the first window ends within the PDCCH skip duration.

[0107] In some implementations, the PDCCH skip duration indicated by the above indication information may include a time period after the end of the first window. In addition, in the embodiment of the present application, the relationship between the PDCCH skip duration and the first window is not limited. For example, the PDCCH skip duration may include part or all of the time period in the first window, as shown in Figures 6 to 8 below. For another example, the PDCCH skip duration may not include part or all of the time period in the first window.

[0108] As described above, the first window may include a RAR window and a message B response window. The following description will be made by taking the case where the first window is a RAR window or the first window is a message B response window as an example.

[0109] Based on the random access process described above, it can be seen that the message B response window is usually used in a 2-step random access process, and the 2-step random access process is usually for transmitting uplink data. For example, when uplink data to be transmitted reaches a terminal device, and the terminal device is in uplink desynchronization and / or has no available uplink resources, the terminal device can perform random access through a 2-step random access process, and the end of the message B response window indicates the end of the 2-step random access process. However, during the 2-step random access process, the network device cannot indicate the uplink resources to the terminal device. Therefore, after the message B response window ends, the terminal device needs to continue monitoring the PDCCH to obtain uplink resources.

[0110] Therefore, in the embodiment of the present application, after the message B response window ends, in order to enable the terminal device to obtain uplink resources as quickly as possible, the terminal device can perform PDCCH monitoring during the PDCCH skip duration. In other words, the above step S510 may include: if the message B response window ends, the terminal device performs PDCCH monitoring.

[0111] In the embodiment of the present application, the situation in which the message B response window ends is not limited. For ease of understanding, the scheme for the end of the message B response window is introduced below in combination with situation 1 and situation 2. In situation 1, if the terminal device successfully receives message B, the message B response window ends. For example, assume that the terminal device includes a CCCH SDU in message A, and then the terminal device receives an uplink configuration (UL assignment) on the MsgB-RNTI-scrambled PDCCH, and correctly receives the transport block (transport block) carrying message B, wherein message B carries a MAC sub-PDU (successRAR MAC subPDU) indicating successful reception of RAR, and the terminal device contention resolution identity (contention resolution identity) in the MAC sub-PDU matches the CCCH SDU.

[0112] For another example, assume that the terminal device carries C-RNTI MAC CE in message A, and the terminal device receives the uplink configuration on the C-RNTI-scrambled PDCCH, and correctly receives the transport block carrying message B, wherein the MAC PDU in the transport block contains the MAC CE (absolute timing advance command MAC CE) of the absolute timing advance command. At this time, the terminal device can end the message B response window.

[0113] In case 2, even if the terminal device does not successfully receive Message B, the Message B response window ends. For example, assuming the random access process is triggered by BFR, the terminal device carries the C-RNTI MAC CE in Message A, and then the terminal device receives the PDCCH scrambled by the C-RNTI, it means that the beam selection process associated with BFR has ended. At this point, the random access process ends, and the terminal device ends the Message B response window. The BFR can include the SpCell BFR or the BFR of the SpCell's BFD-RS set.

[0114] For another example, assume that the terminal device carries C-RNTI MAC CE in message A, and the TAT timer of the main timing advance group PTAG is running. At this time, if the terminal device receives a PDCCH encrypted with C-RNTI, and the PDCCH indicates an uplink grant (UL grant) for new transmission, the terminal device ends the message B response window.

[0115] For another example, assume that the terminal device carries C-RNTI MAC CE in message A, and the CG-SDT process of packet transmission based on pre-configured resources is in progress. At this time, if the terminal device receives a PDCCH encrypted with C-RNTI, and the PDCCH indicates an uplink grant (UL grant) for the new transmission, the terminal device ends the message B response window.

[0116] The following describes a wireless communication method according to an embodiment of the present application in conjunction with FIG6 . As shown in FIG6 , it is assumed that the network device sends a PDCCH skip indication 1 to the terminal device at time t1 to instruct the terminal device to skip PDCCH monitoring within a PDCCH skip duration T1. Furthermore, after the terminal device sends message A to the network device at time t2, it runs a message B response window T2 and receives message B at time t3, ending the message B response window T2.

[0117] Accordingly, during the operation of the message B response window T2 of T1 and in the time period T3 after the end of the message B response window T2, the terminal device performs PDCCH monitoring. The time period T3 is the time period between the end time of the message B response window T2 and the end time of the PDCCH skip duration.

[0118] It should be noted that in the embodiment of the present application, the terminal device can also skip PDCCH monitoring during the operation of the message B response window T2, and the embodiment of the present application does not limit this.

[0119] Taking the first window as the RAR window as an example, the random access process associated with the RAR window can be divided into a non-competition-based random access process and a contention-based random access process. Generally, for a non-competition-based random access process, RAR is usually the last message in the random access process. Therefore, the PDCCH received in the RAR window is particularly important and directly affects whether the random access process is successful. Therefore, in an embodiment of the present application, the first random access process associated with the RAR window can be a non-competition-based random access process. Accordingly, in some implementations, if the RAR window ends, the terminal device can perform PDCCH monitoring during the PDCCH skipping period. That is to say, the above-mentioned step S510 may include: if the RAR window ends, the terminal device performs PDCCH monitoring. Of course, in an embodiment of the present application, the above-mentioned first random access process may also include a contention-based random access process.

[0120] The embodiments of the present application do not limit the circumstances under which the RAR window ends. For ease of understanding, the following describes the scheme for ending the RAR window in conjunction with Case 3 and Case 4. In Case 3, if the terminal device successfully receives the RAR, the RAR window ends. For example, assuming that the terminal device carries a random access preamble index 1 (PREAMBLE_INDEX) in the random access request, if the terminal device then correctly receives the RAR, and the RAR contains a random access preamble index that matches the random access preamble index 1, it indicates that the terminal device successfully receives the RAR. At this point, the terminal device can end the RAR window.

[0121] In case 4, the RAR window ends even if the terminal device does not successfully receive the RAR. For example, assuming that the non-contention-based random access procedure is triggered by BFR, if the terminal device receives a PDCCH scrambled by the C-RNTI, it means that the beam selection process associated with BFR has ended. At this time, the random access procedure ends, and the terminal device can end the RAR window.

[0122] Generally speaking, if the non-competitive random access process is triggered by a PDCCH-command (PDCCH-order), the non-competitive random access process is mainly used for the transmission of downlink data. However, RAR can usually only indicate uplink resources, and cannot indicate downlink resources used for downlink data transmission. Therefore, even if the terminal device successfully receives the RAR (that is, after the RAR window ends), the terminal device can perform PDCCH monitoring, which helps the terminal device to monitor the downlink resources used for downlink data transmission as soon as possible. In other words, the above step S510 includes: if the first random access process is a random access process triggered by a PDCCH-command, the terminal device performs PDCCH monitoring.

[0123] The following describes a wireless communication method according to an embodiment of the present application in conjunction with FIG7 . As shown in FIG7 , it is assumed that the network device sends a PDCCH skip indication 1 to the terminal device at time t1 to instruct the terminal device to skip PDCCH monitoring within the PDCCH skip duration T1. Furthermore, after the terminal device sends a random access request (i.e., Msg1) to the network device at time t2, it runs a RAR window T4 and receives a RAR at time t3, ending the RAR window T4.

[0124] Accordingly, during the operation of the RAR window T4 in T1 and in the time period T5 after the end of the RAR window T4, the terminal device monitors the PDCCH. The time period T5 is the time period between the end time of the RAR window T4 and the end time of the PDCCH skip duration.

[0125] It should be noted that in the embodiment of the present application, the terminal device can also skip PDCCH monitoring during the operation of the RAR window T4, and the embodiment of the present application does not limit this.

[0126] It should be noted that in the embodiment of the present application, if the RAR window ends, the terminal device performs PDCCH monitoring, which can be applied to various types of triggered non-contention-based random access procedures. Of course, if the RAR window ends, the terminal device performs PDCCH monitoring, which can be applied only to the non-contention-based random access procedure triggered by the PDCCH-command.

[0127] Currently, there are many reasons for triggering a non-contention-based random access procedure, for example, the non-contention-based random access procedure triggered by the PDCCH-command described above, or the non-contention-based random access procedure triggered by BFR.

[0128] In an embodiment of the present application, in order to further reduce the power consumption of the terminal device, the behavior of the terminal device (for example, performing PDCCH monitoring or skipping PDCCH monitoring) may be slightly different for non-contention-based random access processes triggered by different reasons.

[0129] For the random access process triggered by BFR, when the terminal device receives the PDCCH encrypted by C-RNTI, it means that the network device has selected a new beam and indicated it to the terminal device through the PDCCH encrypted by C-RNTI. At this time, it can be understood that the beam selection process of the new beam associated with BFR is completed, and the network device usually does not send other PDCCHs to the terminal device. Therefore, in this case, when the RAR window ends, the terminal device can skip PDCCH monitoring based on the indication information. That is to say, the above step S510 may include: if the first random access process is a random access process triggered by BFR, the terminal device skips PDCCH monitoring.

[0130] The following describes a wireless communication method according to an embodiment of the present application in conjunction with FIG8 . As shown in FIG8 , it is assumed that the network device sends a PDCCH skip indication 1 to the terminal device at time t1, instructing the terminal device to skip PDCCH monitoring during the PDCCH skip duration T1. Furthermore, after the terminal device sends a random access request to the network device at time t2, it runs a RAR window T4 and receives a RAR at time t3, ending the RAR window T4.

[0131] Accordingly, during the operation of RAR window T4' in T1, the terminal device skips PDCCH monitoring. During time period T5' after the end of RAR window T4' in T1, the terminal device skips PDCCH monitoring. Time period T5' is the time period between the end of RAR window T4' and the end of PDCCH skip duration T1.

[0132] It should be noted that in the embodiment of the present application, the terminal device can also skip PDCCH monitoring during the operation of the RAR window T4', and the embodiment of the present application does not limit this.

[0133] In embodiment 2, the first condition includes that the terminal device receives indication information and the first SR is canceled, or in other words, the first condition includes that the first SR is canceled during the PDCCH skip duration.

[0134] In some implementations, the PDCCH skip duration indicated by the above indication information includes the time period after the SR is canceled. In addition, in an embodiment of the present application, the relationship between the PDCCH skip duration and the moment when the first SR is canceled is not limited. In some implementations, the PDCCH skip duration may include the moment when the first SR is canceled. For example, the starting moment of the PDCCH skip duration may be before the moment when the first SR is canceled, as shown in Figures 9 and 10. For another example, the starting moment of the PDCCH skip duration may overlap with the moment when the first SR is canceled. Of course, in an embodiment of the present application, the PDCCH skip duration may not include the moment when the first SR is canceled, or in other words, the starting moment of the PDCCH skip duration may be after the moment when the first SR is canceled.

[0135] Based on the above introduction to SR, it can be seen that there are multiple triggering conditions for SR, which can mainly include BSR triggering and / or non-BSR triggering. For SR triggered by BSR, it is mainly used to transmit uplink data. When the SR triggered by BSR is canceled, it means that the terminal device requests uplink resources for transmitting uplink data from the network device through BSR. At this time, the terminal device needs to perform PDCCH monitoring, which helps the terminal device to obtain the uplink resources indicated by PDCCH as soon as possible and reduce the time required to transmit uplink data. In other words, the above step S510 may include: if the first SR is a BSR triggered SR, the terminal device performs PDCCH monitoring.

[0136] It should be noted that, in the embodiment of the present application, the type of BSR is not limited, and the BSR may include a preemptive BSR and / or a non-preemptive BSR (also known as a "normal BSR").

[0137] The wireless communication method of the embodiment of the present application is described below in conjunction with FIG9 . As shown in FIG9 , it is assumed that the network device sends a PDCCH skip indication 1 to the terminal device at time t1 to instruct the terminal device to skip PDCCH monitoring within the PDCCH skip duration T1. In addition, at time t BSR , the terminal device triggers SR1 based on the BSR to be transmitted, and then in time period T SR SR1 is in a pending state until the terminal device cancels the pending SR1 at time t (for example, the terminal device obtains an uplink authorization at time t), where the time period between time t and the end time of the PDCCH skip duration T1 is represented by time period T.

[0138] Accordingly, in the time period T1 SR And in the time period T, the terminal device monitors the PDCCH. It should be noted that in the embodiment of the present application, in the time period T SRThe internal terminal device can also skip PDCCH monitoring, which is not limited in the embodiments of the present application.

[0139] On the contrary, for SRs triggered by non-BSRs, when the SR is canceled, it means that the message that needs to request transmission resources through the SR (hereinafter referred to as the SR-associated request for the sake of description) has been transmitted, or the SR-associated request does not need to be transmitted. For example, for SRs triggered by BFR, when the BFR has been sent through the BFR MAC CE, the SR will be canceled. In this case, if the SR is canceled, the network device will generally not send the PDCCH again. Therefore, the terminal device can skip PDCCH monitoring, which helps to reduce the power consumption of the terminal device. That is, the above step S510 may include: if the first SR is a non-BSR triggered SR, the terminal device skips PDCCH monitoring.

[0140] The wireless communication method of the embodiment of the present application is described below in conjunction with FIG10. Referring to FIG10, it is assumed that the network device sends a PDCCH skip indication 1 to the terminal device at time t1 to instruct the terminal device to skip PDCCH monitoring within the PDCCH skip duration T1. In addition, at time t 非BSR , the terminal device triggers SR2, which is a non-BSR triggered SR. Then in time period T SR1 SR2 is in a pending state until the terminal device cancels the pending SR2 at time t' (for example, the terminal device obtains an uplink authorization at time t), where the time period between time t' and the end of the PDCCH skip duration T1 is represented by time period T'.

[0141] Accordingly, in the time period T1 SR1 The terminal device monitors the PDCCH in the time period T', and skips the PDCCH monitoring in the time period T'. SR The internal terminal device can also skip PDCCH monitoring, which is not limited in the embodiments of the present application.

[0142] In the embodiments of the present application, the first condition is not limited. In some implementations, the first condition may include uplink data to be transmitted. For example, if there is uplink data to be transmitted, the terminal device may monitor the PDCCH during the PDCCH skip duration. For another example, if there is no uplink data to be transmitted, the terminal device may skip PDCCH monitoring during the PDCCH skip duration.

[0143] In some other implementations, the first condition may include downlink data to be transmitted. For example, if there is downlink data to be transmitted, the terminal device may monitor the PDCCH during the PDCCH skip duration. For another example, if there is no downlink data to be transmitted, the terminal device may skip PDCCH monitoring during the PDCCH skip duration.

[0144] In other implementations, the first condition may further include whether the random access procedure is a four-step random access procedure or a two-step random access procedure. For example, if the random access procedure is a two-step random access procedure, the terminal device may monitor the PDCCH during the PDCCH skip duration. For another example, if the random access procedure is a four-step random access procedure, the terminal device may skip PDCCH monitoring during the PDCCH skip duration.

[0145] In other implementations, the first condition may further include whether the random access procedure is a contention-based random access procedure or a non-contention-based random access procedure. For example, if the random access procedure is a non-contention-based random access procedure, the terminal device may monitor the PDCCH during the PDCCH skip duration. For another example, if the random access procedure is a contention-based random access procedure, the terminal device may skip PDCCH monitoring during the PDCCH skip duration.

[0146] The method embodiment of the present application is described in detail above with reference to Figures 1 to 10 . The device embodiment of the present application is described in detail below with reference to Figures 11 and 12 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the preceding method embodiment.

[0147] FIG11 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 1100 shown in FIG11 includes: a processing unit 1110 .

[0148] Processing unit 1110 is used to perform physical downlink control channel PDCCH monitoring or skip PDCCH monitoring if a first condition is met; wherein the first condition is associated with one or more of the following: the terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; the first window ends, and the first window is a response window corresponding to the first random access process; and the first scheduling request SR is canceled.

[0149] In a possible implementation, the first condition includes one or more of the following: the terminal device receives the indication information, and the first window ends; and the terminal device receives the indication information, and the first SR is canceled.

[0150] In a possible implementation manner, the first random access procedure is a non-contention-based random access procedure.

[0151] In a possible implementation, the first random access procedure includes a random access procedure triggered by a beam failure request (BFR) and / or a random access procedure triggered by a PDCCH-command.

[0152] In a possible implementation manner, the processing unit is specifically configured to skip PDCCH monitoring if the first random access procedure is a random access procedure triggered by BFR.

[0153] In a possible implementation manner, the processing unit is specifically configured to perform PDCCH monitoring if the first random access procedure is a random access procedure triggered by a PDCCH-command.

[0154] In a possible implementation, the processing unit is specifically configured to perform PDCCH monitoring if the first window ends.

[0155] In a possible implementation, the first SR includes a buffer status report (BSR) triggered SR and / or a non-BSR triggered SR.

[0156] In a possible implementation manner, the processing unit is specifically configured to perform PDCCH monitoring if the first SR is an SR triggered by a BSR.

[0157] In a possible implementation manner, the processing unit is specifically configured to skip PDCCH monitoring if the first SR is an SR not triggered by a BSR.

[0158] In a possible implementation manner, the processing unit is specifically configured to perform PDCCH monitoring or skip PDCCH monitoring during a PDCCH skip duration.

[0159] In a possible implementation manner, the first window includes a random access response window and / or a message B response window.

[0160] In an optional embodiment, the processing unit 1110 may be a processor 1210. The terminal device 1100 may further include a transceiver 1230 and a memory 1220, as specifically shown in FIG12 .

[0161] Figure 12 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 12 indicate that the unit or module is optional. The device 1200 may be used to implement the method described in the above method embodiment. The device 1200 may be a chip, a terminal device, or a network device.

[0162] The device 1200 may include one or more processors 1210. The processor 1210 may support the device 1200 in implementing the method described in the above method embodiment. The processor 1210 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0163] The apparatus 1200 may further include one or more memories 1220. The memories 1220 store programs that can be executed by the processor 1210, causing the processor 1210 to perform the methods described in the above method embodiments. The memories 1220 may be independent of the processor 1210 or integrated into the processor 1210.

[0164] The apparatus 1200 may further include a transceiver 1230. The processor 1210 may communicate with other devices or chips via the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips via the transceiver 1230.

[0165] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0166] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0167] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0168] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0169] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0170] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0171] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0172] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0173] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0174] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0175] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0176] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0177] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0178] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0179] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0180] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: If the first condition is met, the terminal device monitors the physical downlink control channel PDCCH or skips PDCCH monitoring; The first condition is associated with one or more of the following: The terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; The first window ends, where the first window is a response window corresponding to the first random access procedure; as well as The first scheduling request SR is cancelled.

2. The method according to claim 1, characterized in that The first condition includes one or more of the following: The terminal device receives the indication information, and the first window ends; and The terminal device receives the indication information, and the first SR is canceled.

3. The method according to claim 1 or 2, characterized in that The first random access procedure is a non-contention-based random access procedure.

4. The method according to claim 3, characterized in that The first random access procedure includes a random access procedure triggered by a beam failure request (BFR) and / or a random access procedure triggered by a PDCCH command.

5. The method according to claim 4, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: If the first random access process is a random access process triggered by BFR, the terminal device skips PDCCH monitoring.

6. The method according to claim 5, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: If the first random access process is a random access process triggered by a PDCCH-command, the terminal device performs PDCCH monitoring.

7. The method according to claim 1 or 2, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: If the first window ends, the terminal device monitors the PDCCH.

8. The method according to claim 1 or 2, characterized in that The first SR includes an SR triggered by a buffer status report (BSR) and / or an SR not triggered by a BSR.

9. The method according to claim 8, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: If the first SR is an SR triggered by a BSR, the terminal device performs PDCCH monitoring.

10. The method according to claim 8, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: If the first SR is not a BSR triggered SR, the terminal device skips PDCCH monitoring.

11. The method according to any one of claims 1 to 10, characterized in that The terminal device performs PDCCH monitoring or skips PDCCH monitoring, including: The terminal device performs PDCCH monitoring or skips PDCCH monitoring during the PDCCH skipping duration.

12. The method according to any one of claims 1 to 11, characterized in that The first window includes a random access response window and / or a message B response window.

13. A terminal device, characterized in that: include: a processing unit, configured to perform physical downlink control channel PDCCH monitoring or skip PDCCH monitoring if a first condition is met; The first condition is associated with one or more of the following: The terminal device receives indication information for instructing the terminal device to skip PDCCH monitoring; The first window ends, where the first window is a response window corresponding to the first random access procedure; as well as The first scheduling request SR is cancelled.

14. The terminal device according to claim 13, characterized in that The first condition includes one or more of the following: The terminal device receives the indication information, and the first window ends; and The terminal device receives the indication information, and the first SR is canceled.

15. The terminal device according to claim 13 or 14, characterized in that: The first random access procedure is a non-contention-based random access procedure.

16. The terminal device according to claim 15, characterized in that The first random access procedure includes a random access procedure triggered by a beam failure request (BFR) and / or a random access procedure triggered by a PDCCH command.

17. The terminal device according to claim 16, characterized in that The processing unit is specifically configured to skip PDCCH monitoring if the first random access process is a random access process triggered by BFR.

18. The terminal device according to claim 17, characterized in that The processing unit is specifically configured to perform PDCCH monitoring if the first random access procedure is a random access procedure triggered by a PDCCH-command.

19. The terminal device according to claim 13 or 14, characterized in that: The processing unit is specifically configured to perform PDCCH monitoring if the first window ends.

20. The terminal device according to claim 13 or 14, characterized in that: The first SR includes an SR triggered by a buffer status report (BSR) and / or an SR not triggered by a BSR.

21. The terminal device according to claim 20, characterized in that The processing unit is specifically configured to perform PDCCH monitoring if the first SR is an SR triggered by a BSR.

22. The terminal device according to claim 20, characterized in that The processing unit is specifically configured to skip PDCCH monitoring if the first SR is an SR not triggered by a BSR.

23. The terminal device according to any one of claims 13 to 22, characterized in that: The processing unit is specifically configured to perform PDCCH monitoring or skip PDCCH monitoring during a PDCCH skip duration.

24. The terminal device according to any one of claims 13 to 23, characterized in that: The first window includes a random access response window and / or a message B response window.

25. A terminal device, characterized in that: The terminal device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method according to any one of claims 1 to 12.

26. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 12.

27. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 12.

28. A computer-readable storage medium, characterized in that A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 to 12.

29. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 12.

30. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 12.

Images