WO2024008074A1

WO2024008074A1 - Method for performing synchronous reconfiguration by means of user equipment, and user equipment

Info

Publication number: WO2024008074A1
Application number: PCT/CN2023/105707
Authority: WO
Inventors: 肖芳英; 刘仁茂
Original assignee: 夏普株式会社; 肖芳英
Priority date: 2022-07-07
Filing date: 2023-07-04
Publication date: 2024-01-11
Also published as: CN117460094A

Abstract

According to one aspect of the present invention, provided is a method for performing a synchronous reconfiguration by means of a user equipment. The method comprises: receiving an RRC reconfiguration message from a first network; and when the RRC reconfiguration message comprises configuration information for a secondary serving cell group, if a user equipment is in a MUSIM state, not performing a secondary serving cell configuration, which comprises enabling the secondary serving cell group to be in an activated state, and sending, to the network, a response message indicating that the user equipment is in the MUSIM state.

Description

Method for performing synchronous reconfiguration by user equipment and user equipment

Technical field

The present invention relates to the field of wireless communication technology, and in particular to a method for performing synchronous reconfiguration by user equipment and user equipment.

Background technique

In recent years, multi-USIM card devices have become increasingly popular. For example, a user installs two USIM cards on a mobile phone that supports multiple USIM cards. One USIM card is used to subscribe to private services, and the other USIM card is used to subscribe to office services. Existing devices that support multiple USIM cards are implemented by manufacturers and have not yet been standardized by 3GPP. As a result, different manufacturers adopt different implementation methods, and the behavior of user equipment UE is also different. In the existing implementation, if these USIM cards are registered with the network respectively (either to the same network or to two or more networks), the UE needs to receive paging from these networks. Based on the UE's transceiver capabilities, it may One situation that exists is that when the UE receives paging from the current network, another network also initiates paging for it, or when the UE is communicating with a network, another network initiates paging for it. If the UE switches between different networks, one possible result is that the UE can no longer receive data from the current network when the UE switches to another network. This will harm network performance, for example, the network sends a paging to the UE but the UE does not receive the paging because it switches to another network, or the UE switches to another network and cannot receive the schedule of the current network. Some manufacturers have proposed 3GPP standardization research on the behavior of UEs with multiple USIM cards accessing networks and related networks. The benefit is that network performance can be improved based on predictable UE behavior.

Based on the above reasons, in December 2019, at the 3rd Generation Partnership Project (3GPP) RAN#86 plenary meeting, vivo proposed a work project for version 17 multi-SIM card equipment (see non-patent literature : RP-193263: New WID: Support of Multi-SIM devices in Rel-17), and approved. One of the goals of this work item is to define a mechanism for a UE to notify Network A when it leaves Network A, where Network A is NR, Network B is LTE or NR, and the UE is Single-Rx/Single-Tx or UE dual receive and single transmit (Dual-Rx/Single-Tx).

In December 2021, at the 3GPP RAN#94 meeting, it was agreed to further enhance the multi-USIM card UE with dual reception and dual transmission capabilities (dual Rx/Tx), so that the UE can be in the RRC connection state in two networks at the same time (see non- Patent document: RP-213584 New WI on DualTxRx MUSIM enhancements).

This open discussion discusses relevant issues involved in achieving the goals of the work described above.

Contents of the invention

The object of the present invention is to provide a method that can avoid activating the SCG corresponding to the first network when the user equipment does not prefer to activate the SCG.

According to an aspect of the present invention, a method for performing synchronous reconfiguration by user equipment is provided, including: receiving an RRC reconfiguration message from a first network; when the RRC reconfiguration message includes configuration information for a secondary serving cell group, If the user equipment is in the MUSIM state, the secondary serving cell configuration including making the secondary serving cell group an active state is not performed, and a response message indicating that the user equipment is in the MUSIM state is sent to the network.

According to another aspect of the present invention, a method for performing conditional synchronization reconfiguration by user equipment is provided, including: when the user equipment is in the MUSIM state, even if the user equipment is configured to need to perform conditional reconfiguration, Performing the conditional reconfiguration; and when the user equipment is not in the MUSIM state and the user equipment is configured to need to perform conditional reconfiguration, and the evaluation result after performing conditional reconfiguration condition evaluation is that the reconfiguration condition is met , perform the conditional reconfiguration.

Beneficial effects of the invention

According to the solution of this specification, it is possible to avoid activating the SCG corresponding to the first network when the user equipment does not prefer to activate the SCG.

Description of the drawings

The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

Figure 1 is a schematic diagram for an example of a MUSIM capable user equipment mentioned in this specification.

FIG. 2 is used to illustrate the method executed by user equipment provided by the first embodiment in this specification. An exemplary flowchart of the method.

FIG. 3 is another exemplary flowchart for illustrating the method performed by the user equipment provided by the first embodiment in this specification.

FIG. 4 is an exemplary flowchart for illustrating a method performed by a user equipment provided in the second embodiment of this specification.

FIG. 5 is an exemplary flowchart for illustrating a method for performing synchronous reconfiguration by user equipment according to the third embodiment of this specification.

FIG. 6 is an exemplary flowchart for illustrating a method for performing synchronous reconfiguration by user equipment according to the fourth embodiment of this specification.

FIG. 7 is another exemplary flowchart for illustrating a method for performing synchronous reconfiguration by user equipment according to the fourth embodiment of this specification.

FIG. 8 is an exemplary flow chart for illustrating a method of configuring a secondary serving cell performed by user equipment according to the fifth embodiment of this specification.

FIG. 9 is an exemplary flow chart for illustrating the addition of a secondary serving cell in the method of configuring a secondary serving cell performed by user equipment in the fifth embodiment of this specification.

FIG. 10 is an exemplary flowchart for illustrating the modification of the secondary serving cell in the method of configuring the secondary serving cell performed by the user equipment in the fifth embodiment of this specification.

FIG. 11 is an exemplary flowchart for illustrating a method performed by a user equipment provided in the sixth embodiment of this specification.

FIG. 12 is an exemplary flowchart for illustrating the MUSIM release indication processing process in the method performed by the user equipment provided in the sixth embodiment of this specification.

FIG. 13 is an exemplary flowchart for illustrating a method for restoring an RRC connection performed by a user equipment provided in the seventh embodiment of this specification.

FIG. 14 is an exemplary flowchart for illustrating a method for restoring an RRC connection performed by a user equipment provided in the eighth embodiment of this specification.

Figure 15 is a block diagram of user equipment provided in this specification.

Detailed ways

The present disclosure will be described in detail below with reference to the accompanying drawings and specific implementation modes. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, the Well-known technologies that are not directly related to the present disclosure are described in detail to prevent confusion in the understanding of the present disclosure.

Some terms involved in this disclosure are described below. The specific meanings of the terms can be found in the latest relevant documents of 3GPP, such as TS38.300, TS38.331, TS36.300, TS36.331, etc.

NAS: Non-access stratum, non-access layer.

AS: access stratum, access layer.

RRC: Radio Resource Control, wireless resource control.

RRC_CONNECTED: RRC connected state.

RRC_INACTIVE: RRC inactive state.

RRC_IDLE: RRC idle state.

RLC: Radio Link Control, wireless link control.

CPA: Conditional PSCell Addition, conditional PSCell increases.

CPC: Conditional PSCell Change, conditional PSCell changes.

RAN: Radio Access Network, wireless access layer.

BWP: Bandwidth Part, bandwidth part.

USIM: Universal Subscriber Identity Module, global user identification card.

MUSIM: Multi-Universal Subscriber Identity Module, multiple global user identification cards.

Tx: transmitter, sender.

Rx: receiver, receiver.

NR: New RAT, new wireless access technology.

gNB: Provides NR user plane and control plane protocol stacks (NR user plane and control plane protocol terminations) to UE, and connects to the base station node of the 5G core network through the NG interface.

eNB: Provides E-UTRAN user plane and control plane protocol stacks to UE, and is connected to the base station node of the EPC core network.

ng-eNB: Provides E-UTRAN user plane and control plane protocol stacks to UE, and connects to the base station node of the 5G core network through the NG interface.

Dual connection or multi-connection: means that a UE working in the RRC connection state establishes a physical wireless path with more than one network node and realizes data transmission. In dual connectivity, a multi-Tx/Rx capable UE is configured to use resources provided by two network nodes, which pass Non-ideal backhaul connection. One of the network nodes serves as the master control node (Master Node, MN or MN gNB), and the other network node serves as the secondary control node (Secondary Node, SN or SN gNB). The MN and SN are connected via a network interface and at least the MN is connected to the core network. The MN can be executed by a gNB/eNB/ng-eNB. The serving cell group controlled by the MN is called the Master Cell Group (MCG), that is, the MCG is associated with the MN. There is at least one primary serving cell running on the primary frequency in the MCG, which is called the primary cell PCell (Primary Cell). The UE performs the initial connection establishment process or initiates the connection reestablishment process on the PCell. If the MCG also contains other cells, they can be collectively called secondary serving cells SCell. Correspondingly, SN can be performed by one or more gNB/eNB/ng-eNB, and the serving cell group controlled by the SN is called a secondary serving cell group (SCG), that is, the SCG is associated with the SN. The SCG contains at least one primary serving cell, which is called PSCell (Primary Second Cell). When performing the synchronous reconfiguration (synchronous reconfiguration for SCG or SCG change) procedure, the UE performs random access on the PSCell (performed only when required). If the SCG also contains other cells, they can be collectively called secondary serving cells SCell. A signaling radio bearer SRB can be established between the SN and the UE, usually called SRB3. SRB3 is used for specific RRC messages transmitted on the DCCH logical channel, applicable to UEs in (NG)EN-DC or NR-DC. SRB3 can be used to deliver RRC messages between the SN and the UE, such as SCG-related measurement configuration and reports. In this disclosure, SpCell may refer to PCell of MCG or PSCell of SCG.

An SCG radio bearer is a radio bearer with one RLC bearer in SCG only or a radio bearer with two RLC bearers in a carrier aggregation group duplication. The SCG radio bearer includes SCG signaling radio bearer SRB and SCG data radio bearer DRB.

SRB1 is used to carry all RRC messages using the DCCH logical channel and NAS messages before SRB2 is established.

SRB2 is used to carry NAS messages and all RRC messages containing recorded measurement information using the DCCH logical channel.

EN-DC: E-UTRA-NR dual connection, E-UTRA is MN, NR is dual connection of SN and is connected to EPC.

NGEN-DC: NG-RAN, E-UTRA-NR dual connection, and connected to the 5G core network 5GC.

NR DC: NR-NR dual connection, if and only if the configured mrdc-SecondaryCellGroup is set to nr-SCG.

MR-DC: Multi-Radio Dual Connectivity, multi-wireless dual connectivity, including (NG)EN-DC, NE-DC, NR-DC.

In this disclosure, network (or network node), base station (or base station node) and RAN can be used interchangeably. The network can be a long-term evolution LTE network, an NR network, an enhanced long-term evolution eLTE network, or a subsequent evolution of 3GPP. Other networks defined in the version.

In this disclosure, user equipment UE may refer to a device that physically supports multiple USIM cards (two or more USIM cards), and the USIM may be a physical SIM or eSIM (USIM can be a physical SIM or eSIM). The device is equipped with two or more USIM cards, and each USIM card is associated with a network (that is, an RRC connection is established with a network). The multiple USIM cards can be from the same operator or different operators. From a network perspective, different USIM cards can correspond to different UEs, and each USIM card corresponds to one UE. Unless otherwise specified, this disclosure does not make this distinction. Those skilled in the art can easily determine according to the context whether the UE refers to a UE that supports multiple USIM cards or a UE corresponding to each USIM card in a device that supports multiple USIM cards. User equipment configured with multiple USIM cards can receive and/or send data from multiple networks through time division multiplexing and other methods using single receive and single transmit or dual receive and single transmit. A UE with two Tx and two Rx (dual transmit and dual receive) can send data to two networks at the same time, and can also receive data from two networks at the same time. The hardware capabilities of MUSIM UE are shared by two SIM cards, and related capabilities are dynamically split between the two SIM cards. This will cause a brief hardware conflict, causing the UE to release some resources from one SIM card for use by another SIM card. For example, when SIM A of the UE is in the RRC connected state in network A, and SIM B is in the RRC idle state or RRC inactive state in network B, two radio frequency links (RF chains) or two transceivers are occupied by SIM A. for communication with Network A. If SIM B needs to establish an RRC connection with network B, one of the radio frequency links needs to be switched to SIM B. If network A does not know the changes in UE's radio frequency link capabilities, it will lead to data loss and waste of wireless resources in network A.

In the embodiment of this disclosure, the UE is configured with two USIM cards as an example. Those skilled in the art can easily extend it to the case of multiple USIM cards.

The following describes the fields involved in this disclosure:

The masterCellGroup field is used to configure the master cell group MCG.

The spCellConfig field contains parameters of the SpCell corresponding to the cell group (ie, the PCell of the MCG or the PSCell of the SCG).

The reconfigurationWithSync field contains parameters for synchronous reconfiguration to the target SpCell.

The CellGroupConfig field is used to configure the primary cell group MCG or the secondary serving cell group SCG.

The scg-State field is used to indicate that the SCG is in an inactive state. The base station indicates that the SCG is configured as an active state by not including the scg-State field in the RRC reconfiguration message RRCReconfiguration; and indicates that the SCG is configured as an inactive state by including the scg-State field in the RRC reconfiguration message.

The bfd-and-RLM field is used to indicate whether the UE performs Beam Failure Detection (BFD) and Radio Link Monitoring (RLM) when the SCG is deactivated.

The secondaryCellGroup field contains the configuration of the SCG (for (NG)EN-DC or NR-DC), and the secondaryCellGroup field contains the CellGroupConfig field.

The CellGroupConfig field is used to configure an MCG or SCG. A cell group consists of a MAC entity, a set of logical channels with associated RLC entities (a set of logical channels with associated RLC entities), a SpCell and one or more SCells.

The mrdc-SecondaryCellGroup field contains the RRC message for SCG configuration in NR-DC or NE-DC. In NR-DC, the mrdc-SecondaryCellGroup field contains the RRCReconfiguration message completely generated by the SN gNB. The RRCReconfiguration message generated by the SN gNB Can contain secondaryCellGroup field, otherConfig field, conditionalReconfiguration field and measConfig field.

The otherConfig field contains configurations related to other configurations, such as configuring the UE to report auxiliary information to notify the gNB about the UE's discontinuous reception DRX preference for energy saving, etc.

The conditionalReconfiguration field configures candidate target SpCell(s) and execution conditions for conditional switching and conditional PSCell changes.

The measConfig field defines the measurements performed by the UE, covering intra-frequency (intra-Frequency), inter-frequency (inter-Frequency) and inter-RAT (inter-RAT) mobility and the configuration of the measurement interval.

The nr-SCG field is included in the mrdc-SecondaryCellGroup field and is used to indicate that the dual connection is NR-DC. At this time, the RRC reconfiguration message contained in mrdc-SecondaryCellGroup is completely generated by SN gNB.

The sCellToAddModList field is used to indicate the list of added or modified SCells.

The sCellIndex field is used to identify a SCell.

The sCellState field indicates whether the SCell is considered to be in the activated state when configuring the SCell (indicates whether the SCell shall be considered to be in activated state upon SCell configuration). If the RRC reconfiguration message contains this field, and the field value is set to 'activated', it means that the SCell is in the activated state when configuring the SCell. If the RRC reconfiguration message does not contain this field, it means that the SCell is in the inactive state when configuring the SCell.

The firstActiveDownlinkBWP-Id field is used when configuring SpCell. It contains the identification ID of the downlink BWP activated when performing RRC reconfiguration or contains the identification ID of the downlink BWP used for RLM, BFD and measurement when the SCG is deactivated (when the RRC reconfiguration message This meaning is indicated when the UE needs to perform RLM, BFD and measurement); when used to configure SCell, this field contains the identification ID of the downlink BWP used when activating SCell.

When firstActiveUplinkBWP-Id is used to configure SpCell, it contains the identification ID of the uplink BWP that is activated when performing RRC reconfiguration; when it is used to configure SCell, this field contains the identification ID of the uplink BWP used when activating SCell.

The sCellConfigCommon field corresponds to the ServingCellConfigCommon field that is used to configure configurable cell-specific parameters of the UE's serving cell. The ServingCellConfigCommon field contains parameters obtained from the synchronization signal block SSB, main information block MIB or system information block SIB when the IDLE state UE accesses the cell. When configuring SCell, the network provides this information through dedicated signaling containing this field.

The sCellConfigDedicated field corresponds to the ServingCellConfig field. The ServingCellConfig field is used to configure (that is, add or modify) a serving cell for the UE. This serving cell can be SpCell or SCell of MCG or SCG.

The VarConditionalReconfig variable contains the cumulative configuration including conditional switch CHO, conditional PSCell increase CPA, conditional PSCell change CPC configuration, including pointers to CHO, CPA, CPC execution conditions (associated measId(s)) and stored target candidate SpCell RRC reconfiguration (includes the accumulated configuration of the conditional handover, conditional PSCell addition or conditional PSCell change configurations including the pointers to conditional handover, conditional PSCell addition or conditional PSCell change execution condition (associated measId(s)) and the stored target candidate SpCell RRCReconfigur ation).

The condReconfigID field is used to identify a CHO, CPA, and CPC configuration.

The condRRRCReconfig field contains the RRC reconfiguration message that is applied when the conditions are met.

The condTriggerConfig field is used to configure CHO, CPA, and CPC and set the trigger conditions for CHO, CPA, and CPC.

The measId field is used to identify the measurement identity for which the reporting is being performed.

The DRB-Identity field is used to identify the DRB used by a UE.

The RLC-BearerConfig field is used to configure an RLC entity, the corresponding logical channel in the MAC, and the association with the PDCP entity (the radio bearer of the service).

The SCG failure information message, that is, the SCGFailureInformation message, is used to provide information about the SCG failure detected by the UE.

The RRC Resume Request message RRCResumeRequest or RRCResumeRequest1 is used to request to resume a suspended RRC connection or perform a RAN-based Notification Area (RNA) update. The UE may choose to request to resume an RRC connection with RRCResumeRequest or RRCResumeRequest1 based on whether SIB1 has sent (signal) useFullResumeID field (filed). If SIB1 sends the useFullResumeID field (filed), use RRCResumeRequest1 to request the restoration of an RRC connection. If SIB1 does not send the useFullResumeID field (filed), use RRCResumeRequest to request the restoration of an RRC connection.

The RRC Resume RRCResume message is used to resume the suspended RRC connection. The RRC reconfiguration message RRCReconfiguration is an instruction to modify the RRC connection.

The UEAssistanceInformation message is used to indicate UE assistance information to the network.

The RRC reconfiguration completion message RRCReconfigurationComplete is used to confirm the successful completion of RRC connection reconfiguration.

If the upper layer (such as the RRC layer) indicates to activate the SCG (the SCG in the active state), it can be performed: transmitting SRS on the PSCell, reporting the CSI of the PSCell, monitoring the PDCCH on the PSCell, transmitting the PUCCH on the PSCell, etc.

If the upper layer (such as the RRC layer) instructs to deactivate the SCG, you can perform the following steps: deactivate all SCells of the SCG, deactivate the SCG, clear the configured downlink allocation or type 2 uplink permission of the PSCell associated configuration, and suspend the type 1 associated with the PSCell. Configure uplink permission, reset MAC, etc.

The SCG in the inactive state does not transmit SRS on PSCell, does not report CSI of PSCell, does not transmit UL-SCH on PSCell, does not transmit PUCCH on PSCell, etc.

In this disclosure, the UE believes that the SCG or SCell has been activated, which may mean that the UE instructs the lower layer to activate the SCG or SCell.

It should be noted that in dual connectivity, although the UE performs data transmission with two network nodes, MN and SN, the UE only establishes an RRC connection with the MN. In MUSIM, the UE can establish RRC connections with the network through each SIM card.

Figure 1 is a schematic diagram of a UE with MUSIM capability in dual connectivity in network A. In Figure 1, SIM card A of the UE establishes an RRC connection with network A (denoted as the first network), SIM card B establishes an RRC connection with network B (denoted as the second network), and the UE is configured with dual connectivity by network A. , network A is MN, and network C is SN. The embodiment of the present disclosure is based on the scenario described in Figure 1 .

FIG. 2 is an exemplary flowchart for illustrating a method performed by a user equipment provided in the first embodiment of this specification. In the first embodiment, the user equipment is in the RRC connected state in the first network, and is configured in the first network to need to perform secondary serving cell group network quality detection. In the first network, the secondary serving cell group where the user equipment is located is in an inactive state.

As shown in Figure 2, in S202 to S204, secondary serving cell group network quality detection is performed. Network quality detection can include RLM and BFD.

When the failure of the secondary serving cell group is detected, a secondary serving cell group failure information message transmission process is initiated to the first network. The secondary serving cell failure information message transmission process is used to send to the first network a message indicating that the secondary serving cell group has failed. A secondary serving cell group failure information message indicating that the secondary serving cell group where the user equipment is located in the network has expired. For example, when a beam failure is detected, it may be determined that the secondary serving cell group failure is detected.

Specifically, the secondary serving cell group failure information message transmission process may include S206 to S212.

In S206, it is determined whether the user equipment is in the MUSIM state. The MUSIM state refers to a state in which the user equipment's capabilities are limited, or in other words, a state in which the user equipment can only use part of its capabilities to communicate with the first network. For example, the following situation belongs to one of the MUSIM states: the user equipment including multiple SIMs is in the RRC connection state in the first network and maintains an RRC connection with a second network different from the first network, and the user equipment preference is not the same. Release the RRC connection with the second network.

In this specification, the user equipment can be determined to be in the MUSIM state when any of the following conditions is met: the user equipment is in RRC in a second network different from the first network. Connected state; the user equipment performs uplink data transmission or downlink data transmission in the second network; the secondary serving cell group where the user equipment is located in the first network cannot be activated; the secondary serving cell group where the user equipment is located in the first network The group cannot be configured; the user equipment prefers not to activate the secondary serving cell group in the first network; the user equipment is in a limited user equipment capability state in the first network; some hardware functions of the user equipment are occupied and cannot be used for all purposes. Data transmission of the user equipment in the first network.

When the user equipment is in the MUSIM state, in S208, the secondary serving cell group failure information message includes MUSIM indication information indicating that the user equipment is in the MUSIM state. In other words, a secondary serving cell group failure information message including MUSIM indication information indicating that the user equipment is in the MUSIM state is generated.

As an example, the MUSIM indication message can be included in the secondary serving cell group failure information message in any of the following ways: adding a field for indicating that the user equipment is in the MUSIM state in the secondary serving cell group failure information message; In the serving cell group failure information message, the field used to indicate the cause of the secondary serving cell group failure is assigned a value used to indicate that the user equipment is in the MUSIM state.

Then, in S212, a secondary serving cell group failure information message including MUSIM indication information is sent to the first network. After receiving the secondary serving cell group failure information message, the first network can know that the secondary serving cell group of the user equipment has expired, and can configure a new secondary serving cell for the user equipment. At this time, since the received secondary serving cell group failure information message includes MUSIM indication information, the first network will consider the fact that the user equipment is in the MUSIM state when configuring a new secondary serving cell for the user equipment to avoid configuring a new secondary serving cell for the user equipment. Configure activated SCG. This can prevent problems such as resource waste and data loss caused by the inability to successfully transmit data through the SCG due to some hardware resources of the user equipment being occupied even if the SCG is activated.

When the user equipment is not in the MUSIM state, in S210, a secondary serving cell group failure information message not including MUSIM indication information indicating that the user equipment is in the MUSIM state is generated. Then, in S212, a secondary serving cell group failure information message excluding MUSIM indication information indicating that the user equipment is in the MUSIM state is sent to the first network.

FIG. 3 is another exemplary flowchart for illustrating the method performed by the user equipment provided by the first embodiment in this specification. The difference between Figure 3 and Figure 2 lies in S304. In Figure 3 S302 is the same as the above-mentioned S202, and S306 to S312 are the same as the above-mentioned S206 to S212 respectively.

In S304, it is determined whether the detected secondary serving cell group failure is a beam failure of the PSCell.

When the detected secondary serving cell group failure is a beam failure of the PSCell, the next secondary serving cell group failure information message transmission process is performed.

In addition, in this specification, whether to allow using part of the hardware capabilities of the user equipment to communicate with the first network may be configured by the first network. It should be noted that allowing the use of part of the hardware capabilities of the user equipment to communicate with the first network can be expressed as the UE is configured to report that the UE capabilities are restricted in the first network for MUSIM purposes (or report that the UE capabilities are restricted in the first network or report UE capabilities used in the first network) auxiliary information.

The secondary serving cell group failure information message transmission process may be performed when the user equipment is configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment, that is, determining whether the user equipment is in the MUSIM state. operation. Furthermore, when the user equipment is in the MUSIM state, the secondary serving cell group failure information message includes MUSIM indication information indicating that the user equipment is in the MUSIM state. In this case, the user device needs to notify that it is in the MUSIM state.

On the other hand, when the user equipment is configured by the first network to not allow only part of the hardware capabilities of the user equipment to communicate with the first network or is not configured by the first network to allow only part of the hardware capabilities of the user equipment to communicate with the first network In the case of communication, when the user equipment needs to establish an RRC connection with the second network, the RRC connection with the first network will be released. That is, in this case, there is no MUSIM state.

Specific examples of the first embodiment will be described below.

Embodiment where the UE detects the failure of the PSCell beam of the SCG in the inactive state

Embodiment 1 of the present disclosure is dedicated to solving the problem that a UE with at least dual-receive and dual-transmit capabilities detects that the PSCell beam of the SCG in the inactive state fails when both network A and network B are in the RRC connection state, but the UE considers that network B has priority. Relevant issues involved in sending an SCG invalidation information message to network A at a higher level to avoid network A configuring an active SCG for the UE after receiving the SCG invalidation information message.

Example 1

In this embodiment, the UE is in dual links in network A, where the SCG is in an inactive state but is configured to perform beam failure detection and wireless link monitoring. Specifically, the UE receives the RRC reconfiguration message from the base station, which contains the configuration information of the SCG (that is, the RRC reconfiguration message contains the secondaryCellGroup field or the mrdc-SecondaryCellGroup field), and the SCG is configured as an inactive state but needs to perform BFD and RLM (that is, the SCG configuration information contains the bfd-and-RLM field, and its value is set to "true"). The UE configures the SCG according to the received RRC reconfiguration message.

When the SCG is in the inactive state and PSCell beam failure is detected, the UE initiates the SCG failure information transmission process, which specifically includes at least one of the following:

1) Stop the SCG timer T304 (the SCG's T304 is executed when it is running); T304 is started when receiving the RRC reconfiguration message containing the synchronous reconfiguration of the SCG configured as inactive (start upon reception of RRCRe configuration including reconfigurationWithSync for the SCG not indicated as deactivated in the NR message containing the RRCReconfiguration message), stops when random access is successfully completed on the SpCell or the SCG is released.

2) Stop the conditional reconfiguration evaluation of CPA and/or CPC (only executed when CPA and/or CPC are configured);

3) Initiate transmission of SCG failure information message.

Transmitting the SCG failure information message SCGFaulureInformation includes the following operations:

The UE sets the content of the SCGFaulureInformation message as follows:

If the UE initiates transmission of the SCGFailureInformation message due to detecting beam failure of the PSCell and the SCG is deactivated (if the UE initates transmission of the SCGFaulureInformation message due to beam failure of the PSCell while the SCG is dectivated), then further determine whether the UE is in MUSIM state. If the UE is in the MUSIM state, the SCGFailureInformation message contains indication information that the UE is in the MUSIM state; otherwise, the SCGFailureInformation message does not contain the indication information that the UE is in the MUSIM state.

The indication information that the UE is in the MUSIM state can be implemented through the following implementation methods:

In one implementation, a new field mus is added to the SCGFailureInformation message. im to indicate that the UE is in the MUSIM state. Specifically, if the UE is in the MUSIM state, set the failureType field value in the SCGFailureInformation message to indicate the cause to "other" and set the failureType-v1610 in the SCGFailureInformation message to further indicate the cause to "beamFailure", and include the musim field to Indicate that the UE is in the MUSIM state or set the value of field musim to a value indicating that the UE is in the MUSIM state, such as "true"; if the UE is not in the MUSIM state, set the failureType and value to "other" and set failureType-v1610 to "beamFailure" , and the SCGFailureInformation message does not contain the musim field or the SCGFailureInformation message contains the musim field but its value is set to a value corresponding to the UE not being in the MUSIM state, for example, the musim field value is "false".

In one implementation, the value of a field used to indicate the cause of SCG failure (such as the failureType-v1610 field) is added, and a new value is set for the field to indicate that the UE is in the MUSIM state or the UE that has SCG beam failure is in the MUSIM state. The MUSIM state or the UE in the MUSIM state suffers from SCG beam failure or the UE is in the MUSIM state and the SCG beam fails. For example, when the value of failureType-v1610 is "musim", it means that the UE is in the USIM state or it means that the UE in the MUSIM state detects the failure of the PSCell beam of the inactive SCG.

When the network receives the SCG invalidation information message, it may determine the state of the SCG to be reconfigured for the UE according to whether the message contains an indication indicating that the UE is in the MUSIM state. For example, if the SCG failure information message received by the network contains an indication that the UE is in the MUSIM state, the SCG reconfigured for the UE is set to the inactive state. Otherwise, the SCG can be set to the active state.

In this disclosure, the UE in the MUSIM state includes: the UE is in the RRC connected state in network B, the UE is performing a MUSIM operation (that is, the UE is performing or needs to perform a MUSIM operation that cannot be completed within the MUSIM interval), the UE is in the two networks at the same time. RRC connected state or the SCG cannot be activated or the SCG cannot be configured, the UE does not prefer to activate the SCG (that is, the UE prefers not to activate the SCG or the UE prefers that the SCG is in an inactive state), some UE capabilities (such as transceivers or radio frequency links) ) is occupied (or occupied by another network), communication with network A can only use part of the UE capabilities, the UE's UE capabilities in network A are limited, the UE is in a UE capability-limited state in network A, and the UE preference is limited to the network A's UE capabilities and UE capabilities are shared among multiple networks at the same time. In a carrier aggregation scenario, the UE is in MUSIM state It also includes: the UE does not expect to activate the SCell, the UE does not expect to activate the SCell with the same frequency as the PCell, the UE prefers the SCell to be in the inactive state, and the UE prefers the SCell with the different frequency to the PCell to be in the inactive state.

In this disclosed embodiment, the UE believes that network B has a higher priority including: the UE does not release the RRC connection with network B, the UE prefers to maintain the MUSIM state, the UE prefers not to activate the SCG, the UE prefers not to activate the SCell, and the UE prefers not to activate the SCell. PSCell inter-frequency SCell. The condition that the UE is in the MUSIM state can be replaced by that the UE believes that network B has a higher priority or that the UE is in the MUSIM state and believes that network B has a higher priority.

It should be noted that in the embodiment of the present disclosure, the condition for determining whether the UE is in the MUSIM state can be replaced by determining whether the UE is in the MUSIM state only when the UE is configured by network A to allow the UE to request to enter the MUSIM state, that is, if the UE is configured The UE is allowed to request to enter the MUSIM state, and the UE is in the MUSIM state, then perform the operations that should be performed when the UE is in the MUSIM state in the embodiment. The base station can use the RRC reconfiguration message to configure whether to allow the UE to request to enter the MUSIM state (or configure whether to allow the UE to request to enter the MUSIM state or request to be in the UE capability restricted state, or configure whether to allow the UE to request to limit the UE capability). Correspondingly, if the UE is not in the MUSIM state, it means that the UE is in the RRC connected state in only one of the networks (for example, network A) or the UE does not perform a MUSIM operation or the SCG can be activated or the SCG can be configured or the UE capability (such as a transceiver or radio frequency chain) path) is not occupied by other networks or communication with network A can use all UE capabilities or the UE's UE capabilities in network A are not limited or the UE is not in a UE capability-limited state in network A or the UE preferences are not limited to network A's UE capabilities. In the carrier aggregation scenario, the UE not being in the MUSIM state also includes: the SCell can be activated, the SCell with different frequencies from the PCell can be activated, the UE does not prefer the SCell to be in the inactive state, and the UE does not prefer the SCell with the different frequency to the PCell to be in the inactive state.

In this disclosure, replacing the UE in the MUSIM state with the fact that the UE is configured can request to enter or exit the MUSIM state and the embodiment obtained by the UE being in the MUSIM state is also within the scope of protection of this disclosure, and replacing the UE not in the MUSIM state with the fact that the UE is configured Embodiments in which entry or exit of the MUSIM state may be requested and the UE is not in the MUSIM state or if the UE is not configured may be requested to enter or exit the MUSIM state are also within the scope of the present disclosure. The UE's request to exit the MUSIM state may include: the UE releases the RRC connection in network B, the UE does not perform a MUSIM operation (that is, the UE does not perform or does not need to perform a MUSIM operation that cannot be completed within the MUSIM interval), the UE is only in the first network RRC connected state or SCG can be activated or SCG can be configured, UE capabilities (e.g. transceiver or radio frequency link) is not occupied (or occupied by another network), communication with network A can use all UE capabilities, the UE's UE capabilities in network A are not limited, the UE is not in a UE capability-limited state in network A, UE preferences do not limit UE capabilities in Network A. In the carrier aggregation scenario, the UE not in the MUSIM state also includes: it can activate SCell, and it can activate SCell with different frequency than PCell.

Network A can configure the UE through the RRC reconfiguration message whether to allow the UE to request to enter or exit the MUSIM state or whether to allow the UE to request to limit the UE capabilities in the current network. In this case, Network A configures information that allows the UE to indicate to the network whether the UE is in the MUSIM state only when the UE enters or exits the MUSIM state. If the UE is configured by network A to request to enter or exit the MUSIM state, then when the UE needs to enter the MUSIM state, it sends an RRC message containing indication information requesting to enter the MUSIM state to network A. For example, if the UE is configured by network A, it can request to enter the MUSIM state. When the UE needs to establish an RRC connection with network B, it requests to network A to enter the MUSIM state. When the UE releases the RRC connection with network B, it can indicate to network A The UE exits the MUSIM state so that Network A can use all UE capabilities.

It should be noted that configuring the UE to allow the UE to request to enter or exit the MUSIM state can be replaced by allowing the UE to request UE capabilities limited to the current network, or allowing the use of part of the hardware capabilities of the user equipment to communicate with the first network, or configuring the UE to The MUSIM purpose reports the auxiliary information that limits the UE's capabilities in the first network, or configures the UE for the MUSIM purpose to report the auxiliary information that limits the UE's capabilities in the first network, or configures the UE for the MUSIM purpose to report the UE used in the first network Capability auxiliary information, or auxiliary information for the UE configured for MUSIM purposes to report entering or exiting the UE's capability limited state in the first network, in the embodiments of the present disclosure, any one of these description methods is used to obtain the embodiment. It is also within the scope of this manual.

As shown in Figure 4, in S402, an RRC reconfiguration message from the first network is received. Here, the RRC reconfiguration message is used to configure a new secondary serving cell group and configure the new secondary serving cell group into an active state, or to activate an existing secondary serving cell group. That is, the received RRC reconfiguration message includes configuring a new secondary serving cell group and configuring the new secondary serving cell group into an active state. configuration information, or include configuration information for activating existing secondary serving cell groups.

When receiving the RRC reconfiguration message from the first network, in S404, it is determined whether the user equipment is in the MUSIM state.

If the user equipment is in the MUSIM state, then in S406, an indication message indicating that the user equipment is in the MUSIM state is sent to the first network.

In an example, when the user equipment is in the MUSIM state, if the RRC reconfiguration message is used to configure the new secondary serving cell group and configure the new secondary serving cell group as active, the user equipment does not perform the instructions indicated by the RRC reconfiguration message. Secondary service cell group configuration. At this time, the indication message includes information that the secondary serving cell group configuration has not been performed.

In another example, when the user equipment is in the MUSIM state, if the RRC reconfiguration message is used to configure the new secondary serving cell group and configure the new secondary serving cell group to be active, the user equipment performs the instructions indicated in the RRC reconfiguration message. Secondary serving cell group configuration, but the configured new secondary serving cell group is not activated. At this time, the indication message includes information that the new secondary serving cell group is not activated.

In another example, when the user equipment is in the MUSIM state, if the RRC reconfiguration message is used to activate an existing secondary serving cell group, the user equipment does not perform the secondary serving cell group activation indicated by the RRC reconfiguration message. At this time, the indication message includes information that activation of the secondary serving cell group has not been performed.

In addition, when receiving the RRC reconfiguration message, the user equipment can also determine whether its currently available resources are sufficient to activate a new secondary serving cell group or an existing secondary serving cell group. When the currently available resources of the user equipment are sufficient to activate the new secondary serving cell group or the existing secondary serving cell group, the new secondary serving cell group or the existing secondary serving cell group can be activated regardless of whether the user equipment is in MUSIM mode. How to determine whether the currently available resources are sufficient to activate a new secondary serving cell group or an existing secondary serving cell group can be implemented, for example, by the internal logic of the user equipment, and the internal logic can be provided by the provider of the user equipment. As an example, it can be determined by whether the occupancy rate of the hardware resource is lower than a given threshold or the like.

Furthermore, whether to allow use of part of the hardware capabilities of the user equipment to communicate with the first network may be configured by the first network. The operation of whether the user equipment is in the MUSIM state may be determined to be performed when the user equipment is configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment.

Specific examples of the second embodiment will be described below.

Example of the network configuring active SCG for UE

Embodiment 2 of the present disclosure is dedicated to solving the problem that when a UE with at least dual-receiving and dual-transmitting capabilities is in the RRC connected state, network A configures an SCG for the UE or network A instructs the UE to activate the SCG in the inactive state but the UE Relevant issues involved when in the MUSIM state, in order to prevent the UE in the MUSIM state from activating the SCG and make the SCG state in the UE and network A consistent.

Example 2

This embodiment considers that the UE receives the RRC reconfiguration message RRCReconfiguration from network A. The RRC reconfiguration message is used to configure the SCG and indicates that the SCG is in the active state or the RRC reconfiguration message is used to activate the SCG. Specifically, it includes the following: Condition:

Scenario 1 (MN configures and activates SCG): The UE receives the RRC reconfiguration message from network A (MN) (in the embodiment of this disclosure, it refers to the RRC reconfiguration message generated by the MN and sent in SRB1 and not included in other RRC messages. message), the RRC reconfiguration message is transmitted on SRB1, which contains the configuration information of the SCG, that is, the configuration information of the SCG is provided by including the secondaryCellGroup field in the RRC reconfiguration message (that is, the RRC reconfiguration message is generated by the MN) , and SCG is configured in the active state. This is for the case where the RRC reconfiguration message is used to configure SCG for the UE, which has not been configured with SCG before. In this case, if the UE is in the MUSIM state, the UE can configure the SCG according to the SCG configuration information carried in the RRC reconfiguration message but not activate the SCG, and the UE indicates to Network A (or MN) that the UE is in the MUSIM state. Or information used to indicate that the SCG has been configured but has not been activated (for example, indicated in the RRC reconfiguration complete message). The UE may also indicate to network A that the UE is in the MUSIM state without configuring the SCG or may be used to indicate that the SCG is not configured. information (for example, indicated in the RRC reconfiguration complete message).

For case 1, if the UE adopts the operation of configuring SCG but not activating SCG, the specific steps include: if the RRC reconfiguration message does not contain mrdc-SecondaryCellGroupConfig (an optional condition at this time) and if the RRC reconfiguration message does not contain scg- State and the UE is not in the MUSIM state, the SCG activation process without an SN message is performed; optionally, if the RRC reconfiguration message does not contain scg-State and the UE is in the MUSIM state, the UE indicates to the network MN that the UE is in the MUSIM state. Information or information used to indicate that the SCG has been configured but has not been activated (for example, when RRC reconfiguration is completed RRCReconfigurationComplet e message), in this case, the UE does not activate the SCG.

For case 1, if the UE does not configure the SCG, it specifically includes: if the RRC reconfiguration message contains the configuration information of the SCG and the SCG is configured in an inactive state, or if the RRC reconfiguration message contains the configuration information of the SCG and If the SCG is configured in the active state but the UE is not in the MISIM state, the cell group configuration of the SCG is performed. If the RRC reconfiguration message does not contain mrdc-SecondaryCellGroupConfig (this condition is optional) and if the RRC reconfiguration message contains SCG configuration information and does not contain scg-State but the UE is in the MUSIM state, the UE reports to the network MN Information indicating that the UE is in the MUSIM state or related information used to indicate that the SCG is not configured (for example, indicated in the RRC Reconfiguration Complete RRCReconfigurationComplete message). In this case, the UE does not perform cell group configuration of the SCG.

Case 2 (MN activates the configured SCG): The UE receives the RRC reconfiguration message from network A (MN). The RRC reconfiguration message is transmitted on SRB1 and does not contain scg-State to indicate activation of the configured SCG. This is the case where the MN activates the configured SCG. In this case, if the UE is in MUSIM state and the UE considers that network B has a higher priority, the SCG is not activated. If the UE decides not to activate the SCG, the UE indicates to the network MN information that the UE is in the MUSIM state or information used to indicate that the SCG is not activated (for example, indicated in the RRC reconfiguration complete message).

Specifically, if the RRC reconfiguration message is received from SRB1 and the UE is in NR-DC and the RRC reconfiguration message does not contain mrdc-SecondaryCellGroupConfig (this condition is optional) and if the RRC reconfiguration message does not contain scg -State and the UE is not in the MUSIM state, then perform the SCG activation process without SN message; if the RRC reconfiguration message is received from SRB1 and the UE is in NR-DC and the RRC reconfiguration message does not contain mrdc-SecondaryCellGroupConfig and if the The RRC reconfiguration message does not contain scg-State but the UE is in the MUSIM state, then the UE indicates to the network MN the information that the UE is in the MUSIM state or the information used to indicate that the SCG is not activated (for example, indicated in the RRC reconfiguration complete message) , in this case, the UE does not activate the SCG.

Scenario 3 (SN configures SCG and MN activates SCG): The UE receives the first RRC reconfiguration message containing the hr-SCG field in the mrdc-SecondaryCellGroup field on SRB1, The RRC message (for example, the second RRC reconfiguration message) containing the first RRC reconfiguration message does not contain an scg-State field to indicate that the SCG is configured as an active state. This is a situation where the configuration information of the SCG is completely provided by the SN, and the MN configures the SCG in an active state. In this case, if the UE is in the MUSIM state, the UE may not configure the SCG or the UE configures but does not activate the SCG. Optionally, the UE indicates to the network MN and/or SN that the UE is in the MUSIM state or the SCG is not configured. information or information that the SCG has been configured but not activated.

For case three, if the UE adopts the method of not configuring SCG, it specifically includes: if the first RRC reconfiguration message is an RRC reconfiguration message containing the nr-SCG field in the mrdc-SecondaryCellGroup field and if the first RRC reconfiguration message is received on SRB1. If the reconfiguration message contains secondaryCellGroup, then:

If the RRC message containing the first RRC reconfiguration message contains scg-State, perform SCG cell group configuration; if the RRC message containing the first RRC reconfiguration message does not contain scg-State and the UE is not in In the MUSIM state, the cell group configuration of the SCG is performed; conversely, if the RRC message containing the first RRC reconfiguration message does not contain scg-State and the UE is in the MUSIM state, the cell group configuration of the SCG is not performed; optional , if the first RRC reconfiguration message containing the nr-SCG field in the mrdc-SecondaryCellGroup field is received on SRB1, and the RRC message containing the first RRC reconfiguration message (for example, the second RRC reconfiguration message) does not contain scg-State and the UE is in the MUSIM state, the UE indicates to the network MN and/or SN the information that the UE is in the MUSIM state or the SCG is not configured.

For case three, if the UE adopts the configuration SCG but does not activate the SCG, it specifically includes: if the first RRC reconfiguration message is an RRC reconfiguration message containing the nr-SCG field in the mrdc-SecondaryCellGroup field and if the first RRC reconfiguration message is received on SRB1 and if the The first RRC reconfiguration message contains secondaryCellGroup, then:

If the first RRC reconfiguration message is an RRC reconfiguration message containing the hr-SCG field in the mrdc-SecondaryCellGroup field received on SRB1, and the RRC message containing the first RRC reconfiguration message does not contain scg -State, if the UE is not in the MUSIM state, configure the SCG and perform the SCG activation operation; optionally, if the RRC message containing the first RRC reconfiguration message does not contain scg-State, but the UE is in the MUSIM state, Then configure the SCG and the UE indicates to network A (MN and/or SN) that the UE is Information in the MUSIM state or information that the SCG has been configured but not activated.

Scenario 4 (SN-initiated SCG change and MN activates SCG): The UE receives the first RRC reconfiguration message containing the nr-SCG field in the mrdc-SecondaryCellGroup field on SRB1, and the RRC containing the first RRC reconfiguration message The scg-State field is not included in the message (for example, the second RRC reconfiguration message) to indicate that the SCG is configured as an active state, if the spCellConfig field in the nr-SCG field contains reconfigurationWithSync:

If the UE is not in the MUSIM state, random access is initiated on the PSCell.

If the UE is in the MUSIM state, the UE does not initiate random access until it exits the MUSIM state; or, if the UE is in the MUSIM state, the UE indicates in the response message that the UE is in the MUSIM state (the UE does not initiate random access on the PSCell at this time). The response message may be an RRC reconfiguration completion message. The indication information that the UE is in the MUSIM state may be indicated only in the response message sent to the MN, or may be indicated only in the response message forwarded to the SN through the MN, or may be indicated simultaneously in The response message sent to the MN and indicated in the response message forwarded by the MN to the SN.

In the present disclosure, it may be restricted that MUSIM and DAPS cannot be configured at the same time, or if the UE is in the MUSIM state, DAPS switching cannot be configured.

As shown in Figure 5, at S502, an RRC reconfiguration message is received from the first network.

Then, at S504, it is determined whether the received RRC reconfiguration message includes configuration information for the secondary serving cell group.

The configuration information for the secondary serving cell group may be, for example, the configuration information for changing the secondary serving cell group. In this case, the RRC reconfiguration message may indicate configuring the target secondary serving cell group. The so-called secondary serving cell group change here refers to changing at least the primary and secondary cells PSCell of the secondary serving cell group, that is, changing from the current primary and secondary cells to a target primary and secondary cell that is different from the current primary and secondary cells.

The configuration information for the secondary serving cell group may also be, for example, configuration information used to change the secondary serving cell group where the user equipment is currently located. At this time, the RRC reconfiguration message can indicate to the user The secondary service cell group where the device is currently located is changed. Here, change refers to changing the configurable parameters of the current secondary serving cell group, such as configuring the secondary serving cell group to be in an active state, adding or releasing SCells of the secondary serving cell group.

When it is determined in S504 that the RRC reconfiguration message includes configuration information for the secondary serving cell group, in S506, it is determined whether the user equipment is in the MUSIM state.

If the user equipment is in the MUSIM state, in S508, the secondary serving cell group configuration including making the secondary serving cell group an active state is not performed, and a response message indicating that the user equipment is in the MUSIM state is sent to the network. The so-called non-execution includes synchronous reconfiguration of the secondary serving cell group in the active state. For example, it may be not executing the secondary serving cell group configuration indicated by the RRC reconfiguration message, or executing the secondary serving cell group configuration but not making the secondary serving cell group. Active state (that is, the secondary serving cell group is inactive state).

If the RRC reconfiguration message does not include configuration information for the secondary serving cell group (No in S504) or the user equipment is not in the MUSIM state (No in S506), then in S510, perform reconfiguration indicated by the RRC reconfiguration message.

Specific examples of the third embodiment will be described below.

Switch HO

When both network A and network B are in the RRC connected state, a UE with at least dual-receive and dual-transmit capabilities receives an RRC reconfiguration message from network A instructing the UE to perform a synchronous reconfiguration process, which contains an indication of activating SCG but the UE thinks Related issues involved when network B has a higher priority to avoid UE in MUSIM state from activating SCG and make the SCG state in UE and network A consistent. In the embodiment of the present disclosure, when the UE implements synchronous reconfiguration or handover, the current MCG or SCG is called the source MCG or source SCG, and the MCG or SCG to which the UE is synchronously reconfigured or handed over is called the target MCG or target SCG.

The following describes when the UE receives the RRC reconfiguration message for handover from the MN (that is, the RRC reconfiguration message contains the masterCellGroup field, and the spCellConfig field contained in the masterCellGroup field contains the reconfigurationWithSync field, that is, the synchronous reconfiguration of the MCG) Examples of operations performed.

In this embodiment, the UE receives the RRC reconfiguration message for handover from the MN. If one of the following conditions A1-A3 is met, the UE performs synchronous reconfiguration (reconfiguration with sync). For details, see the latest version of TS38.331 ;

Condition A1: The RRC reconfiguration message does not contain the configuration information of the SCG (that is, the RRC reconfiguration message does not contain the secondaryCellGroup field and the mrdc-SecondaryCellGroupConfig field).

Condition A2: The RRC reconfiguration message contains the configuration information of the SCG (that is, the RRC reconfiguration message contains the secondaryCellGroup field or the mrdc-SecondaryCellGroupConfig field), and the received RRC reconfiguration message contains the scg-State field.

Condition A3: The RRC reconfiguration message contains the configuration information of the SCG (that is, the RRC reconfiguration message contains the secondaryCellGroup field or the mrdc-SecondaryCellGroupConfig field), and the received RRC reconfiguration message does not contain the scg-State field, and the UE Not in MUSIM state.

The UE receives the RRC reconfiguration message for handover from network A (MN), if the following condition B is met:

Condition B: The RRC reconfiguration message contains SCG configuration information, and the received RRC reconfiguration message does not contain the scg-State field, and the UE is in the MUSIM state.

In one implementation, the UE indicates in the response message the information related to the MUSIM state of the UE (at this time, the UE does not perform synchronous reconfiguration, the RRC reconfiguration process ends, and optionally, the UE restores the original configuration); in In another implementation, the UE performs MCG synchronization reconfiguration and configures the SCG but does not activate or configure the SCG, and indicates in the response message information related to the MUSIM state of the UE or information indicating that the SCG has been configured but not activated, or indicates that the SCG Unconfigured information. The response message may be an RRC reconfiguration completion message RRCReconfigurationComplete.

SCG changes

When the first network (denoted as network A) and the second network (denoted as network B) are both in the RRC connected state, a UE with at least dual receiving and dual transmitting capabilities receives an RRC reconfiguration message from network A instructing the UE to perform SCG. Change the process, but the related issues involved when the UE is in the MUSIM state, to avoid the UE in the MUSIM state from activating the SCG and make the SCG state in the UE and network A consistent.

The following describes in detail how the UE receives an RRC reconfiguration message for changing the SCG from the MN (that is, the RRC reconfiguration message contains the secondaryCellGroup field or mrdc-SecondaryCellGroupConfig field, and the secondaryCellGroup field or mrdc-Second An example of operations performed when the spCellConfig field contained in the aryCellGroupConfig field contains the reconfigurationWithSync field, that is, the synchronous reconfiguration of SCG).

In this embodiment, the UE receives the RRC reconfiguration message for changing the SCG from the network A (MN). If one of the following conditions C1-C4 is met, the UE performs SCG synchronization reconfiguration (reconfiguration with sync) (also Called SCG change), see the latest version of TS38.331 for details;:

Condition C1: The received RRC reconfiguration message contains the scg-State field.

Condition C2: The received RRC reconfiguration message does not contain the scg-State field, and the UE is not in the MUSIM state.

Condition C3: The RRC message containing the RRC reconfiguration message contains the scg-State field.

Condition C4: The RRC message containing the RRC reconfiguration message does not contain the scg-State field, and the UE is not in the MUSIM state.

The UE receives the RRC reconfiguration message from the MN for changing the SCG if one of the following conditions D1-D2 is met:

Condition D1: The received RRC reconfiguration message does not contain the scg-State field, and the UE is in the MUSIM state.

Condition D2: The RRC message containing the RRC reconfiguration message does not contain the scg-State field, and the UE is in the MUSIM state.

In one embodiment, the UE indicates in the response message information related to the UE being in the MUSIM state (at this time, the UE does not perform SCG synchronization reconfiguration, the RRC reconfiguration process ends, and optionally, the UE restores the original configuration) or indicates Information related to SCG synchronization reconfiguration not being executed; in another implementation, the UE executes SCG synchronization reconfiguration according to the RRC reconfiguration message but considers that the SCG is deactivated, that is, according to the scg-State field contained in the RRC reconfiguration message. In the case where the RRC reconfiguration message is executed but the SCG is considered to be deactivated, the UE indicates in the response message relevant information that the UE is in the MUSIM state or indicates that the SCG synchronization reconfiguration has been executed but the SCG is not activated. The response message may be an RRC reconfiguration completion message RRCReconfigurationComplete. The indication information that the UE is in the MUSIM state can be indicated only in the response message sent to the MN, or only in the response message forwarded to the SN through the MN, or at the same time in the response message sent to the MN and forwarded to the SN through the MN. Indicated in the SN's response message. In another embodiment, the UE initiates SCG failure information transmission process, indicating that the UE is in the MUSIM state in the SCG failure information message.

In the embodiment of the present disclosure, the RRC message including the RRC reconfiguration message may be an RRC reconfiguration message or an RRC recovery message.

The fourth embodiment of this specification provides a method for user equipment to perform conditional synchronization reconfiguration, including: when the user equipment is in the MUSIM state, even if the user equipment is configured to need to perform conditional reconfiguration, the conditional reconfiguration is not performed. Configuration; and when the user equipment is not in the MUSIM state and the user equipment is configured to need to perform conditional reconfiguration, and the evaluation result after conditional evaluation of performing conditional reconfiguration is that the reconfiguration condition is met, conditional reconfiguration is performed.

A specific example of the fourth embodiment will be described below with reference to FIGS. 6 and 7 .

As shown in Figure 6, in S602 to S604, it is determined whether the user equipment is in the MUSIM state.

When the user equipment is not in the MUSIM state, in S606, evaluation of conditional reconfiguration is performed. And, in S608, it is determined whether the evaluation result satisfies the reconfiguration condition.

When the evaluation result is that the reconfiguration condition is met, in S610, conditional reconfiguration is performed.

When the user equipment is in the MUSIM state (Yes in S604) or does not meet the reconfiguration condition (No in S608), in S612, conditional reconfiguration is not performed. Thus, SCG activation after conditional reconfiguration is performed is avoided.

As shown in Figure 7, in S702, when the user equipment is configured to need to perform conditional reconfiguration, evaluation of conditional reconfiguration is performed. And, in S704, it is determined whether the evaluation result of the conditional reconfiguration satisfies the reconfiguration condition.

When the evaluation result of the conditional reconfiguration is that the reconfiguration condition is met, in S708, it is determined whether the user equipment is in the MUSIM state.

If the user equipment is in the MUSIM state, then in S712, conditional reconfiguration is not performed. Thus, SCG activation after conditional reconfiguration is performed is avoided. If the user equipment is not in the MUSIM state, then in S710, conditional reconfiguration is performed.

In addition, when the reconfiguration conditions are not met, conditional reconfiguration is not performed.

In this embodiment, when the user equipment is instructed to perform conditional reconfiguration and the user equipment is in the MUSIM state, a message indicating that the user equipment is in the MUSIM state may be sent to the network.

In the case where the user equipment is configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment, if it is determined that the user equipment is in the MUSIM state, even if the user equipment is configured to need to perform conditional reconfiguration , nor perform conditional reconfiguration corresponding to the conditional reconfiguration information. This is to avoid activating the secondary serving cell group after performing conditional reconfiguration.

Specific examples of the fourth embodiment will be described below.

Conditional synchronization reconfiguration/conditional PSCell increase/conditional SCG change (CHO/CPA/CPC)

When a UE with at least dual reception and dual transmission capabilities is in the RRC connected state of both the first network (denoted as network A) and the second network (denoted as network B), the UE is configured with CHO, CPA or CPC. When CHO or CPA Or the CPC conditions are met, but the related issues involved when the UE is in the MUSIM state are to prevent the UE in the MUSIM state from activating the SCG and make the SCG state in the UE and network A consistent. The condition reconfiguration described in the following embodiments includes: CHO, CPA, and CPC.

In one embodiment, the UE stops evaluation of conditional reconfiguration when the UE is in the MUSIM state or is configured by Network A to enter (or be in) the MUSIM state. In other words, when the UE is in the MUSIM state or is configured by Network A to enter (or be in) the MUSIM state, if conditional reconfiguration is configured, the UE stops the evaluation of conditional reconfiguration. This is because if the UE performs evaluation of conditional reconfiguration, when the UE detects that the condition is met, it needs to perform CHO or CPA, both of which may activate the SCG. When the UE exits the MUSIM state (or the UE is not in the MUSIM state or sends a request to exit the MUSIM state to Network A), if conditional reconfiguration is configured, the UE starts the evaluation of conditional reconfiguration. Optionally, only when the RRC reconfiguration message for executing CHO contains SCG configuration information but does not contain scg-State, the evaluation of CHO's conditional reconfiguration will be stopped.

In one embodiment, if the UE is configured with conditional reconfiguration and the evaluation conditions of the conditional reconfiguration are met, and if the UE is not in the MUSIM state, the conditional reconfiguration execution process is started. If the UE is configured with conditional reconfiguration and the evaluation conditions for conditional reconfiguration are met, if the UE In the MUSIM state, the UE indicates to Network A the information related to the UE being in the MUSIM state or performs conditional reconfiguration when the UE exits the MUSIM state. Specifically, the evaluation condition for conditional reconfiguration is satisfied when, for each condReconfigID in the variable VarConditionalReconfig, the events associated with all measIds in the condTriggerConfig of the target candidate cell in the saved condRRCReconfig are satisfied. Optionally, when the evaluation conditions of CHO are met, if the RRC reconfiguration message used to perform CHO contains SCG configuration information, conditional reconfiguration will be performed when the UE exits the MUSIM state or indicates to network A that the UE is in the MUSIM state. Information.

The fifth embodiment will be described below with reference to FIGS. 8 to 10 .

As shown in Figure 8, in S802, a secondary serving cell activation indication from the first network is received.

When receiving the secondary serving cell activation indication from the first network, in S804, it is determined whether the user equipment is in the MUSIM state. Here, the secondary serving cell indicated by the secondary serving cell activation indication may use inter-frequency carrier aggregation to transmit data with other activated secondary serving cells or special serving cells in the first network where the user equipment is located.

When the user equipment is in the MUSIM state, in S806, the secondary serving cell activation indicated by the secondary serving cell activation indication is not performed, and an indication message indicating that the user equipment is in the MUSIM state is sent to the first network.

When the user equipment is not in the MUSIM state, in S808, the secondary serving cell activation indicated by the secondary serving cell activation indication is performed.

The secondary serving cell activation indication may be included in the RRC reconfiguration message, and the RRC reconfiguration message may include additional configuration information for adding the secondary serving cell. At this time, you can refer to the process in Figure 9 to add a secondary serving cell.

As shown in Figure 9, in S902, the corresponding secondary serving cell is added based on the added configuration information.

At S904, it is determined whether the user equipment is in the MUSIM state.

When the user equipment is in the MUSIM state, in S906, the added secondary serving cell is placed in an inactive state. When the user equipment is not in the MUSIM state, in S908, the added secondary serving cell is made active.

The RRC reconfiguration message may also include modified configuration information used to modify the secondary serving cell. In this case, the secondary serving cell may be modified with reference to the process of FIG. 10 .

As shown in Figure 10, in S1002, the corresponding secondary serving cell is modified based on the modified configuration information. In S1004, it is determined whether the user equipment is in the MUSIM state.

When the user equipment is in the MUSIM state, in S1006, the modified secondary serving cell is made inactive. When the user equipment is not in the MUSIM state, in S1008, the modified secondary serving cell is made active.

In one example, when the currently available resources of the user equipment are sufficient to perform the secondary serving cell activation indicated by the secondary serving cell activation indication, the secondary serving cell activation may be performed regardless of whether the user equipment is in MUSIM mode.

Furthermore, in one example, in the case where the user equipment is configured by the first network to allow communication with the first network using part of the hardware capabilities of the user equipment, the operation of determining whether the user equipment is in the MUSIM state is performed. Where the user equipment is configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment, or where the first network is not configured to allow communication with the first network using only part of the hardware capabilities of the user equipment In the case of communication, when receiving a secondary serving cell activation indication from the first network, activation of the secondary serving cell corresponding to the secondary serving cell activation indication is performed.

Specific examples of the fifth embodiment will be described below.

The following considers the SCell configuration and activation scenario in the case of carrier aggregation CA.

When a UE with at least dual reception and dual transmission capabilities is in the RRC connected state of both the first network (denoted as network A) and the second network (denoted as network B), the UE receives an instruction to activate the SCell from network A, but is in Related issues involved in the MUSIM state to prevent the UE in the MUSIM state from activating SCell and to make the SCell state consistent between the UE and the network.

The UE working under carrier aggregation receives the instruction to activate the SCell from the network. If the UE is not in the MUSIM state, the UE configures the lower layer to think that the SCell is in the active state or activates the SCell; if the UE is in the MUSIM state, the UE sends the instruction information to the network. Information indicating that the UE is in the MUSIM state or the SCell is not activated (the indication information may include specific cell identification information), in this case, the UE does not activate the SCell. It should be noted that the scenario considered here is that the network indicates that the activated SCell and the UE are currently in the active state. The SCell or PSCell uses inter-frequency carrier aggregation. In other words, the UE capabilities or resources of the UE currently in the MUSIM state cannot support the activation of this/these SCells or even if these SCells are activated, the UE cannot receive or send data from these SCells due to limited UE capabilities. .

The indication to activate SCell may be the sCellState field contained in the RRC reconfiguration message, or it may be SCell activation/deactivation media access control MAC control element CE or enhanced SCell activation/deactivation MAC CE.

The UE receives the RRC reconfiguration message from the base station, which contains the CellGroupConfig field (the field can be included in the masterCellGroup field). Based on the received CellGroupConfig field, the UE performs the following operations:

If the CellGroupConfig field contains the sCellToAddModList field, SCell is added or modified. The SCell addition or modification includes the following operations:

For each sCellIndex value contained in sCellToAddModList that is not part of the current UE configuration (this is the case for SCell additions) do at least one of the following:

(1) Add SCell corresponding to sCellIndex according to sCellConfigCommon and sCellConfigDedicated.

(2) If sCellState is included (that is, SCell is configured as an active state), and the UE is not in the MUSIM state, configure the lower layer to consider the SCell to be in an active state. If sCellState is included but the UE is in the MUSIM state, or sCellState is not included (that is, SCell is configured as an inactive state), the lower layer of the configuration considers the SCell to be in an inactive state.

For each sCellIndex value contained in the sCellToAddModList that is part of the current UE configuration (this is the case for SCell modification) do at least one of the following:

(1) Modify the SCG configuration according to sCellConfigDedicated.

(2) If sCellToAddModList is received from an RRC reconfiguration message containing reconfigurationWithSync, or received from an RRC reconfiguration message containing reconfigurationWithSync and the RRC reconfiguration message is included in another RRC reconfiguration message:

If it contains sCellState and the UE is not in the MUSIM state, configure the lower layer to think that SCell is in the active state.

If it contains sCellState but the UE is in the MUSIM state or it does not contain sCellState, configure the lower layer to consider SCell to be in an inactive state.

The UE indicates in the response message that the UE is in the MUSIM state or indicates SCel. l Inactive related information (optional, this operation is only performed when the SCell is configured in an inactive state but the UE is in MUSIM). The response message may be an RRC reconfiguration completion message RRCReconfigurationComplete.

In one embodiment, if the UE receives an RRC message from the network to configure and activate an SCell with a different frequency than the PSCell, the UE does not configure the SCell and sends indication information to the network that the UE is in the MUSIM state or the SCell is configured. Indication information, optional, containing the unconfigured SCell identifier. In other words, if the UE receives an RRC message from the network to configure (or activate) an SCell with the same frequency as the PSCell, the SCell is configured (or activated) at the UE.

Consider the following under carrier aggregation, the UE receives SCell activation/deactivation MAC C from the base station E or enhanced SCell activation/deactivation MAC CE scenario

For each configured SCell, the MAC entity performs the following operations:

If the SCell is configured in the activated state during SCell configuration, that is, the SCell is configured with an sCellState with a value set to "activated" (that is, the value used to indicate the activation of the SCell), or an SCell activation/deactivation MAC is received. CE or enhanced SCell activation/deactivation MAC CE to activate the SCell, perform the following operations:

(1) If the UE is not in the MUSIM state, further, if (A) if the SCell is deactivated before receiving an SCell activation/deactivation MAC CE or an enhanced SCell activation/deactivation MAC CE, or (B) If the configured sCellState of the SCell is set to "activated" during SCell configuration, perform at least one of the following operations:

(a) If firstActiveDownlinkBWP-Id is not set as dormant BWP, activate SCell; otherwise, stop bwp-InactivaityTImer of this serving cell;

(b) Activate the downlink partial bandwidth BWP and uplink BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id.

(2) Otherwise (that is, the UE is in the MUSIM state), information indicating that the UE is in the MUSIM state or related information indicating that the SCell is not activated is provided to the network, and the SCell is not activated at this time. Specifically, a MAC CE can be defined or an existing MAC CE can be reused, and the MAC CE carries information indicating that the UE is in the MUSIM state or related information indicating that the SCell has not been activated.

In this disclosure, deactivation and inactivation have the same meaning and can be used interchangeably.

As shown in Figure 11, at S1102, it is determined whether there is uplink data that needs to be transmitted through the SCG DRB in the first network.

When the user equipment has uplink data that needs to be transmitted through the SCG DRB in the first network, it is determined whether the predetermined conditions are met. That is, in S1104, it is determined whether the secondary serving cell group corresponding to the SCG DRB is in an inactive state. If the secondary serving cell group is in the inactive state, in S1106, it is determined whether the user equipment is in the MUSIM state.

If the above predetermined conditions are met, then in S1110, the uplink data indication information of the SCG DRB is sent to the first network. The uplink data indication information is used to indicate to the first network that uplink data for the SCG DRB has arrived. The "arrival" here is relative to the transceiver module of the user equipment (for example, the user equipment determines that there is uplink data for the SCG DRB to be sent for the RRC entity of this RRC connection). After receiving the uplink data indication information, the first network may configure corresponding MCG resources for the first network for transmitting uplink data.

If the SCG is in the active state (No in S1104), then in S1108, the uplink data is transmitted through the active SCG.

When the secondary serving cell group corresponding to the SCG DRB is in the inactive state, but the user equipment is not in the MUSIM state, that is, when S1104 is determined to be yes but S1106 is determined to be no, in S1112, a signal is sent to the first network indicating that there is a need to pass An indication message for uplink data transmitted by SCG DRB. This indication message is used to indicate that the UE has uplink data for the deactivated SCG. When receiving the indication message, the first network may configure an activated SCG for the user equipment for transmitting the above uplink data.

The uplink data indication information may include, for example, the identification information of the SCG DRB for the uplink data or the logical channel identification of the SCG RLC entity.

In one example, in addition to the conditions shown in S1104 and S1106, the predetermined conditions may also include any of the following: the user equipment has not sent uplink data indication information to the network for uplink data; the user equipment enters the current After the MUSIM state, no uplink data indication information has been sent to the network for the uplink data; the prohibition timer used to prohibit sending the uplink data indication information is not in the running state, and the prohibition timer is not sending the uplink data indication. information is activated. The prohibition timer is used to limit the frequency of sending uplink data indication information to avoid sending information too frequently.

In one example, the first network may instruct the user equipment to exit the MUSIM state through a MUSIM state release indication. When the user equipment receives the MUSIM state release instruction, it can choose whether to exit the MUSIM state according to its own preferences. Description will be made below with reference to FIG. 12 .

At S1202, a MUSIM state release indication is received from the first network.

When receiving the MUSIM state release instruction, in S1204, it is determined whether the MUSIM state can be exited. In other words, in S1204, it is determined whether the current user equipment prefers to exit the MUSIM state.

If it is determined to be yes in S1204, then in S1206, exit the MUSIM state in response to the MUSIM state release indication, so that the corresponding secondary serving cell group can be activated in the first network. And, then in S1208, a response message indicating that the MUSIM state has been exited is sent to the first network.

When the user equipment determines that it cannot exit the MUSIM state (No in S1204), then in S1210, it sends a request message indicating that the MUSIM state is maintained to the first network. The request message may include information indicating that the user equipment is still in the MUSIM state. For example, when the user equipment believes that there is more urgent data that needs to be transmitted in a second network that is different from the first network or that the data transmitted in the second network has a higher priority, it can be determined that the current preference is not to exit the MUSIM state. .

Furthermore, in one example, if whether the user equipment is allowed to use part of its hardware capabilities to communicate with the first network is configured by the first network, then the user equipment is configured by the first network to allow only part of the hardware capabilities of the user equipment to be used to communicate with the first network. In the case of communication over a network, the predetermined condition includes that the user equipment is in the MUSIM state. When the user equipment is configured by the first network to not allow communication with the first network using only part of the hardware capabilities of the user equipment or is not configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment. If the user equipment prefers to maintain the RRC connection with the second network, the RRC connection with the first network is released.

Specific examples of the sixth embodiment will be described in detail below.

The following describes the scenario when the uplink data of the SCG DRB arrives but the UE is in the MUSIM state.

The UE in the MUSIM state is in the dual connection state in network A, and the SCG is deactivated. When the UE has uplink data for the DRB that does not carry data carried by the MCG RLC, and the UE has not yet sent the uplink data for the DRB to the network. Over indication (the condition can be replaced by: after the UE last entered the MUSIM state or the UE changed the MUSIM state last time, it has not sent an indication to the network for the arrival of the uplink data of the DRB, or the UE has not sent an indication to the network for the DRB before that). The arrival of the uplink data for the DRB has sent an indication to the network). If the prohibition timer is not running (this condition is optional), the UE indicates to the network A the arrival of the uplink data for the DRB. The indication may include the The DRB identifier of the DRB or the corresponding logical channel identifier, optionally, starts the prohibition timer.

Specifically, if the SCG is deactivated and the UE has uplink data to be sent for the SCG RLC entity but before that the UE has no uplink data to send for the SCG RLC entity (the condition can be replaced by: in the UE's latest Entering the MUSIM state or the UE has not sent an indication to the network for the uplink data arrival of the SCG RLC entity since the last change of the MUSIM state, or the UE has not sent an indication to the network for the uplink data arrival of the SCG RLC entity before this. ), and the prohibition timer is not running (this condition is optional), then start transmitting the UE assistance information message to indicate that the UE has any RLC-BearerConfig for which the DRB identity (DRB-Identity) is not included in the CellGroupConfig associated with the MCG. The DRB's uplink data is to be sent and, optionally, the prohibition timer is started.

The following describes the process of transmitting UE assistance information messages:

If the transmission of the UE auxiliary information message is initiated to provide the UE with instructions about the uplink data of the inactive SCG, further, if the UE is in the MUSIM state, the UE auxiliary information message contains the identification of the SCG DRB to which the uplink data is to be sent or The logical channel identifier of the SCG RLC entity that has uplink data to be sent; otherwise (the UE is not in the MUSIM state), the UE auxiliary information message contains a link to indicate that the UE has uplink data to be sent for the SCG RLC entity or the deactivated SCG. uplinkData field.

When the SCG is deactivated and the UE is not in the MUSIM state, the UE only needs to The assistance information message contains the uplinkData field indicating that the UE has uplink data to be sent for the SCG RLC entity. After receiving this message, the network can activate the SCG. However, when the SCG is deactivated and the UE is in the MUSIM state, the UE needs to include in the UE assistance information message the identifier of the SCG DRB or the identifier of the corresponding logical channel indicating that the UE has uplink data for the SCG RLC entity to be sent. The network After receiving this message, the SCG DRB can be reconfigured as an MCG DRB or a detached DRB (that is, an MCG RLC bearer is added to the SCG DRB), thereby reducing the transmission delay of the SCG DRB.

In this disclosure, the data radio bearer DRB without MCG RLC bearer refers to the SCG DRB or SCG RLC entity, that is, the associated RLC bearer is only a DRB in the SCG, that is, the DRB that is only configured with the SCG RLC bearer, that is, the DRB- Identity is not included in the DRB in any RLC-BearerConfig in the associated MCG's CellGroupConfig. These expressions are used interchangeably. Furthermore, in the embodiment of the present disclosure, the operations of starting the prohibition timer and the UE starting the UE assistance information message to indicate the arrival of the uplink data of the DRB may be exchanged. RLC bearer and RLC entity are used interchangeably.

Consider the following scenario when the SCG DRB downlink data arrives but the UE is in the MUSIM state.

When the UE is in the MUSIM state, if network A needs to perform high-priority services or emergency services in the SCG, for example, downlink data for the SCG DRB arrives in network A, network A needs to indicate relevant information to the UE so that the UE can make decisions based on the indication information. Whether to release the RRC connection with another network or release the UE capability restrictions in network A.

Specifically, the UE receives an RRC message from the network, such as an RRC reconfiguration message, which contains a field to instruct the UE to exit the MUSIM state or instruct the UE to release UE capability restrictions in network A. The UE may indicate in the response message that the UE exits or maintains the MUSIM state or the UE releases or maintains (or requests) the capability restrictions in network A. The response message may be an RRC reconfiguration complete message or a UE assistance information message.

In S1302, an RRC recovery request message requesting to recover the RRC connection with the first network is sent to the first network.

Then, at S1304, an RRC recovery message from the first network is received.

Next, at S1306, it is determined whether the received RRC recovery message indicates activation of the secondary serving cell group.

When the RRC recovery message indicates activation of the secondary serving cell group, in S1308, it is determined whether the user prefers not to activate the secondary serving cell group.

If the user equipment prefers not to activate the secondary serving cell group, then in S1310, indication information indicating that the user equipment prefers not to activate the secondary serving cell group is sent to the first network. In one example, the indication information also includes information indicating any of the following: the new secondary serving cell group indicated by the RRC recovery message has not been configured; the new secondary serving cell group indicated by the RRC recovery message has been configured but has not been configured. Activated; the existing secondary serving cell group indicated by the RRC recovery message has not been restored; the existing secondary serving cell group indicated by the RRC recovery message has been restored but has not been activated.

If the RRC recovery message does not indicate activation of the secondary serving cell group, or the RRC recovery message indicates activation of the secondary serving cell group but the user equipment does not prefer not to activate the secondary serving cell group, then in S1312, recovery is performed according to the received RRC recovery message. RRC connection to the first network.

In one example, if the user equipment prefers not to activate the secondary serving cell group, any of the following may be performed: when the RRC recovery message indicates that the new secondary serving cell group is configured, configure the new secondary serving cell according to the RRC recovery message but Do not activate the new secondary serving cell group; when the RRC recovery message indicates to configure the new secondary serving cell group, do not perform the new secondary serving cell group configuration indicated by the RRC recovery message; when the RRC recovery message indicates to restore the existing secondary serving cell group, Do not perform recovery of the existing secondary serving cell group indicated by the RRC recovery message; when the RRC recovery message indicates recovery of the existing secondary serving cell group, recover the existing secondary serving cell group indicated by the RRC recovery message, but do not activate the existing secondary serving cell group. Auxiliary service community group.

In one example, inter-frequency carrier aggregation is used to transmit data between the secondary serving cell indicated by the RRC recovery message and other active secondary serving cells or primary serving cells PCell where the user equipment is located in the first network. In this case, when the RRC recovery message indicates that the activated secondary serving cell and the primary serving cell operate in different frequency bands, if the user equipment prefers not to activate the secondary serving cell, a message indicating that the user equipment prefers not to activate the secondary service is sent to the first network. Instructions for the neighborhood.

In one example, if the first network configures whether to allow the use of part of the hardware capabilities of the user equipment to communicate with the first network, then the user equipment is configured by the first network to allow only the use of In the case where part of the hardware capabilities of the user equipment communicates with the first network, when the RRC recovery message indicates that the secondary serving cell group is activated, if the user equipment prefers not to activate the secondary serving cell group, it may send a message to the first network indicating that the user equipment Indication information indicating that the device prefers not to activate the secondary serving cell group.

As shown in Figure 14, it is determined whether the user prefers not to activate the secondary serving cell group.

If the user equipment prefers not to activate the secondary serving cell group, then in S1404, an RRC recovery request message requesting to restore the RRC connection in the first network is sent to the first network. The RRC recovery request message includes the description indicating that the user equipment prefers not to activate the secondary serving cell group. Instruction information of the secondary serving cell group. On the contrary, if the user equipment does not prefer not to activate the secondary serving cell group, then in S1406, send an RRC recovery request message that does not include the above indication information. As an example, the situation in which the user equipment prefers not to activate the secondary serving cell group may include the user equipment being in the MUSIM state.

In one example, if the first network configures whether to allow the use of part of the hardware capabilities of the user equipment to communicate with the first network, then the user equipment is configured by the first network to allow the use of only part of the hardware capabilities of the user equipment to communicate with the first network. In the case of communication, if the user equipment prefers not to activate the secondary serving cell group, it may send an RRC recovery request message including indication information indicating that the user equipment prefers not to activate the secondary serving cell group to the first network.

Then, at S1408, an RRC recovery message from the first network is received.

And, in S1410, based on the RRC recovery message, the RRC connection with the first network is restored.

In one example, if it is determined according to the context information saved by the user equipment that the secondary serving cell group needs to be activated when entering the RRC connected state in the first network, and the user equipment does not prefer to activate the secondary serving cell group, then the user equipment will restore the secondary serving cell group when the RRC is restored. The request message includes indication information indicating that the user equipment does not prefer to activate the secondary serving cell group. This is to avoid the first network being configured to activate the secondary serving cell group when providing the user equipment with the configuration for restoring the RRC connection.

In the case of sending an RRC recovery request message requesting recovery of the RRC connection in the first network to the first network, if it is determined that the user equipment is in a dual connection state in the first network, releasing the information about the Configuration information of dual connection status.

Specific examples of the seventh and eighth embodiments will be described in detail below.

Consider the following scenario where a UE in the MUSIM state requests to restore the RRC connection in network A.

The UE is in the RRC inactive state in network A (that is, the RRC connection is suspended), and is in the RRC connected state in network B. The UE sends an RRC recovery request RRCResumeRuest message to Network A, requesting to restore the RRC connection in Network A. After receiving the recovery request message, network A may send an RRC recovery message to the UE to recover the suspended RRC connection. In the RRC recovery message, it may be indicated whether to activate the SCG. If the RRC recovery message indicates activation of the SCG, since the UE is in the MUSIM state, if the UE believes that network B has a higher priority, the RRC connection with network B will not be released, resulting in the UE being unable to communicate with the SCG in network A. However, Network A considers that the SCG has been activated and performs data transmission on the SCG. At this time, the UE does not have the ability to receive the data transmitted on the SCG, which will result in a waste of resources of Network A.

Examples are provided below to address this issue.

In one embodiment, if the UE is in the MUSIM state or the UE prefers not to activate the SCG (or prefers the SCG to be in an inactive state), the RRC recovery request message contains an indication information to indicate that the UE is in the MUSIM state or the UE prefers not to activate the SCG. Activate the SCG or prefer the SCG to be inactive.

Specifically, the UE sets the content of the RRC recovery request message as follows: if the UE is in the MUSIM state, the RRC recovery request message contains indication information indicating that the UE is in the MUSIM state or indicates whether to prefer activating the SCG. Specifically, a new field may be defined for indication information indicating that the UE is in the MUSIM state or prefers the SCG to be inactive or prefers the SCG to be in the inactive state. If the UE is in the MUSIM state or the UE prefers not to activate the SCG or prefers the SCG to be in an inactive state, the field is included in the RRC recovery request message; otherwise, the field is not included in the RRC recovery request message. Optionally, only if the SCG is in the active state in the context saved by the UE or the SCG is in the active state before the UE enters the RRC inactive state, the UE includes in the RRC recovery request message that the UE is in the MUSIM state or indicates a preference to deactivate the SCG or to prefer the SCG. Inactive indication.

The UE submits the RRC recovery request message for transmission to the lower layer.

It should be noted that when the embodiment is applied to a carrier aggregation scenario, the indication information is used to indicate that the UE is in the MUSIM state or the UE prefers not to activate the SCell or the UE prefers not to activate the SCell with a different frequency than the PCell. Optionally, the indication information is included in the RRC recovery request message only when there is an SCell with a different frequency than the PCell in the configured SCell.

As a modification of the above embodiment, indication information is included in the RRC recovery request message only when the UE prefers to activate the SCG or the preferred SCG is in the active state, and is used to indicate that the UE prefers to activate the SCG or the preferred SCG is in the active state.

In one embodiment, if the UE receives the RRC recovery RRCResume message from the base station, which does not contain the scg-State instruction configuring the SCG to be in the inactive state, and if the UE is in the MUSIM state, the UE does not activate the SCG. Optionally, the UE sends indication information to the network to indicate that the UE is in the MUSIM state or the SCG is not activated or the SCG is not configured. The indication information may be included in the RRC recovery completion message.

It should be noted that in this embodiment, if the UE is in the MUSIM state, the UE may configure or restore the SCG according to the received RRC recovery message, or may not configure or restore the SCG. Specifically, if the RRC recovery message contains restoreSCG and the UE is not in the MUSIM state, the UE restores mrdc-SecondaryCellGroup from the UE inactive AS context (context). In other words, if the RRC recovery message contains restoreSCG and the UE is in the MUSIM state, or the RRC recovery message does not contain restoreSCG, the MR-DC related configuration is released from the UE inactive AS context.

The restoreSCG field is used to instruct the UE to restore (restore) the SCG configuration from the UE inactive AS context.

In one embodiment, the UE sends an RRC recovery request message to Network A and receives an RRC recovery message from the network. If the UE has MUSIM capability or the UE is configured with multi-SIM (the UE has reported its multi-SIM capability to the network), the SCG configured in the RRC recovery message is in an inactive state, that is, the RRC recovery message contains scg-State. field. In other words, for a UE configured with MUSIM, only an inactive SCG or no SCG can be configured when the RRC connection is restored.

In one embodiment, when the UE initiates the RRC connection recovery process, if the UE is in NR-DC and the UE is in the MUSIM state, the MR-DC related configuration is released from the UE inactive AS context.

In one embodiment, if the UE receives the RRC recovery message from the base station, which contains the indication sCellState that the SCell configured with a different frequency than the PCell is in the active state, and if the UE is in the MUSIM state, the UE does not activate the SCell or configures but does not Activate the SCell or do not configure the SCell. Optionally, the UE sends indication information to the network to instruct the UE to In MUSIM state or SCell is not activated or SCell is not configured or SCell is configured but not activated. The indication information may be an identifier of an unactivated or unconfigured SCell, and the indication information may be included in an RRC recovery completion message.

In this embodiment of the present disclosure, releasing MR-DC related configurations from the UE inactive AS context includes: releasing SRB3 (for the situation where SRB3 has been established), releasing SCG-associated measConfig, releasing SCG configuration, etc.

Figure 15 is a block diagram of user equipment provided in this specification. As shown in Figure 15, the user equipment UE40 includes a processor 151 and a memory 152. The processor 151 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 42 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Memory 152 stores program instructions. When this instruction is executed by the processor 151, it can execute the above method executed by the user equipment as described in detail in the present invention.

In the embodiments of the present disclosure, if it is necessary to determine whether multiple conditions are met before performing certain operations or operations, the embodiment obtained by exchanging the execution order of these judgment conditions is also within the scope of protection of the present disclosure.

The program running on the device according to the present invention may be a program that causes the computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU). The program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

Computer-executable instructions or programs for implementing the functions of various embodiments of the present disclosure may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute these programs. The so-called "computer system" here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices). "Computer-readable storage medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for short-term dynamic storage of a program, or any other computer-readable medium. recording media.

Various features or functional modules of the devices used in the above-described embodiments may be implemented or performed by circuits (eg, single-chip or multi-chip integrated circuits). Circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above. A general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuit may be a digital circuit or an analog circuit. When new integrated circuit technologies emerge to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

Furthermore, the present disclosure is not limited to the above-described embodiment. Although various examples of the embodiments have been described, the disclosure is not limited thereto. Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

As above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-described embodiment, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. Furthermore, components having the same effect described in the above embodiments may be substituted for each other.

Claims

A method for performing synchronous reconfiguration by user equipment, including:

Receive an RRC reconfiguration message from the first network;

When the RRC reconfiguration message includes configuration information for the secondary serving cell group, if the user equipment is in the MUSIM state, the secondary serving cell group configuration including making the secondary serving cell group an active state is not performed, and the user equipment is sent to the MUSIM state. The network sends a response message indicating that the user equipment is in the MUSIM state.
The method according to claim 1, wherein not performing synchronous reconfiguration including making the secondary serving cell group an active state includes:

Do not perform the secondary serving cell group configuration indicated by the RRC reconfiguration message; or

The secondary serving cell group configuration is performed, but the secondary serving cell group is not made into an active state.
The method according to claim 1, wherein the RRC reconfiguration message includes synchronization reconfiguration information, and when any of the following conditions is met, the user equipment performs synchronization corresponding to the synchronization reconfiguration information. Reconfiguration:

The RRC reconfiguration message does not include the configuration information for the secondary serving cell group;

The RRC reconfiguration message includes the configuration information for the secondary serving cell group and the configuration information is used to make the secondary serving cell group in an inactive state;

The configuration information for the secondary serving cell group is used to make the secondary serving cell group an active state, and the user equipment is not in the USIM state.
The method according to claim 1, wherein the configuration information for the secondary serving cell group is configuration information for secondary serving cell group change, and the secondary serving cell group configuration indicated by the RRC reconfiguration message includes the target primary serving cell group. The configuration of the auxiliary community,

or

The configuration information for the secondary serving cell group is the configuration information used to change the primary and secondary cells where the user equipment is currently located. The secondary serving cell configuration indicated by the RRC reconfiguration message includes the configuration of the secondary serving cell where the user equipment is currently located. Change configuration of cell groups.
A method for performing conditional synchronous reconfiguration by user equipment, including:

When the user equipment is in the MUSIM state, even if the user equipment is configured to need to perform conditional reconfiguration, the conditional reconfiguration is not performed; and

When the user equipment is not in the MUSIM state and the user equipment is configured to need to perform conditional reconfiguration, and the evaluation result after performing conditional reconfiguration is that the reconfiguration condition is met, the conditional reconfiguration is performed.
The method according to claim 5, wherein, in the case where the user equipment is configured to need to perform conditional reconfiguration, the method further includes:

Determine whether the user equipment is in the MUSIM state; when the user equipment is not in the MUSIM state, perform an evaluation of conditional reconfiguration; and when the evaluation result of the conditional reconfiguration is that the reconfiguration condition is met, perform the conditional reconfiguration. configuration,

or

When the user equipment is configured to need to perform conditional reconfiguration, perform an evaluation of the conditional reconfiguration; when the evaluation result of the conditional reconfiguration is that the reconfiguration condition is met, determine whether the user equipment is in the MUSIM state; if the If the user equipment is in the MUSIM state, conditional reconfiguration is not performed; and if the user equipment is not in the MUSIM state, conditional reconfiguration is performed.
The method of claim 5, further comprising:

When the user equipment is instructed to perform conditional reconfiguration and the user equipment is in the MUSIM state, a message indicating that the user equipment is in the MUSIM state is sent to the network.
The method according to any one of claims 1 to 7, wherein when the user equipment is in the MUSIM state, even if the user equipment is configured to need to perform conditional reconfiguration, the conditional reconfiguration will not be performed. The conditional reconfiguration corresponding to the information includes:

In the case where the user equipment is configured by the first network to allow communication with the first network using only part of the hardware capabilities of the user equipment, when the user equipment is in the MUSIM state, even if the user equipment The device is configured to require conditional reconfiguration, nor Execute conditional reconfiguration corresponding to the conditional reconfiguration information.
The method according to any one of claims 1 to 7, wherein determining whether the user equipment is in the MUSIM state includes:

When any of the following conditions is met, the user equipment is determined to be in the MUSIM state:

The user equipment is in an RRC connected state in a second network different from the first network;

The user equipment performs uplink data transmission or downlink data transmission in the second network;

The secondary serving cell group where the user equipment is located in the first network cannot be activated;

The user equipment prefers not to activate the secondary serving cell group in the first network;

The user equipment is in a user equipment capability limited state in the first network; the secondary serving cell group where the user equipment is located in the first network cannot be configured;

Part of the hardware functions of the user equipment are occupied and cannot be used for data transmission of the user equipment in the first network.
A user device including:

processor; and

memory, which stores instructions,

wherein the instructions, when executed by the processor, perform a method according to any one of claims 1 to 9.