CN111132228A

CN111132228A - Method and device for processing RRC reconfiguration message, storage medium and terminal

Info

Publication number: CN111132228A
Application number: CN201911359952.1A
Authority: CN
Inventors: 王星
Original assignee: Spreadtrum Semiconductor Chengdu Co Ltd
Current assignee: Spreadtrum Semiconductor Chengdu Co Ltd
Priority date: 2019-12-25
Filing date: 2019-12-25
Publication date: 2020-05-08
Anticipated expiration: 2039-12-25
Also published as: CN111132228B

Abstract

A processing method and device, storage medium and terminal of RRC reconfiguration message are provided, the method comprises: acquiring DRB configuration information contained in the RRC reconfiguration message, and recording the DRB configuration information as first DRB configuration information, wherein the first DRB configuration information comprises at least one of a DRB deletion list and a DRB addition modification list; acquiring current DRB configuration information of the user equipment, and recording the current DRB configuration information as second DRB configuration information; judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information or not according to the first DRB configuration information and the second DRB configuration information; and when the judgment result shows that no parameter conflict exists, performing DRB configuration operation according to the first DRB configuration information. The scheme provided by the invention can better avoid RRC reconstruction operation, furthest tolerate abnormal conditions of a network side and effectively prevent rate from falling.

Description

Method and device for processing RRC reconfiguration message, storage medium and terminal

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for processing an RRC reconfiguration message, a storage medium, and a terminal.

Background

Protocol 36.331, section 5.3.10.3, formulated by the third Generation Partnership Project (3rd Generation Partnership Project, 3GPP), specifies that unless a full configuration function is used in a Radio Resource Control (RRC) reconfiguration message for handover (handover) or in an RRC reconfiguration message after re-establishment (re-establishment), User Equipment (User Equipment, UE) is not supported for network configuration in which the same Data Radio Bearer (DRB) Identity (DRB-Identity, DRBID) is deleted and added in one RRC reconfiguration message at the same time.

However, in an actual network, the following abnormal configuration may occur due to the fact that the network side device does not follow the protocol or the network side device is abnormal:

1) in the RRC reconfiguration message for switching or the reconstructed RRC reconfiguration message, the same DRBID, namely configuration deletion operation and configuration addition operation are carried out without using a complete configuration function;

2) in the RRC reconfiguration message which is not used for switching and the RRC reconfiguration message which is not rebuilt, the same DRBID, namely the configuration deleting operation and the configuration adding operation, is directly configured.

When the UE receives the above abnormal configuration sent by the network side, the currently and commonly used processing manner is to start an RRC connection re-establishment (RRC connection re-establishment) process, referred to as RRC re-establishment operation, according to the description in section 5.3.5.5 of protocol 36.331.

However, the RRC reestablishment operation may not be performed for a while, and thus the rate may drop. A more serious situation is that if the network side always issues the abnormal configuration, the UE is completely unavailable at that location.

Disclosure of Invention

The technical problem solved by the invention is how to avoid RRC reestablishment operation as much as possible so as to prevent the UE rate from dropping.

To solve the foregoing technical problem, an embodiment of the present invention provides a method for processing an RRC reconfiguration message, including: acquiring DRB configuration information contained in the RRC reconfiguration message, and recording the DRB configuration information as first DRB configuration information, wherein the first DRB configuration information comprises at least one of a DRB deletion list and a DRB addition modification list; acquiring current DRB configuration information of the user equipment, and recording the current DRB configuration information as second DRB configuration information; judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information or not according to the first DRB configuration information and the second DRB configuration information; and when the judgment result shows that no parameter conflict exists, performing DRB configuration operation according to the first DRB configuration information.

Optionally, the determining, according to the first DRB configuration information and the second DRB configuration information, whether a parameter conflict exists when the DRB configuration operation is executed according to the first DRB configuration information includes: for each DRBID in a first list, judging whether the configuration of the second DRB configuration information and the first DRB configuration information on the DRBID conflicts, wherein the first list is selected from the first DRB configuration information; and when the judgment results of all DRBIDs in the first list are all non-confliction, determining that no parameter conflict exists.

Optionally, the determining whether the configuration of the DRBID by the second DRB configuration information and the first DRB configuration information conflicts includes: judging whether the second DRB configuration information contains the DRBID; if the second DRB configuration information contains the DRBID, judging whether the configuration of the second DRB configuration information and the first DRB configuration information to the DRBID is the same; and when the judgment result shows that the second DRB configuration information and the first DRB configuration information have the same configuration on the DRBID, determining that no conflict exists.

Optionally, the DRB addition modification list includes EBI configuration information, and the determining whether the configuration of the DRBID by the second DRB configuration information and the first DRB configuration information conflicts further includes: if the second DRB configuration information does not contain the DRBID, judging whether the EBI configuration information contains the EBI associated with the DRBID; determining a conflict when the judgment result indicates that the EBI configuration information does not contain the EBI associated with the DRBID; and when the judgment result shows that the EBI configuration information contains the EBI associated with the DRBID, judging whether the configuration of the EBI conflicts at least according to the second DRB configuration information.

Optionally, the DRB addition modification list includes EBI configuration information, and the determining whether the configuration of the DRBID by the second DRB configuration information and the first DRB configuration information is the same includes: judging whether the EBI configuration information contains the EBI associated with the DRBID; if the EBI configuration information contains the EBI associated with the DRBID, determining whether the configuration is the same at least according to the comparison result of the EBI associated with the DRBID in the EBI configuration information and the EBI associated with the DRBID in the second DRB configuration information; if the EBI configuration information does not include an EBI associated with the DRBID, determining whether the configurations are the same according to whether a second list is included with the DRBID, wherein the second list is selected from the first DRB configuration information and is different from the first list.

Optionally, the first list is a modification list added to the DRB, and the second list is a DRB deletion list.

Optionally, the determining whether the configurations are the same according to whether the second list includes the DRBID includes: determining that the configuration is not the same when the second list contains the DRBID; and when the second list does not contain the DRBID, or the first DRB configuration information does not contain the second list, determining that the configuration is the same.

Optionally, the determining whether the configurations are the same according to at least the comparison result between the EBI associated with the DRBID in the EBI configuration information and the EBI associated with the DRBID in the second DRB configuration information includes: when the EBI associated with the DRBID in the EBI configuration information is the same as the EBI associated with the DRBID in the second DRB configuration information, determining that the configuration is the same; and when the EBI associated with the DRBID in the EBI configuration information is different from the EBI associated with the DRBID in the second DRB configuration information, determining whether the configuration is the same according to whether the DRBID is contained in the DRB deletion list or not.

Optionally, the determining whether the configurations are the same according to whether the second list includes the DRBID includes: when the second list contains the DRBID, judging whether the configuration of the EBI conflicts at least according to the second DRB configuration information, wherein whether the configuration conflicts or not is used for indicating whether the configuration is the same; and when the second list does not contain the DRBID, or the first DRB configuration information does not contain the second list, determining that the configurations are different.

Optionally, the determining, according to at least the second DRB configuration information, whether there is a conflict with respect to the configuration of the EBI includes: judging whether the EBI is contained in the second DRB configuration information; if the EBI is included in the second DRB configuration information, determining whether a conflict exists according to whether the DRBID associated with the EBI in the second DRB configuration information is included in a second list, wherein the second list is selected from the first DRB configuration information, and the second list is different from the first list; and if the EBI is not contained in the second DRB configuration information, determining that no conflict exists.

Optionally, the determining whether the DRBID associated with the EBI is included in the second list according to whether the DRBID in the second DRB configuration information conflicts includes: determining no conflict if the DRBID associated with the EBI in the second DRB configuration information is included in the second list; and if the DRBID associated with the EBI in the second DRB configuration information does not contain the second list, or the first DRB configuration information does not contain the second list, determining a conflict.

Optionally, when the EBI associated with the DRBID in the EBI configuration information is the same as the EBI associated with the DRBID in the second DRB configuration information, the method further includes: and determining the type of DRB configuration operation according to whether the first DRB configuration information contains the second list and/or whether the second list contains the DRBID.

Optionally, the determining the type of DRB configuration operation according to whether the first DRB configuration information includes the second list includes: and when the first DRB configuration information does not contain the second list, determining the type of the DRB configuration operation as a DRB modification operation.

Optionally, the determining, according to whether the first DRB configuration information includes the second list and whether the second list includes the DRBID, the type of the DRB configuration operation includes: when the first DRB configuration information comprises the second list and the second list comprises the DRBID, determining the type of the DRB configuration operation as a DRB adding operation; when the first DRB configuration information contains the second list and the second list does not contain the DRBID, determining the type of the DRB configuration operation as a DRB modification operation.

Optionally, the processing method further includes: and when the judgment result shows that the parameter conflict exists, performing RRC reestablishment operation.

Optionally, the performing the DRB configuration operation according to the first DRB configuration information includes: executing DRB deleting operation according to the DRB deleting list; and executing DRB adding or modifying operation according to the DRB adding and modifying list.

Optionally, the step of determining whether there is a parameter conflict is performed when finding that the RRC reconfiguration message has an abnormal configuration, where the abnormal configuration refers to that the DRB deletion list and the DRB addition modification list contain the same DRBID.

An embodiment of the present invention further provides a device for processing an RRC reconfiguration message, including: a first obtaining module, configured to obtain DRB configuration information included in the RRC reconfiguration message, and record the DRB configuration information as first DRB configuration information, where the first DRB configuration information includes at least one of a DRB deletion list and a DRB addition modification list; a second obtaining module, configured to obtain current DRB configuration information of the user equipment, and record the current DRB configuration information as second DRB configuration information; a judging module, configured to judge whether a parameter conflict exists when performing a DRB configuration operation according to the first DRB configuration information and the second DRB configuration information; and the processing module executes DRB configuration operation according to the first DRB configuration information when the judgment result shows that no parameter conflict exists.

The embodiment of the invention also provides a storage medium, wherein computer instructions are stored on the storage medium, and the computer instructions execute the steps of the method when running.

The embodiment of the present invention further provides a terminal, which includes a memory and a processor, where the memory stores computer instructions capable of running on the processor, and the processor executes the steps of the method when executing the computer instructions.

Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:

the embodiment of the invention provides a method for processing an RRC reconfiguration message, which comprises the following steps: acquiring DRB configuration information contained in the RRC reconfiguration message, and recording the DRB configuration information as first DRB configuration information, wherein the first DRB configuration information comprises at least one of a DRB deletion list and a DRB addition modification list; acquiring current DRB configuration information of the user equipment, and recording the current DRB configuration information as second DRB configuration information; judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information or not according to the first DRB configuration information and the second DRB configuration information; and when the judgment result shows that no parameter conflict exists, performing DRB configuration operation according to the first DRB configuration information.

Compared with the prior art, the method directly performs reconfiguration operation after receiving the RRC reconfiguration message, and immediately performs RRC reestablishment operation when discovering that abnormal configuration exists in the RRC reconfiguration message. The UE adopting the scheme of this embodiment adds a judgment flow before processing the DRB configuration information issued this time by the network side. Specifically, the DRB deletion list, the DRB addition modification list and the current DRB configuration condition of the UE sent by the network side at this time are integrated, and it is determined whether the addition or modification procedure for the DRBID in the RRC reconfiguration message received at this time can be continuously executed.

Further, even if the network side has abnormal configuration this time, if it is determined through the determination process that parameter conflict will not occur with the existing DRB configuration when the DRB configuration operation is executed according to the DRB configuration information sent this time by the network side, it can be determined that the abnormal configuration can be understood and adopted by the UE. On this basis, even if the same DRBID is found in the DRB deletion list and the DRB addition modification list when the DRB configuration operation is subsequently executed according to the first DRB configuration information, since the previous judgment process has determined that no parameter conflict occurs, the UE can continue to apply the configuration of the network side without performing RRC reestablishment operation, so as to tolerate the abnormal situation of the network side to the maximum extent, prevent rate drop, and provide better experience for the mobile phone user.

Further, the determining, according to the first DRB configuration information and the second DRB configuration information, whether a parameter conflict exists when performing the DRB configuration operation according to the first DRB configuration information includes: for each DRBID in a first list, judging whether the configuration of the second DRB configuration information and the configuration of the first DRB configuration information on the DRBID conflict, wherein the first list is the DRB deletion list or the DRB addition modification list; and when the judgment results of all DRBIDs in the first list are all non-confliction, determining that no parameter conflict exists. Therefore, the first list is traversed to avoid conflict among the configurations of the DRBIDs in the first list, and when the judgment results of all the DRBIDs in the first list are not conflicting, the DRB deleting, adding or modifying operation can be executed according to the first DRB configuration information.

Drawings

Fig. 1 is a flowchart of a method for processing an RRC reconfiguration message according to an embodiment of the present invention;

FIG. 2 is a flow chart of one embodiment of step S103 of FIG. 1;

fig. 3 is a schematic structural diagram of a device for processing an RRC reconfiguration message according to an embodiment of the present invention.

Detailed Description

As mentioned in the background, the prior art has a disadvantage that when the UE receives the abnormal configuration on the network side, the normal processing method is to start the RRC reestablishment operation according to the description in section 5.3.5.5 of protocol 36.331.

However, performing the RRC reestablishment operation may cause the UE to have a period of time without data transmission, so that the rate drops. A more serious situation is that if the network side always issues the abnormal configuration, the UE is completely unavailable at that location.

The inventor of the present application finds out that the abnormal configuration can still be understood and adopted by the UE in some cases by deeply analyzing the relationship between the deletion and addition configurations of the DRBID in such abnormal configuration cases. Therefore, under these conditions, the UE can continue to apply the configuration of the network measurement without performing RRC reestablishment operation, so as to tolerate the abnormal condition of the network side to a greater extent, and prevent the rate from dropping, thereby providing better experience for the mobile phone user.

Based on this, an embodiment of the present invention provides a method for processing an RRC reconfiguration message, including: acquiring DRB configuration information contained in the RRC reconfiguration message, and recording the DRB configuration information as first DRB configuration information, wherein the first DRB configuration information comprises at least one of a DRB deletion list and a DRB addition modification list; acquiring current DRB configuration information of the user equipment, and recording the current DRB configuration information as second DRB configuration information; judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information or not according to the first DRB configuration information and the second DRB configuration information; and when the judgment result shows that no parameter conflict exists, performing DRB configuration operation according to the first DRB configuration information.

The UE adopting the scheme of this embodiment adds a judgment flow before processing the DRB configuration information issued this time by the network side. Specifically, the DRB deletion list, the DRB addition modification list and the current DRB configuration condition of the UE sent by the network side at this time are integrated, and it is determined whether the addition or modification procedure for the DRBID in the RRC reconfiguration message received at this time can be continuously executed.

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

Fig. 1 is a flowchart of a method for processing an RRC reconfiguration message according to an embodiment of the present invention.

The scheme of the embodiment can be applied to a Long Term Evolution (LTE for short) scene.

The scheme of this embodiment may be applied to a User Equipment side, for example, executed by a User Equipment (UE).

Specifically, referring to fig. 1, the method for processing an RRC reconfiguration message according to this embodiment may include the following steps:

step S101, obtaining DRB configuration information contained in the RRC reconfiguration message and recording the DRB configuration information as first DRB configuration information; the first DRB configuration information may include at least one of a DRB deletion list (DRB-ToReleaseList) and a DRB addition modification list (DRB-ToAddModList);

step S102, obtaining the current DRB configuration information of the user equipment, and recording the information as second DRB configuration information;

step S103, judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information and the second DRB configuration information;

when the determination result of the step S103 is negative, that is, there is no parameter conflict, further comprising a step S104, performing a DRB configuration operation according to the first DRB configuration information;

when the determination result in step S103 is positive, that is, there is a parameter conflict, step S105 is further included to perform an RRC reestablishment operation.

Specifically, the DRB is used for transmitting data, and the UE may associate a plurality of DRBs to transmit different services.

More specifically, the DRB addition modification list may include evolved packet System Bearer Identity (evolved packet System Bearer Identity, that is, eps-Bearer Identity, abbreviated as EBI) configuration information. A plurality of DRBs are distinguished by DRBIDs, and the DRBIDs correspond to the EBIs one by one.

More specifically, the DRB deletion list may include one or more DRBID. And when processing the DRB deletion list, the UE deletes the DRBID indicated by the DRB deletion list in the second DRB configuration information.

Further, the DRB addition modification list may include a DRB addition list, specifically including one or more DRBID and associated EBI. Wherein, the EBI associated with the DRBID in the DRB addition modification list can be carried by EBI configuration information.

Further, the DRB addition modification list may further include a DRB modification list, specifically including one or more DRBIDs. Wherein, the EBI associated with the DRBID in the DRB modification list can follow the existing configuration.

And when the DRB adding modification list is processed, the UE adds the DRBID in the list to the second DRB configuration information, or executes a modification process aiming at the existing DRBID according to the indication of the DRB adding modification list.

In one implementation, whether a parameter conflict exists is determined by determining whether the first DRB configuration information and the second DRB configuration information contradict the DRBID and EBI configurations.

In one implementation, the steps S101 and S102 may be executed synchronously or asynchronously. In the asynchronous execution, the step S102 may be executed before or after the step S101.

According to the protocol 36.331, section 5.3.10.0, when there are both a DRB deletion list and a DRB addition modification list in the RRC reconfiguration message, the DRB deletion list should be processed first, and then the DRB addition modification list should be processed. Correspondingly, the absence of parameter conflict in this embodiment means that: for DRBIDs simultaneously appearing in the DRB deletion list and the DRB addition modification list, if parameter conflicts do not appear when the DRBIDs are added or modified according to parameters in the DRB addition modification list after the DRB deletion list is processed, the DRBIDs can normally carry out the addition or modification process.

In a specific implementation, the determining step of step S103 may be performed when finding that the RRC reconfiguration message has an abnormal configuration, where the abnormal configuration refers to that the DRB deletion list and the DRB addition modification list contain the same DRBID.

In one implementation, the step S103 may include the steps of: for each DRBID in the first list, judging whether the configuration of the second DRB configuration information and the first DRB configuration information on the DRBID conflicts; and when the judgment results of all DRBIDs in the first list are all non-confliction, determining that no parameter conflict exists.

Specifically, the DRB deletion list and the DRB addition modification list included in the RRC reconfiguration message may be respectively referred to as a first list and a second list. In executing the step S103, the first list may be traversed as a reference to determine whether each DRBID in the first list conflicts with the configuration in the second DRB configuration information. Further, if the RRC reconfiguration message also configures the second list, it is also determined whether each DRBID in the first list conflicts with the configuration of the second list.

For example, the first list may be a modification list for the DRB, and the second list may be a deletion list for the DRB.

Next, referring to fig. 2, a specific flow of the step S103 is described in detail by taking the first list as the DRB addition modification list and the second list as the DRB deletion list as an example. Fig. 2 shows a flowchart of an embodiment of step S103 in fig. 1.

Specifically, step S1031 may be performed to respectively obtain the DRBID included in the DRB addition modification list. To execute a judgment process for each DRBID in the DRB addition modification list.

Further, step S1032 may be executed to determine whether the second DRB configuration information includes the DRBID.

If the determination result in the step S1032 is positive, that is, the DRBID is the same as a DRBID currently configured by the UE, it indicates that the network side configures the DRBID to the UE again under the condition that the UE has configured the DRBID. At this time, it may be further determined whether the DRBID is configured by the second DRB configuration information and the first DRB configuration information.

Specifically, step S1033 may be executed to determine whether the EBI configuration information includes an EBI associated with the DRBID.

If the determination result of the step S1033 is affirmative, it indicates that the EBI configuration for the DRBID exists in the EBI configuration information. However, this does not mean that the first DRB configuration information and the second DRB configuration information are the same for the EBI of the DRBID configuration, and therefore, a further determination is needed, such as determining whether the configuration is the same according to at least a comparison result between the EBI associated with the DRBID in the EBI configuration information and the EBI associated with the DRBID in the second DRB configuration information.

Specifically, step S1034 may be executed to compare whether the EBI associated with the DRBID in the EBI configuration information is the same as the EBI associated with the DRBID in the second DRB configuration information.

If the determination result in the step 1034 is positive, it indicates that the EBI configured by the UE and the network for the same DRBID is also the same. At this time, it may be determined that the first DRB configuration information and the second DRB configuration information are the same for the configuration of the DRBID. And the UE does not generate parameter conflict when executing reconfiguration operation according to the RRC reconfiguration message.

Further, in a case that a determination result of the step S1034 is positive, the type of the DRB configuration operation may also be determined according to whether the first DRB configuration information includes the second list, and/or whether the second list includes the DRBID. In the example shown in fig. 2, the second list is a DRB deletion list.

Specifically, when the determination result in the step S1034 is affirmative, a step S1035 may be further performed to determine whether the first DRB configuration information includes the DRB deletion list.

If the determination result in the step S1035 is negative, it indicates that the DRB deletion list does not exist, the RRC reconfiguration message of the network side does not indicate to delete a specific DRBID, but may only modify the relevant parameters of the currently configured DRBID of the UE. At this time, it may be determined that the type of the DRB configuration operation is a DRB modification operation. That is, when the DRB addition modification list is subsequently processed, a DRB modification procedure may be performed for the DRBID.

If the determination result of the step S1035 is affirmative, it indicates that the DRB deletion list exists. At this time, step S1036 may be further performed to determine whether the DRB deletion list includes the DRBID.

If the determination result in the step S1036 is positive, that is, the first DRB configuration information includes the DRB deletion list, and the DRB deletion list includes the DRBID. At this time, it may be determined that the type of the DRB configuration operation is a DRB addition operation. That is, when the DRB addition modification list is subsequently processed, a DRB addition procedure may be performed for the DRBID.

If the determination result in the step S1036 is negative, that is, the first DRB configuration information includes the DRB deletion list, and the DRB deletion list does not include the DRBID, it indicates that the RRC reconfiguration message of the network side does not indicate to delete the DRBID, but may only modify the relevant parameters of the DRBID. At this time, it may be determined that the type of the DRB configuration operation is a DRB modification operation. That is, when the DRB addition modification list is subsequently processed, a DRB modification procedure may be performed for the DRBID.

If the determination result of the step S1034 is negative, it indicates that the configuration on the network side results in two different EBIs for the same DRBID. However, if the RRC reconfiguration message further includes a DRB deletion list, and the DRB deletion list also includes the DRBID, the DRBID may still be understood and adopted by the UE according to the logic that the DRB deletion list is processed first and then the DRB addition modification list is processed as specified by the existing protocol. Therefore, a further determination is needed, such as determining whether the configuration is the same based on whether the DRB deletion list includes the DRBID.

Specifically, step S1037 may be executed to determine whether the first DRB configuration information includes the DRB deletion list.

If the determination result of the step S1037 is negative, it indicates that the DRB deletion list does not exist. If the addition operation is executed on the DRBID according to the DRB addition modification list, the same DRBID is caused to associate two EBIs, and further parameter conflict is generated. At this time, it may be determined that the authentication failed.

If the determination result of the step S1037 is positive, a step S1038 needs to be further performed to determine whether the DRB deletion list includes the DRBID.

If the determination result in the step S1038 is negative, that is, the DRB deletion list does not include the DRBID, it indicates that the RRC reconfiguration message of the network side does not indicate to delete the DRBID. Then, after the deletion operation is performed according to the DRB deletion list, and when the addition operation is performed on the DRBID according to the DRB addition modification list, since the DRBID currently configured by the UE is not deleted, the same DRBID is still associated with two EBIs, and thus parameter conflict is generated. At this time, it may be determined that the authentication failed.

If the determination result in the step S1038 is positive, that is, the DRB deletion list includes the DRBID, it indicates that the RRC reconfiguration message of the network side indicates to delete the related configuration of the UE for the DRBID currently. However, it is further required to determine whether the EBI configured to the DRBID at this time by the network side conflicts with the EBI associated with the DRBID currently configured by the UE. If so, determining whether to conflict with the configuration of the EBI associated with the DRBID in the EBI configuration information according to at least the second DRB configuration information, where whether to conflict is used to indicate whether the configurations are the same

Specifically, step S1039 may be executed to determine whether the EBI associated with the DRBID in the EBI configuration information is included in the second DRB configuration information.

If the determination result of the step S1039 is negative, that is, there is no case where one EBI associates two DRBID, it may be determined that there is no parameter conflict. Further, when the DRB addition modification list is subsequently processed, a DRB addition procedure may be performed for the DRBID.

If the determination result in the step S1039 is positive, that is, the EBI configured to the DRBID by the network this time is the same as a certain EBI currently configured by the UE, in other words, the EBI configured to the DRBID by the network this time is actually associated with another DRBID currently configured by the UE. But does not exclude the network side deleting the DRBID actually associated with the EBI currently configured by the UE through the DRB deletion list. Therefore, further determination is required from the DRB deletion list.

Specifically, step S1040 may be performed to determine whether the first DRB configuration information includes the DRB deletion list.

If the determination result in the step S1040 is negative, that is, the DRB deletion list does not exist, it indicates that the network side indicates that any DRBID deletion operation is instructed this time. When the addition operation is performed on the DRBID according to the DRB addition modification list, since the EBI of the DRBID association is already configured to another DRBID, one EBI will be caused to associate two DRBIDs, which is not allowed by the protocol. At this time, it may be determined that the authentication failed and there is a parameter conflict.

If the determination result in the step S1040 is positive, that is, the DRB deletion list exists. Step S1041 is further executed to determine whether the DRBID associated with the EBI in the second DRB configuration information is included in the DRB deletion list.

If the determination result in the step S1041 is positive, that is, for the EBI configured by the network side for the DRBID (denoted as the first DRBID), the DRBID (denoted as the second DRBID) associated with the EBI in the DRBs currently configured by the UE exists in the DRB deletion list. At this time, after deleting the second DRBID according to the DRB deletion list, and then adding the first DRBID according to the DRB addition modification list, since the second DRBID associated with the same EBI is already deleted, a situation that one EBI associates two DRBIDs does not occur, and parameter conflict does not occur. Further, when the DRBID addition modification list is subsequently processed, a DRBID addition process may be performed for the DRBID (i.e., the first DRBID).

If the determination result in the step S1041 is negative, that is, for the EBI configured by the network side for the DRBID (denoted as the first DRBID), the DRBID (denoted as the second DRBID) associated with the EBI in the DRB currently configured by the UE does not exist in the DRB deletion list. At this time, after the second DRBID is deleted according to the DRB deletion list, and when the addition of the first DRBID is performed according to the DRB addition modification list, since the second DRBID still exists, one EBI is caused to simultaneously associate two DRBIDs. At this time, it may be determined that the authentication failed and there is a parameter conflict.

If the determination result of the step S1033 is negative, it indicates that there is no EBI configuration for the DRBID in the EBI configuration information. However, at this time, it cannot be excluded that the network does not configure the corresponding EBI due to the modification operation for the DRBID configuration at this time, and therefore, a further determination is needed, for example, whether the configuration is the same according to whether the second list includes the DRBID. In the example shown in fig. 2, the second list is a DRB deletion list.

Specifically, step S1042 may be executed to determine whether the first DRB configuration information includes the DRB deletion list.

If the determination result in the step S1042 is negative, that is, the DRB deletion list does not exist, it indicates that the network side is a modification operation for the DRBID configuration this time. Thus, it can be determined that there is no parameter conflict. Further, when the DRB addition modification list is subsequently processed, a DRB modification procedure may be performed for the DRBID.

If the determination result of the step S1042 is positive, that is, the DRB deletion list exists. Step S1043 is further executed to determine whether the DRB deletion list includes the DRBID.

If the determination result in the step S1043 is positive, it indicates that the network side indicates to delete the current related configuration of the UE for the DRBID, but the RRC reconfiguration message does not have the EBI associated with the DRBID configuration. The UE cannot complete the DRBID addition operation according to the DRB addition modification list after deleting the DRBID according to the DRB deletion list, and there is a parameter conflict.

If the determination result in the step S1043 is negative, it indicates that the network side does not instruct to delete the DRBID. It may be determined that there is no parameter conflict, similarly to the processing when the determination result of the step S1042 is negative. Further, when the DRB addition modification list is subsequently processed, a DRB modification procedure may be performed for the DRBID.

If the determination result in the step S1032 is negative, that is, the DRBID does not belong to the DRB currently configured by the UE, it indicates that the network side configures a new DRBID for the UE. At this time, S1044 may be executed to determine whether the EBI configuration information includes the EBI associated with the DRBID.

If the determination result in the step S1044 is positive, that is, the EBI configuration for the DRBID exists in the EBI configuration information, indicating that the operation type of the network side for the DRBID is a DRB adding operation. At this time, although the DRBID does not conflict with the DRBID currently configured by the UE, it is not excluded that the EBI occupies the EBI associated with the DRBID currently configured by the UE. Therefore, the steps S1039 to S1041 need to be further performed to determine whether there is a parameter conflict.

When the determination result of the step S1044 is negative, that is, there is no EBI configuration for the DRBID in the EBI configuration information. Since it is determined that the DRBID does not belong to the second DRB configuration information at this time, it may be determined that the operation type of the network for the DRBID is a DRB addition operation. However, the network side does not configure the associated EBI for the DRBID to be added, so that the UE cannot complete the adding operation when performing the adding operation of the DRBID according to the DRB addition modification list. Thus, it can be determined that the authentication failed and there is a parameter conflict.

In one implementation, the above-mentioned determination process shown in fig. 2 may be performed for each DRBID in the DRB addition modification list. Further, when all DRBID in the DRB addition and modification list can go to the non-verification-failure end point through the determination process shown in fig. 2, it indicates that there is no parameter conflict, and the DRB deletion and addition/modification operations can be smoothly performed.

In other words, when any DRBID in the DRB addition/modification list goes to the "verification failure" end point through the determination process shown in fig. 2, it indicates that there is a parameter conflict, and the DRB addition/modification operation cannot be performed. At this time, the step S105 is executed to start the RRC reestablishment operation.

In one implementation, the step S104 may include the steps of: executing DRB deleting operation according to the DRB deleting list; and executing DRB adding or modifying operation according to the DRB adding and modifying list.

Thus, with the scheme of this embodiment, the UE adds the determination procedure before processing the DRB configuration information issued this time by the network side. Specifically, the DRB deletion list, the DRB addition modification list and the current DRB configuration condition of the UE sent by the network side at this time are integrated, and it is determined whether the addition or modification procedure for the DRBID in the RRC reconfiguration message received at this time can be continuously executed.

Fig. 3 is a schematic structural diagram of a device for processing an RRC reconfiguration message according to an embodiment of the present invention. Those skilled in the art understand that the processing device of the RRC reconfiguration message (hereinafter, referred to as the processing device 3) according to this embodiment may be used to implement the method technical solutions described in the embodiments shown in fig. 1 and fig. 2.

In particular, with reference to fig. 3, the processing means 3 may comprise: a first obtaining module 31, configured to obtain DRB configuration information included in the RRC reconfiguration message, and record the DRB configuration information as first DRB configuration information, where the first DRB configuration information includes at least one of a DRB deletion list and a DRB addition modification list; a second obtaining module 32, configured to obtain current DRB configuration information of the user equipment, which is recorded as second DRB configuration information; a determining module 33, configured to determine whether a parameter conflict exists when performing a DRB configuration operation according to the first DRB configuration information and the second DRB configuration information; and the processing module 34, when the judgment result indicates that no parameter conflict exists, executing DRB configuration operation according to the first DRB configuration information.

For more details of the operation principle and the operation mode of the processing device 3, reference may be made to the description in fig. 1 and fig. 2, which are not repeated herein.

Further, the embodiment of the present invention also discloses a storage medium, on which computer instructions are stored, and when the computer instructions are executed, the technical solution of the method described in the embodiments shown in fig. 1 and fig. 2 is executed. Preferably, the storage medium may include a computer-readable storage medium such as a non-volatile (non-volatile) memory or a non-transitory (non-transient) memory. The storage medium may include ROM, RAM, magnetic or optical disks, etc.

Further, an embodiment of the present invention further discloses a terminal, which includes a memory and a processor, where the memory stores computer instructions capable of being executed on the processor, and the processor executes the technical solution of the method in the embodiment shown in fig. 1 and fig. 2 when executing the computer instructions. Preferably, the terminal may be a mobile phone.

The technical scheme of the invention can be applied to a 4G (4Generation) communication system (namely an LTE communication system), can also be applied to a 5G communication system and a 3G communication system, and can also be applied to various future new communication systems, such as 6G communication systems and 7G communication systems.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for processing an RRC reconfiguration message, comprising:

acquiring DRB configuration information contained in the RRC reconfiguration message, and recording the DRB configuration information as first DRB configuration information, wherein the first DRB configuration information comprises at least one of a DRB deletion list and a DRB addition modification list;

acquiring current DRB configuration information of the user equipment, and recording the current DRB configuration information as second DRB configuration information;

judging whether parameter conflict exists when DRB configuration operation is executed according to the first DRB configuration information or not according to the first DRB configuration information and the second DRB configuration information;

and when the judgment result shows that no parameter conflict exists, performing DRB configuration operation according to the first DRB configuration information.

2. The processing method of claim 1, wherein the determining whether there is a parameter conflict when performing the DRB configuration operation according to the first DRB configuration information and the second DRB configuration information comprises:

for each DRBID in a first list, judging whether the configuration of the second DRB configuration information and the first DRB configuration information on the DRBID conflicts, wherein the first list is selected from the first DRB configuration information;

and when the judgment results of all DRBIDs in the first list are all non-confliction, determining that no parameter conflict exists.

3. The processing method of claim 2, wherein the determining whether the configuration of the DRBID by the second DRB configuration information and the first DRB configuration information conflicts comprises:

judging whether the second DRB configuration information contains the DRBID;

if the second DRB configuration information contains the DRBID, judging whether the configuration of the second DRB configuration information and the first DRB configuration information to the DRBID is the same;

and when the judgment result shows that the second DRB configuration information and the first DRB configuration information have the same configuration on the DRBID, determining that no conflict exists.

4. The processing method of claim 3, wherein the DRB addition modification list comprises EBI configuration information, and wherein the determining whether the configuration of the DRBID by the second DRB configuration information and the first DRB configuration information conflicts further comprises:

if the second DRB configuration information does not contain the DRBID, judging whether the EBI configuration information contains the EBI associated with the DRBID;

determining a conflict when the judgment result indicates that the EBI configuration information does not contain the EBI associated with the DRBID;

and when the judgment result shows that the EBI configuration information contains the EBI associated with the DRBID, judging whether the configuration of the EBI conflicts at least according to the second DRB configuration information.

5. The processing method of claim 3, wherein the DRB addition modification list includes EBI configuration information, and wherein the determining whether the DRBID configuration is the same as that of the second DRB configuration information and the first DRB configuration information comprises:

judging whether the EBI configuration information contains the EBI associated with the DRBID;

if the EBI configuration information contains the EBI associated with the DRBID, determining whether the configuration is the same at least according to the comparison result of the EBI associated with the DRBID in the EBI configuration information and the EBI associated with the DRBID in the second DRB configuration information;

if the EBI configuration information does not include an EBI associated with the DRBID, determining whether the configurations are the same according to whether a second list is included with the DRBID, wherein the second list is selected from the first DRB configuration information and is different from the first list.

6. The processing method according to claim 5, wherein said determining whether the configurations are the same according to whether the second list contains the DRBID comprises:

determining that the configuration is not the same when the second list contains the DRBID;

and when the second list does not contain the DRBID, or the first DRB configuration information does not contain the second list, determining that the configuration is the same.

7. The processing method of claim 5, wherein the determining whether the configurations are the same according to at least the comparison result between the EBI associated with the DRBID in the EBI configuration information and the EBI associated with the DRBID in the second DRB configuration information comprises:

when the EBI associated with the DRBID in the EBI configuration information is the same as the EBI associated with the DRBID in the second DRB configuration information, determining that the configuration is the same;

and when the EBI associated with the DRBID in the EBI configuration information is different from the EBI associated with the DRBID in the second DRB configuration information, determining whether the configuration is the same according to whether the DRBID is contained in the DRB deletion list or not.

8. The processing method according to claim 7, wherein said determining whether the configurations are the same according to whether the second list contains the DRBID comprises:

when the second list contains the DRBID, judging whether the configuration of the EBI conflicts at least according to the second DRB configuration information, wherein whether the configuration conflicts or not is used for indicating whether the configuration is the same;

and when the second list does not contain the DRBID, or the first DRB configuration information does not contain the second list, determining that the configurations are different.

9. The processing method according to claim 4 or 8, wherein the determining whether there is a conflict for the configuration of the EBI according to at least the second DRB configuration information comprises:

judging whether the EBI is contained in the second DRB configuration information;

if the EBI is included in the second DRB configuration information, determining whether a conflict exists according to whether the DRBID associated with the EBI in the second DRB configuration information is included in a second list, wherein the second list is selected from the first DRB configuration information, and the second list is different from the first list;

and if the EBI is not contained in the second DRB configuration information, determining that no conflict exists.

10. The processing method of claim 9, wherein the determining whether there is a conflict according to whether the DRBID of the EBI association in the second DRB configuration information is included in the second list comprises:

determining no conflict if the DRBID associated with the EBI in the second DRB configuration information is included in the second list;

and if the DRBID associated with the EBI in the second DRB configuration information does not contain the second list, or the first DRB configuration information does not contain the second list, determining a conflict.

11. The processing method of claim 7, wherein when the EBI associated with the DRBID in the EBI configuration information is the same as the EBI associated with the DRBID in the second DRB configuration information, further comprising:

and determining the type of DRB configuration operation according to whether the first DRB configuration information contains the second list and/or whether the second list contains the DRBID.

12. The processing method of claim 11, wherein the determining the type of DRB configuration operation according to whether the first DRB configuration information includes the second list comprises:

and when the first DRB configuration information does not contain the second list, determining the type of the DRB configuration operation as a DRB modification operation.

13. The processing method of claim 11, wherein the determining the type of DRB configuration operation according to whether the first DRB configuration information includes the second list and whether the second list includes the DRBID comprises:

when the first DRB configuration information comprises the second list and the second list comprises the DRBID, determining the type of the DRB configuration operation as a DRB adding operation;

when the first DRB configuration information contains the second list and the second list does not contain the DRBID, determining the type of the DRB configuration operation as a DRB modification operation.

14. The processing method of claim 5, wherein the first list is a modification list added to the DRB, and wherein the second list is a deletion list deleted from the DRB.

15. The processing method of claim 1, further comprising:

and when the judgment result shows that the parameter conflict exists, performing RRC reestablishment operation.

16. The processing method of claim 1, wherein the performing the DRB configuration operation according to the first DRB configuration information comprises:

executing DRB deleting operation according to the DRB deleting list;

and executing DRB adding or modifying operation according to the DRB adding and modifying list.

17. The processing method according to claim 1, wherein the step of determining whether there is a parameter conflict is performed when it is found that there is an abnormal configuration in the RRC reconfiguration message, where the abnormal configuration is that the DRB deletion list and the DRB addition modification list contain the same DRBID.

18. An apparatus for processing an RRC reconfiguration message, comprising:

a first obtaining module, configured to obtain DRB configuration information included in the RRC reconfiguration message, and record the DRB configuration information as first DRB configuration information, where the first DRB configuration information includes at least one of a DRB deletion list and a DRB addition modification list;

a second obtaining module, configured to obtain current DRB configuration information of the user equipment, and record the current DRB configuration information as second DRB configuration information;

a judging module, configured to judge whether a parameter conflict exists when performing a DRB configuration operation according to the first DRB configuration information and the second DRB configuration information;

and the processing module executes DRB configuration operation according to the first DRB configuration information when the judgment result shows that no parameter conflict exists.

19. A storage medium having stored thereon computer instructions, wherein said computer instructions when executed perform the steps of the method of any of claims 1 to 17.

20. A terminal comprising a memory and a processor, the memory having stored thereon computer instructions executable on the processor, wherein the processor, when executing the computer instructions, performs the steps of the method of any one of claims 1 to 17.