CHANNEL MONITORING METHOD, ELECTRONIC DEVICE, AND STORAGE MEDIUM

Abstract

A channel monitoring method is provided. The method comprises: during the duration of skipping physical downlink control channel (PDCCH) monitoring, if a terminal device sends first information, the terminal device resuming PDCCH monitoring. Further disclosed in the present application are another channel monitoring method, an electronic device, and a storage medium.

Claims

1. A channel monitoring method, comprising: within a Physical Downlink Control Channel (PDCCH) skipping duration, resuming, by a terminal device, PDCCH monitoring when the terminal device sends first information.

2. The method of claim 1, wherein the first information comprises: a Scheduling Request (SR).

3. The method of claim 2, wherein the SR is pending.

4. The method of claim 2, wherein resuming, by the terminal device, the PDCCH monitoring comprises: monitoring, by the terminal device, PDCCH on all activated serving cells.

5. The method of claim 2, further comprising: determining, by the terminal device, to monitor PDCCH on at least one activated serving cell according to a related parameter of a Logical Channel Prioritization (LCP) restriction of an uplink logical channel that triggers the SR; wherein determining, by the terminal device, to monitor the PDCCH on at least one activated serving cell according to the related parameter of the LCP restriction of the uplink logical channel that triggers the SR comprises: determining, by the terminal device, to monitor the PDCCH on all activated serving cells in a case where the uplink logical channel that triggers the SR is not configured with the related parameter of the LCP restriction; or wherein determining, by the terminal device, to monitor the PDCCH on at least one activated serving cell according to the related parameter of the LCP restriction of the uplink logical channel that triggers the SR comprises: determining, by the terminal device and according to the related parameter of the LCP restriction, a first serving cell set that is allowed to transmit the uplink logical channel in a case where the uplink logical channel that triggers the SR is configured with the related parameter of the LCP restriction; and determining, by the terminal device, to monitor the PDCCH on a serving cell corresponding to uplink scheduling information capable of indicating any serving cell in the first serving cell set.

6. The method of claim 1, wherein the first information comprises a preamble; and the preamble is sent on a corresponding random access channel resource based on a selected synchronous signal block in a case where the terminal device triggers beam failure recovery; wherein the method further comprises: starting, by the terminal device, a Random Access Response (RAR) receiving window or a message B (Msg B) receiving window.

7. The method of claim 6, wherein resuming, by the terminal device, the PDCCH monitoring comprises: monitoring, by the terminal device, the PDCCH at the RAR receiving window or the MsgB receiving window.

8. The method of claim 1, further comprising: stopping, by the terminal device, skipping the PDCCH monitoring.

9. A channel monitoring method, comprising: transmitting, by a terminal device, second information within a Physical Downlink Control Channel (PDCCH) skipping duration; after transmitting the second information within the PDCCH skipping duration, starting, by the terminal device, a retransmission timer that corresponds to a Hybrid Automatic Repeat Request (HARQ) process corresponding to the second information, and resuming, by the terminal device, PDCCH monitoring.

10. The method of claim 9, after transmitting the second information within the PDCCH skipping duration, starting, by the terminal device, the retransmission timer that corresponds to the HARQ process corresponding to the second information, and resuming, by the terminal device, the PDCCH monitoring comprises: when transmitting the second information within the PDCCH skipping duration, starting, by the terminal device, a Round Trip Timer (RTT) that corresponds to the HARQ process corresponding to the second information; and in a case where the RTT is timeout, starting, by the terminal device, the retransmission timer corresponding to the HARQ process for transmitting the second information, and resuming, by the terminal device, the PDCCH monitoring.

11. The method of claim 9, wherein starting, by the terminal device, the retransmission timer corresponding to the HARQ process for transmitting the second information, and resuming, by the terminal device, the PDCCH monitoring comprises: in a case where the second information comprises uplink transmission, starting, by the terminal device, an uplink retransmission timer corresponding to the HARQ process of the uplink transmission, and resuming, by the terminal device, the PDCCH monitoring; wherein the uplink transmission is sent on Configured Grant (CG) resources; and/or wherein starting, by the terminal device, the retransmission timer corresponding to the HARQ process for transmitting the second information, and resuming, by the terminal device, the PDCCH monitoring comprises: in a case where the second information comprises a Non-Acknowledgment (NACK) message for downlink transmission received by the terminal device within the PDCCH skipping duration, starting, by the terminal device, a downlink retransmission timer corresponding to the HARQ process of the downlink transmission, and resuming, by the terminal device, the PDCCH monitoring; wherein the downlink transmission is transmitted based on Semi-Persistent Scheduling (SPS) resources.

12. The method of claim 9, wherein resuming, by the terminal device, the PDCCH monitoring comprises: monitoring, by the terminal device, the PDCCH on a serving cell within a Discontinuous Reception (DRX) activation period.

13. The method of claim 9, further comprising: stopping, by the terminal device, skipping the PDCCH monitoring.

14. The method of claim 11, further comprising: stopping, by the terminal device, skipping the PDCCH monitoring based on a configuration of a network device.

15. A channel monitoring method, comprising: sending, by a network device, first configuration information, wherein the first configuration information is used to determine whether a terminal device stops skipping Physical Downlink Control Channel (PDCCH) monitoring under a first condition within a PDCCH skipping duration.

16. The method of claim 15, wherein the first condition comprises that: the network device receives a Non-Acknowledgment (NACK) message sent by the terminal device for a Physical Downlink Share Channel (PDSCH).

17. The method of claim 16, wherein the PDSCH is transmitted based on SPS resources within the PDCCH skipping duration.

18. The method of claim 15, wherein the first configuration information is carried in a system broadcast message or Radio Resource Control (RRC) signaling.

19. A terminal device, comprising a processor and a memory configured to store a computer program capable of running on the processor, wherein the processor is configured to: resume PDCCH monitoring when a terminal device sends first information within a Physical Downlink Control Channel (PDCCH) skipping duration.

20. A terminal device, comprising a processor and a memory configured to store a computer program capable of running on the processor, wherein the processor is configured to: transmit second information within a Physical Downlink Control Channel (PDCCH) skipping duration; and start a retransmission timer that corresponds to a Hybrid Automatic Repeat Request (HARQ) process corresponding to the second information, and resume PDCCH monitoring after the second sending unit transmits the second information within the PDCCH skipping duration.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG. 1 illustrates an optional schematic diagram of a discontinuous reception cycle according to the embodiments of the disclosure.

[0021] FIG. 2 illustrates a schematic diagram of composition structure of a communication system according to the embodiments of the disclosure.

[0022] FIG. 3 illustrates an optional processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0023] FIG. 4 illustrates a detailed processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0024] FIG. 5 illustrates a schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration according to the embodiments of the disclosure.

[0025] FIG. 6 illustrates another detailed processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0026] FIG. 7 illustrates another schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration according to the embodiments of the disclosure.

[0027] FIG. 8 illustrates yet another optional processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0028] FIG. 9 illustrates yet another detailed processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0029] FIG. 10 illustrates yet another schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration according to the embodiments of the disclosure.

[0030] FIG. 11 illustrates still another optional detailed processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0031] FIG. 12 illustrates still another schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration according to the embodiments of the disclosure.

[0032] FIG. 13 illustrates another optional processing flowchart of a channel monitoring method according to the embodiments of the disclosure.

[0033] FIG. 14 illustrates a schematic diagram of optional composition structure of a terminal device according to the embodiments of the disclosure.

[0034] FIG. 15 illustrates a schematic diagram of optional composition structure of a network device according to the embodiments of the disclosure.

[0035] FIG. 16 illustrates another schematic diagram of optional composition structure of a terminal device according to the embodiments of the disclosure.

[0036] FIG. 17 illustrates a schematic diagram of hardware composition structure of an electronic device according to the embodiments of the disclosure.

DETAILED DESCRIPTION

[0037] In order to provide a more detailed understanding of the features and technical contents of the embodiments of the disclosure, the implementation of the embodiments of the disclosure will be described in detail below with reference to the accompanying drawings, and the accompanying drawings are for illustrative purposes only and are not intended to limit the embodiments of the disclosure.

[0038] In a New Radio (NR) system, a network device may configure a Discontinuous Reception (DRX) function for a terminal device. The terminal device discontinuously monitors a PDCCH, so as to achieve the purpose of saving electricity for the terminal device. Each Medium Access Control (MAC) entity has one DRX configuration. The configuration parameters of the DRX may include:

[0039] 1) a DRX-onDuration Timer, i.e., the duration of a terminal device waking up at the beginning of a DRX cycle;

[0040] 2) a DRX-SlotOffset, i.e., the time delay of the terminal device starting the DRX-onDuration Timer.

[0041] 3) a DRX-InactivityTimer, i.e., after the terminal device receives a PDCCH indicating uplink initial transmission or downlink initial transmission, a duration of the terminal device continuing monitoring the PDCCH.

[0042] 4) a DRX-RetransmissionTimerDL, i.e., the longest duration of the terminal device monitoring the PDCCH indicating downlink retransmission scheduling. each downlink HARQ process (except the broadcast Hybrid Automatic Repeat Request (HARQ) processes) corresponds to one DRX-Retransmission TimerDL.

[0043] 5) a DRX-RetransmissionTimerUL, i.e., the longest duration of the terminal device monitoring the PDCCH indicating Upper retransmission scheduling. Each uplink HARQ process corresponds to one DRX-RetransmissionTimerUL.

[0044] 6) a DRX-LongCycleStartOffset, used to configure a Long DRX cycle, and a subframe offset at the beginning of the Long DRX Cycle and a Short DRX Cycle.

[0045] 7) a DRX-ShortCycle, which is an optional configuration.

[0046] 8) a DRX-ShortCycleTimer, which refers to the duration of the terminal device in the short DRX cycle (any PDCCH is not received), and is an optional configuration.

[0047] 9) DRX-HARQ-RTT-TimerDL, i.e., the minimum pending time of the terminal device expecting to receive the PDCCH indicating downlink scheduling. Each downlink HARQ process (except the broadcast HARQ) corresponds to one DRX-HARQ-RTT-TimerDL.

[0048] 10) DRX-HARQ-RTT-TimerUL, i.e., the minimum pending time of the terminal device expecting to receive the PDCCH indicating uplink scheduling. Each uplink HARQ process corresponds to one DRX-HARQ-RTT-TimerUL.

[0049] If the terminal device is configured with DRX, then the terminal device needs to monitor the PDCCH at the DRX Active Time. A DRX Active Time includes several cases as follows.

[0050] 1) Any of the following five timers is running: DRX-onDurationTimer, DRX-InactivityTimer, DRX-RetransmissionTimerDL, DRX-RetransmissionTimerUL, and ra-ContentionResolutionTimer.

[0051] 2) A Scheduling Request (SR) is transmitted on a PUCCH and is in a pending state.

[0052] 3) In a competition-based random access process, the terminal device has not received an initial transmission indicated by the PDCCH scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) after successfully receiving a random access response.

[0053] A schematic diagram of the DRX cycle of the terminal device is as illustrated in FIG. 1. The terminal device determines the time for starting the drx-onDurationTimer according to whether the terminal device is in the Short DRX Cycle or the Long DRX Cycle. Specific provisions are as follows.

[0054] 1) If the terminal device is in the Short DRX Cycle, and the current subframe satisfies [(SFN×10)+subframe number] modulo (drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle); or

[0055] 2) If the terminal device is in the Long DRX Cycle, and the current subframe satisfies [(SFN×10)+subframe number] modulo (drx-LongCycle)=drx-StartOffset:

[0056] the drx-onDurationTimer is started at a time after drx-SlotOffset slots from the current sub-frame.

[0057] The condition for the terminal device to start or restart a DRX-InactivityTimer is as follows.

[0058] If the terminal device receives a PDCCH indicating downlink or uplink initial transmission, then the terminal device starts or restarts the drx-InactivityTimer.

[0059] The condition for the terminal device to start and stop DRX-RetransmissionTimerDL is as follows.

[0060] When the terminal device receives a PDCCH indicating the downlink transmission, or when the terminal device receives a Medium Access Control Protocol Data Unit (MAC PDU) on configured downlink grant resources, then the terminal device stops the DRX-RetransmissionTimerDL corresponding to the HARQ process. A terminal starts the DRX-HARQ-RTT-TimerDL corresponding to the HARQ process after completing the transmission fed back by the HARQ process of this downlink transmission.

[0061] If the DRX-HARQ-RTT-TimerDL corresponding to a certain HARQ of the terminal device is timeout, and the downlink data transmitted by using the HARQ process is decoded unsuccessfully, then the terminal device starts the DRX-RetransmissionTimerDL corresponding to the HARQ process.

[0062] The condition for the terminal to start and stop the DRX-RetransmissionTimerUL is as follows.

[0063] When the terminal device receives a PDCCH indicating uplink transmission, or when the terminal device transmits a MAC PDU on the configured downlink grant resources, then the terminal device stops the DRX-RetransmissionTimerUL corresponding to the HARQ process. The terminal device starts the DRX-HARQ-RTT-TimerUL corresponding to the HARQ process after completing a first repetition of this Physical Uplink Share Channel (PUSCH).

[0064] If the DRX-HARQ-RTT-TimerUL corresponding to a certain HARQ of the terminal device is timeout, and the terminal device starts the DRX-RetransmissionTimerUL corresponding to the HARQ process.

[0065] A scheme of reducing blind detection of the PDCCH by the terminal device is proposed in a NR power saving project plan of a 3GPP version 17 (Rel-17). A PDCCH skipping mechanism is introduced in the scheme, that is, the network device may instruct the terminal device to skip the PDCCH monitoring in a period of time by transmitting dynamic signaling. For the terminal device configured with DRX, the terminal device monitors the PDCCH at the DRX active time. The general principle of PDCCH skipping is that when the terminal device receives a PDCCH skipping indication, the terminal device should follow the PDCCH skipping indication, that is the terminal device is at the DRX active time within the PDCCH skipping duration, and the terminal device skips PDCCH monitoring in a subsequent PDCCH skipping duration.

[0066] Generally, the network device will indicate a monitoring behavior of the terminal device on the basis of a downlink service requirement of the terminal device and an uplink service requirement previously reported by the terminal device through a Buffer Status Reports (BSR). In a case where the network device considers that the terminal device does not have an uplink and downlink data transmission requirement in a period of time in the future, the network device may indicate the terminal device to execute the PDCCH skipping within this period of time, so as to achieve the purpose of saving power for the terminal device. However, in a process of implementing the channel monitoring method, the applicant found that in some scenarios, the terminal device will trigger uplink transmission and expect further response from the network device. For example, there is uplink data arrives at the terminal device, an SR is triggered since there is no uplink resources for BSR reporting, or the terminal device transmits a PUSCH by using the CG resources, or the terminal device triggers the BFR, or the terminal device expects the network device to schedule a retransmission for a PDSCH reception failure of the SPS, etc. In these cases, because the terminal device expects the response of the network device, the terminal device has the requirement to monitor PDCCH. If the terminal device is in the PDCCH skipping duration at this time, based on the existing scheme, the terminal device needs to continue to skip PDCCH monitoring according to the PDCCH skipping indication transmitted by the network device. In the scenario, although the electric energy of the terminal device is saved, the terminal device cannot monitor the PDCCH because of expecting the response of the network device, which affects the transmission of a service.

[0067] The technical schemes of the embodiments of the disclosure may be applied to various communications systems, such as a Global System for Mobile Communications (GSM), a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS) system, a Long Term Evolution (LTE) system, a Frequency Division Duplex (FDD) system, a Time Division Duplex (TDD) system, an Advanced Long Term Evolution (LTE-A) system, an NR system, an evolution system of the NR system, an LTE-based Access to Unlicensed Spectrum (LTE-U) system, a NR-based Access to Unlicensed Spectrum (NR-U) system, a Universal Mobile Telecommunications System (UMTS), a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communications system, a Wireless Local Area Network (WLAN), Wireless Fidelity (WiFi), a next generation of communication systems, or other communication systems.

[0068] Network architecture and service scenarios described in the embodiments of the disclosure are intended to describe the technical schemes in the embodiments of the disclosure more clearly, but are not intended to limit the technical schemes provided in the embodiments of the disclosure. Those of ordinary skill in the art may know that as the network architecture evolves and a new service scenario emerges, the technical schemes provided in the embodiments of the disclosure are also applicable to a similar technical problem.

[0069] The network device involved in the embodiments of the disclosure may be a common base station (NodeB or eNB or gNB), a New Radio controller (NR controller), a centralized unit, a new radio base station, a remote radio frequency module, a relay, a distributed network element, a transmission reception point (TRP), a transmission point (TP) or any other devices. No limits are made to specific technologies and specific device forms adopted by the network device in the embodiments of the disclosure. In order to facilitate description, in all embodiments of the disclosure, the abovementioned apparatuses with a wireless communication function provided for the terminal device are collectively referred to a network device.

[0070] In the embodiments of the disclosure, the terminal device may be any terminal. For example, the terminal device may be a User Equipment (UE) in Machine Type Communication (MTC). That is to say, the terminal device may also be called the UE, a Mobile Station (MS), a Mobile Terminal (MT), a terminal, etc. The terminal device may communicate with one or more core networks through a Radio Access Network (RAN). For example, the terminal device may be a mobile terminal (or referred to as a “cellular” phone) and a computer with a mobile terminal. For example, the terminal device may also be a portable, pocket-sized, hand-held, computer built-in, or in-vehicle mobile apparatus, which exchanges language and/or data with the RAN. No specific limitation are made thereto in the embodiments of the disclosure.

[0071] Optionally, the network device and the terminal device may be deployed on land, including indoors or outdoors, and may be held in hands or deployed in vehicles, or may be deployed on water, or may be deployed on an aircraft, a balloon, and an artificial satellite in the air. No limits are made to the disclosure scenario of the network device and the terminal device in the embodiments of the disclosure.

[0072] Optionally, communication may be performed between the network device and the terminal device and between the terminal devices through a licensed spectrum, or through an unlicensed spectrum, or through the licensed spectrum and the unlicensed spectrum simultaneously. Communication may be performed between the network device and the terminal device and between the terminal devices through a spectrum below 7 gigahertz (GHz), or through a spectrum above 7 GHz, or through the spectra below 7 GHz and above 7 GHz simultaneously. No limits are made to the spectrum resource used between the network device and the terminal device in the embodiments of the disclosure.

[0073] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of the communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (D2D) communication, Machine to Machine (M2M) communication, MTC, and Vehicle to Vehicle (V2V) communication, etc. The embodiments of the disclosure can also be applied to these communication systems.

[0074] Exemplarily, the communication system 100 to which the embodiments of the disclosure is applied is as illustrated in FIG. 2. The communication system 100 may include a network device 110. The network device 110 may be a device in communication with a terminal device 120 (or called a communication terminal device or a terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with the terminal device located within the coverage. Optionally, the network device 110 may be a Base Transceiver Station (BTS) in the GSM or the CDMA system, may also be a NodeB (NB) in the WCDMA system, and may further be an Evolutional Node B (eNB or eNodeB) in the LTE system or a wireless controller in a Cloud Radio Access Network (CRAN). Or the network device may be a mobile switching center, a relay station, an access point, an on-board device, a wearable device, a hub, a switch, a network bridge, a router, a network-side device in a future 5G network, a network device in a future evolved Public Land Mobile Network (PLMN) or the like.

[0075] The communication system 100 further includes at least one terminal device 120 located within the coverage of the network device 110. A “terminal device” used herein includes, but not is limited to, an apparatus arranged to receive/transmit a communication signal through a wired line connection, for example, through Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), digital cable and direct cable connections, and/or another data connection/network) and/or through a wireless interface, for example, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network like a Digital Video Broadcasting-Handheld (DVB-H) network, a satellite network and an Amplitude Modulated (AM)-Frequency Modulated (FM) broadcast transmitter, and/or another terminal device, and/or an Internet of Things (IoT) device. The terminal device arranged to communicate through a wireless interface may be called a “wireless communication terminal”, a “wireless terminal” or a “mobile terminal”. Examples of the mobile terminal include, but are not limited to, satellite or cellular phones, Personal Communications System (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities, PDAs that can include radiotelephones, pagers, Internet/Intranet access, Web browsers, notebooks, calendars, and/or Global Positioning System (GPS) receivers, and conventional laptop and/or hand-held receivers or other electronic devices including radiotelephone transceivers. The terminal device may also be referred to as UE, a subscriber unit, a subscriber station, a mobile console, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communications device, a user agent, or a user apparatus. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a hand-held device having a wireless communication function, a computing device or another processing device connected to a wireless modem, an on-board device, a wearable device, a terminal device in a 5G network, a terminal device in a PLMN in future evolution , or the like.

[0076] Optionally, D2D communication may be performed between the terminal devices 120.

[0077] Optionally, a 5G system or a 5G network may also be called an NR system or an NR network.

[0078] FIG. 2 exemplarily illustrates one network device and two terminal devices. Optionally, the communication system 100 may include a plurality of network device and the coverage of each network device may include other number of terminal devices. No limits are made thereto in the embodiments of the disclosure.

[0079] Optionally, the communication system 100 may further include other network entities, such as a network controller and a mobile management entity. No limits are made thereto in the embodiments of the disclosure.

[0080] It is to be understood that a device with a communications function in a network/a system in the embodiments of the disclosure may be called a communication device. Taking a communication system 100 as illustrated in FIG. 2, the communications device may include a network device 110 and a terminal device 120 with a communications function. The network device 110 and the terminal device 120 may be specific devices as described above, which will not be elaborated herein. The communication device 100 may also include other devices, for example, other network entities, such as a network controller and a mobile management entity. No limits are made thereto in the embodiments of the disclosure.

[0081] An optional processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 3, includes the following operations.

[0082] At S201, within a PDCCH skipping duration, a terminal device resumes PDCCH monitoring when the terminal device sends first information.

[0083] In some embodiments, the first information may include at least one of the following: an SR and a Preamble.

[0084] In some embodiments, the operation that the terminal device resumes the PDCCH monitoring can also be understood as that the terminal device is switched from a PDCCH monitoring skipping state into a PDCCH monitoring state.

[0085] In some embodiments, a PDCCH skipping duration may also be referred to as PDCCH skipping onduration, that is, the network device indicates the terminal device not to monitor the PDCCH within the PDCCH skipping onduration.

[0086] For a scenario where the first information includes the SR, if the terminal device transits the SR through the PDCCH in the PDCCH skipping duration, and the SR is in a pending state, then the terminal device monitors the PDCCH on all activated serving cells; or the terminal device determines to monitor the PDCCH on at least one activated serving cell according to a related parameter of a Logical Channel Prioritization (LCP) restriction of an uplink logical channel that triggers the SR. In a case where the uplink logical channel that triggers the SR is not configured with the related parameter of the LCP restriction, the terminal device determines to monitor the PDCCH on all activated serving cells; in a case where the uplink logical channel that triggers the SR is configured with the related parameter of the LCP restriction, the terminal device determines a first serving cell set that is allowed to transmit the uplink logical channel according to the related parameter of the LCP restriction; the terminal device determines to monitor the PDCCH on a serving cell corresponding to uplink scheduling information that can indicate any serving cell in the first serving cell set, that is, the terminal device determines to monitor the PDCCH on a serving cell corresponding to the PDCCH that can transmit the uplink scheduling indicating any serving cell in the first serving cell set.

[0087] The related parameter of the LCP restriction is configured by the network device, and is used to limit the serving cell allowed for the transmission of the uplink logical channel. The related parameter of the LCP limit includes, but is not limited to, the following parameters.

[0088] 1) allowedServingCells, i.e., a list of serving cells that are allowed to transmit the uplink logical channel.

[0089] 2) allowedSCS-List, i.e., a list of subcarrier spacings that are allowed to transmit the uplink logical channel.

[0090] For a scenario where the first information includes a Preamble, if the terminal device triggers Beam Failure Recovery (BFR) in a PDCCH skipping duration, then the terminal device transmits the Preamble transmitted on corresponding Random Access Channel (RACH) resources on the basis of a selected Synchronous Signal Block/Physical Broadcast Channel (SS/PBCH Block, SSB), starts a Random Access Response window (RAR window) for a four-operation random access case, or starts a message (Msg B) window for a two-operation random access case. The terminal device monitors a Cell Radio Network Temporary Identifier (C-RNTI) scrambled PDCCH at the RAR window or the Msg B window.

[0091] It is to be noted that, in the embodiments of the disclosure, the terminal device stops PDCCH skipping in a case of monitoring the PDCCH.

[0092] The channel monitoring method provided by the embodiments of the disclosure is described in detail below with respect to different contents included in the first information.

[0093] For a scenario where the first information includes an SR, an optional detail processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 4, includes the following operations.

[0094] At S301, a terminal device receives configuration information sent by a network device through RRC signaling.

[0095] In some embodiments, the configuration information may include at least one of the following: a DRX configuration parameter, an uplink logical channel related configuration, and an SR related configuration.

[0096] Optionally, the configuration information includes:

[0097] a) the DRX configuration parameter, which may include: long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.

[0098] b) for each uplink logical channel of the terminal device, a network device may choose whether to configure PUCCH resources for transmitting an SR for the uplink logical channel. If the network device chooses to configure the PUCCH resources for transmitting an SR for the uplink logical channel, then the network device configures 0 or 1 PUCCH resource for transmitting the SR for the uplink logical channel on each UpLink Bandwidth Part (UL BWP) of each serving cell of the terminal device.

[0099] c) for each uplink logical channel of the terminal device, the network device may configure a related parameter of the LCP restriction for the uplink logical channel. The related parameter of the LCP restriction is used to limit the serving cell allowed for the transmission of the uplink logical channel. The related parameter of the LCP limit includes, but is not limited to, the following parameters.

[0100] 1) allowedServingCells, that is, a list of serving cells that are allowed to transmit the uplink logical channel.

[0101] 2) allowedSCS-List, that is, a list of subcarrier spacings that are allowed to transmit the uplink logical channel.

[0102] At S302, the terminal device receives the PDCCH skipping information sent by the network device corresponding to the serving cell.

[0103] In some embodiments, the PDCCH skipping information indicates the terminal device to skip the PDCCH monitoring. The PDCCH monitoring may include a PDCCH skipping duration.

[0104] In some embodiments, the terminal device does not monitor to the PDCCH on the service cell during the subsequent PDCCH skipping duration from the completion of receiving a next symbol of the PDCCH after the terminal device receives the PDCCH skipping information.

[0105] At S303, the terminal device sends the SR, and monitors the PDCCH on the serving cell.

[0106] In some embodiments, if the terminal device transmits the SR through the PDCCH and the SR is in a pending state in the PDCCH skipping duration, then the terminal device stops PDCCH skipping, and monitors on the PDCCH on all activated serving cells; or the terminal device determines to monitor the PDCCH on at least one activated serving cell according to the related parameter of the LCP restriction of the uplink logical channel that triggers the SR.

[0107] Optionally, the terminal device determines to monitor the PDCCH on all activated serving cells in a case where the uplink logical channel that triggers the SR is not configured with the related parameter of the LCP restriction.

[0108] Optionally, in a case where the uplink logical channel that triggers the SR is not configured with the related parameter of the LCP restriction, the terminal device determines a first serving cell set that is allowed to transmit the uplink logical channel according to the related parameter of the LCP restriction; the terminal device determines to monitor the PDCCH on a serving cell corresponding to uplink scheduling information that can indicate any serving cell in the first serving cell set, that is, the terminal device determines to monitor the PDCCH on a serving cell corresponding to the PDCCH that can transmit the uplink scheduling indicating any serving cell in the first serving cell set.

[0109] Based on a channel monitoring method as illustrated in FIG. 4, a schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration of the embodiments of the disclosure is as illustrated in FIG. 5. In the PDCCH skipping duration, the terminal device stops monitoring the PDCCH before transmitting the SR. During the PDCCH skipping duration, the terminal device monitors the PDCCH on the serving cell after transmitting the SR.

[0110] For a scenario where the first information includes a Preamble, another optional detail processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 6, includes the following operations.

[0111] At S401, a terminal device receives configuration information sent by a network device through RRC signaling.

[0112] In some embodiments, the configuration information may include at least one of the following: a DRX configuration parameter, and a BFR related configuration.

[0113] Optionally, the configuration information includes:

[0114] a) the DRX configuration parameter, which may include: long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.

[0115] b) a BFR configuration parameter, which may include a non-competition-based RACH configuration for BRF, a candidate Channel State Information Reference Signal (CSI-RS) and/or an SSB list.

[0116] At S402, the terminal device receives the PDCCH skipping information sent by the network device corresponding to the serving cell.

[0117] In some embodiments, the PDCCH skipping information indicates the terminal device to skip the PDCCH monitoring. The PDCCH skipping information may include a PDCCH skipping duration.

[0118] In some embodiments, the terminal device does not monitor to the PDCCH on the service cell during the subsequent PDCCH skipping duration from the completion of receiving a next symbol of the PDCCH after the terminal device receives the PDCCH skipping information.

[0119] At S403, the terminal device sends the Preamble, and monitors the PDCCH at the RAR window or the Msg B window.

[0120] In some embodiments, if the terminal device triggers BFR in a PDCCH skipping duration, then the terminal device transmits the Preamble transmitted on corresponding RACH resources on the basis of a selected SSB, starts a RAR window for a four-operation random access case, or starts an Msg B window for a two-operation random access case. The terminal device stops the PDCCH skipping, and monitors the C-RNTI-scrambled PDCCH at the RAR window or the Msg B window.

[0121] Based on a channel monitoring method as illustrated in FIG. 6, another schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration of the embodiments of the disclosure is as illustrated in FIG. 7. In the PDCCH skipping duration, the terminal device stops monitoring the PDCCH before transmitting the Preamble. During the PDCCH skipping duration, the terminal device monitors the PDCCH on the serving cell after transmitting the SR.

[0122] Another optional processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 8, includes the following operations.

[0123] At S2001, a terminal device sends second information within a PDCCH skipping duration.

[0124] In some embodiments, the second information includes: uplink transmission based on CG resources, or a NACK message for downlink transmission received by the terminal device on the SPS resources in the PDCCH skipping duration. The uplink transmission based on the CG resources may be the uplink transmission transmitted on the CG resources.

[0125] At S2002, after transmitting the second information within the PDCCH skipping duration, the terminal device starts a retransmission timer that corresponds to a HARQ process corresponding to the second information, and resumes PDCCH monitoring.

[0126] In some embodiments, the terminal device resumes the PDCCH monitoring can also be understood that the terminal device is switched from a PDCCH monitoring skipping state into a PDCCH monitoring state.

[0127] In some embodiments, the PDCCH skipping duration may also be referred to as PDCCH skipping onduration, that is, the network device indicates the terminal device not to monitor the PDCCH in the PDCCH skipping onduration.

[0128] For the scenario where the second information includes the uplink transmission based on the CG resources, after the terminal device transmits the uplink transmission on the CG resources, an HARQ process i is used for the uplink transmission, and then the terminal device starts drx-HARQ-RTT-TimerUL corresponding to the HARQ process i at a first (time) symbol after the uplink transmission is completed. In the PDCCH skipping duration, the terminal device starts the drx-RetransmissionTimerUL corresponding to the HARQ process i, and simultaneously, monitors the PDCCH on the serving cell in a case where the DRX-HARQ-RTT-TimerUL, which corresponds to the HARQ process i corresponding to the uplink transmission data, is timeout.

[0129] For the scenario where the second information includes the NACK message for the downlink transmission received by the terminal device on the SPS resources within the PDCCH skipping duration, the PDSCH corresponds to an HARQ process k, then the terminal device starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process i after the terminal device completes the NACK feedback for the downlink transmission. In the PDCCH skipping duration, in a case where the DRX-HARQ-RTT-TimerDL corresponding to the HARQ process k is timeout, the terminal device starts the drx-RetransmissionTimerDL corresponding to the HARQ process k, and monitors the PDCCH on the serving cell, or monitors the PDCCH on the serving cell according to the configuration of the network device. The configuration of the network device may be carried in a system broadcast message or RRC signaling.

[0130] It is to be noted that, in the embodiments of the disclosure, the terminal device stops PDCCH skipping in a case of monitoring the PDCCH.

[0131] The channel monitoring method provided by the embodiments of the disclosure is described in detail below with respect to different contents included in the second information.

[0132] For a scenario where the second information includes the uplink transmission based on the CG resources, yet another optional detail processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 9, includes the following operations.

[0133] At S501, a terminal device receives configuration information sent by a network device through RRC signaling.

[0134] In some embodiments, the configuration information may include at least one of the following: a DRX configuration parameter, and a CG configuration parameter.

[0135] Optionally, the configuration information includes:

[0136] a) the DRX configuration parameter, which may include: long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.

[0137] b) the CG configuration parameter, which may include: CS-RNTI, which is the number of uplink HARQ processes reserved for CG, a CG resource cycle, a CG time-frequency resource, etc.

[0138] At S502, the terminal device receives the PDCCH skipping information sent by a network device corresponding to a serving cell.

[0139] In some embodiments, the PDCCH skipping information indicates the terminal device to skip the PDCCH monitoring. The PDCCH skipping information may include a PDCCH skipping duration.

[0140] In some embodiments, the terminal device does not monitor to the PDCCH on the service cell during the subsequent PDCCH skipping duration from the completion of receiving a next symbol of the PDCCH after the terminal device receives the PDCCH skipping information.

[0141] At S503, the terminal device sends the uplink transmission data on the CG resources, and monitors the PDCCH on the serving cell.

[0142] In some embodiments, if the terminal device transmits the uplink transmission data on the CG resources in the PDCCH skipping duration, an HARQ process i is used for the uplink transmission data, then the terminal device starts the DRX-HARQ-RTT-TimerUL corresponding to the HARQ process i at the first symbol after transmitting the uplink transmission data is sent, and the terminal device starts the drx-RetransmissionTimerUL corresponding to the HARQ process i, and simultaneously, monitors the PDCCH on the serving cell if the DRX-HARQ-RTT-TimerUL corresponding to the HARQ process i is timeout.

[0143] Based on a channel monitoring method as illustrated in FIG. 9, yet another schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration of the embodiments of the disclosure is as illustrated in FIG. 10. In the PDCCH skipping duration, the terminal device transmits the uplink transmission data on the CG resources, and the terminal device stops monitoring the PDCCH before the DRX-HARQ-RTT-TimerUL, which corresponds to the HARQ process i corresponding to the uplink transmission data, is timeout. In the PDCCH skipping duration, the terminal device starts the drx-RetransmissionTimerUL corresponding to the HARQ process i, and simultaneously, monitors the PDCCH on the serving cell in a case where the DRX-HARQ-RTT-TimerUL, which corresponds to the HARQ process i corresponding to the uplink transmission data, is timeout.

[0144] For a scenario where the second information includes the NACK message for the downlink transmission received by the terminal device in the PDCCH skipping duration, still another optional detailed processing flow of the channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 11, includes the following operations.

[0145] At S601, a terminal device receives configuration information sent by a network device through RRC signaling.

[0146] In some embodiments, the configuration information may include at least one of the following: a DRX configuration parameter, and an SPS configuration parameter.

[0147] Optionally, the configuration information includes:

[0148] a) the DRX configuration parameter, which may include: long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.

[0149] b) the SPS configuration parameter, which may include: a CS-RNTI, which is the number of downlink HARQ processes reserved for SPS, an SPS resource cycle, etc.

[0150] At S602, the terminal device receives the SPS resource indicated by the network device.

[0151] At S603, the terminal device receives the PDCCH skipping information sent by a network device corresponding to a serving cell.

[0152] In some embodiments, the PDCCH skipping information indicates the terminal device to skip the PDCCH monitoring. The PDCCH skipping information may include a PDCCH skipping duration.

[0153] In some embodiments, the terminal device does not monitor to the PDCCH on the service cell during the subsequent PDCCH skipping duration from the completion of receiving a next symbol of the PDCCH after the terminal device receives the PDCCH skipping information.

[0154] At S604, the terminal device sends the NACK message for the PDSCH which is transmitted by using the SPS resources and received by the terminal device within the PDCCH skipping duration, and monitors the PDCCH on the serving cell.

[0155] In some embodiments, the terminal device receives the PDSCH transmitted by the network device on the SPS resources in the PDCCH skipping duration, the PDSCH corresponds to an HARQ process k. The terminal device starts the DRX-HARQ-RTT-TimerDL corresponding to the HARQ process k after sending the NACK message for the received PDSCH to the network device. The terminal device starts the drx-RetransmissionTimerDL corresponding to the HARQ process k and monitors the PDCCH on the serving cell, or monitors the PDCCH on the serving cell according to the configuration of the network device in a case where the DRX-HARQ-RTT-TimerDL corresponding to the HARQ process k is timeout. The configuration of the network device may be carried in a system broadcast message or RRC signaling.

[0156] Based on the channel monitoring method as illustrated in FIG. 11, a schematic diagram that a terminal device monitors a PDCCH within a PDCCH skipping duration of the embodiments of the disclosure is as illustrated in FIG. 12. In the PDCCH skipping duration, the terminal device sends a NACK message for the received PDSCH to a network device, and the terminal device stops monitoring the PDCCH before the DRX-HARQ-RTT-TimerDL, which corresponds to the HARQ process k corresponding to the PDSCH, is timeout. In the PDCCH skipping duration, the terminal device starts the drx-RetransmissionTimerDL corresponding to HARQ process k, and simultaneously, the terminal device monitors the PDCCH on a serving cell in a case where the DRX-HARQ-RTT-TimerDL, which corresponds to the HARQ process k corresponding to the PDSCH, is timeout.

[0157] Another optional processing flow of a channel monitoring method provided by the embodiments of the disclosure, as illustrated in FIG. 13, includes the following operations.

[0158] At S801, a network device sends first configuration information. The first configuration information is used to determine whether the terminal device stops skipping the PDCCH monitoring under a first condition within the PDCCH skipping duration.

[0159] In some embodiments, the first condition includes that: the network device receives a NACK message sent by the terminal device for a PDSCH.

[0160] Correspondingly, in some embodiments, the method may also include the following operations.

[0161] A network device transmits a PDSCH to a terminal device on SPS resources in a PDCCH skipping duration. The network device receives the NACK message transmitted by the terminal device for the PDSCH. The first configuration information is used for the terminal device to determine whether to stop skipping the PDCCH after transmitting the NACK message for the PDSCH.

[0162] In various embodiments of the disclosure, it is clear that the terminal device resumes the PDCCH monitoring within the PDCCH skipping duration in the scenarios where the terminal device transmits the SR, the Preamble, the uplink transmission data transmitted on the CG resources, the NACK message for the PDSCH received by the terminal device within the PDCCH skipping duration, etc. Therefore, in the PDCCH skipping duration, the terminal device skips the PDCCH monitoring if the terminal device does not have a data transmission requirement; and the terminal device skips the PDCCH monitoring if the terminal device has a data transmission requirement. Thus, not only the scheduling performance of the terminal device is ensured, but also the power consumption of the terminal device can be reduced.

[0163] It should be understood that, in various embodiments of the disclosure, sequence numbers of the abovementioned processes do not mean execution sequences. The execution sequences of various processes should be determined according to functions and internal logic of the processes, and should not be construed as any limitation on the implementation processes of the embodiments of the disclosure.

[0164] In order to implement the abovementioned channel monitoring method, the embodiments of the disclosure provide a terminal device. A schematic diagram of an optional composition structure of the terminal device 900, as illustrated in FIG. 14, includes a first processing unit 901.

[0165] The first processing unit 901 is configured to resume PDCCH monitoring when a terminal device sends first information within a PDCCH skipping duration.

[0166] In some embodiments, the first information includes: an SR.

[0167] In some embodiments, the SR is in a pending state.

[0168] In some embodiments, the first processing unit 901 is configured to monitor the PDCCH on all activated serving cells.

[0169] In some embodiments, the first processing unit 901 is further configured to determine to monitor the PDCCH on at least one activated serving cell according to a related parameter of an LCP restriction of an uplink logical channel that triggers the SR.

[0170] In some embodiments, the first processing unit 901 is configured to determine to monitor the PDCCH on all activated serving cells in a case where the uplink logical channel that triggers the SR is not configured with the related parameter of the LCP restriction.

[0171] In some embodiments, the first processing unit 901 is configured to: determine a first serving cell set that is allowed to transmit the uplink logical channel according to the related parameter of the LCP restriction in a case where the uplink logical channel that triggers the SR is configured with the related parameter of the LCP restriction; and

[0172] determine to monitor the PDCCH on a serving cell corresponding to uplink scheduling information capable of indicating any serving cell in the first serving cell set.

[0173] In some embodiments, the first information includes a preamble. The preamble is sent on a corresponding random access channel resource based on a selected synchronous signal block in a case where the terminal device triggers beam failure recovery.

[0174] In some embodiments, the first processing unit 901 is further configured to start an RAR receiving window or an Msg B receiving window.

[0175] In some embodiments, the first processing unit 901 is configured to monitor the PDCCH at the RAR receiving window or the Msg B receiving window.

[0176] In some embodiments, the first processing unit 901 is further configured to stop skipping the PDCCH monitoring based on a configuration of a network device.

[0177] In order to implement the abovementioned channel monitoring method, the embodiments of the disclosure provide a network device. A schematic diagram of an optional composition structure of the network device 1000, as illustrated in FIG. 15, includes a first sending unit 1001.

[0178] The first sending unit 1001 is configured to send first configuration information. The first configuration information is used to determine whether the terminal device stops skipping the PDCCH monitoring under a first condition within the PDCCH skipping duration.

[0179] In some embodiments, the first condition includes that: the network device receives a NACK message sent by the terminal device for a PDSCH. Correspondingly, the network device 1000 may further include a receiving unit 1002.

[0180] The receiving unit 1002 is configured to receive the NACK message sent by the terminal device for the PDSCH.

[0181] In some embodiments, the PDSCH is transmitted based on SPS resources within the PDCCH skipping duration.

[0182] In some embodiments, the first configuration information is carried in a system broadcast message or RRC signaling.

[0183] In order to implement the abovementioned channel monitoring method, the embodiments of the disclosure provide a terminal device. A schematic diagram of an optional composition structure of the terminal device 3000, as illustrated in FIG. 16, includes a second sending unit 3001 and a second processing unit 3002.

[0184] The second sending unit 3001 is configured to transmit second information within a PDCCH skipping duration.

[0185] The second processing unit 3002 is configured to start a retransmission timer that corresponds to an HARQ process corresponding to the second information, and resume the PDCCH monitoring after the second sending unit transmits the second information within the PDCCH skipping duration.

[0186] In some embodiments, the second processing unit 3002 is configured to: start an RTT that corresponds to the HARQ process corresponding to the second information when transmitting the second information within the PDCCH skipping duration; and

[0187] in a case where the RTT is timeout, start the retransmission timer corresponding to the HARQ process for transmitting the second information, and resume the PDCCH monitoring.

[0188] In some embodiments, the second processing unit 3002 is configured to: in a case where the second information includes the uplink transmission, start the uplink retransmission timer corresponding to the HARQ process of the uplink transmission, and resumes the PDCCH monitoring.

[0189] In some embodiments, the uplink transmission is sent on CG resources.

[0190] In some embodiments, the second processing unit 3002 is configured to: in a case where the second information includes a NACK message for the downlink transmission received by the terminal device within the PDCCH skipping duration, start a downlink retransmission timer corresponding to the HARQ process of the downlink transmission, and resume the PDCCH monitoring.

[0191] In some embodiments, the downlink transmission is transmitted based on the SRS resources.

[0192] In some embodiments, the second processing unit 3002 is configured to monitor the PDCCH on a serving cell within a DRX activation period.

[0193] In some optional embodiment modes, the second processing unit 3002 is further configured to stop skipping the PDCCH monitoring.

[0194] In some embodiments, the second processing unit 3002 is further configured to stop skipping the PDCCH monitoring based on the configuration of the network device.

[0195] The embodiments of the disclosure further provide a terminal device, which includes a processor and a memory configured to store a computer program capable of running on the processor. The processor is configured to execute the operations of the channel monitoring method executed by the abovementioned terminal device when running the computer program.

[0196] The embodiments of the disclosure further provide a network device, which includes a processor and a memory configured to store a computer program capable of running on the processor. The processor is configured to execute the operations of the channel monitoring method executed by the abovementioned network device when running the computer program.

[0197] The embodiments of the disclosure further provides a chip, which may include a processor, configured to call and run a computer program in a memory to enable a device installed with the chip to execute the channel monitoring method executed by the abovementioned terminal device.

[0198] The embodiments of the disclosure further provides a chip, which may include a processor, configured to call and run a computer program in a memory to enable a device installed with the chip to execute the channel monitoring method executed by the abovementioned network device.

[0199] The embodiments of the disclosure further provide a storage medium, having stored thereon an executable program. The executable program implements the channel monitoring method executed by the abovementioned terminal device when being executed by a processor.

[0200] The embodiments of the disclosure further provide a storage medium, having stored thereon an executable program. The executable program implements the channel monitoring method executed by the abovementioned network device when being executed by a processor.

[0201] The embodiments of the disclosure further provide a computer program product, including computer program instructions. The computer program instructions enable a computer to execute the channel monitoring method executed by the abovementioned terminal device.

[0202] The embodiments of the disclosure further provide a computer program product, including computer program instructions. The computer program instructions enable a computer to execute the channel monitoring method executed by the abovementioned network device.

[0203] The embodiments of the disclosure further provide a computer program. The computer program enables a computer to execute the channel monitoring method executed by the abovementioned terminal device.

[0204] The embodiments of the disclosure further provide a computer program. The computer program enables a computer to execute the channel monitoring method executed by the abovementioned network device.

[0205] FIG. 17 illustrates a schematic diagram of hardware composition structure of an electronic device (terminal device or network device) according to an embodiment of the disclosure. The electronic device 700 includes: at least one processor 701, a memory 702 and at least one network interface 704. Various components of the electronic device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to implement connection and communication between these components. In addition to a data bus, the bus system 705 further includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are marked as the bus system 705 in FIG. 17.

[0206] It is to be understood that the memory 702 may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Ferromagnetic Random Access Memory (FRAM), a flash memory, a magnetic surface memory, an optical disk or a Compact Disc Read-Only Memory (CD-ROM); and the magnetic surface memory may be a magnetic disk memory or a magnetic tape memory. The volatile memory may be a RAM that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as a Static Random Access Memory (SRAM), a Synchronous Static Random Access Memory (SSRAM), a Dynamic Random Access Memory (DRAM), a Synchronous Dynamic Random Access Memory (SDRAM), a Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), an Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), a SyncLink Dynamic Random Access Memory (SLDRAM), and a Direct Rambus Random Access Memory (DRRAM). The memory 702 described in the embodiment of the disclosure is intended to include, but is not limited to, these and any other suitable types of memories.

[0207] The memory 702 in the embodiment of the disclosure is configured to store various types of data to support operation of the electronic device 700. Examples of such data include: any computer disclosure operated on the electronic device 700, such as an disclosure 7022. A program for implementing the method in the embodiment of the disclosure may be included in the disclosure program 7022.

[0208] The method disclosed in the abovementioned embodiment of the disclosure may be applied to the processor 701, or may be implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capability. During implementation, the operations of the foregoing method can be completed by hardware integrated logic circuits in the processor 701 or instructions in the form of software. The abovementioned processor 701 may be a general-purpose processor, a Digital Signal Processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. The processor 701 may implement or execute various methods, operations, and logical block diagrams disclosed in the embodiments of the disclosure. The general-purpose processor may be a microprocessor, or any conventional processor. Operations of the methods disclosed with reference to the embodiments of the disclosure may be directly performed and accomplished by a hardware decoding processor, or may be performed and accomplished by a combination of hardware and software modules in the decoding processor. A software module may be located in a storage medium. The storage medium is located in the memory 702, and the processor 701 reads information in the memory 702 and completes the operations of the foregoing method in combination with hardware thereof

[0209] In an exemplary embodiment, the electronic device 700 may be implemented by one or more Disclosure Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, MPUs, or other electronic elements for executing the foregoing methods.

[0210] The present disclosure is described with reference to flowcharts and/or block diagrams of the method, the device (system) and the computer program product according to the embodiments of the present disclosure. It is to be understood that each flow and/or block in the flowcharts and/or the block diagrams and a combination of the flows and/or the blocks in the flowcharts and/or the block diagrams may be implemented by computer program instructions. These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor or processors of other programmable data processing devices to generate a machine, so that an apparatus for achieving functions designated in one or more flows of the flowcharts and/or one or more blocks of the block diagrams is generated via instructions executed by the computers or the processors of the other programmable data processing devices.

[0211] These computer program instructions may also be stored in a computer readable memory capable of guiding the computers or the other programmable data processing devices to work in a specific mode, so that a manufactured product including an instruction apparatus is generated via the instructions stored in the computer readable memory, and the instruction apparatus achieves the functions designated in one or more flows of the flowcharts and/or one or more blocks of the block diagrams.

[0212] These computer program instructions may also be loaded to the computers or the other programmable data processing devices, so that processing implemented by the computers is generated by executing a series of operation operations on the computers or the other programmable devices, and therefore the instructions executed on the computers or the other programmable devices provide a operation of achieving the functions designated in one or more flows of the flowcharts and/or one or more blocks of the block diagrams.

[0213] It should be understood that the terms “system” and “network” in the disclosure are often used interchangeably herein. The term “and/or” in this disclosure describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character “/” in the disclosure generally indicates an “or” relationship between the associated objects.

[0214] The description above is only the preferred embodiment of the disclosure and is not intended to limit the scope of protection of the disclosure. Any modifications, equivalent replacements, improvements and the like made within the spirit and principle of the disclosure shall fall within the scope of protection of the disclosure.