WO2020147686A1 - 唤醒信号的发送和接收方法及装置、电子装置 - Google Patents

唤醒信号的发送和接收方法及装置、电子装置 Download PDF

Info

Publication number
WO2020147686A1
WO2020147686A1 PCT/CN2020/071802 CN2020071802W WO2020147686A1 WO 2020147686 A1 WO2020147686 A1 WO 2020147686A1 CN 2020071802 W CN2020071802 W CN 2020071802W WO 2020147686 A1 WO2020147686 A1 WO 2020147686A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
service type
service
wus
communication node
Prior art date
Application number
PCT/CN2020/071802
Other languages
English (en)
French (fr)
Inventor
刘旭
戴博
沙秀斌
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20741486.3A priority Critical patent/EP3913989A4/en
Priority to KR1020217025997A priority patent/KR20210116566A/ko
Priority to AU2020208515A priority patent/AU2020208515A1/en
Priority to US17/424,035 priority patent/US20220104125A1/en
Priority to CA3127114A priority patent/CA3127114A1/en
Publication of WO2020147686A1 publication Critical patent/WO2020147686A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power 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/028—Power 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE 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/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communications, for example, to a method and device for sending and receiving a wake-up signal, and an electronic device.
  • WUS Wake Up Signal
  • DRX_gap Discontinuous Reception_gap
  • short_extended-DRX_gap short_eDRX_gap
  • long_extended discontinuous reception_gap There are three types of (long_eDRX_gap).
  • the so-called gap is the interval between the starting position of monitoring WUS and the paging occasion (Paging Occasion, PO). Therefore, after the base station receives the paging message issued by the core network, if the terminal supports WUS, it will group according to all the gap types before the PO. If all terminals of the same gap type are not paging, then the base station WUS will not be sent at the WUS position corresponding to the gap type; if at least one of all terminals of the same gap type has a page, then a page will be sent.
  • the terminal configures the relevant parameters of WUS according to the received System Information Block (SIB) message, such as the gap value (time offset) between WUS and current PO, and the duration of WUS (duration) ,
  • SIB System Information Block
  • the terminal can determine the starting position of WUS detection by reading the WUS configuration in the SIB message.
  • the embodiment of the present invention provides a method and device for sending and receiving a wake-up signal, and an electronic device, so as to at least solve the problem of false wake-up after sending the wake-up signal WUS in the related art.
  • a method for sending a wake-up signal which includes: a communication node negotiates a service type of the terminal with a terminal; and the communication node sends a wake-up signal WUS according to the service type.
  • a method for receiving a wake-up signal including: a terminal and a communication node negotiate a service type of the terminal; and the terminal receives a wake-up sent by the communication node according to the service type Signal WUS.
  • a device for sending a wake-up signal which is applied to a communication node side, and includes: a first negotiation module for negotiating with the terminal for the service type of the terminal; and a sending module for The wake-up signal WUS is sent according to the service type.
  • a device for receiving a wake-up signal which is applied to the terminal side, and includes: a second negotiation module for negotiating with a communication node to determine the service type of the terminal; and a receiving module for Receiving a wake-up signal WUS sent by the communication node according to the service type.
  • an electronic device including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to perform the sending of the above wake-up signal method.
  • an electronic device including a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to perform the above-mentioned receiving of the wake-up signal method.
  • the communication node sends WUS according to the service type of the terminal negotiated with the terminal, thereby preventing terminals of different service types from being awakened, and solving the problem of false wake-up after sending the wake-up signal WUS in the related technology, and improves The accuracy of waking up the terminal.
  • Fig. 1 is a flowchart of a method for sending a wake-up signal according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for receiving a wake-up model according to an embodiment of the present invention
  • Fig. 3 is a first flow chart of negotiating service types between a terminal and a communication node according to an embodiment of the present invention
  • Fig. 4 is a second flowchart of the service type negotiation between a terminal and a communication node according to an embodiment of the present invention
  • Fig. 5 is a first flow chart of a method for a base station to obtain all service types in a cell from a network side according to an optional embodiment of the present invention
  • FIG. 6 is a second flowchart of a method for a base station to obtain all service types in a cell from the network side according to an optional embodiment of the present invention
  • Fig. 7 is a third flowchart of a method for a base station to acquire all service types in a cell from the network side according to an optional embodiment of the present invention
  • Fig. 8 is a flowchart of a method for a base station to determine a service type to which a UE belongs according to WUS grouping according to an optional embodiment of the present invention
  • Fig. 9 is a schematic structural diagram of a device for sending a wake-up signal according to an embodiment of the present invention.
  • Fig. 10 is a schematic structural diagram of an apparatus for receiving a wake-up signal according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for sending a wake-up signal according to an embodiment of the present invention. As shown in FIG. 1, the flow includes the following steps:
  • Step S102 The communication node negotiates with the terminal the service type of the terminal.
  • Step S104 the communication node sends a wake-up signal WUS according to the service type.
  • the communication node sends WUS according to the service type of the terminal negotiated with the terminal, thereby avoiding terminals of different service types from being awakened, and solving the problem of false wake-up after sending the wake-up signal WUS in related technologies , Improve the accuracy of waking up the terminal.
  • MME Mobility Management Entity
  • the communication node and the terminal involved in step S102 in this embodiment negotiate the service type of the terminal, including:
  • the mobility management entity MME receives the first request message sent by the terminal; in response to the first request message, the MME sends a response message carrying a service type identifier for indicating the service type to the terminal.
  • Manner 2 The MME receives the second request message sent by the terminal; where the second request message carries a service type identifier for indicating the service type; the MME sends a response message carrying the service type identifier confirmation to the terminal in response to the second request message.
  • the negotiation process between the communication node and the terminal involved in this embodiment can be the MME and the terminal negotiation, and the negotiation method can be that the terminal informs the MME of its service type, or it can be the MME Inform the terminal of its own service type.
  • this embodiment also involves a method of determining the type of service.
  • the method in this embodiment may further include:
  • Step S100 The base station obtains all sub-service type identifiers in the covered cell to obtain the sub-service type.
  • Step S101 The base station groups the sub-service types according to the service types to obtain a grouping relationship; where the grouping relationship is used to indicate that one service type corresponds to one or more sub-service types.
  • step 100 and step S101 in a specific application scenario, it may be:
  • the base station determines the specific service division according to all the sub-service types within the cell range; for example, the total sub-service types in the cell range include: service_identifier (service_identifier, service_id) a1, service_id a2, service_id a3, service_id a4, service_id a5
  • the possible service group divisions of the base station are, for example, service_id 1: service_id a1, service_id a2; service_id 2: service_id a3, service_id a4, service_id a5; where service_id 1 corresponds to the service type involved in this embodiment, which is the above In method 1 and method 2, the service type negotiated by the MME and the terminal; and service_id a1, service_id a2, service_id a3, service_id a4, service_id a5 are the sub-service types.
  • the base station broadcasts this division method to the terminal through the SIB message.
  • the communication node and the terminal involved in this embodiment negotiate the service type of the terminal including:
  • step S102-11 the MME negotiates with the terminal to determine the sub-service type of the terminal.
  • Step S102-12 The MME sends a system information block SIB message to the terminal, where the SIB message carries a grouping relationship.
  • Another way to determine the service type in this embodiment is that after the base station determines the grouping relationship, the terminal determines the service type according to the grouping relationship.
  • the manner in which the communication node involved in this embodiment sends the wake-up signal WUS according to the service type may include:
  • step S104-11 the base station determines the WUS grouping according to the service type.
  • Step S104-12 the base station sends WUS according to the WUS packet.
  • the group of WUS needs to be determined first, and then WUS can be sent accurately.
  • the method of this embodiment further includes: the base station sends a paging message to the terminal according to the service type.
  • the configuration of the paging message parameters can be: independently configure the paging parameters for each service type, including: nB, the number of paging carriers, the gap between the WUS signal and paging transmission; or: Part parameters of each business are configured independently, and some parameters are shared by all business types, such as independent configuration of gap and sharing of nB.
  • the cell configuration of paging parameters configured according to each service type :
  • service types can be divided in at least one of the following ways: according to service cycles, according to quality of service (Quality of Service, QoS), and according to service attributes defined by the core network.
  • QoS Quality of Service
  • service attributes defined by the core network.
  • the business types that can be obtained according to the business cycle division include: long-cycle business, short-cycle business, and general-cycle business.
  • FIG. 2 is a flowchart of a method for receiving a wake-up model according to an embodiment of the present invention. As shown in FIG. 2, the steps of the method include:
  • Step S202 The terminal negotiates the service type of the terminal with the communication node.
  • Step S204 The terminal receives the wake-up signal WUS sent by the communication node according to the service type.
  • the manner in which the terminal and the communication node involved in step S202 negotiate the service type of the terminal may be:
  • Manner 1 The terminal sends a first request message to the mobility management entity MME; the terminal receives a response message sent by the MME in response to the first request message to the terminal and carries a service type identifier for indicating the service type.
  • Manner 2 The terminal sends a second request message to the MME; where the second request message carries a service type identifier for indicating the service type; the terminal receives a response message that is sent by the MME in response to the second request message and carries the service type identifier confirmation.
  • this embodiment also relates to a method for the terminal and the communication node to negotiate the service type of the terminal.
  • the method includes: the terminal receives the SIB message sent by the MME, where the SIB message carries Information indicating the grouping relationship; wherein the grouping relationship is determined by the base station to indicate that a service type corresponds to one or more sub-service types; the terminal determines the service type of the terminal according to the grouping relationship and the terminal's sub-service type.
  • another way of determining the service type in this embodiment is that after the base station determines the grouping relationship, the terminal determines the service type according to the grouping relationship.
  • step S204 of this embodiment receives the wake-up signal WUS sent by the communication node according to the service type
  • the terminal receives the WUS sent by the base station according to the WUS packet.
  • the method of this embodiment further includes: the terminal receives a paging message sent by the base station according to the service type.
  • the service types involved in this embodiment are divided in at least one of the following ways: according to the service cycle, according to the quality of service QoS, and according to the service attributes defined by the core network.
  • Embodiments 1 and 2 of the present application will be exemplified below in conjunction with optional implementation manners;
  • FIG. 3 is a flow chart of a terminal and a communication node negotiating a service type according to an embodiment of the present invention.
  • the terminal and the network side There must be a clear and consistent service type, so it is necessary for the terminal and the communication node (such as MME) to negotiate to determine its service type; the terminal is updated in the attach process or tracking area (TAU) and MME through non-access Layer (Non-Access Stratum, NAS) signaling negotiates to determine the service type.
  • TAU attach process or tracking area
  • NAS non-access Layer
  • the service type can be divided according to the service cycle (service_id 1: long-cycle service, service_id 2: general cycle service, service_id 3: short-cycle service), or it can be divided in other ways, and the terminal and MME directly negotiate and determine the final use
  • service_id 1 long-cycle service
  • service_id 2 general cycle service
  • service_id 3 short-cycle service
  • the terminal and MME directly negotiate and determine the final use
  • the service type service_id 1 is determined through negotiation, the UE can use the service type to directly determine the reception of packet WUS; it is also possible that the terminal and the MME only negotiate to determine a sub-service type, and the base station is required to indicate the service type.
  • Which service type is used for the WUS packet (specifically described in optional embodiment 3).
  • FIG. 4 is the second flowchart of the service type negotiation between the terminal and the communication node according to the embodiment of the present invention.
  • the terminal and the communication node such as MME
  • the terminal and the communication node need to negotiate to determine its service type; the terminal will negotiate with the MME through NAS signaling during the attach process or the tracking area update (TAU) Determine the type of business.
  • TAU tracking area update
  • the service type can be divided according to the service cycle (service_id 1: long-cycle service, service_id 2: general cycle service, service_id 3: short-cycle service), or determined by other methods.
  • the terminal and MME directly negotiate to determine the final one to be used.
  • Service type if service_id 1 is determined through negotiation, then the UE can use this service type to directly determine the reception of packet WUS; it is also possible that the terminal and MME only negotiate an intermediate service type, and finally the base station is required to indicate which service type belongs to The service type used for the WUS packet (specifically described in optional embodiment 3).
  • the base station needs to indicate the final service division method.
  • the base station needs to know all the service types of the terminals in its cell area, and then divide the final service types according to these service types; in this process, the base station first needs to learn all the service types in its cell area from the network side; the specific process As shown in Figure 5, Figure 6 and Figure 7.
  • the base station determines the specific service division according to all service types within the cell range; for example, the total service type numbers in the cell range are: service_id a1, service_id a2, service_id a3, service_id a4, service_id a5; then the possible service group divisions of the base station For example, (service_id 1: service_id a1, service_id a2), (service_id 2: service_id a3, service_id a4, service_id a5); and the base station broadcasts this division method to the terminal through SIB messages.
  • the UE finally determines the service type number used for WUS grouping through the grouping method of the service in the received broadcast message, and according to the service number determined by itself and the MME through negotiation.
  • the base station will configure the starting position information and/or the corresponding duration information of each group of wus signals based on the service grouping.
  • the paging message sent from the MME to the evolved NodeB (eNB) needs to include the service ID information of the UE; the base station directly determines the service type used for WUS packet or the service broadcasted according to the service ID information of the UE The type division method finally determines the service type used for WUS grouping; then the base station determines the WUS group id to which the UE belongs according to the service-based WUS grouping method, and the process is shown in Figure 8.
  • the base station obtains the service ID information of the UE from the paging message sent by the MME, and the base station directly determines the service type used for WUS packet or according to the service broadcasted by the service ID information of the UE.
  • the type division method finally determines the service type used for WUS grouping; then the base station determines the WUS group to which the UE belongs according to the service-based WUS grouping method. As long as there is one UE in the WUS group that needs to be paged, the base station will send the WUS signal at the location of the corresponding WUS group.
  • the service type used for WUS grouping is directly determined according to its own service ID information or the service type used for WUS grouping is finally determined according to its broadcast service type division method, and then the service type used for WUS grouping The corresponding WUS group position monitors and receives WUS signals.
  • the base station needs to configure the WUS starting position information and/or WUS duration configuration information of each service type based on the service group; then configure the starting position information and WUS duration information of each group based on the UE-ID grouping under each service type Configuration information.
  • the UE can obtain the starting position information of the WUS of the first layer according to its own service type; and then obtain the accurate WUS position information and/or WUS duration information of the second layer according to the UE-ID-based grouping method.
  • the base station needs to configure the starting position information of each group grouped based on UE-ID and/or WUS duration configuration information, and each service type corresponds to the starting position information and/or WUS duration configuration information of each service grouping .
  • the UE obtains the first layer grouping according to the UE-ID grouping method, and then according to the service type and corresponding configuration information; it can determine the WUS location information and/or WUS duration information related to it
  • a device for sending and receiving a wake-up signal is also provided.
  • the device is used to implement the above-mentioned embodiments and preferred implementations, and what has been described will not be repeated.
  • the term "module” may implement a combination of software and/or hardware that performs predetermined functions.
  • the devices described in the following embodiments are preferably implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 9 is a schematic structural diagram of a device for sending a wake-up signal according to an embodiment of the present invention.
  • the device is applied to the side of a communication node.
  • the device includes: a first negotiation module 92 for negotiating with the terminal.
  • the service type of the terminal; the sending module 94 is coupled to the first negotiation module 92 and is configured to send a wake-up signal WUS according to the service type.
  • the first negotiation module includes: a first receiving unit, configured to receive a first request message sent by the terminal; and a first sending unit, configured to respond to the first request The message sends a response message carrying a service type identifier used to indicate the service type to the terminal.
  • the first negotiation module includes: a second receiving unit for receiving a second request message sent by the terminal; wherein the second request message carries a service type identifier for indicating the service type; and the second sending unit for responding Sending a response message carrying a service type identification confirmation to the terminal in the second request message.
  • the communication node involved in this embodiment may also be a base station. Therefore, before the MME and the terminal negotiate the service type of the terminal, the device further includes: an acquisition module for acquiring all the information in the covered cell
  • the sub-service type identification obtains the sub-service type; the processing module is used to group the sub-service types according to the service type to obtain the grouping relationship; wherein, the grouping relationship is used to indicate that one service type corresponds to one or more sub-service types.
  • the first negotiation module further includes: a negotiation unit for negotiating with the terminal for the sub-service type of the terminal; and a third sending unit for sending a system information block SIB message to the terminal, where the SIB message carries Information indicating the grouping relationship.
  • FIG. 10 is a wake-up signal receiving device according to an embodiment of the present invention.
  • the second negotiation module includes: a fourth sending unit, configured to send a first request message to the mobility management entity MME; and a third receiving unit, configured to receive the carrying useful information sent by the MME to the terminal in response to the first request message.
  • the response message indicating the service type identifier of the service type.
  • the second negotiation module includes: a fifth sending unit, configured to send a second request message to the MME; wherein, the second request message carries a service type identifier for indicating a service type; and a fourth receiving unit is configured to The response message carrying the service type identification confirmation sent by the receiving MME in response to the second request message.
  • the second negotiation module includes: a second negotiation unit, configured to negotiate with the MME to determine the sub-service type of the terminal; and a fifth receiving unit, configured to receive the SIB message sent by the MME, wherein the SIB message carries an indication packet Relationship information; wherein the grouping relationship is determined by the base station to indicate that a service type corresponds to one or more sub-service types; the determining unit is used to determine the service type of the terminal according to the grouping relationship and the terminal's sub-service type.
  • the above modules can be implemented by software or hardware, and the latter can be implemented by the following methods, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • An embodiment of the present application further provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the steps in the above method embodiments.
  • the electronic device may further include a transmission device and an input-output device, where the transmission device is connected to the processor, and the input-output device is connected to the processor.
  • the foregoing processor may be configured to perform the following steps through a computer program:
  • S2 Send a wake-up signal WUS according to the service type.
  • the foregoing processor may be configured to execute the following steps through a computer program:
  • S2 Receive the wake-up signal WUS sent by the communication node according to the service type.
  • modules or steps of the present application can be implemented by a general-purpose computing device, and they can be concentrated on a single computing device or distributed on a network composed of multiple computing devices, Alternatively, they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, the programs can be executed in an order different from here
  • the steps shown or described are realized by making them into individual integrated circuit modules, or by making multiple modules or steps among them into a single integrated circuit module. In this way, the book is not limited to any specific combination of hardware and software.

Abstract

本文公开了一种唤醒信号的发送和接收方法及装置、电子装置，其中，该发送方法包括：通信节点与终端协商出所述终端的业务类型；所述通信节点根据所述业务类型发送唤醒信号WUS。

Description

唤醒信号的发送和接收方法及装置、电子装置
本申请要求在2019年01月18日提交中国专利局、申请号为201910108919.5的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如，涉及一种唤醒信号的发送和接收方法及装置、电子装置。
背景技术
在发布(Release)15阶段，引入唤醒信号(Wake Up Signal，WUS)，对于具有相同寻呼时机的终端，如果有终端需要被寻呼，那么基站将在寻呼时机前发送WUS，这些终端都将检测WUS，终端在检测到WUS后，进一步去监听寻呼消息。由于终端配置的WUS的间隔(gap)类型有三类：非连续接收_间隔(Discontinuous Reception_gap，DRX_gap)，短_扩展非连续接收_间隔(short_extended-DRX_gap，short_eDRX_gap)，长_扩展非连续接收_间隔(long_eDRX_gap)三种类型，所谓的gap即为开始监听WUS的起始位置与寻呼时机(Paging Occasion，PO)之间的间隔。因此，基站在接收到核心网下发的寻呼消息后，如果终端支持WUS，那么将根据该PO前的所有的gap类型进行分组，如果同一gap类型的所有终端，都没有寻呼，那么基站将在该gap类型对应的WUS位置不发送WUS；如果同一gap类型的所有终端中至少一个终端有寻呼，将发送寻呼。
终端根据接收到的系统信息块(System Information Block，SIB)消息里关于配置WUS的相关参数，如WUS与当前PO的间隔gap值(时间偏移(time offset))、WUS的持续时长(duration)，终端通过读取SIB消息中关于WUS的配置，即可确定WUS检测的起始位置。
但是具有相同gap类型的一组用户设备(User Equipment，UE)，在数量较多，且只有较少的UE需要被寻呼的情况下，由于需要发送WUS，对于该相同gap类型下的其他UE来说将会造成误唤醒，从而给这些终端带来额外的功耗。
发明内容
本发明实施例提供了一种唤醒信号的发送和接收方法及装置、电子装置，以至少解决相关技术中在发送唤醒信号WUS后导致误唤醒的问题。
根据本申请的一个实施例，提供了一种唤醒信号的发送方法，包括：通信节点与终端协商出所述终端的业务类型；所述通信节点根据所述业务类型发送唤醒信号WUS。
根据本申请的另一个实施例，提供了一种唤醒信号的接收方法，包括：终端与通信节点协商出所述终端的业务类型；所述终端接收所述通信节点根据所述业务类型发送的唤醒信号WUS。
根据本申请的再一个实施例，提供了一种唤醒信号的发送装置，应用于通信节点侧，包括：第一协商模块，用于与终端协商出所述终端的业务类型；发送模块，用于根据所述业务类型发送唤醒信号WUS。
根据本申请的再一个实施例，提供了一种唤醒信号的接收装置，应用于终端侧，包括：第二协商模块，用于与通信节点协商出所述终端的业务类型；接收模块，用于接收所述通信节点根据所述业务类型发送的唤醒信号WUS。
根据本申请的再一个实施例，提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述唤醒信号的发送方法。
根据本申请的再一个实施例，提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述唤醒信号的接收方法。
通过本申请，通信节点根据与终端协商出的终端的业务类型发送WUS，从而避免了不同业务类型的终端被唤醒，并解决了相关技术中在发送唤醒信号WUS后导致误唤醒的问题，提高了唤醒终端的准确率。
附图说明
图1是根据本发明实施例的唤醒信号的发送方法的流程图；
图2是根据本发明实施例的唤醒型号的接收方法的流程图；
图3是根据本发明实施例的终端与通信节点协商业务类型的流程图一；
图4是根据本发明实施例的终端与通信节点协商业务类型的流程图二；
图5是根据本发明可选实施例的基站从网络侧获取小区范围内的所有的业务类型的方法流程图一；
图6是根据本发明可选实施例的基站从网络侧获取小区范围内的所有的业务类型的方法流程图二；
图7是根据本发明可选实施例的基站从网络侧获取小区范围内的所有的业 务类型的方法流程图三；
图8是根据本发明可选实施例的基站根据WUS分组确定UE所属的业务类型的方法流程图；
图9是根据本发明实施例的唤醒信号的发送装置的结构示意图；
图10是根据本发明实施例的唤醒信号的接收装置的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本实施例中提供了一种唤醒信号的发送方法，图1是根据本发明实施例的唤醒信号的发送方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，通信节点与终端协商出终端的业务类型。
步骤S104，通信节点根据业务类型发送唤醒信号WUS。
通过上述步骤S102和步骤S104，通信节点根据与终端协商出的终端的业务类型发送WUS，从而避免了不同业务类型的终端被唤醒，解决了相关技术中在发送唤醒信号WUS后导致误唤醒的问题，提高了唤醒终端的准确率。
需要说明的是，本申请中涉及到的通信节点包括移动管理实体(Mobility Management Entity，MME)和基站。
基于此，本实施例步骤S102中涉及到的通信节点与终端协商出终端的业务类型的方式，包括：
方式1：移动管理实体MME接收终端发送的第一请求消息；MME响应于第一请求消息向终端发送携带有用于指示业务类型的业务类型标识的响应消息。
方式2：MME接收终端发送的第二请求消息；其中，第二请求消息携带有用于指示业务类型的业务类型标识；MME响应于第二请求消息向终端发送携带有业务类型标识确认的响应消息。
通过上述方式1和方式2可知，对于本实施例中涉及到的通信节点与终端协商的过程，可以是MME与终端进行协商，而且协商的方式可以是终端告知 MME其业务类型，也可以是MME告知终端其自身的业务类型。
上述是本实施例中一种确定因为类型的方式，此外，在本实施例的另一个可选实施方式中，本实施例中还涉及一种确定业务类型的方式。首先，在MME与终端协商出终端的业务类型之前，本实施例的方法还可以包括：
步骤S100，基站获取所覆盖的小区内的所有子业务类型标识得到子业务类型。
步骤S101，基站根据业务类型对子业务类型进行分组，得到分组关系；其中，分组关系用于指示一种业务类型对应于一种或多种子业务类型。
对于该步骤100和步骤S101，在具体应用场景中可以是：
基站根据小区范围内的所有的子业务类型，确定具体的业务划分；如小区范围的总的子业务类型包括：服务_标识(service_identifier，service_id)a1，service_id a2，service_id a3，service_id a4，service_id a5；那么基站可能的业务组划分如，service_id 1：service_id a1，service_id a2；service_id 2：service_id a3，service_id a4，service_id a5；其中，service_id 1对应于本实施例中涉及到的业务类型，也就是上述方式1和方式2中，MME与终端协商出的业务类型；而service_id a1，service_id a2，service_id a3，service_id a4，service_id a5就是子业务类型。最后，基站将此划分方式通过SIB消息广播给终端。
基于此，本实施例中涉及到的通信节点与终端协商出终端的业务类型的方式包括：
步骤S102-11，MME与终端协商出终端的子业务类型。
步骤S102-12，MME向所述终端发送系统信息块SIB消息，其中，SIB消息中携带有分组关系。
可见，本实施例中另一个确定业务类型的方式，是由基站确定分组关系后，再由终端根据该分组关系确定其业务类型。
在本实施例的可选实施方式中，对于本实施例中涉及到的通信节点根据业务类型发送唤醒信号WUS的方式，可以包括：
步骤S104-11，基站根据业务类型确定WUS的分组。
步骤S104-12，基站根据WUS的分组发送WUS。
也就是说，对于WUS的方式，需要首先确定WUS的分组，进而才能准确的发送WUS。
需要说明的是，在通信节点根据业务类型发送唤醒信号WUS之后，本实施例的方法还包括：基站根据业务类型向终端发送寻呼消息。
其中，对于寻呼消息参数的配置可以是：针对每个业务类型独立配置寻呼参数，包括：nB，寻呼载波数，WUS信号与寻呼(paging)发送间的间隔gap；也可以是：每个业务部分参数独立配置，部分参数所有业务类型共享，如独立配gap，共享nB。
如按照各个业务类型配置的寻呼参数的信元配置：
Figure PCTCN2020071802-appb-000001
在本实施例中，业务类型可以通过以下至少之一的方式进行划分：根据业务周期进行划分、根据服务质量(Quality of Service，QoS)进行划分、根据核心网定义的业务属性进行划分。
例如，根据业务周期划分可以得到的业务类型包括：长周期业务、短周期业务、一般周期业务。
实施例2
上述实施例1是从通信节点侧进行描述的，而本实施例是从终端侧进行描 述的，两者是对应的。因此，本实施例也提供一种唤醒信号的接收方法，图2是根据本发明实施例的唤醒型号的接收方法的流程图，如图2所示，该方法的步骤包括：
步骤S202，终端与通信节点协商出终端的业务类型。
步骤S204，终端接收通信节点根据业务类型发送的唤醒信号WUS。
在本实施例的可选实施方式中，上述步骤S202中涉及到的终端与通信节点协商出终端的业务类型的方式可以是：
方式1：终端向移动管理实体MME发送第一请求消息；终端接收MME响应于第一请求消息向终端发送的携带有用于指示业务类型的业务类型标识的响应消息。
方式2：终端向MME发送第二请求消息；其中，第二请求消息携带有用于指示业务类型的业务类型标识；终端接收MME响应于第二请求消息发送的携带有业务类型标识确认的响应消息。
在本实施例的另一个可选实施方式中，本实施例还涉及一种终端与通信节点协商出终端的业务类型方式，该方式包括：终端接收MME发送的SIB消息，其中，SIB消息携带有指示分组关系的信息；其中，分组关系是由基站确定的用于指示一种业务类型对应于一种或多种子业务类型；终端根据分组关系和终端的子业务类型确定终端的业务类型。
也就是说，本实施例中另一个确定业务类型的方式，是由基站确定分组关系后，再由终端根据该分组关系确定其业务类型。
需要说明的是，本实施例步骤S204中涉及到的终端接收通信节点根据业务类型发送的唤醒信号WUS的方式可以是：终端接收基站根据WUS的分组发送的WUS。
此外，本实施例中在终端接收通信节点根据业务类型发送的唤醒信号WUS之后，本实施例的方法还包括：终端接收基站根据业务类型发送的寻呼消息。
需要说明的是，本实施例中涉及到的业务类型通过以下至少之一的方式进行划分：根据业务周期进行划分、根据服务质量QoS进行划分、根据核心网定义的业务属性进行划分。
下面结合可选实施方式对本申请的上述实施例1和2进行举例说明；
可选实施方式1：
在本可选实施方式1中，图3是根据本发明实施例的终端与通信节点协商业务类型的流程图一，如图3所示，对于支持基于业务类型的WUS分组，首先 终端和网络侧要有明确一致的业务类型，因此需要终端和通信节点(如MME)进行协商确定其业务类型；终端在附着(attach)过程或跟踪区(Tracing Area Update，TAU)更新的和MME通过非接入层面(Non-Access Stratum，NAS)信令进行协商确定业务类型。
其中，业务类型可以按照业务的周期划分(service_id 1：长周期业务，service_id 2：一般周期业务，service_id 3：短周期业务)，也可以按照其他方式进行划分，由终端和MME直接协商确定最终使用的一个业务类型，如协商确定业务类型service_id 1，那么以后UE可使用该业务类型直接确定分组WUS的接收；也可以终端和MME仅协商确定一个子业务类型，最终还需要基站来指示该业务类型属于哪一个用于WUS分组的业务类型(具体在可选实施方式3中说明)。
可选实施方式2：
在本可选实施方式2中，图4是根据本发明实施例的终端与通信节点协商业务类型的流程图二，如图4所示，对于支持基于业务类型的WUS分组，首先终端和网络侧要有明确一致的业务类型，因此需要终端和通信节点(如MME)进行协商确定其业务类型；终端在附着attach过程或跟踪区(Tracing Area Update，TAU)更新的和MME通过NAS信令进行协商确定业务类型。
业务类型可以包括按照业务的周期划分(service_id 1：长周期业务，service_id 2：一般周期业务，service_id 3：短周期业务)，或者由其他方式来确定，由终端和MME直接协商确定最终使用的一个业务类型，如协商确定service_id 1，那么以后UE可使用该业务类型直接确定分组WUS的接收；也可以终端和MME仅协商确定一个中间的业务类型，最终还需要基站来指示该业务类型属于哪一个用于WUS分组的业务类型(具体在可选实施方式3中说明)。
可选实施方式3
基于上述可选实施方式1和2中的方式，如果终端和MME仅协商确定一个用业务分组的子业务类型标识，那么需要基站指示最终的业务划分方法。基站需要知道其小区范围终端的所有的业务类型，然后根据这些业务类型再划分最终的业务类型；在这个过程中，首先基站需要从网络侧获知其小区范围内的所有的业务类型；具体的流程如图5，图6和图7所示。
基站根据小区范围内的所有的业务类型，确定具体的业务划分；如小区范围的总的业务类型号有：service_id a1，service_id a2，service_id a3，service_id a4，service_id a5；那么基站可能的业务组划分如，(service_id 1：service_id a1，service_id a2)，(service_id 2：service_id a3，service_id a4，service_id a5)； 并且基站将此划分方法通过SIB消息广播给终端。UE通过接收到的广播消息中关于业务的分组方法，并根据自身也MME协商确定的业务号，最终确定用于WUS分组的业务类型号。
另外，基站将配置基于业务分组的各组wus信号的起始位置信息和/或相应的持续时长duration信息。
可选实施方式4
从MME发给演进型基站(evolved NodeB，eNB)的寻呼消息里，需要包含UE的service ID信息；基站根据UE的service ID信息，直接确定用于WUS分组的业务类型或者根据其广播的业务类型划分方法最终确定用于WUS分组的业务类型；然后基站根据基于业务的WUS分组方法，确定UE所属的WUS组(group)id，其流程如图8所示。
可选实施方式5
如可选实施方式4所述，基站从MME发送过来的寻呼消息里，获得UE的service ID信息，基站根据UE的service ID信息，直接确定用于WUS分组的业务类型或者根据其广播的业务类型划分方法最终确定用于WUS分组的业务类型；然后基站根据基于业务的WUS分组方法，确定UE所属的WUS组。只要该WUS组有一个UE需要被寻呼，那么基站将在对应WUS组的位置发送WUS信号。对于UE来说，在每个PO前，先根据自己的service ID信息直接确定用于WUS分组的业务类型或者根据其广播的业务类型划分方法最终确定用于WUS分组的业务类型，然后在与之相对应的WUS组位置监听和接收WUS信号。
可选实施方式6
基站需要配置基于业务分组的每个业务类型的WUS起始位置信息和/或WUS duration的配置信息；再配置各个业务类型下各个基于UE-ID分组的各个组的起始位置信息及WUS duration的配置信息。
UE根据自己的业务类型即可获得第一层WUS的起始位置信息；然后根据基于UE-ID分组方法获得第二层准确地WUS位置信息和/或WUS duration信息。
可选实施方式7
基站需要配置基于UE-ID分组的各个组的起始位置信息和/或WUS duration的配置信息，每个业务类型对应的相对于各个基于业务分组的起始位置信息和/或WUS duration的配置信息。
UE根据基于UE-ID分组方法得到第一层分组，然后根据业务类型及对应的配置信息；即可确定与之相关的WUS位置信息和/或WUS duration信息
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)/随机存取存储器(Random Access Memory，RAM)、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
实施例3
在本实施例中还提供了一种唤醒信号的发送和接收装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图9是根据本发明实施例的唤醒信号的发送装置的结构示意图，该装置应用于通信节点侧，如图9所示，该装置包括：第一协商模块92，用于与终端协商出所述终端的业务类型；发送模块94，与第一协商模块92耦合连接，用于根据所述业务类型发送唤醒信号WUS。
可选地，该在该通信节点为MME的情况下，该第一协商模块包括：第一接收单元，用于接收终端发送的第一请求消息；第一发送单元，用于响应于第一请求消息向终端发送携带有用于指示业务类型的业务类型标识的响应消息。
或者，该第一协商模块包括：第二接收单元，用于接收终端发送的第二请求消息；其中，第二请求消息携带有用于指示业务类型的业务类型标识；第二发送单元，用于响应于第二请求消息向终端发送携带有业务类型标识确认的响应消息。
需要说明的是本实施例中涉及到的通信节点还可以是基站，因此，在MME与终端协商出终端的业务类型之前，该装置还包括：获取模块，用于获取所覆盖的小区内的所有子业务类型标识得到子业务类型；处理模块，用于根据业务类型对子业务类型进行分组，得到分组关系；其中，分组关系用于指示一种业务类型对应于一种或多种子业务类型。
可选地，该第一协商模块还包括：协商单元，用于与终端协商出终端的子业务类型；第三发送单元，用于向终端发送系统信息块SIB消息，其中，SIB消息中携带有指示分组关系的信息。
需要说明的是，上述均是从通信节点侧对本案进行介绍的，而对于终端侧，本实施例还提供了一种唤醒信号的接收装置，图10是根据本发明实施例的唤醒信号的接收装置的结构示意图，该装置应用于终端侧，如图10所示，该装置包括：第二协商模块1002，用于与通信节点协商出所述终端的业务类型；接收模块1004，与第二协商模块1002耦合连接，用于接收所述通信节点根据所述业务类型发送的唤醒信号WUS。
可选地，该第二协商模块包括：第四发送单元，用于向移动管理实体MME发送第一请求消息；第三接收单元，用于接收MME响应于第一请求消息向终端发送的携带有用于指示业务类型的业务类型标识的响应消息。
可选地，该第二协商模块包括：第五发送单元，用于向MME发送第二请求消息；其中，第二请求消息携带有用于指示业务类型的业务类型标识；第四接收单元，用于接收MME响应于第二请求消息发送的携带有业务类型标识确认的响应消息。
可选地，该第二协商模块包括：第二协商单元，用于与MME协商出终端的子业务类型；第五接收单元，用于接收MME发送的SIB消息，其中，SIB消息携带有指示分组关系的信息；其中，分组关系是由基站确定的用于指示一种业务类型对应于一种或多种子业务类型；确定单元，用于根据分组关系和终端的子业务类型确定终端的业务类型。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例4
本申请的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，与终端协商出终端的业务类型。
S2，根据业务类型发送唤醒信号WUS。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以 下步骤：
S1，与通信节点协商出终端的业务类型。
S2，接收通信节点根据业务类型发送的唤醒信号WUS。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本不限制于任何特定的硬件和软件结合。

Claims (19)

  1. 一种唤醒信号的发送方法，包括：
    通信节点与终端协商出所述终端的业务类型；
    所述通信节点根据所述业务类型发送唤醒信号WUS。
  2. 根据权利要求1所述的方法，其中，所述通信节点与终端协商出所述终端的业务类型，包括：
    移动管理实体MME接收所述终端发送的第一请求消息；
    所述MME响应于所述第一请求消息向所述终端发送携带有用于指示业务类型的业务类型标识的响应消息。
  3. 根据权利要求1所述的方法，其中，所述通信节点与终端协商出所述终端的业务类型，包括：
    MME接收所述终端发送的第二请求消息；其中，所述第二请求消息携带有用于指示业务类型的业务类型标识；
    所述MME响应于所述第二请求消息向所述终端发送携带有业务类型标识确认的响应消息。
  4. 根据权利要求1所述的方法，在所述通信节点与终端协商出所述终端的业务类型之前，还包括：
    基站获取所覆盖的小区内的所有子业务类型标识，根据所述所有子业务类型标识得到所述所覆盖的小区内的子业务类型；
    所述基站根据业务类型对所述子业务类型进行分组，得到分组关系；其中，所述分组关系用于指示一种业务类型对应于一种或多种子业务类型。
  5. 根据权利要求4所述的方法，其中，所述通信节点与终端协商出所述终端的业务类型，包括：
    MME与所述终端协商出所述终端的子业务类型；
    所述MME向所述终端发送系统信息块SIB消息，其中，所述SIB消息中携带有指示所述分组关系的信息。
  6. 根据权利要求1至3任一项所述的方法，其中，所述通信节点根据所述业务类型发送WUS，包括：
    基站根据所述业务类型确定WUS的分组；
    所述基站根据所述WUS的分组发送所述WUS。
  7. 根据权利要求6所述的方法，在所述通信节点根据所述业务类型发送 WUS之后，还包括：
    所述基站根据所述业务类型向所述终端发送寻呼消息。
  8. 根据权利要求1至3任一项所述的方法，其中，所述业务类型通过以下至少之一的方式进行划分：
    根据业务周期进行划分、根据服务质量QoS进行划分、根据核心网定义的业务属性进行划分。
  9. 一种唤醒信号的接收方法，包括：
    终端与通信节点协商出所述终端的业务类型；
    所述终端接收所述通信节点根据所述业务类型发送的唤醒信号WUS。
  10. 根据权利要求9所述的方法，其中，所述终端与通信节点协商出所述终端的业务类型，包括：
    所述终端向移动管理实体MME发送第一请求消息；
    所述终端接收所述MME响应于所述第一请求消息向所述终端发送的携带有用于指示业务类型的业务类型标识的响应消息。
  11. 根据权利要求9所述的方法，其中，所述终端与通信节点协商出所述终端的业务类型，包括：
    所述终端向MME发送第二请求消息；其中，所述第二请求消息携带有用于指示业务类型的业务类型标识；
    所述终端接收所述MME响应于所述第二请求消息发送的携带有业务类型标识确认的响应消息。
  12. 根据权利要求9所述的方法，其中，所述终端与通信节点协商出所述终端的业务类型，包括：
    所述终端与MME协商出所述终端的子业务类型；
    所述终端接收所述MME发送的系统信息块SIB消息，其中，所述SIB消息携带有指示分组关系的信息，所述分组关系是由基站确定的用于指示一种业务类型对应于一种或多种子业务类型；
    所述终端根据所述分组关系和所述终端的子业务类型确定所述终端的业务类型。
  13. 根据权利要求9至12任一项所述的方法，其中，所述终端接收所述通信节点根据所述业务类型发送的WUS，包括：
    所述终端接收基站根据WUS的分组发送的所述WUS。
  14. 根据权利要求9至12任一项所述的方法，在所述终端接收所述通信节点根据所述业务类型发送的WUS之后，还包括：
    所述终端接收基站根据所述业务类型发送的寻呼消息。
  15. 根据权利要求9至12任一项所述的方法，其中，所述业务类型通过以下至少之一的方式进行划分：
    根据业务周期进行划分、根据服务质量QoS进行划分、根据核心网定义的业务属性进行划分。
  16. 一种唤醒信号的发送装置，应用于通信节点侧，包括：
    第一协商模块，设置为与终端协商出所述终端的业务类型；
    发送模块，设置为根据所述业务类型发送唤醒信号WUS。
  17. 一种唤醒信号的接收装置，应用于终端侧，包括：
    第二协商模块，设置为与通信节点协商出所述终端的业务类型；
    接收模块，设置为接收所述通信节点根据所述业务类型发送的唤醒信号WUS。
  18. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至8任一项中所述的唤醒信号的发送方法。
  19. 一种电子装置，包括存储器和处理器，其特征在于，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求9至15任一项中所述的唤醒信号的接收方法。
PCT/CN2020/071802 2019-01-18 2020-01-13 唤醒信号的发送和接收方法及装置、电子装置 WO2020147686A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP20741486.3A EP3913989A4 (en) 2019-01-18 2020-01-13 METHOD AND DEVICE FOR TRANSMITTING AND RECEIVING WAKE-UP SIGNALS AND ELECTRONIC DEVICE
KR1020217025997A KR20210116566A (ko) 2019-01-18 2020-01-13 웨이크업 신호의 송신과 수신 방법 및 장치, 전자 장치
AU2020208515A AU2020208515A1 (en) 2019-01-18 2020-01-13 Method and device for sending and receiving wake up signal, and electronic device
US17/424,035 US20220104125A1 (en) 2019-01-18 2020-01-13 Method and Device for Sending and Receiving Wake Up Signal, and Electronic Device
CA3127114A CA3127114A1 (en) 2019-01-18 2020-01-13 Method and device for sending and receiving wake up signal, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910108919.5 2019-01-18
CN201910108919.5A CN111465086B (zh) 2019-01-18 2019-01-18 唤醒信号的发送和接收方法及装置、电子装置

Publications (1)

Publication Number Publication Date
WO2020147686A1 true WO2020147686A1 (zh) 2020-07-23

Family

ID=71614404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071802 WO2020147686A1 (zh) 2019-01-18 2020-01-13 唤醒信号的发送和接收方法及装置、电子装置

Country Status (7)

Country Link
US (1) US20220104125A1 (zh)
EP (1) EP3913989A4 (zh)
KR (1) KR20210116566A (zh)
CN (1) CN111465086B (zh)
AU (1) AU2020208515A1 (zh)
CA (1) CA3127114A1 (zh)
WO (1) WO2020147686A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11576126B2 (en) * 2020-03-24 2023-02-07 Qualcomm Incorporated Wakeup signaling identification
CN112788592B (zh) * 2021-01-20 2022-02-01 广州技象科技有限公司 添加唤醒时间的数据发送处理方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101395846A (zh) * 2006-03-03 2009-03-25 高通股份有限公司 待机时间的改进
CN104581894A (zh) * 2013-10-11 2015-04-29 中兴通讯股份有限公司 无线电唤醒方法和无线电唤醒电路
CN106464379A (zh) * 2014-12-29 2017-02-22 华为技术有限公司 一种无源光网络中唤醒光网络单元的方法、设备和系统
US20180027495A1 (en) * 2015-07-09 2018-01-25 Verizon Patent And Licensing Inc. Wakeup system and method for devices in power saving mode
CN108738110A (zh) * 2017-04-19 2018-11-02 珠海市魅族科技有限公司 无线局域网的通信方法、通信装置和通信设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9998989B2 (en) * 2015-07-09 2018-06-12 Verizon Patent And Licensing Inc. Wakeup method for devices in power saving mode
JP6622920B2 (ja) * 2016-02-01 2019-12-18 テレフオンアクチーボラゲット エルエム エリクソン（パブル） Ｕｅ ｅｄｒｘ下での信頼性のあるページング送信の方法
EP3412113B1 (en) * 2016-02-01 2020-06-10 Telefonaktiebolaget LM Ericsson (PUBL) Methods and apparatus for cell verification under ue edrx
GB2555082A (en) * 2016-09-30 2018-04-25 Nec Corp Communications system
KR102479286B1 (ko) * 2017-05-04 2022-12-20 아이피엘에이 홀딩스 인크. 웨이크 업 신호들 동작
US10638423B2 (en) * 2017-06-09 2020-04-28 Apple Inc. Group wake-up and keep-alive indication
US11240756B2 (en) * 2017-09-28 2022-02-01 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for transmitting a power saving signal
US11706736B2 (en) * 2018-08-09 2023-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Paging occasion reallocation of incapable user equipment
CN115767695A (zh) * 2019-01-10 2023-03-07 华为技术有限公司 唤醒信号的发送方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101395846A (zh) * 2006-03-03 2009-03-25 高通股份有限公司 待机时间的改进
CN104581894A (zh) * 2013-10-11 2015-04-29 中兴通讯股份有限公司 无线电唤醒方法和无线电唤醒电路
CN106464379A (zh) * 2014-12-29 2017-02-22 华为技术有限公司 一种无源光网络中唤醒光网络单元的方法、设备和系统
US20180027495A1 (en) * 2015-07-09 2018-01-25 Verizon Patent And Licensing Inc. Wakeup system and method for devices in power saving mode
CN108738110A (zh) * 2017-04-19 2018-11-02 珠海市魅族科技有限公司 无线局域网的通信方法、通信装置和通信设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3913989A4

Also Published As

Publication number Publication date
EP3913989A1 (en) 2021-11-24
CN111465086A (zh) 2020-07-28
KR20210116566A (ko) 2021-09-27
CN111465086B (zh) 2022-11-29
EP3913989A4 (en) 2022-03-09
CA3127114A1 (en) 2020-07-23
US20220104125A1 (en) 2022-03-31
AU2020208515A1 (en) 2021-08-12

Similar Documents

Publication Publication Date Title
US11463978B2 (en) Network data analytics function, access and mobility function, and control method for UE analytics assistance for network automation and optimisation
US10912058B2 (en) Discontinuous reception communication synchronization method and apparatus
CN104012155B (zh) 寻呼ue的方法、基站及ue
US10798679B2 (en) Paging method, paging monitoring method, device and apparatus, and storage medium
WO2021008381A1 (zh) 一种通信方法及装置
JP6027548B2 (ja) 無線通信システムにおいてマルチキャストデータを受信する方法及びそのためのｍ２ｍ機器
WO2019192218A1 (zh) 寻呼控制信息的指示、接收方法及装置、存储介质、基站、终端
US9398613B2 (en) Apparatus and method for supporting time-controlled service in machine-to-machine communication system
CN108632995B (zh) 一种寻呼优化的方法和装置
WO2017133462A1 (zh) 系统消息更新指示的方法、装置及系统
WO2018177431A1 (zh) 一种用户终端省电方法、装置
WO2021238591A1 (zh) 一种参考信号的配置更新方法及装置
WO2020135628A1 (zh) 一种寻呼消息的监听方法和装置
WO2020147686A1 (zh) 唤醒信号的发送和接收方法及装置、电子装置
WO2017059731A1 (zh) 寻呼处理方法及装置
CN110557765B (zh) 功耗模式调整方法及装置
US20240049137A1 (en) Transmitting Wake-up Signals for Paging Operations
US20170086166A1 (en) Paging message monitoring in electronic devices
WO2020147687A1 (zh) 监听唤醒信号的方法、装置、存储介质及电子装置
US20220303897A1 (en) Wake-up Signal Reception for Paging Operations
CN114374937A (zh) 业务变更通知方法、终端及网络侧设备
CN114731616A (zh) 寻呼冲突处理方法及相关装置
WO2018120900A1 (zh) 一种网络接入方法及装置、系统
WO2021197030A1 (zh) 一种通信方法及设备
WO2023097695A1 (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: 20741486

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3127114

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020208515

Country of ref document: AU

Date of ref document: 20200113

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20217025997

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020741486

Country of ref document: EP

Effective date: 20210818