A communication method, apparatus, medium, and product

Abstract

Embodiments of the present application provide a communication method, device, medium and product, which aims to enable a terminal device to receive emergency messages in time. The method comprises: receiving first information on a monitoring occasion, the first information being used to indicate that there is emergency service; and in the case of a service type being a full-area broadcast type emergency service, a first terminal device enters a wake-up state. In the case of a service type being a directional low-delay emergency service and the first terminal device being a terminal device that needs to receive the directional low-delay emergency service, the first terminal device enters the wake-up state on an nth monitoring time slot MO. Since the period of the monitoring occasion is less than the period of the idle mode discontinuous reception, the network device can faster issue the first information to the first terminal device, so that the first terminal device enters the wake-up state in time, thereby reducing the time required for waiting for the emergency service to be issued, so as to enable the terminal device to receive emergency messages in time and reduce communication delay.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a communication method, apparatus, medium and product. Background Technology

[0002] In the idle mode discontinuous reception (IDRX) scenario, the terminal device will operate according to a predetermined cycle and will only be woken up on the pre-set periodic paging occasions. The rest of the time, it will be in a deep sleep state to reduce the power consumption of the terminal device.

[0003] However, periodically waking up terminal devices still consumes significant power. To further reduce this consumption, one possible approach is to introduce a low-power wake-up signal (LP-WUS) mechanism, combining IDRX and LP-WUS to further enhance energy efficiency. However, when using IDRX and LP-WUS together, the communication latency of the terminal device becomes very significant, causing emergency messages to fail to be transmitted to the terminal device in a timely manner. Therefore, how to enable the terminal device to receive emergency messages in a timely manner has become a technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a communication method, apparatus, medium, and product, with the aim of solving the problem that terminal devices cannot receive emergency messages in a timely manner.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] The first aspect of this application provides a communication method, which can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. For example, the method is applied to a first terminal device, but this application does not limit its application. The following description uses a terminal device as an example. The method includes:

[0007] Receive first information, which indicates the existence of an emergency service and the service type of the emergency service; the first information is received during a monitoring period, the period of which is shorter than the period of discontinuous reception in idle mode;

[0008] When the service type is a region-wide broadcast emergency service, it enters the wake-up state;

[0009] When the service type is a targeted low-latency emergency service, and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, the device enters the wake-up state on the nth monitoring time slot MO, where the nth monitoring time slot is the MO closest to the current time, and n is a positive integer.

[0010] In the above scheme, by enabling the terminal device to receive the first information at the monitoring time and using the first information to indicate the existence of an emergency service and the service type of the emergency service, the terminal device can determine whether an emergency service exists in a shorter period of time. When the emergency service is a region-wide broadcast emergency service, it enters a wake-up state. When the emergency service is a targeted low-latency emergency service, and the first terminal device is the terminal device that needs to receive the targeted low-latency emergency service, it enters a wake-up state on the MO closest to the current time. This allows the first terminal device to determine the existence of an emergency service in a shorter time and wake up the first terminal device in a short time, without having to wait for the next MO corresponding to the first terminal device to send the emergency service. This reduces the waiting time required for the emergency service to be sent, so that the terminal device can receive the emergency message in a timely manner, reduce communication latency, and improve communication quality.

[0011] In some possible implementations, the monitoring timing is located within a deep sleep time slot between two adjacent MOs.

[0012] In the above scheme, by sending the first information in the time slot between two MOs, all terminal devices in the cell are forced to perform an additional fast detection at each monitoring opportunity, specifically for listening to the first information. This mechanism completely decouples the emergency wake-up delay from the terminal's own long IDRX cycle.

[0013] In some possible implementations, the method further includes:

[0014] Receive first configuration information, which is used to indicate the time offset between the monitoring timing and the adjacent MO.

[0015] In the above scheme, by sending configuration information to the terminal devices in the cell in advance, the terminal devices can determine the specific time of the monitoring opportunity, so that the terminal devices can listen for the first information at the accurate time point, and avoid the first terminal device failing to receive the first information sent by the network device.

[0016] In some possible implementations, the method further includes:

[0017] If the first information is not received at the specified monitoring time, return to deep sleep mode.

[0018] In the above scheme, if the first information is not received at the monitoring time, it means that there is no urgent business that the first terminal device needs to handle, and the first terminal device re-enters deep sleep mode to reduce power consumption.

[0019] In some possible implementations, the nth MO is the next MO adjacent to the monitoring time.

[0020] In the above scheme, when the first information is sent at the monitoring time, the MO that is closest to the monitoring time and can be used to transmit emergency services is the next MO adjacent to the monitoring time. In this way, when there is an emergency service that needs to be sent, the emergency service is quickly sent to the first terminal device, so that the first terminal device can receive the emergency service information in a timely manner.

[0021] In some possible implementations, the method further includes:

[0022] Receive second information, which indicates the identifier of the terminal device that needs to receive the targeted low-latency emergency service.

[0023] In the above scheme, an identifier of the terminal device that needs to receive the targeted low-latency emergency service is added to the second information, so that the first terminal device can determine whether it is a terminal device that needs to receive the targeted low-latency emergency service based on the identifier.

[0024] In some possible implementations, the method further includes:

[0025] If the first terminal device is a terminal device that does not need to receive the targeted low-latency emergency service, and the nth MO is the MO corresponding to the first terminal device, the device enters a wake-up state on the nth MO. If the nth MO is preempted by the second terminal device, compensation listening is performed on the (n+1)th MO, which is the next MO after the nth MO.

[0026] In the above scheme, the MO corresponding to the first terminal device is preempted by the second terminal device. The first terminal device performs compensation listening on the next adjacent MO to compensate for the first terminal device and avoid the first terminal device being unable to receive the information that needs to be sent on the MO before it was preempted due to the MO being preempted.

[0027] In some possible implementations, the nth MO is preempted by the second terminal device, including:

[0028] The first terminal device decodes a wake-up signal on the MO corresponding to the first terminal device that does not match the identifier of the first terminal device.

[0029] In the above scheme, if the identifier in the wake-up signal received by the first terminal device on the nth MO corresponding to itself is different from the identifier of the first terminal device itself, the nth MO is preempted by the second terminal device. This allows the first terminal device to determine whether the MO corresponding to itself has been preempted, so that the first terminal device can perform compensatory listening on the next MO after the MO is preempted, avoid missing information and affecting the normal communication of the first terminal device, and ensure communication quality.

[0030] In some possible implementations, the first information is a low-power wake-up signal, which includes a prefix bit and a service type bit. The prefix bit is used to indicate the existence of an emergency service, and the service type bit is used to indicate the service type of the emergency service.

[0031] In the above scheme, a prefix bit and a service type bit are added to the low-power wake-up signal so that the terminal device in the cell can be briefly woken up on the MO and determine whether it needs to remain in the wake-up state on the current MO based on the prefix bit and the service type bit, so that the terminal device that needs to receive the emergency service can receive the information corresponding to the emergency service on the nearest MO.

[0032] In some possible implementations, the nth MO is the MO in which the first terminal device is located at the current moment.

[0033] In the above scheme, since the first information is sent on the MO, if the terminal device needs to receive the information corresponding to the emergency service at the current moment, it can directly receive it on the MO where it is located at the current moment, without having to wait for the next MO corresponding to the first terminal device to send the emergency service. This reduces the waiting time required for the emergency service to be sent, so that the terminal device can receive the emergency message in a timely manner, reduce communication delay, and improve communication quality.

[0034] In some possible implementations, when the service type is a targeted low-latency emergency service, the nth MO is the MO corresponding to the first terminal device, and the nth MO is preempted by the second terminal device, the low-power wake-up signal is also used to indicate a recovery scheduling instruction; the recovery scheduling instruction is used to indicate compensation listening on the mth MO after the nth MO, where m is an integer greater than 0.

[0035] In the above scheme, in the event of preemption, the low-power wake-up signal is also used to indicate the recovery scheduling command so that the preempted terminal device can determine the MO used for compensation and wake up on the compensated MO to avoid missing information and affecting the normal communication of the first terminal device, thus ensuring communication quality.

[0036] In some possible implementations, the first information includes a first subfield and a second subfield, wherein the first subfield indicates the identifier of the first terminal device and the second subfield indicates the value of m.

[0037] In the above scheme, by setting the first subfield and the second subfield in the low-power wake-up signal, the preempted terminal device can determine the compensation MO corresponding to itself based on the identifier, so as to avoid missing information and affect the normal communication of the terminal device and ensure the communication quality.

[0038] A second aspect of this application provides a communication method, which may be executed by a network device, or by a component configured in the network device (such as a circuit, core network unit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example. The method includes:

[0039] Send a first message, which indicates the existence of the emergency service and the service type of the emergency service, wherein the service type is either a region-wide broadcast emergency service or a targeted low-latency emergency service.

[0040] In the above scheme, by enabling network devices to send first information during monitoring, the first information indicates the existence of an emergency service and its service type. This allows terminal devices to determine the existence of an emergency service within a shorter period based on whether they receive the first information. When the emergency service is a broadcast emergency service, the device enters a wake-up state. When the emergency service is a targeted low-latency emergency service, and the first terminal device is the one that needs to receive the targeted low-latency emergency service, the device enters a wake-up state on the MO closest to the current time. This allows network devices to send the first information to the first terminal device in a short time after receiving the emergency service that needs to be sent, and to wake up the first terminal device in a short time after confirming the existence of an emergency service, without having to wait for the next MO corresponding to the first terminal device to send the emergency service. This reduces the waiting time required for the emergency service to be sent, enabling terminal devices to receive emergency messages in a timely manner, reducing communication latency, and improving communication quality.

[0041] In some possible implementations, the method further includes:

[0042] Receive emergency information, which is used to indicate emergency operations.

[0043] In the above scheme, by receiving emergency information, the network device can determine whether there is an emergency service that needs to be issued.

[0044] In some possible implementations, when the emergency information is a public early warning system warning, the service type of the emergency service is a region-wide broadcast emergency service.

[0045] In the above plan, information that requires comprehensive broadcasting, such as warnings from the public early warning system, will be treated as an emergency service broadcast throughout the region to avoid missing any terminal devices.

[0046] In some possible implementations, when the emergency information is data with an ultra-low latency quality of service identifier, the service type of the emergency service is a targeted low-latency emergency service.

[0047] In the above scheme, services that only need to be sent to a portion of terminal subgroups are identified as targeted low-latency emergency services, thereby avoiding resource and energy waste caused by sending them to all terminal devices.

[0048] In some possible implementations, sending the first information includes:

[0049] In the case where the service type is a region-wide broadcast emergency service, or in the case where the service type is a targeted low-latency emergency service and the waiting time is greater than the opportunity window, the first information is sent. The waiting time is the time interval between the current moment and the next monitoring time slot (MO) corresponding to the terminal device that needs to receive the targeted low-latency emergency service. The opportunity window is the maximum waiting time of the targeted low-latency emergency service.

[0050] In the above scheme, when the service type is a region-wide broadcast emergency service, and when the service type is a targeted low-latency emergency service, and the waiting time is greater than the opportunity window, the first message is sent. This allows the network device to send the first message directly under the region-wide broadcast emergency service with higher urgency. Under the low-latency emergency service with relatively lower urgency, it is determined whether the regular wake-up process meets the waiting time. If it does not meet the waiting time, the first message is sent. This reduces the number of wake-up calls for terminal devices and further reduces energy consumption.

[0051] In some possible implementations, the monitoring timing occurs within a deep sleep time slot between two MOs.

[0052] In some possible implementations, the method further includes:

[0053] Send first configuration information, which is used to indicate the time offset between the monitoring timing and the adjacent MO.

[0054] In some possible implementations, the method further includes:

[0055] Send a second message, which indicates the identifier of the terminal device that needs to receive the targeted low-latency emergency service.

[0056] In some possible implementations, the method further includes:

[0057] A first wake-up signal is sent on the (n+1)th MO. The first wake-up signal is a wake-up signal that needs to be sent on the nth MO before the nth MO is preempted. The (n+1)th MO is the next MO after the nth MO.

[0058] In some possible implementations, the first information is a low-power wake-up signal, which includes a prefix bit and a service type bit. The prefix bit is used to indicate the existence of the emergency service, and the service type bit is used to indicate the service type of the emergency service.

[0059] In some possible implementations, when the service type is a targeted low-latency emergency service, the nth MO is the MO corresponding to the first terminal device, and the nth MO is preempted by the second terminal device, the low-power wake-up signal is also used to indicate a recovery scheduling instruction; the recovery scheduling instruction is used to indicate compensation listening on the mth MO after the nth MO, where m is an integer greater than 0.

[0060] In some possible implementations, the first information includes a first subfield and a second subfield, wherein the first subfield indicates the identifier of the terminal device corresponding to the preempted MO, and the second subfield indicates the value of m.

[0061] It should be noted that the technical effects of the above implementation methods can be referred to the technical effects of the corresponding implementation methods in the first aspect.

[0062] A third aspect of this application provides a communication device, including a module for performing the method provided in the first aspect, or a module for performing the method provided in the second aspect.

[0063] A fourth aspect of this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device, implement the method provided in the first aspect or the method provided in the second aspect.

[0064] The fifth aspect of this application provides a computer program product including instructions that, when executed, cause the method provided in the first aspect or the method provided in the second aspect.

[0065] A sixth aspect of this application provides a chip including a processor coupled to a memory for executing a computer program or instructions stored in the memory, such that the chip implements the method provided in the first aspect or the method provided in the second aspect.

[0066] The seventh aspect of this application provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor is used to implement the method provided in the first aspect or the method provided in the second aspect through logic circuits or executing code instructions.

[0067] An eighth aspect of this application provides a communication system, including the communication apparatus provided in the seventh aspect. Attached Figure Description

[0068] Figure 1 This is a schematic diagram of the system architecture of the communication system provided in the embodiments of this application;

[0069] Figure 2 A flowchart illustrating a communication method provided in an embodiment of this application;

[0070] Figure 3 A flowchart illustrating another communication method provided in an embodiment of this application;

[0071] Figure 4 A schematic diagram illustrating the monitoring timing provided in the embodiments of this application;

[0072] Figure 5 A schematic diagram illustrating the waiting time provided in the embodiments of this application;

[0073] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0074] Figure 7 A schematic diagram of MO when the monitoring time is MO, provided for an embodiment of this application;

[0075] Figure 8 A schematic diagram of the structure of a communication device provided in this application;

[0076] Figure 9 A schematic diagram of another communication device provided in this application;

[0077] Figure 10 A schematic diagram of the structure of an electronic device provided in this application;

[0078] Figure 11 A schematic diagram of the structure of another electronic device provided in this application. Detailed Implementation

[0079] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0080] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0081] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0082] The embodiments of this application are applied to communication systems, which can be second-generation (2G) communication systems, third-generation (3G) communication systems, LTE systems, fifth-generation (5G) communication systems, LTE and 5G hybrid architectures, 5G new radio (5G NR) systems, and new communication systems that will emerge in the future development of communication.

[0083] A communication system includes a first device and a second device. The first device can be a network-side device used to provide network communication functions; in some cases, it is also called a network device or network element. Network devices are typically base stations (including functional units of base stations, or combinations of functional units of base stations) or core network units. Core network units can be functional units within the core network, including but not limited to access and mobility management function (AMF) units or session management function (SMF) units. The second device can be a device accessing the network, typically a terminal. An example of a communication system is... Figure 1 As shown, Figure 1 It includes base station 1 and terminal 2.

[0084] In the embodiments provided in this application, the base station can be any device with wireless transceiver capabilities, including but not limited to: evolved base stations (NodeB, eNB, or e-NodeB) in Long Term Evolution (LTE), base stations (gNodeB or gNB) or transmission receiving points / transmission reception points (TRPs) in New Radio (NR), and base stations in subsequent 3GPP evolutions. The base station can be: a macro base station, micro base station, pico base station, small cell, relay station, or balloon station, etc. The base station can include one or more co-located or non-co-located transmission reception points (TRPs). The base station can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The base station can communicate with the terminal, or it can communicate with the terminal through a relay station. The terminal can communicate with multiple base stations using different technologies. For example, the terminal can communicate with base stations that support LTE networks, base stations that support 5G networks, and can also establish dual connections with both LTE and 5G base stations.

[0085] In the embodiments provided in this application, the terminal can take various forms, such as a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. The terminal may also be referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent, or UE device, etc. The terminal can also be a fixed terminal or a mobile terminal.

[0086] IDRX is the fundamental mechanism for UE energy saving. The core of IDRX is that the UE operates according to a configured IDRX cycle. The high-power main radio (MR) module in the UE is in deep sleep most of the time, only being woken up on predefined, periodic paging occasions (PO) to monitor paging messages according to traditional procedures. However, this periodic wake-up itself still consumes considerable power. To address this issue, one possible implementation is to introduce the LP-WUS mechanism. LP-WUS adds a separate, extremely low-power wake-up receiver (LP-WUR). The advantage of LP-WUS is that it allows the MR to enter a deep sleep state, performing duty cycle monitoring only on dedicated LP-WUS occasions (LO). In the combined use of LP-WUS and IDRX, the LP-WUS LO cycle is configured to be the same as the UE's IDRX cycle, and the LO position is defined by an offset relative to a reference PO or paging frame (PF). To achieve refined management and improve energy efficiency, UEs are divided into up to 32 subgroups. The LP-WUS signal sent by the network carries a code point value, with each code point value corresponding to one or more specific subgroups. When the LP-WUS detects an LP-WUS signal for a specific subgroup, it triggers MR wake-up, waking up the MR for that subgroup. After a minimum interval (i.e., wake-up delay) including MR hardware startup and network resynchronization, the MR then monitors traditional paging messages on its associated PO.

[0087] However, in the above implementation, since the UE only listens on the specific monitoring slot (MO) allocated to its subgroup, the communication latency can become very significant in some scenarios with extremely strict latency requirements. Even the shortest DRX period can be longer than the tolerable latency between the time when the data can be transmitted at the gNB and the time when the UE listens to receive it. Even if the network has an extremely urgent PWS warning to issue, it must wait for the next scheduled wake-up time of the target UE. This waiting time is directly related to the UE's IDRX period, and in long-period configurations, it can reach several seconds. For emergency response scenarios, this latency will seriously affect the communication quality.

[0088] To address the aforementioned problems, embodiments of this application provide a communication method, apparatus, medium, and product. To make the technical solutions of this application clearer and easier to understand, the communication method, apparatus, medium, and product provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0089] See Figure 2 The flowchart shown illustrates a communication method, which includes:

[0090] S201: The network device sends first information, which is received during a monitoring period shorter than the period of discontinuous reception in idle mode. Correspondingly, the first terminal device receives the first information, which indicates the existence of an emergency service and the service type of the emergency service, which is either a region-wide broadcast emergency service or a targeted low-latency emergency service.

[0091] Network devices send first information to the first terminal device using any information transmission method such as broadcast, unicast, or multicast. For example, when there is an urgent service that needs to be delivered immediately, the network device sends the first information to the first terminal device. When there is no urgent service that needs to be delivered immediately, the network device does not send the first information. This allows the first terminal device to assume that there is an urgent service that it needs to receive immediately if it receives the first information, and to assume that there is no urgent service that it needs to receive immediately if it does not receive the first information. The period for discontinuous reception in idle mode is the IDRX period, which is the sleep duration of the first terminal device in the idle state.

[0092] Emergency services are those that terminal devices need to receive within a certain period, such as services with a tolerable latency of less than a preset time. Emergency service types include broadcast emergency services and targeted low-latency emergency services. When generating the first information, the network device adds the service type corresponding to the emergency service at the current moment to the first information. In other words, the service type in the first information indicates the service type of the emergency service corresponding to the first terminal device; in this case, the service type in the first information is either a broadcast emergency service or a targeted low-latency emergency service.

[0093] S202: The first terminal device enters the wake-up state when the service type is a regional broadcast emergency service.

[0094] The district-wide broadcast emergency service is an emergency service that needs to be sent to all terminal devices within the community. It is used in scenarios such as public early warning systems that require maximum reach, in order to trigger all terminal devices to synchronously wake up MR to receive subsequent broadcast information.

[0095] When the first terminal device is in the case of a region-wide broadcast emergency service, it immediately enters the wake-up state to wake up the MR, so as to receive the broadcast information immediately. This eliminates the need to wait for the next MO corresponding to the first terminal, enabling the first terminal device to receive the information corresponding to the emergency service, reducing waiting time, lowering communication latency, and ensuring communication quality.

[0096] S203: When the service type of the first terminal device is a targeted low-latency emergency service, and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, the first terminal device enters the wake-up state on the nth monitoring time slot MO. The nth monitoring time slot is the MO closest to the current time, and n is a positive integer.

[0097] Targeted low-latency emergency services are emergency services that need to be sent to one or more terminal device subgroups. They are used for latency-sensitive emergency communications that are not broadcast to the entire area, such as high-priority IoT commands or alarms for specific groups. Targeted low-latency emergency services only need to trigger the wake-up process of terminal devices within a subset of terminal device subgroups, without triggering the wake-up process of unrelated terminal devices, thus avoiding unnecessary power consumption for unrelated terminal devices.

[0098] When the first terminal device receives a first information indication that the service type is a targeted low-latency emergency service, it enters a wake-up state on the MO (Mobile Interchange) closest to the current time. For example, if the current time is on an MO, it enters a wake-up state; if the current time is in the gap between two MOs and is in a sleep state, it enters a wake-up state on the next MO adjacent to the current time. By waking up the first terminal device on the MO closest to the current time, the first terminal device can receive the information corresponding to the emergency service without waiting for the next MO corresponding to the first terminal, reducing waiting time, lowering communication latency, and ensuring communication quality.

[0099] In one optional embodiment, the network device sends first information at the monitoring time. If there is no urgent service that needs to be issued immediately at the current monitoring time, then the first information is not sent at the current monitoring time.

[0100] The network device sends first information during the monitoring period, and the first terminal device receives the first information during the monitoring period. The interval between adjacent monitoring periods is less than the interval between the two MOs corresponding to the first terminal device. The monitoring period is the time when each terminal device in the cell needs to be woken up. For example, the first monitoring period and the second monitoring period are two adjacent monitoring periods. The pre-set MOs corresponding to the first terminal device include the first MO and the third MO. The second MO is included between the first MO and the third MO. The second MO does not correspond to the first terminal device, so the first MO and the third MO are adjacent MOs for the first terminal device. The time interval between the first monitoring period and the second monitoring period is less than the time interval between the first MO and the third MO.

[0101] The monitoring timing can be set based on actual needs. For example, the monitoring timing can be an MO, or an additional timing can be added between two MOs to send the first information.

[0102] To facilitate understanding, the following examples illustrate the situation using the monitoring time as MO and the monitoring time being between two MOs.

[0103] like Figure 3 As shown, taking the monitoring opportunity as an example where the monitoring opportunity is located between two MOs, the nth MO is the next MO adjacent to the monitoring opportunity:

[0104] S301: The network device sends first configuration information, which indicates the monitoring timing, the time offset from adjacent MOs, and the opportunity window. Correspondingly, the first terminal device receives the first configuration information.

[0105] The first configuration information is used to indicate the time offset between the monitoring timing and the adjacent previous MO, or the time offset between the monitoring timing and the adjacent next MO. In this embodiment, the first configuration information indicating the time offset between the monitoring timing and the adjacent previous MO will be used as an example for subsequent explanation.

[0106] Opportunity window is a configurable parameter in milliseconds that provides decision-making support for network devices. It allows network devices to quantify the trade-off between absolute minimum latency and optimal system power consumption, determining how much additional latency a network device is willing to tolerate before initiating an emergency wake-up action for urgent business needs.

[0107] It should be noted that the opportunity window can be set in advance by the network operator based on network policies and business models. For example, based on the priority of emergency services, opportunity windows are allocated to different emergency services with corresponding priorities. The higher the priority, the smaller the opportunity window.

[0108] Network devices broadcast first configuration information within the cell. The first configuration information can be system information block type 1 (SIB1). For example, in the low-power wake-up signal cell configuration (lp-wus-CellConfig) information block, an opportunity window parameter is added.

[0109] like Figure 4 As shown, the monitoring opportunities are all located between two adjacent MOs. Taking the first MO and the second MO as an example, the monitoring opportunity is located between the first MO and the second MO. The time offset between the monitoring opportunity and the adjacent previous MO is the time offset of the monitoring opportunity relative to the first MO.

[0110] S302: The network device determines whether to send the first information during the monitoring period.

[0111] Before sending the first message, the network device needs to receive an emergency message, which indicates an emergency service. If the network device does not receive the emergency message, it does not need to send the first message. If the network device receives the emergency message that needs to be sent, it determines the type of emergency service. In the case of a region-wide broadcast emergency service, step S303 is executed.

[0112] In the case of a targeted low-latency emergency service, the network device calculates the waiting time and compares it with the opportunity window to determine whether to send the first message. If the waiting time is greater than the opportunity window, the first message is sent, and step S303 is executed. If the waiting time is less than or equal to the opportunity window, the first message is not sent. The waiting time is the time interval between the current moment and the next monitoring time slot (MO) corresponding to the terminal device that needs to receive the targeted low-latency emergency service. That is, in this embodiment, in the case of a region-wide broadcast emergency service, or in the case of a targeted low-latency emergency service and the waiting time is greater than the opportunity window, the first message is sent. In this case, the opportunity window compared by the user is the maximum waiting time for the targeted low-latency emergency service.

[0113] To facilitate understanding, examples are given below, such as Figure 5 As shown, the network device records the precise time T_Data available for transmission when it receives the emergency information to obtain the current time. It then queries the first terminal device's listening schedule to find the scheduled transmission time T_lp-wus for the next regular MO corresponding to the first terminal device. The waiting time is the scheduled transmission time minus the current time plus the transmission time.

[0114] If the waiting time is less than or equal to the time window, the time delay is within the acceptable range for emergency services. The network device is in normal mode and does not send any signal at the upcoming monitoring time. When the scheduled transmission time of the next normal MO corresponding to the first terminal device is reached, the LP-WUS is sent to the first terminal device.

[0115] If the waiting time exceeds the time window, the time delay is outside the acceptable range for emergency services. The network device enters MO preemption mode, constructs the first message, and sends the first message on the next CMO.

[0116] It should be noted that if the network device does not send the first information, the first terminal device will not receive the first information during the monitoring period and will return to deep sleep mode.

[0117] S303: The network device sends the first information during the monitoring period. Correspondingly, the first terminal device receives the first information during the monitoring period, which is located within a deep sleep time slot between two adjacent MOs.

[0118] The monitoring timing is specifically a common monitoring occasion (CMO), and the first information is specifically an emergency indication (EI) signal. The EI signal includes a first bit and a second bit. The first bit indicates the mode the base station is in, such as emergency mode or normal mode. If the base station does not receive emergency information, it is in normal mode, and the first bit is 0. If the base station receives emergency information, it is in emergency mode, and the first bit is 1.

[0119] The second bit is used to indicate the service type of the emergency service. When the service type is a region-wide broadcast emergency service, the second bit is 1, and when the service type is a targeted low-latency emergency service, the second bit is 0.

[0120] It should be noted that all terminal devices within the cell are briefly woken up on the CMO for detection to facilitate receiving the first information. If a network device simultaneously receives both a region-wide broadcast emergency service and a targeted low-latency emergency service, the EI corresponding to the region-wide broadcast emergency service is sent on the next CMO, and the EI corresponding to the targeted low-latency emergency service is sent on the next CMO following the EI corresponding to the region-wide broadcast emergency service.

[0121] S304: The first terminal device enters the wake-up state when the service type is a regional broadcast emergency service.

[0122] When the emergency information is issued by the public early warning system, the emergency service type is a district-wide broadcast emergency service.

[0123] S305: When the service type is Targeted Low-Latency Emergency Service and the first information has been sent, the network device sends a second information, which indicates the identifier of the terminal device that needs to receive the Targeted Low-Latency Emergency Service. Accordingly, the first terminal device receives the second information.

[0124] The first terminal device compares its own identifier with the identifier of a terminal device that needs to receive the targeted low-latency emergency service. If the identifiers match, the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, enabling the first terminal device to determine whether it is a terminal device that needs to receive the targeted low-latency emergency service. The second information is a low-power wake-up signal, which carries the identifier of the terminal device that needs to receive the targeted low-latency emergency service.

[0125] S306: When the service type of the first terminal device is a targeted low-latency emergency service, and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, the first terminal device enters the wake-up state on the nth monitoring time slot MO. The nth monitoring time slot is the MO closest to the current time, and n is a positive integer.

[0126] When the emergency information is data with an ultra-low latency service quality identifier, the service type of the emergency service is targeted low-latency emergency service.

[0127] S307: When the service type of the first terminal device is a targeted low-latency emergency service, and the first terminal device is a terminal device that does not need to receive targeted low-latency emergency services, and the nth MO is the MO corresponding to the first terminal device, the first terminal device enters a wake-up state on the nth MO. If the nth MO is preempted by the second terminal device, compensation listening is performed on the (n+1)th MO. Correspondingly, the network device sends a first wake-up signal on the (n+1)th MO. The first wake-up signal is a wake-up signal that needs to be sent on the nth MO before the nth MO is preempted.

[0128] The (n+1)th MO is the next MO after the nth MO, so that even if the MO corresponding to the first terminal device is preempted, it can still successfully receive the LP-WUS signal rescheduled for it by the network device on the next MO.

[0129] The nth MO is preempted by the second terminal device, specifically including: the first terminal device decoding a wake-up signal on the MO corresponding to the first terminal device that does not match the identifier of the first terminal device. For example, the first terminal device decoding an LP-WUS signal on the MO corresponding to the first terminal device that does not match its own ID.

[0130] like Figure 6 As shown, taking the monitoring time MO as an example, the nth MO is the MO where the first terminal device is located at the current time:

[0131] S601: The network device sends second configuration information, which is used to indicate an opportunity window. Correspondingly, the first terminal device receives the second configuration information.

[0132] The network device broadcasts second configuration information within the cell. Specifically, the second configuration information can be of system information block type 1 (SIB1). For example, in the low-power wake-up signal cell configuration (lp-wus-CellConfig) information block, an opportunity window parameter is added. A detailed description of the opportunity window can be found in step S301 above.

[0133] S602: The network device determines whether to send the first message on the MO.

[0134] In this embodiment, the method for determining whether a network device sends the first information on the MO can be referred to the description in step S302 above.

[0135] S603: The network device sends the first information on the MO, and correspondingly, the first terminal device receives the first information on the MO.

[0136] The first piece of information is LP-WUS, which includes newly added prefix bits and service type bits. The prefix bits indicate the presence of an emergency service, and the service type bits indicate the service type of the emergency service. The prefix bit is the first bit in LP-WUS. When the prefix bit is 0, the network device is in normal mode, indicating that there is no emergency service to be issued. Subsequent information bits are defined as normal code points, and one or more terminal device subgroups execute a pre-set paging wake-up procedure. When the prefix bit is 1, the network device is in emergency mode, indicating the presence of an emergency service to be issued. Subsequent information bits are redefined as an emergency terminal device identifier (E-ID), used for accurate and rapid addressing of one or more terminal device subgroups in emergency situations.

[0137] The E-ID payload structure includes a service type bit and a target identifier field. The value of the service type bit determines the meaning of the target identifier field. When the emergency service type is a region-wide broadcast emergency service, the service type bit is 1, and the target identifier field is absent or ignored. When the emergency service type is a targeted low-latency emergency service, the service type bit is 0, and the target identifier field is used to indicate the subgroup ID that needs to receive the targeted low-latency emergency service, in order to accurately address one or more terminal devices that need to receive the targeted low-latency emergency service.

[0138] All terminal devices in the cell are briefly awakened at the start of each MO and, based on LP-WUS, determine whether they need to receive information corresponding to emergency services. If they do not need to receive such information, the terminal devices re-enter deep sleep mode. Figure 7 As shown, an MO consists of MO1 and MO2. MO1 is the period during which all terminal devices in the cell are briefly awakened, and MO2 is the period during which terminal devices that need to receive but do not need to receive re-enter deep sleep. The MO is located within the LP-WUS Occasion (LO).

[0139] Specifically, the first terminal device determines whether it needs to receive information corresponding to emergency services based on LP-WUS. This includes: when the prefix bit of LP-WUS is 0, the first terminal device determines whether the current MO is the MO pre-assigned to it; if not, it immediately returns to sleep. If so, it continues to decode subsequent regular code points, thereby reducing the power consumption of terminal devices unrelated to the current MO.

[0140] S604: The first terminal device enters the wake-up state when the service type is a regional broadcast emergency service.

[0141] When the prefix bit of LP-WUS is 1, if the service bit is 1, the service type is a regional broadcast emergency service, and the first terminal device remains in the wake-up state in the current MO.

[0142] S605: When the service type of the first terminal device is a targeted low-latency emergency service, and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, the first terminal device enters the wake-up state on the nth monitoring time slot MO, where the nth MO is the MO where the first terminal device is located at the current moment.

[0143] When the prefix bit of LP-WUS is 1, if the service bit is 0, the first terminal device will match the subgroup ID carried in the target identifier field with its own stored ID. If they match, the service type is a targeted low-latency emergency service, and the first terminal device itself is determined to be the target to be addressed, and it will remain in a wake-up state on the current MO.

[0144] S606: When the first terminal device is a targeted low-latency emergency service, and the first terminal device does not need to receive targeted low-latency emergency services, and the nth MO is the MO corresponding to the first terminal device, it enters a wake-up state on the nth MO. If the nth MO is preempted by the second terminal device, it performs compensatory listening on the (n+m)th MO. Correspondingly, the network device sends a first wake-up signal on the (n+m)th MO. The first wake-up signal is a wake-up signal that needs to be sent on the nth MO before the nth MO is preempted.

[0145] The first wake-up signal is specifically a recovery scheduling instruction, which instructs the terminal device affected by the preemption to perform compensatory listening on the m-th MO after the current MO.

[0146] Because, when monitoring occurs at the MO (Mobile Oscillator) time, if there is a region-wide broadcast emergency service or a targeted low-latency emergency service with a waiting time longer than the opportunity window, the current MO needs to be preempted. Therefore, to ensure that the terminal device originally corresponding to the preempted MO can successfully obtain the predetermined signal, in cases where the service type is a region-wide broadcast emergency service or a targeted low-latency emergency service, and the nth MO is the MO corresponding to the first terminal device and is preempted by the second terminal device, the low-power wake-up signal is also used to indicate the recovery scheduling command. The recovery scheduling command is used to instruct compensation monitoring to be performed on the mth MO after the nth MO, where m is an integer greater than 0.

[0147] Specifically, the first information sent by the network device includes a first subfield and a second subfield. The first subfield indicates the identifier of the first terminal device, which is the identifier of the terminal device affected by the preemption. The second subfield indicates the value of m, which means that the terminal device affected by the preemption should perform compensation listening on the m-th time after the current moment. The first and second subfields together form the preemption information field. The preemption information field is only included when a preemption occurs, so that this embodiment can use the same emergency LP-WUS signal to accurately wake up the UE that needs to receive emergency services, and also broadcast a recovery scheduling instruction to the preempted UE subgroup.

[0148] Correspondingly, after the terminal device whose MO is preempted fails to match with the E-ID, it matches based on the ID in the first subfield, and after a successful match, it determines the MO to be used for compensation based on the second subfield, and wakes up on the compensation MO, so as to avoid the terminal device whose MO is preempted from missing information due to the preemption.

[0149] The above embodiments enable the terminal device to receive first information at the monitoring time and use the first information to indicate the existence of an emergency service and the service type of the emergency service. This allows the terminal device to determine whether an emergency service exists within a shorter period of time. When the emergency service is a region-wide broadcast emergency service, the terminal device enters a wake-up state. When the emergency service is a targeted low-latency emergency service and the first terminal device is the terminal device that needs to receive the targeted low-latency emergency service, the terminal device enters a wake-up state on the MO closest to the current time. This allows the first terminal device to determine the existence of an emergency service in a shorter time and wake up the terminal device in a short time. There is no need to wait for the next MO corresponding to the first terminal device to send the emergency service, reducing the waiting time required for the emergency service to be sent. This enables the terminal device to receive emergency messages in a timely manner, reduces communication latency, and improves communication quality.

[0150] This application also provides a communication device, including a module for performing a communication method.

[0151] This application also provides a computer-readable storage medium storing a computer program or instructions, which, when executed by a communication device, implements a communication method.

[0152] This application also provides a computer program product, including instructions that, when executed, enable a communication method to be implemented.

[0153] This application also provides a chip, including a processor coupled to a memory, for executing computer programs or instructions stored in the memory, thereby enabling the chip to implement a communication method.

[0154] This application also provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor implements the communication method through logic circuits or executing code instructions.

[0155] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 8As shown, the communication device 800 may include a communication module 810. The communication module 810 can implement corresponding communication functions, which can be internal communication functions of the communication device 800 or communication functions between the communication device 800 and other devices. Optionally, the communication module 810 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 800 also includes a processing module 820. The processing module 820 can implement corresponding processing functions.

[0156] Optionally, the communication device 800 further includes a storage module, which can be used to store instructions and / or data; the processing module 820 can read the instructions and / or data in the storage module so that the communication device 800 can implement the aforementioned method embodiments.

[0157] In one possible design, the communication device 800 may correspond to the terminal device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 800 can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0158] For example, the communication module 810 is used to receive first information, which indicates the existence of emergency service and the service type of the emergency service;

[0159] Processing module 820 is used to enter the wake-up state when the service type is a region-wide broadcast emergency service;

[0160] The processing module 820 is also used to enter the wake-up state on the nth monitoring time slot MO when the service type is a targeted low-latency emergency service and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service. The nth monitoring time slot is the MO closest to the current time, and n is a positive integer.

[0161] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0162] In one possible design, the communication device 800 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 800 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0163] For example, the communication module 810 is used to send first information, which indicates the existence of an emergency service and the service type of the emergency service, which is either a regional broadcast emergency service or a targeted low-latency emergency service.

[0164] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0165] Figure 9 This is another schematic block diagram of the communication device 900 provided in the embodiments of this application. The communication device 900 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The communication device 900 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0166] like Figure 9 As shown, the communication device 900 may include one or more processors 910, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 910 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 900 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0167] In an alternative design, the processor 910 may also store instructions and / or data, which can be executed by the processor 910 to cause the communication device 900 to perform the methods described in the above method embodiments.

[0168] In another alternative design, the communication device 900 may include a communication interface 920 for implementing receiving and transmitting functions. For example, the communication interface 920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0169] Optionally, the communication device 900 may include one or more memories 930, which may store instructions that can be executed on the processor 910, causing the communication device 900 to perform the methods described in the above method embodiments. Optionally, the memories 930 may also store data. Optionally, the processor 910 may also store instructions and / or data. The processor 910 and the memories 930 may be provided separately or integrated together.

[0170] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0171] In one implementation, the communication device 900 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0172] In another implementation, the communication device 900 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0173] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0174] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0175] Figure 10 This application provides an example of the composition of an electronic device. The electronic device can be a terminal device, including but not limited to mobile phones, smart wearable devices (such as smartwatches), and other electronic devices. Taking a mobile phone as an example, the electronic device may include a processor 1010, an external memory interface 1020, internal memory 1021, a display screen 1030, a camera 1040, antenna 1, antenna 2, a mobile communication module 1050, and a wireless communication module 1060, etc.

[0176] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0177] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0178] The external storage interface 1020 can be used to connect external storage cards, such as Micro SD cards, to expand the storage capacity of electronic devices.

[0179] Internal memory 1021 can be used to store executable program code, which includes instructions. Processor 1010 executes various functional applications and data processing of electronic devices by running the instructions stored in internal memory 1021.

[0180] The wireless communication function of electronic devices can be implemented through antenna 1, antenna 2, mobile communication module 1050, wireless communication module 1060, modem processor, and baseband processor.

[0181] The mobile communication module 1050 can provide solutions for wireless communication applications, including 2G / 3G / 4G / 5G, in electronic devices. The mobile communication module 1050 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.

[0182] Furthermore, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows operating systems. Applications can be installed and run on this operating system. Those skilled in the art will understand that, for the sake of convenience and brevity, explanations and beneficial effects of the relevant content in any of the above-described electronic devices can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0183] Figure 11 This application provides another example of the composition of an electronic device. The electronic device may be a first device, including but not limited to a base station and a core network unit. Figure 11A simplified schematic diagram of a base station structure is shown. The base station includes parts 1110, 1120, and 1130. Part 1110 is mainly used for baseband processing and base station control; part 1110 is typically the control center of the base station, often referred to as a processor, used to control the base station to perform the processing operations on the first device side in the above method embodiments. Part 1120 is mainly used for storing computer program code and data. Part 1130 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; part 1130 is often referred to as a transceiver module, transceiver, transceiver circuit, or transceiver. The transceiver module of part 1130, also referred to as a transceiver or transceiver, includes an antenna 1133 and a radio frequency circuit (…). Figure 11 (Not shown in the image), where the radio frequency circuitry is primarily used for radio frequency processing. Optionally, the device in section 1130 used to implement the receiving function can be considered a receiver, and the device used to implement the transmitting function can be considered a transmitter; that is, section 1130 includes receiver 1132 and transmitter 1131. A receiver can also be called a receiving module, receiver circuit, or receiving module, etc., and a transmitter can be called a transmitting module, transmitter, or transmitting circuit, etc.

[0184] Sections 1110 and 1120 may include one or more circuit boards, each of which may include one or more processors and one or more memories. The processors are used to read and execute programs from the memories to implement baseband processing functions and control the base station. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple circuit boards may share one or more processors, multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.

[0185] For example, in one implementation, the transceiver module of section 1130 is used to execute the transceiver-related processes performed by the base station (first device) in the aforementioned method embodiments. The processor of section 1110 is used to execute the processing-related processes performed by the base station in the aforementioned method embodiments.

[0186] It should be understood that Figure 11 This is for illustrative purposes only and not as a limitation. The network devices mentioned above, including processors, memory, and transceivers, may be independent of... Figure 11 The structure shown.

[0187] This application also provides a chip system including a processor for supporting terminal devices or network devices in implementing the functions involved in the above aspects, such as transmitting or processing data and / or information involved in the above methods. In one possible design, the chip system also includes a memory for storing necessary program instructions and data for the terminal device or network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0188] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0189] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

[0190] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0191] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0192] In summary, the above are merely preferred embodiments of the technical solutions of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a first terminal device, the method includes: Receive first information, which indicates the existence of an emergency service and the service type of the emergency service; the first information is received during a monitoring period, the period of which is shorter than the period of discontinuous reception in idle mode; When the service type is a region-wide broadcast emergency service, it enters the wake-up state; When the service type is a targeted low-latency emergency service, and the first terminal device is a terminal device that needs to receive the targeted low-latency emergency service, the device enters the wake-up state on the nth monitoring time slot MO, where the nth monitoring time slot is the MO closest to the current time, and n is a positive integer.

2. The method according to claim 1, characterized in that, The monitoring timing is located within the deep sleep time slot between two adjacent MOs.

3. The method according to claim 2, characterized in that, The method further includes: Receive first configuration information, which is used to indicate the time offset between the monitoring timing and the adjacent MO.

4. The method according to claim 2, characterized in that, The method further includes: If the first information is not received at the specified monitoring time, return to deep sleep mode.

5. The method according to claim 2, characterized in that, The nth MO is the next MO adjacent to the monitoring time.

6. The method according to claim 1, characterized in that, The method further includes: Receive second information, which indicates the identifier of the terminal device that needs to receive the targeted low-latency emergency service.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: If the first terminal device is a terminal device that does not need to receive the targeted low-latency emergency service, and the nth MO is the MO corresponding to the first terminal device, the device enters a wake-up state on the nth MO. If the nth MO is preempted by the second terminal device, compensation listening is performed on the (n+1)th MO, which is the next MO after the nth MO.

8. The method according to claim 7, characterized in that, The nth MO being preempted by the second terminal device includes: The first terminal device decodes a wake-up signal on the MO corresponding to the first terminal device that does not match the identifier of the first terminal device.

9. The method according to claim 1, characterized in that, The first information is a low-power wake-up signal, which includes a prefix bit and a service type bit. The prefix bit is used to indicate the existence of an emergency service, and the service type bit is used to indicate the service type of the emergency service.

10. The method according to claim 1, characterized in that, The nth MO is the MO in which the first terminal device is located at the current moment.

11. The method according to claim 9, characterized in that, When the service type is a targeted low-latency emergency service, the nth MO is the MO corresponding to the first terminal device, and the nth MO is preempted by the second terminal device, the low-power wake-up signal is also used to indicate a recovery scheduling instruction; the recovery scheduling instruction is used to indicate compensation listening on the mth MO after the nth MO, where m is an integer greater than 0.

12. The method according to claim 11, characterized in that, The first information includes a first subfield and a second subfield, wherein the first subfield indicates the identifier of the first terminal device and the second subfield indicates the value of m.

13. A communication method, characterized in that, The method is applied to a network device, and the method includes: Send a first message, which indicates the existence of an emergency service and the service type of the emergency service, which is either a region-wide broadcast emergency service or a targeted low-latency emergency service; the first message is sent during a monitoring period, the period of which is shorter than the period of discontinuous reception in idle mode.

14. The method according to claim 13, characterized in that, The method further includes: Receive emergency information, which is used to indicate the emergency service.

15. The method according to claim 14, characterized in that, When the emergency information is a public early warning system warning, the service type of the emergency service is the region-wide broadcast emergency service.

16. The method according to claim 14, characterized in that, When the emergency information is data with an ultra-low latency service quality identifier, the service type of the emergency service is the targeted low latency emergency service.

17. The method according to claim 13, characterized in that, The sending of the first information includes: In the case where the service type is the area-wide broadcast emergency service, or in the case where the service type is the targeted low-latency emergency service and the waiting time is greater than the opportunity window, the first information is sent. The waiting time is the time interval between the current moment and the next monitoring time slot (MO) corresponding to the terminal device that needs to receive the targeted low-latency emergency service. The opportunity window is the maximum waiting time of the targeted low-latency emergency service.

18. The method according to claim 13, characterized in that, The monitoring timing is located within the deep sleep time slot between two MOs.

19. The method according to claim 18, characterized in that, The method further includes: Send first configuration information, which is used to indicate the time offset between the monitoring timing and the adjacent MO.

20. The method according to claim 17, characterized in that, The method further includes: Send a second message, which indicates the identifier of the terminal device that needs to receive the targeted low-latency emergency service.

21. The method according to any one of claims 13-20, characterized in that, The method further includes: A first wake-up signal is sent on the (n+1)th MO. The first wake-up signal is a wake-up signal that needs to be sent on the nth MO before the nth MO is preempted. The (n+1)th MO is the next MO after the nth MO.

22. The method according to claim 13, characterized in that, The first information is a low-power wake-up signal, which includes a prefix bit and a service type bit. The prefix bit is used to indicate the existence of the emergency service, and the service type bit is used to indicate the service type of the emergency service.

23. The method according to claim 22, characterized in that, When the service type is a targeted low-latency emergency service, the nth MO is the MO corresponding to the first terminal device, and the nth MO is preempted by the second terminal device, the low-power wake-up signal is also used to indicate a recovery scheduling instruction; the recovery scheduling instruction is used to indicate compensation listening on the mth MO after the nth MO, where m is an integer greater than 0.

24. The method according to claim 23, characterized in that, The first information includes a first subfield and a second subfield. The first subfield indicates the identifier of the terminal device corresponding to the preempted MO, and the second subfield indicates the value of m.

25. A communication device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, the processor being used through logic circuits or executing code instructions to implement the method as claimed in any one of claims 1 to 12, or any one of claims 13 to 24.

26. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as claimed in any one of claims 1 to 12, or any one of claims 13 to 24.

27. A computer program product, characterized in that, Includes instructions that, when executed, cause the method as claimed in any one of claims 1 to 12, or any one of claims 13 to 24, to be implemented.

Images