3GPP networking considering energy-related information

Abstract

One aspect of the invention provides a method, a computer readable medium, and an apparatus. The method includes receiving first information from a first network entity or function. The first information is generated by the first network entity or function based on energy-related information. The method includes triggering one or more session management processes based on the first information or based on the determination of the energy-related information.

Description

[0001] Cross-reference to related applications

[0002] This invention claims the benefit of U.S. Provisional Application No. 63 / 594,975, filed November 1, 2023, entitled “3GPP networking considering energy-related information,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This invention relates generally to wireless communication, and more specifically to 3GPP networking technologies that take into account energy-related information. Background Technology

[0004] The statements in this section are provided only as background information in relation to the present invention and do not constitute prior art.

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies, supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted by various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. 5G New Radio (NR) is one such telecommunications standard. 5G NR is part of the Continuous Evolution of Mobile Broadband initiative proposed by the Third Generation Partnership Project (3GPP), designed to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things, IoT), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology still requires further improvement. These improvements may also apply to other multiple access technologies and the telecommunications standards that adopt them. Summary of the Invention

[0007] The following is a simplified overview of one or more aspects to provide a basic understanding of them. This summary is not a comprehensive overview of all proposed aspects, nor is it intended to identify key elements or essential components of all aspects, or to define the scope of any or all aspects. Its sole purpose is to introduce some concepts of one or more aspects in a simplified form as an introduction to the more detailed description that follows.

[0008] In one aspect of the invention, a method, a computer-readable medium, and an apparatus are provided. The method includes receiving first information from a first network entity or function. The first information is generated by the first network entity or function based on energy-related information. The method includes triggering one or more session management procedures based on the first information or a determination result based on energy-related information.

[0009] To achieve the foregoing and related objectives, the one or more aspects include the features detailed below and specifically pointed out in the claims. The following description and accompanying drawings illustrate certain exemplary features of the one or more aspects. However, these features merely indicate a few ways in which the principles of each aspect are applied, and this description is intended to cover all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is an example diagram illustrating a wireless communication system and access network.

[0011] Figure 2 This is a schematic diagram illustrating the communication between a base station and user equipment (UE) in an access network.

[0012] Figure 3An example logical architecture for a distributed access network is shown.

[0013] Figure 4 An example physical architecture of a distributed access network is shown.

[0014] Figure 5 This is an example diagram showing a time slot centered on DL.

[0015] Figure 6 This is an example diagram showing a time slot centered on UL.

[0016] Figure 7 is an example diagram of a wireless communication system including a base station and a UE.

[0017] Figure 8 is an example diagram for adjusting the path structure of the user plane (UP).

[0018] Figure 9 is a flowchart of 3GPP networking based on energy-related information. Detailed Implementation

[0019] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described in this invention can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these specific details can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0020] Various aspects of a telecommunications system will now be presented with reference to various devices and methods. These devices and methods are described in the following detailed embodiments and illustrated in the accompanying drawings through various frames, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0021] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this invention. One or more processors in the processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description languages, or something else.

[0022] Therefore, in one or more example aspects, the described function can be implemented using hardware, software, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or code on a computer-readable medium, or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium accessible by a computer. For example, and without limitation, such computer-readable media can include: random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of computer-readable media of the foregoing types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0023] Figure 1This is an example diagram illustrating a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes: base station 102, UE 104, Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0024] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network, E-UTRAN) can interact with EPC 160 via backhaul link 132 (e.g., SI interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interact with core network 190 via backhaul link 184. In addition to other functions, base station 102 may perform one or more of the following functions: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access stratum (NAS) message distribution, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, location, and warning message delivery. Base stations 102 may communicate directly or indirectly (e.g., via EPC 160 or core network 190) with each other via backhaul link 134 (e.g., X2 interface). Backhaul link 134 may be wired or wireless.

[0025] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolved Node B (HeNB) that can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from base station 102 to UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 may use a spectrum with a bandwidth of up to 7 MHz per carrier (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.), allocated by carrier aggregation up to a total of Yx MHz (x component carriers) used for transmission in each direction. Carriers may be adjacent to each other or may not be adjacent. Carrier allocation may be asymmetrical with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0026] Some UEs 104 can communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 can use DL / UL WWAN spectrum. D2D communication links 158 can use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0027] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 using 5 GHz unlicensed spectrum. When communicating using unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0028] Cell 102' can operate on licensed and / or unlicensed spectrum. When operating on unlicensed spectrum, cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as used by Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0029] Base station 102 (whether it is a small cell 102' or a large-area (e.g., a macro base station)) may include: eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in the conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies when communicating with UE 104. When gNB 180 operates at mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the RF spectrum in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. The ultra-high frequency (SHF) band extends between 3 GHz and 30 GHz, also known as centimeter waves. Communication using mmW / near mmW radio frequency bands (e.g., 3 GHz to 300 GHz) has extremely high path loss and short range. mmW base station 180 can utilize beamforming 182 with UE 104 to compensate for the extremely high path loss and short range.

[0030] Base station 180 can transmit beamformed signals to UE 104 in one or more transmit directions 108a. UE 104 can receive beamformed signals from base station 180 in one or more receive directions 108b. UE 104 can also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 can receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 can perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 can be the same or different. The transmit and receive directions of UE 104 can be the same or different.

[0031] EPC 160 may include: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides carrier and connection management. All user Internet Protocol (IP) packets are transmitted through the Serving Gateway 166 (which itself is connected to the PDN Gateway 172). PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP service 176 may include the Internet, enterprise intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to allocate MBMS traffic to base station 102 in a Multicast Broadcast Single Frequency Network (MBSFN) area belonging to a broadcast-specific service, and can be responsible for session management (start / stop) and collecting eMBMS related billing information.

[0032] The core network 190 may include: Access and Mobility Management Function (AMF) 192, other AMFs 193, Location Management Function (LMF) 198, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and the core network 190. Typically, SMF 194 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP service 197. IP service 197 may include the Internet, enterprise intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0033] A base station may also be referred to as a gNB, Node B, eNB, access point, basic transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended serviceset (ESS), transmit reception point (TRP), or any other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include: cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or any other suitable term.

[0034] Although this invention may refer to 5G New Radio (NR), it is applicable to other similar fields, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communication (GSM), or other wireless / radio access technologies.

[0035] Figure 2 is a block diagram of communication between base station 210 and UE 250 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 275. Controller / processor 275 implements Layer 3 and Layer 2 functions. Layer 3 includes the radio resource control (RRC) layer, and Layer 2 includes the packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, and medium access control (MAC) layer. The controller / processor 275 provides: RRC layer functions associated with broadcast system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing from TBs to MAC SDUs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0036] The transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 216 processes the mapping to the quadrature phase-shift keying (constellation) based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. The individual streams can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse fast fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 274 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate can be derived based on the reference signal and / or channel condition feedback transmitted by UE 250. The individual spatial streams can then be provided to different antennas 220 via separate transmitters 218TX. Each transmitter 218TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0037] At UE 250, each receiver 254RX receives signals through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 256. The TX processor 268 and the RX processor 256 implement Layer 1 functions associated with various signal processing functions. The RX processor 256 can perform spatial processing on this information to recover any spatial stream destined for UE 250. If multiple spatial streams are destined for UE 250, they can be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes individual OFDM symbol streams for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 210. These soft decisions can be based on a channel estimate calculated by channel estimator 258. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 210 on the physical channel. This data and control signals are then provided to controller / processor 259, which implements the functions of layer 3 and layer 2.

[0038] The controller / processor 259 can be associated with a memory 260 that stores program code and data. The memory 260 may be referred to as a computer-readable medium. In the UL, the controller / processor 259 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0039] Similar to the functions described in the DL transmission combined with base station 210, controller / processor 259 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement result reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of TBs to MAC SDUs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0040] The channel estimate derived by channel estimator 258 from the reference signal or feedback transmitted by base station 210 can be used by TX processor 268 to select appropriate coding and modulation schemes and facilitate spatial processing. The spatial stream generated by TX processor 268 can be provided to different antennas 252 via individual transmitters 254TX. Each transmitter 254TX can use the corresponding spatial stream to modulate an RF carrier for transmission. UL transmission is processed at base station 210 in a manner similar to that described in conjunction with the receiver function at UE 250. Each receiver 218RX receives signals through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides this information to RX processor 270.

[0041] The controller / processor 275 can be associated with a memory 276 that stores program code and data. The memory 276 may be referred to as a computer-readable medium. In the UL, the controller / processor 275 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 250. IP packets from the controller / processor 275 can be provided to the EPC 160. The controller / processor 275 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0042] NR can refer to a radio configured to operate under a new air interface (e.g., an air interface other than Orthogonal Frequency Divisional Multiple Access (OFDMA)) or a fixed transport layer (e.g., other than Internet Protocol (IP)). NR can utilize OFDM with a cyclic prefix (CP) on both the uplink and downlink, and can include support for half-duplex operation using time division duplexing (TDD). NR can include: enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., exceeding 80 MHz), mmW targeting high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) targeting non-backward-compatible MTC technologies, and / or mission-critical services targeting ultra-reliable low-latency communication (URLLC).

[0043] It can support a single component carrier bandwidth of 100 MHz. In one example, an NR resource block (RB) can span 12 subcarriers, where the subcarrier bandwidth is 60 kHz for a duration of 0.25 ms, or 30 kHz for a duration of 0.5 ms (similarly, a 50 MHz bandwidth is 15 kHz SCS for a duration of 1 ms). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR slots), each subframe being 10 ms long. Each slot can indicate the link direction of data transmission (i.e., DL or UL), and the link direction of each slot can be dynamically switched. Each slot can include DL / UL data as well as DL / UL control data. The UL and DL slots of NR can be referenced as follows. Figure 5 and Figure 6 To describe in more detail.

[0044] NR RAN can include a central unit (CU) and a distributed unit (DU). NR BS (e.g., gNB, 5G Node B, Node B, Transmission Reception Point (TRP), AP) can correspond to one or more BSs. NR cells can be configured as access cells (ACells) or data-only cells (DCells). For example, the RAN (e.g., central unit or distributed unit) can configure these cells. DCells can be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or handover. In some cases, DCells may not transmit synchronization signals (SS); in others, they may transmit SS. NR BSs can transmit downlink signals indicating the cell type to the UE. Based on the cell type indication, the UE can communicate with the NR BS. For example, the UE can determine the NR BS used for considering cell selection, access, handover, and / or measurement based on the indicated cell type.

[0045] Figure 3An example logical architecture of a distributed RAN 300 according to various aspects of the present invention is shown. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be the central unit (CU) of the distributed RAN. The backhaul interface of the next-generation core network (NG-CN) 404 may terminate at the ANC. The backhaul interface of the adjacent next-generation access (NG-AN) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as BS, NR BS, Node B, 5G NB, AP, or some other term). As mentioned above, TRPs can be used interchangeably with "cell".

[0046] TRP 308 can be a distributed unit (DU). A TRP can be connected to one ANC (ANC302) or more ANCs (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service-dedicated ANC deployments, the TRP can be connected to more than one ANC. A TRP can include one or more antenna ports. A TRP can be configured to provide traffic to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0047] The local architecture of the distributed RAN 300 can be used to illustrate a fronthaul definition. This architecture can be defined to support fronthaul solutions across different deployment types. For example, the architecture can be based on transmit network capabilities (e.g., bandwidth, latency, and / or jitter). The architecture can share features and / or components with LTE. Depending on various aspects, the next-generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share common fronthaul for both LTE and NR.

[0048] This architecture enables collaboration between and within TRPs 308. For example, collaboration can be pre-configured within and / or across TRPs via ANC 302. Depending on the circumstances, inter-TRP interfaces may not be required or present.

[0049] Depending on various factors, the dynamic configuration of the split logic function can exist within the architecture of the distributed RAN 300. PDCP, RLC, and MAC protocols can be adaptively placed at the ANC or TRP.

[0050] Figure 4An example physical architecture of a distributed RAN 400 according to various aspects of the present invention is shown. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functions may be offloaded (e.g., to advanced wireless services (AWS)) to handle peak capacity. A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be located closer to the network edge. A distributed unit (DU) 506 may host one or more TRPs. The DU may be located at the network edge with radio frequency (RF) capabilities.

[0051] Figure 5 This is an example diagram 500 illustrating a DL-centered time slot. The DL-centered time slot may include a control section 502. The control section 502 may exist in the initial or beginning portion of the DL-centered time slot. The control section 502 may include various scheduling and / or control information corresponding to the various portions of the DL-centered time slot. In some configurations, the control section 502 may be a Physical DL Control Channel (PDCCH), as shown in... Figure 5 As indicated in the text. The DL-centric time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 504 may include communication resources used to transmit DL data from a scheduling entity (e.g., a UE or BS) to a lower-level entity (e.g., a UE). In some configurations, the DL data portion 504 may be a physical DL-shared channel (PDSCH).

[0052] The DL-centered time slot may also include a common UL section 506. The common UL section 506 may sometimes be referred to as a UL burst, a common UL burst, and / or various other suitable terms. The common UL section 506 may include feedback information corresponding to the various other sections of the DL-centered time slot. For example, the common UL section 506 may include feedback information corresponding to the control section 502. Non-limiting examples of feedback information may include: ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The common UL section 506 may include additional or alternative information, such as information related to the random access channel (RACH) procedure, scheduling requests (SR), and various other suitable types of information.

[0053] like Figure 5 As illustrated, the end of the DL data portion 504 may be temporally separated from the beginning of the common UL portion 506. This time separation may sometimes be referred to as a gap, guard period, guard interval, and / or various other suitable terms. This separation provides the time for switching from DL communication (e.g., receiving operations of a lower-level entity (e.g., UE)) to UL communication (e.g., transmitting operations of a lower-level entity (e.g., UE)). Those skilled in the art will understand that the foregoing is merely one example of a DL-centric time slot, and alternative structures with similar features may exist without departing from the aspects described in this invention.

[0054] Figure 6 Figure 600 illustrates a UL-centered time slot. A UL-centered time slot may include a control section 602. The control section 602 may be present in the initial or beginning portion of the UL-centered time slot. Figure 6 The control section 602 in the above reference can be similar to the one mentioned above. Figure 5 The control portion 502 is described. The UL-centric time slot may also include a UL data portion 604. The UL data portion 604 may sometimes be referred to as the payload of the UL-centric time slot. The UL portion can refer to the communication resource used to transmit UL data from a lower-level entity (e.g., the UE) to a scheduling entity (e.g., the UE or the BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

[0055] like Figure 6As illustrated, the end of control section 602 may be temporally separated from the beginning of UL data section 604. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This separation provides time for switching from DL communication (e.g., receiving operations of a scheduling entity) to UL communication (e.g., transmitting operations of a scheduling entity). UL-centric time slots may also include common UL section 606. Figure 6 The public UL section 606 in the above reference can be similar to the above. Figure 5 The common UL portion 506 is described. The common UL portion 606 may additionally or alternatively include information regarding the channel quality indicator (CQI), the sounding reference signal (SRS), and various other suitable types of information. Those skilled in the art will understand that the foregoing is merely one example of a UL-centric time slot, and alternative structures with similar features may exist without departing from the aspects described in this invention.

[0056] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signaling. Practical applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Everything (IoE) communication, Internet of Things (IoT) communication, mission-critical meshes, and / or various other suitable applications. Generally, sidelink signaling can refer to a signal transmitted from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless LANs that typically use unlicensed spectrum).

[0057] Figure 7 is an example diagram of a wireless communication system including a base station and a UE. In this example, user equipment 704 is connected to base station 702 on cell 706.

[0058] In 3GPP networks, energy consumption is a factor that needs to be considered. In this case, energy-related information can be used to understand energy consumption.

[0059] In some embodiments, energy-related information may include one or more of the following: 1) Energy consumption; 2) Energy efficiency; 3) Carbon emissions; 4) Energy.

[0060] In some embodiments, energy consumption may include non-renewable energy consumption, renewable energy consumption, or a combination of both. Accordingly, energy may include non-renewable energy, renewable energy, or a combination of both. For example, renewable energy (green energy) may include wind power, solar energy, etc., while non-renewable energy (grey energy) may include coal energy, oil energy, natural gas energy, etc.

[0061] Energy-related information can be collected within a predetermined scope. For example, energy-related information can be collected by network slice set, network entity set, or UE set. A network slice set can contain one network slice or a group of network slices, a network entity set can contain one network entity or a group of network entities, and a UE set can contain one UE or a group of UEs. A network entity can be a 5G network unit or a 6G network unit.

[0062] Network slicing is a technology that divides a physical network into multiple virtual end-to-end networks, enabling the creation of multiple logically separate virtual networks on a shared physical network infrastructure. Each network slice represents an independent virtual network, where all components within the slice are logically separated from components in other slices. Network slicing allows for flexible configuration based on the needs of different users or services, meeting diverse network requirements across various business scenarios.

[0063] Monitoring and Disclosure of Energy-Related Information: To optimize energy use, such as reducing the total energy consumption for providing communication services or reducing overall carbon emissions associated with these services, one or more network units / functions (including Policy Control Functions (PCFs)) need to monitor, measure, and track this information. Based on the received information (which may be called initial information), one or more network units / functions can check whether energy-related criteria are met (e.g., whether energy efficiency exceeds a certain threshold). If the criteria are not met, relevant processes can be triggered to change the network configuration so that the criteria change from "not met" to "met". Furthermore, energy-related information may need to be disclosed (actively or passively) to other network units / functions. For example, a PCF can disclose energy-related information to a Session Management Function (SMF).

[0064] Network slicing related policy control

[0065] As previously mentioned, energy-related information can be collected at the network slice level. Network slices controlled by PDU session-related policies can support functions such as collecting, monitoring, tracking, measuring, reporting, and notifying energy-related information, as well as updating policies based on this information. In some embodiments, updates related to reporting or notification can be sent to the UE, such as UE 704.

[0066] Operator network elements, such as PCF, Application Function (AF), Network Data Analytics Function (NWDAF), SMF, Mobility Management Function (AMF), Charging Function (CHF), Network Repository Function (NRF), or others, can collect and / or monitor energy-related information of network slices in PDU sessions. Additionally, a new 3GPP network entity—the Energy Function (EF)—can be introduced to collect and / or monitor energy-related information of network slices in PDU sessions. The EF can then transmit this energy-related information to the PCF. Reporting and / or notification of energy-related information of network slices in PDU sessions can be exchanged bidirectionally or unidirectionally between the operator network entity, the AF, and the slice service provider.

[0067] Carrier network units (including but not limited to PCF, AF, NWDAF, SMF, AMF, CHF, EF, and NRF) can monitor energy-related information of network slices and ensure that one or more of the following criteria are met: 1) Slices used, selected, or configured for the UE: (a) Lower carbon emissions; (b) Higher proportion of renewable energy; (c) Lower energy consumption; and / or (d) Higher energy efficiency; and / or 2) Energy-related information does not exceed or falls below a specified threshold, for example: (a) The carbon emissions of a network slice are greater than or equal to (>=) the threshold “X”; (b) The proportion of renewable energy is less than or equal to (<=) the threshold “Y”; (c) The value after processing (calculating) energy-related information is greater than or equal to (>=) the threshold “Z”, or less than or equal to (<=) the threshold “Z”; and / or (d) Any combination of the above conditions.

[0068] In addition, if any of the following conditions are met or not met (i.e., energy-related standards / requirements), the network may take one or more measures to optimize energy use, such as reducing carbon emissions or increasing the proportion of renewable energy, for example: (1) If the carbon emissions of the PDU session slice currently being used by the UE are higher than those of the unused available slice, the UE can switch to the latter.

[0069] (2) If the renewable energy used by the PDU session slice that the UE is using is less than that used by the unused available slice, the UE can switch to the latter.

[0070] (3) If the carbon emissions of the PDU session slice that the UE is using are equal to or higher than the threshold (X), while the carbon emissions of the unused available slices are lower than or equal to the threshold, the UE can switch to the latter.

[0071] (4) If the renewable energy used by the PDU session slice that the UE is using is equal to or lower than the threshold (Y), while the renewable energy emissions of the unused available slice are higher than or equal to the threshold, the UE can switch to the latter.

[0072] (5) If the carbon emissions of the network entity that the UE is using (e.g., the User Plane Function (UPF) of the PDU session) are higher than those of the unused available network entity, the UE may switch to using the latter.

[0073] (6) If a network entity that the UE is using (e.g., the UPF of a PDU session) uses less renewable energy than an unused available network entity, the UE may switch to using the latter.

[0074] (7) If the carbon emissions of a network entity that the UE is using (e.g., the UPF of a PDU session) are equal to or higher than the threshold (X), while the carbon emissions of an unused available network entity are lower than or equal to the threshold, the UE may switch to using the latter.

[0075] (8) If the renewable energy used by a network entity that the UE is using (e.g., the UPF of a PDU session) is equal to or lower than the threshold (Y), while the renewable energy used by an unused available network entity is higher than or equal to the threshold, the UE may switch to using the latter.

[0076] In these cases, network entities (such as SMFs) can take one or more measures to facilitate the switch and optimize the use of carbon emissions or renewable energy. These actions may include: (1) Initiate the network-initiated Packet Data Unit (PDU) session release procedure. When the UE re-initiates the PDU session establishment procedure, one or more UPF nodes associated with the new PDU session will be different from the UPF nodes of the released PDU session, resulting in the adjustment of the User Plane (UP) path.

[0077] (2) Initiate a network-initiated PDU session modification process. During this process, one or more UPF nodes associated with the PDU session before modification will be different from the UPF nodes after modification, which will also lead to the adjustment of the UP path.

[0078] In other words, in order to enhance energy-related operations and processes, such as saving energy or improving energy efficiency, the UP path of a PDU session can be adjusted according to predetermined energy-related standards / requirements.

[0079] In summary, network units / functions (e.g., PCF, AF, NWDAF, SMF, AMF, CHF, EF, NRF, etc.) can monitor / collect / acquire (whether actively or passively) energy-related information of one or more network slices associated with UPFs in the UE's PDU session. When the energy-related target conditions are not met, the network unit / function (which may be the SMF itself or other network units / functions besides the SMF, such as PCF, AF, NWDAF, AMF, CHF, EF, NRF) can trigger the SMF to initiate a PDU session release process or a PDU session modification process based on the energy-related information it monitors / collects / acquires.

[0080] Furthermore, thresholds related to energy-related information (e.g., X and Y values) can be determined based on one or more of the following factors: (1) Carrier policies, such as Service Level Agreements (SLAs) associated with specific network slices; (2) Input from the service provider, including the SLA; (3) Preferences or values ​​related to energy information indicated by the UE; (4) User input, for example, the user agrees or prefers to use slices with carbon emissions ≤ X; (5) Subscription information, which may specify the use of slices with renewable energy values ​​≥ Y.

[0081] Figure 8 is a schematic diagram of an example architecture 800 used for adjusting user plane paths. Figure 8 As shown, a PDU session can start from UE 804, pass through RAN 808, some UPFs (such as UPF1 810, UPF2 812-a and UPF3 814), and finally reach the data network (DN) 802 (such as the Internet) to establish a data link.

[0082] During UP path adjustments, the endpoints of the path (specifically, UE 804 and DN 802) remain unchanged because the primary function of a PDU session is to relay data between them. However, intermediate nodes (such as RAN 808 and UPF) may change. For example, the path may switch from using UPF2 812-a to using UPF2 812-b. Alternatively, the path may be rerouted from a high-power base station to a low-power base station.

[0083] In this context, replacing the UPF essentially means switching to a different router, such as one with lower energy consumption. In 3GPP networks, considering energy-related information, the networking process is fundamentally about selecting the optimal routing path between endpoints. In other words, the selection of which UPF / router to use is based on energy-related information, with the aim of meeting predetermined energy-related standards / requirements.

[0084] Energy-related information may include absolute energy consumption, energy efficiency (e.g., gigabytes (GB) of data transmitted per unit of energy), and carbon emissions. Pre-defined energy-related standards / requirements may prioritize routers with lower energy consumption, higher energy efficiency, or lower carbon emissions. Furthermore, the type of energy (renewable versus non-renewable energy; for example, we might require a non-renewable energy ratio greater than 50%) is also an important factor to consider.

[0085] Energy-related information can be monitored or measured by network slice, network entity (e.g., UPF), or UE. Optimizing energy usage may require considering the entire path from UE 804 to DN 802.

[0086] As shown in Figure 8, SMF 806 can establish a PDU session between UE 804 and DN 802 through interactive control / signaling between UE 804 and SMF 806.

[0087] Furthermore, path adjustment decisions are typically made by network functions such as the SMF 806 or other network elements. In other words, the SMF 806 can proactively monitor energy-related information and decide whether to make adjustments based on that information. Alternatively, another network element (such as the EF or PCF) can monitor energy-related information and trigger the release or modification of a PDU session initiated by the SMF 806 by sending a notification message generated based on energy-related information to the SMF 806. The SMF 806 can then passively execute instructions to adjust the path.

[0088] For example, as shown in Figure 8, assuming UPF2 812-a uses 100% grey energy and UPF2' 812-b uses 50% green energy (e.g., solar energy), SMF 806 can adjust its path accordingly based on energy-related information. At night, when no solar energy is available for UPF2' 812-b, either UPF2 812-a or UPF2' 812-b can be used depending on other factors. However, during the day, when the solar panels in UPF2' 812-b begin operating, conditions requiring carbon emission reduction are triggered, at which point the system switches from UPF2 812-a to UPF2' 812-b to utilize renewable energy.

[0089] Policy controls can be implemented on a per-network-slice basis for PDU sessions, enabling customized energy management. For example, ensuring that the carbon emissions of a network slice do not exceed a threshold, or that its renewable energy usage rate is higher than a certain percentage.

[0090] When a certain condition is triggered (e.g., carbon emissions exceed the limit), SMF 806 can release and modify the PDU session to have a more favorable UPF. This process ensures that the UP path is optimized based on energy-related criteria.

[0091] Energy-related standards / requirements can come from various sources. For example, service providers such as power companies can provide energy-related standards / requirements, which operators can use to make decisions. On the other hand, users can also indicate their preferences for carbon emissions or energy efficiency, which are stored in a subscription information database and taken into account during network optimization.

[0092] Figure 9 is a 3GPP networking flowchart 900 based on energy-related information. In block 902, first information is received from a first network entity or function. The first information may be generated by the first network entity or function based on energy-related information. In one embodiment, the first network entity or function may collect, track, or measure energy-related information received from a second network entity or function. The first or second network entity or function may be a Policy Control Function (PCF), Energy Function (EF), Application Function (AF), or Network Data Analytics Function (NWDAF).

[0093] In block 904, based on the determination result of the first information or energy-related information, one or more session management procedures are triggered. In some embodiments, the one or more session management procedures may include a packet data unit (PDU) session release procedure or a PDU session modification procedure. The PDU session release procedure or PDU session modification procedure is triggered to adjust the user plane (UP) path of the PDU session.

[0094] In some embodiments, the energy-related information may include at least one of: energy consumption-related information, energy efficiency-related information, carbon emission-related information, or energy-related information. In one embodiment, energy consumption may include non-renewable energy consumption, renewable energy consumption, or a combination of non-renewable and renewable energy consumption. In some embodiments, energy may include non-renewable energy, renewable energy, or a combination of non-renewable and renewable energy.

[0095] In some embodiments, the first information may also be generated based on a determination result. The determination result may be generated based on whether energy-related criteria associated with energy-related information are met. For example, energy-related criteria may include: energy consumption being higher than, equal to, or lower than a first value; energy efficiency being higher than, equal to, or lower than a second value; carbon emissions being higher than, equal to, or lower than a third value; and renewable or non-renewable energy being higher than, equal to, or lower than a fourth value.

[0096] In some embodiments, energy-related criteria may be determined by: (1) operator policies; (2) service provider inputs; (3) preferences or values ​​associated with energy-related information indicated by user equipment; (4) user inputs; or (5) subscription information.

[0097] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of the boxes in this process / flowchart can be rearranged. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of the boxes in an exemplary order and are not intended to limit the scope to the specific order or hierarchy presented.

[0098] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined in the invention can be applied to other aspects. Therefore, the claims are not intended to limit the invention to the aspects shown, but are to be accorded the full scope consistent with the written claims, wherein, unless expressly stated otherwise, reference to an element in the singular does not mean "one and only one," but rather "one or more." The term "exemplary" as used in this invention is intended to mean "serving as an example, instance, or illustration." Any aspect described as "exemplary" in this invention is not necessarily to be construed as preferred or more advantageous than other aspects. Unless specifically stated otherwise, the term "some" means one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described herein that are known to those skilled in the art or will be known thereafter are expressly incorporated by reference and are covered by the claims. Furthermore, regardless of whether such disclosure is expressly stated in the claims, nothing disclosed herein is intended to be exclusive to the public. The terms "module", "mechanism", "element", "device", etc., cannot be used as substitutes for the term "means". Thus, unless the phrase "means for" is used to expressly state a claim element, no claim element is to be interpreted as means plus function.

Claims

1. A wireless communication method, comprising: Receive first information from a first network entity or function, wherein the first information is generated by the first network entity or function based on energy-related information. as well as One or more session management processes are triggered based on the first information or the determination result based on the energy-related information.

2. The method as described in claim 1, wherein, The first network entity or function collects, tracks, or measures the energy-related information received from the second network entity or function.

3. The method as described in claim 2, wherein, The first network entity or function or the second network entity or function is a policy control function (PCF), energy function (EF), application function (AF), or network data analysis function (NWDAF).

4. The method of claim 1, wherein, The energy-related information includes: Information related to energy consumption, information related to energy efficiency, information related to carbon emissions, and information related to energy.

5. The method of claim 4, wherein, The energy consumption includes non-renewable energy consumption, renewable energy consumption, or a combination of non-renewable and renewable energy consumption.

6. The method of claim 4, wherein, The energy source includes non-renewable energy, renewable energy, or a combination of non-renewable and renewable energy.

7. The method of claim 1, wherein, The one or more session management procedures include a Packet Data Unit (PDU) session release procedure or a PDU session modification procedure.

8. The method of claim 7, wherein, Trigger the PDU session release process or the PDU session modification process to adjust the user plane (UP) path of the PDU session.

9. The method of claim 1, wherein, The first information is generated based on the determination result.

10. The method of claim 1, wherein, The determination result is generated based on whether energy-related criteria associated with the energy-related information are met, wherein the energy-related criteria include at least one of the following: Energy consumption is higher than, equal to, or lower than the first value; Energy efficiency is higher than, equal to, or lower than the second value; Carbon emissions are higher than, equal to or lower than the third value; and Renewable or non-renewable energy sources are above, equal to, or below the fourth value.

11. The method of claim 10, wherein, The energy-related criteria are determined by or based on at least one of the following: (1) Carrier strategy; (2) Service provider input; (3) Preferences or values ​​indicated by the user equipment that are associated with the energy-related information; (4) User input; or (5) Subscription information.

12. A wireless communication device, comprising: Memory; as well as At least one processor coupled to the memory, the processor being configured to: Receive first information from a first network entity or function, wherein the first information is generated by the first network entity or function based on energy-related information. as well as One or more session management processes are triggered based on the first information or the determination result based on the energy-related information.

13. The apparatus of claim 12, wherein, The first network entity or function collects, tracks, or measures the energy-related information received from the second network entity or function.

14. The apparatus of claim 13, wherein, The first network entity or function or the second network entity or function is a policy control function (PCF), energy function (EF), application function (AF), or network data analysis function (NWDAF).

15. The apparatus of claim 12, wherein, The energy-related information includes: Information related to energy consumption, information related to energy efficiency, information related to carbon emissions, and information related to energy.

16. The apparatus of claim 15, wherein, The energy consumption includes non-renewable energy consumption, renewable energy consumption, or a combination of non-renewable and renewable energy consumption.

17. The apparatus of claim 15, wherein, The energy source includes non-renewable energy, renewable energy, or a combination of non-renewable and renewable energy.

18. The apparatus of claim 12, wherein, The one or more session management procedures include a Packet Data Unit (PDU) session release procedure or a PDU session modification procedure.

19. The apparatus of claim 18, wherein, Trigger the PDU session release procedure or the PDU session modification procedure to adjust the user plane (UP) path of the PDU session.

20. A computer-readable medium for storing computer-executable code for user equipment (UE) wireless communication, the computer-readable medium comprising code to execute: Receive first information from a first network entity or function, wherein the first information is generated by the first network entity or function based on energy-related information; and One or more session management processes are triggered based on the first information or the determination result based on the energy-related information.

Images