Failure processing method, terminal, network device, system, and storage medium

Abstract

The present disclosure provides a failure processing method, a terminal, a network device, a system, and a storage medium. The method comprises: receiving a system message sent by a network device; verifying the validity of the system message, and determining a verification result; and when the verification result is that the verification fails, executing a first operation. In the present disclosure, a terminal can be prevented from accessing a pseudo base station, thereby improving the reliability of a radio access process, and achieving high availability.

Description

Failure handling methods, terminals, network devices, systems, and storage media Technical Field

[0001] This disclosure relates to the field of communications, and in particular to failure handling methods, terminals, network devices, systems, and storage media. Background Technology

[0002] Network devices can send system messages to terminals via broadcast. These system messages can be used to ensure that terminals can correctly access the network device. Summary of the Invention

[0003] To improve the reliability of the wireless access process, embodiments of this disclosure provide a failure handling method, a terminal, a network device, a system, and a storage medium.

[0004] According to a first aspect of the present disclosure, a failure handling method is provided, the method being executed by a terminal, the method comprising:

[0005] Receive system messages sent by network devices;

[0006] The validity of the system message is verified, and the verification result is determined;

[0007] The verification result is that the verification failed, so the first operation is executed.

[0008] According to a second aspect of the present disclosure, a failure handling method is provided, the method being executed by a network device, the method comprising:

[0009] A system message is sent to the terminal; wherein the system message is used by the terminal to perform validity verification, and if the verification result is a verification failure, the first operation is performed.

[0010] According to a third aspect of the present disclosure, a terminal is provided, comprising:

[0011] The transceiver module is configured to receive system messages sent by network devices;

[0012] The processing module is configured to verify the validity of the system message and determine the verification result;

[0013] The processing module is also configured to perform a first operation when the verification result is a verification failure.

[0014] According to a fourth aspect of the present disclosure, a network device is provided, comprising:

[0015] The transceiver module is configured to send system messages to the terminal; wherein the system messages are used by the terminal to perform validity verification, and if the verification result is a verification failure, a first operation is performed.

[0016] According to a fifth aspect of the present disclosure, a terminal is provided, comprising:

[0017] One or more processors;

[0018] The processor is used to execute the method described in any one of the first aspects.

[0019] According to a sixth aspect of the present disclosure, a network device is provided, comprising:

[0020] One or more processors;

[0021] The processor is used to execute the failure handling method described in any one of the second aspects.

[0022] According to a seventh aspect of the present disclosure, a communication system is provided, comprising:

[0023] A terminal, the terminal being configured to implement the failure handling method described in any one of the first aspects;

[0024] A network device configured to implement the failure handling method described in any one of the second aspects.

[0025] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a failure handling method as described in any one of the first or second aspects.

[0026] According to a ninth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, is used to implement the failure handling method described in any one of the first or second aspects.

[0027] In this embodiment of the disclosure, the terminal can verify the validity of system messages, and if the verification result is a failure, perform a first operation to prevent the terminal from accessing a fake base station and improve the reliability of the wireless access process.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

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

[0031] Figure 1B is an exemplary interactive diagram of system message security verification provided according to an embodiment of the present disclosure.

[0032] Figure 2 is one of the exemplary interactive diagrams of a failure handling method provided according to an embodiment of the present disclosure.

[0033] Figure 3A is one of the exemplary flowcharts of a failure handling method provided according to an embodiment of the present disclosure.

[0034] Figure 3B is a second exemplary flowchart of a failure handling method provided according to an embodiment of the present disclosure.

[0035] Figure 3C is a third exemplary flowchart of a failure handling method provided according to an embodiment of the present disclosure.

[0036] Figure 3D is a fourth exemplary flowchart of a failure handling method provided according to an embodiment of the present disclosure.

[0037] Figure 4 is a second exemplary interactive schematic diagram of the failure handling method provided according to an embodiment of the present disclosure.

[0038] Figure 5A is an exemplary block diagram of a terminal provided according to an embodiment of the present disclosure.

[0039] Figure 5B is an exemplary block diagram of a network device provided according to an embodiment of the present disclosure.

[0040] Figure 6A is an exemplary interactive schematic diagram of a communication device provided according to an embodiment of the present disclosure.

[0041] Figure 6B is an exemplary interactive schematic diagram of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0042] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0043] This disclosure provides a failure handling method, a terminal, a network device, a system, and a storage medium.

[0044] In a first aspect, embodiments of this disclosure propose a failure handling method, which is executed by a terminal. The method includes: receiving a system message sent by a network device; verifying the validity of the system message and determining a verification result; if the verification result is a verification failure, performing a first operation.

[0045] In the above embodiments, the terminal can verify the validity of system messages, and if the verification result is a failure, it can perform the first operation to prevent the terminal from accessing fake base stations and improve the reliability of the wireless access process.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, performing the first operation includes: performing a first operation corresponding to the Radio Resource Control (RRC) state in which the terminal is located.

[0047] In the above embodiments, the terminal can perform the corresponding first operation based on its own RRC state, which clarifies the terminal behavior when the system message validity verification fails, thereby improving the reliability of the wireless access process.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal is in an RRC connection state, and the first operation includes at least one of the following: ignoring the system message; RRC connection reconstruction operation.

[0049] In the above embodiments, the terminal can perform the first operation in RRC connection state to restore the connection with the network side, avoid the terminal accessing fake base stations, improve the reliability of the wireless access process, and have high availability.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the RRC state is an RRC idle state or an RRC inactive state, and the first operation includes at least one of the following: ignoring the system message; cell reselection; cell selection.

[0051] In the above embodiments, the terminal can perform the first operation in the RRC idle state or the RRC inactive state to restore the connection with the network side, avoid the terminal accessing fake base stations, improve the reliability of the wireless access process, and have high availability.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the first operation includes ignoring the system message, and the method further includes any one of the following: no longer receiving the system message; no longer receiving the system message for a first duration.

[0053] In the above embodiments, if the terminal ignores the system message, it may stop receiving the system message or stop receiving the system message for a certain period of time. This clarifies the terminal behavior when the validity verification of the system message fails, thereby improving the reliability of the wireless access process.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the first operation includes any one of an RRC connection re-establishment operation, a cell reselection operation, and a cell selection operation. The method further includes any one of the following: during the execution of the first operation, selecting a second cell and / or selecting a second frequency point; during the execution of the first operation within a first duration, selecting a second cell and / or selecting a second frequency point; during the execution of the first operation, setting the priority of the first cell and / or the first frequency point to the lowest; during the execution of the first operation within a first duration, setting the priority of the first cell and / or the first frequency point to the lowest; during the execution of the first operation, setting the first cell and / or the first frequency point to prohibit access; during the execution of the first operation within a first duration, setting the first cell and / or the first frequency point to prohibit access; wherein, the second cell is different from the first cell, the first cell is the cell providing the system message, and the second frequency point is different from the first frequency point, the first frequency point is the transmission frequency point of the system message.

[0055] In the above embodiments, when the terminal performs the first operation, it can select a suitable cell and / or a suitable frequency point, or set the priority of the first cell and / or the first frequency point to the lowest, or set the first cell and / or the first frequency point to prohibit access. This clarifies the terminal behavior in the event of failure to verify the validity of the system message, and improves the reliability of the wireless access process.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving first information sent by a network device; determining the first information based on a predefined method; wherein the first information is used to verify the validity of the system message.

[0057] In the above embodiments, the terminal can quickly determine the first piece of information, improving the reliability and timeliness of validating system messages.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: a first security certificate; a first key.

[0059] In the above embodiments, the first information may include, but is not limited to, at least one of the above, so that the terminal can verify the validity of the system message, which is simple to implement and highly usable.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, verifying the validity of the system message includes at least one of the following: verifying the validity of the second security certificate in the system message based on the first security certificate; verifying the validity of the signature information of the system message based on the first key; wherein the signature information is generated based on the system message and the second key corresponding to the network device.

[0061] In the above embodiments, the terminal can verify the validity of system messages to prevent the terminal from accessing fake base stations and improve the reliability of the wireless access process.

[0062] Secondly, this disclosure provides a failure handling method, which is executed by a network device. The method includes: sending a system message to a terminal; wherein the system message is used by the terminal to perform validity verification, and if the verification result is a verification failure, performing a first operation.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the first operation corresponds to the Radio Resource Control (RRC) state in which the terminal is located.

[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal is in an RRC connection state, and the first operation includes at least one of the following: ignoring the system message; RRC connection reconstruction operation.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal is in an RRC idle state or an RRC inactive state, and the first operation includes at least one of the following: ignoring the system message; cell reselection; cell selection.

[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: sending first information to the terminal; wherein the first information is used to verify the validity of the system message.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following: a first security certificate; a first key.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the system message includes at least one of the following: a second security certificate; signature information; wherein the signature information is generated based on the system message and a second key corresponding to the network device.

[0069] Thirdly, this disclosure provides a terminal, including: a transceiver module configured to receive system messages sent by a network device; a processing module configured to verify the validity of the system messages and determine a verification result; the processing module is further configured to perform a first operation if the verification result is a verification failure.

[0070] Fourthly, this disclosure provides a network device, including: a transceiver module configured to send system messages to a terminal; wherein the system messages are used by the terminal to perform validity verification, and if the verification result is a verification failure, a first operation is performed.

[0071] Fifthly, embodiments of this disclosure provide a terminal comprising: one or more processors; wherein the processors are configured to perform the method described in any one of the first aspects.

[0072] In a sixth aspect, embodiments of this disclosure provide a network device comprising: one or more processors; wherein the processors are configured to execute the failure handling method described in any one of the second aspects.

[0073] In a seventh aspect, embodiments of this disclosure provide a communication system comprising: a terminal configured to implement the failure handling method described in any one aspect; and a network device configured to implement the failure handling method described in any one aspect.

[0074] Eighthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform a failure handling method as described in any one of the first or second aspects.

[0075] In a ninth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, is used to implement the failure handling method described in any one of the first or second aspects.

[0076] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0077] This disclosure provides a failure handling method, a terminal, a network device, a system, and a storage medium. In some embodiments, the terms failure handling method, information processing method, communication method, etc., may be used interchangeably.

[0078] 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.

[0079] 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.

[0080] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "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.

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

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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.

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

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

[0088] 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.

[0089] 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”.

[0090] 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.

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

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

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

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

[0098] 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.

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

[0100] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.

[0101] 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.

[0102] In some embodiments, network device 102 includes, but is not limited to, at least one of access network device 102-1 and core network device 102-2.

[0103] In some embodiments, the access network device 102-1 is, for example, 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: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0104] In some embodiments, the technical solutions of this disclosure can be applied to the 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 Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0105] In some embodiments, the access network device 102-1 may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. By adopting the CU-DU structure, the protocol layer of the access network device can be separated. 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, which is centrally controlled by the CU. However, this is not the only possibility.

[0106] In some embodiments, the core network device 102-2 may be a single device comprising multiple network elements, or it may be multiple devices or a group of devices, each comprising some or all of the multiple network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0107] 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.

[0108] 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.

[0109] 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).

[0110] In some embodiments, the system message broadcast by the network device may be one or more System Information Blocks (SIBs). One or more SIBs may be included in a single System Information Message (SI message) and sent within it.

[0111] In some embodiments, this disclosure provides a system message verification method, as shown in Figure 1B, which includes the following steps:

[0112] In step S1201a, the security authorization unit sends a "base station-related security certificate" to the access network device, such as a base station.

[0113] The "base station-related security certificate" contains a "public key" and a "private key".

[0114] Among them, the security authorization unit can be a core network functional element.

[0115] Step S1201b: The terminal obtains the "security root certificate".

[0116] The "security root certificate" includes the "public key".

[0117] The terminal can obtain the "security root certificate" from the factory settings, or it can obtain the "security root certificate" from the security authorization unit through the registration process.

[0118] Step S1202: The base station broadcasts system information.

[0119] In some embodiments, the base station broadcasts "signature information" and "base station-related security certificate" to the terminal.

[0120] The "signature information" is generated by the base station using "system information" and "private key".

[0121] Among them, the "base station related security certificate" contains a "public key" used to verify the "signature information".

[0122] In step S1203, the terminal uses a "security root certificate" to verify the validity of the "base station-related security certificate".

[0123] In step S1204, the terminal uses the "public key" to verify the validity of the "signature information".

[0124] This disclosure does not limit the execution order of the above steps S1203 and S1204.

[0125] In some embodiments, the term "barred" is described as follows:

[0126] For cells set to "barred" status, terminals are not allowed to camp.

[0127] If the terminal does not obtain the Master Indication Block (MIB) for the target cell, the terminal can set the cell to "barred".

[0128] For the target cell, if the MIB indicates that intra-frequency reselection is "not allowed", the terminal will set other intra-frequency cells to "barred".

[0129] In some embodiments, if the validity of system messages is verified, the terminal needs to avoid reconnecting to the base station if the verification fails, thereby avoiding fake base station attacks.

[0130] To improve the reliability of the wireless access process, this disclosure provides the following failure handling methods, terminals, network devices, systems, and storage media.

[0131] Figure 2 is an interactive schematic diagram of a failure handling method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to a failure handling method, which includes:

[0132] In step S2101, network device 102 sends a system message to terminal 101.

[0133] In some embodiments, network device 102 may broadcast system messages to at least one terminal 101.

[0134] In some embodiments, terminal 101 receives system messages.

[0135] In some embodiments, the system message includes at least one SIB.

[0136] In some embodiments, network device 102 may periodically send system messages to terminal 101.

[0137] In some embodiments, network device 102 may send system messages to terminal 101 based on a request from terminal 101.

[0138] In step S2102a, network device 102 sends first information to terminal 101.

[0139] In some embodiments, terminal 101 receives first information.

[0140] In some embodiments, the first information can be used to verify the validity of the system message.

[0141] In some embodiments, the first information may include, but is not limited to, at least one of the following: a first security certificate; a first key.

[0142] In one example, the first security certificate could be a "security root certificate," which is a core component of the digital certificate system and is a self-signed certificate issued by a trusted Certificate Authority (CA). It is the starting point of the digital certificate trust chain and has the highest level of trust.

[0143] In one example, the first key can be the "public key" of network device 102, such as an access network device. A "public key" is a key that can be made public to multiple devices.

[0144] In one example, if network device 102 is an access network device, then the access network device can send the first information to terminal 101 through system messages.

[0145] In one example, network device 102 is a core network device, such as a security authorization unit, and the core network device can send the first information to terminal 101 during the registration process of terminal 101.

[0146] In one example, the first key may be included in the first security certificate.

[0147] In one example, the first key and the first security certificate are independent and can be sent separately by network device 102 to terminal 101.

[0148] In some embodiments, when the terminal 101 registers or accesses the network, the network device 102 sends first information to the terminal 101.

[0149] In some embodiments, network device 102 may send first information to terminal 101 based on a request from terminal 101.

[0150] In some embodiments, step S2102a is an optional execution step. For example, if the terminal 101 receives the first information from another execution entity or determines the first information using a predefined method, step S2102a may not be executed.

[0151] In step S2102b, terminal 101 determines the first information.

[0152] In some embodiments, terminal 101 may determine the first information based on a predefined method.

[0153] In one example, terminal 101 may determine this first information based on factory settings.

[0154] In some embodiments, terminal 101 may receive first information sent by network device 102.

[0155] In step S2103, terminal 101 verifies the validity of the system message and determines the verification result.

[0156] In some embodiments, terminal 101 may verify the validity of system messages based on first information, thereby determining the verification result.

[0157] In one example, the verification result can be "verification successful," at which point terminal 101 can determine that the system message is valid. Furthermore, based on this system message, terminal 101 can access network device 102, for example, by initiating random access using a two-step or four-step random access method, thereby accessing network device 102.

[0158] In one example, the verification result may be verification failure. In this case, terminal 101 can determine that the system message is invalid. This system message may come from a fake base station or an unauthorized network device.

[0159] In some embodiments, terminal 101 may verify the validity of the second security certificate in the system message based on the first security certificate, and / or may verify the validity of the signature information of the system message based on the first key.

[0160] In one example, the second security certificate could be a security certificate provided by the core network device to the access network device, such as the security certificate of the base station.

[0161] In one example, the signature information can be generated based on system messages and a second key corresponding to network device 102. This second key can be the private key of the network device, such as an access network device; a private key is a key that can only be used by the device itself and cannot be disclosed to other devices.

[0162] In one example, if terminal 101 fails to verify the validity of the second security certificate in the system message, and / or fails to verify the validity of the signature information in the system message, then terminal 101 determines the verification result as a verification failure.

[0163] In one example, if terminal 101 successfully verifies the validity of the second security certificate in the system message and successfully verifies the validity of the signature information in the system message, then terminal 101 determines the verification result as successful.

[0164] In step S2104, terminal 101 performs the first operation.

[0165] In some embodiments, if the verification result is a verification failure, terminal 101 performs a first operation.

[0166] In some embodiments, the first operation may be an operation to restore the connection between terminal 101 and network device 102.

[0167] In some embodiments, the first operation may be a related operation for failure handling.

[0168] In some embodiments, the first operation may be an operation to avoid access to fake base stations or unauthorized network devices.

[0169] In some embodiments, the name of the first operation is not limited and can be interchanged with connection recovery operation, failure handling operation, etc.

[0170] In some embodiments, the first operation may be related to the Radio Resource Control (RRC) state in which the terminal 101 is located.

[0171] In some embodiments, the RRC state of terminal 101 includes, but is not limited to, at least one of the following: RRC connected state (RRC_CONNECTED); RRC idle state (RRC_IDLE); RRC inactive state (RRC_INACTIVE).

[0172] Among them, RRC connection state refers to the state in which terminal 101 maintains a connection with the network side and can initiate or receive data transmission at any time.

[0173] In this context, the RRC idle state refers to a state where terminal 101 has no connection with the network side. When terminal 101 wants to initiate data transmission, it needs to re-establish a connection with the network side.

[0174] Among them, the RRC inactive state refers to the state in which terminal 101 maintains a connection with the network but does not allocate any resources or transmit any data.

[0175] In some embodiments, if terminal 101 is in RRC connection state, the first operation may include, but is not limited to, at least one of the following: ignoring the system message; RRC connection reconstruction operation.

[0176] In some embodiments, if terminal 101 is in RRC idle state, the first operation may include, but is not limited to, at least one of the following: ignoring the system message; cell reselection; cell selection.

[0177] In some embodiments, if terminal 101 is in an RRC inactive state, the first operation may include, but is not limited to, at least one of the following: ignoring the system message; cell reselection; cell selection.

[0178] In some embodiments, terminal 101 may perform a first operation corresponding to its current RRC state.

[0179] In step S2105, terminal 101 performs processing related to the first operation.

[0180] In some embodiments, the processing here includes at least one of the following: no longer receiving system messages; selecting a second frequency point and / or a second cell during the execution of the first operation; setting the priority of the first cell and / or the first frequency point to the lowest during the execution of the first operation; setting the first cell and / or the first frequency point to be blocked from access during the execution of the first operation.

[0181] The second cell is different from the first cell, which is the cell that provides the system messages.

[0182] The second frequency point is different from the first frequency point, which is the transmission frequency point of the system message.

[0183] In some embodiments, the first operation performed by terminal 101 includes ignoring the system message, in which case terminal 101 may no longer receive the system message.

[0184] In some embodiments, the first operation performed by terminal 101 includes ignoring the system message, in which case terminal 101 may stop receiving the system message for a first period of time.

[0185] In one example, terminal 101 may determine the first duration based on a predefined method and / or instructions from the network device.

[0186] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection re-establishment operation, a cell reselection operation, and a cell selection operation. In the process of performing the first operation, the terminal may select a second cell and / or select a second frequency point.

[0187] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection re-establishment operation, a cell reselection operation, and a cell selection operation. In this case, the terminal may select a second cell and / or select a second frequency point during the execution of the first operation within a first time period.

[0188] In one example, terminal 101 may determine the first duration based on a predefined method and / or instructions from the network device.

[0189] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection re-establishment operation, a cell reselection operation, and a cell selection operation. In the process of performing the first operation, the terminal may set the priority of the first cell and / or the first frequency point to the lowest.

[0190] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection re-establishment operation, a cell reselection operation, and a cell selection operation. In this case, the terminal may set the priority of the first cell and / or the first frequency point to the lowest during the execution of the first operation within a first time period.

[0191] In one example, terminal 101 may determine the first duration based on a predefined method and / or instructions from the network device.

[0192] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection reconstruction operation, a cell reselection operation, or a cell selection operation. In this case, the terminal may set the first cell and / or the first frequency point to be blocked from access during the execution of the first operation.

[0193] In some embodiments, the first operation performed by the terminal 101 includes any one of an RRC connection reconstruction operation, a cell reselection operation, and a cell selection operation. In this case, the terminal may set the first cell and / or the first frequency point to be blocked from access during the execution of the first operation within a first time period.

[0194] In one example, terminal 101 may determine the first duration based on a predefined method and / or instructions from the network device.

[0195] In some embodiments, the names of information, etc., are not limited to the names 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.

[0196] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0197] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0198] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0199] In some embodiments, the failure handling method involved in this disclosure may include at least one of steps S2101 to S2105. For example, step S2101 may be implemented as a standalone embodiment, step S2102a may be implemented as a standalone embodiment, step S2102b may be implemented as a standalone embodiment, step S2102a + step S2102b may be implemented as a standalone embodiment, step S2103 may be implemented as a standalone embodiment, step S2104 may be implemented as a standalone embodiment, step S2103 + S2104 may be implemented as a standalone embodiment, step S2105 may be implemented as a standalone embodiment, and steps S2101 to S2105 may be implemented as standalone embodiments, but are not limited thereto.

[0200] In some embodiments, steps S2101 to S2105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0201] In some embodiments, the execution order of steps S2101 to S2105 is not limited.

[0202] In the above embodiments, terminal access to fake base stations can be avoided, thereby improving the reliability of the wireless access process.

[0203] Figure 3A is a flowchart illustrating a failure handling method according to an embodiment of the present disclosure. As shown in Figure 3A, this embodiment of the present disclosure relates to a failure handling method, which can be executed by terminal 101, and includes the following steps:

[0204] Step S3101: Obtain system messages.

[0205] In some embodiments, terminal 101 receives system messages sent by network device 102, but is not limited thereto. Terminal 101 may also receive system messages sent by other entities, such as relay devices or other terminals, in which case step S3201 may be omitted.

[0206] In some embodiments, terminal 101 obtains system messages defined by the protocol, in which case step S3101 is omitted.

[0207] In some embodiments, the terminal 101 obtains system messages from the upper layer(s), in which case step S3101 is omitted.

[0208] In some embodiments, the terminal 101 processes the data to obtain system messages, in which case step S3101 is omitted.

[0209] In some embodiments, the terminal 101 autonomously implements the function indicated by the system message, or the above function is a default or default value, in which case step S3101 is omitted.

[0210] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2101 in FIG2 and its optional implementation, and other related parts in the specification, which will not be repeated here.

[0211] Step S3102: Determine the verification result.

[0212] In some embodiments, terminal 101 may verify the validity of the system message and determine the verification result.

[0213] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2103 in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0214] Step S3103: Perform the first operation.

[0215] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2104 in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0216] In some embodiments, steps S3101 to S3103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0217] In some embodiments, the execution order of steps S3101 to S3103 is not limited.

[0218] In the above embodiments, the terminal can verify the validity of system messages, and if the verification result is a failure, it can perform a first operation to prevent the terminal from accessing a fake base station and improve the reliability of the wireless access process.

[0219] Figure 3B is a flowchart illustrating a failure handling method according to an embodiment of the present disclosure. As shown in Figure 3B, this embodiment of the present disclosure relates to a failure handling method, which can be executed by terminal 101, and includes the following steps:

[0220] Step S3201: Obtain system messages.

[0221] In some embodiments, terminal 101 receives system messages sent by network device 102, but is not limited thereto. Terminal 101 may also receive system messages sent by other entities, such as relay devices or other terminals, in which case step S3201 may be omitted.

[0222] In some embodiments, terminal 101 obtains system messages defined by the protocol, in which case step S3201 is omitted.

[0223] In some embodiments, the terminal 101 obtains system messages from the upper layer(s), in which case step S3201 is omitted.

[0224] In some embodiments, the terminal 101 processes the data to obtain system messages, in which case step S3201 is omitted.

[0225] In some embodiments, the terminal 101 autonomously implements the function indicated by the system message, or the above function is default or default, in which case step S3201 is omitted.

[0226] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2101 in FIG2 and its optional implementation, and other related parts in the specification, which will not be repeated here.

[0227] Step S3202: Determine the first information.

[0228] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2102b in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0229] Step S3203: Determine the verification result.

[0230] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2103 in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0231] Step S3204: Perform the first operation.

[0232] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2104 in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0233] Step S3205: Perform the relevant processing.

[0234] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2105 in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0235] In some embodiments, steps S3201 to S3205 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0236] In some embodiments, the execution order of steps S3201 to S3205 is not limited.

[0237] In the above embodiments, the terminal can verify the validity of the system message based on the determined first information, and perform the first operation if the verification result is a verification failure, thereby preventing the terminal from accessing a fake base station and improving the reliability of the wireless access process.

[0238] Figure 3C is a flowchart illustrating a failure handling method according to an embodiment of the present disclosure. As shown in Figure 3C, this embodiment of the present disclosure relates to a failure handling method, which can be executed by network device 102, and includes the following steps:

[0239] Step S3301: Send a system message.

[0240] In some embodiments, network device 102 sends system messages to terminal 101.

[0241] In some embodiments, terminal 101 receives system messages.

[0242] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2101 in FIG2 and its optional implementation, and other related parts in the specification, which will not be repeated here.

[0243] In the above embodiments, the network device can send system messages to the terminal so that the terminal can verify the validity of the system messages. If the verification result is a failure, the first operation is performed to prevent the terminal from accessing a fake base station and improve the reliability of the wireless access process.

[0244] Figure 3D is a flowchart illustrating a failure handling method according to an embodiment of the present disclosure. As shown in Figure 3D, this embodiment of the disclosure relates to a failure handling method, which can be executed by network device 102, and includes the following steps:

[0245] Step S3401: Send a system message.

[0246] In some embodiments, network device 102 sends system messages to terminal 101.

[0247] In some embodiments, terminal 101 receives system messages.

[0248] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2101 in FIG2 and its optional implementation, and other related parts in the specification, which will not be repeated here.

[0249] Step S3402: Send the first message.

[0250] In some embodiments, network device 102 sends first information to terminal 101.

[0251] In some embodiments, terminal 101 receives first information.

[0252] In some embodiments, the first information can be used to verify the validity of the system message.

[0253] In some embodiments, reference can be made to the steps in other embodiments described before or after this embodiment, such as step S2102a in FIG2 and its optional implementation, as well as other related parts in the specification, which will not be repeated here.

[0254] In some embodiments, steps S3401 to S3402 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0255] In some embodiments, the execution order of steps S3401 to S3402 is not limited.

[0256] In the above embodiments, the network device can send system messages and first information to the terminal so that the terminal can verify the validity of the system messages based on the first information, and perform the first operation if the verification result is a failure, thereby preventing the terminal from accessing fake base stations and improving the reliability of the wireless access process.

[0257] The above process is further illustrated with examples below.

[0258] In this embodiment of the disclosure, the terminal adopts a specific recovery behavior when the system information obtained in different states fails to be verified, based on its RRC status. This can avoid receiving the system information that failed to be verified again and can restore the failed connection.

[0259] If the validity verification of a system message (or System Information Block (SIB) fails, the terminal may, according to the network device configuration or protocol agreement, execute a "system message (or, System Information Block (SIB) validity verification failure recovery process" based on its current RRC connection state. This "system message (or, System Information Block (SIB) validity verification failure recovery process" includes any of the following:

[0260] For terminals in RRC connected state, the "system message (or, system information block SIB) validity verification failure recovery process" includes any of the following:

[0261] Method 1: Ignore the system message (or, System Information Block (SIB)).

[0262] Method 2, triggers the connection reconstruction process.

[0263] For terminals in RRC idle or RRC inactive states, the "System Message (or System Information Block SIB) validity verification failure recovery process" includes any of the following:

[0264] Method 1: Ignore the system message (or, System Information Block (SIB));

[0265] Method 2: Perform the cell reselection (or selection) process.

[0266] Method 2.1, the cell reselection (or selection) process excludes "cells or frequencies that send system information (or, system information block SIB)".

[0267] Method 2.2, the cell reselection (or selection) process sets the reselection priority of "the cell or frequency that sends the system information (or, system information block SIB)" to the lowest.

[0268] Method 3: Set the cell or frequency point that sends the system information (or system information block SIB) to be barred, for example, barred.

[0269] Example 1, as shown in Figure 4, includes the following steps in the failure handling process:

[0270] In step S4101, the terminal receives a key and / or security certificate configured by the network for verifying the validity of system messages (or system information blocks SIBs).

[0271] In one example, the terminal obtains the password and / or security certificate from the base station.

[0272] In one example, the terminal obtains the password and / or security certificate from the security authorization unit, i.e., the core network device.

[0273] In one example, the terminal obtains a security certificate from the security authorization unit, i.e., the core network device, and obtains a key from the base station side.

[0274] In one example, the terminal obtains a key from the security authorization unit, i.e., the core network device, and a security certificate from the base station side.

[0275] Step S4102: The terminal receives a system message (or System Information Block (SIB)).

[0276] The terminal determines the validity of the received system message (or system information block SIB) based on the verification information corresponding to the system message (or system information block SIB).

[0277] For example, verify the "signature information" of system messages, where Signature or MAC-I (Message Authentication Code for Integrity) is used for integrity verification.

[0278] Step S4103: The terminal performs a recovery process after the validity verification fails.

[0279] If the validity verification of a system message (or System Information Block (SIB) fails, the terminal, according to its RRC connection state, will execute a "system message (or SIB) validity verification failure recovery process" based on the network configuration or protocol agreement. This "system message (or SIB) validity verification failure recovery process" includes any of the following:

[0280] For terminals in RRC connected state, the "system message (or system information block SIB) validity verification failure recovery process" includes any of the following:

[0281] Method 1: Ignore the system message (or System Information Block (SIB)). Further, it can be specified that the terminal will not receive the system message (or SIB) for a specified duration.

[0282] Method 2, triggering a connection reconstruction process. Further, the connection reconstruction process excludes cells or frequencies that "transmit system information (or, System Information Block (SIB)") from the selected cells or frequencies. Further, it can be limited that the terminal excludes cells or frequencies that "transmit system information (or, System Information Block (SIB))" from the selected cells or frequencies for a specified duration.

[0283] For terminals in RRC idle or RRC inactive states, the "System Message (or System Information Block SIB) validity verification failure recovery process" includes any of the following:

[0284] Method 1: Ignore the system message (or System Information Block (SIB)). Further, it can be specified that the terminal will not receive the system message (or SIB) for a specified duration.

[0285] Method 2 involves performing a cell reselection (or selection) process. Furthermore, this cell reselection (or selection) process, regarding the processing of "cells or frequencies transmitting system information (or System Information Block SIBs)", includes any of the following:

[0286] Method 2.1, the cell reselection (or selection) process excludes cells or frequencies that "transmit system information (or, system information block SIB)". Furthermore, the cell reselection (or selection) process can be limited to a specified time period to exclude cells or frequencies that "transmit system information (or, system information block SIB)".

[0287] Method 2.2: The cell reselection (or selection) process sets the reselection priority of the cell or frequency point that transmits system information (or, system information block SIB) to the lowest. Furthermore, the reselection (or selection) process can be limited to a specified time period, during which the reselection priority of the cell or frequency point that transmits system information (or, system information block SIB) is set to the lowest.

[0288] Method 3 involves setting the cell or frequency point that sends the system information (or system information block SIB) to be barred from access (e.g., barred). Furthermore, this can be limited to a specified time period.

[0289] 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.

[0290] 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.

[0291] 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).

[0292] Figure 5A is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. The terminal 5100 is used to execute any of the above methods. In some embodiments, as shown in Figure 5A, the terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102.

[0293] In some embodiments, the transceiver module 5101 is used to receive system messages sent by the network device.

[0294] In some embodiments, the processing module 5102 is used to verify the validity of the system message and determine the verification result; if the verification result is a verification failure, the first operation is performed.

[0295] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps (such as step S2101, step S2102a, but not limited thereto) performed by the terminal 5100 in any of the above methods, which will not be described in detail here.

[0296] Optionally, the processing module 5102 is used to execute at least one of the other steps executed by the terminal 5100 in any of the above methods (e.g., step S2102b, step S2103, step S2104, step S2105, but not limited thereto), which will not be elaborated here.

[0297] Figure 5B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the network device 5200 may include a transceiver module 5201.

[0298] In some embodiments, the transceiver module 5201 is used to send measurement reporting configuration to the terminal when there are multiple first beams; wherein the measurement reporting configuration includes measurement event configuration; wherein the first beam is a beam available to the terminal or a beam used by the terminal.

[0299] Optionally, the transceiver module 5201 is used to perform at least one of the communication steps (such as step S2101, step S2102a, but not limited thereto) performed by the network device 5200 in any of the above methods, which will not be described in detail here.

[0300] 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.

[0301] 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.

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

[0303] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0304] As shown in Figure 6A, 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.

[0305] 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 such as sending and / or receiving in the above method (e.g., steps S2101, S2102a, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2102b, S2103, S2104, S2105, 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.

[0306] 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 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.

[0307] 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 FIG. 6A. The communication device may be a standalone device or a 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.

[0308] Figure 6B is a schematic diagram of the structure of chip 6200 according to 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 chip 6200 shown in Figure 6B, but it is not limited thereto.

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

[0310] 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.

[0311] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102a, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above 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., steps S2102b, S2103, S2104, S2105, but not limited thereto).

[0312] 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.

[0313] 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 above methods. 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.

[0314] 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.

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

[0316] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0317] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A failure handling method, characterized in that, The method is executed by a terminal, and the method includes: Receive system messages sent by network devices; The validity of the system message is verified, and the verification result is determined; The verification result is that the verification failed, so the first operation is executed.

2. The method according to claim 1, characterized in that, The execution of the first operation includes: Based on the Radio Resource Control (RRC) state of the terminal, a first operation corresponding to the RRC state is executed.

3. The method according to claim 2, characterized in that, The terminal is in RRC connection mode, and the first operation includes at least one of the following: The operation of ignoring the system message; RRC connection rebuild operation.

4. The method according to claim 2, characterized in that, The RRC state is either an RRC idle state or an RRC inactive state, and the first operation includes at least one of the following: The operation of ignoring the system message; Cell reselection operation; Community selection operation.

5. The method according to claim 3 or 4, characterized in that, The first operation includes ignoring the system message, and the method further includes any one of the following: The system messages will no longer be received; During the first time period, no more system messages will be received.

6. The method according to claim 3 or 4, characterized in that, The first operation includes any one of RRC connection reconstruction operation, cell reselection operation, and cell selection operation, and the method further includes any one of the following: During the execution of the first operation, a second cell and / or a second frequency point are selected; During the execution of the first operation within the first time period, a second cell and / or a second frequency point are selected; During the execution of the first operation, the priority of the first cell and / or the first frequency point is set to the lowest. During the execution of the first operation within the first duration, the priority of the first cell and / or the first frequency point is set to the lowest. During the execution of the first operation, the first cell and / or the first frequency point are set to be blocked from access; During the execution of the first operation within the first time period, the first cell and / or the first frequency point are set to be blocked from access; The second cell is different from the first cell, which is the cell that provides the system messages. The second frequency point is different from the first frequency point, which is the transmission frequency point of the system messages.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive the first information sent by the network device; The first piece of information is determined based on a predefined method; The first piece of information is used to verify the validity of the system message.

8. The method according to claim 7, characterized in that, The first information includes at least one of the following: First security certificate; First key.

9. The method according to claim 8, characterized in that, The verification of the validity of the system message includes at least one of the following: Based on the first security certificate, the validity of the second security certificate in the system message is verified; The validity of the signature information of the system message is verified based on the first key; wherein the signature information is generated based on the second key corresponding to the system message and the network device.

10. A failure handling method, characterized in that, The method is performed by a network device, and the method includes: A system message is sent to the terminal; wherein the system message is used by the terminal to perform validity verification, and if the verification result is a verification failure, the first operation is performed.

11. The method according to claim 10, characterized in that, The first operation corresponds to the Radio Resource Control (RRC) state in which the terminal is located.

12. The method according to claim 11, characterized in that, The terminal is in RRC connection mode, and the first operation includes at least one of the following: The operation of ignoring the system message; RRC connection rebuild operation.

13. The method according to claim 11, characterized in that, When the terminal is in an RRC idle state or an RRC inactive state, the first operation includes at least one of the following: The operation of ignoring the system message; Cell reselection operation; Community selection operation.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: Send first information to the terminal; wherein the first information is used to verify the validity of the system message.

15. The method according to claim 14, characterized in that, The first information includes at least one of the following: First security certificate; First key.

16. The method according to claim 15, characterized in that, The system message includes at least one of the following: Second security certificate; Signature information; wherein the signature information is generated based on the system message and the second key corresponding to the network device.

17. A terminal, characterized in that, include: The transceiver module is configured to receive system messages sent by network devices; The processing module is configured to verify the validity of the system message and determine the verification result; The processing module is also configured to perform a first operation when the verification result is a verification failure.

18. A network device, characterized in that, include: The transceiver module is configured to send system messages to the terminal; wherein the system messages are used by the terminal to perform validity verification, and if the verification result is a verification failure, a first operation is performed.

19. A terminal, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 1-9.

20. A network device, characterized in that, include: One or more processors; The processor is used to execute the failure handling method according to any one of claims 10-16.

21. A communication system, characterized in that, include: A terminal, configured to implement the failure handling method according to any one of claims 1-9; A network device configured to implement the failure handling method according to any one of claims 10-16.

22. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the failure handling method as described in any one of claims 1-9 or 10-16.

23. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program is used to implement the failure handling method according to any one of claims 1-9 or 10-16.

Images