Communication methods, communication device and system, and storage medium and program product

Abstract

The present disclosure relates to communication methods, a communication device and system, and a storage medium and a program product. A method, which is executed by a user equipment (UE), comprises: receiving, on a first carrier, a first message transmitted by a network device, wherein the first message is used for notifying a UE to receive a second message; and receiving, on a second carrier, the second message transmitted by the network device, wherein the second carrier and the first carrier are the same, or the second carrier and the first carrier are different.

Description

Communication methods, communication equipment, systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication methods, communication devices, systems, storage media, and program products. Background Technology

[0002] Non-terrestrial Network (NTN) is an important technology introduced in wireless communication. NTN communication provides wireless resources through base stations mounted on satellites (or drones) instead of ground base stations.

[0003] Summary of the Invention

[0004] This disclosure provides a communication method, communication device, system, storage medium, and program product for distributing broadcast messages.

[0005] According to a first aspect of the present disclosure, a communication method is provided, performed by a user equipment (UE), the method comprising: receiving a first message sent by a network device on a first carrier; the first message being used to notify the UE to receive a second message; receiving the second message sent by the network device on a second carrier; wherein the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

[0006] According to a second aspect of the present disclosure, a communication method is provided, performed by a network device, the method comprising sending a first message to a user equipment (UE) on a first carrier; the first message being used to notify the UE to receive a second message; the second message being sent to the UE on a second carrier; the second carrier and the first carrier being the same carrier; or, the second carrier and the first carrier being different carriers.

[0007] According to a third aspect of the present disclosure, a communication method is provided, the method comprising: a network device sending a first message to a user equipment (UE) on a first carrier, the first message being used to notify the UE to receive a second message; the network device sending the second message to the UE on a second carrier; the second carrier and the first carrier being the same carrier; or, the second carrier and the first carrier being different carriers; the UE receiving the first message sent by the network device on the first carrier; the UE receiving the second message sent by the network device on the second carrier; the second carrier and the first carrier being the same carrier; or, the second carrier and the first carrier being different carriers.

[0008] According to a fourth aspect of the present disclosure, a communication device is provided, the communication device comprising: one or more processors; wherein the communication device is configured to execute any one of the technical solutions of the first to second aspects.

[0009] According to a fifth aspect of the present disclosure, a communication system is provided, the communication system including a UE and a network device; the UE is configured to perform the method described by any technical solution of the first aspect; the network device is configured to perform the method described by any technical solution of the second aspect.

[0010] According to a sixth aspect of the present disclosure, a storage medium is provided, the storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in any of the technical solutions of the first to second aspects.

[0011] According to a seventh aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the steps of the method described in any of the technical solutions of the first to second aspects.

[0012] By introducing the above scheme, after receiving the first message on the first carrier, the second message is received on the second carrier to achieve the reception of the second message.

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure. Attached Figure Description

[0014] Figure 1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0015] Figure 1B is an exemplary schematic diagram of an NTN provided according to an embodiment of the present disclosure.

[0016] Figure 2A is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0017] Figure 2B is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0018] Figure 2C is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0019] Figure 2D is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0020] Figure 2E is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0021] Figure 2F is an exemplary interaction diagram of the communication method provided according to an embodiment of the present disclosure.

[0022] Figure 3A is a schematic diagram of the structure of a UE provided according to an embodiment of the present disclosure.

[0023] Figure 3B is a schematic diagram of the structure of a network device provided according to an embodiment of the present disclosure.

[0024] Figure 4A is a schematic diagram of the structure of a communication device according to an exemplary embodiment;

[0025] Figure 4B is a schematic diagram of the structure of a chip according to an exemplary embodiment. Detailed Implementation

[0026] This disclosure provides communication methods, communication devices, systems, storage media, and program products.

[0027] In a first aspect, embodiments of this disclosure provide a communication method executed by a UE, the method comprising: receiving a first message sent by a network device on a first carrier; the first message being used to notify the UE to receive a second message; receiving the second message sent by the network device on a second carrier; wherein the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

[0028] Based on the above scheme, after the UE receives the first message on the first carrier, it receives the second message on the second carrier to achieve the reception of the second message. Furthermore, the first carrier and the second carrier can be the same carrier or different carriers, which can meet the needs of UEs with different carrier capabilities or UEs in different carrier scenarios to receive the second message.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the first carrier is a non-anchor carrier or an anchor carrier, and the second carrier is an anchor carrier.

[0030] Based on the above scheme, it is applicable to both UEs that support non-anchor carriers and UEs that do not support non-anchor carriers, and has the characteristic of wide applicability.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: upon receiving the first message, pausing or stopping uplink transmission on the first carrier.

[0032] Based on the above scheme, after receiving the first message, the UE stops uplink transmission on the first carrier, reducing the mutual interference between uplink transmission and the reception of the second message.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, pausing or stopping uplink transmission on the first carrier includes: pausing or stopping uplink transmission on the first carrier during the timing period of a first timer.

[0034] Based on the above scheme, the UE suspends or stops uplink transmission on the first carrier during the timing period of the first timer, thereby reducing uplink transmission interference on the first carrier to the UE's second message reception on the second carrier and improving the reception quality of the second message.

[0035] In some embodiments, in conjunction with the first aspect, the method further includes: receiving configuration information sent by the network device, the configuration information being used at least to configure the first timer.

[0036] Based on the above scheme, the network device can pre-configure a first timer so that the UE can receive the second message within the first timer.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, receiving configuration information sent by the network device includes one of the following: receiving system information sent by the network device, the system information including the configuration information; receiving RRC dedicated signaling sent by the network device, the RRC dedicated signaling including the configuration information.

[0038] Based on the above scheme, the downlink signaling for network devices to send configuration information can be either system information or RRC-specific signaling. In this way, the downlink signaling for sending configuration information can be flexibly selected as needed.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, stopping uplink transmission on the first carrier includes at least one of the following: clearing the Hybrid Automatic Repeat Request (HARQ) buffer; and suspending uplink transmission by the Media Access Control (MAC) entity.

[0040] Based on the above scheme, upon receiving the second message, uplink transmission on the first carrier is resumed to achieve uplink transmission on the first carrier.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the resumption of uplink transmission on the first carrier includes: the MAC entity resuming uplink operation on the first carrier.

[0042] Based on the above scheme, the recovery of uplink transmission on the first carrier can be easily achieved.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the uplink operation includes uplink transmission.

[0044] In some embodiments, in conjunction with the first aspect, the method further includes: when the first timer times out, the UE switches to RRC idle state; or, when the first timer times out, the UE resumes uplink transmission on the first carrier.

[0045] Based on the above scheme, by clearing the HARQ buffer and / or stopping uplink transmission, it is hoped to more thoroughly prevent the UE from uplink transmission during the reception of the second message.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a second message sent by the network device and resuming uplink transmission on the first carrier.

[0047] Based on the above scheme, the UE enters the RRC idle state to save UE power consumption, or the UE resumes uplink transmission as soon as possible to reduce transmission delay.

[0048] In a second aspect, a communication method is provided, executed by a network device, the method comprising: sending a first message to a user equipment (UE) on a first carrier; the first message being used to notify the UE to receive a second message; sending the second message to the UE on a second carrier; wherein the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first carrier is a non-anchor carrier or an anchor carrier, and the second carrier is an anchor carrier.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0051] Configuration information sent to a user equipment (UE), the configuration information being used to configure at least a first timer, the timing period of the first timer being used for the UE to receive the second message.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information sent to the user equipment (UE) includes one of the following: system information sent to the UE, the system information including the configuration information; or radio resource control (RRC) dedicated signaling sent to the UE, the RRC dedicated signaling including the configuration information.

[0053] Thirdly, a communication method is provided, the method comprising: a network device sending a first message to a user equipment (UE) on a first carrier, the first message being used to notify the UE to receive a second message; the network device sending the second message to the UE on a second carrier; the UE receiving the first message sent by the network device on the first carrier; the UE receiving the second message sent by the network device on the second carrier; the second carrier and the first carrier being the same carrier; or, the second carrier and the first carrier being different carriers.

[0054] Fourthly, a user equipment (UE) is proposed, the UE comprising: a first transceiver module configured to receive a first message sent by a network device on a first carrier; the first message being used to notify the UE to receive a second message; receiving the second message sent by the network device on a second carrier; the second carrier and the first carrier being the same carrier; or, the second carrier and the first carrier being different carriers.

[0055] Fifthly, a network device is provided, the network device comprising: transmitting a first message to a user equipment (UE) on a first carrier; the first message being used to notify the UE to receive a second message; transmitting a second message to the UE on a second carrier; wherein the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

[0056] A sixth aspect provides a communication device for performing the methods provided in any of the first, second, and fifth aspects.

[0057] A seventh aspect provides a communication system comprising: a UE and a network device; the UE being configured to perform the method of any one of the first aspects; and the network device being configured to perform the method of any one of the second aspects.

[0058] Eighthly, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform a method as described in the first aspect and / or the second aspect.

[0059] A ninth aspect provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the steps of any one of the methods of the first and / or second aspects of claim.

[0060] This disclosure provides communication methods, communication devices, systems, storage media, and program products. In some embodiments, terms such as communication method or information processing method may be used interchangeably.

[0061] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the 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.

[0062] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0063] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0064] In the embodiments disclosed herein, "multiple" refers to two or more.

[0065] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0066] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0067] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0068] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0069] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0070] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0071] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0072] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0073] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0074] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0075] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0076] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0077] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0078] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0079] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0080] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0081] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0082] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0083] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102. The network device may include access network equipment and / or core network equipment.

[0084] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0085] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0086] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of the Open Radio Access Network (Open RAN) architecture. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0087] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0088] In some embodiments, the core network equipment may be a single device, including a first network element 1031, a second network element 1032, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1031, the second network element 1032, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0089] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0090] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0091] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0092] Based on the different ways satellites process signals, the NTN can be divided into pass-through mode and regeneration mode. In pass-through mode, the NTN ground station sends the signals from the gNB and / or eNB to the satellite. The satellite converts the signals to its own frequency band and then transmits them to the UE. Aside from frequency conversion and signal amplification, the satellite does not demodulate the gNB and / or eNB signals, similar to a repeater. In regeneration mode, after the NTN ground station sends the signals from the gNB and / or eNB to the satellite, the satellite first demodulates and decodes the signals before re-encoding and modulating them (this process is regeneration) and then transmits the regenerated signals through the satellite frequency band. Figure 1B shows a schematic diagram of the NTN architecture. The base station is mounted on a satellite or Unmanned Aerial System (UAS) platform 201. The airborne base station sends beams to the ground, and the beams hit the ground, forming a beam footprint. The base station on the satellite or UAS platform connects to the ground gateway 203 and is connected to the data network 204 via ground routing. The UE 202 can connect to the airborne base station within its field of view.

[0093] Public Warning System (PWS) messages are: Public warnings provide safe, reliable, flexible, and trustworthy alerts to the public in dangerous areas through networks (such as public mobile communication networks), offering public warning services by establishing a public warning system. Current LTE systems support Earthquake and Tsunami Warning Systems (ETWS) and Commercial Mobile Alert Systems (CMAS). ETWS is a public warning system designed to respond to natural disasters such as earthquakes and tsunamis. Earthquakes and tsunamis spread rapidly and last for short periods, requiring rapid and accurate delivery of alerts to affected users to help them take appropriate emergency measures to escape danger. In LTE systems, ETWS messages are sent via SIB10 and SIB11. Primary Notification: ETWS provides users with notifications of the most urgent events in the shortest possible time (within seconds), such as an impending earthquake, sent via SIB10. Secondary Notification: ETWS sends non-emergency supplementary information issued by the government to users, such as emergency measures, shelter maps, food distribution schedules, etc., and these messages are collectively referred to as ETWS messages and are sent through the System Information Block (SIB) 11.

[0094] Commercial Mobile Alert Service (CMAS) systems can provide users with information such as terrorist attack alerts, disaster warnings, and / or child abduction warnings. These messages are collectively referred to as CMAS messages and are sent via SIB12.

[0095] In LTE systems, after a UE in RRC idle state receives a direct indication message in the paging Physical Downlink Control Channel (PDCCH) or an ETWS and / or CMAS notification in the paging message, the UE receives the corresponding ETWS and / or CMAS messages in system messages (SIB10, 11, 12). After a UE in RRC connected state receives an ETWS / CMAS notification indicated in a direct indication message in the PDCCH scrambled with System Information Radio Network Temporary Identifier (SI-RNTI), the UE receives the corresponding ETWS and / or CMAS messages in system messages (SIB10, 11, 12).

[0096] In some cases, NB-IoT supports multi-carrier technology, meaning a single cell can have multiple carriers: one anchor carrier and several non-anchor carriers. The anchor carrier supports system message broadcasting, while the non-anchor carriers do not.

[0097] For connected NB-IoT UEs, introducing PWS message reception will impact data transmission because: NB-IoT UEs are half-duplex terminals and cannot perform uplink transmission when receiving SIB10, 11, and 12. If the UE is currently operating on a non-anchor carrier, it cannot receive PWS messages because non-anchor carriers do not support SIB broadcasting.

[0098] In view of this, this disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2A, the method includes:

[0099] S2101: The network device sends configuration information to the UE.

[0100] In some embodiments, the network device may include, but is not limited to, access network devices. For example, the network device may include, but is not limited to, access network devices for terrestrial networks (TN) and / or access network devices for NTN.

[0101] In some embodiments, the network device sends system information or RRC signaling to the UE. Configuration information is carried in the system information or RRC signaling.

[0102] In some embodiments, the configuration information is used at least to configure a first timer.

[0103] In some embodiments, the configuration information includes, but is not limited to, at least one of the following: timing duration information, used to indicate the timing duration of the first timer; start time information, used to indicate the start time of the first timer; and event information, used to indicate the triggering event for starting or stopping the first timer.

[0104] In some embodiments, the network device sends system information to the UE, which includes configuration information.

[0105] In some embodiments, the network device sends RRC dedicated signaling to the UE, and the RRC dedicated signaling includes configuration information.

[0106] Of course, the above are just examples of configuration information, and the actual implementation is not limited to the examples above.

[0107] It is worth noting that S2101 can be an optional step. For example, the timing duration and other related information of the first timer can be agreed upon by the protocol, in which case the network device does not need to send it separately.

[0108] In some embodiments, the UE may include, but is not limited to, a half-duplex terminal.

[0109] In some embodiments, the UE can be of various types. For example, the UE can be a single-carrier UE or a multi-carrier UE. Also for example, the UE can be a Narrow Band Internet of Things (NB-IoT) UE.

[0110] In some embodiments, the network device sends configuration information to the UE on a first carrier and / or a second carrier.

[0111] In some embodiments, the second carrier and the first carrier are the same carrier.

[0112] In some embodiments, the second carrier and the first carrier are different carriers.

[0113] In some embodiments, the first carrier is a non-anchor carrier or an anchor carrier, and the second carrier is an anchor carrier.

[0114] S2102: The network device sends the first message to the UE.

[0115] In some embodiments, the network device broadcasts, multicasts, or unicasts a first message to the UE. For example, the network device broadcasts an ETWS notification of an ETWS message and / or a CMAS notification of a CMAS message to the UE.

[0116] In some embodiments, the first message is used to notify the UE to receive the second message. Exemplarily, the second message may include, but is not limited to, various alarm messages. Exemplarily, the second message may include various types of PWS messages. In some embodiments, the PWS message may be a PWS notification message or a PWS notification. In this case, the first message may be a PWS indication, a PWS notification, or a PWS notification indication. In some embodiments, the first message may be carried in a direct indication message. Exemplarily, the direct indication message may be a physical layer message. For example, the network device sends direct indication information to the UE on the Physical Downlink Control Information (PDCCH).

[0117] In some embodiments, the network device broadcasts a paging message to the UE. The paging message includes a first message.

[0118] In some embodiments, the network device sends a first message to the UE on a first carrier.

[0119] The UE can operate in a single-carrier scenario or a multi-carrier scenario.

[0120] In some embodiments, in a single-carrier scenario, the UE operates on the first carrier and receives the first message on the first carrier.

[0121] In some embodiments, in a multi-carrier scenario, the UE can operate on a first carrier, a second carrier, or other carriers. When the UE operates on the first carrier, it receives the first message through the first carrier. The first carrier can be an anchor carrier or a non-anchor carrier. In other words, the UE can operate on an anchor carrier or a non-anchor carrier. The UE can receive the first message on the anchor carrier or on a non-anchor carrier.

[0122] In some embodiments, the network device carries a first message to be sent to the UE in the message that sends a system message change indication to the UE.

[0123] S2103: UE suspends or stops uplink transmission.

[0124] In some embodiments, upon receiving the first message, the UE suspends or stops uplink transmission. In the event that the UE receives the first message, the UE suspends or stops uplink transmission.

[0125] In some embodiments, the UE suspends or stops uplink transmission on the second carrier.

[0126] In some embodiments, pausing or stopping uplink transmission on the first carrier includes at least one of the following: clearing the Hybrid Automatic Repeat Request (HARQ) buffer; and suspending uplink operations on the first carrier by the Media Access Control (MAC) entity.

[0127] In some embodiments, uplink operation includes, but is not limited to, uplink transmission. For example, in some embodiments, uplink operation may also include uplink triggering. For example, triggering a Buffer Size Report (BSR). When the UE acquires uplink resources, it may send a triggered BSR, etc.

[0128] In some embodiments, in a single-carrier scenario, the UE pauses or stops uplink transmission on the first carrier in preparation for receiving a second message on the first carrier. For example, after receiving the first message on the first carrier (i.e., executing S2102), the UE can pause or stop uplink transmission on the first carrier.

[0129] In some embodiments, in a multi-carrier scenario, after the UE receives the first message on the first carrier (i.e., executes S2102), it can pause or stop uplink transmission on the first carrier. The first carrier can be the UE's anchor carrier or a non-anchor carrier.

[0130] In some embodiments, the uplink transmission can be any uplink transmission of the UE. Exemplarily, the uplink transmission may include, but is not limited to, at least one of the following: a random access request of the UE, a scheduling request (SR) of the UE, uplink HARQ information transmission of the UE, uplink service data transmission of the UE, etc.

[0131] In some embodiments, there are multiple ways to stop uplink transmission. It is worth noting that clearing the HARQ cache and / or suspending uplink operations by the UE's Media Access Control (MAC) entity are just examples.

[0132] In summary, there are multiple ways for a UE to stop uplink transmission, and the specific implementation is not limited to the examples mentioned above.

[0133] In some embodiments, when the network device has a configured first timer, the start of the first timer and the execution of the first operation may not have a sequential order. Specifically, for example, the UE may start the first timer simultaneously with stopping uplink transmission upon receiving the first message. Alternatively, the UE may stop uplink transmission first and then start the first timer. Or, the UE may start the first timer first and then stop uplink transmission. Or, the UE may start the first timer according to the start time indicated by the start time information. If the network device has not configured a first timer or the protocol does not specify a first timer, there is no start operation for the first timer. In summary, the start of the first timer and the execution of the first operation may or may not be related.

[0134] S2104: The network device sends a second message to the UE.

[0135] In some embodiments, the network device broadcasts a second message to the UE. For example, the network device broadcasts a PWS message to the UE.

[0136] In some embodiments, the network device sends a second message to the UE on a second carrier of the UE.

[0137] In some embodiments, the UE receives a second message sent by the network device during the timing period of the first timer.

[0138] In some embodiments, after receiving the first message, the UE starts a first timer. During the timing period of the first timer, the second message is received.

[0139] In some embodiments, in a single-carrier scenario, after the UE receives the first message on the first carrier (i.e., executes S2102), it receives the second message on the second carrier. The first carrier and the second carrier are the same carrier.

[0140] In some embodiments, in a multi-carrier scenario, after the UE receives the first message on the first carrier (i.e., executes S2102), the UE receives the second message on the second carrier. The first and second carriers are the same carrier, both being anchor carriers. That is, when the UE receives the first message on the anchor carrier (i.e., executes S2102), the UE stops uplink transmission on the anchor carrier and receives the second message on the anchor carrier.

[0141] In some embodiments, in a multi-carrier scenario, after the UE receives the first message on the first carrier (i.e., executes S2102), the UE receives the second message on the second carrier. The first carrier and the second carrier are different carriers. The first carrier is a non-anchor carrier, and the second carrier is an anchor carrier. That is, when the UE receives the first message on the non-anchor carrier (i.e., executes S2102), the UE stops uplink transmission on the non-anchor carrier and switches to receiving the second message on the non-anchor carrier.

[0142] In some embodiments, in a single-carrier scenario, the UE can receive the second message on the current working carrier without switching between the first and second carriers.

[0143] In some embodiments, in a multi-carrier scenario, the first carrier and the second carrier are different, and the UE operates on the first carrier. In this case, the UE switches from the first carrier to the second carrier to receive the second message.

[0144] In some embodiments, the UE receives the second message in the RRC connected state. In some embodiments, the UE exits the RRC inactive state or the RRC idle state and enters the RRC connected state, where it receives the second message.

[0145] In some embodiments, the network device broadcasts System Information Block (SIB) 10, SIB 11, and / or SIB 12 to the UE. For example, SIB 10 may include a primary notification from an ETWS message. For instance, SIB 10 may include an earthquake early warning message, which may contain summary information about an earthquake. SIB 11 may include a secondary notification from an ETWS message. For example, the secondary notification may include one or more of the following details: the specific estimated time of the earthquake, its location and region, and its magnitude. SIB 12 may include a CMAS message. Of course, these are merely examples, and actual implementations are not limited to these examples.

[0146] In some embodiments, if the UE has started a first timer, the UE can stop the first timer when it receives the second message during the timing period of the first timer. In some embodiments, the UE stops the first timer when it receives the second message during the timing period of the first timer. It is worth noting that stopping the first timer is an optional step when it is not configured. For example, assuming that the transmission resources of the first and second messages have a preset offset, the UE can receive the second message at the corresponding resource location according to the preset offset after completing the reception of the second message, without having to specifically start the first timer for reception timing. In this case, if the reception or decoding of the second message fails at the corresponding resource location, it means that the UE has not received the second message.

[0147] S2105: UE resumes uplink transmission.

[0148] In some embodiments, the UE resumes uplink transmission after receiving the second message or when the first timer times out.

[0149] In some embodiments, resuming uplink transmission may include: the UE's MAC entity resuming uplink operation.

[0150] In some embodiments, in a single-carrier scenario, the UE operates on the first carrier, and uplink transmission on the first carrier is stopped during the reception of the first message, and uplink transmission on the first carrier is resumed after the reception of the first message is completed.

[0151] In some embodiments, in a multi-carrier scenario, the UE can operate on the first carrier, or on the second carrier or other carriers. When the UE operates on the first carrier, uplink transmission on the first carrier is stopped. Similarly, after receiving the second message, uplink transmission on the first carrier is resumed. The first carrier can be an anchor carrier or a non-anchor carrier.

[0152] In some embodiments, the UE's MAC entity resumes uplink operation. For example, the suspend operation of the UE's MAC entity's uplink transmission is canceled.

[0153] In some embodiments, the second operation is the UE resuming uplink transmission. Exemplarily, the UE has an anchor carrier, and the UE resumes uplink transmission on the anchor carrier. The UE has both an anchor carrier and non-anchor carriers, and the UE resumes uplink transmission on both the anchor carrier and / or the non-anchor carrier.

[0154] In some embodiments, in a multi-carrier scenario, if the UE operates on the first carrier before receiving the second message, then the UE switches to the first carrier after completing the reception of the first message.

[0155] In a single-carrier scenario, the UE does not need to switch the working carrier before or after receiving the second message.

[0156] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2105. For example, any one of steps S2101 to S2105 can be implemented as an independent embodiment. For example, the timing duration of the first timer is agreed upon by the protocol, or if the first timer is not configured, then S2101 can be omitted. As another example, if the UE completes the reception of the second message and waits for the network device to indicate whether to resume uplink transmission, then S2105 can be omitted. As yet another example, after the network device sends configuration information to the UE, there may be no second message to send, and therefore no first message to send either; in this case, steps S2102 to S2105 are all optional steps.

[0157] In some embodiments, the names of information, etc., are not limited to those described in the embodiments. Terms such as "information," "message," "signal," "signaling," "report," "configuration," "indication," "instruction," "command," "channel," "parameter," "domain," "field," "symbol," "symbol," "codebook," "codeword," "codepoint," "bit," "data," "program," and "chip" can be used interchangeably. For example, "information" in "first information" can also be understood as "message," "parameter," or "configuration," etc.

[0158] This disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2B, the method includes:

[0159] S2201: The network device sends configuration information to the UE.

[0160] In some embodiments, the configuration information is used to configure at least a first timer.

[0161] In some embodiments, the configuration information includes, but is not limited to, at least one of the following:

[0162] The timing duration information is used to indicate the timing duration of the first timer;

[0163] Start time information, used to indicate the start time of the first timer;

[0164] Event information, used to indicate the triggering event that starts or stops the first timer.

[0165] Of course, the above are just examples of configuration information, and the actual implementation is not limited to the examples above.

[0166] In some embodiments, optional implementations of S2201 can be found in S2101 of the embodiment corresponding to FIG2A, and will not be repeated here. Similarly, descriptions of at least one of the network device, configuration information, and UE can be found in S2101 of the embodiment corresponding to FIG2A.

[0167] It is worth noting that S2201 can be an optional step. For example, the timing duration and other related information of the first timer can be agreed upon by the protocol, in which case the network device does not need to send it separately.

[0168] In some embodiments, the UE may include, but is not limited to, a half-duplex terminal.

[0169] S2202: The network device sends the first message to the UE.

[0170] In some embodiments, the network device broadcasts, multicasts, or unicasts a first message to the UE.

[0171] In some embodiments, the first message is used to notify the UE to receive the second message.

[0172] In some embodiments, the second message may, exemplarily, include, but is not limited to, various alarm messages. For example, the second message may include a PWS message. In some embodiments, the PWS message may be a PWS notification message or a PWS notification. In this case, the first message may be a PWS indication or a PWS notification. In some embodiments, the first message may be carried in a direct indication message. For example, the direct indication message may be a physical layer message. For instance, the network device sends direct indication information to the UE via the PDCCH.

[0173] In some embodiments, the network device broadcasts a paging message to the UE. The paging message includes a first message.

[0174] For an alternative embodiment of S2202, please refer to S2102 of the embodiment corresponding to FIG2A, which will not be described again here.

[0175] S2203: UE suspends or stops uplink transmission.

[0176] In some embodiments, upon receiving the first message, the UE suspends or stops uplink transmission. That is, upon receiving the first message, the UE suspends or stops uplink transmission.

[0177] In some embodiments, the UE receives a second message on a second carrier. The second carrier may be the UE's anchor carrier. The UE stops uplink transmission on the first carrier. The first carrier may be an anchor carrier or a non-anchor carrier. The first carrier and the second carrier may be the same. Alternatively, the first carrier and the second carrier may be different.

[0178] In some embodiments, the uplink transmission can be any uplink transmission of the UE. Exemplarily, the uplink transmission may include, but is not limited to, at least one of the following: a random access request of the UE, a scheduling request (SR) of the UE, uplink HARQ information transmission of the UE, uplink service data transmission of the UE, etc.

[0179] In some embodiments, optional implementations of S2203 can be found in S2103 of the embodiment corresponding to FIG2A, and will not be repeated here. Similarly, descriptions of at least one of the network device, configuration information, and UE can be found in S2103 of the embodiment corresponding to FIG2A.

[0180] S2204: The network device sends a second message to the UE.

[0181] In some embodiments, the network device broadcasts a second message to the UE. For example, the network device broadcasts a PWS message to the UE.

[0182] In some embodiments, the network device sends a second message to the UE on a second carrier. The second carrier may be an anchor carrier. In a single-carrier scenario, the second carrier and the first carrier may be the same. In a multi-carrier scenario, the second carrier and the first carrier may be different.

[0183] In a single-carrier scenario, the UE operates on the first carrier and receives the second message on the first carrier.

[0184] In a multi-carrier scenario, the UE can operate on the first carrier, the second carrier, or other carriers. When the UE is operating on the first carrier, it switches to the second carrier to receive the second message. In short, the UE will receive the second message on the anchor carrier.

[0185] In some embodiments, optional implementations of S2204 can be found in S2104 of the embodiment corresponding to FIG2A, and will not be repeated here. Similarly, descriptions of at least one of the network device, configuration information, and UE can be found in S2104 of the embodiment corresponding to FIG2A.

[0186] S2205: UE switches to RRC idle state and / or resumes uplink transmission.

[0187] In some embodiments, if the UE does not receive the second message, the UE switches to RRC idle state or resumes uplink transmission. For example, the UE's failure to receive the second message may be due to a failure to receive or decode the second message. For instance, in cases of poor channel quality, the UE may not receive the second message, or may be unable to successfully decode it.

[0188] In some embodiments, if the UE receives a second message during the timing period of the first timer and does not receive the second message until the first timer expires, the UE switches to RRC idle state or resumes uplink transmission.

[0189] If the UE switches to the RRC idle state when the first timer expires, the UE can enter a low-power state, thereby saving unnecessary power consumption.

[0190] In some embodiments, resuming uplink transmission may include: resuming uplink transmission on a second carrier.

[0191] In some embodiments, resuming uplink transmission may include: the MAC entity resuming uplink operation.

[0192] In some embodiments, resuming uplink transmission may include sending an uplink command to a network device on a first carrier.

[0193] In some embodiments, the uplink instruction includes one or more of the following: random access message; MACCE; RRC signaling.

[0194] In some embodiments, the random access message may include a contention-based random access message 1 or a non-contention-based random access message 1. Exemplarily, the random access message may include a random access preamble.

[0195] In some embodiments, MAC CE may include, but is not limited to, at least one of the following:

[0196] MAC CE includes a Buffer Size Report (BSR);

[0197] MAC CE includes a Time Advance (TA) report;

[0198] MAC CE includes a Power Headroom Report (PHR);

[0199] First MAC CE. Exemplarily, the first MAC CE may be dedicated to indicating that the second message has been received.

[0200] In some embodiments, the length of the payload of the first MAC CE may be 0.

[0201] In some embodiments, the first MAC CE has a first logical channel identifier (LCID) or a first extended logical channel identifier (eLCID).

[0202] For example, the first LCID is different from the LCID carried by other MAC CEs. The first eLCID is different from the eLCID carried by other MAC CEs.

[0203] For example, the first LCID or the first eLCID is carried in the MAC subheader.

[0204] In some embodiments, the RRC signaling includes, but is not limited to, RRC signaling containing UE assistance information. For example, the RRC signaling includes, but is not limited to, UE assistance information.

[0205] In some embodiments, in a single-carrier scenario, the UE enters the RRC idle state and / or resumes uplink transmission on the first carrier. The first carrier may be an anchor carrier. Alternatively, the first carrier may be a non-anchor carrier.

[0206] In some embodiments, in a multi-carrier scenario, the UE enters the RRC idle state and / or resumes uplink transmission on the first carrier. In this case, the first carrier may be different from the second carrier. The first carrier may be an anchor carrier or a non-anchor carrier.

[0207] In some embodiments, in a multi-carrier scenario, if the UE operates on the first carrier before receiving the second message, and the UE returns to the second carrier to receive the second message, then the UE can switch its operating carrier back to the first carrier.

[0208] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2205. For example, any one of steps S2201 to S2205 can be implemented as an independent embodiment. For example, the timing duration of the first timer is agreed upon by the protocol, or, if the first timer is not configured, then S2201 can be omitted. As another example, if the first timer times out, and the system waits for the network device to indicate whether to resume uplink, then S2205 can be omitted.

[0209] This disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2C, the method includes:

[0210] S2301: The network device sends a first message to the UE. In some embodiments, the relevant descriptions of the network device, the UE, and one or more of the first messages can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0211] In some embodiments, the optional operation for the network device to send the first message to the UE can be found in S2102 of the embodiment corresponding to FIG2A and S2202 of the embodiment corresponding to FIG2B.

[0212] S2302: UE suspends or stops uplink transmission.

[0213] In some embodiments, the relevant descriptions of pausing or stopping uplink transmission can be found in the relevant descriptions of the embodiments corresponding to Figures 2A and / or 2B.

[0214] In some embodiments, the UE may suspend or stop uplink transmission, as can be seen in S2103 of the embodiment corresponding to FIG2A and S2203 of the embodiment corresponding to FIG2B.

[0215] This disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2D, the method includes:

[0216] S2401: The network device sends the first message to the UE.

[0217] In some embodiments, the relevant descriptions of the network device, UE, and one or more of the first message can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0218] In some embodiments, the optional operation for the network device to send the first message to the UE can be found in S2102 of the embodiment corresponding to FIG2A and S2202 of the embodiment corresponding to FIG2B.

[0219] S2402: UE suspends or stops uplink transmission.

[0220] In some embodiments, the relevant description of stopping uplink transmission can be found in the relevant description of the corresponding embodiments of FIG2A and / or FIG2B.

[0221] In some embodiments, the UE stops uplink transmission, as can be seen in S2103 of the embodiment corresponding to FIG2A and S2203 of the embodiment corresponding to FIG2B.

[0222] S2403: The network device sends a second message.

[0223] In some embodiments, alternative implementations of the network device sending a second message can be found in S2104 of FIG2A and / or S2204 of the corresponding embodiment of FIG2B.

[0224] This disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2E, the method includes:

[0225] S2501: The network device sends the first message to the UE on the first carrier.

[0226] In some embodiments, the relevant descriptions of the network device, UE, and one or more of the first message can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0227] In some embodiments, the optional operation for the network device to send the first message to the UE can be found in S2102 of the embodiment corresponding to FIG2A and S2202 of the embodiment corresponding to FIG2B.

[0228] S2502: The UE suspends or stops uplink transmission on the first carrier.

[0229] In some embodiments, the relevant descriptions of pausing or stopping uplink transmission can be found in the relevant descriptions of the embodiments corresponding to Figures 2A and / or 2B.

[0230] S2503: The network device sends a second message to the UE on the first carrier.

[0231] In some embodiments, alternative implementations of the network device sending a second message can be found in S2104 of FIG2A and / or S2204 of the corresponding embodiment of FIG2B.

[0232] S2504: The UE resumes uplink transmission on the first carrier.

[0233] In some embodiments, the relevant descriptions for resuming uplink transmission can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0234] This disclosure provides a communication method, executed by the communication system shown in FIG1A. As shown in FIG2F, the method includes:

[0235] S2601: The network device sends the first message to the UE on the first carrier.

[0236] In some embodiments, the relevant descriptions of the network device, UE, and one or more of the first message can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0237] In some embodiments, the optional operation for the network device to send the first message to the UE can be found in S2102 of the embodiment corresponding to FIG2A and S2202 of the embodiment corresponding to FIG2B.

[0238] S2602: The UE suspends or stops uplink transmission on the first carrier.

[0239] In some embodiments, the relevant descriptions of pausing or stopping uplink transmission can be found in the relevant descriptions of the embodiments corresponding to Figures 2A and / or 2B.

[0240] S2603: The network device sends a second message to the UE on the second carrier.

[0241] In some embodiments, alternative implementations of the network device sending a second message can be found in S2104 of FIG2A and / or S2204 of the corresponding embodiment of FIG2B.

[0242] S2604: The UE resumes uplink transmission on the first carrier.

[0243] In some embodiments, the relevant descriptions for resuming uplink transmission can be found in the relevant descriptions of the embodiments corresponding to FIG2A and / or FIG2B.

[0244] This disclosure provides a method for a connected NB-IoT UE to receive PWS messages, enabling the terminal to receive ETWS messages and / or CMAS messages while minimizing the impact on data transmission.

[0245] In some embodiments, after receiving a PWS notification, the UE performs a first operation to obtain the corresponding PWS message. For example, it reads SIB10, 11, and / or 12 to obtain the PWS message contained in SIB10, SIB11, and / or SIB12.

[0246] In some embodiments, the first operation includes one or more of the following:

[0247] Clear all HARQ caches.

[0248] No uplink transmission is performed.

[0249] MAC entities suspend uplink operations, such as stopping RACH, stopping SR, and stopping uplink (UL) HARQ operations.

[0250] In some embodiments, when the UE completes the acquisition of the PWS message, the UE performs a second operation.

[0251] In some embodiments, the second operation includes one or more of the following:

[0252] Perform uplink transmission;

[0253] MAC entities resume uplink operations, such as resuming RACH, SR, and UL HARQ operations.

[0254] In some embodiments, the network configures a timer duration, during which the UE acquires PWS messages.

[0255] The UE receives a timer duration configured by the network, which indicates the maximum allowed time to acquire PWS messages. The timer duration parameter can be configured via system messages or RRC-specific signaling.

[0256] In some embodiments, a timer is started when the UE receives a PWS notification (e.g., carried in a direct indication message). The first timer stops when the UE has finished acquiring the PWS message. If the timer times out, the terminal stops acquiring PWS messages.

[0257] Furthermore, upon the expiration of the first timer, the terminal may perform at least one of the following operations:

[0258] Switch to RRC idle state.

[0259] Performing uplink transmissions or resuming uplink operations, for example, resuming uplink operations may include resuming RACH, SR, and / or UL HARQ operations.

[0260] In some embodiments, when the UE has obtained the PWS message, the UE sends a first uplink signaling to the network to notify the network to schedule subsequent data transmission.

[0261] In some embodiments, the first uplink signaling can be one or more of the following:

[0262] Random Access Channel (RACH) signaling, such as Msg1 or a random access preamble, can be either contention-based random access (CBRA) or contention-free random access (CFRA).

[0263] MAC CE, such as existing BSR MAC CE, PHR MAC CE, or TA report MAC CE, or a new MAC CE. The payload of a new MAC CE (e.g., named PWS completion MAC CE) can be 0 bytes long and is identified by a specific LCID or eLCID in the MAC subheader.

[0264] RRC signaling, for example, the RRC signaling may be a UE auxiliary information message.

[0265] In some embodiments, after receiving a PWS notification, the UE switches to the anchor carrier to receive PWS messages, and returns to the non-anchor carrier after completing the PWS message reception. For example, the anchor carrier may correspond to the aforementioned first carrier.

[0266] If the UE is currently operating on a non-anchor carrier, after receiving the PWS notification, the UE switches to an anchor carrier to receive PWS messages. Once the UE has finished acquiring the PWS message, it returns to its previous non-anchor carrier. The non-anchor carrier corresponds to the aforementioned second carrier. For example, the PWS notification may correspond to the aforementioned first message. The PWS message may correspond to the aforementioned second message.

[0267] In some embodiments, the first uplink signaling is transmitted via the preceding non-anchor carrier.

[0268] In some embodiments, the UE performs uplink transmission or resumes uplink operation on a non-anchor carrier.

[0269] Of course, the above are just examples, and the specific implementation is not limited to the examples above.

[0270] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0271] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0272] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0273] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0274] Figure 3A is a schematic diagram of the structure of a UE according to an embodiment of this disclosure. UE 3100 is used to perform any of the above methods. In some embodiments, as shown in Figure 3A, UE 3100 may include at least one of a first transceiver module 3101, a first processing module 3102, etc. In some embodiments, the first transceiver module 3101 is used to receive a first message sent by a network device on a first carrier; the first message is used to notify the UE to receive a second message; and to receive the second message sent by the network device on a second carrier; the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers. Optionally, the first transceiver module 3101 is used to perform the communication steps such as transmission and reception performed by the first network device in any of the above methods (e.g., at least one of steps such as S2101, S2102, S2104, S2201, S2202, S2204, S2301, S2401, S2403, S2501, S2503, S2601, S2603, etc.). Optionally, the first processing module 3102 described above is used to execute at least one of the other steps executed by the UE in any of the above methods (e.g., S2103, S2105, S2203, S2205, S2302, S2402, S2502, S2504, but not limited thereto), which will not be elaborated here.

[0275] Figure 3B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 3200 is used to perform any of the above methods. In some embodiments, as shown in Figure 3B, the network device 3200 may include at least one of a second transceiver module 3201, a second processing module 3202, etc. In some embodiments, the second transceiver module 3201 is used to send a first message to a user equipment (UE) on a first carrier; the first message is used to notify the UE to receive a second message; the second message is sent to the UE on a second carrier; the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers. Optionally, the second transceiver module 3201 is used to perform the transmission and reception communication steps performed by the second network device in any of the above methods, but in specific implementation, it is not limited to the step of receiving the first information. The second transceiver module 3201 described above can be used to execute at least one of the communication steps (such as S2101, S2101, S2102, S2104, S2201, S2202, S2204, S2301, S2401, S2403, S2501, S2503, S2601, S2603, etc.) performed by the second network device in any of the above methods, which will not be elaborated here. Optionally, the second processing module 3202 described above can be used to execute other steps performed by the network device in any of the above methods, which will not be elaborated here.

[0276] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0277] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0278] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0279] As shown in Figure 4A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0280] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S2101, S2102, S2103, but not limited thereto) in the above method, and the processor 6101 performs at least one of other steps (e.g., determining third information, determining a second network device, determining a third network device, determining a broadcast area, etc., in specific implementations but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0281] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102 and can be used to receive data and / or instructions from the memory 6102 or other devices, and can be used to send data and / or instructions to the memory 6102 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6102 and send the data and / or instructions to the processor 6101.

[0282] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG4A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0283] In some embodiments, one or more of the aforementioned first network device, second network device, third network device, and terminal can be collectively referred to as communication devices. One or more of the aforementioned first network device, second network device, third network device, and terminal can all be communication devices 6100.

[0284] Figure 4B is a schematic diagram of the structure of the chip 6200 proposed in an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 4B, but it is not limited thereto.

[0285] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0286] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0287] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., one or more of S2101, S2102, and S2103, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., one or more related steps such as determining third information, determining a second network device, determining a third network device, determining a broadcast area, etc., in specific implementations, but not limited thereto).

[0288] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0289] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0290] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0291] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, executed by a user equipment (UE), characterized in that, The method includes: The UE receives a first message sent by a network device on a first carrier; the first message is used to notify the UE to receive a second message. Receive the second message sent by the network device on the second carrier; The second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

2. The method according to claim 1, characterized in that, The first carrier is either a non-anchor carrier or an anchor carrier, and the second carrier is an anchor carrier.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Upon receiving the first message, pause or stop uplink transmission on the first carrier.

4. The method according to claim 3, characterized in that, Suspending or stopping uplink transmission on the first carrier includes: Uplink transmission on the first carrier is paused or stopped during the timing period of the first timer.

5. The method according to claim 4, characterized in that, The method further includes: The configuration information sent by the network device is received, and the configuration information is used to configure at least the first timer.

6. The method according to claim 5, characterized in that, The configuration information received from the network device includes one of the following: Receive system information sent by the network device, the system information including the configuration information; The network device receives RRC dedicated signaling, which includes the configuration information.

7. The method according to any one of claims 3 to 6, characterized in that, The cessation of uplink transmission on the first carrier includes at least one of the following: Clear the HARQ cache for Hybrid Automatic Retransmission Requests; The Media Access Control (MAC) entity suspends uplink operations on the first carrier.

8. The method according to any one of claims 3 to 7, characterized in that, The method further includes: Upon receiving the second message from the network device, uplink transmission on the first carrier is resumed.

9. The method according to claim 8, characterized in that, The resumption of uplink transmission on the first carrier includes: the MAC entity resuming uplink operation on the first carrier.

10. The method according to claim 7 or 9, characterized in that, The uplink operation includes uplink transmission.

11. The method according to any one of claims 3 to 6, characterized in that, The method further includes: When the first timer times out, the UE switches to RRC idle state; or, When the first timer expires, the UE resumes uplink transmission on the first carrier.

12. A communication method performed by a network device, the method comprising: The first message is sent to the user equipment (UE) on the first carrier. The first message is used to notify the UE to receive the second message; A second message sent to the UE on a second carrier; The second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers.

13. The method according to claim 12, characterized in that, The first carrier is a non-anchor carrier, and the second carrier is an anchor carrier.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Configuration information sent to a user equipment (UE), the configuration information being used to configure at least a first timer, the timing period of the first timer being used for the UE to receive the second message.

15. The method according to claim 14, characterized in that, The configuration information sent to the user equipment (UE) includes one of the following: System information sent to the UE, the system information including the configuration information; Send Radio Resource Control (RRC) dedicated signaling to the UE, the RRC dedicated signaling including the configuration information.

16. A communication method, characterized in that, The method includes: The network device sends a first message to the user equipment (UE) on the first carrier, the first message being used to notify the UE to receive a second message; The network device sends the second message to the UE on a second carrier; the second carrier and the first carrier are the same carrier; or, the second carrier and the first carrier are different carriers. The UE receives the first message sent by the network device on the first carrier. The UE receives the second message sent by the network device on the second carrier.

17. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 11, 12 to 15, and 16.

18. A communication system, characterized in that, The communication system includes: user equipment (UE) and network equipment; The UE is configured to perform the method according to any one of claims 1 to 11; The network device is configured to perform the method according to any one of claims 12 to 15.

19. A storage medium storing instructions, characterized in that, When the instructions are executed on a communication device, the communication device performs the method as described in any one of claims 1 to 11, 12 to 15, and 16.

20. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the steps of the method according to any one of claims 1 to 11, 12 to 15, and 16.

Images