WO2022199479A1 - 用户设备及其执行方法 - Google Patents

用户设备及其执行方法 Download PDF

Info

Publication number
WO2022199479A1
WO2022199479A1 PCT/CN2022/081667 CN2022081667W WO2022199479A1 WO 2022199479 A1 WO2022199479 A1 WO 2022199479A1 CN 2022081667 W CN2022081667 W CN 2022081667W WO 2022199479 A1 WO2022199479 A1 WO 2022199479A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
network
message
rrc
rrc connection
Prior art date
Application number
PCT/CN2022/081667
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 WO2022199479A1 publication Critical patent/WO2022199479A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present invention relates to the technical field of wireless communication, and more particularly, the present invention relates to a user equipment and an execution method thereof.
  • multi-SIM devices have become more and more popular.
  • a user installs two USIM cards on a mobile phone that supports multiple USIM cards, where one USIM card is used for subscribing to private services, and the other USIM card is used for subscribing to office services.
  • Existing devices supporting multiple USIM cards are implemented based on manufacturers and have not been standardized by 3GPP.
  • 3GPP 3rd Generation Partnership Project
  • different manufacturers adopt different implementation manners, and the behaviors of user equipment UEs are also different.
  • these USIM cards are registered with the network respectively (can be registered to the same network or to two or more networks respectively), the UE needs to receive paging from these networks through these USIM cards.
  • Transceiver capability there may be a situation that when the UE receives the paging of the current network through one USIM card, the network of another USIM card (which may be the same as the aforementioned network or may be different) also initiates paging to it, and then Or when the UE is communicating with one network through one USIM card, the network of another USIM card (which may be the same as or different from the aforementioned network) also initiates paging to it.
  • the network of another USIM card which may be the same as or different from the aforementioned network
  • the base station when the UE sends a RRCResumeRequest message for performing a RAN-based Notification Area Update (RAN-based Notification Area Update) to the base station, the base station can send a RRCResume message or an RRCRelease message as a response.
  • the UE receives the RRCResume message, it will execute the RRCResume message and enter the RRC connected state.
  • MUSIM ie, multi-SIM
  • the UE when the UE is in the RRC connected state in the network A, when the UE sends the RRCResumeRequest to the network B for performing the notification area update RNAU based on the wireless access network, it receives RRCResume message from network B.
  • the UE will also enter the RRC connected state in the network B.
  • the network A and the network B may be the same or different, and the same is true below.
  • the present disclosure aims to solve how to prevent a UE supporting multiple USIM cards from being in an RRC connected state simultaneously through multiple USIM cards in one or more networks.
  • the purpose of the present invention is to provide a user equipment and an execution method thereof, so as to avoid that a UE supporting multiple USIM cards is simultaneously in an RRC connection state through multiple USIM cards in one or more networks.
  • a method for executing user equipment where the user equipment supports multiple USIM cards that can be respectively connected to a network, that is, supports MUSIM
  • the executing method for the user equipment includes: the user equipment Send an RRCResumeRequest message for performing RNAU to the first network corresponding to the first USIM card; and the user equipment receives a response message from the first network, and the RRCResumeRequest message includes a message for indicating that the user equipment cannot communicate with An indication that the first network establishes an RRC connection.
  • the indication identifier is used to indicate that the user equipment is in an RRC connection state in a second network corresponding to a second SIM card different from the first USIM card, or,
  • the indication flag is used to indicate that the first network cannot reply to the RRCResume message or the RRCSetup message as the response message, or the indication flag is used to indicate that the user equipment does not expect to receive the RRCResume message or the RRCSetup message as the response message.
  • a response message, or the indication identifier is used to indicate that the user equipment expects the first network to send a RRCRelease message as the response message.
  • the value of the ResumeCause field in the RRCResumeRequest message is set to a value defined for the user equipment supporting MUSIM to execute RNAU.
  • the RRC layer of the user equipment indicates to the upper layer information that RNAU needs to be executed in the first network, and the upper layer determines whether the user equipment can communicate with the user equipment.
  • the first network establishes an RRC connection
  • the RRCResumeRequest message includes a message indicating that the user equipment cannot establish an RRC connection with the first network.
  • the indication identifier that the network establishes the RRC connection.
  • a method for executing user equipment where the user equipment supports multiple USIM cards that can be respectively connected to a network, that is, supports MUSIM
  • the executing method for the user equipment includes: the user equipment The device sends the RRCResumeRequest message for performing RNAU to the first network corresponding to the first USIM card; the user equipment receives the RRCResume message or the RRCSetup message from the first network as a response message; and the RRC layer of the user equipment will communicate with The information related to the RRCResume message or the RRCSetup message is indicated to the upper layer.
  • the upper layer of the RRC layer of the user equipment determines whether the user equipment can continue or establish an RRC connection with the first network.
  • the upper layer instructs the user equipment to release the RRC connection, and instructs the user equipment to establish an RRC connection with the first network, and the priority of the service on the first USIM card is lower than the one that is being executed with the first network.
  • the upper layer instructs the user equipment not to establish an RRC connection with the first network.
  • the RRCResume message or the RRCSetup message includes an RRC state to indicate that the user equipment should enter when the user equipment cannot continue or establish an RRC connection with the first network indicator.
  • the user equipment In the execution method of the above user equipment, preferably, if the response message contains suspendConfig and the upper layer determines that the user equipment cannot continue or establish an RRC connection with the first network, the user equipment will follow the The configuration indicated by suspendConfig enters the RRC inactive state. If the response message does not contain suspendConfig and the upper layer determines that the user equipment cannot continue or establish an RRC connection with the first network, the user equipment enters the RRC idle state. .
  • a user equipment that supports multiple USIM cards that can be respectively connected to a network, that is, supports MUSIM
  • the user equipment includes: a processor; and a memory that stores instructions; wherein, the instructions
  • the execution method of the user equipment described in any one of the above is executed when being run by the processor.
  • FIG. 1 is a flowchart showing an execution method of the user equipment according to the first embodiment of the present invention.
  • FIG. 2 is a flowchart showing an execution method of the user equipment according to the second embodiment of the present invention.
  • FIG. 3 is a block diagram showing a schematic configuration of a user equipment according to the present invention.
  • the present invention takes a user equipment UE (ie a multi-SIM device) configured with two SIM/USIM cards as an example to describe the embodiment, but it should be noted that the embodiment of the present invention is not limited to the corresponding UEs configured with two SIM/USIM cards. It can also be used in application scenarios where multiple SIM/USIM cards are configured.
  • the user equipment UE configured with two SIM/USIM cards refers to the user equipment UE that the UE can register with the two networks and establish a connection with the two networks or send and receive data respectively.
  • NAS Non-access stratum, non-access stratum.
  • AS access stratum, access layer.
  • DRB Data Radio Bearer
  • RRC Radio Resource Control, radio resource control.
  • RRC_CONNECTED RRC connected state.
  • RRC_INACTIVE RRC inactive state.
  • RRC_IDLE RRC idle state.
  • Radio Access Network radio access network
  • RNAU RAN-based Notification Area Update, RAN-based Notification Area Update.
  • New RAT New Radio Access Technology.
  • USIM Universal Subscriber Identity Module, global user identification card.
  • Tx transmitter, transmitter.
  • Rx receiver, receiver.
  • RRCResumeRequest or RRCResumeRequest1 is used to request to continue a suspended (suspended) RRC connection or execute RNAU; the information element suspendConfig is used to indicate the configuration of RRC_INACTIVE (Indicates configuration for the RRC_INACTIVE state).
  • RRCResumeRequest is uniformly used in the present invention, but an embodiment obtained by replacing RRCResumeRequest with RRCResumeRequest1 is also within the protection scope of the present invention.
  • the RRCResume message is used to continue a suspended RRC connection (The RRCResume message is used to resume the suspended RRC connection.); the RRCSetup message is used to establish the signaling radio bearer SRB1.
  • the RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection.
  • the RRCReject message is used to reject an RRC connection establishment or RRC connection continuation (The RRCReject message is used to reject an RRC connection establishment or an RRC connection resumption).
  • network can be used interchangeably, and the network can be a long-term evolution LTE network, an NR network, an enhanced long-term evolution eLTE network, or other networks defined in the subsequent evolution version of 3GPP.
  • the user equipment UE may refer to a device that physically supports multiple USIM cards (two or more USIM cards), the device is equipped with two or more USIM cards, and each USIM card is associated with a network.
  • the UE establishes an RRC connection with the network through different USIM cards respectively (the UE corresponding to the USIM card is in the RRC connection state in the network at this time) or resides in the network (the UE corresponding to the USIM card is in the RRC idle state in the network at this time) or RRC inactive state).
  • the network to which a USIM card is connected or registered or resides is the network corresponding to the USIM.
  • the multiple USIM cards may be from the same operator or different operators.
  • each USIM card corresponds to one UE
  • the core network and/or the base station respectively allocate a NAS and/or AS layer identifier to the UE corresponding to each USIM card, respectively.
  • the NAS layer identifier allocated by the core network to the UE corresponding to each USIM card is marked as 5G-S-TMSI or S-TMSI
  • the AS layer identifier allocated by the base station to the UE corresponding to each USIM card is marked as C-RNTI.
  • the NAS and/or AS layer identifiers allocated by the core network and/or the base station to UEs corresponding to different USIM cards are different.
  • a UE configured with multiple USIM cards has different NAS and/or AS layers corresponding to different USIM cards. logo. Unless otherwise specified, in this embodiment of the present invention, it is not clear whether the UE is a UE configured with multiple USIM cards or a UE corresponding to each USIM card in a device configured with multiple USIM cards. Those skilled in the art can easily determine whether the UE is a UE according to the context. Refers to the UE supporting multiple USIM cards (or the UE configured with multiple USIM cards) or the UE corresponding to each USIM card in the device supporting multiple USIM cards.
  • a UE configured with multiple USIM cards can receive and/or transmit data from multiple networks using single-receiver-single-transmit or dual-receiver-single-transmit by means of time division multiplexing, etc. For a UE with two Rx, it can receive data from two networks at the same time data.
  • the USIM described in the present invention may be a physical SIM or an eSIM (USIM can be a physical SIM or eSIM).
  • the UE is configured with two USIM cards as an example, and those skilled in the art can easily extend to the case of multiple USIM cards.
  • a user equipment UE with two USIM cards at least has a single-receive-single-transmit (Single-Rx/Single-Tx) or dual-receive-single-transmit (Dual-Rx/Single-Tx) capability.
  • Different UEs corresponding to two USIM cards can share a pair of Tx and Rx or share one Tx but have their own Rx.
  • the UE is connected to the network A through the USIM card A, and is connected to the network B through the USIM card B, and the switching of the UE between different networks is realized by switching the working USIM card.
  • the UE (or USIM card A) working in one network (network A, the first network) means that the UE is in the RRC connection state in the network A and monitors the network A (receives/transmits data or signaling from the network A), Meanwhile, the UE may leave network A periodically or intermittently to monitor another network (network B, second network), for example to receive paging messages from said network B or to measure another USIM card (ie USIM card B ), the signal quality of the serving cell, camping cell, or measurement object, etc.
  • Network A and Network B can be different networks or the same network.
  • the time information when the UE leaves the network A to receive the paging message from the network B or measure the signal quality of the serving cell or the camping cell of another USIM card or the measurement object is the scheduling gap (Scheduling gap) of the UE in the network A. Or called the scheduling interval for network B.
  • the scheduling gap the scheduling interval
  • the UE does not expect network A to schedule the UE, and the UE stops data transmission/reception in network A to receive paging messages from network B or measure another USIM card (ie USIM card B). ), the signal quality of the serving cell, the camped cell, or the measurement object, etc.
  • the scheduling interval of the UE in the network A refers to that when the UE works on the network A, within the time period indicated by the scheduling interval, the network A will not schedule the UE or the UE will not schedule the UE within the time period indicated by the scheduling interval No data is received from or expected to be scheduled by Network A.
  • the UE working in the network A described in the present disclosure may correspond to a handover procedure (referred to as the first handover procedure) for the UE to notify the network A reached by the RAN2 at the 3GPP RAN2 #113e meeting.
  • the switching procedure is used by the UE to notify the network A that the UE wishes to maintain the RRC connection state in the network A but temporarily switch to the network B (The switching procedure can be used to notify network A that the UE has a preference to be kept in RRC_CONNECTED state in network A while temporarily switching to network B).
  • RAN2 also reached another handover procedure (called the second handover procedure) for the UE to notify the network A.
  • the handover procedure is for the UE to notify the network A that the UE wishes to leave the network A.
  • RRC connection state Switchching procedure can be used to notify network A that the UE has a preference to leave RRC_CONNECTED state in network A).
  • the UE may perform RNAU at network B.
  • the benefit of allowing the UE to perform RNAU to network B within the scheduling interval for network B when network A is in RRC connected state is to avoid signaling overhead and reduce UE energy consumption. If it is stipulated that UE needs to perform RNAU to network B, it must first disconnect the RRC connection with network A (that is, adopt the second handover process), when the UE enters RRC idle state or RRC inactive state after network B performs RNAU The RRC connection of network A has been released. At this time, if the UE needs to return to network A for data transmission and reception, it needs to re-execute the RRC connection establishment process in network A, which will lead to huge signaling overhead and energy consumption.
  • the following embodiments of the present invention provide a method to avoid the UE in the RRC connected state in the network A from entering the RRC connected state when the network B performs RNAU (that is, avoiding the UE using the first handover process from entering the RRC connected state when the network B performs RNAU).
  • RNAU avoiding the UE using the first handover process from entering the RRC connected state when the network B performs RNAU.
  • a UE configured with multiple USIM cards has multiple RRC entities, and the RRC connection for each USIM card corresponds to one RRC entity respectively.
  • the operation performed by the UE or the operation performed by the RRC of the UE refers to the operation performed by the UE on the RRC (that is, the RRC layer or the RRC entity) of a certain USIM card, and the upper layer refers to the RRC the upper layer.
  • the present invention uses two implementations to avoid entering the RRC connected state when the UE in the RRC connected state in the network A performs the RNAU in the network B.
  • the UE decides whether to enter the RRC connected state in the network B when sending the RRCResumeRequest message for performing RNAU in the network B; in the second embodiment, the UE receives a response to the RRCResumeRequest message from the base station After the message, it is determined whether the network B can enter the RRC connection state.
  • FIG. 1 is a flowchart showing an execution method of the user equipment according to the first embodiment of the present invention.
  • the user equipment mentioned here supports multiple USIM cards that can be respectively connected to the network, that is, supports MUSIM.
  • step S101 the user equipment UE sends an RRCResumeRequest message for performing RNAU to the first network corresponding to the first USIM card.
  • the RRCResumeRequest message includes an indication identifier for indicating that the UE cannot establish an RRC connection with the first network.
  • step S102 the UE receives a response message from the first network.
  • Embodiment 1 illustrates that when the network B cannot enter the RRC connected state, the RRC of the UE includes an indicator in the RRCResumeRequest message for the RNAU to indicate that the UE cannot enter the RRC connected state;
  • the RRC of the UE sets the value of the ResumeCause field contained in the RRCResumeRequest message for the RNAU to a special value to indicate that the UE cannot enter the RRC connected state;
  • Embodiment 3 illustrates that the RRC of the UE is determined by the upper layer Whether the UE can enter the RRC connected state.
  • the UE includes an indicator in the RRCResumeRequest message for RNAU (that is, the ResumeCause field of the RRCResumeRequest message is set to rna-Update), and the indicator is used to indicate that the base station cannot reply to the RRCResume message or the RRCSetup message as a response message, or is used to indicate The UE does not expect to receive the RRCResume message or the RRCSetup message as a response message, or it is used to indicate that the UE expects the base station to send an RRCRelease message as a response message, or it is used to indicate that the UE cannot enter the RRC connected state (that is, the UE cannot enter the RRC connected state in the current network) , or used to indicate that the UE is already in the RRC connected state in another network.
  • the indicator in the RRCResumeRequest message for RNAU that is, the ResumeCause field of the RRCResumeRequest message is set to rna-Update
  • RNAU if the UE continues the RRC connection triggered by RNAU (if the resumption of the RRC connection is triggered due to an RNA updated), if the UE supports MUSIM (ie multi-SIM) and/or the UE is in the RRC connection state in other networks, then The indication identifier is included in the RRCResumeRequest message.
  • MUSIM ie multi-SIM
  • the UE initiates the process of transmitting the RRCResumeRequest message to the base station (initiate transmission of the RRCResumeRequest message). It should be noted that, before the UE starts to transmit the RRCResumeRequest message, it needs to perform other operations of the RRCResumeRequest message sent to realize the RNAU specified in the latest 3GPP TS38.331 protocol, such as applying the default layer-L1 parameter value defined by the physical layer protocol. , the default configuration of SRB1 is applied, and so on.
  • the UE receives an RRCRelease message from the base station.
  • the UE when the UE performs the operation of continuing the RRC connection for the purpose of realizing the RNAU, it needs to perform access control, that is, select an appropriate access category and perform the unified access control procedure (perform the unified access control procedure).
  • the UE may send the RRCResumeRequest message only if the access attempt is not barred. In other words, if the access attempt is barred, the continued RRC connection procedure triggered by the RNAU is aborted.
  • the access class is set to 8 ( select'8'as the Access Category) or set the access category to be defined specifically for MUSIM-enabled UEs and/or UEs in RRC connected state in other networks and/or UEs that do not wish to establish an RRC connection with the current network to perform RNAU value of .
  • the operation of including the indication in the RRCResumeRequest message is performed when the unified access control procedure is performed and the access attempt is not prohibited.
  • the operation of including the indication identifier in the RRCResumeRequest message is performed before the unified access control process is performed, that is, the unified access control process is performed after the indication identifier is included in the RRCResumeRequest message .
  • the ResumeCause field is used to provide the continuation cause for the RRC connection continuation request provided by the upper layer or RRC (that is, the RRC entity or the RRC layer) (Provides the resume cause for the RRC connection resume request as provided by the upper layers or RRC) .
  • the UE supports MUSIM (ie multi-SIM) and/or the UE is in the RRC connected state in other networks according to the embodiment of the present invention is replaced with the UE being a MUSIM device and/or the UE is in the RRC connected state in other networks , or replaced by the UE does not expect to establish an RRC connection with the current network, or replaced by the expectation that the base station does not respond to the RRCResume message or RRCSetup message as a response message, or replaced by the UE does not expect to receive the RRCResume message or RRCSetup message as a response message, or replaced by The UE expects the base station to send the RRCRelease message as a response message, or the UE cannot enter the RRC connected state (that is, the UE cannot enter the RRC connected state in the current network or the UE does not expect to establish an RRC connection with the current network), or the UE is in another network.
  • MUSIM ie multi-SIM
  • UEs supporting MUSIM can be replaced by UEs supporting MUSIM and/or UEs in RRC connected state in other networks and/or UEs that do not expect to establish an RRC connection with the current network, or can be replaced by UEs that do not expect the base station to reply to the RRCResume message or RRCSetup message as a response message, or replaced by a UE that does not expect to receive an RRCResume message or an RRCSetup message as a response message, or replaced by a UE that expects the base station to send an RRCRelease message as a response message, or replaced by a UE that cannot enter the RRC connected state ( That is, the UE cannot enter the RRC connected state in the current network or the UE does not expect to establish an RRC connection with the current network).
  • the UE sets the value of the ResumeCause field contained in the RRCResumeRequest message for RNAU to the RNAU specifically for UEs supporting MUSIM and/or UEs in RRC connected state in other networks and/or UEs that do not wish to establish an RRC connection with the current network The value set for the purpose.
  • the UE in the RRC inactive state if the timer T380 expires or the RNAU is triggered by receiving SIB1, if the UE supports MUSIM and/or the UE is in the RRC connected state in other networks (or the UE needs to indicate that the base station cannot Reply the RRCResume message or the RRCSetup message as a response message, or the UE does not expect to receive the RRCResume message or the RRCSetup message as the response message, or the UE expects the base station to send the RRCRelease message as the response message, or the UE cannot enter the RRC connected state (that is, the UE cannot Enter the RRC connected state), or the UE is already in the RRC connected state in another network or the UE does not expect to establish an RRC connection with the current network), then start the RRC connection continuation process and instruct resumeCause for UEs that support MUSIM and/or in other The value of the RNAU purpose setting for UEs whose network is
  • T380 is used to trigger the periodic RNAU process. Specifically, when receiving the RRCRelease message including t380, start T380; when receiving the RRCResume or RRCSetup or RRCRelease message, stop T380; when T380 expires, execute the RRC connection continuation process for RNAU.
  • SIB1 contains relevant information for evaluating whether a UE is allowed to access a cell and defines scheduling of other system information (SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information); it It also includes radio resource configuration information common to all UEs and prohibition information applied to the unified access control (It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control).
  • the UE supports MUSIM
  • the relevant information may be the value rna-Update of resumeCause when the RRC connection is continued for the purpose of RNAU, or the relevant information may be the value rna-Update of the resumeCause for the purpose of performing the continuation of the RRC connection and the corresponding resumeCause for the purpose of RNAU.
  • the RRC layer will not trigger the continuation of the RRC connection process, but the upper layer will decide whether to trigger the continuation of the RRC connection process for the RNAU.
  • a UE in RRC inactive state if T380 expires or an RNAU is triggered due to receipt of SIB1, if the UE supports MUSIM and/or the UE is in an RRC connected state in other networks and/or the UE does not expect to communicate with the current network
  • Establish an RRC connection and/or the upper layer needs to decide whether to perform the RRC connection continuation process and/or need the upper layer to decide whether an RRC connection can be established with the current network, indicating to the upper layer RNAU or indicating to the upper layer that the UE needs to perform RNAU in the current network related information, Otherwise (ie UE does not support MUSIM and/or UE is not in RRC connected state in other networks and/or UE can establish RRC connection with current network and/or it is not necessary for upper layer to decide whether to perform RRC connection continuation procedure and/or upper layer is not required Determine whether the RRC connection can be established with the current network), start the RRC connection continuation process and indicate resumeCause as rna
  • the upper layer After the upper layer receives the indication information, if it decides to trigger the RRC layer to perform the RRC connection continuation process but cannot establish an RRC connection with the current network, then trigger the RRC layer to perform the RRC connection continuation process and indicate that the value of resumeCause is defined in Embodiment 2.
  • a value specially set for the RNAU purpose of UEs supporting MUSIM and/or UEs in RRC connected state in other networks and/or UEs that do not expect to establish an RRC connection with the current network (here, although the value of resumeCause is the same as that of Example 2 The same; but there are the following differences from Embodiment 2:
  • the value of resumeCause is determined by the RRC layer, and here, the value of resumeCause is indicated by the NAS). If it is decided to trigger the RRC layer to perform the RRC connection continuation procedure and the RRC connection can be established with the current network, the RRC layer is triggered to perform the RRC connection continuation procedure and the value indicating resumeCause is rna-Update.
  • the precondition of indicating that the value of resumeCause is rna-Update is that the upper layer has no other reason to trigger the RRC layer to perform the RRC connection continuation process.
  • RRC connection then instruct the upper layer to indicate RNAU or indicate to the upper layer that the UE needs to perform RNAU in the current network, otherwise (that is, the UE does not support MUSIM and/or the UE is not in the RRC connection state in other networks and/or the UE can communicate with the current network.
  • the RRC connection is established and/or the upper layer does not need to decide whether to perform the RRC connection continuation procedure and/or the upper layer does not need to decide whether the RRC connection can be established with the current network), start the RRC connection continuation procedure and indicate resumeCause as rna-Update.
  • the upper layer it needs to be decided by the upper layer whether to perform the RRC connection continuation process, which may be configured by the base station.
  • the RNAU is indicated to the upper layer or the relevant information that the UE needs to perform RNAU in the current network is indicated to the upper layer.
  • the UE variable VarpendingRNA_Update corresponding to pendingRNA_Update is used to indicate whether there is a pending RNAU process.
  • the UE variable VarPendingRNA-Update indicates whether there is a pending RNA update procedure or not.
  • the setting of this BOOLEAN variable to true means that there is a pending RNA Update procedure) .
  • the UE decides whether to enter the RRC connected state in the network B after receiving the response message for the RRCResumeRequest message from the base station.
  • FIG. 2 is a flowchart showing an execution method of the user equipment according to the second embodiment of the present invention.
  • the user equipment mentioned here supports multiple USIM cards that can be respectively connected to the network, that is, supports MUSIM.
  • step S201 the user equipment UE sends an RRCResumeRequest message for performing RNAU to the first network corresponding to the first USIM card.
  • step S202 the user equipment UE receives the RRCResume message or the RRCSetup message from the first network as a response message.
  • step S203 the RRC layer of the user equipment UE indicates information related to the received RRCResume message or RRCSetup message to the upper layer.
  • Example 4 will be specifically given and described.
  • the RRC instructs the upper layer or the RRC to indicate the information related to the RRCResume message or the RRCSetup message to the upper layer, and the related information
  • the information is, for example, the RRC indicating that the upper layer RRC has received a message to continue/establish an RRC connection with the current network, or the RRC requests the upper layer to decide whether to continue/establish an RRC connection with the current network.
  • the upper layer may determine whether to instruct the RRC to perform the operation of entering the RRC connected state according to information such as the service priorities of the two USIM cards.
  • the upper layer For example, if the upper layer considers that the priority of the service to be executed by the USIM card corresponding to the current RRC is higher than the priority of the service being executed by another USIM card, the upper layer instructs the other USIM card to release the corresponding RRC connection, and then instructs the current RRC card to release the corresponding RRC connection. Establish an RRC connection; if the upper layer believes that the priority of the service to be executed by the USIM card corresponding to the current RRC is lower than the priority of the service being executed by another USIM card, the upper layer instructs the current RRC not to establish an RRC connection.
  • the UE that supports MUSIM receives an RRCResume message or an RRCSetup message from the base station after sending the RRCResumeRequest message for performing RNAU to the base station, if the UE is in an RRC connection state in another network or the UE cannot directly communicate with the current network Continue or establish an RRC connection or RRC cannot determine whether it can continue or establish an RRC connection with the current network. Only then does RRC instruct the upper layer or RRC to indicate the information related to the RRCResume message or the RRCSetup message to the upper layer or receive a request to continue/establish an RRC connection with the current network. Message or request upper layer to decide whether to continue/establish RRC connection with the current network.
  • the RRC layer continues to receive the RRCResume message or The operation that needs to be performed by the RRCSetup message (that is, the operation performed when the RRCResume message is received as specified in TS38.331 5.3.13.4 or the operation performed when the RRCSetup message is received as specified in TS38.331 5.3.13.7).
  • RRC receives an instruction from the upper layer indicating that the RRC layer terminates the RRC connection or stops establishing the RRC connection (or receives an instruction from the upper layer indicating that the RRC layer terminates the RRC connection and stops establishing the RRC connection related information), RRC performs the following two operations. an implementation.
  • RRC performs an entry into RRC_IDLE and sets the release reason to 'RRC connection failure' or 'RRC Resume failure' or 'other' or other value set for this purpose.
  • the base station For the RRCResumeRequest message sent by the UE supporting MUSIM for the purpose of RNAU, the base station includes an indicator in the RRCResume message or the RRCSetup message as the response message, which is used to indicate when the RRC of the UE or the upper layer of the RRC decides not to continue the RRC connection or establish the RRC In connection-related operations, the RRC state that the UE enters (ie, the RRC idle state or the RRC inactive state).
  • the indication identifier may be suspendConfig.
  • the UE enters the RRC inactive state according to the configuration indicated by suspendConfig. If the response message does not contain suspendConfig and the UE determines not to continue or establish the RRC connection, the UE performs the operation of entering the RRC idle state and sets the release cause as 'RRC connection failure' or 'RRC Resume failure' or 'other' or as other values set for this purpose.
  • the RRC enters the RRC inactive state according to the configuration indicated by the last received suspendConfig; if the indicator indicates that the UE enters the RRC idle state, the UE executes the entry into the RRC inactive state. Operation in the RRC idle state with the release reason set to 'RRC connection failure' or 'RRC Resume failure' or 'other' or any other value set for this purpose.
  • the suspendConfig is used to indicate the configuration of the RRC inactive state.
  • the operations performed after receiving the RRCResume message include (see 5.3.13.4 of TS38.331 for details): stop T319, stop T380 (if it is running), and so on.
  • the operations that need to be performed after receiving the RRCSetup message include (see TS38.331 5.3.13.7 for details): Discard all UE-stored inactive AS contexts and suspendConfig (discard any stored UE Inactive AS context and suspendConfig), discard all current AS security contexts (discard any current AS security context), etc.
  • FIG. 3 is a schematic structural block diagram of the user equipment involved in the present invention.
  • the user equipment 300 includes at least a processor 301 and a memory 302 .
  • the processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • the memory 302 may include, for example, volatile memory (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory systems, or the like.
  • the memory 302 has program instructions stored thereon. When the instruction is executed by the processor 301, one or several steps of the execution method of the user equipment described in the above-mentioned FIG. 1 or FIG. 2 of the present disclosure may be executed.
  • the user equipment shown above may include more modules, for example, may also include modules that can be developed or developed in the future and that can be used in a base station, an MME, or a UE, and so on.
  • the various identifiers shown above are only exemplary and not restrictive, and the present disclosure is not limited to the specific information elements exemplified by these identifiers. Numerous changes and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments.
  • the various components inside the base station and the user equipment in the above embodiments may be implemented by various devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processing Controllers, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (CPLDs), etc.
  • DSP digital signal processing
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • CPLDs Programmable Logic Devices
  • the computer-executable instructions or programs running on the apparatus according to the present invention may be programs that cause 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 (eg, random access memory RAM), a hard disk drive (HDD), non-volatile memory (eg, flash memory), or other memory systems.
  • Computer-executable instructions or programs for implementing the functions of the various embodiments of the present invention may be recorded on a computer-readable storage medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” as used herein may be a computer system embedded in the device, and may include an operating system or hardware (eg, peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short period of time, or any other recording medium readable by a computer.
  • circuits eg, monolithic or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general-purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit. Where new integrated circuit technologies have emerged as a result of advances in semiconductor technology to replace existing integrated circuits, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-described embodiments. Although various examples of the described embodiments have been described, the invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本发明提供用户设备的执行方法以及用户设备。所述用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM，其中，所述用户设备的执行方法包括：所述用户设备向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息；以及所述用户设备从所述第一网络接收应答消息，在所述RRCResumeRequest消息中包含用于指示所述用户设备不能与所述第一网络建立RRC连接的指示标识。

Description

用户设备及其执行方法 技术领域
本发明涉及无线通信技术领域，更具体地，本发明涉及用户设备及其执行方法。
背景技术
近年来，多USIM卡设备(multi-SIM device)越来越流行。例如一个用户在支持多USIM卡的手机上安装两张USIM卡，其中一张USIM卡用于订阅私人业务，另一张USIM卡用于订阅办公业务。现有支持多USIM卡的设备是基于厂商实现，尚未被3GPP标准化。导致不同的厂商采用不同的实现方式，用户设备UE的行为也各不相同。现有实现方式中，如果这些USIM卡分别向网络注册(可注册到同一网络也可分别注册到两个或两个以上网络)，UE需要通过这些USIM卡从这些网络接收寻呼，基于UE的收发能力，可能存在的一种情形是，UE通过一个USIM卡在接收当前网络的寻呼时，另一个USIM卡的网络(可以与前述网络相同，也可以不同)也对其发起寻呼，又或者UE正通过一个USIM卡与一个网络通信时另一个USIM卡的网络(可以与前述网络相同，也可以不同)也对其发起寻呼。当不同的USIM卡注册到不同的网络时，如果UE在不同的网络之间切换，可能导致的一个结果是当UE切换到另一个网络时UE不能再从当前网络接收数据。这将损害网络性能，例如网络向UE发送了寻呼但UE因切换到另一个网络而没有接收到这个寻呼，或UE切换到另一个网络而不能接收当前网络的调度。针对上述情况，部分厂商提出对具备多USIM卡的UE接入网络的行为及相关网络进行3GPP标准化研究，其好处在于可以基于可预测的UE行为，提升网络性能。
基于上述原因，2019年12月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#86次全会上，vivo提出了针对版本17 的多SIM卡设备的工作项目(参见非专利文献：RP-193263：New WID：Stupport of Multi-SIM devices in Rel-17)，并获批准。
在现有系统中，当UE向基站发送用于执行基于无线访问网络的通知区域更新RNAU(RAN-based Notification Area Update)的RRCResumeRequest消息时，基站可以发送RRCResume消息或者RRCRelease消息作为响应。当UE接收到RRCResume消息时，将执行RRCResume消息并进入RRC连接态。但是，对于支持MUSIM(即multi-SIM)的UE，当该UE在网络A处于RRC连接态时，在UE向网络B发送用于进行基于无线访问网络的通知区域更新RNAU的RRCResumeRequest时，接收到来自网络B的RRCResume消息。按照现有系统定义的操作，UE将在网络B也进入RRC连接态。按照3GPP达成的结论，至少对于单收单发或单收双发的UE，不允许其在网络A和网络B同时处于RRC连接态。其中，网络A和网络B可以相同，也可以不同，以下同理。
本公开致力于解决如何避免支持多USIM卡的UE在一个或多个网络通过多个USIM卡同时处于RRC连接态。
发明内容
本发明的目的在于提供用户设备及其执行方法，避免支持多USIM卡的UE在一个或多个网络通过多个USIM卡同时处于RRC连接态。
根据本发明的一个方面，提供一种用户设备的执行方法，所述用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM，其中，所述用户设备的执行方法包括：所述用户设备向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息；以及所述用户设备从所述第一网络接收应答消息，在所述RRCResumeRequest消息中包含用于指示所述用户设备不能与所述第一网络建立RRC连接的指示标识。
在上述用户设备的执行方法中，优选的是，所述指示标识用于指示所述用户设备在与所述第一USIM卡不同的第二SIM卡对应的第二网络处于RRC连接态，或者，所述指示标识用于指示所述第一网络不能回复RRCResume消息或RRCSetup消息作为所述应答消息，或者，所述指示标识用于指示所述用户设备不期望接收到RRCResume消息或RRCSetup消息作为所 述应答消息，或者，所述指示标识用于指示所述用户设备期望所述第一网络发送RRCRelease消息作为所述应答消息。
在上述用户设备的执行方法中，优选的是，所述RRCResumeRequest消息中的ResumeCause字段的值设置为用于支持MUSIM的用户设备执行RNAU而定义的值。
在上述用户设备的执行方法中，优选的是，所述用户设备的RRC层将需要在所述第一网络执行RNAU的信息指示给上层，由所述上层决定所述用户设备是否能与所述第一网络建立RRC连接，在所述上层决定所述用户设备不能与所述第一网络建立RRC连接的情况下，在所述RRCResumeRequest消息中包含用于指示所述用户设备不能与所述第一网络建立RRC连接的所述指示标识。
根据本发明的另一个方面，提供一种用户设备的执行方法，所述用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM，其中，所述用户设备的执行方法包括：所述用户设备向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息；所述用户设备从所述第一网络接收RRCResume消息或RRCSetup消息作为应答消息；以及所述用户设备的RRC层将与所述RRCResume消息或所述RRCSetup消息相关的信息指示给上层。
在上述用户设备的执行方法中，优选的是，由所述用户设备的RRC层的所述上层确定所述用户设备是否能与所述第一网络继续或建立RRC连接。
在上述用户设备的执行方法中，优选的是，在所述第一USIM卡的业务的优先级高于正在执行的与所述第一USIM卡不同的第二USIM卡的业务的优先级时，所述上层指示所述用户设备释放RRC连接，并指示所述用户设备与所述第一网络建立RRC连接，在所述第一USIM卡的业务的优先级低于正在执行的与所述第一USIM卡不同的第二USIM卡的业务的优先级时，所述上层指示所述用户设备不与所述第一网络建立RRC连接。
在上述用户设备的执行方法中，优选的是，在所述RRCResume消息或所述RRCSetup消息中包含用于指示所述用户设备不能与所述第一网络继续或建立RRC连接时应进入的RRC状态的指示标识。
在上述用户设备的执行方法中，优选的是，如果所述应答消息中包含suspendConfig且所述上层确定所述用户设备不能与所述第一网络继续或建 立RRC连接，则所述用户设备按照该suspendConfig指示的配置进入RRC非激活态，如果所述应答消息中不包含suspendConfig且所述上层确定所述用户设备不能与所述第一网络继续或建立RRC连接，则所述用户设备进入RRC空闲态。
根据本发明的另一个方面，提供一种用户设备，支持能分别连接到网络的多个USIM卡即支持MUSIM，所述用户设备包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行上述任一项所述的用户设备的执行方法。
发明效果
根据本发明涉及的用户设备的执行方法及用户设备，能够避免支持多USIM卡的UE在一个或多个网络通过多个USIM卡同时处于RRC连接态。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1是表示本发明第一实施方式所涉及的用户设备的执行方法的流程图。
图2是表示本发明第二实施方式所涉及的用户设备的执行方法的流程图。
图3是表示本发明所涉及的用户设备的简要结构框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。本发明以配置了两张SIM/USIM卡的用户设备UE(即multi-SIM device)为例描述实施例，但应注意，本发明实施例不局限于配置了两张SIM/USIM卡的UE对应的应用场景，也可以用于配置了多张SIM/USIM卡的应用场景。配置了两张SIM/USIM卡的用户设备UE是指UE可以在两个网络注册并分别与两个网络建立连接或收发数据的用户设备UE。
下面描述本发明涉及的部分术语，术语的具体含义见3GPP最新相关文档，例如TS38.300、TS38.331、TS36.300、TS36.331等。
NAS：Non-access stratum，非接入层。
AS：access stratum，接入层。
DRB：数据无线承载。
RRC：Radio Resource Control，无线资源控制。
RRC_CONNECTED：RRC连接态。
RRC_INACTIVE：RRC非激活态。
RRC_IDLE：RRC空闲态。
RAN；Radio Access Network，无线接入网络。
RNAU：RAN-based Notification Area Update，基于RAN的通知区域更新。
NR：New RAT，新无线接入技术。
USIM：Universal Subscriber Identity Module，全球用户识别卡。
Tx：transmitter，发信机。
Rx：receiver，接收机。
本发明中，RRCResumeRequest或RRCResumeRequest1用于请求继续一个挂起(suspended)的RRC连接或执行RNAU；信息元素suspendConfig用于指示RRC_INACTIVE的配置(Indicates configuration for the RRC_INACTIVE state)。此外，本发明中统一采用RRCResumeRequest，但是将RRCResumeRequest替换为RRCResumeRequest1得到的实施例也是本发明保护的范围。RRCResume消息用于继续一个挂起的RRC连接(The RRCResume message is used to resume the suspended RRC connection.)；RRCSetup消息用于建立信令无线承载SRB1。RRCRelease消息用于命令释放一个RRC连接或挂起一个RRC连接(The RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection)。RRCReject消息用于拒绝一个RRC连接建立或RRC连接继续(The RRCReject message is used to reject an RRC connection establishment or an RRC connection resumption)。
本发明中，网络、基站和RAN可互换使用，所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
本发明中，用户设备UE可指物理上支持多USIM卡(两个或两个以上USIM卡)的设备，所述设备装配了两个或两个以上USIM卡，每个USIM卡关联一个网络。UE通过不同的USIM卡分别与网络建立RRC连接(此时这个USIM卡对应的UE在这个网络处于RRC连接态)或驻留在网络(此时这个USIM卡对应的UE在这个网络处于RRC空闲态或RRC非激活态)。一个USIM卡所连接或注册或驻留的网络就是这个USIM对应的网络。所述多个USIM卡可以来自同一个运营商或不同的运营商。从网络的角度来看，不同的USIM卡对应不同的UE，每个USIM卡对应一个UE，核心网和/或基站分别为每个USIM卡对应的UE分别分配一个NAS和/或AS层标识，例如，核心网为每个USIM卡对应的UE分配的NAS层标识记为5G-S-TMSI或S-TMSI，基站为每个USIM卡对应的UE分配的AS层标识记为C-RNTI。核心网和/或基站为不同USIM卡对应的UE所分配的NAS和/或AS层标识是不同的，一个配置了多USIM卡的UE，对应不同的USIM卡有不同的NAS和/或AS层标识。如未特别说明，本发明实施例中没有明确UE是配置了多USIM卡的UE还是配置了多USIM卡的设备中每个USIM卡对应的UE，本领域技术人员可以根据上下文容易地确定UE是指支持多USIM卡的UE(或配置了多USIM卡的UE)还是支持多USIM卡的设备中每个USIM卡分别对应的UE。配置了多USIM卡的UE可以通过时分复用等方式利用单收单发或双收单发从多个网络接收和/或发送数据，对于具有两个Rx的UE，可以同时从两个网络接收数据。此外，本发明所述USIM可以是物理SIM或eSIM(USIM can be a physical SIM or eSIM)。
本发明实施例以UE配置两个USIM卡为例，本领域技术人员可以容易的扩展到多个USIM卡的情况。具有两个USIM卡的用户设备UE至少具有单收单发(Single-Rx/Single-Tx)或双收单发(Dual-Rx/Single-Tx)能力。两个USIM卡对应的不同UE可以共用一对Tx和Rx或共用一个Tx但分别具有各自的Rx。本发明实施例中，UE通过USIM卡A连接到网络A，通过USIM卡B连接到网络B，UE在不同网络间的切换是通过切换工作的USIM卡实现。
本发明中，UE(或USIM卡A)工作在一个网络(网络A，第一网络)是指UE在网络A处于RRC连接态，监听网络A(从网络A收/发数据或信令)，同时，UE可以周期性或间歇性地离开网络A去监听另一个网络(网络B，第二网络)，例如去接收来自所述网络B的寻呼消息或测量另一个USIM卡(即USIM卡B)的服务小区或驻留小区或测量对象等的信号质量。网络A和网络B可以是不同的网络，也可以是同一个网络。UE离开网络A去接收来自所述网络B的寻呼消息或测量另一个USIM卡的服务小区或驻留小区或测量对象等的信号质量的时间信息就是UE在网络A的调度间隔(Scheduling gap)或称为针对网络B的调度间隔。在所述调度间隔内，UE不期望网络A调度所述UE，UE停止在网络A的数据收/发而去接收来自所述网络B的寻呼消息或测量另一个USIM卡(即USIM卡B)的服务小区或驻留小区或测量对象等的信号质量等。换言之，UE在网络A的调度间隔是指当UE工作在网络A时，在所述调度间隔指示的时间段内，网络A将不调度所述UE或者UE在所述调度间隔指示的时间段内不从网络A接收数据或不期望被网络A调度。本公开中所述UE工作在网络A可以对应在3GPP RAN2#113e次会议上RAN2达成的一个用于UE通知网络A的切换过程(称为第一切换过程)。所述切换过程用于UE通知网络A UE希望在网络A保持RRC连接态但暂时切换到网络B(The switching procedure can be used to notify network A that the UE has a preference to be kept in RRC_CONNECTED state in network A while temporarily switching to network B)。此外，在3GPP RAN2#113e次会议上RAN2还达成的另一个用于UE通知网络A的切换过程(称为第二切换过程)，所述切换过程用于UE通知网络A UE希望在网络A离开RRC连接态(Switching procedure can beused to notify network A that the UE has a preference to leave RRC_CONNECTED state in network A)。
本公开讨论第一切换过程所涉及的问题。在网络A调度间隔内，UE可以在网络B执行RNAU。允许UE在网络A处于RRC连接态时在针对网络B的调度间隔内向网络B执行RNAU的好处在于可以避免信令开销并减少UE能耗。如果规定UE需要向网络B执行RNAU时必须先断开与网络A的RRC连接(即采用第二切换过程)，当UE在网络B执行完RNAU后进入RRC空闲态或RRC非激活态，由于与网络A的RRC连接已经释放，此 时如果UE需要返回网络A进行数据收发，则需要在网络A重新执行RRC连接建立过程，这将导致巨大的信令开销和能耗。
本发明以下实施方式给出了避免在网络A处于RRC连接态的UE在网络B执行RNAU时进入RRC连接态(即避免采用第一切换过程的UE在网络B执行RNAU时进入RRC连接态)的不同实现方法。
另外，一个配置了多个USIM卡的UE具有多个RRC实体，针对每个USIM卡的RRC连接分别对应一个RRC实体。在本发明实施例中，如未特别说明，UE执行的操作或UE的RRC执行的操作是指UE的针对某个USIM卡的RRC(即RRC层或RRC实体)执行的操作，上层是指RRC的上层。
具体来说，本发明通过两种实施方式来避免在网络A处于RRC连接态的UE在网络B执行RNAU时进入RRC连接态。在第一实施方式中，UE在发送用于在网络B执行RNAU的RRCResumeRequest消息时决定是否能在网络B进入RRC连接态；在第二实施方式中，UE在从基站接收到针对RRCResumeRequest消息的应答消息后决定是否能在网络B进入RRC连接态。
以下具体地描述本发明的第一和第二实施方式。
第一实施方式
图1是表示本发明第一实施方式所涉及的用户设备的执行方法的流程图。其中，这里所说的用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM。
在步骤S101中，用户设备UE向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息。其中，在该RRCResumeRequest消息中包含用于指示该UE不能与第一网络建立RRC连接的指示标识。
在步骤S102中，该UE从第一网络接收应答消息。
以下，具体给出实施例1～3来进行说明。其中，实施例1说明当不能在网络B进入RRC连接态时，UE的RRC在用于RNAU的RRCResumeRequest消息中包含一个指示标识来指示该UE不能进入RRC连接态；实施例2说明当不能在网络B进入RRC连接态时，UE的RRC将 用于RNAU的RRCResumeRequest消息中所包含ResumeCause字段的值设置为专门的值来指示该UE不能进入RRC连接态；实施例3说明UE的RRC经由上层来决定该UE是否能进入RRC连接态。
实施例1
UE在用于RNAU的RRCResumeRequest消息(即RRCResumeRequest消息的ResumeCause字段设置为rna-Update)中包含一个指示标识，所述指示标识用于指示基站不能回复RRCResume消息或RRCSetup消息作为应答消息，或者用于指示UE不期望接收到RRCResume消息或RRCSetup消息作为应答消息，或者用于指示UE期望基站发送RRCRelease消息作为应答消息，或者用于指示UE不能进入RRC连接态(即UE在当前网络不能进入RRC连接态)，或者用于指示UE在另一个网络已经处于RRC连接态。
具体的，如果UE因RNAU触发继续RRC连接(ifthe resumption of the RRC connection is triggered due to an RNA updated)，如果UE支持MUSIM(即multi-SIM)和/或UE在其他网络处于RRC连接态，则在RRCResumeRequest消息中包含所述指示标识。
可选的，UE启动向基站传输RRCResumeRequest消息的过程(initiate transmission of the RRCResumeRequest message)。需要说明的是，UE在启动传输RRCResumeRequest消息之前需要执行最新3GPP TS38.331协议中规定的为实现RNAU而发送的RRCResumeRequest消息的其他操作，例如应用物理层协议定义的缺省的层一L1参数值，应用SRB1的缺省配置等等。
可选的，UE接收来自基站的RRCRelease消息。
需要说明的是，UE在为实现RNAU目的执行继续RRC连接的操作时，需要执行访问控制，即选择合适的访问类别并执行统一的访问控制过程(perform the unified access control procedure)。UE只有在访问尝试没有被禁止(the access attempt is not barred)时才可以发送RRCResumeRequest消息。换言之，如果访问尝试被禁止，则中止由RNAU触发的继续RRC连接过程。可选的，对于支持MUSIM的UE和/或在其他网络处于RRC连接态的UE和/或不期望与当前网络建立RRC连接的UE，因RNAU触发的继续RRC连接，将访问类别设置为8(select′8′as the Access Category)或者将访问类别设置为专门为支持MUSIM的UE和/或在其他网络处于RRC连接态 的UE和/或不期望与当前网络建立RRC连接的UE执行RNAU而定义的值。在这种情况下，在RRCResumeRequest消息中包含所述指示标识的操作是在执行统一的访问控制过程并且访问尝试没有被禁止时才执行。作为替换实施例，在这种情况下，在RRCResumeRequest消息中包含所述指示标识的操作是在执行统一的访问控制过程前执行，即在RRCResumeRequest消息中包含所述指示标识后执行统一的访问控制过程。
本发明中，ResumeCause字段用于为RRC连接继续请求提供由上层或RRC(即RRC实体或RRC层)提供的继续原因(Provides the resume cause for the RRC connection resume request as provided by the upper layers or RRC)。
需要说明的是，将本发明实施例所述UE支持MUSIM(即multi-SIM)和/或UE在其他网络处于RRC连接态替换为UE是一个MUSIM设备和/或UE在其他网络处于RRC连接态，或者替换为UE不期望与当前网络建立RRC连接，或者替换为期望基站不回复RRCResume消息或RRCSetup消息作为应答消息，或者替换为UE不期望接收到RRCResume消息或RRCSetup消息作为应答消息，或者替换为UE期望基站发送RRCRelease消息作为应答消息，或者替换为UE不能进入RRC连接态(即UE在当前网络不能进入RRC连接态或UE不期望与当前网络建立RRC连接)，或者替换为UE在另一个网络已经处于RRC连接态，其他操作不变，可以得到新的实施例。此外，支持MUSIM的UE可以替换为支持MUSIM的UE和/或在其他网络处于RRC连接态的UE和/或不期望与当前网络建立RRC连接的UE，或者替换为不期望基站回复RRCResume消息或RRCSetup消息作为应答消息的UE，或者替换为不期望接收到RRCResume消息或RRCSetup消息作为应答消息的UE，或者替换为期望基站发送RRCRelease消息作为应答消息的UE，或者替换为不能进入RRC连接态的UE(即UE在当前网络不能进入RRC连接态或UE不期望与当前网络建立RRC连接)。虽然本发明部分实施例中给出了UE支持MUSIM(即multi-SIM)和/或UE在其他网络处于RRC连接态以及支持MUSIM的UE的部分替换描述方式，但也可以替换为此处列出的其他替换描述方式。当实施例中给出其中一种或几种描述时，可以替换为本处列出的其他替换描述。这些替换描述适用 于本发明所有实施例，以下不再累述。
实施例2
UE将用于RNAU的RRCResumeRequest消息中所包含ResumeCause字段的值设置为专门为支持MUSIM的UE和/或在其他网络处于RRC连接态的UE和/或不期望与当前网络建立RRC连接的UE的RNAU目的而设置的值。
具体的，对处于RRC非激活态的UE，如果定时器T380到期或因接收到SIB1而触发的RNAU，如果UE支持MUSIM和/或UE在其他网络处于RRC连接态(或者UE需要指示基站不能回复RRCResume消息或RRCSetup消息作为应答消息，或者UE不期望接收到RRCResume消息或RRCSetup消息作为应答消息，或者UE期望基站发送RRCRelease消息作为应答消息，或者UE不能进入RRC连接态(即UE在当前网络不能进入RRC连接态)，或者UE在另一个网络已经处于RRC连接态或者UE不期望与当前网络建立RRC连接)，则启动RRC连接继续过程并指示resumeCause为专门为支持MUSIM的UE和/或在其他网络处于RRC连接态的UE和/或不期望与当前网络建立RRC连接的UE的RNAU目的设置的值。
需要说明的是，本发明中，T380用于触发周期性RNAU过程。具体的，在接收到包含t380的RRCRelease消息时，启动T380；在接收到RRCResume或RRCSetup或RRCRelease消息时，停止T380；当T380到期时，执行用于RNAU的RRC连接继续过程。SIB1包含用于评价一个UE是否允许访问一个小区的相关信息以及定义了其他系统信息的调度(SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information)；它还包括所有UE共同的无线资源配置信息和应用于统一的访问控制的禁止信息(It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control)。
实施例3
如果UE支持MUSIM，处于RRC非激活态的UE(或UE的RRC)需要执行RNAU时，指示上层或将需要执行RNAU的相关信息指示上层。所述相关信息可以是为RNAU目的执行继续RRC连接时resumeCause的值 rna-Update，或者所述相关信息是为RNAU目的执行继续RRC连接及其对应的resumeCause的值rna-Update。在这种情况下，RRC层将不触发继续RRC连接过程而是由上层决定是否为RNAU触发继续RRC连接过程。
具体的，对处于RRC非激活态的UE，如果T380到期或因接收到SIB1而触发的RNAU，如果UE支持MUSIM和/或者UE在其他网络处于RRC连接态和/或UE不期望与当前网络建立RRC连接和/或需要由上层决定是否执行RRC连接继续过程和/或需要上层决定是否可以与当前网络建立RRC连接，向上层指示RNAU或向上层指示UE需要在当前网络执行RNAU的相关信息，否则(即UE不支持MUSIM和/或UE在其他网络未处于RRC连接态和/或UE可以与当前网络建立RRC连接和/或不需要由上层决定是否执行RRC连接继续过程和/或不需要上层决定是否可以与当前网络建立RRC连接)，启动RRC连接继续过程并指示resumeCause为rna-Update。
上层在接收到所述指示信息后，如果决定触发RRC层执行RRC连接继续过程但不能与当前网络建立RRC连接，则触发RRC层执行RRC连接继续过程并指示resumeCause的值为实施例2中定义的专门为支持MUSIM的UE和/或在其他网络处于RRC连接态的UE和/或不期望与当前网络建立RRC连接的UE的RNAU目的设置的值(在此处，虽然resumeCause的值与实施例2相同；但是此处与实施例2存在以下区别：在实施例2中，resumeCause的值是由RRC层决定的，而此处，resumeCause的值是由NAS指示的)。如果决定触发RRC层执行RRC连接继续过程并且可以与当前网络建立RRC连接，则触发RRC层执行RRC连接继续过程并将指示resumeCause的值为rna-Update。指示resumeCause的值为rna-Update的前题条件是上层没有其他原因需要触发RRC层执行RRC连接继续过程。
对处于RRC非激活态的UE，如果访问类型‘8’或访问类型‘2’的禁止被解除(if barring is alleviated for Access Category‘8’or Access Category‘2’)，如果上层没有请求RRC继续RRC连接并且pendingRNA_Update被设置为true，如果UE支持MUSIM和/或UE不期望与当前网络建立RRC连接和/或需要由上层决定是否执行RRC连接继续过程和/或需要上层决定是否可以与当前网络建立RRC连接，则向上层指示RNAU或向上层指示UE需要在当前网络执行RNAU的相关信息，否则(即UE不支持MUSIM和/或UE 在其他网络未处于RRC连接态和/或UE可以与当前网络建立RRC连接和/或不需要由上层决定是否执行RRC连接继续过程和/或不需要上层决定是否可以与当前网络建立RRC连接)，启动RRC连接继续过程并指示resumeCause为rna-Update。
其中，需要由上层决定是否执行RRC连接继续过程可以是由基站配置。换言之，只有UE被配置了相应的字段，才向上层指示RNAU或向上层指示UE需要在当前网络执行RNAU的相关信息。此外，pendingRNA_Update对应的UE变量VarpendingRNA_Update用于指示是否存在挂起的RNAU过程。当设置为true时表示有一个挂起的RNAU过程(The UE variable VarPendingRNA-Update indicates whether there is a pending RNA update procedure or not.The setting of this BOOLEAN variable to true means that there is a pending RNA Update procedure)。
第二实施方式
在第二实施方式中，UE在从基站接收到针对RRCResumeRequest消息的应答消息后决定是否能在网络B进入RRC连接态。
图2是表示本发明第二实施方式所涉及的用户设备的执行方法的流程图。其中，这里所说的用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM。
在步骤S201中，用户设备UE向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息。
在步骤S202中，该用户设备UE从第一网络接收RRCResume消息或RRCSetup消息作为应答消息。
在步骤S203中，该用户设备UE的RRC层将与接收到的RRCResume消息或RRCSetup消息相关的信息指示给上层。
以下，具体给出实施例4来进行说明。
实施例4
如果支持MUSIM的UE在向基站发送用于执行RNAU的RRCResume Request消息后接收到来自基站的RRCResume消息或RRCSetup消息，RR C指示上层或RRC将RRCResume消息或RRCSetup消息相关的信息指示上层，该相关的信息例如是RRC指示上层RRC接收到了与当前网络继续/建立RRC连接的消息，或RRC请求上层决定是否可以与当前网络继续/建立RRC连接。上层可以依据两个USIM卡的业务优先级等信息确定是否指示RRC执行进入RRC连接态的操作。例如，如果上层认为当前RRC对应的USIM卡要执行的业务优先级高于另一个USIM卡正在执行的业务的优先级时，则上层指示另一个USIM卡释放对应的RRC连接，之后再指示当前RRC建立RRC连接；如果上层认为当前RRC对应的USIM卡要执行的业务优先级低于另一个USIM卡正在执行的业务的优先级时，则上层指示当前RRC不建立RRC连接。
可选的，如果支持MUSIM的UE在向基站发送用于执行RNAU的RRCResumeRequest消息后接收到来自基站的RRCResume消息或RRCSetup消息，如果UE在另一个网络处于RRC连接态或UE目前不能直接与当前网络继续或建立RRC连接或RRC不能确定是否可以与当前网络继续或建立RRC连接，RRC才指示上层或RRC才将RRCResume消息或RRCSetup消息相关的信息指示上层或接收到与当前网络继续/建立RRC连接的消息或请求上层决定是否可以与当前网络继续/建立RRC连接。如果RRC接收到来自上层的指示RRC层继续RRC连接或建立RRC连接(或接收到来自上层的指示RRC层继续RRC连接或建立RRC连接相关信息)的指示，则RRC层继续执行接收到RRCResume消息或RRCSetup消息需要执行的操作(即执行TS38.331 5.3.13.4规定的接收到RRCResume消息时执行的操作或执行TS38.331 5.3.13.7规定的接收到RRCSetup消息时执行的操作)。如果RRC接收到来自上层的指示RRC层终止继续RRC连接或停止建立RRC连接(或接收到来自上层的指示RRC层终止继续RRC连接停止建立RRC连接相关信息)的指示，RRC执行的操作有以下两种实现方式。
实现方式1
RRC执行进入RRC_IDLE的操作并将释放原因设置为′RRC connection failure‘或′RRC Resume failure‘或′other′或为这一目的而设置的其他值。
实现方式2
针对支持MUSIM的UE为RNAU目的发送的RRCResumeRequest消息，基站在作为应答消息的RRCResume消息或RRCSetup消息中包含一个指示标识，用于指示当UE的RRC或RRC的上层决定不执行继续RRC连接或建立RRC连接的相关操作时，UE进入的RRC状态(即RRC空闲态或RRC非激活态)。优选的，如果指示UE进入RRC非激活态，所述指示标识可以是suspendConfig。换言之，如果应答消息中包含suspendConfig并且UE确定不继续或不建立RRC连接，则UE按照suspendConfig指示的配置进入RRC非激活态。如果应答消息中不包含suspendConfig并且UE确定不继续或不建立RRC连接，则UE执行进入RRC空闲态的操作并将释放原因设置为′RRC connection failure‘或′RRC Resume failure‘或′other′或为这一目的而设置的其他值。备选的，如果所述指示标识指示UE进入RRC非激活态，RRC按照最后一次接收到的suspendConfig指示的配置进入RRC非激活态；如果所述指示标识指示UE进入RRC空闲态，则UE执行进入RRC空闲态的操作并将释放原因设置为′RRC connection failure‘或′RRC Resume failure‘或′other′或为这一目的而设置的其他值。
其中suspendConfig用于指示RRC非激活态的配置。
需要说明的是，本实施例中，接收到RRCResume消息执行的操作包括(具体见TS38.331 5.3.13.4)：停止T319，停止T380(如果在运行)等。
接收到RRCSetup消息需要执行的操作包括(具体见TS38.331 5.3.13.7)：丢弃所有UE存储的非激活态AS上下文和suspendConfig(discard any stored UE Inactive AS context and suspendConfig)，丢弃所有目前AS安全上下文(discard any current AS security context)等。
以上对本发明的实施方式进行了具体说明，下面说明本发明的用户设备。
图3是本发明所涉及的用户设备的简要结构框图。
如图3所示，该用户设备300至少包括处理器301和存储器302。处理器301例如可以包括微处理器、微控制器、嵌入式处理器等。存储器302例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、 非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器302上存储有程序指令。该指令在由处理器301运行时，可以执行本公开的上述图1或者图2所描述的用户设备的执行方法中的一个或几个步骤。
上文已经结合优选实施例对本公开的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的，而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。
上面示出的用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本公开并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解，本公开的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
另外，运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他 记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种用户设备的执行方法，所述用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM，其中，所述用户设备的执行方法包括：
    所述用户设备向第一USIM卡对应的第一网络发送用于执行RNAU的RRCResumeRequest消息；以及
    所述用户设备从所述第一网络接收应答消息，
    在所述RRCResumeRequest消息中包含用于指示所述用户设备不能与所述第一网络建立RRC连接的指示标识。
  2. 根据权利要求1所述的用户设备的执行方法，其中，
    所述指示标识用于指示所述用户设备在与所述第一USIM卡不同的第二SIM卡对应的第二网络处于RRC连接态，或者，
    所述指示标识用于指示所述第一网络不能回复RRCResume消息或RRCSetup消息作为所述应答消息，或者，
    所述指示标识用于指示所述用户设备不期望接收到RRCResume消息或RRCSetup消息作为所述应答消息，或者，
    所述指示标识用于指示所述用户设备期望所述第一网络发送RRCRelease消息作为所述应答消息。
  3. 根据权利要求1所述的用户设备的执行方法，其中，
    所述RRCResumeRequest消息中的ResumeCause字段的值设置为用于支持MUSIM的用户设备执行RNAU而定义的值。
  4. 根据权利要求1所述的用户设备的执行方法，其中，
    所述用户设备的RRC层将需要在所述第一网络执行RNAU的信息指示给上层，由所述上层决定所述用户设备是否能与所述第一网络建立RRC连接，
    在所述上层决定所述用户设备不能与所述第一网络建立RRC连接的情况下，在所述RRCResumeRequest消息中包含用于指示所述用户设备不能与所述第一网络建立RRC连接的所述指示标识。
  5. 一种用户设备的执行方法，所述用户设备支持能分别连接到网络的多个USIM卡即支持MUSIM，其中，所述用户设备的执行方法包括：
    所述用户设备向第一USIM卡对应的第一网络发送用于执行RNAU的 RRCResumeRequest消息；
    所述用户设备从所述第一网络接收RRCResume消息或RRCSetup消息作为应答消息；以及
    所述用户设备的RRC层将与所述RRCResume消息或所述RRCSetup消息相关的信息指示给上层。
  6. 根据权利要求5所述的用户设备的执行方法，其中，
    由所述用户设备的RRC层的所述上层确定所述用户设备是否能与所述第一网络继续或建立RRC连接。
  7. 根据权利要求6所述的用户设备的执行方法，其中，
    在所述第一USIM卡的业务的优先级高于正在执行的与所述第一USIM卡不同的第二USIM卡的业务的优先级时，所述上层指示所述用户设备释放RRC连接，并指示所述用户设备与所述第一网络建立RRC连接，
    在所述第一USIM卡的业务的优先级低于正在执行的与所述第一USIM卡不同的第二USIM卡的业务的优先级时，所述上层指示所述用户设备不与所述第一网络建立RRC连接。
  8. 根据权利要求5～7中任一项所述的用户设备的执行方法，其中，
    在所述RRCResume消息或所述RRCSetup消息中包含用于指示所述用户设备不能与所述第一网络继续或建立RRC连接时应进入的RRC状态的指示标识。
  9. 根据权利要求8所述的用户设备的执行方法，其中，
    如果所述应答消息中包含suspendConfig且所述上层确定所述用户设备不能与所述第一网络继续或建立RRC连接，则所述用户设备按照该suspendConfig指示的配置进入RRC非激活态，
    如果所述应答消息中不包含suspendConfig且所述上层确定所述用户设备不能与所述第一网络继续或建立RRC连接，则所述用户设备进入RRC空闲态。
  10. 一种用户设备，支持能分别连接到网络的多个USIM卡即支持MUSIM，所述用户设备包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至4中任 一项所述的方法或者权利要求5至9中任一项所述的用户设备的执行方法。
PCT/CN2022/081667 2021-03-22 2022-03-18 用户设备及其执行方法 WO2022199479A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110304650.5A CN115119340A (zh) 2021-03-22 2021-03-22 用户设备及其执行方法
CN202110304650.5 2021-03-22

Publications (1)

Publication Number Publication Date
WO2022199479A1 true WO2022199479A1 (zh) 2022-09-29

Family

ID=83322979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081667 WO2022199479A1 (zh) 2021-03-22 2022-03-18 用户设备及其执行方法

Country Status (2)

Country Link
CN (1) CN115119340A (zh)
WO (1) WO2022199479A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024092778A1 (zh) * 2022-11-04 2024-05-10 Oppo广东移动通信有限公司 信息指示方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111727620A (zh) * 2018-02-16 2020-09-29 瑞典爱立信有限公司 Rlm和波束监视参数的优化的重新配置
CN111867057A (zh) * 2019-04-29 2020-10-30 华为技术有限公司 通信方法、装置和系统
US20200396788A1 (en) * 2019-06-14 2020-12-17 Samsung Electronics Co., Ltd. Method and system for handling of closed access group related procedure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111727620A (zh) * 2018-02-16 2020-09-29 瑞典爱立信有限公司 Rlm和波束监视参数的优化的重新配置
CN111867057A (zh) * 2019-04-29 2020-10-30 华为技术有限公司 通信方法、装置和系统
US20200396788A1 (en) * 2019-06-14 2020-12-17 Samsung Electronics Co., Ltd. Method and system for handling of closed access group related procedure

Also Published As

Publication number Publication date
CN115119340A (zh) 2022-09-27

Similar Documents

Publication Publication Date Title
JP6822402B2 (ja) 無線端末及びその方法
US11191020B2 (en) Terminal state conversion method and apparatus
EP3689044B1 (en) Systems and methods providing an idle early data transmission solution accommodating power-saving mode
RU2765430C1 (ru) Способ и пользовательское оборудование для создания соединения, избегающие ненужных действий
US10098176B2 (en) Mobile communications system, control apparatus, policy supply system, state transition control method, and policy supply method
US9445310B2 (en) Mobile communication system, network device, and mobile communication method
EP3991508B1 (en) Handling of idle measurement results in rrc_connected
TWI497962B (zh) 回應傳呼訊息
KR20160011339A (ko) 디바이스간 통신을 위한 자원 관리 방법 및 장치
US12069525B2 (en) Communications device, infrastructure equipment and methods
JPWO2019030938A1 (ja) 無線基地局及び無線通信方法
JP2021525462A (ja) リジェクトウェイトタイムの処理
CN110582089B (zh) 系统信息发送的方法以及用户设备
WO2022117007A1 (zh) 用户设备的连接方法以及用户设备
WO2022199479A1 (zh) 用户设备及其执行方法
WO2023098654A1 (zh) 用户设备、基站及其方法
AU2019266726A1 (en) Control method in user equipment, and user equipment
US10383169B2 (en) Base station and terminal connection management method of base station
CN116724663A (zh) 用于维持多sim配置的方法和用户设备
WO2022194194A1 (zh) 在多个网络连接之间切换网络连接的方法及用户设备
CN114698148A (zh) 由用户设备执行的方法以及用户设备
WO2023104142A1 (zh) 由用户设备执行的方法以及用户设备
CN110740484A (zh) 用户设备的控制方法以及用户设备
US20240224366A1 (en) Processing method for remote user equipment and user equipment
WO2022002194A1 (zh) 用户设备执行的网络连接方法以及用户设备

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: 22774140

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22774140

Country of ref document: EP

Kind code of ref document: A1