WO2024008071A1 - 由用户设备执行的用于恢复rrc连接的方法及用户设备 - Google Patents

由用户设备执行的用于恢复rrc连接的方法及用户设备 Download PDF

Info

Publication number
WO2024008071A1
WO2024008071A1 PCT/CN2023/105702 CN2023105702W WO2024008071A1 WO 2024008071 A1 WO2024008071 A1 WO 2024008071A1 CN 2023105702 W CN2023105702 W CN 2023105702W WO 2024008071 A1 WO2024008071 A1 WO 2024008071A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
serving cell
user equipment
secondary serving
rrc
Prior art date
Application number
PCT/CN2023/105702
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Publication of WO2024008071A1 publication Critical patent/WO2024008071A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present invention relates to the field of wireless communication technology, and specifically relates to a method executed by user equipment for restoring an RRC connection and the user equipment.
  • 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.
  • the UE 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.
  • Non-Patent Document: RP-193263: New WID: Support of Multi-SIM devices in Rel-17 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).
  • 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.
  • a method for resuming an RRC connection performed by a user equipment including: sending an RRC resumption request message to a first network requesting resumption of the RRC connection in the first network; receiving from RRC recovery message of the first network; when the RRC recovery message indicates activation of the secondary serving cell group, if the user equipment prefers not to activate the secondary serving cell group, then sending an indication to the first network that the user equipment It is preferred not to activate the indication information of the secondary serving cell group.
  • a method for resuming an RRC connection performed by a user equipment including: sending an RRC resumption request message to a first network requesting resumption of the RRC connection in the first network, if If the user equipment prefers not to activate the secondary serving cell group, the RRC recovery request message includes indication information indicating that the user equipment prefers not to activate the secondary serving cell group; receive the RRC recovery message from the first network; The RRC connection in the first network is restored based on the RRC restoration message.
  • Figure 1 is a schematic diagram for an example of a MUSIM capable user equipment mentioned in this specification.
  • FIG. 2 is an exemplary flowchart for illustrating a method performed by a user equipment provided in the first embodiment of this specification.
  • 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.
  • 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.
  • 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.
  • NR user plane and control plane protocol stacks NR user plane and control plane protocol terminations
  • 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.
  • a capable UE is configured to use resources provided by two network nodes connected via a non-ideal backhaul.
  • 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.
  • MCG Master Cell Group
  • 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.
  • 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.
  • SCG secondary serving cell group
  • the SCG contains at least one primary serving cell, which is called PSCell (Primary Second Cell).
  • PSCell Primary Second Cell
  • the UE 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.
  • 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.
  • 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 mrdc-SecondaryCellGroup is configured nr-SCG set.
  • MR-DC Multi-Radio Dual Connectivity, multi-wireless dual connectivity, including (NG)EN-DC, NE-DC, NR-DC.
  • network or network node
  • base station or base station node
  • 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.
  • 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.
  • 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 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.
  • SIM A of the UE is in the RRC connected state in network A
  • 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.
  • SIM B needs to establish an RRC connection with network B
  • one of the radio frequency links needs to be switched to SIM B.
  • 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.
  • 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 masterCellGroup field is used to configure the master cell group MCG.
  • the spCellConfig field contains the SpCell of the corresponding cell group (that is, the PCell or SC of the MCG G's PSCell) parameters.
  • 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.
  • BFD Beam Failure Detection
  • RLM Radio Link Monitoring
  • 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.
  • the mrdc-SecondaryCellGroup field contains the RRCReconfiguration message generated entirely by the SN gNB.
  • the RRCReconfiguration message generated by the SN gNB The message can contain the 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.
  • 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 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.
  • firstActiveUplinkBWP-Id 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.
  • the network 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 RRCReconfiguration).
  • 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 RRCResumeRequestl is used to request to resume a suspended RRC connection or to perform a RAN-based Notification Area (RNA) update.
  • the UE may choose to request to resume an RRC connection with RRCResumeRequest or RRCResumeRequestl 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.
  • 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.
  • 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 inactive SCG does not transmit SRS on the PSCell and does not report the CS of the PSCell. I. Do not transmit UL-SCH on PSCell, do not transmit PUCCH on PSCell, etc.
  • 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.
  • the UE performs data transmission with two network nodes, MN and SN, the UE only establishes an RRC connection with the MN.
  • MN network nodes
  • SN network nodes
  • the UE only establishes an RRC connection with the MN.
  • MUSIM MUSIM
  • the UE can establish RRC connections with the network through each SIM card.
  • FIG. 1 is a schematic diagram of a UE with MUSIM capability in dual connectivity in network A.
  • 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)
  • the UE is configured with dual connectivity by network A.
  • network A is MN
  • 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.
  • 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.
  • the secondary serving cell group where the user equipment is located is in an inactive state.
  • Network quality detection can include RLM and BFD.
  • 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.
  • the secondary serving cell group failure information message transmission process may include S206 to S212.
  • 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.
  • 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.
  • the user equipment when any of the following conditions is met, it can be determined that the user equipment is in MUSIM state: the user equipment is in the RRC connection 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 user equipment is in the first network
  • the secondary serving cell group cannot be activated; the secondary serving cell group where the user equipment is located in the first network cannot be configured; the user equipment prefers not to activate the secondary serving cell group in the first network; the user equipment is in The user equipment has a limited capability state; 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.
  • the secondary serving cell group failure information message includes MUSIM indication information indicating that the user equipment is in the MUSIM state.
  • MUSIM indication information indicating that the user equipment is in the MUSIM state.
  • 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.
  • a secondary serving cell group failure information message including MUSIM indication information is sent to the first network.
  • 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.
  • 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.
  • 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.
  • 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 used to illustrate the method executed by the user equipment provided by the first embodiment in this specification. Another exemplary flowchart of the method. The difference between Figure 3 and Figure 2 lies in S304, S302 in Figure 3 is the same as the above-mentioned S202, and S306 to S312 are the same as the above-mentioned S206 to S212 respectively.
  • the next secondary serving cell group failure information message transmission process is performed.
  • 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.
  • the user equipment 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
  • the RRC connection with the first network 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.
  • 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.
  • 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.
  • 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.
  • the UE 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:
  • 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 RRCReconfguration including reconfigurationWithSync for the SCGnot 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.
  • Transmitting the SCG failure information message SCGFaulurelnformation includes the following operations:
  • the UE sets the content of the SCGFaulureInformation message as follows:
  • 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:
  • a new field musim is added to the SCGFailureInformation message 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
  • 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.
  • 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.
  • the network 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.
  • 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.
  • 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, UE Capabilities are shared among multiple networks simultaneously.
  • the UE in the MUSIM state also includes: the UE does not expect to activate the SCell, the UE does not expect to activate the SCell with different frequencies from 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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
  • 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 connection state Either the SCG can be activated or the SCG can be configured, the UE capabilities (such as transceivers or radio frequency links) are not occupied (or occupied by another network), communication with Network A can use all UE capabilities, the UE is in Network A The UE capabilities are not limited, the UE is not in a UE capability-limited state in Network A, and the UE preferences are not limited to the 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.
  • 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.
  • the UE 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.
  • 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.
  • FIG. 4 is an exemplary flowchart for illustrating a method performed by user equipment provided in the second embodiment of this specification.
  • an RRC reconfiguration message from the first network is received.
  • 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
  • the configuration message includes configuration information for configuring a new secondary serving cell group and configuring the new secondary serving cell group into an active state, or includes configuration information for activating an existing secondary serving cell group.
  • an indication message indicating that the user equipment is in the MUSIM state is sent to the first network.
  • the user equipment 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.
  • the user equipment 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.
  • the user equipment 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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): 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 MN and sent in SRB1 that is 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.
  • MN network A
  • 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.
  • Network A or MN
  • Information or information used to indicate that the SCG has been configured but not 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 information used to indicate that the SCG has not been activated.
  • Configuration information for example, indicated in the RRC reconfiguration complete message).
  • 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 used to indicate that the SCG is configured but not Information related to being activated (for example, indicated in the RRC Reconfiguration Complete RRCReconfigurationComplete message), in this case, the UE does not activate the SCG.
  • the UE 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.
  • 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).
  • 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): UE receives a message containing In the first RRC reconfiguration message of the hr-SCG field in the mrdc-SecondaryCellGroup field, the RRC message containing the first RRC reconfiguration message (for example, the second RRC reconfiguration message) does not contain the scg-State field to indicate SCG is configured as active.
  • the RRC message containing the first RRC reconfiguration message (for example, the second RRC reconfiguration message) does not contain the scg-State field to indicate SCG is configured as active.
  • the MN configures the SCG in an active state.
  • the UE may not configure the SCG or the UE configures but does not activate the SCG.
  • 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.
  • the UE if it 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 received on SRB1 and if the first RRC If the reconfiguration message contains secondaryCellGroup, then:
  • 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
  • the UE if it 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:
  • 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 SCG and perform SCG activation operations; optionally, if the RRC message containing the first RRC reconfiguration message does not contain scg-State, but the UE is in In the MUSIM state, the SCG is configured and the UE indicates to Network A (MN and/or SN) the information that the UE is in the MUSIM state or the SCG has been configured but not activated.
  • Network A MN and/or SN
  • 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:
  • 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.
  • MUSIM and DAPS cannot be configured at the same time, or if the UE is in the MUSIM state, DAPS switching cannot be configured.
  • 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.
  • an RRC reconfiguration message is received from the first network.
  • the configuration information for the secondary serving cell group may be, for example, the configuration information for changing the secondary serving cell group.
  • 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 used to change the current configuration of the user equipment.
  • the RRC reconfiguration message may indicate changing the secondary serving cell group where the user equipment is currently located.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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 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.
  • 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), see the latest version of TS38.331 for details;
  • 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).
  • 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.
  • 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:
  • 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.
  • 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
  • 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.
  • 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 UE receives an RRC reconfiguration message from the MN for changing the SCG (that is, the RRC reconfiguration message contains the secondaryCellGroup field or mrdc-Second).
  • the RRC reconfiguration message contains the secondaryCellGroup field or mrdc-Second.
  • daryCellGroupConfig field, and the secondaryCellGroup field or the spCellConfig field contained in the mrdc-SecondaryCellGroupConfig field contains the reconfigurationWithSync field, that is, the synchronous reconfiguration of SCG).
  • 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;:
  • 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 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:
  • 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.
  • 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.
  • 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. SN indicated in the response message.
  • the UE initiates the SCG invalidation information transmission process and indicates in the SCG invalidation information message that the UE is in the MUSIM state.
  • 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.
  • 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.
  • conditional reconfiguration is performed.
  • conditional reconfiguration is not performed.
  • SCG activation after conditional reconfiguration is performed is avoided.
  • 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.
  • 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.
  • conditional reconfiguration is not performed.
  • a message indicating that the user equipment is in the MUSIM state may be sent to the network.
  • 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.
  • Conditional synchronization reconfiguration/conditional PSCell increase/conditional SCG change (CHO/CPA/CPC)
  • the UE 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.
  • 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.
  • 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.
  • 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.
  • conditional reconfiguration 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.
  • conditional reconfiguration execution process is started. If the UE is configured with conditional reconfiguration and the evaluation conditions for conditional reconfiguration are met, and if the UE is 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • the corresponding secondary serving cell is added based on the added configuration information.
  • the added secondary serving cell is placed in an inactive state.
  • the added The secondary serving cell is active.
  • the RRC reconfiguration message may also include modified configuration information used to modify the secondary serving cell.
  • the secondary serving cell may be modified with reference to the process of FIG. 10 .
  • the corresponding secondary serving cell is modified based on the modified configuration information.
  • the modified secondary serving cell is made inactive.
  • the modified secondary serving cell is made active.
  • the secondary serving cell activation may be performed regardless of whether the user equipment is in MUSIM mode.
  • the operation of determining whether the user equipment is in the MUSIM state is performed.
  • 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
  • the operation of determining whether the user equipment is in the MUSIM state is performed.
  • 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
  • activation of the secondary serving cell corresponding to the secondary serving cell activation indication is performed.
  • the UE 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. Need explanation What is considered here is that the SCell indicated by the network to be activated and the currently activated SCell or PSCell in the UE adopt 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. SCell or even if these SCells are activated, data cannot be received or sent 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:
  • SCell is added or modified.
  • the SCell addition or modification includes the following operations:
  • the UE indicates in the response message that the UE is in the MUSIM state or that the SCell is not activated (optional, this operation is only performed when the SCell is configured in the inactive state but the UE is in the MUSIM state).
  • the response message may be an RRC reconfiguration completion message RRCReconfigurationComplete.
  • the UE 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.
  • the UE receives SCell activation/deactivation MAC C from the base station E or enhanced SCell activation/deactivation MAC CE scenario
  • the MAC entity For each configured SCell, the MAC entity performs the following operations:
  • SCell activation/deactivation MAC CE or enhanced SCell activation/deactivation MAC CE to activate the SCell, perform the following operations:
  • 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.
  • deactivation and inactivation have the same meaning and can be used interchangeably.
  • FIG. 11 is an exemplary flowchart for illustrating a method performed by a user equipment provided in the sixth embodiment of this specification.
  • the user equipment 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.
  • 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).
  • the first network may configure corresponding MCG resources for the first network for transmitting uplink data.
  • the uplink data is transmitted through the active SCG.
  • 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.
  • 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.
  • 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; used to prohibit sending the uplink data.
  • the prohibition timer of the indication information is not in the running state, and the prohibition timer is started when the uplink data indication information is sent. The prohibition timer is used to limit the frequency of sending uplink data indication information to avoid sending information too frequently.
  • the first network may instruct the user equipment to exit the MUSIM state through a MUSIM state release indication.
  • 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 .
  • 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.
  • a MUSIM state release indication is received from the first network.
  • 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. .
  • 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.
  • the predetermined condition includes that the user equipment is in the MUSIM state.
  • 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. Under this condition, if the user equipment prefers to maintain the RRC connection with the second network, the RRC connection with the first network is released. connect.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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 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 the logical channel identifier used to indicate that the UE has uplink data to be sent for the SCG RLC entity or the deactivated SCG. uplinkData field.
  • the UE When the SCG is deactivated and the UE is not in the MUSIM state, the UE only needs to include the uplinkData field in the UE assistance information message 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. After receiving this message, the SCG DRB can be reconfigured as an MCG DRB or detached DRB (that is, adding an MCG RLC bearer to the SCG DRB), thereby reducing the transmission delay of the SCG DRB.
  • 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.
  • RLC bearer and RLC entity are used interchangeably.
  • network A 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.
  • 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.
  • 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.
  • indication information indicating that the user equipment prefers not to activate the secondary serving cell group is sent to the first network.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the RRC recovery message indicates that the activated secondary serving cell and the primary serving cell operate in different frequency bands
  • a message indicating that the user equipment prefers not to activate the secondary service is sent to the first network. Instructions for the neighborhood.
  • the user equipment may send indication information indicating that the user equipment prefers not to activate the secondary serving cell group to the first network.
  • 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.
  • 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.
  • 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.
  • 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.
  • the user equipment 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.
  • the user equipment 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.
  • 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.
  • 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.
  • network A may send an RRC recovery message to the UE to recover the suspended RRC connection.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 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.
  • 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.
  • the indication information is included in the RRC recovery request message only when the frequency SCell is used.
  • 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.
  • the UE 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.
  • 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.
  • 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.
  • 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.
  • the MR-DC related configuration is released from the UE inactive AS context.
  • the UE 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 shown.
  • the UE sends indication information to the network to indicate that the UE is in the MUSIM state or the SCell is not activated or the SCell is not configured or the 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.
  • 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.
  • 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.
  • 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 media” may be semiconductor recording media, optical recording media, Magnetic recording media, recording media for short-term dynamic storage of programs, or any other recording media readable by a computer.
  • 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.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种由用户设备执行的用于恢复RRC连接的方法，包括：向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC恢复请求消息；接收来自第一网络的RRC恢复消息；当所述RRC恢复消息指示激活辅服务小区组时，如果所述用户设备偏好不激活所述辅服务小区组，则向所述第一网络发送表示所述用户设备偏好不激活所述辅服务小区组的指示信息。

Description

由用户设备执行的用于恢复RRC连接的方法及用户设备 技术领域
本发明涉及无线通信技术领域，具体涉及由用户设备执行的用于恢复RRC连接的方法及用户设备。
背景技术
近年来，多USIM卡设备越来越流行。例如一个用户在支持多USIM卡的手机上安装两张USIM卡，其中一张USIM卡用于订阅私人业务，另一张USIM卡用于订阅办公业务。现有支持多USIM卡的设备是基于厂商实现，尚未被3GPP标准化。导致不同的厂商采用不同的实现方式，用户设备UE的行为也各不相同。现有实现方式中，如果这些USIM卡分别向网络注册(可注册到同一网络也可分别注册到两个或两个以上网络)，UE需要从这些网络接收寻呼，基于UE的收发能力，可能存在的一种情形是UE在接收当前网络的寻呼时另一个网络也对其发起寻呼，又或者UE正与一个网络通信时另一个网络对其发起寻呼。如果UE在不同的网络之间切换，可能导致的一个结果是当UE切换到另一个网络时UE不能再从当前网络接收数据。这将损害网络性能，例如网络向UE发送了寻呼但UE因切换到另一个网络而没有接收到这个寻呼，或UE切换到另一个网络而不能接收当前网络的调度。部分厂商提出对具备多USIM卡的UE接入网络的行为及相关网络进行3GPP标准化研究，其好处在于可以基于可预测的UE行为，提升网络性能。
基于上述原因，2019年12月，在第三代合作伙伴计划(3rd Generat ion Partnership Project：3GPP)RAN#86次全会上，vivo提出了针对版本17的多SIM卡设备的工作项目(参见非专利文献：RP-193263：New WID：Stupport of Multi-SIM devices in Rel-17)，并获批准。该工作项目的目标之一是定义UE在离开网络A时通知网络A的机制，其中网络A是NR，网络B是LTE或NR，且UE单收单发(Single-Rx/Single-Tx)或UE双收单发(Dual-Rx/Single-Tx)。
2021年12月，在3GPP RAN#94次会议上达成对具有双收双发能力(dual Rx/Tx)的多USIM卡UE进一步增强，使得UE可以在两个网络同时处于RRC连接态(参见非专利文献：RP-213584 New WI on DualTx Rx MUSIM enhancements)。
本公开讨论达成上述工作目标所涉及的相关问题。
发明内容
本发明的目的在于提供能够避免在用户设备不偏好激活与第一网络对应的SCG时激活该SCG的方法。
根据本发明的一个方面，提供一种由用户设备执行的用于恢复RRC连接的方法，包括：向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC恢复请求消息；接收来自第一网络的RRC恢复消息；当所述RRC恢复消息指示激活辅服务小区组时，如果所述用户设备偏好不激活所述辅服务小区组，则向所述第一网络发送表示所述用户设备偏好不激活所述辅服务小区组的指示信息。
根据本发明的另一方面，提供一种由用户设备执行的用于恢复RRC连接的方法，包括：向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC恢复请求消息，如果所述用户设备偏好不激活辅服务小区组，则在所述RRC恢复请求消息中包括表示所述用户设备偏好不激活所述辅服务小区组的指示信息；接收来自第一网络的RRC恢复消息；以基于所述RRC恢复消息，恢复在所述第一网络中的RRC连接。
本发明的有益效果
根据本说明书的方案，能够避免在用户设备不偏好激活与第一网络对应的SCG时激活该SCG。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1是用于本说明书中提及的具有MUSIM能力用户设备的一个示例的示意图。
图2是用于说明本说明书中的第一实施方式提供的由用户设备执行的方法的示例性流程图。
图3是用于说明本说明书中的第一实施方式提供的由用户设备执行的方法的另一示例性流程图。
图4是用于说明本说明书中的第二实施方式提供的由用户设备执行的方法的示例性流程图。
图5是用于说明本说明书中的第三实施方式提供的由用户设备执行同步重配置的方法的示例性流程图。
图6是用于说明本说明书中的第四实施方式提供的由用户设备执行同步重配置的方法的示例性流程图。
图7是用于说明本说明书中的第四实施方式提供的由用户设备执行同步重配置的方法的另一示例性流程图。
图8是用于说明本说明书中的第五实施方式提供的由用户设备执行的配置辅服务小区的方法的示例性流程图。
图9是用于说明本说明书中的第五实施方式提供的由用户设备执行的配置辅服务小区的方法中增加辅服务小区的示例性流程图。
图10是用于说明本说明书中的第五实施方式提供的由用户设备执行的配置辅服务小区的方法中修改辅服务小区的示例性流程图。
图11是用于说明本说明书中的第六实施方式提供的由用户设备执行的方法的示例性流程图。
图12是用于说明本说明书中的第六实施方式提供的由用户设备执行的方法中MUSIM释放指示处理过程的示例性流程图。
图13是用于说明本说明书中的第七实施方式提供的由用户设备执行的用于恢复RRC连接的方法的示例性流程图。
图14是用于说明本说明书中的第八实施方式提供的由用户设备执行的用于恢复RRC连接的方法的示例性流程图。
图15是本说明书中提供的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本 公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，术语的具体含义见3GPP最新相关文档，例如TS38.300、TS38.331、TS36.300、TS36.331等。
NAS：Non-access stratum，非接入层。
AS：access stratum，接入层。
RRC：Radio Resource Control，无线资源控制。
RRC_CONNECTED：RRC连接态。
RRC_INACTIVE：RRC非激活态。
RRC_IDLE：RRC空闲态。
RLC：Radio Link Control，无线链路控制。
CPA：Conditional PSCell Addition，条件PSCell增加。
CPC：Conditional PSCell Change，条件PSCell改变。
RAN：Radio Access Network，无线接入层。
BWP：Bandwidth Part，带宽部分。
USIM：Universal Subscriber Identity Module，全球用户识别卡。
MUSIM：Multi-Universal Subscriber Identity Module，多全球用户识别卡。
Tx：transmitter，发信机。
Rx：receiver，接收机。
NR：New RAT，新无线访问技术。
gNB：向UE提供NR用户面和控制面协议栈(NR user plane and control plane protocol terminations)，并通过NG接口连接到5G核心网的基站节点。
eNB：向UE提供E-UTRAN用户面和控制面协议栈，并连接到EPC核心网的基站节点。
ng-eNB：向UE提供E-UTRAN用户面和控制面协议栈，并通过NG接口连接到5G核心网的基站节点。
双连接或者多连接：是指工作在RRC连接态的UE与多于一个网络节点建立物理上的无线通路，并实现数据传输。在双连接中，具有多Tx/Rx 能力的UE被配置使用由两个网络节点提供的资源，这两个网络节点通过非理想回程(non-ideal backhaul)连接。其中一个网络节点作为主控制节点(Master Node，MN或MN gNB)，另一个网络节点作为辅控制节点(Secondary Node，SN或SN gNB)。MN和SN通过网络接口连接并且至少MN连接到核心网。MN可由一个gNB/eNB/ng-eNB来执行，由MN控制的服务小区组称为主小区组(Master Cell Group，MCG)，即MCG关联MN。MCG中至少有一个运行在主频率上的主服务小区，被称主小区PCell(Primary Cell)，UE在PCell上执行初始连接建立过程或者发起连接重建过程。MCG中如果还包含了其他小区，可以统称为辅服务小区SCell。相应地，SN可由一个或多个gNB/eNB/ng-eNB来执行，由SN控制的服务小区组称为辅服务小区组(Secondary Cell Group，SCG)，即SCG关联到SN。SCG中至少包含了一个主服务小区，被称为主辅小区PSCell(Primary Second Cell)。当执行同步重配置(针对SCG的同步重配置或SCG改变)过程时UE在PSCell上执行随机接入(在需要执行时才执行)。SCG中如果还包含了其他小区，可以统称为辅服务小区SCell。SN和UE之间可以建立信令无线承载SRB，通常称为SRB3。SRB3用于特定的在DCCH逻辑信道上传输的RRC消息，适用于处于(NG)EN-DC或NR-DC的UE。SRB3可用于传递SN和UE之间的RRC消息，例如SCG相关联的测量配置和报告。本公开中，SpCell可以指MCG的PCell或SCG的PSCell。
SCG无线承载是仅在SCG中的具有一个RLC承载的无线承载或在载波聚合分组重复中具有两个RLC承载的无线承载。SCG无线承载包括SCG信令无线承载SRB和SCG数据无线承载DRB。
SRB1用于承载所有使用DCCH逻辑信道的RRC消息以及SRB2建立前的NAS消息。
SRB2用于承载NAS消息和所有使用DCCH逻辑信道的包含记录的测量信息的RRC消息。
EN-DC：E-UTRA-NR双连接，E-UTRA为MN，NR为SN的双连接且连接到EPC。
NGEN-DC：NG-RAN，E-UTRA-NR双连接，且连接到5G核心网5GC。
NR DC：NR-NR双连接，当且仅当配置的mrdc-SecondaryCellGroup 被设置的nr-SCG。
MR-DC：Multi-Radio Dual Connectivity，多无线双连接，包括(NG)EN-DC、NE-DC、NR-DC。
本公开中，网络(或网络节点)、基站(或基站节点)和RAN可互换使用，所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
本公开中，用户设备UE可指物理上支持多USIM卡(两个或两个以上USIM卡)的设备，所述USIM可以是物理SIM或eSIM(USIM can be a physical SIM or eSIM)。所述设备装配了两个或两个以上USIM卡，每个USIM卡关联一个网络(即与一个网络建立RRC连接)。所述多个USIM卡可以来自同一个运营商或不同的运营商。从网络的角度来看，不同的USIM卡可对应不同的UE，每个USIM卡对应一个UE。如未特别说明，本公开不对此加以区分。本领域技术人员可以根据上下文容易地确定UE是指支持多USIM卡的UE还是支持多USIM卡的设备中每个USIM卡分别对应的UE。配置了多USIM卡的用户设备可以通过时分复用等方式利用单收单发或双收单发从多个网络接收和/或发送数据。而具有两个Tx和两个Rx(双发双收)的UE，可以同时向两个网络发送数据，也可以同时从两个网络接收数据。MUSIM UE的硬件能力被两个SIM卡共享，相关的能力在两个SIM卡之间动态分配(dynamically split)。这将导致短暂的硬件冲突，使得UE从一个SIM卡释放一些资源供另一个SIM卡使用。例如，当UE的SIM A在网络A处于RRC连接态，SIM B在网络B处于RRC空闲态或RRC非激活态，两个射频链路(RF chains)或两个收发器被SIM A占用以用于与网络A的通信。如果SIM B需要与网络B建立RRC连接，其中一个射频链路需要切换到SIM B。如果网络A不知道UE在射频链路能力的改变，将导致网络A的数据丢失以及无线资源的浪费。
本公开实施例以UE配置两个USIM卡为例，本领域技术人员可以容易的扩展到多个USIM卡的情况。
以下描述本公开涉及的字段(filed)：
masterCellGroup字段用于配置主小区组MCG。
spCellConfig字段包含对应小区组的SpCell(即MCG的PCell或SC G的PSCell)的参数。
reconfigurationWithSync字段包含同步重配置到目标SpCell的参数。
CellGroupConfig字段用于配置主小区组MCG或辅服务小区组SCG。
scg-State字段用于指示SCG处于非激活态。基站通过在RRC重配置消息RRCReconfiguration中不包含scg-State字段来指示SCG被配置为激活态；通过在RRC重配置消息中包含scg-State字段来指示SCG被配置为非激活态。
bfd-and-RLM字段用于当SCG被去激活(deactivated)时指示UE是否执行波束失效检测(Beam Failure Detection，BFD)和无线链路监测(Radio Link Monitoring，RLM)。
secondaryCellGroup字段包含SCG的配置(针对(NG)EN-DC或NR-DC)，secondaryCellGroup字段包含CellGroupConfig字段。
CellGroupConfig字段用于配置一个MCG或SCG，一个小区组由一个MAC实体、一个关联相关RLC实体的逻辑信道集(a set of logical channels with associated RLC entities)、一个SpCell和一个或多个SCell组成。
mrdc-SecondaryCellGroup字段包含用于NR-DC或NE-DC中SCG配置的RRC消息，在NR-DC中，mrdc-SecondaryCellGroup字段包含完全由SN gNB产生的RRCReconfiguration消息，所述由SN gNB产生的R RCReconfiguration消息可以包含secondaryCellGroup字段、otherConfig字段、conditionalReconfiguration字段和measConfig字段。
otherConfig字段包含与其他配置相关的配置，例如配置UE报告辅助信息以通知gNB关于UE为节能的非连续接收DRX偏好等。
conditionalReconfiguration字段为条件切换和条件PSCell改变配置候选目标SpCell(s)和执行条件。
measConfig字段定义由UE执行的测量，覆盖频率内(intra-Frequency)、频率间(inter-Frequency)和RAT间(inter-RAT)的移动以及测量间隔的配置。
nr-SCG字段包含在mrdc-SecondaryCellGroup字段中，用于表示双连接为NR-DC，此时mrdc-SecondaryCellGroup包含的RRC重配置消息完全由SN gNB产生。
sCellToAddModList字段用于指示增加或修改的SCell的列表。
sCellIndex字段用于标识一个SCell。
sCellState字段指示在配置SCell时该SCell是否被认为是激活态(indicates whether the SCell shall be considered to be in activated state upon SCell configuration)。如果RRC重配置消息中包含该字段，字段值设置为‘activated‘表示在配置SCell时该SCell是激活态，如果RRC重配置消息中不包含该字段，表示在配置SCell时该SCell是非激活态。
firstActiveDownlinkBWP-Id字段用于配置SpCell时，包含在执行RRC重配置时激活的下行BWP的标识ID或者包含用作SCG被去激活时RLM、BFD和测量的下行BWP的标识ID(当RRC重配置消息中指示UE需要执行RLM、BFD和测量时才表示此含义)；用于配置SCell时，这个字段包含在激活SCell时使用的下行BWP的标识ID。
firstActiveUplinkBWP-Id用于配置SpCell时，包含执行RRC重配置时激活的上行BWP的标识ID；用于配置SCell时，这个字段包含激活SCell时使用的上行BWP的标识ID。
sCellConfigCommon字段对应用于配置UE的服务小区的可配置的小区特定参数的ServingCellConfigCommon字段。ServingCellConfigCommon字段包含IDLE态UE访问小区时从同步信号块SSB、主信息块MIB或系统信息块SIB获取的参数，在配置SCell时，网络通过包含这个字段的专用信令提供这些信息。
sCellConfigDedicated字段对应ServingCellConfig字段，ServingCellConfig字段用于为UE配置(即增加或修改)一个服务小区，这个服务小区可以是MCG或SCG的SpCell或SCell。
VarConditionalReconfig变量包含包括条件切换CHO、条件PSCell增加CPA、条件PSCell改变CPC配置的累积配置，包括指向CHO、CPA、CPC执行条件(关联的measId(s))和存储的目标候选SpCell RRC重配置的指针(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 RRCReconfiguration)。
condReconfigID字段用于标识一个CHO、CPA、CPC配置。
condRRCReconfig字段包含当条件满足时应用的RRC重配置消息。
condTriggerConfig字段用于CHO、CPA、CPC配置，设置CHO、CPA、CPC的触发条件。
measId字段用于标识正在执行报告的测量标识(identifies the measurement identity for which the reporting is being performed)。
DRB-Identity字段用于标识(identify)一个UE使用的DRB。
RLC-BearerConfig字段用于配置一个RLC实体、MAC中对应的逻辑信道以及与PDCP实体的关联(服务的无线承载)。
SCG失效信息消息即SCGFailureInformation消息用于提供UE检测到的关于SCG失效的信息。
RRC恢复请求消息RRCResumeRequest或RRCResumeRequestl用于请求恢复一个挂起的RRC连接或执行基于RAN的通知区域(RNA)更新。UE可基于SIBl是否发送了(signal)useFullResumeID字段(filed)来选择用RRCResumeRequest或RRCResumeRequestl请求恢复一个RRC连接。如果SIB1发送了useFullResumeID字段(filed)，则用RRCResumeRequest1来请求恢复一个RRC连接，如果SIB1没有发送useFullResumeID字段(filed)，则用RRCResumeRequest来请求恢复一个RRC连接。
RRC恢复RRCResume消息用于恢复挂起的RRC连接。RRC重配置消息RRCReconfiguration是修改RRC连接的指令。
UEAssistanceInformation消息用于向网络指示UE辅助信息。
RRC重配置完成消息RRCReconfigurationComplete用于确认成功完成RRC连接重配置。
如果上层(例如RRC层)指示激活SCG(处于激活态的SCG)，可以执行：在PSCell上传输SRS、报告PSCell的CSI、在PSCell上监测PDCCH、在PSCell上传输PUCCH等。
如果上层(例如RRC层)指示去激活SCG，可以执行：去激活SCG的所有SCell、去激活SCG、清空PSCell关联的配置的下行分配或类型2配置的上行许可、挂起PSCell关联的类型1的配置上行许可、重置(reset)MAC等。
处于非激活态的SCG不在PSCell上传输SRS、不报告PSCell的CS I、不在PSCell上传输UL-SCH、在不PSCell上传输PUCCH等。
本公开中，UE认为SCG或SCell已激活可表示UE指示下层激活SCG或SCell。
需要特别说明的是在双连接中，UE虽然与两个网络节点MN和SN进行数据传输，但是UE仅与MN建立RRC连接。而在MUSIM中，UE可以通过各个SIM卡与网络分别建立RRC连接。
图1是具有MUSIM能力的UE在网络A处于双连接的示意图。在图1中，UE的SIM卡A与网络A(记为第一网络)建立RRC连接，SIM卡B与网络B(记为第二网络)建立RRC连接，并且UE被网络A配置了双连接，网络A是MN，网络C是SN。本公开实施例是基于图1所述场景。
图2是用于说明本说明书中的第一实施方式提供的由用户设备执行的方法的示例性流程图。在第一实施方式中，用户设备在第一网络中处于RRC连接态，并且在第一网络中被配置为需要执行辅服务小区组网络质量检测。在第一网络中，用户设备所在的辅服务小区组处于非激活态。
如图2所示，在S202～S204，执行辅服务小区组网络质量检测。网络质量检测可以包括RLM和BFD。
在检测到辅服务小区组失效时，发起向第一网络的辅服务小区组失效信息消息传输过程，所述辅服务小区失效信息消息传输过程用于向所述第一网络发送表示在所述第一网络中所述用户设备所在的辅服务小区组已失效的辅服务小区组失效信息消息。例如是可以在检测到波束失效时，确定为检测到辅服务小区组失效。
具体而言，辅服务小区组失效信息消息传输过程可以包括S206～S212。
在S206，确定用户设备是否处于MUSIM状态。MUSIM状态是指用户设备的能力受到限制的状态，或者换言之是用户设备仅能够使用其部分能力与第一网络通信的状态。例如，在如下情况属于MUSIM状态的一种：包括多个SIM的用户设备在第一网络中处于RRC连接态，并且在与不同于第一网络的第二网络保持RRC连接，而且用户设备偏好不释放与第二网络的RRC连接。
在本说明书，可以在满足以下中的任一条件时，确定为用户设备处于 MUSIM状态：用户设备在不同于所述第一网络的第二网络中处于RRC连接态；用户设备在第二网络中执行上行数据传输或下行数据传输；用户设备在所述第一网络中所在的辅服务小区组不能被激活；用户设备在第一网络中所在的辅服务小区组不能被配置；用户设备在第一网络中偏好不激活辅服务小区组；用户设备在所述第一网络中处于用户设备能力受限状态；用户设备的部分硬件功能被占用从而不能用于所述用户设备在所述第一网络中的数据传输。
当用户设备处于MUSIM状态时，在S208，在辅服务小区组失效信息消息中包括指示用户设备处于MUSIM状态的MUSIM指示信息。换言之，生成包括指示用户设备处于MUSIM状态的MUSIM指示信息的辅服务小区组失效信息消息。
作为示例，可以通过以下中的任一种方式来在辅服务小区组失效信息消息中包括MUSIM指示消息：在辅服务小区组失效信息消息中增加用于指示用户设备处于MUSIM状态的字段；在辅服务小区组失效信息消息中，对用于指示辅服务小区组失效原因的字段赋予用于指示用户设备处于MUSIM状态的值。
然后，在S212，向第一网络发送包括MUSIM指示信息的辅服务小区组失效信息消息。第一网络在接收到辅服务小区组失效信息消息之后，能够得知该用户设备的辅服务小区组已经失效，可以为用户设备配置新的辅服务小区。此时，由于所接收到的辅服务小区组失效信息消息包括MUSIM指示信息，因而第一网络在为用户设备配置新的辅服务小区时会考虑用户设备处于MUSIM状态这一情况，避免为用户设备配置激活的SCG。由此，能够防止即便SCG被激活，但是因用户设备的部分硬件资源被占用而不能顺利在通过SCG传输数据而造成的资源浪费以及数据丢失等问题。
当用户设备不处于MUSIM状态时，在S210，生成不包括指示用户设备处于MUSIM状态的MUSIM指示信息的辅服务小区组失效信息消息。然后接着在S212，向第一网络发送不包括指示用户设备处于MUSIM状态的MUSIM指示信息的辅服务小区组失效信息消息。
图3是用于说明本说明书中的第一实施方式提供的由用户设备执行 的方法的另一示例性流程图。图3与图2的不同之处在于S304，图3中的S302与上述S202相同，S306～S312分别与上述S206～S212相同。
在S304中，确定检测到的辅服务小区组失效是否是PSCell的波束失效。
当所检测到的辅服务小区组失效是PSCell的波束失效时，执行接下来的辅服务小区组失效信息消息传输过程。
此外，在本说明书中，可以由第一网络来配置是否允许使用用户设备的部分硬件能力与第一网络进行通信。需要说明的是，允许使用用户设备的部分硬件能力与第一网络进行通信可以表述为UE被配置了为MUSIM目的报告在第一网络限制UE能力(或报告在第一网络UE能力受限或报告在第一网络所使用的UE能力)的辅助信息。
可以在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，执行辅服务小区组失效信息消息传输过程，即，确定执行用户设备是否处于MUSIM状态的操作。进而，当用户设备处于MUSIM状态时，在辅服务小区组失效信息消息中包括指示用户设备处于MUSIM状态的MUSIM指示信息。在这种情况下，用户设备需要通知其处于MUSIM状态这一状况。
另一方面，在用户设备被第一网络配置为不允许仅使用用户设备的部分硬件能力与第一网络进行通信或未被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，当用户设备需要与第二网络建立RRC连接的情况下，将会释放与第一网络的RRC连接。即，在这种情况下，不存在MUSIM状态。
下以对第一实施方式的具体实施例进行说明。
UE检测到处于非激活态的SCG的PSCell波束失效的实施例
本公开实施例1致力于解决至少具有双收双发能力的UE在网络A和网络B都处于RRC连接态时，UE检测到处于非激活态的SCG的PSCell波束失效但UE认为网络B的优先级更高时向网络A发送SCG失效信息消息所涉及的相关问题，以避免网络A在收到所述SCG失效信息消息后为UE配置处于激活态的SCG。
实施例1
在本实施例中，UE在网络A处于双链接，其中SCG处于非激活态但被配置了需要执行波束失效检测和无线链路监测。具体的，UE接收到来自基站的RRC重配置消息，其中包含SCG的配置信息(即RRC重配置消息中包含secondaryCellGroup字段或mrdc-SecondaryCellGroup字段)，并且SCG被配置为非激活态但需要执行BFD和RLM(即SCG的配置信息中包含bfd-and-RLM字段，其值设置为“true”)。UE按照接收到的RRC重配置消息配置SCG。
当SCG处于非激活态且检测到PSCell波束失效，UE发起SCG失效信息传输过程，具体包括以下至少一项：
1)停止SCG的定时器T304(SCG的T304正在运行时才执行)；T304在接收到包含针对被配置为非激活态的SCG的同步重配置的RRC重配置消息时启动(start upon reception of RRCReconfguration including reconfigurationWithSync for the SCGnot indicated as deactivated in the NR message containing the RRCReconfiguration message)，在SpCell上成功完成随机接入或释放SCG时停止。
2)停止CPA和/或CPC的条件重配置评估(conditional reconfiguration evaluation)(在配置了CPA和/或CPC时才执行)；
3)发起传输SCG失效信息消息。
传输SCG失效信息消息SCGFaulurelnformation包括以下操作：
UE按照如下方式设置SCGFaulureInformation消息的内容：
如果UE启动传输SCGFailureInformation消息是由于检测到PSCell的波束失效而SCG是非激活的(if the UE initates transmission of the SCGFaulureInformation message due to beam failure of the PSCell while the SCG is dectivated)，则进一步判断UE是否处于MUSIM状态。如果UE处于MUSIM状态，则在所述SCGFailureInformation消息中包含UE处于MUSIM状态的指示信息，否则，SCGFailureInformation消息中不包含UE处于MUSIM状态的指示信息。
所述UE处于MUSIM状态的指示信息可以通过以下几种实施方式实现：
在一种实施方式中，SCGFailureInformation消息中增加新的字段musim来指示UE处于MUSIM状态。具体的，如果UE处于MUSIM状态，则设置SCGFailureInformation消息中用于指示原因的failureType字段值为“other”和设置SCGFailureInformation消息中用于进一步指示原因字段failureType-v1610为“beamFailure”，并且包含musim字段以指示UE处于MUSIM状态或设置字段musim的值为指示UE处于MUSIM状态的值，例如“true”；如果UE不是处于MUSIM状态，则设置failureType和值为“other”和设置failureType-v1610为“beamFailure”，并且SCGFailureInformation消息不包含musim字段或者SCGFailureInformation消息包含musim字段但其值设置为对应UE不处于MUSIM状态的值，例如musim字段值为“false”。
在一种实施方式中，增加用于指示SCG失效原因的字段(例如failureType-v1610字段)的取值，为所述字段设置一个新的值来指示UE处于MUSIM状态或者发生SCG波束失效的UE处于MUSIM状态或者处于MUSIM状态的UE发生SCG波束失效或者UE处于MUSIM状态且发生SCG波束失效。例如，failureType-v1610取值为“musim”时表示UE处于USIM状态或表示处于MUSIM状态的UE检测到非激活SCG的PSCell波束失效。
网络在接收到SCG失效信息消息时，可以根据所述消息中是否包含指示UE处于MUSIM状态的指示标识来决定为UE重配置的SCG的状态。例如，如果网络接收到的SCG失效信息消息中包含UE处于MUSIM状态的指示标识，则将为UE重新配置的SCG设置为非激活态，否则，可以设置SCG为激活态。
本公开中，UE处于MUSIM状态包括：UE在网络B处于RRC连接态、UE正在执行MUSIM操作(即UE正在执行或需要执行在MUSIM间隔内无法完成的MUSIM操作)、UE在两个网络同时处于RRC连接态或者SCG不能被激活或SCG不能被配置、UE不偏好(prefer)激活SCG(即UE偏好不激活SCG或UE偏好SCG处于非激活态)、部分UE能力(例如收发机或射频链路)被占用(或被另一个网络占用)、与网络A的通信仅可使用部分UE能力、UE在网络A的UE能力受限、UE在网络A处于UE能力受限状态、UE偏好限制在网络A的UE能力、UE 能力同时在多个网络间共享。在载波聚合场景中，UE处于MUSIM状态还包括：UE不期望激活SCell、UE不期望激活与PCell异频的SCell、UE偏好SCell处于非激活态、UE偏好与PCell异频的SCell处于非激活态。
本公开实施例中，UE认为网络B的优先级更高包括：UE不释放与网络B的RRC连接、UE偏好保持MUSIM状态、UE偏好不激活SCG、UE偏好不激活SCell、UE偏好不激活与PSCell异频的SCell。UE处于MUSIM状态的条件可以替换为UE认为网络B的优先级更高或者UE处于MUSIM状态且认为网络B的优先级更高。
需要说明的是在本公开实施例中，判断UE是否处于MUSIM状态的条件可以替换为在UE被网络A配置了允许UE请求进入MUSIM状态时才判断UE是否处于MUSIM状态，即如果UE被配置了允许UE请求进入MUSIM状态，并且UE处于MUSIM状态，则执行实施例中满足UE处于MUSIM状态时应执行的操作。基站可通过RRC重配置消息，配置是否允许UE请求进入MUSIM状态(或配置是否允许UE请求进入MUSIM状态或请求处于UE能力受限状态或配置是否允许UE请求限制UE能力)。相应地，UE不处于MUSIM状态就是UE仅在其中一个网络(例如网络A)处于RRC连接态或者UE未执行MUSIM操作或者SCG可以被激活或SCG可以被配置或者UE能力(例如收发机或射频链路)未被其他网络占用或与网络A的通信可使用全部UE能力或UE在网络A的UE能力不受限或UE在网络A不处于UE能力受限状态或者UE偏好不限制在网络A的UE能力。在载波聚合场景中，UE不处于MUSIM状态还包括：可以激活SCell、可以激活与PCell异频的SCell、UE不偏好SCell处于非激活态、UE不偏好与PCell异频的SCell处于非激活态。
本公开中，将UE处于MUSIM状态替换为UE被配置了可以请求进入或退出MUSIM状态并且UE处于MUSIM状态得到的实施例也是本公开保护的范围，将UE不处于MUSIM状态替换为UE被配置了可以请求进入或退出MUSIM状态并且UE不处于MUSIM状态或者如果UE没有被配置可以请求进入或退出MUSIM状态得到的实施例也是本公开保护的范围。UE请求退出MUSIM状态可以包括：UE释放了在网络B的RRC连接、UE没有执行MUSIM操作(即UE未执行或不需要执行在MUSIM间隔内无法完成的MUSIM操作)、UE仅在第一网络处于RRC连接态 或者SCG可以被激活或SCG可以被配置、UE能力(例如收发机或射频链路)未被占用(或被未另一个网络占用)、与网络A的通信可使用全部UE能力、UE在网络A的UE能力不受限、UE在网络A不处于UE能力受限状态、UE偏好不限制在网络A的UE能力。在载波聚合场景中，UE不处于MUSIM状态还包括：可以激活SCell、可以激活与PCell异频的SCell。
网络A可以通过RRC重配置消息为UE配置是否允许UE请求进入或退出MUSIM状态或者是否允许UE请求限制在当前网络的UE能力。在这种情况下，网络A配置了允许UE进入或退出MUSIM状态时UE才能向网络指示UE是否处于MUSIM状态的信息。如果UE被网络A配置了可以请求进入或退出MUSIM状态，则当UE需要进入MUSIM状态时，向网络A发送包含请求进入MUSIM状态的指示信息的RRC消息。例如，如果UE被网络A配置了可以请求进入MUSIM状态，当UE需要与网络B建立RRC连接时，向网络A请求进入MUSIM状态，当UE释放与网络B的RRC连接时，可以向网络A指示UE退出MUSIM状态，这样网络A就可以使用全部的UE能力。
需要说明的是为UE配置允许UE请求进入或退出MUSIM状态可替换为允许UE请求限制在当前网络的UE能力，或者允许使用用户设备的部分硬件能力与第一网络进行通信，或为UE配置为MUSIM目的报告在第一网络限制UE能力的辅助信息，或为UE配置为MUSIM目的报告在第一网络UE能力受限的辅助信息，或为UE配置为MUSIM目的报告在第一网络所使用的UE能力的辅助信息，或为UE配置为MUSIM目的报告在第一网络进入或退出UE能力受限状态的辅助信息，在本公开实施例中采用这些描述方式中的任意一种描述方式得到的实施例也是本说明书包含的范围。
图4是用于说明本说明书中的第二实施方式提供的由用户设备执行的方法的示例性流程图。
如图4所示，在S402中，接收来自第一网络的RRC重配置消息。在此，RRC重配置消息用于配置新辅服务小区组并将新辅服务小区组配置为激活态，或用于激活已有辅服务小区组。即，所接收到的RRC重配 置消息包括配置新辅服务小区组并将新辅服务小区组配置为激活态的配置信息，或包括激活已有辅服务小区组的配置信息。
当接收到来自第一网络的RRC重配置消息时，在S404，确定用户设备是否处于MUSIM状态。
如果用户设备处于MUSIM状态，则在S406，向第一网络发送表示用户设备处于MUSIM状态的指示消息。
在一个示例中，当用户设备处于MUSIM状态时，若RRC重配置消息用于配置新辅服务小区组并将新辅服务小区组配置为激活态，则用户设备不执行RRC重配置消息所指示的辅服务小区组配置。此时，指示消息包括辅服务小区组配置未被执行的信息。
在另一示例中，当用户设备处于MUSIM状态时，若RRC重配置消息用于配置新辅服务小区组并将新辅服务小区组配置为激活态，则用户设备执行RRC重配置消息所指示的辅服务小区组配置，但不激活所配置的新辅服务小区组。此时，指示消息包括新辅服务小区组未被激活的信息。
在另一示例中，当用户设备处于MUSIM状态时，若RRC重配置消息用于激活已有辅服务小区组，则用户设备不执行RRC重配置消息所指示的辅服务小区组激活。此时，指示消息包括辅服务小区组激活未被执行的信息。
此外，在接收到RRC重配置消息时，用户设备也可以确定其当前可用资源是否足以激活新辅服务小区组或已有辅服务小区组。当用户设备的当前可用资源足以激活新辅服务小区组或已有辅服务小区组时，不管用户设备是否处于MUSIM模式，均可以激活新辅服务小区组或已有辅服务小区组。关于如何确定当前可用资源是否足以激活新辅服务小区组或已有辅服务小区组，例如可以由用户设备的内部逻辑实现，该内部逻辑可以由用户设备的提供端来提供。作为示例，例如可以通过硬件资源的占有率是否低于给定阈值等来确定。
此外，可以由第一网络来配置是否允许使用用户设备的部分硬件能力与第一网络进行通信。可以在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，确定执行用户设备是否处于MUSIM状态的操作。
以下对第二实施方式的具体实施例进行说明。
网络为UE配置激活态SCG的实施例
本公开实施例2致力于解决至少具有双收双发能力的UE在网络A和网络B都处于RRC连接态时，网络A为UE配置SCG或网络A指示UE激活处于非激活态的SCG但UE处于MUSIM状态时所涉及的相关问题，以避免处于MUSIM状态的UE激活SCG并使得UE和网络A中SCG状态一致。
实施例2
本实施例考虑UE接收到来自网络A的RRC重配置消息RRCReconfiguration，所述RRC重配置消息用于配置SCG且指示SCG处于激活态或所述RRC重配置消息用于激活SCG，具体包括以下几种情况：
情况一(MN配置并激活SCG)：UE接收到来自网络A(MN)的RRC重配置消息(在本公开实施例中指由MN产生的在SRBl发送的不包含在其他RRC消息中的RRC重配置消息)，所述RRC重配置消息在SRBl上传输，其中包含SCG的配置信息，即通过在RRC重配置消息中包含secondaryCellGroup字段来提供SCG的配置信息(即所述RRC重配置消息由MN产生)，且SCG被配置为激活态。这是针对RRC重配置消息用来为UE配置SCG的情况，UE在此之前没有被配置SCG。在这种情况下，UE如果处于MUSIM状态，则UE可以根据RRC重配置消息中携带的SCG的配置信息配置SCG但不激活SCG，并且UE向网络A(或MN)旨示UE处于MUSIM状态的信息或用于指示SCG已配置但未被激活相关的信息(例如在RRC重配置完成消息中指示)，UE也可以不配置SCG而向网络A指示UE处于MUSIM状态的信息或用于指示SCG未配置的信息(例如在RRC重配置完成消息中指示)。
针对情况一，如果UE采用配置SCG但不激活SCG的操作具体包括：如果所述RRC重配置消息中不包含mrdc-SecondaryCellGroupConfig(这时可选的条件)并且如果RRC重配置消息中不包含scg-State并且UE不处于MUSIM状态，则执行无SN消息的SCG激活过程；可选的，如果RRC重配置消息中不包含scg-State并且UE处于MUSIM状态，则UE向网络MN指示UE处于MUSIM状态的信息或用于指示SCG已配置但未 被激活相关的信息(例如在RRC重配置完成RRCReconfigurationComplete消息中指示)，在这种情况下，UE不激活SCG。
针对情况一，如果UE采用不配置SCG具体包括：如果所述RRC重配置消息中包含SCG的配置信息并且所述SCG被配置为非激活态，或者如果RRC重配置消息中包含SCG的配置信息并且所述SCG被配置为激活态但UE不处于MISIM状态，则执行SCG的小区组配置。如果所述RRC重配置消息中不包含mrdc-SecondaryCellGroupConfig(这个条件是可选的)并且如果RRC重配置消息中包含SCG的配置信息并且不包含scg-State但UE处于MUSIM状态，则UE向网络MN指示UE处于MUSIM状态的信息或用于指示SCG未被配置的相关信息(例如在RRC重配置完成RRCReconfigurationComplete消息中指示)，在这种情况下，UE不执行SCG的小区组配置。
情况二(MN激活已配置的SCG)：UE接收到来自网络A(MN)的RRC重配置消息，所述RRC重配置消息在SRB1上传输，其中不包含scg-State以指示激活已配置SCG。这是针对MN激活已配置的SCG情况。在这种情况下，如果UE处于MUSIM状态且UE认为网络B的优先级更高，则不激活SCG。如果UE决定不激活SCG，则UE向网络MN指示UE处于MUSIM状态的信息或用于指示SCG未被激活相关的信息(例如在RRC重配置完成消息中指示)。
具体的，如果RRC重配置消息接收自SRB1且UE处于NR-DC且所述RRC重配置消息中不包含mrdc-SecondaryCellGroupConfig(这个条件是可选的)且如果所述RRC重配置消息中不包含scg-State并且UE不处于MUSIM状态，则执行无SN消息的SCG激活过程；如果RRC重配置消息接收自SRB1且UE处于NR-DC且所述RRC重配置消息中不包含mrdc-SecondaryCellGroupConfig且如果所述RRC重配置消息中不包含scg-State但UE处于MUSIM状态，则UE向网络MN指示UE处于MUSIM状态的信息或用于指示SCG未被激活相关的信息(例如在RRC重配置完成消息中指示)，在这种情况下，UE不激活SCG。
情况三(SN配置SCG且MN激活SCG)：UE在SRBl上接收到包含 在mrdc-SecondaryCellGroup字段中hr-SCG字段的第一RRC重配置消息，包含所述第一RRC重配置消息的RRC消息(例如，第二RRC重配置消息)中不包含scg-State字段以指示SCG被配置为激活态。这是针对SCG的配置信息完全由SN提供，并且MN配置SCG处于激活态的情况。在这种情况下，如果UE处于MUSIM状态，则UE可以不配置SCG或者UE配置但不激活SCG，可选的，UE向网络MN和/或SN指示UE处于MUSIM状态的信息或SCG未被配置的信息或SCG已配置但未被激活的信息。
针对情况三，如果UE采用不配置SCG具体包括：如果第一RRC重配置消息是在SRBl上接收到的包含在mrdc-SecondaryCellGroup字段中nr-SCG字段的RRC重配置消息并且如果所述第一RRC重配置消息中包含secondaryCellGroup，则：
如果包含所述第一RRC重配置消息的RRC消息中包含scg-State，则执行SCG的小区组配置；如果包含所述第一RRC重配置消息的RRC消息中不包含scg-State且UE不处于MUSIM状态，则执行SCG的小区组配置；反之，如果如果包含所述第一RRC重配置消息的RRC消息中不包含scg-State且UE处于MUSIM状态，则不执行SCG的小区组配置；可选的，如果在SRB1上接收到包含在mrdc-SecondaryCellGroup字段中nr-SCG字段的第一RRC重配置消息，并且包含第一RRC重配置消息的RRC消息(例如第二RRC重配置消息)中不包含scg-State并且UE处于MUSIM状态，则UE向网络MN和/或SN指示UE处于MUSIM状态的信息或SCG未被配置的信息。
针对情况三，如果UE采用配置SCG但不激活SCG具体包括：如果第一RRC重配置消息是在SRBl上接收到的包含在mrdc-SecondaryCellGroup字段中nr-SCG字段的RRC重配置消息并且如果所述第一RRC重配置消息中包含secondaryCellGroup，则：
如果所述第一RRC重配置消息是在SRB1上接收到的包含在mrdc-SecondaryCellGroup字段中hr-SCG字段的RRC重配置消息，并且包含所述第一RRC重配置消息的RRC消息中不包含scg-State，如果UE不处于MUSIM状态，则配置SCG并执行SCG激活的操作；可选的，如果包含所述第一RRC重配置消息的RRC消息中不包含scg-State，但UE处于 MUSIM状态，则配置SCG并UE向网络A(MN和/或SN)指示UE处于MUSIM状态的信息或SCG已被配置但未被激活的信息。
情况四(SN发起的SCG改变且MN激活SCG)：UE在SRBl上接收到包含在mrdc-SecondaryCellGroup字段中nr-SCG字段的第一RRC重配置消息，包含所述第一RRC重配置消息的RRC消息(例如，第二RRC重配置消息)中不包含scg-State字段以指示SCG被配置为激活态，如果nr-SCG字段中的spCellConfig字段包含reconfigurationWithSync：
如果UE不处于MUSIM状态，则在PSCell上启动(initiate)随机接入。
如果UE处于MUSIM状态，则UE直到退出MUSIM状态才发起随机接入；或者，如果UE处于MUSIM状态，则UE在应答消息中指示UE处于MUSIM状态(此时UE不在PSCell上启动随机接入)。所述应答消息可以时RRC重配置完成消息，UE处于MUSIM状态的指示信息可以仅在发送给MN的应答消息中指示，也可以仅在通过MN转发给SN的应答消息中指示，还可以同时在发送给MN的应答消息和在通过MN转发给SN的应答消息中指示。
在本公开中，可以限制MUSIM和DAPS不能同时配置，或者如果UE处于MUSIM状态，则不能配置DAPS切换。
图5是用于说明本说明书中的第三实施方式提供的由用户设备执行同步重配置的方法的示例性流程图。
如图5所示，在S502，从第一网络接收RRC重配置消息。
然后，在S504，确定所接收到的RRC重配置消息是否包括针对辅服务小区组的配置信息。
针对辅服务小区组的配置信息例如可以是用于辅服务小区组变更的配置信息，此时RRC重配置消息可以指示对目标辅服务小区组进行配置。在此所谓的辅服务小区组变更是指至少变更辅服务小区组的主辅小区PSCell，即从当前主辅小区变更到不同于当前主辅小区的目标主辅小区。
针对辅服务小区组的配置信息例如还可以是用于改变用户设备当前 所在辅服务小区组的配置信息。此时，RRC重配置消息可以指示对用户设备当前所在辅服务小区组进行改变。在此，改变是指改变当前所在辅服务小区组的可配置参数，例如配置辅服务小区组为激活态、增加或释放辅服务小区组的SCell。
当在S504中确定为RRC重配置消息包括针对辅服务小区组的配置信息时，在S506，确定用户设备是否处于MUSIM状态。
若用户设备处于MUSIM状态，则在S508，不执行包括使辅服务小区组为激活态的辅服务小区组配置，并向网络发送表示用户设备处于MUSIM状态的应答消息。所谓不执行包括使辅服务小区组为激活态的同步重配置，例如可以是不执行RRC重配置消息所指示的辅服务小区组配置，或执行辅服务小区组配置但不使辅服务小区组为激活态(即使辅服务小区组为非激活态)。
若RRC重配置消息不包括针对辅服务小区组的配置信息(S504中的否)或用户设备不处于MUSIM状态(S506中的否)，则在S510，执行由RRC重配置消息指示的重配置。
以下对第三实施方式的具体实施例进行说明。
切换HO
至少具有双收双发能力的UE在网络A和网络B都处于RRC连接态时，接收到来自网络A的RRC重配置消息指示UE执行同步重配置过程，其中包含激活SCG的指示标识但UE认为网络B的优先级更高时所涉及的相关问题，以避免处于MUSIM状态的UE激活SCG并使得UE和网络A中SCG状态一致。在本公开实施例中，UE在实施同步重配置或切换时，当前MCG或SCG称为源MCG或源SCG，同步重配置或切换到的MCG或SCG称为目标MCG或目标SCG。
以下描述UE在接收到来自MN的用于切换的RRC重配置消息(即RRC重配置消息中包含masterCellGroup字段，并且masterCellGroup字段中包含的spCellConfig字段中含有reconfigurationWithSync字段，也即MCG的同步重配置)时执行的操作的实施例。
在本实施例中，UE接收到来自MN的用于切换的RRC重配置消息，如果满足以下条件A1-A3之一，则UE执行同步重配置(reconfiguration  with sync)，具体见TS38.331最新版本；
条件A1：所述RRC重配置消息中不包含SCG的配置信息(即RRC重配置消息中不包含secondaryCellGroup字段和mrdc-SecondaryCellGroupConfig字段)。
条件A2：所述RRC重配置消息中包含SCG的配置信息(即RRC重配置消息中包含secondaryCellGroup字段或mrdc-SecondaryCellGroupConfig字段)，并且接收到的RRC重配置消息中包含scg-State字段。
条件A3：所述RRC重配置消息中包含SCG的配置信息(即RRC重配置消息中包含secondaryCellGroup字段或mrdc-SecondaryCellGroupConfig字段)，并且接收到的RRC重配置消息中不包含scg-State字段，并且UE不处于MUSIM状态。
UE接收到来自网络A(MN)的用于切换的RRC重配置消息，如果满足以下条件B：
条件B：所述RRC重配置消息中包含SCG的配置信息，并且接收到的RRC重配置消息中不包含scg-State字段，并且UE处于MUSIM状态。
则在一种实施方式中，UE在应答消息中指示UE处于MUSIM状态相关的信息(此时，UE不执行同步重配置，RRC重配置过程结束，可选的，UE恢复原来的配置)；在另一种实施方式中，UE执行MCG同步重配置并配置SCG但不激活或不配置SCG，并在应答消息中指示UE处于MUSIM状态相关的信息或指示SCG已配置但未激活的信息或指示SCG未配置的信息。所述应答消息可以是RRC重配置完成消息RRCReconfigurationComplete。
SCG改变
至少具有双收双发能力的UE在第一网络(记为网络A)和第二网络(记为网络B)都处于RRC连接态时，接收到来自网络A的RRC重配置消息指示UE执行SCG改变过程，但UE处于MUSIM状态时所涉及的相关问题，以避免处于MUSIM状态的UE激活SCG并使得UE和网络A中SCG状态一致。
以下具体描述UE在接收到来自MN的用于改变SCG的RRC重配置消息(即RRC重配置消息中包含secondaryCellGroup字段或mrdc-Secon daryCellGroupConfig字段，并且secondaryCellGroup字段或mrdc-SecondaryCellGroupConfig字段中包含的spCellConfig字段中含有reconfigurationWithSync字段，也即SCG的同步重配置)时执行的操作的实施例。
在本实施例中，UE接收到来自网络A(MN)的用于改变SCG的RRC重配置消息，如果满足以下条件C1-C4之一，则UE执行SCG同步重配置(reconfiguration with sync)(也称为SCG改变)，具体见TS38.331最新版本；：
条件C1：所述接收到的RRC重配置消息中包含scg-State字段。
条件C2：所述接收到的RRC重配置消息中不包含scg-State字段，并且UE不处于MUSIM状态。
条件C3：包含所述RRC重配置消息的RRC消息中包含scg-State字段。
条件C4：包含所述RRC重配置消息的RRC消息中不包含scg-State字段，并且UE不处于MUSIM状态。
UE接收到来自MN的用于改变SCG的RRC重配置消息，如果满足以下条件D1-D2之一：
条件DI：所述接收到的RRC重配置消息中不包含scg-State字段，并且UE处于MUSIM状态。
条件D2：包含所述RRC重配置消息的RRC消息中不包含scg-State字段，并且UE处于MUSIM状态。
在一种实施方式中，UE在应答消息中指示UE处于MUSIM状态相关的信息(此时，UE不执行SCG同步重配置，RRC重配置过程结束，可选的，UE恢复原来的配置)或指示SCG同步重配置未执行的相关信息；在另一种实施方式中，UE按照RRC重配置消息执行SCG同步重配置但认为SCG是去激活的，即按照RRC重配置消息中包含scg-State字段的情况执行RRC重配置消息但认为SCG是去激活的，UE在应答消息中指示UE处于MUSIM状态相关的信息或者指示SCG同步重配置已执行但SCG未激活的相关信息。所述应答消息可以是RRC重配置完成消息RRCReconfigurationComplete。UE处于MUSIM状态的指示信息可以仅在发送给MN的应答消息中指示，也可以仅在通过MN转发给SN的应答消息中指示，也可以同时在发送给MN的应答消息和在通过MN转发给SN 的应答消息中指示。在又一种实施方式中，UE发起SCG失效信息传输过程，在SCG失效信息消息中指示UE处于MUSIM状态。
本公开实施例中，包含RRC重配置消息的RRC消息可以是RRC重配置消息或者RRC恢复消息。
本说明书的第四实施例提供一种由用户设备执行条件同步重配置的方法，包括：当用户设备处于MUSIM状态时，即便用户设备被配置为需要执行条件重配置，也不执行所述条件重配置；以及当用户设备不处于MUSIM状态且用户设备被配置为需要执行条件重配置，并且在执行条件重配置的条件评估之后的评估结果为满足重配置条件时，执行条件重配置。
以下结合图6和图7对第四实施例的具体示例进行说明。
图6是用于说明本说明书中的第四实施方式提供的由用户设备执行同步重配置的方法的示例性流程图。
如图6所示，在S602～S604，确定用户设备是否处于MUSIM状态。
当用户设备不处于MUSIM状态时，在S606，执行条件重配置的评估。并且，在S608，确定评估结果是否是满足重配置条件。
在评估结果为满足重配置条件时，在S610，执行条件重配置。
当用户设备处于MUSIM状态(S604中的是)或不满足重配置条件(S608中的否)时，在S612，不执行条件重配置。由此，避免在执行条件重配置后将SCG激活。
图7是用于说明本说明书中的第四实施方式提供的由用户设备执行同步重配置的方法的另一示例性流程图。
如图7所示，在S702，当用户设备被配置为需要执行条件重配置时，执行条件重配置的评估。并且，在S704，确定条件重配置的评估结果是否为满足重配置条件。
在条件重配置的评估结果为满足重配置条件时，在S708，确定用户设备是否处于MUSIM状态。
如果用户设备处于MUSIM状态，则在S712，不执行条件重配置。由此，避免在执行条件重配置后将SCG激活。如果用户设备不处于MUSIM状态，则在S710，执行条件重配置。
此外，当不满足重配置条件时，也不执行条件重配置。
在本实施方式中，当用户设备被指示执行条件重配置并且用户设备处于MUSIM状态时，可以向网络发送表示用户设备处于MUSIM状态的消息。
在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，如果确定为用户设备处于MUSIM状态时，则即便用户设备被配置为需要执行条件重配置，也不执行与条件重配置信息对应的条件重配置。这是为了避免在执行条件重配置之后激活辅服务小区组。
以下对第四实施方式的具体实施例进行说明。
条件同步重配置/条件PSCell增加/条件SCG改变(CHO/CPA/CPC)
至少具有双收双发能力的UE在第一网络(记为网络A)和第二网络(记为网络B)都处于RRC连接态时，UE被配置了CHO或CPA或CPC，当CHO或CPA或CPC条件被满足，但UE处于MUSIM状态时所涉及的相关问题，以避免处于MUSIM状态的UE激活SCG，使得UE和网络A中SCG状态一致。以下实施例中所述条件重配置包括：CHO、CPA、CPC。
在一个实施例中，当UE处于MUSIM状态或被网络A配置进入(或处于)MUSIM状态时，UE停止条件重配置的评估。换言之，当UE处于MUSIM状态或被网络A配置进入(或处于)MUSIM状态时，如果配置了条件重配置，UE停止条件重配置的评估。这是因为，如果UE执行条件重配置的评估，当UE检测到条件满足时，需要执行CHO或CPA，这两种行为都可能激活SCG。当UE退出MUSIM状态(或UE不处于MUSIM状态或向网络A发送退出MUSIM状态请求)时，如果配置了条件重配置，UE启动条件重配置的评估。可选的，仅当执行CHO的RRC重配置消息中包含SCG的配置信息但不包含scg-State，才停止CHO的条件重配置的评估。
在一个实施例中，如果UE被配置了条件重配置并且条件重配置的评估条件满足，如果UE不处于MUSIM状态，则启动条件重配置执行过程。 如果UE被配置了条件重配置并且条件重配置的评估条件满足，如果UE处于MUSIM状态，则UE向网络A指示UE处于MUSIM状态相关的信息或者UE退出MUSIM状态时执行条件重配置。具体的，条件重配置的评估条件满足是指对于变量VarConditionalReconfig中的每个condReconfigID，关联到保存的condRRCReconfig中目标候选小区的condTriggerConfig中的所有measId的事件被满足。可选的，当CHO的评估条件满足时，如果用于执行CHO的RRC重配置消息中包含SCG的配置信息时才在UE退出MUSIM状态时执行条件重配置或者向网络A指示UE处于MUSIM状态相关的信息。
以下参照图8至图10来对第五实施方式进行说明。
图8是用于说明本说明书中的第五实施方式提供的由用户设备执行的配置辅服务小区的方法的示例性流程图。
如图8所示，在S802，接收到来自第一网络的辅服务小区激活指示。
在接收到来自第一网络的辅服务小区激活指示时，在S804，确定用户设备是否处于MUSIM状态。在此，由辅服务小区激活指示所指示的辅服务小区可以与在第一网络中用户设备所在的处于激活态的其他辅服务小区或特殊服务小区之间采用频间载波聚合来传输数据。
当用户设备处于MUSIM状态时，在S806，不执行辅服务小区激活指示所指示的辅服务小区激活，并向第一网络发送表示处于MUSIM状态的指示消息。
当用户设备不处于MUSIM状态时，在S808，执行由辅服务小区激活指示所指示的辅服务小区激活。
辅服务小区激活指示可以被包含于RRC重配置消息，RRC重配置消息可以包括用于增加辅服务小区的增加配置信息。此时，可以参照图9的流程来增加辅服务小区。
如图9所示，在S902，基于增加配置信息增加对应的辅服务小区。
在S904，确定用户设备是否处于MUSIM状态。
当用户设备处于MUSIM状态时，在S906，使所增加的辅服务小区处于非激活态。当用户设备不处于MUSIM状态时，在S908，使所增加 的辅服务小区处于激活态。
RRC重配置消息还可以包括用于修改辅服务小区的修改配置信息。在该情况下，可以参照图10的流程来修改辅服务小区。
如图10所示，在S1002，基于修改配置信息来修改对应的辅服务小区。在S1004，确定用户设备是否处于MUSIM状态。
当用户设备处于MUSIM状态时，在S1006，使所修改的辅服务小区处于非激活态。当用户设备不处于MUSIM状态时，在S1008，使所修改的辅服务小区处于激活态。
在一个示例中，可以在用户设备的当前可用资源足以执行辅服务小区激活指示所指示的辅服务小区激活时，不管用户设备是否处于MUSIM模式，均执行所述辅服务小区激活。
此外，在一个示例中，在用户设备被第一网络配置为允许使用用户设备的部分硬件能力与第一网络进行通信的情况下，执行确定用户设备是否处于MUSIM状态的操作。在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，或在第一网络未被配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，当接收到来自第一网络的辅服务小区激活指示时，执行与辅服务小区激活指示对应的辅服务小区激活。
以下对第五实施方式的具体实施例进行说明。
以下考虑载波聚合CA情况下的SCell配置和激活场景
至少具有双收双发能力的UE在第一网络(记为网络A)和第二网络(记为网络B)都处于RRC连接态时，UE接收到来自网络A的激活SCell的指示，但处于MUSIM状态时所涉及的相关问题，以避免处于MUSIM状态的UE激活SCell，并使得UE和网络中SCell状态一致。
工作在载波聚合下的UE接收到来自网络的激活SCell的指示，如果UE不处于MUSIM状态，则UE配置下层认为SCell处于激活态或者激活SCell；如果UE处于MUSIM状态，则UE向网络发送指示信息以指示UE处于MUSIM状态或者SCell未激活(所述指示信息可以包含具体的小区标识信息)的信息，在这种情况下，UE不激活SCell。需要说明 的是，此处考虑的场景是网络指示激活的SCell与UE中当前处于激活态的SCell或PSCell是采用频间载波聚合，换言之当前处于MUSIM状态的UE的UE能力或资源无法支持激活这个/这些SCell或者即使激活这些SCell，由于UE能力受限，无法从这些SCell接收或发送数据。
所述激活SCell的指示可以是包含在RRC重配置消息中的sCellState字段，也可以是SCell激活/去激活媒体访问控制MAC控制元素CE或增强的SCell激活/去激活MAC CE。
UE接收到来自基站的RRC重配置消息，其中包含CellGroupConfig字段(所述字段可包含在masterCellGroup字段中)，基于接收到的CellGroupConfig字段，UE执行以下操作：
如果CellGroupConfig字段中包含sCellToAddModList字段，则执行SCell增加或修改。所述SCell增加或修改包括以下操作：
对于包含在sCellToAddModList中的不是目前UE配置的一部分的每个sCellIndex值(这是针对SCell增加的情况)执行以下操作至少一项：
(1)根据sCellConfigCommon和sCellConfigDedicated增加对应sCellIndex的SCell。
(2)如果包含sCellState(即SCell被配置为激活态)，并且UE不处于MUSIM状态，配置下层认为SCell处于激活态。如果包含sCellState但UE处于MUSIM状态，或者不包含sCellState(即SCell被配置为非激活态)，配置下层认为SCell处于非激活态。
对于包含在sCellToAddModList中的是目前UE配置的一部分的每个sCellIndex值(这是针对SCell修改的情况)执行以下操作至少一项：
(1)根据sCellConfigDedicated修改SCG配置。
(2)如果sCellToAddModList接收自包含reconfigurationWithSync的RRC重配置消息中，或者接收自包含reconfigurationWithSync的RRC重配置消息并且该RRC重配置消息包含在另一RRC重配置消息中：
如果其中包含sCellState并且UE不处于MUSIM状态，则配置下层认为SCell处于激活态。
如果其中包含sCellState但UE处于MUSIM状态或者其中不包含sCellState，则配置下层认为SCell处于非激活态。
UE在应答消息中指示UE处于MUSIM状态相关的信息或指示SCell未被激活的相关信息(可选的，仅在SCell被配置未激活态但UE处于MUSIM时才执行此操作)。所述应答消息可以是RRC重配置完成消息RRCReconfigurationComplete。
在一个实施例中，如果UE接收到来自网络的RRC消息配置并激活一个与PSCell不同频的SCell，在UE不配置所述SCell，并向网络发送UE处于MUSIM状态的指示信息或SCell为配置的指示信息，可选的，其中包含未配置的SCell标识。换言之，如果UE接收到来自网络的RRC消息配置(或激活)一个与PSCell同频的SCell，在UE配置(或激活)所述SCell。
以下考虑载波聚合下，UE接收到来自基站的SCell激活/去激活MAC C E或增强的SCell激活/去激活MAC CE的场景
对于每个配置的SCell，MAC实体执行以下操作：
如果在SCell配置时所述SCell被配置为激活态，即所述SCell被配置了值设置为“activated”(即用于指示激活SCell的值)的sCellState，或者接收到一个SCell激活/去激活MAC CE或者增强的SCell激活/去激活MAC CE来激活所述SCell，则进行以下操作：
(1)如果UE不处于MUSIM状态，进一步的，在满足(A)如果在接收到一个SCell激活/去激活MAC CE或者增强的SCell激活/去激活MAC CE前所述SCell是去激活的，或者(B)如果在SCell配置时所述SCell被配置的sCellState被设置为“activated”时，执行以下操作至少一项：
(a)如果firstActiveDownlinkBWP-Id没有被设置为休眠BWP，则激活SCell；否则，停止本服务小区的bwp-InactivaityTImer；
(b)激活firstActiveDownlinkBWP-Id和firstActiveUplinkBWP-Id指示的下行部分带宽BWP和上行BWP。
(2)否则(即UE处于MUSIM状态)，则向网络指示UE处于MUSIM状态的信息或指示SCell未被激活的相关信息，此时不激活SCell。具体的，可以定义一个MAC CE或重用已有MAC CE，在所述MAC CE中携带用于指示UE处于MUSIM状态的信息或指示SCell未被激活的相关信息。
本公开中，去激活和非激活含义相同，可替换使用。
图11是用于说明本说明书中的第六实施方式提供的由用户设备执行的方法的示例性流程图。
如图11所示，在S1102，确定在第一网络中是否存在需要通过SCG DRB来传输的上行数据。
当用户设备在第一网络中存在需要通过SCG DRB来传输的上行数据时，确定是否满足预定条件。即，在S1104，确定对应于该SCG DRB的辅服务小区组是否处于非激活态。如果辅服务小区组处于非激活态，则在S1106，确定用户设备是否处于MUSIM状态。
如果满足上述预定条件，则在S1110，向第一网络发送SCG DRB的上行数据指示信息，上行数据指示信息用于向第一网络指示有针对SCG DRB的上行数据到达。此处的“到达”是相对于用户设备的收发模块而言的(例如，用户设备针对此RRC连接的RRC实体确定有针对SCG DRB的上行数据要发送)。第一网络在收到上行数据指示信息后，可以为第一网络配置相应的MCG资源，以用于传输上行数据。
如果SCG处于激活态(S1104判定为否)，则在S1108，通过激活态的SCG来传输上行数据。
当对应于该SCG DRB的辅服务小区组处于非激活态，但用户设备不处于MUSIM状态时，即当S1104判定为是但S1106判定为否时，在S1112，向第一网络发送表示存在需要通过SCG DRB来传输的上行数据的指示消息，该指示消息用于指示UE有针对去激活态SCG的上行数据。第一网络在收到该指示消息时，可以为用户设备配置激活的SCG，以用于传输上述上行数据。
上行数据指示信息例如可以包括针对上行数据的SCG DRB的标识信息或SCG RLC实体的逻辑信道标识。
在一个示例中，除S1104和S1106所示出的条件以外，预定条件还可以包括以下中的任一者：用户设备尚未针对上行数据而向网络发送过上行数据指示信息；在用户设备进入当前的MUSIM状态之后尚未针对所述上行数据而向网络发送过上行数据指示信息；用于禁止发送所述上行数据 指示信息的禁止定时器不处于运行状态，禁止定时器在发送上行数据指示信息时被启动。禁止定时器用于限制发送上行数据指示信息的频率，避免过于频繁的信息发送。
在一个示例中，第一网络可以通过MUSIM状态释放指示来指示用户设备退出MUSIM状态。用户设备在收到该MUSIM状态释放指示时，可以根据自身的偏好来选择是否退出MUSIM状态。以下参照图12来进行说明。
图12是用于说明本说明书中的第六实施方式提供的由用户设备执行的方法中MUSIM释放指示处理过程的示例性流程图。
在S1202，从第一网络接收MUSIM状态释放指示。
在收到MUSIM状态释放指示时，在S1204，确定是否能够退出MUSIM状态。换言之，在S1204，确定当前用户设备是否偏好退出MUSIM状态。
如果在S1204判定为是，则在S1206，响应于MUSIM状态释放指示而退出MUSIM状态，以使得能够在第一网络中激活相应的辅服务小区组。并且，接着在S1208，向第一网络发送表示已退出所述MUSIM状态的应答消息。
当用户设备确定不能退出MUSIM状态时(S1204中的否)，则在S1210向第一网络发送表示MUSIM状态被维持的请求消息。该请求消息可以包括表示用户设备仍然处于MUSIM状态的信息。例如，当用户设备认为在与第一网络不同的第二网络中有更紧急的数据需要传输或认为在第二网络中传输的数据的优先级更高，则可以确定为当前偏好不退出MUSIM状态。
此外，在一个示例中，若是否允许用户设备使用其部分硬件能力与第一网络通信由第一网络来配置，则在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，预定条件包括用户设备处于MUSIM状态。在用户设备被第一网络配置为不允许仅使用用户设备的部分硬件能力与第一网络进行通信或未被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，如果用户设备更偏好维持与第二网络的RRC连接，则释放与第一网络的RRC 连接。
以下对第六实施方式的具体实施例进行详细说明。
以下说明当SCG DRB的上行数据到达但UE处于MUSIM状态的场景
处于MUSIM状态的UE在网络A处于双连接状态，SCG被去激活，当UE有针对没有MCG RLC承载的数据无线承载DRB的上行数据到达，且UE尚未针对所述DRB的上行数据到达向网络发送过指示(所述条件可替换为：在UE最近一次进入MUSIM状态或UE在最近一次改变MUSIM状态后尚未针对所述DRB的上行数据到达向网络发送过指示，或者在此之前UE没有针对所述DRB的上行数据到达向网络发送过指示)，如果禁止定时器未运行(这个条件是可选的)时，UE向网络A指示针对所述DRB的上行数据到达，所述指示中可以包含所述DRB的DRB标识或对应的逻辑信道标识，可选的，启动所述禁止定时器。
具体的，如果SCG被去激活，并且UE有针对SCG RLC实体的上行数据要发送但在此之前UE没有针对所述SCG RLC实体的上行数据要发送(所述条件可替换为：在UE最近一次进入MUSIM状态或UE在最近一次改变MUSIM状态后尚未针对所述SCG RLC实体的上行数据到达向网络发送过指示，或者在此之前UE没有针对所述SCG RLC实体的上行数据到达向网络发送过指示)，并且禁止定时器未运行(这个条件是可选的)，则启动传输UE辅助信息消息以指示UE有针对DRB标识(DRB-Identity)不包含在关联MCG的CellGroupConfig中的任何RLC-BearerConfig中的DRB的上行数据要发送，可选的，启动所述禁止定时器。
以下描述传输UE辅助信息消息过程：
如果启动传输UE辅助信息消息是为了提供UE有关于非激活SCG的上行数据的指示，进一步的，如果UE处于MUSIM状态，则在UE辅助信息消息中包含有上行数据要发送的SCG DRB的标识或有上行数据要发送的SCG RLC实体的逻辑信道标识；否则(UE不处于MUSIM状态)，在UE辅助信息消息中包含用于指示UE有针对SCG RLC实体或去激活态SCG的上行数据要发送的uplinkData字段。
当SCG被去激活且UE不处于MUSIM状态时，UE仅需要在UE辅助信息消息中包含指示UE有针对SCG RLC实体的上行数据要发送的uplinkData字段，网络在接收到这个消息后，可以激活SCG。但是当SCG被去激活且UE处于MUSIM状态时，UE需要在UE辅助信息消息中包含指示UE中有针对SCG RLC实体的上行数据要发送的SCG DRB的标识或对应的逻辑信道的标识，网络在收到这个消息后，可以将SCG DRB重配置为MCG DRB或分离DRB(即为所述SCG DRB增加MCG RLC承载)，从而减少SCG DRB的传输时延。
本公开中，没有MCG RLC承载的数据无线承载DRB是指SCG DRB或SCG RLC实体，也就是关联的RLC承载仅在SCG中的DRB，也就是仅配置了SCG RLC承载的DRB，也就是DRB-Identity不包含在关联MCG的CellGroupConfig中的任何RLC-BearerConfig中的DRB，这些表述可互换使用。此外，在本公开实施例中，可以交换启动禁止定时器和UE启动UE辅助信息消息以指示DRB的上行数据到达的操作。RLC承载和RLC实体可互换使用。
以下考虑当SCG DRB下行数据到达但UE处于MUSIM状态的场景
当UE处于MUSIM状态，如果网络A需要在SCG执行高优先级业务或紧急业务，例如在网络A有针对SCG DRB的下行数据到达，网络A需要向UE指示相关信息，使得UE可根据指示信息决定是否释放与另一网络的RRC连接或释放在网络A的UE能力限制。
具体的，UE接收到来自网络的RRC消息，例如RRC重配置消息，其中包含一个字段用于指示UE退出MUSIM状态或指示UE在网络A释放UE能力限制。UE可以在应答消息中指示UE退出或保持MUSIM状态或者UE释放或维持(或请求)在网络A的能力限制。所述应答消息可以是RRC重配置完成消息或UE辅助信息消息。
图13是用于说明本说明书中的第七实施方式提供的由用户设备执行的用于恢复RRC连接的方法的示例性流程图。
在S1302，向第一网络发送请求恢复与第一网络的RRC连接的RRC 恢复请求消息。
然后，在S1304，接收来自第一网络的RRC恢复消息。
接着在S1306，确定所接收到的RRC恢复消息是否指示激活辅服务小区组。
当RRC恢复消息指示激活辅服务小区组时，在S1308，确定用户是否偏好不激活辅服务小区组。
如果用户设备偏好不激活辅服务小区组，则在S1310，向第一网络发送表示用户设备偏好不激活辅服务小区组的指示信息。在一个示例中，指示信息还包括表示以下中的任一者的信息：RRC恢复消息所指示的新辅服务小区组未被配置；RRC恢复消息所指示的新辅服务小区组被配置但未被激活；RRC恢复消息所指示的已有辅服务小区组未被恢复；RRC恢复消息所指示的已有辅服务小区被恢复但未被激活。
如果RRC恢复消息未指示激活辅服务小区组，或RRC恢复消息指示激活辅服务小区组但用户设备并不偏好不激活辅服务小区组，则在S1312，根据据所接收到的RRC恢复消息来恢复与第一网络的RRC连接。
在一个示例中，如果用户设备偏好不激活辅服务小区组，则可以执行以下中的任一者：当RRC恢复消息指示配置新辅服务小区组时，根据RRC恢复消息，配置新辅服务小区但不激活该新辅服务小区组；当RRC恢复消息指示配置新辅服务小区组时，不执行RRC恢复消息指示的新辅服务小区组配置；当RRC恢复消息指示恢复已有辅服务小区组时，不执行RRC恢复消息所指示的已有辅服务小区组恢复；当RRC恢复消息指示恢复已有辅服务小区组时，恢复RRC恢复消息所指示的已有辅服务小区组，但不激活该已有辅服务小区组。
在一个示例中，在由RRC恢复消息所指示的辅服务小区与在第一网络中用户设备所在的处于激活态的其他辅服务小区或主服务小区PCell之间采用频间载波聚合来传输数据的情况下，当RRC恢复消息指示激活的辅服务小区与主服务小区工作在不同频带下时，如果用户设备偏好不激活辅服务小区，则向所述第一网络发送表示用户设备偏好不激活辅服务小区的指示信息。
在一个示例中，如果由第一网络来配置是否允许使用用户设备的部分 硬件能力与第一网络通信，则在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，当RRC恢复消息指示激活辅服务小区组时，如果用户设备偏好不激活所述辅服务小区组，则可以向第一网络发送表示用户设备偏好不激活辅服务小区组的指示信息。
图14是用于说明本说明书中的第八实施方式提供的由用户设备执行的用于恢复RRC连接的方法的示例性流程图。
如图14所示，确定用户是否偏好不激活辅服务小区组。
如果用户设备偏好不激活辅服务小区组，则在S1404，向第一网络发送请求恢复在第一网络中的RRC连接的RRC恢复请求消息，该RRC恢复请求消息包括表示用户设备偏好不激活所述辅服务小区组的指示信息。反之，如果用户设备并不偏好不激活辅服务小区组，则在S1406，发送不包括上述指示信息的RRC恢复请求消息。作为示例，用户设备偏好不激活辅服务小区组的情形可以包括用户设备处于MUSIM状态。
在一个示例中，如果由第一网络来配置是否允许使用用户设备的部分硬件能力与第一网络通信，则在用户设备被第一网络配置为允许仅使用用户设备的部分硬件能力与第一网络进行通信的情况下，如果用户设备偏好不激活辅服务小区组，则可以向第一网络发送包括表示用户设备偏好不激活辅服务小区组的指示信息的RRC恢复请求消息。
然后，在S1408，接收来自第一网络的RRC恢复消息。
并且，在S1410，基于RRC恢复消息，恢复与第一网络的RRC连接。
在一个示例中，如果根据用户设备所保存的上下文信息确定出当在第一网络中进入RRC连接态时需要激活辅服务小区组，并且用户设备不偏好激活该辅服务小区组，则在RRC恢复请求消息中包括表示用户设备不偏好激活辅服务小区组的指示信息。这是为了避免第一网络在为用户设备提供用于恢复RRC连接的配置时配置为激活辅服务小区组。
在向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC恢复请求消息的情况下，如果确定所述用户设备在所述第一网络中处于双连接状态，则释放关于所述双连接状态的配置信息。
以下对第七和第八实施方式的具体实施例进行详细说明。
以下考虑处于MUSIM状态的UE请求恢复在网络A的RRC连接的场景
UE在网络A处于RRC非激活态(即RRC连接被挂起)，在网络B处于RRC连接态。UE向网络A发送RRC恢复请求RRCResumeRuest消息，请求恢复在网络A的RRC连接。网络A在接收到所述恢复请求消息后，可向UE发送RRC恢复消息以恢复挂起的RRC连接。在所述RRC恢复消息中，可以指示是否激活SCG。如果RRC恢复消息中指示激活SCG，由于UE处于MUSIM状态，如果UE认为网络B的优先级更高，则将不释放与网络B的RRC连接，导致UE无法在网络A中与SCG通信。但是网络A认为SCG已激活，并在SCG上进行数据传输，而此时UE没有能力接收在SCG上传输的数据，这将导致网络A的资源浪费。
以下提供实施例解决这一问题。
在一个实施例中，如果UE处于MUSIM状态或者UE偏好不激活SCG(或偏好SCG处于非激活态)，则在RRC恢复请求消息中包含一个指示信息，用于指示UE处于MUSIM状态或者UE偏好不激活SCG或偏好SCG处于非激活态。
具体的，UE按照如下方式设置RRC恢复请求消息的内容：如果UE处于MUSIM状态，则在RRC恢复请求消息中包含用于指示UE处于MUSIM状态的指示信息或包含是否偏好激活SCG的指示信息。具体的，可以定义一个新的字段用于指示UE处于MUSIM状态或偏好不激活SCG或偏好SCG处于非激活态的指示信息。如果UE处于MUSIM状态或UE偏好不激活SCG或偏好SCG处于非激活态，则在RRC恢复请求消息中包含所述字段，否则，在RRC恢复请求消息中不包含所述字段。可选的，仅当UE保存的上下文中SCG处于激活态或SCG在UE进入RRC非激活态之前处于激活态，UE在RRC恢复请求消息中包含UE处于MUSIM状态或者指示偏好不激活SCG或偏好SCG处于非激活态的指示信息。
UE将用于传输的RRC恢复请求消息递交下层。
需要说明的是，所述实施例应用于载波聚合的场景时，所述指示信息用于指示UE处于MUSIM状态或UE偏好不激活SCell或UE偏好不激活与PCell异频的SCell。可选的，仅当已配置的SCell中存在与PCell异 频的SCell时才在RRC恢复请求消息中包含所述指示信息。
做为上述实施例的变形，在UE偏好激活SCG或偏好SCG处于激活态时才在RRC恢复请求消息中包含指示信息，用于指示UE偏好激活SCG或偏好SCG处于激活态。
在一个实施例中，如果UE接收来自基站的RRC恢复RRCResume消息，其中不包含配置SCG处于非激活态的指示scg-State，如果UE处于MUSIM状态，则UE不激活SCG。可选的，UE向网络发送指示信息，用于指示UE处于MUSIM状态或者SCG未激活或SCG未配置。所述指示信息可以包含在RRC恢复完成消息中。
需要说明的是，在本实施例中，如果UE处于MUSIM状态，UE可以根据接收到的RRC恢复消息配置或恢复SCG，或者不配置或不恢复SCG。具体的，如果RRC恢复消息中包含restoreSCG且UE不处于MUSIM状态，则UE从UE非激活AS上下文(context)恢复mrdc-SecondaryCellGroup。换言之，如果RRC恢复消息中包含restoreSCG且UE处于MUSIM状态，或RRC恢复消息中不包含restoreSCG，则从UE非激活AS上下文中释放MR-DC相关的配置。
其中restoreSCG字段用于指示UE从UE非激活AS上下文恢复(restore)SCG配置。
在一个实施例中，UE向网络A发送RRC恢复请求消息，并接收来自网络的RRC恢复消息。如果UE具有MUSIM能力或者UE是配置了多SIM的UE(UE已经向网络上报了其多SIM能力)，则所述RRC恢复消息中配置SCG处于非激活态，即RRC恢复消息中包含scg-State字段。换言之，对于配置了MUSIM的UE，在恢复RRC连接时只能配置处于非激活态的SCG或不配置SCG。
在一个实施例中，UE在发起RRC连接恢复过程时，如果UE处于NR-DC，并且UE处于MUSIM状态，则从UE非激活AS上下文中释放MR-DC相关的配置。
在一个实施例中，如果UE接收到来自基站的RRC恢复消息，其中包含配置与PCell不同频的SCell处于激活态的指示sCellState，如果UE处于MUSIM状态，则UE不激活所述SCell或配置但不激活所述SCell 或不配置所示SCell。可选的，UE向网络发送指示信息，用于指示UE处于MUSIM状态或者SCell未激活或SCell未配置或SCell已配置但未激活。所述指示信息可以是未激活或未配置的SCell的标识，所述指示信息可以包含在RRC恢复完成消息中。
在本公开实施例中，从UE非激活AS上下文中释放MR-DC相关的配置包括：释放SRB3(针对SRB3已经建立的情况)、释放SCG关联的measConfig、释放SCG配置等。
图15是本说明书中提供的用户设备的框图。如图15所示，该用户设备UE40包括处理器151和存储器152。处理器151例如可以包括微处理器、微控制器、嵌入式处理器等。存储器42例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器152上存储有程序指令。该指令在由处理器151运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
本公开实施例中，如果在执行某个或某些操作前需要判断是否满足多个条件，交换这些判断条件的执行顺序得到的实施例也是本公开保护的范围。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、 磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的用于恢复RRC连接的方法，包括：
    向第一网络发送请求恢复与所述第一网络的RRC连接的RRC恢复请求消息；
    接收来自第一网络的RRC恢复消息；
    当所述RRC恢复消息指示激活辅服务小区组时，如果所述用户设备偏好不激活所述辅服务小区组，则向所述第一网络发送表示所述用户设备偏好不激活所述辅服务小区组的指示信息。
  2. 根据权利要求1所述的方法，其中，还包括：
    如果所述用户设备偏好不激活所述辅服务小区组，则执行以下中的任一者：
    当所述RRC恢复消息指示配置新辅服务小区组时，根据所述RRC恢复消息，配置所述新辅服务小区但不激活该新辅服务小区组；
    当所述RRC恢复消息指示配置新辅服务小区组时，不执行所述RRC恢复消息指示的新辅服务小区组配置；
    当所述RRC恢复消息指示恢复已有辅服务小区组时，不执行所述RRC恢复消息所指示的已有辅服务小区组恢复；
    当所述RRC恢复消息指示恢复已有辅服务小区组时，恢复所述RRC恢复消息所指示的已有辅服务小区组，但不激活该已有辅服务小区组。
  3. 根据权利要求1所述的方法，其中，所述指示信息还包括表示以下中的任一者的信息：
    所述RRC恢复消息所指示的新辅服务小区组未被配置；
    所述RRC恢复消息所指示的新辅服务小区组被配置但未被激活；
    所述RRC恢复消息所指示的已有辅服务小区组未被恢复；
    所述RRC恢复消息所指示的已有辅服务小区被恢复但未被激活。
  4. 根据权利要求1所述的方法，其中，还包括：
    在由所述RRC恢复消息所指示的辅服务小区与在所述第一网络中所述用户设备所在的处于激活态的其他辅服务小区或主服务小区之间采用频间载波聚合来传输数据的情况下，当所述RRC恢复消息指示激活的辅服务小区与主服务小区工作在不同频带下时，如果所述用户设备偏好不激活所述辅服务小区，则向所述第一网络发送表示所述用户设备偏好不激活所述辅服务小区的指示信息。
  5. 根据权利要求1所述的方法，其中，还包括：
    在所述用户设备被所述第一网络配置为允许仅使用所述用户设备的部分硬件能力与所述第一网络进行通信的情况下，当所述RRC恢复消息指示激活辅服务小区组时，如果所述用户设备偏好不激活所述辅服务小区组，则向所述第一网络发送表示所述用户设备偏好不激活所述辅服务小区组的指示信息。
  6. 一种由用户设备执行的用于恢复RRC连接的方法，包括：
    向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC恢复请求消息，如果所述用户设备偏好不激活辅服务小区组，则在所述RRC恢复请求消息中包括表示所述用户设备偏好不激活所述辅服务小区组的指示信息；
    接收来自第一网络的RRC恢复消息；以及
    基于所述RRC恢复消息，恢复与所述第一网络的RRC连接。
  7. 根据权利要求6所述的方法，其中，还包括：
    如果根据所述用户设备所保存的上下文信息确定出当在所述第一网络中进入RRC连接态时需要激活辅服务小区组，并且所述用户设备不希望激活所述辅服务小区组，则在所述RRC恢复请求消息中包括表示所述用户设备不希望激活所述辅服务小区组的指示信息。
  8. 根据权利要求6所述的方法，其中，还包括：
    在向第一网络发送请求恢复在所述第一网络中的RRC连接的RRC 恢复请求消息的情况下，如果确定所述用户设备在所述第一网络中处于双连接状态，则释放关于所述双连接状态的配置信息。
  9. 根据权利要求1-8中任一项所述的方法，其中，所述用户设备偏好不激活所述辅服务小区组包括所述用户设备处于MUSIM状态。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
PCT/CN2023/105702 2022-07-07 2023-07-04 由用户设备执行的用于恢复rrc连接的方法及用户设备 WO2024008071A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210807215.9 2022-07-07
CN202210807215.9A CN117440536A (zh) 2022-07-07 2022-07-07 由用户设备执行的用于恢复rrc连接的方法及用户设备

Publications (1)

Publication Number Publication Date
WO2024008071A1 true WO2024008071A1 (zh) 2024-01-11

Family

ID=89454384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/105702 WO2024008071A1 (zh) 2022-07-07 2023-07-04 由用户设备执行的用于恢复rrc连接的方法及用户设备

Country Status (2)

Country Link
CN (1) CN117440536A (zh)
WO (1) WO2024008071A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219787A (zh) * 2014-09-10 2014-12-17 电信科学技术研究院 一种恢复无线链路的方法和设备
CN113825187A (zh) * 2020-06-19 2021-12-21 维沃移动通信有限公司 小区组处理方法、装置及通信设备
CN114073167A (zh) * 2019-11-07 2022-02-18 联发科技股份有限公司 使能辅小区组挂起和恢复或主辅小区去激活和激活的方法及其装置
WO2022037948A1 (en) * 2020-08-17 2022-02-24 Nokia Technologies Oy Dual connectivity scenario for coordinated leave

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219787A (zh) * 2014-09-10 2014-12-17 电信科学技术研究院 一种恢复无线链路的方法和设备
CN114073167A (zh) * 2019-11-07 2022-02-18 联发科技股份有限公司 使能辅小区组挂起和恢复或主辅小区去激活和激活的方法及其装置
CN113825187A (zh) * 2020-06-19 2021-12-21 维沃移动通信有限公司 小区组处理方法、装置及通信设备
WO2022037948A1 (en) * 2020-08-17 2022-02-24 Nokia Technologies Oy Dual connectivity scenario for coordinated leave

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "[AT118-e][230][MUSIM] NR RRC corrections for MUSIM (vivo) Discussion and Agreement", 3GPP TSG-RAN WG2 MEETING #118-E R2-22XXXXX, vol. RAN WG2, no. Online, 9th – 20th May 2022, 20 May 2022 (2022-05-20), pages 1 - 15, XP093124628 *

Also Published As

Publication number Publication date
CN117440536A (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
US9113369B2 (en) Method for coordinating inter-cell interference and base station
KR101860585B1 (ko) 무선 통신 시스템에서 로그된 측정 수행 방법 및 장치
US9369960B2 (en) Method for operation based on switching discontinuous reception state in wireless communication system and apparatus for the same
US11937115B2 (en) Method for constructing logged measurement entry and device supporting the same
JP6431206B2 (ja) ページングシグナリングを減少させるための方法及び装置
KR20100129691A (ko) 무선 통신 시스템에서 측정 결과 보고 방법 및 장치
US20120300657A1 (en) Method and apparatus of limiting measurement reports
WO2014129850A1 (ko) 무선 통신 시스템에서 설정 핸들링 기반 운영 방법 및 이를 지원하는 장치
US11032730B2 (en) Method and device for terminal performing WLAN measurement
EP3288321B1 (en) Method for d2d operation performed by terminal in wireless communication system, and terminal using same
EP3397014B1 (en) Method for operating terminal in accordance with semi-persistent scheduling in wireless communication system, and terminal device using method
US20220038929A1 (en) Terminal device, base station device, method, and integrated circuit
WO2014035154A1 (ko) 무선 통신 시스템에서 자율적 서빙 셀 관리를 기반으로 한 통신 방법 및 이를 지원하는 장치
WO2014112853A1 (ko) 무선 통신 시스템에서 우선순위 핸들링 기반 운영 방법 및 이를 지원하는 장치
WO2022143754A1 (en) Method for maintaining multi-sim configuration and user equipment
WO2024008071A1 (zh) 由用户设备执行的用于恢复rrc连接的方法及用户设备
WO2024008074A1 (zh) 由用户设备执行同步重配置的方法及用户设备
WO2024008072A1 (zh) 由用户设备执行的配置辅服务小区的方法及用户设备
WO2024008067A1 (zh) 由用户设备执行的方法及用户设备
US20230276284A1 (en) Terminal apparatus, method, and integrated circuit
WO2024008069A1 (zh) 由用户设备执行的方法以及用户设备
JP2020077962A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2023185689A1 (zh) 由用户设备执行的方法以及用户设备
US20230328817A1 (en) Terminal apparatus, base station apparatus, method, and integrated circuit
KR102670815B1 (ko) 무선 이동 통신 시스템에서 기기내 공존을 위한 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23834838

Country of ref document: EP

Kind code of ref document: A1