CN115552978A - Method, device, equipment and storage medium for monitoring channel - Google Patents

Method, device, equipment and storage medium for monitoring channel Download PDF

Info

Publication number
CN115552978A
CN115552978A CN202080100747.8A CN202080100747A CN115552978A CN 115552978 A CN115552978 A CN 115552978A CN 202080100747 A CN202080100747 A CN 202080100747A CN 115552978 A CN115552978 A CN 115552978A
Authority
CN
China
Prior art keywords
logical channel
channel
indication information
configuration information
pdcch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202080100747.8A
Other languages
Chinese (zh)
Inventor
李海涛
胡奕
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN115552978A publication Critical patent/CN115552978A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Abstract

The application provides a method, a device, equipment and a storage medium for monitoring a channel, and relates to the technical field of communication. The method comprises the following steps: during the PDCCH skipping monitoring period, if a first request is triggered through a logic channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.

Description

Method, device, equipment and storage medium for monitoring channel Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring a channel.
Background
In a communication system, when DRX (Discontinuous Reception) is configured for a terminal device in a connected state, the terminal device monitors a PDCCH (Physical Downlink Control Channel) during a DRX active time (DRX active time).
At present, in order to reduce the PDCCH blind detection of the terminal device, a PDCCH skipping monitoring mechanism is introduced, that is, when the network device considers that the terminal device does not have uplink and downlink data transmission requirements in a future period of time, the network device can instruct the terminal device to skip the PDCCH monitoring in the period of time by sending a PDCCH skipping monitoring instruction, so that the purpose of saving power is achieved. In general, if the terminal device receives the PDCCH skip monitor indication, the terminal device does not monitor the PDCCH during the subsequent PDCCH skip monitor period, even if the terminal device is in the DRX active period during the PDCCH skip monitor period.
However, in some scenarios, the terminal device may trigger uplink transmission itself and expect the network device to have further response, for example, the terminal device triggers SR (Scheduling Request). In this case, since the terminal device may wait for the network device to respond, the terminal device may have a need to monitor the PDCCH. What kind of operation the terminal device should perform becomes a hot spot of research if the terminal device is in the PDCCH skip monitoring period at this time.
Disclosure of Invention
The embodiment of the application provides a method, a device, equipment and a storage medium for monitoring a channel, which can be used for solving the problem of what operation is to be executed after a terminal device is in a PDCCH (physical Downlink control channel) skipping monitoring period to trigger uplink transmission in the related art. The technical scheme is as follows:
in one aspect, a method for listening to a channel is provided, where the method includes:
during the monitoring skipping period of the physical downlink control channel PDCCH, if a first request is triggered through a logic channel, whether the PDCCH monitoring is recovered or not is determined according to first configuration information;
the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In another aspect, a method of listening to a channel is provided, the method including:
sending first configuration information to the terminal equipment;
the first configuration information is used for determining whether to recover PDCCH monitoring under the condition that the terminal equipment triggers a first request corresponding to the first configuration information through a logic channel during the PDCCH monitoring skipping period, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In another aspect, an apparatus for listening to a channel is provided, the apparatus comprising:
a determining module, configured to determine whether to resume PDCCH monitoring according to first configuration information if a first request is triggered through a logical channel when a PDCCH of a physical downlink control channel skips monitoring;
the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In another aspect, an apparatus for listening to a channel is provided, the apparatus comprising:
the sending module is used for sending first configuration information to the terminal equipment;
the first configuration information is used for the terminal device to determine whether to resume PDCCH monitoring when a first request corresponding to the first configuration information is triggered through a logical channel during a physical downlink control channel PDCCH skipping monitoring period, where the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In another aspect, an apparatus is provided that includes a processor and a memory, the memory storing at least one instruction for execution by the processor to implement the method of listening for a channel provided in any of the above aspects or to implement the method of listening for a channel provided in any of the above aspects.
In another aspect, a computer-readable storage medium is provided, which stores at least one instruction for execution by a processor to implement the method of listening for a channel provided in any of the above aspects, or to implement the method of listening for a channel provided in any of the above aspects.
In another aspect, a computer program product is provided, the computer program product comprising one or more computer programs that, when executed by a processor, are configured to implement the method of listening for a channel as provided in any of the above aspects, or the method of listening for a channel as provided in any of the above aspects.
The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:
and during the PDCCH monitoring skipping period, if a first request is triggered through a logic channel, determining whether to recover PDCCH monitoring according to the first configuration information. The first request is used for requesting the network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a schematic illustration of an implementation environment provided by an exemplary embodiment of the present application;
fig. 2 is a flowchart of a method of listening to a channel provided by an exemplary embodiment of the present application;
fig. 3 is a diagram of PDCCH monitoring provided by an exemplary embodiment of the present application;
fig. 4 is a diagram of PDCCH monitoring provided by another exemplary embodiment of the present application;
fig. 5 is a schematic diagram of PDCCH monitoring provided in another exemplary embodiment of the present application;
fig. 6 is a flowchart of a method of listening to a channel provided by another exemplary embodiment of the present application;
fig. 7 is a schematic structural diagram of an apparatus for listening to a channel according to an exemplary embodiment of the present application;
fig. 8 is a schematic structural diagram of an apparatus for listening to a channel according to an exemplary embodiment of the present application;
fig. 9 is a schematic structural diagram of an apparatus provided in another exemplary embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Before describing the method for monitoring a channel provided in the embodiment of the present application in detail, a brief description is first given to an implementation environment related to the embodiment of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a GSM (Global System For Mobile communications) System, a CDMA (Code Division Multiple Access) System, a WCDMA (Wideband Code Division Multiple Access) System, a GPRS (General Packet Radio Service), an LTE (Long Term Evolution ) System, an FDD (Frequency Division Duplex) System, a TDD (Time Division Duplex) System, an LTE-a (aa advanced Long Term Evolution, advanced Long Term Evolution) System, an NR (New relay, new Wireless) System, evolution System of NR System, LTE-U (LTE-based Access To Unlicensed Spectrum), NR-U (NR-based Access To Unlicensed Spectrum), UMTS (Universal Mobile telecommunications System), wiMAX (Worldwide Interoperability For Microwave Access), WLAN (Wireless Local Area network), wiFi (Wireless Fidelity), next-generation communication System, other communication System, and the like.
Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technology, mobile Communication systems will support not only conventional Communication, but also, for example, D2D (Device to Device) Communication, M2M (Machine to Machine) Communication, MTC (Machine Type Communication), and V2V (Vehicle to Vehicle) Communication, and the embodiments of the present application can also be applied to these Communication systems.
The system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.
For example, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the Network device 110 may be an eNB (evolved Node B), or a wireless controller in a CRAN (Cloud Radio Access Network), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.
The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, a connection via a wire Line, such as a connection via PSTN (Public Switched Telephone network), DSL (Digital Subscriber Line), digital cable, direct cable; and/or another data connection/network; and/or via a wireless interface, such as for a cellular network, a WLAN, a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or IoT (Internet of Things) devices. A terminal that is arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; a PCS (Personal Communications System) terminal that can combine a cellular radiotelephone with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or GPS (Global Positioning System) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, UE (User Equipment), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network or a terminal in a PLMN for future evolution, etc.
Optionally, D2D communication may be performed between terminal devices 120.
Alternatively, the 5G communication system or the 5G network may also be referred to as an NR system or an NR network.
Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and each network device may include other number of terminal devices within the coverage area, such as, in a handover scenario, a first network device and a second network device are typically included, the first network device is a source network device, and the second network device is a target network device, that is, a terminal is handed over from the first network device to the second network device.
Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which are not limited in this embodiment.
After describing the implementation environment related to the embodiments of the present application, a detailed description will be given below of a method for listening to a channel according to the embodiments of the present application with reference to the accompanying drawings.
Referring to fig. 2, fig. 2 is a flowchart of a method for listening to a channel according to an exemplary embodiment, where the method may be applied in the implementation environment shown in fig. 1 and is mainly performed by a terminal device, and the method may include the following implementation steps:
step 201: during the PDCCH skipping monitoring period, if a first request is triggered through a logic channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
The logical channel refers to an uplink logical channel, and as an example, the logical channel may be selected by the terminal device according to actual requirements.
As an example, the first Request is a Scheduling Request (SR).
Of course, the first request is only an SR example, and in other embodiments, the first request may also be another request, which is not limited in this application.
The first configuration information may include configuration information related to transmission of the first request, for example, a logical channel identifier of a logical channel triggering transmission of the first request, a request identifier of the first request, and a request resource identifier of a request resource for transmitting the first request. The request identifier may be used to determine request configuration information of the first request, for example, the request configuration information includes a prohibited duration, wherein the prohibited duration is used to indicate how many durations a second first request is not allowed to be retransmitted.
Illustratively, the first request is an SR, in which case the first configuration information may include the following parameters: scheduling request identification (schedulingRequestId), scheduling request resource identification (schedulingRequestResourceId), logical channel identification (logical ChannelIdentity).
Wherein, the scheduling request identifier is used for indicating the corresponding scheduling request configuration. For example, one scheduling request configuration may include a prohibit time period, where the prohibit time period is used to indicate how many time periods a second scheduling request is not allowed to be retransmitted.
Wherein, the scheduling request resource identifier is used for indicating the corresponding scheduling request resource.
Each logical channel identifier may indicate a scheduling request identifier, and the logical channel identifier and the scheduling request identifier may be in a one-to-one relationship or a many-to-one relationship. That is, one logical channel identifier corresponds to one scheduling request identifier, or a plurality of logical channel identifiers correspond to one scheduling request identifier.
In addition, each scheduling request resource identifier may indicate one scheduling request identifier, and the scheduling request resource identifier and the scheduling request identifier may be in a one-to-one relationship or a many-to-one relationship. That is, one scheduling request resource identifier corresponds to one scheduling request identifier, or multiple scheduling request resource identifiers correspond to one scheduling request identifier.
Each scheduling request resource identifier may indicate one PUCCH resource index, and the scheduling request resource identifier and the PUCCH resource index may be in a one-to-one relationship or a many-to-one relationship. That is, one scheduling request resource identifier corresponds to one PUCCH resource index, or a plurality of scheduling request resource identifiers correspond to one PUCCH resource index.
In this way, when the first request needs to be transmitted using PUCCH resources, the terminal device may uniquely determine one PUCCH resource index according to the above several sets of correspondence relationships, thereby determining the corresponding PUCCH resource.
The first configuration information may be configured by the network device to the terminal device in advance, for example, the first configuration information is configured by the network device through a Radio Resource Control (RRC) signaling, or the first configuration information is configured by the network device through a media Access Control (MAC CE) Element (MAC CE) signaling.
Generally, when the network device determines that the terminal device does not have a need for uplink and downlink data transmission within a next period of time, a PDCCH skipping monitoring indication is sent to the terminal device, and correspondingly, the terminal device receives the PDCCH skipping monitoring indication from the network device. Further, the network device may also configure a PDCCH skipping monitoring duration for the terminal device, that is, configure a duration for stopping monitoring the PDCCH for the terminal device, so that the terminal device does not monitor the PDCCH on the serving cell during the subsequent PDCCH skipping monitoring period, starting with the next symbol after the PDCCH is received, even if the terminal device is in the DRX active period.
In some embodiments, during the PDCCH monitoring skip period, the terminal device may trigger uplink transmission and expect the network device to have further response, for example, taking the first request as SR, if the terminal device has uplink data arriving but does not have uplink resource for BSR (Buffer Status Report), the terminal device triggers SR through a logical channel to request the network device to allocate uplink resource for the terminal device.
It should be noted that, after the terminal device sends the first request, the first request is in a waiting state, that is, enters a pending state, for example, after the terminal device sends the SR, the terminal device enters the pending state, so in some embodiments, the implementation of step 201 may be described as: during the PDCCH skipping monitoring period, if a first request is triggered through a logic channel and the first request is in a waiting state, whether PDCCH monitoring is resumed is determined according to first configuration information.
Since the terminal device waits for the response of the network device after sending the first request, the terminal device has a requirement for PDCCH monitoring, and if the terminal device is in the PDCCH skip monitoring period at this time, the terminal device can determine whether to resume PDCCH monitoring according to the first configuration information, that is, whether to continue to skip PDCCH monitoring based on a PDCCH skip monitoring instruction sent by the network device before, or to switch to a state of monitoring PDCCH.
And if the PDCCH monitoring is determined to be resumed, stopping the current PDCCH from skipping monitoring and starting monitoring the PDCCH. That is, the terminal device does not continue to skip PDCCH monitoring based on the PDCCH skip monitoring indication previously transmitted by the network device, but transitions to a state of monitoring the PDCCH.
It is understood that if it is determined that PDCCH monitoring is not resumed, the current PDCCH skipping monitoring is continued, that is, the terminal device continues to skip PDCCH monitoring based on a PDCCH skipping monitoring indication previously sent by the network device, that is, PDCCH monitoring is not resumed.
In this embodiment of the present application, during a PDCCH skipping monitoring period, if a first request is triggered through a logical channel, it is determined whether to resume the PDCCH monitoring according to first configuration information, where the first request is used to request a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
In implementation, according to different contents included in the first configuration information, the specific implementation process of the listening channel provided in the present application is different, and the following embodiments will be described separately.
In an embodiment, the method of listening to the channel may include, but is not limited to, the following:
step A1: during the PDCCH skipping monitoring period, if a first request is triggered through a logic channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
As an example, the first request is an SR.
In general, the network device may select whether to configure PUCCH resources for transmitting SR for the uplink logical channel. The network device may configure a plurality of PUCCH resources for transmitting the SR for the terminal device, where a configuration parameter corresponding to each PUCCH resource for transmitting the SR includes: a periodicity of the PUCCH resource, a slot, a time symbol offset, and a PUCCH resource index.
In implementation, if a logical channel triggers an SR, if the network device configures a PUCCH resource for transmitting the SR for the logical channel, the terminal device sends the SR on the PUCCH resource for transmitting the SR corresponding to the logical channel; otherwise, the terminal initiates a random access procedure.
The first configuration information may be pre-configured to the terminal device by the network device, for example, the first configuration information is configured by the network device through RRC signaling, or the first configuration information is configured by the network device through MAC CE signaling.
As an example, the first configuration information includes a logical channel identifier of the logical channel, in which case, the specific implementation of determining whether to resume PDCCH monitoring according to the first configuration information may include: and determining whether to recover PDCCH monitoring according to the indication information associated with the logical channel identifier.
Wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to resume. Illustratively, the indication information includes first indication information or second indication information, the first indication information is used for indicating that the PDCCH monitoring is allowed to be resumed, and the second indication information is used for indicating that the PDCCH monitoring is not allowed to be resumed.
As an example, the logical channel identifier is used to indicate the type of the logical channel.
As an example, the type of logical channel includes a first channel type and a second channel type; the logical channel identification includes a first channel identification and a second channel identification. The first channel identifier is associated with the first channel type, and the first channel identifier is associated with first indication information, the first indication information is used for indicating that the PDCCH monitoring is allowed to be resumed, the second channel identifier is associated with the second channel type, and the second channel identifier is associated with second indication information, and the second indication information is used for indicating that the PDCCH monitoring is not allowed to be resumed.
In general, the data transmitted by the logical channel corresponding to the first channel type has a high delay requirement, and the data transmitted by the logical channel corresponding to the second channel type has a relatively low delay requirement. Or, the logical channel corresponding to the first channel type is used for transmitting the specified service data, and the logical channel corresponding to the second channel type is used for transmitting the service data except the specified service data. The designated service data can be set according to actual requirements.
As an example, the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
Among them, the delay sensitive logical channel has high requirement on data transmission delay, and usually requires not to exceed a certain threshold, for example, the delay sensitive logical channel is usually used for transmitting service data such as instant messaging. The delay insensitive logical channel has relatively low requirement on data transmission delay, for example, the delay insensitive logical channel is generally used for downloading service data such as video.
The network device may configure the indication information according to the type of the logical channel and associate the indication information with a logical channel identifier, which includes a first channel identifier and a second channel identifier based on the associated indication information, for example, the first channel identifier may be represented by "LC1-1" and the second logical channel identifier may be represented by "LC1-2", where the prefix LC1 may be used to indicate the logical channel and the suffixes "1" and "0" are used to indicate the type of the logical channel. The first indication information may be associated with a first channel identification for delay sensitive logical channels, and the second indication information may be associated with a second channel identification for delay insensitive logical channels, for example. In this way, for the terminal device, it may be determined whether to resume PDCCH monitoring according to the indication information associated with the logical channel identifier of the logical channel.
Since the first indication information is used to indicate that the PDCCH monitoring is allowed to be resumed, if the terminal device determines that the indication information associated with the logical channel identifier is the first indication information, it indicates that the network device allows the terminal device to resume the PDCCH monitoring, that is, the PDCCH may be stopped from skipping the monitoring process.
Since the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed, if the terminal device determines that the indication information associated with the logical channel identifier is the second indication information, it indicates that the network device does not allow the terminal device to resume the PDCCH monitoring, that is, the PDCCH cannot be stopped to skip the monitoring process.
As another example, if there is no first indication information associated with the logical channel identifier, it is determined not to resume PDCCH monitoring.
If there is no first indication information associated with the logical channel identifier, it may be considered that the network device does not allow the terminal device to resume PDCCH monitoring, that is, it needs to continuously comply with a rule that PDCCH skips monitoring. Therefore, the terminal device determines not to resume PDCCH monitoring, i.e. to continue to skip PDCCH monitoring based on the PDCCH skip monitoring indication sent by the network device before, or it can be understood that the terminal device does not end the timing of the PDCCH skip monitoring duration.
As another example, if an indication information field in the first configuration information is empty, it is determined not to resume PDCCH monitoring, where the indication information field is used to fill the first indication information. That is to say, the indication information field for carrying the first indication information in the first configuration information is empty, and it may be considered that the PDCCH monitoring is not allowed to be resumed, in which case, the terminal device may determine not to resume the PDCCH monitoring.
That is, during the period that monitoring is skipped over by the PDCCH, the logical channel triggers SR, the terminal device sends SR on the PUCCH of one serving cell, and then determines whether the network device configures the first indication information allowing recovery of PDCCH monitoring for the logical channel identifier of the logical channel. And if the first indication information is configured, the terminal equipment stops the current PDCCH skipping monitoring and starts to monitor the PDCCH in the serving cell. Of course, if the second indication information that does not allow the PDCCH monitoring to be resumed is configured or no indication information is configured, the terminal device continues to be in a state where the PDCCH skips monitoring.
For example, as shown in fig. 3, since the network device configures the first indication information for LC1 (first channel identifier), the terminal device resumes PDCCH monitoring after LC1 triggers SR 1. Since the network device configures the second indication information for LC2 (second channel identifier), the terminal device does not resume PDCCH monitoring after the LC2 triggers SR 2.
In the embodiment of the present application, during the PDCCH skipping monitoring, if a first request is triggered through a logical channel, it is determined whether to resume PDCCH monitoring according to first configuration information. The first request is used for requesting the network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
In another embodiment, the method of listening to the channel may include, but is not limited to, the following:
step B1: during the PDCCH skipping monitoring period, if a first request is triggered through a logic channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
As an example, the first request is an SR.
In general, the network device may select whether to configure PUCCH resources for transmitting SR for the uplink logical channel. The network device may configure a plurality of PUCCH resources for transmitting the SR for the terminal device, where a configuration parameter corresponding to each PUCCH resource for transmitting the SR includes: a period, slot, time symbol offset, and PUCCH resource index of the PUCCH resource.
In this embodiment, the network device may select whether to configure PUCCH resources for transmitting SR for the uplink logical channel. The network equipment can configure a plurality of PUCCH resources for transmitting SR for the terminal equipment
In implementation, if a logical channel triggers an SR, if the network device configures a PUCCH resource for transmitting the SR for the logical channel, the terminal device sends the SR on the PUCCH resource for transmitting the SR corresponding to the logical channel; otherwise, the terminal initiates a random access procedure.
The first configuration information may be pre-configured to the terminal device by the network device, for example, the first configuration information is configured by the network device through RRC signaling, or the first configuration information is configured by the network device through MAC CE signaling.
As an example, if the first configuration information includes a scheduling request identifier, the scheduling request identifier is used to indicate a corresponding scheduling request configuration, and the scheduling request identifier is associated with a logical channel identifier of the logical channel, in this case, determining whether to resume implementation of PDCCH monitoring according to the first configuration information may include: and determining whether to recover the PDCCH monitoring according to the indication information associated with the scheduling request identifier.
As an example, the logical channel identifier is used to indicate a type of the logical channel, and the type of the logical channel includes a first channel type and a second channel type.
As an example, the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
Among them, the delay sensitive logical channel has high requirement on data transmission delay, and usually requires not to exceed a certain threshold, for example, the delay sensitive logical channel is usually used for transmitting service data such as instant messaging. The latency insensitive logical channel has relatively low requirement on data transmission latency, for example, the latency insensitive logical channel is usually used for downloading traffic data such as video.
Wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to resume. Illustratively, the indication information includes first indication information or second indication information, the first indication information is used for indicating that the PDCCH monitoring is allowed to be resumed, and the second indication information is used for indicating that the PDCCH monitoring is not allowed to be resumed.
The network device may configure the indication information according to the type of the logical channel, and associate the indication information with the scheduling request identifier corresponding to the logical channel identifier, for example, for a delay-sensitive logical channel, a first indication information may be associated with the corresponding scheduling request identifier, and for example, for a delay-insensitive logical channel, a second indication information may be associated with the corresponding scheduling request identifier. In this way, for the terminal device, it may be determined whether to resume PDCCH monitoring according to the indication information associated with the scheduling request identifier.
Since the first indication information is used to indicate that the PDCCH monitoring is allowed to be resumed, if the terminal device determines that the indication information associated with the scheduling request identifier is the first indication information, which indicates that the network device allows the terminal device to resume the PDCCH monitoring, that is, the PDCCH can be stopped from skipping the monitoring process.
Since the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed, if the terminal device determines that the indication information associated with the scheduling request identifier is the second indication information, it indicates that the network device does not allow the terminal device to resume the PDCCH monitoring, that is, the PDCCH cannot be stopped to skip the monitoring process.
As another example, if there is no first indication information associated with the scheduling request identity, it is determined not to resume PDCCH monitoring.
If the first indication information associated with the scheduling request identifier does not exist, it may be considered that the network device does not allow the terminal device to resume PDCCH monitoring, that is, it is necessary to continuously follow the rule that PDCCH skips monitoring. Therefore, the terminal device determines not to resume PDCCH monitoring, i.e. to continue to skip PDCCH monitoring based on the PDCCH skip monitoring indication sent by the network device before, or it can be understood that the terminal device does not end the timing of the PDCCH skip monitoring duration.
As another example, it is determined not to resume PDCCH monitoring if an indication information field in the first configuration information is empty, where the indication information field is used to fill the first indication information. That is to say, the indication information field for carrying the first indication information in the first configuration information is empty, and it may be considered that the PDCCH monitoring is not allowed to be resumed, in which case, the terminal device may determine not to resume the PDCCH monitoring.
In this way, for the terminal device, during the period that the PDCCH skips monitoring, the logical channel triggers the SR, the terminal device sends the SR on the PUCCH of one serving cell, and determines whether the first indication information allowing recovery of PDCCH monitoring is configured for the scheduling request identifier network device. And if the first indication information is configured, the terminal equipment stops the current PDCCH skipping monitoring and starts to monitor the PDCCH in the serving cell. Of course, if the second indication information that does not allow the PDCCH monitoring to be resumed is configured or no indication information is configured, the terminal device continues to be in a state where the PDCCH skips monitoring.
For example, as shown in fig. 4, since the network device configures the first indication information for the resource used by SR1, the terminal device resumes PDCCH monitoring after the logical channel triggers SR 1. Since the network device configures the second indication information for the resource used by SR2, the terminal device does not resume PDCCH monitoring after the logical channel triggers SR 2.
In this embodiment of the present application, during a PDCCH skipping monitoring period, if a first request is triggered through a logical channel, whether PDCCH monitoring is resumed is determined according to first configuration information, where the first request is used to request a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
In another embodiment, the method of listening to the channel may include, but is not limited to, the following:
step C1: during the PDCCH skipping monitoring period, if a first request is triggered through a logical channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
As an example, the first request is an SR.
In general, the network device may select whether to configure PUCCH resources for transmitting SR for the uplink logical channel. The network device may configure a plurality of PUCCH resources for transmitting the SR for the terminal device, where a configuration parameter corresponding to each PUCCH resource for transmitting the SR includes: a periodicity of the PUCCH resource, a slot, a time symbol offset, and a PUCCH resource index.
In implementation, if the logical channel triggers SR, if the network device configures a PUCCH resource for transmitting SR for the logical channel, the terminal device sends SR on the PUCCH resource for transmitting SR corresponding to the logical channel; otherwise, the terminal initiates a random access procedure.
The first configuration information may be pre-configured to the terminal device by the network device, for example, the first configuration information is configured by the network device through RRC signaling, or the first configuration information is configured by the network device through MAC CE signaling.
As an example, the first configuration information includes a scheduling request resource identifier, which is used to indicate a corresponding scheduling request resource, and the scheduling request resource identifier is associated with a logical channel identifier of the logical channel. In this case, determining whether to resume the implementation of PDCCH monitoring according to the first configuration information may include: and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
As an example, the logical channel identifier is used to indicate a type of the logical channel, and the type of the logical channel includes a first channel type and a second channel type.
As an example, the first channel type is a delay sensitive logical channel and the second channel type is.
The delay-sensitive logical channel has a high requirement on data transmission delay, and generally the requirement cannot exceed a certain threshold, for example, the delay-sensitive logical channel is generally used for transmitting service data such as instant messaging messages. The delay insensitive logical channel has relatively low requirement on data transmission delay, for example, the delay insensitive logical channel is generally used for downloading service data such as video.
Wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to resume. Illustratively, the indication information includes first indication information indicating that the PDCCH monitoring is allowed to be resumed or second indication information indicating that the PDCCH monitoring is not allowed to be resumed.
The network device may configure the indication information according to the type of the logical channel, and associate the indication information with the scheduling request resource identifier corresponding to the logical channel identifier, for example, for a delay-sensitive logical channel, a first indication information may be associated with the corresponding scheduling request resource identifier, and for example, for a delay-insensitive logical channel, a second indication information may be associated with the corresponding scheduling request resource identifier. In this way, for the terminal device, it may determine whether to resume PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
Since the first indication information is used to indicate that the PDCCH monitoring is allowed to be resumed, if the terminal device determines that the indication information associated with the scheduling request resource identifier is the first indication information, which indicates that the network device allows the terminal device to resume the PDCCH monitoring, the PDCCH can be stopped from skipping the monitoring process.
Since the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed, if the terminal device determines that the indication information associated with the scheduling request resource identifier is the second indication information, it indicates that the network device does not allow the terminal device to resume the PDCCH monitoring, that is, the PDCCH cannot be stopped to skip the monitoring process.
As another example, if there is no first indication information associated with the scheduling request resource identifier, it is determined not to resume PDCCH monitoring.
If the first indication information associated with the scheduling request resource identifier does not exist, it may be considered that the network device does not allow the terminal device to resume PDCCH monitoring, that is, it is necessary to continuously follow a rule that PDCCH skips monitoring. Therefore, the terminal device determines not to resume PDCCH monitoring, i.e. to continue to skip PDCCH monitoring based on the PDCCH skip monitoring indication sent by the network device before, or it can be understood that the terminal device does not end the timing of the PDCCH skip monitoring duration.
As another example, if an indication information field in the first configuration information is empty, it is determined not to resume PDCCH monitoring, where the indication information field is used to fill the first indication information. That is to say, the indication information field for carrying the first indication information in the first configuration information is empty, and it may be considered that the PDCCH monitoring is not allowed to be resumed, in which case, the terminal device may determine not to resume the PDCCH monitoring.
In this way, for the terminal device, during the period that the PDCCH skips monitoring, the logical channel triggers the SR, the terminal device sends the SR on the PUCCH of one serving cell, and determines whether the network device configures the first indication information that allows recovery of PDCCH monitoring for the scheduling request resource identifier corresponding to the logical channel identifier. And if the first indication information is configured, the terminal equipment stops the current PDCCH skipping monitoring and starts to monitor the PDCCH in the serving cell. Of course, if the second indication information that does not allow the PDCCH monitoring to be resumed is configured or no indication information is configured, the terminal device continues to be in a state where the PDCCH skips monitoring.
In this embodiment of the present application, during a PDCCH skipping monitoring period, if a first request is triggered through a logical channel, it is determined whether to resume the PDCCH monitoring according to first configuration information, where the first request is used to request a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
In another embodiment, the method of listening to the channel may include, but is not limited to, the following:
step D1: during the PDCCH skipping monitoring period, if a first request is triggered through a logical channel, whether PDCCH monitoring is resumed is determined according to first configuration information, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
As an example, the first request is an SR.
In general, the network device may select whether to configure PUCCH resources for transmitting the SR for the uplink logical channel. The network device may configure a plurality of PUCCH resources for transmitting the SR for the terminal device, where the configuration parameter corresponding to each PUCCH resource for transmitting the SR includes: a period, slot, time symbol offset, and PUCCH resource index of the PUCCH resource.
In implementation, if a logical channel triggers an SR, if the network device configures a PUCCH resource for transmitting the SR for the logical channel, the terminal device sends the SR on the PUCCH resource for transmitting the SR corresponding to the logical channel; otherwise, the terminal initiates a random access process.
The first configuration information may be configured by the network device to the terminal device in advance, for example, the first configuration information is configured by the network device through RRC signaling, or the first configuration information is configured by the network device through MAC CE signaling.
As an example, the first configuration information includes a scheduling limited duration corresponding to the logical channel, where the scheduling limited duration is used to indicate a maximum duration for waiting for the network device to schedule after the first request is sent for the logical channel. In this case, determining whether to resume the PDCCH monitoring according to the first configuration information may include: and determining the residual PDCCH skipping monitoring time length, and determining whether to recover PDCCH monitoring based on the scheduling limited time length and the residual PDCCH skipping monitoring time length.
For example, the scheduling restriction duration may be compared with the remaining PDCCH skip monitoring duration, and then it may be determined whether to resume PDCCH monitoring according to the comparison result.
As an example, the determining whether to resume PDCCH monitoring based on the scheduling restriction duration and the remaining PDCCH monitoring skipping duration may include: and if the scheduling limited time length is less than or equal to the monitoring skipping time length of the residual PDCCH, determining to restore the PDCCH monitoring.
If the scheduling limit duration is less than or equal to the remaining PDCCH monitoring skipping duration, it indicates that the remaining PDCCH monitoring skipping duration is longer, and in this case, if PDCCH monitoring is not resumed, scheduling of the network device may be missed. Therefore, in this case, the terminal device determines to resume PDCCH monitoring.
As another example, the specific implementation of determining whether to resume PDCCH monitoring based on the scheduling restriction duration and the remaining PDCCH skip monitoring duration may include: and if the scheduling limited time length is longer than the monitoring skipping time length of the residual PDCCH, determining not to restore the PDCCH monitoring.
If the scheduling limit time is longer than the remaining PDCCH monitoring skipping time, the remaining PDCCH monitoring skipping time is shorter, and in this case, the PDCCH monitoring can be automatically resumed without needing to elapse of time, so that the terminal equipment can determine not to resume the PDCCH monitoring.
For example, as shown in fig. 5, since the scheduling limited duration configured for LC1 by the network device is less than the remaining PDCCH monitoring skipping duration, after the LC1 triggers SR1, the terminal device resumes PDCCH monitoring. Since the scheduling limited duration configured for LC2 by the network device is greater than the remaining PDCCH monitoring skipping duration, after the LC2 triggers SR2, the terminal device does not resume PDCCH monitoring.
In the embodiment of the application, during the period that the monitoring is skipped by the PDCCH, if a first request is triggered through a logical channel, whether the monitoring of the PDCCH is resumed is determined according to first configuration information. The first request is used for requesting the network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
Referring to fig. 6, fig. 6 is a flowchart of a method for listening to a channel according to another exemplary embodiment, where the method may be applied in the foregoing implementation environment, and is mainly performed by a network device, and the method may include the following implementation steps:
step 601: and sending the first configuration information to the terminal equipment.
The first configuration information is used for the terminal device to determine whether to resume PDCCH monitoring when a first request corresponding to the first configuration information is triggered through a logical channel during PDCCH skip monitoring, where the first request is used to request a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
As an example, the first request is a scheduling request SR.
As an example, the first configuration information includes a logical channel identifier of a logical channel, in which case, according to a type of the logical channel, indication information is determined, the indication information is used for indicating whether to allow PDCCH monitoring to be resumed, and the indication information is associated with the logical channel identifier.
As an example, the first configuration information includes a scheduling request identifier indicating a corresponding scheduling request configuration, the scheduling request identifier being associated with a logical channel identifier of the logical channel. In this case, indication information for indicating whether to allow resumption of PDCCH monitoring is determined according to the type of the logical channel, and the indication information is associated with the scheduling request identity.
As an example, the first configuration information includes a scheduling request resource identifier indicating a corresponding scheduling request resource, and the scheduling request resource identifier is associated with a logical channel identifier of the logical channel. In this case, indication information for indicating whether to allow resumption of PDCCH monitoring is determined according to the type of the logical channel, and the indication information is associated with the scheduling request identity.
As an example, the logical channel identifier is used to indicate a type of the logical channel, and the type of the logical channel includes a first channel type and a second channel type.
As an example, determining the specific implementation of the indication information according to the type of the logical channel may include: if the type of the logical channel is a first channel type, determining that the indication information is first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be recovered; and if the type of the logical channel is a second channel type, determining that the indication information is second indication information, wherein the second indication information is used for indicating that the PDCCH monitoring is not allowed to be resumed.
As an example, the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
The delay-sensitive logical channel has a high requirement on data transmission delay, and generally the requirement cannot exceed a certain threshold, for example, the delay-sensitive logical channel is generally used for transmitting service data such as instant messaging messages. The latency insensitive logical channel has relatively low requirement on data transmission latency, for example, the latency insensitive logical channel is usually used for downloading traffic data such as video.
Wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to resume. Illustratively, the indication information includes first indication information indicating that the PDCCH monitoring is allowed to be resumed or second indication information indicating that the PDCCH monitoring is not allowed to be resumed.
The network device may configure the indication information according to the type of the logical channel and associate the indication information with the logical channel identifier, for example, for a delay-sensitive logical channel, a first indication information may be associated with the logical channel identifier, and for example, for a delay-insensitive logical channel, a second indication information may be associated with the logical channel identifier. In this way, for the terminal device, it may be determined whether to resume PDCCH monitoring according to the indication information associated with the logical channel identifier.
Alternatively, the network device may configure the indication information according to the type of the logical channel, and associate the indication information with the scheduling request identifier corresponding to the logical channel identifier, for example, for a delay-sensitive logical channel, a first indication information may be associated with the scheduling request identifier, and for example, for a delay-insensitive logical channel, a second indication information may be associated with the scheduling request identifier. In this way, for the terminal device, it may be determined whether to resume PDCCH monitoring according to the indication information associated with the scheduling request identifier.
Still alternatively, the network device may configure the indication information according to the type of the logical channel, and associate the indication information with the scheduling request resource identifier corresponding to the logical channel identifier, for example, for a delay-sensitive logical channel, the first indication information may be associated with the scheduling request resource identifier, and for example, for a delay-insensitive logical channel, the second indication information may be associated with the scheduling request resource identifier. In this way, for the terminal device, it may determine whether to resume PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
In a possible implementation manner of the present application, the network device may send the first configuration information to the terminal device through an RRC signaling; alternatively, the network device may send the first configuration information to the terminal device through the MAC CE.
It should be noted that, for the related implementation of the network device side, reference may be made to the related implementation of the terminal device side in the foregoing embodiments.
In this embodiment, the network device sends first configuration information to the terminal device, where the first configuration information is configuration information associated with transmission of the first request. During the PDCCH skipping monitoring period, the terminal equipment triggers a first request for requesting the network equipment to allocate uplink resources through a logic channel. According to the first configuration information, it may be determined whether to resume PDCCH monitoring. Thus, missing PDCCH monitoring can be avoided.
Referring to fig. 7, fig. 7 is a schematic structural diagram of an apparatus for listening to a channel according to an exemplary embodiment, where the apparatus may be configured in a terminal device, and the apparatus may include:
a determining module 710, configured to determine whether to resume PDCCH monitoring according to first configuration information if a first request is triggered through a logical channel during a period when a PDCCH of a physical downlink control channel skips monitoring; the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In a possible implementation manner of the present application, the first configuration information includes a logical channel identifier of the logical channel;
the determining module 720 is configured to: and determining whether to recover PDCCH monitoring according to the indication information associated with the logical channel identifier.
In a possible implementation manner of the present application, the first configuration information includes a scheduling request identifier, where the scheduling request identifier is used to indicate a corresponding scheduling request configuration, and the scheduling request identifier is associated with a logical channel identifier of the logical channel;
the determining module 720 is configured to: and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request identifier.
In a possible implementation manner of the present application, the first configuration information includes a scheduling request resource identifier, where the scheduling request resource identifier is used to indicate a corresponding scheduling request resource, and the scheduling request resource identifier is associated with a logical channel identifier of the logical channel;
the determining module 720 is configured to: and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
In a possible implementation manner of the present application, the indication information includes first indication information or second indication information, where the first indication information is used to indicate that the PDCCH monitoring is allowed to be resumed, and the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed.
In one possible implementation manner of the present application, the logical channel identifier is used to indicate a type of the logical channel.
In one possible implementation manner of the present application, the types of the logical channels include a first channel type and a second channel type; the logical channel identification comprises a first channel identification and a second channel identification; the first channel identifier is associated with the first channel type, and the first channel identifier is associated with first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be resumed; the second channel identifier is associated with the second channel type, and the second channel identifier is associated with second indication information, where the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed.
In a possible implementation manner of the present application, the first channel type is a delay-sensitive logical channel, and the second channel type is a delay-insensitive logical channel.
In a possible implementation manner of the present application, the first configuration information includes a scheduling limited duration corresponding to the logical channel, where the scheduling limited duration is used to indicate a maximum duration for waiting for network device scheduling after the first request is sent for the logical channel;
the determining module 720 is configured to: determining the monitoring time length skipped by the rest PDCCHs; and determining whether to resume PDCCH monitoring based on the scheduling limited duration and the remaining PDCCH skipping monitoring duration.
In one possible implementation manner of the present application, the determining module 720 is configured to: and if the scheduling limited duration is less than or equal to the monitoring skipping duration of the residual PDCCH, determining to restore the PDCCH monitoring.
In one possible implementation manner of the present application, the determining module 720 is configured to: and if the scheduling limited time length is greater than the monitoring skipping time length of the residual PDCCH, determining not to restore the PDCCH monitoring.
In a possible implementation manner of the present application, the determining module 720 is further configured to: and if the PDCCH monitoring is determined to be resumed, stopping the current PDCCH from skipping monitoring and starting monitoring the PDCCH.
In a possible implementation manner of the present application, the first configuration information is configured by the network device through radio resource control RRC signaling, or the first configuration information is configured by the network device through medium access control MAC control element CE signaling.
In a possible implementation manner of the present application, the first request is a scheduling request SR.
In the embodiment of the application, during the period that the monitoring is skipped by the PDCCH, if a first request is triggered through a logical channel, whether the monitoring of the PDCCH is resumed is determined according to first configuration information. The first request is used for requesting the network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request. Thus, missing PDCCH monitoring can be avoided.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an apparatus for listening to a channel according to an exemplary embodiment, where the apparatus may be configured in a network device, and the apparatus may include:
a sending module 810, configured to send first configuration information to a terminal device;
the first configuration information is used for the terminal device to determine whether to resume PDCCH monitoring when a first request corresponding to the first configuration information is triggered through a logical channel during a physical downlink control channel PDCCH skipping monitoring period, where the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
In a possible implementation manner of the present application, the first configuration information includes a logical channel identifier of the logical channel;
the sending module 810 is further configured to: determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered; and associating the indication information with the logical channel identification.
In a possible implementation manner of the present application, the first configuration information includes a scheduling request identifier, where the scheduling request identifier is used to indicate a corresponding scheduling request configuration, and the scheduling request identifier is associated with a logical channel identifier of the logical channel;
the sending module 810 is further configured to: determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered; and associating the indication information with the scheduling request identifier.
In a possible implementation manner of the present application, the first configuration information includes a scheduling request resource identifier, where the scheduling request resource identifier is used to indicate a corresponding scheduling request resource, and the scheduling request resource identifier is associated with a logical channel identifier of the logical channel;
the sending module 810 is further configured to: determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered; and associating the indication information with the scheduling request identification.
In a possible implementation manner of the present application, the types of the logical channels include a first channel type and a second channel type, and the sending module 810 is further configured to: if the type of the logical channel is the first channel type, determining that the indication information is first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be recovered; and if the type of the logical channel is the second channel type, determining that the indication information is second indication information, wherein the second indication information is used for indicating that the PDCCH monitoring is not allowed to be recovered.
In a possible implementation manner of the present application, the first channel type is a delay-sensitive logical channel, and the second channel type is a delay-insensitive logical channel.
In a possible implementation manner of the present application, the first request is a scheduling request SR.
In a possible implementation manner of this application, the sending module 810 is configured to:
sending the first configuration information to the terminal equipment through Radio Resource Control (RRC) signaling; alternatively, the first and second electrodes may be,
and sending the first configuration information to the terminal equipment through a Media Access Control (MAC) control unit (CE).
In this embodiment, the network device sends first configuration information to the terminal device, where the first configuration information is configuration information associated with transmission of the first request. During the PDCCH skipping monitoring period, the terminal equipment triggers a first request for requesting the network equipment to allocate uplink resources through a logic channel. According to the first configuration information, it may be determined whether to resume PDCCH monitoring. Thus, missing PDCCH monitoring can be avoided.
Referring to fig. 9, a schematic structural diagram of an apparatus provided in an exemplary embodiment of the present application is shown. The device may be the terminal device, or the device may be the network device. The apparatus may include: a processor 901, a receiver 902, a transmitter 903, a memory 904, and a bus 905.
The processor 901 includes one or more processing cores, and the processor 901 executes various functional applications and information processing by running software programs and modules.
The receiver 902 and the transmitter 903 may be implemented as one communication component, which may be a communication chip.
The memory 904 is coupled to the processor 901 via a bus 905.
The memory 904 may be configured to store at least one instruction, and the processor 901 is configured to execute the at least one instruction to implement the steps performed by the terminal device in the foregoing various method embodiments, or to implement the steps performed by the network device in the foregoing various method embodiments.
Further, the memory 904 may be implemented by any type or combination of volatile or non-volatile storage devices, including, but not limited to: magnetic or optical disk, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM (Electrically Erasable Programmable Read-Only Memory), SRAM (Static Random Access Memory), ROM (Read-Only Memory), magnetic Memory, flash Memory, PROM (Programmable Read-Only Memory).
The present application provides a computer-readable storage medium, in which at least one instruction is stored, and the at least one instruction is loaded and executed by the processor to implement the method provided by the above-mentioned method embodiments.
The present application also provides a computer program product, which when run on a computer causes the computer to execute the method provided by the above method embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (46)

  1. A method of listening to a channel, the method comprising:
    during the period that the PDCCH skips monitoring, if a first request is triggered through a logic channel, whether the PDCCH monitoring is recovered is determined according to first configuration information;
    the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
  2. The method of claim 1, wherein the first configuration information comprises a logical channel identification of the logical channel;
    the determining whether to recover the PDCCH monitoring according to the first configuration information includes:
    and determining whether to recover PDCCH monitoring according to the indication information associated with the logical channel identifier.
  3. The method of claim 1, wherein the first configuration information comprises a scheduling request identity indicating a corresponding scheduling request configuration, the scheduling request identity being associated with a logical channel identity of the logical channel;
    the determining whether to resume the PDCCH monitoring according to the first configuration information includes:
    and determining whether to recover the PDCCH monitoring according to the indication information associated with the scheduling request identifier.
  4. The method of claim 1, wherein the first configuration information comprises a scheduling request resource identification indicating a corresponding scheduling request resource, the scheduling request resource identification being associated with a logical channel identification of the logical channel;
    the determining whether to resume the PDCCH monitoring according to the first configuration information includes:
    and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
  5. The method of any one of claims 2-4, wherein the indication information comprises first indication information indicating that PDCCH monitoring is allowed to resume or second indication information indicating that PDCCH monitoring is not allowed to resume.
  6. The method according to any of claims 2-4, wherein the logical channel identity is used to indicate the type of the logical channel.
  7. The method of claim 6, wherein the types of logical channels comprise a first channel type and a second channel type; the logical channel identification comprises a first channel identification and a second channel identification;
    the first channel identifier is associated with the first channel type, and the first channel identifier is associated with first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be recovered;
    the second channel identifier is associated with the second channel type, and the second channel identifier is associated with second indication information, where the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed.
  8. The method of claim 7, wherein the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
  9. The method of claim 1, wherein the first configuration information comprises a scheduling-limited duration corresponding to the logical channel, and wherein the scheduling-limited duration is used to indicate a maximum duration for waiting for a network device to schedule after the first request is sent for the logical channel;
    the determining whether to resume the PDCCH monitoring according to the first configuration information includes:
    determining the monitoring time length skipped by the rest PDCCHs;
    and determining whether to resume PDCCH monitoring based on the scheduling limited duration and the remaining PDCCH skipping monitoring duration.
  10. The method of claim 9, wherein the determining whether to resume PDCCH monitoring based on the scheduling restriction duration and the remaining PDCCH skip monitoring duration comprises:
    and if the scheduling limited duration is less than or equal to the monitoring skipping duration of the residual PDCCH, determining to restore the PDCCH monitoring.
  11. The method of claim 9, wherein the determining whether to resume PDCCH monitoring based on the scheduling restriction duration and the remaining PDCCH skip monitoring duration comprises:
    and if the scheduling limited duration is greater than the monitoring skipping duration of the rest PDCCH, determining not to restore the PDCCH monitoring.
  12. The method of any one of claims 1-11, further comprising:
    and if the PDCCH monitoring is determined to be resumed, stopping the current PDCCH from skipping monitoring and starting monitoring the PDCCH.
  13. The method of any one of claims 1-12, wherein the first configuration information is configured by a network device through radio resource control, RRC, signaling or the first configuration information is configured by a network device through medium access control, MAC, control element, CE, signaling.
  14. The method according to any of claims 1-13, wherein the first request is a scheduling request, SR.
  15. A method of listening to a channel, the method comprising:
    sending first configuration information to the terminal equipment;
    the first configuration information is used for determining whether to recover PDCCH monitoring under the condition that the terminal equipment triggers a first request corresponding to the first configuration information through a logic channel during the PDCCH monitoring skipping period, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
  16. The method of claim 15, wherein the first configuration information includes a logical channel identification of the logical channel;
    the method further comprises the following steps:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the logical channel identification.
  17. The method of claim 15, wherein the first configuration information comprises a scheduling request identity indicating a corresponding scheduling request configuration, the scheduling request identity being associated with a logical channel identity of the logical channel;
    the method further comprises the following steps:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the scheduling request identification.
  18. The method of claim 15, wherein the first configuration information comprises a scheduling request resource identification indicating a corresponding scheduling request resource, the scheduling request resource identification being associated with a logical channel identification of the logical channel;
    the method further comprises the following steps:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the scheduling request identification.
  19. The method according to any of claims 16-18, wherein the type of logical channel comprises a first channel type and a second channel type, and the determining the indication information according to the type of logical channel comprises:
    if the type of the logical channel is the first channel type, determining that the indication information is first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be resumed;
    and if the type of the logical channel is the second channel type, determining that the indication information is second indication information, wherein the second indication information is used for indicating that the PDCCH monitoring is not allowed to be recovered.
  20. The method of claim 19, wherein the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
  21. The method according to any of claims 15-20, wherein the first request is a scheduling request, SR.
  22. The method of any one of claims 15-21, wherein sending first configuration information to a terminal device comprises:
    sending the first configuration information to the terminal equipment through Radio Resource Control (RRC) signaling; alternatively, the first and second electrodes may be,
    and sending the first configuration information to the terminal equipment through a Media Access Control (MAC) control unit (CE).
  23. An apparatus for listening to a channel, the apparatus comprising:
    a determining module, configured to determine whether to resume PDCCH monitoring according to first configuration information if a first request is triggered through a logical channel when a PDCCH of a physical downlink control channel skips monitoring;
    the first request is used for requesting a network device to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
  24. The apparatus of claim 23, wherein the first configuration information comprises a logical channel identification of the logical channel;
    the determination module is to:
    and determining whether to recover the PDCCH monitoring according to the indication information associated with the logical channel identifier.
  25. The apparatus of claim 23, wherein the first configuration information comprises a scheduling request identity indicating a corresponding scheduling request configuration, the scheduling request identity being associated with a logical channel identity of the logical channel;
    the determination module is to:
    and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request identifier.
  26. The apparatus of claim 23, wherein the first configuration information comprises a scheduling request resource identification indicating a corresponding scheduling request resource, the scheduling request resource identification being associated with a logical channel identification of the logical channel;
    the determination module is to:
    and determining whether to recover PDCCH monitoring according to the indication information associated with the scheduling request resource identifier.
  27. The apparatus of any one of claims 24-26, wherein the indication information comprises first indication information indicating that the PDCCH monitoring is allowed to be resumed or second indication information indicating that the PDCCH monitoring is not allowed to be resumed.
  28. The apparatus of any of claims 24-26, wherein the logical channel identification is to indicate a type of the logical channel.
  29. The apparatus of claim 28, wherein the types of logical channels comprise a first channel type and a second channel type; the logical channel identification comprises a first channel identification and a second channel identification;
    the first channel identifier is associated with the first channel type, and the first channel identifier is associated with first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be recovered;
    the second channel identifier is associated with the second channel type, and the second channel identifier is associated with second indication information, where the second indication information is used to indicate that the PDCCH monitoring is not allowed to be resumed.
  30. The apparatus of claim 29, wherein the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
  31. The apparatus of claim 23, wherein the first configuration information comprises a scheduling-limited duration corresponding to the logical channel, the scheduling-limited duration indicating a maximum duration of waiting for network device scheduling after sending the first request for the logical channel;
    the determination module is to:
    determining the monitoring skipping duration of the rest PDCCHs;
    and determining whether to resume PDCCH monitoring based on the scheduling limited duration and the remaining PDCCH skipping monitoring duration.
  32. The apparatus of claim 31, wherein the determination module is to:
    and if the scheduling limited duration is less than or equal to the monitoring skipping duration of the residual PDCCH, determining to restore the PDCCH monitoring.
  33. The apparatus of claim 31, wherein the determination module is to:
    and if the scheduling limited time length is greater than the monitoring skipping time length of the residual PDCCH, determining not to restore the PDCCH monitoring.
  34. The apparatus of any one of claims 23-33, wherein the determination module is further to:
    and if the PDCCH monitoring is determined to be resumed, stopping the current PDCCH skipping monitoring and starting to monitor the PDCCH.
  35. The apparatus of any one of claims 23-34, wherein the first configuration information is configured by the network device through radio resource control, RRC, signaling or the first configuration information is configured by the network device through medium access control, MAC, control element, CE, signaling.
  36. The apparatus according to any of claims 23-35, wherein the first request is a scheduling request, SR.
  37. An apparatus for listening to a channel, the apparatus comprising:
    the sending module is used for sending first configuration information to the terminal equipment;
    the first configuration information is used for determining whether to recover PDCCH monitoring under the condition that the terminal equipment triggers a first request corresponding to the first configuration information through a logic channel during the PDCCH monitoring skipping period, wherein the first request is used for requesting network equipment to allocate uplink resources, and the first configuration information is configuration information associated with transmission of the first request.
  38. The apparatus of claim 37, wherein the first configuration information comprises a logical channel identification of the logical channel;
    the sending module is further configured to:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the logical channel identification.
  39. The apparatus of claim 37, wherein the first configuration information comprises a scheduling request identity indicating a corresponding scheduling request configuration, the scheduling request identity being associated with a logical channel identity of the logical channel;
    the sending module is further configured to:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the scheduling request identification.
  40. The apparatus of claim 37, wherein the first configuration information comprises a scheduling request resource identification indicating a corresponding scheduling request resource, the scheduling request resource identification being associated with a logical channel identification of the logical channel;
    the sending module is further configured to:
    determining indication information according to the type of the logical channel, wherein the indication information is used for indicating whether the PDCCH monitoring is allowed to be recovered;
    and associating the indication information with the scheduling request identification.
  41. The apparatus of any one of claims 38-40, wherein the types of logical channels comprise a first channel type and a second channel type, the sending module further to:
    if the type of the logical channel is the first channel type, determining that the indication information is first indication information, wherein the first indication information is used for indicating that the PDCCH monitoring is allowed to be recovered;
    and if the type of the logical channel is the second channel type, determining that the indication information is second indication information, wherein the second indication information is used for indicating that the PDCCH monitoring is not allowed to be recovered.
  42. The apparatus of claim 41, wherein the first channel type is a delay sensitive logical channel and the second channel type is a delay insensitive logical channel.
  43. The apparatus according to any of claims 37-42, wherein the first request is a scheduling request, SR.
  44. The apparatus of any one of claims 37-43, wherein the sending module is to:
    sending the first configuration information to the terminal equipment through Radio Resource Control (RRC) signaling; alternatively, the first and second electrodes may be,
    and sending the first configuration information to the terminal equipment through a Media Access Control (MAC) control unit (CE).
  45. An apparatus comprising a processor and a memory, the memory storing at least one instruction for execution by the processor to implement a method of listening for a channel as provided in any of claims 1-14 or a method of listening for a channel as provided in any of claims 15-22.
  46. A computer-readable storage medium, characterized in that the computer-readable storage medium stores at least one instruction for execution by a processor to implement the method of listening for a channel as provided in any one of claims 1-14 or the method of listening for a channel as provided in any one of claims 15-22.
CN202080100747.8A 2020-05-22 2020-05-22 Method, device, equipment and storage medium for monitoring channel Pending CN115552978A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091919 WO2021232433A1 (en) 2020-05-22 2020-05-22 Channel monitoring method and apparatus, and device and storage medium

Publications (1)

Publication Number Publication Date
CN115552978A true CN115552978A (en) 2022-12-30

Family

ID=78707749

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080100747.8A Pending CN115552978A (en) 2020-05-22 2020-05-22 Method, device, equipment and storage medium for monitoring channel

Country Status (2)

Country Link
CN (1) CN115552978A (en)
WO (1) WO2021232433A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116887358A (en) * 2022-03-28 2023-10-13 维沃移动通信有限公司 PDCCH monitoring method, terminal, network equipment and medium

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483925A (en) * 2008-01-08 2009-07-15 华硕电脑股份有限公司 Method of receiving signaling and related communication device
CN102123399A (en) * 2010-01-08 2011-07-13 华为技术有限公司 Scheduling request method and device
CN102655666A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Scheduling delay method and system
CN104081856A (en) * 2013-01-25 2014-10-01 华为技术有限公司 Uplink resource allocation method, UE and base station
US20150181571A1 (en) * 2012-08-15 2015-06-25 Lg Electronics Inc. Method monitoring pdcch based on drx and communication device thereof
US20160157256A1 (en) * 2014-12-01 2016-06-02 Asustek Computer Inc. Method and apparatus for handling prohibit timer for scheduling request (sr) in a wireless communication system
US20170118747A1 (en) * 2015-10-22 2017-04-27 Qualcomm Incorporated Harq and control channel timing for enhanced machine type communications (emtc)
CN109429258A (en) * 2017-07-17 2019-03-05 中国移动通信有限公司研究院 A kind of indicating means of channel-monitoring, monitor method, terminal and network side equipment
CN109792792A (en) * 2016-09-30 2019-05-21 Lg 电子株式会社 PDCCH monitoring after DRX is configured or reconfigured
US20190190661A1 (en) * 2016-08-10 2019-06-20 Huawei Technologies Co., Ltd. Hybrid automatic repeat request method and terminal device
WO2019196663A1 (en) * 2018-04-13 2019-10-17 维沃移动通信有限公司 Method for monitoring physical downlink control channel, user equipment, and network side device
WO2020011180A1 (en) * 2018-07-13 2020-01-16 维沃移动通信有限公司 Channel detection instruction method, terminal, and network device
CN110830198A (en) * 2018-08-09 2020-02-21 华为技术有限公司 Control information transmission method and equipment
CN110868749A (en) * 2018-08-28 2020-03-06 华为技术有限公司 Communication method, communication apparatus, and storage medium
WO2020057489A1 (en) * 2018-09-18 2020-03-26 电信科学技术研究院有限公司 Channel monitoring method and apparatus, energy saving signal processing method and apparatus, terminal, and network side device
CN110958622A (en) * 2018-09-27 2020-04-03 电信科学技术研究院有限公司 Information sending and receiving method and device, terminal and base station
WO2020077643A1 (en) * 2018-10-19 2020-04-23 Oppo广东移动通信有限公司 Wireless communication method and terminal device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10057851B2 (en) * 2015-01-06 2018-08-21 Mediatek Inc. Wireless communication method and device
US20190116552A1 (en) * 2017-10-18 2019-04-18 Apple Inc. Power Efficient Downlink Control Information Framework for Cellular Communication
CN111148052B (en) * 2020-01-21 2023-03-24 展讯通信(上海)有限公司 State determination method, system, medium, and electronic device

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483925A (en) * 2008-01-08 2009-07-15 华硕电脑股份有限公司 Method of receiving signaling and related communication device
CN102123399A (en) * 2010-01-08 2011-07-13 华为技术有限公司 Scheduling request method and device
CN102655666A (en) * 2011-03-02 2012-09-05 中兴通讯股份有限公司 Scheduling delay method and system
US20130336301A1 (en) * 2011-03-02 2013-12-19 Zte Corporation Method and System for Delay Scheduling
US20150181571A1 (en) * 2012-08-15 2015-06-25 Lg Electronics Inc. Method monitoring pdcch based on drx and communication device thereof
CN104081856A (en) * 2013-01-25 2014-10-01 华为技术有限公司 Uplink resource allocation method, UE and base station
US20160157256A1 (en) * 2014-12-01 2016-06-02 Asustek Computer Inc. Method and apparatus for handling prohibit timer for scheduling request (sr) in a wireless communication system
US20170118747A1 (en) * 2015-10-22 2017-04-27 Qualcomm Incorporated Harq and control channel timing for enhanced machine type communications (emtc)
US20190190661A1 (en) * 2016-08-10 2019-06-20 Huawei Technologies Co., Ltd. Hybrid automatic repeat request method and terminal device
CN109792792A (en) * 2016-09-30 2019-05-21 Lg 电子株式会社 PDCCH monitoring after DRX is configured or reconfigured
CN109429258A (en) * 2017-07-17 2019-03-05 中国移动通信有限公司研究院 A kind of indicating means of channel-monitoring, monitor method, terminal and network side equipment
WO2019196663A1 (en) * 2018-04-13 2019-10-17 维沃移动通信有限公司 Method for monitoring physical downlink control channel, user equipment, and network side device
CN110381569A (en) * 2018-04-13 2019-10-25 维沃移动通信有限公司 Monitor method, user equipment and the network side equipment of Physical Downlink Control Channel
WO2020011180A1 (en) * 2018-07-13 2020-01-16 维沃移动通信有限公司 Channel detection instruction method, terminal, and network device
CN110830198A (en) * 2018-08-09 2020-02-21 华为技术有限公司 Control information transmission method and equipment
CN110868749A (en) * 2018-08-28 2020-03-06 华为技术有限公司 Communication method, communication apparatus, and storage medium
WO2020057489A1 (en) * 2018-09-18 2020-03-26 电信科学技术研究院有限公司 Channel monitoring method and apparatus, energy saving signal processing method and apparatus, terminal, and network side device
CN110958622A (en) * 2018-09-27 2020-04-03 电信科学技术研究院有限公司 Information sending and receiving method and device, terminal and base station
WO2020077643A1 (en) * 2018-10-19 2020-04-23 Oppo广东移动通信有限公司 Wireless communication method and terminal device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
""R2-1908072_EmailDisc-27_PDCCH-skipping - summary - final"", 3GPP TSG_RAN\\WG2_RL2, 3 May 2019 (2019-05-03) *
CATT: "R2-1905665 "Report of [105bis#27][NR/Power Saving] - PDCCH skipping (CATT)"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 3 May 2019 (2019-05-03), pages 19 *
HUAWEI, HISILICON: "R2-1906904 "Further discussion on the impact of DCI-based PDCCH skipping"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 3 May 2019 (2019-05-03), pages 4 - 6 *

Also Published As

Publication number Publication date
WO2021232433A1 (en) 2021-11-25

Similar Documents

Publication Publication Date Title
US20230123151A1 (en) Data transmission method and device
CN108541034B (en) Apparatus and method for processing state transition
WO2020019187A1 (en) Channel monitoring method and apparatus, terminal device, and network device
MX2013003423A (en) Method and apparatus for avoiding in-device coexistence interference.
CN113645164B (en) Communication method, terminal equipment and network equipment
CN113196858B (en) Method and device for sending release auxiliary indication message
WO2022077442A1 (en) Method and apparatus for multicast and broadcast services
CN115004605A (en) Data transmission method and device and terminal equipment
WO2020001123A1 (en) Downlink control channel detection method and apparatus, and terminal device
CN115004789A (en) Channel monitoring method, electronic equipment and storage medium
US20220053580A1 (en) Information processing method, and first and second terminal devices
CN115767783A (en) Data transmission method and device, network equipment and terminal
WO2021232433A1 (en) Channel monitoring method and apparatus, and device and storage medium
US20230042849A1 (en) Multi-USIM UE Assistance Information with Unavailable Time
JP7262610B2 (en) Channel transmission methods, electronics and storage media
CN113115257B (en) Connection configuration method, equipment and storage medium
EP4048015A1 (en) Energy detection threshold value determination method and apparatus
CN115039452A (en) Channel monitoring method, electronic equipment and storage medium
CN114667800A (en) Method and device for determining activation period
WO2022205266A1 (en) Method and apparatus for data transmission in non-connected state
EP4307776A1 (en) Communication method and apparatus
KR102571050B1 (en) Timer-based processing method, terminal device and network device
US20220322377A1 (en) Method for transmitting data, and devices
CN111771417B (en) Bandwidth part activation method and related equipment
CN112640508B (en) Control method for data replication and transmission, terminal equipment and network equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination