Communication method, communication apparatus, and electronic device

By independently detecting whether the verification failure of the RRC reconfiguration message in an electronic device can be ignored and ignoring the verification failure result when necessary, the problem of call interruption in the RRC reconfiguration process is solved, improving the stability and reliability of communication .

WO2024244608A1PCT designated stage expired Publication Date: 2024-12-05HONOR DEVICE CO LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/081712
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2024-03-14
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

After the RRC reconfiguration process of the base station and user equipment (UE) fail, it may lead to call interruption. The prior art is difficult to effectively solve the problem of call lag and communication interruption caused by verification failure.

Method used

Provides a communication method. When an electronic device receives an RRC reconfiguration message, it automatically detects whether the verification failure can be ignored, and ignores the verification failure result to avoid triggering wireless link failure (RLF), thereby avoiding call lag and communication interruption. . The method includes saving the relevant configuration items before receiving the RRC reconfiguration message, performing verification processing, and sending the RRC reconfiguration completion message if the verification failure is negligible to ensure that the process continues.

Benefits of technology

It effectively reduces the occurrence of call interrupts, ensures that the wireless link failure is not triggered when the verification fails, avoids communication interrupts caused by RRC connection re-establishment, and improves communication stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024081712_05122024_PF_FP_ABST
    Figure CN2024081712_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application relate to the technical field of communications, and provide a communication method, a communication apparatus and an electronic device. A negligible verification processing failure item can be automatically skipped to complete a radio resource control (RRC) reconfiguration process, thereby avoiding call interruption caused by entering an RRC connection reestablishment process due to a negligible verification processing failure item. The method may comprise: an electronic device receives a first RRC reconfiguration message, the first RRC reconfiguration message comprising a first parameter and a value of the first parameter; before the first RRC reconfiguration message is received, the electronic device stores a first configuration item, wherein the first configuration item comprises a second parameter and a value of the second parameter; the electronic device performs verification processing on the first RRC reconfiguration message and the first configuration item, wherein the verification processing comprises first verification; and when a verification failure result of the first verification can be ignored or the process of the first verification can be ignored, the electronic device sends a first RRC reconfiguration completion message.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, communication device and electronic equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 26, 2023, with application number 202310614032.X and invention name “A communication method, communication device and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and in particular to a communication method, a communication device, and an electronic device. Background Art

[0003] Currently, after a base station and a user equipment (UE) fail in an RRC reconfiguration process, the UE and the base station will enter an RRC connection reestablishment process.

[0004] The RRC reconfiguration process can fail for a variety of reasons. For example, the UE can verify multiple parameters configured by the base station through the RRC reconfiguration message. If the verification fails, the RRC reconfiguration process fails. This can cause call interruptions after the RRC connection reestablishment process begins.

[0005] Summary of the Invention

[0006] The present application provides a communication method, a communication device, and an electronic device, which can reduce the occurrence of call interruption problems.

[0007] To achieve the above technical objectives, this application adopts the following technical solutions:

[0008] In a first aspect, a communication method is provided. The method is applied to an electronic device that is in a call, the method comprising: the electronic device receiving a first radio resource control (RRC) reconfiguration message, the first RRC reconfiguration message including a first parameter and a first value corresponding to the first parameter. Prior to receiving the first RRC reconfiguration message, the electronic device stores a first configuration item, the first configuration item including a second parameter and a second value corresponding to the second parameter, the first parameter and the second parameter being related to the same attribute corresponding to the same object. The electronic device performs a verification process on the first RRC reconfiguration message and the first configuration item, the verification process including a first verification process, the first verification process including verifying the first parameter and the first value corresponding to the first parameter, and the second parameter and the second value corresponding to the second parameter. If a verification failure result of the first verification can be ignored, or if the first verification process can be ignored, the electronic device sends a first RRC reconfiguration completion message.

[0009] In this way, the electronic device can autonomously detect whether the current verification failure can be ignored. As a result, when the first verification fails and the verification process or verification result of the first verification is negligible, the electronic device will not trigger a radio link failure (RLF) due to the failure of the first verification, and there will be no corresponding call freeze. In addition, since the result of the first verification failure is ignored, the electronic device will not exit the current RRC reconfiguration process and enter the RRC connection re-establishment process due to the failure of the first verification. This can also avoid the problem of communication interruption caused by this.

[0010] Optionally, the first parameter and the second parameter being related to the same attribute corresponding to the same object include: the first parameter and the second parameter are both related to the encryption attribute corresponding to the first DRB. In this way, it is clarified that in this example, the first parameter and the second parameter used for the first verification can be related configurations of the encryption attribute of the same DRB.

[0011] Optionally, the electronic device storing the first configuration item includes: before receiving the first RRC reconfiguration message, the electronic device receives a second RRC reconfiguration message, the second RRC reconfiguration message including the second parameter and a second value corresponding to the second parameter, the second parameter being an encryption identifier corresponding to the first DRB, and the second value corresponding to the encryption identifier of the first DRB indicating that data transmitted through the first DRB does not require encryption. The first parameter is an encryption algorithm, the first value corresponding to the first parameter is content corresponding to the encryption algorithm, and the content corresponding to the encryption algorithm indicates that data transmitted through the first DRB needs to be encrypted based on the content corresponding to the encryption algorithm. The first RRC reconfiguration message does not include the encryption identifier corresponding to the first DRB and the value corresponding to the encryption identifier of the first DRB. In this example, the first parameter may correspond to an encryption algorithm, and the first value it carries may be the content of the encryption algorithm. Then, when the first parameter is configured, the electronic device is instructed to encrypt all DRBs and SRBs, including the first DRB, based on the first value. In addition, the second parameter may correspond to an encryption identifier, which may be used to configure the encryption attributes of a single DRB. For example, when the value of the second parameter is configured to be the second value, it indicates that the corresponding first DRB does not need to be encrypted. In this way, during the verification process of the first verification, it is possible to verify whether the encryption attribute configuration of the same DRB (such as the first DRB) is consistent with the first parameter and the second parameter.

[0012] Optionally, the second RRC reconfiguration message includes the second parameter and the second value corresponding to the second parameter, the second parameter is the encryption identifier corresponding to the first DRB, and the second value corresponding to the encryption identifier of the first DRB indicates that the data transmitted through the first DRB does not need to be encrypted, including: the second RRC reconfiguration message includes a first cipheringDisabled field, and the first cipheringDisabled field corresponds to the first DRB. The first cipheringDisabled field indicates the encryption identifier of the first DRB; the value of the first cipheringDisabled field is configured to true, indicating that the data transmitted through the first DRB does not need to be encrypted. The first RRC reconfiguration message includes a first parameter and the first value corresponding to the first parameter, the first parameter is an encryption algorithm, the first value corresponding to the first parameter is the content corresponding to the encryption algorithm, and the content corresponding to the encryption algorithm indicates that the data transmitted through the first DRB needs to be encrypted based on the content corresponding to the encryption algorithm, including: the first RRC reconfiguration message includes an encryption configuration securityConfig field, the securityConfig field is used to indicate the encryption algorithm, and the securityConfig field indicates that the first DRB needs to be encrypted based on the encryption algorithm. This example further provides the specific implementation of the encryption algorithm and encryption identifier.

[0013] Optionally, when the first cipheringDisabled field is configured to true, the first RRC reconfiguration message carries the securityConfig field and the content corresponding to the securityConfig field, and the first RRC reconfiguration message does not include the first cipheringDisabled field and the value corresponding to the first cipheringDisabled field, the first verification fails. It is understandable that the protocol stipulates that once the cipheringDisabled field is configured, the cipheringDisabled field cannot be changed if the corresponding DRB is not released. In this way, after the second RRC reconfiguration message configures the first cipheringDisabled field to be true, the second RRC reconfiguration message configures the securityConfig field and the content corresponding to the securityConfig field, and does not include the first cipheringDisabled field as true in the second RRC reconfiguration message, the corresponding first verification will fail.

[0014] Optionally, before the electronic device sends the first RRC reconfiguration completion message, the method further includes: the electronic device determines that the verification failure result of the first verification can be ignored, or the process of the first verification can be ignored. The electronic device sends the first RRC reconfiguration completion message, including: the electronic device ignores the verification failure result of the first verification or skips the first verification, and sends the first RRC reconfiguration completion message. In this way, before performing the first verification, the electronic device can determine that the process or result of the first verification can be ignored. That is, whether the first verification is performed or what its result is, the verification can be considered successful. Then, the electronic device can not perform the first verification, saving corresponding overhead.

[0015] Optionally, configuration information is stored in the electronic device, and the configuration information includes first indication information, and the first indication information is used to indicate whether the failed result or process of the first verification can be ignored. The electronic device determines that the failed verification result of the first verification can be ignored, or that the process of the first verification can be ignored, including: the electronic device determines that the failed verification result of the first verification can be ignored, or that the process of the first verification can be ignored, based on the first indication information. In this way, by storing the configuration information in the electronic device, the electronic device can accurately determine whether the process or result of the first verification can be ignored.

[0016] Optionally, when the electronic device receives the first RRC reconfiguration message, the electronic device resides in a first cell, where the first cell corresponds to the first base station. Before the electronic device sends the first RRC reconfiguration complete message, the method further includes: the electronic device resides in the first cell. The electronic device sending the first RRC reconfiguration complete message includes: the electronic device sending the first RRC reconfiguration complete message to the first base station. Thus, the electronic device can continue to reside in the first cell through the current RRC reconfiguration process and indicate to the first base station that the RRC reconfiguration process is successful.

[0017] Optionally, when the electronic device receives the first RRC reconfiguration message, the electronic device resides in a first cell, and the first cell corresponds to the first base station. The first RRC reconfiguration message includes cell information of the second cell, and the first RRC reconfiguration message is used to instruct the electronic device to switch and reside in the second cell. Before the electronic device sends the first RRC reconfiguration completion message, the method also includes: the electronic device resides in the second cell according to the cell information of the second cell, and the second cell corresponds to the second base station. The second cell is different from the first cell. The electronic device sends the first RRC reconfiguration completion message, including: the electronic device sends the first RRC reconfiguration completion message to the second base station. Thus, the electronic device can switch to reside in the second cell through the current RRC reconfiguration process, and indicate to the second base station that the RRC reconfiguration process is successful.

[0018] Optionally, the second RRC reconfiguration message is received by the electronic device before entering a call. For example, the second RRC reconfiguration message may be received during a call establishment process, in which case the first DRB may correspond to the DRB of the IMB of the current call. Alternatively, the second RRC reconfiguration message may be received before the call establishment process, in which case the first DRB may correspond to the default bearer DRB.

[0019] Optionally, before the electronic device sends the first RRC reconfiguration completion message, the method further includes: the electronic device determines, based on at least one preset ignore configuration, that the verification failure result of the first verification can be ignored. The at least one ignore configuration includes a first ignore flag, and the first ignore flag is configured as a third value, indicating that the first verification process can be ignored. Alternatively, the first ignore flag is configured as a fourth value, indicating that the first verification process can be ignored. This provides a specific implementation of a solution for determining that the first verification process or failure result can be ignored.

[0020] Optionally, the electronic device is configured with a skip switch, which is used to enable the verification failure result of the first verification to be ignored, or the skip switch is used to enable the first verification process to be ignored. Before the electronic device sends the first RRC reconfiguration completion message, the method also includes: the electronic device determining that the skip switch is turned on. In this way, when there are multiple ignorable verification processes, the skip switch can be used to perform overall control of all ignorable items. Each ignorable item is also an ignorable verification process.

[0021] Optionally, before the electronic device receives the first RRC reconfiguration message, the method further includes: the electronic device receiving a first measurement event, the electronic device performing measurement corresponding to the first measurement event, and the electronic device sending a first measurement report.

[0022] Optionally, the first measurement event is any one of the following: event A2, event A3, event B1, event B2.

[0023] This provides a scenario implementation in which a base station configures a first RRC reconfiguration message for an electronic device. For example, if the electronic device moves during a call and signal quality degrades, a mobility measurement is triggered. For example, an A3 measurement is performed and an A3 measurement report is submitted to the base station. The base station can then send the first RRC reconfiguration message to the electronic device, thereby instructing the electronic device to perform a cell handover.

[0024] In a second aspect, a communication device is provided. The device is applied to an electronic device and is used to communicate with a base station according to the communication method provided in the first aspect and any possible design thereof.

[0025] According to a third aspect, an electronic device is provided, comprising a processor and a memory, wherein one or more computer programs are stored in the memory. When the one or more computer programs are executed by the processor, the electronic device executes the communication method provided in the first aspect and any possible design thereof to communicate with a base station.

[0026] Optionally, the processor includes a modem.

[0027] In a fourth aspect, a chip system is provided, which is applied to an electronic device. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected via a line. The interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor, where the signal includes a computer instruction stored in the memory. When the processor executes the computer instruction, the electronic device executes the communication method provided in the first aspect and any possible design thereof.

[0028] Optionally, the chip system includes a modem in an electronic device.

[0029] In a fifth aspect, the present application also provides a computer-readable storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0030] In a sixth aspect, the present application also provides a computer program product, which, when running on a computer, enables the computer to execute the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0031] It can be understood that the solutions provided in the second to sixth aspects of the present application can respectively correspond to the first aspect and any possible design thereof, so the beneficial effects that can be achieved are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] FIG1 is a schematic diagram of an interaction in which RRC reconfiguration is successful;

[0033] FIG2 is a schematic diagram of an encryption configuration performed via an RRC reconfiguration message;

[0034] FIG3 is a schematic diagram of an interaction in which an RRC reconfiguration fails;

[0035] FIG4A is a schematic diagram of an interaction in a scenario where a UE performs cell handover;

[0036] FIG4B is a schematic diagram of configuring an encryption identifier for an RRC reconfiguration message 41;

[0037] FIG4C is a schematic diagram of an RRC reconfiguration message 42 configured with an encryption algorithm;

[0038] FIG5A is an interactive diagram of a communication method provided in an embodiment of the present application;

[0039] FIG5B is an interactive diagram of a communication method provided in an embodiment of the present application;

[0040] FIG6 is an interactive diagram of a communication method provided in an embodiment of the present application;

[0041] FIG7 is an interactive diagram of a communication method provided in an embodiment of the present application;

[0042] FIG8 is an interactive diagram of a communication method provided in an embodiment of the present application;

[0043] FIG9 is a schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0044] FIG10 is a schematic diagram of the composition of an electronic device provided in an embodiment of the present application;

[0045] FIG11 is a schematic diagram of the composition of another electronic device provided in an embodiment of the present application;

[0046] FIG12 is a schematic diagram of the composition of a chip module in an electronic device provided in an embodiment of the present application;

[0047] FIG13 is a schematic diagram showing the composition of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0049] The technical solutions provided in the embodiments of the present application can be applied to various wireless communication networks, such as: global system for mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, universal mobile telecommunication system (UMTS) system, general packet radio service (GPRS) system, long term evolution (LTE) system, long term evolution advanced (LTE-A) system, world-wide interoperability for microwave access (WiMAX) system, new radio network of fifth generation mobile communication technology (5G), network of sixth generation mobile communication technology (6G), etc. The terms "network" and "system" are interchangeable.

[0050] In the embodiments of the present application, a base station (BS) may be a device that communicates with user equipment (UE) or other communication sites such as relay sites, and the base station may provide communication coverage for a specific physical area. For example, the base station may be a base transceiver station (BTS) or a base station controller (BSC) in GSM or CDMA; it may also be a node B (NB) in UMTS or a radio network controller (RNC) in UMTS; it may also be an evolved Node B (eNB or eNodeB) in LTE; it may also be a next generation Node B (gNB) in 5G NR; or it may be other access network devices that provide access services in a wireless communication network, but the present invention is not limited thereto.

[0051] The UE can transmit signaling and / or data via the radio bearer between the UE and the base station.

[0052] The radio bearer may include a signaling radio bearer (SRB) and / or a data radio bearer (DRB).

[0053] SRBs may have a variety of different types. For example, the types of SRBs may include SRB0, SRB1, and / or SRB2.

[0054] SRB0 is used by the base station to send a radio resource control (RRC) connection reconfiguration message to the UE; or the UE to send an RRC connection reconfiguration request message to the base station to reconfigure SRB1 or SRB2 between the base station and the UE. SRB1 and SRB2 are used to transmit RRC messages between the base station and the UE. The RRC connection reconfiguration message may also be referred to as the RRC reconfiguration message, and the RRC connection reconfiguration request message may also be referred to as the RRC reconfiguration request message.

[0055] DRBs may include DRBs for transmitting RRC messages and DRBs for transmitting user data.

[0056] It is understood that the UE needs to maintain a stable RRC connection with the base station during communication with the base station. In scenarios such as cell handover, if the quality of the original RRC connection deteriorates, the UE can perform an RRC connection reconfiguration process with the base station to improve the RRC connection quality.

[0057] In the above example, the RRC connection reconfiguration message or RRC connection reconfiguration request message interaction performed in SRB0 may be performed in the RRC connection reconfiguration process.

[0058] In this application, the RRC connection reconfiguration process is used to modify the RRC connection between the UE and the base station, for example, to establish / modify / release resource elements (RBs), perform cell handover, prepare / modify / release measurements, etc.

[0059] Taking the 5G NR network as an example, the RRC reconfiguration process can be initiated by the base station on the network side (such as gNB).

[0060] Referring to Figure 1 , which is a schematic diagram of an interaction of an RRC reconfiguration process, Figure 1 shows a specific example of successful RRC reconfiguration.

[0061] As shown in FIG1 , the RRC reconfiguration process may include:

[0062] S101. A base station sends an RRC reconfiguration message to a UE. For example, the RRC reconfiguration message may include RRCReconfiguration.

[0063] In this example, the RRC reconfiguration message may carry multiple field information corresponding to the RRC resources reconfigured for the UE.

[0064] 2 , the multiple fields corresponding to the RRC resource may include a field corresponding to an encryption identifier and / or a field corresponding to an encryption algorithm.

[0065] In some embodiments, the field indicated by the RRC reconfiguration message may include a field corresponding to the encryption identifier corresponding to the DRB.

[0066] Take the encryption identifier as the cipheringDisabled field as an example. The cipheringDisabled field can be effective for the configured DRB. If the cipheringDisabled field is configured to true, then the corresponding DRB does not need to be encrypted. Correspondingly, if the network is not configured with the cipheringDisabled field, then the corresponding DRB needs to be encrypted. In an embodiment of the present application, the DRB does not need to be encrypted, that is, the data transmitted through the DRB does not need to be encrypted. Correspondingly, the DRB needs to be encrypted, that is, the data transmitted through the DRB needs to be encrypted.

[0067] It should be noted that, in other embodiments, the field for configuring the encryption identifier of the DRB may also be other fields, which is not limited in the embodiments of the present application.

[0068] In other embodiments, the multiple fields indicated by the RRC reconfiguration message may further include an encryption algorithm (or security configuration).

[0069] For example, the encryption algorithm is identified by the encryption configuration (securityConfig) field. Figure 2 provides an illustration of the securityConfig field in the existing protocol. As shown in Figure 2, securityConfig indicates the security algorithms and keys used for signaling and data radio bearers configured using the list in this IERadioBearerConfig. When this field is not included after AS security is activated, the UE should continue to use the currently configured keyToUse and security algorithm for radio bearers reconfigured using the list in this IERadioBearerConfig. This field is not included when configuring SRB1 before AS security is activated. In the description of usage rules (KeyToUse), securityConfig indicates whether the bearers configured using the list in this IERadioBearerConfig are using primary or secondary keys to derive encryption and / or integrity protection keys. For MR-DC, the network should not configure secondary keys for SRB1 and SRB2, nor should it configure primary keys for SRB3. When this field is not included, the UE should continue to use the currently configured keyToUse for radio bearers reconfigured using the list in this IERadioBearerConfig. securityConfig also indicates the security algorithms for signalling and data radio bearers configured using the list in this IE RadioBearerConfig. When this field is not included, the UE shall continue to use the currently configured security algorithms for radio bearers reconfigured using the list in this IE RadioBearerConfig.

[0070] Therefore, in an embodiment of the present application, the securityConfig field can be effective for all radio bearers of the current communication configuration (i.e., all DRBs and SRBs currently configured). That is, after the base station configures the securityConfig field for the UE, the corresponding indication will be that all DRBs and SRBs in the current communication need to be encrypted based on the securityConfig field. For example, after the securityConfig field is configured, if no DRB or SRB is configured as not encrypted through the cipheringDisabled field, it means that all data transmitted through all DRBs and SRBs need to be encrypted based on the securityConfig field.

[0071] It can be seen that whether any DRB in the communication needs to be encrypted can be configured through the encryption identifier and / or encryption algorithm.

[0072] In different embodiments, the base station may use one of the two encryption configuration methods described above to configure, via an RRC reconfiguration message, whether DRB encryption is required to the UE. Alternatively, the base station may use both of the two encryption configuration methods described above to configure, via one or more RRC reconfiguration messages, whether DRB encryption is required to the UE.

[0073] It should be noted that, in existing protocol regulations, once the value of the cipheringDisabled field for the same DRB is configured, the value of the field cannot be changed before the DRB is released.

[0074] For example, the base station configures the value of the cipheringDisabled field of DRB-A to true through the RRC reconfiguration message A1. Then, before the DRB-A is released, the encryption configuration of the DRB-A needs to remain unencrypted. After the RRC reconfiguration message A1, if the base station configures the securityConfig field for the current communication through the RRC reconfiguration message A2, it is necessary to carry a configuration indicating that the cipheringDisabled field of DRB-A is true in the RRC reconfiguration message A2. This ensures that the cipheringDisabled field of the DRB-A does not change before and after the configuration. In this way, through the RRC reconfiguration message A2, the base station can instruct the UE to encrypt all radio bearers except DRB-A based on the securityConfig field. However, the DRB-A is not encrypted.

[0075] S102. The UE determines that the verification is successful according to the RRC reconfiguration message.

[0076] In this example, the UE may perform verification based on at least the fields carried in the RRC reconfiguration message to determine that the verification is successful. In some cases, the UE may also perform verification based on parameters configured in fields carried in previously received historical RRC reconfiguration messages.

[0077] Exemplarily, when the base station uses an encryption identifier and an encryption algorithm to configure whether the DRB is encrypted, the UE can determine whether the verification processing item is successful based on whether there is a change in the encryption identifier when the base station configures the encryption algorithm to the UE. For example, the base station configures the encryption identifier (such as the cipheringDisabled field) and the encryption algorithm (such as the securityConfig field) to the UE through two different RRC reconfiguration messages. Then, when the cipheringDisabled field of the same DRB does not change in the two RRC reconfiguration messages, the verification processing is successful. On the contrary, when the cipheringDisabled field of the same DRB changes in the two RRC reconfiguration messages, it violates the protocol provisions and corresponds to a verification processing failure. Among them, the cipheringDisabled field can be configured to true or not configured (that is, the cipheringDisabled field is empty). Then, for the same DRB, if the cipheringDisabled field is configured to true in the first RRC reconfiguration message and the securityConfig field is configured but the cipheringDisabled field is not configured (corresponding to the cipheringDisabled field being empty) in the second RRC reconfiguration message, the UE can infer that the cipheringDisabled field of the DRB is false based on the second RRC reconfiguration message. In this way, the value of the cipheringDisabled field configured for the same DRB in two different RRC reconfiguration messages can be understood as having changed, and the corresponding verification process has failed.

[0078] In conjunction with the example in S101, the base station configures the cipheringDisabled field of DRB-A to true for the UE through RRC reconfiguration message A1. Thereafter, when the base station configures the securityConfig field to the UE through RRC reconfiguration message A2, if the RRC reconfiguration message A2 carries the configuration that the cipheringDisabled field of DRB-A is true, the cipheringDisabled field of DRB-A does not change, which complies with the protocol requirements, and the corresponding verification process is successful.

[0079] S103. The UE sends an RRC reconfiguration complete message to the base station. For example, the RRC reconfiguration complete message may include RRCReconfigurationComplete.

[0080] Thus, the current RRC reconfiguration process can be completed.

[0081] In the example of FIG1 , the UE is described by taking the case where the verification process is successful according to the RRC reconfiguration message as an example. In other cases, the verification process performed by the UE according to the RRC reconfiguration message may also fail.

[0082] For example, referring to Figure 3, which is a schematic diagram of another interaction of an RRC reconfiguration process, Figure 3 shows a specific example of an RRC reconfiguration failure.

[0083] As shown in Figure 3, the process may include:

[0084] S301. The base station sends an RRC reconfiguration message to the UE.

[0085] The specific implementation of S301 may refer to S101 in FIG. 1 .

[0086] S302. The UE determines, according to the RRC reconfiguration message, that verification has failed.

[0087] Combined with the description in S102, when the base station uses the encryption identifier and encryption algorithm to configure whether the DRB is encrypted, the UE can determine whether the verification processing item is successful based on whether the encryption identifier changes when the base station configures the encryption algorithm to the UE. For example, the base station configures the encryption identifier (such as the cipheringDisabled field) and the encryption algorithm (such as the securityConfig field) to the UE through two RRC reconfiguration messages. When the cipheringDisabled field of the same DRB changes in two RRC reconfiguration messages, it corresponds to a verification processing failure.

[0088] It should be noted that if the cipheringDisabled field of DRB-A is not carried in the RRC reconfiguration message, it corresponds to the configuration that DRB-A requires encryption. Compared with the case where the cipheringDisabled field of DRB-A is configured as true, there is also a case where the cipheringDisabled field is changed.

[0089] As a possible implementation, the base station configures the cipheringDisabled field of DRB-B to true through RRC reconfiguration message B1. The base station configures the securityConfig field of the current communication to the UE through RRC reconfiguration message B2, and the RRC reconfiguration message B2 does not carry the configuration that the cipheringDisabled field of DRB-B is true.

[0090] Then, since the cipheringDisabled field of the DRB-B configured by the two RRC reconfiguration messages has changed, the UE may determine that the verification process has failed.

[0091] When the UE determines that the verification process fails, the current RRC reconfiguration process ends and the following S303 is executed.

[0092] S303: The UE initiates an RRC connection re-establishment process to the base station. For example, the RRC connection re-establishment process may be an RRC connection re-establishment process.

[0093] Exemplarily, the UE may send an RRC connection reestablishment request (such as RRCReestablishmentRequest) to the base station. The cause value carried in the RRC connection reestablishment request may include: reconfiguration failure.

[0094] Correspondingly, after entering the RRC connection re-establishment process as shown in S303 in FIG. 3 , the base station will also respond.

[0095] For example, after receiving the RRC connection re-establishment request with a cause value of "reconfiguration failure", the base station can search for context information of the current PDU session.

[0096] If the current base station is able to obtain the context information of the current PDU session, the base station can send an RRC re-establishment response (such as RRCReestablishment) to the UE. Then, the UE can perform RRC re-establishment based on the RRC re-establishment response and feedback an RRC re-establishment completion message (such as RRCReestablishmentComplete) to the base station.

[0097] In this case, although the RRC connection re-establishment process can be successfully completed, the UE cannot communicate with the base station during the RRC connection re-establishment process. Therefore, the current communication may be stuck or interrupted during the RRC connection re-establishment process.

[0098] Correspondingly, if the current base station is unable to obtain the context information of the current PDU session, the base station can send an RRC setup (RRCsetup) message to the UE. Then, the UE can perform RRC setup according to the RRCsetup message and feedback an RRC setup completion message (such as RRCSetupComplete) to the base station.

[0099] In this case, since the base station cannot obtain the context of the UE during the previous communication process, it cannot continue to maintain communication with the UE. This will cause the connection to be disconnected based on the 503 message. Then, the UE's ongoing communication will also be unable to continue.

[0100] For the specific implementation of the above RRC connection reconfiguration process, reference may be made to the relevant provisions on RRC connection re-establishment in R16 of the existing protocol.

[0101] In actual networks, after receiving an RRC connection re-establishment request, the base station may trigger a disconnection of the connection with the UE due to insufficient bearer resources, regardless of whether the current PDU session context can be found. This may cause communication interruption on the UE side.

[0102] In addition, after the UE determines that the RRC reconnection process has failed, it can trigger a limitless link failure (RLF) and, based on the configured policy, access a cell with better communication quality. This process can also cause communication to be stuck before entering the RRC connection reestablishment process.

[0103] In order to more clearly describe the above problem, the following takes the scenario where the UE needs to perform cell switching (such as switching to cell B) during a call with cell A as an example, and illustrates the RRC reconfiguration process shown in Figure 3 and the subsequent situation where the call is triggered after entering the RRC connection re-establishment process.

[0104] Cell A and cell B may be different cells belonging to the same base station; or, cell A and cell B may be different cells belonging to different base stations. In this application, communication between a UE and cell A is communication between the UE and the base station to which cell A belongs. Similarly, communication between a UE and cell B is communication between the UE and the base station to which cell B belongs.

[0105] For example, the base station to which cell A belongs is base station A, and the base station to which cell B belongs is base station B. In different implementations, base station A and base station B may be the same base station, or base station A and base station B may be different base stations.

[0106] 4A , which is a schematic diagram of the interaction between the UE and the cell in a cell handover scenario in which the UE establishes a call with the cell A through the base station A.

[0107] S401. Base station A sends an RRC reconfiguration message 41 to a UE.

[0108] Exemplarily, the RRC reconfiguration message 41 may be used to configure multiple DRBs including the first DRB to the UE.

[0109] In some embodiments, as shown in FIG4A , the RRC reconfiguration message 41 may configure the first DRB to the UE during the call establishment process. Furthermore, the RRC reconfiguration message 41 may also include a configuration for the first cipheringDisabled field of the first DRB. For example, the RRC reconfiguration message 41 may include a configuration of first cipheringDisabled=true, thereby indicating that the first DRB does not require encryption.

[0110] In this scenario, the first DRB may be a DRB of the IP multimedia subsystem (IMS). In some implementations, the RRC reconfiguration message 41 may be used to configure the first DRB corresponding to 5QI=1 to the UE. 5QI is used as a reference for 5G Quality of Service (QoS) characteristics, i.e., access node-specific parameters (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, etc.) that control QoS forwarding processing of QoS flows.

[0111] As a specific implementation, take the first DRB including drb-Identity 4 and drb-Identity 5 of pdu-Session 1 as an example.

[0112] 4B , base station A may send an RRC reconfiguration message 41 to the UE in a downlink dedicated control channel (DL_Dedicated Control Channel, DL_DCCH) during the communication establishment process.

[0113] In the example shown in FIG4B , base station A may configure the DRB resources in pdu-Session 1 to the UE through the RRC reconfiguration message 41. For example, the DRB resources in pdu-Session 1 may include drb-Identity 4 and drb-Identity 5.

[0114] As shown in Figure 4B, through the RRC reconfiguration message 41, base station A also configures the encryption flag (i.e., cipheringDisabled) of drb-Identity 4 to true, corresponding to not encrypting drb-Identity 4. Through the RRC reconfiguration message 41, base station A also configures the encryption flag (i.e., cipheringDisabled) of drb-Identity 5 to true, corresponding to not encrypting drb-Identity 5.

[0115] After the call is established, the UE can provide call services to the user through the cell A provided by the base station A, that is, enter the call stage.

[0116] It should be noted that, in the description of S401 above, the configuration of the first cipheringDisabled field of the first DRB is explained through the RRC reconfiguration message 41 during the call establishment process. In other embodiments of the present application, the first DRB may also be one of the default bearers configured after the UE is powered on. In this way, the first cipheringDisabled field of the first DRB may be configured after the UE is powered on (that is, before entering the communication establishment phase); or, the first cipheringDisabled field of the first DRB may also be configured through the RRC reconfiguration message 41 after entering the communication establishment phase.

[0117] In the following examples, the solution shown in FIG4A is used as an example.

[0118] S402: Base station A sends measurement configuration including event A3 to UE.

[0119] In this example, when the UE moves to the edge of cell A or the communication quality of the current access point deteriorates, cell handover measurement may be triggered.

[0120] When cell handover measurements are triggered, the base station can send the corresponding measurement event to the UE. The UE can perform measurements based on the measurement event and, if the corresponding conditions are met, report the measurement report to the base station. This allows the base station to instruct the UE based on the measurement report, or the UE to perform cell handover autonomously.

[0121] For example, the measurement events may include: event A3, event A2, event B1, event B2, etc.

[0122] Among them, Event A3 is used to trigger the same-frequency measurement of the neighboring cell of the same network standard. When the Reference Signal Receiving Power (RSRP) value of the neighboring cell is higher than the RSRP of the resident cell and the RSRP value of the neighboring cell exceeds the corresponding threshold, the measurement report is uploaded.

[0123] Event A2 is used to trigger measurement of the resident cell. When the RSRP value of the resident cell is lower than the corresponding threshold, a measurement report is uploaded.

[0124] Event B1 can be used to trigger the measurement of a high-priority heterogeneous system cell. When the RSRP of the neighboring cell is higher than the corresponding threshold, the terminal uploads a measurement report.

[0125] Event B2 can be used to trigger measurement of heterogeneous cells of the same or lower priority. When the RSRP of the resident cell is lower than the corresponding threshold and the RSRP of the heterogeneous neighboring cell is higher than the corresponding threshold, the terminal uploads a measurement report.

[0126] In this example, the measurement event is event A3.

[0127] In this way, base station A instructs the UE to perform same-system and same-frequency measurement by sending an A3 measurement event. In this A3 measurement event, cell A is the resident cell and cell B is the neighboring cell of the same frequency and same system.

[0128] S403. The UE sends an A3 measurement report to base station A.

[0129] In conjunction with the description in S402, the UE may perform corresponding measurements according to the A3 measurement event. When the measurement result meets the requirements of event A3, the UE may send a corresponding A3 measurement report to the base station.

[0130] For example, the UE may obtain the RSRP-cella of the currently camped cell (such as base station A), and the UE may obtain the RSRP-cellb of cell B in the same system and frequency. When RSRP-cellb is greater than RSRP-cella and RSRP-cellb is greater than the corresponding threshold, the UE may execute S403 and send an A3 measurement report to the base station to which base station A belongs.

[0131] S404. Base station A sends an RRC reconfiguration message 42 to the UE.

[0132] In this example, RRC reconfiguration message 42 is sent after the base station receives an A3 measurement report. It can be understood that when base station A receives the A3 measurement report, it indicates that the UE has determined, through measurement, that the signal quality of a neighboring cell (e.g., cell B) is better than that of the current cell. Base station A can then instruct the UE to switch to cell B through RRC reconfiguration message 42.

[0133] Exemplarily, the RRC reconfiguration message 42 may include cell information of cell B. The cell information of cell B may be used for the UE to switch to and camp on cell B. In some embodiments, the cell information of cell B may include cell ID, frequency, and other information of cell B.

[0134] In this example, base station A may also configure the encryption algorithm for current communication to the UE through the RRC reconfiguration message 42 .

[0135] As an example, referring to FIG. 4C , base station A may send an RRC reconfiguration message 42 to the UE in a downlink dedicated control channel (DL_DedicatedControl Channel, DL_DCCH).

[0136] In the example shown in Figure 4C , base station A can configure the securityConfig field corresponding to the current communication to the UE through the RRC reconfiguration message 42. Through this configuration, base station A can instruct the UE to encrypt all DRBs and SRBs in the current communication. In addition, in the RRC reconfiguration message 42, base station A does not configure any cipheringDisabled field to the UE. For example, the first cipheringDisabled field corresponding to the first DRB is not included in the RRC reconfiguration message 42.

[0137] It is understandable that the RRC reconfiguration message 42 is used to instruct the UE to switch to cell B. Correspondingly, the configuration of the securityConfig field is used to instruct the UE to encrypt all DRBs and SRBs during the communication process in cell B using the securityConfig field.

[0138] As a specific implementation, with reference to the example of Figure 4B, pdu-Session 1 may include multiple DRBs such as drb-Identity 4 and drb-Identity 5. Then, through the configuration of the securityConfi g field, base station A may instruct the UE to encrypt multiple DRBs including drb-Identity 4 and drb-Identity 5 and other SRBs.

[0139] S405. The UE verifies the DRB of the current session.

[0140] It is understood that the verification process may be a protocol compliance check of the information carried in the RRC reconfiguration message. Through the verification process, the UE can determine whether the currently configured parameters comply with the protocol provisions. If all verifications are successful, the configured multiple parameters are used to re-establish the RRC connection, thereby maintaining the current communication.

[0141] In this example, the verification processes corresponding to the multiple configurations can be performed serially or in parallel. The verification processes corresponding to the multiple configurations can include a first verification process. The first verification corresponds to a verification process based on whether the cipheringdisabled configuration of the same DRB (such as the first DRB) has changed.

[0142] It is understandable that if the first cipheringDisabled field of the first DRB does not change, then the first verification is successful. Conversely, if the first cipheringDisabled field of the first DRB changes before the first DRB is released, then the first verification fails.

[0143] Take the first verification of drb-Identity 4 as an example.

[0144] In RRC reconfiguration message 42, base station A does not configure the cipheringdisabled field for drb-identity 4. Thus, for the same drb-identity 4, the cipheringdisabled field changes from "true" to empty, indicating whether drb-identity 4 is encrypted. Consequently, when the UE performs the first verification of drb-identity 4, the verification fails, as shown in S302 in Figure 3 . The UE then exits the RRC reconfiguration process.

[0145] Similarly, a similar verification failure may occur during the first verification of drb-Identity 5.

[0146] It is understood that in some implementations, the UE may directly exit the current RRC reconfiguration process if it determines that a verification failure occurs. In other implementations, the UE may exit the current RRC reconfiguration process after completing all verification processes and if multiple verification process results include at least one verification failure.

[0147] In this example, the UE can trigger a Radio Link Failure (RLF) after exiting the RRC reconfiguration process. This allows the UE to access a cell based on the configured policy. For example, in the example shown in Figure 4A , the UE can access cell B, which has better signal quality.

[0148] Thus, since the RLF is triggered, the current communication may be blocked or interrupted.

[0149] After the RRC reconfiguration process fails and exits, referring to FIG3 , the UE may enter the RRC connection reestablishment process with the base station corresponding to the currently accessed cell.

[0150] 3 , the RRC connection re-establishment process is described. In the case where the base station can obtain or cannot obtain the context information of the UE, the RRC connection re-establishment process can be implemented in two different specific ways.

[0151] The following S406a uses the example of the base station being able to obtain the UE's context information for the current communication. This solution implementation allows for successful RRC connection reestablishment. Furthermore, S406b uses the example of the base station being unable to obtain the UE's context information for the current communication. This solution implementation corresponds to a failure in RRC connection reestablishment. It is understood that in different scenarios, either S406a or S406b may be performed depending on the actual situation. Each is described in detail below.

[0152] S406a. The UE initiates an RRC connection re-establishment process to base station B, and the RRC connection re-establishment process is successfully completed.

[0153] It is understandable that after the current UE triggers RLF, it has already accessed cell B of base station B. Therefore, the UE can initiate the RRC connection re-establishment process to base station B.

[0154] As shown in S406a, the process may specifically include: the UE sends an RRC connection re-establishment request (RRCReestablishmentRequest) to base station B. For example, the cause value of the RRCReestablishmentRequest may be configured as: reconfiguration failure (reestablishmentCause reconfigurationFailure). Correspondingly, base station B may attempt to obtain the context of the UE in the current communication. If the context in the current communication can be obtained, base station B may send an RRC re-establishment response (RRCReestablishment) to the UE. Correspondingly, the UE may perform RRC re-establishment based on the RRC re-establishment response (RRCReestablishment), and upon completing the RRC re-establishment, send an RRC re-establishment completion (RRCReestablishmentComplete) to base station B.

[0155] It is understandable that although the RRC connection is eventually re-established successfully in S406a, the UE is unable to communicate with base station B during the execution of S406a. This results in a communication interruption during the RRC connection re-establishment process after the RLF freeze.

[0156] S406b: The UE initiates an RRC connection re-establishment process to base station B, but the RRC connection re-establishment process fails.

[0157] It is understandable that after the current UE triggers RLF, it has already accessed cell B of base station B. Therefore, the UE can initiate the RRC connection re-establishment process to base station B.

[0158] As shown in S406b, the process may specifically include: the UE sending an RRC connection reestablishment request (RRCReestablishmentRequest) to base station B. For example, the cause value of the RRCReestablishmentRequest may be configured as: reconfiguration failure (reestablishmentCause reconfigurationFailure). Accordingly, base station B may attempt to obtain the UE's context in the current communication. If the context in the current communication cannot be obtained, base station B may send an RRC setup (RRCsetup). Accordingly, the UE may feedback an RRC setup complete (RRCSetupComplete) to base station B.

[0159] It is understandable that in the example of S406b, base station B cannot obtain the context of the UE and therefore cannot continue to provide the current communication service to the UE. Then, base station B can communicate with the relevant node of the service control network and pass the received IMS_SIP_BYE response to the UE (as shown in S407 in Figure 4A). Exemplarily, the IMS_SIP_BYE response can carry Reason: SIP; cause = 503; text = "Insufficient Bearer Resource", which is used to indicate that the reason for hanging up is insufficient bearer resources. In this way, base station B can disconnect the current communication connection with the UE. This will result in the UE being unable to maintain the current communication after entering the RRC connection re-establishment process after the RLF is stuck, which will manifest as problems such as call interruption.

[0160] It can be understood that the example of FIG. 4A is merely an example of triggering the re-establishment of the RRC connection shown in FIG. 3 .

[0161] For example, the scenario shown in Figure 4A is multiple configurations of RRC reconfiguration messages caused by cell handover. In other examples, the base station may also configure the cipheringdisabled field of the same DRB to the UE through multiple RRC reconfiguration messages, resulting in changes. This in turn triggers the verification process failure shown in S302 and the RRC connection reestablishment shown in S303.

[0162] For example, in the scenario shown in Figure 4A, the verification process failure is caused by a conflicting change in the cipheringDisabled field of the DRB. In other examples, the UE can also verify other configurations of the DRB. If the corresponding verification process item fails, it will also trigger the RRC connection re-establishment shown in Figure 3, which will lead to subsequent call interruption.

[0163] For another example, in the scenario shown in Figure 4A, the UE sends an RRC connection re-establishment request message to the base station to initiate the RRC connection re-establishment process, which is triggered by a verification failure. In other examples, the UE may also send an RRC connection re-establishment request message to the base station to initiate the RRC connection re-establishment process based on other protocol requirements, thereby causing subsequent call interruption.

[0164] To address the aforementioned issues, embodiments of the present application provide a communication method that enables a UE to automatically ignore verification failures that will not affect subsequent calls based on preset ignorable verification protocol items. This allows the UE to successfully complete the RRC reconfiguration process. Thus, when an ignorable verification failure occurs, the UE will not experience call freezes corresponding to RLF, nor will it experience call interruptions due to entering RRC connection reestablishment.

[0165] As an example, FIG5A is an interactive diagram of a communication method provided in an embodiment of the present application, wherein the first verification fails and the failure result of the first verification can be ignored as an example.

[0166] As shown in FIG5A , the scheme may include:

[0167] S501. Base station A sends an RRC reconfiguration message 51 to a UE.

[0168] For example, the execution of S501 may refer to S401 in Figure 4A , wherein the RRC reconfiguration message 51 may correspond to the RRC reconfiguration message 41 in Figure 4A .

[0169] In conjunction with the description in FIG4A , in this example, the RRC reconfiguration message 51 is sent during the call establishment process, and the first cipheringDisabled=true configuration of the first DRB corresponding to the IMS is performed as an example. In other embodiments, the first DRB may also be a default bearer. In this way, the first cipheringDisabled=true configuration may also be configured before entering the call establishment process, or the first DRB is configured after the UE is powered on, and the first cipheringDisabled=true configuration may be configured during the call establishment process.

[0170] S502: Base station A sends a measurement configuration including event A3 to the UE.

[0171] Exemplarily, the execution of S502 may refer to S402 in FIG. 4A .

[0172] Base station A may be the base station of the cell currently accessed by the UE (e.g., cell A). S502 may be a cell handover measurement triggered by a decrease in communication quality after the UE enters a call due to reasons such as UE mobility. The measurement configuration for event A3 may include cell information of cell B, such as the cell identifier and cell frequency of cell B. This instructs the UE to perform measurements on cell B and the currently residing cell A.

[0173] In this example, the cell handover measurement includes an A3 event. In combination with the description in S402, in other embodiments, the cell handover measurement may also include an A2 event, a B1 event, a B2 event, and the like.

[0174] S503. The UE sends an A3 measurement report to base station A.

[0175] Exemplarily, the execution of S503 may refer to S403 in FIG. 4A .

[0176] For example, when the requirements of event A3 are met, the UE may generate and feed back an A3 measurement report to base station A, so that base station A knows that the current cell B meets the cell handover requirements corresponding to event A3.

[0177] S504. Base station A sends an RRC reconfiguration message 52 to the UE.

[0178] For example, the execution of S504 may refer to S404 in FIG4A , wherein the RRC reconfiguration message 52 may correspond to the RRC reconfiguration message 42 in FIG4A .

[0179] In this example, the RRC reconfiguration message 52 may include cell information of cell B. The cell information of cell B may be used for the UE to switch to camp on cell B. In some embodiments, the cell information of cell B may include cell identifier, frequency, and other information of cell B.

[0180] In addition, the RRC reconfiguration message 52 may further include a securityConfig field. Meanwhile, the RRC reconfiguration message 52 does not include the configuration of the first cipheringDisabled corresponding to the first DRB.

[0181] That is, through the RRC reconfiguration message 52, base station A can instruct the UE to switch to cell B. In the communication with base station B corresponding to cell B, all DRBs and SRBs are encrypted based on the securityConfig field.

[0182] S505. The UE performs a verification process including a first verification.

[0183] Combined with the description of the verification process in the above example. After the UE receives the RRC reconfiguration message from base station A and enters the RRC reconfiguration process, it can perform at least one verification process on each configured parameter. In this example, the verification process may include a first verification, and the first verification corresponds to the verification process of whether the cipheringDisabled configuration of the same DRB (such as the first DRB) has changed. In the case that the first cipheringDisabled configuration of the first DRB has not changed, the first verification is successful. On the contrary, in the case that the first cipheringDisabled configuration of the first DRB has changed, the first verification fails.

[0184] In the following examples, it is taken that all verification processes except the first verification are successful. That is, if the first verification is successful, the UE successfully completes the RRC reconfiguration process according to the mechanism shown in FIG1 .

[0185] S506: The UE determines that the first verification fails.

[0186] In this example, for the first DRB, base station A configured the first cipheringDisabled = true via RRC reconfiguration message 51. Base station A configured the securityConfig field via RRC reconfiguration message 52, but did not include the first cipheringDisabled. Thus, the first cipheringDisabled configuration changed from "true" to empty. Therefore, the first check for the first DRB failed.

[0187] S507: The UE determines that the process / failure result of the first verification can be ignored.

[0188] Exemplarily, the UE may be pre-configured with at least one ignore flag. One ignore flag corresponds to one verification process. For example, a first ignore flag corresponds to a first verification process.

[0189] In some embodiments, each ignore flag may be configured with a different value.

[0190] As a possible implementation, when the ignore flag is configured to the third value, it indicates that the corresponding verification processing can be ignored; in this way, the UE can selectively execute or skip the verification processing, so that when the verification processing is executed, the verification results are considered successful; when the verification processing is skipped, the verification results are also considered successful.

[0191] For example, if the first ignore flag is configured to the third value, it indicates that the first check process can be ignored. In other words, whether the first check is performed and whether the execution result is successful can be ignored. Therefore, the UE can skip the first check when it is required and consider the first check successful. Alternatively, the UE can perform the first check and consider the first check successful regardless of whether the first check result is successful or failed.

[0192] As another possible implementation, when the ignore flag is configured to the fourth value, it indicates that the corresponding verification process failure result can be ignored. In this way, the UE can perform the verification process and, if the verification process fails, ignore the failure result and continue other processes based on the success of the verification process. Alternatively, when the ignore flag is determined to be the fourth value, the UE can know that the result of the verification process currently to be performed can be ignored even if it fails. In this case, the UE can also skip the verification process and directly consider it successful.

[0193] For example, the first ignore flag is configured as the fourth value, indicating that the failure result of the first check can be ignored. Then, in some implementations, the UE can perform the first check and ignore the failure result if the first check fails. That is, the first check is considered successful. In other implementations, the UE can determine that the first ignore flag is the fourth value before performing the first check, thereby determining that the check can be considered successful regardless of whether the first check result succeeds or fails. Then, the UE can skip the first check.

[0194] The above examples illustrate the specific implementation of the verification result being ignorable or the verification process being ignorable. Correspondingly, when the first ignore flag is configured to the fifth value, it indicates that the verification result cannot be ignored; when the first ignore flag is configured to the sixth value, it indicates that the verification process cannot be ignored. In this way, before the UE performs the first verification, the UE can determine that the first ignore flag is the fifth value or the sixth value, and continue to perform the first verification. When the UE performs the first verification and obtains a verification failure result, the UE can determine that the first ignore flag is the fifth value or the sixth value, and continue to determine that the failure result cannot be ignored, triggering the RLF as shown in Figure 4A, determining that the RRC reconfiguration process has failed, and entering the RRC connection reconfiguration process.

[0195] It should be noted that the above-mentioned indication of whether the process / result of the corresponding verification process can be ignored by the value of the ignore flag is only a specific implementation. In other embodiments of the present application, the ignore flag may not include a specific value. Then, for a verification process configured with the ignore flag, it can be indicated that the process / result of the verification process can be ignored. Conversely, for a verification process not configured with the ignore flag, it can be indicated that both the process and the result of the verification process cannot be ignored.

[0196] It can be understood that, in a specific implementation process, the at least one ignore flag mentioned above may be included in the configuration information stored in the electronic device.

[0197] Exemplarily, the configuration information may include first indication information, which corresponds to any one of at least one ignorable flag. Therefore, the first indication information may point to the verification process corresponding to the corresponding ignorable flag. For example, the first indication information may point to the first verification process. The first indication information is used to indicate that the process / result of the corresponding verification process (e.g., the first verification process) can be ignored. In a specific implementation, the configuration of the value in the first indication information, or whether the first indication information is configured, can refer to the configuration implementation of the ignorable flag described above. For example, when the first indication information is configured to the fourth value, it indicates that a failed result of the first verification process can be ignored. When the first indication information is configured to the third value, it indicates that the first verification process can be ignored. When the first indication information is configured to the fifth value, it indicates that a failed result of the first verification process cannot be ignored. When the first indication information is configured to the sixth value, it indicates that the first verification process cannot be ignored. In a specific implementation, the third and fourth values ​​may be the same. The fifth and sixth values ​​may also be the same. Thus, the value of the first indication information can include two situations: when the first indication information value is the third or fourth value, it indicates that the process / result of the first verification process can be ignored; and when the first indication information value is the fifth or sixth value, it indicates that the process / result of the first verification process cannot be ignored. In other embodiments, the configuration information only includes first indication information for verification processes whose processes / results can be ignored. That is, the UE can determine whether the current verification process can be ignored based on the configuration of the first indication information. For example, if the first verification process is configured with the first indication information, the process / result corresponding to the first verification process can be ignored. Conversely, if the first verification process is not configured with the first indication information, the process / result corresponding to the first verification process cannot be ignored.

[0198] As a possible implementation, the first indication information in the configuration information can be stored in a specific table entry of the electronic device, so that the electronic device can retrieve the specific table entry when executing S507 and determine whether the process / result of the currently executed verification processing can be ignored. As another possible implementation, the first indication information in the configuration information can also be stored in a specific code segment in the UE, so that the electronic device can retrieve the specific code segment when executing S507 and determine whether the process / result of the currently executed verification processing can be ignored.

[0199] Thus, in this example, although the first check violates the protocol due to the change in the first cipheringDisabled, the UE can determine that the process / failure result of the first check can be ignored. Therefore, if all other check items are successful, the UE can consider that all checks are successful and confirm that the current RRC reconfiguration process can be continued.

[0200] S508. The UE accesses cell B.

[0201] It is understandable that, when all verification processes are successful, the UE can switch to cell B and continue the current call according to the switching indication to cell B configured in the RRC reconfiguration message 52.

[0202] S509 : The UE sends an RRC reconfiguration complete message 53 to base station B.

[0203] In this way, even if the first verification fails during the verification process, the UE can continue the current RRC reconfiguration process if it determines that the first verification process / failure result can be ignored, and camp on cell B according to the handover instruction issued by the base station to continue the current call. This can avoid RLF or enter the RRC connection reestablishment process, thereby avoiding the resulting call freeze or interruption.

[0204] It is understood that in the implementation of the solution shown in FIG5A , the example is taken as follows: after the UE performs and determines that the first verification process / failure result can be ignored. In other embodiments, the UE may also determine that the first verification process / failure result can be ignored before performing the first verification.

[0205] As an example, referring to FIG5B , there is provided a flow chart of a communication method according to an embodiment of the present application.

[0206] In conjunction with the implementation of the solution in FIG5A , in the solution shown in FIG5B , the UE can perform a verification process after receiving the RRC reconfiguration message 52. Continuing with the example of all verification processes other than the first verification being successful. In the implementation of the solution shown in FIG5B , the UE can execute S510 before performing the first verification process to determine whether the process / failure result of the first verification can be ignored. It is understood that the specific implementation of S510 can refer to S507 shown in FIG5A . In this way, before performing the first verification, the UE can know that the process / failure result of the first verification has no impact on the success of the subsequent RRC reconfiguration process. In this example, the UE can skip the execution of the first verification and directly execute S508 according to the success of the RRC reconfiguration process, that is, access cell B under the instruction of the RRC reconfiguration message 52. Next, the UE can execute S509 to send an RRC reconfiguration completion message 53 to the base station B of the currently accessed cell. As a result, the UE can save time and power consumption overhead for the first verification.

[0207] In this way, through the implementation of the scheme of Figures 5A and 5B above, based on the judgment of whether the verification processing process / failure result corresponding to the verification failure provided in the embodiment of the present application can be ignored, the preset ignorable verification processing can be made to avoid RLF caused by verification failure and enter the RRC connection reconfiguration process, thereby avoiding the corresponding communication interruption.

[0208] 5A and 5B , the description is made by taking the negligible verification process as the first verification process. In other embodiments of the present application, the negligible verification process may further include other verification processes.

[0209] For this purpose, an embodiment of the present application also provides a communication method, which can enable the preset negligible verification processing to obtain the effect of successfully completing the RRC reconfiguration process as shown in the examples shown in Figures 5A and 5B even if the verification fails.

[0210] For example, referring to FIG6 , the first base station corresponding to the first cell currently accessed by the UE instructs the UE to access the second cell. The second cell corresponds to the second base station. The solution may include:

[0211] S601. UE receives an RRC reconfiguration message 61 from a first base station.

[0212] Exemplarily, the RRC reconfiguration message 61 may correspond to the RRC reconfiguration message 52 shown in FIG. 5A or FIG. 5B . In some implementations, the RRC reconfiguration message 61 may include the securityConfig field in the above example. In other implementations, the RRC reconfiguration message 61 may also include other fields configured to the UE.

[0213] S602: UE performs verification processing.

[0214] Exemplarily, the UE may perform at least one verification process after entering the RRC reconfiguration process. For example, the at least one verification process may include a first verification process. Alternatively, the at least one verification process may also include other protocol compliance verification processes.

[0215] It should be noted that, in combination with the above description, in the implementation of S602, the object of the verification process may include the parameters delivered in the RRC reconfiguration message 61. In other implementations, the object of the verification process may also include parameters delivered by other RRC reconfiguration messages before the RRC reconfiguration message 61.

[0216] S603: For each verification process, the UE determines whether the verification process result is failure. If failure, execute S604.

[0217] S604: The UE determines whether the failure item can be ignored. If so, S605 is executed. The UE may be preset with at least one ignore flag, each of which corresponds to a verification process. The UE may determine whether the current failure item can be ignored based on the value of the ignore flag or the configuration of the ignore flag. The specific execution process can be referred to S507 shown in FIG. 5A . This description is not repeated here.

[0218] In this example, the UE first performs a verification process and then determines whether it can be ignored. In conjunction with the description in FIG5B , in other embodiments, the UE may also determine whether the verification process can be ignored before performing the verification process. In this way, if the verification process or failure result is negligible, the UE can selectively perform or skip the verification process. If the verification process fails during execution, the result can be considered successful and other verification processes can be continued.

[0219] It should be noted that, as shown in FIG6 , in the case of multiple verification processes, the UE may execute S602 to S604 for each verification process until all verification processes are completed and it is determined that all verification processes are successful, or the verification failure result can be ignored. The UE may then execute the following S605 .

[0220] S605: The UE switches and resides in the second cell.

[0221] If all verification processes are successful, or if there is a verification failure that can be ignored, the UE may continue to perform the RRC reconfiguration process according to the configuration of base station A. For example, the UE may switch to camp on the second cell according to the cell information of the second cell carried in the RRC reconfiguration message 61.

[0222] S606. The UE sends an RRC reconfiguration complete message 62 to the second base station.

[0223] It is understandable that since all verification processes are successful, or there is a verification failure and the verification failure can be ignored, the UE can successfully complete the RRC reconfiguration process. In this way, in conjunction with the example in Figure 1, the UE can send an RRC reconfiguration complete message 62 to the second base station corresponding to the currently camped cell (such as the second cell).

[0224] Thus, based on the solution shown in FIG6 , the UE can ignore the corresponding verification process / failure result according to at least one preset ignore flag, thereby avoiding RLF caused by the corresponding verification process failure and entering RRC connection re-establishment, thereby avoiding the corresponding call interruption.

[0225] In the implementation of the above solutions, the UE switches to the second base station according to the instruction of the first base station and sends an RRC reconfiguration completion message as an example. The solution provided in the embodiment of the present application can also be applied to the scenario where the UE always resides in the first cell corresponding to the first base station.

[0226] For example, refer to FIG7 , which is a flowchart of another communication method provided in an embodiment of the present application.

[0227] As shown in Figure 7, the solution may include:

[0228] S701. UE receives an RRC reconfiguration message 71 from a first base station.

[0229] S702: UE performs verification processing.

[0230] S703: For each verification process, the UE determines whether the verification process result is failure. If failure, execute S704.

[0231] S704: The UE determines whether the failure item can be ignored. If so, S705 is executed.

[0232] S705. The UE continues to reside in the first cell.

[0233] S706. The UE sends an RRC reconfiguration complete message 72 to the first base station.

[0234] In this example, in combination with the scheme description in Figure 6, the execution of each step can refer to each other. The main difference is that, in this example, the RRC reconfiguration message 71 is different from the RRC reconfiguration message 61. The RRC reconfiguration message 71 may carry the cell information of the currently resident cell (such as the first cell), or the RRC reconfiguration message 71 may not include the cell information. In this way, the UE can continue to reside in the current first cell after successfully completing the current RRC reconfiguration process. For example, after S704, if all verification processes are successful, or the verification processes of failed verifications can be ignored, the UE can continue to reside in the first cell. Correspondingly, in S706, the UE can send an RRC reconfiguration completion message 72 to the first base station of the currently resident first cell.

[0235] In the description of FIG. 5A to FIG. 7 above, the UE can configure whether each verification process is ignorable by configuring a corresponding ignore flag for each verification process (or configuring a prescribed ignore flag for an ignorable verification process).

[0236] In other embodiments of the present application, the UE may also be configured with functions for managing and controlling all ignored configurations.

[0237] Exemplarily, the UE may be configured with a skip switch, which is used to enable one or more ignore configuration capabilities. For example, each check process is configured with an ignore flag, and the process / failure result of the check process with the ignore flag set to the third value or the fourth value can be ignored.

[0238] Thus, when the skip switch is on, the ignore configuration for each check process with the ignore flag set to the third or fourth value takes effect. For example, if the ignore flag for the first check is the third value, the UE can ignore the failure result if the first check fails; alternatively, the UE can skip the first check. For another example, if the ignore flag for the first check is the fourth value, the UE can ignore the failure result if the first check fails; alternatively, the UE can skip the first check.

[0239] Correspondingly, when the skip switch is off, the ignore configuration does not take effect. For example, the ignore flag of the first check is the first value. Since the skip switch is off, if the first check fails, the corresponding RLF and subsequent RRC connection re-establishment will be triggered.

[0240] In addition, if multiple ignore flags are configured in the UE, the skip switch can be used for overall control. For example, if multiple ignore flags are all the third or fourth values, if the skip switch is turned off, all corresponding verification process failure results or verification process ignore configurations will not take effect.

[0241] It should be noted that, in conjunction with the description of the specific implementation of the ignore flag in S507 above, in some embodiments of the present application, the skip switch may be configured in configuration information including first indication information. The first indication information corresponds to any one of the at least one ignore flag. Thus, in an implementation where the UE is configured to determine whether the skip switch is on, the UE may call the configuration information and then obtain, from the specified field / table entry in the configuration information, whether the skip switch is currently configured to be on or off.

[0242] As an example, refer to Figure 8. In this example, the solution shown in Figure 6 is used to implement the skip switch judgment logic. Similarly, the solution shown in Figure 7 can also be combined with the skip switch judgment logic for overall control. The specific implementation is similar and will not be repeated here.

[0243] As shown in Figure 8, the solution may include:

[0244] S801. Base station A sends an RRC reconfiguration message 81 to a UE.

[0245] S802: UE performs verification processing.

[0246] S803: For each verification process, the UE determines whether the verification process result fails. If failed, execute S804.

[0247] S804: The UE determines whether the failure item can be ignored. If so, S805 is executed.

[0248] S805: The UE determines whether the skip switch is on. If the skip switch is on, the process proceeds to S806.

[0249] S806: The UE switches and camps on the second cell.

[0250] S807. The UE sends an RRC reconfiguration complete message 82 to the second base station.

[0251] In the implementation of the solution shown in FIG8 , the execution of each step can refer to the implementation of the solution shown in FIG6 . In this example, before S806 , the UE can determine whether the skip switch is turned on when it is determined that there is at least one failure item that can be ignored. If the skip switch is turned on, all corresponding skip configurations take effect. In this way, the UE can confirm that all verification failure results or the corresponding verification processing can be ignored, successfully perform the RRC reconfiguration process, and switch to the second cell to continue the current call. Correspondingly, if there is at least one failure item that can be ignored, but the skip switch is turned off. In this way, the UE can exit the current RRC reconfiguration process based on the existence of at least one verification failure result, trigger RLF and enter the RRC connection reconfiguration process.

[0252] For example, if the first verification fails and the process / failure result of the first verification is negligible, the UE can determine whether the skip switch is on if it determines that the process / failure result of the first verification is negligible. If the skip switch is on and all other verification processes are successful, the UE can confirm that the RRC reconfiguration process has been successfully completed and switch to the second cell to continue the current call.

[0253] In the example solution shown in Figure 8, if the UE determines that the failure item corresponding to the verification result is ignorable, it may perform subsequent operations such as S805. In other cases, the current verification result cannot be ignored. Accordingly, embodiments of the present application also provide a communication method for the UE to perform corresponding processing when it determines that the current verification result has failed or the verification process cannot be ignored. As an example, the solution may include: a first base station sends an RRC reconfiguration message 91 to the UE. The UE performs verification processing. The UE determines whether the verification result has failed. For example, after performing a first verification, the UE determines that the first verification has failed. The UE determines whether the failure item is ignorable. In some embodiments, if all verification failures are ignorable, the UE may continue to perform subsequent operations. In other embodiments, if a verification failure cannot be ignored, the UE may skip to perform subsequent operations. For example, after completing the first verification, the UE may determine that the first verification has failed. Accordingly, the UE may query the value of the verification configuration corresponding to the first verification. If the value of the verification configuration indicates that the first verification cannot be ignored, the UE initiates an RRC connection reestablishment process with the second base station. This avoids the base station determining that the RRC reconfiguration is complete, causing the current communication to be unable to continue.

[0254] In the case that all verification failure results can be ignored, the UE determines whether the skip switch is turned on.

[0255] When the skip switch is turned on, the UE switches and camps on the second cell. Then, the UE may send an RRC reconfiguration complete message 92 to the second base station.

[0256] On the contrary, when the skip switch is turned off, the UE can initiate an RRC connection re-establishment process to the second base station, thereby preventing the base station from determining that the RRC reconfiguration is complete, resulting in the inability to continue the current communication.

[0257] In this example, if a failure item cannot be ignored or the switch is skipped and turned off, the UE can stop the current RRC reconfiguration process and instead initiate an RRC connection reestablishment process to the base station (such as the second base station) to which the current resident cell (such as the second cell) belongs.

[0258] As shown in FIG8 , the UE may determine whether the skip switch is on after determining whether the failed item is ignorable. In other embodiments of the present application, the UE may also determine whether the failed item is ignorable after determining whether the skip switch is on. The present application does not limit the order of triggering the determination of whether the failed item is ignorable or the determination of whether the skip switch is on after a verification process fails.

[0259] Therefore, through the solutions provided in Figures 5A to 8 above, the UE can avoid terminating the RRC reconfiguration process even if a negligible verification protocol failure occurs (such as a change in the cipheringdisabled field configuration of a DRB). This prevents the UE from entering the RRC connection reestablishment process with the base station, thereby avoiding the resulting communication interruption problem.

[0260] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of an electronic device (such as UE). Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0261] The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.

[0262] For example, FIG9 shows a schematic diagram of the composition of a communication device 900. The communication device 900 can be applied to an electronic device (such as a UE). The communication device 900 shown in FIG9 can be used to implement the communication method provided in any one of FIG5A to FIG8.

[0263] As shown in FIG9 , the communication device 900 may include:

[0264] The receiving unit 901 is configured to receive a first radio resource control RRC reconfiguration message.

[0265] The verification unit 902 is configured to perform a verification process, where the verification process includes a first verification.

[0266] The sending unit 903 is configured to send a first RRC reconfiguration completion message when the verification failure result of the first verification can be ignored or the first verification process can be ignored.

[0267] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0268] Referring to Figure 10 , a schematic diagram illustrating the components of an electronic device 1000 provided in an embodiment of the present application is provided. As shown in Figure 10 , the electronic device 1000 may include a processor 1001 and a memory 1002. The memory 1002 is configured to store computer-executable instructions. For example, in some embodiments, when the processor 1001 executes the instructions stored in the memory 1002, the electronic device 1000 may perform any of the methods described in the aforementioned embodiments.

[0269] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0270] It is understandable that the example shown in FIG10 provides a schematic diagram of the composition of a possible electronic device, which may correspond to the UE involved in the aforementioned embodiments.

[0271] In other embodiments, as shown in FIG11 , the embodiment of the present application also provides another possible composition of an electronic device.

[0272] In this example, the electronic device may include at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, or a smart city device. The embodiments of the present application do not impose any particular restrictions on the specific type of the electronic device.

[0273] The electronic device may include a processor 1110, an external memory interface 1120, an internal memory 1121, a universal serial bus (USB) connector 130, a charging management module 1140, a power management module 1141, a battery 1142, an antenna 1, an antenna 2, a mobile communication module 1150, a wireless communication module 1160, an audio module 1170, a speaker 1170A, a receiver 1170B, a microphone 1170C, an earphone interface 1170D, a sensor module 1180, a button 1190, a motor 1191, an indicator 1192, a camera module 1193, a display screen 1194, and a subscriber identification module (SIM) card interface 1195, etc. The sensor module 1180 may include a pressure sensor 1180A, a gyroscope sensor 1180B, an air pressure sensor 1180C, a magnetic sensor 1180D, an acceleration sensor 1180E, a distance sensor 1180F, a proximity light sensor 1180G, a fingerprint sensor 1180H, a temperature sensor 1180J, a touch sensor 1180K, an ambient light sensor 1180L, a bone conduction sensor 1180M, etc.

[0274] Processor 1110 may include one or more processing units. For example, as shown in FIG11 , in this example, processor 1110 may include a first processor 1110A and a second processor 1110B. In some implementations, first processor 1110A may be an application processor (AP). In other implementations, second processor 1110B may be a modem processor.

[0275] In other embodiments, the processor 1110 may further include a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor (BP or BBP), and / or a neural-network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0276] The processor can generate operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0277] Processor 1110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 1110 may be a cache memory. This memory can store instructions or data that have been used or are frequently used by processor 1110. When processor 1110 needs to use the instruction or data, it can directly access it from this memory. This avoids duplicate accesses, reduces processor 1110 latency, and thus improves system efficiency.

[0278] In some embodiments, the processor 1110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc. The processor 1110 may be connected to a touch sensor, an audio module, a wireless communication module, a display, a camera module, etc. through at least one of the above interfaces.

[0279] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only for illustrative purposes and does not constitute a structural limitation on the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0280] It should be noted that the structures illustrated in the embodiments of this application do not constitute specific limitations on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0281] In an embodiment of the present application, one or more chip systems may be provided in the UE. The one or more chip systems may be used to support the UE in implementing the communication method provided in any one of Figures 5A to 8. The chip system may also be referred to as a chip module.

[0282] As an example, FIG12 is a schematic diagram of the composition of an electronic device provided in an embodiment of the present application.

[0283] As shown in Figure 12, the electronic device may include a first chip module and a second chip module. In some embodiments, the first chip module may correspond to the second processor shown in Figure 11, and the second chip module may correspond to the first processor shown in Figure 11.

[0284] In the example shown in FIG. 12 , the first chip module may include a NAS layer 1201 , an RRC layer 1202 , a PDCP layer 1203 , an RLC layer 1204 , a MAC layer 1205 , and a PHY layer 1206 .

[0285] NAS stands for Non-Access Stratum, and NAS layer 1201 is also known as the non-access stratum. NAS layer 1201 is primarily responsible for providing control and management of the non-access stratum. For example, it manages EPS bearer management, authentication, mobility management in the EPS connection management mode idle state (i.e., ECM-IDLE state), generates paging messages for UEs in the ECM-IDLE state, and performs security control.

[0286] The RRC layer 1202 is a high-level layer in the control plane, primarily responsible for controlling the L1 / L2 layer to complete air interface resource transmission and providing information transmission services for the NAS layer 1201. For example, the RRC layer 1202 can be used to manage functions such as system message broadcasting, RRC connection control, mobility management, and measurement configuration reporting. RRC connection control management includes paging, establishing / modifying / suspending / resume / release RRC connections, initial security activation, establishing / modifying / activating SRBs / DRBs, cell management in DC and CA modes, and radio link failure recovery.

[0287] The various judgments and control logics provided in the embodiments of the present application can be implemented by the RRC layer 1202. For example, S602-S604 in Figure 6 can be implemented by the RRC layer 1202. In the implementation of the solution shown in Figure 6, other steps can also be implemented by other protocol layers and the RRC layer 1202.

[0288] PDCP is the abbreviation of Packet Data Convergence Protocol, and the PDCP layer 1203 is also the packet data convergence protocol layer. The PDCP layer 1203 is used to process RRC messages on the control plane and Internet Protocol (IP) packets on the user plane. For example, on the user plane, after the PDCP layer 1203 receives the IP data packet from the upper layer, it can perform header compression and encryption on the IP data packet, and then submit it to the RLC layer 1204. The PDCP layer 1203 also provides in-order submission and duplicate packet detection functions to the upper layer. In the control plane, the PDCP layer 1203 provides signaling transmission services for the upper layer RRC, and implements encryption and consistency protection of RRC signaling, as well as decryption and consistency checking of RRC signaling in the reverse direction.

[0289] RLC stands for Radio Link Control, and the RLC layer 1204 is the radio link control layer. The RLC layer 1204 primarily provides radio link control functions, offering services such as segmentation, retransmission control, and on-demand transmission to upper layers. The RLC layer 1204 supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). It primarily provides functions such as error correction, segmentation, and reassembly.

[0290] MAC stands for Media Access Control, and the MAC layer 1205 is the media access control layer. The MAC layer 1205 provides mapping between logical channels and transport channels; multiplexes MAC SDUs from one or more logical channels into a transport block and passes it to the PHY layer 1206; demultiplexes the transport block from the PHY layer 1206 into multiple MAC SDUs and passes them to one or more logical channels; reports scheduling information; performs error correction through HARQ; manages user priorities through dynamic scheduling; and manages logical channel priorities.

[0291] The PHY layer 1206 is the physical layer. It provides the mechanical, electrical, functional, and regulatory characteristics required to create, maintain, and dismantle the physical links required for data transmission. The physical layer ensures that raw data can be transmitted across various physical media.

[0292] As shown in FIG12 , in an embodiment of the present application, the NAS layer 1201, RRC layer 1202, PDCP layer 1203, RLC layer 1204, MAC layer 1205, and PHY layer 1206 can be integrated into a first chip module of an electronic device. For example, the first chip module can be a modem of the electronic device.

[0293] In addition, in some embodiments, an application layer 1207 may be provided in the electronic device. The application layer 1207 may be provided above the NAS layer 1201. The application layer may be used to process and judge signaling from the NAS layer, and to send communication signaling and data to the NAS layer.

[0294] In the example shown in FIG12 , the application layer 1207 may be provided in a second chip module of the electronic device. For example, the second chip module may be an application processor (APU or AP) of the electronic device.

[0295] In other embodiments, the application 1207, the NAS layer 1201, the RRC layer 1202, the PDCP layer 1203, the RLC layer 1204, the MAC layer 1205, and the PHY layer 1206 may also be in the same chip module. The embodiments of the present application do not specifically limit the division and configuration of the various protocol layers in the electronic device.

[0296] In the example shown in Figure 12 above, the chip system in the electronic device is illustrated from the perspective of protocol division. In other embodiments of the present application, refer to Figure 13, which is a schematic diagram of the composition of a chip system 1300. The chip system 1300 may include: a processor 1301 and a communication interface 1302, which are used for the UE to implement the functions involved in the above embodiments. In one possible design, the chip system also includes a memory for storing program instructions and data necessary for the electronic device. The chip system can be composed of chips, or it can include chips and other discrete devices. It should be noted that in some implementations of the present application, the communication interface 1302 can also be referred to as an interface circuit. As a possible implementation, the chip system 1300 can correspond to the first chip module and / or the second chip module shown in Figure 12, etc.

[0297] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0298] The functions, actions, operations, steps, etc. in the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that can be integrated with one or more media. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0299] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: The method is applied to an electronic device, and the electronic device is in a call process, and the method includes: The electronic device receives a first radio resource control (RRC) reconfiguration message, where the first RRC reconfiguration message includes a first parameter and a first value corresponding to the first parameter; before receiving the first RRC reconfiguration message, the electronic device stores a first configuration item, where the first configuration item includes a second parameter and a second value corresponding to the second parameter, and the first parameter and the second parameter are related to the same attribute corresponding to the same object; The electronic device performs verification processing on the first RRC reconfiguration message and the first configuration item, wherein the verification processing includes a first verification, and the first verification includes verifying the first parameter and a first value corresponding to the first parameter, and the second parameter and a second value corresponding to the second parameter; When the verification failure result of the first verification can be ignored, or the first verification process can be ignored, the electronic device sends a first RRC reconfiguration completion message.

2. The method according to claim 1, characterized in that: The first parameter and the second parameter are related to the same attribute corresponding to the same object, including: the first parameter and the second parameter are both related to the encryption attribute corresponding to the first DRB.

3. The method according to claim 2, characterized in that The first configuration item is stored in the electronic device, including: before receiving the first RRC reconfiguration message, the electronic device receives a second RRC reconfiguration message, the second RRC reconfiguration message includes the second parameter and a second value corresponding to the second parameter, the second parameter is an encryption identifier corresponding to the first DRB, and the second value corresponding to the encryption identifier of the first DRB indicates that data transmitted through the first DRB does not need to be encrypted; The first parameter is an encryption algorithm, and the first value corresponding to the first parameter is the content corresponding to the encryption algorithm, and the content corresponding to the encryption algorithm indicates that the data transmitted through the first DRB needs to be encrypted based on the content corresponding to the encryption algorithm; the first RRC reconfiguration message does not include the encryption identifier corresponding to the first DRB and the value corresponding to the encryption identifier of the first DRB.

4. The method according to claim 3, characterized in that The second RRC reconfiguration message includes the second parameter and a second value corresponding to the second parameter, where the second parameter is an encryption identifier corresponding to the first DRB, and the second value corresponding to the encryption identifier of the first DRB indicates that data transmitted through the first DRB does not need to be encrypted, including: The second RRC reconfiguration message includes a first cipheringDisabled field, the first cipheringDisabled field corresponds to the first DRB; the first cipheringDisabled field indicates an encryption identifier of the first DRB; the value of the first cipheringDisabled field is configured to true, indicating that data transmitted through the first DRB does not need to be encrypted; The first RRC reconfiguration message includes a first parameter and a first value corresponding to the first parameter, the first parameter is an encryption algorithm, the first value corresponding to the first parameter is content corresponding to the encryption algorithm, and the content corresponding to the encryption algorithm indicates that data transmitted through the first DRB needs to be encrypted based on the content corresponding to the encryption algorithm, including: The first RRC reconfiguration message includes an encryption configuration securityConfig field, where the securityConfig field is used to indicate the encryption algorithm, and the securityConfig field indicates that the first DRB needs to be encrypted based on the encryption algorithm.

5. The method according to claim 4, characterized in that When the first cipheringDisabled field is configured to true, the first RRC reconfiguration message carries the securityConfig field and the content corresponding to the securityConfig field, and the first RRC reconfiguration message does not include the first cipheringDisabled field and the value corresponding to the first cipheringDisabled field, the first verification fails.

6. The method according to any one of claims 1 to 5, characterized in that Before the electronic device sends the first RRC reconfiguration completion message, the method further includes: The electronic device determines that a verification failure result of the first verification can be ignored, or that a process of the first verification can be ignored; The electronic device sending a first RRC reconfiguration completion message includes: The electronic device ignores the verification failure result of the first verification or skips the first verification, and sends a first RRC reconfiguration completion message.

7. The method according to any one of claims 1 to 6, characterized in that Configuration information is stored in the electronic device, and the configuration information includes first indication information, and the first indication information is used to indicate whether a failure result or process of the first verification can be ignored; The electronic device determines that a verification failure result of the first verification can be ignored, or that a process of the first verification can be ignored, including: The electronic device determines, based on the first indication information, that a verification failure result of the first verification can be ignored, or that the first verification process can be ignored.

8. The method according to any one of claims 1 to 7, characterized in that When the electronic device receives the first RRC reconfiguration message, the electronic device resides in a first cell, and the first cell corresponds to a first base station; Before the electronic device sends the first RRC reconfiguration completion message, the method further includes: The electronic device continues to reside in the first cell; The electronic device sending a first RRC reconfiguration completion message includes: The electronic device sends the first RRC reconfiguration completion message to the first base station.

9. The method according to any one of claims 1 to 7, characterized in that: When the electronic device receives the first RRC reconfiguration message, the electronic device resides in a first cell, and the first cell corresponds to a first base station; The first RRC reconfiguration message includes cell information of the second cell, and the first RRC reconfiguration message is used to instruct the electronic device to switch to the second cell; Before the electronic device sends the first RRC reconfiguration completion message, the method further includes: The electronic device resides in the second cell according to the cell information of the second cell, the second cell corresponds to a second base station; the second cell is different from the first cell; The electronic device sending a first RRC reconfiguration completion message includes: The electronic device sends the first RRC reconfiguration completion message to the second base station.

10. The method according to any one of claims 2 to 4, characterized in that: The second RRC reconfiguration message is received by the electronic device before entering a call process.

11. The method according to claim 7, characterized in that At least one ignore configuration is preset in the electronic device, and the first indication information corresponds to any one of the at least one ignore configuration; Before the electronic device sends the first RRC reconfiguration completion message, the method further includes: The electronic device determines, according to the at least one ignore configuration, that a verification failure result of the first verification can be ignored, or that a process of the first verification can be ignored; Wherein, the at least one ignore configuration includes a first ignore flag, When the first ignore flag is configured as a third value, it indicates that the first verification process can be ignored; or, When the first ignore flag is configured as a fourth value, it indicates that the verification failure result of the first verification can be ignored.

12. The method according to claim 7, characterized in that The configuration information of the electronic device further includes a skip switch, wherein the skip switch is used to enable a verification failure result of the first verification to be ignored, or the skip switch is used to enable a process of the first verification to be ignored; Before the electronic device sends the first RRC reconfiguration completion message, the method further includes: The electronic device determines that the skip switch is turned on.

13. A communication device, characterized in that: The device is applied in an electronic device, and is used to communicate with a base station according to the communication method according to any one of claims 1 to 12.

14. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein one or more computer programs are stored in the memory. When the one or more computer programs are executed by the processor, the electronic device executes the communication method according to any one of claims 1 to 12 to communicate with the base station.

15. The electronic device according to claim 14, characterized in that: The processor includes a modem.

16. A chip system, characterized in that: The chip system is applied to an electronic device; the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through lines; the interface circuit is used to receive a signal from a memory of the electronic device and send the signal to the processor, the signal including a computer instruction stored in the memory; when the processor executes the computer instruction, the electronic device executes the method as described in any one of claims 1-12.

17. The chip system according to claim 16, characterized in that: The chip system includes a modem.

Citation Information

Patent Citations

  • Communication method, communication device and electronic equipment

    CN119031517A

  • Evolved Node B reconfiguration method, user equipment, and evolved Node B

    CN104618927A

  • RRC (Radio Resource Control) connection reestablishment method and device and storage medium

    CN115150852A

  • Message processing method and device

    CN115426697A

  • Communication method

    CN117062253A