WO2021013104A1 - 一种唤醒信号wus检测方法及装置 - Google Patents

一种唤醒信号wus检测方法及装置 Download PDF

Info

Publication number
WO2021013104A1
WO2021013104A1 PCT/CN2020/102843 CN2020102843W WO2021013104A1 WO 2021013104 A1 WO2021013104 A1 WO 2021013104A1 CN 2020102843 W CN2020102843 W CN 2020102843W WO 2021013104 A1 WO2021013104 A1 WO 2021013104A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
wus
pucch
information
wake
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.)
Ceased
Application number
PCT/CN2020/102843
Other languages
English (en)
French (fr)
Inventor
周涵
铁晓磊
花梦
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20844418.2A priority Critical patent/EP3996427B1/en
Publication of WO2021013104A1 publication Critical patent/WO2021013104A1/zh
Priority to US17/579,368 priority patent/US12108332B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0251Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0212Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0261Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1861Physical mapping arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signalling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of wireless communication technology, and in particular to a method and device for detecting a wake-up signal WUS.
  • the network side device can send a physical downlink control channel (Physical Downlink Control Channel, PDCCH) wake-up signal (Wake-up signal, WUS) to multiple user equipment (User Equipment, UE) through Group-based WUS (group-based wake-up signal) ), the Group-based WUS carries wake-up information for waking up the UE, and also carries information for indicating physical uplink control channel (PUCCH) resources for each UE to feedback information.
  • PUCCH Physical Uplink control channel
  • the UE can use the PUCCH resource used to indicate the UE feedback information to feed back to the network side device whether a wake-up information message is received.
  • the information indication generally used to indicate the PUCCH resource for each UE to feedback information needs to occupy 4-6 bits. Assuming that a Group-based WUS indicates a total of 5 UEs, the PUCCH resource information used to indicate the feedback information of these 5 UEs in the Group-based WUS needs to occupy 25 bits, plus the wake-up information used to wake up the UE. It may exceed the number of bits that can be carried by Group-based WUS, or affect the receiving performance of WUS.
  • the usual approach is to reduce the number of UEs indicated in each Group-based WUS, and correspondingly reduce the PUCCH resource information that is used to indicate UE feedback information carried in the Group-based WUS.
  • the total number of UEs that need to be indicated is reduced.
  • the embodiments of the present application provide a WUS detection method and device.
  • the PUCCH resource is not indicated in the WUS issued by the network-side device, thereby reducing the signaling overhead of the network-side device.
  • a WUS detection method is provided.
  • the network side device sends the WUS to the terminal device, and the WUS includes the dedicated domain of the terminal device.
  • the terminal device detects the dedicated domain of the terminal device in the detected WUS; if the dedicated domain of the terminal device is detected in WUS, and the wake-up information of the terminal device is detected in WUS, the terminal device determines the specific domain in the pre-configured PUCCH resource.
  • the first PUCCH resource corresponding to the terminal device sends a first PUCCH, and the first PUCCH includes a first message for feeding back the wake-up information of the terminal device.
  • the network side device receives the first PUCCH, and determines that the terminal device has received the wake-up information according to the first message included in the first PUCCH for feeding back the wake-up information of the terminal device.
  • the WUS can be UE-specific PDCCH WUS, or Group-based WUS.
  • the WUS may include the PUCCH transmission time offset, and may also include information indicating time-frequency resource switching, and the information indicating time-frequency resource switching may include information indicating BWP switching.
  • the terminal device is pre-configured with the PUCCH resource for feedback information, and the network side device does not indicate the PUCCH resource for the feedback information of the terminal device when sending WUS to the terminal device, which can reduce the number of bits occupied by the PUCCH resource in WUS. Therefore, one WUS can carry wake-up information of more terminal devices and instruct more terminal devices to wake up. When the number of instructed terminal devices remains unchanged, the signaling overhead of the network-side device WUS can be saved.
  • the network side device may send a second message to the terminal device before sending the WUS to the terminal device, and the terminal device receives the second message, and the second message is used to pre-configure PUCCH resources.
  • the PUCCH resource preconfigured in the second message may be the first PUCCH resource used when only the terminal device feeds back information, or may include the first PUCCH resource used when multiple terminal devices feed back information, where the multiple terminal devices Including the terminal equipment.
  • the second message may be RRC signaling, or reuse other existing signaling, or a predefined new command.
  • the network side device configures PUCCH resources for the terminal device in advance. After the terminal device configures the PUCCH resource, the network side device sends WUS to the terminal device. The sent WUS does not indicate the PUCCH resource for the terminal device feedback information, so it can reduce The signaling overhead of PUCCH resources in WUS.
  • the second message sent by the network side device to the terminal device is specifically used to configure the uplink BWP of the terminal device and configure the first PUCCH resource for each uplink BWP.
  • the network side device can also pre-configure the uplink BWP and the PUCCH resources on the uplink BWP for the terminal device, and the terminal device can switch to the uplink BWP to send uplink control information.
  • the terminal device determines the identification information of the terminal device, and based on the identification information and WIF, determines the location of the terminal device's dedicated domain in WUS; the terminal device determines the terminal device's dedicated domain The first PUCCH resource corresponding to the location information of the domain.
  • the identification information of the terminal device may include one or more of the identifier of the terminal device, the terminal device ID, and the RNTI of the terminal device.
  • the terminal device may perform calculations on the identification information of the second terminal device and WIF, such as addition, subtraction, multiplication, division (the result of the division operation can be rounded down or rounded up), modulo operation, etc. , According to the calculation result, determine the location information of the dedicated domain of the second terminal device in the WUS.
  • the terminal device may use the location information of the dedicated domain of the terminal device as the first index, and determine the first PUCCH resource corresponding to the first index in the pre-configured PUCCH resource, where the second terminal device may indicate the terminal device to be awakened .
  • the network side device and the terminal device can determine the location of the terminal device’s dedicated domain in WUS according to the terminal device’s identification information and WIF, and the terminal device indicated in the WUS can be several non-fixed terminal devices. It can flexibly instruct the terminal device to wake up in the dedicated domain of different terminal devices according to WIF.
  • the terminal device determines the identification information of the terminal device, and according to the identification information, determines the location of the terminal device's private domain in WUS; the terminal device determines the terminal device's private domain The first PUCCH resource corresponding to the location information of.
  • the terminal device may use the location information of the dedicated domain of the terminal device as the first index, and determine the first PUCCH resource corresponding to the first index among the pre-configured PUCCH resources.
  • the network side device and the terminal device can determine the location of the dedicated domain of the terminal device in the WUS according to the identification information of the terminal device, thereby determining the first PUCCH resource corresponding to the location information of the dedicated domain of the terminal device.
  • the WUS or the second message also includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between receiving WUS and sending PUCCH feedback information Or the time interval between the time when the terminal device starts the wake-up mode of discontinuous reception of the DRX state and the time when the PUCCH feedback information is sent.
  • a WUS detection method is provided.
  • a network side device sends a WUS to a terminal device, and the WUS includes a dedicated domain of the terminal device;
  • the terminal device detects the dedicated domain of the terminal device in the detected WUS
  • the terminal device uses the location information of the dedicated domain of the terminal device as the first index to determine the first index corresponding to the first index.
  • PUCCH resource, sending the first PUCCH, the first PUCCH includes a first message used to feed back received wake-up information of the terminal device; the network side device receives the first PUCCH sent by the terminal device using the pre-configured first PUCCH resource; according to The first message included in the first PUCCH for feeding back the received wake-up information of the terminal device determines that the terminal device receives the wake-up information.
  • the network side device sends a second message to the terminal device before sending the WUS to the terminal device, and the terminal device receives the second message sent by the network side device, and the second message is used to configure the terminal device to feedback information The first PUCCH resource used at the time.
  • the terminal device determines the identification information of the terminal device; based on the identification information and the WIF, determines the location of the dedicated domain of the terminal device in the WUS.
  • the terminal device determines the location of the dedicated domain of the terminal device in WUS according to the identification information of the terminal device; according to the identification information.
  • the WUS or the second message also includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between receiving WUS and sending PUCCH feedback information Or the time interval between the time when the terminal device starts the wake-up mode of discontinuous reception of the DRX state and the time when the PUCCH feedback information is sent.
  • a WUS detection method is provided.
  • the network side device sends WUS to the terminal device, and the WUS includes the dedicated domain of the terminal device; the terminal device detects the dedicated domain of the terminal device in the detected WUS; The dedicated domain of the terminal device is detected in the WUS, and it is detected that the WUS includes the wake-up information of the terminal device, the terminal device uses the pre-configured first physical uplink control channel PUCCH resource to send the first PUCCH ,
  • the first PUCCH includes a first message for feeding back the wake-up information of the terminal device; the network side device receives the first PUCCH sent by the terminal device using the pre-configured first PUCCH resource; according to the first PUCCH
  • the first message used to feed back the received wake-up information of the terminal device included in the determines that the terminal device receives the wake-up information.
  • the WUS is UE-specific PDCCH WUS.
  • the terminal device if the terminal device does not detect the UE-specific PDCCH WUS, the terminal device tries to detect the Group-based WUS.
  • the terminal device uses the pre-configured second PUCCH resource to send the second PUCCH, and the second PUCCH includes a method for feeding back that the WUS is not received.
  • the network side device receives the second PUCCH resource sent by the terminal device using the second PUCCH resource; according to the third message included in the second PUCCH for feedback that the Group-based WUS is not received, it is determined that the terminal device has not received it To wake up information.
  • the network side device may pre-configure a second PUCCH for the terminal device, and the second PUCCH information is used to feed back a message that the terminal device has not received the wake-up information.
  • the network side device sends a second message to the terminal device before sending the WUS to the terminal device, and the terminal device receives the second message sent by the network side device, and the second message is used to configure the terminal device to feedback information The first PUCCH resource used at the time.
  • the terminal device determines the identification information of the terminal device; based on the identification information and the WIF, determines the location of the dedicated domain of the terminal device in the WUS.
  • the terminal device determines the location of the dedicated domain of the terminal device in WUS according to the identification information of the terminal device; according to the identification information.
  • the WUS or the second message also includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between receiving WUS and sending PUCCH feedback information Or the time interval between the time when the terminal device starts the wake-up mode of discontinuous reception of the DRX state and the time when the PUCCH feedback information is sent.
  • a WUS detection method is provided.
  • the terminal device tries to detect UE-specific PDCCH WUS; if UE-specific PDCCH WUS is detected, it is determined to receive WUS; if UE-specific PDCCH WUS is not detected, the terminal device tries to detect Group -based WUS; If Group-based WUS is not detected, the terminal device determines that the downlink channel quality is poor and can perform link reply.
  • the terminal device can use the second PUCCH resource to send the second PUCCH.
  • the terminal device detects the dedicated domain of the terminal device and the wake-up information of the terminal device in Group-based WUS. If the dedicated domain of the terminal device or the wake-up information of the terminal device is not detected, determine the network side device and The terminal device is not awakened. If Group-based WUS is detected, and the dedicated domain of the terminal device and the wake-up information of the terminal device are detected in the Group-based WUS, it is determined that the network side wakes up the terminal device.
  • the terminal device detects the dedicated domain of the terminal device in Group-based WUS, and if the dedicated domain of the terminal device is detected, the terminal device is detected in the dedicated domain of the terminal device Wake-up information.
  • a WUS detection device in a fifth aspect, has the function of realizing the terminal device or the network side device in the above method, and it includes means for executing the steps or functions described in the above method.
  • the steps or functions can be realized by software, or by hardware (such as a circuit), or by a combination of hardware and software.
  • the foregoing device includes one or more processors and communication units.
  • the one or more processors are configured to support the apparatus to perform the corresponding functions of the terminal device or the network side device in the foregoing method.
  • the device may further include one or more memories, where the memory is used for coupling with the processor and stores necessary program instructions and/or data for the device.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the foregoing device may include a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory so that the device executes the first aspect or any one of the first aspect It is possible to implement the method completed by the terminal device or the network side device in the manner.
  • the foregoing device includes one or more processors and communication units.
  • the one or more processors are configured to support the apparatus to perform the corresponding functions of the terminal device or the network side device in the foregoing method.
  • the device may further include one or more memories, which are used for coupling with the processor and store necessary program instructions and/or data for the terminal device or the network side device.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the device may be located in a terminal device or a network side device, or be a terminal device or a network side device.
  • the above device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory so that the device executes the above-mentioned first, second, and third aspects.
  • the fourth aspect, or the method performed by the terminal device or the network-side device in any one of the possible implementation manners of the first aspect, the second aspect, the third aspect, and the fourth aspect.
  • a computer-readable storage medium for storing a computer program.
  • the computer program includes a computer program for executing the first aspect, the second aspect, the third aspect, the fourth aspect, or the first aspect and the fourth aspect.
  • the instruction of the method in any one of the possible implementation modes of the second, third, and fourth aspects.
  • a computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the first, second, and third aspects above , The fourth aspect, or the method in any one of the possible implementation manners of the first, second, third, and fourth aspects.
  • a communication system in an eighth aspect, includes a network-side device and a terminal device.
  • the network-side device and the terminal device are used to implement the first, second, third, and third aspects described above.
  • Figure 1 is a schematic diagram of a DRX cycle
  • Figure 2 is a schematic diagram of a Group-based WUS signal format
  • Figure 3 is a schematic diagram of a terminal device switching BWP
  • FIG. 4 is a schematic diagram of a WUS detection process applicable in the embodiments of this application.
  • FIG. 5 is a schematic structural diagram of a WUS applicable in an embodiment of this application.
  • FIG. 6 is a schematic structural diagram of a WUS applicable in an embodiment of this application.
  • FIG. 7 is a schematic diagram of searching for a PUCCH resource applicable in an embodiment of this application.
  • FIG. 8 is a schematic diagram of a PUCCH feedback applicable in an embodiment of this application.
  • FIG. 9 is a schematic diagram of a WUS detection process applicable in an embodiment of this application.
  • FIG. 10 is a schematic diagram of a WUS detection process applicable in an embodiment of this application.
  • FIG. 11 is a structural diagram of a WUS detection device applicable in an embodiment of this application.
  • FIG. 12 is a structural diagram of a WUS detection device applicable in the embodiments of this application.
  • the term "exemplary” is used to indicate an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the term example is used to present the concept in a concrete way.
  • a terminal device can be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • a wireless terminal can communicate with one or more core networks via a radio access network (RAN).
  • the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal For example, they can be portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices, which exchange language and/or data with the wireless access network.
  • Wireless terminals can also be called systems, subscriber units (Subscriber Unit), subscriber stations (Subscriber Station), mobile stations (Mobile Station), mobile stations (Mobile), remote stations (Remote Station), access points (Access Point), Remote terminal (Remote Terminal), access terminal (Access Terminal), user terminal (User Terminal), user agent (User Agent), user equipment (User Device), or user equipment (User Equipment).
  • Examples of other terminal devices are: mobile phones (mobile phones), tablets, laptops, handheld computers, mobile internet devices (mobile internet devices, MID), smart point of sale (POS), wearable devices, virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, etc.
  • the network side equipment located in the communication system, can provide connection services for the terminal equipment and can connect the terminal equipment to the Internet.
  • the network device may be a base station device or an access point in a communication system.
  • Base station equipment such as gNode B (gNB), gateway (gateway) equipment, ground station equipment, etc.
  • the network device may also be a non-terrestrial network gateway/satellite gateway (Non-terrestrial networks Gateway, NTN-Gateway) etc. in a satellite communication system.
  • WUS Wake-up signal
  • WUS may include a dedicated domain for terminal equipment.
  • the terminal device in the idle state, the terminal device is generally in a dormant state, and the terminal device tries to receive WUS. If it receives WUS, the terminal device will continue to try to receive a paging message (Paging) for waking up. If the terminal device does not receive WUS, The terminal device will not try to receive Paging and continue to sleep, thereby saving the power consumption of the terminal device.
  • WUS may include a user equipment dedicated PDCCH wake-up signal (UE-specific PDCCH WUS), and/or Group-based WUS.
  • UE-specific PDCCH WUS user equipment dedicated PDCCH wake-up signal
  • Group-based WUS Group-based WUS.
  • the UE specific field(s) of the terminal equipment is also called the dedicated bit field of the terminal equipment, and the dedicated field of the terminal equipment is included in the WUS.
  • the dedicated field of a terminal device refers to a bit field that carries information allocated for a specific terminal device.
  • the dedicated domain of the terminal device is used to carry related information of the terminal device, and is used to indicate the wake-up information of the terminal device and other related information of the terminal device.
  • other related information of the terminal device includes information indicating time-frequency resource switching.
  • the time-frequency resource switching information may include information indicating BWP switching.
  • the network-side equipment and terminal equipment can determine the dedicated domain of the terminal device in WUS through the position of the dedicated domain of the terminal device. The position of the dedicated domain of the terminal device can be used to indicate the order in which the dedicated domain of the terminal device appears in WUS, or to indicate The private domain of the terminal device is the first private domain in WUS.
  • the wake-up information of the terminal device is used to instruct the terminal device to wake up.
  • the wake-up information of the terminal device can be included in WUS, and WUS indicates the wake-up of the terminal device.
  • WUS can explicitly instruct the terminal device to wake up, or WUS can implicitly instruct the terminal device to wake up.
  • the terminal device's dedicated field in WUS indicates the wake-up information of the terminal device, and the specific bit of the terminal device's dedicated field indicates the wake-up of the terminal device; in the case of implicit indication, WUS indicates the terminal device The wake-up information of the terminal device is indicated by the WUS.
  • WUS is UE-specific PDCCH WUS
  • UE-specific PDCCH WUS implicitly indicates the wake-up information of the terminal device.
  • the terminal device detects the UE-specific PDCCH WUS, it can determine that the wake-up information of the terminal device is detected.
  • WUS is Group-based WUS
  • Group-based WUS displays the wake-up information indicating the terminal device.
  • the terminal device detects Group-based WUS, it can also detect the wake-up of the terminal device in the dedicated domain of the terminal device in Group-based WUS information.
  • PUCCH resource the uplink resource used when the terminal device sends uplink control information.
  • the terminal device can feed back information to the network side device through the PUCCH resource, such as hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ) feedback information.
  • Hybrid Automatic Repeat request Hybrid Automatic Repeat request, HARQ
  • the "and/or” in this application describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. This situation.
  • the character "/" generally indicates that the associated objects are in an "or” relationship.
  • the multiple involved in this application refers to two or more.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as the fourth generation (4th Generation, 4G), the 4G system includes the long term evolution (LTE) system, and the worldwide interconnection for microwave access (worldwide interoperability).
  • 4G fourth generation
  • LTE long term evolution
  • WiMAX microwave access
  • 5G future 5th Generation
  • NR new-generation radio access technology
  • 6G systems future communication systems, such as 6G systems.
  • the 3GPP standards organization is currently formulating a protocol standard for the 5th Generation (5th Generation, 5G) cellular mobile communication system.
  • 5G is also known as the New Radio (NR).
  • NR New Radio
  • LTE Long Term Evolution
  • NR supports a larger transmission bandwidth, more transceiver antenna arrays, higher transmission rates, and a more flexible, smaller-granularity scheduling mechanism.
  • LTE Long Term Evolution
  • NR provides more scope of application based on the above characteristics, it greatly increases the power consumption burden of terminal equipment.
  • 3GPP introduced the Power saving research topic in the NR rel-16 version. The purpose is to study the ability of terminal equipment to operate in various states (including Connection state, idle state, As well as possible power reduction solutions in the inactive state, how to save the power consumption of the terminal device in the Connection state is a research focus.
  • DRX Discontinuous Reception
  • the terminal device starts an inactive timer (inactive timer) in the active state of the connected state, and the terminal device continuously tries to receive the Physical Downlink Control Channel (PDCCH). If the terminal device receives the scheduling downlink control information (Downlink Control Information, DCI) on the PDCCH, the terminal device will restart the inactive timer. If the terminal device does not receive the scheduling DCI for a period of time, the inactive timer times out, the terminal device will Enter DRX inactive state.
  • DCI Downlink Control Information
  • the basic time unit in the DRX state is a DRX cycle (DRX cycle), and the length of the DRX cycle is the DRX cycle.
  • a DRX cycle consists of a Sleep (ie inactive) state and an On Duration. (Duration) State composition.
  • On Duration is the wake-up mode, also called DRX_ON.
  • On Duration is the wake-up mode, also called DRX_ON.
  • the terminal device will be awakened and monitor the PDCCH. Once the scheduled DCI is received in the PDCCH, the terminal device will restart the inactive timer. If the inactive timer finally times out, the terminal device will return to Sleep mode.
  • the Sleep state, or sleep mode is also called DRX_OFF.
  • the terminal device in Sleep mode can completely turn off communication devices such as the radio frequency transceiver and baseband processor to reduce power consumption.
  • the terminal device does not wake up when OnDuration arrives, but wakes up in a few time slots before OnDuration arrives, and receives downlink reference signals for time-frequency offset synchronization to prevent the terminal
  • the system clock and working frequency deviate from the base station clock and working frequency due to the long sleep of the device; at the same time, the terminal device can also try to receive the downlink synchronization signal and update the system message first to prevent the terminal device from moving from one cell to another. Later, the system message deviated.
  • WUS is a control signal introduced in the Narrowband Internet of Things (NB-IoT) to reduce the power consumption of terminal equipment. It is mainly used in the idle state. In the paging mechanism. In the idle state, the terminal device is generally in a dormant state, but the terminal device needs to wake up every period of time to try to receive paging. The time when the terminal device is awakened to receive a paging is called a paging opportunity (Paging Occasion, PO). In an actual system, the base station does not send Paging to the terminal device at every PO.
  • Paging Occasion PO
  • the terminal device wakes up and receives Paging at the PO most of the time, which is an invalid operation and increases the power consumption of the terminal device. For this reason, WUS is introduced into the NB-IoT system. If the base station does send Paging to the terminal device in a certain PO, the base station will send WUS before the PO arrives, otherwise the base station will not send WUS. Correspondingly, the terminal device will try to receive WUS before the PO arrives. If the terminal device receives WUS, the terminal device will confirm that there is a Paging message in the next PO, and the terminal device will continue to try to receive Paging.
  • the terminal device will consider that there is no Paging message in the next PO, and the terminal device will not try to receive Paging and continue to sleep. Since the power consumption and complexity of the terminal device when receiving WUS is much smaller than the power consumption and complexity when the terminal device tries to receive Paging, and the probability of the base station sending Paging in the idle state of the terminal device is not high, it is determined by whether the WUS is received Whether the terminal device wakes up can greatly save the power consumption of the terminal device.
  • PDCCH-based WUS also known as PDCCH WUS, which means that WUS is carried by PDCCH.
  • WUS can be carried by PDCCH and DCI, that is, WUS can be carried by scheduling DCI in PDCCH.
  • PDCCH includes at least UE-specific PDCCH WUS (user equipment dedicated PDCCH wake-up signal) and Group-based (PDCCH) WUS (group-based wake-up signal).
  • UE-specific PDCCH WUS is a signal sent to a single terminal device, that is, PDCCH DCI only Carrying the WUS signal of a terminal device, the signal format of Group-based WUS can be seen in Figure 2.
  • Group-based WUS carries the WUS signal of N terminal devices, including dedicated domains of 1 to N terminal devices, that is, terminal
  • the device specific field(s) is also called the dedicated bit field of the terminal device.
  • the dedicated field of the terminal device carries the information of the WUS signal of the terminal device.
  • Group-based WUS also includes cyclic redundancy calibration. Cyclic Redundancy Check (CRC) bit.
  • CRC Cyclic Redundancy Check
  • the terminal device may check whether the received Group-based WUS is a normal WUS according to the CRC bit, instead of a false alarm WUS.
  • the PDCCH WUS may also carry other configuration information.
  • the other configuration information may include configuration parameters of the terminal device in a power saving state.
  • the other configuration information may include information indicating time-frequency resource switching, for example, including the bandwidth part (Bandwidth Part, BWP) of the terminal device after waking up.
  • BWP Bandwidth Part
  • the terminal device may reside on a BWP with a narrow bandwidth to detect WUS.
  • WUS indicates the working BWP after the terminal device wakes up.
  • the working BWP has a larger bandwidth and a higher data transmission rate, which is more convenient for the terminal device to perform data transmission on the working BWP after waking up.
  • PDCCH WUS can carry targets For the identification information of the BWP, the terminal device parses the identification information of the BWP in the PDCCH WUS, and switches to the new target BWP for data transmission.
  • the UE-specific PDCCH WUS can carry a large amount of configuration information of the terminal device, and the large amount of configuration information of the terminal device may occupy a resource in the entire PDCCH, and the resource overhead is relatively large.
  • Group-based WUS can carry more terminal device configuration information, but each terminal device may carry less configuration information, and network side devices use Group-based WUS to wake up terminal devices When compared with UE-specific PDCCH WUS, it can occupy less downlink control signaling.
  • the information indicating time-frequency resource switching needs to have high reliability. This is because if the information indicating time-frequency resource switching is received incorrectly or missed, the terminal device will not switch to the time-frequency resource designated by the network side device to receive the downlink At this time, the network side device has switched to the designated time-frequency resource to send scheduling DCI, but the terminal device stays on the previous time-frequency resource or the wrong time-frequency resource to receive the data on the network side device, causing the terminal device and the network side The downlink resources of the device do not match. If this happens, the terminal device and the network side device can only switch to the default time-frequency resource until the set timer expires before restarting data scheduling.
  • the set timer is the same as the inactive timer of DRX.
  • the terminal device sends feedback to the WUS sent by the network side device Information, such as Hybrid Automatic Repeat request (HARQ) feedback information, is used to inform the network side device whether the terminal device itself has correctly received the WUS, or inform the network side device whether the terminal device itself has received the wake-up information.
  • HARQ Hybrid Automatic Repeat request
  • the feedback information sent by the terminal equipment is generally on the Physical Uplink Control Channel (PUCCH), which needs to occupy uplink time-frequency resources.
  • PUCCH Physical Uplink Control Channel
  • the network-side equipment indicates time-frequency resource switching information in WUS, it also instructs the terminal equipment to feedback
  • the PUCCH resource of the information is the PUCCH resource used when the terminal device feeds back the information.
  • the following takes the information indicating time-frequency resource switching including the working BWP after the terminal device wakes up as an example for description:
  • the network side equipment and the terminal equipment side in the NR system may be configured with different bandwidths.
  • the terminal equipment can configure its own maximum working bandwidth according to its own business requirements and manufacturing costs. For example, The working bandwidth of low-cost and low-rate terminal equipment may only be 5 MHz (Mega Hertz, MHz), while the working bandwidth of high-rate and high-performance terminal equipment may reach 100MHz.
  • a carrier bandwidth of the cell is set according to low-cost and low-rate terminal equipment (For example, it is set to 5-10MHz), then for high-speed and high-performance terminal equipment, carrier aggregation may be required to obtain a higher rate, which will inevitably increase the control signaling overhead and processing complexity; if the cell The carrier bandwidth is set according to high speed and high performance (for example, set to 100MHz), then low-cost and low-performance terminal equipment may need to be equipped with radio frequency and baseband devices suitable for large bandwidth to be able to access the cell, which will undoubtedly increase the cost. Therefore, the concept of BWP is introduced in NR.
  • a BWP is a continuous frequency resource on a cell carrier.
  • the network-side equipment can configure BWPs with different bandwidths for different terminal devices.
  • the BWP When the BWP is configured and activated, the BWP is called For active BWP, the data and control information sent by the terminal device in the uplink or the data and control information received by the terminal device in the downlink will be completed in the active BWP.
  • a terminal device In the NR Rel-15 version protocol, a terminal device can only have one active BWP in the uplink and downlink respectively. Therefore, in order to enable terminal devices to work on corresponding BWPs to receive and transmit data at different times according to business needs, NR supports the use of scheduling DCI to trigger terminal devices to switch DCI, where different DCIs can be used to indicate different BWPs. Scheduling DCI is called scheduling DCI, and scheduling DCI is also called DCI for scheduling data.
  • It can include the DCI (such as format 1_1) that schedules terminal equipment to receive downlink physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) data, and can also include The terminal device is scheduled to transmit the DCI (such as format 0_1) of the uplink physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) data. After receiving the scheduled DCI, the terminal device receives or sends data on the new BWP indicated by the DCI.
  • DCI such as format 1_1
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • the terminal device receives the WUS sent by the network side device on the BWP2.
  • the WUS indicates that the terminal device wakes up and instructs the terminal device to switch to BWP1 to work, the DRX cycle enters On Duration, and the terminal The device wakes up and switches to BWP1, and the terminal device detects PDCCH and PDSCH on BWP1.
  • the WUS sent by the network side device instructs the terminal device to switch to a new working BWP, it also instructs the terminal device to send the PUCCH resource of the HARQ feedback information.
  • the PUCCH resource information used to instruct the terminal device to send the HARQ feedback information may include the following content: K1 And HARQ resource indicator (HARQ Resource Indicator, ARI), where K1 is used to indicate the time interval between the time slot where the network side device sends WUS and the time slot where the terminal device sends HARQ feedback information.
  • the ARI is specifically used for Indicate which PUCCH resource is used for WUS feedback, which may include the identification information of the PUCCH resource, the occupied frequency domain position (such as the starting physical resource block (Physical Resource Block, PRB)), and one or more of the PUCCH resource format item.
  • the identification information of the PUCCH resource such as the starting physical resource block (Physical Resource Block, PRB)
  • PRB Physical Resource Block
  • indicating K1 requires at least 2 to 3 bits
  • indicating ARI requires at least 2 to 3 bits. Therefore, for each terminal device, at least 4 to 6 bits are required to indicate the PUCCH resource for sending HARQ feedback information. Therefore, in UE-specific PDCCH WUS, at least 4 to 6 bits are required to indicate the PUCCH resource for the terminal device to send HARQ feedback information. For each terminal device in Group-based WUS, at least 4 to 6 bits are required to indicate the terminal device PUCCH resource for sending HARQ feedback information.
  • the PUCCH resource information used to indicate the feedback information of these 5 terminal devices in the Group-based WUS needs to occupy 25 bits, plus the wake-up used to wake up the terminal device Information, it may exceed the number of bits that the Group-based WUS can carry, or if the payload of the Group-based WUS is 40 bits, then the PUCCH resources used to instruct the five terminal devices to send HARQ feedback information occupy the Group -based WUS More than 60% of the bits are occupied, which increases the bit rate of Group-based WUS and reduces the receiving performance of Group-based WUS.
  • the payload is the payload, which is the removal of information from the cell. The pure information part outside the header.
  • the network side device sends WUS, especially when sending Group-based WUS.
  • the number of terminal devices indicated in the Group-based WUS can be reduced, for example, from 5 terminal device multiplexing to 3 terminal device multiplexing, so that when the total number of terminal devices that need to be indicated remains the same, it needs to be sent More Group-based WUS can be used to indicate all terminal equipment, which will also cause excessive signaling overhead for network-side equipment and reduce downlink system capacity.
  • this application proposes a wake-up signal WUS detection method to ensure that the PUCCH resource is not indicated in the WUS issued by the network-side equipment, so as to reduce the signaling of the network-side equipment. Order overhead.
  • the terminal device is pre-configured with PUCCH resources for feedback information, so the terminal device can use the PUCCH resource to feed back whether it has received the terminal device's wake-up information message, so the network side sends the WUS in the terminal device It only needs to include the wake-up information used to instruct the terminal device to wake up.
  • a WUS can carry the wake-up information of as many terminal devices as possible, which can save the signaling overhead caused by indicating the PUCCH resource in the WUS and reduce the network-side equipment Signaling overhead.
  • Step 401 The network side device sends a second message to the first terminal device.
  • the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the terminal device pre-configured with PUCCH resources is called the first terminal device, and the number of the first terminal device may be one or more.
  • the network side device may be each terminal device connected to it as the first terminal device pre-configured with PUCCH resources.
  • the network-side device may first determine the terminal device to be awakened before sending WUS to the terminal device.
  • the terminal device to be awakened is called the second terminal device, and the network-side device may determine that the PUCCH is pre-configured in the second terminal device.
  • the first terminal device of the resource that is, assuming that there are N second terminal devices to be awakened
  • the network-side device instructs the terminal device to switch time-frequency resources, it may cause the subsequent network-side device and the terminal device to fail to switch to the same time-frequency resource, resulting in mismatched uplink and downlink resources.
  • the terminal device whose time-frequency resource is switched is selected as the first terminal device pre-configured with PUCCH resources.
  • the second message only includes the first PUCCH resource used when a specific first terminal device feeds back information.
  • the specific first terminal device is also used to receive the second message.
  • the second message may include the first PUCCH resource used when each first terminal device feeds back information.
  • the second message may specifically include the first PUCCH resource and its corresponding index used when each first terminal device feeds back information.
  • the subsequent terminal device can find the first PUCCH resource corresponding to the terminal device through the index.
  • the second message may also include a PUCCH transmission time offset, and the PUCCH transmission time offset is used to indicate the time for the terminal device to feed back the PUCCH.
  • the PUCCH transmission time offset includes: the time interval between the time when WUS is received and the time when PUCCH feedback information is sent, or the time when the terminal device starts the wake-up mode in the DRX state and the time when PUCCH feedback information is sent. The time interval between.
  • the second message sent by the network side device to the first terminal device may also be specifically used to configure the uplink BWP of the first terminal device and configure the first PUCCH resource for each uplink BWP.
  • the subsequent terminal device can work in the uplink BWP and use the first PUCCH resource to send uplink data (such as uplink control information).
  • the network-side device can send the second message through signaling.
  • the signaling can be Radio Resource Control (RRC) signaling, which can reuse other existing signaling, or it can be a custom new message.
  • RRC Radio Resource Control
  • Ling et al. are not limited here.
  • Step 402 The first terminal device receives the second message sent by the network side device.
  • the first terminal device receives the second message sent by the network side device, and configures the first PUCCH resource used when the terminal device feedbacks information included in the second message to the first terminal device.
  • the first terminal device may switch to the first terminal device after being awakened according to the second message
  • the uplink BWP works, and the first PUCCH resource corresponding to the uplink BWP is used to send uplink data.
  • Step 403 The network side device sends WUS to the second terminal device.
  • the network side device may first determine the terminal device to be awakened before sending the WUS to the terminal device.
  • the terminal device to be awakened is called the second terminal device, and the second terminal device to be awakened may be one or more.
  • the network side device may send WUS to the second terminal device to be awakened. Specifically, the network side generates WUS according to the second terminal device to be awakened, and then delivers the generated WUS to the second terminal device.
  • the network-side device regards each terminal device connected to it as the first terminal device pre-configured with PUCCH resources, not all the first terminal devices configured with PUCCH resources may need to wake up, so the second terminal device to be awakened can understand It is part (or all) of the terminal devices in the first terminal device configured with PUCCH resources.
  • the WUS sent by the network-side device to the second terminal device includes UE-specific PDCCH WUS.
  • the network side device when the network side device generates the UE-specific PDCCH WUS, it may directly include the wake-up information for waking up the second terminal device and other related information of the second terminal device in the UE-specific PDCCH WUS.
  • the network side device determines the location of the dedicated domain of the second terminal device in UE-specific PDCCH WUS, and includes the wake-up information of the second terminal device and/or other related information of the second terminal device in the second terminal device’s In a private domain.
  • the UE-specific PDCCH WUS may include a dedicated domain of the second terminal device. Specifically, all information in the UE-specific PDCCH WUS may be considered as a dedicated domain of the second terminal device.
  • the WUS sent by the network-side device to the second terminal device includes Group-based WUS.
  • the network-side device when the network-side device generates Group-based WUS, it can determine the position of the second terminal device to be instructed to wake up in the dedicated domain of Group-based WUS according to the second terminal device to be instructed to wake up.
  • the position of the dedicated domain of the terminal device in the Group-based WUS can be used to indicate which of the dedicated domains of the terminal device in the Group-based WUS is the dedicated domain of the second terminal device, that is, the dedicated domain of the second terminal device is in the Group-based WUS.
  • the network side device may include the wake-up information of the second terminal device and other related information of the second terminal device in the Group-based WUS.
  • the network side device may also include the wake-up information of the second terminal device and/or other related information of the second terminal device in the dedicated domain of the terminal device.
  • Group-based WUS includes one or more dedicated domains for second terminal devices.
  • the network side device may determine the location of the dedicated domain of the second terminal device in the WUS according to the identification information of the second terminal device.
  • the identification information of the terminal device may include the identifier of the terminal device, may be a unique code (Identity document, ID) of the terminal device, or may be one of the radio network temporary identity (RNTI Radio Network Temporary Identity, RNTI), etc. Item or multiple items.
  • ID a unique code
  • RNTI Radio Network Temporary Identity
  • the network side device may perform a modulo operation on the identifier of the second terminal device, and use the result of the modulo operation as the dedicated domain of the second terminal device in the WUS Information in the location.
  • the network side device determines the position of the dedicated domain of the second terminal device in the WUS.
  • the structure of the generated WUS can be as shown in Figure 2.
  • Figure 2 includes 1 to N second terminal devices. Dedicated field and CRC check bit.
  • the network-side device may include a wake-up indicator field (WIF) in the WUS, and the network-side device determines the second terminal device's identification information according to the identification information of the second terminal device and the WIF.
  • WIF wake-up indicator field
  • the network side device can calculate the identification information of the second terminal device and the WIF, such as performing addition, subtraction, multiplication, and division (the result of the division operation can be forwarded to Round down or round up), modulo operation, etc., determine the position of the dedicated domain of the second terminal device in the WUS according to the calculation result.
  • the network side device generates WUS according to the determined position of the dedicated domain of the second terminal device in WUS, and the structure of generating WUS may be as shown in Figure 5, which includes WIF and 1 ⁇ N second terminal devices.
  • the dedicated field and CRC check bit In the actual WUS structure, the location of the WIF can be located at the head, middle, or tail of the WUS, and there is no limitation.
  • other related information of the second terminal device may also include PUCCH transmission time offset and/or information indicating time-frequency resource switching.
  • the information indicating time-frequency resource switching may include information indicating BWP switching.
  • the information indicating the BWP switching may be information of the working BWP for the terminal device to receive downlink data
  • the information of the working BWP for the terminal device to receive downlink data may be identification information of the BWP.
  • the working BWP for the terminal device to receive downlink data may be the working BWP for the terminal device to receive downlink data during the DRX ON (that is, the wake-up mode in the DXR state).
  • the PUCCH transmission time offset includes: the time interval between the time when WUS is received and the time when PUCCH feedback information is sent, or the time when the terminal device starts the wake-up mode in the DRX state and the time when PUCCH feedback information is sent. The time interval between.
  • the second message and/or the WUS may both include the PUCCH transmission time offset
  • the structure of WUS may be as shown in Figure 2 or Figure 5.
  • the structure of WUS can be as shown in Figure 6, where Figure 6 is an improvement on the basis of Figure 5.
  • Figure 6 includes WIF, 1 ⁇ N second terminal equipment
  • the dedicated field of the second terminal device and the CRC check bit, the second dedicated field of the second terminal device includes the PUCCH transmission time offset T_offset.
  • the second message includes the PUCCH transmission time offset, which can reduce the signaling overhead in WUS. Compared with the PUCCH transmission time offset included in the second message, although the PUCCH transmission time offset included in the WUS occupies a small amount of signaling overhead in the WUS, it can improve the flexibility of uplink transmission of the PUCCH.
  • Step 404 If the third terminal device detects the WUS sent by the network side device, the third terminal device detects the dedicated domain of the terminal device in the WUS, and detects the terminal device in the WUS Wake-up information.
  • the network side device may not be able to send out WUS, or the terminal device may not detect the WUS sent by the network side device, so in this step, the WUS sent by the network side device will be detected.
  • the terminal device is called the third terminal device to distinguish it from the second terminal device actually delivered by the network side device, where the third terminal device is part or all of the second terminal device.
  • the terminal device can also try to detect WUS before it receives WUS.
  • the terminal device monitors the PDCCH channel, and detects whether WUS is received on the PDCCH channel.
  • the third terminal device detects UE-specific PDCCH WUS or Group-based WUS, it can be considered that WUS has been detected.
  • the third terminal device attempts to detect UE-specific PDCCH WUS. Since all the information in UE-specific PDCCH WUS can be considered as the dedicated domain of the terminal device, if UE-specific PDCCH WUS is detected, then The third terminal device can determine that there is WUS; if the UE-specific PDCCH WUS is not detected by the terminal device, the third terminal device tries to detect Group-based WUS. If it detects Group-based WUS, since Group-based WUS usually includes multiple The third terminal device can also detect the dedicated domain of the terminal device in Group-based WUS to confirm whether the dedicated domain of the third terminal device and the wake-up information of the third terminal device exist, so as to confirm whether WUS is detected.
  • the third terminal device detects WUS, it will detect the dedicated domain of the third terminal device in the detected WUS, and detect the wake-up information of the third terminal device in WUS.
  • all control information in the UE-specific PDCCH WUS is considered to be a dedicated domain of the third terminal device, and the third terminal device can directly confirm the presence of the third terminal according to the detected UE-specific PDCCH WUS
  • the dedicated domain of the device; for Group-based WUS, part of the control information in the Group-based WUS is the dedicated domain of the third terminal device.
  • the third terminal device needs to determine the third terminal device's domain based on the detected Group-based WUS The location of the private domain, and then according to the location of the private domain of the third terminal device, it is confirmed whether there is a private domain of the third terminal device.
  • the terminal device determining the location of the dedicated domain of the terminal device in receiving WUS is basically the same as the process of determining the dedicated location of the terminal device when the network side device generates the WUS.
  • the third terminal device determines the identification information of the third terminal device, and according to the identification information, determines that the dedicated domain of the third terminal device is in the WUS. Location, so as to locate the dedicated domain of the third terminal device in WUS.
  • the third terminal device determines the identification information of the third terminal device, and determines the position of the dedicated domain of the third terminal device in the WUS according to the identification information and the WIF . After the third terminal device determines the location information of the private domain of the third terminal device in the WUS, it may detect the private domain of the third terminal device at the location in the WUS. WUS may also include wake-up information, and the third terminal device may also detect whether the third terminal device's wake-up information is included in WUS.
  • the dedicated domain of the third terminal device in the WUS may include the wake-up information of the third terminal device.
  • Step 405 If the third terminal device detects the dedicated domain of the third terminal device in the WUS, and detects that the WUS includes the wake-up information of the third terminal device, the third terminal device uses the pre-configured PUCCH resource The first PUCCH resource is determined in, and the first PUCCH is sent, and the first PUCCH includes a first message for feeding back the wake-up information of the third terminal device.
  • the network side device receives the first PUCCH, and according to the first message included in the first PUCCH, determines that the terminal device receives the wake-up information.
  • the third terminal device stores the first PUCCH resource used when the feedback information is configured in advance.
  • the process of configuring the PUCCH resource for the third terminal device by the network side device refer to step 401 and step 402.
  • the first PUCCH resource used in the pre-configured feedback information stored in the third terminal device may only include the first PUCCH resource used when the third terminal device feeds back information, and may include the first PUCCH resource used when multiple terminal devices feed back information.
  • the third terminal device can directly determine its corresponding first PUCCH resource.
  • the third terminal device may determine the dedicated use of the third terminal device from the pre-configured first PUCCH resource
  • the first PUCCH resource corresponding to the location information of the domain, where for Group-based WUS, the location of the private domain of the third terminal device is the order in which the private domain of the third terminal device appears in the private domain of the Group-based WUS.
  • the third terminal device uses the location information of the dedicated domain of the third terminal device as the first index, and determines the first PUCCH resource corresponding to the first index among the pre-configured first PUCCH resources.
  • the order of the dedicated fields of the terminal device in WUS is consistent with the order of the PUCCH resources configured for the terminal device, so the terminal device can change the dedicated field of the terminal device
  • the location information of is used as the index, and the PUCCH resource corresponding to the index is searched in the configured PUCCH resource. If the location of UE-specific field 1 is 1, and the index is 1, then the PUCCH resource corresponding to the index of 1 in the configured PUCCH resource is PUCCH resource 1, find the PUCCH resource corresponding to the terminal device.
  • the third terminal device determines the first PUCCH resource corresponding to the third terminal device, after the PUCCH transmission time offset, the third terminal device The first PUCCH is sent on the first PUCCH resource corresponding to the device.
  • Figure 8 is a schematic diagram of feeding back the first PUCCH on the basis of Figure 6.
  • the dedicated field of the third terminal device is UE-specific field 2
  • the dedicated field of the third terminal device includes PUCCH Sending time offset T_offset
  • the PUCCH sending time offset includes the time interval between the time of receiving WUS and the time of sending PUCCH feedback information
  • the third terminal device receives the T_offset time of the WUS after receiving the T_offset time of the WUS
  • the first PUCCH is sent on the first PUCCH resource corresponding to the device, that is, on the PUCCH resource 2 in the UL BWP of the uplink bandwidth part as shown in FIG. 8.
  • the third terminal device may try to detect and schedule PDCCH in DRX ON.
  • the third terminal device detects information indicating time-frequency resource switching in the dedicated domain of the third terminal device, the third terminal device can also switch to work on the time-frequency resource indicated in WUS, for example, the one that indicates time-frequency resource switching
  • the information includes information indicating BWP switching, and the third terminal device switches to work on the indicated BWP to perform data transmission and reception.
  • the first PUCCH includes a first message for feeding back the wake-up information of the third terminal device. If the network-side device receives the first PUCCH, the network-side device determines the first PUCCH according to the first message included in the first PUCCH. 3. The terminal device receives the wake-up information. Optionally, if information indicating time-frequency resource switching is indicated in the WUS, after receiving the first PUCCH, the network side device may also determine that the third terminal device has switched to the indicated according to the first message included in the first PUCCH Work on time-frequency resources.
  • the terminal device determines whether the terminal device has not receive the WUS, or the terminal device does not detect the dedicated domain of the terminal device in the received WUS, or the terminal device does not detect the wake-up information of the terminal device in the received WUS. If the wake-up information of the terminal device is not received, it can also be considered that the terminal device has not received WUS, or the terminal device has not received the scheduled DCI correctly.
  • the terminal device that has not received the wake-up information can be referred to as the fourth terminal device.
  • the fourth terminal device may be pre-configured with the second PUCCH resource. If the fourth terminal device determines that the wake-up information is not received, the fourth terminal device uses the second PUCCH resource to send the second PUCCH, and the second PUCCH includes information for feedback The third message of wake-up information is not received.
  • the fourth terminal device does not detect UE-specific PDCCH WUS, after attempting to detect Group-based WUS, Group-based WUS is not detected, and it is determined that WUS is not received, the third message can also be used The feedback did not receive Group-based WUS.
  • the network-side device determines that the terminal device has not received the wake-up information according to the third message included in the second PUCCH, or that the terminal device has not received the Group-based WUS, and then determines the terminal device No wake-up message was received.
  • the terminal device is pre-configured with PUCCH resources for feedback information.
  • the terminal device can use the pre-configured PUCCH resource corresponding to the first terminal device PUCCH resources, feed back the first message of the wake-up information received from the terminal device, reduce the number of bits of feedback indication information carried in WUS, reduce the PDCCH code rate, reduce the signaling overhead of the network side device, and increase the downlink channel capacity.
  • Embodiment 1 Take the WUS detection process shown in Figure 9 as an example for description, including the following steps:
  • Step 901 The network side sends a second message to the terminal device, where the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the second message also includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time interval between the time of receiving WUS and the time of sending PUCCH feedback information, or the terminal device The time interval between the time when the wake-up mode of the DRX state starts and the time when PUCCH feedback information is sent.
  • Step 902 The terminal device receives the second message sent by the network side device.
  • Step 903 The network side device sends WUS to the terminal device.
  • the PUCCH transmission time offset is also included in the WUS.
  • Step 904 The terminal device receives the WUS, and detects the dedicated domain of the terminal device in the WUS.
  • the terminal device detects the wake-up information of the terminal device in the WUS.
  • Step 905 If the terminal device detects the dedicated domain of the terminal device and the wake-up information of the terminal device in WUS, the terminal device uses the location information of the dedicated domain of the terminal device as the first index, and determines the corresponding to the first index
  • the first PUCCH resource sends the first PUCCH, and the first PUCCH includes a first message for feeding back the wake-up information of the terminal device received.
  • the terminal device determines the identification information of the terminal device, and determines the location of the dedicated domain of the terminal device in the WUS according to the identification information and the WIF.
  • the terminal device determines the identification information of the terminal device, and determines the location of the dedicated domain of the terminal device in WUS according to the identification information.
  • Step 906 The network side device receives the first PUCCH, and according to the first message included in the first PUCCH, determines that the terminal device receives the wake-up information.
  • Embodiment 2 Take the WUS detection process shown in Figure 10 as an example for description, including the following steps:
  • Step 1001 The network side sends a second message to the terminal device, where the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the second message also includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time interval between the time of receiving WUS and the time of sending PUCCH feedback information, or the terminal device The time interval between the time when the wake-up mode of the DRX state starts and the time when PUCCH feedback information is sent.
  • Step 1002 The terminal device receives the second message sent by the network side device.
  • Step 1003 The network side device sends WUS to the terminal device.
  • the PUCCH transmission time offset is also included in the WUS.
  • WUS is UE-specific PDCCH WUS, or WUS is Group-based WUS.
  • Step 1004 The terminal device receives the WUS, and detects the dedicated domain of the terminal device in the WUS.
  • the terminal device detects the wake-up information of the terminal device in the WUS.
  • the terminal device detects UE-specific PDCCH WUS, and if it detects UE-specific PDCCH WUS, it is determined to receive WUS.
  • the terminal device if the terminal device does not detect UE-specific PDCCH WUS, the terminal device tries to detect Group-based WUS, and if it detects Group-based WUS, it determines to receive WUS. If the Group-based WUS is not detected, the terminal device uses the pre-configured second PUCCH resource to send the second PUCCH, and the second PUCCH includes a third message for feeding back that the Group-based WUS is not received.
  • Step 1005 If the terminal device detects the dedicated domain of the terminal device and the wake-up information of the terminal device in the WUS, the terminal device uses the pre-configured first PUCCH resource to send the first PUCCH, and the first PUCCH includes information for receiving feedback The first message of wake-up information to the terminal device.
  • the terminal device determines the identification information of the terminal device, determines the location of the dedicated domain of the terminal device in WUS according to the identification information and the WIF, and determines the location of the dedicated domain of the terminal device The first PUCCH resource corresponding to the information.
  • the terminal device determines the identification information of the terminal device, determines the location of the dedicated domain of the terminal device in WUS according to the identification information, and determines the location information of the dedicated domain of the terminal device The corresponding first PUCCH resource.
  • Step 1006 The network side device receives the first PUCCH, and according to the first message included in the first PUCCH, determines that the terminal device has received the wake-up information.
  • the network side device receives the second PUCCH sent using the second PUCCH resource, it is determined that the terminal device has not received the wake-up message according to the third message in the second PUCCH.
  • the WUS detection method of the embodiment of the present application is described in detail above with reference to FIGS. 4 to 10. Based on the same inventive concept as the above-mentioned WUS detection method, the embodiment of the present application also provides a WUS detection device, as shown in FIG. 11,
  • the WUS detection device 1100 includes a processing unit 1101 and a transceiver unit 1102, and the device 1100 can be used to implement the method described in the foregoing method embodiment applied to a terminal device or a network side device.
  • the apparatus 1100 is applied to a terminal device.
  • the processing unit 1101 is configured to detect the dedicated domain of the terminal device in the detected WUS; if the dedicated domain of the terminal device is detected in the WUS, and it is detected that the WUS includes The wake-up information of the terminal device uses the location information of the dedicated domain of the terminal device as the first index to determine the first PUCCH resource corresponding to the first index.
  • the transceiver unit 1102 is configured to use the first PUCCH resource to send a first PUCCH, where the first PUCCH includes a first message for feeding back the wake-up information of the terminal device.
  • the transceiver unit 1102 is further configured to receive a second message sent by the network side device, where the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the processing unit 1101 is specifically configured to determine the identification information of the terminal device if the WUS includes WIF; and determine the dedicated domain of the terminal device according to the identification information and the WIF Position in the WUS.
  • the processing unit 1101 is specifically configured to determine the identification information of the terminal device if the WUS does not include WIF; according to the identification information, determine that the dedicated domain of the terminal device is in the Location in WUS.
  • the WUS or the second message further includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between the time when the WUS is received and the time when the PUCCH feedback information is sent Interval, or the time interval between the time when the terminal device starts the wake-up mode in the discontinuous reception DRX state and the time when the PUCCH feedback information is sent.
  • the device is applied to terminal equipment.
  • the processing unit 1101 is configured to detect the dedicated domain of the terminal device in the WUS if WUS is detected; if the dedicated domain of the terminal device is detected in the WUS, and detect all The WUS includes the wake-up information of the terminal device, and determines the pre-configured first PUCCH resource.
  • the transceiver unit 1102 is configured to use the first PUCCH resource to send a first PUCCH, where the first PUCCH includes a first message for feeding back the wake-up information of the terminal device.
  • the WUS is UE-specific PDCCH WUS.
  • the processing unit 1101 is further configured to use that the WUS is a Group-based WUS. If the terminal device does not detect the UE-specific PDCCH WUS, the terminal device tries to detect the Group-based WUS.
  • the transceiving unit 1102 is further configured to use a pre-configured second PUCCH resource to send a second PUCCH if the terminal device does not detect Group-based WUS, and the second PUCCH includes It is reported that the third message of the Group-based WUS is not received.
  • the transceiver unit 1102 is further configured to receive a second message sent by the network side device, where the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the processing unit 1101 is specifically configured to determine the identification information of the terminal device if the WUS includes WIF; and determine the dedicated domain of the terminal device according to the identification information and the WIF The location in the WUS; determining the first PUCCH resource corresponding to the location information of the dedicated domain of the terminal device.
  • the processing unit 1101 is specifically configured to determine the identification information of the terminal device if the WUS does not include WIF; according to the identification information, determine that the dedicated domain of the terminal device is in the Location in WUS; determining the first PUCCH resource corresponding to the location information of the dedicated domain of the terminal device.
  • the WUS or the second message further includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between the time of receiving WUS and the time of sending PUCCH feedback information Interval, or the time interval between the time when the terminal device starts the wake-up mode in the discontinuous reception DRX state and the time when the PUCCH feedback information is sent.
  • the device is applied to a network side device.
  • the transceiving unit 1102 is configured to send WUS to a terminal device, where the WUS includes a dedicated domain of the terminal device; receive the first PUCCH sent by the terminal device using a pre-configured first PUCCH resource;
  • the processing unit 1101 is configured to determine that the terminal device receives the wake-up information according to the first message included in the first PUCCH for feeding back the wake-up information of the terminal device.
  • the transceiver unit 1102 is further configured to send a second message to the terminal device, and the second message is used to configure the first PUCCH resource used when the terminal device feeds back information.
  • the WUS or the second message further includes a PUCCH transmission time offset
  • the PUCCH transmission time offset includes: the time between the time of receiving WUS and the time of sending PUCCH feedback information Interval, or the time interval between the time when the terminal device starts the wake-up mode in the discontinuous reception DRX state and the time when the PUCCH feedback information is sent.
  • the transceiving unit 1102 is further configured to receive the second PUCCH sent by the terminal device using the second PUCCH resource.
  • the processing unit 1101 is further configured to determine that the terminal device does not receive wake-up information according to the third message included in the second PUCCH for feeding back that the Group-based WUS is not received.
  • each functional unit in each embodiment of this application It can be integrated into one processing unit, or it can exist alone physically, or two or more units can be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • an embodiment of the present application also provides a schematic structural diagram of a WUS detection device 1200.
  • the apparatus 1200 may be used to implement the method described in the foregoing method embodiment applied to a terminal device or a network side device, and reference may be made to the description in the foregoing method embodiment.
  • the device 1200 includes one or more processors 1201.
  • the processor 1201 may be a general-purpose processor or a special-purpose processor. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, terminals, or chips, etc.), execute software programs, and process software program data.
  • the communication device may include a transceiving unit to implement signal input (reception) and output (transmission).
  • the transceiver unit may be a transceiver, a radio frequency chip, or the like.
  • the apparatus 1200 includes one or more processors 1201, and the one or more processors 1201 can implement the method of the terminal device or the network side device in the above-mentioned embodiment.
  • the processor 1201 may implement other functions in addition to implementing the methods in the above-mentioned embodiments.
  • the processor 1201 can execute instructions to make the device 1200 execute the method described in the foregoing method embodiment.
  • the instructions may be stored in the processor in whole or in part, such as the instruction 1203, or in the memory 1202 coupled to the processor, in whole or in part, such as the instruction 1204, or the instructions 1203 and 1204 can be used together to make
  • the apparatus 1200 executes the method described in the foregoing method embodiment.
  • the communication device 1200 may also include a circuit, and the circuit may implement the function of the terminal device or the network side device in the foregoing method embodiment.
  • the device 1200 may include one or more memories 1202, on which instructions 1204 are stored, and the instructions may be executed on the processor, so that the device 1200 executes the above method The method described in the examples.
  • data may also be stored in the memory.
  • the optional processor may also store instructions and/or data.
  • the one or more memories 1202 may store the corresponding relationship described in the foregoing embodiment, or related parameters or tables involved in the foregoing embodiment.
  • the processor and memory can be provided separately or integrated together.
  • the device 1200 may further include a transceiver 1205 and an antenna 1206.
  • the processor 1201 may be called a processing unit, and controls a device (terminal or base station).
  • the transceiver 1205 may be called a transceiver, a transceiver circuit, or a transceiver unit, etc., and is used to implement the transceiver function of the device through the antenna 1206.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the embodiment of the present application also provides a computer-readable medium on which a computer program is stored.
  • the computer program is executed by a computer, the WUS detection method described in any method embodiment applied to a terminal device or a network side device is implemented .
  • the embodiments of the present application also provide a computer program product that, when executed by a computer, implements the WUS detection method described in any method embodiment applied to a terminal device or a network side device.
  • An embodiment of the present application also provides a communication system, which includes a terminal device for implementing any of the foregoing method embodiments and a network side device for implementing any of the foregoing method embodiments.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) etc.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the WUS detection method described in any method embodiment applied to a terminal device or a network side device.
  • the foregoing processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, At this time, the processor may be a general-purpose processor, which is implemented by reading the software code stored in the memory, and the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a computer.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or data structures
  • Any connection can suitably become a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , Fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the media.
  • Disk and disc include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy discs and Blu-ray discs. Disks usually copy data magnetically, while discs The laser is used to optically copy data. The above combination should also be included in the protection scope of the computer-readable medium.

Landscapes

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

Abstract

本申请实施例涉及一种唤醒信号WUS检测方法及装置,用以减少网络侧设备的信令开销,该WUS检测方法为:终端设备在检测到的WUS中检测所述终端设备的专用域;如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,所述终端设备以所述终端设备的专用域的位置信息作为第一索引,确定与所述第一索引对应的第一物理上行控制信道PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息。

Description

一种唤醒信号WUS检测方法及装置
相关申请的交叉引用
本申请要求在2019年07月19日提交中国专利局、申请号为201910656648.7、申请名称为“一种唤醒信号WUS检测方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域,尤其涉及一种唤醒信号WUS检测方法及装置。
背景技术
网络侧设备可以通过Group-based WUS(基于组的唤醒信号)来向多个用户设备(User Equipment,UE)发送物理下行控制信道(Physical Downlink Control Channel,PDCCH)唤醒信号(Wake-up signal,WUS),Group-based WUS中携带有用于唤醒UE的唤醒信息,还携带有用于指示每个UE反馈信息的物理上行控制信道(Physical Uplink Control Channel,PUCCH)资源的信息。UE可以通过该用于指示UE反馈信息的PUCCH资源,向网络侧设备反馈是否接收到唤醒信息的消息。
通常用于指示每个UE反馈信息的PUCCH资源的信息指示需要占用4~6比特。假设一个Group-based WUS共指示5个UE,Group-based WUS中用于指示这5个UE反馈信息的PUCCH资源的信息就需要占用25个比特,再加上用于唤醒UE的唤醒信息,就有可能超出Group-based WUS所能承载的比特数,或者是影响WUS的接收性能。
因此通常的做法就是减少每个Group-based WUS中指示的UE的数量,对应的减少Group-based WUS中携带的用于指示UE反馈信息的PUCCH资源的信息,但是这样在需要指示的UE的总量不变的情况下,就需要发送更多的Group-based WUS才能实现指示全部的UE,造成了网络侧设备信令开销过大。
发明内容
本申请实施例提供了WUS检测方法及装置,网络侧设备下发的WUS中不指示PUCCH资源,从而减少网络侧设备的信令开销。
第一方面,提供了一种WUS检测方法,网络侧设备向终端设备发送WUS,WUS中包括终端设备的专用域。终端设备在检测到的WUS中检测终端设备的专用域;如果在WUS中检测到终端设备的专用域,且在WUS中检测到了终端设备的唤醒信息,终端设备在预先配置的PUCCH资源中确定所述终端设备对应的第一PUCCH资源,发送第一PUCCH,该第一PUCCH中包括用于反馈接收到该终端设备的唤醒信息的第一消息。网络侧设备接收第一PUCCH,根据第一PUCCH中包括的用于反馈接收到该终端设备的唤醒信息的第一消息,确定终端设备接收到唤醒信息。该WUS可以为UE-specific PDCCH WUS,可以为Group-based WUS。该WUS中可以包括PUCCH的发送时间偏移,还可以包括指示时频资源切换的信息,该指示时频资源切换的信息可以包括指示BWP切换的信息。
上述方案中,终端设备中预先配置有反馈信息的PUCCH资源,网络侧设备在向终端设备发送WUS中,不指示终端设备反馈信息的PUCCH资源,可以减少PUCCH资源在WUS中所占用的比特数,因此,一个WUS中可以携带更多终端设备的唤醒信息,指示更多终端设备唤醒,在指示的终端设备的数量不变时,能够节省网络侧设备WUS的信令开销。
在一种可能的实现中,网络侧设备可以在向终端设备发送WUS之前,向终端设备发送第二消息,终端设备接收该第二消息,该第二消息用于预先配置PUCCH资源。该第二消息中预先配置的PUCCH资源可以为仅包括该终端设备反馈信息时使用的第一PUCCH资源,可以为包括多个终端设备反馈信息时使用的第一PUCCH资源,其中该多个终端设备中包括该终端设备。该第二消息可以为RRC信令,或者复用现有其他信令,或者预定义的新增命令等。
在该实现中,网络侧设备预先为终端设备配置PUCCH资源,在终端设备配置PUCCH资源后,网络侧设备向终端设备发送WUS,发送的WUS中不指示终端设备反馈信息的PUCCH资源,因此可以减少PUCCH资源在WUS中的信令开销。
在一种可能的实现中,网络侧设备向终端设备发送的第二消息具体用于配置终端设备的上行BWP,以及为每个上行BWP配置第一PUCCH资源。
在该实现中,网络侧设备还可以预先为终端设备配置上行BWP和上行BWP上的PUCCH资源,终端设备可以切换到上行BWP上进行上行控制信息的发送。
在一种可能的实现中,如果WUS中包括WIF,终端设备确定终端设备的标识信息,根据该标识信息和WIF,确定终端设备的专用域在WUS中的位置;终端设备确定该终端设备的专用域的位置信息对应的第一PUCCH资源。终端设备的标识信息可以包括终端设备的标识符、终端设备ID、终端设备的RNTI等中的一项或多项。
示例性的,终端设备可以对第二终端设备的标识信息与WIF进行计算,如进行加法、减法、乘法、除法(除法运算的结果可以进行向下取整或向上取整)、取模运算等,根据计算结果确定第二终端设备的专用域在WUS中的位置的信息。终端设备可以将终端设备的专用域的位置信息作为第一索引,在预先配置的PUCCH资源中确定该第一索引对应的第一PUCCH资源,其中所述第二终端设备可以表示待唤醒的终端设备。
在该实现中,网络侧设备和终端设备可以根据终端设备的标识信息和WIF,确定终端设备的专用域在WUS中的位置,并且WUS中指示的终端设备可以非固定的几个终端设备,而是可以根据WIF灵活地在不同的终端设备的专用域指示终端设备唤醒。
在一种可能的实现中,如果WUS中不包括WIF,终端设备确定终端设备的标识信息,根据该标识信息,确定终端设备的专用域在WUS中的位置;终端设备确定该终端设备的专用域的位置信息对应的第一PUCCH资源。
终端设备可以将终端设备的专用域的位置信息作为第一索引,在预先配置的PUCCH资源中确定该第一索引对应的第一PUCCH资源。
在该实现中,网络侧设备和终端设备,可以根据终端设备的标识信息,确定终端设备的专用域在WUS中的位置,从而确定终端设备的专用域的位置信息对应的第一PUCCH资源。
在一种可能的实现中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间 的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
第二方面,提供了一种WUS检测方法,网络侧设备向终端设备发送WUS,该WUS中包括终端设备的专用域;
终端设备在检测到的WUS中检测该终端设备的专用域;
如果在WUS中检测到了终端设备的专用域,且检测WUS中包括终端设备的唤醒信息,该终端设备以终端设备的专用域的位置信息作为第一索引,确定与该第一索引对应的第一PUCCH资源,发送第一PUCCH,该第一PUCCH中包括用于反馈接收到终端设备的唤醒信息的第一消息;网络侧设备接收终端设备采用预先配置的第一PUCCH资源发送的第一PUCCH;根据该第一PUCCH中包括的用于反馈接收到的终端设备的唤醒信息的第一消息,确定该终端设备接收到唤醒信息。
在一种可能的实现中,网络侧设备向终端设备发送WUS之前,向终端设备发送第二消息,终端设备接收网络侧设备发送的该第二消息,该第二消息用于配置终端设备反馈信息时使用的第一PUCCH资源。
在一种可能的实现中,如果WUS中包括WIF,终端设备确定该终端设备的标识信息;根据该标识信息和WIF,确定终端设备的专用域在该WUS中的位置。
在一种可能的实现中,如果WUS中不包括WIF,终端设备根据该终端设备的标识信息;根据该标识信息,确定终端设备的专用域在WUS中的位置。
在一种可能的实现中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
第三方面,提供了一种WUS检测方法,网络侧设备向终端设备发送WUS,该WUS中包括终端设备的专用域;终端设备在检测到的WUS中检测该终端设备的专用域;如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,所述终端设备采用预先配置的第一物理上行控制信道PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息;网络侧设备接收终端设备采用预先配置的第一PUCCH资源发送的第一PUCCH;根据该第一PUCCH中包括的用于反馈接收到的终端设备的唤醒信息的第一消息,确定该终端设备接收到唤醒信息。
在一种可能的实现中,该WUS为UE-specific PDCCH WUS。
在一种可能的实现中,如果终端设备未检测到UE-specific PDCCH WUS,终端设备尝试检测所述Group-based WUS。
在一种可能的实现中,如果所述终端设备未检测到Group-based WUS,终端设备采用预先配置的第二PUCCH资源发送第二PUCCH,所述第二PUCCH中包括用于反馈未接收到所述Group-based WUS的第三消息。
示例性的,网络侧设备接收终端设备采用第二PUCCH资源发送的第二PUCCH资源;根据该第二PUCCH中包括的用于反馈未接收到Group-based WUS的第三消息,确定终端设备未接收到唤醒信息。网络侧设备可以为终端设备预先配置第二PUCCH,该第二PUCCH信息用于反馈终端设备未接收到唤醒信息的消息。
在一种可能的实现中,网络侧设备向终端设备发送WUS之前,向终端设备发送第二消息,终端设备接收网络侧设备发送的该第二消息,该第二消息用于配置终端设备反馈信息时使用的第一PUCCH资源。
在一种可能的实现中,如果WUS中包括WIF,终端设备确定该终端设备的标识信息;根据该标识信息和WIF,确定终端设备的专用域在该WUS中的位置。
在一种可能的实现中,如果WUS中不包括WIF,终端设备根据该终端设备的标识信息;根据该标识信息,确定终端设备的专用域在WUS中的位置。
在一种可能的实现中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
第四方面,提供了一种WUS检测方法,终端设备尝试检测UE-specific PDCCH WUS;如果检测到UE-specific PDCCH WUS,确定接收WUS;如果未检测到UE-specific PDCCH WUS,终端设备尝试检测Group-based WUS;如果未检测到Group-based WUS,终端设备确定下行信道质量较差,可以进行链路回复,终端设备可以采用第二PUCCH资源,发送第二PUCCH。
如果检测到Group-based WUS,终端设备在Group-based WUS检测终端设备的专用域,以及终端设备的唤醒信息,如果未检测到终端设备的专用域或终端设备的唤醒信息,确定网络侧设备并未对终端设备进行唤醒。如果检测到Group-based WUS,且在Group-based WUS中检测到了终端设备的专用域以及终端设备的唤醒信息,确定网络侧对终端设备进行唤醒。
在一种可能的实现中,如果检测到Group-based WUS,终端设备在Group-based WUS检测终端设备的专用域,如果检测到终端设备的专用域,在该终端设备的专用域中检测终端设备的唤醒信息。
第五方面,提供了一种WUS检测装置。本申请提供的装置具有实现上述方法方面终端设备或网络侧设备的功能,其包括用于执行上述方法方面所描述的步骤或功能相对应的部件(means)。所述步骤或功能可以通过软件实现,或硬件(如电路)实现,或者通过硬件和软件结合来实现。
在一种可能的设计中,上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中终端设备或网络侧设备相应的功能。可选的,所述装置还可以包括一个或多个存储器,所述存储器用于与处理器耦合,其保存装置必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起,也可以与处理器分离设置。本申请并不限定。
另一个可能的设计中,上述装置,可以包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号,该存储器用于存储计算机程序,该处理器用于运行该存储器中的计算机程序,使得该装置执行第一方面或第一方面中任一种可能实现方式中终端设备或网络侧设备完成的方法。
在一种可能的设计中,上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中终端设备或网络侧设备相应的功能。可选的,所述装置还可以包括一个或多个存储器,所述存储器用于与处理器耦合,其保存终端设备 或网络侧设备必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起,也可以与处理器分离设置。本申请并不限定。
所述装置可以位于终端设备或网络侧设备中,或为终端设备或网络侧设备。
另一个可能的设计中,上述装置,包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号,该存储器用于存储计算机程序,该处理器用于运行存储器中的计算机程序,使得该装置执行上述第一方面、第二方面、第三方面、第四方面,或第一方面、第二方面、第三方面、第四方面中任一种可能实现方式中终端设备或网络侧设备完成的方法。
第六方面,提供了一种计算机可读存储介质,用于存储计算机程序,该计算机程序包括用于执行上述第一方面、第二方面、第三方面、第四方面,或第一方面、第二方面、第三方面、第四方面中任一种可能实现方式中的方法的指令。
第七方面,提供了一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码在计算机上运行时,使得计算机执行上述第一方面、第二方面、第三方面、第四方面,或第一方面、第二方面、第三方面、第四方面中任一种可能实现方式中的方法。
第八方面,提供了一种通信系统,所述通信系统包括网络侧设备和终端设备,所述网络侧设备和所述终端设备用于实现上述第一方面、第二方面、第三方面、第四方面,或第一方面、第二方面、第三方面、第四方面中任一种可能实现方式中的方法。
附图说明
图1为一种DRX cycle的示意图;
图2为一种Group-based WUS的信号格式的示意图;
图3为一种终端设备切换BWP的示意图;
图4为本申请实施例中适用的一种WUS检测流程示意图;
图5为本申请实施例中适用的一种WUS的结构示意图;
图6为本申请实施例中适用的一种WUS的结构示意图;
图7为本申请实施例中适用的一种PUCCH资源的查找示意图;
图8为本申请实施例中适用的一种反馈PUCCH的示意图;
图9为本申请实施例中适用的一种WUS检测流程示意图;
图10为本申请实施例中适用的一种WUS检测流程示意图;
图11为本申请实施例中适用的一种WUS检测装置结构图;
图12为本申请实施例中适用的一种WUS检测装置结构图。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是,各个系统可以包括另外的设备、组件、模块等,并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外,还可以使用这些方案的组合。
另外,在本申请实施例中,“示例的”一词用于表示作例子、例证或说明。本申请中被 描述为“示例”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言,使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
以下对本申请实施例的部分用语进行解释说明,以便于本领域技术人员理解。
1)终端设备,可以是指向用户提供语音和/或数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网进行通信,无线终端可以是移动终端,如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机,例如,可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与无线接入网交换语言和/或数据。例如,个人通信业务(Personal Communication Service,PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(Wireless Local Loop,WLL)站、个人数字助理(Personal Digital Assistant,PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)、移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device)、或用户设备(User Equipment)。其他终端设备的举例为:手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、智能销售终端(point of sale,POS)、可穿戴设备、虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备等。
2)网络侧设备,位于通信系统,能够为终端设备提供连接服务,可以将终端设备接入到互联网中。例如,所述网络设备可以是通信系统中的基站设备或者接入点。基站设备如gNode B(gNB)、网关(gateway)设备、地面站设备等。所述网络设备又或者可以是卫星通信系统中的非陆地网络网关/卫星网关(Non-terrestrial networks Gateway,NTN-Gateway)等。
3)唤醒信号(Wake-up signal,WUS),用于降低终端设备功耗的一种控制信号,WUS中可以包括终端设备的专用域。例如,在空闲态中,终端设备一般处于休眠状态,终端设备尝试接收WUS,如果接收到WUS,终端设备会继续尝试接收用于唤醒的寻呼消息(Paging),如果终端设备未接收到WUS,终端设备将不尝试接收Paging并继续休眠,从而节省终端设备的功耗。示例的,WUS可以包括用户设备专用PDCCH唤醒信号(UE-specific PDCCH WUS),和/或Group-based WUS。
4)终端设备的专用域(UE specific field(s)),也称为终端设备的专用比特域,终端设备的专用域包括在WUS中。终端设备的专用域指承载为特定终端设备分配的信息的比特域。一般地,终端设备的专用域用于承载终端设备的相关信息,用于指示唤醒终端设备的唤醒信息以及终端设备的其他相关信息,例如终端设备的其他相关信息中包括指示时频资源切换的信息、PUCCH的发送时间偏置/发送时间偏移、激活或者去激活跨时隙调度的指示信息、指示多输入多输出(Multiple-Input Multiple-Output,MIMO)的最大层数的信息等,其中指示时频资源切换的信息可以包括指示BWP切换的信息。网络侧设备和终端 设备可以通过终端设备的专用域的位置在WUS中确定终端设备的专用域,终端设备的专用域的位置可以用来指示终端设备的专用域在WUS中出现的顺序,或者指示终端设备的专用域为WUS中的第几个专用域。
5)终端设备的唤醒信息,用于指示终端设备唤醒。终端设备的唤醒信息可以包括在WUS中,由WUS指示终端设备的唤醒。可选的,WUS可以显式指示终端设备唤醒,或者WUS可以隐式指示终端设备唤醒。例如,在显式指示时,WUS中终端设备的专用域中指示终端设备的唤醒信息,由终端设备的专用域的特定的比特来指示终端设备的唤醒;在隐式指示时,WUS指示终端设备的唤醒信息,由该WUS来指示终端设备的唤醒。示例的,当WUS为UE-specific PDCCH WUS时,UE-specific PDCCH WUS隐式指示终端设备的唤醒信息,终端设备一旦检测到了UE-specific PDCCH WUS,就可以确定检测到了终端设备的唤醒信息,当WUS为Group-based WUS,Group-based WUS显示指示终端设备的唤醒信息,终端设备检测到Group-based WUS后,还可以通过在Group-based WUS中终端设备的专用域中检测该终端设备的唤醒信息。
6)PUCCH资源,终端设备发送上行控制信息时使用的上行资源。终端设备可以通过PUCCH资源向网络侧设备反馈信息,如混合自动重传请求(Hybrid Automatic Repeat request,HARQ)反馈信息。
本申请中的“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请中所涉及的多个,是指两个或两个以上。
另外,需要理解的是,在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
本申请实施例的技术方案可以应用于各种通信系统,例如:第四代(4th Generation,4G),4G系统包括系统长期演进(long term evolution,LTE)系统,全球互联微波接入(worldwide interoperability for microwave access,WiMAX)通信系统,未来的第五代(5th Generation,5G)系统,如新一代无线接入技术(new radio access technology,NR),及未来的通信系统,如6G系统等。
为了便于理解本申请实施例,下面对本申请的应用场景进行说明。
3GPP标准组织目前正在制定第5代蜂窝移动通信系统(5th Generation,5G)的协议标准,5G也被称为新空口(New Radio,NR)。与长期演进(Long Term Evolution,LTE)系统相比,NR支持更大的传输带宽,更多的收发天线阵列,更高的传输速率以及更灵活、粒度更小的调度机制。虽然基于上述特性NR提供更多的适用范围,但是却极大的增加了终端设备的功耗负担。为了降低终端设备的功耗,3GPP在NR rel-16版本中引入了Power saving(功耗节省)研究课题,其目的是研究使终端设备可在各种状态下(包括Connection连接态,空闲态,以及非激活态)下可能的降功耗方案,其中,在Connection连接态如何节省终端设备功耗是一个研究重点。
在LTE系统中,3GPP设计了不连续接收(Discontinuous Reception,DRX)机制来降低终端设备在连接态的功耗。在DRX机制中,终端设备在连接态的激活状态下,会启动一个inactive timer(非激活定时器),终端设备不断尝试接收物理下行控制信道(Physical Downlink Control Channel,PDCCH)。如果终端设备接收到PDCCH上的调度下行控制信 息(Downlink Control Information,DCI)时,终端设备会重启inactive timer,如果终端设备一段时间内都未接收到调度DCI,使得inactive timer超时,则终端设备会进入DRX非激活状态。
如图1所示,DRX状态下的基本时间单位为一个DRX cycle(DRX循环),DRX cycle的时间长短为DRX周期,一个DRX cycle由一个Sleep(休眠)状态(即非激活状态)和On Duration(持续时间)状态组成。On Duration即唤醒模式也称为DRX_ON,当DRX cycle进入到On Duration时,终端设备将被唤醒并监听PDCCH,一旦在PDCCH中接收到了调度DCI,终端设备将重新启动inactive timer计时。如果最终inactive timer超时,终端设备将重新回到Sleep模式。Sleep状态即休眠模式也称为DRX_OFF,处于Sleep模式下的终端设备可以完全关闭射频收发器和基带处理器等通信器件以降低功耗。
需要注意的是,一般情况下终端设备并不是在On Duration到来时才唤醒,而是会在On Duration到来前的几个时隙内先唤醒,并接收下行参考信号进行时频偏同步,防止终端设备因为长时间休眠造成系统的时钟和工作频率与基站的时钟和工作频率出现偏差;同时终端设备也可以先尝试接收下行同步信号和更新系统消息,以防止终端设备从一个小区移动到另一个小区后系统消息出现偏差。
并且在LTE系统中,3GPP还设计了WUS,WUS是在窄带物联网(Narrow band Internet of Things,NB-IoT)中引入的用以降低终端设备功耗的一种控制信号,主要应用在空闲状态的寻呼机制中。在空闲态中,终端设备一般情况下处于休眠状态,但终端设备需要每过一段时间唤醒来尝试接收Paging(寻呼)。其中终端设备被唤醒接收寻呼的时间被称为寻呼机会(Paging Occasion,PO)。在实际系统中,基站并不是在每个PO都会给终端设备发送Paging,因此终端设备在大部分时间中在PO唤醒接收Paging都属于无效操作,并且会增加终端设备的功耗。为此,NB-IoT系统中引入了WUS,如果在某一个PO中基站确实向终端设备发送了Paging,基站会在PO到来之前发送WUS,反之基站不会发送WUS。对应的,终端设备会在PO到来之前的时间尝试接收WUS,如果终端设备接收到了WUS,终端设备确认接下来的PO中存在Paging消息,终端设备会继续尝试接收Paging,反之,如果终端设备没有接收到WUS,终端设备将认为接下来的PO中不存在Paging消息,终端设备将不尝试接收Paging并继续休眠。由于终端设备接收WUS时的功耗和复杂度远小于终端设备尝试接收Paging时的功耗和复杂度,而且基站在终端设备空闲态发送Paging的概率并不高,因此通过是否接收到WUS来确定终端设备是否唤醒可以极大的节省终端设备的功耗。
NR Rel-16考虑引入PDCCH-based WUS,也称为PDCCH WUS,也就是说WUS是通过PDCCH来承载。一种可能的实施例中,WUS可以通过PDCCH DCI来承载,即WUS通过PDCCH中的调度DCI来承载。PDCCH至少包括UE-specific PDCCH WUS(用户设备专用PDCCH唤醒信号)和Group-based(PDCCH)WUS(基于组的唤醒信号),UE-specific PDCCH WUS是发给单个终端设备的信号,即PDCCH DCI只承载一个终端设备的WUS信号,Group-based WUS的信号格式可以参见图2所示,Group-based WUS中承载了N个终端设备的WUS信号,包括1~N个终端设备的专用域,即终端设备specific field(s)(特定字段),也称为终端设备的专用比特域,终端设备的专用域中承载有终端设备的WUS信号的信息,此外,Group-based WUS中还包括循环冗余校验(Cyclic Redundancy Check,CRC)位,在一种可能的实施例中,终端设备可以在接收到的Group-based WUS根据CRC位校 验是否为正常的WUS,而非虚警WUS。
PDCCH WUS除了承载唤醒指示外,还可以承载其他配置信息,例如该其他配置信息可以包括终端设备在功耗节省状态下的配置参数。该其他配置信息可以包括指示时频资源切换的信息,例如包括终端设备唤醒后的工作带宽部分(Bandwidth Part,BWP),通常地,终端设备可以驻留在一个带宽较窄的BWP上检测WUS,WUS中指示终端设备唤醒后的工作BWP,该工作BWP的带宽较大,具有更高的数据传输速率,更加方便终端设备唤醒后在工作BWP上进行数据传输,示例的,PDCCH WUS中可以携带目标BWP的标识信息,终端设备解析到PDCCH WUS中的BWP的标识信息,并切换到新的目标BWP上进行数据传输。UE-specific PDCCH WUS能够承载该终端设备大量的配置信息,该终端设备大量的配置信息可能占用一整个PDCCH中的资源,所占的资源开销较大。相比于UE-specific PDCCH WUS,Group-based WUS中能够承载更多个终端设备的配置信息,但是针对每个终端设备可能承载的配置信息较少,网络侧设备使用Group-based WUS唤醒终端设备时,相比于UE-specific PDCCH WUS,能够占用较少的下行控制信令。
指示时频资源切换的信息需要有较高的可靠性,这是因为指示时频资源切换的信息如果收错或漏检,终端设备将不会切换到网络侧设备指定的时频资源上接收下行数据,而此时网络侧设备已经切换到了指定的时频资源上发送调度DCI,终端设备却停留在网络侧设备之前的时频资源或错误的时频资源上接收数据,导致终端设备和网络侧设备的下行资源不匹配。如果发生了这种情况,终端设备和网络侧设备只能等到设定的定时器超时才会切换到默认的时频资源上,重新开始数据调度,其中该设定的定时器与DRX的inactive timer可以不同,而等待该设定的定时器超时的过程的时间较长,将会带来很大的数据传输时延,因此一种解决的方式为:终端设备针对网络侧设备发送的WUS发送反馈信息,如混合自动重传请求(Hybrid Automatic Repeat request,HARQ)反馈信息,用于告知网络侧设备终端设备自身是否已经正确接收到了WUS,或者是告知网络侧设备终端设备自身是否已经接收唤醒信息。
终端设备发送反馈信息一般是在物理上行控制信道(Physical Uplink Control Channel,PUCCH)上反馈,需要占用上行时频资源,网络侧设备在WUS中指示时频资源切换的信息时,也指示终端设备反馈信息的PUCCH资源,该PUCCH资源为终端设备反馈信息时使用的PUCCH资源。
下面以指示时频资源切换的信息包括终端设备唤醒后的工作BWP为例进行说明:
首先对BWP进行简单地介绍,与LTE系统相比,NR系统中网络侧设备和终端设备侧可能配置不同的带宽,终端设备可以根据自己的业务需求和制造成本配置自己的最大工作带宽,例如,低成本低速率终端设备的工作带宽可能只有5兆赫(Mega Hertz,MHz),而高速率高性能终端设备的工作带宽可能会达到100MHz,如果小区的一个载波带宽按照低成本低速率终端设备进行设置(如设置为5~10MHz),那么对于高速率高性能终端设备可能需要采用载波聚合(carrier aggregation)的方式才能获得较高的速率,这势必增加了控制信令开销和处理复杂度;如果小区的载波带宽按照高速率高性能来设置(如设置为100MHz),那么低成本低性能终端设备可能需要装备适合大带宽的射频和基带器件才能够接入小区,这无疑会增加了成本。因此NR中引入了BWP的概念,一个BWP是一个小区载波上一段连续的频率资源,网络侧设备可以给不同的终端设备配置不同带宽大小的BWP,当BWP被配置并且激活后,该BWP被称为active BWP,终端设备上行发送的数据和控制 信息或终端设备下行接收的数据和控制信息都将在active BWP内完成。在NR Rel-15版本协议中,一个终端设备在上行和下行分别只能有一个active BWP。因此为了使得根据业务需要在不同时刻,终端设备能够工作在相应的BWP上收发数据,NR支持使用在调度DCI中触发终端设备进行DCI切换,其中不同的DCI可以用来指示不同的BWP。其中调度DCI被称为scheduling DCI,调度DCI也称为调度数据的DCI,可以包括调度终端设备接收下行物理下行共享信道(Physical Downlink Shared Channel,PDSCH)数据的DCI(如format 1_1),也可以包括调度终端设备发送上行物理上行共享信道(Physical Uplink Shared Channel,PUSCH)数据的DCI(如format 0_1)。终端设备接收到调度DCI后,根据该DCI指示的新的BWP上接收或发送数据。
如图3所示,在DRX cycle内终端设备在BWP2上接收网络侧设备发送的WUS,该WUS中指示了终端设备唤醒,并指示了终端设备切换到BWP1工作,DRX cycle进入到On Duration,终端设备唤醒并切换到BWP1上,终端设备在BWP1上检测PDCCH和PDSCH。
网络侧设备发送的WUS中指示终端设备切换到新的工作BWP时,还指示终端设备发送HARQ反馈信息的PUCCH资源,用于指示终端设备发送HARQ反馈信息的PUCCH资源的信息可以包括以下内容:K1和HARQ资源指示(HARQ Resource Indicator,ARI),其中K1用于指示网络侧设备发送WUS时所在的时隙与终端设备发送HARQ反馈信息时所在的时隙之间的时间间隔,ARI中具体用于指示针对WUS的反馈使用哪个PUCCH资源,可以包括PUCCH资源的标识信息,所占的频域位置(如起始物理资源块(Physical Resource Block,PRB)),和PUCCH资源格式中的一项或多项。
一般地,指示K1至少需要2~3比特,指示ARI至少需要2~3比特,因此针对每个终端设备,至少需要4~6比特来指示发送HARQ反馈信息的PUCCH资源。因此在UE-specific PDCCH WUS中至少需要4~6比特来指示该终端设备发送HARQ反馈信息的PUCCH资源,在Group-based WUS中针对每个终端设备,均至少需要4~6比特来指示终端设备发送HARQ反馈信息的PUCCH资源。假设一个Group-based WUS共指示5个终端设备,Group-based WUS中用于指示这5个终端设备反馈信息的PUCCH资源的信息就需要占用25个比特,再加上用于唤醒终端设备的唤醒信息,就有可能超出Group-based WUS所能承载的比特数,或者如果Group-based WUS的净荷为40比特,那么用于指示该5个终端设备发送HARQ反馈信息的PUCCH资源就占用了Group-based WUS 60%以上的比特数,占用的比特数过多,从而提高了Group-based WUS的码率,降低了Group-based WUS的接收性能,其中净荷为Payload,为信元中除去信头以外的纯信息部分。
因此为了保证WUS中携带的指示反馈信息的PUCCH资源的信息不超过其所能承载的比特数,以及保证WUS的接收性能,网络侧设备在发送WUS时,尤其是在发送Group-based WUS时,可以通过减少Group-based WUS中指示的终端设备数目,例如从5个终端设备复用减少为3个终端设备复用,这样在需要指示的终端设备的总数量不变的情况下,就需要发送更多的Group-based WUS才能实现指示全部的终端设备,这样同样会造成网络侧设备信令开销过大,降低下行的系统容量。
鉴于此,为了减少网络侧设备信令开销,提高下行的系统容量,本申请提出一种唤醒信号WUS检测方法来保证网络侧设备下发的WUS中不指示PUCCH资源,以减少网络侧设备的信令开销。
在该方法中,终端设备中预先配置有用于反馈信息的PUCCH资源,因此终端设备可 以通过该PUCCH资源,反馈是否接收到该终端设备的唤醒信息的消息,因此网络侧发送给终端设备中的WUS至少包括用于指示唤醒终端设备的唤醒信息即可,一个WUS中可以携带尽可能多地终端设备的唤醒信息,可以节省在WUS中指示PUCCH资源带来的信令开销,并减少网络侧设备的信令开销。
下面结合图4,详细说明WUS检测方法的具体过程。如图4所示,该过程包括:
步骤401:网络侧设备向第一终端设备发送第二消息。其中第二消息用于配置终端设备反馈信息时使用的第一PUCCH资源。在该步骤中,将预先配置PUCCH资源的终端设备称为第一终端设备,第一终端设备的数量可以为一个或多个。
网络侧设备可以是将与其连接的每个终端设备作为预先配置PUCCH资源的第一终端设备。
或者,网络侧设备在向终端设备发送WUS之前,可以先确定待唤醒的终端设备,这里将待唤醒的终端设备称为第二终端设备,网络侧设备可以在第二终端设备中确定预先配置PUCCH资源的第一终端设备,即假设待唤醒的第二终端设备为N个,网络侧设备在N个第二终端设备中确定M个第一终端设备,M<=N。例如,通常网络侧设备指示终端设备切换时频资源时,有可能造成后续网络侧设备和终端设备双方未切换到同一时频资源上,导致上下行资源不匹配数据收发错误,因此网络侧设备可以在第二终端设备中,选取时频资源发生切换的终端设备作为预先配置PUCCH资源的第一终端设备。
在一种实现方式中,第二消息中仅包括特定一个第一终端设备反馈信息时使用的第一PUCCH资源。一般地,该特定一个第一终端设备还用于接收该第二消息。
在另一种实现方式中,第二消息中可以包括每个第一终端设备反馈信息时使用的第一PUCCH资源。
在该实现方式中,第二消息中具体可以包括每个第一终端设备反馈信息时使用的第一PUCCH资源及其对应的索引。后续终端设备可以通过索引查找到终端设备对应的第一PUCCH资源。
可选地,第二消息中还可以包括PUCCH的发送时间偏移,该PUCCH的发送时间偏移用于指示终端设备反馈PUCCH的时间。所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
可选地,网络侧设备向第一终端设备发送的第二消息,具体还可以用于配置第一终端设备的上行BWP,以及为每个上行BWP配置第一PUCCH资源。后续终端设备可以在上行BWP工作,并采用第一PUCCH资源,发送上行数据(如上行控制信息)。
网络侧设备可以通过信令发送第二消息,例如,该信令可以为无线资源控制(Radio Resource Control,RRC)信令,可以复用现有其他信令,也可以为自定义的新增信令等,在此不做限定。
步骤402:第一终端设备接收网络侧设备发送的第二消息。
第一终端设备接收网络侧设备发送的第二消息,将第二消息中包括的终端设备反馈信息时使用的第一PUCCH资源配置到该第一终端设备中。
可选地,如果网络侧设备向第一终端设备发送的第二消息中还配置了第一终端设备的上行BWP,第一终端设备可以根据该第二消息的指示,在被唤醒之后,切换到上行BWP工作,并采用该上行BWP对应的第一PUCCH资源,发送上行数据。
步骤403:网络侧设备向第二终端设备发送WUS。
网络侧设备在向终端设备发送WUS之前,可以先确定待唤醒的终端设备,这里将待唤醒的终端设备称为第二终端设备,其中待唤醒的第二终端设备可以一个或多个。网络侧设备可以向待唤醒的第二终端设备发送WUS,具体的,网络侧根据待唤醒的第二终端设备,生成WUS,然后将生成的WUS下发给第二终端设备。
如果网络侧设备是将与其连接的每个终端设备作为预先配置PUCCH资源的第一终端设备,则配置有PUCCH资源的第一终端设备可能并非都需要唤醒,因此待唤醒的第二终端设备可以理解为是配置有PUCCH资源的第一终端设备中的部分(或全部)终端设备。
在一个示例中,网络侧设备向第二终端设备发送的WUS包括UE-specific PDCCH WUS。在该示例中,网络侧设备在生成UE-specific PDCCH WUS时可以直接将用于唤醒第二终端设备的唤醒信息及第二终端设备的其他相关信息包括在UE-specific PDCCH WUS中。
或者,网络侧设备在UE-specific PDCCH WUS确定该第二终端设备的专用域的位置,将第二终端设备的唤醒信息和/或第二终端设备的其他相关信息包括在该第二终端设备的专用域中。
UE-specific PDCCH WUS中可以包括一个第二终端设备的专用域,具体的,UE-specific PDCCH WUS中的所有信息可以均认为是该一个第二终端设备的专用域。
在另一个示例中,网络侧设备向第二终端设备发送的WUS包括Group-based WUS。在该示例中,网络侧设备在生成Group-based WUS时可以是根据待指示唤醒的第二终端设备,确定待指示唤醒的第二终端设备在Group-based WUS中的专用域的位置,第二终端设备在Group-based WUS中的专用域的位置可以用于指示Group-based WUS中的第几个终端设备专用域为该第二终端设备的专用域,即第二终端设备的专用域在Group-based WUS的专用域中出现的顺序,网络侧设备可以将第二终端设备的唤醒信息及第二终端设备的其他相关信息包括在Group-based WUS中。可选地,网络侧设备还可以将第二终端设备的唤醒信息和/或第二终端设备的其他相关信息包括在终端设备的专用域中。
Group-based WUS中包括一个或多个第二终端设备的专用域。
在一种实现方式中,网络侧设备可以根据第二终端设备的标识信息,确定第二终端设备的专用域在该WUS中的位置。
可选地,终端设备的标识信息可以包括终端设备的标识符,可以是终端设备的唯一编码(Identity document,ID),可以为无线网络临时标识(RNTI Radio Network Temporary Identity,RNTI)等中的一项或多项。
以终端设备的标识信息为终端设备的标识符为例,网络侧设备可以对第二终端设备的标识符进行取模运算,将取模运算的结果作为第二终端设备的专用域在所述WUS中的位置的信息。
在该实现方式中,网络侧设备根据确定的第二终端设备的专用域在WUS中的位置,生成的WUS的结构可以如图2所示,图2中包括1~N个第二终端设备的专用域和CRC校验位。
在另一种实现方式中,网络侧设备可以在WUS中包括唤醒指示域(Wake-up indicator fields,WIF),网络侧设备根据第二终端设备的标识信息和WIF,确定该第二终端设备的专用域在WUS中的位置信息。
还以终端设备的标识信息为终端设备的标识符为例,网络侧设备可以对第二终端设备 的标识信息与WIF进行计算,如进行加法、减法、乘法、除法(除法运算的结果可以进行向下取整或向上取整)、取模运算等,根据计算结果确定第二终端设备的专用域在WUS中的位置的信息。
在该实现方式中,网络侧设备根据确定的第二终端设备的专用域在WUS中的位置,生成WUS的结构可以如图5所示,图5中包括WIF、1~N个第二终端设备的专用域和CRC校验位。在实际WUS的结构中,WIF的位置可以位于WUS的头部、中间或尾部,可以不做限定。
可选地,第二终端设备的其他相关信息还可以包括PUCCH的发送时间偏移和/或指示时频资源切换的信息。
例如,指示时频资源切换的信息可以包括指示BWP切换的信息。该指示BWP切换的信息可以为终端设备接收下行数据的工作BWP的信息,该终端设备接收下行数据的工作BWP的信息可以为BWP的标识信息。具体地,该终端设备接收下行数据的工作BWP可以为终端设备在DRX ON(即DXR状态的唤醒模式)期间接收下行数据的工作BWP。
所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
实际应用中,所述第二消息和/或所述WUS中均可以包括PUCCH的发送时间偏移,第二消息中包括PUCCH的发送时间偏移时,WUS的结构可以如图2或图5所示,WUS中包括PUCCH的发送时间偏移时,WUS的结构可以如图6所示,其中图6为在图5的基础上的改进,图6中包括WIF、1~N个第二终端设备的专用域和CRC校验位,第二个第二终端设备的专用域中包括PUCCH的发送时间偏移T_offset。
第二消息中包括PUCCH的发送时间偏移,可以减少占用WUS中的信令开销。与所述第二消息中包括PUCCH的发送时间偏移相比,所述WUS中包括PUCCH的发送时间偏移虽然占用了WUS中少量的信令开销,但是可以提高上行传输PUCCH的灵活性。
步骤404:如果第三终端设备检测到网络侧设备发送的所述WUS,所述第三终端设备在所述WUS中检测所述终端设备的专用域,并在所述WUS中检测所述终端设备的唤醒信息。
如果下行PDCCH资源阻塞或下行信道质量较差时,网络侧设备可能无法发送出WUS,或终端设备没有检测到网络侧设备发送的WUS,因此在该步骤中将检测到网络侧设备发送的WUS的终端设备称为第三终端设备,用以与网络侧设备实际下发的第二终端设备进行区分,其中第三终端设备为部分或全部第二终端设备。终端设备在没有接收到WUS之前,还可以尝试检测WUS。
在一个示例中,如果终端设备在DRX状态,终端设备监听PDCCH信道,在所述PDCCH信道上检测是否接收到WUS。
第三终端设备检测到UE-specific PDCCH WUS或Group-based WUS,均可以认为检测到WUS。
在另一个示例中,第三终端设备尝试检测UE-specific PDCCH WUS,由于UE-specific PDCCH WUS中的所有信息可以均认为是该终端设备的专用域,因此如果检测到UE-specific PDCCH WUS,则第三终端设备可以确定存在WUS了;如果未终端设备检测到UE-specific PDCCH WUS,第三终端设备尝试检测Group-based WUS,如果检测到 Group-based WUS,由于Group-based WUS中通常包括多个终端设备的专用域,第三终端设备还可以检测Group-based WUS中终端设备的专用域,来确认是否存在该第三终端设备的专用域,和第三终端设备的唤醒信息,从而确认是否检测到了WUS。
第三终端设备如果检测到WUS,会在检测到的WUS中检测第三终端设备的专用域,以及在WUS中检测第三终端设备的唤醒信息。对于UE-specific PDCCH WUS,该UE-specific PDCCH WUS中全部的控制信息均认为是第三终端设备的专用域,第三终端设备根据检测到的UE-specific PDCCH WUS可以直接确认存在该第三终端设备的专用域;对于Group-based WUS,该Group-based WUS中的部分控制信息为第三终端设备的专用域,第三终端设备根据检测到的Group-based WUS,需要确定第三终端设备的专用域的位置,然后根据该第三终端设备的专用域的位置,确认是否存在该第三终端设备的专用域。
终端设备在接收WUS中确定终端设备的专用域的位置,与网络侧设备生成WUS时确定终端设备的专用的位置的过程基本相同。
在一个实现方式中,如果WUS中不包括唤醒指示域WIF,第三终端设备确定该第三终端设备的标识信息,根据该标识信息,确定该第三终端设备的专用域在所述WUS中的位置,从而定位到WUS中第三终端设备的专用域的位置。
在另一个实现方式中,如果WUS中包括WIF,第三终端设备确定该第三终端设备的标识信息,根据该标识信息和WIF,确定该第三终端设备的专用域在所述WUS中的位置。第三终端设备确定该第三终端设备的专用域在WUS中的位置的信息后,可以在WUS中该位置处检测该第三终端设备的专用域。WUS中还可以包括唤醒信息,第三终端设备还可以在WUS中检测是否包括该第三终端设备的唤醒信息。
可选地,WUS中第三终端设备的专用域中可以包括第三终端设备的唤醒信息。
步骤405:第三终端设备如果在WUS中检测到所述第三终端设备的专用域,且检测所述WUS中包括所述第三终端设备的唤醒信息,第三终端设备在预先配置的PUCCH资源中确定第一PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述第三终端设备的唤醒信息的第一消息。
网络侧设备接收第一PUCCH,根据该第一PUCCH中包括的第一消息,确定终端设备接收到唤醒信息。
第三终端设备中保存有预先配置的反馈信息时使用的第一PUCCH资源,网络侧设备为第三终端设备配置PUCCH资源的过程可以参见步骤401和步骤402。
第三终端设备中保存的预先配置的反馈信息时使用的第一PUCCH资源,可以仅包括该第三终端设备反馈信息时使用的第一PUCCH资源,可以包括多个终端设备反馈信息时使用的第一PUCCH资源,其中该多个终端设备中包括该第三终端设备。
如果第三终端设备中保存的第一PUCCH资源仅包括该第三终端设备反馈信息时使用的第一PUCCH资源,第三终端设备可以直接确定其对应的第一PUCCH资源。
如果第三终端设备中保存的第一PUCCH资源包括多个终端设备反馈信息时使用的第一PUCCH资源,第三终端设备可以在预先配置的第一PUCCH资源中,确定该第三终端设备的专用域的位置信息对应的第一PUCCH资源,其中对于Group-based WUS,第三终端设备的专用域的位置为第三终端设备的专用域在Group-based WUS的专用域中出现的顺序。
可选地,第三终端设备以该第三终端设备的专用域的位置信息作为第一索引,在预先 配置的第一PUCCH资源中,确定与该第一索引对应的第一PUCCH资源。
如图7所示,在图5的基础上查找PUCCH资源的示意图,WUS中的终端设备的专用域的顺序与配置给终端设备的PUCCH资源的顺序一致,因此终端设备可以将终端设备的专用域的位置信息作为索引,在配置的PUCCH资源中查找索引对应的PUCCH资源,如果UE-specific field 1的位置为1,索引为1,则在配置的PUCCH资源中该索引为1对应的PUCCH资源为PUCCH resource 1,则查找到该终端设备对应的PUCCH资源。
如果WUS或者第二消息中包括PUCCH的发送时间偏移,则第三终端设备确定所述第三终端设备对应的第一PUCCH资源后,可以在该PUCCH的发送时间偏移后,在第三终端设备对应的第一PUCCH资源上,发送第一PUCCH。
如图8所示,图8为在图6的基础上反馈第一PUCCH的示意图,如果第三终端设备的专用域为UE-specific field 2,并且该第三终端设备的专用域中包括PUCCH的发送时间偏移T_offset,如果该PUCCH的发送时间偏移包括接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,则第三终端设备在接收该WUS的T_offset时间之后,在第三终端设备对应的第一PUCCH资源上,即如图8所示的上行带宽部分UL BWP中的PUCCH resource 2上,发送第一PUCCH。
如果第三终端设备在WUS中检测到该第三终端设备的唤醒信息,第三终端设备可以尝试在DRX ON中检测调度PDCCH。
如果第三终端设备在该第三终端设备的专用域中检测到指示时频资源切换的信息,第三终端设备还可以切换到WUS中指示的时频资源上工作,例如指示时频资源切换的信息包括指示BWP切换的信息,第三终端设备切换到该指示的BWP上工作,进行数据收发。
第一PUCCH中包括用于反馈接收到该第三终端设备的唤醒信息的第一消息,如果网络侧设备接收该第一PUCCH,网络侧设备根据该第一PUCCH中包括的第一消息,确定第三终端设备接收到唤醒信息。可选地,如果WUS中指示有指示时频资源切换的信息,网络侧设备接收到该第一PUCCH后,还可以根据第一PUCCH中包括的第一消息,确定第三终端设备切换到了指示的时频资源上工作。
可选地,如果终端设备没有接收到的WUS,或者终端设备在接收到的WUS未检测到终端设备的专用域,或者终端设备在接收到WUS中未检测到终端设备的唤醒信息,确定终端设备没有接收到终端设备的唤醒信息,也可以认为终端设备没有接收到WUS,或者终端设备没有正确接收到调度DCI,这里可以将没有接收到唤醒信息的终端设备称为第四终端设备。
第四终端设备中可以预先配置有第二PUCCH资源,如果第四终端设备确定没有接收到唤醒信息,第四终端设备采用该第二PUCCH资源发送第二PUCCH,该第二PUCCH中包括用于反馈未接收唤醒信息的第三消息。
在一个示例中,如果第四终端设备未检测到UE-specific PDCCH WUS,尝试检测Group-based WUS后,也未检测到Group-based WUS,确定未接收到WUS,该第三消息还可以用于反馈未接收到Group-based WUS。
如果网络侧设备接收到第二PUCCH,网络侧设备根据该第二PUCCH中包括的第三消息,确定终端设备未接收到唤醒信息,或者确定终端设备未接收到Group-based WUS,进而确定终端设备未接收到唤醒信息。
通过本申请实施例提供的方案,在终端设备中预先配置有用于反馈信息的PUCCH资 源,终端设备在接收到发给自身的WUS之后,能够通过该预先配置的PUCCH资源中终端设备对应的第一PUCCH资源,反馈接收到该终端设备的唤醒信息的第一消息,降低了WUS中携带的反馈指示信息的比特数,降低了PDCCH码率,减少了网络侧设备的信令开销,增加了下行信道容量。
下面以几个具体的实施例进行说明。
实施例一:以图9所示的WUS检测过程为例进行说明,包括以下步骤:
步骤901:网络侧向终端设备发送第二消息,该第二消息用于配置该终端设备反馈信息时使用的第一PUCCH资源。
可选地,第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
步骤902:终端设备接收网络侧设备发送的第二消息。
步骤903:网络侧设备向终端设备发送WUS。
可选地,WUS中还包括PUCCH的发送时间偏移。
步骤904:终端设备接收WUS,并在该WUS中检测该终端设备的专用域。
可选地,终端设备在该WUS中检测该终端设备的唤醒信息。
步骤905:如果终端设备在WUS中检测到了该终端设备的专用域和该终端设备的唤醒信息,终端设备以该终端设备的专用域的位置信息作为第一索引,确定与该第一索引对应的第一PUCCH资源,发送第一PUCCH,第一PUCCH中包括用于反馈接收到该终端设备的唤醒信息的第一消息。
在一个示例中,如果WUS中包括WIF,终端设备确定该终端设备的标识信息,根据该标识信息和该WIF,确定终端设备的专用域在WUS中的位置。
在另一个示例中,如果WUS中不包括WIF,终端设备确定该终端设备的标识信息,根据该标识信息,确定终端设备的专用域在WUS中的位置。
步骤906:网络侧设备接收第一PUCCH,根据该第一PUCCH中包括的第一消息,确定终端设备接收到唤醒信息。
实施例二:以图10所示的WUS检测过程为例进行说明,包括以下步骤:
步骤1001:网络侧向终端设备发送第二消息,该第二消息用于配置该终端设备反馈信息时使用的第一PUCCH资源。
可选地,第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
步骤1002:终端设备接收网络侧设备发送的第二消息。
步骤1003:网络侧设备向终端设备发送WUS。
可选地,WUS中还包括PUCCH的发送时间偏移。
可选地,WUS为UE-specific PDCCH WUS,或者WUS为Group-based WUS。
步骤1004:终端设备接收WUS,并在该WUS中检测该终端设备的专用域。
可选地,终端设备在该WUS中检测该终端设备的唤醒信息。
在一种实施方式中,终端设备检测UE-specific PDCCH WUS,如果检测到UE-specific PDCCH WUS,确定接收到WUS。
在另一种实施方式中,如果终端设备未检测到UE-specific PDCCH WUS,终端设备尝试检测Group-based WUS,如果检测到Group-based WUS,确定接收到WUS。如果未检测到Group-based WUS,终端设备采用预先配置的第二PUCCH资源发送第二PUCCH,该第二PUCCH中包括用于反馈未接收到该Group-based WUS的第三消息。
步骤1005:如果终端设备在WUS中检测到了该终端设备的专用域和该终端设备的唤醒信息,终端设备采用预先配置的第一PUCCH资源,发送第一PUCCH,第一PUCCH中包括用于反馈接收到该终端设备的唤醒信息的第一消息。
在一个示例中,如果WUS中包括WIF,终端设备确定该终端设备的标识信息,根据该标识信息和该WIF,确定终端设备的专用域在WUS中的位置,确定该终端设备的专用域的位置信息对应的第一PUCCH资源。
在另一个示例中,如果WUS中不包括WIF,终端设备确定该终端设备的标识信息,根据该标识信息,确定终端设备的专用域在WUS中的位置,确定该终端设备的专用域的位置信息对应的第一PUCCH资源。
步骤1006:网络侧设备接收第一PUCCH,根据该第一PUCCH中包括的第一消息,确定终端设备接收到唤醒信息。
可选地,如果网络侧设备接收到采用第二PUCCH资源发送的第二PUCCH,根据该第二PUCCH中第三消息,确定终端设备未接收到唤醒消息。
以上结合图4至图10详细说明了本申请实施例的WUS检测方法,基于与上述WUS检测方法的同一发明构思,本申请实施例还提供了一种WUS检测装置,如图11所示,所述WUS检测装置1100中包含处理单元1101和收发单元1102,装置1100可用于实现上述应用于终端设备或网络侧设备的方法实施例中描述的方法。
在一个实施例中,装置1100应用于终端设备。
具体的,所述处理单元1101,用于在检测到的WUS中检测所述终端设备的专用域;如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,以所述终端设备的专用域的位置信息作为第一索引,确定与所述第一索引对应的第一PUCCH资源。所述收发单元1102,用于采用所述第一PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息。
在一个实现方式中,所述收发单元1102,还用于接收网络侧设备发送的第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
在一个实现方式中,所述处理单元1101,具体用于如果所述WUS中包括WIF,确定所述终端设备的标识信息;根据所述标识信息和所述WIF,确定所述终端设备的专用域在所述WUS中的位置。
在一个实现方式中,所述处理单元1101,具体用于如果所述WUS中不包括WIF,确定所述终端设备的标识信息;根据所述标识信息,确定所述终端设备的专用域在所述WUS中的位置。
在一个实现方式中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移, 所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
在另一个实施例中,装置应用于终端设备。
具体的,所述处理单元1101,用于如果检测到WUS,在所述WUS中检测所述终端设备的专用域;如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,确定预先配置的第一PUCCH资源。所述收发单元1102,用于采用所述第一PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息。
在一个实现方式中,所述WUS为UE-specific PDCCH WUS。
在一个实现方式中,所述处理单元1101,还用于所述WUS为Group-based WUS,如果终端设备未检测到UE-specific PDCCH WUS,终端设备尝试检测所述Group-based WUS。
在一个实现方式中,所述收发单元1102,还用于如果所述终端设备未检测到Group-based WUS,采用预先配置的第二PUCCH资源发送第二PUCCH,所述第二PUCCH中包括用于反馈未接收到所述Group-based WUS的第三消息。
在一个实现方式中,所述收发单元1102,还用于接收网络侧设备发送的第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
在一个实现方式中,所述处理单元1101,具体用于如果所述WUS中包括WIF,确定所述终端设备的标识信息;根据所述标识信息和所述WIF,确定所述终端设备的专用域在所述WUS中的位置;确定所述终端设备的专用域的位置信息对应的第一PUCCH资源。
在一个实现方式中,所述处理单元1101,具体用于如果所述WUS中不包括WIF,确定所述终端设备的标识信息;根据所述标识信息,确定所述终端设备的专用域在所述WUS中的位置;确定所述终端设备的专用域的位置信息对应的第一PUCCH资源。
在一个实现方式中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
在又一个实施例中,装置应用于网络侧设备。
具体的,所述收发单元1102,用于向终端设备发送WUS,所述WUS中包括所述终端设备的专用域;接收所述终端设备采用预先配置的第一PUCCH资源发送的第一PUCCH;
所述处理单元1101,用于根据所述第一PUCCH中包括的用于反馈接收到所述终端设备的唤醒信息的第一消息,确定所述终端设备接收到唤醒信息。
在一个实现方式中,所述收发单元1102,还用于向所述终端设备发送第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
在一个实现方式中,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
在一个实现方式中,所述收发单元1102,还用于接收所述终端设备采用第二PUCCH资源发送的第二PUCCH。所述处理单元1101,还用于根据所述第二PUCCH中包括的用 于反馈未接收到Group-based WUS的第三消息,确定所述终端设备未接收到唤醒信息。
需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于与上述WUS检测方法相同的构思,如图12所示,本申请实施例还提供了一种WUS检测装置1200的结构示意图。装置1200可用于实现上述应用于终端设备或网络侧设备的方法实施例中描述的方法,可以参见上述方法实施例中的说明。
所述装置1200包括一个或多个处理器1201。所述处理器1201可以是通用处理器或者专用处理器等。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理,中央处理器可以用于对通信装置(如,基站、终端、或芯片等)进行控制,执行软件程序,处理软件程序的数据。所述通信装置可以包括收发单元,用以实现信号的输入(接收)和输出(发送)。例如,所述收发单元可以为收发器,射频芯片等。
所述装置1200包括一个或多个所述处理器1201,所述一个或多个处理器1201可实现上述所示的实施例中终端设备或网络侧设备的方法。
可选的,处理器1201除了实现上述所示的实施例的方法,还可以实现其他功能。一种设计中,处理器1201可以执行指令,使得所述装置1200执行上述方法实施例中描述的方法。所述指令可以全部或部分存储在所述处理器内,如指令1203,也可以全部或部分存储在与所述处理器耦合的存储器1202中,如指令1204,也可以通过指令1203和1204共同使得装置1200执行上述方法实施例中描述的方法。
在又一种可能的设计中,通信装置1200也可以包括电路,所述电路可以实现前述方法实施例中终端设备或网络侧设备的功能。在又一种可能的设计中所述装置1200中可以包括一个或多个存储器1202,其上存有指令1204,所述指令可在所述处理器上被运行,使得所述装置1200执行上述方法实施例中描述的方法。可选的,所述存储器中还可以存储有数据。可选的处理器中也可以存储指令和/或数据。例如,所述一个或多个存储器1202可以存储上述实施例中所描述的对应关系,或者上述实施例中所涉及的相关的参数或表格等。所述处理器和存储器可以单独设置,也可以集成在一起。
在又一种可能的设计中,所述装置1200还可以包括收发器1205以及天线1206。所述处理器1201可以称为处理单元,对装置(终端或者基站)进行控制。所述收发器1205可以称为收发机、收发电路、或者收发单元等,用于通过天线1206实现装置的收发功能。
应注意,本申请实施例中的处理器可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读介质,其上存储有计算机程序,该计算机程序被计算机执行时实现上述应用于终端设备或网络侧设备的任一方法实施例所述的WUS检测方法。
本申请实施例还提供了一种计算机程序产品,该计算机程序产品被计算机执行时实现上述应用于终端设备或网络侧设备的任一方法实施例所述的WUS检测方法。
本申请实施例还提供了一种通信系统,所述通信系统包括用于实现上述任一方法实施例的终端设备和用于实现上述任一方法实施例的网络侧设备。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计 算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,高密度数字视频光盘(Digital Video Disc,DVD))、或者半导体介质(例如,固态硬盘(Solid State Disk,SSD))等。
本申请实施例还提供了一种处理装置,包括处理器和接口;所述处理器,用于执行上述应用于终端设备或网络侧设备的任一方法实施例所述的WUS检测方法。
应理解,上述处理装置可以是一个芯片,所述处理器可以通过硬件来实现也可以通过软件来实现,当通过硬件实现时,该处理器可以是逻辑电路、集成电路等;当通过软件来实现时,该处理器可以是一个通用处理器,通过读取存储器中存储的软件代码来实现,改存储器可以集成在处理器中,可以位于所述处理器之外,独立存在。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、计算机软件或者二者的结合来实现,为了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另外,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接,也可以是电的,机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到本申请可以用硬件实现,或固件实现,或它们的组合方式来实现。当使用软件实现时,可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于:计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如,如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源 传输的,那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的,盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟,其中盘通常磁性的复制数据,而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之,以上所述仅为本申请技术方案的较佳实施例而已,并非用于限定本申请的保护范围。凡在本申请的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本申请的保护范围之内。

Claims (21)

  1. 一种唤醒信号WUS检测方法,其特征在于,包括:
    终端设备在检测到的WUS中检测所述终端设备的专用域;
    如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,所述终端设备以所述终端设备的专用域的位置信息作为第一索引,确定与所述第一索引对应的第一物理上行控制信道PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息。
  2. 如权利要求1所述的方法,其特征在于,终端设备在检测到的WUS中检测所述终端设备的专用域之前,还包括:
    所述终端设备接收网络侧设备发送的第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
  3. 如权利要求1或2所述的方法,其特征在于,如果所述WUS中包括唤醒指示域WIF,确定所述终端设备的专用域的位置包括:
    所述终端设备确定所述终端设备的标识信息;
    根据所述标识信息和所述WIF,确定所述终端设备的专用域在所述WUS中的位置。
  4. 如权利要求1-3任一项所述的方法,其特征在于,如果所述WUS中不包括WIF,确定所述终端设备的专用域的位置包括:
    所述终端设备确定所述终端设备的标识信息;
    根据所述标识信息,确定所述终端设备的专用域在所述WUS中的位置。
  5. 如权利要求2所述的方法,其特征在于,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
  6. 一种唤醒信号WUS检测方法,其特征在于,包括:
    终端设备如果检测到WUS,在所述WUS中检测所述终端设备的专用域;
    如果在所述WUS中检测到了所述终端设备的专用域,且检测到所述WUS中包括所述终端设备的唤醒信息,所述终端设备采用预先配置的第一物理上行控制信道PUCCH资源,发送第一PUCCH,所述第一PUCCH中包括用于反馈接收到所述终端设备的唤醒信息的第一消息。
  7. 如权利要求6所述的方法,其特征在于,所述WUS为终端设备专用下行控制信道唤醒信号UE-specific PDCCH WUS。
  8. 如权利要求6所述的方法,其特征在于,所述WUS为基于组的唤醒信号Group-based WUS,还包括:
    如果终端设备未检测到UE-specific PDCCH WUS,终端设备尝试检测所述Group-based WUS。
  9. 如权利要求8所述的方法,其特征在于,如果所述终端设备未检测到Group-based WUS,还包括:
    所述终端设备采用预先配置的第二PUCCH资源发送第二PUCCH,所述第二PUCCH中包括用于反馈未接收到所述Group-based WUS的第三消息。
  10. 如权利要求6-8任一项所述的方法,其特征在于,在所述WUS中检测所述终端设备的专用域之前,所述方法还包括:
    所述终端设备接收网络侧设备发送的第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
  11. 如权利要求6或7或8或10所述的方法,其特征在于,如果所述WUS中包括唤醒指示域WIF,所述终端设备确定第一PUCCH资源包括:
    所述终端设备确定所述终端设备的标识信息;
    根据所述标识信息和所述WIF,确定所述终端设备的专用域在所述WUS中的位置;
    确定所述终端设备的专用域的位置信息对应的第一PUCCH资源。
  12. 如权利要求6或7或8或10或11所述的方法,其特征在于,如果所述WUS中不包括WIF,所述终端设备确定第一PUCCH资源包括:
    所述终端设备确定所述终端设备的标识信息;
    根据所述标识信息,确定所述终端设备的专用域在所述WUS中的位置;
    确定所述终端设备的专用域的位置信息对应的第一PUCCH资源。
  13. 如权利要求10所述的方法,其特征在于,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
  14. 一种唤醒信号WUS检测方法,其特征在于,包括:
    网络侧设备向终端设备发送WUS,所述WUS中包括所述终端设备的专用域;
    所述网络侧设备接收所述终端设备采用预先配置的第一物理上行控制信道PUCCH资源发送的第一PUCCH;根据所述第一PUCCH中包括的用于反馈接收到所述终端设备的唤醒信息的第一消息,确定所述终端设备接收到唤醒信息。
  15. 如权利要求14所述的方法,其特征在于,所述网络侧设备向终端设备发送WUS之前,所述方法还包括:
    所述网络侧设备向所述终端设备发送第二消息,所述第二消息用于配置所述终端设备反馈信息时使用的第一PUCCH资源。
  16. 如权利要求15所述的方法,其特征在于,所述WUS或所述第二消息中还包括PUCCH的发送时间偏移,所述PUCCH的发送时间偏移包括:接收WUS的时间和发送PUCCH反馈信息的时间之间的时间间隔,或所述终端设备在不连续接收DRX状态的唤醒模式开始时的时间和发送PUCCH反馈信息的时间之间的时间间隔。
  17. 如权利要求14-16任一项所述的方法,其特征在于,所述方法还包括:
    所述网络侧设备接收所述终端设备采用第二PUCCH资源发送的第二PUCCH;根据所述第二PUCCH中包括的用于反馈未接收到基于组的唤醒信号Group-based WUS的第三消息,确定所述终端设备未接收到唤醒信息。
  18. 一种唤醒信号WUS检测装置,其特征在于,包括处理器和存储器,所述处理器与所述存储器耦合;
    存储器,用于存储计算机程序;
    处理器,用于执行所述存储器中存储的计算机程序,以使得所述装置执行如权利要求1-17中任一项所述的方法。
  19. 一种计算机可读存储介质,其特征在于,包括程序或指令,当所述程序或指令在计算机上运行时,如权利要求1-17中任意一项所述的方法被执行。
  20. 一种计算机程序产品,其特征在于,包括程序或指令,当所述程序或指令在计算机上运行时,如权利要求1-17中任意一项所述的方法被执行。
  21. 一种芯片,其特征在于,所述芯片与存储器耦合,用于读取并执行所述存储器中存储的程序指令,以执行权利要求1-17中任意一项所述的方法。
PCT/CN2020/102843 2019-07-19 2020-07-17 一种唤醒信号wus检测方法及装置 Ceased WO2021013104A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20844418.2A EP3996427B1 (en) 2019-07-19 2020-07-17 Wake-up signal (wus) detection method and apparatus
US17/579,368 US12108332B2 (en) 2019-07-19 2022-01-19 Wake-up signal WUS detection method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910656648.7 2019-07-19
CN201910656648.7A CN112243287B (zh) 2019-07-19 2019-07-19 一种唤醒信号wus检测方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/579,368 Continuation US12108332B2 (en) 2019-07-19 2022-01-19 Wake-up signal WUS detection method and apparatus

Publications (1)

Publication Number Publication Date
WO2021013104A1 true WO2021013104A1 (zh) 2021-01-28

Family

ID=74168198

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/102843 Ceased WO2021013104A1 (zh) 2019-07-19 2020-07-17 一种唤醒信号wus检测方法及装置

Country Status (4)

Country Link
US (1) US12108332B2 (zh)
EP (1) EP3996427B1 (zh)
CN (1) CN112243287B (zh)
WO (1) WO2021013104A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115696274A (zh) * 2021-07-29 2023-02-03 华为技术有限公司 一种通信方法、装置及系统
US20240015653A1 (en) * 2021-09-02 2024-01-11 Apple Inc. Low-Power Wake Up Radio Operation in Wireless Communication
US20230276361A1 (en) * 2021-09-06 2023-08-31 Apple Inc. New Radio Low Power Wakeup Radio
CN117641536A (zh) * 2022-08-18 2024-03-01 北京三星通信技术研究有限公司 一种低功率唤醒技术的方法及设备
CN115103461B (zh) * 2022-08-24 2023-01-06 中国信息通信研究院 一种网络非连续发送和接收的方法和设备
CN117812673A (zh) * 2022-09-23 2024-04-02 维沃移动通信有限公司 信号检测和发送方法、终端及网络侧设备
CN118235377A (zh) * 2022-10-20 2024-06-21 北京小米移动软件有限公司 时域确定方法及装置
CN118339886A (zh) * 2022-11-04 2024-07-12 北京小米移动软件有限公司 发送和接收唤醒响应消息的方法及装置
WO2024197568A1 (zh) * 2023-03-28 2024-10-03 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备
WO2024239156A1 (zh) * 2023-05-19 2024-11-28 北京小米移动软件有限公司 通信方法、装置及存储介质
CN119071886A (zh) * 2023-06-01 2024-12-03 维沃移动通信有限公司 数据传输方法、唤醒信号的监听方法及装置、终端和设备
WO2025015485A1 (zh) * 2023-07-14 2025-01-23 北京小米移动软件有限公司 信息指示方法及终端、网络设备、通信系统及存储介质
CN121713630A (zh) * 2023-08-10 2026-03-20 中兴通讯股份有限公司 用于信道覆盖增强的系统和方法
CN120075829A (zh) * 2023-11-30 2025-05-30 华为技术有限公司 通信方法、装置及系统
CN120604573A (zh) * 2024-01-03 2025-09-05 北京小米移动软件有限公司 信号传输方法、终端、网络设备、通信系统和存储介质
CN120935843A (zh) * 2024-05-10 2025-11-11 大唐移动通信设备有限公司 信息发送方法、监听方法、装置、终端及网络侧设备
WO2025231839A1 (en) * 2024-05-10 2025-11-13 Apple Inc. Systems and methods for reducing misalignment between network and user equipment regarding low-power wake-up signal monitoring at the user equipment
WO2026016092A1 (en) * 2024-07-17 2026-01-22 Lenovo (Beijing) Limited Wus indication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018202693A1 (en) * 2017-05-05 2018-11-08 Sony Corporation Terminal device, infrastructure equipment, wireless telecommunications system and methods
WO2019033112A1 (en) * 2017-08-11 2019-02-14 Intel Corporation ALARM SIGNALING IN WIRELESS TELECOMMUNICATION NETWORKS
WO2019059674A1 (ko) * 2017-09-25 2019-03-28 엘지전자 주식회사 하향링크 채널 또는 하향링크 신호를 모니터링하는 방법 및 무선 기기

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101503966B1 (ko) * 2011-10-28 2015-03-25 삼성전기주식회사 Rf 다이렉트 웨이크업 기능을 갖는 무선 통신 단말기 및 그의 웨이크업 방법
WO2018169649A1 (en) * 2017-03-17 2018-09-20 Qualcomm Incorporated Techniques and apparatuses for control channel monitoring using a wakeup signal
US11297674B2 (en) * 2018-02-14 2022-04-05 Samsung Electronics Co., Ltd. Method and apparatus for power savings at a user equipment
WO2019182420A1 (ko) * 2018-03-22 2019-09-26 주식회사 윌러스표준기술연구소 가변 길이의 웨이크-업 프레임을 이용하는 무선 통신 방법 및 무선 통신 단말
WO2020029245A1 (en) * 2018-08-10 2020-02-13 Zte Corporation Power saving transmission techniques
WO2020060890A1 (en) * 2018-09-17 2020-03-26 Apple Inc. Systems, methods, and devices for signaling for power saving

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018202693A1 (en) * 2017-05-05 2018-11-08 Sony Corporation Terminal device, infrastructure equipment, wireless telecommunications system and methods
WO2019033112A1 (en) * 2017-08-11 2019-02-14 Intel Corporation ALARM SIGNALING IN WIRELESS TELECOMMUNICATION NETWORKS
WO2019059674A1 (ko) * 2017-09-25 2019-03-28 엘지전자 주식회사 하향링크 채널 또는 하향링크 신호를 모니터링하는 방법 및 무선 기기

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3996427A4 *
SHARP: "Consideration on UE-group wake-up signal for Rel-16 NB-IoT", 3GPP TSG RAN WG1 MEETING #97 R1-1907207, 17 May 2019 (2019-05-17), XP051709233, DOI: 20200930100742 *
SONY: "UE-Group Wake-Up Signal for NB-IoT", 3GPP TSG RAN WG1 MEETING #97 R1-1907192, 17 May 2019 (2019-05-17), XP051709218 *

Also Published As

Publication number Publication date
US20220141771A1 (en) 2022-05-05
EP3996427A1 (en) 2022-05-11
US12108332B2 (en) 2024-10-01
EP3996427A4 (en) 2022-12-07
EP3996427B1 (en) 2023-12-20
CN112243287B (zh) 2023-11-17
CN112243287A (zh) 2021-01-19

Similar Documents

Publication Publication Date Title
WO2021013104A1 (zh) 一种唤醒信号wus检测方法及装置
WO2021204215A1 (zh) 一种drx控制方法及装置
US12089158B2 (en) Method and apparatus for sending indication information
WO2020125433A1 (zh) 一种通信方法及装置
CN114928875B (zh) 监测信号的方法和装置
CN111934830B (zh) 一种通信方法及设备
US12035237B2 (en) Method for detecting control channel and terminal device
CN115515163A (zh) 监听物理下行控制信道的方法和通信装置
CN116391404A (zh) 一种通信方法及装置
WO2020143747A1 (zh) 通信方法和装置
WO2021204214A1 (zh) 一种检测方法及装置
WO2020143727A1 (zh) 一种通信方法及装置
WO2020063782A1 (zh) 一种通信方法及装置
WO2020164143A1 (zh) 非连续接收的方法、终端设备和网络设备
WO2023098566A1 (zh) 一种通信方法及装置
WO2021097648A1 (zh) 检测物理下行控制信道pdcch的方法以及装置
US20250220522A1 (en) Uplink transmission method and communication apparatus
WO2023030037A1 (zh) 信息监听的方法和装置
US20240357501A1 (en) Wireless communication method, terminal device, and network device
CN114846855B (zh) 通信方法、设备和计算机可读介质
CN111436101A (zh) 一种通信方法及装置
US20240323974A1 (en) Transmission indication method and communication apparatus
WO2022151418A1 (zh) 一种通信方法及装置
CN114640413A (zh) 一种信道监听方法及装置
WO2022151405A1 (zh) 通信方法和装置

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: 20844418

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020844418

Country of ref document: EP

Effective date: 20220207