Information transmission method and apparatus, communication device, and storage medium

Abstract

Embodiments of the present disclosure relate to information transmission methods and apparatuses, communication devices and storage media. A base station transmits indication information, wherein the indication information indicates a time threshold; the time threshold is used by a user equipment (UE) to determine whether to verify a radio resource control reject (RRCReject) message.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of wireless communication technology, and particularly to information transmission methods, apparatus, communication devices, and storage media. Background Technology

[0002] In cellular mobile communication systems, when a User Equipment (UE) attempts to establish a Radio Resource Control (RRC) connection, the network can reject the UE's RRC connection process by sending a Radio Resource Control Reject (RRCReject) message via the Common Control Channel (CCCH). The RRCReject message lacks security protection. When the UE receives the RRCReject message from the network, if a RejectwaitTime information element (IE) exists, the UE will remain in an RRC disconnected state according to the IE until the timeout occurs before re-initiating or resuming the RRC connection. Summary of the Invention

[0003] In view of the above, embodiments of this disclosure provide an information transmission method, apparatus, communication device, and storage medium.

[0004] According to a first aspect of the present disclosure, an information transmission method is provided, wherein the method is executed by a base station, the method comprising:

[0005] Send indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the user equipment (UE) to determine whether to verify the RRCReject message.

[0006] According to a second aspect of the present disclosure, an information transmission method is provided, wherein the method is executed by a UE, the method comprising:

[0007] The system receives indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0008] According to a third aspect of the present disclosure, an information transmission apparatus is provided, wherein the apparatus includes:

[0009] The sending module is configured to send indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0010] According to a fourth aspect of the present disclosure, an information transmission apparatus is provided, wherein the apparatus includes:

[0011] The receiving module is configured to receive indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0012] According to a fifth aspect of the present disclosure, a communication device apparatus is provided, including a processor, a memory, and an executable program stored in the memory and executable by the processor, wherein when the processor executes the executable program, it performs the steps of the information transmission method as described in the first or second aspect.

[0013] According to a sixth aspect of the present disclosure, a storage medium is provided that stores an executable program thereon, wherein the executable program, when executed by a processor, implements the steps of the information transmission method as described in the first or second aspect.

[0014] According to the information transmission method, apparatus, communication device, and storage medium provided in the embodiments of this disclosure, a base station sends indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message. Thus, the UE can determine whether to verify the RRCReject message based on the duration threshold, which improves the flexibility of RRCReject message verification compared to not verifying RRCReject messages at all or verifying every single RRCReject message, and meets different security requirements for RRCReject messages.

[0015] 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 the embodiments of this disclosure. Attached Figure Description

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

[0017] Figure 1 This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0018] Figure 2 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0019] Figure 3 This is a flowchart illustrating another information transmission method according to an exemplary embodiment;

[0020] Figure 4This is a block diagram illustrating an information transmission device according to an exemplary embodiment;

[0021] Figure 5 This is a block diagram illustrating another information transmission device according to an exemplary embodiment;

[0022] Figure 6 This is a block diagram illustrating an apparatus for information transmission according to an exemplary embodiment. Detailed Implementation

[0023] 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 those of the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of the present invention as detailed in the appended claims.

[0024] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0025] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0026] Please refer to Figure 1 This illustration shows a schematic diagram of the structure of a wireless communication system provided in an embodiment of this disclosure. Figure 1 As shown, the wireless communication system is a communication system based on cellular mobile communication technology. The wireless communication system may include: a number of terminals 11 and a number of base stations 12.

[0027] Terminal 11 can be a device that provides voice and / or data connectivity to a user. Terminal 11 can communicate with one or more core networks via a Radio Access Network (RAN). Terminal 11 can be an Internet of Things (IoT) terminal, such as a sensor device, a mobile phone (or "cellular" phone), and a computer with an IoT terminal. For example, it can be a fixed, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted device. Examples include a station (STA), subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment (UE). Alternatively, Terminal 11 can also be a device in an unmanned aerial vehicle (UAV). Alternatively, Terminal 11 can also be a vehicle-mounted device, such as a vehicle computer with wireless communication capabilities, or a wireless communication device connected to an external vehicle computer. Alternatively, terminal 11 can also be a roadside device, such as a street light, traffic light, or other roadside device with wireless communication capabilities.

[0028] Base station 12 can be a network-side device in a wireless communication system. This wireless communication system can be a 4G system (also known as Long Term Evolution, LTE); or it can be a 5G system (also known as a New Radio, NR, or 5G NR system); or it can be the next generation after 5G. In this case, the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network); or it can be an MTC system.

[0029] In this embodiment, base station 12 can be an evolved NB (eNB) used in a 4G system. Alternatively, base station 12 can also be a gNB (gNB) using a centralized-distributed architecture in a 5G system. When base station 12 adopts a centralized-distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DU). The central unit is equipped with a protocol stack of Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) layers; the distributed units are equipped with a physical (PHY) layer protocol stack. This disclosure does not limit the specific implementation of base station 12.

[0030] Base station 12 and terminal 11 can establish a wireless connection via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as a new air interface; or, the wireless air interface can also be a wireless air interface based on a next-generation mobile communication network technology standard based on 5G.

[0031] In some embodiments, terminals 11 can also establish E2E (End to End) connections. Examples include V2V (vehicle to vehicle), V2I (vehicle to Infrastructure), and V2P (vehicle to pedestrian) communication scenarios in vehicle-to-everything (V2X) communication.

[0032] In some embodiments, the wireless communication system described above may further include a network management device 13.

[0033] Several base stations 12 are connected to network management device 13. Network management device 13 can be a core network device in a wireless communication system, such as a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, it can be other core network devices, such as a Serving Gateway (SGW), a Public Data Network Gateway (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS). The implementation of network management device 13 is not limited in this embodiment.

[0034] The execution entities involved in the embodiments disclosed herein include, but are not limited to: UEs such as mobile phone terminals in cellular mobile communication systems, network-side equipment such as access network equipment such as base stations, and core networks.

[0035] Since RRCReject messages lack any security protection mechanism, if an attacker launches an attack on the UE using RRCReject messages and arbitrarily tampers with RejectwaitTime IE, the UE will suffer a denial-of-service (DoS) attack and thus be unable to enter connected state send and receive services.

[0036] Therefore, a field called RejectMAC-I can be introduced into the RRCReject message for protection. RejectMAC-I can be calculated using a predefined algorithm, such as the NIA algorithm, and the following input parameters:

[0037] a) Key (KEY): The key stored in the current UE context RRCint ;

[0038] b) Bearer: Bearer identifier;

[0039] c) Direction: Data direction;

[0040] d) Count COUNT: Current COUNT value;

[0041] e) Message, including: source C-RNTI, source PCI, target Cell-ID, response cause (resumeCause) and / or waitTime.

[0042] When a UE receives an RRCReject message from a base station (such as a gNB), it needs to verify the RejectMAC-I field in the RRCReject message using the same algorithm. Only when the verification is successful will the UE accept the RRCReject message, thus effectively preventing attackers from attacking the message.

[0043] However, the network does not need to have RejectMAC-I functionality every time it sends an RRCReject message. Therefore, how to flexibly use RejectMAC-I to meet different security needs and improve compatibility is an urgent problem to be solved.

[0044] like Figure 2 As shown, this exemplary embodiment provides an information transmission method that can be executed by the core network of a cellular mobile communication system, including:

[0045] Step 201: Send indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0046] Here, the RRCReject message is a message sent by the base station when the UE initiates an RRC connection to reject the UE's RRC connection process. The RRC connection initiated by the UE can include: RRC connection recovery performed by an inactive UE. The RRC connection initiated by the UE can also include: RRC connection establishment when the UE is idle or newly activated, and RRC reconnection after connection failure.

[0047] The step of determining whether to verify the RRCReject message may include determining whether to verify the security of the RRCReject message.

[0048] For example, a message carrying the indicated information is different from the RRCReject message.

[0049] For example, determining whether to verify the security of the RRCReject message includes: determining whether to verify the verification information carried by the RRCReject message, or verifying whether the waiting time carried by the RRCReject message is an unaltered duration.

[0050] The RRCReject message sent by the base station may or may not contain verification information. Verification information may include security verification information and / or integrity verification information. Verification information can be a field in the RRCReject message: RejectMAC-I. The determination method is as described above and will not be repeated here. Verifying RejectMAC-I can determine whether the RRCReject message has been tampered with and to verify its integrity, thereby improving the security of information transmission.

[0051] Verification of RRCReject messages can include verifying verification information to determine the integrity and / or security of the RRCReject message. This reduces reception errors or security vulnerabilities caused by incomplete or tampered RRCReject messages.

[0052] The duration threshold can be used to compare the UE with the duration associated with the RRC connection. Based on the comparison result, it is determined whether to verify the RRCReject message. The predetermined duration may include, but is not limited to: the waiting time (waitTime) indicated by the RRCReject message, the time from UE release from RRC to RRC connection restoration, etc. Here, the waiting time, i.e., the rejection waiting time (RejectwaitTime), is the duration indicated by the base station that the UE is not allowed to restore the RRC connection.

[0053] In this way, the UE can determine whether to verify the RRCReject message based on the duration threshold. Compared with not verifying the RRCReject message at all or verifying every RRCReject message, this improves the flexibility of RRCReject message verification and meets different security requirements for RRCReject messages.

[0054] In one embodiment, the effective region of the duration threshold is:

[0055] The cell to which the instruction information is sent;

[0056] or,

[0057] The instruction information is sent to the access network notification area RNA of the cell.

[0058] The duration threshold can be effective in the cell where the indication information is sent. That is, after the UE receives the indication information in the current cell, it uses the duration threshold to determine whether to verify the RRCReject message received in the current cell. Here, the cell where the indication information is sent refers to the cell where the base station sends the indication information. For example, if the base station sends the indication information in cell A, then the duration threshold indicated by the indication information is effective in cell A.

[0059] The access network notification area (RNA) can be the area within the signal coverage of the access network. The duration threshold can take effect on the access network RNA that sends the indication information; that is, after receiving the indication information, the UE uses the duration threshold to determine whether to verify the RRCReject message received by the access network RNA.

[0060] In this way, by using the duration threshold, the UE can determine whether to verify the RRCReject message in the effective area, thus meeting the RRCReject message verification requirements of different areas.

[0061] In one embodiment, the indication information is carried in at least one of the following messages:

[0062] Radio Resource Control release RRCRelease message;

[0063] or,

[0064] System message.

[0065] The base station sends an indication information indicating a duration threshold to the UE via an RRCRelease message. This duration threshold can be effective within the cell that sends the RRCRelease message or within the access network RNA that sends the RRCRelease message.

[0066] For example, the duration threshold indicated by the indication information carried in the RRCRelease message is effective in the RNA: the base station sends the duration threshold to the UE through the RRCRelease message, and it is effective throughout the RNA region. This is used by the UE to determine whether to verify the RejectMAC-I message when it receives the RRCReject message.

[0067] For example, the duration threshold indicated by the indication information carried in the RRCRelease message takes effect in the RNA: If the UE receives the duration threshold in the RRCRelease message from the anchor base station, but moves to another cell (belonging to the same RNA) while in a non-connected state and initiates RRC connection recovery, the duration threshold currently stored by the UE can be applied to the cell that initiated the RRC connection recovery. Here, the anchor base station is the base station from which the UE is released from the RRC connected state to the RRC idle state / RRC inactive state.

[0068] The base station sends indication information indicating a duration threshold to the UE via system messages. This duration threshold can be effective within the cell that sends the system message or within the RNA of the access network that sends the system message. Here, the system message may include a System Information Block (SIB). The indication information can be carried in an existing SIB, or a new SIB can be added to carry the indication information.

[0069] For example, the duration threshold indicated by the indication information carried in the system message takes effect in the cell that sent the system message: the base station sends the duration threshold to the UE through system message broadcasting, and it takes effect in the current cell, so that the UE can determine whether to verify RejectMAC-I when it receives the RRCReject message.

[0070] For example, the duration threshold indicated by the indication information carried in the system message takes effect in the RNA that sends the system message: the base station sends the duration threshold to the UE via system message broadcasting, and it takes effect throughout the entire RNA region. This is used by the UE to determine whether to verify the RejectMAC-I message when it receives the RRCReject message. Alternatively, all base stations under all RNAs broadcast the same duration threshold, and regardless of whether the UE is in the anchor cell or moves to a new cell, the same duration threshold is used to determine the verification of the RRCReject message.

[0071] In one embodiment,

[0072] The waiting time indicated by the RRCReject message is less than the time threshold, and the RRCReject message does not contain verification information;

[0073] The waiting time indicated by the RRCReject message is greater than or equal to the time threshold, and the RRCReject message contains the verification information.

[0074] The duration threshold can be set based on the security settings of the RRCReject message. If the waiting time indicated by the RRCReject message is less than the duration threshold, such as 1 second or 2 seconds, then the possibility of the RRCReject message being tampered with during that time period is low. Therefore, verification information can be omitted from the RRCReject message. The UE does not need to perform verification after receiving the RRCReject message.

[0075] For example, if the waiting time that the base station currently wants to send is less than the currently configured time threshold, then the RejectMAC-I function is not needed, and an RRCReject message without RejectMAC-I is sent directly to the UE, that is, there is no authentication mechanism.

[0076] For example, when a UE receives a duration threshold from the system message broadcast of the current base station and receives an RRCReject message in the RRC connection recovery process, if no waiting duration is configured or the waiting duration is less than the duration threshold, the verification process is ignored.

[0077] For example, when the UE receives a duration threshold from the RRCRelease message from the anchor base station and receives an RRCReject message during the cell-to-cell RRC connection recovery process under the entire RNA, if no waiting duration is configured or the waiting duration is less than the duration threshold, the verification process is ignored.

[0078] If the waiting time indicated by the RRCReject message is greater than or equal to a time threshold, then the RRCReject message may be tampered with during that time period. Therefore, verification information can be set in the RRCReject message. The UE needs to perform verification after receiving the RRCReject message.

[0079] For example, if the base station currently wants to send a waiting time that is greater than or equal to the currently configured time threshold, it needs to use the RejectMAC-I function to send an RRCReject message carrying RejectMAC-I to the UE for the UE to authenticate the message.

[0080] For example, when a UE receives a duration threshold from the system message broadcast of the current base station and receives an RRCReject message in the RRC connection recovery process, if the configured waiting duration is greater than or equal to the duration threshold, it needs to verify according to the RejectMAC-I carried in the message.

[0081] For example, when the UE receives the duration threshold from the RRCRelease message of the anchor base station and receives the RRCReject message during the cell-to-cell connection recovery process under the entire RNA, if the configured waiting duration is greater than or equal to the duration threshold, it needs to be verified according to the RejectMAC-I carried in the message.

[0082] The instruction information is carried in the system message.

[0083] In one embodiment, before sending the indication information, the method further includes:

[0084] Whether to send the indication information is determined at least based on the duration threshold;

[0085] The sending instruction information includes:

[0086] In response to the configured duration threshold, the indication information is sent.

[0087] The base station can determine whether to send an indication message based on whether a duration threshold is configured.

[0088] If a duration threshold is configured, the base station can send an indication message to the UE and determine whether to carry verification information, i.e., RejectMAC-I, in the RRCReject message based on the comparison result between the duration threshold and the waiting duration.

[0089] In one embodiment, determining whether to send the indication information, at least based on the duration threshold, includes:

[0090] If the duration threshold is not configured, the base station does not need to send the indication information.

[0091] In one embodiment, in response to determining that no indication information should be sent, the RRCReject message does not contain verification information.

[0092] In one embodiment, in response to the RRCReject message not indicating a waiting time, the RRCReject message does not contain verification information.

[0093] If the base station has not configured a duration threshold, or if the base station has not configured a waiting duration, then the base station may not include a security verification message when sending the RRCReject message. The UE will not perform verification upon receiving the RRCReject message.

[0094] For example, if the base station has not currently configured a duration threshold (e.g., it has not used the RRCRelease message to configure a duration threshold for any UE, or it has not broadcast a duration threshold), then the RejectMAC-I function is unnecessary. If the current UE has not received a duration threshold from the base station via a broadcast system message or RRCRelease message, the verification process is ignored.

[0095] In one embodiment, the method further includes:

[0096] Upon successful verification of the RRCReject message, the UE will not initiate RRC connection recovery within the specified waiting time.

[0097] If the UE successfully verifies the RRCReject message (e.g., successfully verifies RejectMAC-I), it will directly use the denial-of-service duration specified in the RRCReject message during the waiting period. During this waiting period, it will not initiate RRC connection restoration. The UE can initiate RRC connection restoration after the waiting period.

[0098] In one embodiment, the method further includes:

[0099] The UE ignores the RRCReject message in response to the failure to verify it.

[0100] If the UE fails to verify the RRCReject message, such as failing to verify the RejectMAC-I of the RRCReject message, it can be determined that the RRCReject message has been tampered with or corrupted. In this case, the RRCReject message can be ignored, that is, it is assumed that no message has been sent from the base station side until the T319 timeout, at which point the UE determines that the recovery has failed.

[0101] In one embodiment, the method further includes:

[0102] In response to not verifying the RRCReject message, the UE does not initiate RRC connection recovery within the waiting period.

[0103] If the UE ignores the authentication process, i.e., does not authenticate the RRCReject message, the UE can directly use the waiting duration in the RRCReject message to respond to the denial-of-service duration of the RRCReject message. During this waiting duration, RRC connection restoration will not be initiated. After the waiting duration, the UE can initiate RRC connection restoration.

[0104] In practical applications, fake base stations modify the waiting duration in the RRCReject message, typically by making the modified waiting duration shorter than the original one. If the pre-defined waiting duration in the RRCReject message is greater than a time limit, then when the UE receives the RRCReject message, comparing the waiting duration with the time limit can preliminarily determine whether the waiting duration has been modified. If the waiting duration is less than the time limit, then it can be confirmed that the waiting duration has been modified. In other words, the time limit also serves as a verification mechanism.

[0105] like Figure 3 As shown, this exemplary embodiment provides an information transmission method that can be executed by a UE of a cellular mobile communication system, including:

[0106] Step 301: Receive indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0107] Here, the RRCReject message is a message sent by the base station when the UE initiates an RRC connection to reject the UE's RRC connection process. The RRC connection initiated by the UE can include: RRC connection recovery performed by an inactive UE. The RRC connection initiated by the UE can also include: RRC connection establishment when the UE is idle or newly activated, and RRC reconnection after connection failure.

[0108] The step of determining whether to verify the RRCReject message may include determining whether to verify the security of the RRCReject message. The message carrying the indication information may be different from the RRCReject message.

[0109] For example, determining whether to verify the security of the RRCReject message includes: determining whether to verify the verification information carried by the RRCReject message, or verifying whether the waiting time carried by the RRCReject message is an unaltered duration.

[0110] The RRCReject message sent by the base station may or may not contain verification information. Verification information may include security verification information and / or integrity verification information. Verification information can be a field in the RRCReject message: RejectMAC-I. The determination method is as described above and will not be repeated here. Verifying RejectMAC-I can determine whether the RRCReject message has been tampered with and to verify its integrity, thereby improving the security of information transmission.

[0111] Verification of RRCReject messages can include verifying verification information to determine the integrity and / or security of the RRCReject message. This reduces reception errors or security vulnerabilities caused by incomplete or tampered RRCReject messages.

[0112] The duration threshold can be used to compare the UE with the duration associated with the RRC connection. Based on the comparison result, it is determined whether to verify the RRCReject message. The predetermined duration may include, but is not limited to: the waiting time indicated by the RRCReject message, the time from UE release from RRC to RRC connection restoration, etc. Here, the waiting time is the duration indicated by the base station that the UE is not allowed to restore the RRC connection.

[0113] In this way, the UE can determine whether to verify the RRCReject message based on the duration threshold. Compared with not verifying the RRCReject message at all or verifying every RRCReject message, this improves the flexibility of RRCReject message verification and meets different security requirements for RRCReject messages.

[0114] In one embodiment, the effective region of the duration threshold is:

[0115] The cell to which the instruction information is sent;

[0116] or,

[0117] The instruction information is sent to the access network notification area (RAN) of the cell in which it is located.

[0118] The duration threshold can be effective in the cell where the indication information is sent. That is, after the UE receives the indication information in the current cell, it uses the duration threshold to determine whether to verify the RRCReject message received in the current cell. Here, the cell where the indication information is sent refers to the cell where the base station sends the indication information. For example, if the base station sends the indication information in cell A, then the duration threshold indicated by the indication information is effective in cell A.

[0119] The access network notification area (RNA) can be the area within the signal coverage of the access network. The duration threshold can take effect on the access network RNA that sends the indication information; that is, after receiving the indication information, the UE uses the duration threshold to determine whether to verify the RRCReject message received by the access network RNA.

[0120] In this way, by using the duration threshold, the UE can determine whether to verify the RRCReject message in the effective area, thus meeting the RRCReject message verification requirements of different areas.

[0121] In one embodiment, the indication information is carried in at least one of the following messages:

[0122] Radio Resource Control release RRCRelease message;

[0123] or,

[0124] System message.

[0125] The base station sends an indication information indicating a duration threshold to the UE via an RRCRelease message. This duration threshold can be effective within the cell that sends the RRCRelease message or within the access network RNA that sends the RRCRelease message.

[0126] For example, the duration threshold indicated by the indication information carried in the RRCRelease message is effective in the RNA: the base station sends the duration threshold to the UE through the RRCRelease message, and it is effective throughout the RNA region. This is used by the UE to determine whether to verify the RejectMAC-I message when it receives the RRCReject message.

[0127] For example, the duration threshold indicated by the indication information carried in the RRCRelease message takes effect in the RNA: If the UE receives the duration threshold in the RRCRelease message from the anchor base station, but moves to another cell (belonging to the same RNA) while in a non-connected state and initiates RRC connection recovery, the duration threshold currently stored by the UE can be applied to the cell that initiated the RRC connection recovery. Here, the anchor base station is the base station from which the UE is released from the RRC connected state to the RRC idle state / RRC inactive state.

[0128] The base station sends indication information indicating a duration threshold to the UE via system messages. This duration threshold can be effective within the cell that sends the system message or within the RNA of the access network that sends the system message. Here, the system message may include a System Information Block (SIB). The indication information can be carried in an existing SIB, or a new SIB can be added to carry the indication information.

[0129] For example, the duration threshold indicated by the indication information carried in the system message takes effect in the cell that sent the system message: the base station sends the duration threshold to the UE through system message broadcasting, and it takes effect in the current cell, so that the UE can determine whether to verify RejectMAC-I when it receives the RRCReject message.

[0130] For example, the duration threshold indicated by the indication information carried in the system message takes effect in the RNA that sends the system message: the base station sends the duration threshold to the UE via system message broadcasting, and it takes effect throughout the entire RNA region. This is used by the UE to determine whether to verify the RejectMAC-I message when it receives the RRCReject message. Alternatively, all base stations under all RNAs broadcast the same duration threshold, and regardless of whether the UE is in the anchor cell or moves to a new cell, the same duration threshold is used to determine the verification of the RRCReject message.

[0131] In one embodiment, determining whether to verify the RRCReject message includes,

[0132] If the waiting time indicated by the RRCReject message is less than the time threshold, it is determined not to verify the RRCReject message;

[0133] or,

[0134] In response to a wait duration greater than or equal to the duration threshold indicated by the RRCReject message, the verification of the RRCReject message is determined.

[0135] The duration threshold can be set based on the security settings of the RRCReject message. If the waiting time indicated by the RRCReject message is less than the duration threshold, such as 1 second or 2 seconds, then the possibility of the RRCReject message being tampered with during that time period is low. Therefore, verification information can be omitted from the RRCReject message. The UE does not need to perform verification after receiving the RRCReject message.

[0136] For example, if the waiting time that the base station currently wants to send is less than the currently configured time threshold, then the RejectMAC-I function is not needed, and an RRCReject message without RejectMAC-I is sent directly to the UE, that is, there is no authentication mechanism.

[0137] For example, when a UE receives a duration threshold from the system message broadcast of the current base station and receives an RRCReject message in the RRC connection recovery process, if no waiting duration is configured or the waiting duration is less than the duration threshold, the verification process is ignored.

[0138] For example, when the UE receives a duration threshold from the RRCRelease message from the anchor base station and receives an RRCReject message during the cell-to-cell RRC connection recovery process under the entire RNA, if no waiting duration is configured or the waiting duration is less than the duration threshold, the verification process is ignored.

[0139] If the waiting time indicated by the RRCReject message is greater than or equal to a time threshold, then the RRCReject message may be tampered with during that time period. Therefore, verification information can be set in the RRCReject message. The UE needs to perform verification after receiving the RRCReject message.

[0140] For example, if the base station currently wants to send a waiting time that is greater than or equal to the currently configured time threshold, it needs to use the RejectMAC-I function to send an RRCReject message carrying RejectMAC-I to the UE for the UE to authenticate the message.

[0141] For example, when a UE receives a duration threshold from the system message broadcast of the current base station and receives an RRCReject message in the RRC connection recovery process, if the configured waiting duration is greater than or equal to the duration threshold, it needs to verify according to the RejectMAC-I carried in the message.

[0142] For example, when the UE receives the duration threshold from the RRCRelease message of the anchor base station and receives the RRCReject message during the cell-to-cell connection recovery process under the entire RNA, if the configured waiting duration is greater than or equal to the duration threshold, it needs to be verified according to the RejectMAC-I carried in the message.

[0143] In one embodiment, the method further includes:

[0144] In response to the absence of the indicated information, the RRCReject message is not verified;

[0145] or,

[0146] Since the RRCReject message does not indicate a waiting time, the RRCReject message is not verified.

[0147] If the base station has not configured a duration threshold, or if the base station has not configured a waiting duration, then the base station may not include a security verification message when sending the RRCReject message. The UE will not perform verification upon receiving the RRCReject message.

[0148] For example, if the base station has not currently configured a duration threshold, such as not using the RRCRelease message to configure a duration threshold for any UE, or not broadcasting a duration threshold, then the RejectMAC-I function is not required. If the current UE has not received a duration threshold from the base station via a broadcast system message or RRCRelease message, the verification process is ignored.

[0149] In one embodiment, the method further includes:

[0150] In response to the successful verification of the RRCReject message, no RRC connection recovery is initiated within the specified waiting time.

[0151] If the UE successfully verifies the RRCReject message (e.g., successfully verifies RejectMAC-I), it will directly use the denial-of-service duration specified in the RRCReject message during the waiting period. During this waiting period, it will not initiate RRC connection restoration. The UE can initiate RRC connection restoration after the waiting period.

[0152] In one embodiment, the method further includes:

[0153] If verification of the RRCReject message fails, the RRCReject message is ignored.

[0154] If the UE fails to verify the RRCReject message, such as failing to verify the RejectMAC-I of the RRCReject message, it can be determined that the RRCReject message has been tampered with or corrupted. In this case, the RRCReject message can be ignored, that is, it is assumed that no message has been sent from the base station side until the T319 timeout, at which point the UE determines that the recovery has failed.

[0155] In one embodiment, the method further includes:

[0156] In response to not verifying the RRCReject message, no RRC connection recovery is initiated within the waiting period.

[0157] If the UE ignores the authentication process, i.e., does not authenticate the RRCReject message, the UE can directly use the waiting duration in the RRCReject message to respond to the denial-of-service duration of the RRCReject message. During this waiting duration, RRC connection restoration will not be initiated. After the waiting duration, the UE can initiate RRC connection restoration.

[0158] The following provides a specific example in conjunction with any of the above embodiments:

[0159] 1. The base station sends the following message to the UE to limit the wait time threshold in the Radio Resource Control Reject (RRCReject) message:

[0160] a. Radio Resource Control Release (RRCRelease) message;

[0161] b. System message (SystemInfo).

[0162] Example a: The base station sends a duration threshold to the UE via an RRCReject message, which is effective throughout the entire RNA region. This is used by the UE to determine whether to verify RejectMAC-I when it receives an RRCReject message.

[0163] Example b: The base station sends a duration threshold to the UE via system message broadcast (SIBx, which can be an existing SIB or a newly added SIB), and it is effective throughout the entire RNA region. The duration threshold is used by the UE to determine whether to verify RejectMAC-I when it receives the RRCReject message.

[0164] Example c: The base station sends a duration threshold to the UE via system message broadcast (SIBx, which can be an existing SIB or a newly added SIB), and this threshold is effective in the current cell. The duration threshold is used by the UE to determine whether to verify the RejectMAC-I when it receives an RRCReject message. That is, if the UE moves to another cell, the duration threshold broadcast by that other cell is used.

[0165] 2. The duration threshold configured by the current base station is effective throughout the entire RNA region.

[0166] Example a: The UE receives the duration threshold in the RRC Release message of the anchor base station, but moves to another cell (belonging to the same RNA) in the non-connected state and initiates RRC connection recovery. At this time, the duration threshold received and stored by the UE in the anchor base station can be applied to the cell that newly initiates connection recovery.

[0167] Example b: All base stations under RNA broadcast the same duration threshold. Regardless of whether the UE is in the anchor cell or moves to a new cell, the same duration threshold is used to verify the RRCReject message. The anchor base station is the base station from which the UE is released from the connected state to the idle / inactive state, i.e., the last serving cell.

[0168] 3. The base station sends an RRCReject message (carrying RejectMAC-I) to the UE according to the configured duration threshold.

[0169] Example a: If the waiting time that the base station wants to send is less than the currently configured time threshold, then the RejectMAC-I function is not required, and an RRCReject message without RejectMAC-I is sent directly to the UE, i.e. there is no authentication mechanism.

[0170] Example b: If the base station currently wants to send a waiting time that is greater than or equal to the currently configured time threshold, it needs to use the RejectMAC-I function to send an RRCReject message carrying RejectMAC-I to the UE for the UE to authenticate the message.

[0171] Example c: If the base station has not configured a duration threshold, such as not using the RRCRelease message to configure a duration threshold for any UE, or not broadcasting a duration threshold, then the RejectMAC-I function is not required.

[0172] Terminal side

[0173] 1. The UE determines whether the waiting time in the RRCReject message needs to be verified based on whether the base station has configured a duration threshold.

[0174] Example a: When the UE receives the duration threshold from the system message broadcast of the current base station, and receives the RRCReject message in the RRC connection recovery process, if no waiting time is configured, or the waiting time is less than the duration threshold, the verification process is ignored.

[0175] Example b: When the UE receives the duration threshold from the system message broadcast of the current base station, and receives the RRCReject message in the RRC connection recovery process, if the configured waiting time is greater than or equal to the duration threshold, it needs to be verified according to the RejectMAC-I carried in the message.

[0176] For system message broadcasting, the duration threshold may or may not be effective throughout the entire RNA region. The UE should always verify the system message broadcast duration threshold according to the currently camped cell.

[0177] Example c: Scenario where the duration threshold applies throughout the entire RNA region. When the UE receives the duration threshold from the RRCRelease message from the anchor base station, and receives the RRCReject message during the cell-to-cell RRC connection recovery process throughout the entire RNA region, if no waiting time is configured, or the waiting time is less than the duration threshold, the verification process is ignored.

[0178] Example d: Scenario where the duration threshold is effective throughout the entire RNA region. When the UE receives the duration threshold from the anchor base station's RRCReject message, and receives the RRCReject message during the cell's RRC connection recovery process throughout the entire RNA region, if the configured waiting time is greater than or equal to the duration threshold, verification is required based on the RejectMAC-I carried in the message.

[0179] Example e: If the current UE does not receive the duration threshold sent by the base station (broadcast or RCRelease), the verification process is ignored.

[0180] 2. The UE responds to the verification result of RejectMAC-I by deciding whether to receive the RRCReject message.

[0181] Example a: If the UE fails to verify RejectMAC-I, the RRCReject message is ignored, meaning that no message has been sent from the base station. At this time, the UE considers the recovery to have failed after T319 times out.

[0182] Example b: According to examples a / c / e, if the UE ignores the verification process, it directly uses the waiting time to respond to the denial-of-service duration of the RRCReject message. During this waiting time, it will not initiate a second RRC connection recovery.

[0183] Example c: If the UE successfully verifies RejectMAC-I, it directly uses the waiting time to respond to the denial-of-service duration of the RRCReject message. During this waiting time, it will not initiate a second RRC connection recovery.

[0184] This invention also provides an information transmission device, such as... Figure 4 As shown, in a base station used for cellular mobile wireless communication, the device 100 includes:

[0185] The sending module 110 is configured to send indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0186] In one embodiment, the effective region of the duration threshold is:

[0187] The cell to which the instruction information is sent;

[0188] or,

[0189] The instruction information is sent to the access network notification area RNA of the cell.

[0190] In one embodiment, the waiting time indicated by the RRCReject message is less than the time threshold, and the RRCReject message does not contain verification information;

[0191] The waiting time indicated by the RRCReject message is greater than or equal to the time threshold, and the RRCReject message contains the verification information.

[0192] In one embodiment, the indication information is carried in at least one of the following messages:

[0193] Radio Resource Control release RRCRelease message;

[0194] or,

[0195] System message.

[0196] In one embodiment, the device 100 further includes:

[0197] The determining module 120 is configured to determine whether to send the indication information based at least on the duration threshold before sending the indication information;

[0198] The sending module 110 is specifically configured to send the indication information in response to the configured duration threshold.

[0199] In one embodiment, the determining module 120 is specifically configured to determine not to send the indication information in response to the absence of the duration threshold.

[0200] In one embodiment, in response to determining that no indication information should be sent, the RRCReject message does not contain verification information.

[0201] In one embodiment, in response to the RRCReject message not indicating a waiting time, the RRCReject message does not contain verification information.

[0202] This invention also provides an information transmission device, such as... Figure 5 As shown, in a UE used in cellular mobile wireless communication, the device 200 includes:

[0203] The receiving module 210 is configured to receive indication information, wherein the indication information indicates a duration threshold; the duration threshold is used by the UE to determine whether to verify the RRCReject message.

[0204] In one embodiment, the effective region of the duration threshold is:

[0205] The cell to which the instruction information is sent;

[0206] or,

[0207] The instruction information is sent to the access network notification area (RAN) of the cell in which it is located.

[0208] In one embodiment, the receiving module 210 is specifically configured as follows:

[0209] If the waiting time indicated by the RRCReject message is less than the time threshold, it is determined not to verify the RRCReject message;

[0210] or,

[0211] In response to a wait duration greater than or equal to the duration threshold indicated by the RRCReject message, the verification of the RRCReject message is determined.

[0212] In one embodiment, the device 200 further includes:

[0213] The first control module 220 is configured to not initiate RRC connection recovery within the waiting time period in response to the successful verification of the RRCReject message.

[0214] In one embodiment, the device 200 further includes:

[0215] The second control module 230 is configured to ignore the RRCReject message in response to a failure to verify the RRCReject message.

[0216] In one embodiment, the device 200 further includes:

[0217] The third control module 240 is configured to not initiate RRC connection recovery within the waiting time in response to not verifying the RRCReject message.

[0218] In one embodiment, the receiving module 210 is specifically configured as follows:

[0219] Determine whether to verify the verification information carried in the RRCReject message.

[0220] In one embodiment, the indication information is carried in at least one of the following messages:

[0221] Radio Resource Control release RRCRelease message;

[0222] or,

[0223] System message.

[0224] In one embodiment, the apparatus further includes:

[0225] The fourth control module 250 is configured to not verify the RRCReject message in response to not receiving the indication information;

[0226] or,

[0227] The fifth control module 260 is configured to not verify the RRCReject message in response to the RRCReject message not indicating a waiting time.

[0228] In an exemplary embodiment, the transmitting module 110, determining module 120, receiving module 210, first control module 220, second control module 230, third control module 240, fourth control module 250, or fifth control module 260 may be implemented by one or more central processing units (CPUs), graphics processing units (GPUs), baseband processors (BPs), application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0229] Figure 6 This is a block diagram illustrating an apparatus 3000 for information transmission according to an exemplary embodiment. For example, apparatus 3000 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0230] Reference Figure 6 The device 3000 may include one or more of the following components: processing component 3002, memory 3004, power supply component 3006, multimedia component 3008, audio component 3010, input / output (I / O) interface 3012, sensor component 3014, and communication component 3016.

[0231] Processing component 3002 typically controls the overall operation of device 3000, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 3002 may include one or more modules to facilitate interaction between processing component 3002 and other components. For example, processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002.

[0232] Memory 3004 is configured to store various types of data to support the operation of device 3000. Examples of this data include instructions for any application or method operating on device 3000, contact data, phonebook data, messages, pictures, videos, etc. Memory 3004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0233] Power supply component 3006 provides power to various components of device 3000. Power supply component 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 3000.

[0234] Multimedia component 3008 includes a screen that provides an output interface between device 3000 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 3008 includes a front-facing camera and / or a rear-facing camera. When device 3000 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0235] Audio component 3010 is configured to output and / or input audio signals. For example, audio component 3010 includes a microphone (MIC) configured to receive external audio signals when device 3000 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 3004 or transmitted via communication component 3016. In some embodiments, audio component 3010 also includes a speaker for outputting audio signals.

[0236] I / O interface 3012 provides an interface between processing component 3002 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.

[0237] Sensor assembly 3014 includes one or more sensors for providing state assessments of various aspects of device 3000. For example, sensor assembly 3014 may detect the on / off state of device 3000, the relative positioning of components such as the display and keypad of device 3000, changes in the position of device 3000 or a component of device 3000, the presence or absence of user contact with device 3000, the orientation or acceleration / deceleration of device 3000, and temperature changes of device 3000. Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 3014 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 3014 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0238] Communication component 3016 is configured to facilitate wired or wireless communication between device 3000 and other devices. Device 3000 can access wireless networks based on communication standards, such as Wi-Fi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 3016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 3016 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0239] In an exemplary embodiment, the apparatus 3000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0240] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 3004 including instructions, which can be executed by a processor 3020 of the device 3000 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

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

[0242] It should be understood that the embodiments of the present invention are 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 their scope. The scope of the embodiments of the present invention is limited only by the appended claims.

Claims

1. An information transmission method, wherein, The method, executed by the base station, includes: Determine whether to send an instruction message; In response to the configuration of a duration threshold, the indication information is sent, wherein the indication information indicates the duration threshold; the duration threshold is used by the user equipment (UE) to determine whether to verify the Radio Resource Control Reject (RRCReject) message; the RRCReject message is ignored by the UE in the event of verification failure; In response to determining that the indication information will not be sent, the RRCReject message does not contain verification information, which is used to verify the RRCReject message; if the RRCReject message does not contain the verification information, the UE does not verify the RRCReject message and initiates Radio Resource Control (RRC) connection recovery after a waiting period, where the waiting period is the duration indicated by the base station that the UE is not allowed to perform RRC connection recovery.

2. The method according to claim 1, wherein, The effective area of ​​the duration threshold is: The cell to which the instruction information is sent; or, The instruction information is sent to the access network notification area RNA of the cell.

3. The method according to claim 1 or 2, wherein, The waiting time indicated by the RRCReject message is less than the time threshold, and the RRCReject message does not contain verification information; The waiting time indicated by the RRCReject message is greater than or equal to the time threshold, and the RRCReject message contains the verification information.

4. The method according to claim 1 or 2, wherein, The indication information is carried in at least one of the following messages: Radio Resource Control release RRCRelease message; or, System message.

5. The method according to claim 1, wherein, The determination of whether to send indication information includes: In response to the absence of the duration threshold being configured, it is determined not to send the indication information.

6. An information transmission method, wherein, The method, executed by the user equipment (UE), includes: The system receives indication information, wherein the indication information is sent when the base station is configured with a duration threshold, and the indication information indicates the duration threshold; the duration threshold is used by the UE to determine whether to verify the Radio Resource Control Reject (RRCReject) message. In response to the failure to verify the RRCReject message, the RRCReject message is ignored; Wherein, if the UE does not receive the indication information, the RRCReject message does not contain verification information, which is used to verify the RRCReject message; if the RRCReject message does not contain the verification information, the UE does not verify the RRCReject message, and initiates Radio Resource Control (RRC) connection recovery after a waiting period, where the waiting period is the duration indicated by the base station that the UE is not allowed to perform RRC connection recovery.

7. The method according to claim 6, wherein, The effective area of ​​the duration threshold is: The cell to which the instruction information is sent; or, The instruction information is sent to the RAN (Access Network Notification Area) of the cell in which it is located.

8. The method according to claim 6, wherein, The process of determining whether to verify the RRCReject message includes, If the waiting time indicated by the RRCReject message is less than the time threshold, it is determined not to verify the RRCReject message; or, In response to the waiting time indicated by the RRCReject message being greater than or equal to the time threshold, it is determined to verify the RRCReject message.

9. The method according to claim 8, wherein, The method further includes: In response to the successful verification of the RRCReject message, no RRC connection recovery is initiated within the specified waiting time.

10. The method according to claim 8, wherein, The method further includes: In response to not verifying the RRCReject message, no RRC connection recovery is initiated within the waiting period.

11. The method according to any one of claims 6 to 10, wherein, The step of determining whether to verify the RRCReject message. include, Determine whether to verify the verification information carried in the RRCReject message.

12. The method according to any one of claims 6 to 10, wherein, The indication information is carried in at least one of the following messages: Radio Resource Control release RRCRelease message; or, System message.

13. An information transmission device, wherein, The device includes: The module is configured to determine whether to send an indication message. The sending module is configured to send the indication information in response to a configured duration threshold, wherein the indication information indicates the duration threshold; the duration threshold is used by the user equipment (UE) to determine whether to verify the Radio Resource Control Reject (RRCReject) message; the RRCReject message is ignored by the UE in the event of verification failure; In response to determining that the indication information will not be sent, the RRCReject message does not contain verification information, which is used to verify the RRCReject message; if the RRCReject message does not contain the verification information, the UE does not verify the RRCReject message and initiates Radio Resource Control (RRC) connection recovery after a waiting period, where the waiting period is the duration during which the base station indicates that the UE is not allowed to perform RRC connection recovery.

14. The apparatus according to claim 13, wherein, The effective area of ​​the duration threshold is: The cell to which the instruction information is sent; or, The instruction information is sent to the access network notification area RNA of the cell.

15. The apparatus according to claim 13 or 14, wherein, The waiting time indicated by the RRCReject message is less than the time threshold, and the RRCReject message does not contain verification information; The waiting time indicated by the RRCReject message is greater than or equal to the time threshold, and the RRCReject message contains the verification information.

16. The apparatus according to claim 13 or 14, wherein, The indication information is carried in at least one of the following messages: Radio Resource Control release RRCRelease message; or, System message.

17. The apparatus according to claim 13, wherein, The determining module is specifically configured to determine not to send the indication information in response to the absence of the duration threshold.

18. An information transmission device, wherein, The device includes: The receiving module is configured to receive indication information, wherein the indication information is sent when the base station is configured with a duration threshold, and the indication information indicates the duration threshold; the duration threshold is used by the user equipment (UE) to determine whether to verify the Radio Resource Control Reject (RRCReject) message. The second control module is configured to ignore the RRCReject message in response to a failure to verify the RRCReject message. Wherein, if the UE does not receive the indication information, the RRCReject message does not contain verification information, which is used to verify the RRCReject message; if the RRCReject message does not contain the verification information, the UE does not verify the RRCReject message, and initiates Radio Resource Control (RRC) connection recovery after a waiting period, where the waiting period is the duration indicated by the base station that the UE is not allowed to perform RRC connection recovery.

19. The apparatus according to claim 18, wherein, The effective area of ​​the duration threshold is: The cell to which the instruction information is sent; or, The instruction information is sent to the RAN (Access Network Notification Area) of the cell in which it is located.

20. The apparatus according to claim 18, wherein, The receiving module is specifically configured as follows: If the waiting time indicated by the RRCReject message is less than the time threshold, it is determined not to verify the RRCReject message; or, In response to the waiting time indicated by the RRCReject message being greater than or equal to the time threshold, it is determined to verify the RRCReject message.

21. The apparatus according to claim 20, wherein, The device further includes: The first control module is configured to not initiate RRC connection recovery within the waiting time period in response to successful verification of the RRCReject message.

22. The apparatus according to claim 20, wherein, The device further includes: The third control module is configured to not initiate RRC connection recovery within the waiting time period in response to not verifying the RRCReject message.

23. The apparatus according to any one of claims 18 to 22, wherein, The receiving module is specifically configured as follows: Determine whether to verify the verification information carried in the RRCReject message.

24. The apparatus according to any one of claims 18 to 22, wherein, The indication information is carried in at least one of the following messages: Radio Resource Control release RRCRelease message; or, System message.

25. A communication device apparatus, comprising a processor, a memory, and an executable program stored in the memory and executable by the processor, wherein, When the processor runs the executable program, it performs the steps of the information transmission method as described in any one of claims 1 to 5 or 6 to 12.

26. A storage medium having an executable program stored thereon, wherein, When the executable program is executed by a processor, it implements the steps of the information transmission method as described in any one of claims 1 to 5 or 6 to 12.

Images