[go: up one dir, main page]

WO2024113580A1 - Procédé de configuration d'informations de commande latérale - Google Patents

Procédé de configuration d'informations de commande latérale Download PDF

Info

Publication number
WO2024113580A1
WO2024113580A1 PCT/CN2023/085733 CN2023085733W WO2024113580A1 WO 2024113580 A1 WO2024113580 A1 WO 2024113580A1 CN 2023085733 W CN2023085733 W CN 2023085733W WO 2024113580 A1 WO2024113580 A1 WO 2024113580A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
control information
side control
rrc
smart node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/085733
Other languages
English (en)
Inventor
Jianxun Ai
Jing Liu
Nan Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/085733 priority Critical patent/WO2024113580A1/fr
Priority to CN202380095673.7A priority patent/CN120883556A/zh
Publication of WO2024113580A1 publication Critical patent/WO2024113580A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/11—Semi-persistent scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present subject matter is directed generally to wireless communications. Particularly, the present subject matter relates to methods, devices, and systems for configuring side control information for a smart node when transitioning the smart node to the RRC_INACTIVE or RRC_IDLE states.
  • Integrated Access and Backhaul was introduced in 5G New Radio (NR) Release 16 (Rel-16) and enhanced in NR Rel-17 as a new type of network node that does not require a wired backhaul.
  • NR New Radio
  • RF radio frequency
  • the present subject matter is directed to a method, device, and system for configuring side control information for a smart node in a wireless communication system.
  • a method for configuring side control information for a smart node in a wireless communication system may include transferring a first message from a centralized unit of a base station to a distributed unit of the base station.
  • the first message may instruct the distributed unit to generate the side control information.
  • the method may further include receiving, at the centralized unit, a second message from the distributed unit, wherein the second message comprises the side control information.
  • the method may further include transferring a third message from the centralized unit to the smart node.
  • the third message may include the side control information.
  • the first message may be a UE context modification request.
  • the second message may be a UE context modification response.
  • the third message may be a radio resource control (RRC) reconfiguration message.
  • RRC radio resource control
  • the third message may be an RRC release message configured to cause the smart node to transition to an RRC_INACTIVE or an RRC_IDLE state.
  • the first message may further include an indication that the side control information is to be applied to perform forwarding at the smart node when the smart node is in an RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state.
  • the first message may further include an instruction to remove at least some configured side control information of the smart node.
  • the at least some configuration side control information may include one or more of: periodic side control information, semi-persistent side control information, or aperiodic side control information.
  • the first message may further include an indication or request for a value of a wake-up timer.
  • the second may further include the value of the wake-up timer.
  • the first message may further include an indication or request for beam information for a backhaul link of the smart node.
  • the second message may further include an ON/OFF indicator.
  • the second message may further include an instruction to release existing side control information configured for the smart node.
  • the second message may further include the beam information.
  • the third message may further include an ON/OFF indicator.
  • the third message may further include beam information for a backhaul link of the smart node.
  • the third message may further include the value of the wake-up timer.
  • the method may further include receiving an RRC reconfiguration complete message from the smart node.
  • an apparatus for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory.
  • the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a device for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory.
  • the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.
  • a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.
  • FIG. 1 shows an example wireless communication system including a wireless base station and user equipment.
  • FIG. 2 shows an example of a base station.
  • FIG. 3 shows an example of user equipment.
  • FIG. 4 shows an example wireless communication system including a wireless base station, smart node, and user equipment.
  • FIG. 5 shows an example overall architecture of a Centralized Unit (CU) /Distributed Unit (DU) split of a base station.
  • CU Centralized Unit
  • DU Distributed Unit
  • FIG. 6 shows an example swim lane diagram of an example communication between a base station having a centralized unit/distributed unit and a smart node.
  • the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures, or characteristics in a plural sense.
  • terms, such as “a” , “an” , or “the” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • NCR network-controlled repeater
  • RF radio frequency
  • An NCR may be regarded as a stepping stone of Reconfigurable Intelligent Surfaces (RIS) , an RIS node may adjust the phase and amplitude of a received signal to improve the coverage.
  • RIS Reconfigurable Intelligent Surfaces
  • such kinds of network nodes including but not limited to NCRs, smart repeaters, RISes, and IABs are denoted as smart nodes for simplicity in facilitating the following discussion.
  • Fig. 1 shows a diagram of an example wireless communication system 100 including a plurality of communication nodes (or just nodes) that are configured to wirelessly communicate with each other.
  • the communication nodes include at least one user device 102 and at least one wireless access node 104.
  • the example wireless communication system 100 in Fig. 1 is shown as including two user devices 102, including a first user device 102 (1) and a second user device 102 (2) , and one wireless access nodes 104.
  • various other examples of the wireless communication system 100 that include any of various combinations of one or more user devices 102 and/or one or more wireless access nodes 104 may be possible.
  • a user device as described herein such as the user device 102, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, capable of communicating wirelessly over a network.
  • a user device may comprise or otherwise be referred to as a user terminal, a user terminal device, or a user equipment (UE) .
  • UE user equipment
  • a user device may be or include, but not limited to, a mobile device (such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved for long periods of time, such as appliances, other relatively heavy devices including Internet of things (IoT) , or computing devices used in commercial or industrial environments, as non-limiting examples) .
  • a mobile device such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved
  • a user device 102 may include transceiver circuitry 106 coupled to an antenna 108 to effect wireless communication with the wireless access node 104.
  • the transceiver circuitry 106 may also be coupled to a processor 110, which may also be coupled to a memory 112 or other storage device.
  • the memory 112 may store therein instructions or code that, when read and executed by the processor 110, cause the processor 110 to implement various ones of the methods described herein.
  • a wireless access node as described herein such as the wireless access node 104, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, and may comprise one or more base stations or other wireless network access points capable of communicating wirelessly over a network with one or more user devices and/or with one or more other wireless access nodes 104.
  • the wireless access node 104 may comprise a 4G LTE base station, a 5G NR base station, a 5G central-unit base station, a 5G distributed-unit base station, a next generation Node B (gNB) , an enhanced Node B (eNB) , or other similar or next-generation (e.g., 6G) base stations, in various embodiments.
  • a wireless access node 104 may include transceiver circuitry 114 coupled to an antenna 116, which may include an antenna tower 118 in various approaches, to effect wireless communication with the user device 102 or another wireless access node 104.
  • the transceiver circuitry 114 may also be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device.
  • the memory 122 may store therein instructions or code that, when read and executed by the processor 120, cause the processor 120 to implement one or more of the methods described herein.
  • two communication nodes in the wireless communication system 100 such as a user device 102 and a wireless access node 104, two user devices 102 without a wireless access node 104, or two wireless access nodes 104 without a user device 102-may be configured to wirelessly communicate with each other in or over a mobile network and/or a wireless access network according to one or more standards and/or specifications.
  • the standards and/or specifications may define the rules or procedures under which the communication nodes can wirelessly communicate, which, in various embodiments, may include those for communicating in millimeter (mm) -Wave bands, and/or with multi-antenna schemes and beamforming functions.
  • the standards and/or specifications are those that define a radio access technology and/or a cellular technology, such as Fourth Generation (4G) Long Term Evolution (LTE) , Fifth Generation (5G) New Radio (NR) , or New Radio Unlicensed (NR-U) , as non-limiting examples.
  • 4G Fourth Generation
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • NR New Radio
  • NR-U New Radio Unlicensed
  • the communication nodes are configured to wirelessly communicate signals between each other.
  • a communication in the wireless communication system 100 between two communication nodes can be or include a transmission or a reception, and is generally both simultaneously, depending on the perspective of a particular node in the communication.
  • the first node may be referred to as a source or transmitting node or device
  • the second node may be referred to as a destination or receiving node or device
  • the communication may be considered a transmission for the first node and a reception for the second node.
  • a single communication node may be both a transmitting/source node and a receiving/destination node simultaneously or switch between being a source/transmitting node and a destination/receiving node.
  • particular signals may be characterized or defined as either an uplink (UL) signal, a downlink (DL) signal, or a sidelink (SL) signal.
  • An uplink signal is a signal transmitted from a user device 102 to a wireless access node 104.
  • a downlink signal is a signal transmitted from a wireless access node 104 to a user device 102.
  • a sidelink signal is a signal transmitted from a one user device 102 to another user device 102, or a signal transmitted from one wireless access node 104 to another wireless access node 104.
  • a first/source user device 102 directly transmits a sidelink signal to a second/destination user device 102 without any forwarding of the sidelink signal to a wireless access node 104.
  • signals communicated between communication nodes in the wireless communication system 100 may be characterized or defined as a data signal or a control signal.
  • a data signal is a signal that includes or carries data, such multimedia data (e.g., voice and/or image data)
  • a control signal is a signal that carries control information that configures the communication nodes in certain ways to communicate with each other, or otherwise controls how the communication nodes communicate data signals with each other.
  • certain signals may be defined or characterized by combinations of data/control and uplink/downlink/sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.
  • a physical channel corresponds to a set of time-frequency resources used for transmission of a signal.
  • Different types of physical channels may be used to transmit different types of signals.
  • physical data channels (or just data channels) are used to transmit data signals
  • physical control channels (or just control channels) are used to transmit control signals.
  • Example types of physical data channels include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PSSCH physical sidelink shared channel
  • example types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals.
  • a particular type of physical channel is also used to refer to a signal that is transmitted on that particular type of physical channel, and/or a transmission on that particular type of transmission.
  • a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission.
  • a communication node transmitting or receiving a PDSCH means that the communication node is transmitting or receiving a signal on a PDSCH.
  • a control signal that a communication node transmits may include control information comprising the information necessary to enable transmission of one or more data signals between communication nodes, and/or to schedule one or more data channels (or one or more transmissions on data channels) .
  • control information may include the information necessary for proper reception, decoding, and demodulation of a data signals received on physical data channels during a data transmission, and/or for uplink scheduling grants that inform the user device about the resources and transport format to use for uplink data transmissions.
  • control information includes downlink control information (DCI) that is transmitted in the downlink direction from a wireless access node 104 to a user device 102.
  • DCI downlink control information
  • control information includes uplink control information (UCI) that is transmitted in the uplink direction from a user device 102 to a wireless access node 104, or sidelink control information (SCI) that is transmitted in the sidelink direction from one user device 102 (1) to another user device 102 (2) .
  • DCI downlink control information
  • UCI uplink control information
  • SCI sidelink control information
  • a slot format for a plurality of slots or frames may be configured by the wireless access node 104 or specified by a protocol.
  • a slot may be indicated or specified as a downlink slot, a flexible slot, or an uplink slot.
  • an orthogonal frequency divisional multiplexing (OFDM) symbol may be indicated or specified as a downlink symbol, a flexible symbol, or an uplink symbol, in various embodiments.
  • OFDM orthogonal frequency divisional multiplexing
  • FIG. 2 shows an example of base station 200.
  • the example base station 200 may include radio transmitting/receiving (Tx/Rx) circuitry 208 to transmit/receive communication with UEs and/or other base stations.
  • the base station 200 may also include network interface circuitry 209 to communicate the base station with other base stations and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols.
  • the base station 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.
  • I/O input/output
  • the base station 200 may also include system circuitry 204.
  • System circuitry 204 may include processor (s) 221 and/or memory 222.
  • Memory 222 may include an operating system 224, instructions 226, and parameters 228.
  • Instructions 226 may be configured for the one or more of the processors 124 to perform the functions of the base station.
  • the parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.
  • FIG. 3 shows an example of an electronic device to implement a terminal device 300 (for example, user equipment (UE) ) .
  • the UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle.
  • the UE 300 may include communication interfaces 302, a system circuitry 304, an input/output interfaces (I/O) 306, a display circuitry 308, and a storage 309.
  • the display circuitry may include a user interface 310.
  • the system circuitry 304 may include any combination of hardware, software, firmware, or other logic/circuitry.
  • the system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry.
  • SoC systems on a chip
  • ASIC application specific integrated circuits
  • the system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300.
  • the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310.
  • the user interface 310 and the inputs/output (I/O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements.
  • I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input /output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
  • USB Universal Serial Bus
  • the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314.
  • the communication interface 302 may include one or more transceivers.
  • the transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium.
  • the transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings.
  • the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , and 5G standards.
  • UMTS Universal Mobile Telecommunications System
  • HSPA High Speed Packet Access
  • LTE Long Term Evolution
  • 5G 5G
  • the system circuitry 304 may include one or more processors 321 and memories 322.
  • the memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328.
  • the processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300.
  • the parameters 328 may provide and specify configuration and operating options for the instructions 326.
  • the memory 322 may also store any BT, WiFi, 3G, 4G, 5G or other data that the UE 300 will send, or has received, through the communication interfaces 302.
  • a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.
  • FIG. 4 illustrates an example wireless communication system including a smart node 405, base station 200, and UE 300.
  • the smart node 405 may be include a forwarding part 410 and a mobile-termination part 415.
  • a radio link between the base station 200 and forwarding part 410 may be a backhaul link 420.
  • a radio link between the base station 200 and the mobile-termination part 415 may be a control link 425.
  • a radio link between smart node 405 and the UE 300 may be an access link 430.
  • Each of the backhaul link 420, control link 425, and access link 430 may further include a downlink and uplink as shown in FIG. 4.
  • the forwarding part 410 may receive the radio signal transmitted from the base station 200 and forward radio signals to the UE 300 via the access link 430.
  • the forwarding part 410 may forward radio signals received from UE 300 to the base station 200.
  • the forwarding part 410 may process the radio signals and/or merely amplify-and-forward radio signals.
  • the mobile-termination part 415 may connect to the base station 200 as a normal mobile device (e.g., UE 300) and may receive side control information 435 via a downlink of the control link 425 from base station 200.
  • the side control information 435 may be used to control the forwarding behavior of the forwarding part 410, and for this reason, the side control information 435 may also be referred to as the forwarding configuration or beam indication.
  • the side control information 435 may be of the following types: periodic side control information, semi-persistent side control information, or aperiodic side control information.
  • Periodic side control information may be configured via a radio resource control (RRC) message transmitted from the base station 200 to the smart node 405.
  • RRC radio resource control
  • the smart node 405 may apply the periodic side control information when it receives the RRC message such that the periodic side control information is used to perform forwarding of the radio signals.
  • the periodic side control information may include a list of periodic time resources and corresponding beam information.
  • the smart node 405 may forward radio signals over access link 430 according to the configured time resource and the corresponding beam information.
  • the semi-persistent side control information may be configured via an RRC message transmitted from the base station 200 to the smart node 405.
  • the semi-persistent side control information may include a list of periodic time resources and corresponding beam information.
  • the smart node 405 may apply the semi-persistent side control information when it receives a MAC control element (MAC CE) from the base station 200.
  • MAC CE may be used to activate the semi-persistent side control information.
  • the smart node 405 may stop applying the semi-persistent side control information when it receives a MAC CE that is used to deactivate the semi-persistent side control information.
  • the aperiodic side control information may include an aperiodic time resource that may be configured via an RRC message and a DCI.
  • the DCI may include aperiodic time resource information, which refers to the aperiodic time resource configured by the RRC message, and corresponding beam information.
  • the smart node 405 may forward radio signals over access link 430 according to the aperiodic time resource information and corresponding beam information included in the DCI.
  • FIG. 5 illustrates an example overall architecture of a Centralized Unit (CU) /Distributed Unit (DU) split of a base station 200.
  • the gNB 505 may include a gNB Centralized Unit (gNB-CU 510) and one or more gNB Distributed Units (gNB-DU 515) .
  • a gNB-CU 510 and a gNB-DU 515 may be connected via an F1 interface 520.
  • the gNB-CU 510 may be defined as a logical node hosting radio resource control (RRC) , SDAP and packet data convergence protocols (PDCP) of the gNB 505, or RRC and PDCP protocols of the en-gNB, that control the operation of the one or more gNB-DUs 515.
  • RRC radio resource control
  • PDCP packet data convergence protocols
  • the gNB-DU 515 may be defined as a logical node hosting RLC, MAC, and PHY layers of the gNB 505 or en-gNB, and the operation of the gNB-DU 515 may be partly controlled by the gNB-CU 510.
  • One gNB-DU 515 may support one or more cells. One cell may be supported by only one gNB-DU 515.
  • a smart node 405 may be operating in ON or OFF according to the last configuration of side control information 435 before the smart node 405 is released to RRC_IDLE mode or RRC_INACTIVE states.
  • the network may need to remove all configured side control information 435 before the smart node 405 is released to the RRC_IDLE or RRC_INACTIVE states.
  • side control information 435 may be generated by the gNB-DU 515 while the decision to release the smart node 405 to the RRC_IDLE or RRC_INACTIVE states is made in the gNB-CU 510. Accordingly, the techniques of the present subject matter are needed to configure side control information 435 that is applied by the smart node 405 when in the RRC_IDLE or RRC_INACTIVE states.
  • FIG. 6 illustrates an example swim lane diagram of an example communication 600 between a base station having a centralized unit/distributed unit and smart node 405 to configure side control information 435 that is applied by the smart node 405 when in the RRC_IDLE or RRC_INACTIVE states.
  • a first message 610 may be transmitted from the gNB-CU 510 to the gNB-DU 515.
  • the first message 610 may be, for example, a UE context modification request message or a UE context setup request message and may include one or more of the following indications for the smart node 405.
  • the first message 610 may indicate to the gNB-DU 515 that the smart node 405 will be released to the RRC_IDLE or RRC_INACTIVE states.
  • the first message 610 may instruct the gNB-DU 515 to generate side control information 435 for the smart node 405 and indicate, e.g., by including an indicator, that the side control information 435 may be applied when the smart node 405 is in the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states.
  • the first message 610 may instruct the gNB-DU 515 to remove at least some or all the configured side control information 435 of the smart node 405, including periodic side control information, semi-persistent side control information, or aperiodic side control information from the current configured side control information 435 of the smart node 405.
  • the first message 610 may indicate that the value of a wake-up timer is needed or requested. The wake-up timer may be started in the smart node 405 when the smart node 405 is released to the RRC_IDLE or RRC_INACTIVE states.
  • the smart node 405 may stop forwarding, or initiate an RRC connection setup or an RRC connection resume procedure.
  • the gNB-DU 515 may include the value of the wake-up timer in a second message 615 sent from the gNB-DU 515 to the gNB-CU 510.
  • the first message 610 may indicate that beam information for the backhaul link 420 of the smart node 405 is needed or requested. The beam information may be applied for transmission and/or reception in the backhaul link 420 of the smart node 405 when the smart node 405 is in the RRC_IDLE or RRC_INACTIVE states.
  • the gNB-DU 515 may perform one or more of the following actions in response.
  • the gNB-DU 515 may generate side control information 435 for the smart node 405 based on the first message 610.
  • the side control information 435 may be applied when the smart node 405 is in the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states.
  • the gNB-DU 515 may include the side control information 435 in the second message 615.
  • the second message 615 may be, for example, a UE context modification response message or a UE context setup response message.
  • the gNB-DU 515 may include, in the second message 615, an ON/OFF indicator or instructions that may be used to release existing side control information 435 configured for the smart node 405.
  • the “OFF” indicator of the ON/OFF indicator may indicate that the forwarding part 410 of the smart node 405 is not performing forwarding.
  • the “ON” indicator of the ON/OFF indicator may indicate that the forwarding part 410 of the smart node 405 is performing forwarding according to side control information 435.
  • the gNB-DU 515 may determine whether beam information is needed for the backhaul link 420 of the smart node 405 when the smart node 405 is in the RRC_IDLE or RRC_INACTIVE states. More specifically, the beam used for the backhaul link 420 when the smart node 405 is in the RRC_IDLE or RRC_INACTIVE states may be different from the beam currently configured for the backhaul link, or the beam for the backhaul link 420 may not be configured at all. In these circumstances, the gNB-DU 515 may make the determination as to whether the beam information is needed. The gNB-DU 515 may include the beam information for the backhaul link 420 in the second message 615.
  • the gNB-DU 515 may determine whether a wake-up timer is needed for the smart node 405 in the RRC_IDLE or RRC_INACTIVE states.
  • the gNB-DU 515 may determine whether the wake-up timer is needed according to the first message 610, which may indicate that the value of a wake-up timer is needed or requested as previously described.
  • the gNB-DU 515 may determine the value of the wake-up timer.
  • the wake-up timer may be started in the smart node 405 when the smart node 405 is released to the RRC_IDLE or RRC_INACTIVE states.
  • the smart node 405 may stop forwarding, and/or initiate an RRC connection setup or an RRC connection resume procedure.
  • the gNB-DU 515 may include the value of the wake-up timer in the second message 615.
  • the gNB-DU 515 may generate the second message 615 and transmit the second message 615 to the gNB-CU 510.
  • the gNB-CU 510 may perform one or more of the following actions in response.
  • the gNB-CU 510 may generate a third message 620 that includes at least one of the side control information 435, the ON/OFF indicator, the beam information used for the backhaul link 420 of the smart node 405, or the value of the wake-up timer.
  • the third message 620 may be, for example, an RRC reconfiguration message.
  • the third message 620 may be sent from the gNB-CU 510 to the smart node 405.
  • the smart node 405 may be an NCR 605, a smart repeater, an RIS, and/or an IAB as previously described.
  • the smart node 405 may respond to the third message 620 by generating a fourth message 625 and transmitting the fourth message 625 to the gNB-CU 510.
  • the fourth message 625 may be, for example, an RRC reconfiguration complete message.
  • the gNB-CU 510 may generate and send a fifth message 630 to release and/or transition the smart node 405 to the RRC_IDLE or RRC_INACTIVE states.
  • the fifth message 630 may be, for example, an RRC release message.
  • the fifth message 630 may include at least one of: the side control information 435, the ON/OFF indicator, the beam information used for the backhaul link 420 of the smart node 405, or the value of the wake-up timer depending on whether any of these items of information are included in the third message 620.
  • the smart node 405 upon receiving the fifth message 630, may enter the RRC_INACTIVE or RRC_IDLE state and apply the configuration, which may include one or more of the following in either the third message 620 or fifth message 630: the side control information 435, the ON/OFF indicator, the beam information used for the backhaul link 420 of the smart node 405, or the value of the wake-up timer.
  • terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for the existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the subject matter of the disclosure may also relate to or include, among others, the following aspects:
  • a first aspect includes a method for configuring side control information for a smart node in a wireless communication system, including: transferring a first message from a centralized unit of a base station to a distributed unit of the base station, wherein the first message instructs the distributed unit to generate the side control information; receiving, at the centralized unit, a second message from the distributed unit, wherein the second message includes the side control information; and transferring a third message from the centralized unit to the smart node, wherein the third message comprises the side control information.
  • a second aspect includes the method of the first aspect, wherein the first message is a UE context modification request.
  • a third aspect includes the method of the first or second aspects, wherein
  • the second message is a UE context modification response.
  • a fourth aspect includes the method of any preceding aspect, wherein the third message is a radio resource control (RRC) reconfiguration message.
  • RRC radio resource control
  • a fifth aspect includes the method of any preceding aspect, wherein the third message is an RRC release message configured to cause the smart node to transition to an RRC_INACTIVE or an RRC_IDLE state.
  • a sixth aspect includes the method of any preceding aspect, wherein the first message further comprises an indication that the side control information is to be applied when the smart node is in an RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state.
  • a seventh aspect includes the method of any preceding aspect, wherein the first message further comprises an instruction to remove at least some configured side control information of the smart node.
  • An eighth aspect includes the method of any preceding aspect, wherein the at least some configuration side control information comprises one or more of: periodic side control information, semi-persistent side control information, or aperiodic side control information.
  • a ninth aspect includes the method of any preceding aspect, wherein the first message further comprises an indication or request for a value of a wake-up timer.
  • a tenth aspect includes the method of any preceding aspect, wherein the second message further comprises the value of the wake-up timer.
  • An eleventh aspect includes the method of any preceding aspect, wherein the first message further comprises an indication or request for beam information for a backhaul link of the smart node.
  • a twelfth aspect includes the method of any preceding aspect, wherein the second message further comprises an ON/OFF indicator.
  • a thirteenth aspect includes the method of any preceding aspect, wherein the second message further comprises an instruction to release existing side control information configured for the smart node.
  • a fourteenth aspect includes the method of any preceding aspect, wherein the second message further comprises the beam information.
  • a fifteenth aspect includes the method of any preceding aspect, wherein the third message further comprises an ON/OFF indicator.
  • a sixteenth aspect includes the method of any preceding aspect, wherein the third message further comprises beam information for a backhaul link of the smart node.
  • a seventeenth aspect includes the method of any preceding aspect, wherein the third message further comprises the value of the wake-up timer.
  • An eighteenth aspect includes the method of any preceding aspect, further including receiving an RRC reconfiguration complete message from the smart node.
  • a nineteenth aspect includes a device for wireless communication including a processor; and a memory in communication with the processor, the memory storing a plurality of instructions executable by the processor to cause the device to implement the method of any preceding aspect.
  • a twentieth aspect includes a non-transitory computer-readable medium including instructions operable, when executed by one or more processors, to implement the method of any preceding aspect.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne des procédés et des dispositifs de configuration d'informations de commande latérale d'un nœud intelligent dans un système sans fil. Une unité centralisée d'une station de base transfère un premier message à une unité distribuée de la station de base. Le premier message ordonne à l'unité distribuée de générer les informations de commande latérale. L'unité centralisée reçoit un second message provenant de l'unité distribuée. Le second message comprend les informations de commande latérale. L'unité centralisée transfère un troisième message comprenant les informations de commande latérale au nœud intelligent. Le nœud intelligent effectue une transition vers un état inactif RRC (RRC_INACTIVE) ou un état de veille RRC (RRC_IDLE) en réponse à la réception du troisième message.
PCT/CN2023/085733 2023-03-31 2023-03-31 Procédé de configuration d'informations de commande latérale Pending WO2024113580A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/085733 WO2024113580A1 (fr) 2023-03-31 2023-03-31 Procédé de configuration d'informations de commande latérale
CN202380095673.7A CN120883556A (zh) 2023-03-31 2023-03-31 侧行控制信息配置方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/085733 WO2024113580A1 (fr) 2023-03-31 2023-03-31 Procédé de configuration d'informations de commande latérale

Publications (1)

Publication Number Publication Date
WO2024113580A1 true WO2024113580A1 (fr) 2024-06-06

Family

ID=91322869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/085733 Pending WO2024113580A1 (fr) 2023-03-31 2023-03-31 Procédé de configuration d'informations de commande latérale

Country Status (2)

Country Link
CN (1) CN120883556A (fr)
WO (1) WO2024113580A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022046757A1 (fr) * 2020-08-25 2022-03-03 Qualcomm Incorporated Acquisition autonome d'informations de configuration dans des répéteurs radiofréquences
CN115606221A (zh) * 2022-06-28 2023-01-13 北京小米移动软件有限公司（Cn） 一种中继通信方法、装置、设备及存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022046757A1 (fr) * 2020-08-25 2022-03-03 Qualcomm Incorporated Acquisition autonome d'informations de configuration dans des répéteurs radiofréquences
CN115606221A (zh) * 2022-06-28 2023-01-13 北京小米移动软件有限公司（Cn） 一种中继通信方法、装置、设备及存储介质

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "IAB Node Integration Procedure", 3GPP DRAFT; R3-190354 - IAB NODE INTEGRATION PROCEDURE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051604295 *
GEORG HAMPEL, QUALCOMM INC.: "Management of Network-Controlled Repeater", 3GPP DRAFT; R3-230231; TYPE DISCUSSION; NR_NETCON_REPEATER, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 3, no. Athens, GR; 20230227 - 20230303, 16 February 2023 (2023-02-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052244079 *
JUHA KORHONEN, NOKIA, NOKIA SHANGHAI BELL: "[AT121][706][NCR] Access Link (Nokia)", 3GPP DRAFT; R2-2302155; TYPE DISCUSSION; NR_NETCON_REPEATER, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Athens, GR; 20230227 - 20230303, 3 March 2023 (2023-03-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052254038 *
SEN XU, CHINA TELECOMMUNICATIONS: "Further Discussion on NCR Management", 3GPP DRAFT; R3-230644; TYPE DISCUSSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 3, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052244487 *

Also Published As

Publication number Publication date
CN120883556A (zh) 2025-10-31

Similar Documents

Publication Publication Date Title
EP4104418B1 (fr) Mettre à jour des informations de configuration de dispositifs en aval pendant une migration inter-donneur
US12289761B2 (en) Electronic device and method for wireless communication, and computer-readable storage medium
US20230163917A1 (en) Methods and devices for enhancing sounding reference signal transmission
US12368536B2 (en) Methods and devices for transmitting feedback information
US11234249B2 (en) Electronic device and method for wireless communication, and computer readable storage medium
WO2024113580A1 (fr) Procédé de configuration d'informations de commande latérale
US20240349131A1 (en) Methods, devices, and systems for supporting l1/l2 based inter-cell mobility
WO2025065623A1 (fr) Procédé de communication pour uav
US12225421B2 (en) Method of a serving cell measurement object configuration
WO2024216997A1 (fr) Procédé de mesure de retard
WO2024108936A1 (fr) Utilisation et communication de capacité pour duplex à répartition dans le temps
WO2024148727A1 (fr) Utilisation de spectre pour une communication sans fil
WO2024169065A1 (fr) Procédé d'authentification primaire déclenchée par un réseau domestique pour rafraîchissement de clé akma
WO2024011516A1 (fr) Procédés et dispositifs de rapport d'interférences coexistant à l'intérieur d'un dispositif
WO2025015464A1 (fr) Utilisation de ressources spectrales pour une communication sans fil
US20250119900A1 (en) Methods and devices for reporting in-device coexistence interference
WO2025166575A1 (fr) Procédés et dispositifs de gestion de session de service de données dans un système sans fil
US20240349140A1 (en) Methods, devices, and systems for modifying candidate cells for l1/l2 based inter-cell mobility
US20230354285A1 (en) Methods, devices, and systems for configuring group-based bandwidth part switch
WO2025166596A1 (fr) Procédés et dispositifs de gestion de service de données dans un système de communication sans fil
WO2024021113A1 (fr) Écart de mesure dans une unité centralisée et une unité distribuée divisée
WO2023029949A1 (fr) Procédé et appareil de communication
WO2024160032A1 (fr) Procédé de désactivation de faisceau et appareil de communication
KR20250135197A (ko) 반복이 있는 pucch 및 pusch에 대한 uci 멀티플렉싱을 위한 방법들 및 디바이스들
CN120642527A (zh) 用于无线网络的uci和pucch映射的方法、设备和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23895748

Country of ref document: EP

Kind code of ref document: A1