Apparatus, device and method for network management

Abstract

Various aspects of the present disclosure provide apparatuses, devices, and methods for network management in various network systems to reduce power consumption of apparatuses and / or devices on the network side. A network device can receive, from a serving cell, configuration information for configuring the network device to determine whether to transmit a report indicating that a power consumption event has occurred. The network device can determine, based on the configuration information, whether one or more conditions indicating that the power consumption event has occurred are satisfied. When the one or more conditions indicating that the power consumption event has occurred are satisfied, the network device can transmit the report to the serving cell.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more particularly to apparatus, devices, and methods for network management. Background Technology

[0002] In wireless communication systems such as Fourth Generation (4G) Long-Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR), power-saving or power management functions have been implemented at the user equipment (UE) level. For example, discontinuous reception (DRX) and discontinuous transmission (DTX) are used to achieve power saving or management of the UE, such as extending its battery life.

[0003] However, for network-side devices (e.g., transmission and receive points, TRPs), there are no standard functions equivalent to DRX or DTX modes. Therefore, power saving or power management is typically not implemented on network-side devices. In fact, power saving or power management is not the most important consideration for network-side devices in wireless communication systems.

[0004] However, energy conservation or power management on the network side is gaining importance, for example, in many countries, especially those facing rising energy costs, the need to achieve carbon neutrality is growing. Given that many countries have already committed to carbon neutrality, many network operators now need to implement energy conservation or power management on the network side. According to a recent report by the Global System for Mobile Communications Association (GSMA), radio access network (RAN) energy consumption accounts for approximately 23% of network operators' operational expenditures (OPEX).

[0005] Therefore, there is a need to deploy new devices and methods for network management in various communication networks (e.g., Sixth Generation, 6G), especially in terms of energy saving and / or power management of network-side devices. Summary of the Invention

[0006] In wireless communication systems (e.g., Fourth Generation (4G) Long-Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR)), discontinuous reception (DRX) and discontinuous transmission (DTX) are used for power saving or management on the user equipment (UE) side. However, there are no standards for power saving or management on the network side. Existing network-side power saving and management methods are only applicable to one or more specific networks. However, such network-specific power saving and management presents difficulties in management, maintenance, and expansion, and may therefore be less than ideal. Instead, a standardized approach to power saving and / or network management may be needed. Standardized approaches to power saving and / or network management are likely easier to manage, maintain, and expand compared to network-specific power saving and management.

[0007] Various aspects of this disclosure provide methods, apparatuses, systems, and devices for overcoming the aforementioned disadvantages, as well as specific methods for network management in various network systems.

[0008] According to some aspects of this disclosure, a method for network management is provided, comprising: a first network device receiving configuration information from a second network device, wherein the configuration information is used to configure the first network device to send a report indicating that a power consumption event has occurred. Accordingly, the first network device determines to send the report based on the configuration information.

[0009] In some implementations, the second network device is a device that can provide a serving cell for the first network device. It should be noted that the second network device in this disclosure can be replaced with a serving cell. For example, the phrase "the first network device receives from the second network device" can also be expressed as "the first network device receives from the serving cell," and should be understood in the same or similar manner.

[0010] In some implementations, configuration information is used by the first network device to determine whether to send a report. For example, the configuration may include threshold information indicating that a power consumption event has occurred if a specific measurement of a power consumption-related parameter is greater than or equal to, or less than or equal to, a threshold, and the first network device may send feedback or a report indicating that a power consumption event has occurred.

[0011] In some implementations, the method further includes determining whether a power consumption event has occurred based on configuration information. For example, the first network device determines whether one or more conditions for a power consumption event are met, i.e., one or more conditions indicate that a power consumption event has occurred.

[0012] In some implementations, a report is sent when a power consumption event has occurred. For example, a first network device may send a report when one or more conditions indicating that a power consumption event has occurred are met.

[0013] In some implementations, the configuration information includes at least one of the following: information for identifying the type of power consumption event to be detected by the first network device; information indicating a threshold related to the type of power consumption event, which will be compared with the detection data to determine whether a power consumption event has occurred; information indicating the offset of the measured power consumption exceeding the threshold to determine a power consumption event; information indicating the duration of the power consumption event that triggers the transmission of a report; information indicating whether the first network device is assigned to send a report when a power consumption event has occurred; information indicating the type of power consumption measurement to be reported; information indicating whether a network device group including the first network device is assigned to send a report when a power consumption event has occurred; or information indicating the reporting device in the network device group assigned to send a report when a power consumption event has occurred.

[0014] In some implementations, the type of power consumption event to be detected is related to at least one of the following: power consumption exceeding a threshold; power consumption exceeding a threshold by an offset; power consumption of a network device group including the first network device exceeding a threshold; or power consumption of a network device group including the first network device exceeding a threshold by an offset.

[0015] In some implementations, the report includes at least one of the following: information identifying the first network device; information identifying the network device group including the first network device; information indicating the type of power consumption event measured by the first network device; information indicating the amount of power consumption measured by the first network device; or information indicating the service carrier frequency detected by the first network device for the power consumption event.

[0016] In some implementations, at least one of the following conditions must be met: the first network device serves the first coverage area; or the second network device corresponds to the second coverage area.

[0017] In some implementations, at least one of the following conditions must be met: the first coverage area is smaller than the second coverage area; at least a portion of the first coverage area is in the second coverage area; or the first coverage area overlaps with the second coverage area.

[0018] According to some aspects of this disclosure, a method is provided, comprising: a first network device receiving configuration information from a second network device, wherein the configuration information includes a power consumption command, the power consumption command indicating at what power the first network device should transmit, the duration for which the power is turned on or off, and functions that the first network device should turn on or off.

[0019] In some implementations, the second network device is a device that can provide a serving cell for the first network device. It should be noted that the second network device in this disclosure can be replaced with a serving cell. For example, the phrase "the first network device receives from the second network device" can also be expressed as "the first network device receives from the serving cell," and should be understood in the same or similar manner.

[0020] In some implementations, configuration information, including power consumption commands, is received in the binary sequence of reference signals sent by the second network device.

[0021] In some implementations, the binary sequence of the reference signal includes: one or more bits indicating the power at which the first network device should transmit; one or more bits indicating the duration of power on or off; and one or more bits indicating one or more functions that the first network device should turn on or off.

[0022] In some implementations, the binary sequence of the reference signal includes: one or more bits indicating the power-on function, and the same number of bits not included in the power-off function; or one or more bits indicating the power-off function, and the same number of bits not included in the power-on function.

[0023] In some implementations, configuration information, including power consumption commands, is received from the radio resource control (RRC) protocol signaling of the second network device.

[0024] In some implementations, configuration information, including power consumption commands, is received from the downlink control information (DCI) of the second network device.

[0025] In some implementations, the method further includes: a first network device detecting a control channel carrying control information from a second network device, wherein the control information carries configuration information.

[0026] In some implementations, the control information includes a cyclic redundancy check (CRC) scrambled with a radio network temporary identifier (RNTI).

[0027] In some implementations, the control channel is a dedicated control channel for the first network device.

[0028] In some implementations, a first network device serves a first coverage area; and / or a second network device serves a second coverage area.

[0029] In some implementations, at least one of the following conditions must be met: the first coverage area is smaller than the second coverage area; at least a portion of the first coverage area is in the second coverage area; or the first coverage area overlaps with the second coverage area.

[0030] In some implementations, the first network device is the first terrestrial transmission and receive point (T-TRP).

[0031] In some implementations, the second network device is a non-terrestrial transmission and receive point (NT-TRP).

[0032] In some implementations, the first network device will send a report to a second network device or another NT-TRP that is different from the NT-TRP and acts as the second network device.

[0033] In some implementations, when the first network device is the first T-TRP and the second network device is the first NT-TRP, the first NT-TRP can provide services and coverage for the first T-TRP, or serve as a serving cell for the first T-TRP.

[0034] In some implementations, the second network device is the first NT-TRP, and the first network device sends reports to the second network device or a second NT-TRP that is different from the first NT-TRP.

[0035] In some implementations, the second network device is either on the same track as other NT-TRP devices, or on a different track, with each track providing coverage for the first network device.

[0036] According to some aspects of this disclosure, a method for network management is provided, comprising: a first network device sending configuration information to a second network device, wherein the configuration information is used to configure the second network device to send a report indicating that a power consumption event has occurred in the network served by the second network device. Accordingly, the second network can determine whether to send the report based on the configuration information sent by the first network device.

[0037] In some implementations, the first network device is a device that can provide a serving cell to the second network device. It should be noted that the first network device in this disclosure can be replaced by a serving cell. For example, the phrase "the first network device sends to the second network device" can also be expressed as "the serving cell sends to the second network device," and should be understood in the same or similar manner.

[0038] In some implementations, configuration information is used to configure the second network device to determine whether to send a report. For example, the configuration may include threshold information, indicating that a power consumption event has occurred if a specific measurement of a power consumption-related parameter is greater than or equal to, or less than or equal to, a threshold, and the second network device may send feedback or a report indicating that a power consumption event has occurred.

[0039] In some implementations, the method further includes receiving a report when the second network device determines, based on configuration information, that one or more conditions indicating a power consumption event have been met. For example, the second network device may send a report when one or more conditions indicating a power consumption event have been met.

[0040] In some implementations, the configuration information includes at least one of the following: information for identifying the type of power consumption event to be detected by the second network device; information indicating a threshold related to the type of power consumption event, which will be compared with the detection data to determine whether a power consumption event has occurred; information indicating the offset of the measured power consumption exceeding the threshold to determine a power consumption event; information indicating the duration of the power consumption event that triggers the transmission of a report; information indicating whether the second network device is assigned to send a report when a power consumption event has occurred; information indicating the type of power consumption measurement to be reported; information indicating whether a group of network devices in the network including the second network device is assigned to send a report when a power consumption event has occurred; or information indicating the reporting device in the group of network devices assigned to send a report when a power consumption event has occurred.

[0041] In some implementations, the type of power consumption event to be detected is related to at least one of the following: power consumption exceeding a threshold; power consumption exceeding a threshold by an offset; power consumption of a network device group including the first network device exceeding a threshold; or power consumption of a network device group including the first network device exceeding a threshold by an offset.

[0042] In some implementations, the report includes at least one of the following: information identifying the second network device; information identifying a group of network devices in a network that includes the second network device; information indicating the type of power consumption event measured by the second network device; information indicating the amount of power consumption measured by the second network device; or information indicating the frequency of the service carrier detected by the second network device.

[0043] According to some aspects of this disclosure, a method is provided, comprising: a first serving cell sending configuration information to a second network device, wherein the configuration information includes a power consumption command that indicates at what power the second network device should transmit, the duration for which the power is turned on or off, and functions that the second network device should turn on or off.

[0044] In some implementations, the first network device is a device that can provide a serving cell to the second network device. It should be noted that the first network device in this disclosure can be replaced by a serving cell. For example, the phrase "the first network device sends to the second network device" can also be expressed as "the serving cell sends to the second network device," and should be understood in the same or similar manner.

[0045] In some implementations, configuration information, including power consumption commands, is received in the binary sequence of reference signals sent by the first network device.

[0046] In some implementations, the binary sequence of the reference signal includes: one or more bits indicating the power at which the second network device should transmit; one or more bits indicating the duration of power on or off; and one or more bits indicating one or more functions that the serving network device should turn on or off.

[0047] In some implementations, the binary sequence of the reference signal includes: one or more bits indicating the power-on function, and the same number of bits not included in the power-off function; or one or more bits indicating the power-off function, and the same number of bits not included in the power-on function.

[0048] In some implementations, the first network device sends configuration information, including power consumption commands, in the radio resource control (RRC) protocol signaling.

[0049] In some implementations, the first network device sends configuration information, including power consumption commands, in the downlink control information (DCI).

[0050] In some implementations, the control information includes a cyclic redundancy check (CRC) scrambled with a radio network temporary identifier (RNTI).

[0051] In some implementations, the second network device is the first terrestrial transmission and receive point (T-TRP).

[0052] In some implementations, the first network device is a non-terrestrial transmission and receive point (NT-TRP).

[0053] In some implementations, the second network device will send reports to the first network device or another NT-TRP that is different from the first network device and acts as the first network device.

[0054] In some implementations, the first network device is on the same track as other NT-TRP devices, or on a different track, with each track providing coverage for the second network device.

[0055] In some implementations, when the second network device is the first T-TRP and the first network device is the second T-TRP, the second T-TRP can provide services and coverage for the first T-TRP, or serve as a serving cell for the first T-TRP to provide services and coverage.

[0056] In some implementations, when the second network device is the first T-TRP and the first network device is the first NT-TRP, the first NT-TRP can provide services and coverage for the first T-TRP, or serve as a serving cell for providing services and coverage for the first T-TRP.

[0057] In some implementations, a first network device serves a first coverage area; and / or a second network device serves a second coverage area.

[0058] According to one aspect of this disclosure, a network device is provided, including means for performing the methods described in this disclosure. For example, the network device includes a processor and a computer-readable medium. The computer-readable medium stores computer-executable instructions that, when executed, cause the processor to perform the methods described above or detailed below. Non-limiting examples of this network device are terrestrial transmission and receive points (T-TRPs) or non-terrestrial TRPs. In some implementations, the network device includes a chip, such as an integrated circuit (IC) chip. In some implementations, the network device does not execute instructions via a processor to perform the methods described above; for example, a first network device may include circuitry for performing the methods described above, such as a field-programmable gate array (FPGA), a graphics processing unit (GPU), or an application-specific integrated circuit (ASIC). More generally, the network device may include modules, units, or means for performing the methods.

[0059] According to some aspects of this disclosure, a non-transitory computer-readable storage medium is provided, wherein the computer-readable storage medium stores instructions that, when executed by a processor of a device, enable the device to perform the methods described above or as detailed below.

[0060] According to one aspect of this disclosure, a computer program is provided. The computer program includes computer-executable instructions that, when executed, cause a computer to perform the methods described above or elsewhere in this disclosure. Attached Figure Description

[0061] To gain a more comprehensive understanding of this embodiment and its advantages, reference will now be made to the following description by way of example, in conjunction with the accompanying drawings, in which:

[0062] Figure 1 A schematic diagram of a communication system in which embodiments of the present disclosure may be implemented is shown.

[0063] Figure 2 Another schematic diagram of a communication system in which embodiments of the present disclosure may be implemented is shown.

[0064] Figure 3 A block diagram of a unit or module in a device in which embodiments of the present disclosure may be implemented is shown.

[0065] Figure 4 A block diagram of a unit or module in a device in which embodiments of the present disclosure may be implemented is shown.

[0066] Figure 5 An exemplary network is shown in which network devices and service cells communicate and operate according to embodiments of the present disclosure.

[0067] Figure 6 Another exemplary network is shown in which network devices and service cells communicate and operate according to embodiments of the present disclosure.

[0068] Figure 7 An exemplary communication link between a serving cell and a network device serving the serving cell is illustrated according to an embodiment of the present disclosure.

[0069] Figure 8 An exemplary signal flow diagram for reporting power consumption events in a network according to embodiments of the present disclosure is shown.

[0070] Figure 9 An example is shown of a network device according to an embodiment of the present disclosure reporting power consumption events based on configuration information received from the serving cell.

[0071] Figure 10A and Figure 10BAn example of a power consumption command sent from the serving cell to a terrestrial network device in a primary synchronization signal (PSS) according to an embodiment of the present disclosure is shown.

[0072] Figure 11A and Figure 11B Another example of a power consumption command sent from the serving cell to a terrestrial network device in a PSS according to an embodiment of the present disclosure is shown.

[0073] Figure 12A and Figure 12B An example is shown of a network device according to an embodiment of the present disclosure reporting a power consumption command in a downlink control information (DCI) message signaling based on configuration information received from the serving cell. Detailed Implementation

[0074] For illustrative purposes, specific exemplary embodiments will be explained in more detail below with reference to the accompanying drawings.

[0075] The embodiments described herein provide sufficient information to practice the claimed subject matter and illustrate methods for practicing it. Those skilled in the art, upon reading the following description in conjunction with the accompanying drawings, will be able to understand the concepts of the claimed subject matter and recognize the applications of these concepts not specifically stated herein. It should be understood that these concepts and applications are within the scope of this disclosure and the appended claims.

[0076] Furthermore, it should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing information such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, compact disc read-only memory (CD-ROM), digital video disc, or digital versatile disc (DVD). Optical discs or other optical storage devices; volatile and non-volatile, removable and non-removable media implemented in any method or technology; random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies. Any such non-transitory computer / processor storage medium may be part of a device or accessible or connected to a device. Computer / processor-readable / executable instructions used to implement the applications or modules described herein may be stored or otherwise preserved by such non-transitory computer / processor-readable storage media.

[0077] As described above, in wireless communication systems (e.g., Fourth Generation (4G) Long-Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR)), discontinuous reception (DRX) and discontinuous transmission (DTX) are used for energy saving and / or power management on the user equipment (UE) side. For example, when the UE is operating in sleep mode in DRX mode, it does not receive any physical layer signals / channels. For instance, the UE does not detect and measure reference signals (RS) or detect and decode messages carried in logical channels, such as the physical downlink control channel (PDCCH) and / or the physical downlink shared channel (PDSCH). Similarly, when the UE is operating in sleep mode in DTX mode, it does not transmit any physical layer signals / channels. For example, the user equipment does not perform signal processing related to generating uplink signals or uplink logical channels (such as the physical uplink control channel (PUCCH) and / or the physical uplink shared channel (PUSCH)). These techniques enable the user equipment to reduce power by activating its receivers or transmitters only when the user equipment is in active DRX and / or DTX modes.

[0078] There are no standards for energy saving or power management on network-side devices (e.g., transmission and receive points, TRPs). However, previous attempts have all aimed to achieve energy saving on network-side devices.

[0079] One proposed method for achieving energy savings on network-side devices is to use a “simplified” synchronization signal (SS) / physical broadcast channel (PBCH) (SS / PBCH) block. This approach suggests simplifying the SS / PBCH block to reduce power consumption on the network-side devices. For example, the SS / PBCH block can be simplified by including only the primary synchronization signal (PSS) or the secondary synchronization signal (SSS). Other variants that can be considered simplified SS / PBCH blocks have significantly longer cycles than the SS / PBCH blocks supported by wireless communication systems (e.g., 5G NR).

[0080] The second proposed method for achieving energy savings on network-side devices is to use "cell DRX" and "cell DTX," which essentially reflect the aforementioned DRX / DTX modes used for user equipment. For example, when the TRP is in sleep mode in cell DRX mode, the TRP does not receive any physical layer signals / channels (e.g., it does not detect and measure reference signals (RS) or detect and decode messages carried in logical channels such as PUCCH and / or PUSCH). Similarly, when the TRP is operating in sleep mode in DTX mode, the TRP does not transmit any physical layer signals / channels (e.g., it does not perform any signal processing related to generating downlink signals or downlink logical channels such as PDCCH and / or PDSCH).

[0081] A third proposed method for achieving energy savings on network-side devices is bandwidth part (BWP) adaptation. For example, compared to data transmission on a BWP with a larger bandwidth, cell handover is performed so that a BWP with a narrower bandwidth is used for data transmission, thereby reducing the amount of power required for data transmission. To achieve this, the UE can configure multiple BWPs (e.g., capable of dynamically adjusting their bandwidth) and indicate a handover from one BWP (e.g., a BWP with a wider bandwidth) to another BWP (e.g., a BWP with a narrower bandwidth). For example, DCI signaling can be used to send the indication for BWP handover.

[0082] Energy-saving and management methods used on the network side, such as those mentioned above, can be network-specific. Network-specific or customized energy-saving implementations may be feasible; for example, network operators can perform energy saving and management based on heuristics, traffic load management, and balancing.

[0083] However, as mentioned above, network energy-saving and management technologies specific to certain networks may be difficult to manage, maintain, or scale. For example, some network-specific energy-saving and management technologies may require network operators to use network equipment and accessories from only one network hardware vendor. Given that network operators typically use a variety of network equipment and accessories from multiple network hardware vendors, network-specific energy-saving and management technologies may not be necessary. Instead, a standardized approach to energy saving and / or network management may be required, as standardized approaches to energy saving and / or network management may be easier to manage, maintain, or scale than network-specific energy-saving and management technologies, especially when network operators use network equipment and accessories from multiple network hardware vendors.

[0084] Various aspects of this disclosure provide methods and apparatus for overcoming the aforementioned drawbacks, as well as specific methods for network management in various network systems. According to some implementations of this disclosure, a serving cell can support power management within the coverage area served by a network device (e.g., a terrestrial TRP). The serving cell can be considered a base station that allows and supports power management based on power event reports sent by the network device. In some implementations, the base station can be a terrestrial base station. In some implementations, the base station can be a non-terrestrial base station. In some implementations, the network device can be a terrestrial base station. The network device can send a report indicating that a power event has occurred. A power event can be an event in which at least one detected power consumption indicator is equal to or greater than, equal to, or less than a threshold. The network device can send a report when one or more conditions indicating that a power event has occurred are met based on configuration information received from the serving cell. The configuration information can be used by the network device to determine whether to send a report indicating that a power event has occurred.

[0085] In some implementations, a control channel carrying control information messages can be used to schedule the transmission of configuration information. In some implementations, the control channel can be a common control channel shared with one or more other network devices (e.g., base stations) in the network. In some implementations where the control channel is a common control channel, the configuration information can be carried on a system information block (SIB). In some implementations where the control channel is a common control channel, the control information message may include a cyclic redundancy check (CRC) scrambled with a radio network temporary identifier (RNTI). In some implementations, the control channel can be a network device-specific control channel. In some implementations where the control channel is a network device-specific control channel, the configuration information can be carried on a radio resource control (RRC) configuration message.

[0086] Some aspects of this disclosure enable seamless global network coverage while achieving carbon neutrality in various network systems, such as terrestrial network systems, non-terrestrial network systems, and integrated terrestrial and non-terrestrial network systems (e.g., network systems where terrestrial and non-terrestrial equipment can coexist). Some aspects of this disclosure also enable efficient management of power consumption and network traffic load in various network systems.

[0087] Although the various aspects of this disclosure are primarily described in some network systems, such as integrated terrestrial and non-terrestrial network systems, it should be noted that the various aspects of this disclosure are not limited to the integrated terrestrial and non-terrestrial network systems described herein, but are more broadly applicable to terrestrial network systems, non-terrestrial network systems, or other types of network systems that can utilize the methods, apparatus, and / or devices described herein. In other words, the various aspects of this disclosure are not limited to a particular type of communication or a particular wireless access technology.

[0088] Figure 1 , Figure 2 , Figure 3 A network and device context is provided, which may be in a network and may implement various aspects of this disclosure.

[0089] refer to Figure 1This diagram, provided as an illustrative example and not as limiting, is a simplified schematic of a communication system. Communication system 100 includes a radio access network 120. Radio access network 120 can be a next-generation (e.g., sixth-generation, 6G, or later) radio access network or a traditional (e.g., 5G, 4G, 3G, or 2G) radio access network. In radio access network 120, one or more communication electric devices (EDs) 110a to 120j (collectively referred to as 110) can be interconnected with each other and can also, or alternatively, connected to one or more network nodes (170a, 170b (collectively referred to as 170); 172). Network nodes 170a and 170b can be terrestrial network nodes, and network node 172 can be a non-terrestrial network node. It should be noted that one or more communication EDs 110 and... Figure 1 The described connection between one or more network nodes 170 and / or 172 is merely an example. Figure 1 One or more connections that are not explicitly described are also possible. For example, although the connection between ED 110e and network node 172 is not explicitly included... Figure 1 However, ED 110e and network node 172 can be interconnected. Core network 130 can be part of the communication system and can rely on or be independent of the wireless access technology used in communication system 100. In addition, communication system 100 includes public switched telephone network (PSTN) 140, Internet 150, and other networks 160.

[0090] Figure 2 An exemplary communication system 100 that can implement this disclosure is shown. Generally, system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of system 100 may be to provide content (voice, data, video, text) via broadcast, narrowcast, user equipment to user equipment, etc. System 100 can achieve efficient operation by sharing resources such as bandwidth.

[0091] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110c, radio access networks (RANs) 120a and 120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Although Figure 2 A certain number of these components or elements are shown, but the system 100 may include any suitable number of these components or elements.

[0092] ED 110a to ED 110c are used for operation and / or communication in system 100. For example, ED 110a to ED 110c are used for transmitting and / or receiving via a wireless communication channel. ED 110a to ED 110c represent any suitable end-user equipment for wireless operation and may include (or be referred to as): user equipment (UE / user device), wireless transmit / receive unit (WTRU), mobile station, mobile user unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop computer, computer, touchpad, wireless sensor, or consumer electronic device.

[0093] Figure 2 An exemplary communication system 100 that can implement this disclosure is shown. Generally, the communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of the communication system 100 may be to provide content (voice, data, video, text) via broadcast, multicast, unicast, user equipment to user equipment, etc. The communication system 100 can operate by sharing resources such as bandwidth.

[0094] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110d, radio access networks (RANs) 120a to 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Although Figure 2 A certain number of these components or elements are shown, but the communication system 100 may include any suitable number of these components or elements.

[0095] ED 110a to ED 110d are used for operation and / or communication in communication system 100. For example, ED 110a to ED 110d are used for transmitting and / or receiving via a wireless communication channel or a wired communication channel. ED 110a to ED 110d all represent any suitable end-user equipment for wireless operation and may include (or be referred to as): user equipment (UE / user device), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop computer, computer, tablet computer, wireless sensor, or consumer electronic device.

[0096] exist Figure 2 In this configuration, RAN 120a and RAN 120b include base stations 170a and 170b, respectively. Both base stations 170a and 170b are used to establish wireless connections with one or more EDs (EDs) from ED 110a to ED 110c, enabling access to any other base stations 170a and 170b, core network 130, PSTN 140, Internet 150, and / or other networks 160. For example, base stations 170a and 170b may include (or may be) one or more of several known devices, such as a base transceiver station (BTS), a 3G base station (NodeB), an evolved NodeB (eNodeB), a home eNodeB, a gNodeB, a transmission and receive point (TRP), a site controller, an access point (AP), or a wireless router.

[0097] In some examples, base station 170a and / or base station 170b may be a ground-based base station connected to the ground. For example, a ground-based base station may be mounted on a building or tower. Alternatively, one or more of base stations 172 may be a non-ground-based base station not attached to the ground, or a non-terrestrial TRP (NT-TRP). A flying base station is an example of a non-ground-based base station. A flying base station can be implemented using communication equipment supported or carried by flying equipment. Non-limiting examples of flying equipment include airborne platforms (e.g., small airships or spacecraft), balloons, quadcopters, and other aircraft. In some implementations, a flying base station may be supported or carried by an unmanned aerial system (UAS) or an unmanned aerial vehicle (UAV) (e.g., a drone or quadcopter). A flying base station may be a mobile or portable base station capable of being flexibly deployed in different locations to meet network requirements. A satellite base station is another example of a non-ground-based base station. A satellite base station can be implemented using communication equipment supported or carried by a satellite. A satellite base station may also be referred to as an orbital base station.

[0098] ED 110a to ED 110d can be used alternatively or additionally for connection, access or communication with any other base station 170a and 170b, Internet 150, core network 130, PSTN 140, other network 160 or any combination thereof.

[0099] ED 110a to ED 110d, as well as base stations 170a, 170b, and 172, are examples of communication devices that can be used to implement some or all of the operations and / or embodiments described herein. Figure 2In the example shown, base station 170a is part of RAN 120a, which may include other base stations, one or more base station controllers (BSCs), one or more radio network controllers (RNCs), relay nodes, components, and / or equipment. Base stations 170a and 170b can be individual components as shown, or multiple components distributed within the corresponding RAN. Similarly, base station 170b is also part of RAN 120b, which may include other base stations, components, and / or equipment. Base stations 170a and 170b transmit and / or receive radio signals within a specific geographical area or region (sometimes referred to as a "cell" or "coverage area"). A cell may be further divided into cell sectors; for example, base stations 170a and 170b may employ multiple transceivers to provide service to multiple sectors. In some implementations, there may be established picocells or femtocells supported by radio access technologies. In some implementations, for example, multiple transceivers can be used for each cell using multiple-input multiple-output (MIMO) technology. The number of RANs 120a and RAN 120b shown is merely exemplary. Any number of RANs can be considered when designing the communication system 100.

[0100] Base stations 170a, 170b, and 172 use radio frequency (RF), microwave, and infrared (IR) wireless communication links to communicate with one or more of the following electrical devices (EDs) 110a to 110d via one or more air interfaces 190a and 190c. Air interfaces 190a and 190c can use any suitable wireless access technology. For example, communication system 100 can implement one or more orthogonal or non-orthogonal channel access methods in air interfaces 190a and 190c, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA).

[0101] Base stations 170a, 170b, and 172 communicate with each other via one or more air interfaces 190e and 190f using radio frequency (RF), microwave, or infrared (IR) wireless communication links. Air interfaces 190e and 190f can use any suitable wireless access technology and can be substantially similar to, but not substantially similar to, air interfaces 190a and 190c used by ED 110a to ED 110d to communicate with base stations 170a, 170b, and 172. For example, the communication system 100 can implement one or more channel access methods in the SL air interface 190e and air interface 190f, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or single-carrier FDMA (SC-FDMA).

[0102] Base stations 170a, 170b, and 172 can implement Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access (UTRA) to establish air interfaces 190a and 190c using wideband CDMA (WCDMA). In this case, base stations 170a, 170b, and 172 can implement protocols such as High Speed ​​Packet Access (HSPA) and Evolved HPSA (HSPA+), optionally including High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Packet Uplink Access (HSPUA). Alternatively, base stations 170a, 170b, and 172 can use LTE, LTE-A, and / or LTE-B to establish air interfaces 190a and 190c with Evolved UTMS Terrestrial Radio Access (E-UTRA). The prerequisite is that the communication system 100 can use multi-channel access operation, including the schemes described above. Other wireless technologies used to implement the air interface include IEEE 802.11, 802.15, 802.16, CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemes and wireless protocols can also be used.

[0103] RAN 120a and RAN 120b communicate with core network 130 to provide various services to ED 110a through ED 110c, such as voice, data, and other services. RAN 120a and RAN 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown). One or more other RANs may or may not be directly served by core network 130, and may or may not use the same radio access technology as RAN 120a and / or RAN 120b. Core network 130 may also serve as a gateway access between (i) RAN 120a and RAN 120b and / or between ED 110a through ED 110c, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160).

[0104] ED 110a to ED 110d use radio frequency (RF), microwave, infrared (IR), or other wireless communication links to communicate with each other via one or more sidelink (SL) air interfaces 190b and 190d. SL air interfaces 190b and 190d can use any suitable wireless access technology and can be substantially similar to, or significantly different from, air interfaces 190a and 190c used by ED 110a to ED 110c to communicate with base stations 170a and / or 170b. For example, the communication system 100 may implement one or more channel access methods in the SL air interface 190b and air interface 190d, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). In some implementations, the SL air interface 190b and air interface 190d may be implemented at least partially on unlicensed spectrum.

[0105] Furthermore, some or all of ED 110a to ED 110d may include operations that communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. The ED may communicate with a service provider or exchange (not shown) via a wired communication channel and with the Internet 150, rather than wirelessly (or also wirelessly). PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and / or subnets (intranets) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a to ED 110d may be multimode devices capable of operating according to multiple wireless access technologies and include multiple transceivers required to support multiple wireless access technologies.

[0106] In some implementations, the signal is transmitted from a terrestrial BS to the UE, or directly from the UE to the terrestrial BS; in both cases, the signal is not reflected by the RIS. However, the signal may be reflected by obstacles and reflective sources such as buildings, walls, and furniture. In some implementations, the signal communicates between the UE and a non-terrestrial BS (e.g., satellites, drones, and high-altitude platforms). In some implementations, the signal communicates between a relay and the UE, between a relay and a BS, or between two relays. In some implementations, the signal is transmitted between two UEs. In some implementations, one or more RIS are used to reflect signals from a transmitter and a receiver, where either the transmitter or receiver includes the UE, a terrestrial or non-terrestrial BS, and a relay.

[0107] Figure 3 Another example of ED 110 and network equipment is shown, including base station 170a, base station 170b (at 170), and NT-TRP 172. ED 110 is used to connect people, objects, machines, etc. ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, automated delivery and mobility, etc.

[0108] Each ED 110 represents any suitable end-user equipment used for wireless operation, which may include (or may be referred to as) user equipment (UE / user device), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics device, smart book, vehicle, car, truck, bus, train, or IoT device, industrial equipment or apparatus of the above (e.g., communication module, modem, or chip), etc. Future generations of ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, hereinafter referred to as T-TRP 170. Also in Figure 3 As shown, NT-TRP will be referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be configured to be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or in response to one or more of connection availability and connection necessity.

[0109] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure. Alternatively, one, part, or all of the antennas may be panels. For example, the transmitter 201 and receiver 203 may be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver may also be used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure to generate signals for wireless or wired transmission and / or process signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure to transmit and / or receive wireless or wired signals.

[0110] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, and executed by one or more processing units 210. Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, etc.

[0111] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1 or Figure 2 (Wired interface of Internet 150 in the network). Input / output devices support interaction with users or other devices in the network. Each input / output device includes any structure suitable for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0112] ED 110 also includes a processor 210 for performing operations related to preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170, operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and operations related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, the downlink transmission may be received by receiver 203 using receive beamforming, and processor 210 may extract signaling from the downlink transmission (e.g., by detecting and / or decoding signaling). For example, the signaling may be a reference signal transmitted by NT-TRP 172 and / or T-TRP 170. In some implementations, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications (e.g., beam angle information (BAI)) received from T-TRP 170. In some implementations, processor 210 can perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some implementations, processor 210 can perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0113] Although not shown, processor 210 may be part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may be part of processor 210.

[0114] Processor 210, as well as the processing components of transmitter 201 and receiver 203, may each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components in processor 210, as well as transmitter 201 and receiver 203, may be implemented using special-purpose circuitry such as a field-programmable gate array (FPGA), a graphics processing unit (GPU), or an application-specific integrated circuit (ASIC).

[0115] In some implementations, ED 110 can be a device (also called a component), such as a communication module, modem, chip, or chipset, which includes at least one processor 210 and an interface or at least one pin. In this scenario, transmitter 201 and receiver 203 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as sending information to an interface or at least one pin, or sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. Receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. The information may include control signaling and / or data. Similar rules may apply to other nodes / entities in this disclosure. In some implementations, T-TRP 170 may be referred to by other names, such as: base station, base transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved NodeB (eNodeB or eNB), femtocell, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP) or wireless router, relay station, remote radio head, ground node, ground network device or ground base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. T-TRP 170 can be a macro BS, pico BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned device or a component within the aforementioned device (e.g., a communication module, modem, or chip). Although the accompanying drawings and the description of examples and embodiments of this disclosure generally use the terms AP, BS, and AP or BS, it should be understood that such device may be any of the types described above.

[0116] In some implementations, the various parts of the T-TRP 170 can be distributed. For example, some modules of the T-TRP 170 can be located remotely from the device housing the antenna of the T-TRP 170 and can be coupled to the device housing the antenna via a communication link (not shown), sometimes referred to as a fronthaul, such as a Common Public Radio Interface (CPRI). Therefore, in some implementations, the term "T-TRP 170" can also refer to modules on the network side that perform processing operations such as ED 110 location determination, resource allocation (scheduling), message generation, and encoding / decoding; these modules are not necessarily part of the device housing the antenna of the T-TRP 170. These modules can also be coupled to other T-TRPs. In some implementations, the T-TRP 170 can actually consist of multiple T-TRPs that work together, for example, through coordinated multicast transmissions, to serve the ED 110.

[0117] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure. Alternatively, one, part or all of the antennas may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing the following operations: preparing transmissions for downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmissions to NT-TRP 172, and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing transmissions for downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing uplink or backhaul transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processor 260 can also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB), generating system information, etc. In some implementations, processor 260 also generates beam direction indications, such as BAI, which can be scheduled for transmission by scheduler 253. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the location for deploying NT-TRP 172, etc. In some implementations, processor 260 can generate signaling, such as one or more parameters for configuring ED 110 and / or one or more parameters for NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that "signaling" as used herein may also be referred to as control signaling. Dynamic signaling can be transmitted in control channels, such as the physical downlink control channel (PDCCH). Static or semi-static higher-layer signaling can be included in packets transmitted in data channels such as the physical downlink shared channel (PDSCH).

[0118] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included in or operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, and / or backlink transmissions, including issuing scheduling authorizations and / or configuring schedule-free (“configuration authorization”) resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules executed by processor 260 for implementing some or all of the functions and / or embodiments described herein.

[0119] Although not shown, processor 260 may be part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may be part of processor 260.

[0120] The processor 260, scheduler 253, and processing components of transmitter 252 and receiver 254 may each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, and transmitter 252 and receiver 254 may be implemented using dedicated circuitry such as FPGA, GPU, or ASIC.

[0121] When T-TRP 170 is a device (also referred to as a component, such as a communication module, modem, chip, or chipset in a device), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., chips, memory, or buses). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as sending information to an interface or at least one pin. Receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. The information may include control signaling and / or data.

[0122] Although the NT-TRP 172 is shown as a drone for example only, it can be implemented in any suitable non-terrestrial form. Furthermore, in some implementations, the NT-TRP 172 may be referred to by other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figure. Alternatively, one, some, or all of the antennas may be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing the following operations: preparing transmissions for downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmissions to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing for downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing uplink or backhaul transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some implementations, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some implementations, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some implementations, NT-TRP 172 implements physical layer processing but not higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, NT-TRP 172 may more generally implement higher-level functions in addition to physical layer processing.

[0123] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, a processor 276 may form part of the transmitter 272 and / or receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0124] The processor 276 and the processing components of the transmitter 272 and receiver 274 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processor 276 and the processing components of the transmitter 272 and receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, GPU, or ASIC. In some implementations, the NT-TRP 172 may actually be multiple NT-TRPs, which, for example, work together via coordinated multipoint transmissions to serve ED 110.

[0125] When T-TRP 170 is a device (also referred to as a component, such as a communication module, modem, chip, or chipset in a device), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., chips, memory, or buses). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as sending information to an interface or at least one pin. Receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. The information may include control signaling and / or data.

[0126] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components have been omitted.

[0127] It should be noted that, for simplicity, the term "signaling" used herein can also be referred to as control signaling, control message, control information, or simply message. Signaling between a BS (e.g., network node 170) and a terminal or sensing device (e.g., ED 110), or between different terminals or sensing devices (e.g., between ED 110i and ED 110j), can be carried in physical layer signaling (also known as dynamic signaling), which is transmitted in the physical layer control channel. For the downlink, physical layer signaling can be referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be referred to as uplink control information (UCI) transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., between ED 110i and ED 110j) can be referred to as sidelink control information (SCI) transmitted in the physical sidelink control channel (PSCCH). Signaling can be carried in higher-layer (e.g., above the physical layer) signaling, which is transmitted in physical layer data channels. For example, downlink signaling is transmitted in the physical downlink shared channel (PDSCH), uplink signaling in the physical uplink shared channel (PUSCH), and sidelink signaling in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be referred to as static signaling or semi-static signaling. Higher-layer signaling can be radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can include a combination of physical layer signaling and higher-layer signaling.

[0128] It should be noted that in this disclosure, when “information” and “message” are not the same, they can be carried in a single message or in more than one single message.

[0129] One or more steps of the method provided in this article can be derived from... Figure 3 The corresponding unit or module shown will be executed. Figure 3 The diagram illustrates units or modules within the device, such as those located in ED 110, T-TRP 170, or NT-TRP 172. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of the units or modules may be integrated circuits, such as a programmed FPGA, GPU, or ASIC. It should be understood that if the modules are implemented by a processor through software execution, the processor can retrieve all or part of these modules as needed, retrieve them individually or in combination for processing, and support single-instance or multi-instance retrieval, and these modules themselves may include instructions for further deployment and instantiation.

[0130] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0131] One or more steps of the methods in the embodiments provided herein can be derived from... Figure 4 The corresponding unit or module shown will be executed. Figure 4 The diagram illustrates units or modules within the device, such as those located in ED 110, T-TRP 170, or NT-TRP 172. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of the units or modules may be integrated circuits, such as a programmed FPGA, GPU, or ASIC. It should be understood that if the modules are implemented by a processor through software execution, the processor can retrieve all or part of these modules as needed, retrieve them individually or in combination for processing, and support single-instance or multi-instance retrieval, and these modules themselves may include instructions for further deployment and instantiation.

[0132] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0133] For future wireless networks, the number of new devices is likely to grow exponentially, with increasingly diverse functionalities. Furthermore, many new applications and use cases may emerge in future wireless networks that did not exist in 5G, and there may be more diverse quality of service requirements. All of these will bring highly challenging new key performance indicators (KPIs) to future wireless networks (e.g., 6G networks), thus leading to the introduction of sensing technologies and AI technologies, especially ML (deep learning), in the telecommunications field to improve system performance and efficiency.

[0134] AI / ML technology applications encompass communication at both the physical layer and the media access control (MAC) layer. At the physical layer, AI / ML communication can be used to optimize component design and improve algorithm performance, such as in channel coding, channel modeling, channel estimation, channel decoding, modulation, demodulation, MIMO, waveform analysis, multiple access, PHY component parameter optimization and updating, beamforming and tracing, sensing, and localization. At the MAC layer, AI / ML communication leverages AI / ML capabilities to learn, predict, and make decisions to solve complex optimization problems using better strategies and optimal solutions, thereby optimizing MAC functionality. Examples include intelligent TRP management, intelligent beam management, intelligent channel resource allocation, intelligent power control, intelligent spectrum utilization, intelligent modulation and coding schemes (MCS), intelligent hybrid automatic repeat request (HARQ) strategies, and intelligent transmit / receive (Tx / Rx) mode adaptation.

[0135] AI / ML architectures typically consist of multiple nodes. These nodes can be organized in centralized or distributed modes, both of which can be deployed in access networks, core networks, edge computing systems, or third-party networks. Centralized training and computing architectures may be subject to significant communication overhead and strict user data privacy constraints. Distributed training and computing architectures include several frameworks, such as distributed machine learning and federated learning. AI / ML architectures include intelligent controllers, based on joint or individual optimization, which can act as single or multiple agents. New protocols and signaling mechanisms are needed to enable the execution of corresponding interface links with customized parameters to meet specific requirements, while minimizing signaling overhead and maximizing overall system spectral efficiency through customized AI technologies.

[0136] Furthermore, both terrestrial and non-terrestrial networks can enable a range of new services and applications, such as terrestrial detection, remote sensing, passive perception and localization, navigation, line tracking, automated delivery, and mobility. Terrestrial-based and non-terrestrial-based perception can provide intelligent context-aware networks to enhance the user experience. For example, terrestrial-based and non-terrestrial-based perception can offer opportunities for localization and perception applications based on a new set of features and service capabilities. Applications such as terahertz (THz) imaging and spectroscopy have the potential to provide continuous, real-time physiological information for future digital health technologies through dynamic, non-invasive, and contactless measurements. Simultaneous localization and mapping (SLAM) methods can not only enable advanced cross-reality (XR) applications but also enhance navigation for autonomous objects such as vehicles and drones. In both terrestrial and non-terrestrial networks, measured channel data and perceived localization data can be acquired through high bandwidth, additional spectrum, dense networks, and additional light-of-sight (LOS) links. Based on this data, wireless environment maps can be drawn using AI / ML methods, where channel information is linked to its corresponding location or environmental information to provide enhanced physical layer designs based on this map.

[0137] A sensing coordinator is a node in the network that assists in sensing operations. These nodes can be independent nodes dedicated solely to sensing operations, or they can be other nodes (e.g., TRP 170, ED110, or core network nodes) that perform sensing operations in parallel with communication transmissions. New protocols and signaling mechanisms are needed to enable the execution of corresponding interface links with customized parameters to meet specific requirements, while minimizing signaling overhead and maximizing overall system spectral efficiency.

[0138] AI / ML and perception methods require massive amounts of data. To apply AI / ML and perception to wireless communications, increasingly more data needs to be collected, stored, and exchanged. The characteristics of wireless data extend considerably across multiple dimensions, ranging from sub-6 GHz, millimeter-wave to terahertz carrier frequencies; from spatial, outdoor to indoor scenes; and from text, voice to video. The collection, processing, and use of this data can be conducted within a unified framework or different frameworks.

[0139] Some embodiments described herein refer to control information. Control information may also be referred to as control signaling, or signaling. In some cases, control information can be transmitted dynamically, for example, in physical layer control channels such as the physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), or physical downlink control channel (PDCCH). An example of dynamically indicated control information is information sent in physical layer control signaling, such as uplink control information (UCI) sent in PUCCH or PUSCH, or downlink control information (DCI) sent in PDCCH. Dynamic indication can be an indication at a lower layer (e.g., physical layer / layer 1 signaling) rather than at a higher layer (e.g., except in RRC signaling or MAC CE). Semi-static indication can be an indication in semi-static signaling. Semi-static signaling, as used in this document, can refer to non-dynamic signaling, such as higher-layer signaling (e.g., RRC signaling) and / or MAC CE. Dynamic signaling, as used in this document, can refer to dynamic signaling, such as physical layer control signaling transmitted in the physical layer, such as DCI transmitted in PDCCH, or UCI transmitted in PUCCH or PUSCH.

[0140] This disclosure discloses apparatus, devices, and methods for network management in various network systems, including terrestrial network systems, non-terrestrial network systems, and integrated terrestrial and non-terrestrial network systems (e.g., network systems where terrestrial and non-terrestrial devices can coexist). Network management can be performed based on power event reports from network devices (e.g., terrestrial transmission and receive points (T-TRPs)).

[0141] Some aspects of this disclosure relate to power event reporting. For example, a network device (e.g., a T-TRP) can send a report indicating that a power event has occurred (e.g., a power event occurring within the coverage area served by the network device). The network device can send the report to a given network entity (e.g., a non-terrestrial TRP). The report can be generated based on one or more metrics and key performance indicators (KPIs). Some examples of metrics used in the report might include TRP power consumption (in joules), transmit power consumption (in joules), and baseband unit temperature (in degrees Celsius / Kelvin). Thus, a power event can be an event in which at least one of these metrics is equal to or greater than, or equal to or less than, a threshold. For example, when the TRP power consumption in joules is equal to or greater than a certain threshold, or when the transmit power consumption in joules is equal to or greater than a certain threshold, or when the baseband unit temperature in degrees Celsius / Kelvin is equal to or greater than a certain threshold.

[0142] Some aspects of this disclosure relate to power consumption configuration and signaling, wherein a non-terrestrial network (NTN) TRP sends power-on / power-off commands to a terrestrial network (TN) TRP. Power-off commands can be sent in the form of power-off signals or power-off control signaling. Similarly, power-on commands can be sent in the form of power-on signals or power-on control signaling.

[0143] Some aspects of this disclosure relate to the configuration of power consumption events, or the configuration of power consumption event reporting. A network device (e.g., a T-TRP) can receive configuration information from the serving cell to configure the network device to determine whether to send a report indicating that a power consumption event has occurred. In some implementations, configuration information can be sent from the serving cell to the network device using a common signaling mechanism (e.g., a common control channel that can be shared with one or more other network devices in the network). For example, common configuration information can be provided from the serving cell to multiple network devices via multicast using a system information block (SIB). In some implementations, configuration information can be sent from the serving cell to a specific network device using a dedicated signaling mechanism (e.g., a control channel dedicated to a network device). For example, configuration information dedicated to a specific network device can be provided from the serving cell to a specific network device via unicast using radio resource control (RRC) configuration messages.

[0144] In the context of cellular networks, a serving cell can refer to the geographical area where a terminal device (e.g., a UE or a UE-like device) can receive, detect, and measure signals associated with a physical cell identity (PCI). This is typically associated with, for example, a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), whose pseudo-random noise (PRN) sequence is generated from the PCI. For instance, when a terminal device detects a PSS and / or SSS with a received power higher than a certain threshold within a certain (coverage) area served by a given cell, the terminal device can be considered to be within the coverage area of ​​that given cell. From the terminal device's perspective, a "serving cell" can refer to an area where one or more terminal devices (e.g., UEs) can camp, or a cell where one or more network devices can detect certain information (e.g., system information). In fact, the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.304 defines a "serving cell" as "the cell where a UE camps."

[0145] Based on the foregoing, it can be assumed that a cell, serving cell, or beam associated with a cell / serving cell can be associated with the same PCI. Therefore, in one possible interpretation, a cell, serving cell, beam associated with a cell, or beam associated with a serving cell can refer to any network entity that can broadcast the same PCI through its physical synchronization signals and channels (e.g., PSS, SSS, PBCH, and / or synchronization signal block (SSB)). Certain aspects of this disclosure are described based on this possible, loose interpretation.

[0146] In some implementations, a serving cell can refer to a base station that can serve a coverage area and provide network services and coverage to one or more network devices. A serving cell can serve and / or correspond to a coverage area, where one or more network devices can reside or detect certain information (e.g., system information, service-related information, energy-saving commands, etc.) from that coverage area. A serving cell can be a non-terrestrial TRP (e.g., an airborne vehicle, a space vehicle, a satellite (low Earth orbit (LEO) satellite / medium Earth orbit (MEO) satellite / geostationary equatorial orbit (GEO) satellite), a drone, a balloon, a high-altitude platform station (HAPS), and an unmanned airborne vehicle (UAV)) or a terrestrial TRP (e.g., a base station). In some implementations, a network device can refer to a device that can serve a coverage area and provide network services and coverage to one or more terminal devices (e.g., user equipment (UE)). Network equipment can serve a coverage area, where one or more terminal devices can reside, or where one or more terminal devices can detect certain information (e.g., system information) from the coverage area. Network equipment can be a terrestrial TRP (e.g., a base station).

[0147] In some implementations, the coverage area served by the network device can be smaller than the coverage area corresponding to the serving cell. For example, the following will combine... Figure 7 Detailed explanation. In some implementations, at least a portion of the coverage area served by the network device may be within the coverage area corresponding to the serving cell. In some implementations, the coverage area served by the network device may overlap with the coverage area corresponding to the serving cell.

[0148] Some aspects of this disclosure can be implemented using any device that supports terrestrial TRPs (e.g., base stations) and non-terrestrial TRPs (e.g., airborne vehicles, space vehicles, satellites (low Earth orbit (LEO) satellites / medium Earth orbit (MEO) satellites / geostationary equatorial orbit (GEO) satellites), drones, balloons, high-altitude platform stations (HAPS), and unmanned airborne vehicles (UAVs), etc.), or that supports radio access technologies such as fifth-generation (5G) New Radio (NR) or next-generation (e.g., sixth-generation (6G) or higher) radio access networks. However, it is not limited to devices supporting a specific radio access network or a specific radio access technology, but can include any type of radio access technology that supports terrestrial and / or non-terrestrial types of communication. In this disclosure, the terms "power consumption" and "energy saving" are used interchangeably.

[0149] Furthermore, as stated above, although the various aspects of this disclosure are primarily described in some network systems, such as integrated terrestrial and non-terrestrial network systems, it should be noted that the various aspects of this disclosure are not limited to the integrated terrestrial and non-terrestrial network systems described herein, but can be more broadly applied to terrestrial network systems, non-terrestrial network systems, or other types of network systems that can use the methods, apparatus, and / or devices described herein. In other words, the various aspects of this disclosure are not limited to a specific type of communication or a specific wireless access technology.

[0150] Figure 5 An exemplary network 500 is illustrated in which network devices and serving cells communicate and operate according to embodiments of the present disclosure. Network 500 may be an integrated terrestrial and non-terrestrial network system. Network 500 includes network devices 501a, 501b, 501c, 511a, 511b, and 511c. Network 500 also includes a first serving cell represented by non-terrestrial network device 502, a second serving cell represented by non-terrestrial network device 512, and a third serving cell represented by non-terrestrial network device 522. Network 500 also includes a non-terrestrial network (NTN) gateway 524, a first terrestrial network (TN) gateway 526, a second terrestrial network (TN) gateway 528, and a core network 530.

[0151] In some implementations, network devices 501a, 501b, 501c, 511a, 511b, and 511c can be terrestrial TRPs. Network device 501a can serve coverage area 503a, on which one or more terminal devices can be hosted. Figure 5 (Not shown). Similarly, other network devices 501b, 501c, 511a, 511b, and 511c can respectively serve coverage areas 503b, 503c, 513a, 513b, and 513c, each of which can host one or more terminal devices ( Figure 5 (not shown), such as Figure 5 Network devices 501a, 501b, and 501c can communicate with the first serving cell via non-terrestrial network device 502. Network devices 511a, 511b, and 511c can communicate with the second serving cell via non-terrestrial network device 512. Network devices 501a, 501b, and 501c can communicate with the core network 530 via the first serving cell represented by non-terrestrial network device 502 and NTN gateway 524. Network devices 511a, 511b, and 511c can communicate with the core network 530 via the second TN gateway 528. Additionally or alternatively, network devices 511a, 511b, and 511c can communicate with the core network 530 via the second serving cell represented by non-terrestrial network device 512 and NTN gateway 524.

[0152] The first, second, and third serving cells can all be part of a satellite constellation. A satellite constellation typically comprises multiple satellite orbits, each of which may contain multiple satellites (e.g., the first non-terrestrial network device 502, the second non-terrestrial network device 512, and the third non-terrestrial network device 522). Some or all of the satellites in the constellation (e.g., the first non-terrestrial network device 502 and the second non-terrestrial network device 512) can provide wireless coverage or network services to the Earth (e.g., network devices 501a, 501b, 501c, 511a, 511b, and 511c).

[0153] The satellite constellation can communicate with the core network 530 through a dedicated satellite gateway. For example, the first, second, and third serving cells can communicate with the core network 530 through NTN gateways 524 dedicated to the first, second, and third serving cells, respectively, via non-terrestrial network equipment 502, non-terrestrial network equipment 512, and non-terrestrial network equipment 522. Figure 5 As stated above.

[0154] Figure 6 Another exemplary network 600 is shown, in which network devices and serving cells communicate and operate according to embodiments of the present disclosure. Network 600 may be an integrated terrestrial and non-terrestrial network system. Network 600 can be considered as described above regarding... Figure 5 Variations of network 500 are described. Network 600 includes network devices 601a, 601b, 601c, 611a, 611b, and 611c. Network 600 also includes a first serving cell represented by non-terrestrial network device 602, a second serving cell represented by non-terrestrial network device 612, and a third serving cell represented by non-terrestrial network device 622. Network 600 also includes an NTN gateway 624 and a core network 630.

[0155] In some implementations, network devices 601a, 601b, 601c, 611a, 611b, and 611c can be terrestrial TRPs. Network device 601a can serve coverage area 603a, on which one or more terminal devices can be hosted. Figure 6 (Not shown). Similarly, other network devices 601b, 601c, 611a, 611b, and 611c can respectively serve coverage areas 603b, 603c, 613a, 613b, and 613c, each of which can host one or more terminal devices ( Figure 6 (Not shown). Network devices 601a, 601b, and 601c can establish communication connections with the serving cell through non-terrestrial network device 602, for example, using a wireless link. Network devices 601a, 601b, and 601c can establish communication connections with the core network 630 through a first serving cell represented by non-terrestrial network device 602, a third serving cell represented by non-terrestrial network device 622, and NTN gateway 624, such as... Figure 6 As shown. Network devices 611a, 611b, and 611c can establish communication connections with the serving cell through non-terrestrial network device 612, for example, using a wireless link. Network devices 611a, 611b, and 611c can establish communication connections with the core network 630 through a second serving cell represented by non-terrestrial network device 612, a third serving cell represented by non-terrestrial network device 622, and NTN gateway 624, such as... Figure 6 As shown.

[0156] like Figure 6 The first serving cell, the second serving cell, and the third serving cell can communicate with each other through non-terrestrial network device 602, non-terrestrial network device 612, and non-terrestrial network device 622, respectively, for example, through a free-space optical link (e.g., laser).

[0157] In some implementations, the first serving cell, the second serving cell, and the third serving cell can all be part of a satellite constellation. A satellite constellation typically includes multiple satellite orbits, each of which can contain multiple satellites (e.g., non-terrestrial network devices 602, 612, and 622). Some (or all) of the satellites in the constellation (e.g., non-terrestrial network devices 602 and 612) can provide wireless coverage or network services to the Earth (e.g., network devices 601a, 601b, 601c, 611a, 611b, and 611c). The satellites in the constellation (e.g., non-terrestrial network devices 602, 612, and 622) can effectively act as gateways for terrestrial network devices (e.g., network devices 601a, 601b, 601c, 611a, 611b, and 611c). The satellites in the constellation can communicate with the core network 630 via a wireless link through a ground-based NTN gateway. For example, non-terrestrial network devices 602, 612, and 622 can establish a communication connection with the core network 630 through the NTN gateway 624, such as... Figure 6 As shown.

[0158] In some implementations, the NTN gateway 624 can use a wireless link, a wired link (e.g., a fiber optic link), or a combination thereof to establish a communication connection with the core network 630.

[0159] Figure 7 An exemplary communication link between a serving cell and a network device serving the serving cell is illustrated according to an embodiment of the present disclosure. Network 700 may be an integrated terrestrial and non-terrestrial network system. Network 700 includes a first network device 701, a second network device 711, a third network device 721, and a serving cell represented by a non-terrestrial network device 702.

[0160] refer to Figure 7 The first network device 701 can serve the first coverage area 703, and one or more terminal devices can be hosted on it. Figure 7 (Not shown). Similarly, the second network device 711 and the third network device 721 can serve the second coverage area 713 and the third coverage area 723 respectively, and one or more terminal devices can be hosted on them. Figure 7 (Not shown). The serving cell represented by the non-terrestrial network device 702 can serve the coverage area 704, on which the first network device 701, the second network device 711, and the third network device 721 can be hosted, or the first network device 701, the second network device 711, and the third network device 721 can detect certain information (e.g., system information, service-related information, energy-saving commands, etc.).

[0161] In some implementations, such as Figure 7As shown, the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be smaller than the coverage area 704 corresponding to the serving cell represented by the non-terrestrial network device 702. In some implementations, the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be within the coverage area 704. In some implementations, at least a portion of the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be within the coverage area 704. In some implementations, the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be in a different... Figure 7 The manner described overlaps with coverage area 704. For example, only a portion of the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be included in coverage area 704, while other portions of the first coverage area 703, the second coverage area 713, and / or the third coverage area 723 may be outside coverage area 704.

[0162] In some implementations, the first network device 701, the second network device 711, and the third network device 721 can serve and provide network services to ground-based terminal devices. Figure 7 (Not shown) and / or other devices (e.g., smart meters, smart traffic lights, devices that may be considered Internet of Things (IoT) devices). In some cases, the first network device 701, the second network device 711, and the third network device 721 may experience a power consumption event, such as measured power consumption exceeding a threshold, or a power consumption exceeding the threshold by an offset. When such a power consumption event occurs, the first network device 701, the second network device 711, and the third network device 721 can send a report indicating that a power consumption event has occurred on the ground (e.g., the first coverage area 703, the second coverage area 713, and / or the third coverage area 723) to the serving cell via the non-terrestrial network device 702. The report may be based on, for example, measured power consumption exceeding a threshold, a power consumption exceeding the threshold by an offset, and / or other power consumption events.

[0163] In some implementations, when a power consumption event occurs in the first coverage area 703, the first network device 701 can send a report indicating, for example, that a power consumption event has occurred in the first coverage area 703 to the serving cell via the non-terrestrial network device 702. Similarly, when a power consumption event occurs in the second coverage area 713, the second network device 711 can send a report indicating, for example, that a power consumption event has occurred in the second coverage area 713 to the serving cell via the non-terrestrial network device 702. When a power consumption event occurs in the third coverage area 723, the third network device 721 can send a report indicating, for example, that a power consumption event has occurred in the third coverage area 723 to the serving cell via the non-terrestrial network device 702.

[0164] In some implementations, a report can be sent to the serving cell via a non-terrestrial network device 702 based on a power consumption event that has occurred, for example, in a combined area of ​​the first coverage area 703, the second coverage area 713, and the third coverage area 723. For example, when a power consumption event occurs (commonly) in one or more of the first coverage area 703, the second coverage area 713, and the third coverage area 723, one of the first network device 701, the second network device 711, and the third network device 721 (or another device designated to report power consumption events occurring in the first coverage area 703, the second coverage area 713, and the third coverage area 723) can send a report indicating that a power consumption event has occurred in the combined area of ​​the first coverage area 703, the second coverage area 713, and the third coverage area 723.

[0165] like Figure 7As shown, the first network device 701, the second network device 711, and the third network device 721 can establish a communication connection with the serving cell through the non-terrestrial network device 702. In some implementations, the first network device 701, the second network device 711, and the third network device 721 can communicate with the serving cell using a bidirectional wireless link through the non-terrestrial network device 702. For illustrative purposes, each bidirectional wireless link between the respective network device and the serving cell can be considered as including a downlink, which may refer to a link from the serving cell (e.g., via a non-terrestrial TRP) to the network device (e.g., a terrestrial TRP); and an uplink, which may refer to a link from the respective network device to the serving cell. In network 700, the first network device 701 can use the uplink 705u to send information to the serving cell via the non-terrestrial network device 702, and use the downlink 705d to receive information from the serving cell via the non-terrestrial network device 702. Similarly, the second network device 711 can use the uplink 715u to send information to the serving cell via the non-terrestrial network device 702, and use the downlink 715d to receive information from the serving cell via the non-terrestrial network device 702; the third network device 721 can use the uplink 725u to send information to the serving cell via the non-terrestrial network device 702, and use the downlink 725d to receive information from the serving cell via the non-terrestrial network device 702.

[0166] It should be noted that this downlink is different from the downlink (DL), which can be considered as a link from the network to the end device. Similarly, this uplink is different from the uplink (UL), which can be considered as a link from the end device to the network.

[0167] It should also be noted that, although in Figure 7 While not described in the text, some network devices (e.g., terrestrial TRPs) can use unidirectional radio links or a combination of bidirectional and unidirectional radio links to establish communication connections with serving cells (e.g., non-terrestrial TRPs).

[0168] Figure 8A signal flow diagram of an exemplary process 800 for reporting power consumption events in a network according to embodiments of the present disclosure is shown. Process 800 illustrates signaling between a terrestrial TRP (T-TRP) 801 and a non-terrestrial TRP (NT-TRP) 802. In some implementations, T-TRP 801 may be one of the network devices shown above or elsewhere in this disclosure, and NT-TRP 802 may be one of the serving cells shown above or elsewhere in this disclosure. In some implementations, NT-TRP 802 may be within a satellite constellation and may continuously move in satellite orbit.

[0169] In step 810, NT-TRP 802 may send signaling carrying configuration information for power event reporting. The configuration information may be sent from NT-TRP 802 to the ground-based T-TRP 801 using a common signaling mechanism (e.g., a common control channel that may be shared with one or more other TRPs in the network) or a dedicated signaling mechanism (e.g., a control channel dedicated to T-TRP 801). The configuration information may be used to configure T-TRP 801 to determine whether to send a report indicating that a power event has occurred. For example, the power event may have occurred in the coverage area served by T-TRP 801. Some non-limiting examples of the configuration information may include information identifying the type of power event to be detected by T-TRP 801, information indicating a threshold to be compared with detection data to determine whether a power event has occurred, information indicating the duration of the power event that triggers the sending of a report, and information indicating whether T-TRP 801 should be assigned to send a report when a power event has occurred.

[0170] In some implementations where the NT-TRP 802 is located within a satellite constellation and continuously moves in satellite orbit, in step 820, the NT-TRP 802 can send additional configuration information for power event reporting using either a common signaling mechanism or a dedicated signaling mechanism. In some implementations, the additional configuration information may be an update to existing configuration information. Step 820 may be optional.

[0171] In step 830, when T-TRP 801 determines that a power consumption event has occurred, for example, within the coverage area served by T-TRP 801, T-TRP 801 may send a report indicating that a power consumption event has occurred to NT-TRP 802. Whether a power consumption event has occurred can be determined based on configuration information received from NT-TRP 802.

[0172] Despite Figure 8Not shown in the diagram, but in some implementations, the NT-TRP 802 can send network management-related command signaling to the T-TRP 801 after receiving a report indicating that a power consumption event has occurred.

[0173] Despite Figure 8 Not shown in the diagram, but in some implementations where multiple NT-TRPs, including NT-TRP 802, move on the same track, T-TRP 801 can send power event reports to other NT-TRPs different from NT-TRP 802, and / or receive network management-related command signaling from other NT-TRPs different from NT-TRP 802.

[0174] It should be noted that although procedure 800 illustrates the signaling between T-TRP 801 and NT-TRP 802, power event reporting can be performed between the two T-TRPs, where one T-TRP acts as a super base station instead of the NT-TRP acting as the serving cell. This approach is similar to that shown above or elsewhere in this disclosure.

[0175] As described above, in various aspects of this disclosure, the serving cell (e.g., a non-terrestrial TRP, a terrestrial TRP acting as a super base station) can support power consumption and traffic management within the coverage area served by network equipment (e.g., a terrestrial TRP). The serving cell can transmit control information messages via a control channel. These control information messages can schedule configuration information, which can be used to configure the network equipment to determine whether to send a report indicating that a power consumption event has occurred. In some implementations, power consumption events can include power consumption events occurring within the coverage area served by the network equipment. Configuration information and its transmission will be further discussed below or elsewhere in this disclosure.

[0176] In some implementations, a report indicating that a power consumption event has occurred can be sent based on whether a specific metric (such as power consumption exceeding a threshold or power consumption offset exceeding a threshold) exceeds a specifically configured threshold.

[0177] Network devices can detect signaling from the serving cell (e.g., a non-terrestrial TRP operating in a given constellation) and can receive signaling from the serving cell carrying configuration information for power event reporting. The signaling can be higher-layer signaling (e.g., radio resource control (RRC) signaling).

[0178] For example, network devices can detect control channels carrying control information messages from the serving cell. These control information messages can schedule the transmission of configuration information, which can be used to configure the network device to determine whether to send power event reports. The configuration information can be carried in RRC configuration messages.

[0179] In some implementations, the configuration information used for power event reporting can be an information element (IE) (an example of such an IE could be titled "PowerConsEventReporting"), which can be carried in higher-level signaling (e.g., RRC signaling). The configuration information can indicate one or more metrics that can be detected and used to determine whether a power event has occurred. An example of an abstraction or template used for such configuration information is described below as a configuration information abstract syntax (1), using abstract syntax notation 1 (ASN.1):

[0180]

[0181] Configuration Information Abstract Syntax (1)

[0182] In some implementations, the configuration information abstract syntax (1) or configuration information abstract (or configuration information template) may include one or more of “pcAboveThreshold”, “pcAmountOffsetAboveThreshold”, “pcInsideGroupAboveThreshold”, “pcInsideGroupAmountOffsetAboveThreshold” and their values, based on the value of the “pcEventType” parameter.

[0183] Referring to the configuration information abstract syntax (1) shown above, the “pcEventType” parameter can carry information to identify the type of power event to be detected by the network device (e.g., terrestrial TRP) to determine whether a power event has occurred. In the configuration information abstract syntax (1), the possible values ​​of the “pcEventType” parameter are “pcAboveThreshold”, “pcAmountOffsetAboveThreshold”, “pcInsideGroupAboveThreshold”, and “pcInsideGroupAmountOffsetAboveThreshold”. “pcAboveThreshold” can indicate that the measured power consumption of a single TRP exceeds a threshold, “pcAmountOffsetAboveThreshold” can indicate the offset by which the power consumption of a single TRP exceeds the threshold, “pcInsideGroupAboveThreshold” can indicate that the measured power consumption of a group of terrestrial TRPs exceeds the threshold, and “pcInsideGroupAmountOffsetAboveThreshold” can indicate the offset by which the power consumption of a group of terrestrial TRPs exceeds the threshold.

[0184] The “pcThreshold” parameter can carry a value used to set the threshold used by the network device when comparing power consumption events. Its unit can be, for example, joules (when “reportQuantity” is set to energy) or joules per second (when “reportQuantity” is set to power). In the configuration information abstract syntax (1), the possible values ​​of “pcThreshold” are integers between 10 and 10000000000.

[0185] The “pcOffset” parameter can carry a value to set the offset by which the measured power consumption must exceed a threshold to trigger an event. In the configuration information abstract syntax (1), the possible values ​​of “pcOffset” are integers between –10000 and +10000.

[0186] The “timeDuration” parameter can carry information indicating the duration of a power consumption event to trigger the transmission of a report (done by the network device). In the configuration information abstract syntax (1), the possible values ​​for “timeDuration” are 10 seconds, 30 seconds, 60 seconds, 600 seconds, and 3600 seconds.

[0187] The “reportPerTrp” parameter can carry information indicating whether the network device is assigned (or expected) to send a report when a power event has occurred (e.g., in a coverage area served by the given network device). The value of “reportPerTrp” can also indicate whether a power event has occurred, for example, in a coverage area served by the network device. In the configuration information abstract syntax (1), “reportPerTrp” is a Boolean parameter, so the possible values ​​of “reportPerTrp” can be “true” and “false” (or “0” and “1”; or “TRUE” and “FALSE”).

[0188] The “reportQuantity” parameter can carry a value to set the number of power consumption reports. In the configuration information abstract syntax (1), the possible values ​​for “reportQuantity” are power or energy.

[0189] It should be noted that the above configuration information abstract syntax (1) is only an example of configuration information abstraction or configuration information template, and the configuration information used for power event reporting can be based on it. Other configuration information abstractions or configuration information templates may include one or more other parameters not described above, and / or one or more parameters shown in configuration information abstract syntax (1) may not be included in other configuration information abstractions or templates. In addition, other configuration information abstractions or configuration information templates may include one or more parameters that are the same as those included in configuration information abstract syntax (1), but may have different possible values ​​than those shown in configuration information abstract syntax (1) above.

[0190] An example of configuration information based on the configuration information abstract syntax (1) with specific parameter values ​​is shown below: Configuration information (1):

[0191]

[0192] Configuration information (1)

[0193] As described above, configuration information (1) configures the network device to detect the throughput served by the network device and determine whether a power consumption event has occurred (e.g., the measured service throughput exceeds the service throughput threshold "pcThreshold" within the duration "timeDuration" configured in configuration information (1), for example, in the coverage area served by the network device). According to configuration information (1), when the measured power exceeds 1,000,000 joules for at least 1 minute, the network device is triggered to send a report. In other words, when the measured power exceeds 1,000,000 joules for at least 1 minute, a power consumption event is considered to have occurred.

[0194] In some implementations, a network device may send a report to the serving cell indicating, for example, that a power consumption event has occurred in the coverage area served by the network device. The network device may send a power consumption event report when one or more conditions indicating that a power consumption event has occurred are met. The network device may determine whether one or more conditions indicating that a power consumption event has occurred are met based on configuration information received from the serving cell (e.g., configuration information (1)).

[0195] In some implementations, power event reports can be information elements (IEs) (examples of such IEs may have the title "PowerConsReport"). The following describes an example of an abstraction or template for a report (or power event report) using ASN.1, referred to as the power report abstract syntax (1):

[0196]

[0197] Abstract syntax for power consumption event reporting (1)

[0198] In some implementations, the power consumption report abstract syntax (1) or power consumption event report abstract (or power consumption event report template) may include the "pcEventType" parameter, which takes the value of one or more of "pcAboveThreshold", "pcAmountOffsetAboveThreshold", "pcInsideGroupAboveThreshold" and "pcInsideGroupAmountOffsetAboveThreshold", based on the value of the "pcEventType" parameter in the configuration information received from the serving cell.

[0199] Referring to the power event reporting abstract syntax (1) shown above, the “trpIdentity” parameter can carry information identifying the network device (e.g., a terrestrial TRP), such as the physical layer identifier of the network device. According to the power event reporting abstract syntax (1), the possible values ​​of the “trpIdentity” parameter can be integers between 0 and 4095.

[0200] The “measPowerCons” parameter can carry information indicating the measured power consumption of the network device. According to the power event reporting abstract syntax (1), the possible values ​​of the “measPowerCons” parameter can be integers between 0 and 10000000000.

[0201] The “carrierFrequency” parameter can carry information indicating the service carrier frequency at which a network device measures or detects a given metric. For example, the “carrierFrequency” parameter could be the carrier frequency at which power consumption is measured or detected by a terrestrial TRP. In the power event reporting abstract syntax (1), the value of the “carrierFrequency” parameter can be an integer, which can be understood in the unit “megahertz” (MHz). In the power event reporting abstract syntax (1), the possible values ​​of the “carrierFrequency” parameter can be integers between 1 and 10,000,000. More generally, in some power event reporting abstractions (or templates), such a parameter represents the carrier frequency and can be expressed in units other than MHz.

[0202] It should be noted that the above power event reporting abstract syntax (1) is merely an example of a power event reporting abstract or template, upon which power event reports can be based. Other power event reporting abstracts or templates may include one or more other parameters not described above, and / or one or more parameters shown in power event reporting abstract syntax (1) may not be included in other power event reporting abstracts or templates. Furthermore, other power event reporting abstracts or templates may include one or more parameters that are the same as those included in power event reporting abstract syntax (1), but may have different possible values ​​than those shown in the above power event reporting abstract syntax (1).

[0203] Figure 9 An example is shown of a network device according to an embodiment of the present disclosure reporting power consumption events based on configuration information received from a serving cell. Network 900 includes a first network device 901, a second network device 911, a third network device 921, and a serving cell represented by a non-terrestrial network device 902. The first network device 901, the second network device 911, and the third network device 921 may be terrestrial TRPs, and the serving cell represented by the non-terrestrial network device 902 may be a non-terrestrial TRP.

[0204] refer to Figure 9 The first network device 901 can serve a first coverage area 903, on which one or more UEs 905 can be hosted. The UE can also be a machine-type device, such as a smart meter, smart traffic light, and / or any other device that may be considered an Internet of Things (IoT) device. Similarly, the second network device 911 can serve a second coverage area 913, on which one or more UEs 915 can be hosted, and the third network device 921 can serve a third coverage area 923, on which one or more UEs 925 can be hosted. The serving cell represented by the non-terrestrial network device 902 includes coverage area 908, which includes coverage areas 903, 913, and 923 corresponding to the first network device 901, the second network device 911, and the third network device 921, respectively.

[0205] like Figure 9As shown, the first network device 901, the second network device 911, and the third network device 921 can establish a communication connection with the serving cell represented by the non-terrestrial network device 902. The first network device 901 can receive configuration information from the serving cell represented by the non-terrestrial network device 902 via downlink 906d and send power consumption event reports to the serving cell represented by the non-terrestrial network device 902 via uplink 906u. Similarly, the second network device 911 can receive configuration information from the serving cell represented by the non-terrestrial network device 902 via downlink 916d and send power consumption event reports to the serving cell represented by the non-terrestrial network device 902 via uplink 916u; the third network device 921 can receive configuration information from the serving cell represented by the non-terrestrial network device 902 via downlink 926d and send power consumption event reports to the serving cell represented by the non-terrestrial network device 902 via uplink 926u.

[0206] In some implementations, the first network device 901, the second network device 911, and the third network device 921 can receive configuration information (1) from the serving cell represented by the non-terrestrial network device 902 via downlinks 906d, 916d, and 926d, respectively. Based on the configuration information (1), the first network device 901, the second network device 911, and the third network device 921 can be used to detect the power used by the first network device 901, the second network device 911, and the third network device 921. In the specific example of a power consumption event described above, when the measured power exceeds 1 MJ for at least 1 minute, the first network device 901, the second network device 911, and the third network device 921 can be triggered to send a power consumption event report. In other words, the first network device 901, the second network device 911, and the third network device 921 can all consider a power consumption event to have occurred when the measured power exceeds 1 MJ for at least 1 minute. However, it should be understood that, in contrast to the same thresholds mentioned above, the thresholds for defining power consumption events may be different for one or more different network devices that receive different configuration information (i.e., configuration information different from configuration information (1)).

[0207] In description Figure 9 In a specific example, when the service throughput measured by the second network device 911 exceeds 1 Mjoule for at least 1 minute, the second network device 911 can send a report indicating that a power consumption event has occurred to the serving cell represented by the non-terrestrial network device 902 via the uplink 916u. An example of the report sent by the second network device 911 is shown below as a power consumption event report (1):

[0208]

[0209] Power consumption event report

[0210] Ground TRP transmission reports are sent in the green coverage area, where the “trpIdentity” field is set to 45, the “pcEventType” field is set to the value of “pcAboveThreshold”, the “measPowerCons” field is set to 1004075, and the “carrierFrequency” field is set to 30000 (i.e. 30 GHz).

[0211] In some implementations, the serving cell (in some embodiments, the serving cell may be a non-terrestrial TRP) sends a power-off command using power-off bits embedded in a binary sequence of reference signals to one or more ground devices (which may be terrestrial TRPs). The one or more ground devices detect the reference signals from the serving cell, such as those of a non-terrestrial TRP operating in a given constellation. In some implementations, the serving cell sends synchronization reference signals based on a Gold sequence. The ground devices are configured within logical groups, and within each group, the ground devices are configured with logical identifiers, such as... Integer values ​​within the range.

[0212] In some implementations, M bits are used to generate "power-off commands" (POffC), where M is an integer number of bits, satisfying the following relationship: Where M0, M1, and M2 are integer values. In a specific example, the bit width of M0 is 2, the bit width of M1 is 2, and the bit width of M2 is 3. However, it should be understood that the bit widths of M0, M1, and M2 may differ from those indicated in the example above.

[0213] The parameter M0 corresponds to the transmit power that the network device should send. Different M0 values ​​correspond to different transmit powers. In a specific example, M0 includes... The values ​​in the set of bit pairs, where "00" is a placeholder value and "01" corresponds to the maximum transmit power. "10" corresponds to the maximum transmission power. "11" corresponds to the maximum transmission power. However, it should be understood that the transmitted values ​​assigned to different bit values ​​may differ from the indications in the examples above.

[0214] The parameter M1 corresponds to the duration to which POffC can be applied. Different M1 values ​​correspond to different durations. In a specific example, M1 includes... The values ​​in the set of bit pairs are given, where "00" is a placeholder value, "01" corresponds to a duration of 1 minute, "10" corresponds to a duration of 10 minutes, and "11" corresponds to a duration of 1 hour. However, it should be understood that the duration values ​​assigned to different bit values ​​may differ from the indications in the example above.

[0215] Parameter M2 corresponds to a function that the network device can disable to support the UE that the network device is serving. In a specific example, M2 includes... The values ​​in the bit set are: "000" is a placeholder value; "001" indicates that the network device should disable data transmission to the UE it is serving; "010" indicates that the network device should disable data transmission and beam management; "011" indicates that the network device should disable data transmission, beam management, and radio link detection; "100" indicates that the network device should disable data transmission, beam management, radio link detection, and radio resource management; "101" indicates that the network device should disable data transmission, beam management, radio link detection, radio resource management, and paging; "110" indicates that the network device should disable data transmission, beam management, radio link detection, radio resource management, paging, and system information transmission; and "111" indicates that the network device should disable all radio functions.

[0216] Figure 10A An example is shown where the serving cell (which may be a non-terrestrial TRP) sends a Primary Synchronization Signal (PSS) to a terrestrial network device (which may be a terrestrial TRP). Figure 10A A network 1000 is illustrated, comprising a first network device 1001, a second network device 1011, a third network device 1021, and a serving cell represented by a non-terrestrial network device 1002. The first network device 1001, the second network device 1011, and the third network device 1021 can be terrestrial TRPs, and the serving cell represented by the non-terrestrial network device 1002 can be a non-terrestrial TRP. The first network device 1001, the second network device 1011, and the third network device 1021 each have corresponding coverage areas 1003, 1013, and 1023, respectively. The serving cell represented by the non-terrestrial network device 1002 includes a coverage area 1008, which includes coverage areas 1003, 1013, and 1023 corresponding to the first network device 1001, the second network device 1011, and the third network device 1021, respectively.

[0217] In some implementations, different network devices are used to detect PSS located at different times.

[0218] Figure 10AIt also includes representations of three PSSs, 1004, 1014 and 1024, which can be sent by the non-terrestrial network device 1002 to the first network device 1001, the second network device 1011 and the third network device 1021 respectively. Figure 10B An alternative representation of the three PSS signals 1004, 1014, and 1024 is provided, along with a representation of the binary data in each PSS indicating the operation that the corresponding network device should perform.

[0219] The first network device 1001 receives the POffC bit "1001000" in PSS 1004. These POffC bits include the M1, M2, and M3 bit groups as described above. This is a power-down command instructing the first network device 1001 to set its transmission power to 50% of its maximum transmission power, the power-down command is applied for 1 minute, and the first network device 1001 is expected to perform all its transmission functions normally.

[0220] The second network device 1011 receives the POffC bit "0110100" in PSS 1014. This is a power-off command instructing the second network device 1011 to set its transmission power to 25% of its maximum transmission power. The power-off command is applied for 10 minutes, and the second network device 1011 is intended to disable data transmission, beam management, wireless link detection, and wireless resource management functions.

[0221] The third network device 1021 receives the POffC bit "0011111" in PSS 1024. This is a power-off command instructing the third network device 1021 to disable all wireless functions for one hour. The first two bits are placeholder commands, which are effectively overwritten by the last three bits, resulting in the third network device 1021 setting its transmission power to 0.

[0222] It should be noted that this embodiment only shows three network devices on the ground, each detecting PSS sent at different times. However, a group of network devices can be used to detect the same PSS, and this will cause the group of network devices to apply the same power-down command simultaneously. This mechanism allows the serving cell to address multiple network devices on the ground simultaneously.

[0223] In some implementations, a power-on command using power-on bits embedded in a binary sequence of reference signals is sent by the serving cell. Network devices detect the reference signals from the serving cell, which can be represented by a non-terrestrial TRP operating in a given constellation. In some implementations, the serving cell sends synchronization reference signals based on a Gold sequence. Network devices are configured within logical groups, and within each group, network devices are configured with logical identifiers, such as... Integer values ​​within the range.

[0224] In some implementations, M bits are used to generate "Power-On Commands" (POnC), where M is an integer number of bits, satisfying the following relationship: Where M0, M1, M2, and M3 are integer values. In a specific example, the bit width of M0 is 2, the bit width of M1 is 2, the bit width of M2 is 3, and the bit width of M3 is 2. However, it should be understood that the bit widths of M0, M1, M2, and M3 may differ from those indicated in the above example.

[0225] The parameter M0 corresponds to the transmit power that the network device should send. Different M0 values ​​correspond to different transmit powers. In a specific example, M0 includes... The values ​​in the set of bit pairs are: "00" is a placeholder value, "01" corresponds to 25% of the maximum transmit power, "10" corresponds to 50% of the maximum transmit power, and "11" corresponds to 100% of the maximum transmit power. However, it should be understood that the transmit values ​​assigned to different bit values ​​may differ from the indications in the example above.

[0226] The parameter M1 corresponds to the duration to which PONC can be applied. Different M1 values ​​correspond to different durations. In a specific example, M1 includes... The values ​​in the set of bit pairs are given, where "00" is a placeholder value, "01" corresponds to a duration of 1 minute, "10" corresponds to a duration of 10 minutes, and "11" corresponds to a duration of 1 hour. However, it should be understood that the duration values ​​assigned to different bit values ​​may differ from the indications in the example above.

[0227] Parameter M2 corresponds to the functionality that the ground TRP can disable to support the UE it is serving. In a specific example, M2 includes... The values ​​in the bit set are: "000" is an unused value; "001" indicates that the network device should enable data transmission to the UE it is serving; "010" indicates that the network device should enable data transmission and beam management; "011" indicates that the network device should enable data transmission, beam management, and radio link detection; "100" indicates that the network device should enable data transmission, beam management, radio link detection, and radio resource management; "101" indicates that the network device should enable data transmission, beam management, radio link detection, radio resource management, and paging; "110" indicates that the network device should enable data transmission, beam management, radio link detection, radio resource management, paging, and system information transmission; and "111" indicates that the network device should enable all radio functions.

[0228] Parameter M3 corresponds to the power-on function, and its purpose is to distinguish between power-off and power-on commands. If the binary sequence lengths of the power-off and power-on commands are the same, network devices will not be able to differentiate between the two commands, and the commands will be easily misinterpreted. By adding the M3 bit to provide different binary sequence lengths, the ground TRP can use these sequence lengths to distinguish between power-off and power-on commands and avoid any type of misinterpretation during detection and decoding.

[0229] Figure 11A An example is shown where a non-ground TRP sends a Primary Synchronization Signal (PSS) to a ground TRP. Figure 11A Network 1100 is shown, which includes a first network device 1101, a second network device 1111, a third network device 1121, and a serving cell represented by a non-terrestrial network device 1002. The first network device 1101, the second network device 1111, and the third network device 1121 can be terrestrial TRPs, and the serving cell represented by the non-terrestrial network device 1102 can be a non-terrestrial TRP. The first network device 1101, the second network device 1111, and the third network device 1021 each have corresponding coverage areas 1103, 1113, and 1123. The serving cell represented by the non-terrestrial network device 1102 includes a coverage area 1108, which includes coverage areas 1103, 1113, and 1123 corresponding to the first network device 1101, the second network device 1111, and the third network device 1121, respectively.

[0230] In some implementations, different network devices are used to detect PSS located at different times.

[0231] Figure 11A It also includes representations of three PSSs, 1104, 1114 and 1124, which can be sent by the serving cell represented by the non-terrestrial network device 1102 to the first network device 1101, the second network device 1111 and the third network device 1121 respectively. Figure 11B An alternative representation of the three PSS signals 1104, 1114 and 1124 is provided, along with a representation of the binary data in each PSS indicating the operation that the corresponding network device should perform.

[0232] Because of the two additional bits in the PSS sequence ("11" contained in each of the three PSSs), the network device interprets the power-on command field in the following manner.

[0233] The first network device TRP 1101 receives the PONC bit "1110111" in PSS 1104. These PONC bits include the M1, M2, and M3 bit groups as described above. This is a power-on command instructing the first network device 1101 to set its transmission power to 100% of its maximum transmission power. The power-on command is applied for 10 minutes, and the first network device 1101 is expected to enable all wireless functions and perform all its transmission functions normally.

[0234] The second network device 1111 receives the PONC bit "1111111" in PSS 1114. This is a power-on command instructing the second network device 1111 to set its transmission power to 100% of its maximum transmission power. This power-on command is applied for 60 minutes, and the second network device 1111 is expected to turn on all wireless functions and perform all its transmission functions normally.

[0235] The third ground TRP 1121 receives the PONC bit "1101111" in PSS 1124. This is a power-on command instructing the third network device 1121 to enable all wireless functions for one minute. The first two bits are placeholders, and their effect is actually overridden by the last three bits. As a result, the third network device 1121 is expected to enable all wireless functions and is expected to perform all its transmission functions normally.

[0236] It should be noted that this embodiment only shows three network devices on the ground, each detecting PSS sent at different times. However, a group of network devices can be used to detect the same PSS, which would cause the group of network devices to apply the same power-on command simultaneously. This allows the serving cell to address multiple network devices on the ground simultaneously.

[0237] In some implementations, RRC signaling is used to send power-on commands. The serving cell uses the RRC protocol to transmit higher-layer signaling to the terrestrial network equipment. Other protocols or layers that achieve the same purpose may be used in other embodiments.

[0238] The serving cell sends power consumption commands to network devices to conserve energy, allowing different network devices to operate at different transmission powers. The power consumption command can carry information about the expected transmission power of the network device. An example using Abstract Syntax Notation 1 (ASN.1) is provided below:

[0239]

[0240] The “trpTxpower” field carries an integer value to indicate the transmission power of the network device. In some implementations, this field expresses power in decibels. Possible values ​​for “trpTxpower” are integers between -30 and +60.

[0241] The “pcCommand” field carries two additional parameters. The first parameter is the “commandType” field, which carries a value indicating whether the command is a power-on or power-off command. Possible values ​​for the “commandType” field include “On” or “Off”. The second parameter is the “functions” field, which carries one or more values ​​indicating which functions to enable or disable. Possible values ​​for the “functions” field include data, beam management (BM), channel state information (CSI), radio link management (RLM), radio resource management (RRM), paging (PAG), system information (SI), or any of the previously identified functions.

[0242] The "timeDuration" parameter can carry information indicating the duration for which a power command should be applied (by the network device). Possible values ​​for "timeDuration" are 10 seconds, 30 seconds, 60 seconds, 600 seconds, and 3600 seconds.

[0243] The "carrierFrequency" parameter can carry information indicating the service carrier frequency at which network devices measure or detect a given metric. For example, the "carrierFrequency" parameter could be the carrier frequency at which power consumption is measured or detected by a terrestrial TRP. The value of the "carrierFrequency" parameter can be an integer, which can be understood in the unit "megahertz" (MHz). Possible values ​​for the "carrierFrequency" parameter can be integers between 1 and 10,000,000. More generally, such a parameter represents the carrier frequency and can be expressed in units other than MHz.

[0244] In some embodiments, the serving cell may send energy-saving commands to terrestrial network devices via a dedicated control channel (i.e., the serving cell sends a given command to a given network device). The network devices are deployed as a group according to the operator's plan and are within the coverage area of ​​the serving cell, which may be one or more non-terrestrial TRPs in a satellite constellation.

[0245] Figure 12A An example is shown where the serving cell sends energy-saving commands to the ground TRP. Figure 12A Network 1200 is shown, which includes a first network device 1201, a second network device 1211, a third network device 1221, and a serving cell represented by a non-terrestrial network device 1202. The first network device 1201, the second network device 1211, and the third network device 1221 can be terrestrial TRPs, and the serving cell represented by the non-terrestrial network device 1202 can be a non-terrestrial TRP. The first network device 1201, the second network device 1211, and the third network device 1221 each have corresponding coverage areas 1203, 1213, and 1223, respectively. The serving cell represented by the non-terrestrial network device 1202 includes a coverage area 1208, which includes coverage areas 1203, 1213, and 1223 corresponding to the first network device 1201, the second network device 1211, and the third network device 1221, respectively.

[0246] In some implementations, different network devices are used to detect power-saving commands located at different times and locations.

[0247] Figure 12B It provides representations for three energy-saving command signals: 1204, 1214, and 1224.

[0248] The first network device 1201 receives a power consumption command 1204 and sets its transmission power to 30 dB, disabling data transmission and beam management functions for the UE serving at a 30 GHz carrier frequency for 10 minutes.

[0249] The second network device 1211 receives the power consumption command 1214 and sets its transmission power to 20 dB, disabling data transmission, beam management, and radio link detection functions for the UE serving at a 30 GHz carrier frequency for a duration of 1 minute.

[0250] The third network device 1221 receives the power consumption command 1224 and sets its transmission power to -30 dB, shutting down all radio functions of the UE serving at a 30 GHz carrier frequency for 1 hour.

[0251] It should be noted that this embodiment only shows three terrestrial network devices, each detecting its own power consumption command from the serving cell. However, a group of network devices may receive common RRC signaling, which would cause the terrestrial TRP group to apply the same power consumption command simultaneously. This allows the serving cell to address multiple terrestrial network devices simultaneously.

[0252] It should also be noted that when the three power commands 1204, 1214 and 1224 point to the “off” function, other embodiments of the power commands can “turn on” the network device by setting the “commandType” field to the value “on”.

[0253] In some implementations, downlink control information (DCI) signaling is used to send power-on commands. The serving cell can use physical layer control channels to transmit power consumption signaling to terrestrial network devices. For example, the serving cell sends Power Saving Control Information (PSCI) formatted messages to terrestrial network devices. These PSCI formatted messages may be appended with a cyclic redundancy code (CRC) for error detection, and the CRC may be further scrambled with a unicast / multicast / broadcast radio network temporary identifier (RNTI) to make the PSCI format applicable to specific network devices, groups of network devices, or all network devices covered by the serving cell. The PSCI format may include one or more of the following fields.

[0254] 1) The “CommandType” field is a 1-bit field that indicates whether it is a power-on command or a power-off command.

[0255] 2) The “Functions” field is an n-bit field where n is an integer, indicating which wireless functions the network device should turn on or off.

[0256] 3) The “TrpTxPower” field is an n-bit field where n is an integer, representing the transmission power of the network device in a quantified manner. Different values ​​correspond to different transmission powers.

[0257] 4) The “TimeDuration” field is an n-bit field where n is an integer and represents the duration for which the power command should be applied.

[0258] 5) The “CarrierFreq” field is an n-bit field where n is an integer representing the carrier frequency at which the power command should be applied.

[0259] Other fields may be added to the PSCI format, depending on the context of network power saving. In one example, the DCI format can be dedicated to power saving purposes when a network device uses it to detect a logical control channel carrying a DCI format for power saving. In another example, existing DCI format messages can be reused for power saving by reinterpreting existing fields of the DCI format message in a power-compatible manner.

[0260] In some implementations, configuration information can be used for energy event reporting. Energy event reporting can be an information element (IE) (an example of such an IE could have the title "EnergyConsEventReporting"), which can be carried in higher-level signaling (e.g., RRC signaling). Configuration information can indicate one or more metrics that can be detected and used to determine whether an energy event has occurred. An example of an abstraction or template for such configuration information, described below using abstract syntax notation 1 (ASN.1), is referred to as the configuration information abstract syntax (2):

[0261]

[0262] Configuration Information Abstract Syntax (2)

[0263] In some implementations, based on the value of the “ecEventType” parameter, the configuration information abstract syntax (2) or configuration information abstract (or configuration information template) may include one or more of the following: “ecAboveThreshold”, “ecAmountOffsetAboveThreshold”, “ecInsideGroupAboveThreshold”, “ecInsideGroupAmountOffsetAboveThreshold”, “energyCreditAboveThreshold”, “energyCreditInsideGroupAboveThreshold”, “maxEnergyCreditExpired”, “maxEnergyCreditInsideGroupExpired”, and their values. In some implementations, an “energy credit” can be defined as a number that corresponds to a given energy consumption. In the first example, an energy credit can be defined such that the energy credit corresponds to 1000 joules of energy consumption (e.g., generated by ground TRP). In the second example, an energy credit can be defined such that the energy credit corresponds to 1000 joules of energy consumption (e.g., generated by a ground TRP group). In the third example, an energy limit can be defined such that it corresponds to an energy consumption of 1000 joules per second for 1 second (e.g., generated by ground-based TRP). In the fourth example, an energy limit can be defined such that it corresponds to an energy consumption of 1000 joules per second for 1 second (e.g., generated by a ground-based TRP group). In the fifth example, an energy limit can be defined such that it corresponds to an energy consumption of 1000 joules per second for 1 hour (e.g., generated by ground-based TRP). In the sixth example, an energy limit can be defined such that it corresponds to an energy consumption of 1000 joules per second for 1 hour (e.g., generated by a ground-based TRP group). In the seventh example, an energy limit can be defined such that it corresponds to an energy consumption of 1 billion electron volts (eV) (e.g., generated by ground-based TRP). In the eighth example, an energy limit can be defined such that it corresponds to an energy consumption of 1 billion electron volts (eV) (e.g., generated by a ground-based TRP group). Other values ​​or definitions for the energy limit can also be envisioned and considered. Energy quotas can also be referred to as "energy quanta," "energy currency," and / or other similar terms.

[0264] In some implementations, network devices such as terrestrial TRPs may have "energy credit accounts" used by the network devices (e.g., terrestrial TRPs) to hold and / or store energy credits. In some examples, energy credits may be associated with a given type of network slice, such as enhanced Mobile Broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine-type communication (mMTC), public safety, etc. In further examples, energy credit accounts may be associated with a given type of network slice, such as eMBB, URLLC, mMTC, or public safety. In further examples, the energy credit accounts of network devices (e.g., terrestrial TRPs) can be configured using, for example, higher-layer signaling (e.g., RRC signaling).

[0265] Referring to the configuration information abstract syntax (2) shown above, the “ecEventType” parameter can carry information to identify the type of energy consumption event to be detected by the network device (e.g., terrestrial TRP) to determine whether an energy consumption event has occurred. In the configuration information abstract syntax (2), the possible values ​​of the “ecEventType” parameter are “ecAboveThreshold”, “ecAmountOffsetAboveThreshold”, “ecInsideGroupAboveThreshold”, “ecInsideGroupAmountOffsetAboveThreshold”, “energyCreditAboveThreshold”, “energyCreditInsideGroupAboveThreshold”, “maxEnergyCreditExpired”, and “maxEnergyCreditInsideGroupExpired”. "ecAboveThreshold" indicates that the measured energy consumption of a specific ground device exceeds a threshold. "ecAmountOffsetAboveThreshold" indicates the offset of the measured energy consumption of a specific ground device from exceeding a threshold. "ecInsideGroupAboveThreshold" indicates that the measured energy consumption of a ground TRP group exceeds a threshold. "ecInsideGroupAmountOffsetAboveThreshold" indicates the offset of the measured energy consumption of a ground TRP group from exceeding a threshold. "energyCreditAboveThreshold" indicates that the measured energy credit usage has exceeded a threshold. "energyCreditInsideGroupAboveThreshold" indicates that the measured energy credit usage of a ground TRP group has exceeded a threshold. "maxEnergyCreditExpired" indicates that the measured energy credit usage has exceeded the maximum energy credit usage. "maxEnergyCreditInsideGroupExpired" indicates that the measured energy credit usage of a ground TRP group has exceeded the maximum energy credit usage.

[0266] The “ecThreshold” parameter can carry a value to set the threshold used by the network device when comparing energy consumption events. Its unit can be, for example, joules (when “reportQuantity” is set to energy) or units of energy quota (when “reportQuantity” is set to energy quota). In the configuration information abstract syntax (2), the possible values ​​of “ecThreshold” are integers between 10 and 10000000000.

[0267] The “ecOffset” parameter can carry a value to set the offset by which the measured energy consumption must exceed a threshold to trigger an event. In the configuration information abstract syntax (2), the possible values ​​of “ecOffset” are integers between –10000 and +10000.

[0268] The “timeDuration” parameter can carry information indicating the duration of an energy consumption event to trigger the transmission of a report (done by the network device). In the configuration information abstract syntax (2), the possible values ​​for “timeDuration” are 10 seconds, 30 seconds, 60 seconds, 600 seconds, and 3600 seconds.

[0269] The “maxEnergyCredit” parameter can carry information indicating the maximum amount of energy a network device, such as a terrestrial TRP, can use for wireless communication purposes (e.g., transmitting and / or receiving physical layer channels and / or signals over the air). In the configuration information abstract syntax (2), the possible values ​​for “maxEnergyCredit” are integers between 10 and 1,000,000,000.

[0270] The “reportPerTrp” parameter can carry information indicating whether a network device is assigned (or expected) to send a report when an energy consumption event has occurred (e.g., in a coverage area served by the given network device). The value of “reportPerTrp” can also indicate whether an energy consumption event has occurred, for example, in a coverage area served by the network device. In the configuration information abstract syntax (2), “reportPerTrp” is a Boolean parameter, so the possible values ​​of “reportPerTrp” can be “true” and “false” (or “0” and “1”; or “TRUE” and “FALSE”).

[0271] The “reportQuantity” parameter can carry a value to set the number of energy consumption reports. In the configuration information abstract syntax (2), the possible values ​​for “reportQuantity” are energy or energy quota.

[0272] It should be noted that the above configuration information abstract syntax (2) is only an example of configuration information abstraction or configuration information template, and the configuration information used for energy consumption event reporting can be based on it. Other configuration information abstractions or configuration information templates may include one or more other parameters not described above, and / or one or more parameters shown in configuration information abstract syntax (2) may not be included in other configuration information abstractions or templates. In addition, other configuration information abstractions or configuration information templates may include one or more parameters that are the same as those included in configuration information abstract syntax (2), but may have different possible values ​​than those shown in configuration information abstract syntax (2) above.

[0273] An example of configuration information based on the configuration information abstract syntax (2) with specific parameter values ​​is shown below:

[0274]

[0275] Configuration Information (2)

[0276] In some implementations, an energy event report can be an information element (IE) about energy consumption (an example of such an IE could have the title "EnergyConsReport"). Energy can be expressed in, for example, joules, and time in, for example, seconds, which makes watts equal to joules per second. The following example of using ASN.1 to describe an abstraction or template for a report (or energy event report) is called the Energy Consumption Report Abstract Syntax (1):

[0277]

[0278] Abstract syntax for energy consumption reports (1)

[0279] In some implementations, the energy consumption reporting abstract syntax (1) or energy consumption event reporting abstract may include the "ecEventType" parameter based on the value of the "ecEventType" parameter in the configuration information received from the serving cell. This parameter may be one or more of the following: "ecAboveThreshold", "ecAmountOffsetAboveThreshold", "ecInsideGroupAboveThreshold", "ecInsideGroupAmountOffsetAboveThreshold", "energyCreditAboveThreshold", "energyCreditInsideGroupAboveThreshold", "maxEnergyCreditExpired", and "maxEnergyCreditInsideGroupExpired".

[0280] Referring to the abstract syntax (1) for energy event reporting shown above, the “trpIdentity” parameter can carry information identifying a network device (e.g., a terrestrial TRP), such as the physical layer identifier of the network device. According to the abstract syntax (1) for energy event reporting, the possible values ​​of the “trpIdentity” parameter can be integers between 0 and 4095.

[0281] The “measEnergyCons” parameter can carry information indicating the measured energy consumption of network devices. According to the abstract syntax of energy event reporting (1), the possible values ​​of the “measEnergyCons” parameter can be integers between 0 and 10000000000.

[0282] The “energyCreditUse” parameter can carry information indicating the amount of energy consumed by network devices. According to the abstract syntax of energy event reporting (1), the possible values ​​of the “energyCreditUse” parameter can be integers between 0 and 10000000000.

[0283] The “carrierFrequency” parameter can carry information indicating the service carrier frequency at which network devices measure or detect a given metric. For example, the “carrierFrequency” parameter could be the carrier frequency at which energy consumption is measured or detected by a terrestrial TRP. In the energy event reporting abstract syntax (1), the value of the “carrierFrequency” parameter can be an integer, which can be understood in the unit “megahertz” (MHz). Possible values ​​for the “carrierFrequency” parameter can be integers between 1 and 10,000,000. More generally, in some energy event reporting abstractions (or templates), such a parameter represents the carrier frequency and can be expressed in units other than MHz.

[0284] It should be noted that the above-described abstract syntax (1) for energy event reporting is merely an example of an abstract syntax or template for energy event reporting, upon which energy event reports can be based. Other abstract syntax or templates for energy event reporting may include one or more other parameters not described above, and / or one or more parameters shown in the abstract syntax (1) may not be included in other abstract syntax or templates for energy event reporting. Furthermore, other abstract syntax or templates for energy event reporting may include one or more parameters that are the same as those included in the abstract syntax (1) for energy event reporting, but may have different possible values ​​than those shown in the above-described abstract syntax (1).

[0285] In some implementations, the configuration information abstract syntax for energy event reporting, namely EnergyConsEventReportConfig, can include a parameter "ecEventType" set to the value "outOfEnergyCredit". The value "outOfEnergyCredit" can indicate that the energy credit account has reached a "zero" value, that is, the network device's energy credit account is empty, or it is equivalent to the network device having exhausted its energy credit. Similarly, the energy reporting abstract syntax (1), namely EnergyConsReport, can include a parameter "ecEventType" set to the value "outOfEnergyCredit", which can indicate an "exhausted energy credit" event, that is, the network device's energy credit account is empty, or it is equivalent to the network device having exhausted its energy credit.

[0286] In some implementations, the abstract syntax for energy consumption reporting (1), namely EnergyConsReport, can include the parameter “remainingEnergyCredits”, which can carry information indicating the remaining amount of energy available to the network device. The possible values ​​of the “remainingEnergyCredits” parameter can be integers between 1 and 10000000000.

[0287] In some implementations, the abstract syntax for energy consumption reporting (1), namely EnergyConsReport, can include the parameter "networkSlice", which can carry information indicating the type of network slice. The possible values ​​of the parameter "networkSlice" are: In this context, "embb" can be a value indicating enhanced mobile broadband, "urllc" can be a value indicating ultra-reliable low-latency communication, "mmtc" can be a value indicating large-scale machine-type communication, and "ps" can be a value indicating public safety.

[0288] In some implementations, the configuration information abstract syntax (1) for energy event reporting can include a parameter “ecEvent” set to the value “remainingEnergyCreditBelowThreshold”. The value of “remainingEnergyCreditBelowThreshold” can indicate the value of an account that has reached an energy credit limit below a threshold, which can be given by “ecThreshold”. Network devices can send energy reports using the energy reporting abstract syntax (1), which can include a parameter “remainingEnergyCredits”, which can carry information indicating the remaining amount of energy credit still available to the network device. The possible values ​​of the “remainingEnergyCredits” parameter can be integers between 1 and 100000000000.

[0289] In some implementations, energy consumption reports sent by network devices to non-terrestrial network devices can also be sent to the core network for further processing to implement network-wide energy-saving strategies and other strategies related to meeting carbon neutrality goals.

[0290] In some implementations, network devices such as terrestrial TRPs can maintain an internal counter called, for example, "currentEnergyCredits," which is initially configured with a value set to "maxEnergyCredit" and decrements by an energy allowance corresponding to the amount of energy consumed by the network device (e.g., terrestrial TRP) every certain time unit (e.g., seconds). In other embodiments, network devices such as terrestrial TRPs can maintain an internal counter called, for example, "currentEnergyCredits," which is initially configured with a value set to "maxEnergyCredit" and decrements by an energy allowance corresponding to the amount of energy consumed by the network device group (e.g., terrestrial TRP group) to which the network device (e.g., terrestrial TRP) belongs every certain time unit (e.g., seconds).

[0291] It should be noted that the expression "at least one of A or B" as used herein is interchangeable with the expression "A and / or B". It refers to a list from which "A or B" or "A and B" can be selected. Similarly, the expression "at least one of A, B, or C" as used herein is interchangeable with "A and / or B and / or C" or "A, B, and / or C". It refers to a list from which: A or B or C, or A and B, or A and C, or B and C, or all of A, B, and C can be selected. The same principle applies to longer lists with the same format.

[0292] In this disclosure, when used in conjunction with the terms “comprising” or “including” in the claims and / or specification, the word “a” or “an” may mean “one”, but it also has the same meaning as “one or more,” “at least one,” and “one or more,” unless otherwise expressly stated in the content. Similarly, the word “another” may mean at least a second or more, unless otherwise expressly stated in the content.

[0293] In this disclosure, the use of terms such as "first," "second," etc., before the same term (e.g., ED or operational step) does not imply an order or sequence of the terms. For example, unless otherwise specified, "first ED" and "second ED" refer to two different EDs; similarly, unless otherwise specified, "first step" and "second step" refer to two different operational steps, but this does not mean that the first step must occur before the second step. The actual order depends on the logical relationship between the two steps.

[0294] The terms “coupled,” “coupled,” or “connected” as used herein may have several different meanings depending on the context in which they are used. For example, as used herein, the terms “coupled,” “coupled,” or “connected” may indicate that two elements or devices are directly connected to each other, or, depending on the specific context, are connected to each other by mechanical elements through one or more intermediate elements or devices.

[0295] The terms “receive,” “detect,” and “decode” used in this document can have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” can indicate that information (e.g., DCI or MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can include both “detect” and “decode,” or it can mean the same thing; for example, “receive paging” means that the paging was correctly decoded and successfully retrieved, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. For example, “not received paging” means that the receiving side attempted to detect and / or decode the paging but failed to retrieve it. The term “receive” can sometimes mean that a signal has arrived at the receiving side, but this does not necessarily mean that the information in the signal has been correctly detected and decoded. In this case, the receiving side needs to perform detection and decoding on the signal to obtain the information carried in the signal. In this scenario, “receive,” “detect,” and “decode” can represent different processes by which the receiving side obtains information.

[0296] It should be understood that one or more steps in the methods of the embodiments provided herein can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmitting unit or transmitting module. A signal can be received by a receiving unit or receiving module. A signal can be processed by a processing unit or processing module. The corresponding units / modules can be hardware, software, or a combination thereof. For example, one or more units / modules can be integrated circuits, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). It should be understood that if these modules are software, the processor can search for all or part of these modules as needed, search for them individually or in combination for processing, and support single-instance or multi-instance retrieval, and these modules themselves can include instructions for further deployment and instantiation. Although combinations of features are shown in the illustrated embodiments, not all features need to be combined to achieve the advantages of the various embodiments of this disclosure. In other words, a system or method designed according to embodiments of this disclosure does not necessarily include all features shown in any of the figures or all parts schematically shown in the figures. Furthermore, selected features of one exemplary embodiment can be combined with selected features of other exemplary embodiments.

[0297] Although this disclosure has been described with reference to illustrative embodiments, this description is not intended to be limiting. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of this disclosure, will be apparent to those skilled in the art upon reference to this specification. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A method for network management, characterized in that, include: The first network device receives configuration information from the second network device, wherein the configuration information is used to configure the first network device to determine whether to send a report indicating that a power consumption event has occurred.

2. The method according to claim 1, characterized in that, Also includes: Based on the configuration information, determine whether one or more conditions indicating that the power consumption event has occurred are met.

3. The method according to claim 2, characterized in that, Also includes: The report is sent when one or more of the conditions indicating that the power consumption event has occurred are met.

4. The method according to any one of claims 1 to 3, characterized in that, The configuration information includes at least one of the following: Information used to identify the type of power consumption event to be detected in the first network device; Information indicating a threshold related to the type of the power consumption event, which will be compared with detection data to determine whether the power consumption event has occurred; Information indicating the offset of the measured power consumption exceeding the threshold to determine the power consumption event; Information indicating the duration of the power consumption event that triggered the sending of the report; Information indicating whether the first network device is allocated to send the report when the power consumption event has occurred; Information indicating the type of measurement quantity of the power consumption to be reported; The information indicates whether the network device group of the first network device is allocated to send the report when the power consumption event has occurred; or This indicates the information of the reporting device in the network device group that is assigned to send the report when the power consumption event has occurred.

5. The method according to claim 4, characterized in that, The type of the power consumption event to be detected is related to at least one of the following: Power consumption exceeds the threshold; The offset by which power consumption exceeds the threshold; The power consumption of the network device group, including the first network device, exceeds a threshold; or The offset of the power consumption of the network device group including the first network device exceeding the threshold.

6. The method according to any one of claims 1 to 5, characterized in that, The report includes at least one of the following: Information identifying the first network device; The identifier includes information about the network device group of the first network device; Information indicating the type of power consumption event measured by the first network device; Information indicating the amount of power consumed as measured by the first network device; or Information indicating the service carrier frequency detected by the first network device.

7. The method according to any one of claims 1 to 6, characterized in that, At least one of the following must be met: The first network device serves the first coverage area; or The second network device corresponds to the second coverage area.

8. The method according to claim 7, characterized in that, At least one of the following must be met: The first coverage area is smaller than the second coverage area; At least a portion of the first coverage area is within the second coverage area; or The first coverage area overlaps with the second coverage area.

9. A method, characterized in that, include: The first network device receives configuration information from the second network device, wherein the configuration information includes a power consumption command, which indicates at what power the first network device should transmit, the duration for which the power is turned on or off, and the functions that the first network device should turn on or off.

10. The method according to claim 9, characterized in that, The configuration information, including the power consumption command, is received in the binary sequence of the reference signal sent by the second network device.

11. The method according to claim 10, characterized in that, The binary sequence of the reference signal includes: One or more bits that indicate at what power the first network device should transmit; One or more bits indicating the duration for which the power is turned on or off; One or more bits indicating one or more functions that the first network device should turn on or off.

12. The method according to claim 10 or 11, characterized in that, The binary sequence of the reference signal includes: One or more bits indicating the power-on function, and the same number of bits not included in the power-off function; or One or more bits indicating the power-off function, and the same number of bits not included in the power-on function.

13. The method according to claim 9, characterized in that, The configuration information, including the power consumption command, is received from the Radio Resource Control (RRC) protocol signaling of the second network device.

14. The method according to claim 9, characterized in that, The configuration information, including the power consumption command, is received from the downlink control information (DCI) of the second network device.

15. The method according to claim 14, characterized in that, Also includes: The first network device detects a control channel carrying control information messages from the second network device, the control information messages carrying the configuration information.

16. The method according to claim 15, characterized in that, The control information message includes a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI).

17. The method according to claim 15, characterized in that, The control channel is a dedicated control channel for the first network device.

18. The method according to any one of claims 9 to 17, characterized in that, At least one of the following must be met: The first network device serves the first coverage area; or The second network device serves the second coverage area.

19. The method according to claim 18, characterized in that, At least one of the following must be met: The first coverage area is smaller than the second coverage area; At least a portion of the first coverage area is within the second coverage area; or The first coverage area overlaps with the second coverage area.

20. The method according to any one of claims 1 to 8 or 9 to 19, characterized in that, The first network device is the first ground transmission and reception point (T-TRP).

21. The method according to any one of claims 1 to 8 or 9 to 20, characterized in that, The second network device is a non-terrestrial transmission receiving point (NT-TRP).

22. The method according to claim 21, characterized in that, The first network device sends the report to the second network device or another NT-TRP that is different from the NT-TRP and acts as the second network device.

23. The method according to claim 22, characterized in that, The second network device and the other NT-TRP: Located on the same orbit; or Located on different tracks, each track provides coverage for the first network device.

24. A network device, characterized in that, include: processor; A computer-readable medium having stored thereon computer-executable instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 8 and 9 to 23.

25. A method for network management, characterized in that, include: The first network device sends configuration information to the second network device and the first serving cell, wherein the configuration information is used to configure the second network device to determine whether to send a report indicating that a power consumption event has occurred in the network served by the second network device.

26. The method according to claim 25, characterized in that, Also includes: The second network device receives the report when it determines, based on the configuration information, that one or more conditions indicating that the power consumption event has occurred are met.

27. The method according to claim 25 or 26, characterized in that, The configuration information includes at least one of the following: Information used to identify the type of power consumption event to be detected in the second network device; Information indicating a threshold related to the type of the power consumption event, which will be compared with detection data to determine whether the power consumption event has occurred; Information indicating the offset of the measured power consumption exceeding the threshold to determine the power consumption event; Information indicating the duration of the power consumption event that triggered the sending of the report; Information indicating whether the second network device is allocated to send the report when the power consumption event has occurred; Information indicating the type of power consumption measurement to be reported; Information indicating whether a network device group in the network, including the second network device, is allocated to send the report when the power consumption event has occurred; or This indicates the information of the reporting device in the network device group that is assigned to send the report when the power consumption event has occurred.

28. The method according to claim 27, characterized in that, The type of the power consumption event to be detected is related to at least one of the following: Power consumption exceeds the threshold; The offset by which power consumption exceeds the threshold; The power consumption of the network device group, including the first network device, exceeds a threshold; or The offset of the power consumption of the network device group including the first network device exceeding the threshold.

29. The method according to any one of claims 25 to 28, characterized in that, The report includes at least one of the following: Information identifying the second network device; Information identifying the network device group in the network including the second network device; Information indicating the type of power consumption event measured by the second network device; Information indicating the amount of power consumed as measured by the second network device; or Information indicating the service carrier frequency detected by the second network device.

30. A method, characterized in that, include: The first serving cell sends configuration information to the second network device, wherein the configuration information includes a power consumption command, which indicates at what power the second network device should transmit, the duration for which the power is turned on or off, and the functions that the second network device should turn on or off.

31. The method according to claim 30, characterized in that, The configuration information, including the power consumption command, is received in the binary sequence of the reference signal sent by the first network device.

32. The method according to claim 30, characterized in that, The binary sequence of the reference signal includes: One or more bits instructing the second network device on what power to transmit; One or more bits indicating the duration for which the power is turned on or off; One or more bits that indicate one or more functions that the service network device should turn on or off.

33. The method according to claim 31 or 32, characterized in that, The binary sequence of the reference signal includes: One or more bits indicating the power-on function, and the same number of bits not included in the power-off function; or One or more bits indicating the power-off function, and the same number of bits not included in the power-on function.

34. The method according to claim 30, characterized in that, The first network device sends the configuration information, including the power consumption command, in the Radio Resource Control (RRC) protocol signaling.

35. The method according to claim 30, characterized in that, The first network device sends the configuration information, including the power consumption command, in the downlink control information (DCI).

36. The method according to claim 35, characterized in that, The control information message includes a Cyclic Redundancy Check (CRC) scrambled with the Radio Network Temporary Identifier (RNTI).

37. The method according to any one of claims 25 to 36, characterized in that, The second network device is the first ground transmission receiving point (T-TRP).

38. The method according to claim 37, characterized in that, The first network device is a non-terrestrial transmission and receiving point (NT-TRP).

39. The method according to claim 37, characterized in that, The second network device sends the report to the first network device or another NT-TRP that is different from the NT-TRP and acts as the first network device.

40. The method according to claim 39, characterized in that, The first network device and the other NT-TRP: Located on the same orbit; or Located on different tracks, each track provides coverage for the second network device.

41. A network device, characterized in that, include: processor; A computer-readable medium having stored thereon computer-executable instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 25 to 29 and 30 to 40.

42. A non-transitory computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by the processor of the device, cause the device to perform the method of any one of claims 1 to 8, 9 to 24, 25 to 29, or 30 to 40.

Images