Communication method and communication apparatus
By using RRC release messages carrying PWS information in the wireless communication system, the problem of NB-IoT terminals being unable to receive PWS information in a timely manner is solved, enabling direct reception of PWS information in the connected state and improving the timeliness and efficiency of information.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2025-12-30
- Publication Date
- 2026-07-30
AI Technical Summary
In existing communication systems, NB-IoT terminals cannot receive Public Alarm System (PWS) information in a timely manner when connected, and the need to detect paging messages in the idle state causes a delay in receiving PWS information.
By introducing RRC release messages into the wireless communication system, which carry trigger information related to PWS information, such as PWS type, location, and time-frequency resources, the terminal is directly triggered to switch from the connected state to the idle state to receive PWS information. In the connected state, the PWS information can be directly obtained through system messages, thus avoiding data communication conflicts.
This enables NB-IoT terminals to receive PWS information in a timely manner while in connected mode, reducing latency, improving the timeliness and reception efficiency of PWS information, and avoiding data communication conflicts.
Smart Images

Figure CN2025147152_30072026_PF_FP_ABST
Abstract
Description
Communication methods and communication devices
[0001] This application claims priority to Chinese Patent Application No. 202510125246.X, filed on January 24, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communications, and more particularly to communication methods and communication devices. Background Technology
[0003] A public warning system (PWS) is a dedicated mechanism for broadcasting emergency alerts and public safety notifications. In emergency situations, it can be used to transmit critical information, which can be referred to as PWS messages.
[0004] In a communication system, after receiving PWS information, the network-side device sends PWS information to the terminal through a system message. The network-side device also indicates a change in the system message in the paging message. After detecting the paging message, the terminal learns from the indication in the paging message that the system message has changed and receives the system message, thereby receiving the PWS information.
[0005] However, this method of transmitting PWS information has the problem that the terminal cannot receive the PWS information in a timely manner. Summary of the Invention
[0006] This application provides a communication method and a communication device, which helps the terminal to obtain PWS information in a timely manner.
[0007] Firstly, a communication method is provided, which can be executed by a first communication device. The first communication device can be a communication equipment, or a device within the communication equipment (e.g., a module, communication module, circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip), a chip system, or a processor), or a logical node, logical module, or software capable of implementing all or part of the functions of the communication equipment. As an example, the communication equipment is an access network device or a core network device.
[0008] The method includes: receiving PWS information; sending a first message, wherein the first message is associated with the first information, and the first information is used to trigger the terminal to receive the PWS information.
[0009] In this application, the first information is used to trigger the terminal to receive PWS information, which can also be understood as the first information being used to instruct the terminal to receive PWS information, or the first information being used to inform the terminal that "the network side has sent PWS information". Based on this scheme, the terminal can promptly know that the network side has sent PWS information, and thus can promptly receive PWS information in scenarios where it is necessary to receive PWS information.
[0010] In some possible designs, PWS information is carried as system messages.
[0011] In one possible design, the first message is a radio resource control (RRC) release message. Using an RRC release message to instruct the terminal to receive PWS information helps terminals with limited capabilities and in a connected state to promptly switch to an idle state to receive PWS information.
[0012] In one possible design, the first piece of information includes the RRC release reason. This design reuses existing fields in the RRC to indicate to the terminal that it is receiving PWS information, which helps to save transmission overhead and reduce the implementation complexity of the scheme.
[0013] In one possible design, the reasons for RRC release include: PWS type, or the location of the PWS information in the system message, or the time-frequency resource where the PWS information is located, or the master message of the Earthquake and Tsunami Warning System (ETWS).
[0014] In this design, by using the PWS type, the position of the PWS information in the system message, the time-frequency resource where the PWS information is located, or the main message of ETWS, the terminal is implicitly instructed to receive the PWS information, and additional information related to the PWS information is also provided to the terminal, thereby saving signaling overhead.
[0015] For example, if the RRC release reason includes the PWS type, the terminal can not only know that the network side sent PWS information based on the RRC release reason, but also know the PWS type. In this way, the terminal can understand the urgency of the event based on the PWS type. In cases where the event is highly urgent, this can help the terminal avoid missing PWS information.
[0016] For example, if the RRC release reason includes the ETWS master message, based on the RRC release reason, it can not only know that the network side sent PWS information, but also that the type of the PWS information sent by the network side is ETWS, and further, it can obtain the content of the ETWS master message. In this way, the terminal can determine the urgency of the PWS information based on the type of the PWS information, thereby determining whether it needs to receive the PWS information; furthermore, if it is determined to receive the PWS information, since the content of the ETWS master message has already been received, the efficiency of receiving the PWS information can be saved and the transmission overhead of transmitting the ETWS master message through other messages can be avoided.
[0017] In one possible design, the first message is used to trigger the terminal to receive a system message, which includes PWS information. As an example, the terminal is in a connected state. As another example, the first message is UE-level signaling.
[0018] Based on this possible design, a terminal in the connected state can be triggered to receive system messages without switching to the idle state, thereby receiving the PWS information carried in the system messages, and thus enabling the terminal to receive the PWS information in a timely manner.
[0019] In one possible design, system messages include the system information block SIB31.
[0020] Based on this possible design, in satellite communications, the SIB31 can enable the terminal to receive PWS information even in connected mode.
[0021] In one possible design, the method further includes: sending data after the first moment, wherein the time interval between the first moment and the moment of sending the first message is greater than or equal to a time interval threshold.
[0022] In this design, data is sent after the first moment, which can be understood as no data being sent between the sending of the first message and the first moment.
[0023] Based on this possible design, the first communication device does not send data during the time interval between the first moment and the moment of sending the first message. This helps the terminal to avoid conflicts between receiving PWS information and data communication when in the connected state, so that the terminal can receive the correct PWS information.
[0024] In one possible design, the method further includes sending a second message, which includes a time interval threshold.
[0025] Based on this possible design, the time interval threshold is configured by the network side, which helps to improve the rationality of the time interval threshold. This can further ensure that there is no conflict between receiving PWS information and data communication, and ensure that the terminal can receive the correct PWS information.
[0026] In one possible design, the first message is the downlink control channel, and the first information is the scrambling method of the first message.
[0027] Based on this possible design, the terminal can receive PWS information even in the connected state without having to enter the idle state, which helps the terminal obtain information in a timely manner.
[0028] Secondly, a communication method is provided, which can be executed by a terminal, or can be a device within the terminal (e.g., a module, communication module, circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), chip system or processor), or can be a logical node, logical module or software that can realize all or part of the terminal.
[0029] The method includes: receiving a first message, the first message being associated with first information, the first information being used to trigger the terminal to receive public alarm system (PWS) information; and obtaining PWS information based on the first information.
[0030] In one possible design, the first message is an Infinite Resource Control (RRC) release message.
[0031] In one possible design, the first information includes the reason for RRC release.
[0032] In one possible design, the reasons for RRC release include: PWS type, or the position of PWS information in system messages, or the time-frequency resource where PWS information is located, or the main message of ETWS.
[0033] In one possible design, the first information is used to trigger the terminal to receive system messages, which include PWS information.
[0034] In one possible design, system messages include the system information block SIB31.
[0035] In one possible design, the method further includes: receiving data after a first moment, wherein the time interval between the first moment and the moment of receiving the first message is greater than or equal to a time interval threshold.
[0036] In one possible design, the method further includes receiving second information, which includes a time interval threshold.
[0037] In one possible design, the first message is the downlink control channel, and the first information is the scrambling method of the first message.
[0038] Thirdly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any possible implementation of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.
[0039] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the first aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the first aspect or any possible implementation thereof.
[0040] Fourthly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any possible implementation thereof.
[0041] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the second aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the second aspect or any possible implementation thereof.
[0042] Fifthly, an apparatus is provided, including a processor, wherein instructions, when executed by the processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented.
[0043] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.
[0044] A sixth aspect provides an apparatus including a processor, wherein instructions, when executed by the processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.
[0045] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.
[0046] In a seventh aspect, a chip is provided, including processing circuitry for running a program or instructions to cause the methods described in the first aspect or any possible implementation thereof to be implemented.
[0047] Optionally, the chip may further include a memory for storing programs or instructions.
[0048] Optionally, the chip may also include the transceiver circuit, or an input / output interface.
[0049] Eighthly, a chip is provided, including processing circuitry for running a program or instructions to implement a method as described in the second aspect or any possible implementation thereof.
[0050] Optionally, the chip may further include a memory for storing programs or instructions.
[0051] Optionally, the chip may also include the transceiver circuit, or an input / output interface.
[0052] A ninth aspect provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause the method as described in the first aspect or any possible implementation thereof to be implemented.
[0053] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.
[0054] Eleventhly, a computer program product is provided, the computer program product including computer program code or instructions, which, when the computer program code or instructions are run, cause the method as described in the first aspect or any possible implementation thereof to be implemented.
[0055] In a twelfth aspect, a computer program product is provided, the computer program product comprising computer program code or instructions that, when the computer program code or instructions are executed, cause the method as described in the second aspect or any possible implementation thereof to be implemented.
[0056] In a thirteenth aspect, a communication system is provided, comprising: means for performing the first aspect or any possible implementation thereof, and means for performing the second aspect or any possible implementation thereof.
[0057] It is understood that the technical effects of any of the second to thirteenth aspects of this application can be referred to the relevant content in the first aspect, and will not be repeated here. Attached Figure Description
[0058] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;
[0059] Figure 2 is a schematic diagram of a communication system according to another embodiment of this application;
[0060] Figure 3 is a flowchart of a communication method according to an embodiment of this application;
[0061] Figures 4 and 5 are schematic diagrams of the structure of communication devices according to various embodiments of this application. Detailed Implementation
[0062] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.
[0063] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0064] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.
[0065] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.
[0066] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is 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.
[0067] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.
[0068] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.
[0069] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.
[0070] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.
[0071] A public warning system (PWS) is a dedicated mechanism for broadcasting emergency alerts and public safety notifications. It can rapidly and widely disseminate critical information during emergencies via wireless communication networks. In this application, the critical information broadcast by PWS can be referred to as PWS information or PWS signal. PWS is divided into two types: earthquake and tsunami warning systems (ETWS) and commercial mobile alert systems (CMAS). Currently, PWS information is carried as system messages.
[0072] In some wireless communication systems, the network side notifies the terminal of changes in system messages via paging messages, allowing the terminal to obtain updated system messages. If the network side sends PWS information, the terminal can retrieve the PWS information based on the received system messages.
[0073] For example, a terminal can receive PWS information in either connected or idle mode. When in idle mode, the terminal can receive PWS information based on paging messages. Specifically, in idle mode, the terminal can schedule PWS information using downlink control information (DCI) scrambled with the physical radio network temporary identifier (P-RNTI). When in connected mode, after system messages are updated, the terminal can send downlink control information (DCI) via the physical downlink control channel (PDCCH) scrambled with the system information radio network temporary identifier (SI-RNTI). This DCI contains scheduling information for system messages; for example, SIB1 can be used to schedule system messages carrying PWS information. The terminal can then receive system messages carrying PWS information based on the received DCI.
[0074] Satellite communication offers unique advantages over terrestrial communication, such as wider coverage and less susceptibility to natural disasters or external damage. Therefore, the field of communications has proposed incorporating satellite communication into terrestrial communication systems, for example, in fifth-generation mobile networks (5G).
[0075] Satellite communication systems offer significant advantages in terms of wide coverage, high reliability, multiple connections, and high throughput. For example, they can provide communication services to areas such as oceans and forests where terrestrial communication networks cannot reach; they can enhance communication reliability, ensuring users on airplanes and trains receive higher-quality communication services; and they can provide more resources for data transmission, thus increasing network speed.
[0076] Because satellite communication has a relatively low link budget, coverage enhancement techniques are suitable for data transmission. The most common coverage enhancement technique is to transmit signals repeatedly. Since Narrow Band Internet of Things (NB-IoT) can support a large number of repetitions and has good coverage, satellite communication primarily serves NB-IoT.
[0077] Because satellite communication has a wide coverage area, it is convenient to provide emergency information broadcasting services to terminals in most areas, such as tsunami and earthquake warning messages. In other words, the introduction of satellite communication makes it easy to provide PWS information to NB-IoT.
[0078] However, existing NB-IoT terminals do not support obtaining PWS information in connected mode, nor do they have corresponding system messages carrying PWS information. This means that when NB-IoT terminals are used in everyday life as a non-terrestrial network (NTN) terminal application, such as when they are integrated into mobile phones to provide PWS services to ordinary handheld terminals, they cannot obtain PWS information in a timely manner.
[0079] Furthermore, due to limitations in the capabilities of NB-IoT terminals, even if system messages carrying PWS information are introduced to NB-IoT terminals, the NB-IoT terminals will still be unable to receive system messages in the connected state, resulting in the inability to obtain PWS information published by the network side in a timely manner.
[0080] Furthermore, even if the NB-IoT terminal is in an idle state and a system message carrying PWS information is defined for the NB-IoT terminal, the NB-IoT terminal needs to receive a paging message and determine whether the system message has changed based on the content of the paging message before it will receive the system message. This will result in the NB-IoT terminal not being able to obtain the PWS information in a timely manner.
[0081] To address at least one of the aforementioned problems, this application provides a new technical solution. The technical solution provided by this application helps NB-IoT terminals receive PWS information in a timely manner. The technical solution provided by this application is described below with reference to the accompanying drawings.
[0082] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems, such as fourth-generation (4G) systems like long-term evolution (LTE), 5G systems like new radio (NR), hybrid LTE and 5G networks, non-terrestrial networks (NTN), or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.
[0083] The solutions proposed in this application can also be applied to various NTN systems. In satellite communication systems, 3GPP converged satellite communication wireless technologies can be broadly categorized into transparent relay systems and base station onboard systems.
[0084] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application. The system includes a terminal, a satellite, a ground station and a ground base station, a core network, and a data network.
[0085] The terminal communicates with satellites, ground stations, and terrestrial base stations via an air interface. The air interface refers to the wireless link between the terminal and the base station. The satellite, acting as a relay node in this system, does not process the signal; it only performs radio frequency filtering, frequency conversion, and amplification. In other words, the satellite acts as a transparent relay node in this system. The satellite primarily functions as an L1 relay, regenerating physical layer signals and does not involve any higher protocol layers. Base stations deployed on the ground are called terrestrial base stations. Ground stations and terrestrial base stations are key nodes connecting the satellite and the core network. Ground stations forward signaling and service data between the satellite and the core network, while terrestrial base stations have processing capabilities, providing wireless access services and scheduling wireless resources.
[0086] The core network can be divided into a control plane and a user plane. The control plane includes access mobility functions and session management functions; the user plane includes the user plane processing unit, which can transmit data with the data network.
[0087] It should be noted that in a transparent relay system, satellites generally cannot communicate with each other.
[0088] Figure 2 is a schematic diagram of a communication system according to another embodiment of this application. The system includes a terminal, a satellite, a ground station, a core network, and a data network.
[0089] The terminal communicates with the satellite via an air interface. The air interface refers to the wireless link between the terminal and the base station. The base station is deployed on the satellite and communicates with the ground-based core network via the wireless link. The satellite not only performs radio frequency filtering, frequency conversion, and amplification but also possesses the processing functions of a base station; in this system, the satellite can be considered the base station. The ground station is the key node connecting the satellite and the core network, capable of forwarding signaling and service data between the satellite (base station) and the core network. In NR systems, the satellite communicates with the core network through the NG interface; in LTE systems, the satellite communicates with the core network through the S1 interface. Based on the NG or S1 interface, the satellite primarily interacts with the core network's network access server (NAS) and other signaling, as well as user service data.
[0090] The core network can be divided into a control plane and a user plane. The control plane includes access mobility functions and session management functions; the user plane includes the user plane processing unit, which transmits data with the data network.
[0091] It should be noted that in this system, wireless links can exist between satellites. Since base stations are deployed on satellites, signaling interaction and user data transmission between base stations are possible. In LTE systems, satellites communicate via the X2 interface. In NR systems, satellites communicate via the Xn interface. The X2 or Xn interface is primarily used for signaling interaction such as handover.
[0092] The base stations in the aforementioned systems can be base stations in 4G systems, 5G systems, or future communication systems; this application does not impose any restrictions on this.
[0093] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.
[0094] In this application's embodiments, the core network (CN) equipment can be any equipment within the core network that provides service support to the terminal. The core network can be divided into control plane and data plane functional entities, capable of providing services such as user access control, mobility management, session management, user security authentication, and billing to the terminal. The core network can consist of multiple functional units, such as access and mobility management function (AMF) network elements and user plane function (UPF) network elements. Of course, the core network can also include other core network equipment, without limitation.
[0095] AMF (Access Default Mode) network elements are primarily responsible for terminal access management, security authentication, and mobility management in mobile networks, such as user location updates, user network registration, and user handover. UPF (User Plane Functional Element) network elements are user plane functional network elements, mainly responsible for connecting to external networks and managing user plane data transmission, traffic statistics, and other functions.
[0096] It should be noted that in this application, network elements can also be referred to as entities or functional entities. For example, an AMF network element can also be referred to as an AMF entity or an AMF functional entity. Furthermore, the aforementioned UPF network element may have other names in future communication systems, and this application does not specifically limit its usage.
[0097] The access network equipment involved in this application can be a radio access network (RAN) node (or device) that connects a terminal to a wireless network. The access network equipment in the embodiments of this application can include various forms of base stations (BS), capable of providing wireless access services, scheduling wireless resources to access terminals, and providing reliable wireless transmission protocols and data encryption protocols, etc. For example, a base station can be an evolved Node B (gNB), a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved Node B (or home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wi-Fi) access point (AP), a satellite base station, a satellite ground station, etc. The embodiments of this application do not specifically limit this.
[0098] The terminal involved in the embodiments of this application can be a mobile device that provides voice and / or data connectivity to users, supports an air interface, and is capable of accessing the network and initiating services such as making calls and accessing the Internet. It can also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios. For example, it can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons, and satellites). The terminal can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. This application does not specifically limit this.
[0099] In one possible scenario, the terminal in this application embodiment is an NB-IoT terminal, or simply an NB-IoT terminal.
[0100] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0101] The communication method provided in this application will be described below with reference to the aforementioned communication system, taking the interaction between the first communication device and the terminal as an example. It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between the first communication device and the terminal are merely examples, and may be other names in other embodiments. The method provided in this application does not specifically limit these names.
[0102] It is understood that in the embodiments of this application, the first communication device and the terminal may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the various steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.
[0103] It is understood that this application uses a first communication device and a terminal as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the first communication device in this application can also be executed by a module applied to the first communication device (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software that can implement all or part of the functions of the first communication device; similarly, the method executed by the terminal in this application can also be executed by a module applied to the terminal (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software that can implement all or part of the functions of the terminal.
[0104] Furthermore, in this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module within a device sending information to another logic module. For example, "the first communication device sending information" can be understood as the first communication device sending information to another device (such as a terminal), or it can be understood as logic module 1 (such as a processing module) in the first communication device sending information to logic module 2 (such as a communication module) in the first communication device.
[0105] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "terminal receiving information" can be understood as the terminal receiving information from another device (such as the first communication device), or it can be understood as logical module 1 (such as the processing module) in the terminal receiving information from logical module 2 (such as the communication module) in the terminal.
[0106] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a first communication device)," "receiving information from... (e.g., a first communication device)," or "receiving information sent by (e.g., a first communication device)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a first communication device. This can include receiving information directly or indirectly from a first communication device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.
[0107] Figure 3 is a flowchart of a communication method according to an embodiment of this application. The method may include S301, S302 and S303.
[0108] S301, The first communication device receives PWS information.
[0109] In one possible implementation, the first communication device can be a network-side device, such as a core network device or an access network device.
[0110] For example, when a relevant organization receives PWS information, it can send the PWS information to the first communication device through a cell broadcast entity (CBE). Correspondingly, the first communication device receives the PWS information.
[0111] For example, PWS information may include warning type, warning level, expected area range, warning message content, etc.
[0112] S302, the first communication device sends a first message, the first message is associated with first information, and the first information is used to trigger the terminal to receive PWS information. Accordingly, the terminal receives the first message.
[0113] For example, the first message is associated with first information, including: the first message carries the first information.
[0114] The first message is used to trigger the terminal to receive PWS information. It can be understood as: the first message is used to instruct the terminal to receive PWS information, or the first message is used to notify the network side that PWS information has been sent.
[0115] As an example, when the first information is predefined to carry specific information content, it indicates that the network side has sent PWS information, or in other words, the first information indicates that the terminal is instructed to receive PWS information.
[0116] For example, the predefined characteristic information content includes: PWS type, location of PWS information, time-frequency resources of PWS information or ETWS master message.
[0117] As an example, the terminal in this embodiment is an NB-IoT terminal. It is understood that the terminal in this embodiment may also be a non-NB-IoT terminal, and this application does not limit this.
[0118] S303, The terminal obtains PWS information based on the first information.
[0119] Once the terminal determines that the network side has sent PWS information based on the first information, it can promptly receive the PWS information.
[0120] In some implementations, the device that sends PWS information to the terminal is a first communication device. For example, the first communication device is an access network device. In this case, the first communication device sends both PWS information and the first message.
[0121] In the technical solution of this embodiment, the first communication device explicitly instructs the network side to send PWS information to the terminal, which helps the terminal to know the existence of PWS information in a timely manner, so that the terminal can receive PWS information in a timely manner.
[0122] As one possible implementation, the first communication device sends a first message to the terminal. The first message is an RRC release message, which carries PWS information. In this way, the terminal can obtain the PWS information at the same time as receiving the first message.
[0123] As one possible implementation, the first message is an RRC release message, which carries first information. For example, the first information is carried in the RRC release reason within the RRC release message.
[0124] For example, when the 3GPP network receives PWS information from the network operator, if the terminal is in the connected state, the first communication device releases the terminal's RRC connection, allowing the terminal to enter the idle state. That is, the first communication device sends an RRC release message to the terminal, and after receiving the RRC release message, the terminal enters the idle state.
[0125] Furthermore, the first communication device sends an RRC release message to the connected terminal upon receiving PWS information, thus instructing the terminal on the reason for RRC release. This reason can be used to trigger the terminal to receive PWS information. In other words, releasing RRC at this time is intended to allow the terminal to receive PWS information as soon as possible after entering the idle state, rather than using reasons for RRC release as in existing technologies, such as load balancing.
[0126] During information exchange, to reduce the overhead of the first communication device sending the first message, the first information may be an RRC release reason. For example, the first communication device sends an RRC release message carrying an RRC release reason. The information carried in the RRC release reason includes one or more of the following: PWS type, location of the PWS information, time-frequency resources of the PWS information, and the main message of the ETWS. Alternatively, the RRC release reason may carry other predefined information used to instruct the terminal to receive the PWS information.
[0127] For example, if another predefined message used to indicate that the terminal needs to receive PWS information is "warning", and the RRC release reason carries a warning, the terminal can determine that it needs to receive PWS information after receiving the RRC release message.
[0128] For example, PWS types can be divided into ETWS, CMAS, etc. This allows the terminal to clearly understand the reason for the RRC release, as well as the specific PWS type, and thus understand the urgency of the event based on the specific PWS type.
[0129] As an example, when the RRC release reason includes a PWS type, the terminal can determine whether it needs to receive PWS information promptly based on the PWS type. For instance, if the PWS type is a high-urgency PWS information type, the PWS information should be received promptly; otherwise, the PWS information can be received in the normal way.
[0130] For example, when PWS information is carried within a system message, the position of the PWS information is the same as its position within the system message. For instance, the position of the PWS information within the system message can be a predefined character, allowing the terminal to receive the system message carrying the PWS information based on this predefined character.
[0131] As an example, when the RRC release reason includes the time-frequency resource where the PWS information is located, the terminal can receive the PWS information in a timely manner based on the time-frequency resource where the PWS information is located. For example, the time-frequency resource where the PWS information is located can be a radio frame number, subframe number, etc.
[0132] In some implementations, the RRC release reason includes the ETWS master message. For example, if the first communication device sends an RRC release message to the connected terminal because it has received PWS information, and the type of PWS information is ETWS, the content of the RRC connection release reason can be the ETWS master message.
[0133] It should be noted that the existing standard has higher latency requirements for ETWS. ETWS is divided into two types of messages: ETWS main messages and ETWS auxiliary messages. Typically, ETWS main messages are carried in SIB10, and ETWS auxiliary messages are carried in SIB11.
[0134] For example, the ETWS master message has a fixed message format or fixed message content, such as the message format or message content specified by the protocol. When the terminal receives the ETWS master message associated with the RRC release message, that is, the message format or message content, it can trigger the terminal to receive PWS information.
[0135] For example, the main message of ETWS includes a unique identifier. When the terminal receives the RRC release reason containing this unique identifier, it can trigger the terminal to receive PWS information.
[0136] In one possible implementation, the reason for RRC release can be categorized according to the latency of different alarm messages, with the latency of different alarm messages representing different levels of urgency. For example, since ETWS has a low latency, it means that the event corresponding to ETWS has a high level of urgency. Other alarm messages have high latency, which means that the event corresponding to other alarm messages has a low level of urgency.
[0137] For example, if the first communication device receives PWS information and the type of PWS information is not ETWS, the RRC release reason may include other alarm messages in the PWS information besides the main message of ETWS.
[0138] In another possible implementation, when the first communication device receives PWS information and the type of PWS information is not ETWS, because the urgency of PWS information is low, the RRC release reason can be other (as already known in the prior art). The terminal enters an idle state and performs corresponding operations, such as monitoring paging messages to determine whether system messages have been updated, and then obtaining PWS information.
[0139] In one possible implementation, after the terminal receives the RRC release message (i.e., after receiving the RRC release reason), if the RRC release reason instructs the terminal to receive PWS information, then it can directly read the system message from the corresponding resource based on the scheduling information of the system message, without needing to monitor the paging message to obtain whether the system message has been updated, thereby obtaining the PWS information. This is equivalent to the RRC release message acting as an indication of system message updates.
[0140] For example, if the RRC release reason includes the ETWS main message, the terminal will need to receive the ETWS auxiliary message after entering the idle state.
[0141] For example, the auxiliary messages of ETWS can be carried in SIB11. After the terminal enters the idle state, it receives SIB11 to obtain PWS information.
[0142] Therefore, the above method enables the terminal to receive PWS information as soon as possible after entering the idle state from the connected state, so as to avoid losses caused by untimely reception of PWS information.
[0143] Furthermore, since the reason for RRC release is receiving PWS information, after the terminal finishes receiving the PWS information in the idle state, if the terminal needs to enter the connected state, it can enter the connected state from the idle state again.
[0144] As one implementation method, the first information triggering terminal to receive PWS information is achieved in the following way: the first information triggering connected terminal receives a system message, which includes PWS information.
[0145] For example, the first communication device sends first information to the terminal in the connected state to trigger the terminal to receive a system message, which includes PWS information, thereby enabling the terminal to receive PWS information in the connected state.
[0146] As one implementation, the system message carrying PWS information is SIB31. In this case, the network-side triggering terminal receiving SIB31 is equivalent to the network-side triggering terminal receiving PWS information.
[0147] It should be noted that in current satellite communications, to ensure that the terminal can maintain uplink synchronization, the terminal is allowed to read updated ephemeris information while in connected state. The corresponding system message can be SIB31.
[0148] In one implementation, the system message carrying PWS information is SIB10, SIB11, or SIB12, and the scheduling information of the system message carrying PWS information is carried in SIB31. In this case, when the network side needs to instruct the terminal to receive PWS information, it can send a trigger message to the terminal to receive SIB31. After receiving the trigger message, the terminal receives SIB31, obtains the scheduling information of SIB10, SIB11, or SIB12 based on SIB31, and receives SIB10, SIB11, or SIB12 based on the scheduling information, thereby obtaining the PWS information.
[0149] As one implementation, the scheduling information of SIB10, SIB11, or SIB12 is not carried in SIB31, but can be obtained through other means. For example, if the terminal obtains the scheduling information of SIB10, SIB11, or SIB12 in the previous idle state, the scheduling information will not expire for a period of time and will still be valid after the terminal enters the connected state. At this time, the terminal can receive SIB10, SIB11, or SIB12 according to the pre-obtained scheduling information, thereby obtaining PWS information.
[0150] Furthermore, as a possible implementation, after sending the first information to the terminal, the first communication device can also send PWS information to the terminal. As an example, the PWS information can be carried in terminal-level signaling, such as radio resource control (RRC) or medium access control element (MAC CE) messages.
[0151] As one possible implementation, the method further includes: sending data after the first moment, wherein the time interval between the first moment and the moment of sending the first message is greater than or equal to a time interval threshold. Accordingly, the terminal receives data after the first moment.
[0152] Understandably, after the first communication device sends the first message, but before the first moment, it does not send and / or receive data. That is, the first communication device does not send and / or receive data during the time interval between the first moment and the moment the first message was sent, to ensure that the terminal does not conflict with data communication when reading system messages in the connected state. Alternatively, it can be understood that after the terminal receives the first message, but before the first moment, it does not send and / or receive data; the terminal does not receive and / or send data during the time interval between the first moment and the moment the first message was received; or the terminal does not monitor other downlink control channels unrelated to PWS information during the time interval between the first moment and the moment the first message was received.
[0153] As one possible implementation, the method further includes: a first communication device sending second information, the second information including a time interval threshold.
[0154] Correspondingly, the terminal receives the second information.
[0155] The time interval threshold here may not be indicated by the first communication device. For example, the terminal receives a trigger command and begins receiving PWS information after the agreed time interval threshold has elapsed.
[0156] Understandably, the time interval threshold is a positive number.
[0157] In some implementations, the terminal successfully obtains the PWS information and notifies the network side to resume normal data scheduling.
[0158] Furthermore, as one possible implementation, the terminal acquires the PWS information at a second time point, which is less than or equal to the first time point, meaning the terminal acquired the PWS information before the first time point. After the second time point, the terminal can also send indication information to the first communication device, indicating that the terminal has acquired the PWS information. Upon receiving the indication information, the first communication device can send data to the terminal. For example, this indication information can be sent through a random access procedure.
[0159] As one possible implementation, the first message is used to schedule downlink data, and the first information is the scrambling method of the first message. For example, the first message is a downlink control channel, such as a PDCCH, and the first information is the scrambling method of the downlink control channel. This scrambling method instructs the terminal to receive PWS information. As an example, this scrambling method could be a newly defined scrambling method.
[0160] As an example, this downlink control channel is a user-level downlink control channel.
[0161] As an example, this downlink control channel is the downlink control channel for scheduling paging messages.
[0162] In this way, after the connected terminal receives the downlink control channel, it can promptly determine whether it needs to receive PWS information based on the scrambling method of the downlink control channel. Essentially, after successfully descrambling the downlink control channel, it can determine that the system message has been updated based on the scrambling method, without needing to know the information in the downlink control channel to determine if the system message has been updated. This allows it to receive system messages promptly, and consequently, PWS information promptly.
[0163] For example, if a terminal in the connected state determines that it needs to receive PWS information based on the scrambling method of the downlink control channel, it can receive system messages in a timely manner, thereby receiving PWS information in a timely manner.
[0164] As an example, this downlink control channel is the downlink control channel for scheduling multicast messages. PWS information is carried in the multicast message.
[0165] In this way, after receiving the downlink control channel, the connected terminal can determine whether it needs to receive PWS information based on the scrambling method of the downlink control channel. Then, the terminal obtains the PWS information by receiving multicast messages.
[0166] In some implementations, when the first communication device sends the paging message control channel, it does not send the control channels for other messages. This helps a terminal with limited capabilities to monitor the paging message control channel in the connected state, thereby enabling it to receive the paging message in the connected state and, consequently, receive PWS information in a timely manner.
[0167] The method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.
[0168] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, 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 and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0169] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.
[0170] Figure 4 is a schematic diagram of the structure of a communication device 40 according to an embodiment of this application. The communication device 40 includes a processing module 401 and a communication module 402. The communication device 40 can be used to implement the functions of the first communication device or terminal described above.
[0171] In some embodiments, the communication device 40 may further include a storage module (not shown in FIG4) for storing program instructions and data.
[0172] In some embodiments, the communication module 402, also known as a transceiver unit, is used to implement sending and / or receiving functions. The communication module 402 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.
[0173] In some embodiments, the communication module 402 may include a receiving module and a sending module, respectively configured to perform the receiving and sending steps performed by the first communication device or terminal in the above method embodiments, and / or other processes to support the technology described herein; the processing module 401 may be configured to perform the processing steps performed by the first communication device or terminal in the above method embodiments, and / or other processes to support the technology described herein.
[0174] In one possible implementation, when the communication device 40 is used to perform the functions of the first communication device:
[0175] The communication module 402 is used to receive PWS information and send a first message, which is associated with first information and is used to trigger the terminal to receive PWS information.
[0176] In one possible implementation, the first message is an unlimited resource control (RRC) release message, and the first information includes the reason for the RRC release.
[0177] In one possible implementation, the reasons for RRC release include: PWS type, or the location of PWS information in system messages, or the time-frequency resource where PWS information is located, or the master message of the Earthquake and Tsunami Warning System (ETWS).
[0178] In one possible implementation, the first information is used to trigger the terminal to receive a system message, which includes PWS information.
[0179] In one possible implementation, the system message includes a system information block SIB31.
[0180] In one possible implementation, the communication module 402 is further configured to send data after the first moment, wherein the time interval between the first moment and the moment of sending the first message is greater than or equal to a time interval threshold.
[0181] In one possible implementation, the communication module 402 is also used to send second information, which includes a time interval threshold.
[0182] In one possible implementation, the first message is a downlink control channel, and the first information is the scrambling method of the first message.
[0183] In one possible implementation, when the communication device 40 is used to implement the functions of a terminal:
[0184] The communication module 402 is used to receive a first message, which is associated with first information. The first information is used to trigger the terminal to receive public alarm system (PWS) information. The processing module 401 is used to obtain PWS information based on the first information.
[0185] In one possible implementation, the first message is an Infinite Resource Control (RRC) release message, and the first information includes the reason for the RRC release.
[0186] In one possible implementation, the reasons for RRC release include: PWS type, or the location of PWS information in system messages, or the time-frequency resource where PWS information is located, or the main message of ETWS.
[0187] In one possible implementation, the first information is used to trigger the terminal to receive a system message, which includes PWS information.
[0188] In one possible implementation, the system message includes a system information block SIB31.
[0189] In one possible implementation, the communication module 402 is further configured to receive data after the first moment, wherein the time interval between the first moment and the moment of receiving the first message is greater than or equal to a time interval threshold.
[0190] In one possible implementation, the communication module 402 is also configured to receive second information, which includes a time interval threshold.
[0191] In one possible implementation, the first message is a downlink control channel, and the first information is the scrambling method of the first message.
[0192] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.
[0193] In this application, the communication device 40 can be presented in an integrated manner by dividing it into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.
[0194] In some embodiments, when the communication device 40 in FIG4 is a chip or chip system, the function / implementation process of the communication module 402 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 401 can be implemented through the processor (or processing circuit) of the chip or chip system.
[0195] Since the communication device 40 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.
[0196] As a possible product form, the first communication device or terminal described in the embodiments of this application can be implemented using one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.
[0197] As another possible product form, the first communication device or terminal in this application may adopt the composition structure shown in FIG5, or include the components shown in FIG5. FIG5 is a schematic diagram of the structure of a communication device 500 according to an embodiment of this application. The communication device 500 may be a terminal or a chip or system-on-a-chip in a terminal; or, it may be a first communication device or a module, chip or system-on-a-chip in the first communication device.
[0198] As shown in Figure 5, the communication device 500 includes at least one processor 501 and at least one communication interface (Figure 5 is merely an example illustrating the inclusion of a communication interface 504 and a processor 501). Optionally, the communication device 500 may also include a communication bus 502 and a memory 503.
[0199] Processor 501 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 501 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.
[0200] The communication bus 502 is used to connect different components in the communication device 500, enabling communication between them. The communication bus 502 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 5, but this does not indicate that there is only one bus or one type of bus.
[0201] Communication interface 504 is used for communicating with other devices or communication networks. For example, communication interface 504 can be a module, circuit, transceiver, or any device capable of communication. Optionally, communication interface 504 can also be an input / output interface located within processor 501, used to implement signal input and signal output for the processor.
[0202] The memory 503 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.
[0203] For example, memory 503 may be read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions; it may also be random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions; it may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.
[0204] It should be noted that the memory 503 can exist independently of the processor 501, or it can be integrated with the processor 501. The memory 503 can be located inside or outside the communication device 500, without limitation. The processor 501 can be used to execute the instructions stored in the memory 503 to implement the methods provided in the following embodiments of this application.
[0205] As an optional implementation, the communication device 500 may also include an output device 505 and an input device 506. The output device 505 communicates with the processor 501 and can display information in various ways. For example, the output device 505 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 506 communicates with the processor 501 and can receive user input in various ways. For example, the input device 506 may be a mouse, keyboard, touchscreen device, or sensing device, etc.
[0206] In some embodiments, those skilled in the art will recognize that the communication device 40 shown in FIG4 can take the form of the communication device 500 shown in FIG5 in terms of hardware implementation.
[0207] As an example, the function / implementation process of the processing module 401 in Figure 4 can be implemented by the processor 501 in the communication device 500 shown in Figure 5 calling computer execution instructions stored in the memory 503. The function / implementation process of the communication module 402 in Figure 4 can be implemented by the communication interface 504 in the communication device 500 shown in Figure 5.
[0208] It should be noted that the structure shown in Figure 5 does not constitute a specific limitation on the first communication device or terminal. For example, in other embodiments of this application, the first communication device or terminal may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0209] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.
[0210] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.
[0211] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.
[0212] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.
[0213] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.
[0214] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions performed by the first communication device in any of the above method embodiments.
[0215] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions implemented by the terminal in any of the above method embodiments.
[0216] This application also provides a computer program product that, when executed by a computer, implements the functions performed by the first communication device in any of the above method embodiments.
[0217] This application also provides a computer program product that, when executed by a computer, implements the functions performed by the terminal in any of the above method embodiments.
[0218] This application also provides a communication system, including a first communication device and a terminal.
[0219] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0220] It is understood that the systems, apparatuses, and methods described in this application can also 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 couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.
[0221] The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0222] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0223] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.
[0224] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.
[0225] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.
Claims
1. A communication method characterized by comprising: The method includes: Receive Public Warning System (PWS) information; Send a first message, which is associated with first information, and the first information is used to trigger the terminal to receive the PWS information.
2. The method of claim 1, wherein, The method further includes: Data is sent after the first moment, and the time interval between the first moment and the moment when the first message is sent is greater than or equal to the time interval threshold.
3. The method of claim 2, wherein, The method further includes: Send a second message, which includes the time interval threshold.
4. A communication method characterized by comprising: The method includes: Receive a first message, the first message being associated with first information, the first information being used to trigger the terminal to receive public alarm system (PWS) information; The PWS information is obtained based on the first information.
5. The method of claim 4, wherein, The method further includes: Data is received after the first moment, and the time interval between the first moment and the moment when the first message is received is greater than or equal to a time interval threshold.
6. The method of claim 5, wherein, The method further includes: Receive second information, which includes the time interval threshold.
7. The method according to any one of claims 1 to 6, characterized in that, The first message is an Infinite Resource Control (RRC) release message, and the first information includes the reason for the RRC release.
8. The method of claim 7, wherein, The reasons for RRC release include: PWS type, or the location of PWS information in system messages, or the time-frequency resource where PWS information is located, or the main message of the Earthquake and Tsunami Warning System (ETWS).
9. The method according to any one of claims 1 to 6, characterized in that, The first information is used to trigger the terminal to receive a system message, the system message including the PWS information.
10. The method of claim 9, wherein, The system message includes system information block SIB31.
11. The method according to any one of claims 1 to 6, characterized in that, The first message is a downlink control channel, and the first information is the scrambling method of the first message.
12. A communications device, characterized by The communication device includes a module for performing the method as described in any one of claims 1 to 11.
13. A communications device, characterized by The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1 to 11.
14. A chip or chip system, characterized by The chip or chip system includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the method as described in any one of claims 1 to 11 to be performed.
15. A computer readable storage medium characterized by: The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method as described in any one of claims 1 to 11 to be performed.
16. A computer program product, characterised in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method as described in any one of claims 1 to 11 is performed.