Energy-saving method and device, equipment and storage medium
Patent Information
- Application Number
- CN202511946147.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-08-05
- Filing Date
- 2022-08-10
- Publication Date
- 2026-02-10
AI Technical Summary
[0005]然而目前的节能研究主要针对终端,尚无针对网络节能技术的研究
Smart Images

Figure CN121510171A_ABST
Abstract
Description
[0001] This application is a divisional application of patent application filed on August 10, 2022, with application number 202280096025.9 and invention title "Energy Saving Method, Apparatus, Equipment and Storage Medium".
[0002] This application claims priority to patent application filed on August 5, 2022, with application number PCT / CN2022 / 110715, entitled "Energy Saving Method, Apparatus, Equipment and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communications, and in particular to an energy-saving method, apparatus, device, and storage medium. Background Technology
[0004] Energy consumption has become a significant component of operators' operating costs. The energy cost of mobile networks accounts for approximately 23% of operators' total costs, with the majority of this energy consumption coming from radio access networks, particularly active antenna units (AAUs).
[0005] However, current energy-saving research mainly focuses on the terminal, and there is no research on network energy-saving technologies. Summary of the Invention
[0006] This application provides an energy-saving method, apparatus, device, and storage medium to support network energy saving. The technical solution is as follows: According to one aspect of this application, an energy-saving method is provided, the method being executed by a terminal, the method comprising: The method is executed by a terminal, and the method includes: Perform operations related to network energy saving.
[0007] According to one aspect of this application, an energy-saving method is provided, the method being executed by a network, the method comprising: Perform operations related to network energy saving.
[0008] According to one aspect of this application, an energy-saving device is provided, the device comprising: The first processing module is used to perform operations related to network energy saving.
[0009] According to one aspect of this application, an energy-saving device is provided, the device comprising: The second processing module is used to perform operations related to network energy saving.
[0010] According to one aspect of this application, a terminal is provided, the terminal comprising: a processor; a transceiver connected to the processor; and a memory for storing an executable program of the processor; wherein the processor is configured to load and execute the executable program to implement the energy-saving method as described above.
[0011] According to one aspect of this application, a network device is provided, the network device comprising: a processor; a transceiver connected to the processor; and a memory for storing an executable program of the processor; wherein the processor is configured to load and execute the executable program to implement the energy-saving method as described above.
[0012] According to one aspect of this application, a computer-readable storage medium is provided, wherein an executable program is stored therein, the executable program being loaded and executed by a processor of a communication device to implement the energy-saving method as described above.
[0013] According to one aspect of this application, a computer program product is provided, the computer program product comprising a computer program stored in a computer-readable storage medium, a processor of a communication device reading the computer program from the computer-readable storage medium, the processor executing the computer program, causing the communication device to perform the energy-saving method as described above.
[0014] According to one aspect of this application, a chip is provided, the chip including programmable logic circuitry or a program, and a communication device on which the chip is mounted is used to implement the energy-saving method as described above.
[0015] The technical solutions provided in this application have at least the following beneficial effects: By performing network energy-saving operations, the goal of network energy saving can be achieved. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This diagram illustrates a system message update in the related art. Figure 2 A flowchart illustrating a condition-triggered switching process in the related technology is shown. Figure 3This illustration shows a schematic diagram of a communication system provided by one embodiment of the present application; Figure 4 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 5 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 6 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 7 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 8 A schematic diagram of an energy-saving method provided in an illustrative embodiment of this application is shown; Figure 9 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 10 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 11 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 12 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 13 This illustration shows a structural diagram of a first piece of information provided in an illustrative embodiment of this application; Figure 14 This illustration shows a structural diagram of a first piece of information provided in an illustrative embodiment of this application; Figure 15 A schematic diagram of an energy-saving method provided in an illustrative embodiment of this application is shown; Figure 16 A schematic diagram of an energy-saving method provided in an illustrative embodiment of this application is shown; Figure 17 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 18 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 19 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 20 A schematic diagram of an energy-saving method provided in an illustrative embodiment of this application is shown; Figure 21A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 22 A schematic flowchart of an energy-saving method according to an illustrative embodiment of this application is shown; Figure 23 A schematic diagram of a CG / SPS configuration provided in an illustrative embodiment of this application is shown; Figure 24 The illustration shows a schematic diagram of an architecture provided by one illustrative embodiment of this application; Figure 25 This illustration shows a structural block diagram of an energy-saving device according to an illustrative embodiment of the present application; Figure 26 This illustration shows a structural block diagram of an energy-saving device according to an illustrative embodiment of the present application; Figure 27 The diagram shows a schematic embodiment of an energy-saving device provided in this application. Detailed Implementation
[0018] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0019] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0020] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."
[0021] First, the relevant technologies involved in the embodiments of this application will be introduced: With people's pursuit of speed, latency, high-speed mobility, and energy efficiency, and the increasing diversity and complexity of communication services in future life, the 3rd Generation Partnership Project (3GPP) international standards organization began developing fifth-generation mobile communication technology (5G). The main application scenarios for 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC).
[0022] eMBB still aims to provide users with multimedia content, services, and data, and its demand is growing rapidly. On the other hand, because eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made; a detailed analysis based on the specific deployment scenario is necessary. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include high connection density, small data volume, latency-insensitive services, low module cost, and long module lifespan.
[0023] New Radio (NR) can also be deployed independently. In 5G network environments, to reduce air interface signaling, quickly restore radio connectivity, and quickly restore data services, a new Radio Resource Control (RRC) state has been defined, namely the RRC Inactive (RRC_INACTIVE) state. This state is different from the RRC Idle (RRC_IDLE) and RRC Active (RRC_ACTIVE) states.
[0024] RRC_IDLE: Mobility is based on User Equipment (UE) cell selection and reselection. Paging is initiated by the Core Network (CN), and the paging area is configured by the CN. There is no UE Access Stratum (AS) context on the base station side. No RRC connection exists.
[0025] RRC_CONNECTED: An RRC connection exists, and the base station and UE share a UE AS context. The network side knows the UE's location at the cell level. Mobility is network-controlled. Unicast data can be transmitted between the UE and the base station.
[0026] RRC_INACTIVE: Mobility is based on UE cell selection reselection, there is a connection between CN and NR, the UE AS context exists on a certain base station, paging is triggered by the Radio Access Network (RAN), the RAN-based paging area is managed by the RAN, and the network side knows the UE's location at the RAN-based paging area level.
[0027] Bandwidth Part (BWP) Technology To provide higher data transmission rates and improve user experience, 5G NR further increases system bandwidth compared to 4G. In 5G NR, for frequency bands below 6GHz, the maximum bandwidth supported by a single carrier is 100MHz; for frequency bands above 6GHz, the maximum bandwidth supported by a single carrier is 400MHz. For a large carrier bandwidth, such as 100MHz, the bandwidth required by the terminal is often very limited. If the terminal were to continuously detect and measure across the entire bandwidth, it would pose a significant challenge to terminal power consumption, hindering power saving. Therefore, 5G NR introduces the concept of BWP (Blocked Width Portfolio), which allocates a continuous portion of the large-bandwidth carrier for the terminal to transmit and receive data. The terminal only needs to perform relevant operations within this portion of the network-configured bandwidth, thereby achieving energy saving.
[0028] Based on 5G NR standards, for each serving cell of a terminal, the network can configure one or more Backend Devices (BWPs) for the terminal in that serving cell via RRC reconfiguration messages, with a maximum of four BWPs. At any given time, the terminal can only have one active downlink (DL) BWP and one active uplink (UL) BWP in that serving cell, and the terminal can only send and receive data on the active BWPs. Considering the diversity of terminal services and the differences in the characteristics of different services, the terminal may need to adjust its BWP. For example, when the terminal has a high traffic volume and desires high-speed service, a large-bandwidth BWP is needed for data transmission. When the terminal has a low traffic volume, a small-bandwidth BWP can be used for data transmission. The active BWP of the terminal in that serving cell can be changed through BWP handover. Currently, the relevant standards support the following four BWP handover methods: 1. BWP handover based on Physical Downlink Control Channel (PDCCH) Network-controlled BWP handover. The network informs individual terminals of the target BWP by sending a PDCCH with the Cell-Radio Network Temporary Identifier (C-RNTI) scrambled.
[0029] 2. BWP handover based on RRC (re)configuration Network-controlled BWP switching. By including firstActiveDownlinkBWP-Id or / and firstActiveUplinkBWP-Id in the RRC (re)configuration message, the terminal is instructed to switch the active BWP to firstActiveDownlinkBWP-Id or / and firstActiveUplinkBWP-Id.
[0030] 3. BWP switching based on timer timeout This is an implicit BWP handover method. The network side configures a timer, bwp-InactivityTimer, for each serving cell of the terminal. If the terminal's currently active DL BWP is a BWP other than the default BWP and the initial DL BWP, the timer bwp-InactivityTimer is started or restarted each time the terminal receives a PDCCH indicating uplink or downlink scheduling for the UE on the currently active BWP, or whenever the terminal receives a PDCCH indicating uplink or downlink scheduling for the UE on the currently active BWP. When the timer bwp-InactivityTimer expires, the terminal automatically switches to either the default BWP or the initial DL BWP, where the default BWP and the initial BWP are determined by the RRC configuration.
[0031] 4. BWP handover caused by random access initialization During the Random Access Channel (RACH) initialization process, if the terminal does not configure a Physical Random Access Channel (PRACH) occasion on the currently active UL BWP, the terminal will automatically switch the UL BWP to the initial UL BWP and simultaneously switch the DL BWP to the initial DL BWP.
[0032] System message update In Long Term Evolution (LTE) and NR systems, the concept of a system message update period is used. When the network needs to update system messages, it first retransmits the system message update indication in the nth system message update period, and then retransmits the modified system message in the (n+1)th system message update period. The boundary of the system message update period is defined as the SFN that satisfies System Frame Number (SFN) mod m = 0, where m is the number of SFNs contained in a Modification Period (MP). modificationPeriodCoeff * defaultPagingCycle ,in modificationPeriodCoeff and defaultPagingCycle These are the system message update cycle coefficient and the default paging cycle, respectively. Both parameters are determined by network broadcast. A diagram illustrating the system message update process is shown below. Figure 1 As shown.
[0033] In the NR system, the system message update cycle applies to updates of system messages other than System Information Blocks (SIBs) 6, 7, and 8, as well as positioning assistance data. In NR, short messages in the paging downlink control information (DCI) are used to notify system information update indications, and the PDCCH containing the paging DCI is scrambled via paging-RNTI.
[0034] • If in the text message systemInfoModification A value of 1 indicates that for system messages other than SIB6, SIB7, and SIB8, updates are required, and the terminal will obtain the updated system messages in the next system message update cycle.
[0035] • If in the text message etwsAndCmasIndication A value of 1 indicates that the network is about to send a notification from the Earthquake and Tsunami Warning System (ETWS) and / or the Commercial Mobile Alert System (CMAS). In this case, the terminal will immediately reread SIB1, as well as SIB6, SIB7, and SIB8 after receiving the short message.
[0036] Conditional Handover (CHO) To address the issues of frequent handovers and handover failures in high-speed mobile and high-frequency deployment scenarios, LTE and NR systems have introduced condition-triggered handover processes, such as... Figure 2 As shown. Its basic principle is that the base station pre-assigns the target cell to the terminal (201), and includes the conditions for triggering the UE to hand over in the HO command (203). When the conditions related to the target cell are triggered according to the conditions configured by the network side, the UE performs the handover to the target cell according to the pre-configured handover command (204), that is, triggers the random access procedure and sends the handover completion message, avoiding the problem that the UE cannot send measurement reports and receive the handover command in time when entering the poor coverage area due to high-speed movement.
[0037] For Handover Notices (CHOs), the network can configure multiple candidate target cells in the handover command (HO command) and configure CHO execution conditions for each candidate target cell. The CHO execution conditions for each candidate target cell can include one or two triggering events. In related technologies, A3 and A5 events are available for use as CHO events, and A4 events are also generally accepted as CHO events. The terminal determines which target cell to access based on the configured CHO execution conditions.
[0038] The measurement events currently supported in NR include the following: • A1 event: The signal quality of the serving cell exceeds a threshold; • A2 event: The signal quality of the serving cell is below a threshold; • A3 event: The signal quality of a neighboring cell is higher than the signal quality of a special cell (SpCell) by a threshold. • A4 Incident: The signal quality of a neighboring cell is higher than a threshold; • A5 event: The signal quality of SpCell is below a threshold 1, while the signal quality of the neighboring cell is above a threshold 2; • Event A6: The signal quality of a neighboring cell is higher than the signal quality of the secondary cell (SCell) by a certain threshold; • B1 Incident: Signal quality of neighboring cells with different technologies exceeds a threshold; • B2 event: The signal quality of the primary cell (PCell) is below a threshold 1, and the signal quality of a neighboring cell of a different technology is above a threshold 2.
[0039] Condition-triggered Primary Secondary Cell (PSCell) Change PSCell Change (CPC) To address the issue of frequent PSCell changes in high-speed mobile and high-frequency deployment scenarios, related technologies have introduced a condition-triggered PSCell change process for LTE and NR systems. The basic principle is that the secondary node (SN) pre-assigns the target cell to the terminal, including conditions that trigger the terminal to perform a PSCell change. The terminal evaluates these conditions based on the network-configured conditions, and when the conditions are met, the terminal initiates a PSCell change. This avoids the problem of being unable to send measurement reports or receive PSCell change commands in time when entering poor coverage areas due to high-speed movement.
[0040] Similar to CHO, for CPC, the network can configure multiple candidate target cells for the terminal and configure CPC execution conditions for each candidate target cell. The CPC execution conditions for each candidate target cell can include one or two triggering events. Among related technologies, A3 and A5 events are available for CPC events. The terminal determines which target cell to access based on the configured CPC execution conditions.
[0041] Network energy saving project Energy consumption has become a significant component of operators' operating costs. According to reports, energy costs for mobile networks account for approximately 23% of operators' total costs. The majority of energy consumption comes from the radio access network, particularly active antenna units (AAUs), while data centers and fiber optic transmission account for a smaller share. Radio access network power consumption includes two types: • Dynamic components: such as the overhead during data transmission / reception; • Static components: such as the overhead of maintaining the necessary operation of wireless access devices, even when there is no continuous data transmission / reception.
[0042] Network energy conservation research should not only assess the potential benefits of network energy consumption, but also evaluate and balance the impact on network and user performance. For example, this research should not have a particularly large impact on some key performance indicators (KPIs), such as: spectrum efficiency, capacity, user-perceived throughput (UPT), latency, terminal power consumption, complexity, handover performance, call drop rate, and initial access performance.
[0043] However, current research mostly focuses on energy-saving technologies for terminals, without considering network energy saving. Furthermore, how technologies such as CHO and BWP switching support network energy saving technologies, or how they can be integrated with network energy saving technologies, remains undiscussed.
[0044] Therefore, this application proposes an energy-saving method, focusing on network energy-saving technology. The energy-saving method proposed in this application is illustrated below with illustrative embodiments.
[0045] Figure 3 The diagram illustrates a block diagram of a communication system provided in an exemplary embodiment of this application, which may include a network (NW) 32 and a terminal 34.
[0046] The network 32 in this application provides wireless communication functionality. This network 32 includes, but is not limited to: Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B, or Home Node B, HNB), Baseband Unit (BBU), Access Point (AP) in a Wi-Fi system, Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP), or Transmission and Reception Point (TRP), etc. It can also support Next Generation Node B (NGB) in 5G systems. B, gNB) or transmission point (TRP or TP), or, in a 5G system, one or a group of antenna panels (including multiple antenna panels) of a base station, or, network nodes constituting a gNB or transmission point, such as baseband unit (BBU) or distributed unit (DU), or base station in a 6G communication system, or core network (CN), fronthaul, backhaul, radio access network (RAN), network slicing, or the terminal's serving cell, Pcell, Pscell, SpCell, SCell, neighboring cell, etc.
[0047] In this application, terminal 34 may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user apparatus. This terminal includes, but is not limited to: handheld devices, wearable devices, in-vehicle devices, and IoT devices, such as: mobile phones, tablets, e-readers, laptops, desktop computers, televisions, game consoles, mobile internet devices (MID), augmented reality (AR) terminals, virtual reality (VR) terminals, mixed reality (MR) terminals, wearable devices, controllers, electronic tags, controllers, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wireless terminals in remote medical surgery, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, and wireless local loops. Loop (WLL) stations, personal digital assistants (PDAs), set-top boxes (STBs), customer premises equipment (CPEs), etc.
[0048] Network 32 and terminal 34 communicate with each other through some air interface technology, such as the Uu interface.
[0049] For example, there are two communication scenarios between network 32 and terminal 34: uplink communication scenario and downlink communication scenario. Uplink communication refers to sending signals to network 32; downlink communication refers to sending signals to terminal 34.
[0050] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Advanced Long Term Evolution (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 5th Generation (5G), New Radio (NR), evolution systems of NR, and LTE-based access to unlicensed spectrum. This application can be applied to unlicensed spectrum (LTE-U) systems, NR (NR-based access to unlicensed spectrum) systems, non-terrestrial networks (NTN) systems, wireless local area networks (WLAN), wireless Fidelity (Wi-Fi), cellular IoT systems, and cellular passive IoT systems. It can also be applied to subsequent evolutions of 5G NR systems, as well as 6G and later evolutions. In some embodiments of this application, "NR" can also be referred to as a 5G NR system or a 5G system. The 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networks.
[0051] The technical solutions provided in the embodiments of this application can also be applied to Machine Type Communication (MTC), Long Term Evolution-Machine (LTE-M) technology, Device to Device (D2D) networks, Machine to Machine (M2M) networks, Internet of Things (IoT) networks, or other networks. Among them, IoT networks may include, for example, vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as Vehicle to X (V2X), where X can represent anything. For example, V2X may include: Vehicle to Vehicle (V2V) communication, Vehicle to Infrastructure (V2I) communication, Vehicle to Pedestrian (V2P) communication, or Vehicle to Network (V2N) communication, etc.
[0052] Figure 4 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 420: Perform operations related to network energy saving.
[0053] The terminal in this application includes at least one of the following: • The terminal in the first communication protocol version, optionally, the first communication protocol version includes 3GPP R18 and / or subsequent versions of 3GPP R18 and / or subsequent versions of 3GPP; • Terminals designed for network energy saving; • Terminals instructed to report auxiliary information, which is used to assist in achieving network energy saving; • Terminals that have reported auxiliary information, which is used to assist in achieving network energy saving; • Terminals that access the current cell; • Terminals residing in the current community; • Terminals configured to a specific group; • Directs to terminals in a specific group; Terminals that reported network energy-saving capabilities; Terminals that reported network energy-saving requirements.
[0054] • Connected terminal.
[0055] • Non-connected terminal.
[0056] Among them, non-connected terminals include: idle terminals, and / or inactive terminals.
[0057] The network in this application includes at least one of the following: • Base station; • The base station corresponding to the serving cell of the terminal; • The base station corresponding to the terminal's main cell; • The base stations corresponding to the primary and secondary cells of the terminal; • The service area of the terminal; • The terminal's main cell; • Primary and secondary cells of the terminal; • Neighboring base stations; • The terminal's neighboring cells; • Cells in the Automatic Neighbor Relation (ANR) list; • Base stations in the ANR list.
[0058] In this application, the operations related to network energy saving include at least one of the following: • Report auxiliary information to the network. For example, the auxiliary information may be used to help achieve network energy saving; • Depending on the network configuration, perform data transmission and / or signaling transmission and / or system information transmission. For example, at least one of the network configurations is related to network energy saving. • Based on network status, perform data transmission and / or signaling transmission and / or system information transmission. For example, at least one of the network statuses is related to network energy saving; • Based on changes in network status, perform data transmission and / or signaling transmission and / or system information transmission. For example, at least one of the changed network statuses is related to network energy saving; • Based on network discontinuous transmission (DTX) configuration and / or network discontinuous reception (DRX) configuration, perform data transmission and / or signaling transmission and / or system information transmission. For example, at least one of the network DTX configuration and / or network DRX configuration is related to network energy saving; • Perform BWP handover based on first information. For example, at least one piece of the first information is related to network power saving, or at least one piece of the first information is related to network status, or at least one piece of the first information is related to network configuration, or at least one piece of the first information is determined based on network power saving; for example, the BWP handover is one of cell-specific, UE-specific, or UE-group-specific.
[0059] • Perform DRX transmission or reception based on DRX parameters and / or DRX configuration, wherein the DRX parameters and / or DRX configuration are specific to the terminal; • Perform cell handover based on cell handover information, where the cell handover information is terminal group handover information or cell-level handover information.
[0060] In some embodiments, when a Configured Grant (CG) period is configured with a non-integer period or non-integer parameters, the Physical Uplink Shared Channel (PUSCH) opportunity is calculated based on a first formula. In this formula, the parameters related to the CG period are rounded up or down.
[0061] In some embodiments, when a semi-persistent scheduling (SPS) cycle is configured with non-integer cycles or non-integer parameters, the Physical Downlink Shared Channel (PDSCH) opportunity is calculated based on the second formula. In the second formula, the parameters related to the SPS cycle are rounded up or down.
[0062] In summary, the method provided in this embodiment enables the terminal to perform network energy-saving related operations, thereby achieving the purpose of network energy saving.
[0063] Figure 5 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 520: Report auxiliary information to the network.
[0064] For example, the network uses auxiliary information to perform related operations. For example, the auxiliary information is used to assist in achieving network energy saving and / or scheduling / resource allocation.
[0065] For example, a connected UE, or a UE with reporting capabilities, or the aforementioned UE reporting the auxiliary information to the network.
[0066] In some embodiments, before step 520, the terminal receives a network request to report auxiliary information, or the terminal receives a network instruction to report auxiliary information.
[0067] Figure 6 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 620: Receive auxiliary information reported by the terminal.
[0068] For example, the network uses auxiliary information to perform related operations. For example, the auxiliary information is used to assist in achieving network energy saving and / or scheduling / resource allocation.
[0069] In some embodiments, prior to step 620, the network requests the terminal to report auxiliary information, or the network instructs the terminal to report auxiliary information.
[0070] Step 640: The network uses auxiliary information to perform related operations (optional).
[0071] For example, network energy saving and / or scheduling / resource allocation can be achieved based on auxiliary information.
[0072] In some embodiments, achieving network energy saving includes: achieving the purpose of network energy saving, or selecting or indicating network energy saving technology, or selecting or indicating network energy saving configuration.
[0073] Based on Figure 5 and / or Figure 6 In an optional embodiment, the auxiliary information used to assist in achieving network energy saving includes: auxiliary information for network energy saving, or auxiliary information for performing network energy saving, or auxiliary information for obtaining services or service-related information, or auxiliary information for ensuring service transmission performance while ensuring network energy saving, or auxiliary information for balancing network energy saving and network performance, or auxiliary information for selecting or configuring network energy saving parameters or technologies.
[0074] Based on Figure 5 and / or Figure 6 In an optional embodiment, the assistance information is carried in at least one of an RRC message, a Media Access Control (MAC) control element (CE), and Uplink Control Information (UCI). Optionally, the RRC message is an Uplink (UL) RRC message. Optionally, the UL RRC message is a dedicated RRC message, or a terminal assistance information message (such as a UE Assistance Information message).
[0075] Based on Figure 5 and / or Figure 6 In an optional embodiment, the terminal reports auxiliary information to the network when a first condition is met; the first condition includes at least one of the following: The terminal was instructed to report auxiliary information; • Changes to the terminal's characteristics, including at least one of the following: service characteristics, whether the service is activated, or whether the service is in use; • The terminal's preference changes include at least one of the following: preferred transmission method, preferred network configuration parameters, recommended information, whether energy saving is required, whether energy saving requirements are prioritized, and whether performance requirements are prioritized. • This terminal has not sent the auxiliary information since it was configured to report it; The current value is different from the value indicated in the last transmission of this auxiliary information.
[0076] Based on Figure 5 and / or Figure 6 In an alternative embodiment, the network includes base stations and / or cells; The base station includes at least one of the following: the base station corresponding to the serving cell of the terminal, the base station corresponding to the primary cell of the terminal, the base station corresponding to the primary and secondary cells of the terminal, the adjacent base station of the base station corresponding to the serving cell of the terminal, the adjacent base station of the base station corresponding to the primary cell of the terminal, the adjacent base station of the base station corresponding to the primary and secondary cells of the terminal, and the base station in the ANR list.
[0077] The cell includes at least one of the following: the serving cell of the terminal, the primary cell of the terminal, the primary and secondary cells of the terminal, the neighboring cells of the terminal, the cells of the neighboring base stations of the base station, and the cells of the base stations in the ANR list.
[0078] Based on Figure 5 and / or Figure 6 In an optional embodiment, the auxiliary information includes at least one of the following: • Traffic information; For example, traffic characteristics can include at least one of the following: period, arrival time, data size, latency tolerance or tolerance, and traffic priority.
[0079] Optionally, the service feature is associated with a QoS flow. For example, the service feature includes a QoS flow identity.
[0080] For example, when the service characteristics are reported, at least one of the following information can be reported: traffic periodicity, message size, timing offset, and QoS-flow identity.
[0081] Optionally, the UE NAS or application layer informs the UE AS of the service characteristics (further including QoS flow information corresponding to the service). The service characteristics may be those of all or part of the QoS flows. For example, QoS flows with the same service characteristics, or QoS flows with a one-to-one mapping between services and QoS flows, or specific QoS flows, or all QoS flows. Alternatively, the UE NAS informs the AS of the service characteristics of all or part of the QoS flows based on the service characteristics learned from the application and the relationship between the service and the QoS flows. For example, QoS flows with the same service characteristics, or QoS flows with a one-to-one mapping between services and QoS flows, or specific QoS flows, or all QoS flows. The UE AS informs the base station of the service characteristics (further including QoS flow identifiers or information).
[0082] In other implementations, the core network may inform the base station of the service characteristics. These service characteristics may be associated with corresponding QoS flow identifiers and / or QoS parameters. The service characteristics may be indicated to the base station along with the QoS parameters of the QoS flow. The service characteristics may be provided directly by the core network or requested by the base station from the core network.
[0083] Optionally, for the base station, the gNB can make good energy-saving and / or scheduling decisions based on the service characteristics associated with a QoS flow and / or the QoS parameters of that QoS flow.
[0084] Optionally, the service characteristics or variations thereof may be recommended service modes, DTX / DRX priority or preference configurations, or recommendations for cell activation or deactivation. Optionally, a related information configuration method or information element (IE) may be designed as follows (the range of values is merely an example and is not limited in this application): TrafficPatternInfo::=SEQUENCE { trafficPeriodicityENUMERATED {ms20, ms50, ms100, ms200, ms300, ms400,ms500, ms600, ms700, ms800, ms900, ms1000}, timingOffsetINTEGER (0..10239), messageSizeBIT STRING (SIZE (8)), QoS-FlowIdentity-r16QoS-FlowIdentity-r16 } Optional, recommended DTX configurations may include periods (long periods and / or short periods), time offset, duration of inactivetime, and at least one of the short periods.
[0085] Optionally, one possible information configuration method or IE design is as follows (the range of values is only an example and is not limited in this application): DTX-Preference ::=SEQUENCE { preferredDTX-InactivityTimerENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50,ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDTX-LongCycleENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256,ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12,spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2,spare1} OPTIONAL, preferredDTX-ShortCycleENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30,ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640,spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}OPTIONAL, preferredDTX-ShortCycleTimerINTEGER (1..16)OPTIONAL } • Recommended network on information; For example, the recommended network activation information may include at least one of the following: cell identifier, base station identifier, network activation instruction request, and network activation time. The network activation time may include at least one of the following: pattern, network activation duration, network activation start time, network activation end time, the sequence of network deactivation and activation, and network activation period. The pattern may include at least one of the following: network activation-network deactivation pattern or network deactivation-network activation pattern, network activation time periods or network activation time distributions within the pattern, and the pattern's period.
[0086] For example, the UE is a connected UE, or the UE is a power-saving UE, or a UE with the reporting capability, or the aforementioned UE.
[0087] In some implementations, the UE may request its serving cell to switch to a cell-off state or use cell DTX / DRX configuration. Optionally, the UE may request its serving cell to switch to a cell-off state or use cell DTX / DRX configuration based on special characteristics, or if it is determined that there is a service transmission requirement, or if it is determined that the service transmission requirement is discontinuous.
[0088] • Recommended network off information; For example, the recommended network shutdown information may include at least one of the following: cell identifier, base station identifier, network shutdown instruction request, and network shutdown time. The network shutdown time may include at least one of the following: mode, network shutdown duration, network shutdown start time, network shutdown end time, the order of network shutdown and network activation, and network shutdown cycle. The mode may include at least one of the following: network activation-network shutdown mode or network shutdown-network activation mode, network shutdown time periods or network shutdown time distributions within a mode, and the cycle of the mode.
[0089] For example, the UE is a connected UE, or the UE is a power-saving UE, or a UE with the reporting capability, or the aforementioned UE.
[0090] In some implementations, the UE may request its serving cell to switch to a cell-off state or use cell DTX / DRX configuration. Optionally, the UE may request its serving cell to switch to a cell-off state or use cell DTX / DRX configuration based on special characteristics, or when it is determined that there is a service transmission requirement, or when it is determined that the service transmission requirement is discontinuous, or when there is no service transmission requirement for a period of time.
[0091] • Recommended network DTX information; For example, the recommended network DTX information includes at least one of the following: cell identifier, base station identifier, network DTX indication, and network DTX configuration.
[0092] The network DTX configuration includes at least one of the following: DTX period, DTX mode, DTX enable information, DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable within a DTX period, the order of DTX enable and disable within a DTX mode, DTX start offset (DTX start time point), DTX enable start time, and DTX disable start time.
[0093] Optionally, the configuration or mode of DTX may include at least one cycle, such as a long cycle and / or a short cycle.
[0094] Optionally, the DTX configuration or mode includes a DTX on / DTX off configuration, such as: long DTX on configuration / short DTX off configuration, different DTX on start time / DTX off start time, and different DTX on / DTX off duration.
[0095] Optionally, within a DTX cycle or mode, DTX is enabled first, and DTX is disabled second.
[0096] Optionally, recommended cell DTX configurations may include cell identifier, period (long period and / or short period), time offset, duration of inactive state, number of short periods, and at least one of the DTX configuration usage duration or time period.
[0097] Optionally, one possible information configuration method or information IE design is as follows (the range of values is merely an example and is not limited in this application): DTX-Preference ::=SEQUENCE { preferredDTX-InactivityTimerENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50,ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDTX-LongCycleENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256,ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12,spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2,spare1} OPTIONAL, preferredDTX-ShortCycleENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30,ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640,spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}OPTIONAL, preferredDTX-ShortCycleTimerINTEGER (1..16)OPTIONAL } • Recommended network DRX information; For example, recommended network DRX information includes at least one of the following: cell identifier, base station identifier, network DRX indication, and network DRX configuration.
[0098] The network DRX configuration includes at least one of the following: DRX cycle, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable in a DRX cycle, the order of DRX enable and disable in a DRX mode, DRX start offset (DRX start time point), DRX enable start time, and DRX disable start time.
[0099] Optionally, the DRX configuration or mode includes at least one cycle, such as a long cycle and / or a short cycle.
[0100] Optionally, DRX configurations or modes include a DRX on / off configuration, such as: long DRX on / off configuration, short DRX off configuration, different DRX on start times / DRX off start times, and different DRX on / off durations.
[0101] Optionally, within a DRX cycle or mode, DRX is enabled first, and DRX is disabled second.
[0102] Optionally, recommended cell DRX configurations may include cell identifier, period (long period and / or short period), time offset, duration of inactive state, number of short periods, and at least one of the DRX configuration usage duration or time period.
[0103] Optionally, one possible information configuration method or information IE design is as follows (the range of values is merely an example and is not limited in this application): DRX-Preference ::=SEQUENCE { preferredDRX-InactivityTimerENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50,ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9,spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDRX-LongCycleENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256,ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12,spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2,spare1} OPTIONAL, preferredDRX-ShortCycleENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30,ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640,spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}OPTIONAL, preferredDRX-ShortCycleTimerINTEGER (1..16)OPTIONAL} • Recommended terminal DTX information; For example, the recommended terminal DTX information includes at least one of the following: UE identifier, terminal DTX request, terminal DTX indication, and terminal DTX configuration recommendation.
[0104] The recommended configuration for terminal DTX includes at least one of the following: DTX cycle, DTX mode, DTX enable information, DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and DTX disable within a DTX cycle, the order of DTX enable and DTX disable within a DTX mode, DTX start offset (DTX start time point), DTX enable start time, and DTX disable start time.
[0105] Optionally, the configuration or mode of DTX may include at least one cycle, such as a long cycle and / or a short cycle.
[0106] Optionally, the DTX configuration or mode includes a DTX on / DTX off configuration, such as: long DTX on configuration / short DTX off configuration, different DTX on / DTX off start times, and different DTX on / DTX off durations.
[0107] Optionally, within a DTX cycle or mode, DTX is enabled first, and DTX is disabled second.
[0108] Optional, recommended DTX configurations may include periods (long periods and / or short periods), time offset, duration of inactivetime, and at least one of the following: number of short periods.
[0109] Optionally, one possible information configuration method or information IE design is as follows (the range of values is merely an example and is not limited in this application): DTX-Preference ::=SEQUENCE { preferredDTX-InactivityTimerENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50,ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDTX-LongCycleENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256,ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12,spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2,spare1} OPTIONAL, preferredDTX-ShortCycleENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30,ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640,spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}OPTIONAL, preferredDTX-ShortCycleTimerINTEGER (1..16)OPTIONAL } • Recommended terminal DRX information; For example, the recommended terminal DRX information includes at least one of the following: UE identifier, terminal DRX request, terminal DRX indication, and terminal DRX configuration recommendation.
[0110] The recommended configuration for terminal DRX includes at least one of the following: DRX cycle, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and DRX disable within a DRX cycle, the order of DRX enable and DRX disable within a DRX mode, DRX start offset (DRX start time point), DRX enable start time, and DRX disable start time.
[0111] Optionally, the DRX configuration or mode includes at least one cycle, such as a long cycle and / or a short cycle.
[0112] Optionally, DRX configurations or modes include a DRX on / DRX off configuration, such as: long DRX on configuration / short DRX off configuration, different DRX on / DRX off start times, and different DRX on / DRX off durations.
[0113] Optionally, within a DRX cycle or mode, DRX is enabled first, and DRX is disabled second.
[0114] Optional, recommended DRX configurations may include periods (long periods and / or short periods), time offsets, duration of inactive states, and at least one of the short periods.
[0115] Optionally, one possible information configuration method or information IE design is as follows (the range of values is merely an example and is not limited in this application): DRX-Preference ::=SEQUENCE { preferredDRX-InactivityTimerENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50,ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, preferredDRX-LongCycleENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256,ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12,spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2,spare1} OPTIONAL, preferredDRX-ShortCycleENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30,ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640,spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}OPTIONAL, preferredDRX-ShortCycleTimerINTEGER (1..16)OPTIONAL } • Instruct or request the network to change the cell state; For example, instructing or requesting a network to transition a cell state may include at least one of the following: cell identifier, base station identifier, cell state transition indication, transitioned or transitioned to a cell state, and duration of cell state transition.
[0116] The duration of cell state transition includes at least one of the following: cell state transition start time, cell state transition duration, and cell state transition end time.
[0117] • Instruct or request the network to perform a network state transition; For example, instructing or requesting a network to perform a network state transition includes at least one of the following: cell identifier, base station identifier, network state transition indication, the network state to which the transition is performed, and the duration of the network state transition.
[0118] The duration of a network state transition includes at least one of the following: network state transition start time, network state transition duration, and network state transition end time.
[0119] • Instruct or request the network to enter DTX state; For example, instructing or requesting the network to enter DTX state includes at least one of the following: cell identifier, base station identifier, DTX state indication, DTX state request, and duration of DTX state.
[0120] The duration of the DTX state includes at least one of the following: DTX state start time, DTX state duration, and DTX state end time.
[0121] • Instruct or request the network to enter DRX state; For example, instructing or requesting the network to enter DRX state includes at least one of the following: cell identifier, base station identifier, DRX state indication, DRX state request, and duration of DRX state.
[0122] The duration of the DRX state includes at least one of the following: DRX state start time, DRX state duration, and DRX state end time.
[0123] • Requested network state mode; For example, network status includes at least one of the following: network on, network off, network asleep, network not asleep, network transmitting normally, network DRX status, network DTX status, and at least two load states.
[0124] The network status mode can be two or more, such as: network on / network off, network on / network off / DRX / DTX, low load / medium load / high load.
[0125] Optionally, the network status mode reporting may also include cell identifier and / or base station identifier.
[0126] • Recommended reference signal transmission configuration; For example, the reference signal transmission configuration includes at least one of the following: sequence information, port information, frequency domain resources, time domain resources, code domain resources, spatial information, and power information.
[0127] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0128] • Recommended reference signal transmission interval; For example, the reference signal transmission interval includes a time slot interval.
[0129] Optionally, the reporting may also include the types of reference information involved, such as SRS, CSI-RS, PRS, etc.
[0130] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0131] • Recommended reference signal transmission mode; For example, the reference signal transmission mode includes at least one of the following: DTX, DRX, periodic, semi-persistent, and non-periodic.
[0132] Optionally, the reporting may also include the types of reference information involved, such as SRS, CSI-RS, PRS, etc.
[0133] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0134] • Recommended data transfer configuration; For example, the data transmission configuration includes at least one of the following: sequence information, port information, frequency domain resources, time domain resources, code domain resources, spatial information, and power information.
[0135] Optionally, the reporting may also include the data types involved, such as onfigured grant, SPS, dynamic grant (DG), PUSCH, PDSCH, etc.
[0136] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0137] • Recommended data transmission interval; For example, the data transmission interval includes a time slot interval.
[0138] Optionally, the reporting may also include the data types involved, such as configured grant, SPS, DG, PUSCH, PDSCH, etc.
[0139] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0140] • Recommended data transfer mode; For example, the data transmission modes include at least one of the following: DTX, DRX, periodic, semi-persistent, and aperiodic.
[0141] Optionally, the reporting may also include the data types involved, such as configured grant, SPS, DG, PUSCH, PDSCH, etc.
[0142] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0143] • Recommended system information transmission configuration; For example, the system information transmission configuration includes at least one of the following: sequence information, port information, frequency domain resources, time domain resources, code domain resources, spatial information, and power information.
[0144] Optionally, the reporting may also include the types of system information involved, such as MIB, SIB1, SIB2, on-demand SIB, other SIBs, etc.
[0145] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0146] • Recommended system information transmission interval; For example, the system information transmission interval includes a time slot interval.
[0147] Optionally, the reporting may also include the types of system information involved, such as MIB, SIB1, SIB2, on-demand SIB, other SIBs, etc.
[0148] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0149] • Recommended system information transmission mode; For example, the system information transmission mode includes at least one of the following: DTX, DRX, periodic, semi-persistent, and non-periodic.
[0150] Optionally, the reporting may also include the types of system information involved, such as MIB, SIB1, SIB2, on-demand SIB, other SIBs, etc.
[0151] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0152] • Preferred transmission method; For example, preferred transmission methods include at least one of the following: whether to transmit, how to transmit, and what information to transmit.
[0153] Optionally, the reporting may also include the type corresponding to the preferred transmission method, such as data, channel, reference signal, system information, etc.
[0154] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0155] • Preferred network configuration parameters.
[0156] For example, network configuration parameters include at least one of the configuration parameters in RRC private signaling and / or public signaling.
[0157] For example, network configuration parameters include at least one of the following: CG (configured grant) configuration parameters, SPS configuration parameters, Physical Uplink Control Channel (PUCCH) configuration parameters, PUSCH configuration parameters, Synchronization Signal Block (SSB) configuration parameters, MIB configuration parameters, SIB configuration parameters, PDSCH configuration parameters, Scheduling Request (SR) configuration parameters, PRACH configuration parameters, DRX configuration parameters, Search Space configuration parameters, DTX configuration parameters, RACH configuration parameters, PDCCH configuration parameters, Reference Signal configuration parameters, and DG configuration parameters.
[0158] Optionally, the reporting may also include cell identifier and / or base station identifier.
[0159] In summary, based on Figure 5 and / or Figure 6 The method provided in the embodiments, by reporting auxiliary information, enables the transmission performance requirements to be guaranteed while ensuring the goal of network energy saving.
[0160] Figure 7 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 720: Obtain network status or network configuration; Network status includes base station status or cell status; The base station status includes at least one of the following: the status of the base station corresponding to the serving cell of the terminal, the status of the base station corresponding to the primary cell of the terminal, the status of the base station corresponding to the primary and secondary cells of the terminal, the status of the neighboring base stations of the base station corresponding to the serving cell of the terminal, the status of the neighboring base stations of the base station corresponding to the primary cell of the terminal, the status of the neighboring base stations of the base station corresponding to the primary and secondary cells of the terminal, and the status of the base stations in the ANR list.
[0161] Cell status includes at least one of the following: the status of the terminal's serving cell, the status of the terminal's primary cell, the status of the terminal's primary and secondary cells, the status of the terminal's neighboring cells, the status of cells of the base station's neighboring base stations, and the status of cells of base stations in the ANR list.
[0162] In some embodiments, the network status may include at least one of the following: cell network on indication, cell network off indication, base station network on indication, base station network off indication, cell identifier, base station identifier, cell DTX indication, base station DTX indication, cell DRX indication, base station DRX indication, base station network on indication, base station network off information (such as...). Figure 5 or Figure 6 In the corresponding embodiments), information on cell network activation, information on cell network deactivation, base station DRX configuration, base station DTX configuration, cell DRX configuration, cell DTX configuration (such as... Figure 5 or Figure 6 In the corresponding embodiments, the states are: cell network sleep, cell network non-sleep, base station network sleep, base station network non-sleep, cell network normal transmission, base station network normal transmission, cell network DRX state, base station network DRX state, cell network DTX state, base station network DTX state, first-level load state in at least two load states, second-level load state in at least two load states, and third-level load state in at least two load states.
[0163] In some embodiments, the network state is implicit, meaning the network indicates the use of a network power-saving technology or configuration, and the network power-saving technology or configuration corresponds to a specific network state. For example, a network indicating an extended parameter configuration corresponds to a DTX state, a DRX state, or a medium load state; or, a network indicating the transmission of data and / or signaling and / or system information according to a first configuration corresponds to a DTX state, a DRX state, or a medium load state; or, a network indicating no transmission of data and / or signaling and / or system information corresponds to a network off state.
[0164] In some embodiments, the network state is an implicit network state, that is, the network indicates information transmitted / sent / received. This information includes data and / or signaling and / or system information.
[0165] In some embodiments, the network state is an implicit network state, i.e., an updated RRC configuration message, or a network update RRC configuration. Exemplarily, the network configuration includes at least one of the configuration parameters in RRC-specific signaling and / or public signaling.
[0166] For example, network configuration can be an RRC message carrying at least one of the following configurations: CG configuration, SPS configuration, PUSCH configuration, PDSCH configuration, SR configuration, PRACH configuration, RACH configuration, PUCCH configuration, PDCCH configuration, SIB configuration, Master Indication Block (MIB) configuration, Reference Signal configuration, Search Space configuration, DRX configuration, DTX configuration, DG configuration, SSB configuration, etc.
[0167] Step 740: Based on network configuration, network status, or changes in network status, perform data transmission and / or signaling transmission and / or system information transmission; In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed according to a network configuration; at least one of the network configurations is related to network energy saving.
[0168] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed according to network status, at least one of which is related to network energy saving.
[0169] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed based on network state changes, wherein at least one of the changed network states is related to network energy saving.
[0170] In some embodiments, the network state can be two or more, such as: network on / network off, network on / network off / DRX / DTX, low load / medium load / high load state.
[0171] In some embodiments, the terminal performs data transmission and / or signaling transmission and / or system information transmission upon network indication or enable, at least one of the network indication or enable information being related to network energy saving.
[0172] In some embodiments, the mode of data and / or signaling transmission and / or system information transmission is determined based on network state change indications or information.
[0173] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed according to network conditions, including at least one of the following: • When the network instructs the terminal, perform data transmission and / or signaling transmission and / or system information transmission according to the network status; • When the terminal reports auxiliary information, perform data transmission and / or signaling transmission and / or system information transmission according to the network status.
[0174] In some embodiments, when the network indicates a network state or a state change to the terminal, data transmission and / or signaling transmission and / or system information transmission are performed according to the network state or network state change indication.
[0175] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed according to network conditions, including at least one of the following: • When the network is shut down, data transmission and / or signaling transmission and / or system information transmission will not be performed; • In the event of network shutdown, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; • When the network is shut down, perform data transmission and / or signaling transmission and / or system information transmission according to the network's DTX / DRX configuration; • When the network is enabled, perform data transmission and / or signaling transmission and / or system information transmission; • With the network enabled, data transmission and / or signaling transmission and / or system information transmission are performed according to the default configuration; • With network DTX enabled, perform data transmission and / or signaling transmission and / or system information transmission (such as...) Figure 8 (as shown) • When network DTX is disabled, data transmission and / or signaling transmission and / or system information transmission (such as...) are not performed. Figure 8 (as shown) • With network DTX disabled, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; • In the case of network DTX, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; This can be understood as: performing data transmission at cell DTX on state or enlarge the data transmission interval.
[0176] • When network DRX is enabled, perform data transmission and / or signaling transmission and / or system information transmission (such as... Figure 8 (as shown) • When network DRX is disabled, data transmission and / or signaling transmission and / or system information transmission (such as...) are not performed. Figure 8 (as shown) • With network DRX disabled, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; • In the case of network DRX, perform data and / or signaling transmission and / or system information transmission according to the first configuration; The first configuration is a configuration related to network energy saving, or the first configuration is a configuration with an increased interval compared to the default configuration.
[0177] This can be understood as: performing data transmission at cell DRX on state or enlarge the data transmission interval.
[0178] If the cell shutdown mechanism is enabled, we understand that no data transmission should occur during cell shutdown. From the UE's perspective, when the UE is aware of the cell shutdown information or receives a data transmission disable indication, it can stop data transmission. If a mechanism to reduce / adapt to transmission / reception timing is enabled, we understand that discontinuous transmission is allowed. For example, the UE can use specific durations to transmit data, such as when the UE receives cell DRX / DTX configuration or extended signaling configuration, transmitting data in DTX / DRX mode or using extended data transmission intervals.
[0179] The UE should be informed of this configuration or cell on / off status to align with network intent. This configuration or cell on / off status can be transmitted via dynamic signaling (e.g., RRC / DCI signaling) or semi-static configuration (e.g., configuration mode). Therefore, the UE can rely on this network information to operate data transmission.
[0180] That is, "If the cell off mechanism is enabled, we understand that there should be no data transmitted during the cell off situation. From the UE perspective, the UE can stop data transmission when it knows the cell off information or receives the data transmission disabling indication. If the reduced / adapted transmission / reception occasion mechanism is enabled, we understand that discontinuous transmission is allowed. For example, the UE can transmit data using a certain duration, e.g., performing data transmission in DTX / DRX mode or using an enlarged data transmission interval when the UE receives a cell DRX / DTX configuration or an enlarged signaling configuration." the UE should be informed with such configuration or the cell on / offsituation to align with the network intention. Such configuration or the cell on / off situation can be sent via dynamic signaling (eg RRC / DCI signaling) or a semi-static configuration (eg a configured pattern). Accordingly, the UE can rely on this kind of network information to operate the datatransmission. ” Step 760: Obtain updated network status or updated network configuration.
[0181] Updated network status includes updated base station status or updated cell status; The updated base station status includes at least one of the following: the status of the base station corresponding to the serving cell of the updated terminal, the status of the base station corresponding to the primary cell of the updated terminal, the status of the base station corresponding to the primary and secondary cells of the updated terminal, the status of the neighboring base stations of the base station corresponding to the serving cell of the updated terminal, the status of the neighboring base stations of the base station corresponding to the primary cell of the updated terminal, the status of the neighboring base stations of the base station corresponding to the primary and secondary cells of the updated terminal, and the status of the base stations in the updated ANR list.
[0182] The updated cell status includes at least one of the following: the status of the serving cell of the updated terminal, the status of the primary cell of the updated terminal, the status of the primary and secondary cells of the updated terminal, the status of the neighboring cells of the updated terminal, the status of the cells of the neighboring base stations of the updated base station, and the status of the cells of the base stations in the updated ANR list.
[0183] In some embodiments, the updated network status may include at least one of the following: cell network on indication, cell network off indication, base station network on indication, base station network off indication, cell identifier, base station identifier, cell DTX indication, base station DTX indication, cell DRX indication, base station DRX indication, base station network on information, base station network off information (such as...). Figure 5 or Figure 6In the corresponding embodiments), information on cell network activation, information on cell network deactivation, base station DRX configuration, base station DTX configuration, cell DRX configuration, cell DTX configuration (such as... Figure 5 or Figure 6 In the corresponding embodiments, the states are: cell network sleep, cell network non-sleep, base station network sleep, base station network non-sleep, cell network normal transmission, base station network normal transmission, cell network DRX state, base station network DRX state, cell network DTX state, base station network DTX state, first-level load state in at least two load states, second-level load state in at least two load states, and third-level load state in at least two load states.
[0184] In some embodiments, the updated network state is an implicit network state, that is, the network indicates the network power-saving technology or network power-saving configuration used, and the network power-saving technology or network power-saving configuration corresponds to the corresponding updated network state. For example, the network indicates an extended parameter configuration, corresponding to a DTX state, a DRX state, or a medium load state; or, the network indicates that data and / or signaling and / or system information is transmitted according to a first configuration, corresponding to a DTX state, a DRX state, or a medium load state; or, the network indicates that no data and / or signaling and / or system information is transmitted, corresponding to a network off state.
[0185] In some embodiments, the updated network state is an implicit network state, that is, the network indicates information transmitted / sent / received. This information includes data and / or signaling and / or system information.
[0186] In some embodiments, the network state is an implicit network state, that is, an updated RRC configuration message, or a network update RRC configuration.
[0187] For example, network configuration parameters include at least one of the configuration parameters in RRC private signaling and / or public signaling.
[0188] For example, network configuration can be an RRC message carrying at least one of the following configurations: CG configuration, SPS configuration, PUSCH configuration, PDSCH configuration, SR configuration, PRACH configuration, RACH configuration, PUCCH configuration, PDCCH configuration, SIB configuration, Master Indication Block (MIB) configuration, Reference Signal configuration, Search Space configuration, DRX configuration, DTX configuration, DG configuration, SSB configuration, etc.
[0189] For example, indicating a change in cell situation to cell off. When switching to cell off, we understand there should be no data transmission. From the UE's perspective, when the UE knows the cell off information or receives a data transmission disabling indication, it can stop data transmission. Another example is indicating updated network configurations, such as an extended transmission interval or triggering DRX / DTX. When switching to an extended transmission interval or triggering DRX / DTX, we understand discontinuous transmission is allowed. For example, the UE can transmit data for a specific duration, such as when the UE receives a cell DRX / DTX configuration or an enlarged signaling configuration, by transmitting data in DTX / DRX mode or using an enlarged data transmission interval.
[0190] The UE should be informed of this configuration or cell on / off status to align with network intent. This configuration or cell on / off status can be transmitted via dynamic signaling (e.g., RRC / DCI signaling) or a semi-static configuration (e.g., a configured pattern). Therefore, the UE can rely on this network information to operate data transmission. In some embodiments, data and / or signaling and / or system information includes at least one of the following: • Public information or signaling; Terminal-specific information, signaling, or data.
[0191] In some embodiments, the public information or signaling includes at least one of the following: SSB, MIB, System Information Block SIB1, other SIBs, Reference Signal (RS), and Physical Random Access Channel (PRACH); Terminal-specific information, signaling, or data includes at least one of the following: terminal-specific reference signal, physical downlink control channel (PDCCH), physical uplink control channel (PUCCH), downlink data, uplink data, DG, SPS, CG, and SR.
[0192] In summary, the method provided in this embodiment supports executing different transmission modes according to network conditions, thereby achieving the goal of network energy saving.
[0193] Figure 9 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 920: Based on the network DTX configuration and / or network DRX configuration, perform data transmission and / or signaling transmission and / or system information transmission.
[0194] Among them, at least one of the network DTX configuration and / or network DRX configuration is related to network energy saving.
[0195] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed based on network DTX configuration and / or network DRX configuration, including at least one of the following: • When network DTX is enabled, perform data transmission and / or signaling transmission and / or system information transmission; • When network DTX is disabled, data transmission and / or signaling transmission and / or system information transmission are not performed; • With network DTX disabled, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; • In the case of network DTX, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; This can be understood as: performing data transmission at cell DTX on state or enlarge the data transmission interval.
[0196] • When network DRX is enabled, perform data transmission and / or signaling transmission and / or system information transmission; • When network DRX is disabled, data transmission and / or signaling transmission and / or system information transmission are not performed; • With network DRX disabled, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; • In the case of network DRX, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; This can be understood as performing data transmission at cell DRX on state or enlarging the data transmission interval. In some embodiments, increasing the data transmission interval can be understood as "the data transmission interval in energy-saving state is greater than the data transmission interval in non-energy-saving state". The first configuration is a configuration related to network energy saving, or the first configuration is a configuration with an increased interval compared to the default configuration.
[0197] In some embodiments, data and / or signaling and / or system information are default, network-indicated, or pre-configured.
[0198] In some embodiments, data transmission and / or signaling transmission and / or system information transmission are performed based on network DTX configuration and / or network DRX configuration. This can be understood as the default, network-indicated, or pre-configured data and / or signaling and / or system information being transmitted in accordance with the network DTX configuration and / or network DRX configuration.
[0199] Step 940: Get the network status, or the updated network status.
[0200] In some embodiments, the network status is obtained before or during step 920.
[0201] In some embodiments, after step 920, the updated network status is obtained.
[0202] In some embodiments, the network status is determined based on network status change indications or information.
[0203] In some embodiments, the updated network status is determined based on network status change indications or information.
[0204] In some embodiments, the network status or updated network status is implicitly indicated based on at least one of the following: • Energy-saving technology guidelines; • Energy-saving configuration; • Energy saving indicator; • Network status transition indication; • Whether a network state transition indicator has been received; • Network transmission configuration; • Network configuration; • Indicates the information that can be transmitted / sent / received; • Public information or signaling; • Terminal-specific information, signaling, or data.
[0205] Figure 10 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 1020: Configure or instruct network DTX configuration and / or network DRX configuration.
[0206] For example, at least one of the network DTX configuration and / or network DRX configuration is related to network energy saving.
[0207] Step 1040: Perform data transmission and / or signaling transmission and / or system information transmission.
[0208] The transmission method of data and / or signaling and / or system information corresponds to at least one configuration in the network DTX configuration; And / or, the transmission method of data and / or signaling and / or system information corresponds to at least one configuration in the network DRX configuration.
[0209] Based on Figure 9 and / or Figure 10 In an optional embodiment, the network DTX configuration and / or network DRX configuration are determined based on the network status; And / or, the network DTX configuration and / or network DRX configuration are determined based on service transmission requirements.
[0210] Based on Figure 9 and / or Figure 10 In an optional embodiment, the network status includes base station status or cell status; The base station status includes at least one of the following: the status of the base station corresponding to the serving cell of the terminal, the status of the base station corresponding to the primary cell of the terminal, the status of the base station corresponding to the primary and secondary cells of the terminal, the status of the neighboring base stations of the base station corresponding to the serving cell of the terminal, the status of the neighboring base stations of the base station corresponding to the primary cell of the terminal, the status of the neighboring base stations of the base station corresponding to the primary and secondary cells of the terminal, and the status of the base stations in the ANR list.
[0211] Cell status includes at least one of the following: the status of the terminal's serving cell, the status of the terminal's primary cell, the status of the terminal's primary and secondary cells, the status of the terminal's neighboring cells, the status of cells of the base station's neighboring base stations, and the status of cells of base stations in the ANR list.
[0212] Based on Figure 9 and / or Figure 10 In an optional embodiment, the network state can be two or more, such as: network on / network off, network on / network off / DRX / DTX, low load / medium load / high load state.
[0213] Based on Figure 9 and / or Figure 10 In an optional embodiment, the data and / or signaling and / or system information includes at least one of the following: • Public information or signaling; Terminal-specific information, signaling, or data.
[0214] Based on Figure 9 and / or Figure 10 In an optional embodiment, the common information or signaling includes at least one of the following: synchronization signal block SSB, master information block MIB, system information block SIB1, other SIBs, common reference signal RS, and random access channel PRACH; Terminal-specific information, signaling, or data includes at least one of the following: terminal-specific reference signal, physical downlink control channel (PDCCH), physical uplink control channel (PUCCH), downlink data, uplink data, dynamic scheduling resource (DG), semi-persistent scheduling (SPS), configuration authorization (CG), and scheduling request (SR).
[0215] Based on Figure 9 and / or Figure 10 In an alternative embodiment, the network DTX configuration includes at least one of the following: network DTX indication; network DTX configuration parameters.
[0216] Based on Figure 9 and / or Figure 10 In an alternative embodiment, the network DRX configuration includes at least one of the following: network DRX indication; network DRX configuration parameters.
[0217] Based on Figure 9 and / or Figure 10 In an optional embodiment, the configuration parameters of network DTX include at least one of the following: DTX period, DTX mode, DTX enable information, DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable in a DTX period, the order of DTX enable and disable in a DTX mode, DTX start offset, DTX enable start time, DTX disable start offset, and DTX disable start time. The configuration parameters of network DRX include at least one of the following: DRX period, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable in a DRX period, the order of DRX enable and disable in a DRX mode, DRX start offset, DRX enable start time, DRX disable start offset, and DRX disable start time.
[0218] Optionally, the configuration or mode of DTX may include at least one cycle, such as a long cycle and / or a short cycle.
[0219] Optionally, the DTX configuration or mode includes a DTX on / DTX off configuration, such as: long DTX on configuration / short DTX off configuration, different DTX on / DTX off start times, and different DTX on / DTX off durations.
[0220] Optionally, within a DTX cycle or mode, DTX is enabled first, and DTX is disabled second.
[0221] Optionally, the DRX configuration or mode includes at least one cycle, such as a long cycle and / or a short cycle.
[0222] Optionally, DRX configurations or modes include a DRX on / DRX off configuration, such as: long DRX on configuration / short DRX off configuration, different DRX on / DRX off start times, and different DRX on / DRX off durations.
[0223] Optionally, within a DRX cycle or mode, DRX is enabled first, and DRX is disabled second.
[0224] In summary, based on Figure 9 and / or Figure 10 The method provided in the embodiments introduces network DRX and / or DTX configurations, performs transmissions based on the configurations, and achieves the purpose of network energy saving.
[0225] Figure 11 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 1120: Perform BWP handover based on the first information.
[0226] In some embodiments, the terminal receives the first information through a common search space; Alternatively, the first information can be received through the UE-specific search space. Alternatively, receive the first information through the first search space; The first search space is configured or predefined by the network; optionally, the first search space is a specific search space.
[0227] In some embodiments, the public search space and / or the terminal-specific search space are shared.
[0228] In some embodiments, the public search space and / or the terminal-specific search space are configured independently.
[0229] In some embodiments, the first information is received through a public search space, or the first information is received through a terminal-specific search space, or the first information is received through a first search space.
[0230] In some embodiments, receiving first information through a public search space or a first search space when a first condition is met can also be understood as the terminal performing a BWP handover based on the first information when the first condition is met. The first condition includes at least one of the following: • The network status is in state 1; The terminal obtains the network status as the first state; • Instruct BWP to switch; • BWP indicator for switching.
[0231] The first state includes at least one of the following: no network load, network load in the first load state, network sleep state, network DRX state, network DTX state, and power saving state. Optionally, the first load state can be a low load state.
[0232] In some embodiments, receiving the first information through the terminal-specific search space or the first search space when the second condition is met can also be understood as the terminal performing a BWP handover based on the first information when the second condition is met. The second condition includes at least one of the following: • The network status is in the second state; The terminal obtains the network status as the second state; • Instruct BWP to switch; • BWP indicator for switching.
[0233] The second state includes at least one of the following: network load in a second load state, network non-sleep state, network normal transmission state, and non-energy-saving state. Optionally, the second load state can be a high load state.
[0234] In some embodiments, when a third condition is met, the terminal switches the BWP to the second BWP based on the first information. This can also be understood as the terminal performing a BWP switch based on the first information when the third condition is met. The third condition includes at least one of the following: • The network status is in state 1; The terminal obtains the network status as the first state; • Instructed to perform BWP handover; • Instruct BWP to switch; • BWP indicator for switching.
[0235] The first state includes at least one of the following: no network load, network load in the first load state, network sleep state, network DRX state, network DTX state, and power saving state; optionally, the first load state can be a low load state.
[0236] The second BWP includes at least one of the following: a common BWP, a low-bandwidth BWP, a BWP indicating a switchover, a default BWP, a first BWP, a BWP with bandwidth less than a first threshold, a historically used BWP, a historically activated BWP, a BWP activated or used before the currently activated BWP, a BWP that was activated before the currently activated BWP, and a BWP with bandwidth greater than a second threshold.
[0237] The instruction to perform a BWP switch includes at least one of: a BWP switch instruction bit and a BWP switch instruction identifier.
[0238] In some embodiments, when a fourth condition is met, the terminal switches the BWP to a third BWP based on the first information. This can also be understood as the terminal performing a BWP handover based on the first information when the fourth condition is met. The fourth condition includes at least one of the following: • The network status is in the second state; The terminal obtains the network status as the second state; • Instructed to perform BWP handover; • Instruct BWP to switch; • BWP indicator for switching.
[0239] The second state includes at least one of the following: network load is in a second load state, network is not in sleep state, network is in normal transmission state, and network is not in energy-saving state; optionally, the second load state can be a high load state.
[0240] The third BWP includes at least one of the following: public BWP, high-bandwidth BWP, BWP indicating switching, default BWP, first BWP, historically used BWP, historically activated BWP, BWP activated or used before the currently activated BWP, the BWP activated before the currently activated BWP, and BWP with bandwidth greater than the second threshold.
[0241] The instruction to perform a BWP switch includes at least one of: a BWP switch instruction bit and a BWP switch instruction identifier.
[0242] In some embodiments, the default BWP included in the second BWP may be the same as or different from the default BWP included in the third BWP.
[0243] In some embodiments, the first BWP included in the second BWP may be the same as or different from the first BWP included in the third BWP.
[0244] For example, if network load decreases, it is reasonable for a smart network implementation to switch all UEs to a common, low-bandwidth environment. And if network load increases, the network can switch all UEs to a common, high-bandwidth environment or instruct the UEs to switch back to the previously activated BWP. Optionally, the common low-bandwidth BWP and the common high-bandwidth BWP can be different bandwidth segments, or they can overlap.
[0245] In some embodiments, the terminal performs a BWP handover based on first information, including: Upon receiving the first information, the terminal performs a BWP handover; Alternatively, upon receiving the first information, the terminal may, at the indicated handover time (e.g., Figure 14 (As shown), perform BWP switching; Or, the time when the terminal adds the first offset duration to the start time of receiving the first information (e.g.) Figure 15 (As shown), perform BWP switching; Alternatively, the terminal performs a BWP handover at the moment when the reception of the first information ends plus the second offset time. Alternatively, the terminal performs a BWP handover at the moment when the decoding of the first information begins plus the third offset duration; Alternatively, the terminal may perform a BWP handover at the moment when the decoding of the first information ends plus the fourth offset duration.
[0246] In some embodiments, the method provided in this embodiment is applicable to Pcell switching and / or Scell reactivation.
[0247] Figure 12 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 1220: Explicitly or implicitly instruct the terminal to perform a BWP handover using the first information.
[0248] In some embodiments, the method provided in this embodiment is applicable to Pcell switching and / or Scell reactivation.
[0249] Based on Figure 11 and / or Figure 12 In an optional embodiment, at least one piece of the first information is related to network energy saving, or at least one piece of the first information is related to network status, or at least one piece of the first information is related to network configuration, or at least one piece of the first information is determined based on network energy saving.
[0250] Based on Figure 11 and / or Figure 12 In an optional embodiment, the switched BWP includes at least one of the following: • Default BWP; • Historically used BWP; • Historically activated BWP; • The currently activated BWP is a BWP that was activated or used before. • The previous active BWP; • First BWP, optional, the first BWP is a specific BWP; • The first information indicated by the BWP; • The second information indicated by the BWP; • Public BWP; • High-bandwidth BWP; • Low bandwidth BWP; • Specific BWP.
[0251] Among them, the BWP used in the past includes at least one of the following: the BWP used before the current BWP, the BWP used before the current BWP, or the BWP used before the BWP switch indication, or the BWP used when receiving the first message, or the BWP used when receiving the second message, or the BWP determined by the rules in the BWP used in the past.
[0252] Historically activated BWPs include at least one of the following: previously activated BWPs, such as BWPs activated or used before the currently activated BWP, BWPs that were activated before the currently activated BWP, or BWPs that were activated before the BWP switching indication, or BWPs activated when the first message was received, or BWPs activated when the second message was received, or BWPs determined by rules among previously activated BWPs.
[0253] A specific BWP is: a BWP used during a BWP switch, or a BWP used at different times or in different patterns, or a BWP used in different states or configurations, or a BWP used at different numbers of BWP switches.
[0254] Based on Figure 11 and / or Figure 12 In an optional embodiment, the first information is carried in the SIB or in the first downlink information; optionally, the first downlink information includes at least one of the following: • Group DCI; • DCI with RNTI scrambling; • PDSCH of DCI scheduling with RNTI scrambling; • PDSCH for group DCI scheduling; • Group PDSCH; • Group of downlink MAC protocol data units (PDU).
[0255] Based on Figure 11 and / or Figure 12 In an alternative embodiment, the second information is carried in the SIB or in the first downlink information.
[0256] Based on Figure 11 and / or Figure 12In an optional embodiment, the MAC PDU carries one or more MAC sub-PDUs, each MAC sub-PDU corresponding to a UE-specific information; or, the MAC PDU carries one or more MAC sub-PDUs, each MAC sub-PDU corresponding to information of a terminal group; or, the MAC PDU carries one or more MAC sub-PDUs, each MAC sub-PDU corresponding to information at the cell level.
[0257] In one example, the MAC sub-PDU carries a common part, such as Figure 13 As shown; in one example, the MAC sub-PDU carries the UE ID or UE-specific information, such as Figure 14 As shown.
[0258] In one example, upon receiving the first information, the UE performs a BWP handover, such as... Figure 15 As shown; in one example, upon receiving the first information, the UE performs a BWP handover at the indicated handover time, as follows. Figure 16 As shown.
[0259] Based on Figure 11 and / or Figure 12 In an optional embodiment, the first BWP is configured by the network or predefined. Optionally, the first BWP includes at least one of the following: a network-powered BWP, a non-network-powered BWP, a BWP with a specific identifier (such as a BWP index), or an initial BWP.
[0260] Based on Figure 11 and / or Figure 12 In an optional embodiment, the first information includes at least one of the following: • BWP switching indicator; • Network status indication or network status change; • The changed BWP logo; • Network load status; • Should network energy saving be prioritized? • Should transmission performance be prioritized? • Energy-saving technology guidelines; • Energy-saving configuration; • Energy saving indicator; • Network status indication; • Whether a network state transition indicator has been received; • Network DTX transmission configuration; • Network off instruction; • Network on indicator; • Network DRX transmission configuration; • Network DTX configuration; • Network DRX transmission configuration; • Indicates the information that can be transmitted / sent / received; • Switching time; • Switch delay offset.
[0261] In summary, based on Figure 11 and / or Figure 12 The embodiments provided introduce a BWP handover method for different network loads. Alternatively, they provide a unified or specific BWP handover method depending on whether network energy saving is required.
[0262] Figure 17 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 1720: Perform DRX transmission or reception based on DRX parameters and / or DRX configuration.
[0263] The DRX parameters and / or DRX configurations are specific to the terminal.
[0264] In some embodiments, the DRX parameter and / or DRX configuration is all or part of the DRX parameters in related technologies, or all or part of the DRX parameters in a first communication protocol version, or all or part of the DRX parameters newly added in a first communication protocol version. Optionally, the first communication protocol version includes 3GPP Release 18 and / or subsequent versions of 3GPP Release 18 and / or subsequent versions of 3GPP.
[0265] In some embodiments, DRX transmission or reception is performed based on DRX parameters and / or DRX configuration, including: Based on DRX parameters and / or DRX configuration, and network indication information, perform updated DRX parameters or configuration; Alternatively, DRX sending or receiving may be performed based on the updated DRX parameters and / or DRX configuration, as well as network indication information.
[0266] In some embodiments, DRX transmission or reception is performed based on DRX parameters and / or DRX configuration, including: Receive at least one set of DRX parameters, each set of DRX parameters corresponding to a different index; receive the first index, and perform DRX sending or receiving based on the DRX parameters corresponding to the first index; Alternatively, receive at least one DRX configuration, with each DRX configuration corresponding to a different index; receive a second index, and based on the DRX configuration corresponding to the second index, perform DRX sending or receiving.
[0267] In some embodiments, performing DRX transmission or reception based on DRX parameters and / or DRX configuration further includes at least one of the following: • Receive two sets of DRX parameters and switch between them; In some embodiments, the terminal receives a DRX parameter switching instruction, or receives an update instruction on network status, network load, or whether energy saving is required, and the terminal switches between two sets of DRX parameters.
[0268] • Receive two DRX configurations and switch between them; • Use DRX parameters with short on-time or long cycle in energy-saving situations; • Use DRX configurations with short activation durations or long cycles when energy saving is required; • Use DRX parameters with long on-time or short cycle in non-energy-saving situations; • Use DRX configurations with long on-time or short cycles in non-energy-saving situations; • Use the first set of DRX parameters from at least one set of DRX parameters in energy-saving scenarios; • Use the first DRX configuration out of at least one DRX configuration in an energy-efficient configuration. • In non-energy-efficient situations, use the second set of DRX parameters from at least one set; • Use the second DRX configuration from at least one DRX configuration in non-energy-efficient situations.
[0269] In some embodiments, DRX transmission or reception is performed based on DRX parameters and / or DRX configuration, including: Receive at least one set of DRX parameter configurations, which correspond to different network states, network loads, or energy-saving requirements; receive indications of network states, network loads, or energy-saving requirements; determine the DRX parameters to use based on the indications of network states, network loads, or energy-saving requirements; and perform DRX sending or receiving. Alternatively, receive at least one DRX configuration, which corresponds to different network states, network loads, or energy-saving requirements; receive the indicated network state, network load, or energy-saving requirements; determine the DRX configuration to use based on the indicated network state, network load, or energy-saving requirements; and perform DRX sending or receiving.
[0270] In some embodiments, DRX transmission or reception is performed based on DRX parameters and / or DRX configuration, including: Receive a set of DRX parameter configurations, which correspond to network status, network load, or energy-saving requirements; receive indications of network status, network load, or energy-saving requirements; based on the indications of network status, network load, or energy-saving requirements, determine whether to use a set of DRX parameters and perform DRX sending or receiving. Alternatively, receive a set of DRX configurations, which correspond to network status, network load, or energy-saving requirements; receive indications of network status, network load, or energy-saving requirements; based on the indications of network status, network load, or energy-saving requirements, determine whether to use a set of DRX configurations, and perform DRX sending or receiving.
[0271] In some embodiments, performing DRX transmission or reception based on DRX parameters and / or DRX configuration further includes: Receive DRX parameters or DRX configuration updates at the cell or terminal group level; Perform DRX send or receive using updated DRX parameters or DRX configuration.
[0272] Among them, the updated DRX parameters or configurations at the cell or terminal group level are indicated by the public DCI or public MAC CE or system information or the PDSCH carried by the public DCI or public PDSCH.
[0273] Figure 18 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 1820: Configure DRX parameters and / or DRX configuration.
[0274] The DRX parameters and / or DRX configurations are specific to the terminal.
[0275] In some embodiments, DRX parameters and / or DRX configuration, as well as network indication information, are sent.
[0276] In some embodiments, at least one set of DRX parameters is sent, which corresponds to different indexes; Alternatively, send at least one set of DRX configurations corresponding to different indexes, and send a second index.
[0277] In some embodiments, two sets of DRX parameters and / or two sets of DRX configurations are sent.
[0278] In some embodiments, at least one set of DRX parameters is sent, which corresponds to different network states or network loads or energy-saving requirements; and an indication of the network state or network load or energy-saving requirements is sent. Alternatively, send at least one DRX configuration corresponding to different network states, network loads, or energy-saving requirements; send an indication of the network state, network load, or energy-saving requirements.
[0279] In some embodiments, a set of DRX parameter configurations is sent, which corresponds to network status, network load, or energy-saving requirements; an indication of network status, network load, or energy-saving requirements is sent. Alternatively, send a set of DRX configurations corresponding to network status, network load, or energy-saving requirements; send an indication of network status, network load, or energy-saving requirements.
[0280] In some embodiments, updated DRX parameters or DRX configurations at the cell or terminal group level are sent; wherein the updated DRX parameters or configurations at the cell or terminal group level are indicated by a public DCI or public MAC CE or system information or a PDSCH carried by a public DCI or a public PDSCH.
[0281] Step 1840: Receive or send DRX.
[0282] The transmission / send / receive method of DRX corresponds to the configuration of at least one set of parameters in DRX parameters; And / or, the DRX transmission / send / receive method corresponds to at least one set of configurations in the DRX configuration.
[0283] In summary, based on Figure 17 and / Figure 18 The methods provided in the embodiments introduce a way to use or update DRX parameters based on energy-saving needs or network conditions. This can reduce complexity or latency while achieving network energy savings.
[0284] Figure 19 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a terminal as an example, the method includes at least some of the following steps: Step 1920: Perform cell handover based on cell handover information.
[0285] Among them, cell handover information refers to information on terminal group handover or cell-level handover.
[0286] In some embodiments, cell handover is performed when at least one of the following conditions is met: • The currently serving community is closed; • Network energy saving; • The network load is in the first load state; optionally, the first load state is the low load state. • No network load.
[0287] Figure 21 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 2120: Send cell handover information.
[0288] Among them, cell handover information refers to information on terminal group handover or cell-level handover.
[0289] In some embodiments, cell handover information is sent under at least one of the following conditions: • The currently serving community is closed; • Network energy saving; • The network load is in the first load state; optionally, the first load state is the low load state. • No network load.
[0290] Based on Figure 19 and / or Figure 21 In an optional embodiment, the cell handover information includes handover parameters or configurations, which include: a common part and / or a terminal-specific part.
[0291] Based on Figure 19 and / or Figure 21 In an optional embodiment, the common portion is carried in the SIB or the first downlink information, and the terminal-specific portion is carried in the second downlink information; Alternatively, both the public portion and the terminal-specific portion may be carried in the first downlink information.
[0292] Based on Figure 19 and / or Figure 21 In an optional embodiment, the first downlink information includes at least one of the following: • Group DCI; • DCI with RNTI scrambling; • PDSCH of DCI scheduling with RNTI scrambling, such as the Random Access Procedure (RAR) method; • PDSCH for group DCI scheduling, such as the RAR method; • Public PDSCH; The second downlink information includes at least one of the following: • Group DCI; • DCI with RNTI scrambling; • PDSCH of DCI scheduling with RNTI scrambling, such as in the RAR method; • Public PDSCH.
[0293] Based on Figure 19 and / or Figure 21 In an optional embodiment, the information in the terminal-specific portion corresponds one-to-one with a MAC sub-PDU, and one or more MAC sub-PDUs are carried in the MAC PDU, such as... Figure 20 As shown.
[0294] Based on Figure 19 and / or Figure 21 In an optional embodiment, the MAC PDU also carries one or more MAC sub-PDUs corresponding to the common part information.
[0295] Based on Figure 19 and / or Figure 21 In an optional embodiment, the information of the terminal-specific part corresponds to all terminals in the cell, or to the terminal located in the first position, or to the first group of terminals.
[0296] The first location can be an absolute geographical location, such as latitude and longitude; or a relative geographical location, such as the relative location from the base station, the number of cells between cells, or the relative location from the terminal; or a coordinate range, such as a coordinate range on a latitude and longitude coordinate system or a coordinate range on a virtual coordinate system.
[0297] The first group of terminals can be a specific group of terminals configured by the network device, indicated by the network device, or predefined by the communication protocol; the specific group of terminals can also be a group of terminals determined by rules configured by the network device, indicated by the network device, or predefined by the communication protocol.
[0298] Based on Figure 19 and / or Figure 21 In an optional embodiment, the information of the common part corresponds to all terminals in the cell, or to the terminal located in the first position, or to the first group of terminals, or to all or some of the terminals in the first group.
[0299] The first location can be an absolute geographical location, such as latitude and longitude; or a relative geographical location, such as the relative location from the base station, the number of cells between cells, or the relative location from the terminal; or a coordinate range, such as a coordinate range on a latitude and longitude coordinate system or a coordinate range on a virtual coordinate system.
[0300] The first group of terminals can be a specific group of terminals configured or indicated by the network device, or predefined by the communication protocol; or it can be a group of terminals determined by rules configured or indicated by the network device, or predefined by the communication protocol. All or some of the terminals within the first group can be specific terminals configured or indicated by the network device, or predefined by the communication protocol; or they can be determined by rules configured or indicated by the network device, or predefined by the communication protocol.
[0301] In summary, the method provided in this embodiment offers a group switching method for network energy saving, achieving energy saving while reducing latency / overhead.
[0302] Figure 22 The illustration shows a flowchart of an energy-saving method provided in an exemplary embodiment of this application. Taking the method being executed by a network as an example, the method includes at least some of the following steps: Step 2220: Perform operations related to network energy saving.
[0303] Operations related to network energy saving include at least one of the following: • Receive reported auxiliary information, which is used to help achieve network energy saving; • Send network configuration, at least one of which is related to network energy saving; • Send network status, at least one of which is related to network energy saving; • Send network state changes, where at least one of the changed network states is related to network energy saving; • Send network DTX configuration and / or network DRX configuration, at least one of which is related to network power saving; • Send first information to perform BWP handover, wherein at least one of the first information is related to network power saving, or at least one of the first information is related to network status, or at least one of the first information is related to network configuration, or at least one of the first information is determined based on network power saving; • Send DRX parameters and / or DRX configuration, and perform DRX sending or receiving, wherein the DRX parameters and / or DRX configuration are specific to the terminal; • Send cell handover information, which may be terminal group handover information or cell level handover information.
[0304] In some embodiments, when a Configured Grant (CG) period is configured with a non-integer period or non-integer parameters, the Physical Uplink Shared Channel (PUSCH) opportunity is calculated based on a first formula. In this formula, the parameters related to the CG period are rounded up or down.
[0305] In some embodiments, when a semi-persistent scheduling (SPS) cycle is configured with non-integer cycles or non-integer parameters, the Physical Downlink Shared Channel (PDSCH) opportunity is calculated based on the second formula. In the second formula, the parameters related to the SPS cycle are rounded up or down.
[0306] In summary, the method provided in this embodiment enables the network to perform operations related to network energy saving, thereby achieving the goal of network energy saving.
[0307] An exemplary embodiment of this application provides a formula for calculating the PUSCH / PDSCH chances.
[0308] The non-integer configuration PUSCH / PDSCH opportunity calculation method provided in this embodiment is used to transmit data for a certain service. This service can be network energy saving, a service related to network energy saving, or a service independent of network energy saving. A PUSCH / PDSCH opportunity can be a single PUSCH / PDSCH opportunity or multiple PUSCH / PDSCH opportunities. The calculation method related to the PUSCH / PDSCH opportunity calculation formula provided in this embodiment can be used independently of network energy saving technology (e.g., for specific services or scenarios independent of network energy saving technology), or it can be used in conjunction with network energy saving technology.
[0309] When a CG cycle is configured with a non-integer cycle or a non-integer parameter, the PUSCH opportunity is calculated based on the first formula. When an SPS cycle is configured with a non-integer cycle or a non-integer parameter, the PUSCH opportunity is calculated based on the second formula. In the first formula, the parameters related to the CG period are rounded up or down, and in the second formula, the parameters related to the SPS period are rounded up or down.
[0310] In some embodiments, the parameters associated with the CG period or SPS period include at least one of the following: N, period, symbol length, number of time slots in each frame, position of the first PDSCH transmission at the start of SPS, and position of the first PUSCH transmission at the start of SPS.
[0311] Optionally, the location of the first PDSCH transmission in the initial SPS includes at least one of the following: the SFN of the first PDSCH transmission (i.e., the SFN at which the PDSCH transmission begins), the timeslot of the first PDSCH transmission (i.e., the timeslot at which the PDSCH transmission begins), and the symbol of the first PDSCH transmission (i.e., the symbol at which the PDSCH transmission begins). The location of the first PUSCH transmission in the initial SPS includes at least one of the following: the SFN of the first PUSCH transmission (i.e., the SFN at which the PUSCH transmission begins), the timeslot of the first PUSCH transmission (i.e., the timeslot at which the PUSCH transmission begins), and the symbol of the first PUSCH transmission (i.e., the symbol at which the PUSCH transmission begins).
[0312] In some embodiments, parameters related to the CG cycle include: N * first cycle, or N * first cycle plus the position of the first PUSCH transmission at the beginning of the CG. N represents the Nth CG cycle, the Nth PUSCH opportunity, or the first PUSCH opportunity in the Nth CG cycle, and the first cycle is related to the SPS cycle and symbol length.
[0313] Optionally, the first PUSCH opportunity in the Nth CG cycle can be the first PUSCH opportunity to appear; it can also be a specific PUSCH opportunity configured by the network device, indicated by the network device, or predefined by the communication protocol; or it can be a PUSCH opportunity determined by rules configured by the network device, indicated by the network device, or predefined by the communication protocol.
[0314] In some embodiments, parameters related to the SPS period include: N * second period, or N * second period * number of slots in each frame divided by 10, or N * second period plus the position of the first PDSCH transmission at the beginning of the SPS, or N * second period * number of slots in each frame divided by 10 plus the position of the first PDSCH transmission at the beginning of the SPS. Wherein, N represents the Nth SPS period, the nth PDSCH opportunity, or the first PDSCH opportunity in the Nth SPS period, and the second period is related to the SPS period and the symbol length.
[0315] Optionally, the first PDSCH opportunity in the Nth SPS cycle can be the first PDSCH opportunity to appear; it can also be a specific PDSCH opportunity configured by the network device, indicated by the network device, or predefined by the communication protocol; or it can be a PDSCH opportunity determined by rules configured by the network device, indicated by the network device, or predefined by the communication protocol.
[0316] In some embodiments, the first period is equal to the CG period divided by the duration of each symbol, or the period of each packet divided by the duration of each symbol, or the configured period; And / or, the second cycle is equal to the SPS cycle divided by the duration of each symbol, or the cycle of each packet divided by the duration of each symbol, or the configured cycle.
[0317] Optionally, the first period and / or the second period may be related to the business cycle or package rate or a non-integer business cycle.
[0318] Optionally, the first period and / or the second period can be represented as a non-integer (e.g., with a decimal part) or as a fraction.
[0319] Optionally, the first period and / or the second period can be equal to the service period or packet rate or a non-integer service period, or a variation of the service period or packet rate or a non-integer service period (e.g., one in fps, one in ms / symbol, etc.), or a reduction of the service period or packet rate or a non-integer service period (e.g., a fraction or decimal or a non-rounded number (integer or decimal) or a rounded number (integer or decimal)).
[0320] For example, in CG type 1: After configuring uplink grants for CG type 1, the Media Access Control (MAC) entity should sequentially consider the Nth (N>=0) uplink grant appearing in the following symbols: After an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the Nth (N>= 0) uplink grantoccurs in the symbol for which: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) + (slot number in the frame × numberOfSymbolsPerSlot ) + symbol number in the slot] = ( timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + ceiling{N × periodicity}) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) or, [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) + (slot number in the frame × numberOfSymbolsPerSlot ) + symbol number in the slot] = (ceiling{ timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity}) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) Wherein, SFN is the system frame number; numberOfSlotsPerFrame is the number of slots per frame; numberOfSymbolsPerSlot is the number of symbols per slot; slot number in the frame is the slot number in the frame; symbol number in the slot is the symbol number in the slot; timeReferenceSFN is the time-domain reference SFN used to determine the SFN offset of resources in the time domain; timeDomainOffset is the offset of resources in the time domain where SFN=0; S is the starting symbol; ceiling indicates rounding up; periodicity = the configured period value divided by the duration of each symbol (e.g., several milliseconds), or periodicity = the period of each packet (e.g., the set of Protocol Data Units (PDUs), the burst period) divided by the duration of each symbol, or the configured period value.
[0321] Optionally, the first period and / or the second period may be related to the business cycle or package rate or a non-integer business cycle.
[0322] Optionally, the first period and / or the second period can be represented as a non-integer (e.g., with a decimal part) or as a fraction.
[0323] Optionally, the first period and / or the second period can be equal to the service period or packet rate or a non-integer service period, or a variation of the service period or packet rate or a non-integer service period (e.g., one in fps, one in ms / symbol, etc.), or a reduction of the service period or packet rate or a non-integer service period (e.g., a fraction or decimal or a non-rounded number (integer or decimal) or a rounded number (integer or decimal)).
[0324] The above calculation method is an example of rounding up. The case of rounding down can be represented by floor.
[0325] In CG type 2: After configuring uplink grants for CG type 2, the MAC entity should sequentially consider the Nth (N>=0) uplink grant appearing in the following symbols: After an uplink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the Nth (N>= 0) uplink grantoccurs in the symbol for which: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) + (slot number in the frame × numberOfSymbolsPerSlot ) + symbol number in the slot] = [(SFN start time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot start time × numberOfSymbolsPerSlot + symbol start time ) + ceiling{ N × periodicity}] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) or, [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) + (slot number in the frame × numberOfSymbolsPerSlot ) + symbol number in the slot] = [ceiling{ (SFN start time ×numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot start time × numberOfSymbolsPerSlot + symbol start time ) + N × periodicity}] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot ) Among them, SFN start time The SFN, slot represents the first transmission of PUSCH. start time The symbol represents the time slot of the first transmission of PUSCH. start time The symbol representing the first transmission of PUSCH.
[0326] Optionally, the periods in CG type 1 and CG type 2 above are in milliseconds, or in frames per second (FPS), or in fractions, or in symbols, or in non-integers (e.g., with a decimal part).
[0327] The above calculation method is an example of rounding up. The case of rounding down can be represented by floor.
[0328] Optionally, the calculation formula for the corresponding CG position can also be similar to that for SPS to calculate the position of CGPUSCH.
[0329] For example, in SPS option 1 (rounded up): After configuring downlink allocation for SPS, the MAC entity should consider the Nth downlink allocation occurring in the following time slots: ( numberOfSlotsPerFrame × SFN + slot number in the frame) = [( numberOfSlotsPerFrame × SFN start time + slot start time ) + ceiling{N × periodicity × numberOfSlotsPerFrame / 10}] modulo (1024 × numberOfSlotsPerFrame ) or, ( numberOfSlotsPerFrame × SFN + slot number in the frame) = [ceiling{ ( numberOfSlotsPerFrame × SFNstart time + slot start time ) + N × periodicity × numberOfSlotsPerFrame / 10}] modulo (1024 × numberOfSlotsPerFrame ) Among them, SFN start time The SFN, slot represents the first transmission of PDSCH. start time This indicates the time slot for the first transmission of PDSCH, during which the configured downlink allocation is (re)initialized.
[0330] where SFN start time and slot start time are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was(re-)initialised. In SPS option 2 (rounding down): After configuring downlink allocation for SPS, the MAC entity should consider the Nth downlink allocation occurring in the following time slots: ( numberOfSlotsPerFrame × SFN + slot number in the frame) = [( numberOfSlotsPerFrame × SFN start time + slot start time ) + floor{N × periodicity × numberOfSlotsPerFrame / 10}] modulo (1024 × numberOfSlotsPerFrame ) or, ( numberOfSlotsPerFrame × SFN + slot number in the frame) = [floor{ ( numberOfSlotsPerFrame × SFN start time + slot start time ) + N × periodicity × numberOfSlotsPerFrame / 10}] modulo (1024 × numberOfSlotsPerFrame ) Among them, SFN start time The SFN, slot represents the first transmission of PDSCH. start timeThis indicates the time slot for the first transmission of PDSCH, during which the configured downlink allocation is (re)initialized.
[0331] Optionally, periodicity can be a second period or a configured period.
[0332] Optionally, the configured period value can be related to the business cycle, packet rate, or non-integer business cycle.
[0333] Optionally, the configured period value can be represented as a non-integer (e.g., with a decimal part) or as a fraction.
[0334] Optional, the configured or used period value is equal to the service period or packet rate or a non-integer service period, or it can be a variant of the service period or packet rate or a non-integer service period (e.g., one using fps, one using ms / symbol, etc.), or it can be a reduction of the service period or packet rate or a non-integer service period (e.g., a fraction or decimal or a non-rounded number (integer or decimal) or a rounded number (integer or decimal)).
[0335] Optionally, the period in the SPS mentioned above can be in milliseconds, or in frames per second (FPS), or in fractions, or in symbols, or in non-integer form.
[0336] Optionally, the following is an example of a CG / SPS calculation formula (the difference from the previous one is the presence or absence of square brackets or parentheses). ·SPS PDSCH: (numberOfSlotsPerFrame × SFN + slot number in the frame) =ceiling{[(numberOfSlotsPerFrame × SFNstart time + slotstart time) + N ×periodicity × numberOfSlotsPerFrame / 10]} modulo (1024 ×numberOfSlotsPerFrame) SPS supports periods of {100 / 3ms, 50 / 3ms, 100 / 9ms, 25 / 3ms}.
[0337] That is, the periodicities supported for SPS are {100 / 3ms, 50 / 3ms, 100 / 9ms,25 / 3ms}. ·CG Type 1: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slotnumber in the frame × numberOfSymbolsPerSlot) + symbol number in the slot]=ceiling{(timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot+ timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity)} modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) ·CG Type 2: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slotnumber in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = ceiling{[(SFNstart time × numberOfSlotsPerFrame ×numberOfSymbolsPerSlot + slotstart time × numberOfSymbolsPerSlot +symbolstart time) + N × periodicity]} modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) Additionally, in network configuration, there may be situations where multiple CG / SPS cycles correspond to a single service, logical channel, or transmission; or multiple CG / SPS configurations correspond to a single service cycle (i.e., one service cycle has multiple CG / SPS configurations corresponding to different resource locations); or multiple CG / SPS configurations have the same cycle but different resource configuration sizes and / or starting positions. This situation can occur in a network energy-saving environment or independently of network energy saving (i.e., there is no coupling relationship with network energy saving).
[0338] When multiple PUSCH / PDSCH opportunities exist, and multiple PUSCH / PDSCH transmission opportunities correspond to one service, or multiple CG / SPS (which also result in multiple PUSCH / PDSCH opportunities) are used to transmit one service, or multiple CG / SPS cycles correspond to one service, logical channel, or transmission, or multiple CG / SPS configurations correspond to one service cycle (i.e., one service cycle has multiple CG / SPS configurations corresponding to resource locations), or multiple CG / SPS configurations have the same cycle but different resource configuration sizes and / or starting positions, the terminal or network can indicate whether some opportunities are used or canceled, or the terminal or network can indicate which CG / SPS configuration(or PUSCH / PDSCH opportunity) is activated and / or deactivated. Further, it may include at least one of the following: • Indicates the location or identifier (one or more) of an opportunity that is used or activated, or the SPS / CG index that is used or activated, or the CG / SPS group index that is used or activated; • Locations or identifiers (one or more) indicating opportunities that are not used or deactivated, or SPS / CG indexes that are not used or deactivated, or CG / SPS group indexes that are not used or deactivated; • Indicates whether a portion of the opportunities in the current period have been used or canceled, or indicates whether a portion of the opportunities in subsequent periods (one or more) have been used or canceled; • Locations or identifiers (one or more) indicating the use or cancellation of an opportunity; • Indicated via one of the following: MAC CE, RRC, CG-UCI, SR, UCI, DCI, DL DG-DCI (indication information carried on the DG); • Indicate specific opportunities within a cycle, such as the first, the first N (N can be 1), the first X (X is a positive integer) opportunities that are used or canceled; • The chance of partial use or cancellation could be, for example, the last one, the last Y, where Y is a positive integer.
[0339] Optionally, the above indication can be the first or a specific opportunity or CG / SPS index indication, or it can be the currently active or used opportunity or CG / SPS index indication.
[0340] Optionally, the resources or resource size of multiple CG / SPS within a single cycle, or the resources or resource size configured in multiple CG / SPS, can be the same or different.
[0341] Optionally, the resources or resource size of multiple CG / SPS within a cycle, or the resources or resource size configured by multiple CG / SPS, correspond to different business data transmission requirements, business data volume transmission requirements, packet size, or data rate.
[0342] Optionally, multiple CG / SPS may have the same resources or resource size within a cycle, or multiple CG / SPS may be configured with the same resources or resource size, and at least a portion of the multiple CG / SPS may be used together for service transmission, or specific service transmission, or logical channel (LCH) transmission, or data transmission.
[0343] Optionally, the resources or resource sizes of multiple CG / SPS within a cycle or the resources or resource sizes of multiple CG / SPS configured are different, one of the CG / SPS is used for service transmission or specific service transmission or LCH transmission or data transmission, or at least some of the multiple CG / SPS are used together for service transmission or specific service transmission or LCH transmission or data transmission.
[0344] In some embodiments, the packet arrival rate is {30, 60, 90, 120} fps, and its service cycle should correspond to {33.33, 16.67, 11.11, 8.33} ms. Correspondingly, the CG / SPS cycle is {33.33, 16.67, 11.11, 8.33} ms. That is, there are no restrictions on the CG / SPS cycle configuration. In this case, the CG / SPS position calculated using the ceiling or floor formula can be considered, although the calculation result may have transmission position deviations.
[0345] In some embodiments, the packet arrival rate is {30, 60, 90, 120} fps, and its service cycle should correspond to {33.33, 16.67, 11.11, 8.33} ms. Accordingly, for 33.33ms, 11.11ms, and 8.33ms, the CG / SPS cycle is {33.33, 11.11, 8.33} ms, while the CG / SPS cycle corresponding to 16.67ms is limited to 16.66ms. That is, the CG / SPS cycle is not limited for 33.33ms, 11.11ms, and 8.33ms, but the CG / SPS cycle for 16.67ms should be limited. Otherwise, the CG / SPS position calculated using rounding formulas such as rounding up or rounding down will have deviations, which is detrimental to service transmission. Furthermore, if the decimal places of the value corresponding to the business cycle are greater than 0.5, then the CG / SPS configuration of that business cycle needs to be restricted (i.e., retaining the last decimal place without rounding up). In other embodiments, the consideration is whether to perform a rounding operation on the business cycle after considering the symbol, or on the CG / SPS cycle after considering the symbol. For example, whether to round up the cycle, or whether to round up the value obtained by dividing the cycle by the symbol duration.
[0346] In some embodiments, the packet arrival rate is {30, 60, 90, 120} fps, and its service cycle should correspond to {33.33, 16.67, 11.11, 8.33} ms. Correspondingly, the CG / SPS cycle is {33.33, 16.67, 11.11, 8.33} ms. That is, there is no restriction on the CG / SPS cycle configuration. In this case, the CG / SPS position calculated using a rounding formula (rounding up + rounding down) can be considered to avoid deviations in the transmission position and ensure service transmission. For example, the following condition can be used to determine whether to use rounding up or rounding down: For example, if the condition N mod M = 0, then the rounding down formula is used; otherwise, the rounding up formula is used. Here, N is the value of N used in the CG / SPS opportunity calculation formula when calculating the current position, or N is the Nth CG / SPS opportunity after the starting CG / SPS position or cycle, or N is the value of the Nth position corresponding to the CG / SPS configuration minus 1. Where M is the denominator for fps (for example, 60fps is 50 / 3, and the denominator is 3).
[0347] An example of a possible calculated CG / SPS position is as follows: Figure 23 As shown. When the packet arrival rate is 60fps, the service cycle is 16.67 (1000 / 60) ms. If the rounding method is used, the result can be calculated as follows. Figure 23The diagram shows the SPS PDSCH chance positions at 0ms, 17ms, 34ms, and 50ms. If a rounding-down calculation is used, the SPS PDSCH chance positions can be calculated as 0ms, 16ms, 33ms, and 50ms. Another calculation method yields SPS PDSCH chance positions at 0ms, 17ms, 34ms, and 51ms. The CG calculation position is the same or similar (e.g., considering symbol factors).
[0348] In some embodiments, for XR services or for non-integer service periods (e.g., packet arrival rates of {30, 60, 90, 120} fps, the service period should correspond to {33.33, 16.67, 11.11, 8.33} ms), a CG / SPS pattern configuration can be used to configure the transmission resources or locations for XR services or services with non-integer periods. Optionally, this CG / SPS pattern configuration is periodic. The method of configuring this CG / SPS pattern can be independent of network power-saving technologies (e.g., for specific services or specific scenarios independent of network power-saving technologies), or it can be used in conjunction with network power-saving technologies.
[0349] Optionally, multiple PUSCH / PDSCH transmission opportunities can be configured within each or a specific CG / SPS mode. These multiple PUSCH / PDSCH transmission opportunities are non-contiguous transmission opportunities.
[0350] Optionally, for this PUSCH / PDSCH transmission opportunity, the interval between a transmission opportunity and the most recent previous transmission opportunity is fixed (except for the interval between the last two transmission opportunities).
[0351] At least one of the following—CG / SPS mode configuration, CG / SPS mode period, interval between transmission opportunities, and number of transmission opportunities per CG / SPS mode—is related to at least one of the following: service period, service arrival time, and data (service packet) size. For example, for a DL 60fps XR video service, the SPS mode configuration period is 50ms. Within each SPS mode, three SPS-PDSCH transmission opportunities can be configured, with each SPS transmission opportunity having a 17ms interval between it and its most recent preceding SPS-PDSCH transmission opportunity (excluding the interval between the last two SPS-PDSCH transmission opportunities).
[0352] A possible CG / SPS mode is as follows: Figure 23 As shown. When the packet arrival rate is 60fps, the service cycle is 16.67 (1000 / 60) ms. If the rounding method is used, the result can be calculated as follows.Figure 23 The diagram shows the SPS PDSCH chance positions at 0ms, 17ms, 34ms, and 50ms. If a rounding-down calculation is used, the SPS PDSCH chance positions can be calculated as 0ms, 16ms, 33ms, and 50ms. Another calculation method yields SPS PDSCH chance positions at 0ms, 17ms, 34ms, and 51ms. The CG calculation position is the same or similar (e.g., considering symbol factors).
[0353] Optionally, for any of the period-related content in this application, such as the non-integer period, XR period, fractional period, period using the FPS identifier, period with decimal places, etc., at least one of these can be configured in the RRC configuration or MAC usage, and / or, an equivalent definition used in the configuration can be executed. (For example, for CG / SPS) For example: RRC configuration: periodicityExt2-r18ENUMERATED {ms1000 / 30, ms1000 / 60, ms1000 / 90,ms1000 / 120, spare4, spare3, spare2, spare1} OPTIONAL -- Need R; or, [[ periodicityExt2-r18ENUMERATED {ms33dot33, ms16dot66, ms11dot11,ms8dot33, spare4, spare3, spare2, spare1} OPTIONAL -- Need R ]]; or, periodicityExt2-r18ENUMERATED {msOnethousandthirty,msOnethousandsixty, msOnethousandninety, msOnethousandonehundredtwenty,spare4, spare3, spare2, spare1} OPTIONAL -- Need R.
[0354] For example, this is explained in the MAC or RRC configuration: periodicityExt2 此字段用于计算类型1和类型2无UL授权时UL传输的周期(见TS 38.321 [3],第5、8.2条)。如果此字段存在,则忽略字段周期和周期扩展。所使用的是周期扩展2除以与配置的BWP SCS相关联的符号长度。
[0355] Alternatively, 此字段用于计算类型1和类型2无UL授权时UL传输的周期(见TS 38.321 [3],第5、8.2条)。所使用的是周期扩展2除以与配置的BWP SCS相关联的符号长度。
[0356] Alternatively, 根据配置的子载波间隔[符号],CG支持以下周期: ·对于15kHz,为{100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14}; ·对于30kHz,为0.5 x {100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14}; ·对于60kHz且具有正常CP,为0.25 x {100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14}; ·0.25 x {100 / 3 / 12, 50 / 3 / 12, 100 / 9 / 12, 25 / 3 / 12} for 60kHz with ECP; ·0.125 x {100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14} for 120kHz; ·0.0625 x {100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14} for 480kHz; ·0.03125 x {100 / 3 / 14, 50 / 3 / 14, 100 / 9 / 14, 25 / 3 / 14} for 960kHz. In some embodiments, when the terminal is the sender, the first data packet is segmented at the SDAP layer or the PDCP layer; when the terminal is the receiver, the second data packet is reassembled at the SDAP layer or the PDCP layer. Specifically, the size of the first data packet exceeds the maximum data packet limit of PDCP, and / or the size of the second data packet does not exceed the maximum data packet limit of PDCP. Optionally, this method can be used for network energy saving, or services related to network energy saving, or other services independent of network energy saving. This method is suitable for scenarios where higher-layer data exceeds the lower-layer data transmission limits, such as scenarios where the transmitted data exceeds the 9000 bytes required by PDCP.
[0357] When this method is used in transmission scenarios independent of network energy conservation, such as Extended-Range (XR) services, the data packet size is relatively large and variable. For example, • 30Mbps: Average packet size: 0.5Mbit = 62500 bytes, minimum to maximum packet size is 0.5~1.5 times the average packet size; • 60Mbps: average packet size: 1Mbit = 125000 bytes, minimum to maximum packet size is 0.5~1.5 times the average packet size.
[0358] However, the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) now has a packet size limit of 9000 bytes. The maximum supported size of a PDCP SDU is 9000 bytes. The maximum supported size of a PDCP Control PDU is also 9000 bytes. Therefore, it is possible for an XR packet to exceed the PDCP packet size limit. To address this issue, the following functionality can be introduced for both the sender and / or receiver (the sender includes the terminal and / or base station, and the receiver includes the terminal and / or base station): • Sending end: Add segmentation functionality. Optionally, this functionality is implemented in Service Data Adaptation Protocol (SDAP) (e.g., after identifying the PDU set, or before routing), or in PDCP; • Receiver: Add re-assembly functionality. Optionally, this functionality can be implemented in SDAP or PDCP.
[0359] For example, for PDCP implementation, it can be as follows: Figure 24 The architecture shown.
[0360] Additionally, network configurations may specify scenarios where the service period, DRX period, CG / SPS period, or the period's DRX pattern or CG / SPS pattern is not divisible by 10240ms. This can occur in a network energy-saving environment or independently of network energy saving, meaning it is not coupled with network energy saving.
[0361] 1. When the above calculation method is used in other services independent of network energy saving, if the service period is not divisible by 10240ms, or the DRX period is not divisible by 10240ms, or the CG / SPS period is not divisible by 10240ms, or the DRX pattern of the period is not divisible by 10240ms, or the CG / SPS pattern of the period is not divisible by 10240ms, then the position of PUSCH / PDSCH / DRX calculated according to the position of the SFN start (SNF0) after wrap around will be problematic.
[0362] For example, XR traffic has a periodicity mismatch issue: for 60FPS video traffic, the traffic period is 1000 / 60 = 50 / 3 (ms), which means the traffic pattern repeats every 50ms. However, SFN runs from 0 to 1024, and 10240ms is not an integer multiple of 50ms.
[0363] There is a periodicity mismatch issue for XR traffic: For a videotraffic of 60FPS, the traffic periodicity is 1000 / 60 = 50 / 3 (ms), which means the traffic pattern repeats in every 50ms. However, the SFN runs from 0 to1024, and 10240ms is not an integer multiple of 50ms.
[0364] Therefore, in this case, it's necessary to address the issue of the value not being divisible by 10240ms. This can be mainly categorized into the following three cases: Case 1: If the DRX cycle is not divisible by 10240ms, modify the existing DRX start calculation formula (Long and Short DRX cycle starts). The position of the SFN, subframe, or slot on the left side of the equals sign represents the accumulated SFN, subframe, or slot. Specifically, the accumulated SFN, subframe, or slot is the total accumulated SFN, subframe, or slot from the DRX start position (the position of the first DRX after receiving the DRX configuration, or the position of the first calculated DRX cycle, or the first calculated position for the DRX configuration) to the current SFN, subframe, or slot. If the accumulated SFN, subframe, or slot satisfies the equation, then the SFN, subframe, or slot is the calculated start position of this DRX cycle.
[0365] For example: (taking a subframe or milliseconds as an example) 1. If a short DRX cycle is used for a DRX group, and [A] modulo ( drx-ShortCycle ) = ( drx- StartOffset modulo ( drx-ShortCycle ).
[0366] If the Short DRX cycle is used for a DRX group, and [A] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle). Where A = (SFN × 10) + subframe number, where A is the cumulative subframe, or SFN is the cumulative SFN.
[0367] 2. After the drx-SlotOffset at the start of the subframe, start the drx-on duration timer for this DRX group.
[0368] Start drx-on duration timer for this DRX group after drx-SlotOffset from the beginning of the subframe. For example: 1. If a long DRX cycle is used for a DRX group, and [B] modulo ( drx-ShortCycle ) = (drx- StartOffset modulo ( drx-ShortCycle ).
[0369] If the Long DRX cycle is used for a DRX group, and [B] modulo ( drx- LongCycle ) = drx-StartOffset . Where B = (SFN × 10) + subframe number, B is the cumulative subframe, or SFN is the cumulative SFN.
[0370] 2. Or: 3. After the drx-SlotOffset at the start of the subframe, start the drx-on duration timer for this DRX group.
[0371] Start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. For example: 1. If a short DRX cycle is used for a DRX group, and [A] modulo ( drx-ShortCycle-slot- level ) = ( drx-StartOffset modulo ( drx-ShortCycle ).
[0372] If the Short DRX cycle is used for a DRX group, and [A] modulo ( drx- ShortCycle-slot-level ) = ( drx-StartOffset modulo ( drx-ShortCycle-slot- level Where A = (SFN × 10) + subframe number + slot. Where A represents the cumulative slot.
[0373] 2. After the subframe begins, start the drx-on duration timer for this DRX group.
[0374] Start drx-on duration timer for this DRX group from the beginning of the subframe. Scenario 2: If the periodic DRX mode is not divisible by 10240ms, when calculating the position of each mode in the periodic DRX mode, or the start position, the position in the formula is used as the accumulated SFN, subframe, or time slot. Specifically, the accumulated SFN, subframe, or time slot is the total number of SFN, subframe, or time slots accumulated from the DRX start position (the position of the first DRX after receiving the DRX configuration, or the position of the first calculated DRX cycle, or the first calculated position for the DRX configuration) to the current SFN, subframe, or time slot. If the accumulated SFN, subframe, or time slot satisfies the equation, then the SFN, subframe, or time slot is the calculated start position of this DRX cycle.
[0375] For example: the position of the Nth pattern is: [starting position of the pattern + N * pattern period] modulo(10240ms) = (pattern -StartOffset The starting position of the mode is either at the time slot level or the subframe level. Optionally, the first DRX is started in this time slot of the mode. drx-on duration timer。
[0376] For example: the position of the Nth pattern is: [starting position of the pattern + N * pattern period] modulo(10240ms) = (pattern -StartOffset The starting position of the mode is at the subframe level. Optionally, the first DRX is enabled after the time slot offset at the beginning of this subframe of the mode. drx-on duration timer。
[0377] Case 3: If the periodic CG / SPS mode is not divisible by 10240ms, when calculating the position of each mode in the periodic CG / SPS mode, or the start position, the position in the formula is used as the accumulated SFN, subframe, or time slot. Specifically, the accumulated SFN, subframe, or time slot is the total accumulated SFN, subframe, or time slot from the DRX start position (the position of the first DRX after receiving the DRX configuration, or the position of the first calculated DRX cycle, or the first calculated position for the DRX configuration) to the current SFN, subframe, or time slot. If the accumulated SFN, subframe, or time slot satisfies the equation, then the SFN, subframe, or time slot is the calculated start position of this DRX cycle.
[0378] For example: the position of the Nth pattern is: [starting position of the pattern + N * pattern period] modulo(10240ms) = (pattern -StartOffsetThe starting position of the pattern is either at the time slot level or the subframe level. Optionally, this time slot position of the pattern can be the CG / SPS opportunity position, or the time slot position of the pattern plus a sign offset can be the CG / SPS opportunity position. 。
[0379] For example: the position of the Nth pattern is: [starting position of the pattern + N * pattern period] modulo(10240ms) = (pattern -StartOffset The starting position of the pattern is at the symbol level. Optionally, the starting position of this symbol in the pattern is the CG / SPS opportunity position. 。
[0380] Additionally, in network configurations, there may be multiple PUSCH / PDSCH opportunities within a single CG / SPS cycle, or multiple CG / SPS cycles (which will also generate multiple PUSCH / PDSCH opportunities) used to transmit a single service. This situation can occur in network energy-saving environments or independently of network energy saving; that is, it is not coupled with network energy saving.
[0381] 2. When there are multiple PUSCH / PDSCH opportunities in a single CG / SPS cycle, or when multiple CG / SPS cycles (which would also generate multiple PUSCH / PDSCH opportunities) are used to transmit a service, the terminal or network can indicate whether some opportunities are used or canceled. Further, this may include at least one of the following: • Indicates whether a portion of the opportunities in the current period have been used or canceled, or indicates whether a portion of the opportunities in subsequent periods (one or more) have been used or canceled; • Locations or identifiers (one or more) indicating the use or cancellation of an opportunity; • Indicated via one of the following: MAC CE, RRC, CG-UCI, SR, UCI, DCI, DL DG-DCI (indication information carried on the DG); • By indicating specific opportunities within a cycle, such as the first, the top N (N can be 1) opportunities that are used or canceled, or the top X opportunities; • The chances of being partially used or canceled could be, for example, the last one, or the last Y.
[0382] Optionally, the above indication can be the first or a specific opportunity or CG / SPS index indication, or it can be the currently active or used opportunity or CG / SPS index indication.
[0383] Additionally, packet loss processing may be performed on remaining PDUs (such as PDUs in a PDU set that have not yet been transmitted, or PDUs that meet the PDU set delay budget but have not yet been transmitted or successfully transmitted) or a set of PDUs, or it may be indicated that packet loss processing can be performed on remaining PDUs or a set of PDUs, or it may be supported to perform packet loss processing on remaining PDUs or a set of PDUs. This situation can occur in a network energy-saving environment or independently of network energy saving. That is, there is no coupling relationship with network energy saving.
[0384] 3. When packet loss processing needs to be performed on the remaining PDUs (such as PDUs in a PDU set that have not yet been transmitted, or PDUs that meet the PDU set delay budget but have not been transmitted or have been successfully transmitted) or the PDU set, or when it is indicated that packet loss processing can be performed on the remaining PDUs or the PDU set, or when packet loss processing is supported on the remaining PDUs or the PDU set, the packet loss processing execution entity can be the sending end and / or the receiving end. Optional: The sending end determines whether to perform packet loss processing based on the indication information from the receiving end. If it receives the indication information or feedback (such as a negative acknowledgment (NACK) for a PDU set or PDUs within a PDU set), it performs packet loss processing. The indication information can be sent by the receiving end itself. For example, the receiving end can send the indication information to the sending end under one of the following conditions: a status report is triggered, a PSDB timeout occurs, a PDU set transmission fails (e.g., NACK), or a PDU transmission within the PDU set fails (e.g., NACK), in which case the receiving end performs packet loss processing; alternatively, the sending end can send the indication information after requesting it, such as when the receiving end receives a request feedback and / or a request for a status report. The indication information can be a packet loss indication, a status report, or a PSDB timeout.
[0385] The receiving end determines whether to perform packet loss processing based on the sending end's indication information. Packet loss processing is performed if at least one of the following conditions is met: receiving indication information; receiving a packet loss indication; PSDB timeout; or receiving a PDU transmission status indication, such as partial data not being sent or successful transmission (for the PDU set or PDUs within the PDU set). The indication information can be sent by the sending end itself (e.g., when a status report is met, PSDB timeout occurs, or confirmation of PDU or PDU set transmission status is required, in which case the sending end performs packet loss processing), or it can be requested by the receiving end (e.g., requesting the sending end to send the indication information).
[0386] The receiving end determines whether to perform packet loss handling based on the PDU set or the transmission status of PDU set packets. For example, if the PSDB is exceeded, it is determined that a packet has not been transmitted or has been transmitted completely, and at least one NACK feedback is received, packet loss handling is performed.
[0387] The sending end determines whether to perform packet loss handling based on the PDU set or the transmission status of PDU set packets. For example, if the PSDB is exceeded, it is determined that some packets have not been transmitted or have been transmitted completely, and at least one NACK feedback is received, packet loss handling is performed.
[0388] Additionally, regarding whether SR (PUCCH) and PUSCH in different PUCCH groups can be transmitted simultaneously, or whether an overlap issue exists, one of the following solutions can be considered. This problem can occur in a network energy-saving environment, or it can be independent of network energy saving; that is, it does not exist in the coupling relationship of network energy saving.
[0389] Option 1: The determination of overlap or the restriction on simultaneous transmission is within the same PUCCH group. For example, an SR (PUCCH) and PUSCH within the same PUCCH group are considered to be in conflict, or their impact on prioritization is considered, or their impact on whether a resource is a prioritization resource. Alternatively, it is considered that SRs (PUCCHs) and PUSCHs within the same PUCCH group cannot be transmitted simultaneously. Or, it is considered that SRs (PUCCHs) and PUSCHs in different PUCCH groups can be transmitted simultaneously.
[0390] The protocol that may be affected is TS 38.321. The following is an example of a protocol that may be affected: When the MAC entity is configured with lch-basedPrioritization, foreach uplink grant delivered to the HARQ entity and whose associated PUSCH canbe transmitted by lower layers, the MAC entity shall: 1>if this uplink grant is received in a Random Access Response (i.e.in a MAC RAR or fallback RAR), or addressed to Temporary C-RNTI, or isdetermined as specified in clause 5.1.2a for the transmission of the MSGApayload: 2>consider this uplink grant as a prioritized uplink grant. 1>else if this uplink grant is addressed to CS-RNTI with NDI = 1 orC-RNTI: 2>if there is no overlapping PUSCH duration of a configured uplinkgrant which was not already de-prioritized, in the same BWP, whose priorityis higher than the priority of the uplink grant; and 2>if there is no overlapping PUCCH resource with an SR transmissionwhich was not already de-prioritized, in the same PUCCH group, and thesimultaneous transmission of the SR and the uplink grant is not allowed byconfiguration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, and the priority of the logical channel that triggeredthe SR is higher than the priority of the uplink grant: 3>consider this uplink grant as a prioritized uplink grant; 3>consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); 3>consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s); 3>if the de-prioritized uplink grant(s) is a configured uplink grantconfigured with autonomousTx whose PUSCH has already started: 4>stop the configuredGrantTimer for the corresponding HARQ process ofthe de-prioritized uplink grant(s); 4>stop the cg-RetransmissionTimer for the corresponding HARQ processof the de-prioritized uplink grant(s). 1>else if this uplink grant is a configured uplink grant: 2>if there is no overlapping PUSCH duration of another configureduplink grant which was not already de-prioritized, in the same BWP, whosepriority is higher than the priority of the uplink grant; and 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI = 1 or C-RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to thepriority of the uplink grant; and 2>if there is no overlapping PUCCH resource with an SR transmissionwhich was not already de-prioritized, in the same PUCCH group, and thesimultaneous transmission of the SR and the uplink grant is not allowed byconfiguration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, and the priority of the logical channel that triggeredthe SR is higher than the priority of the uplink grant: 3>consider this uplink grant as a prioritized uplink grant; 3>consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); 3>if the de-prioritized uplink grant(s) is a configured uplink grantconfigured with autonomousTx whose PUSCH has already started: 4>stop the configuredGrantTimer for the corresponding HARQ process ofthe de-prioritized uplink grant(s); 4>stop the cg-RetransmissionTimer for the corresponding HARQ processof the de-prioritized uplink grant(s). 3>consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s). As long as at least one SR is pending, the MAC entity shall for eachpending SR: 1>if the MAC entity has no valid PUCCH resource configured for thepending SR: 2>initiate a Random Access procedure (see clause 5.1) on the SpCelland cancel the pending SR. 1>else, for the SR configuration corresponding to the pending SR: 2>when the MAC entity has an SR transmission occasion on the validPUCCH resource for SR configured; and 2>if sr-ProhibitTimer is not running at the time of the SRtransmission occasion; and 2>if the PUCCH resource for the SR transmission occasion does notoverlap with a measurement gap: 3>if the PUCCH resource for the SR transmission occasion overlapswith neither a UL-SCH resource, in the same PUCCH group, and whosesimultaneous transmission with the SR is not allowed by configuration ofsimultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup nor anSL-SCH resource; or 3>if the MAC entity is able to perform this SR transmissionsimultaneously with the transmission of the SL-SCH resource; or 3>if the MAC entity is configured with lch-basedPrioritization, andthe PUCCH resource for the SR transmission occasion does not overlap with thePUSCH duration of an uplink grant received in a Random Access Response orwith the PUSCH duration of an uplink grant addressed to Temporary C-RNTI orwith the PUSCH duration of a MSGA payload, in the same PUCCH group, and thePUCCH resource for the SR transmission occasion for the pending SR triggeredas specified in clause 5.4.5 overlaps with any other UL-SCH resource(s), inthe same PUCCH group, and the physical layer can signal the SR on one validPUCCH resource for SR, and the priority of the logical channel that triggeredSR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and itssimultaneous transmission with the SR is not allowed by configuration ofsimultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, andthe priority of the uplink grant is determined as specified in clause 5.4.1;or. (omited) Option 2: Introduce RRC configuration. When this configuration is configured only on the network, the determination of overlap or simultaneous transmission is limited to within the same PUCCH group. For example, a conflict is only considered a conflict if SR and PUSCH conflict within a PUCCH group, or if it affects the determination of prioritization, or if it affects the determination of whether a prioritization resource is available. Alternatively, it is considered that SR (PUCCH) and PUSCH cannot be transmitted simultaneously within the same PUCCH group. Or, it is considered that SR (PUCCH) and PUSCH can be transmitted simultaneously in different PUCCH groups. Furthermore, introduce RRC configuration and UE capability. When this configuration is configured only on the network and the UE has this capability, the determination of overlap or simultaneous transmission is limited to within the same PUCCH group. For example, a conflict is only considered a conflict if SR and PUSCH conflict within a PUCCH group, or if it affects the determination of prioritization, or if it affects the determination of whether a prioritization resource is available. Alternatively, it is considered that SR (PUCCH) and PUSCH cannot be transmitted simultaneously within the same PUCCH group. Alternatively, it can be assumed that SR (PUCCH) and PUSCH in different PUCCH groups can be transmitted simultaneously. Furthermore, RRC configuration and UE capabilities are introduced. The affected protocols are at least one of TS 38.321, TS38.331, and TS38.306. The following is an example of one protocol impact: When the MAC entity is configured with lch-basedPrioritization, foreach uplink grant delivered to the HARQ entity and whose associated PUSCH canbe transmitted by lower layers, the MAC entity shall: 1>if this uplink grant is received in a Random Access Response (i.e.in a MAC RAR or fallback RAR), or addressed to Temporary C-RNTI, or isdetermined as specified in clause 5.1.2a for the transmission of the MSGApayload: 2>consider this uplink grant as a prioritized uplink grant. 1>else if this uplink grant is addressed to CS-RNTI with NDI = 1 orC-RNTI: 2>if there is no overlapping PUSCH duration of a configured uplinkgrant which was not already de-prioritized, in the same BWP, whose priorityis higher than the priority of the uplink grant; and 2>if there is no overlapping PUCCH resource with an SR transmissionwhich was not already de-prioritized and the simultaneous transmission of theSR and the uplink grant is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousPUCCH-PUSCH-differentPUCCHgroup, and the priority of the logical channel thattriggered the SR is higher than the priority of the uplink grant: 3>consider this uplink grant as a prioritized uplink grant; 3>consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); 3>consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s); 3>if the de-prioritized uplink grant(s) is a configured uplink grantconfigured with autonomousTx whose PUSCH has already started: 4>stop the configuredGrantTimer for the corresponding HARQ process ofthe de-prioritized uplink grant(s); 4>stop the cg-RetransmissionTimer for the corresponding HARQ processof the de-prioritized uplink grant(s). 1>else if this uplink grant is a configured uplink grant: 2>if there is no overlapping PUSCH duration of another configureduplink grant which was not already de-prioritized, in the same BWP, whosepriority is higher than the priority of the uplink grant; and 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI = 1 or C-RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to thepriority of the uplink grant; and 2>if there is no overlapping PUCCH resource with an SR transmissionwhich was not already de-prioritized and the simultaneous transmission of theSR and the uplink grant is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousPUCCH-PUSCH-differentPUCCHgroup, and the priority of the logical channel thattriggered the SR is higher than the priority of the uplink grant: 3>consider this uplink grant as a prioritized uplink grant; 3>consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s); 3>if the de-prioritized uplink grant(s) is a configured uplink grantconfigured with autonomousTx whose PUSCH has already started: 4>stop the configuredGrantTimer for the corresponding HARQ process ofthe de-prioritized uplink grant(s); 4>stop the cg-RetransmissionTimer for the corresponding HARQ processof the de-prioritized uplink grant(s). 3>consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s). Only PUCCH resources on a BWP which is active at the time of SRtransmission occasion are considered valid. As long as at least one SR is pending, the MAC entity shall for eachpending SR: 1>if the MAC entity has no valid PUCCH resource configured for thepending SR: 2>initiate a Random Access procedure (see clause 5.1) on the SpCelland cancel the pending SR. 1>else, for the SR configuration corresponding to the pending SR: 2>when the MAC entity has an SR transmission occasion on the validPUCCH resource for SR configured; and 2>if sr-ProhibitTimer is not running at the time of the SRtransmission occasion; and 2>if the PUCCH resource for the SR transmission occasion does notoverlap with a measurement gap: 3>if the PUCCH resource for the SR transmission occasion overlapswith neither a UL-SCH resource whose simultaneous transmission with the SR isnot allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup nor an SL-SCH resource or simultaneousPUCCH-PUSCH-differentPUCCHgroup; or 3>if the MAC entity is able to perform this SR transmissionsimultaneously with the transmission of the SL-SCH resource; or 3>if the MAC entity is configured with lch-basedPrioritization, andthe PUCCH resource for the SR transmission occasion does not overlap with thePUSCH duration of an uplink grant received in a Random Access Response orwith the PUSCH duration of an uplink grant addressed to Temporary C-RNTI orwith the PUSCH duration of a MSGA payload, and the PUCCH resource for the SRtransmission occasion for the pending SR triggered as specified in clause5.4.5 does not overlap with any other UL-SCH resource(s), and the physical layer can signal the SR on one valid PUCCH resource for SR, and the priority of the logical channel that triggered SR is higher than the priority of the uplink grant(s) for any UL-SCH resource(s) where the uplink grant was not already de-prioritized and its simultaneous transmission with the SR is not allowed by configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousPUCCH-PUSCH-differentPUCCHgroup, and the priority of the uplink grant is determined as specified in clause 5.4.1; or. (omitted) In PhysicalCellGroupConfig of TS38.331, the RRC configuration simultaneousPUCCH-PUSCH-differentPUCCHgroup-r17 is introduced. Optionally, for example, the following simultaneousPUCCH-PUSCH-differentPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup simultaneousPUCCH-PUSCH-differentPUCCHgroup Enables simultaneous SR and PUSCH transmissions in different PUCCHgroups. The TS38.331 UE capability introduces simultaneousTransmission PUCCH-PUSCH-r17. This can be found, for example, in the MAC capability parameters (MAC-Parameters). For instance, the following... simultaneousTransmissionPUCCH-PUSCH-r17ENUMERATED {supported}OPTIONAL The TS38.306 UE capability introduces simultaneousTransmission PUCCH-PUSCH-r17. This can be found, for example, in the MAC capability parameters (MAC-Parameters). For instance, the following...
[0391] The specific implementation process of Example 1 (UE reporting auxiliary information) is as follows: 1. The UE reports auxiliary information to the network. Specifically, this may include at least one of the following: 1) The network is a base station, or the base station corresponding to the UE's serving cell / Pcell / Pscell, or the UE's serving cell / Pcell / Pscell.
[0392] 2) The UE is an R18 UE, or a UE with network energy saving purpose, or a UE that is instructed by the UE to report the auxiliary information.
[0393] 3) The auxiliary information is reported by the UE in the event of an NW request, or when the UE receives a network instruction to report the auxiliary information.
[0394] 4) The auxiliary information is used for network energy saving, or for the purpose of performing network energy saving, or for obtaining business or business-related information, or for ensuring business transmission performance while ensuring network energy saving, or for balancing network energy saving and network performance, or for selecting or configuring network energy saving parameters or technologies.
[0395] 5) The auxiliary information includes at least one of the following: The auxiliary information is at least one of the following: • Traffic information, such as traffic characteristics (e.g., period, arrival time, data size, etc.).
[0396] • Recommended base station or cell / cell shutdown information. Specifically, it may include at least one of the following: cell or base station activation / deactivation indication request, activation / deactivation time (such as including at least one of the following: mode (such as activation-deactivation mode or deactivation-activation mode, activation / deactivation time period or time distribution within the mode, mode period at least one), deactivation duration, activation duration, activation start time, deactivation start time, activation end time, deactivation end time, deactivation sequence, activation period, deactivation period).
[0397] • Recommended DTX / DRX information for base stations or cells. Specifically, it may include at least one of the following: cell or base station DTX indication, cell or base station DTX configuration (including at least one of the following: DTX period, DTX mode, DTX enable information and / or DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable within a DTX period, the order of DTX enable and disable within a DTX mode, DTX start offset (DTX start time point), DTX enable start time, DTX disable start time), cell or base station DRX indication, cell or base station DRX configuration (including at least one of the following: DRX period, DRX mode, DRX enable information and / or DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable within a DTX period, the order of DRX enable and disable within a DTX mode, DRX start offset (DRX start time point), DRX enable start time, DRX disable start time).
[0398] • Optionally, the DTX / DRX configuration or mode includes at least one cycle, such as including long cycles and / or short cycles.
[0399] • Optionally, the DTX / DRX cycle or mode may include at least one on / off configuration, such as a long on configuration / short off configuration, different on / off start times, or different on / off durations.
[0400] • Optionally, within a DTX / DRX cycle or mode, enable it first and disable it later (similar to the existing UE DRX configuration or usage).
[0401] • Recommended UE DTX / DRX information. Specifically, it may include at least one of the following: UE DTX request, UE DTX configuration recommendation (including at least one of the following: DTX period, DTX mode, DTX enable information and / or DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable within a DTX period, the order of DTX enable and disable within a DTX mode, DTX start offset (DTX start time point), DTX enable start time, DTX disable start time), UE DRX request, UE DRX configuration recommendation (including at least one of the following: DRX period, DRX mode, DRX enable information and / or DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable within a DTX period, the order of DRX enable and disable within a DTX mode, DRX start offset (DRX start time point), DRX enable start time, DRX disable start time).
[0402] • Optionally, the DTX / DRX configuration or mode includes at least one cycle, such as including long cycles and / or short cycles.
[0403] • Optionally, the DTX / DRX cycle or mode may include at least one on / off configuration, such as a long on configuration / short off configuration, different on / off start times, or different on / off durations.
[0404] • Optionally, within a DTX / DRX cycle or mode, enable first, disable later.
[0405] • Instruct or request the network to switch cell states, or instruct or request the network to switch network states, specifically including at least one of the following: handover instruction, handover duration (start, duration, termination, at least one of the following).
[0406] • Instruct or request the network to enter DRX and / or DTX status. Specifically, this may include at least one of the following: DRX and / or DTX status indication, duration of DRX and / or DTX status (start, duration, termination, at least one).
[0407] • Requested network state mode. Optionally, the network state can be two or more, such as on / off, on / off / DRX / DTX, or low / medium / high load state.
[0408] The auxiliary information can be reported by the UE using at least one of the following: UL RRC message, MAC CE, or UCI. Optionally, the UL RRC message can be a dedicated RRC message or a UE auxiliary information message (such as a UEAssistanceInformation message).
[0409] The UE reports the auxiliary information and / or starts the auxiliary information reporting timer for the auxiliary information under at least one of the following conditions (optionally, the auxiliary information can only be reported if the timer is not running): the UE is instructed to report the auxiliary information; the UE characteristics change (such as service characteristic changes, UE preference changes (e.g., whether energy saving is required, whether energy saving needs are prioritized, whether performance needs are prioritized, etc.); the UE has not sent relevant auxiliary information (e.g., UEAssistanceInformation message) since it was configured to report; the current value is different from the value indicated in the last transmission of the relevant auxiliary information (e.g., UEAssistanceInformation message).
[0410] 2. The network receives auxiliary information reported by the UE.
[0411] 3. Optionally, the network may achieve network energy saving based on the auxiliary information reported by the UE, or select or instruct network energy saving technology or configuration.
[0412] Beneficial effects: The UE reporting auxiliary information ensures that transmission performance requirements are met while maintaining network energy efficiency. This embodiment can be used alone or in combination with other embodiments in this solution.
[0413] Example 2 (Data and / or signaling transmission for network configuration or network status) is implemented as follows (applicable to UL and / or DL): 1. The UE performs data and / or signaling transmissions based on network conditions. Specifically, this may include at least one of the following: 1) The UE performs data and / or signaling transmissions based on network configuration or network status information.
[0414] 2) The network status refers to the base station or cell status. Optionally, the cell status is the status of the UE's serving cell / Pcell / Pscell / neighboring cell, and the base station status is the status of the base station corresponding to the UE's serving cell / Pcell / Pscell / neighboring cell.
[0415] 3) Optionally, the network state can be two or more, such as on / off, on / off / DRX / DTX, or low, medium, and high load states.
[0416] 4) The UE is an R18 UE, or a UE with network energy saving purpose, or a UE that is instructed by the UE to report the auxiliary information, or a UE that has reported UE auxiliary information.
[0417] 5) The UE's performance of data and / or signaling transmission based on network status can be an action performed by the UE when NW is indicated or enabled. And / or, it can be an action performed by the UE when it reports auxiliary information (as in Example 1, where the UE has already reported auxiliary information).
[0418] 6) The UE performs data and / or signaling transmissions according to network conditions, including at least one of the following: • When the cell / base station is off, the UE does not perform data and / or signaling transmission, or transmits according to configuration X (enlarged configuration or interval), or transmits according to cell / gNB DRX / DTX.
[0419] • When the cell / base station is enabled, the UE performs data and / or signaling transmission, or performs data and / or signaling transmission according to the default configuration.
[0420] • When the UE is in the case of cell / base station DTX, it performs data and / or signaling reception if cell / base station DTX is enabled, and / or does not perform data and / or signaling reception or performs data and / or signaling reception according to configuration X (such as enlarged configuration or interval) if cell / base station DTX is disabled. Alternatively, when the UE is in the case of cell / base station DTX, it performs data and / or signaling reception using configuration X (such as enlarged configuration or interval).
[0421] performing data transmission at cell DTX on state or enlarge the datatransmission interval. • When the cell / base station DRX is enabled, the UE performs data and / or signaling transmission; and / or, when the cell / base station DRX is disabled, it does not perform data and / or signaling transmission or performs data and / or signaling transmission according to configuration X (such as enlarged configuration or interval). Alternatively, when the cell / base station DRX is enabled, the UE performs data and / or signaling reception using configuration X (such as enlarged configuration or interval).
[0422] performing data transmission at cell DRX on state or enlarge the datatransmission interval. 7) The data and / or signaling includes at least one of the following: public information / signaling, UE-specific information / signaling / data.
[0423] Optionally, the information includes at least one of the following: Synchronization Signal Block (SSB), SIB1, other SIB, Reference Signal (RS), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Downlink Data, Uplink Data, Random Access Channel (PRACH), Dynamic Scheduling Resource (DG), Semi-Persistent Scheduling (SPS), Configuration Grant (CG), and Scheduling Request (SR).
[0424] 2. Before or after the first step, the UE obtains the network status or updates the network status.
[0425] 1) Optionally, the network status may include at least one of the following: cell on / off indication, base station on / off indication, cell identifier, base station identifier, cell / gNB DTX indication, cell / gNB DRX indication, base station or cell on / off information (as in Example 1), base station or cell DRX / DTX configuration (as in Example 1).
[0426] 2) Optionally, the network status is an implicit network status, that is, the network indicates the energy-saving technology or configuration used, and the energy-saving technology will be configured with the corresponding network status.
[0427] For example, extended parameter configurations correspond to DTX / DRX status, or medium load status.
[0428] For example, it indicates that first information is transmitted according to a first configuration, either in DTX / DRX state or medium load state. The first information includes at least one of the following: Synchronization Signal Block (SSB), SIB1, other SIB, Reference Signal (RS), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Downlink Data, Uplink Data, Random Access Channel (PRACH), Dynamic Scheduling Resource (DG), Semi-Persistent Scheduling (SPS), Configuration Grant (CG), and Scheduling Request (SR).
[0429] For example, indicating that the first information is not transmitted is in the off state. The first information includes at least one of the following: Synchronization Signal Block (SSB), SIB1, other SIB, Reference Signal (RS), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Downlink Data, Uplink Data, Random Access Channel (PRACH), Dynamic Scheduling Resource (DG), Semi-Persistent Scheduling (SPS), Configuration Grant (CG), and Scheduling Request (SR).
[0430] 3) Optionally, the network state is an implicit network state, i.e., network indication of transmitted / sent / received information. The information includes at least one of the following: public information / signaling, UE-specific information / signaling / data.
[0431] Optionally, the information includes at least one of the following: Synchronization Signal Block (SSB), SIB1, other SIB, Reference Signal (RS), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Downlink Data, Uplink Data, Random Access Channel (PRACH), Dynamic Scheduling Resource (DG), Semi-Persistent Scheduling (SPS), Configuration Grant (CG), and Scheduling Request (SR).
[0432] Beneficial effects: The UE executes different transmission modes according to the network status, achieving the goal of network energy saving. This embodiment can be used alone or in combination with other embodiments in this solution, such as in combination with Embodiment 1.
[0433] Example 3 (Network configuration cell or base station DRX / DTX configuration): The specific implementation process is as follows (applicable to UL and / or DL): 1. Network configuration or instruction for cell / gNB DTX and / or DRX configuration. Specifically, this may include at least one of the following: 1) The cell / gNB DTX and / or DRX configuration is determined based on network status and / or service transmission requirements.
[0434] Optionally, the network status refers to the base station or cell status. Optionally, the cell status refers to the status of the UE's serving cell / Pcell / Pscell / neighboring cells, and the base station status refers to the status of the base station corresponding to the UE's serving cell / Pcell / Pscell / neighboring cells.
[0435] • Optionally, the network status can be two or more, such as on / off, on / off / DRX / DTX, or low, medium, and high load states.
[0436] 2) The cell / gNB DTX and / or DRX configuration is used for UE to transmit data and / or signaling.
[0437] Specifically, the data and / or signaling can be predefined, default, or network-indicated. Optionally, the data and / or signaling can be as described in the second step of this embodiment.
[0438] 3) The cell / gNB DTX and / or DRX configuration may include at least one of the following: • Cell or base station DTX indication, cell or base station DTX configuration (including at least one of the following: DTX period, DTX pattern, DTX enable information and / or DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable within a DTX period, the order of DTX enable and disable within a DTX pattern, DTX start offset (DTX start time point), DTX enable start time, DTX disable start time), cell or base station DRX indication, cell or base station DRX configuration (including at least one of the following: DRX period, DRX pattern, DRX enable information and / or DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable within a DTX period, the order of DRX enable and disable within a DTX pattern, DRX start offset (DRX start time point), DRX enable start time, DRX disable start time).
[0439] • Optionally, the DTX / DRX configuration or pattern includes at least one cycle, such as including long cycles and / or short cycles.
[0440] • Optionally, the DTX / DRX cycle or pattern may include at least one on / off configuration, such as a long on / off configuration, a short off configuration, different on / off start times, or different on / off durations.
[0441] • Optionally, within a DTX / DRX cycle or pattern, enable it first and disable it later (similar to the existing UE DRX configuration or usage).
[0442] 2. The UE performs data and / or signaling transmissions according to the configured or indicated cell / gNB DTX and / or DRX configuration.
[0443] 1) The UE is an R18 UE, or a UE with network energy saving purpose, or a UE that is instructed by the UE to report the auxiliary information, or a UE that has reported UE auxiliary information.
[0444] 2) The UE performs data and / or signaling transmission including at least one of the following: • When the UE is in the case of cell / base station DTX, it performs data and / or signaling reception if cell / base station DTX is enabled, and / or does not perform data and / or signaling reception or performs data and / or signaling reception according to configuration X (such as enlarged configuration or interval) if cell / base station DTX is disabled. Alternatively, when the UE is in the case of cell / base station DTX, it performs data and / or signaling reception using configuration X (such as enlarged configuration or interval).
[0445] · performing data transmission at cell DTX on state or enlarge the data transmission interval. • When the cell / base station DRX is enabled, the UE performs data and / or signaling transmission; and / or, when the cell / base station DRX is disabled, it does not perform data and / or signaling transmission or performs data and / or signaling transmission according to configuration X (such as enlarged configuration or interval). Alternatively, when the cell / base station DRX is enabled, the UE performs data and / or signaling reception using configuration X (such as enlarged configuration or interval).
[0446] · performing data transmission at cell DRX on state or enlarge the data transmission interval. The data and / or signaling include at least one of the following: public information / signaling, UE-specific information / signaling / data.
[0447] Optionally, the information includes at least one of the following: Synchronization Signal Block (SSB), SIB1, other SIB, Reference Signal (RS), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Downlink Data, Uplink Data, Random Access Channel (PRACH), Dynamic Scheduling Resource (DG), Semi-Persistent Scheduling (SPS), Configuration Grant (CG), and Scheduling Request (SR).
[0448] Optionally, the network may instruct the data and / or signaling to be affected by the cell / gNB DTX and / or DRX configuration. That is, only the default, network-instructed, or pre-configured data and / or signaling may be transmitted according to the DTX and / or DRX configuration or instructions.
[0449] 3) Optionally, the UE may also be indicated with network status, or updated network status.
[0450] Beneficial effects: By introducing DRX and / or DTX configurations for a network or cell, the UE performs transmissions based on these configurations, achieving network energy saving. This embodiment can be used alone or in combination with other embodiments in this solution, such as Embodiment 1 and Embodiment 2.
[0451] Example 4 (A method for BWP switch): Note: The method in this embodiment can also be applied to Pcell switching and Scell reactivation.
[0452] The specific implementation process is as follows: 1. The network explicitly or implicitly instructs the UE to perform a BWP handover through first information. Specifically, this may include at least one of the following: a) The instruction to the UE to perform a BWP handover can also be an instruction to the UE to switch from the first BWP to the second BWP.
[0453] b) The switched BWP, or the second BWP, is the default BWP, or the previous BWP (e.g., the BWP before switching to the first BWP, such as the BWP before the BWP switching indication, such as the BWP used when or under the circumstances of receiving the first information and / or the second information), or a specific BWP (e.g., at least one of the following: network energy-saving BWP, non-energy-saving BWP, BWP with a specific identifier such as the BWP index, initial BWP), or the BWP indicated in the first information, or the BWP indicated by the second information (e.g., the first information is carried in the group information (e.g., group RNTI, group DCI, group MAC CE), and the second information is carried in the SIB, or the first information is carried in the SIB, and the second information is carried in the group information (e.g., group RNTI, group DCI, group MAC CE)).
[0454] c) The first information may include at least one of the following: BWP handover indication; network status indication or network status change; BWP identifier after handover; network load status; whether to prioritize network energy saving or transmission performance. d) The first information is received through the common search space, or through the UE-specific search space, or through a specific search space (configured by the network, or predefined. Alternatively, the common search space and / or UE-specific search space can be shared, or they can be configured independently).
[0455] For example, all signals are received through the common search space. For example, all signals are received through the terminal-specific search space. For example, all signals are received through a specific search space. For example, when the network load is low or no load, or when the network state is in the first state (e.g., no load, low load, base station or cell DRX, base station or cell DTX, energy-saving state, etc.), or when the UE obtains a low or no load network condition, or when the UE obtains a first state network condition (e.g., no load, low load, base station or cell DRX, base station or cell DTX, energy-saving state, etc.), signals are received through the common search space, or through a specific search space. For example, when the network load is high, or when the network state is in the second state (e.g., high load, non-energy-saving state, etc.), or during normal transmission, or when the UE obtains a high network load, or when the UE obtains a second state network condition (e.g., high load, non-energy-saving state, etc.), or when the UE obtains normal transmission, signals are received through the terminal-specific search space, or through a specific search space. For example, the UE cuts off to the BWP to be switched to based on the BWP information indicated by the network in the first and / or second information (such as the BWP index indicated by the network). For example, when the network load is low or no load, or when the network state is in the first state (such as no load, low load, base station or cell DRX, base station or cell DTX, power saving state, etc.), or when the UE obtains that the network load is low or no load, or when the UE obtains that the network state is in the first state (such as no load, low load, base station or cell DRX, base station or cell DTX, power saving state, etc.), or when the UE is instructed to perform a BWP handover (if there is a BWP handover indication bit, which may or may not be given a BWP index), the UE switches to BWP A. The BWP A can be at least one of the following: a default BWP (e.g., default BWP 1, predefined, or indicated by the network via SIB), a specific BWP (e.g., at least one of the following: a network-efficient BWP, a BWP with a specific identifier such as a BWP index (e.g., the smallest index, such as index 0), an initial BWP), a low-bandwidth BWP, a previous BWP (e.g., the first BWP, or the BWP used when the BWP handover indication or first information indication was received, or the BWP used before the currently used or activated BWP), or a high-bandwidth BWP. For example, if the network indicates which BWP each UE switches to, there are issues with handover latency and network overhead. Allowing the UE to autonomously switch to its original BWP can solve this problem.
[0456] ·For example: if the gNB knows the no / small traffic load, the gNB couldswitch all or most UEs to the same bandwidth part with a small bandwidth.Such BWP switch can be indicated to the UE via one group common DCI. a) UE can switch to the BWP indicated by network, or, UE canautonomously switch to the initial BWP, or, the index M BWP, or, the BWP defined for energy saving. For example, when the network load is high, or the network status is in the second state (such as high load, or non-energy saving state, etc.), or normal transmission, or when the UE obtains that the network load is high, or the UE obtains that the network status is in the second state (such as high load, non-energy saving state, etc.), or the UE obtains that normal transmission, or when instructing the UE to perform BWP handover (if there is a BWP handover indication bit, the BWP index may or may not be given), the UE switches to BWP B. The BWP can be at least one of the following: a default BWP (e.g., default BWP 2, predefined, or indicated by the network via SIB), a specific BWP (e.g., at least one of the following: a non-network energy-saving BWP, a BWP with a non-specific identifier such as a BWP index (e.g., an index other than 0 or the smallest), a BWP with a specific identifier such as a BWP index (e.g., the largest index), a non-initial BWP), a previous BWP (e.g., a BWP before switching to the first BWP, or, as the first BWP, or, as the BWP used when the BWP handover indication or first information indication is received, or, as the BWP used before the currently used or active BWP), or a high-bandwidth BWP. For example, if the network indicates which BWP each UE switches to, there are issues with handover latency and network overhead. Allowing the UE to autonomously switch to its original BWP can solve this problem.
[0457] ·For example: if the network traffic load changes to larger, the activatedBWP for each UE can be adapted accordingly. For example, the UE canautonomous switch to the previous BWP (when the BWP switch indication isreceived) or the UE switches to the BWP with large bandwidth which isexplicitly indicated by the network. e) The UE is either a UE that accesses the current cell, or a UE that camps in the current cell, or a UE that is configured / indicated to a specific group, or a UE that has network energy-saving capabilities, or a UE that has reported network energy-saving capabilities or requirements.
[0458] f) The first information may also include at least one of the following: switching time or switching delay offset.
[0459] g) Optionally, the first information may also be carried via SIB, or carried within the first information. The first information may be a DCI scrambled by a group DCI or a DCI scrambled by a group RNTI, or a PDSCH scheduled by a DCI scrambled by a group DCI or a DCI scrambled by a group RNTI (e.g., in a RAR manner).
[0460] For example, a MAC PDU carries one or more MAC sub-PDUs, and each MAC sub-PDU corresponds to a UE-specific piece of information.
[0461] For example, a MAC PDU carries one or more MAC sub-PDUs, and each MAC sub-PDU corresponds to information about a UE group.
[0462] For example, a MAC PDU carries one or more MAC sub-PDUs, and each MAC sub-PDU corresponds to cell-level information.
[0463] 2. The UE performs a BWP handover. Optionally, there are two options: a) Option 1: Upon receiving the first message, the terminal performs a BWP handover; b) Option 2: When the terminal receives the first information, BWP handover is performed at the indicated handover time, or at the time of receiving / decoding the first information plus the offset.
[0464] Beneficial effects: This invention introduces a BWP switching method for different network loads. Alternatively, it provides a unified or specific BWP switching method depending on whether network energy saving is required. This embodiment can be used alone or in combination with other embodiments in this solution, such as Embodiment 1.
[0465] Example 5 (Methods for using DRX, or methods for changing or using DRX parameters): The specific implementation process is as follows (applicable to UL and / or DL): 1. Configure DRX parameters or settings in the network.
[0466] a) The DRX parameters or configurations mentioned are for the UE (not for the cell).
[0467] 2. The UE receives the DRX parameters or configuration from the network and performs DRX sending or receiving.
[0468] 3. The UE executes updated DRX parameters or configurations based on network indication information, or performs transmissions based on the updated DRX parameters or configurations. Specifically, this may include at least one of the following: a) The DRX parameters or configurations mentioned may be all or part of the existing DRX parameters, or all or part of the DRX parameters newly added in subsequent versions.
[0469] b) For example, the network may configure multiple sets of DRX parameters or configurations, corresponding to different indices. The UE performs data transmission based on the values of the DRX parameters or configurations corresponding to the indices indicated by the network.
[0470] i. Specifically, the multiple sets of DRX parameters or configurations are divided into two sets, and the UE can switch directly between the two sets (e.g., as long as a DRX parameter or configuration switching instruction is received, or an update instruction on network status, network load, or whether energy saving is required is received, the UE can switch between the two sets).
[0471] ii. For example, use DRX parameters or configurations with short on-duration or long periods in energy-saving scenarios. For example, use DRX parameters or configurations with long on-duration or short periods in non-energy-saving scenarios.
[0472] c) For example, the network may be configured with multiple sets of DRX parameters or configurations, each corresponding to different network states, network loads, or energy-saving requirements. The UE determines the DRX parameters or configuration to use based on the network state, network load, or energy-saving requirements indicated by the network, and then performs data transmission.
[0473] d) For example, the network is configured with a set of DRX parameters or configurations that correspond to network status (e.g., low load, power saving, cellDRX / DTX, etc.) or network load (e.g., low, none, etc.) or power saving requirements. The UE determines whether to use the DRX parameters or configurations based on the network status or network load indicated by the network, or whether power saving is required, and then performs data transmission.
[0474] e) For example, the network indicates updates to DRX parameters or configurations at the cell or UE group level via the contents of the common DCI, common MAC CE, system information, or PDSCH carried in the common DCI. The UE then performs transmissions using the updated configuration based on these updates.
[0475] Beneficial effects: This invention introduces a method for using or updating DRX parameters based on energy-saving needs or network status. While achieving network energy savings, it can also reduce complexity or latency. This embodiment can be used alone or in combination with other embodiments in this solution, such as Embodiment 1.
[0476] Example 6 (UE group or cell-level handover implementation method): The specific implementation process is as follows: 1. The base station switches the UE(s) to a second cell via group handover or cell-level handover. Specifically, this may include at least one of the following: a) For example, when the current serving cell is off, or when energy is being saved, or when the network is under low or no load, the UE is switched to a second cell.
[0477] b) Parameters or configurations for group handover or cell-level handover include common and / or UE-specific components. Optional, i. The common portion is carried in the SIB. Alternatively, the common portion is carried in the first information, and the terminal-specific portion is carried in the second information. Alternatively, it is carried together with the terminal-specific portion in the first information. The first information may be a DCI scrambled by a group DCI or a group RNTI, or a PDSCH (e.g., in a RAR manner) scheduled by a DCI scrambled by a group DCI or a group RNTI. The second information is a PDSCH (e.g., in a RAR manner) scheduled by a DCI scrambled by a group DCI or a group RNTI.
[0478] For example, a MAC PDU may carry one or more MAC sub-PDUs, each corresponding to terminal-specific information. Optionally, a MAC PDU may also carry one or more MAC sub-PDUs carrying common information.
[0479] • Optionally, the terminal-specific information may be specific to each UE or to a UE at a specific location (such as different locations or different coordinate ranges).
[0480] • Optional, public information, which can be for all UEs under a cell, for a UE at a specific location, or for a group of UEs.
[0481] a) For example, public is for the cell, while terminal-specific is for a UE at a specific location.
[0482] b) For example, public is for a group of UEs, while terminal-specific is for a specific UE.
[0483] c) For example, public is for a cell, while terminal-specific is for a specific UE group.
[0484] 2. The UE performs a handover based on the handover information.
[0485] Beneficial effects: This paper presents a group switching method for network energy saving, which achieves energy saving while reducing latency / overhead.
[0486] The energy-saving methods provided in the above embodiments can be used individually to achieve network energy saving, or they can be used in combination to achieve network energy saving.
[0487] Figure 25 An exemplary embodiment of this application provides an energy-saving device. Taking the device as an example of its application in a terminal, the device includes at least some of the following modules: a first processing module 2410, a first transmitting module 2412, and a first receiving module 2414. The first sending module 2412 is used to execute the sending-related steps performed on the terminal side in the above embodiments; the first receiving module 2414 is used to execute the receiving-related steps performed on the terminal side in the above embodiments; the first processing module 2410 is used to execute the sending, receiving, and processing-related steps performed on the terminal side in the above embodiments, wherein the processing includes all or part of data processing related to the sending step, data processing related to the receiving step, and other data processing unrelated to sending and receiving. Further details will not be elaborated here.
[0488] The steps performed by the device provided in this embodiment can be referred to the above method embodiment.
[0489] In summary, the device provided in this embodiment achieves network energy saving by performing operations related to network energy saving. Because it supports performing network energy saving-related operations under various scenarios and requirements, the flexibility, reliability, and efficiency of network energy saving are greatly improved.
[0490] Figure 26 An exemplary embodiment of this application provides an energy-saving device. Taking the device as an example of its application in a network, the device includes at least some of the modules selected from the second processing module 2510, the second receiving module 2512, and the second transmitting module 2514. The second sending module 2514 is used to execute the sending-related steps performed on the network side in the above embodiments; the second receiving module 2512 is used to execute the receiving-related steps performed on the network side in the above embodiments; the second processing module 2510 is used to execute the sending, receiving, and processing-related steps performed on the network side in the above embodiments, the processing including all or part of data processing related to the sending step, data processing related to the receiving step, and other data processing unrelated to sending and receiving. Further details will not be elaborated here.
[0491] The steps performed by the device provided in this embodiment can be referred to the above method embodiment.
[0492] In summary, the device provided in this embodiment achieves network energy saving by performing operations related to network energy saving. Because it supports performing network energy saving-related operations under various scenarios and requirements, the flexibility, reliability, and efficiency of network energy saving are greatly improved.
[0493] It should be noted that the device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0494] Regarding the apparatus in this embodiment, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
[0495] Figure 27 The diagram shows a schematic of the structure of an energy-saving device (terminal or network device) provided in an exemplary embodiment of this application. The energy-saving device 2600 includes: a processor 2601, a receiver 2602, a transmitter 2603, a memory 2604, and a bus 2605.
[0496] The processor 2601 includes one or more processing cores. The processor 2601 executes various functional applications and information processing by running software programs and modules. In some embodiments, the processor 2601 can be used to implement the functions and steps of the first processing module 2410 and / or the second processing module 2510 described above.
[0497] Receiver 2602 and transmitter 2603 can be implemented as a communication component, which can be a communication chip. In some embodiments, receiver 2602 can be used to implement the functions and steps of the first receiving module 2414 and / or the second receiving module 2512 as described above. In some embodiments, transmitter 2603 can be used to implement the functions and steps of the first transmitting module 2412 and / or the second transmitting module 2514 as described above.
[0498] The memory 2604 is connected to the processor 2601 via a bus 2605. The memory 2604 can be used to store at least one instruction, which the processor 2601 uses to execute to implement the various steps in the above method embodiments.
[0499] Furthermore, the memory 2604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random-access memory (SRAM), read-only memory (ROM), magnetic storage, flash memory, and programmable read-only memory (PROM).
[0500] In some embodiments, the receiver 2602 independently receives signals / data, or the processor 2601 controls the receiver 2602 to receive signals / data, or the processor 2601 requests the receiver 2602 to receive signals / data, or the processor 2601 cooperates with the receiver 2602 to receive signals / data.
[0501] In some embodiments, the transmitter 2603 independently transmits signals / data, or the processor 2601 controls the transmitter 2603 to transmit signals / data, or the processor 2601 requests the transmitter 2603 to transmit signals / data, or the processor 2601 cooperates with the transmitter 2603 to transmit signals / data.
[0502] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores an executable program that is loaded and executed by a processor of a communication device to implement the energy-saving method as described above.
[0503] In an exemplary embodiment, a chip is also provided, which includes programmable logic circuitry or a program, and a communication device on which the chip is mounted is used to implement the energy-saving method as described above.
[0504] In an exemplary embodiment, a computer program product is also provided, which includes a computer program stored in a computer-readable storage medium. A processor of a communication device reads the computer program from the computer-readable storage medium and executes the computer program, causing the communication device to perform the energy-saving method as described above.
[0505] The above embodiments can be used individually or in combination freely.
[0506] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.
[0507] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. An energy-saving method, characterized in that, The method is executed by a terminal, and the method includes: Perform operations related to network energy saving.
2. The method according to claim 1, characterized in that, The operations related to network energy saving include: The network reports auxiliary information, which is used to assist in achieving network energy saving.
3. The method according to claim 2, characterized in that, The auxiliary information includes at least one of the following: Recommended network activation information; Recommended network shutdown information; Recommended network DTX information; Recommended network DRX information; Recommended terminal DTX information; Recommended terminal DRX information; Recommended data transmission interval; Preferred network configuration parameters.
4. The method according to claim 3, characterized in that, The recommended network activation information includes at least one of the following: the network activation instruction request, the duration of the network activation, the start time of the network activation, the end time of the network activation, the activation cycle of the network activation, and the order of the network activation and deactivation. The recommended network shutdown information includes at least one of the following: the network shutdown instruction request, the duration of the network shutdown, the start time of the network shutdown, the end time of the network shutdown, the shutdown period of the network shutdown, and the order of the network opening and closing. The recommended network DTX information includes at least one of: network DTX indication and network DTX configuration; The recommended network DRX information includes at least one of: network DRX indication and network DRX configuration; The recommended terminal DTX information includes at least one of: terminal DTX indication and terminal DTX configuration; The recommended terminal DRX information includes at least one of: terminal DRX indication and terminal DRX configuration; The transmission interval includes a time slot interval; The network configuration parameters include at least one of the following: Configuration Grant CG configuration parameters, Semi-Static Scheduling SPS configuration parameters, Physical Uplink Control Channel (PUCCH) configuration parameters, Physical Uplink Shared Channel (PUSCH) configuration parameters, Master Information Block (MIB) configuration parameters, System Information Block (SIB) configuration parameters, Physical Downlink Shared Channel (PDSCH) configuration parameters, Physical Downlink Control Channel (PDCCH) configuration parameters, Scheduling Request (SR) configuration parameters, Physical Random Access Channel (PRACH) configuration parameters, Random Access Channel (RACH) configuration parameters, Discontinuous Receive (DRX) configuration parameters, Discontinuous Transmit (DTX) configuration parameters, Reference Signal configuration parameters, Search Space configuration parameters, Dynamic Grant (DG) configuration parameters, and Synchronization Signal Block (SSB) configuration parameters.
5. The method according to claim 4, characterized in that, The recommended terminal DRX information includes at least one of the following: UE identifier, terminal DRX request, terminal DRX indication, and terminal DRX configuration recommendation; The recommended configuration of the terminal DRX includes at least one of the following: DRX cycle, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and DRX disable in a DRX cycle, the order of DRX enable and DRX disable in a DRX mode, DRX start offset, DRX enable start time, and DRX disable start time. The terminal DRX configuration or the DRX mode includes at least one cycle, the at least one cycle including: a long cycle and / or a short cycle.
6. The method according to any one of claims 2 to 5, characterized in that, The auxiliary information is carried in the RRC message; The reporting of auxiliary information to the network includes: If a first condition is met, auxiliary information is reported to the network; the first condition includes at least one of the following: The terminal is instructed to report the auxiliary information; The terminal's preference change includes at least one of the network configuration parameters of the preference and recommended information.
7. The method according to any one of claims 1 to 6, characterized in that, The operations related to network energy saving include: According to the network configuration, data transmission and / or signaling transmission and / or system information transmission are performed; at least one of the network configurations is related to network energy saving. Alternatively, depending on the network status, data transmission and / or signaling transmission and / or system information transmission may be performed, wherein at least one of the network statuses is related to the network energy saving; Alternatively, based on changes in network status, data transmission and / or signaling transmission and / or system information transmission may be performed, where at least one of the network statuses before and after the change is related to the network energy saving.
8. The method according to claim 7, characterized in that, The network status includes the cell status; The cell status includes at least one of the following: the status of the serving cell of the terminal, the status of the primary cell of the terminal, the status of the primary and secondary cells of the terminal, the status of the neighboring cells of the terminal, the status of the cells of the neighboring base stations of the base station, and the status of the cells of the base stations in the ANR list.
9. The method according to claim 7, characterized in that, The network status includes at least one of the following: network DRX status and network DTX status.
10. The method according to claim 7, characterized in that, The step of performing data transmission and / or signaling transmission and / or system information transmission according to network status includes: When the terminal is instructed by the network, data transmission and / or signaling transmission and / or system information transmission are performed according to the network status. When the terminal reports auxiliary information, data transmission and / or signaling transmission and / or system information transmission are performed according to the network status.
11. The method according to claim 10, characterized in that, When the network instructs the terminal, performing data transmission and / or signaling transmission and / or system information transmission according to the network status includes: When the network indicates a network status or a status change to the terminal, data transmission and / or signaling transmission and / or system information transmission shall be performed according to the network status or network status change indication.
12. The method according to claim 7, characterized in that, The step of performing data transmission and / or signaling transmission and / or system information transmission based on network status includes at least one of the following: When the network is shut down, data transmission and / or signaling transmission and / or system information transmission shall not be performed; When the network is off, perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; When the network is shut down, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the DTX / DRX configuration of the network; When the network is enabled, perform data transmission and / or signaling transmission and / or system information transmission; With the network enabled, data transmission and / or signaling transmission and / or system information transmission are performed according to the default configuration. With network DTX enabled, perform data transmission and / or signaling transmission and / or system information transmission; When network DTX is disabled, data transmission and / or signaling transmission and / or system information transmission are not performed; With network DTX disabled, data transmission and / or signaling transmission and / or system information transmission shall be performed according to the first configuration; In the case of network DTX, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; When network DRX is enabled, data transmission and / or signaling transmission and / or system information transmission are performed; When network DRX is disabled, data transmission and / or signaling transmission and / or system information transmission are not performed; With network DRX disabled, data transmission and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; In the case of network DRX, data and / or signaling transmission and / or system information transmission shall be performed in accordance with the first configuration; Wherein, the first configuration is a configuration related to network energy saving, or the first configuration is a configuration with an extended interval compared to the default configuration.
13. The method according to any one of claims 1 to 12, characterized in that, The operations related to network energy saving include: Based on network DTX configuration and / or network DRX configuration, perform data transmission and / or signaling transmission and / or system information transmission; Wherein, at least one of the network DTX configuration and / or network DRX configuration is related to the network energy saving; The network DTX configuration and / or network DRX configuration are determined based on the network status. And / or, The network DTX configuration and / or network DRX configuration are determined based on service transmission requirements.
14. The method according to any one of claims 7 or 10 to 13, characterized in that, The data and / or signaling and / or system information are default, network-indicated, or pre-configured.
15. The method according to claim 13, characterized in that, The network DTX configuration includes at least one of the following: network DTX indication, Network DTX configuration parameters; The network DRX configuration includes at least one of the following: network DRX indication, Network DRX configuration parameters; The configuration parameters of the network DTX include at least one of the following: DTX period, DTX mode, DTX enable information, DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable in a DTX period, the order of DTX enable and disable in a DTX mode, DTX start offset, DTX enable start time, DTX disable start offset, and DTX disable start time. The configuration parameters of the network DRX include at least one of the following: DRX period, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order in which DRX is enabled and disabled in a DRX period, the order in which DRX is enabled and disabled in a DRX mode, DRX start offset, DRX enable start time, DRX disable start offset, and DRX disable start time.
16. The method according to any one of claims 7 to 15, characterized in that, The data and / or signaling and / or system information includes at least one of the following: Public information or signaling; terminal-specific information, signaling, or data; The public information or signaling includes at least one of the following: Synchronization Signal Block (SSB), Master Information Block (MIB), System Information Block (SIB1), other SIBs, Common Reference Signal (RS), and Random Access Channel (PRACH). The terminal-specific information, signaling, or data includes at least one of the following: terminal-specific reference signal, physical downlink control channel (PDCCH), physical uplink control channel (PUCCH), downlink data, uplink data, dynamic scheduling resource (DG), semi-persistent scheduling (SPS), configuration authorization (CG), and scheduling request (SR).
17. The method according to any one of claims 1 to 16, characterized in that, The operations related to network energy saving include: Perform cell handover based on cell handover information; The cell handover information refers to terminal group handover information or cell-level handover information.
18. The method according to claim 17, characterized in that, The cell handover information includes handover parameters or configurations, which include: a common part and / or a terminal-specific part; The common part is carried in the SIB or the first downlink information, the terminal-specific part is carried in the second downlink information, or both the common part and the terminal-specific part are carried in the first downlink information; The first downlink information includes at least one of the following: Group Downlink Control Information (DCI); Group wireless network temporary identifier RNTI scrambled DCI; Physical downlink shared channel (PDSCH) scheduled by DCI with RNTI scrambling; PDSCH for group DCI scheduling; Public PDSCH; The second downlink information includes at least one of the following: Group DCI; DCI with RNTI scrambling; PDSCH of DCI scheduling with RNTI scrambling; Public PDSCH.
19. The method according to any one of claims 1 to 18, characterized in that, The terminal includes: Connected terminal.
20. An energy-saving method, characterized in that, The method is executed by a network, and the method includes: Perform operations related to network energy saving.
21. The method according to claim 20, characterized in that, The operations related to network energy saving include: The system receives auxiliary information reported by the terminal, which is used to assist in achieving network energy saving.
22. The method according to claim 21, characterized in that, The auxiliary information includes at least one of the following: Recommended network activation information; Recommended network shutdown information; Recommended network DTX information; Recommended network DRX information; Recommended terminal DTX information; Recommended terminal DRX information; Recommended data transmission interval; Preferred network configuration parameters.
23. The method according to claim 22, characterized in that, The recommended network activation information includes at least one of the following: the network activation instruction request, the duration of the network activation, the start time of the network activation, the end time of the network activation, the activation cycle of the network activation, and the order of the network activation and deactivation. The recommended network shutdown information includes at least one of the following: the network shutdown instruction request, the duration of the network shutdown, the start time of the network shutdown, the end time of the network shutdown, the shutdown period of the network shutdown, and the order of the network opening and closing. The recommended network DTX information includes at least one of: network DTX indication and network DTX configuration; The recommended network DRX information includes at least one of: network DRX indication and network DRX configuration; The recommended terminal DTX information includes at least one of: terminal DTX indication and terminal DTX configuration; The recommended terminal DRX information includes at least one of: terminal DRX indication and terminal DRX configuration; The transmission interval includes a time slot interval; The network configuration parameters include at least one of the following: Configuration Grant CG configuration parameters, Semi-Static Scheduling SPS configuration parameters, Physical Uplink Control Channel (PUCCH) configuration parameters, Physical Uplink Shared Channel (PUSCH) configuration parameters, Master Information Block (MIB) configuration parameters, System Information Block (SIB) configuration parameters, Physical Downlink Shared Channel (PDSCH) configuration parameters, Physical Downlink Control Channel (PDCCH) configuration parameters, Scheduling Request (SR) configuration parameters, Physical Random Access Channel (PRACH) configuration parameters, Random Access Channel (RACH) configuration parameters, Discontinuous Receive (DRX) configuration parameters, Discontinuous Transmit (DTX) configuration parameters, Reference Signal configuration parameters, Search Space configuration parameters, Dynamic Grant (DG) configuration parameters, and Synchronization Signal Block (SSB) configuration parameters.
24. The method according to claim 23, characterized in that, The recommended network DRX information includes at least one of the following: cell identifier, base station identifier, network DRX indication, and network DRX configuration. The network DRX configuration includes at least one of the following: DRX period, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order of DRX enable and disable in a DRX period, the order of DRX enable and disable in a DRX mode, DRX start offset, DRX enable start time, and DRX disable start time. The network DRX configuration or the DRX mode includes at least one cycle, the at least one cycle including: a long cycle and / or a short cycle.
25. The method according to any one of claims 21 to 23, characterized in that, The auxiliary information is carried in the RRC message.
26. The method according to any one of claims 20 to 25, characterized in that, The operations related to network energy saving include: Based on the network configuration, data transmission and / or signaling transmission and / or system information transmission are performed; at least one of the network configurations is related to network energy saving. Alternatively, based on the network state, data transmission and / or signaling transmission and / or system information transmission may be performed, wherein at least one of the network states is related to network energy saving; Alternatively, based on the network state change, data transmission and / or signaling transmission and / or system information transmission may be performed, where at least one of the network states before and after the change is related to the network energy saving.
27. The method according to claim 26, characterized in that, The network status includes the cell status; The cell status includes at least one of the following: the status of the serving cell of the terminal, the status of the primary cell of the terminal, the status of the primary and secondary cells of the terminal, the status of the neighboring cells of the terminal, the status of the cells of the neighboring base stations of the base station, and the status of the cells of the base stations in the ANR list.
28. The method according to claim 27, characterized in that, The network status includes at least one of the following: network DRX status and network DTX status.
29. The method according to claim 28, characterized in that, The process of performing data transmission and / or signaling transmission and / or system information transmission based on network status includes: When the terminal is instructed, data transmission and / or signaling transmission and / or system information transmission are performed based on the network status; When the terminal reports auxiliary information, the network status is sent, and data transmission and / or signaling transmission and / or system information transmission are performed.
30. The method according to claim 29, characterized in that, The step of performing data transmission and / or signaling transmission and / or system information transmission based on the network state when instructing the terminal includes: Indicate the network state or a change in the network state to the terminal so that data transmission and / or signaling transmission and / or system information transmission can be performed based on the network state or the change in the network state.
31. The method according to claim 26, characterized in that, The step of instructing the terminal on the network state or a change in the network state, so as to perform data transmission and / or signaling transmission and / or system information transmission based on the network state or the change in the network state, includes at least one of the following: Send the network off status to the terminal and indicate that no data transmission and / or signaling transmission and / or system information transmission will be performed; Send the network off status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; Send the network off status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the DTX / DRX configuration of the network; Send the network enabled status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission; Send the network enabled status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the default configuration; Send the network DTX enabled status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission; Send the network DTX status to the terminal, and indicate that no data transmission and / or signaling transmission and / or system information transmission will be performed; Send the network DTX off status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; Send the network DTX status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; Send the network DRX enabled status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission; Send the network DRX status to the terminal, and indicate that no data transmission and / or signaling transmission and / or system information transmission will be performed; Send the network DRX off status to the terminal, and perform data transmission and / or signaling transmission and / or system information transmission according to the first configuration; Send the network DRX status to the terminal, and perform data and / or signaling transmission and / or system information transmission according to the first configuration; Wherein, the first configuration is a configuration related to network energy saving, or the first configuration is a configuration with an extended interval compared to the default configuration.
32. The method according to any one of claims 20 to 31, characterized in that, The operations related to network energy saving include: Send network DTX configuration and / or network DRX configuration so that the terminal can perform data transmission and / or signaling transmission and / or system information transmission based on the network DTX configuration and / or network DRX configuration; At least one of the network DTX configuration and / or network DRX configuration is related to the network energy saving; The network DTX configuration and / or network DRX configuration are determined based on the network status. And / or, the network DTX configuration and / or network DRX configuration are determined based on service transmission requirements.
33. The method according to any one of claims 26 or 29 to 32, characterized in that, The data and / or the signaling and / or the system information are default, network-indicated, or pre-configured.
34. The method according to claim 32, characterized in that, The network DTX configuration includes at least one of the following: Network DTX indicator, Network DTX configuration parameters; The network DRX configuration includes at least one of the following: Network DRX instructions Network DRX configuration parameters; The configuration parameters of the network DTX include at least one of the following: DTX period, DTX mode, DTX enable information, DTX disable information, DTX enable duration, DTX disable duration, the order of DTX enable and disable in a DTX period, the order of DTX enable and disable in a DTX mode, DTX start offset, DTX enable start time, DTX disable start offset, and DTX disable start time. The configuration parameters of the network DRX include at least one of the following: DRX period, DRX mode, DRX enable information, DRX disable information, DRX enable duration, DRX disable duration, the order in which DRX is enabled and disabled in a DRX period, the order in which DRX is enabled and disabled in a DRX mode, DRX start offset, DRX enable start time, DRX disable start offset, and DRX disable start time.
35. The method according to any one of claims 26 to 34, characterized in that, The data and / or signaling and / or system information includes at least one of the following: Public information or signaling; Terminal-specific information, signaling, or data; The public information or signaling includes at least one of the following: Synchronization Signal Block (SSB), Master Information Block (MIB), System Information Block (SIB1), other SIBs, Common Reference Signal (RS), and Random Access Channel (PRACH). The terminal-specific information, signaling, or data includes at least one of the following: terminal-specific reference signal, physical downlink control channel (PDCCH), physical uplink control channel (PUCCH), downlink data, uplink data, dynamic scheduling resource (DG), semi-persistent scheduling (SPS), configuration authorization (CG), and scheduling request (SR).
36. The method according to any one of claims 20 to 35, characterized in that, The operations related to network energy saving include: Send cell handover information, which is terminal group handover information or cell level handover information.
37. The method according to claim 36, characterized in that, The cell handover information includes handover parameters or configurations, which include: a common part and / or a terminal-specific part; The common portion is carried in the SIB or the first downlink information, and the terminal-specific portion is carried in the second downlink information; Alternatively, both the common portion and the terminal-specific portion may be carried in the first downlink information; The first downlink information includes at least one of the following: Group Downlink Control Information (DCI); Group wireless network temporary identifier RNTI scrambled DCI; Physical downlink shared channel (PDSCH) scheduled by DCI with RNTI scrambling; PDSCH for group DCI scheduling; Public PDSCH; The second downlink information includes at least one of the following: Group DCI; DCI with RNTI scrambling; PDSCH of DCI scheduling with RNTI scrambling; Public PDSCH.
38. The method according to any one of claims 20 to 37, characterized in that, The terminal includes: Connected terminal.
39. An energy-saving device, characterized in that, The device includes: The first processing module is used to perform operations related to network energy saving.
40. An energy-saving device, characterized in that, The device includes: The second processing module is used to perform operations related to network energy saving.
41. A terminal, characterized in that, The terminal includes: processor; A transceiver connected to the processor; Memory for storing the executable program of the processor; The processor is configured to load and execute the executable program to implement the energy-saving method as described in any one of claims 1 to 19.
42. A network device, characterized in that, The network device includes: processor; A transceiver connected to the processor; Memory for storing the executable program of the processor; The processor is configured to load and execute the executable program to implement the energy-saving method as described in any one of claims 20 to 38.
43. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an executable program, which is loaded and executed by the processor of the communication device to implement the energy-saving method as described in any one of claims 1 to 19, or the energy-saving method as described in any one of claims 20 to 38.
44. A chip, characterized in that, The chip includes a programmable logic circuit or a program, and the communication device on which the chip is installed is used to implement the energy-saving method as described in any one of claims 1 to 19, or the energy-saving method as described in any one of claims 20 to 38.
45. A computer program product, characterized in that, The computer program product includes a computer program stored in a computer-readable storage medium, a processor of the communication device reads the computer program from the computer-readable storage medium, and the processor executes the computer program to cause the communication device to perform the energy-saving method as described in any one of claims 1 to 19, or the energy-saving method as described in any one of claims 20 to 38.