CN116321324B

CN116321324B - Communication method and related equipment

Info

Publication number: CN116321324B
Application number: CN202310470982.XA
Authority: CN
Inventors: 何彦召
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-04-27
Filing date: 2023-04-27
Publication date: 2023-10-13
Anticipated expiration: 2043-04-27
Also published as: CN116321324A

Abstract

The embodiment of the application provides a communication method and related equipment, relates to the technical field of wireless communication, and aims to solve the problem of how to recover normal communication when communication abnormality occurs. The communication method provided by the embodiment of the application is applied to the User Equipment (UE), and comprises the following steps: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability. And executing the following operations according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; or delete all CA combinations; or the current cell is set as a black cell and is switched to other cells. Therefore, before the CA capability is returned to the receiving of the SCC reconfiguration message, when the CA combination is abnormal or the resident cell is abnormal, the normal communication between the UE and the network equipment can be recovered in time, and the user experience can be improved.

Description

Communication method and related equipment

Technical Field

The embodiment of the application relates to the technical field of wireless communication, in particular to a communication method and related equipment.

Background

Carrier aggregation (Carrier aggregation, CA) refers to a User Equipment (UE) simultaneously using spectrum resources of multiple serving cells for data transmission. In the early stage of CA deployment, abnormal communication related to CA is caused due to various links such as interaction of signaling or data between UE and network equipment, parameter configuration in the network equipment, interaction of signaling or data between an access network and a core network and the like, so that normal communication between the UE and the network equipment is influenced.

Disclosure of Invention

The embodiment of the application provides a communication method and related equipment, which aim to solve the problem of how to restore normal communication when communication abnormality occurs.

A first aspect of an embodiment of the present application provides a communication method, applied to a user equipment UE, where the method includes: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability. And executing the following operations according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; or delete all CA combinations; or the current cell is set as a black cell and is switched to other cells.

By adopting the communication method of the embodiment, the UE responds to the successful registration and the reported CA capability, and detects the abnormal communication type after receiving the SCC reconfiguration message. Any one of the following operations is performed according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; deleting all CA combinations; and setting the current cell as a black cell and switching to other cells. Therefore, before the CA capability is returned to the receiving of the SCC reconfiguration message, when the CA combination is abnormal or the resident cell is abnormal, the normal communication between the UE and the network equipment can be recovered in time, and the user experience can be improved.

In one embodiment, detecting a communication anomaly type includes: in response to receiving the delete SCC reconfiguration message during operation of the first timer T1, counting a number of times the delete SCC reconfiguration message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. Wherein, T1 and T2 are synchronously started, and the operation time of T1 is smaller than the operation time of T2.

With the communication method of this embodiment, the UE starts T1 and T2 after receiving the SCC reconfiguration added message. When the UE receives the delete SCC reconfiguration message during T1 operation and continuously receives the add SCC reconfiguration message and the delete SCC reconfiguration message during T2 operation, it may be confirmed that the communication anomaly type is SCC continuous addition release.

In another embodiment, detecting a communication anomaly type includes: in response to receiving the radio resource configuration RRC release message during operation of the first timer T1, counting the number of times the RRC release message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. The method comprises the steps that T1 and T2 are synchronously started, the operation duration of T1 is smaller than the operation duration of T2, and the operation duration of T1 is smaller than the operation duration of a counted UE inactivity timer.

With the communication method of this embodiment, the UE starts T1 and T2 after receiving the SCC reconfiguration added message. When the UE receives the RRC release message during T1 operation, it may confirm that communication abnormality occurs. When the UE continuously receives the addition SCC reconfiguration message and the RRC release message during T2 operation, it may be confirmed that the communication abnormality type is continuous RRC connection establishment failure.

In another embodiment, after setting the current cell as a black cell and switching to another cell, the method further includes: and in response to the duration of camping on the new cell exceeding the preset duration or switching from the flight mode to the communication mode, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

By adopting the communication method of the embodiment, the UE responds to the fact that the duration of the resident new cell exceeds the preset duration or is switched from the flight mode to the communication mode, and sends a UE registration request message to the network equipment, so that a UE registration flow is initiated. The network device may configure the serving cell of the UE as a new cell, thereby facilitating resumption of normal communication between the UE and the network device and avoiding ping-pong effects.

In another embodiment, deleting all CA combinations associated with the SCC, or deleting all CA combinations, includes: and initiating a Mobility Registration Update (MRU) process, wherein the MRU process is used for updating CA capability. When reporting CA capabilities, all CA combinations associated with the SCC are deleted, or all CA combinations are deleted.

By adopting the communication method of the embodiment, after the UE initiates the MRU procedure, the network device may send a UE capability query message to the UE. The UE reports UE capabilities including CA capabilities in response to the UE capability query message. When the CA capabilities are reported, all CA combinations or all CA combinations associated with the SCC that the CA capabilities contain are deleted, thereby updating the CA capabilities. And reporting the updated CA capability to the network equipment, so that the CA capability can be retracted before the SCC reconfiguration message is received, and the normal communication between the UE and the network equipment can be recovered.

A second aspect of an embodiment of the present application provides a communication method, applied to a user equipment UE, where the method includes: and responding to the reported carrier aggregation CA capability, and receiving a UE registration failure message, and acquiring a reason value from the UE registration failure message. And confirming the communication abnormality type according to the cause value. And deleting all CA combinations according to the communication anomaly type, and initiating a UE registration flow.

By adopting the communication method of the embodiment, when the communication anomaly type is continuous registration failure, the UE deletes all CA combinations and initiates the UE registration flow, so that when the continuous registration failure is related to CA, the success of the UE registration is guaranteed by updating CA capacity, and normal communication between the UE and the network equipment is recovered.

In one embodiment, confirming the communication abnormality type according to the cause value includes: traversing a preset reason value set according to the reason value. And confirming the communication abnormality type in response to the cause value being any one of the preset cause value sets.

By adopting the communication method of the embodiment, after the UE obtains the cause value, the UE traverses the preset cause value set according to the cause value. When the cause value is any one of the preset cause value sets, it can be confirmed that the communication abnormality type is continuous registration failure.

In another embodiment, deleting all CA combinations according to the communication anomaly type and initiating a UE registration procedure, including: timing begins with the deletion of all CA combinations. And in response to the counted time period being longer than the running time period of the third timer T31 and switching to other cells, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

By adopting the communication method of the embodiment, when deleting all CA combinations, the UE starts T31 and starts timing. When the time duration is longer than the operation time duration of the T31 and the current resident cell of the UE is inconsistent with the resident cell before all CA combinations are deleted, the UE sends a UE registration request message to the network equipment, and therefore a UE registration flow is initiated. The UE registration process is restarted by setting a certain waiting time delay, so that the situation that the UE registration fails due to short network signal failure is avoided, and normal communication between the UE and the network equipment is recovered.

A third aspect of the embodiment of the present application provides a communication method, applied to a user equipment UE, where the method includes: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability. And deleting all CA combinations related to the SCC according to the detected communication abnormality type. In response to the updated CA capabilities, after receiving the SCC reconfiguration message, a communication anomaly type is detected. And deleting all CA combinations according to the detected communication abnormality type. In response to the updated CA capabilities, after receiving the SCC reconfiguration message, a communication anomaly type is detected. And setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells.

By adopting the communication method of the embodiment, the UE deletes all CA combinations related to the SCC according to the detected communication abnormality type, so that when the communication abnormality type is related to the SCC, the CA capability can be retracted before the SCC reconfiguration message is received, and normal communication between the UE and the network equipment can be recovered. After deleting all CA combinations related to the SCC, if the communication abnormality is detected again, the UE deletes all CA combinations according to the detected communication abnormality type, so that when the communication abnormality type is related to the PCC (and the SCC), the CA capability can be returned to the time before the SCC reconfiguration message is received, and normal communication between the UE and the network equipment is recovered. After deleting all CA combinations, if the UE detects communication abnormality again, setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells, so that when the communication abnormality type is related to a resident cell, the CA capability can be returned to before the SCC reconfiguration message is received, and normal communication between the UE and the network equipment can be recovered.

A fourth aspect of the present application provides a communication device, applied to a user equipment UE, where the communication device includes an anomaly identification module, a capability adjustment module, and a capability recovery module. Wherein, the unusual identification module is used for: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability. The capacity adjustment module is used for: the following operations are performed according to the detected communication anomaly type: deleting all CA combinations associated with the SCC; or delete all CA combinations; or the current cell is set as a black cell and is switched to other cells. The capability recovery module is used for: after the corresponding operation is performed according to the detected communication abnormality type, the CA capability is re-reported or registration is re-initiated.

The communication device provided by the embodiment of the application can be used for executing the technical scheme about the UE in the communication method embodiment of the application.

A fifth aspect of the present application provides a baseband processor, where the baseband processor is configured to perform the technical solution related to the UE in the foregoing communication method embodiment of the present application.

A sixth aspect of the present application provides a baseband chip, including: the processor is configured to execute the technical scheme related to the UE in the foregoing communication method embodiment of the present application.

A seventh aspect of the present application provides a user equipment, comprising: the baseband processor provided in the above embodiment, or the baseband chip provided in the above embodiment.

An eighth aspect of the present application provides a computer readable storage medium storing a computer program or code, which when executed by a processor, implements the technical solution of the above-mentioned communication method embodiment of the present application regarding a user equipment UE.

Drawings

Fig. 1 is a schematic diagram of an exemplary radio communication network architecture.

Fig. 2 is a schematic diagram illustrating interaction between UE registration and UE capability reporting provided by an example.

Fig. 3 is an interactive schematic diagram of RRC connection release provided by an example.

Fig. 4 is a flow chart of a communication method provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of a communication anomaly type provided by an example.

Fig. 6 is a schematic diagram of a communication anomaly type provided by another example.

Fig. 7 is an interactive schematic diagram of a communication method according to an embodiment of the present application.

Fig. 8 is a flow chart of a communication method according to another embodiment of the present application.

Fig. 9 is an interactive schematic diagram of a communication method according to another embodiment of the present application.

Fig. 10 is a flow chart of a communication method according to another embodiment of the present application.

Fig. 11 is an interactive schematic diagram of a communication method according to another embodiment of the present application.

Fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Fig. 13 is a schematic structural diagram of a user equipment according to an embodiment of the present application.

Detailed Description

It should be noted that, in the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and the representation may have three relationships, for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

It should be further noted that, in the method disclosed in the embodiment of the present application or the method shown in the flowchart, one or more steps for implementing the method are included, and the execution order of the steps may be interchanged with each other, where some steps may be deleted without departing from the scope of the claims.

The radio communication network architecture and some technical terms involved in the embodiments of the present application are explained below.

A Radio communication network architecture (e.g., a long term evolution (Long Term Evolution, LTE) system, an LTE-Advanced (LTE-a) system, an LTE-Advanced (Pro) system, or a 5G New Radio, NR) Radio access network (Radio Access Network, RAN)) generally includes at least one network device, at least one User Equipment (UE), and one or more optional network elements that provide connectivity to a Network (NW). The UE communicates with a Network (e.g., core Network (CN), evolved packet Core (Evolved Packet Core, EPC) Network, evolved universal terrestrial radio access Network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN), 5G Core (5G Core,5 gc), or the internet) through a RAN established by one or more Network devices.

For example, as shown in fig. 1, the radio communication network architecture 10 includes a user equipment 100 and a network device 200. For the user equipment 100 configured with carrier aggregation (Carrier aggregation, CA), the user equipment 100 communicates with the network equipment 200 through CA combination. The CA combination includes multiple component carriers (Component Carrier, CC), e.g., one primary component carrier (Primary Component Carrier, PCC) and multiple secondary component carriers (SecondaryComponent Carrier, SCC). PCC is used for communication of Primary Cell (PCell), and SCC is used for communication of Secondary Cell (SCell). The network device 200 may configure a plurality of cells, such as one primary cell and a plurality of secondary cells. The user equipment 100 is connected to AN Access Network (AN) through a Network equipment 200, and is further connected to a CN through the Access Network.

A network device refers to a device deployed in the RAN to provide a wireless communication function for a UE, such as a Base Station (BS) or a transmission reception point (Transmission Reception Point, TRP). Wherein the BS may be configured to provide communication services according to at least one of the following radio access technologies (Radio Access Technology, RAT): global microwave access interoperability (Worldwide Interoperability for Microwave Access, wiMAX), global system for mobile communications (Global System for Mobile communications, GSM, commonly referred to as 2G), GSM enhanced data rates for GSM evolution (Enhanced Data rates for GSM Evolution, EDGE) radio access network (GSM EDGE Radio Access Network, GERAN), general packet radio services (General Packet Radio Service, GPRS), wideband code division multiple access (Wideband-Code Division Multiple Access, W-CDMA), high speed packet access (High-Speed Packet Access, HSPA), LTE-A, eLTE (evolved LTE, e.g. LTE connected to 5 GC), NR (commonly referred to as 5G) and/or LTE-a Pro (Universal Mobile Telecommunication System, UMTS, commonly referred to as 3G). It will be appreciated that the scope of embodiments of the present application should not be limited to the above protocols.

The network devices may include, but are not limited to, node BS (Node BS, NB) in UMTS, evolved Node BS (enbs) in LTE or LTE-a, radio network controllers (Radio Network Controller, RNC) in UMTS, base station controllers (Base Station Controller, BSC) in GERAN, next generation enbs (next-generation enbs, ng-enbs) in Evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) BS connected to 5GC, next generation Node BS (next-generation Node B, gNB) in 5G access network (5G Access Network,5G-AN), and any other device capable of controlling radio communications and managing radio resources within a cell. The network device may serve one or more UEs through a radio interface connected to the NW.

The network device may be operable to provide radio coverage to a particular geographic area using a plurality of cells included in the RAN. The network device may support operation of the cell. Each cell (commonly referred to as a serving cell) may be used to provide service to at least one UE within its radio coverage area. For example, each cell schedules Downlink (DL) and optional Uplink (UL) resources to at least one UE within its radio coverage for DL and optional UL packet transmission.

The UE may include, but is not limited to, a mobile station, a mobile terminal or device, a user communication radio terminal. For example, the UE may be a portable radio that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a vehicle, or a personal digital assistant (Personal Digital Assistant, PDA) with wireless communication capability. The UE is configured to receive signals over an air interface and to transmit signals to one or more cells in the RAN.

The UE may move within the coverage of a serving RAN (comprised of one or more cells). Each cell may be configured and supported by a network device. As the UE moves within the radio coverage of the RAN, the UE may perform a cell reselection procedure to select one of the serving cells to camp on, also referred to as camping on. In addition, the UE may keep receiving system information (System Information, SI) broadcast by the same serving cell to monitor the operating state of the serving cell.

For a UE configured with CA, the term "serving Cell" is used to denote the set of cells consisting of a Special Cell (SpCell) and all scells. The term "special cell" refers to the PCell of the primary cell group (Master Cell Group, MCG) or the primary secondary cell (PrimarySecondary Cell, PSCell) of the secondary cell group (Secondary Cell Group, SCG). The network equipment selects a cell with signal quality meeting a specific condition based on the measurement report result of the UE on the adjacent cells, and configures the cell as a service cell of the UE.

The CA is configured by the network device. The network equipment configures CA for the UE according to the CA Capability (CA Capability) reported by the UE so as to facilitate communication between the network equipment and the UE. Each UE may have different CA capabilities. CA Capability includes all CA combinations.

In the early stage of CA deployment, abnormal communication related to CA is caused due to various links such as interaction of signaling or data between UE and network equipment, parameter configuration in the network equipment, interaction of signaling or data between AN and CN and the like, so that normal communication between the UE and the network equipment is influenced.

For example, as shown in fig. 2, when the user equipment 100 moves into the radio coverage of the network equipment 200, the user equipment 100 transmits a UE registration request message to the network equipment 200 (see step S201), the UE registration request message being used to request registration to the network equipment 200. The network device 200 initiates a UE registration procedure in response to the UE registration request message (see step S202). The UE registration procedure includes, for example, an attach, a data service, or a location information update, etc. service procedure to facilitate access to the network. After initiating the UE registration procedure, the network device 200 transmits a UE capability query message to the user device 100 (see step S203), where the UE capability query message is used to query the UE capabilities supported by the user device 100. Illustratively, the UE capabilities include CA capabilities. The user equipment 100 reports the UE capability to the network equipment 200 in response to the UE capability query message (see step S204). The network device 200 transmits a UE registration response message to the user device 100 (see step S205), the UE registration response message indicating a UE registration result including a UE registration success or a UE registration failure. The UE registration response message includes a UE registration success message or a UE registration failure message, for example. After the user equipment 100 reports the CA capability, the network equipment 200 allocates CA resources to the user equipment 100 according to the CA capability reported by the user equipment 100, so that the user equipment 100 can communicate with the network equipment 200 through the CA combination.

In the above interaction process, when an abnormality occurs in signaling or data transmission between the user equipment 100 and the network equipment 200 or an abnormality occurs in parameter configuration in the network equipment 200, the network equipment 200 may not normally allocate CA resources to the user equipment 100, thereby affecting normal communication between the user equipment 100 and the network equipment 200.

As another example, as shown in fig. 3, when the network device 200 does not require the user device 100 to maintain a radio resource control (Radio Resource Control, RRC) connected state, the network device 200 transmits an RRC release message (see step S301) to the user device 100, the RRC release message being for instructing the user device 100 to switch to an RRC idle (rrc_idle) state or an RRC inactive (rrc_inactive) state.

It will be appreciated that when the UE is in the RRC connected state, the UE has established an RRC connection with the network device, and signaling or data can be transferred between the UE and the network device. When the UE is in the rrc_idle state or the rrc_inactive state, the UE and the network device do not establish an RRC connection, and signaling or data cannot be transmitted between the UE and the network device.

In the above interaction process, when the ue 100 receives the RRC release message, the ue 100 switches to the rrc_idle state or the rrc_inactive state, and no signaling or data can be continuously transmitted between the ue 100 and the network device 200, thereby affecting normal communication between the ue 100 and the network device 200.

The embodiment of the application provides a communication method and related equipment, which are used for responding to a received UE registration success message and reporting the carrier aggregation CA capability, and detecting the abnormal communication type after receiving an SCC reconfiguration message added with an auxiliary component carrier. Any one of the following operations is performed according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; deleting all CA combinations; and setting the current cell as a black cell and switching to other cells. Therefore, before the CA capability is returned to the receiving of the SCC reconfiguration message, when the CA combination or the resident cell is abnormal, the normal communication between the UE and the network equipment can be recovered in time, and the user experience can be improved.

It can be appreciated that the communication method according to the embodiment of the present application may be applied to a UE, and may also be applied to a communication apparatus in the UE. By way of example, the communication device may be a baseband processor, baseband chip or modem (modem), etc., and embodiments of the application are not limited in this regard.

The following describes the technical scheme of the embodiment of the present application in detail by using specific embodiments. The embodiments may be combined with each other and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 4 is a flow chart of a communication method provided by an embodiment of the present application. The main body of the communication method of the present embodiment is exemplified by UE. As shown in fig. 4, the communication method includes the steps of:

s401, in response to receiving the UE registration success message and reporting the carrier aggregation CA capability, detecting the communication anomaly type after receiving the SCC reconfiguration message added with the auxiliary component carrier.

Wherein the addition of the SCC reconfiguration message is used to instruct the UE to add the SCC related CA combination.

In this embodiment, the UE may initiate a UE registration procedure and report CA capability through steps S201 to S205 shown in fig. 2. After the UE is successfully registered and CA capabilities have been reported, the network device allocates CA resources to the UE to facilitate the UE to communicate with the network device through the CA combination. After receiving the SCC reconfiguration message adding the secondary component carrier, the UE detects the communication anomaly type. The communication anomaly type may include, but is not limited to, SCC continuous addition release, continuous RRC connection establishment failure, continuous registration failure.

In one embodiment, detecting the communication anomaly type may include: in response to receiving the delete SCC reconfiguration message during operation of the first timer T1, counting a number of times the delete SCC reconfiguration message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. Wherein, T1 and T2 are synchronously started, and the operation time of T1 is smaller than the operation time of T2.

In the above embodiment, the delete SCC reconfiguration message is used to instruct the UE to delete the SCC related CA combination.

It can be understood that T1 and T2 are timers on the UE side. T1 and T2 may be run periodically, with one run period of T2 comprising at least one run length of T1. The operation time periods of T1 and T2 may be set as desired, for example, the operation time period of T1 may be set to 2 seconds(s) or 3 s, and the operation time period of T2 may be set to 10 s or 15 s.

After receiving the SCC added reconfiguration message, the UE starts T1 and T2. When the UE receives the delete SCC reconfiguration message during T1 operation and continuously receives the add SCC reconfiguration message and the delete SCC reconfiguration message during T2 operation, it may be confirmed that the communication anomaly type is SCC continuous addition release.

The determination manner of continuously receiving the addition SCC reconfiguration message and the deletion SCC reconfiguration message may include: the number of times the SCC reconfiguration message is deleted is counted, or the number of times the SCC reconfiguration message is added is counted, or the number of times a set of messages (including the SCC reconfiguration message is added and the SCC reconfiguration message is deleted) is counted. When the number of times is greater than the number of times threshold, it may be determined that the SCC reconfiguration message is added and the SCC reconfiguration message is deleted are continuously received.

It will be appreciated that the number of times threshold may be set as desired, for example, the number of times threshold may be set to 2, 3 or 4.

For example, as shown in fig. 5, in a scenario where the communication anomaly type is SCC continuous addition release, the UE starts T1 and T2 after receiving the addition SCC reconfiguration message (see step S501). During at least one T1 operation, the UE receives at least one delete SCC reconfiguration message. During one T2 run, the UE counts the number of times the SCC reconfiguration message is deleted received (see step S502).

In another embodiment, detecting the communication anomaly type may include: in response to receiving the radio resource configuration RRC release message during operation of the first timer T1, counting the number of times the RRC release message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. The method comprises the steps that T1 and T2 are synchronously started, the operation duration of T1 is smaller than the operation duration of T2, and the operation duration of T1 is smaller than the operation duration of a counted UE inactivity timer.

It is understood that the UE inactivity timer is a timer on the network device side. The UE inactivity timer is used by the network device to detect whether the UE is transmitting data. When the duration of the data transmission of the UE is longer than the running duration of the UE inactivity timer, the network equipment sends an RRC release message to the UE, so that the RRC connection is released. When the duration of the UE not transmitting data is less than or equal to the running duration of the UE inactivity timer, the network device maintains the RRC connection of the UE. The UE inactivity timer may run for 10 s or 20 s. For the UE, since the running duration of the UE inactivity timer is unknown, it is necessary to count the running duration of the UE inactivity timer according to the duration of the untransmitted data.

In the above embodiment, the UE starts T1 and T2 after receiving the SCC reconfiguration message. When the UE receives the RRC release message during T1 operation, it may confirm that communication abnormality occurs. When the UE continuously receives the SCC reconfiguration message and the RRC release message added during T2 operation, it may be confirmed that the communication abnormality type is continuous RRC connection establishment failure.

The determination manner of continuously receiving the added SCC reconfiguration message and the RRC release message may include: the number of times an RRC release message is received is counted, or the number of times an SCC reconfiguration message is added is counted, or the number of times a set of messages (including the SCC reconfiguration message and the RRC release message) is received is counted. When the number of times is greater than the number of times threshold, it may be determined that the SCC reconfiguration message and the RRC release message are added are continuously received.

For example, as shown in fig. 6, in a scenario where the communication anomaly type is a continuous RRC connection establishment failure, the UE starts T1 and T2 after receiving the SCC reconfiguration message added (see step S601). During at least one T1 operation, the UE receives at least one RRC release message. During one T2 operation, the UE counts the number of times of received RRC release messages (see step S602).

S402, executing the following operations according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; or delete all CA combinations; or the current cell is set as a black cell and is switched to other cells.

The black cell refers to a cell in which abnormal communication with the UE occurs. The UE is not allowed to handover or reselect to a black cell. The other cell may be any cell other than the black cell.

In this embodiment, when the communication anomaly type is related to the SCC, the UE can fall back the CA capability until the SCC reconfiguration message is received by performing any of the above operations, thereby facilitating recovery of normal communication between the UE and the network device. When the communication anomaly type is related to the PCC (and the SCC), since the communication cannot be restored by deleting all CA combinations related to the SCC, the UE can return the CA capability until the SCC reconfiguration message is received by deleting all CA combinations or setting the current cell as a black cell and switching to other cells, thereby facilitating restoration of normal communication between the UE and the network device. When the communication anomaly type is related to the resident cell, since all CA combinations related to the SCC are deleted or all CA combinations are deleted, the UE can return the CA capability until the SCC reconfiguration message is received by setting the current cell as a black cell and switching to other cells, thereby facilitating restoration of normal communication between the UE and the network device.

In one embodiment, deleting all CA combinations associated with the SCC, or deleting all CA combinations, includes: and initiating a Mobility Registration Update (MRU) process, wherein the MRU process is used for updating CA capability. When reporting CA capabilities, all CA combinations associated with the SCC are deleted, or all CA combinations are deleted.

In the above embodiment, after the UE initiates the MRU procedure, the network device may send a UE capability query message to the UE. The UE reports UE capabilities including CA capabilities in response to the UE capability query message. When the CA capabilities are reported, all CA combinations or all CA combinations associated with the SCC that the CA capabilities contain are deleted, thereby updating the CA capabilities. And reporting the updated CA capability to the network equipment, so that the CA capability can be retracted before the SCC reconfiguration message is received, and the normal communication between the UE and the network equipment can be recovered.

In another embodiment, after setting the current cell as a black cell and switching to another cell, the communication method further includes: and in response to the duration of camping on the new cell exceeding the preset duration or switching from the flight mode to the communication mode, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

The flight mode refers to a mode in which the UE prohibits communication. The communication mode refers to a mode in which the UE allows communication.

The UE may camp on a new cell after switching to another cell. If the UE camps on the new cell for a short period of time, a ping-pong effect (also referred to as ping-pong handover) may occur. The ping-pong effect refers to the UE switching back and forth between two cells. Thus, it is advantageous to avoid ping-pong effects by increasing the duration of the UE camping on a new cell, or switching the UE to the flight mode.

In the above embodiment, the UE sends the UE registration request message to the network device in response to the duration of camping on the new cell exceeding the preset duration, or switching from the flight mode to the communication mode, thereby initiating the UE registration procedure. The network device may configure the serving cell of the UE as a new cell, thereby facilitating resumption of normal communication between the UE and the network device and avoiding ping-pong effects.

It is understood that the preset time period may be set as desired, for example, the preset time period may be set to 2 minutes (min) or 3 min.

Fig. 7 is an interactive schematic diagram of a communication method according to an embodiment of the present application. Based on the above embodiments, the communication method of this embodiment takes interaction between the UE and the network device as an example. As shown in fig. 7, the communication method includes the steps of:

S701, the UE sends a UE registration request message to the network device.

S702, the network equipment responds to the UE registration request message and initiates a UE registration flow.

S703, the network device sends a UE capability query message to the UE.

And S704, the UE responds to the UE capability query message and reports the UE capability to the network equipment, wherein the UE capability comprises CA capability.

S705, the network device sends a UE registration success message to the UE.

S706, the network device sends an add SCC reconfiguration message to the UE.

S707, the UE adds a SCC related CA combination in response to adding the SCC reconfiguration message.

S708, the network device sends a delete SCC reconfiguration message (or RRC release message) to the UE.

S709, the UE counts the number of times the SCC reconfiguration message (or RRC release message) was received during T2 operation in response to the registration success and the CA capability has been reported, and the SCC reconfiguration message (or RRC release message) was received during T1 operation.

S710, the UE confirms that the communication anomaly type is SCC continuous addition release (or continuous RRC connection establishment failure) in response to the number of times being greater than the number of times threshold.

S711, the UE performs any one of the following operations according to the detected communication anomaly type: deleting all CA combinations associated with the SCC; deleting all CA combinations; and setting the current cell as a black cell and switching to other cells.

In this embodiment, the UE performs any of the operations described above according to the detected type of communication anomaly, so that the CA capability can be rolled back until the SCC reconfiguration message is received, thereby facilitating recovery of normal communication between the UE and the network device, and facilitating enhancement of user experience.

Fig. 8 is a flow chart of a communication method according to another embodiment of the present application. On the basis of the above-described embodiments, the communication method of the present embodiment takes a scenario in which the communication anomaly type is continuous registration failure as an example. As shown in fig. 8, the communication method includes the steps of:

s801, responding to the reported carrier aggregation CA capability, and receiving a UE registration failure message, and acquiring a reason value from the UE registration failure message.

Wherein the UE registration failure message includes a cause value. The cause value is used to indicate the cause of the UE registration failure.

In this embodiment, the UE may initiate a UE registration procedure and report CA capability through steps S201 to S205 shown in fig. 2. After the CA capability has been reported and the UE registration has failed, the UE obtains a cause value from the received UE registration failure message, thereby confirming the cause of the UE registration failure.

S802, confirming the communication abnormality type according to the cause value.

In this embodiment, the UE may confirm the cause of the UE registration failure by the cause value. When the cause of the UE registration failure is ambiguous, the communication anomaly type may be confirmed as continuous registration failure.

The cause ambiguity refers to an ambiguity of a link causing the registration failure of the UE. Causes of ambiguity may include, but are not limited to, implicit de-registration (explicit de-registration), no suitable cells in the tracking area (No suitable cells in tracking area), or no forwarding of the payload (Payload was not forwarded).

In one embodiment, confirming the communication anomaly type according to the cause value includes: traversing a preset reason value set according to the reason value. And confirming the communication abnormality type in response to the cause value being any one of the preset cause value sets.

In the above embodiment, the preset cause value set may include a cause value corresponding to at least one ambiguous cause.

For example, the set of cause values may be set to {0x0A,0x0F,0x5A,0x5F,0x60,0x61,0x62,0x63,0x64,0x65,0x6F }. The reason corresponding to the reason value 0x0A is implicit de-registration. The reason for the reason value of 0x0F is that there is no suitable cell in the tracking area. The reason for the reason value 0x5A is that the payload is not forwarded. The reason corresponding to the reason value 0x5F is a message (Semantically incorrect message) with incorrect semantics. The reason corresponding to the cause value 0x60 is invalid mandatory information (Invalid mandatory information). The reason for the reason value 0x61 is that the Message type does not exist or is not implemented (Message type non-existent or not implemented). The reason for the reason value 0x62 is that the message type is not compatible with the protocol state (Message type not compatible with the protocol state). The reason for the reason value 0x63 is that the information element is not present or implemented (Information element non-existent or not implemented). The cause corresponding to the cause value 0x64 is a conditional information element (Information Element, IE) error (Conditional IE error). The reason for the reason value 0x65 is that the message is not compatible with the protocol state (Message not compatible with the protocol state). The reason for the reason value 0x6F is a Protocol error, which is not described (unshared).

After the UE acquires the reason value, traversing the preset reason value set according to the reason value. When the cause value is any one of the preset cause value sets, it can be confirmed that the communication abnormality type is continuous registration failure.

S803, deleting all CA combinations according to the communication anomaly type, and initiating a UE registration flow.

In this embodiment, when the communication anomaly type is continuous registration failure, the UE deletes all CA combinations and initiates a UE registration procedure, so that when the continuous registration failure is related to CA, the success of the registration of the UE is guaranteed by updating CA capability, thereby facilitating recovery of normal communication between the UE and the network device.

In one embodiment, deleting all CA combinations according to the communication anomaly type and initiating a UE registration procedure, including: timing begins with the deletion of all CA combinations. And in response to the counted time period being longer than the running time period of the third timer T31 and switching to other cells, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

Wherein T31 is a timer at the UE side. The operation duration of T31 may be set as desired, for example, the operation duration of T31 may be set to 24 hours (h) or 30 h.

In the above embodiment, the UE starts T31 when deleting all CA combinations and starts timing. When the time duration is longer than the operation time duration of the T31 and the current resident cell of the UE is inconsistent with the resident cell before all CA combinations are deleted, the UE sends a UE registration request message to the network equipment, and therefore a UE registration flow is initiated. The UE registration process is restarted by setting a certain waiting time delay, so that the situation that the UE registration fails due to short network signal failure is avoided, and normal communication between the UE and the network equipment is recovered.

Fig. 9 is an interactive schematic diagram of a communication method according to another embodiment of the present application. Based on the above embodiments, the communication method of this embodiment takes interaction between the UE and the network device as an example. As shown in fig. 9, the communication method includes the steps of:

s901, the UE sends a UE registration request message to the network device.

S902, the network device initiates a UE registration procedure in response to the UE registration request message.

S903, the network device sends a UE capability query message to the UE.

S904, the UE reports UE capabilities, including CA capabilities, to the network device in response to the UE capability query message.

S905, the network device transmits a UE registration failure message to the UE.

S906, the UE responds to the reported CA capability and the registration fails, and the reason value is obtained from the received UE registration failure message.

S907, the UE traverses the preset reason value set according to the reason value.

S908, the UE confirms that the communication anomaly type is a continuous registration failure in response to the cause value being any one of the preset cause value sets.

S909, the UE deletes all CA combinations according to the communication anomaly type.

S910, the UE starts T31 when deleting all CA combinations and starts timing.

And S911, the UE responds to the timing time longer than the operation time of the T31 and is switched to other cells, and sends a UE registration request message to the network equipment.

In this embodiment, in a scenario where the communication anomaly type is continuous registration failure, the UE deletes all CA combinations according to the communication anomaly type and initiates a UE registration procedure, so that when the communication anomaly type is related to CA, the CA capability is updated to be beneficial to ensuring that the UE registration is successful, thereby recovering normal communication between the UE and the network device. In addition, the UE registration process is restarted by setting a certain waiting time delay, so that the situation that the UE registration fails due to short network signal failure is avoided, and normal communication between the UE and the network equipment is recovered.

Fig. 10 is a flow chart of a communication method according to another embodiment of the present application. On the basis of the above-described embodiments, the communication method of the present embodiment takes as an example that the UE successively performs a plurality of operations according to the detected communication abnormality type. As shown in fig. 10, the communication method includes the steps of:

s1001, in response to receiving the UE registration success message and having reported the carrier aggregation CA capability, detecting a communication anomaly type after receiving the SCC reconfiguration message with the secondary component carrier added.

S1002, deleting all CA combinations related to the SCC according to the detected communication abnormality type.

S1003, in response to the updated CA capability, after receiving the SCC reconfiguration message, detects a communication abnormality type.

And S1004, deleting all CA combinations according to the detected communication abnormality type.

S1005, in response to the updated CA capability, after receiving the SCC reconfiguration message, detects a communication abnormality type.

S1006, setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells.

In this embodiment, the UE deletes all CA combinations related to the SCC according to the detected communication anomaly type, so that when the communication anomaly type is related to the SCC, CA capability can be rolled back before the SCC reconfiguration message is received, thereby facilitating recovery of normal communication between the UE and the network device. After deleting all CA combinations related to the SCC, if the communication abnormality is detected again, the UE deletes all CA combinations according to the detected communication abnormality type, so that when the communication abnormality type is related to the PCC (and the SCC), the CA capability can be returned to the time before the SCC reconfiguration message is received, and normal communication between the UE and the network equipment is recovered. After deleting all CA combinations, if the UE detects communication abnormality again, setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells, so that when the communication abnormality type is related to a resident cell, the CA capability can be returned to before the SCC reconfiguration message is received, and normal communication between the UE and the network equipment can be recovered.

Fig. 11 is an interactive schematic diagram of a communication method according to another embodiment of the present application. Based on the above embodiments, the communication method of this embodiment takes interaction between the UE and the network device as an example. As shown in fig. 11, the communication method includes the steps of:

s1101, the UE sends a UE registration request message to the network device.

S1102, the network device initiates a UE registration procedure in response to the UE registration request message.

S1103, the network device sends a UE capability query message to the UE.

S1104, the UE reports UE capabilities including CA capabilities to the network device in response to the UE capability query message.

S1105, the network device sends a UE registration success message to the UE.

S1106, the network device sends an add SCC reconfiguration message to the UE.

S1107, the UE adds a SCC related CA combination in response to adding the SCC reconfiguration message.

S1108, the network device sends a delete SCC reconfiguration message (or RRC release message) to the UE.

S1109, in response to the registration success and the CA capability has been reported, detecting the communication anomaly type after receiving the SCC reconfiguration message.

S1110, deleting all CA combinations related to the SCC according to the detected communication abnormality type.

S1111, in response to the updated CA capability, after receiving the SCC reconfiguration message, detects a communication abnormality type.

S1112, deleting all CA combinations according to the detected communication abnormality types.

S1113, in response to the updated CA capability, after receiving the SCC reconfiguration message, detects the communication abnormality type.

And S1114, setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells.

In this embodiment, the UE sequentially performs the above operations according to the detected communication anomaly type, so that the CA capability can be rolled back until the SCC reconfiguration message is received, thereby facilitating recovery of normal communication between the UE and the network device, and facilitating improvement of user experience.

Fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication apparatus of the present embodiment is applicable to a UE. As shown in fig. 12, the communication apparatus 1000 includes an abnormality identification module 1001, a capability adjustment module 1002, and a capability restoration module 1003.

Wherein, the anomaly identification module 1001 is used for: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability.

The capability adjustment module 1002 is configured to: the following operations are performed according to the detected communication anomaly type: deleting all CA combinations associated with the SCC; or delete all CA combinations; or the current cell is set as a black cell and is switched to other cells.

The capability recovery module 1003 is configured to: after the corresponding operation is performed according to the detected communication abnormality type, the CA capability is re-reported or registration is re-initiated.

In this embodiment, the communication apparatus 1000 performs any of the operations described above according to the detected type of communication anomaly, so that the CA capability can be rolled back until the SCC reconfiguration message is received, thereby facilitating recovery of normal communication between the UE and the network device, and facilitating enhancement of user experience.

In one embodiment, the anomaly identification module 1001 is specifically configured to: in response to receiving the delete SCC reconfiguration message during operation of the first timer T1, counting a number of times the delete SCC reconfiguration message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. Wherein, T1 and T2 are synchronously started, and the operation time of T1 is smaller than the operation time of T2.

In another embodiment, the anomaly identification module 1001 is specifically configured to: in response to receiving the radio resource configuration RRC release message during operation of the first timer T1, counting the number of times the RRC release message is received during operation of the second timer T2. And in response to the number of times being greater than the number of times threshold, confirming the communication anomaly type. The method comprises the steps that T1 and T2 are synchronously started, the operation duration of T1 is smaller than the operation duration of T2, and the operation duration of T1 is smaller than the operation duration of a counted UE inactivity timer.

In another embodiment, the capability adjustment module 1002 is specifically configured to: and initiating a Mobility Registration Update (MRU) process, wherein the MRU process is used for updating CA capability. When reporting CA capabilities, all CA combinations associated with the SCC are deleted, or all CA combinations are deleted.

In another embodiment, the capability restoration module 1003 is specifically configured to: and in response to the duration of camping on the new cell exceeding the preset duration or switching from the flight mode to the communication mode, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

In other embodiments, the anomaly identification module 1001 is configured to: and responding to the reported carrier aggregation CA capability, and receiving a UE registration failure message, and acquiring a reason value from the UE registration failure message. And confirming the communication abnormality type according to the cause value.

The capability adjustment module 1002 is configured to: all CA combinations are deleted according to the communication anomaly type.

The capability recovery module 1003 is configured to: after all CA combinations are deleted according to the communication anomaly type, registration is reinitiated.

In one embodiment, the anomaly identification module 1001 is specifically configured to: traversing a preset reason value set according to the reason value. And confirming the communication abnormality type in response to the cause value being any one of the preset cause value sets.

In another embodiment, the capability restoration module 1003 is specifically configured to: timing begins with the deletion of all CA combinations. And in response to the counted time period being longer than the running time period of the third timer T31 and switching to other cells, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

In other embodiments, the anomaly identification module 1001 is configured to: and detecting the abnormal communication type after receiving the SCC reconfiguration message of the added secondary component carrier in response to receiving the UE registration success message and reporting the carrier aggregation CA capability. And detecting a communication anomaly type after receiving the SCC reconfiguration message in response to the updated CA capability.

The capability adjustment module 1002 is configured to: the following operations are successively performed according to the detected communication abnormality type: deleting all CA combinations associated with the SCC; deleting all CA combinations; and setting the current cell as a black cell and switching to other cells.

In this embodiment, the communication apparatus 1000 sequentially performs the above operations according to the detected communication anomaly type, and can rollback the CA capability until the SCC reconfiguration message is received, thereby facilitating recovery of normal communication between the UE and the network device, and facilitating enhancement of user experience.

It will be appreciated that the individual modules illustrated in this embodiment do not constitute a particular limitation of the communications device. In other embodiments, the communication device may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The embodiment of the application also provides a baseband processor, which is used for executing the technical scheme about the UE in the communication method embodiment of the application.

The embodiment of the application also provides a baseband chip, which comprises: the processor is configured to execute the technical scheme related to the UE in the foregoing communication method embodiment of the present application.

It will be appreciated that in other embodiments, the baseband chip may further include a memory, where the memory is configured to store a computer program or code related to the technical solution of the UE in the foregoing embodiments of the communication method of the present application.

The embodiment of the application also provides user equipment, which comprises: the baseband processor provided in the above embodiment, or the baseband chip provided in the above embodiment.

Fig. 13 is a schematic structural diagram of a user equipment according to an embodiment of the present application. As shown in fig. 13, the user device 100 includes a processor 110, a memory 120, a power module 130, a communication module 140, and a display 150. The processor 110 may execute a computer program or code stored in the memory 120 to implement the technical solution in the foregoing communication method embodiment of the present application.

Processor 110 may include one or more processing units. For example, the processor 110 may include, but is not limited to, an application processor (Application Processor, AP), a modem processor, a graphics processor (Graphics Processing Unit, GPU), an image signal processor (Image Signal Processor, ISP), a controller, a video codec, a digital signal processor (Digital Signal Processor, DSP), a baseband processor, a Neural-Network Processor (NPU), and the like. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include, but are not limited to, integrated circuit (Inter-Integrated Circuit, I2C) interfaces, integrated circuit built-in audio (Inter-Integrated Circuit Sound, I2S) interfaces, pulse code modulation (Pulse Code Modulation, PCM) interfaces, universal asynchronous receiver Transmitter (Universal Asynchronous Receiver/Transmitter, UART) interfaces, mobile industry processor interfaces (Mobile Industry Processor Interface, MIPI), general-Purpose Input/Output (GPIO) interfaces, subscriber identity module (Subscriber Identity Module, SIM) interfaces, universal serial bus (Universal Serial Bus, USB) interfaces, and the like.

It should be understood that the connection relationship between the modules illustrated in this embodiment is only illustrative, and does not limit the structure of the user equipment. In other embodiments, the ue may also use different interfacing manners in the foregoing embodiments, or a combination of multiple interfacing manners.

Memory 120 may include an external memory interface and an internal memory. The external memory interface may be used to connect to an external memory card, such as a Micro SD card, to extend the memory capability of the user device 100. The external memory card communicates with the processor 110 through an external memory interface to implement data storage functions. The internal memory may be used to store computer-executable program code that includes instructions. The internal memory may include a stored program area and a stored data area. The storage program area may store an application program (e.g., a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (e.g., audio data, phonebook, etc.) created during use of the user device 100, and the like. In addition, the internal memory may include a high-speed random access memory, and may also include a nonvolatile memory, such as at least one disk storage device, a flash memory device, or a universal flash memory (Universal Flash Storage, UFS), or the like. The processor 110 executes various functional applications of the user equipment 100 and data processing, such as implementing the technical solutions in the above-mentioned communication method embodiments of the present application, by executing instructions stored in an internal memory, and/or instructions stored in a memory provided in the processor 110.

The power module 130 is configured to receive a charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the power module 130 may receive a charging input of a wired charger through a USB interface. In some wireless charging embodiments, the power module 130 may receive wireless charging input through a wireless charging coil of the user device 100.

The power module 130 may include a battery. The power module 130 may also provide power to other electronic devices while charging the battery. The power module 130 receives battery input and provides power to the processor 110, the memory 120, the communication module 140, the audio module 150, the display 170, and the like. The power module 130 may also be used to monitor battery capacity, battery cycle times, battery health (leakage, impedance) and other parameters. In some embodiments, the power module 130 may also be disposed in the processor 110.

The communication module 140 may include a mobile communication module and a wireless communication module. The mobile communication module may provide a solution including wireless communication of 2G/3G/4G/5G/6G etc. applied on the user equipment 100. The wireless communication module may provide solutions for wireless communication including wireless local area network (Wireless Local Area Networks, WLAN) (e.g., wireless fidelity (Wireless Fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (Global Navigation Satellite System, GNSS), frequency modulation (Frequency Modulation, FM), near field wireless communication technology (Near Field Communication, NFC), infrared technology (IR), etc., as applied on the user device 100.

The display 150 includes a display panel. The display panel may employ, but is not limited to, a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), an Active-Matrix Organic Light-Emitting Diode (AMOLED), a flexible Light-Emitting Diode (FLED), a Mini-LED, a Micro-OLED, a quantum dot Light-Emitting Diode (QLED), or the like. In some embodiments, the user device 100 may include 1 or N display screens 150, N being a positive integer greater than 1.

It will be appreciated that the structure illustrated in this embodiment does not constitute a specific limitation on the user equipment. In other embodiments, the user device may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The embodiment of the application also provides a computer readable storage medium, which is used for storing a computer program or code, and when the computer program or code is executed by a processor, the technical scheme about the UE in the communication method embodiment of the application is realized.

Computer-readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer-readable storage media includes, but is not limited to, random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), electrically-charged erasable programmable Read-Only Memory (EEPROM), flash Memory or other Memory, compact disk Read-Only Memory (CD-ROM), digital versatile disks (Digital Versatile Disc, DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

The embodiments of the present application have been described in detail with reference to the accompanying drawings, but the present application is not limited to the above embodiments, and various changes can be made within the knowledge of one of ordinary skill in the art without departing from the spirit of the present application.

Claims

1. A communication method applied to a user equipment UE, the method comprising:

in response to receiving a UE registration success message and reporting carrier aggregation CA capability, detecting a communication anomaly type after receiving an SCC reconfiguration message of adding a secondary component carrier, wherein the communication anomaly type comprises at least one of SCC continuous addition release and continuous RRC connection establishment failure;

and executing the following operations according to the detected communication abnormality type:

continuously adding and releasing the SCC based on the communication anomaly type, deleting all CA combinations related to the SCC, or deleting all CA combinations, or setting the current cell as a black cell and switching to other cells;

and deleting all CA combinations or setting the current cell as a black cell and switching to other cells based on the communication anomaly type as the continuous RRC connection establishment failure.

2. The communication method according to claim 1, wherein the detecting of the communication abnormality type includes:

counting the number of times the deleted SCC reconfiguration message is received during the operation of the second timer T2 in response to the deleted SCC reconfiguration message being received during the operation of the first timer T1;

Responsive to the number of times being greater than a number of times threshold, confirming the communication anomaly type;

the T1 and the T2 are synchronously started, and the operation duration of the T1 is smaller than that of the T2.

3. The communication method according to claim 1, wherein the detecting of the communication abnormality type includes:

counting the number of times of receiving a Radio Resource Configuration (RRC) release message during the operation of a second timer (T2) in response to receiving the RRC release message during the operation of the first timer (T1);

the T1 and the T2 are synchronously started, the operation duration of the T1 is smaller than the operation duration of the T2, and the operation duration of the T1 is smaller than the operation duration of the counted UE inactivity timer.

4. A communication method according to any of claims 1 to 3, characterized in that after setting the current cell as a black cell and switching to the other cell, the method further comprises:

and in response to the duration of the new cell residence exceeding the preset duration or switching from the flight mode to the communication mode, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting registration to the network equipment.

5. A communication method according to any of claims 1 to 3, wherein said deleting all CA combinations associated with the SCC, or deleting all CA combinations, comprises:

initiating a Mobility Registration Update (MRU) process, wherein the MRU process is used for updating the CA capability;

when reporting the CA capabilities, all CA combinations associated with the SCC are deleted, or all CA combinations are deleted.

6. A communication method applied to a user equipment UE, the method comprising:

responding to the reported carrier aggregation CA capability, and receiving a UE registration failure message, and detecting a communication anomaly type;

based on the communication anomaly type being a continuous registration failure, performing the following operations:

acquiring a cause value from the UE registration failure message;

based on the reason value indicating that the reason of the UE registration failure is a first reason, deleting all CA combinations and initiating a UE registration flow;

wherein the first reason includes at least one of implicit de-registration, no suitable cell in the tracking area, not forwarded payload, semantically incorrect message, invalid mandatory information, no or unrealized message type, incompatible message type and protocol state, no or unrealized information element, conditional information element error, incompatible message and protocol state, and unexplained protocol error.

7. The communication method of claim 6, wherein the indicating the reason for the UE registration failure based on the cause value is a first reason, deleting all CA combinations, and initiating a UE registration procedure comprises:

traversing a preset reason value set corresponding to the first reason according to the reason value;

and deleting all CA combinations and initiating a UE registration flow in response to the cause value being any one of the preset cause value sets.

8. The communication method according to claim 6 or 7, wherein the deleting all CA combinations and initiating a UE registration procedure comprises:

starting timing from deleting all CA combinations;

and in response to the counted time length being longer than the running time length of the third timer T31 and switching to other cells, sending a UE registration request message to the network equipment, wherein the UE registration request message is used for requesting to register to the network equipment.

9. A communication method applied to a user equipment UE, the method comprising:

Deleting all CA combinations related to the SCC according to the detected communication abnormality type;

detecting the communication anomaly type after receiving the SCC reconfiguration message in response to the CA capability having been updated;

deleting all CA combinations according to the detected communication abnormality type;

and setting the current cell as a black cell according to the detected communication abnormality type, and switching to other cells.

10. The communication method according to claim 9, wherein the detecting the communication abnormality type includes:

11. The communication method according to claim 9, wherein the detecting whether the communication abnormality occurs comprises:

12. The communication method according to any one of claims 9 to 11, characterized in that after setting the current cell as a black cell and switching to another cell, the method further comprises:

13. The communication method according to any one of claims 9 to 11, wherein the deleting all CA combinations associated with the SCC, or deleting all CA combinations, comprises:

14. A baseband processor, comprising: a microcontroller for performing the communication method according to any one of claims 1 to 13.

15. A baseband chip, comprising: a processor for performing the communication method according to any of claims 1 to 13.

16. A user device, comprising: a baseband processor as claimed in claim 14, or a baseband chip as claimed in claim 15.