Communication method and apparatus

Abstract

Disclosed are a communication method and apparatus, relating to the technical field of communications. The method comprises: upon receiving PWS indication information, when GNSS acquisition is triggered and PWS notification reception is not completed, a UE first receives a PWS notification and then performs GNSS acquisition, or first performs GNSS acquisition and, upon acquiring a new GNSS location, acquires the PWS notification by means of a system message or a dedicated RRC message. Therefore, when the UE in an RRC connected state receives the PWS indication information, and the GNSS location of the UE becomes invalid, the behavior of the UE is clarified, thereby ensuring that the UE can both receive PWS alarm message content and perform GNSS acquisition, preventing the UE from entering an RRC idle state.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411587960.2, filed with the State Intellectual Property Office of China on November 7, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Currently, network devices notify terminal devices of a warning notification being broadcast, supporting notifications of system message changes to both idle and connected terminal devices. Upon receiving the Public Warning System (PWS) instruction, PWS-enabled terminal devices retrieve the alarm message content.

[0004] Before connecting to a Non-Terrestrial Network (NTN) cell, the terminal device must possess a valid Global Navigation Satellite System (GNSS) position. In connected mode, the terminal device acquires a new GNSS position to maintain GNSS validity. If the GNSS position becomes invalid, the terminal device enters an idle state. Access layer operations are suspended during GNSS position acquisition.

[0005] Therefore, how can terminal devices ensure GNSS location acquisition and PWS notification acquisition? Summary of the Invention

[0006] This application provides a communication method and apparatus to ensure GNSS location acquisition and PWS notification acquisition.

[0007] In a first aspect, a communication method is provided, which is executed by a terminal device or by a module applied to the terminal device, including: receiving PWS indication information; and receiving a PWS notification when GNSS acquisition is triggered but PWS notification reception is not completed.

[0008] Therefore, when the user equipment (UE) in the connected state of Radio Resource Control (RRC) receives the PWS indication information and the UE's GNSS location also fails, the behavior of the UE is clarified, ensuring that the UE can both receive the PWS alarm message content and perform GNSS acquisition, thus preventing the UE from entering the RRC idle state.

[0009] In one possible implementation, the PWS indication information includes at least one of Earthquake and Tsunami Warning System (ETWS) indication information or Commercial Mobility Warning System (CMAS) indication information. GNSS acquisition is triggered by receiving a GNSS expiration indication, a GNSS Measurement Medium Access Control Channel Unit (GMACC) command, or an uplink transmission extension expiration. The PWS notification includes one or more of the ETWS primary notification, ETWS secondary notification, or CMAS notification. Incomplete PWS notification reception includes not initiating PWS notification reception, or initiating PWS notification reception but not receiving all segments of the PWS notification.

[0010] In another possible implementation, GNSS acquisition is performed after receiving the PWS notification; or, GNSS acquisition is performed after receiving the ETWS main notification.

[0011] Upon receiving a PWS instruction, if GNSS acquisition is triggered but PWS notification reception is incomplete, the terminal device should immediately acquire the PWS notification or continue acquiring it before performing GNSS acquisition. This ensures that the terminal device can both receive the PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering the RRC idle state.

[0012] In another possible implementation, GNSS acquisition is performed after the PWS receive timer expires.

[0013] In another possible implementation, between receiving system message block 1 and the PWS notification, GNSS acquisition is performed according to the implementation of the terminal device, and system message block 1 includes scheduling information for the PWS notification.

[0014] In another possible implementation, GNSS acquisition is performed during the PWS idle period.

[0015] In another possible implementation, GNSS acquisition is performed based on the PWS transmission start time.

[0016] The timing for initiating GNSS acquisition is determined based on the instructions from the network device. This ensures that the terminal device can both receive PWS alarm messages and perform GNSS acquisition, preventing the terminal device from entering the RRC idle state.

[0017] In another possible implementation, the method further includes receiving at least one of PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

[0018] In another possible implementation, receiving PWS notifications includes receiving PWS notifications via a dedicated RRC message after GNSS acquisition is triggered.

[0019] The terminal device does not read or stops reading PWS-related system messages, and obtains PWS notifications from dedicated signaling. This ensures that the terminal device can both receive PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering the RRC idle state.

[0020] Secondly, a communication method is provided, which is executed by a terminal device or by a module applied to the terminal device, including: receiving PWS indication information; and receiving PWS notification via a dedicated RRC message before GNSS acquisition is triggered.

[0021] Based on the remaining GNSS validity period, the network device determines whether to send a PWS notification to the terminal device via a dedicated RRC message. This is to quickly notify the terminal device of the alarm message content, allowing the terminal device to perform GNSS acquisition normally. This ensures that the terminal device can both receive the PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering the RRC idle state.

[0022] Thirdly, a communication method is provided, which is executed by a network device or by a module applied to the network device, including: sending PWS indication information; and sending PWS notification based on the remaining GNSS validity period.

[0023] In one possible implementation, the method further includes sending at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

[0024] In another possible implementation, PWS notification is sent based on the remaining GNSS validity period, including: sending PWS notification via a dedicated Radio Resource Control (RRC) message before GNSS expires, based on the remaining GNSS validity period; or sending PWS notification via a dedicated RRC message upon receiving the reported remaining GNSS validity period.

[0025] Fourthly, a communication method is provided, which is executed by a terminal device or by a module applied to the terminal device, including: receiving PWS indication information, wherein the PWS indication information is at least one of ETWS indication information or Commercial Mobile Warning System (MAS) indication information; performing GNSS acquisition when GNSS acquisition is triggered and PWS notification reception is not completed; and receiving or continuing to receive PWS notification after acquiring a new GNSS location.

[0026] In one possible implementation, receiving PWS notifications includes receiving PWS notifications via dedicated RRC messages or system messages.

[0027] Fifthly, a communication method is provided, which is executed by a terminal device or by a module applied to the terminal device, comprising: receiving a number of PWS alarm message segments; sending a first duration to a network device, the first duration indicating the duration required to obtain a PWS notification, the PWS notification including multiple PWS alarm message segments.

[0028] In a sixth aspect, a communication method is provided, which is executed by a terminal device or by a module applied to the terminal device, comprising: receiving indication information, the indication information including a PWS indication; receiving a PWS notification, the PWS notification including multiple PWS alarm message segments; sending a PWS notification reception start indication and a PWS notification reception completion indication; or, when the last PWS alarm message segment of the PWS notification is received, sending the segment number of the PWS alarm message segment that was not received.

[0029] The UE and network device notify each other of the PWS reception time period, thereby avoiding data scheduling or triggering GNSS acquisition by the network device when the UE receives the PWS. Based on the unreceived segment numbers reported by the UE, the network device efficiently schedules the transmission of alarm message segments, enabling the UE to complete the reception of all alarm message segments more quickly.

[0030] In a seventh aspect, a communication device is provided, the advantages of which can be found in the descriptions of the first to sixth aspects. The communication device has the functions described in the methods of the first to sixth aspects. These functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. In one possible design, the communication device includes a transceiver unit and a processing unit.

[0031] When the communication device is used to implement the functions of the terminal device, the transceiver unit is used to receive first system information indicating the timing of the first PUSCH and to receive PWS indication information; the transceiver unit is also used to receive PWS notification when GNSS acquisition is triggered and PWS notification reception is not completed.

[0032] These modules can perform the corresponding functions in the method examples of the first to sixth aspects above, as detailed in the method examples.

[0033] Eighthly, a communication device is provided, which can be a terminal device as described in the above method embodiments, or a chip disposed in a terminal device. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, it causes the communication device to perform the method executed by the terminal device in the above method embodiments.

[0034] Ninthly, a communication device is provided, which can be a network device in the above method embodiments or a chip disposed in a network device. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, it causes the communication device to perform the method executed by the network device in the above method embodiments.

[0035] In a tenth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when the computer program code is executed, causes the methods executed by the terminal device in the above aspects to be performed.

[0036] In the eleventh aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when run, causes the methods executed by the network device in the above aspects to be performed.

[0037] In a twelfth aspect, a chip system is provided, including a processor for implementing the functions of the terminal device in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing program instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices.

[0038] In a thirteenth aspect, a chip system is provided, comprising a processor for implementing the functions of the network device in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing program instructions and / or data. This chip system may be composed of chips or may include chips and other discrete devices.

[0039] In a fourteenth aspect, a computer-readable storage medium is provided that stores a computer program, which, when run, implements the methods executed by a terminal device in the foregoing aspects.

[0040] In a fifteenth aspect, a computer-readable storage medium is provided that stores a computer program, which, when run, implements the methods executed by a network device in the foregoing aspects.

[0041] The technical effects of any of the implementation methods in aspects seven through fifteen can be found in the technical effects of the corresponding implementation methods in aspects one through six. Attached Figure Description

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

[0043] Figure 2 is a schematic diagram of a base station-side NR protocol stack and network element module provided in this application;

[0044] Figure 3 is a schematic diagram of an O-RAN architecture provided in this application;

[0045] Figure 4 is a flowchart illustrating a communication method provided in this application;

[0046] Figure 5 is a schematic diagram of a GNSS acquisition process provided in this application;

[0047] Figure 6 is a flowchart illustrating another communication method provided in this application;

[0048] Figure 7 is a flowchart illustrating another communication method provided in this application;

[0049] Figure 8 is a flowchart illustrating another communication method provided in this application;

[0050] Figure 9 is a flowchart illustrating another communication method provided in this application;

[0051] Figure 10 is a schematic diagram of the structure of a communication device provided in this application;

[0052] Figure 11 is a schematic diagram of another communication device provided in this application. Detailed Implementation

[0053] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal 120 is wirelessly connected to RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be independent and different physical devices, or they can be the same physical device integrating the logical functions of core network equipment and RAN nodes. The communication system 1000 may also include the Internet 300.

[0054] RAN100 refers to cellular systems related to the 3rd Generation Partnership Project (3GPP), such as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), New Radio (NR) systems, Non-Terrestrial Networks (NTN), or future radio access systems. RAN100 also includes two or more of these different radio access systems. RAN100 can also be an Open RAN (O-RAN or ORAN), a Cloud Radio Access Network (CRAN), or a Wireless Fidelity (WiFi) system, or a converged communication system of two or more of these systems.

[0055] RAN nodes, also known as radio access network devices, network devices, RAN entities, or access nodes, constitute part of a communication system and are used to help terminals access the communication system wirelessly. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN nodes 110 and terminals 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN nodes 110 and terminals 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0056] In one application scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB) in a fifth-generation mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or an indoor station (as shown in Figure 1, 110b), or a relay node or donor node. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All network equipment refers to radio access network equipment.

[0057] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. As shown in Figure 2, for example, RAN nodes can be central units (CUs), distributed units (DUs), CUs (control planes, CPs), CUs (user planes, UPs), or radio units (RUs). Here, the CU performs the functions of the base station's radio resource control (RRC) protocol and packet data convergence protocol (PDCP), and can also perform the service data adaptation protocol (SDAP) function. The DU performs the functions of the base station's radio link control (RLC) layer and media access control (MAC) layer, and can also perform some or all of the physical layer (PHY) functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. Therefore, the CU has RRC, PDCP, and SDAP processing capabilities. The DU has RLC, MAC, and PHY processing capabilities. It is understood that the above functional division is merely an example and does not constitute a limitation on CU and DU. CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). The CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed within the DU, which is centrally controlled by the CU. RU can be used to implement radio frequency signal transmission and reception functions. RU can be included in radio frequency equipment or radio frequency units, such as in remote radio units (RRU), active antenna units (AAU), or remote radio heads (RRH).

[0058] O-RAN aims to achieve an intelligent and open access network. The main features of the O-RAN architecture are hardware and software separation, achieving network function virtualization and hardware standardization. Furthermore, O-RAN incorporates artificial intelligence (AI). Figure 3 shows a schematic diagram of an O-RAN architecture provided in this application.

[0059] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), a CU-CP can be called an O-CU-CP, a CU-UP can be called an O-CU-UP, and an RU can be called an open RU (O-RU). In different systems, CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art will understand their meaning. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.

[0060] The correspondence between the access network equipment (network element modules) of O-RAN and their achievable protocol layer functions can be found in Table 1 below.

[0061] Table 1

[0062] Core network equipment refers to the equipment in the core network (CN) that provides service support to terminals. Examples of core network equipment include: Access and Mobility Management Function (AMF) entities, Session Management Function (SMF) entities, User Plane Function (UPF) entities, etc., which will not be listed here. The AMF entity is responsible for terminal access management and mobility management. The SMF entity is responsible for session management, such as user session establishment. The UPF entity can be a user plane functional entity, mainly responsible for connecting to external networks. In this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and an SMF entity can also be called an SMF network element or an SMF functional entity, etc.

[0063] A terminal is a device with wireless transceiver capabilities, which sends signals to or receives signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0064] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0065] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0066] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0067] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0068] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. To communicate with the base station, the terminal needs to establish a radio connection on a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with this serving cell, it is also susceptible to interference from signals from neighboring cells.

[0069] In the embodiments of this application, the time-domain symbol can be an orthogonal frequency division multiplexing symbol or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol. Unless otherwise specified, the symbols in the embodiments of this application refer to time-domain symbols.

[0070] For ease of understanding, the main terms used in this application are explained.

[0071] A Public Warning System (PWS) is a communication system that broadcasts emergency (warning) information to the public immediately or continuously, indicating impending events and their current status. Examples of public warning systems include the Earthquake and Tsunami Warning System (ETWS) and the Commercial Mobile Alert System (CMAS).

[0072] ETWS is used to send warning notifications to the public related to earthquakes and / or tsunamis. ETWS warning notifications include a primary notification and secondary notifications. For example, the primary notification is a short notification sent within 4 seconds, containing brief information about the event. The secondary notification contains detailed information about the event. CMAS is used to send multiple concurrent warning notifications.

[0073] The evolved universal terrestrial radio access network (E-UTRAN) supports the Common Alarm System (CMAS) through its system information broadcasting capabilities. E-UTRAN is responsible for paging UEs to provide an indication that a warning notification is being broadcast. E-UTRAN sends multiple concurrent CMAS warning notifications to UEs and handles any updates to CMAS warning notifications. The Mobility Management Entity (MME) sends alarm message content to E-UTRAN, which receives alarm message content containing instances of warning notifications. E-UTRAN schedules and broadcasts the alarm message content.

[0074] In the Long Term Evolution (LTE) mechanism, UEs other than Narrowband Internet of Things (NB-IoT) UEs and Bandwidth Reduced Low Complexity (BL) UEs, including normal UEs and UEs in coverage enhancement (UE in CE) mode, receive PWS alarm message content through SystemInformationBlockType10, SystemInformationBlockType11 and SystemInformationBlockType12.

[0075] Primary notifications are broadcast in SystemInformationBlockType10, while secondary notifications are broadcast in SystemInformationBlockType11. CMAS notifications are broadcast in SystemInformationBlockType12. In this document, System Information Block (SIB) is also used to refer to SystemInformationBlockType; both refer to system message blocks.

[0076] In the New Radio (NR) mechanism, the UE receives PWS alarm messages through SystemInformationBlock6-8, and the principle is similar.

[0077] In some embodiments, the UE receives SystemInformationBlockType10 within 4 seconds. Before the E-UTRAN sends the alarm message content, the alarm message content is segmented according to its size. These segments are then sent via SystemInformationBlockType11 and SystemInformationBlockType12. If the UE does not receive all segments of the alarm message content within 3 hours, it continues to receive either SystemInformationBlockType11 or SystemInformationBlockType12 to receive all segments of the ETWS or CMAS alarm message content.

[0078] E-UTRAN notifies the UE to provide a warning notification that is being broadcast, and supports notifying RRC idle UEs and RRC connected UEs of system message changes, that is, it supports notifying RRC idle UEs and RRC connected UEs of ETWS indication and CMAS indication.

[0079] After receiving the ETWS indication or CMAS indication, UEs that support ETWS / CMAS immediately obtain SIB1 (from SIB1, obtain the scheduling information of SIB10 / SIB11 / SIB12) and SIB10 / SIB11 / SIB12. The UE in CE determines when to start obtaining SIB10 based on the UE implementation.

[0080] Before a UE connects to an NTN cell, it needs a valid Global Navigation Satellite System (GNSS) position. When the UE is in RRC connected state, it performs GNSS acquisition to obtain a new GNSS position to maintain GNSS validity. If the UE cannot acquire a valid GNSS position, it enters RRC idle state. In this document, GNSS acquisition is also referred to as GNSS measurement.

[0081] GNSS acquisition can be triggered by the network or the UE. In network-triggered GNSS acquisition, the RAN instructs the UE to trigger GNSS acquisition via the GNSS Measurement Medium Access Control Channel Unit (GNSS Measurement Command MAC CE). In UE-triggered GNSS acquisition, the network configures the UE to enable automatic GNSS acquisition.

[0082] When the UE receives a GNSS expiration indication or when the uplink transmission timer expires (T390 expires), it automatically performs GNSS acquisition. If the GNSS location is outdated and the uplink transmission extension is not activated (T390 timer is not configured, not running, or has expired), GNSS acquisition fails, and the UE enters RRC idle state. When GNSS expires, if GNSS acquisition is not triggered and uplink transmission is not activated, the UE enters RRC idle state. After completing GNSS acquisition, the UE triggers a reporting procedure for the remaining valid GNSS duration.

[0083] When performing GNSS acquisition, the UE suspends access layer operations (e.g., radio link monitoring related timers, data inactivity timers, conditional handover execution, neighbor cell measurement, random access, scheduling requests, buffer status reports).

[0084] When an RRC-connected UE receives an ETWS indication and / or CMAS indication from the network side, and the UE's GNSS location also expires, how the UE can ensure GNSS location acquisition and PWS notification acquisition is an urgent problem to be solved.

[0085] To address the issue of how a UE can ensure both GNSS location acquisition and PWS notification reception, this application provides a communication method. This method includes the UE receiving a PWS indication message, prioritizing the reception of the PWS notification, and then performing GNSS acquisition. For example, the network device determines to send the PWS notification to the UE via a dedicated RRC message based on the remaining GNSS validity period, ensuring that the UE completes the reception of the PWS notification before GNSS acquisition is triggered. Alternatively, after the UE receives the PWS indication, if GNSS acquisition is triggered but PWS notification reception is incomplete, the UE can immediately acquire or continue acquiring the PWS notification before performing GNSS acquisition. The timing of initiating GNSS acquisition can also be determined based on the network device's indication information, or the UE can obtain the PWS notification from dedicated signaling without reading PWS-related system messages. Alternatively, after receiving the PWS indication message, the UE first performs GNSS acquisition, and after acquiring the new GNSS location, obtains the PWS notification via system messages or dedicated RRC messages. Therefore, when the UE receives the PWS indication information in the RRC connected state and the UE's GNSS location also fails, the behavior of the UE is clarified, ensuring that the UE can both receive the PWS alarm message content and perform GNSS acquisition, thus preventing the UE from entering the RRC idle state.

[0086] The implementation of the communication method provided in this application will now be described in detail with reference to the accompanying drawings.

[0087] Next, the method for prioritizing UE reception of PWS notifications to ensure GNSS location acquisition and PWS notification acquisition will be described in detail. The terminal device establishes an RRC connection with the network device, and the terminal device is in a connected state. The terminal device and network device are, for example, the terminal and base station shown in Figure 1. As shown in Figure 4, the method includes the following steps.

[0088] Step 410: The network device sends PWS indication information. Correspondingly, the terminal device receives the PWS indication information.

[0089] The PWS indication information includes at least one of ETWS indication information or CMAS indication information.

[0090] Network devices send PWS indication information using different messages based on the status of the terminal device. For example, E-UTRAN notifies the UE of ETWS indication and CMAS indication in the following way.

[0091] In the RRC idle state, E-UTRAN sends ETWS indication and CMAS indication to UEs (except NB-IoT UEs) via paging messages. It also sends ETWS and CMAS indications to BL UEs and UEs in CE via Direct Indication Information messages (transmitted on the Narrowband Physical Downlink Control Channel, NPDCCH), scrambled with the Physical Radio Network Temporary Identifier (P-RNTI).

[0092] In RRC connected state, E-UTRAN sends ETWS indication and / or CMAS indication to UE (except NB-IoT UEs, BL UEs, and UEs in CE) via paging messages.

[0093] In RRC connected state, E-UTRAN sends ETWS and / or CMAS indications to UEs in CE via Direct Indication Information messages (transmitted in NPDCCH), scrambled with System Information RNTI (SI-RNTI).

[0094] Step 420: The network device sends at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time. Correspondingly, the terminal device receives at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

[0095] The network device indicates to the UE at least one of the following via Direct Indication Information message, paging message, or SIB1 message: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

[0096] Optionally, the network device may send PWS indication information and at least one of PWS receive timer configuration information, PWS idle time period, or PWS transmission start time via Direct Indication Information message or Paging message.

[0097] Optionally, the network device sends PWS indication information via a Direct Indication Information message or a Paging message. It also sends at least one of the following via SIB1: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time; that is, SIB1 carries at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

[0098] Optionally, the communication method steps provided in the embodiments of this application may be appropriately adjusted, for example, by adjusting the order of the steps, adding or removing steps, etc. For example, the order of steps 410 and 420 can be interchanged, that is, the network device executes step 420 first, then step 410. Or steps 410 and 420 can be executed simultaneously. Alternatively, the network device may not execute step 420, that is, it may not send at least one of the following to the terminal device: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application.

[0099] Step 430: The network device sends a PWS notification. Correspondingly, the terminal device receives the PWS notification. If GNSS acquisition is triggered but PWS notification reception is incomplete, the terminal device receives the PWS notification.

[0100] PWS notifications include at least one of ETWS primary notifications, ETWS secondary notifications, or CMAS notifications. Terminal devices receive PWS notifications via system messages or dedicated RRC messages. For example, a network device broadcasts one or more of SystemInformationBlockType10, SystemInformationBlockType11, and SystemInformationBlockType12. SystemInformationBlockType10 carries the ETWS primary notification, SystemInformationBlockType11 carries the ETWS secondary notification, and SystemInformationBlockType12 carries the CMAS notification. Terminal devices receive one or more of SystemInformationBlockType10, SystemInformationBlockType11, and SystemInformationBlockType12 to obtain the PWS notification. The PWS notification represents the alarm message content, i.e., the terminal device obtains the alarm message content. Alternatively, a network device sends a dedicated RRC message carrying the alarm message content, and the terminal device receives the dedicated RRC message to obtain the alarm message content.

[0101] GNSS acquisition is triggered when a GNSS expiration indication is received, or a GNSS measurement MAC CE is received, or an uplink transmission extension expires (T390 expiration).

[0102] For example, a GNSS expiration indication means that the GNSS validity period has expired. When the GNSS validity period expires, GNSS acquisition is triggered, and the terminal device performs GNSS acquisition.

[0103] For example, if the GNSS validity period expires and the uplink transmission extension expires, GNSS acquisition is triggered, and the terminal device performs GNSS acquisition.

[0104] For example, a network device sends a GNSS Measurement Command MAC CE to a terminal device, instructing the terminal device to trigger GNSS acquisition. Upon receiving the GNSS Measurement Command MAC CE, the terminal device triggers GNSS acquisition and performs the acquisition.

[0105] Incomplete PWS notification reception can occur when PWS notification reception is not initiated, or when PWS notification reception is initiated but not all segments or alarm message content of the PWS notification are received. For example, not initiating PWS notification reception means not starting to acquire one or more of SIB10, SIB11, and SIB12, which may include not acquiring SIB1, or acquiring SIB1 but not acquiring one or more of SIB10, SIB11, and SIB12. When GNSS acquisition is triggered but PWS notification reception is incomplete, the terminal device prioritizes receiving the PWS notification before performing GNSS acquisition. For example, when the terminal device receives a PWS indication, the UE determines that GNSS acquisition has been triggered. As described above, when GNSS acquisition is triggered, the UE immediately acquires SIB1 and one or more of SIB10, SIB11, and SIB12. Alternatively, after receiving the PWS indication, if the UE acquires SIB1 but has not yet acquired one or more of SIB10, SIB11, and SIB12, and the UE determines that GNSS acquisition has been triggered, the UE acquires one or more of SIB10, SIB11, and SIB12 according to the scheduling information of SIB1. Alternatively, after receiving the PWS indication, if the UE acquires SIB1 and one or more of SIB10, SIB11, and SIB12, but has not received all segments of the alarm message, and the UE determines that GNSS acquisition has been triggered, the UE continues to acquire one or more of SIB10, SIB11, and SIB12.

[0106] The following provides several possible implementation methods for receiving PWS notifications.

[0107] In the first possible implementation, GNSS acquisition is performed after the terminal device has completed receiving the PWS notification.

[0108] In some embodiments, as shown in FIG5(a), the network device sends a PWS notification through at least one of SIB10, SIB11, or SIB12. The terminal device receives at least one of SIB10, SIB11, or SIB12 and then performs GNSS acquisition. The UE first acquires SIB1 and obtains scheduling information from SIB1. The scheduling information in SIB1 indicates the presence of at least one of SIB10, SIB11, and SIB12, that is, the network side sends at least one of SIB10, SIB11, and SIB12. After the terminal device receives the PWS notification sent by the network side through the SIB, it performs GNSS acquisition.

[0109] For example, the scheduling information in SIB1 indicates the existence of SIB10, SIB11, and SIB12, meaning that the network device has sent SIB10, SIB11, and SIB12. After the terminal device has finished receiving SIB10, SIB11, and SIB12, it performs GNSS acquisition.

[0110] For example, the scheduling information in SIB1 indicates the existence of SIB10, meaning that the network device sent SIB10. After the terminal device completes receiving SIB10 and SIB10, it performs GNSS acquisition.

[0111] For example, the scheduling information in SIB1 indicates the existence of SIB11, meaning that the network device sent SIB11. After the terminal device completes receiving SIB10 and SIB11, it performs GNSS acquisition.

[0112] For example, after the network device sends SIB10 and SIB11, the terminal device performs GNSS acquisition after receiving SIB10 and SIB11.

[0113] For example, after the network device sends SIB12, the terminal device performs GNSS acquisition after receiving SIB12.

[0114] For example, the scheduling information in SIB1 indicates the existence of SIB10 / SIB11 (one of SIB10 and SIB11) and SIB12, that is, the network device sends SIB10 / SIB11 and SIB12, and after the terminal device completes receiving SIB10 / SIB11 and SIB12, it performs GNSS acquisition.

[0115] For example, the scheduling information in SIB1 indicates the existence of SIB12, meaning that the network device sent SIB12. After the terminal device completes receiving SIB12, it performs GNSS acquisition.

[0116] In the second possible implementation, the terminal device performs GNSS acquisition after receiving the ETWS master notification.

[0117] As shown in Figure 5(b), for example, the network device sends SIB10, SIB11, and SIB12. After the terminal device completes receiving SIB10, it performs GNSS acquisition. After obtaining the new GNSS location, the terminal device receives SIB11 and SIB12.

[0118] For example, the network device sends SIB10 and SIB11 / SIB12. After the terminal device receives SIB10, it performs GNSS acquisition. After obtaining the new GNSS location, the terminal device receives SIB11 / SIB12.

[0119] For example, when a network device sends SIB11 / SIB12, the terminal device performs GNSS acquisition, obtains the new GNSS location, and then receives SIB11 / SIB12.

[0120] In the third possible implementation, GNSS acquisition is performed after the PWS receive timer expires.

[0121] The PWS receive timer indicates the duration for receiving PWS notifications, i.e., the time window for receiving PWS notifications. The network device sends PWS receive timer configuration information, which is then received by the terminal device. The PWS receive timer configuration information indicates the duration for receiving PWS notifications. The terminal device configures the PWS receive timer. When the PWS receive timer expires, the terminal device performs GNSS acquisition. For example, after completing GNSS acquisition, the UE continues to receive PWS notifications, either through system messages or dedicated RRC messages.

[0122] For example, as shown in Figure 5(c), after the PWS receive timer expires, GNSS acquisition is performed even if the terminal device has not received all segments of the alarm message content notified by the PWS. This avoids the terminal device waiting to receive all segments of the alarm message content, which could cause the GNSS validity period to expire and the terminal device to enter an idle state.

[0123] Optionally, during the PWS receive timer operation (before timeout), if the terminal device receives all segments of the alarm message content, the terminal device performs GNSS acquisition.

[0124] In a fourth possible implementation, GNSS acquisition is performed between receiving SIB1 and the PWS notification, depending on the terminal device's implementation. SIB1 includes scheduling information for the PWS notification.

[0125] As shown in Figure 5(d), the network device sends a PWS notification through at least one of SIB10, SIB11, or SIB12. The scheduling information of the PWS notification indicates the time-frequency resources of SIB10, SIB11, and SIB12, such as the period. The terminal device first obtains the scheduling information from SIB1 to enable the terminal device to receive at least one of SIB10, SIB11, or SIB12, i.e., to receive the PWS notification.

[0126] There is a time interval between the terminal device receiving SIB1 and PWS notifications, during which the terminal device performs GNSS acquisition. Understandably, due to differences in the moving speed of terminal devices or the capabilities of terminal devices from different manufacturers, the time required for the terminal device to acquire a new GNSS location will vary. If the terminal device determines that it can acquire a new GNSS location within this time interval, it will perform GNSS acquisition. Some terminal devices may not be able to acquire a new GNSS location within this time interval, in which case the terminal device does not need to perform GNSS acquisition during this interval.

[0127] In the fifth possible implementation, GNSS acquisition is performed during the PWS idle period.

[0128] The PWS idle period is the time period during which the network device does not send PWS notifications. For example, as shown in Figure 5(e), the network device divides the alarm message content into multiple segments. The network device sends multiple segments of the PWS notification according to a periodic time interval (e.g., the periodic time interval is 8, 16, 32 or 64 radio frames, etc.). That is, after the network device sends the i-th segment, it waits for a time interval before sending the (i+1)-th segment, where i is a positive integer greater than or equal to 1.

[0129] Since the network device does not send PWS notifications during the PWS idle period, the terminal device does not need to receive PWS notifications and performs GNSS acquisition.

[0130] In the sixth possible implementation, GNSS acquisition is performed based on the PWS transmission start time.

[0131] The PWS transmission start time indicates the time when the PWS notification is sent. When the network device sends the PWS transmission start time and the terminal device receives it, the terminal device knows when the network device sent the PWS notification. When the network device does not send a PWS notification, the terminal device does not need to receive the PWS, and the terminal device determines when to initiate GNSS acquisition. For example, as shown in Figure 5(f), before the PWS transmission start time, if the terminal device determines that it can acquire a new GNSS location before the PWS transmission start time, the terminal device performs GNSS acquisition.

[0132] In the seventh possible implementation, after GNSS acquisition is triggered, PWS notification is received via a dedicated RRC message.

[0133] Upon receiving a PWS indication, if GNSS acquisition is triggered but PWS notification reception is incomplete (e.g., receiving a GNSS failure indication or a GNSS measurement indication from the network side), and the terminal device does not start PWS notification reception or has not received a complete PWS notification, the terminal device may not immediately acquire, not acquire, or stop acquiring at least one of SIB1, SIB10, SIB11, or SIB12. The terminal device will then perform GNSS acquisition. The network device will notify the terminal device in RRC connected state of the PWS alarm message content via a dedicated RRC message. The terminal device will receive the dedicated RRC message to receive the PWS alarm message content.

[0134] In some embodiments, as shown in Figure 5(g), the terminal device performs GNSS acquisition. After acquiring the new GNSS location, it reports the remaining GNSS validity period to the network device. Upon learning that GNSS acquisition is complete, the network device sends a PWS notification to the terminal device via a dedicated RRC message. Compared to sending the PWS notification via a system message, using a dedicated RRC message allows the terminal device to obtain the alarm message content included in the PWS notification more quickly.

[0135] In the eighth possible implementation, the PWS notification is obtained when the terminal device enters the RRC idle state.

[0136] The network device sends a PWS notification through at least one of SIB10, SIB11 or SIB12, and the terminal device leaves the RRC connected state and enters the RRC idle state, receiving at least one of SIB10, SIB11 or SIB12.

[0137] The communication method provided in this application, after the terminal device receives a PWS indication, determines the actions of both the network device and the terminal device when GNSS acquisition is likely to be triggered or has already been triggered. Based on the remaining GNSS validity period, the network device decides to send a PWS notification to the terminal device via a dedicated RRC message; or, upon receiving the PWS indication and GNSS acquisition being triggered, the terminal device immediately acquires or continues acquiring the PWS notification before performing GNSS acquisition; or, based on the network device's indication information, determines when to initiate GNSS acquisition; or, the terminal device does not read PWS-related system messages but acquires the PWS notification from dedicated signaling. This ensures that the terminal device can both receive the PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering an RRC idle state.

[0138] In other embodiments, the network device determines to send a PWS notification to the terminal device via a dedicated RRC message based on the remaining GNSS validity time reported by the terminal device, in order to indicate the content of the PWS alarm message to the terminal device. Figure 6 shows a schematic diagram of another communication method provided in this application.

[0139] Step 610: The network device sends PWS indication information. Correspondingly, the terminal device receives the PWS indication information.

[0140] The PWS indication information includes at least one of ETWS indication information or CMAS indication information. For an explanation of how the network device sends the PWS indication information, please refer to the description in step 410.

[0141] Step 620: Based on the remaining GNSS validity period, the network device sends a PWS notification via a dedicated RRC message before the GNSS expires. Correspondingly, before GNSS acquisition is triggered, the terminal device receives the PWS notification via a dedicated RRC message.

[0142] The terminal device performs GNSS acquisition. After acquiring the new GNSS location, it reports the remaining GNSS validity period to the network device. Knowing the remaining GNSS validity period, the network device sends a PWS notification via a dedicated RRC message before the GNSS expires, ensuring the terminal device receives the PWS notification promptly via the dedicated RRC message. This effectively shortens the latency for the terminal device to receive the PWS notification. It ensures the terminal device can both receive the PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering an RRC idle state.

[0143] Next, the method for prioritizing GNSS acquisition by the UE to ensure GNSS location acquisition and PWS notification acquisition will be described in detail. The terminal device establishes an RRC connection with the network device, and the terminal device is in a connected state. The terminal device and network device are, for example, the terminal and base station shown in Figure 1. As shown in Figure 7, the method includes the following steps.

[0144] Step 710: The network device sends PWS indication information. Correspondingly, the terminal device receives the PWS indication information.

[0145] The PWS indication information includes at least one of ETWS indication information or CMAS indication information. For an explanation of how the network device sends the PWS indication information, please refer to the description in step 410.

[0146] Step 720: The network device sends a PWS notification. Correspondingly, the terminal device receives the PWS notification. If GNSS acquisition is triggered but PWS notification reception is incomplete, the terminal device performs GNSS acquisition, and after acquiring the new GNSS location, receives or continues to receive PWS notifications.

[0147] PWS notifications include at least one of ETWS primary notifications, ETWS secondary notifications, or CMAS notifications. Network devices send PWS notifications via system messages or dedicated RRC messages. PWS notifications include alarm message content. For example, network devices may broadcast one or more of SIB10, SIB11, or SIB12. Alternatively, network devices may send dedicated RRC messages carrying alarm message content.

[0148] If GNSS acquisition is triggered but PWS notification reception is incomplete, the terminal device performs GNSS acquisition. After acquiring the new GNSS location, it receives or continues to receive PWS notifications. In some embodiments, the terminal device receives PWS notifications via dedicated RRC messages or system messages.

[0149] For example, the terminal device receives one or more of SIB10, SIB11, or SIB12 to obtain the alarm message content. The terminal device receives a dedicated RRC message to obtain the alarm message content.

[0150] For example, after the terminal device completes GNSS acquisition, it can initiate the reception of PWS notifications based on the terminal device.

[0151] In some embodiments, when a terminal device receives a dedicated RRC message to obtain alarm message content, the network device sends a dedicated RRC message to the terminal device after receiving a GNSS validity period remaining time report.

[0152] Among them, GNSS acquisition is triggered when a GNSS expiration indication is received, or a GNSS measurement MAC CE is received, or an uplink transmission extension expires (T390 expiration).

[0153] The communication method provided in this application, upon receiving a PWS indication, determines the behavior of the network device and the terminal device when GNSS acquisition is likely to be triggered or has already been triggered. The terminal device performs GNSS acquisition and then acquires the PWS notification via system message or dedicated RRC message. This ensures that the terminal device can both receive the PWS alarm message content and perform GNSS acquisition, preventing the terminal device from entering the RRC idle state.

[0154] Next, the time period required for the network device to obtain the PWS notification received by the terminal device will be described in detail. The terminal device establishes an RRC connection with the network device, and the terminal device is in a connected state. The terminal device and network device are, for example, the terminal and base station shown in Figure 1. As shown in Figure 8, the method includes the following steps.

[0155] Step 810: The network device sends PWS indication information. Correspondingly, the terminal device receives the PWS indication information.

[0156] The PWS indication information includes at least one of ETWS indication information or CMAS indication information. For an explanation of how the network device sends the PWS indication information, please refer to the description in step 410.

[0157] Step 820: Number of PWS alarm message segments sent by the network device. Correspondingly, number of PWS alarm message segments received by the terminal device.

[0158] The network device segments the alarm message content according to its size. This application does not limit the number of segments.

[0159] The network device indicates the number of PWS alarm message segments to the UE via Direct Indication Information, paging, or SIB1 messages.

[0160] Optionally, the network device may send PWS indication information and the number of PWS alarm message segments via Direct Indication Information messages or Paging messages.

[0161] Optionally, the network device sends PWS indication information via Direct Indication Information messages or Paging messages. The number of PWS alarm message segments sent via SIB1 is the number of PWS alarm message segments carried by SIB1.

[0162] Step 830: The terminal device sends a first duration, which indicates the duration required to obtain the PWS notification. Correspondingly, the network device receives the first duration.

[0163] The terminal device assesses, calculates, or determines the time required to acquire all PWS segments based on the number of PWS alarm message segments. The terminal device then reports the duration required to acquire the PWS notification to the network device.

[0164] In some embodiments, the terminal device determines the duration required to receive one segment, and further determines the time required to acquire all segments of the PWS.

[0165] Step 840: The network device sends a PWS notification. Correspondingly, the terminal device receives the PWS notification.

[0166] Network devices send PWS notifications via system messages or dedicated RRC messages. A PWS notification consists of multiple PWS alarm message segments. The network device sends these multiple PWS alarm message segments. The terminal device receives these multiple PWS alarm message segments. The time required for the terminal device to receive these multiple PWS alarm message segments is the first duration.

[0167] Therefore, based on the number of alarm message segments provided by the network device, the time required for the terminal device to report and receive PWS is reduced, thus avoiding data scheduling or triggering the terminal device to perform GNSS acquisition when the terminal device receives PWS.

[0168] Next, the time period required for the network device to obtain the PWS notification received by the terminal device will be described in detail. The terminal device establishes an RRC connection with the network device, and the terminal device is in a connected state. The terminal device and network device are, for example, the terminal and base station shown in Figure 1. As shown in Figure 9, the method includes the following steps.

[0169] Step 910: The network device sends PWS indication information. Correspondingly, the terminal device receives the PWS indication information.

[0170] The PWS indication information includes at least one of ETWS indication information or CMAS indication information. For an explanation of how the network device sends the PWS indication information, please refer to the description in step 410.

[0171] Step 920: The network device sends a PWS notification. Correspondingly, the terminal device receives the PWS notification.

[0172] Network devices send PWS notifications via system messages or dedicated RRC messages. Each PWS notification consists of multiple PWS alarm message segments. The network device sends these multiple PWS alarm message segments, and the terminal device receives them. The time required for the terminal device to receive these multiple PWS alarm message segments is the first duration.

[0173] Step 930: The terminal device sends a PWS notification reception start indication and a PWS notification reception completion indication. Correspondingly, the network device receives the PWS notification reception start indication and the PWS notification reception completion indication.

[0174] Upon the terminal device starting to receive the first segment, a PWS notification indicating reception initiation is sent. After the terminal device has received all segments, a PWS notification indicating reception completion is sent. This allows the network device to know the time period during which the terminal device receives PWS, thereby avoiding data scheduling or triggering the terminal device to perform GNSS acquisition while it is receiving PWS.

[0175] Step 940: The terminal device sends the segment number of the last PWS alarm message segment it received when it received the PWS notification, and sends the segment number of the segment for which no PWS alarm message was received. Correspondingly, the network device receives the segment number of the segment for which no PWS alarm message was received.

[0176] The terminal device may receive the last PWS alarm message segment of the PWS notification first, or it may not receive the other PWS alarm message segments. In this case, the terminal device sends the segment number of the PWS alarm message segment that was not received.

[0177] This allows network devices to schedule the transmission of segments, enabling terminal devices to receive all segments more quickly.

[0178] Optionally, the communication method steps provided in the embodiments of this application may be appropriately adjusted. For example, steps may be added or removed. For instance, the terminal device may execute only one or all of steps 930 and 940. The terminal device may execute only step 930. Alternatively, the terminal device may execute only 940. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application.

[0179] This clarifies the time period or status of PWS reception that the terminal device indicates to the network device. The terminal device and network device communicate the PWS reception time period, thus avoiding data scheduling or triggering GNSS acquisition by the network device while the terminal device is receiving PWS. Based on the unreceived segment numbers reported by the terminal device, the network device efficiently schedules the transmission of alarm message segments, enabling the terminal device to complete the reception of all alarm message segments more quickly.

[0180] It is understood that, in order to achieve the functions in the above embodiments, the network device and terminal device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0181] Figures 10 and 11 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of terminal devices or network devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the terminal 120 shown in Figure 1, the base station 110 shown in Figure 1, or a module (such as a chip) applied to a terminal device or network device.

[0182] As shown in Figure 10, the communication device 1000 includes a processing unit 1010 and a transceiver unit 1020. The communication device 1000 is used to implement the functions of the terminal device or network device in the method embodiments shown in Figures 4, 6 to 9 above.

[0183] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in FIG4: the transceiver unit 1020 is used to perform the steps of obtaining GNSS location and PWS notification, and the processing unit 1010 is used to process the PWS notification.

[0184] When the communication device 1000 is used to implement the function of the network device in the method embodiment shown in FIG4: the transceiver unit 1020 is used to execute steps 410, 420 and 430; the processing unit 1010 is used to process the PWS notification.

[0185] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in FIG6: the transceiver unit 1020 is used to perform the steps of obtaining GNSS location and PWS notification, and the processing unit 1010 is used to process the PWS notification.

[0186] When the communication device 1000 is used to implement the function of the network device in the method embodiment shown in FIG6: the transceiver unit 1020 is used to execute steps 610 and 620; the processing unit 1010 is used to process the PWS notification.

[0187] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in FIG7: the transceiver unit 1020 is used to perform the steps of obtaining GNSS location and PWS notification, and the processing unit 1010 is used to process the PWS notification.

[0188] When the communication device 1000 is used to implement the function of the network device in the method embodiment shown in FIG7: the transceiver unit 1020 is used to execute steps 710 and 720; the processing unit 1010 is used to process the PWS notification.

[0189] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in FIG8: the transceiver unit 1020 is used to execute step 830, and the processing unit 1010 is used to process the PWS notification.

[0190] When the communication device 1000 is used to implement the functions of the network device in the method embodiment shown in FIG8: the transceiver unit 1020 is used to execute steps 810, 820 and 840; the processing unit 1010 is used to process the PWS notification.

[0191] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in FIG9: the transceiver unit 1020 is used to execute step 930, and the processing unit 1010 is used to process the PWS notification.

[0192] When the communication device 1000 is used to implement the functions of the network device in the method embodiment shown in FIG9: the transceiver unit 1020 is used to execute steps 910, 920 and 940; the processing unit 1010 is used to process the PWS notification.

[0193] For a more detailed description of the above-mentioned processing unit 1010 and transceiver unit 1020, please refer to the relevant descriptions in the method embodiments shown in Figures 4, 6 to 9.

[0194] As shown in Figure 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 can be a transceiver or an input / output interface. Optionally, the communication device 1100 may also include a memory 1130 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute instructions, or storing data generated after the processor 1110 executes instructions. Sometimes, the interface circuit 1120 can also be understood as part of the processor 1110, in which case the communication device 1100 includes the processor 1110.

[0195] When the communication device 1100 is used to implement the method shown in FIG4, FIG6 to FIG9, the processor 1110 is used to implement the function of the processing unit 1010, and the interface circuit 1120 is used to implement the function of the transceiver unit 1020.

[0196] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from the base station, which can be understood as the information being first received by other modules in the terminal (such as an RF module or antenna), and then sent to the terminal chip by these modules. The terminal chip sends information to the base station, which can be understood as the information being first sent to other modules in the terminal (such as an RF module or antenna), and then sent to the base station by these modules.

[0197] When the aforementioned communication device is a chip applied to a base station, the base station chip implements the functions of the base station in the above method embodiments. The base station chip receives information from the terminal, which can be understood as the information being first received by other modules in the base station (such as an RF module or antenna), and then sent to the base station chip by these modules. The base station chip sends information to the terminal, which can be understood as the information being sent down to other modules in the base station (such as an RF module or antenna), and then sent to the terminal by these modules.

[0198] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0199] It is understood that the processor in the embodiments of this application can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0200] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, optical discs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the ASIC can reside in a base station or terminal. The processor and the storage medium can also exist as discrete components in the base station or terminal.

[0201] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0202] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0203] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can 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. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0204] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, include: Receive indication information from the Public Warning System (PWS); If GNSS acquisition is triggered but PWS notification reception is incomplete, receive or continue to receive PWS notifications.

2. The method according to claim 1, characterized in that, The PWS indication information includes at least one of Earthquake and Tsunami Warning System indication information or Commercial Mobile Early Warning System (CMAS) indication information; The triggering of GNSS acquisition includes receiving a GNSS expiration indication, receiving a GNSS measurement medium access control channel unit command, or an uplink transmission extension expiration. The situations in which PWS notification reception is incomplete include not starting PWS notification reception, or starting PWS notification reception but not receiving all segments of the PWS notification; The PWS notification includes one or more of the following: ETWS main notification, ETWS secondary notification, or CMAS notification.

3. The method according to claim 1 or 2, characterized in that, After receiving the PWS notification, perform GNSS acquisition; or, After receiving the ETWS master notification, GNSS acquisition is performed.

4. The method according to claim 1 or 2, characterized in that, After the PWS receive timer expires, GNSS acquisition is performed.

5. The method according to claim 1 or 2, characterized in that, Between receiving system message block 1 and the PWS notification, GNSS acquisition is performed according to the implementation of the terminal device. System message block 1 includes the scheduling information of the PWS notification.

6. The method according to claim 1 or 2, characterized in that, GNSS acquisition is performed during PWS idle periods.

7. The method according to claim 1 or 2, characterized in that, GNSS acquisition is performed based on the PWS transmission start time.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: Receive at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

9. The method according to claim 1, characterized in that, Receive PWS notifications, including: After GNSS acquisition is triggered, the PWS notification is received via a Dedicated Radio Resource Control (RRC) message.

10. A communication method, characterized in that, include: Receive indication information from the Public Warning System (PWS); Before GNSS acquisition is triggered, PWS notifications are received via Dedicated Radio Resource Control (RRC) messages.

11. A communication method, characterized in that, include: Send Public Warning System (PWS) indication information; PWS notifications are sent based on the remaining validity period of the Global Navigation Satellite System (GNSS).

12. The method according to claim 11, characterized in that, The method further includes: Send at least one of the following: PWS receive timer configuration information, PWS idle time period, or PWS transmission start time.

13. The method according to claim 11 or 12, characterized in that, Send PWS notifications based on the remaining validity period of the Global Navigation Satellite System (GNSS), including: Based on the remaining validity period of the GNSS, the PWS notification is sent via a Dedicated Radio Resource Control (RRC) message before the GNSS expires. or, Upon receiving the reported remaining GNSS validity period, the PWS notification is sent via a dedicated RRC message.

14. A communication method, characterized in that, include: Receive Public Warning System (PWS) indication information, wherein the PWS indication information is at least one of Earthquake and Tsunami Warning System (ETWS) indication information or Commercial Mobile Warning System (CMAS) indication information; If GNSS acquisition is triggered but PWS notification reception is not completed, GNSS acquisition is performed. After acquiring the new GNSS position, PWS notifications are received or reception continues.

15. The method according to claim 14, characterized in that, Retrieve PWS notifications, including: The PWS notification is received via Dedicated Radio Resource Control (RRC) messages or system messages.

16. A communication method, characterized in that, include: Number of segments of Public Warning System (PWS) alarm messages received; A first duration is sent to the network device, the first duration being used to indicate the duration required to obtain the PWS notification, the PWS notification including multiple PWS alarm message segments.

17. A communication method, characterized in that, include: Receive indication information, the indication information including Public Warning System (PWS) indication; Receive a PWS notification, wherein the PWS notification includes multiple PWS alarm message segments; Send the PWS notification reception start indication and the PWS notification reception completion indication; Alternatively, when the last PWS alarm message segment of the PWS notification is received, the segment number of the segment for which no PWS alarm message segment was received is sent.

18. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, and the processor is used to implement the method as described in any one of claims 1 to 17 through logic circuits or execution code instructions.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 17.

20. A computer program product, characterized in that, The computer program product includes a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 17.

Images