Method in node for wireless communication, and apparatus
Patent Information
- Application Number
- PCT/CN2025/085770
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-28
- Publication Date
- 2026-10-01
Smart Images

Figure CN2025085770_01102026_PF_FP_ABST
Abstract
Description
Methods and apparatus for nodes used in wireless communication Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a method and apparatus for use in a node for wireless communication. Background Technology
[0002] The 5G New Radio (NR) standard introduced discontinuous reception (DRX) technology to save power consumption in terminal devices. To further reduce terminal device power consumption, a low-power receiver (LR) was introduced to receive a low-power wake-up signal (LP-WUS). LP-WUS is one of the key technologies of 5G NR, allowing the network to dynamically allocate a portion of available bandwidth for the user terminal (UE), aiming to flexibly allocate and manage spectrum resources and address the issues of varying device capabilities and diverse service requirements. However, with the introduction of LP-WUS, how the LP-WUS mechanism can be integrated with the network-configured LP-WUS is a question that needs to be considered. Summary of the Invention
[0003] This application provides a method and apparatus for use in a node for wireless communication. The various aspects of this application will be described below.
[0004] In a first aspect, a method for wireless communication in a first node is provided, the method being applied to a first node including a first communication module and a second communication module, comprising: receiving a wake-up signal through the first communication module; and, in response to the wake-up signal, listening to a PDCCH on a first BWP through the second communication module; wherein the first BWP is a dedicated BWP of the first node.
[0005] In a second aspect, a method is provided for a second node in wireless communication, comprising: sending a wake-up signal, the wake-up signal being used to trigger a first node to receive the wake-up signal through a first communication module of the first node; and listening to the PDCCH on a first BWP through a second communication module of the first node; wherein the first BWP is a dedicated BWP of the first node.
[0006] Thirdly, a first node for wireless communication is provided, including a first processing module and a first transceiver module; the first transceiver module is configured to receive a wake-up signal through the first communication module; in response to the wake-up signal, the first processing module is configured to listen to the PDCCH on a first BWP through a second communication module; wherein, the first BWP is a dedicated BWP of the first node.
[0007] Fourthly, a second node for wireless communication is provided, including a second transceiver module for:
[0008] Sending a wake-up signal, the wake-up signal being used to trigger the first node to receive the wake-up signal through the first communication module of the first node; and listening to the PDCCH on the first BWP through the second communication module of the first node; wherein, the first BWP is a dedicated BWP of the first node.
[0009] Fifthly, a first node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the first node to perform the method as described in the first aspect.
[0010] In a sixth aspect, a second node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the second node to perform the method as described in the second aspect.
[0011] In a seventh aspect, embodiments of this application provide a communication system including the aforementioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or second node as described in the embodiments of this application.
[0012] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.
[0013] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.
[0014] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.
[0015] This application combines BWP, DRX, and LP-WUS mechanisms to achieve optimal power saving. Attached Figure Description
[0016] Figure 1 is a system architecture example diagram of a wireless communication system that can be applied to the embodiments of this application.
[0017] Figure 2 is a schematic diagram of a network architecture applicable to embodiments of this application.
[0018] Figures 3A and 3B are schematic diagrams of wireless protocol stack structures applicable to embodiments of this application.
[0019] Figures 4A and 4B are schematic diagrams of the DRX mechanism applicable to embodiments of this application.
[0020] Figure 5A is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.
[0021] Figure 5B is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.
[0022] Figure 5C is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.
[0023] Figure 6 is a schematic diagram of a BWP configuration for a cell provided in an embodiment of this application.
[0024] Figure 7 is a schematic diagram of an application example of LP-WUS provided in the embodiments of this application.
[0025] Figure 8A is an example of the method shown in Figure 7.
[0026] Figure 8B is another example of the method shown in Figure 7.
[0027] Figure 9 is a flowchart illustrating a method in a node for wireless communication provided in an embodiment of this application.
[0028] Figure 10 is a flowchart illustrating another method for a node used in wireless communication provided in an embodiment of this application.
[0029] Figure 11 is a schematic diagram of the structure of a first node for wireless communication provided in an embodiment of this application.
[0030] Figure 12 is a schematic diagram of the structure of a second node for wireless communication provided in an embodiment of this application.
[0031] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
[0032] Figure 14 is a schematic diagram of the hardware module of the communication device provided in the embodiment of this application. Detailed Implementation
[0033] Communication system architecture
[0034] The wireless communication system of this application embodiment may include a network device and a terminal device. The network device may be a device that communicates with the terminal device. The network device may provide communication coverage for a specific geographical area and may communicate with terminal devices located within that coverage area.
[0035] Figure 1 exemplarily illustrates a wireless communication system 100 including a network device 110 and multiple terminal devices, such as terminal devices 120a to 120j in the figure. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area; this application embodiment does not limit this.
[0036] Optionally, the wireless communication system may also include other network entities such as a network controller and a mobility management entity, which is not limited in this application embodiment.
[0037] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th-generation (5G) systems or new radio (NR) systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, advanced long-term evolution (LTE-A) systems, enhanced 5G (5G advanced) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th-generation (6G) mobile communication systems, satellite communication systems, etc.
[0038] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal device in the embodiments of this application may be a mobile phone, tablet computer, laptop computer, handheld computer, camera equipment, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Optionally, the terminal device may be used to act as a base station. For example, the terminal device may act as a scheduling entity, providing sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D) connections. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices can communicate without relaying communication signals through base stations.
[0039] The network device in this application embodiment can be a device for communicating with terminal devices. This network device can also be called an access network device or a radio access network device, such as a base station (BS). In this application embodiment, the network device can refer to a radio access network (RAN) node or a next-generation RAN (NG-RAN) node (or device) that connects user equipment to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, transmitting and receiving node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.
[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.
[0041] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.
[0042] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.
[0043] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).
[0044] Figure 2 illustrates a schematic diagram of a network architecture 200 according to an embodiment of this application. This network architecture 200 describes the network architecture of a 5G NR / LTE / LTE-A system, which can also be referred to as a 5G system (5GS) / evolved packet system (EPS) network architecture. The network architecture 200 includes at least one of the following: network device 110, terminal device 120, 5G core network (5GC) / evolved packet core (EPC) 210, home subscriber server (HSS) / unified data management (UDM) 220, and Internet service 230. The network device and terminal device in Figure 2 are illustrated using RAN and UE as examples, respectively.
[0045] As shown in Figure 2, network device 110 provides user plane and control plane protocol termination to terminal device 120. Network device 110 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes a mobility management entity (MME) / authentication management field (AMF) / session management function (SMF) 211, other MMEs / AMFs / SMFs 214, a service gateway (S-GW) / user plane function (UPF) 212, and a packet data network gateway (P-GW) / UPF 213. MME / AMF / SMF 211 is the control node that handles signaling between terminal device 120 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF212, which is itself connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-compliant Internet Protocol services, specifically including the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched streaming services. It is evident that network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented herein can be extended to networks providing circuit-switched services or other cellular networks.
[0046] Figures 3A and 3B respectively illustrate a schematic diagram of a wireless protocol stack structure according to an embodiment of this application. Figures 3A and 3B use a 5G wireless protocol stack as an example for illustration. The 5G wireless protocol stack is divided into two planes: the user plane (UP) protocol stack and the control plane (CP) protocol stack. The user plane protocol stack is the protocol suite used for user data transmission, and the control plane protocol stack is the protocol suite used for control signaling transmission in the 5G system. The specific names of each protocol stack layer are as follows:
[0047] As shown in Figure 3A, the user plane protocol stack includes, from top to bottom, the following layers: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer.
[0048] As shown in Figure 3B, the control plane protocol stack includes, from top to bottom: non-access stratum (NAS); radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.
[0049] It should be understood that the different layers in the above protocol stack have different functions, and they work together through inter-layer interaction to achieve communication between terminal devices and network devices. With the development of artificial intelligence technology, AI-assisted computing has permeated the processing implementation methods of the above protocol stack. For example, the scheduling algorithm of the MAC layer and the encoding / decoding algorithm of the PHY layer can apply artificial intelligence algorithms to improve the performance of communication algorithms.
[0050] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the first node in this application.
[0051] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the second node in this application.
[0052] It should be understood that some functionalities in a wireless protocol architecture can also be implemented in one or more devices. For example, the functions of different layers in the control plane protocol stack can be implemented by multiple nodes on the network side.
[0053] It should be understood that the interpretation of the terminology in the embodiments of this application may refer to the TS36, TS37 and TS38 series of specifications of the 3rd generation partnership project (3GPP), but may also refer to the specifications of the Institute of Electrical and Electronics Engineers (IEEE).
[0054] To facilitate understanding, some technical terms used in the embodiments of this application will be explained below:
[0055] 1) First communication module and second communication module
[0056] The first communication module, also known as the main radio (MR), main receiver, or main communication module, is used by the terminal device in idle or connected states to periodically sleep and wake the MR via discontinuous reception (DRX) or extended DRX mechanisms to reduce power consumption. For example, when idle, the terminal device can disable the MR or put it into deep sleep mode, and then listen to LP-WUS via the second communication module, thereby reducing the terminal device's power consumption. As another example, for a terminal device in connected state, it can run either the MR or the receiver.
[0057] The second communication module, also known as a low-power wake-up module or low-power wake-up receiver (LP-WUR), or low-power wake-up radio (LP-WUR).
[0058] Terminal devices can use a separate low-power wake-up module to receive wake-up signals. The wake-up signal received by the terminal device using this low-power wake-up module can be called a low-power wake-up signal (LP WUS).
[0059] This low-power wake-up module can be implemented using a simple, single small circuit or chip with low power consumption. This low-power wake-up module can be referred to as a wake-up radio (WUR), a wake-up circuit, or simply LR, or a low-power wake-up receiver (LP-WUR), etc. This application does not limit its naming. For ease of explanation, it will be uniformly described as a low-power wake-up module below. Furthermore, for ease of explanation, the signal received by the terminal device using the low-power wake-up module will be referred to as the wake-up signal.
[0060] In some embodiments, LP-WUS can support bandwidths of 5MHz-20MHz. When LP-WUS is embedded in a relevant communication system, the main communication module (or MR) and the low-power wake-up module (LP-WUR or LR) on the terminal device side can be two communication modules or integrated together as a single communication module. The LP-WUR can support various receiver architectures.
[0061] 2) On-off keying (OOK) modulation
[0062] To reduce power consumption in the wake-up circuit, LP-WUS can employ OOK modulation, and the corresponding wake-up circuit can use envelope detection to receive the wake-up signal. When using OOK modulation, each (encoded) bit corresponds to a symbol (also called a chip). When the bit is 1, a signal is emitted within the symbol length (i.e., the signal power within the symbol length is not 0), which can be conveniently referred to as the ON signal. Conversely, when the bit is 0, no signal is emitted within the symbol length (i.e., the signal power within the symbol length is 0), which can be conveniently referred to as the OFF signal.
[0063] 5G NR systems employ OFDM modulation, and network equipment in 5G NR systems can transmit signals modulated by orthogonal frequency division multiplexing (OFDM). To ensure compatibility with 5G NR systems as much as possible, the aforementioned OOK signal can be implemented using an OFDM-modulated transmitter. One possibility is that the length of an OOK symbol can be the same as the length of an OFDM symbol. In this case, when an ON signal of one symbol length is needed, the transmitter sends a specific signal, making its contour within the symbol length resemble a square wave as closely as possible. When an OFF signal is needed, the transmitter turns off the signal for one symbol length. Another possibility is that an OFDM transmitter can transmit multiple OOK symbols within the length of one OFDM symbol, thus shortening the OOK symbol length and allowing more OOK symbols to be transmitted in the same amount of time, thereby increasing the data rate.
[0064] 3) Frequency Shift Keying (FSK) Modulation
[0065] LP-WUS can also use FSK modulation. When using FSK modulation, different information uses different frequency resources. For example, 2FSK can carry 1 bit of information. When the information bit is 0, the information can be transmitted on frequency resource f0 and not on frequency resource f1; when the information bit is 1, the information can be transmitted on frequency resource f1 and not on frequency resource f0.
[0066] FSK can also support higher modulation orders to carry more information. For example, 4FSK can carry 2 bits of information. When the information bit is 00, information can be transmitted on frequency resource f0, and not on frequency resources f1, f2, and f3; when the information bit is 01, information can be transmitted on frequency resource f1, and not on frequency resources f0, f2, and f3; when the information bit is 10, information can be transmitted on frequency resource f2, and not on frequency resources f0, f1, and f3; when the information bit is 11, information can be transmitted on frequency resource f3, and not on frequency resources f0, f1, and f2. Similarly, the receiving end can compare the power levels on multiple frequency resources to determine what information is being transmitted.
[0067] 4) Discontinuous reception (DRX)
[0068] The DRX mechanism allows terminal devices to periodically enter sleep mode for certain periods, thereby saving power consumption. Terminal devices in Radio Resource Control (RRC) connected mode use Connected Discontinuous Reception (C-DRX).
[0069] For example, a DRX cycle includes a "wake-up time (DRXON)" and a "sleep time (DRXOFF)". During the wake-up time, the terminal device listens for and receives the physical downlink control channel (PDCCH); during the sleep time, the terminal device has the opportunity not to listen for or receive the PDCCH to reduce power consumption. Specifically, the DRX mechanism includes a persistent timer (onDurationTimer or drx-onDurationTimer), as shown in Figure 4A. At the beginning of each DRX cycle (i.e., the beginning of the onDuration of each DRX cycle), the terminal device needs to start the drx-onDurationTimer. When the drx-onDurationTimer times out, it indicates that the "onDuration" time has ended. If there are no other timers to keep the UE in the DRX ON state, the UE enters the DRX OFF state. The DRX mechanism also includes a deactivation timer (InactivityTimer or drx-InactivityTimer), as shown in Figure 4B. Each time the terminal device receives a DCI that schedules a new data packet, it starts / restarts the drx-InactivityTimer. The duration of either drx-OnDurationTimer or drx-InactivityTimer is referred to as the Active Time. During the Active Time, the terminal device monitors the PDCCH, receives the Channel State Information Reference Signal (CSI-RS), provides CSI feedback, and sends a Sounding Reference Signal (SRS). In this embodiment, outside of the Active Time, the terminal device does not monitor the PDCCH, does not provide periodic CSI feedback or semi-persistent CSI feedback, and does not send periodic SRS or semi-persistent SRS. The C-DRX cycle length, the drx-OnDurationTimer length, and the drx-InactivityTimer length are all configured by the network device for the terminal device.
[0070] In addition, network devices can also configure other DRX parameters for terminal devices, such as short DRX cycle and long DRX cycle.
[0071] In the DRX mechanism, a long DRX cycle can be configured as the default, while a short DRX cycle can be configured as an option. For terminal devices configured with a short DRX cycle, the conversion between long and short DRX cycles can be achieved in the following way:
[0072] Generally, a terminal device uses a short DRX cycle when any of the following conditions are met: 1. During the operation of the shortDRX cycle timer;
[0073] Generally, a terminal device uses a long DRX cycle when any of the following conditions are met: 1. The short DRX cycle timer (Drx-shortCycleTimer) times out; 2. The terminal device receives a long DRX command MCA CE (long DRX command MAC 20CE).
[0074] 5) Bandwidth Part (BWP) Switching Mechanism
[0075] BWP: This can be understood as a group of physical resource blocks (PRBs) within a carrier, or as the terminal's operating bandwidth. A terminal can be configured with multiple BWPs, but only one BWP can be active at a time. The terminal can send and receive data on the active BWP. Different BWPs can use different SCSs or cyclic prefixes (CPs).
[0076] In some embodiments, LP-WUS can support bandwidths of 5MHz-20MHz. When LP-WUS is embedded in a related communication system, the main communication module (or MR) and the low-power wake-up module (LP-WUR or LR) on the terminal device side can be two modules or integrated together as a single module. LP-WUR can support various receiver architectures. The following description uses the three receiver architectures shown in Figures 5A to 5C as examples to illustrate LP-WUR.
[0077] Figure 5A is a schematic diagram of an LP-WUR based on radio frequency (RF) envelope detection. The receiver architecture shown in Figure 5A includes a matching network 2001, an RF bandpass filter (BPF) 2002, an RF low noise amplifier (LNA) 2003, an RF envelope detector 2004, a baseband (BB) asymmetric processing (AMP) 2005, a BB low pass filter (LPF) 2006, a 1-bit or multi-bit analog-to-digital converter (ADC) 2007, and digital BB processing 2008.
[0078] In the architecture shown in Figure 5A, the RF signal is directly converted into a baseband signal via an RF envelope detector. Relatively low power consumption can be achieved due to the absence of a local oscillator (LO) and phase-locked loop (PLL). Optionally, the architecture may include a 1-bit or multi-bit ADC, an RF LNA and / or a BB AMP, a high-Q matching network and / or an RF BPF and / or a BB LPF. Optionally, to support multiple frequency bands and / or carriers, multiple high-Q matching networks and / or RF BPFs or multiple off-chip components may be required to suppress adjacent channel interference or interference from conventional NR signals and / or other LP WUS from adjacent subcarriers, and to support frequency band and / or carrier tuning.
[0079] Figure 5B shows a schematic architecture of an LP-WUR based on heterodyne architecture with intermediate frequency (IF) envelope detection. The receiver architecture shown in Figure 5B includes a matching network 3001, an RF BPF 3002, an RFLNA 3003, a mixer 3004, a receiver-over-frequency (LO) 3005, an IF AMP 3006, an IF BPF 3007, an IF envelope detector 3008, a BB AMP 3009, a BB LPF 3010, a 1-bit or multi-bit ADC 3011, and a digital BB processor 3012.
[0080] In the architecture shown in Figure 5B, the RF signal is converted to an intermediate frequency (IF) signal by an RF mixer with a LO. The IF signal is then converted to a baseband signal via IF envelope detection. Depending on the design, there may be one or more IF stages, achieving lower power consumption by relaxing the accuracy and stability requirements of the LO. This architecture can employ a 1-bit or multi-bit ADC. A high-Q matching network and / or an RF BPF and / or an IF BPF (and / or a BB LPF) can be used to suppress adjacent channel interference or interference from conventional NR signals and / or other LP WUS from adjacent subcarriers. Optionally, the architecture can incorporate components to improve sensitivity, such as an RF LNA and / or an IF AMP and / or a BB AMP. Optionally, the architecture can achieve band and / or carrier tuning by tuning the LO frequency.
[0081] Figure 5C shows a schematic architecture of an LP-WUR based on a homodyne or zero-IF architecture with baseband (BB) envelope detection. The receiver architecture shown in Figure 5C includes a matching network 4001, an RF BPF 4002, an RFLNA 4003, a mixer 4004, a receiver-on-a-band (LO) 4005, a BB AMP 4006, a BB LPF / BPF 4007, a 1-bit or multi-bit ADC 4008, and a digital BB processor 4009.
[0082] In the architecture shown in Figure 5C, band and / or carrier tuning can be achieved by tuning the LO frequency. Using a BB BPF / LPF instead of a high-Q matched network and / or an RF BPF allows for more effective and simpler suppression of adjacent channel interference or interference from conventional NR signals and / or other LP WUS on adjacent subcarriers. An RF LNA can be applied to improve sensitivity. Baseband envelope detection (not shown in the figure) can be performed in the analog domain (before the ADC) or the digital domain (after the ADC).
[0083] The preceding text, with reference to Figures 5A to 5C, introduced various LP-WUR architectures. All LP-WUR architectures are applicable to on-off keying (OOK) modulation. Some architectures are also applicable to other modulations, such as frequency-shift keying (FSK).
[0084] It's worth noting that in 4G, the radio resources used by terminals are managed on a carrier (cell) basis. This means a terminal can use one or more carriers for communication, but not a portion of a single carrier. Because each carrier has its own independent reference signal overhead, the reference signal occupies a relatively high proportion of radio resources. To reduce the proportion of radio resources occupied by the reference signal, 5G technology introduces large-bandwidth carriers, extending the bandwidth supported by a single carrier from 20MHz to 100MHz–400MHz. Large-bandwidth carriers are suitable for high-data-rate terminals, but not for low-data-rate terminals. This is because low-data-rate terminals require RF and baseband processing adapted to the large bandwidth to receive data from the carrier, resulting in higher power consumption and placing high demands on the UE's RF / baseband capabilities. The BWP handover mechanism introduced in 5G can improve this issue.
[0085] In 5G, a carrier is configured with an initial Baseframe Window (BWP) for transmitting synchronization signals, system information blocks (SIBs), and receive preambles. This initial BWP is identical for all UEs within the cell. Additionally, the base station can configure a "default BWP" for each UE. After a UE accesses a cell, it either operates on a dedicated BWP or the default BWP. Upon powering on, the UE searches for synchronization signals and randomly accesses the cell. The base station then configures one or more dedicated BWPs for the UE via RRC messages, corresponding to different service QoS requirements, as well as the default BWP. Subsequently, the base station switches the UE to a dedicated BWP by transmitting a Direct Message Interface (DCI) on the initial BWP. The UE receives data on the dedicated BWP, as shown in Figure 6. It is worth noting that to prevent the UE from failing to receive base station instructions due to DCI transmission failure on the dedicated BWP, the UE uses a timer (bwp-InactivityTimer). Each time a DCI is received on the dedicated BWP, the timer is started or restarted. If the timer expires, the UE returns to the default BWP (if a default BWP is configured) or the initial BWP (if no default BWP is configured). BWP is essentially a frequency-domain power-saving process.
[0086] For a given cell, network equipment can configure multiple downlink (DL) BWPs and / or multiple uplink (UL) BWPs for terminal devices. The frequency domain resources of different BWPs may or may not overlap. At any given time, one DL BWP and one UL BWP can be active within a cell.
[0087] In one possible implementation, for time division duplexing (TDD) scenarios (or unpaired spectrum scenarios), DL BWPs and UL BWPs with the same ID are associated, and the center frequency of each pair of associated DL BWPs and UL BWPs is the same. When a DL BWP switches, a corresponding UL BWP will also switch; when a UL BWP switches, a corresponding DL BWP will also switch.
[0088] In another possible implementation, the network device can configure a timer (bwp-InactivityTimer) for BWP handover to the terminal device. This timer is used for the terminal device to fall back from the currently active BWP to the default BWP. For example, the network device can configure the identity (ID) of the default BWP via RRC signaling, allowing the terminal device to fall back from the currently active BWP to the BWP corresponding to the default BWP identity. Alternatively, if the network device does not configure a default BWP identity, the terminal device can fall back to the initial BWP configured by the network device.
[0089] In one possible embodiment, different BWPs can correspond to different subcarrier intervals, and different subcarrier intervals correspond to different time slot lengths.
[0090] It's worth noting that in scenarios without the LP-WUS mechanism, if the UE is not configured with DRX but only with a dedicated BWP, after the UE accesses the cell, it uses the MR to listen to the PDCCH in the default BWP or initial BWP. If it detects a DCI, and the DCI contains a "BWP hop indication," the MR switches to the dedicated BWP. After data transmission is complete, the UE receives the DCI indication, or the timer (bwp-InactivityTimer) times out, and the UE returns to the default BWP or initial BWP to continue listening to the PDCCH using the MR, as shown in Figure 7. Clearly, this process does not fully utilize the LP-WUS mechanism and cannot achieve further power saving.
[0091] In another scenario, the LP-WUS mechanism is introduced. If a DRX cycle is also configured, the LP-WUS mechanism and the DRX cycle can work together in the following two ways.
[0092] Option 1 (option 1-1):
[0093] As shown in Figure 8A, the UE is configured with a DRXON window T1, and an LP-WUS listening window T2 is configured before each DRX window. The UE first uses LR to listen for LP-WUS within the LP-WUS listening window T2. If no LP-WUS is detected, MR is not started. If LP-WUS is detected, the UE starts using MR to listen for PDCCH at the beginning of the predefined DRX ON window T1. If DCI is detected, an inactivity timer or a new timer is started. If the UE receives a MAC CE notification from the base station indicating UE DRX OFF, or if the inactivity timer times out, or if the newly defined timer times out, MR stops working, and the UE enters the DRXOFF state until the next DRX cycle, at which point the UE decides whether to restart MR based on the result of LP-WUS listening.
[0094] The second option (option 1-2):
[0095] As shown in Figure 8B, the UE first uses LR to listen for LP-WUS. If LP-WUS is not detected, MR is not started. If the UE detects LP-WUS, it starts using MR to listen for PDCCH. When the UE detects DCI during PDCCH listening, it starts an inactivity timer or a new timer. If the UE receives a MAC CE notification from the base station that UE DRX OFF, or the inactivity timer times out, or the newly defined timer times out, the UE stops listening for PDCCH, MR stops working, and LR is used to listen for LP-WUS instead.
[0096] However, the two methods mentioned above do not clearly specify which BWP is used by the MR to monitor the PDCCH. Based on this, this application proposes a method for wireless communication that combines three different energy-saving mechanisms—BWP switching, DRX, and LP-WUS—to achieve greater power-saving gains.
[0097] For ease of understanding, the method for wireless communication according to an embodiment of this application is described below with reference to FIG9. FIG9 is a schematic flowchart of the method for wireless communication in the first node according to an embodiment of this application. FIG9 is described from the perspective of the first node.
[0098] As an example, the first node can be a network-controlled repeater (NCR).
[0099] As an example, the first node can be a terminal device. For example, terminal devices 120a to 120j shown in Figure 1. The second node can be a network device. For example, the second node is an access network device or a core network device. Another example is a gNB. Yet another example is an LMF. The following embodiments are basically illustrated with the UE as the first node and the gNB as the second node.
[0100] As an example, the first node can be a relay, such as a relay terminal.
[0101] As an example, the first node can be any type of network device, such as network device 110 shown in Figure 1.
[0102] In some embodiments, the first node may be in a connected state.
[0103] The method shown in Figure 9 may include steps S910 to S920, which are described below.
[0104] In S910, the first node receives a wake-up signal through the first communication module.
[0105] In some embodiments, the wake-up signal includes first indication information, which is used to indicate a first BWP. The first BWP is a dedicated BWP for the first node. For example, the wake-up signal is an LP-WUS, which may employ OFDM modulation and includes the first indication information. It should be understood that the base station may also configure LP-WUS including different indication information to instruct the UE to switch to different BWPs.
[0106] In some embodiments, the first node may also receive first configuration information, which includes second indication information used to indicate the first BWP. For example, the wake-up signal is LP-WUS. Because LP-WUS can use OOK modulation, it is impossible to indicate the BWP in LP-WUS. The gNB can notify the UE of the dedicated BWP used via an RRC reconfiguration message, or via MAC CE or DCI.
[0107] In some embodiments, the first node may also receive second configuration information, which includes parameters for a discontinuous reception period; wherein the discontinuous reception period includes a wake-up time and a sleep time, during which the second communication module listens for the PDCCH on the first BWP, and during the sleep time, the second communication module stops working. For example, the gNB can notify the UE of the DRX parameters used via an RRC reconfiguration message, or via MAC CE or DCI.
[0108] For example, the DRX parameters include at least one of the following: the long listening period of the wake-up signal, the short listening period of the wake-up signal, the time offset of the wake-up signal, or the continuous listening duration of the wake-up signal. The first node calculates the listening timing of LP WUS based on these parameters.
[0109] In S920, in response to the wake-up signal, the first node listens to the PDCCH on the first BWP through the second communication module; wherein, the first BWP is a dedicated BWP for the first node.
[0110] In one possible embodiment, the first node directly listens to the PDCCH on the first BWP via the second communication module. That is, in the first stage, there is no need to switch from the default BWP or the initial BWP to a dedicated BWP. Upon receiving the wake-up signal MR, the node directly operates on its own dedicated BWP to listen to the PDCCH.
[0111] In another possible embodiment, the first node switches from the second BWP to the first BWP. The first node listens for the PDCCH on the first BWP through the second communication module, wherein the second BWP is the default BWP or the initial BWP. For example, when the UE receives LP-WUS, the UE's MR starts working on the default BWP / initial BWP and then switches to a dedicated BWP.
[0112] In some embodiments, the UE can obtain first configuration information and / or second configuration information via an RRC reconfiguration message. Optionally, the first and second configuration information received via the RRC reconfiguration message can take effect immediately, or their effectiveness or ineffectiveness can be determined by an activation / deactivation indication. It should be understood that the activation / deactivation indication can be notified to the UE via a MAC CE or a DCI. For example, 1 bit can be used in the MAC CE or DCI to notify the UE of activation / deactivation. Exemplarily, 1 indicates activation and 0 indicates deactivation.
[0113] In some embodiments, the first node may first send capability information to the second node, the capability information indicating that the first node supports the BWP mechanism and the wake-up mechanism. Optionally, the capability information may further indicate that the first node supports the DRX mechanism. For example, when the gNB actively requests capability information through UECapabilityEnquiry, the UE reports the capability information through UECapabilityInformation. Alternatively, the core network controls the first node to notify the base station of the capability information.
[0114] In some embodiments, the capability information includes at least one of the following: supporting at least four different BWPs; supporting a combination of BWPs with a bandwidth of 5MHz or more and a wake-up mechanism; supporting a combination of BWPs with a bandwidth of less than 400MHz and a wake-up mechanism; supporting BWPs with a subcarrier spacing of 10kHz or more; or supporting BWPs with a subcarrier spacing of less than 60kHz.
[0115] In some embodiments, the second node can independently indicate whether the BWP is switched when the MR starts working, and whether the BWP is switched when the MR ends working.
[0116] In some embodiments, the second node may indicate that "MR starts working directly on a dedicated BWP," that is, on which dedicated BWP the MR listens to the PDCCH. The specific content of the indication information may be a BWP index. This indication information can be notified to the UE via an RRC reconfiguration message, or via MAC CE or DCI.
[0117] In some embodiments, if the MR starts working by jumping to a dedicated BWP via the default BWP / initial BWP, the configuration information from the second node does not need to indicate which dedicated BWP. The UE can obtain the dedicated BWP indication from the DCI received by the default BWP / initial BWP and then jump to the dedicated BWP.
[0118] For example, by combining the LP-WUS mechanism shown in Figures 8A and 8B with the two methods of DRX periodic coordination, the base station can indicate the UE's MR transition behavior from inactive to active in the following scenarios:
[0119] Scenario 1A: In the above working mode option 1-1, when the UE receives LP-WUS, the UE's MR directly jumps to the pre-configured dedicated BWP to start working.
[0120] Scenario 1B: In the above working mode option 1-1, when the UE receives LP-WUS, the UE's MR jumps to the default BWP / initial BWP working mode.
[0121] Scenario 1C: In the above operating mode option 1-1, when the UE receives an LP-WUS, the LP-WUS notifies whether the UE's MR is operating in the initial BWP or a dedicated BWP. Optionally, when the LP-WUS indicates that it is operating in a dedicated BWP, it can further indicate the information of the dedicated BWP, such as the dedicated BWP's identifier (ID), index (IDX), or frequency point, or a combination of frequency point and BWP bandwidth. In this way, after receiving the LP-WUS, the UE can operate in the dedicated BWP corresponding to that information.
[0122] Scenario 2A: In the above working modes options 1-2, when the UE receives LP-WUS, the UE's MR directly jumps to the pre-configured dedicated BWP.
[0123] Scenario 2B: In the above working modes options 1-2, when the UE receives LP-WUS, the UE's MR switches to the default BWP / initial BWP working mode.
[0124] Scenario 2C: In the above operating modes options 1-2, when the UE receives an LP-WUS, the LP-WUS notifies whether the UE's MR is operating in the initial BWP or a dedicated BWP. Optionally, when the LP-WUS indicates that it is operating in a dedicated BWP, it can further indicate the ID of the dedicated BWP. In this way, after receiving the LP-WUS, the UE can operate in the dedicated BWP corresponding to that ID.
[0125] In one possible embodiment, when the first node finishes listening to the PDCCH via the second communication module after the first BWP has finished, the second communication module directly stops working. For example, when the base station sends a signaling message to the UE instructing the UE's MR to terminate, it directly jumps from the dedicated BWP to the MR-stopped state.
[0126] In one possible embodiment, when the first node switches from the first BWP to the second BWP after the first BWP finishes listening to the PDCCH via the second communication module, it then jumps from the second BWP to a state where the second communication module stops working. For example, the base station sends a first signaling message to the UE, indicating that when the MR (Metal Transporter) stops working, it jumps from the dedicated BWP to the default BWP / initial BWP. The base station then sends a second signaling message to the UE via the default BWP / initial BWP, indicating that the MR jumps from the default BWP / initial BWP to a state where the MR stops working. This first and second signaling messages can be communicated to the UE via an RRC (Reconfiguration Control Code) message, or via MAC CE (Configuration Execution Code) or DCI (Distributed Control Code). Optionally, besides the base station sending the second signaling message to the UE via the default BWP, a timer can also be used to implement the function of the second signaling message. For example, when the UE jumps to the default BWP, a timer is started. If an indication is received from the base station during the timer's operation, and the indication is not a notification that the MR has stopped working, the UE restarts the timer; if the timer expires, the UE enters the state where the MR has stopped working.
[0127] In one possible implementation, the base station can indicate a uniform MR operating mode for the UE across all scenarios, or it can indicate separate MR operating modes for different scenarios. The implementation logic for different scenarios is described below, combining the aforementioned operating modes option 1-1 and option 1-2.
[0128] Table 1
[0129] As shown in Table 1, in Scenario 1A (option 1-1), when the UE receives a MAC CE notifying it to execute "DRX OFF", the UE operates in the dedicated BWP and directly jumps to the MR inactive state. The LR waits until the next LR listening window before starting work. In Scenario 1B (option 1-1), when the UE receives a MAC CE notifying it to execute "DRX OFF", the UE operates in the dedicated BWP and jumps to the MR operating in the default BWP / initial BWP. Whether it jumps to the MR inactive state depends on further instructions from the base station, or it may switch to the MR inactive state after listening in the default BWP / initial BWP for a period of time. The LR waits until the next LR listening window before starting work. In Scenario 1C (option 1-1), when the UE receives a MAC CE notifying it to execute "DRX OFF", the UE operates in the default BWP / initial BWP and directly jumps to the MR inactive state. The LR waits until the next LR listening window before starting work. In Scenario 1D (option 1-1), when the DRX inactive timer times out, the UE operates in the dedicated BWP and directly jumps to the MR inactive state. LR will wait until the next LR listener window before it starts working.
[0130] Scenario 1E: In option 1-1, the DRX inactive timer times out. The UE operates in the dedicated BWP and transitions to the MR, operating in the default BWP / initial BWP. Whether it transitions to the MR inactive state depends on further instructions from the base station, or it may transition to the MR inactive state after listening for a period of time in the default BWP / initial BWP. The LR waits for the next LR listening window before resuming operation. Scenario 1F: In option 1-1, the DRX inactive timer times out. The UE operates in the default BWP / initial BWP and directly transitions to the MR inactive state. The LR waits for the next LR listening window before resuming operation. Scenario 1G: In option 1-1, the timer newly defined in R19 times out (this timer starts when the UE's MR begins listening to the PDCCH, equivalent to the OnDuration timer in the DRX mechanism). The UE operates in the dedicated BWP and directly transitions to the MR inactive state. The LR waits for the next LR listening window before resuming operation. Scenario 1H: In option 1-1, the timer newly defined in R19 times out (this timer starts when the UE's MR begins listening to the PDCCH, equivalent to the OnDuration timer in the DRX mechanism). The UE is working in a dedicated BWP. When switching to MR, it works in the default BWP / initial BWP. Whether it switches to the MR inactive state depends on further instructions from the base station, or it may switch to the MR inactive state after listening in the default BWP / initial BWP for a period of time. The LR waits for the next LR listening window before starting work.
[0131] Scenario 1I: In option 1-1, the newly defined timer in R19 times out (this timer starts when the UE's MR begins listening to the PDCCH, equivalent to the OnDuration timer in the DRX mechanism). The UE operates in the default BWP / initial BWP and directly jumps to the MR inactive state. LR waits until the next LR listening window to resume operation. Scenario 1J: In option 1-1, the bwp-InactivityTimer times out. The UE operates in the dedicated BWP and directly jumps to the MR inactive state. LR waits until the next LR listening window to resume operation.
[0132] It is worth noting that in the working mode option1-2 scenario, the working mode of MR in UE is similar as shown in Table 1. The difference is that in working mode option1-1, whether LR is working is determined by the LR's listening window, while in working mode option1-2, LR enters the working state during the time period when MR is not working.
[0133] The following section further illustrates the above method with reference to the example shown in Figure 10. Figure 10 is presented from the perspective of the interaction between the UE and the gNB.
[0134] The method shown in Figure 10 may include steps S1000 to S1040, which are described below.
[0135] In S1000, the UE sends capability information to the gNB, which indicates that the UE supports the combined use of the DRX mechanism, wake-up mechanism and BWP mechanism.
[0136] In S1010, the gNB sends RRC reconfiguration information to the UE, which indicates the UE's dedicated BWP.
[0137] In S1020, gNB sends LP-WUS to UE.
[0138] In S1030, the UE listens to LP-WUS via LR and listens to PDCCH on a dedicated BWP via MR.
[0139] In S1040, after the UE finishes listening to the PDCCH, the MR stops working until the next DRX cycle.
[0140] For specific examples of S1000, S1010, S1020, S1030 and S1040 above, please refer to the description corresponding to Figure 9 above, which will not be repeated here.
[0141] The method embodiments of this application have been described in detail above with reference to Figures 1 to 10. The apparatus embodiments of this application will be described in detail below with reference to Figures 11 to 14. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.
[0142] Figure 11 illustrates a first node for wireless communication according to an embodiment of this application. The first node can be a terminal device or a network device. As shown in Figure 11, the first node 1100 includes a first processing module 1110 and a first transceiver module 1120.
[0143] The first transceiver module 1120 is used to receive a wake-up signal through the first communication module.
[0144] In response to the wake-up signal, the first processing module 1110 is configured to listen to the PDCCH on the first BWP through the second communication module; wherein the first BWP is a dedicated BWP of the first node.
[0145] In some embodiments, when the first processing module 1110 listens to the PDCCH on the first BWP through the second communication module, it is specifically used to: listen to the PDCCH directly on the first BWP through the second communication module.
[0146] In some embodiments, when the first processing module 1110 listens to the PDCCH on the first BWP through the second communication module, it is specifically used for:
[0147] Switching from the second BWP to the first BWP, and listening to the PDCCH on the first BWP through the second communication module, wherein the second BWP is the default BWP or the initial BWP.
[0148] In some embodiments, the first processing module 1110 is further configured to: after the second communication module finishes listening to the PDCCH in the first BWP, the second communication module directly stops working.
[0149] In some embodiments, the first processing module 1110 is further configured to: switch from the first BWP to the second BWP after the first BWP finishes listening to the PDCCH via the second communication module, and then jump from the second BWP to the state where the second communication module stops working.
[0150] In some embodiments, the wake-up signal includes first indication information, which is used to indicate the first BWP.
[0151] In some embodiments, the first transceiver module 1120 is further configured to: receive first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
[0152] In some embodiments, the first transceiver module 1120 is further configured to: receive second configuration information, the second configuration information including parameters of a discontinuous reception period; wherein the discontinuous reception period includes a wake-up time and a sleep time, and during the wake-up time, the second communication module listens to the PDCCH on the first BWP.
[0153] In some embodiments, the first transceiver module 1120 is further configured to: send capability information, the capability information being used to indicate that the first node supports the BWP mechanism and the wake-up mechanism.
[0154] In some embodiments, the capability information includes at least one of the following: supporting at least four different BWPs; supporting a combination of BWPs with a bandwidth of 5MHz or more and a wake-up mechanism; supporting a combination of BWPs with a bandwidth of less than 400MHz and a wake-up mechanism; supporting BWPs with a subcarrier spacing of 10kHz or more; or supporting BWPs with a subcarrier spacing of less than 60kHz.
[0155] As one embodiment, the first processing module 1110 may be a processor 1310. The first node 1100 may also include a memory 1320 and a transceiver 1330, as shown in FIG13.
[0156] Figure 12 illustrates a second node for wireless communication according to an embodiment of this application. The second node can be a network-side device or entity used for positioning, such as a gNB. As shown in Figure 12, the second node 1200 includes a second transceiver module 1210.
[0157] The second transceiver module 1210 is configured to: send a wake-up signal, the wake-up signal being used to trigger the first node to receive the wake-up signal through the first communication module of the first node; and listen to the PDCCH on the first BWP through the second communication module of the first node; wherein the first BWP is a dedicated BWP of the first node.
[0158] As one embodiment, the wake-up signal includes first indication information, which is used to indicate the first BWP.
[0159] As an example, the second transceiver module 1210 is further configured to: send first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
[0160] As one embodiment, the second transceiver module 1210 is further configured to: send second configuration information, the second configuration information including parameters of discontinuous reception periods;
[0161] The discontinuous reception period includes wake-up time and sleep time. During the wake-up time, the second communication module listens for the PDCCH on the first BWP.
[0162] As an example, the second transceiver module 1210 is further configured to: receive capability information, the capability information being used to indicate that the first node supports the BWP mechanism and the wake-up mechanism.
[0163] As an example, the capability information includes at least one of the following: supporting at least 4 different BWPs; supporting a combination of BWPs with a bandwidth of 5MHz or more and a wake-up mechanism; supporting a combination of BWPs with a bandwidth of 400MHz or less and a wake-up mechanism; supporting BWPs with a subcarrier spacing of 10kHz or more; or, supporting BWPs with a subcarrier spacing of 60kHz or less.
[0164] As one embodiment, the second transceiver module 1210 can be a transceiver 1330. The second node 1200 may also include a memory 1320 and a processor 1310, as shown in FIG13.
[0165] Figure 13 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 13 indicate that the unit or module is optional. This device 1300 can be used to implement the methods described in the above method embodiments. Device 1300 can be a chip, user equipment, or network device.
[0166] Apparatus 1300 may include one or more processors 1310. The processor 1310 may support apparatus 1300 in implementing the methods described in the preceding method embodiments. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0167] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store a program that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the preceding method embodiments. The memories 1320 may be independent of the processor 1310 or integrated within the processor 1310.
[0168] The device 1300 may also include a transceiver 1330. The processor 1310 can communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 can send and receive data with other devices or chips via the transceiver 1330.
[0169] Figure 14 is a schematic diagram of the hardware modules of the communication device provided in this application embodiment. Specifically, Figure 14 shows a block diagram of a first communication device 1450 and a second communication device 1410 communicating with each other in the access network.
[0170] The first communication device 1450 includes a controller / processor 1459, a memory 1460, a data source 1467, a transmitter processor 1468, a receiver processor 1456, a multi-antenna transmitter processor 1457, a multi-antenna receiver processor 1458, a transmitter / receiver 1454, and an antenna 1452.
[0171] The second communication device 1410 includes a controller / processor 1475, a memory 1476, a data source 1477, a receiver processor 1470, a transmitter processor 1416, a multi-antenna receiver processor 1472, a multi-antenna transmitter processor 1471, a transmitter / receiver 1418, and an antenna 1420.
[0172] In the transmission from the second communication device 1410 to the first communication device 1450, at the second communication device 1410, upper-layer data packets from the core network or from the data source 1477 are provided to the controller / processor 1475. The core network and data source 1477 represent all protocol layers above the L2 layer. The controller / processor 1475 implements the functionality of the L2 layer. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication device 1450 based on various priority metrics. The controller / processor 1475 is also responsible for retransmitting lost packets and signaling to the first communication device 1450. The transmit processor 1416 and the multi-antenna transmit processor 1471 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 1416 performs encoding and interleaving to facilitate forward error correction at the second communication device 1410, and mapping of signal clusters based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). Multi-antenna transmit processor 1471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 1416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 1471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 1418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 1471 into an radio frequency stream, which is then provided to different antennas 1420.
[0173] In the transmission from the second communication device 1410 to the first communication device 1450, at the first communication device 1450, each receiver 1454 receives a signal through its corresponding antenna 1452. Each receiver 1454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 1456. The receiver processor 1456 and the multi-antenna receiver processor 1458 implement various signal processing functions of Layer 1. The multi-antenna receiver processor 1458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 1454. The receiver processor 1456 uses a fast Fourier transform to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 1456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 1458 after multi-antenna detection to recover any spatial stream destined for the first communication device 1450. Symbols on each spatial stream are demodulated and recovered in the receive processor 1456, generating soft decisions. The receive processor 1456 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the second communication device 1410 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 1459. The controller / processor 1459 implements the functions of Layer 2. The controller / processor 1459 may be associated with a memory 1460 storing program code and data. The memory 1460 may be referred to as computer-readable media. In the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the second communication device 1410. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.
[0174] In the transmission from the first communication device 1450 to the second communication device 1410, at the first communication device 1450, upper-layer data packets are provided to the controller / processor 1459 using a data source 1467. The data source 1467 represents all protocol layers above Layer 2. Similar to the transmission functions at the second communication device 1410 described in the transmission from the second communication device 1410 to the first communication device 1450, the controller / processor 1459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between the logical and transport channels, implementing Layer 2 functions for the user plane and control plane. The controller / processor 1459 is also responsible for retransmitting lost packets and signaling to the second communication device 1410. Transmit processor 1468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 1457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 1468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 1457, the stream is provided to different antennas 1452 via transmitter 1454. Each transmitter 1454 first converts the baseband symbol stream provided by multi-antenna transmit processor 1457 into a radio frequency symbol stream before providing it to antenna 1452.
[0175] In the transmission from the first communication device 1450 to the second communication device 1410, the function at the second communication device 1410 is similar to the receiving function at the first communication device 1450 described in the transmission from the second communication device 1410 to the first communication device 1450. Each receiver 1418 receives radio frequency signals through its corresponding antenna 1420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 1472 and the receiving processor 1470. The receiving processor 1470 and the multi-antenna receiving processor 1472 jointly implement the L1 layer function. The controller / processor 1475 implements the L2 layer function. The controller / processor 1475 may be associated with a memory 1476 that stores program code and data. The memory 1476 may be referred to as computer-readable media. In the transmission from the first communication device 1450 to the second communication device 1410, the controller / processor 1475 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the first communication device 1450. The upper-layer data packets from the controller / processor 1475 can be provided to the core network or all protocol layers above Layer 2, and various control signals can also be provided to the core network or Layer 3 for Layer 3 processing.
[0176] As one embodiment, the first communication device 1450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor.
[0177] As one embodiment, the first communication device 1450 includes: a memory storing a computer-readable instruction program that produces action when executed by at least one processor.
[0178] As an example, the first communication device 1450 corresponds to the first node in this application.
[0179] As one embodiment, the second communication device 1410 corresponds to the second node in this application.
[0180] As an example, the first communication device 1450 is a user equipment that can act as a relay node.
[0181] As an example, the first communication device 1450 is a network control relay (NCR).
[0182] As an example, the first communication device 1450 is a relay wireless repeater.
[0183] As an example, the first communication device 1450 is a relay.
[0184] As one embodiment, the second communication device 1410 is a Location Management Function (LMF).
[0185] As an example, the first communication device 1450 corresponds to the first node in this application, and the controller / processor 1159 is used to execute the above method.
[0186] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in various embodiments of this application.
[0187] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.
[0188] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.
[0189] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.
[0190] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0191] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.
[0192] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.
[0193] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including user equipment and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.
[0194] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.
[0195] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0196] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0197] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0198] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0199] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0200] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.
[0201] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for a first node in wireless communication, characterized in that, The method is applied to a first node including a first communication module and a second communication module, including: The wake-up signal is received through the first communication module; In response to the wake-up signal, the PDCCH is monitored on the first BWP via the second communication module; wherein the first BWP is a dedicated BWP for the first node.
2. The method according to claim 1, characterized in that, Listening to the PDCCH on the first BWP via the second communication module includes: The second communication module directly listens to the PDCCH on the first BWP.
3. The method according to claim 1, characterized in that, Listening to the PDCCH on the first BWP via the second communication module includes: Switching from the second BWP to the first BWP, and listening to the PDCCH on the first BWP through the second communication module, wherein the second BWP is the default BWP or the initial BWP.
4. The method according to any one of claims 1 to 3, characterized in that, Also includes: Once the PDCCH listening by the first BWP ends via the second communication module, the second communication module stops working directly.
5. The method according to claim 3, characterized in that, Also includes: When the PDCCH listening of the first BWP ends through the second communication module, the system switches from the first BWP to the second BWP, and then jumps from the second BWP to the state where the second communication module stops working.
6. The method according to any one of claims 1 to 5, characterized in that, The wake-up signal includes first indication information, which is used to indicate the first BWP.
7. The method according to any one of claims 1 to 5, characterized in that, Also includes: Receive first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
8. The method according to any one of claims 1 or 5, characterized in that, Also includes: Receive second configuration information, which includes parameters for discontinuous reception periods; The discontinuous reception period includes wake-up time and sleep time. During the wake-up time, the second communication module listens for the PDCCH on the first BWP.
9. The method according to any one of claims 1 to 8, characterized in that, Also includes: Send capability information, which indicates that the first node supports the BWP mechanism and the wake-up mechanism.
10. The method according to claim 9, characterized in that, The capability information includes at least one of the following: Supports at least 4 different BWPs; Supports BWP with bandwidth of 5MHz or higher combined with wake-up mechanisms; Supports BWP with bandwidth below 400MHz and wake-up mechanism combination; Supports BWP with a subcarrier spacing of 10kHz or higher; Alternatively, it supports BWP with a subcarrier spacing of less than 60kHz.
11. A method for a second node in wireless communication, characterized in that, include: Send a wake-up signal, the wake-up signal being used to trigger the first node to receive the wake-up signal through the first communication module of the first node; And listen to the PDCCH on the first BWP through the second communication module of the first node; wherein, the first BWP is a dedicated BWP of the first node.
12. The method according to claim 11, characterized in that, The wake-up signal includes first indication information, which is used to indicate the first BWP.
13. The method according to claim 11 or 12, characterized in that, Also includes: Send first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
14. The method according to claim 11 or 12, characterized in that, Also includes: Send second configuration information, which includes parameters for discontinuous reception periods; The discontinuous reception period includes wake-up time and sleep time. During the wake-up time, the second communication module listens for the PDCCH on the first BWP.
15. The method according to any one of claims 11 to 14, characterized in that, Also includes: The first node receives capability information, which indicates that it supports the BWP mechanism and the wake-up mechanism.
16. The method according to claim 15, characterized in that, The capability information includes at least one of the following: Supports at least 4 different BWPs; Supports BWP with bandwidth of 5MHz or higher combined with wake-up mechanisms; Supports BWP with bandwidth below 400MHz and wake-up mechanism combination; Supports BWP with a subcarrier spacing of 10kHz or higher; Alternatively, it supports BWP with a subcarrier spacing of less than 60kHz.
17. A first node for wireless communication, characterized in that, It includes a first processing module and a first transceiver module; The first transceiver module is used to receive a wake-up signal through the first communication module of the first node; In response to the wake-up signal, the first processing module is configured to listen to the PDCCH on the first BWP through the second communication module of the first node; wherein the first BWP is a dedicated BWP of the first node.
18. The first node according to claim 17, characterized in that, When the first processing module listens to the PDCCH on the first BWP through the second communication module, it is specifically used for: The second communication module directly listens to the PDCCH on the first BWP.
19. The first node according to claim 17, characterized in that, When the first processing module listens to the PDCCH on the first BWP through the second communication module, it is specifically used for: Switching from the second BWP to the first BWP, and listening to the PDCCH on the first BWP through the second communication module, wherein the second BWP is the default BWP or the initial BWP.
20. The first node according to any one of claims 17 to 19, characterized in that, The first processing module is also used for: Once the PDCCH listening by the first BWP ends via the second communication module, the second communication module stops working directly.
21. The first node according to claim 19, characterized in that, The first processing module is also used for: When the PDCCH listening of the first BWP ends through the second communication module, the system switches from the first BWP to the second BWP, and then jumps from the second BWP to the state where the second communication module stops working.
22. The first node according to any one of claims 17 to 21, characterized in that, The wake-up signal includes first indication information, which is used to indicate the first BWP.
23. The first node according to any one of claims 17 to 21, characterized in that, The first transceiver module is also used for: Receive first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
24. The first node according to any one of claim 17 or 21, characterized in that, The first transceiver module is also used for: Receive second configuration information, which includes parameters for discontinuous reception periods; The discontinuous reception period includes wake-up time and sleep time. During the wake-up time, the second communication module listens for the PDCCH on the first BWP.
25. The first node according to any one of claims 17 to 24, characterized in that, The first transceiver module is also used for: Send capability information, which indicates that the first node supports the BWP mechanism and the wake-up mechanism.
26. The first node according to claim 25, characterized in that, The capability information includes at least one of the following: Supports at least 4 different BWPs; Supports BWP with bandwidth of 5MHz or higher combined with wake-up mechanisms; Supports BWP with bandwidth below 400MHz and wake-up mechanism combination; Supports BWP with a subcarrier spacing of 10kHz or higher; Alternatively, it supports BWP with a subcarrier spacing of less than 60kHz.
27. A second node for wireless communication, characterized in that, Includes a second transceiver module, used for: Sending a wake-up signal, the wake-up signal being used to trigger the first node to receive the wake-up signal through the first communication module of the first node; and listening to the PDCCH on the first BWP through the second communication module of the first node; wherein, the first BWP is a dedicated BWP of the first node.
28. The second node according to claim 27, characterized in that, The wake-up signal includes first indication information, which is used to indicate the first BWP.
29. The second node according to claim 27 or 28, characterized in that, The second transceiver module is also used for: Send first configuration information, the first configuration information including second indication information, the second indication information being used to indicate the first BWP.
30. The second node according to claim 27 or 28, characterized in that, The second transceiver module is also used for: Send second configuration information, which includes parameters for discontinuous reception periods; The discontinuous reception period includes wake-up time and sleep time. During the wake-up time, the second communication module listens for the PDCCH on the first BWP.
31. The second node according to any one of claims 27 to 30, characterized in that, The second transceiver module is also used for: The first node receives capability information, which indicates that it supports the BWP mechanism and the wake-up mechanism.
32. The second node according to claim 31, characterized in that, The capability information includes at least one of the following: Supports at least 4 different BWPs; Supports BWP with bandwidth of 5MHz or higher combined with wake-up mechanisms; Supports BWP with bandwidth below 400MHz and wake-up mechanism combination; Supports BWP with a subcarrier spacing of 10kHz or higher; Alternatively, it supports BWP with a subcarrier spacing of less than 60kHz.
33. A node used for wireless communication, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the node performs the method as described in any one of claims 1-10 or 11-16.
34. A communication device, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-10 or 11-16.
35. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-10 or 11-16.
36. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-10 or 11-16.
37. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-10 or 11-16.
38. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-10 or 11-16.