Communication method and device in cell discontinuous sending / receiving scene

Abstract

The embodiment of the invention provides a communication method and device in a cell discontinuous sending / receiving scene, and the method comprises the steps that when a network is in a network energy-saving mode, terminal equipment does not trigger a scheduling request and / or executes a behavior related to the network energy-saving mode for a suspended scheduling request (SR). According to the embodiment of the invention, when the network is in the network energy-saving mode, the terminal equipment does not trigger the SR, so that the suspended SR can be prevented from triggering a random access process, and the network energy consumption is reduced. And on the other hand, when the network is in the network energy-saving mode, for the pending SR, the terminal equipment executes behaviors related to the network energy-saving mode, so that the suspended SR does not enable the terminal to release uplink configuration.

Description

Communication method and device in cell discontinuous transmission / reception scenario Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] As a crucial component of new global infrastructure, 5G (fifth-generation mobile communication technology) communications networks have experienced rapid global development in recent years. As networks scale, operators' energy consumption continues to rise. According to data released by China's Ministry of Industry and Information Technology, energy consumption is projected to increase by approximately 80% between 2015 and 2022.

[0003] With the rollout of 5G and the widespread commercialization of 5G active antenna units (AAUs), energy consumption is expected to increase exponentially compared to the remote radio units (RRUs) primarily used in 3G and 4G, due to the higher power consumption of AAUs. 5G defines three major service types: enhanced mobile broadband (eMBB), massive machine type of communication (mMTC), and ultra-reliable low-latency communication (URLLC). This is driving an increase in bursty small packet traffic and the 24 / 7 operation of base stations. The average daily energy consumption of 5G sites is expected to be more than double that of 4G.

[0004] The 3rd Generation Partnership Project (3GPP) has introduced key technologies such as Massive MIMO and increased RF bandwidth in the 5G era. 5G supports higher data rates and greater data traffic, requiring more transmission bandwidth. High-frequency bands will be the primary frequency band for future 5G expansion. However, the transmission characteristics of high-frequency bands limit site coverage, resulting in denser deployment of 5G sites. Furthermore, the increased energy consumption will place significant pressure on operators' operating costs. Therefore, network energy conservation is crucial for reducing operating costs, and energy conservation in 5G networks is a pressing issue.

[0005] To achieve energy conservation, network devices can implement energy conservation in the time, frequency, spatial, and / or energy domains, depending on network load. For example, in the spatial and energy domains, network devices can power down some antennas when the load is low. In the time domain, network devices can implement cell-level discontinuous transmission / reception technology, which prevents network devices from transmitting and / or receiving signals during certain sleep periods, thereby achieving energy conservation.

[0006] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0007] Summary of the Invention

[0008] The inventors have discovered that for connected mode user equipments (UEs), during the cell discontinuous transmitting / receiving (DTX / DRX) inactive phase, at least the following candidate channels / signals are considered not to be transmitted / received:

[0009] Downside:

[0010] Periodic / semi-persistent CSI-RS (Channel State Information-Reference Signal) (including TRS (Tracking RS));

[0011] PRS (Positioning Reference Signal, positioning reference signal);

[0012] PDCCH (Physical Downlink Control Channel) scrambled with the UE-specific RNTI (Radio Network Temporary Identity);

[0013] PDCCH in Type-3 CSS (Common Search Space);

[0014] SPS PDCCH (semi-persistently scheduled PDCCH);

[0015] Uplink:

[0016] SR (Scheduling Request);

[0017] Periodic / semi-persistent CSI (Channel State Information) report (CSI report);

[0018] Periodic / semi-persistent SRS (Sounding Reference Signal, detection (sounding) reference signal);

[0019] CG (Configured Grant)-PUSCH (Physical Uplink Shared Channel);

[0020] That is, for connected mode UEs, during the cell DTX / DRX inactive phase, the UE does not send an SR. This interrupts the process of triggering an SR to request uplink resources and the sending of the triggered pending SR, thus causing problems.

[0021] To address the above issues, embodiments of the present application provide a communication method and apparatus in a cell discontinuous transmission / reception scenario.

[0022] According to one aspect of an embodiment of the present application, a communication apparatus is provided, configured in a terminal device, the apparatus comprising:

[0023] A processing unit is configured to not trigger a scheduling request and / or perform actions related to the network energy saving mode for a pending scheduling request (SR) when the network is in the network energy saving mode.

[0024] In some embodiments, the network energy saving mode refers to at least one of the following:

[0025] The NES mode is activated.

[0026] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0027] The terminal equipment is in the inactive state of cell DTX / DRX.

[0028] In some embodiments, the scheduling request includes at least one of the following:

[0029] Buffer Status Report (BSR) scheduling request;

[0030] Beam Failure Recovery (BFR) scheduling request;

[0031] Scheduling requests for consistent LBT failure recovery;

[0032] Integration and Access Backhaul (IAB) related scheduling requests;

[0033] Positioning-related scheduling requests;

[0034] Non-terrestrial network (NTN) related scheduling requests.

[0035] In some embodiments, the behaviors related to the network energy saving mode include at least one of the following:

[0036] Cancel the pending scheduling request (pending SR);

[0037] It is considered that there are no valid PUCCH resources configured for the pending SR;

[0038] Consider SR transmission to be a low-priority SR transmission;

[0039] Suspend SR counter;

[0040] Do not initiate a random access process;

[0041] No emptying and / or releasing operations are performed;

[0042] Use a larger maximum SR transmission time (sr-TransMax).

[0043] According to another aspect of an embodiment of the present application, a communication device is provided, configured in a network device, the device comprising:

[0044] The first indicating unit indicates information related to network energy saving to the terminal device.

[0045] One of the beneficial effects of the embodiments of the present application is that, according to the embodiments of the present application, when the network is in network energy-saving mode, the terminal device does not trigger an SR, thereby preventing the pending SR from triggering a random access procedure, thereby reducing network energy consumption. Furthermore, when the network is in network energy-saving mode, for a pending SR, the terminal device performs actions related to the network energy-saving mode, thereby preventing the pending SR from causing the terminal to release its uplink configuration.

[0046] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0047] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0048] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0050] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0051] FIG2 is a schematic diagram of using legacy BFR MAC CE to carry secondary cell BFR information;

[0052] FIG3 is a schematic diagram of using enhanced BFR MAC CE to carry BFR information of a secondary cell;

[0053] FIG4 is a schematic diagram of a communication method according to an embodiment of the present application;

[0054] FIG5 is another schematic diagram of the communication method according to an embodiment of the present application;

[0055] FIG6 is a schematic diagram of a communication device according to an embodiment of the present application;

[0056] FIG7 is another schematic diagram of a communication device according to an embodiment of the present application;

[0057] FIG8 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0058] FIG9 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0059] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0060] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0061] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0062] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0063] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0064] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0065] Base stations may include, but are not limited to, Node B (NB), evolved Node B (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, IAB-DUs, or IAB-donors. The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. The terms "cell" and "base station" may be used interchangeably to avoid confusion.

[0066] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT, a station, and so on.

[0067] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0068] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0069] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0070] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0071] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0072] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0073] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0074] In the following description, “if,” “in the case of,” and “when” can be used interchangeably without causing confusion.

[0075] In an embodiment of the present application, the scheduling request is used to request UL-SCH (Uplink Shared Channel) resources for new transmission.

[0076] A MAC (Media Access Control) entity can be configured with zero, one, or multiple SR configurations. An SR configuration consists of a set of PUCCH (Physical Uplink Control Channel) resources for SR across different BWPs (Bandwidth Parts) and cells. For logical channel or SCell (secondary cell) beam failure recovery and persistent LBT (listen before talk) failure recovery, at most one PUCCH resource for SR is configured per BWP. For logical channels serving radio bearers configured with SDT (Short Data Transfer), no PUCCH resources for SR are configured for SDT. For beam failure recovery of the BFD-RS (Beam Failure Detection-Reference Signal) set of the serving cell, at most two PUCCH resources for SR are configured per BWP configuration. For positioning measurement gap activation / deactivation requests, a dedicated SR configuration is configured.

[0077] Each SR configuration corresponds to one or more logical channels and / or SCell beam failure recovery and / or persistent LBT failure recovery and / or beam failure recovery of a BFD-RS set and / or positioning measurement gap activation / deactivation request. Each logical channel, SCell beam failure recovery, beam failure recovery of a BFD-RS set and persistent LBT failure recovery can be mapped to zero or one SR configuration configured by RRC (Radio Resource Control). The SR configuration of the logical channel that triggers the BSR (Buffer Status Report) or the SCell beam failure recovery or the beam failure recovery of a BFD-RS set or the persistent LBT failure recovery (if such a configuration exists) or the positioning measurement gap activation / deactivation request is regarded as the corresponding SR configuration for the triggered SR. Any SR configuration can be used for the SR triggered by a Pre-emptive BSR or a timing advance report.

[0078] The RRC configures the following parameters for the scheduling request process:

[0079] -sr-ProhibitTimer (configured per SR);

[0080] -sr-TransMax (per SR configuration).

[0081] The following UE variables are used in the scheduling request procedure:

[0082] -SR_COUNTER (according to SR configuration).

[0083] If an SR is triggered and no other SR corresponding to the same SR configuration is pending, the MAC entity shall set the SR_COUNTER of the corresponding SR configuration to 0.

[0084] When a SR is triggered, it should be considered pending until it is canceled.

[0085] Before a MAC PDU (Protocol Data Unit) is assembled, all pending SRs for BSRs triggered according to the BSR procedure shall be canceled, and each corresponding sr-ProhibitTimer (SR prohibit timer) shall be stopped when the MAC PDU is transmitted, and the PDU includes a long or short BSR MAC CE (Control Element) containing the buffer status up to and including the last event that triggered the BSR before the MAC PDU is assembled. When the UL (Uplink) grant can accommodate all pending data available for transmission, all pending SRs for BSRs triggered according to the BSR procedure shall be canceled, and each corresponding sr-ProhibitTimer shall be stopped.

[0086] For each pending SR that is not triggered according to the BSR procedure of the serving cell, the MAC entity shall:

[0087] 1> if the SR is triggered by the Pre-emptive BSR procedure before MAC PDU assembly and a MAC PDU containing the relevant Pre-emptive BSR-MAC CE is sent; or

[0088] 1> If the SR is triggered by beam failure recovery of an SCell and a MAC PDU is sent, and the PDU includes a MAC CE for BFR (Beam Failure Recovery), the MAC CE contains beam failure recovery information for the SCell; or

[0089] 1> If the SR is triggered by beam failure recovery of the BFD-RS set of the serving cell, and a MAC PDU is sent, and the PDU includes an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE, the BFR MAC CE contains beam failure recovery information for the BFD-RS set of the serving cell; or

[0090] 1> If the SR is triggered by beam failure recovery of an SCell and the SCell is deactivated; or

[0091] 1> If the SR is triggered by beam failure recovery of the BFD-RS set of the SCell, and the SCell is deactivated; or

[0092] 1> If the SR is triggered by a Positioning Measurement Gap Activation / Deactivation Request, and the Positioning Measurement Gap Activation / Deactivation Request MAC CE that triggered the SR has been cancelled; or

[0093] 1> If the SR is triggered by the recovery of a persistent LBT failure of the SCell, and a MAC PDU is sent, and the MAC PDU includes an LBT Failure MAC CE indicating a persistent LBT failure of the SCell; or

[0094] 1> If the SR is triggered by the recovery of a persistent LBT failure of the SCell, and all triggered persistent LBT failures of the SCell are canceled; or

[0095] 1> If the SR is triggered by a timing advance report and all triggered timing advance reports are canceled:

[0096] 2>Cancel the pending SR and stop the corresponding sr-ProhibitTimer, if it is running.

[0097] Only PUCCH resources on the BWP that are active at the time of the SR transmission opportunity are considered valid.

[0098] As long as at least one SR is pending, for each pending SR, the MAC entity will:

[0099] 1> If the MAC entity does not configure valid PUCCH resources for the pending SR:

[0100] 2>Initiate a random access procedure on the SpCell (special cell) and cancel the suspended SR.

[0101] 1> Otherwise, for the SR configuration of the corresponding pending SR:

[0102] 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource configured for SR; and

[0103] 2> If sr-ProhibitTimer is not running at the time of the SR transmission opportunity; and

[0104] 2> If the PUCCH resources used for SR transmission opportunities do not overlap with measurement gaps:

[0105] 3> If the PUCCH resources used for the SR transmission opportunity do not overlap with UL-SCH (Uplink Shared Channel) resources (UL-SCH resources not allowed to be transmitted simultaneously with SR through the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups) nor with SL-SCH (Sidelink Shared Channel) resources; or

[0106] 3> if the MAC entity is able to perform the SR transmission simultaneously with the transmission of SL-SCH resources; or

[0107] 3> If the MAC entity is configured with lch-based Prioritization and the PUCCH resources used for the SR transmission opportunity do not overlap with the PUSCH duration of the uplink grant received in the random access response, or do not overlap with the PUSCH duration of the uplink grant addressed to the temporary C-RNTI (Cell Radio Network Temporary Identifier, cell radio network temporary identifier), or do not overlap with the MSGA (message A, message A) payload overlaps with the PUSCH duration, and the PUCCH resource of the SR transmission opportunity that triggered the pending SR overlaps with any other UL-SCH resource, and the physical layer is able to signal the SR on a valid PUCCH resource for the SR, and the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant of any UL-SCH resource, where the uplink grant has not been de-prioritized and its simultaneous transmission with the SR is not allowed by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCHgroups, and the priority of the uplink grant is determined; or

[0108] 3> If sl-PrioritizationThres and ul-PrioritizationThres are configured, and the PUCCH resources of the SR transmission opportunity that triggers a pending SR overlap with any UL-SCH resources carrying a MAC PDU, and the value of the priority determined to trigger the SR is lower than sl-PrioritizationThres, and the value of the highest priority of the logical channels in the MAC PDU is higher than or equal to ul-PrioritizationThres, and any prioritized MAC CE is not included in the MAC PDU, the MAC PDU is not prioritized by upper layer; or

[0109] 3> if for the SR transmission opportunity that triggered the pending SR, the SL-SCH resources overlap with the PUCCH resources and the MAC entity cannot perform the SR transmission concurrently with the transmission of the SL-SCH source, and the transmission on the SL-SCH resources is not prioritized or the priority value of the logical channel that triggered the SR is lower than ul-PrioritizationThres (if configured); or

[0110] 3> If for the SR transmission opportunity of a triggered pending SR, the SL-SCH resources overlap with the PUCCH resources and the MAC entity cannot perform the SR transmission simultaneously with the transmission of the SL-SCH, and, for the SL-SCH resources, the priority of the determined triggered SR is higher than the priority of the determined MAC PDU:

[0111] 4> Treat SR transmission as SR transmission with priority.

[0112] 4> Treat other overlapping uplink grants (if any) as deprioritized uplink grants, except for overlapping uplink grants whose simultaneous transmission is allowed by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0113] 4> If the deprioritized uplink grant is an uplink grant configured with autonomousTx (whose PUSCH has been started):

[0114] 5> Stop the configuredGrantTimer of the corresponding HARQ process of the de-prioritized uplink grant;

[0115] 5> Stop the cg-RetransmissionTimer of the corresponding HARQ process of the de-prioritized uplink grant.

[0116] 4>If SR_COUNTER <sr-TransMax:

[0117] 5> instructing the physical layer to signal the SR on a valid PUCCH resource for SR;

[0118] 5> If no LBT failure indication is received from the lower layer:

[0119] 6>Increase SR_COUNTER by 1;

[0120] 6>Start sr-ProhibitTimer.

[0121] 5> Otherwise, if lbt-FailureRecoveryConfig is not configured:

[0122] 6>Increment SR_COUNTER by 1.

[0123] 4> Otherwise:

[0124] 5> Notify RRC to release PUCCH of all serving cells;

[0125] 5> Notify RRC to release SRS of all serving cells;

[0126] 5> Clear any configured downlink allocation and uplink authorization;

[0127] 5> Clear any PUSCH resources used for semi-persistent CSI reporting;

[0128] 5>Initiate a random access process on the SpCell and cancel all pending SRs.

[0129] 3> Otherwise:

[0130] 4> Treat SR transmission as de-prioritized SR transmission.

[0131] NOTE 1: Except for SR for SCell beam failure recovery, when the MAC entity has more than one overlapping valid PUCCH resource for SR transmission opportunities, the selection of which valid PUCCH resource for SR to signal the SR is left to the UE implementation.

[0132] NOTE 2: If more than one separate SR triggers the instruction from the MAC entity to the PHY layer to signal the SR on the same valid PUCCH resource, the SR_COUNTER of the related SR configuration is incremented only once.

[0133] NOTE 3: When the MAC entity has a pending SR for SCell beam failure recovery and the MAC entity has one or more PUCCH resources (in addition to the PUCCH resources for the pending SR for beam failure recovery of a BFD-RS set), the MAC entity only considers the PUCCH resources for SCell beam failure recovery to be valid. When the MAC entity has a pending SR for beam failure recovery of a BFD-RS set of a serving cell and the MAC entity has one or more PUCCH sources (in addition to the PUCCH resources for the pending SR for beam failure recovery) that overlap with the PUCCH resources for beam failure recovery of the BFD-RS set for an SR transmission opportunity, the MAC entity only considers the PUCCH resources for beam failure recovery of the BFD-RS set to be valid.

[0134] NOTE 4: For UEs operating in semi-static channel access mode, PUCCH resources that overlap with a set of consecutive symbols that the UE does not transmit before the start of the next channel occupancy time are considered invalid.

[0135] NOTE 5: If the MAC entity is configured with ICH-based Prioritization, the MAC entity does not consider UCI multiplexing when determining whether valid PUCCH resources for SR transmission can be signaled by the physical layer and whether the SR transmission opportunity overlaps with the PUSCH duration of the uplink grant of the MSGA payload.

[0136] NOTE 6: When the MAC entity has PUCCH resources for pending SR for SCell beam failure recovery that overlap with PUCCH resources for pending SR for beam failure recovery for a BFD-RS set for an SR transmission opportunity, it is up to the UE implementation to select the PUCCH resources for SCell beam failure recovery or the PUCCH resources for beam failure recovery for a BFD-RS set.

[0137] During the BSR process, the MAC entity will:

[0138] 1> If the cache status reporting process determines that at least one BSR is triggered and not canceled:

[0139] 2> If UL-SCH resources are available for new transmission and the result of logical channel priority is that the UL-SCH resources can accommodate the BSR MAC CE plus its subheader;

[0140] 3> Instructs the multiplexing and assembly process to generate BSR MAC CE(s);

[0141] 3> Except when all generated BSRs are long or short truncated or extended long or short phase BSRs, start or restart periodicBSR-Timer;

[0142] 3> Enable or restart retxBSR-Timer.

[0143] 2>If the regular BSR is triggered and the logicalChannelSR-DelayTimer is not running;

[0144] 3> if there are no UL-SCH resources available for new transmission; or

[0145] 3> If the MAC entity is configured with an uplink grant and for a logical channel with logicalChannelSR-Mask set to false, a regular BSR is triggered; or

[0146] 3> If the UL-SCH resources available for new transmission do not meet the LCP (Logical Channel Prioritization) mapping constraints configured for the logical channel that triggered the BSR;

[0147] 4>Trigger scheduling request.

[0148] NOTE 2: UL-SCH resources are considered available if the MAC entity is configured or receives or determines an uplink grant. If the MAC entity has determined that UL-SCH resources are available at a given point in time, this does not mean that UL-SCH is available at that point in time.

[0149] During the BFR process, the MAC entity will:

[0150] 1> If the beam failure recovery procedure determines that, for an SCell for which the evaluation of candidate beams has been completed as required, at least one BFR has been triggered and not cancelled, and if none of the serving cells of this MAC entity has two BFD-RS sets configured:

[0151] 2> If UL-SCH resources are available for the new transmission and if the result of the LCP is that the UL-SCH resources can accommodate the BFR MAC CE plus its subheader:

[0152] 3> Instructs the multiplexing and assembly process to generate BFR MAC CE;

[0153] 2> Otherwise if UL-SCH resources are available for the new transmission and if the result of the LCP is that the UL-SCH resources can accommodate the truncated BFR MAC CE plus its subheader:

[0154] 3> Instructs the multiplexing and assembly process to generate a truncated BFR MAC CE;

[0155] 2> Otherwise:

[0156] 3> For SCell beam failure recovery of each SCell where BFR has been triggered and not cancelled, the evaluation of candidate beams has been completed as required, and SR is triggered.

[0157] 1> If the beam failure recovery procedure determines that at least one BFR for any BFD-RS set has been triggered and not cancelled, and the evaluation of candidate beams has been completed as required for the SCell; or

[0158] 1> If the beam failure recovery process determines that at least one BFR of only one BFD-RS set has been triggered and not cancelled, and the evaluation of candidate beams has been completed as required for the SpCell; or

[0159] 1> If the beam failure recovery procedure determines that at least one BFR has been triggered and not cancelled, and the evaluation of candidate beams has been completed as required for the SCell, and if at least one serving cell of the MAC entity is configured with two BFD-RS sets:

[0160] 2> If UL-SCH resources are available for the new transmission and if the result of the LCP is that the UL-SCH resources can accommodate the enhanced BFR MAC CE plus its subheader:

[0161] 3> Instructs the multiplexing and assembly process to generate enhanced BFR MAC CE;

[0162] 2> Otherwise if UL-SCH resources are available for the new transmission and if the result of the LCP is that the UL-SCH resources can accommodate the truncated enhanced BFR MAC CE plus its subheader:

[0163] 3> Instructs the multiplexing and assembly process to generate a truncated enhanced BFR MAC CE;

[0164] 2> Otherwise:

[0165] 3> For beam failure recovery of each BFD-RS set where BFR has been triggered and not cancelled, and the evaluation of candidate beams has been completed as required, SR is triggered;

[0166] 3> For SCell beam failure recovery of each SCell where BFR has been triggered and not canceled, the evaluation of candidate beams has been completed as required, and SR is triggered.

[0167] For each serving cell, RRC can configure the MAC entity with a beam failure recovery procedure, which is used to indicate a new SSB or CSI-RS to the serving gNB when beam failure is detected on the serving SSB(s) / CSI-RS(s). In Rel-15 and Rel-16, cell-level beam failure detection is supported. The MAC entity shall:

[0168] If the beam failure recovery process determines that at least one BFR has been triggered and not cancelled:

[0169] If UL-SCH resources are available for a new transmission and if the result of the LCP is that this UL-SCH resource can accommodate the BFR MAC CE plus its subheader, the multiplexing and assembly process is instructed to generate the BFR MAC CE.

[0170] Otherwise, if UL-SCH resources are available for a new transmission and if the result of the LCP is that this UL-SCH resource can accommodate the Truncated BFR MAC CE plus its subheader, instruct the multiplexing and assembly process to generate the Truncated BFR MAC CE.

[0171] Otherwise, SR is triggered for the secondary cell beam failure recovery of each secondary cell for which BFR is triggered and not cancelled.

[0172] Under R17 multi-TRP operation, beam failure detection of a separate BFD-RS (Beam Failure Detection Reference Signal) group per TRP is supported, and simultaneous configuration of cell-specific BFR and TRP-specific BFR on different CCs (component carriers) is supported, but simultaneous configuration of TRP-specific BFR and Rel-15 / 16BFR (i.e., BeamFailureRecoveryConfig / BeamFailureRecoverySCellConfig-r16) on one CC is not supported.

[0173] According to the agreement reached at the last RAN 2 (Radio Access Network Working Group 2) meeting, legacy BFR MAC CE and enhanced BFR MAC CE are not triggered simultaneously. If at least one cell is configured with two BFD-RS groups, the enhanced BFR MAC CE is used for BFR in the serving cell with or without a BFD-RS group.

[0174] Based on the above consensus, the BFR process described by the current protocol is shown in Figures 2 and 3.

[0175] As shown in Figure 2, the MAC entity will:

[0176] 1> If the beam failure recovery process determines that at least one BFR has been triggered and not cancelled for a secondary cell for which candidate beam evaluation has been completed, and if this MAC entity does not have two BFD-RS groups configured in the serving cell:

[0177] 2> If UL-SCH resources are available for a new transmission and if the result of LCP is that this UL-SCH resource can accommodate the BFR MAC CE plus its subheader:

[0178] 3> Indicates the multiplexing and assembly process to generate BFR MAC CE.

[0179] 2> Otherwise, if UL-SCH resources are available for a new transmission and if the result of LCP is that this UL-SCH resource can accommodate the Truncated BFR MAC CE plus its subheader:

[0180] 3> Indicates the multiplexing and assembly process to generate Truncated BFR MAC CE.

[0181] 2> Otherwise:

[0182] 3> Trigger SR for secondary cell beam failure recovery for each secondary cell for which BFR is triggered, not cancelled, and candidate beam evaluation is completed.

[0183] In addition, as shown in Figure 3, the MAC entity will:

[0184] 1> If the beam failure recovery process determines that a secondary cell for which candidate beam evaluation has completed has triggered BFR for at least one BFD-RS group and has not been cancelled; or

[0185] 1> If the beam failure recovery process determines that a special cell for which candidate beam evaluation has been completed has only one BFD-RS group that has triggered BFR for at least one BFD-RS group and has not been cancelled; or

[0186] 1> If the beam failure recovery process determines that at least one BFR has been triggered and not cancelled for a secondary cell for which candidate beam evaluation has been completed, and if at least one serving cell of this MAC entity is configured with two BFD-RS groups:

[0187] 2> If UL-SCH resources are available for a new transmission and if the result of LCP is that this UL-SCH resource can accommodate the Enhanced BFR MAC CE plus its subheader:

[0188] 3> Indicates the multiplexing and assembly process to generate Enhanced BFR MAC CE.

[0189] 2> Otherwise, if UL-SCH resources are available for a new transmission and if the result of the LCP is that this UL-SCH resource can accommodate the Truncated Enhanced BFR MAC CE plus its subheader:

[0190] 3> Indicates the multiplexing and assembly process to generate Truncated Enhanced BFR MAC CE.

[0191] 2> Otherwise:

[0192] 3> triggering SR for beam failure recovery for each BFD-RS group for which BFR is triggered, not cancelled, and candidate beam evaluation is completed;

[0193] 3> Trigger SR for secondary cell beam failure recovery for each secondary cell for which BFR is triggered, not cancelled, and candidate beam evaluation is completed.

[0194] During the LBT failure detection and recovery process, the MAC entity will:

[0195] 1> If a persistent LBT failure is triggered in SpCell and not cancelled; and

[0196] 1> If UL-SCH resources are available for new transmissions in the SpCell and if the result of logical channel priority is that these UL-SCH resources can accommodate the LBT failure MAC CE plus its subheader,

[0197] 2> Instruct the multiplexing and assembly process to generate the LBT failure MAC CE.

[0198] 1> Otherwise, if a persistent LBT failure is triggered in at least one SCell and is not cancelled:

[0199] 2> If UL-SCH resources are available for new transmissions in the serving cell in which a persistent LBT failure has not been triggered, and the result of the logical channel priority is that these UL-SCH resources can accommodate the LBT failure MAC CE plus its subheader,

[0200] 3> Instruct the multiplexing and assembly process to generate the LBT failure MAC CE.

[0201] 2> Otherwise:

[0202] 3>Trigger a scheduling request for the LBT failed MAC CE.

[0203] The embodiments of the present application are described below with reference to the accompanying drawings and specific implementation methods.

[0204] Embodiments of the first aspect

[0205] An embodiment of the present application provides a communication method in a cell discontinuous transmission / reception scenario, which is described from the side of a terminal device.

[0206] FIG4 is a schematic diagram of a communication method according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0207] 401: When the network is in the network energy-saving mode, the terminal device does not trigger a scheduling request and / or performs actions related to the network energy-saving mode for a pending scheduling request.

[0208] It is worth noting that FIG4 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG4 above.

[0209] According to the above embodiment, when the network is in network energy-saving mode, the terminal device does not trigger an SR. This prevents a pending SR from triggering a random access procedure, thereby reducing network energy consumption. Furthermore, when the network is in network energy-saving mode, the terminal device performs actions related to the pending SR in response to the network energy-saving mode. Therefore, a pending SR does not cause the terminal to release its uplink configuration.

[0210] In some embodiments, the network energy saving mode is one of the following:

[0211] Network energy saving mode is activated;

[0212] Discontinuous transmission / reception of the cell is configured and / or activated;

[0213] The terminal device is in the inactive phase of discontinuous transmission / reception of the cell.

[0214] In the above embodiment, the network energy saving mode is activated (the NES mode is activated), for example, the network device instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling (broadcast or dedicated message), MAC CE signaling, and DCI signaling. However, the present application is not limited to this, and the network energy saving mode can also be activated by other means.

[0215] In the above embodiment, cell discontinuous transmission / reception (cell DTX / DRX is configured / activated) is configured and / or activated, for example, the network device configures the parameters of cell discontinuous transmission / reception, such as period, on-duration time, etc., through RRC signaling (broadcast or dedicated message); for another example, the network device indicates the activation of (at least one) cell discontinuous transmission / reception of the terminal device through at least one of RRC signaling (broadcast or dedicated message), MAC CE signaling and DCI signaling; for another example, the network device configures the parameters of cell discontinuous transmission / reception through RRC signaling (broadcast or dedicated message), and indicates the activation of at least one cell discontinuous transmission / reception of the terminal device through at least one of RRC signaling (broadcast or dedicated message), MAC CE signaling and DCI signaling. However, the present application is not limited to this, and cell discontinuous transmission / reception may also be configured and / or activated in other ways.

[0216] In the above embodiment, the terminal device is in the inactive stage of cell discontinuous transmission / reception (the UE is in inactive state of cell DTX / DRX). For example, according to the cell discontinuous transmission / reception configuration, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception; for another example, according to the cell discontinuous transmission / reception configuration, when the cell discontinuous transmission / reception is activated, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception.

[0217] In the above embodiment, "cell discontinuous transmission / reception configuration" may be, for example, that the network device configures the cell discontinuous transmission / reception parameters, such as the period, on-duration time, etc., through RRC signaling (broadcast or dedicated message). However, the present application is not limited thereto, and other configuration methods may also be used.

[0218] In the above embodiment, "cell discontinuous transmission / reception is activated", for example, the network device may indicate the activation of (at least one) cell discontinuous transmission / reception of the terminal device through at least one of RRC signaling (broadcast or dedicated message), MAC CE signaling, and DCI signaling. However, the present application is not limited to this, and other activation methods may also be used.

[0219] In the aforementioned embodiments, RRC signaling may be broadcast signaling, that is, the network device may perform the above-mentioned indication / configuration / activation by broadcasting; RRC signaling may also be dedicated signaling, that is, the network device may perform the above-mentioned indication / configuration / activation for a certain terminal device or a certain cell, etc.

[0220] In some embodiments, the scheduling request includes at least one of the following:

[0221] Buffer Status Report (BSR) scheduling request;

[0222] Beam Failure Recovery (BFR) scheduling request;

[0223] Scheduling requests for consistent LBT failure recovery;

[0224] Integration and Access Backhaul (IAB) related scheduling requests;

[0225] Positioning-related scheduling requests;

[0226] Non-terrestrial network (NTN) related scheduling requests.

[0227] In the above embodiment, the BSR scheduling request is, for example, a pending SR triggered according to a BSR process.

[0228] The following table shows the possible behaviors of the MAC entity when an SR is triggered according to the BSR procedure:

[0229] According to this embodiment, when the network is in the network energy-saving mode, the terminal device does not trigger the SR of the BSR, thereby avoiding the suspended SR from triggering the random access process, thereby reducing network energy consumption.

[0230] In the above embodiment, the BFR scheduling request is, for example, an SR triggered by a secondary cell BFR (SCell BFR), or another example, an SR triggered by a BFD-RS set BFR (BFD-RS set BFR).

[0231] The following table shows the possible behaviors of the MAC entity when SCell BFR triggers SR:

[0232] The following table shows the possible behaviors of the MAC entity when BFD-RS set BFR triggers SR:

[0233] According to this embodiment, when the network is in network energy-saving mode, BFR-triggered SRs, such as SCell BFR-triggered SRs and / or BFD-RS combined with BFR-triggered SRs, are not triggered. This prevents pending SRs from triggering random access procedures, thereby reducing network energy consumption.

[0234] In the above embodiment, the scheduling request for consistent LBT failure recovery is, for example, an SR triggered by consistent LBT failure recovery.

[0235] The following table shows the possible behaviors of the MAC entity in this example:

[0236] According to this embodiment, when the network is in the network energy-saving mode, the SR for consistent LBT failure recovery is not triggered, thereby avoiding the random access process triggered by the pending SR, thereby reducing network energy consumption.

[0237] In the above embodiment, in some implementations, if IAB / Positioning / NTN and network energy saving are supported simultaneously, the above scheduling request may also be an IAB-related SR and / or a Positioning-related SR and / or an NTN-related SR.

[0238] For example, when the parent node or IAB-donor of an IAB node is in the network energy-saving mode, SR is not triggered.

[0239] The following table shows the possible behaviors of the MAC entity in this example:

[0240] For another example, for the positioning measurement gap activation / deactivation request MAC CE, when the network is in the network energy saving mode, no SR is triggered.

[0241] The following table shows the possible behaviors of the MAC entity in this example:

[0242] For example, in NTN, in order to provide the UE timing advance value, T TA ,Using the timed advance reporting process, when the network is in the network energy saving mode, SR is not triggered.

[0243] The following table shows the possible behaviors of the MAC entity in this example:

[0244] According to this embodiment, when the network node is an IAB node or IAB-donor, or the network is an NTN, or the network is used for positioning, and the network is in a network energy-saving mode, SR is not triggered. This can prevent a pending SR from triggering a random access procedure, thereby reducing network energy consumption.

[0245] In the above embodiment, in other implementations, IAB or NTN does not support network energy saving, and Positoning and network energy saving are not configured at the same time, then not triggering the scheduling request may mean not configuring IAB and / or not configuring Positoning and / or not configuring NTN.

[0246] In some embodiments, the behaviors related to the network energy saving mode include at least one of the following:

[0247] Cancel the pending scheduling request (pending SR);

[0248] It is considered that there are no valid PUCCH resources configured for the pending SR;

[0249] Consider SR transmission to be a low-priority SR transmission;

[0250] Suspend SR counter;

[0251] Do not initiate a random access process;

[0252] No emptying and / or releasing operations are performed;

[0253] Use a larger maximum SR transmission time (sr-TransMax).

[0254] In the above embodiment, “SR transmission is considered to be a low-priority SR transmission”. For example, if the network is in the network energy-saving mode, the SR transmission is considered to be a low-priority SR transmission; for another example, if the network is not in the network energy-saving mode, the SR transmission is considered to be a high-priority SR transmission.

[0255] The following table shows a possible modification of the protocol according to the above embodiment:

[0256] The following table shows another possibility of protocol modification according to the above embodiment:

[0257] In the above embodiment, “suspending the SR counter” means, for example, suspending the SR counter if the network is in the network energy-saving mode; or adding 1 to the SR counter if the network is not in the network energy-saving mode.

[0258] The following table shows a possible modification of the protocol according to the above embodiment:

[0259] In the above embodiment, “not initiating a random access process” means, for example, not initiating a random access process or not initiating a triggered random access process if the network is in a network energy-saving mode; or initiating a random access process or a triggered random access process if the network is not in a network energy-saving mode.

[0260] The following table shows a possible modification of the protocol according to the above embodiment:

[0261] In the above embodiment, "using a larger maximum SR transmission number (sr-TransMax)", for example, configuring the maximum SR transmission number to an infinite value; for another example, when the maximum SR transmission number is not configured, the terminal device considers that the maximum SR transmission number is an infinite value.

[0262] The following table shows a possible modification of the protocol according to the above embodiment:

[0263] The following table shows another possibility of protocol modification according to the above embodiment:

[0264] In the above example, the protocol description of "sr-TransMax" can be:

[0265] In the above embodiment, “no clearing and / or releasing operation is performed”, for example, if the network is in the network energy-saving mode, no clearing and / or releasing operation is performed; for another example, if the network is not in the network energy-saving mode, the clearing and / or releasing operation is performed.

[0266] In the above embodiment, if the network is not in the network energy saving mode, clearing and / or releasing operations are performed, for example, this may include, if the network is not in the network energy saving mode, and if the SR counter reaches a maximum value, clearing and / or releasing operations are performed.

[0267] In the above embodiment, if the network is not in the network energy saving mode, performing the clearing and / or releasing operation may further include initiating a random access procedure on the special cell; and / or canceling all pending SRs.

[0268] In the aforementioned embodiments, the “clear” operation includes: clearing any configured downlink allocation and uplink grant; and / or clearing any PUSCH resources used for semi-persistent CSI reporting.

[0269] In the aforementioned embodiments, the “release” operation includes: notifying the RRC to release the PUCCH for all serving cells; and / or notifying the RRC to release the SRS of all serving cells.

[0270] For example, if the SR counter reaches the maximum value, and if the network is not in network energy saving mode, notify RRC to release PUCCH for all serving cells, notify RRC to release SRS for all serving cells, clear any configured downlink assignments and uplink grants, clear any PUSCH resources used for semi-persistent CSI reporting, initiate a random access procedure on the special cell, and cancel all pending SRs.

[0271] For another example, if the SR counter reaches a maximum value and if the network is in a network energy saving mode, a random access procedure is initiated on the special cell and all pending SRs are canceled.

[0272] For example, if the SR counter reaches the maximum value, a random access procedure is initiated on the special cell, all pending SRs are canceled, and if the network is not in network energy saving mode, the RRC is notified to release the PUCCH for all serving cells, the SRS for all serving cells is notified to release, any configured downlink allocations and uplink grants are cleared, and any PUSCH resources used for semi-persistent CSI reporting are cleared.

[0273] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0274] According to the method of the above embodiment, when the network is in network energy-saving mode, the terminal device does not trigger an SR. This prevents the pending SR from triggering a random access procedure, thereby reducing network energy consumption. Furthermore, when the network is in network energy-saving mode, the terminal device performs actions related to the pending SR in response to the network energy-saving mode. Therefore, the pending SR does not cause the terminal to release its uplink configuration.

[0275] Embodiments of the second aspect

[0276] The embodiment of the present application provides a communication method in a cell discontinuous transmission / reception scenario, which is described from the perspective of a network device, and the contents that are the same as those in the embodiment of the first aspect are not repeated.

[0277] FIG5 is a schematic diagram of a communication method according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0278] 501: The network device indicates information related to network energy saving to the terminal device.

[0279] According to the above embodiment, the network device indicates information related to network energy saving to the terminal device, thereby, the terminal device may not trigger SR when the network is in network energy saving mode, or perform actions related to the network energy saving mode for the pending SR, thereby avoiding the pending SR from triggering the random access process, thereby reducing network energy consumption, or the pending SR will not cause the terminal to release the uplink configuration.

[0280] In some embodiments, the network device indicates information related to network energy saving to the terminal device. For example, the network device may indicate to the terminal device that it is in network energy saving mode. This application does not limit the specific indication method. The indication may be provided by sending indication information, or by sending configuration information, or by other means. Furthermore, this application does not limit the carrying method of the indication information or configuration information. The indication information or configuration information may be carried in various possible signaling.

[0281] In the above embodiment, the network energy-saving mode refers to at least one of the following:

[0282] The NES mode is activated.

[0283] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0284] The terminal equipment is in the inactive state of cell DTX / DRX.

[0285] For example, when the network energy saving mode is "network energy saving mode is activated", the network device may further instruct the terminal device to activate the network energy saving mode (502) through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0286] For another example, when the network energy saving mode is "cell discontinuous transmission / reception configured and / or activated", the network device may further configure the cell discontinuous transmission / reception parameters through RRC signaling (503).

[0287] For another example, when the network energy saving mode is "cell discontinuous transmission / reception configured and / or activated", the network device can also indicate the activation of at least one cell discontinuous transmission / reception of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling (504).

[0288] For another example, when the network energy-saving mode is "the terminal device is in the inactive stage of cell discontinuous transmission / reception", the network device may also send the cell discontinuous transmission / reception configuration (505) to the terminal device, whereby the terminal device may enter the sleep or inactive time according to the cell discontinuous transmission / reception configuration, or the terminal device is not within the duration of cell discontinuous transmission / reception; or, when the cell discontinuous transmission / reception is activated, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of cell discontinuous transmission / reception.

[0289] In the aforementioned embodiments, the RRC signaling may be broadcast signaling or dedicated signaling.

[0290] In some embodiments, the network device indicates information related to network energy saving to the terminal device. For example, the network device coordinates SR configuration and cell discontinuous transmission / reception duration (cell DTX / DRX on-duration time).

[0291] In the above embodiment, the SR configuration and the duration of discontinuous transmission / reception of the cell are coordinated, for example, so that there is no valid PUCCH resource (valid PUCCH resource) during the inactive time of discontinuous transmission / reception of the cell; for another example, the valid PUCCH resource (valid PUCCH resource) can be within the active time of discontinuous transmission / reception of the cell.

[0292] In some embodiments, the network device indicates information related to network energy saving to the terminal device. For example, if the network device supports one of IAB, NTN and positioning, the network device does not indicate that it is in network energy saving mode or the network device is in network energy saving mode.

[0293] In the above embodiment, the network energy-saving mode refers to at least one of the following:

[0294] The NES mode is activated.

[0295] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0296] The terminal equipment is in the inactive state of cell DTX / DRX.

[0297] The above-mentioned network energy-saving mode has been described in the embodiment of the first aspect, and its content is incorporated here and will not be repeated here.

[0298] In some embodiments, when the network device indicates that it is in the network energy saving mode, the network device does not support one of IAB, NTN, and positioning.

[0299] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0300] According to the method of the above embodiment, when the network is in network energy-saving mode, the terminal device does not trigger an SR. This prevents the pending SR from triggering a random access procedure, thereby reducing network energy consumption. Furthermore, when the network is in network energy-saving mode, the terminal device performs actions related to the pending SR in response to the network energy-saving mode. Therefore, the pending SR does not cause the terminal to release its uplink configuration.

[0301] Embodiments of the third aspect

[0302] The present application provides a communication device. The device may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. The communication device of the present application corresponds to the method of the first aspect of the embodiment, and the contents that are the same as those of the first aspect of the embodiment are not repeated here.

[0303] FIG6 is a schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG6 , the communication device 600 according to the embodiment of the present application includes:

[0304] The processing unit 601 is configured to not trigger a scheduling request and / or perform actions related to the network energy saving mode for a suspended scheduling request when the network is in the network energy saving mode.

[0305] In some embodiments, the network energy saving mode refers to at least one of the following:

[0306] The NES mode is activated.

[0307] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0308] The terminal equipment is in the inactive state of cell DTX / DRX.

[0309] In the above embodiment, the network energy saving mode is activated, which may include, for example:

[0310] The network device instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0311] In the above embodiment, configuring and / or activating discontinuous transmission / reception of a cell may include, for example:

[0312] The network equipment configures the cell's discontinuous transmission / reception parameters through RRC signaling.

[0313] In the above embodiment, configuring and / or activating discontinuous transmission / reception of a cell may include, for example:

[0314] The network device indicates the activation of discontinuous transmission / reception of at least one cell of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0315] In the above embodiment, the terminal device is in an inactive phase of discontinuous transmission / reception of a cell, which may include:

[0316] According to the cell discontinuous transmission / reception configuration, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception; or,

[0317] According to the cell discontinuous transmission / reception configuration, when the cell discontinuous transmission / reception is activated, the terminal device enters a sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception.

[0318] In the aforementioned embodiments, the RRC signaling may be broadcast signaling or dedicated signaling.

[0319] In some embodiments, the scheduling request includes at least one of the following:

[0320] Buffer Status Report (BSR) scheduling request;

[0321] Beam Failure Recovery (BFR) scheduling request;

[0322] Scheduling requests for consistent LBT failure recovery;

[0323] Integration and Access Backhaul (IAB) related scheduling requests;

[0324] Positioning-related scheduling requests;

[0325] Non-terrestrial network (NTN) related scheduling requests.

[0326] In the above embodiment, in some implementations, if it is supported to be used simultaneously with network energy saving, the scheduling request includes one of an IAB-related scheduling request, a positioning-related scheduling request, and an NTN-related scheduling request.

[0327] In the above embodiment, in some implementations, the processing unit 601 does not trigger a scheduling request, including:

[0328] The processing unit 601 does not configure any one of IAB, NTN, and positioning.

[0329] In some embodiments, the processing unit 601 performs actions related to the network energy saving mode including:

[0330] The processing unit 601 cancels the pending scheduling request (pending SR);

[0331] The processing unit 601 considers that there is no valid PUCCH resource configured for the pending SR;

[0332] The processing unit 601 considers the SR transmission to be a low-priority SR transmission;

[0333] The processing unit 601 suspends the SR counter;

[0334] The processing unit 601 does not initiate a random access procedure;

[0335] The processing unit 601 does not perform clearing and / or releasing operations;

[0336] The processing unit 601 uses a larger maximum SR transmission number (sr-TransMax).

[0337] In the above embodiment, the processing unit 601 considers that the SR transmission is a low-priority SR transmission, which may include:

[0338] If the network is in the network energy saving mode, the processing unit 601 considers the SR transmission to be a low priority SR transmission; or

[0339] If the network is not in the network energy-saving mode, the processing unit 601 considers the SR transmission to be a high-priority SR transmission.

[0340] In the above embodiment, the processing unit 601 suspends the SR counter, which may include:

[0341] If the network is in the network energy saving mode, the processing unit 601 suspends the SR counter; or

[0342] If the network is not in the network energy-saving mode, the processing unit 601 increases the SR counter by 1.

[0343] In the above embodiment, the processing unit 601 does not initiate a random access process, which may include:

[0344] If the network is in the network energy-saving mode, the processing unit 601 does not initiate a random access procedure or does not initiate a triggered random access procedure; or

[0345] If the network is not in the network energy-saving mode, the processing unit 601 initiates a random access procedure or a triggered random access procedure.

[0346] In the above embodiment, the processing unit 601 uses a larger maximum number of SR transmission times, which may include:

[0347] The processing unit 601 configures the maximum number of SR transmission times to an infinite value;

[0348] When the maximum number of SR transmission times is not configured, the processing unit 601 considers the maximum number of SR transmission times to be infinite.

[0349] In the above embodiment, the processing unit 601 does not perform the clearing and / or releasing operations, which may include:

[0350] If the network is in the network energy-saving mode, the processing unit 601 does not perform the clearing and / or releasing operations;

[0351] If the network is not in the network energy-saving mode, the processing unit 601 performs a clearing and / or releasing operation.

[0352] In the above embodiment, if the network is not in the network energy-saving mode, the processing unit 601 performs a clearing and / or releasing operation, which may include:

[0353] If the network is not in the network energy saving mode and if the SR counter reaches the maximum value, the processing unit 601 performs a clearing and / or releasing operation.

[0354] In the above embodiment, if the network is not in the network energy-saving mode, the processing unit 601 performs a clearing and / or releasing operation, which may further include:

[0355] The processing unit 601 initiates a random access procedure on the special cell; and / or

[0356] Processing unit 601 cancels all pending SRs.

[0357] In the aforementioned embodiments, clearing may include:

[0358] Clear any configured downlink allocations and uplink grants; and / or,

[0359] Clear any PUSCH resources used for semi-persistent CSI reporting.

[0360] In the aforementioned embodiments, releasing may include:

[0361] Notify RRC to release PUCCH for all serving cells; and / or,

[0362] Notify RRC to release the SRS of all serving cells.

[0363] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0364] The present application also provides a communication device. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The communication device of the present application corresponds to the method of the second aspect of the embodiment, and the contents that are the same as those of the second aspect of the embodiment are not repeated here.

[0365] FIG7 is a schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG7 , the communication device 700 according to the embodiment of the present application includes:

[0366] The processing unit 701 indicates information related to network energy saving to the terminal device.

[0367] In some embodiments, the processing unit 701 indicates to the terminal device information related to network energy saving, including:

[0368] The processing unit 701 indicates to the terminal device that the network is in the network energy saving mode.

[0369] In the above embodiment, in some implementations, the network energy-saving mode refers to at least one of the following:

[0370] The NES mode is activated.

[0371] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0372] The terminal equipment is in the inactive state of cell DTX / DRX.

[0373] In some embodiments, as shown in FIG7 , the apparatus 700 may further include:

[0374] The first indication unit 702 instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0375] In the above embodiment, the network energy saving mode means that the network energy saving mode is activated (the NES mode is activated).

[0376] In some embodiments, as shown in FIG7 , the apparatus 700 may further include:

[0377] The configuration unit 703 configures the parameters of discontinuous transmission / reception of the cell through RRC signaling.

[0378] In the above embodiment, the network energy saving mode means that cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated.

[0379] In some embodiments, as shown in FIG7 , the apparatus 700 may further include:

[0380] The second indication unit 704 indicates activation of discontinuous transmission / reception of at least one cell of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0381] In the above embodiment, the network energy saving mode means that cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated.

[0382] In some embodiments, as shown in FIG7 , the apparatus 700 may further include:

[0383] The sending unit 705 sends the cell discontinuous transmission / reception configuration to the terminal device, whereby the terminal device can enter the sleep or inactive time according to the cell discontinuous transmission / reception configuration, or the terminal device is not within the duration of the cell discontinuous transmission / reception; or, when the cell discontinuous transmission / reception is activated, the terminal device enters the sleep or inactive time, or, the terminal device is not within the duration of the cell discontinuous transmission / reception.

[0384] In the above embodiment, the network energy-saving mode means that the terminal device is in an inactive phase of discontinuous transmission / reception of the cell.

[0385] In the aforementioned embodiments, the RRC signaling may be broadcast signaling or dedicated signaling.

[0386] In some embodiments, the processing unit 701 indicates to the terminal device information related to network energy saving, including:

[0387] The processing unit 701 coordinates the SR configuration and the cell discontinuous transmission / reception duration (cell DTX / DRX on-duration time).

[0388] In the above embodiment, the processing unit 701 coordinates the SR configuration and the cell discontinuous transmission / reception duration, including:

[0389] The processing unit 701 ensures that the cell has no valid PUCCH resources (valid PUCCH resources) during the discontinuous transmission / reception inactive time (inactive time); or

[0390] The processing unit 701 ensures that valid PUCCH resources are within the discontinuous transmission / reception activation time of the cell.

[0391] In some embodiments, the processing unit 701 indicates to the terminal device information related to network energy saving, including:

[0392] If the network device supports one of IAB, NTN and positioning, the processing unit 701 does not indicate that the network is in the network energy-saving mode or the processing unit 701 considers that the network is in the network energy-saving mode.

[0393] In the above embodiment, the network energy-saving mode refers to at least one of the following:

[0394] The NES mode is activated.

[0395] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0396] The terminal equipment is in the inactive state of cell DTX / DRX.

[0397] In the embodiment of the present application, when the processing unit 701 indicates that the network is in the network energy-saving mode, the network device does not support one of IAB, NTN, and positioning.

[0398] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0399] It is worth noting that the above description only describes the components or modules related to this application, but this application is not limited thereto. Communication devices 600 and 700 may also include other components or modules. For the specific content of these components or modules, please refer to the relevant art. In addition, the above components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0400] According to the apparatus of the above embodiment, when the network is in network energy-saving mode, the terminal device does not trigger an SR, thereby preventing the pending SR from triggering a random access procedure, thereby reducing network energy consumption. Furthermore, when the network is in network energy-saving mode, the terminal device performs actions related to the pending SR in response to the network energy-saving mode. Therefore, the pending SR does not cause the terminal to release its uplink configuration.

[0401] Embodiments of the fourth aspect

[0402] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0403] In some embodiments, the terminal device includes the apparatus described in FIG6 of the embodiment of the third aspect, and is configured to execute the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0404] In some embodiments, the network device includes the apparatus described in FIG7 of the embodiment of the third aspect, and is configured to execute the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.

[0405] An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other terminal devices.

[0406] Figure 8 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 8 , terminal device 800 may include a processor 801 and a memory 802. Memory 802 stores data and programs and is coupled to processor 801. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0407] In some embodiments, the functions of the device of Figure 6 of the embodiment of the third aspect can be integrated into the processor 801, wherein the processor 801 can be configured to execute a program to implement the method described in the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0408] In other embodiments, the device of Figure 6 of the embodiment of the third aspect can be configured separately from the processor 801. For example, the device of Figure 6 of the embodiment of the third aspect can be configured as a chip connected to the processor 801, and the functions of the device of Figure 6 of the embodiment of the third aspect can be implemented through the control of the processor 801.

[0409] As shown in Figure 8 , the terminal device 800 may further include: a communication module 803, an input unit 804, a display 805, and a power supply 806. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 800 does not necessarily include all of the components shown in Figure 8 , and the above components are not essential. Furthermore, the terminal device 800 may also include components not shown in Figure 8 , for which reference may be made to related art.

[0410] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0411] Figure 9 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 9 , network device 900 may include a processor 901 and a memory 902 ; the memory 902 is coupled to the processor 901 . The memory 902 may store various data and information processing programs, which are executed under the control of the processor 901 .

[0412] In some embodiments, the functions of the device 700 of Figure 7 of the embodiment of the third aspect can be integrated into the processor 901, wherein the processor 901 can be configured to execute a program to implement the method described in the embodiment of the second aspect, the content of which is incorporated herein and will not be repeated here.

[0413] In other embodiments, the device 700 of Figure 7 of the embodiment of the third aspect can be configured separately from the processor 901. For example, the device 700 of Figure 7 of the embodiment of the third aspect can be configured as a chip connected to the processor 901, and the functions of the device 700 of Figure 7 of the embodiment of the third aspect can be implemented through the control of the processor 901.

[0414] Furthermore, as shown in FIG9 , network device 900 may further include transceivers 903 and 904. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that network device 900 does not necessarily include all of the components shown in FIG9 ; furthermore, network device 900 may also include components not shown in FIG9 , for which reference may be made to related art.

[0415] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0416] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0417] An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0418] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0419] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0420] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0421] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and storage medium may be located in an ASIC. The software module may be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if a device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0422] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0423] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0424] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0425] 1. A communication method, wherein the method comprises:

[0426] When the network is in the network energy saving mode, the terminal device does not trigger a scheduling request (SR) and / or perform actions related to the network energy saving mode for a pending scheduling request (pending SR).

[0427] 2. The method according to Note 1, wherein the network energy-saving mode is at least one of the following:

[0428] The NES mode is activated.

[0429] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0430] The terminal equipment is in the inactive state of cell DTX / DRX.

[0431] 3. The method according to Note 2, wherein the network energy saving mode is activated, comprising:

[0432] The network device instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0433] 4. The method according to Note 2, wherein configuring and / or activating cell discontinuous transmission / reception comprises:

[0434] The network equipment configures the cell's discontinuous transmission / reception parameters through RRC signaling.

[0435] 5. The method according to Note 2, wherein configuring and / or activating cell discontinuous transmission / reception comprises:

[0436] The network device indicates the activation of discontinuous transmission / reception of at least one cell of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0437] 6. The method according to Note 2, wherein the terminal device is in an inactive phase of discontinuous transmission / reception of the cell, comprising:

[0438] According to the cell discontinuous transmission / reception configuration, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception; or,

[0439] According to the cell discontinuous transmission / reception configuration, when the cell discontinuous transmission / reception is activated, the terminal device enters a sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception.

[0440] 7. The method according to Note 3, 4 or 5, wherein:

[0441] The RRC signaling is broadcast signaling or dedicated signaling.

[0442] 8. The method according to Supplementary Note 1, wherein the scheduling request includes at least one of the following:

[0443] Buffer Status Report (BSR) scheduling request;

[0444] Beam Failure Recovery (BFR) scheduling request;

[0445] Scheduling requests for consistent LBT failure recovery;

[0446] Integration and Access Backhaul (IAB) related scheduling requests;

[0447] Positioning related scheduling requests;

[0448] Non-terrestrial network (NTN) related scheduling requests.

[0449] 9. The method according to Supplementary Note 8, wherein:

[0450] If it is supported to be used simultaneously with network energy saving, the scheduling request includes one of the IAB-related scheduling request, the positioning-related scheduling request, and the NTN-related scheduling request.

[0451] 10. The method according to Supplementary Note 1, wherein not triggering a scheduling request comprises:

[0452] Do not configure any of IAB, NTN, or positioning.

[0453] 11. The method according to Supplementary Note 1, wherein the behavior related to the network energy-saving mode includes:

[0454] Cancel the pending scheduling request (pending SR);

[0455] It is considered that there are no valid PUCCH resources configured for the pending SR;

[0456] Consider SR transmission to be a low-priority SR transmission;

[0457] Suspend SR counter;

[0458] Do not initiate a random access process;

[0459] No emptying and / or releasing operations are performed;

[0460] Use a larger maximum SR transmission time (sr-TransMax).

[0461] 12. The method according to supplementary note 11, wherein the SR transmission is considered to be a low-priority SR transmission, comprising:

[0462] If the network is in network energy saving mode, the SR transmission is considered a low priority SR transmission; or

[0463] If the network is not in the network energy saving mode, the SR transmission is considered to be a high priority SR transmission.

[0464] 13. The method according to supplementary note 11, wherein suspending the SR counter comprises:

[0465] If the network is in network power saving mode, suspend the SR counter; or

[0466] If the network is not in the network energy saving mode, the SR counter is incremented by 1.

[0467] 14. The method according to note 11, wherein not initiating a random access procedure comprises:

[0468] If the network is in a network energy saving mode, no random access procedure is initiated or no triggered random access procedure is initiated; or

[0469] If the network is not in the network energy saving mode, a random access procedure is initiated or a triggered random access procedure is initiated.

[0470] 15. The method according to Note 11, wherein using a larger maximum number of SR transmission times comprises:

[0471] Set the maximum number of SR transmission times to infinite;

[0472] When the maximum number of SR transmissions is not configured, the terminal device considers the maximum number of SR transmissions to be infinite.

[0473] 16. The method according to Note 11, wherein the step of not performing a clearing and / or releasing operation comprises:

[0474] If the network is in network energy saving mode, no clearing and / or releasing operations are performed;

[0475] If the network is not in network power saving mode, perform flushing and / or releasing operations.

[0476] 17. The method according to note 16, wherein if the network is not in the network energy-saving mode, performing the clearing and / or releasing operation comprises:

[0477] If the network is not in the network energy saving mode and if the SR counter reaches the maximum value, a clearing and / or releasing operation is performed.

[0478] 18. The method according to Note 17, wherein if the network is not in the network energy-saving mode, performing the clearing and / or releasing operation further comprises:

[0479] Initiate a random access procedure on a special cell; and / or

[0480] Cancel all pending SRs.

[0481] 19. The method according to any one of Notes 11 to 18, wherein the clearing comprises:

[0482] Clear any configured downlink allocations and uplink grants; and / or,

[0483] Clear any PUSCH resources used for semi-persistent CSI reporting.

[0484] 20. The method according to any one of Notes 11 to 18, wherein the releasing comprises:

[0485] Notify RRC to release PUCCH for all serving cells; and / or,

[0486] Notify RRC to release the SRS of all serving cells.

[0487] 21. A communication method, wherein the method comprises:

[0488] The network device indicates information related to network energy saving to the terminal device.

[0489] 22. The method according to note 21, wherein the network device indicates information related to network energy saving to the terminal device, comprising:

[0490] The network device indicates to the terminal device that it is in the network energy-saving mode.

[0491] 23. The method according to Note 22, wherein the network energy-saving mode is at least one of the following:

[0492] The NES mode is activated.

[0493] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0494] The terminal equipment is in the inactive state of cell DTX / DRX.

[0495] 24. The method according to Note 23, wherein the network energy saving mode is activated (the NES mode is activated), the method further comprising:

[0496] The network device instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0497] 25. The method according to Note 23, wherein cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated, and the method further comprises:

[0498] The network device configures the parameters of discontinuous transmission / reception of the cell through RRC signaling.

[0499] 26. The method according to Note 23, wherein cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated, and the method further comprises:

[0500] The network device indicates activation of discontinuous transmission / reception of at least one cell of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling.

[0501] 27. The method according to Note 22, wherein the terminal device is in an inactive phase of cell discontinuous transmission / reception, the method further comprising:

[0502] The network device sends a cell discontinuous transmission / reception configuration to the terminal device, and the terminal device enters a sleep or non-activation time according to the cell discontinuous transmission / reception configuration, or the terminal device is not within the duration of the cell discontinuous transmission / reception; or, when the cell discontinuous transmission / reception is activated, the terminal device enters a sleep or non-activation time, or the terminal device is not within the duration of the cell discontinuous transmission / reception.

[0503] 28. The method according to Note 24, 25 or 26, wherein:

[0504] The RRC signaling is broadcast signaling or dedicated signaling.

[0505] 29. The method according to Supplementary Note 21, wherein the network device indicates information related to network energy saving to the terminal device, comprising:

[0506] The network device coordinates the SR configuration and the cell discontinuous transmission / reception duration (cell DTX / DRX on-duration time).

[0507] 30. The method according to note 29, wherein coordinating SR configuration and cell discontinuous transmission / reception duration comprises:

[0508] ensuring that the cell has no valid PUCCH resources during the discontinuous transmission / reception inactive time; or

[0509] Make sure that the valid PUCCH resource is within the discontinuous transmission / reception activation time of the cell.

[0510] 31. The method according to Note 21, wherein the network device indicates information related to network energy saving to the terminal device, comprising:

[0511] If the network device supports one of IAB, NTN, and positioning, the network device does not indicate that it is in the network energy saving mode or the network device is in the network energy saving mode.

[0512] 32. The method according to Note 31, wherein the network energy-saving mode is at least one of the following:

[0513] The NES mode is activated.

[0514] Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated;

[0515] The terminal equipment is in the inactive state of cell DTX / DRX.

[0516] 33. The method according to any one of Notes 22 to 28, wherein:

[0517] When the network device indicates that it is in the network energy saving mode, the network device does not support one of IAB, NTN and positioning.

[0518] 34. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 20.

[0519] 35. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 21 to 33.

[0520] 36. A communication system comprising the terminal device described in Note 34 and the network device described in Note 35.

Claims

1. A communication device, configured in a terminal device, wherein: The device comprises: A processing unit, which, when the network is in a network energy-saving mode, does not trigger a scheduling request (SR) and / or performs actions related to the network energy-saving mode for a pending scheduling request (pending SR).

2. The device according to claim 1, wherein: The network energy-saving mode refers to at least one of the following: The NES mode is activated. Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated; The terminal equipment is in the inactive state of cell DTX / DRX.

3. The device according to claim 2, wherein: The network energy saving mode is activated, including: The network device instructs the terminal device to activate the network energy saving mode through at least one of RRC signaling, MAC CE signaling and DCI signaling.

4. The device according to claim 2, wherein: The configuring and / or activating discontinuous transmission / reception of a cell includes: The network equipment configures the parameters of discontinuous transmission / reception of the cell through RRC signaling.

5. The device according to claim 2, wherein: The configuring and / or activating discontinuous transmission / reception of a cell includes: The network device indicates the activation of discontinuous transmission / reception of at least one cell of the terminal device through at least one of RRC signaling, MAC CE signaling and DCI signaling.

6. The device according to claim 2, wherein: The terminal device is in an inactive phase of discontinuous transmission / reception of a cell, including: According to the discontinuous transmission / reception configuration of the cell, the terminal device enters the sleep or inactive time, or the terminal device is not within the duration of the discontinuous transmission / reception of the cell; or, According to the cell discontinuous transmission / reception configuration, when the cell discontinuous transmission / reception is activated, the terminal device enters a sleep or inactive time, or the terminal device is not within the duration of the cell discontinuous transmission / reception.

7. The device according to claim 1, wherein: The scheduling request includes at least one of the following: Buffer Status Report (BSR) scheduling request; Beam Failure Recovery (BFR) scheduling request; Scheduling requests for consistent LBT failure recovery; Integration and Access Backhaul (IAB) related scheduling requests; Positioning related scheduling requests; Non-Terrestrial Network (NTN) related dispatch requests.

8. The device according to claim 7, wherein: If it is supported to be used simultaneously with network energy saving, the scheduling request includes one of the scheduling request related to the IAB, the scheduling request related to the positioning, and the scheduling request related to the NTN.

9. The device according to claim 1, wherein: The processing unit does not trigger a scheduling request, including: The processing unit does not configure one of IAB, NTN and positioning.

10. The device according to claim 1, wherein: The behaviors related to the network energy saving mode include: Cancel the pending scheduling request (pending SR); It is considered that there are no valid PUCCH resources configured for the pending SR; Consider SR transmission to be a low priority SR transmission; Suspend SR counter; Do not initiate a random access process; No emptying and / or releasing operations are performed; Use a larger maximum SR transmission number (sr-TransMax).

11. The device according to claim 10, wherein: If the network is not in the network energy saving mode, the processing unit performs a clearing and / or releasing operation, including: Initiate a random access procedure on a special cell; and / or Cancel all pending SRs.

12. A communication device, configured in a network device, wherein: The device comprises: A processing unit that indicates network energy saving related information to the terminal device.

13. The device according to claim 12, wherein: The processing unit indicates information related to network energy saving to the terminal device, including: The processing unit indicates to the terminal device that it is in the network energy saving mode.

14. The device according to claim 13, wherein: The network energy-saving mode refers to at least one of the following: The NES mode is activated. Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated; The UE is in an inactive state of cell discontinuous transmission / reception DTX / DRX).

15. The device according to claim 12, wherein: The processing unit indicates information related to network energy saving to the terminal device, including: The processing unit coordinates the SR configuration and the cell discontinuous transmission / reception duration (cell DTX / DRX on-duration time).

16. The device according to claim 15, wherein: The processing unit coordinates SR configuration and cell discontinuous transmission / reception duration, including: The processing unit makes the cell have no valid PUCCH resource (valid PUCCH resource) during the discontinuous transmission / reception inactive time (inactive time); or The processing unit enables a valid PUCCH resource (valid PUCCH resource) to be within the discontinuous transmission / reception activation time of the cell.

17. The device according to claim 12, wherein: The processing unit indicates information related to network energy saving to the terminal device, including: If the network device supports one of IAB, NTN and positioning, the processing unit does not indicate that the network device is in the network energy saving mode or the network device is in the network energy saving mode.

18. The device according to claim 17, wherein: The network energy-saving mode refers to at least one of the following: The NES mode is activated. Cell discontinuous transmission / reception (cell DTX / DRX) is configured and / or activated; The terminal equipment is in the inactive state of cell DTX / DRX.

19. The device according to claim 13, wherein: When the network device indicates that it is in the network energy saving mode, the network device does not support one of IAB, NTN and positioning.

20. A communication system, comprising a network device and a terminal device, wherein: The terminal device is configured as follows: When the network is in a network energy saving mode, not triggering a scheduling request (SR) and / or performing actions related to the network energy saving mode for a pending scheduling request (pending SR); and / or, The network device is configured as follows: Indicates network energy saving related information to terminal devices.

Images