WO2022002194A1 - 用户设备执行的网络连接方法以及用户设备 - Google Patents

用户设备执行的网络连接方法以及用户设备 Download PDF

Info

Publication number
WO2022002194A1
WO2022002194A1 PCT/CN2021/103980 CN2021103980W WO2022002194A1 WO 2022002194 A1 WO2022002194 A1 WO 2022002194A1 CN 2021103980 W CN2021103980 W CN 2021103980W WO 2022002194 A1 WO2022002194 A1 WO 2022002194A1
Authority
WO
WIPO (PCT)
Prior art keywords
layer
rrc
network
user equipment
indication
Prior art date
Application number
PCT/CN2021/103980
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 WO2022002194A1 publication Critical patent/WO2022002194A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established 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 disclosure relates to the technical field of wireless communication, and more particularly, to a network connection method performed by a user equipment and a user equipment.
  • multi-USIM card 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. As a result, different manufacturers adopt different implementation manners, and the behaviors of user equipment UEs are also different.
  • a UE registered to two or more networks needs to receive paging from these networks, based on the transmitting and receiving capabilities of the UE, there may be a situation that the UE receives a paging from the current network when another It is also paged by the network, or the UE is being paged by another network while the UE is communicating with another network. If the UE switches between different networks, one possible consequence is that the UE can no longer receive data from the current network when the UE switches to another network. This will impair network performance, eg the network sends a page to the UE but the UE does not receive the page due to handover to another network, or the UE is handed over to another network and cannot receive the current network's schedule.
  • the benefit of 3GPP standardization is that it can improve network performance based on predictable UE behavior.
  • One of the goals of this work item is to solve the problem that UEs associated to two networks (Network A and Network B) through different USIM cards collide when receiving pages from the two networks, where Network A can be NR, Network A can be NR, Network B can be LTE or NR, and the UE is single-acquisitive (Single-Rx/Single-Tx); another goal of this work item is to define a mechanism for the UE to notify network A when it leaves network A, where network A is NR, Network B is LTE or NR, and UE single receive single transmit (Single-Rx/Single-Tx) or UE dual receive single transmit (Dual-Rx/Single-Tx).
  • This disclosure discusses related issues involved in achieving the above-mentioned work objectives.
  • a network connection method performed by a user equipment works on a first network or supports multiple USIM cards
  • the network connection method performed by the user equipment includes: the user equipment receives a message from a second network The paging message initiated by the RAN (Radio Access Network, radio access) of the network; the RRC (Radio Resource Control, Radio Resource Control) layer of the user equipment sends or indicates the first layer to the upper layer, that is, the NAS (Non-access stratum, non-access) layer.
  • RAN Radio Access Network, radio access
  • RRC Radio Resource Control, Radio Resource Control
  • the NAS layer determines whether to instruct the RRC layer to initiate an RRC connection continuation process for the second network according to the first indication information, where the first indication information is used to indicate that the upper layer, the user equipment or the RRC layer has received the paging initiated by the RAN A message or an indication that the upper layer needs to trigger the RRC connection continuation process.
  • the cause information is indicated to the upper layer, that is, the NAS layer, and the NAS layer can determine whether to indicate the RRC layer or the second layer based on the cause information.
  • the RRC layer of the network initiates the RRC connection continuation process, and the reason information can be indicated by the PagingCause field.
  • the NAS layer decides to instruct the RRC layer to trigger the RRC connection continuation procedure, it can re-indicate the PagingCause indicated by the RRC layer to the RRC layer.
  • Another embodiment of the present invention is a network connection method performed by a user equipment, where the user equipment works on a first network or supports multiple USIM cards, and the network connection method performed by the user equipment includes: the user equipment receives a message from the first network.
  • the paging message initiated by the RAN (Radio Access Network, radio access) of the second network; the RRC entity layer of the user equipment sends or indicates the second indication to the upper layer, that is, the NAS layer; the NAS layer determines whether to instruct the RRC layer to target the second indication according to the second indication
  • the network initiates the RRC connection continuation process, that is, the NAS layer sends a third indication to the RRC layer; if the RRC layer receives the third indication, it triggers the RRC connection continuation process with the second network or the RRC layer determines whether or not according to the received third indication Trigger the RRC connection continuation process with the second network, wherein the second indication information is used to indicate that the upper-layer user equipment or the RRC has received the paging message initiated by
  • the reason information is indicated to the upper layer, and the NAS layer can send the reason information to the RRC layer or the RRC layer for the second network based on the reason information Third instruction.
  • the RRC layer initiates an RRC connection continuation procedure for the second network; if the third indication is the second indication In the case of a negative acknowledgement, based on the third indication, the RRC layer sends an RRC message to the second network, where the RRC message contains a message indicating that the user equipment is currently busy or, Tx (transmitter, transmitter) and/ Or Rx (receiver, receiver) is currently unavailable or the user equipment is currently unable or does not wish to establish or continue an RRC connection with the network, so that the user equipment or the RRC layer does not establish or continue an RRC connection with the second network.
  • the RRC entity layer can start the first timer after sending or indicating the second indication to the upper layer, namely the NAS layer, or send or indicate the second indication to the upper layer, namely the NAS layer after starting the first timer.
  • the third indication of The paging message is not indicated to the upper layer, that is, the NAS layer.
  • a network connection method performed by a user equipment the user equipment is in an RRC inactive state
  • the network connection method performed by the user equipment includes: if any one of the first condition and the second condition is satisfied condition, the RRC layer of the user equipment or the RRC layer for the second network sends or indicates the fourth indication to the upper layer, that is, the NAS layer; the RRC layer receives the fifth indication from the upper layer, that is, the NAS layer; based on the fifth indication, the RRC The layer initiates the RRC connection continuation process to the second network, or the user equipment or the RRC layer of the user equipment sets the RNA update as the pending RNA process, wherein the fourth indication is for the RRC layer to indicate the pending RNA update to the NAS layer
  • the process or the RRC layer triggers the RNA update process or the RRC layer triggers the RRC connection continuation process caused by the RNA update or the RRC layer needs to perform the RRC connection continuation process
  • the fifth indication is the response of the fourth indication
  • the RRC layer of the user equipment or the RRC layer for the second network starts the second timer after sending or indicating the fourth indication to the upper layer, that is, the NAS layer, or the RRC layer of the user equipment or the RRC layer for the second network starts the second timer.
  • a fourth instruction is sent or indicated to the upper layer, that is, the NAS layer.
  • the RRC layer receives the fifth instruction from the upper layer, that is, the NAS layer, the second timer can be stopped.
  • a user equipment of an embodiment of the present invention includes: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method according to any one of claims 1 to 9 .
  • the invention of the present application can solve the network connection problem caused by receiving the paging message initiated by the RAN from the network B when the UE works in the network A.
  • FIG. 1 is a flowchart showing a network connection method performed by a user equipment UE based on Embodiment 1 of the present disclosure.
  • FIG. 2 is a flowchart showing a network connection method performed by a user equipment UE based on Embodiment 2 of the present disclosure.
  • FIG. 3 is a flowchart showing a network connection method performed by a user equipment UE based on Embodiment 3 of the present disclosure.
  • FIG. 4 is a block diagram representing a user equipment 400 based on an embodiment of the present disclosure.
  • NAS Non-access stratum, non-access stratum.
  • AS access stratum, access layer.
  • 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 layer
  • RNA Notification area for RAN.
  • USIM Universal Subscriber Identity Module, global user identification card.
  • PDCCH Physical Downlink Control Channel.
  • Tx transmitter, transmitter.
  • Rx receiver, receiver.
  • New RAT New Radio Access Technology.
  • USIM and SIM can be used interchangeably, and network, base station and RAN can be used interchangeably, and the network can be a long-term evolution LET network, a new radio access technology (New RAT, NR) network, an enhanced long-term evolution eLTE network , or other networks defined in the subsequent evolution version of 3GPP.
  • New RAT new radio access technology
  • eLTE enhanced long-term evolution eLTE network
  • the user equipment UE may refer to a device that physically supports multiple USIM cards (two or more USIM cards), and the device is equipped with two or more USIM cards. From the perspective of the network, different USIM cards correspond to different UEs, and each USIM card corresponds to one UE. If not specifically stated, the present disclosure does not distinguish this. Those skilled in the art can easily determine whether the UE refers to a UE supporting multiple USIM cards or a UE corresponding to each USIM card in the device supporting multiple USIM cards according to the context.
  • User equipment configured with multiple USIM cards can receive and/or transmit data from multiple networks using single-receiver-single-transmit or dual-receiver-single-transmit through time division multiplexing. For UEs with two Rx, data can be received from two networks at the same time .
  • a user equipment UE with multiple USIM cards has a single-receive-single-transmit (Single-Rx/Single-Tx) or dual-receive-single-transmit (Dual-Rx/Single-Tx) capability.
  • Single-receive-single-transmit Single-Rx/Single-Tx
  • dual-receive-single-transmit Dual-Rx/Single-Tx
  • paging message a paging message initiated by the RAN
  • NAS layer or core network
  • These two kinds of messages are determined by different values or data types of the field ue-Identity in the PagingRecord field carried in the paging message.
  • the value or data type of ue-Identity is ng-5G-S-TMSI
  • the value or data type of ue-Identity is fullI-RNTI
  • the UE in the RRC inactive state, if the ue-Identity (that is, the ue-Identity is fullI-RNTI) contained in a certain PagingRecord field contained in the received paging message is the same as the one stored by the UE If the stored fullI-RNTI matches or is the same (the ue-Identity included the PagingRecord matches the UE's stored fullI-RNT), the UE will initiate the RRC connection resumption procedure. For the operations that need to be performed by the UE to initiate the RRC connection continuation process, see section TS38.3315.3.13 in the latest 3GPP document.
  • a single-acquisition-single-transmit or dual-acquisition-single-transmit UE that supports multiple USIM cards
  • the paging message is a paging message initiated by the RAN (that is, the ue-Identity contained in the PagingRecord field in the received paging message and the fullI stored in the UE) - RNTI matching)
  • the UE receives the paging message initiated by the RAN it will trigger the process of performing the RRC connection continuation in the network B.
  • the UE performs the RRC connection continuation procedure in the network B, which will cause the UE to lose the connection with the network A.
  • the present disclosure aims to solve the problem caused by the UE receiving the RAN-initiated paging message from the network B when the UE is working in the network A.
  • Network A means that the UE is in the RRC connected state, the RRC inactive state or the RRC idle state in the network A, and monitors the network A (receives/transmits data or signaling from the network A) at the same time period leave network A intermittently or intermittently to monitor another network (network B), for example to receive paging messages from said network B.
  • the UE when the UE (or the RRC entity of the UE) receives the paging message initiated by the RAN of the network B, it means that the ue-Identity contained in the PagingRecord field contained in the received paging message is the same as the one stored by the UE. fullI-RNTI matching.
  • FIG. 1 shows a network connection method performed by a user equipment UE related to the first embodiment.
  • the UE working in the network A or the UE supporting multiple USIM cards receives the paging message initiated by the RAN of the network B.
  • the RRC entity sends or indicates indication information to the upper layer or the NAS layer (ie, the NAS layer for network B), and the NAS layer determines whether to instruct the RRC layer to initiate an RRC connection continuation process for network B according to the indication information.
  • the UE working on the network A or the UE supporting multiple USIM cards (or the UE for the RRC layer of the network B) receives a paging message initiated by the RAN of the network B (step 101 ).
  • the RRC layer sends (or indicates) the first indication information to the upper layer (or the NAS layer) (step 102).
  • the first indication information is used to indicate that the upper layer or the NAS layer has received the paging message initiated by the RAN (or indicate that the upper layer UE or the RRC layer has received the paging message initiated by the RAN or indicate that the upper layer needs to trigger the RRC connection continuation process).
  • the NAS layer determines whether to instruct the RRC layer to initiate an RRC connection continuation process for network B according to the first indication information (step 103).
  • the paging message or the PagingRecord field for the UE
  • cause information is indicated to the upper layer (or the NAS layer).
  • the cause information may be indicated by a field, such as a PagingCause field, which may be included in the PagingRecord field, and different values of the PagingCause field indicate different reasons for the network to trigger the paging message initiated by the RAN.
  • the NAS layer may determine whether to instruct the RRC layer (or the RRC layer for network B) to initiate an RRC connection continuation procedure based on the cause information.
  • the PagingCause indicated by the RRC layer may be re-indicated to the RRC layer.
  • the NAS layer may be replaced by an entity in the core network that processes related procedures, such as the access and mobility management function AMF.
  • FIG. 2 shows a network connection method performed by the user equipment UE related to the second embodiment.
  • the UE working on the network A or the UE supporting multiple USIM cards receives a paging message from the RAN of the network B (step 201).
  • the RRC entity sends or indicates a second indication to the upper layer (or the NAS layer, that is, the NAS layer for network B) (step 202), and the NAS layer determines whether to instruct the RRC layer to initiate the RRC connection continuation process for network B according to the second indication, that is, the NAS
  • the layer sends a third indication to the RRC layer (step 203).
  • the RRC layer triggers the RRC connection continuation procedure with the network B or the RRC layer determines whether to trigger the RRC connection continuation procedure with the network B according to the receipt of the third indication (step 204).
  • the UE working in the network A or the UE supporting multiple USIM cards receives the paging message initiated by the RAN of the network B.
  • the UE sends or indicates the second indication information to the upper layer or the NAS layer to the RRC layer of the network B.
  • the second indication information is used to indicate that the upper layer UE or the RRC has received the paging message initiated by the RAN or that the upper layer RRC layer needs to trigger the RRC connection continuation process.
  • the cause information is indicated to the upper layer.
  • the reason information can be indicated by a field, and different values of this field indicate the reason why the network triggers the paging message initiated by the RAN.
  • the NAS layer can send a third indication to the RRC layer or the RRC layer for network B based on the reason information. .
  • the third indication may be at least one of the following (1) or (2):
  • the third indication is a positive response to the second indication.
  • the third indication indicates that the RRC layer can initiate an RRC connection continuation procedure for network B.
  • the RRC layer initiates an RRC connection continuation procedure for network B.
  • the RRC layer sets the value of resumeCause according to the access identifier (AccessIdentity) configured by the upper layer for the UE.
  • the RRC connection continuation process is initiated and resumeCause is set to mps-PriorityAccess; if the UE is configured with access identifier 2 by the upper layer, the RRC connection continuation process is initiated and resumeCause is set It is mcs-PriorityAccess; otherwise, if the UE is configured by the upper layer with access identifiers as one or more of 11-15 (if the UE is configured byupper layers with one or more Access Identities equal to 11-15), then initiate an RRC connection to continue procedure and set resumeCause to highPriorityAccess, otherwise, initiate an RRC connection to continue procedure and set resumeCause to mt-Access. In other embodiments of the present disclosure, during the continuation process of the RRC connection triggered by the RRC layer, resumeCause may also be set according to the description of this embodiment.
  • the third indication is a negative acknowledgment of the second indication indicating that the UE (or the NAS layer or the RCC layer) is currently busy (BUSY) or that Tx and or Rx are currently unavailable.
  • the RRC layer sends an RRC message (eg, RRCResumeRequest or RRCResumeRequest1) to the network B, the message contains a message indicating that the UE is busy or is currently busy or that Tx and/or Rx is currently unavailable or that the UE is currently unavailable or A field for information such as not wishing to establish or continue an RRC connection with the network, so that the UE or the RRC layer does not establish or continue an RRC connection with the network B.
  • RRC message eg, RRCResumeRequest or RRCResumeRequest1
  • the RRC layer initiates an RRC connection continuation process for network B, and the RRC connection continuation message includes a field, such as busyIndecation, to indicate that the UE is currently busy and cannot establish or continue RRC with the network. connect.
  • the third indication is used to indicate that the UE cannot or does not wish to initiate an RRC connection continuation procedure to the network B. In other words, the UE ends this process after receiving the third indication.
  • the RRC entity reports to the upper layer (or the RRC entity).
  • the NAS layer that is, the NAS layer for network B) sends or instructs the second instruction and starts the first timer (it should be noted that the execution sequence of starting the first timer and sending the second instruction can be exchanged to form a new embodiment ); if the RRC layer receives the third indication from the NAS layer, it stops the first timer.
  • the UE working on the network A or the UE supporting multiple USIM cards receives the paging initiated by the RAN of the network B
  • the message is not indicated to the upper layer or the NAS layer.
  • the timer is a prohibit timer, if the UE working in network A or the UE supporting multiple USIM cards (or the RRC layer or RRC entity of the UE for network B) receives a paging message from the RAN of network B and the first timer is not running, send or indicate a second indication to the upper layer; or if the UE working in network A or the UE supporting multiple USIM cards (or the RRC layer or RRC entity of the UE for network B) receives A paging message initiated by the RAN of network B, the reason information carried in the paging message is the same as the reason information contained in the paging message received last time and the first timer is not running, then send to the upper layer Or instruct a second instruction.
  • the UE terminates the current procedure, that is, the UE does not initiate an RRC connection continuation procedure to the network B.
  • the UE initiates an RRC connection continuation process to the network B (that is, sends an RRC message RRCResumeRequest or RRCResumeRequest1), and the RRC message carries indication information or an indication identifier for indicating that the UE is busy .
  • the judgment conditions "the reason information carried in the paging message is the same as the reason information contained in the paging message received last time" and "the first timer is not running" can be executed in an interchangeable order to obtain a new implementation. example.
  • the RRC layer or the NAS layer for the network B refers to the equivalent layer of the RRC layer or the NAS layer of the network B, and the layer and the entity may be used interchangeably.
  • the UE working in network A or the UE supporting multiple USIM cards receives a paging message initiated by the RAN of network B
  • the specific implementation of carrying the indication information or indication identifier for indicating that the UE is busy in the RRC message may be one of the following two implementation manners: (1) ResumeCause included in the RRC message or RRCResumeRequest or RRCResumeRequest1 The value of the field is set to the corresponding value indicating that the UE is currently busy or that the UE does not wish to establish or continue the RRC connection, such as BUSY; (2) The field BusyIndication is included in the RRC message or RRCResumeRequest or RRCResumeRequest1 message, indicating that the UE is currently Busy or UE does not wish to establish or continue RRC connection.
  • UEs working in network A UEs supporting multiple USIM cards, UEs configured with multiple USIM cards, UEs that are not available for lower layer transmission of network B, UEs that network B Tx/Rx are unavailable, and network indications It supports UE access with multiple USIM cards and the UE is a UE that supports multiple USIM cards, the UE is configured to report the time information of leaving the current network, supports the reporting of the time information of leaving the current network, supports the UE that dynamically switches between different networks, shares Tx and /or Rx UE, these expressions are used interchangeably.
  • the UE or the RRC layer of the UE will initiate an RRC connection continuation process.
  • the UE works in network A and leaves network A periodically or intermittently to monitor network B, for example, to receive a request from network B call message.
  • the UE has an RNA update for the network B, according to the operation defined by the existing system, when the RNA update occurs, the UE will trigger the process of performing the RRC connection continuation in the network B.
  • the timer T380 is used to trigger the timer of the periodic RNA update procedure in the UE (T380 refers to the timer that triggers the periodicRNAU procedure in UE).
  • FIG. 3 shows a network connection method performed by the user equipment UE related to the third embodiment.
  • T380 expires or RNA update is triggered due to reception of SIB1, and if the UE is a UE that supports multiple USIM cards;
  • Condition 2 If the prohibition of access type 8 and access type 2 is lifted (if barring isalleviated for Access Category′8′or Access Category′2′), and the upper layer does not request RRC to continue the RRC connection (if upper layers do not request RRC the resumption of anRRC connection), and the value of the variable pendingRNA-Update is set to true, and if the UE is a UE that supports multiple USIM cards;
  • the RRC layer (or the RRC layer for network B) of the UE supporting multiple USIM cards sends or indicates the fourth indication to the upper layer or the NAS layer. That is, if the UE in the RRC inactive state satisfies any one of the above two conditions, the RRC layer of the user equipment or the RRC layer for the second network sends or indicates the fourth indication to the upper layer or the NAS layer (step 301), Optionally, start the second timer (the execution order can be exchanged by sending the fourth indication and starting the second timer). Optionally, the RRC layer will continue cause information rnaUpdate to instruct the upper layer or set resumeCause to rnaUpdate and instruct the upper layer.
  • the RRC layer receives the fifth indication from the upper layer or the NAS layer (step 302), and optionally, stops the second timer.
  • the fourth indication is for the RRC layer to indicate to the NAS layer the pending RNA update process or the RRC layer triggers the RRC connection continuation process caused by the RNA update or the RRC layer needs to perform the RRC connection continuation process.
  • the fifth indication is a response to the fourth indication. Based on the fifth indication, the RRC layer initiates the RRC connection continuation procedure to the network B, or the UE or the RRC layer of the UE sets the RNA update as the pending RNA procedure (step 303).
  • the RRC layer initiates an RRC connection continuation process to the network B, and optionally, resumeCause is set to rnaUpdate, which is used to instruct the UE to continue
  • the reason for this pending RRC connection is RNA renewal.
  • the UE or the RRC layer of the UE sets the RNA update as a pending RNA process, for example, sets the variable pendingRNA-Update to A value set to true indicates that the RNA is updated to a pending RNA process.
  • the UE or the RRC layer of the UE sets the RNA update as a pending (pending) RNA process, for example, sets the value of the variable pendingRNA-Update to true (true), indicating that the RNA update for the RNA process to be processed.
  • the affirmative response and negative response of the fourth indication can be realized by different values of the fifth indication, and can also be realized by different indications, for example, the fifth indication indicates a positive response, and the sixth indication indicates a negative response.
  • the RRC may not perform the operations that need to be performed for receiving the negative response of the fourth indication described in the above embodiment, but terminate the RNA update. process, because in this case the value of the variable pendingRNA-Update has already been set to true.
  • the second timer may also be a disable timer, and during the running period of the second timer, the RRC layer cannot again indicate the fourth indication to the upper layer.
  • the UE supporting multiple USIM cards sets the RNA update as the pending RNA process.
  • the RRC layer of the UE (or the RRC layer for network B) may send or indicate the sixth indication to the upper layer or the NAS layer.
  • the sixth indication is used for the RRC layer to indicate to the NAS layer the pending RNA update process or the RRC layer triggers the RRC connection continuation process caused by the RNA update or the RRC layer needs to perform the RRC connection continuation process.
  • the RRC layer will continue the reason information rnaUpdate to indicate the upper layer or set resumeCause to rnaUpdate and indicate the upper layer.
  • the RRC layer receives the seventh indication from the upper layer or the NAS layer (the seventh indication can be regarded as a response to the sixth indication). Based on the seventh indication, the RRC layer initiates an RRC connection continuation process to the network B, and optionally, resumeCause is set to rnaUpdate, which is used to instruct the UE to continue the suspended RRC connection because of RNA update.
  • the resumeCause field is included in the RRC connection continuation request message for requesting to resume a suspended (suspended) RRC connection, and it provides a continuation reason for sending the RRC connection continuation request (it provides the resumecause for the RRC connenction resume request)
  • a UE with multiple USIM cards means that the UE includes two or more USIM cards, and accesses or accesses or registers or resides in different or the same network respectively. For example, one of the USIM cards subscribes to network A, and the other USIM card subscribes to network B. The UE is scheduled or communicated with the network on the two networks according to its registered USIM card information or access information.
  • the UE supporting multiple USIM cards may also be referred to as a UE sharing one Tx, or a UE sharing a pair of Rx and Tx. A pair of Rx and Tx includes one Rx and one Tx.
  • RRC, RRC entity, and RRC layer can be used interchangeably, and NAS, NAS entity, and NAS layer can be used interchangeably.
  • NAS, NAS entity, and NAS layer can be used interchangeably.
  • the RRC when the RRC needs to initiate the RRC connection continuation process because it receives a paging message initiated by the RAN or needs to perform an RNA update, it may not instruct the upper layer, but instruct the RRC corresponding to another USIM card,
  • the indication information and response are the same as or similar to those described in the embodiments of the present disclosure, and are not repeated here. Those skilled in the art can deduce the operations performed when indicating the RRC entity corresponding to another USIM card according to the embodiments of the present disclosure.
  • FIG. 4 is a schematic structural block diagram of the user equipment UE involved in the present invention.
  • the user equipment UE400 includes a processor 401 and a memory 402 .
  • the processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
  • the memory 402 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, or the like.
  • Program instructions are stored on the memory 402 . When the instructions are executed by the processor 401, the above-mentioned methods described in detail in the present invention and executed by the user equipment can be executed.
  • the computer-executable instructions or programs running on the apparatus according to the present disclosure may be programs that cause the computer to implement the functions of the embodiments of the present disclosure 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 various embodiments of the present disclosure 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. In the event that new integrated circuit technologies emerge as a result of advances in semiconductor technology to replace existing integrated circuits, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

Landscapes

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

Abstract

本发明提供一种用户设备执行的网络连接方法，该用户设备工作在第一网络或者支持多USIM卡，所述用户设备执行的网络连接方法包括：所述用户设备接收到来自第二网络的RAN(Radio Access Network，无线接入)发起的寻呼消息；用户设备的RRC(Radio Resource Control，无线资源控制)层向上层即NAS(Non-access stratum，非接入)层发送或指示第一指示信息；NAS层根据所述第一指示信息确定是否指示RRC层针对第二网络发起RRC连接继续过程，所述第一指示信息用于指示上层、用户设备或RRC层接收到了RAN发起的寻呼消息或指示上层需要触发RRC连接继续过程。

Description

用户设备执行的网络连接方法以及用户设备 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及一种用户设备执行的网络连接方法以及用户设备。
背景技术
近年来，多USIM卡设备越来越流行。例如一个用户在支持多USIM卡的手机上安装两张USIM卡，其中一张USIM卡用于订阅私人业务，另一张USIM卡用于订阅办公业务。现有支持多USIM卡的设备是基于厂商实现，尚未被3GPP标准化。导致不同的厂商采用不同的实现方式，用户设备UE的行为也各不相同。现有实现方式中，如果注册到两个或两个以上网络的UE需要从这些网络接收寻呼，基于UE的收发能力，可能存在的一种情形是UE在接收当前网络的寻呼时另一个网络也对其发起寻呼，又或者UE正与一个网络通信时另一个网络对其发起寻呼。如果UE在不同的网络之间切换，可能导致的一个结果是当UE切换到另一个网络时UE不能再从当前网络接收数据。这将损害网络性能，例如网络向UE发送了寻呼但UE因切换到另一个网络而没有接收到这个寻呼，或UE切换到另一个网络而不能接收当前网络的调度。3GPP标准化的好处在于其可以基于可预测的UE行为，提升网络性能。
基于上述原因，2019年12月，在第三代合作伙伴计划(3rd GenerationPartnership Project：3GPP)RAN#86次全会上，vivo提出了针对版本17的多SIM卡设备的工作项目(参见非专利文献：RP-193263：New WID：StupportofMulti-SIM devices in Rel-17)，并获批准。该工作项目的目标之一是解决通过不同的USIM卡关联到两个网络(网络A和网络B)的UE在接收来自两个网络的寻呼发生冲突的问题，其中网络A可以是NR，网络B可以是LTE或NR，且UE单收单发(Single-Rx/Single-Tx)；该工作项目的另一个目标是定义UE在离开网络A时通知网络A的机制，其中网络A是 NR，网络B是LTE或NR，且UE单收单发(Single-Rx/Single-Tx)或UE双收单发(Dual-Rx/Single-Tx)。
本公开讨论达成上述工作目标所涉及的相关问题。
发明内容
本申请发明的一个实施方式的用户设备执行的网络连接方法，该用户设备工作在第一网络或者支持多USIM卡，所述用户设备执行的网络连接方法包括：所述用户设备接收到来自第二网络的RAN(Radio AccessNetwork，无线接入)发起的寻呼消息；用户设备的RRC(Radio ResourceControl，无线资源控制)层向上层即NAS(Non-access stratum，非接入)层发送或指示第一指示信息；NAS层根据所述第一指示信息确定是否指示RRC层针对第二网络发起RRC连接继续过程，所述第一指示信息用于指示上层、用户设备或RRC层接收到了RAN发起的寻呼消息或指示上层需要触发RRC连接继续过程。
如果所述寻呼消息或针对所述用户设备的PagingRecord字段中包含原因信息，则将所述原因信息指示给上层即NAS层，NAS层可以基于所述原因信息判断是否指示RRC层或针对第二网络的RRC层发起RRC连接继续过程，所述原因信息能用PagingCause字段指示。
如果NAS层决定指示RRC层触发RRC连接继续过程，则能将RRC层指示的PagingCause重新指示给RRC层。
本申请发明的另一实施方式的用户设备执行的网络连接方法，该用户设备工作在第一网络或者支持多USIM卡，所述用户设备执行的网络连接方法包括：所述用户设备接收到来自第二网络的RAN(Radio AccessNetwork，无线接入)发起的寻呼消息；用户设备的RRC实体层向上层即NAS层发送或指示第二指示；NAS层根据第二指示判断是否指示RRC层针对第二网络发起RRC连接继续过程，即NAS层向RRC层发送第三指示；如果RRC层接收到第三指示，则触发与第二网络的RRC连接继续过程或RRC层根据接收到的第三指示确定是否触发与第二网络的RRC连接继续过程，其中，所述第二指示信息用于指示上层用户设备或RRC接收到了RAN发起的寻呼消息或指示上层RRC层需要触发RRC连接继续过程，所述第 三指示是第二指示的应答。
如果所述寻呼消息或针对所述用户设备的PagingRecord字段中包含原因信息，则将所述原因信息指示给上层，NAS层可以基于所述原因信息向RRC层或针对第二网络的RRC层发送第三指示。
在所述第三指示是所述第二指示的肯定应答的情况下，基于所述第三指示，RRC层针对第二网络发起RRC连接继续过程；在所述第三指示是所述第二指示的否定应答的情况下，基于所述第三指示，RRC层向第二网络发送RRC消息，所述RRC消息中包含用于指示用户设备当前正繁忙或、Tx(transmitter，发信机)和/或Rx(receiver，接收机)当前不可用或用户设备当前无法或不希望与网络建立或继续RRC连接等信息，使得用户设备或RRC层不与第二网络建立或继续RRC连接。
RRC实体层能向上层即NAS层发送或指示第二指示之后启动第一定时器，或者在启动第一定时器之后向上层即NAS层发送或指示第二指示，如果RRC层接收到来自NAS层的第三指示时，则停止第一定时器，在所述第一定时器运行期间，所述用户设备或用户设备针对第二网络的RRC层或RRC实体层接收到来自第二网络的RAN发起的寻呼消息时不指示给上层即NAS层。
本发明的再一实施方式的用户设备执行的网络连接方法，所述用户设备处于RRC非激活态，所述用户设备执行的网络连接方法包括：如果满足第一条件和第二条件中的任一个条件，则用户设备的RRC层或针对第二网络的RRC层向上层即NAS层发送或指示第四指示；RRC层接收到来自上层即NAS层的第五指示；基于所述第五指示，RRC层向第二网络发起RRC连接继续过程、或者用户设备或用户设备的RRC层将RNA更新设置为待处理RNA过程，其中，所述第四指示用于RRC层向NAS层指示待处理的RNA更新过程或RRC层触发了RNA更新过程或RRC层触发了由RNA更新导致的RRC连接继续过程或者RRC层需要进行RRC连接继续过程，所述第五指示是第四指示的应答，所述第一条件为T380到期或因接收到SIB1而触发RNA更新，并且如果用户设备是支持多USIM卡的用户设备，所述第二条件为第一访问类型和第二访问类型的禁止被解除，并且上层没有请求RRC继续RRC连接，并且变量pendingRNA-Update的值被设置为真， 并且用户设备是支持多USIM卡的用户设备。
用户设备的RRC层或针对第二网络的RRC层在向上层即NAS层发送或指示第四指示之后启动第二定时器，或者用户设备的RRC层或针对第二网络的RRC层在启动第二定时器之后向上层即NAS层发送或指示第四指示，在RRC层接收到来自上层即NAS层的第五指示时，能停止第二定时器。
本发明的一实施方式的用户设备，包括：处理器；以及存储器，存储有指令，其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
发明效果
本申请发明能够解决当UE工作在网络A而接收到来自网络B的RAN发起的寻呼消息所导致的网络连接问题。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1为表示基于本公开的实施例一的用户设备UE执行的网络连接方法的流程图。
图2为表示基于本公开的实施例二的用户设备UE执行的网络连接方法的流程图。
图3为表示基于本公开的实施例三的用户设备UE执行的网络连接方法的流程图。
图4为表示基于本公开的实施例的用户设备400的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，术语的具体含义见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空闲态。
RAN；Radio Access Network，无线接入层。
RNA：RAN的通知区域。
USIM：Universal Subscriber Identity Module，全球用户识别卡。
PDCCH：物理下行控制信道。
Tx：transmitter，发信机。
Rx：receiver，接收机。
NR：New RAT，新无线访问技术。
本公开中，USIM和SIM可互换使用，网络、基站和RAN可互换使用，所述网络可以是长期演进LET网络、新无线访问技术(New RAT，NR)网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
本公开中，用户设备UE可指物理上支持多USIM卡(两个或两个以上USIM卡)的设备，所述设备装配了两个或两个以上USIM卡。从网络的角度来看，不同的USIM卡对应不同的UE，每个USIM卡对应一个UE。如未特别说明，本公开不对此加以区分。本领域技术人员可以根据上下文容易地确定UE是指支持多USIM卡的UE还是支持多USIM卡的设备中每个USIM卡对应的UE。配置了多USIM卡的用户设备可以通过时分复用方式利用单收单发或双收单发从多个网络接收和/或发送数据，对于具有两个Rx的UE，可以同时两个网络接收数据。
本公开中，具有多个USIM卡的用户设备UE具有单收单发(Single-Rx/Single-Tx)或双收单发(Dual-Rx/Single-Tx)能力。多个USIM对应的不同UE共用一对Tx和Rx或共用一个Tx但分别具有各自的Rx。
在NR中，支持两种类型的寻呼消息，其中一种是由RAN发起的寻呼消息(Paging message)，另一种是由NAS层(或核心网)发起的寻呼消息。 这两种消息是通过携带在寻呼消息中的PagingRecord字段中的字段ue-Identity的不同取值或数据类型确定的。当ue-Identity的取值或数据类型是ng-5G-S-TMSI，表示是NAS层发起的寻呼；当ue-Identity的取值或数据类型是fullI-RNTI，表示是RAN发起的寻呼。
以下是TS38.331定义的寻呼消息携带的字段信息(各字段的含义见TS38.331、TS38.304等相关文档中的描述)：
Figure PCTCN2021103980-appb-000001
在现有的系统中，处于RRC非激活态的UE，如果接收到的寻呼消息中包含的某个PagingRecord字段中所包含的ue-Identity(即ue-Identity是fullI-RNTI)与UE所存贮的fullI-RNTI匹配或相同(the ue-Identity includedin the PagingRecord matches the UE′s stored fullI-RNT)，UE将发起RRC连接继续过程(initiate the RRC connection resumption procedure)。UE发起RRC连接继续过程需要执行的操作见3GPP最新文档TS38.3315.3.13节。
但是，对于支持多USIM卡的单收单发或双收单发的UE，当UE工作在网络A并且周期性或间歇性地离开网络A去监测网络B，例如去接收来自网络B的寻呼消息。当接收到来自网络B的寻呼消息时，如果所述寻呼消息是RAN发起的寻呼消息(即接收到的寻呼消息中PagingRecord字段中所包含的ue-Identity与UE所存贮的fullI-RNTI匹配)，按照现有系统定义 的操作，UE在接收到RAN发起的寻呼消息时，将触发在网络B执行RRC连接继续的过程。但是，如果此时UE在网络A处于RRC连接态，UE在网络B执行RRC连接继续过程将导致UE丢失与网络A的连接。本公开致力于解决当UE工作在网络A而接收到来自网络B的RAN发起的寻呼消息所导致的问题。
本公开中，UE工作在一个网络(网络A)是指UE在网络A处于RRC连接态或RRC非激活态或RRC空闲态，监测网络A(从网络A收/发数据或信令)同时周期性或间歇性的离开网络A去监测另一个网络(网络B)，例如去接收来自所述网络B的寻呼消息。
本公开中，UE(或UE的RRC实体)接收到来自网络B的RAN发起的寻呼消息是指接收到的寻呼消息中包含的PagingRecord字段中所包含的ue-Identity与UE所存贮的fullI-RNTI匹配。
以下，结合附图来详细描述本发明的若干实施例。
(实施例一)
参照图1对实施例进行具体说明。图1中示出实施例一相关的用户设备UE执行的网络连接方法。
在实施例一中，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息。RRC实体向上层或NAS层(即针对网络B的NAS层)发送或指示指示信息，NAS层根据所述指示信息确定是否指示RRC层针对网络B发起RRC连接继续过程。具体地，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层)接收到来自网络B的RAN发起的寻呼消息(步骤101)。RRC层向上层(或NAS层)发送(或指示)第一指示信息(步骤102)。所述第一指示信息用于指示上层或NAS层接收到了RAN发起的寻呼消息(或指示上层UE或RRC层接收到了RAN发起的寻呼消息或指示上层需要触发RRC连接继续过程)。NAS层根据所述第一指示信息确定是否指示RRC层针对网络B发起RRC连接继续过程(步骤103)。可选的，如果所述寻呼消息(或针对所述UE的PagingRecord字段)中还包含原因信息，则将所述原因信息指示给上层(或NAS层)。所述原因信息可以用一个字段指示，例如用PagingCause字段表示，所述字段可以包含在PagingRecord字段中，PagingCause字段的不同取值表示网络触发RAN 发起的寻呼消息的不同原因。NAS层可以基于所述原因信息判断是否指示RRC层(或针对网络B的RRC层)发起RRC连接继续过程。可选的，如果NAS层决定指示RRC层触发RRC连接继续过程，可以将RRC层指示的PagingCause重新指示给RRC层。
需要说明的是，本公开中NAS层可以用核心网中处理相关过程的实体代替，例如接入和移动管理功能AMF。
(实施例二)
参照图2对实施例进行具体说明。图2中示出实施例二相关的用户设备UE执行的网络连接方法。
在实施例二中，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息(步骤201)。RRC实体向上层(或NAS层，即针对网络B的NAS层)发送或指示第二指示(步骤202)，NAS层根据第二指示判断是否指示RRC层针对网络B发起RRC连接继续过程，即NAS层向RRC层发送第三指示(步骤203)。如果RRC层接收到第三指示，则触发与网络B的RRC连接继续过程或RRC层根据接收到第三指示确定是否触发与网络B的RRC连接继续过程(步骤204)。具体地，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层)接收到来自网络B的RAN发起的寻呼消息。UE针对网络B的RRC层向上层或NAS层发送或指示第二指示信息。所述第二指示信息用于指示上层UE或RRC接收到了RAN发起的寻呼消息或指示上层RRC层需要触发RRC连接继续过程。可选的，如果所述寻呼消息或针对所述UE的PagingRecord字段中还包含原因信息，则将所述原因信息指示给上层。所述原因信息可以用一个字段指示，该字段的不同取值表示网络触发RAN发起的寻呼消息的原因，NAS层可以基于所述原因信息向RRC层或针对网络B的RRC层发送第三指示。所述第三指示可以是以下(1)或(2)的至少之一：
(1)所述第三指示是第二指示的肯定应答，例如第三指示指示RRC层可以针对网络B发起RRC连接继续过程，基于所述第三指示，RRC层针对网络B发起RRC连接继续过程。可选的，在RRC层针对网络B发起RRC连接继续过程时，RRC层根据上层为UE配置的访问标识(AccessIdentity)设置resumeCause的值。具体的，如果UE被上层配置了具有访问 标识1，则发起RRC连接继续过程并将resumeCause设置为mps-PriorityAccess；如果UE被上层配置了具有访问标识2，则发起RRC连接继续过程并将resumeCause设置为mcs-PriorityAccess；否则，如果UE被上层配置了访问标识为11-15中一个或多个(if the UE is configured byupper layers with one or more Access Identities equal to 11-15)，则发起RRC连接继续过程并将resumeCause设置为highPriorityAccess，否则，发起RRC连接继续过程并将resumeCause设置为mt-Access。在本公开其他实施例中，在由RRC层触发的RRC连接继续过程中，也可以按照本实施例的描述设置resumeCause。
(2)所述第三指示是第二指示的否定应答，所述第三指示指示UE(或NAS层或RCC层)当前正繁忙(BUSY)或Tx和或Rx当前不可用。基于所述第三指示，RRC层向网络B发送RRC消息(例如RRCResumeRequest或RRCResumeRequest1)，所述消息中包含用于指示UE繁忙或当前正繁忙或Tx和/或Rx当前不可用或UE当前无法或不希望与网络建立或继续RRC连接等信息的字段，使得UE或RRC层不与网络B建立或继续RRC连接。例如，基于所述第三指示，RRC层针对网络B发起RRC连接继续过程，在所述RRC连接继续消息中包含一个字段，例如busyIndecation，用于指示UE当前正忙，无法与网络建立或继续RRC连接。备选的，所述第三指示用于指示UE不能或不希望向网络B发起RRC连接继续过程。换言之，UE在接收到所述第三指示后，结束这一过程。
可选的，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息时，RRC实体向上层(或NAS层，即针对网络B的NAS层)发送或指示第二指示并启动第一定时器(需要说明的是，可以交换启动第一定时器和发送第二指示的执行顺序，形成新的实施例)；如果RRC层接收到来自NAS层的第三指示时，停止第一定时器。优选的，在所述第一定时器运行期间，工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息时不指示给上层或NAS层。换言之，所述定时器是禁止定时器，如果工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息且所述第一定时器未运行，则向 上层发送或指示第二指示；或者如果工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层或RRC实体)接收到来自网络B的RAN发起的寻呼消息，所述寻呼消息中携带的原因信息与上一次接收到的寻呼消息中包含的原因信息相同且所述第一定时器未运行，则向上层发送或指示第二指示。备选的，在所述定时器到期时，UE终止当前过程，即UE不向网络B发起RRC连接继续过程。备选的，在所述定时器到期时，UE向网络B发起RRC连接继续过程(即发送RRC消息RRCResumeRequest或RRCResumeRequest1)，在所述RRC消息中携带用于指示UE繁忙的指示信息或指示标识。需要说明的是判断条件“寻呼消息中携带的原因信息与上一次接收到的寻呼消息中包含的原因信息相同”和“所述第一定时器未运行”可交换顺序执行得到新的实施例。
在本公开实施例中，针对网络B的RRC层或NAS层是指网络B的RRC层或NAS层的对等层，层与实体可互换使用。
本公开实施例中，“工作在网络A的UE或支持多USIM卡的UE(或UE针对网络B的RRC层)接收到来自网络B的RAN发起的寻呼消息”可以描述为“接收到寻呼消息，如果UE处于RRC非激活态，对于寻呼消息中包含的每个PagingRecord，如果包含在PagingRecord中的ue-Identity与UE存储的fullI-RNTI相同或匹配并且UE是支持多USIM卡的UE或工作在网络A的UE”。
在本公开实施例中，RRC消息中携带用于指示UE繁忙的指示信息或指示标识的具体实现可以是以下两种实现方式中的一个：(1)将RRC消息或RRCResumeRequest或RRCResumeRequest1中包含的ResumeCause字段的值设置为表示UE当前繁忙对应的值或的UE不希望建立或继续RRC连接的对应的值，例如BUSY；(2)在RRC消息或RRCResumeRequest或RRCResumeRequest1消息中包含字段BusyIndication，表示UE当前的繁忙或UE不希望建立或继续RRC连接。
本公开实施例中，工作在网络A的UE、支持多USIM卡的UE、被配置了多USIM卡的UE、网络B下层传输不可用的UE、网络B Tx/Rx不可用的UE、网络指示其支持多USIM卡UE接入且UE是支持多USIM卡的UE、UE被配置上报离开当前网络的时间信息、支持上报离开当前网络时间信息、支持在不同网络间动态切换的UE、共享Tx和/或Rx的UE，这些 表述可互换使用。
以上支持多USIM卡的UE在接收到RAN发起的寻呼消息时面临的问题在支持多USIM卡的UE发送基于RAN的通知区域(RAN-basedNotificationArea)RNA更新时同样会出现。以下具体描述。
在现有的系统中，对处于RRC非激活态的UE而言，如果T380到期或因接收到SIB1而触发RNA更新等，UE或UE的RRC层会发起RRC连接继续过程。同样的，对于支持多USIM卡的单收单发或双收单发的UE，当UE工作在网络A并且周期性或间歇性的离开网络A去监测网络B，例如去接收来自网络B的寻呼消息。当UE发生针对网络B的RNA更新时，按照现有系统定义的操作，UE在发生RNA更新时，将触发在网络B执行RRC连接继续的过程。但是，如果此时UE在网络A处于RRC连接态，UE在网络B执行RRC连接继续过程将导致UE丢失与网络A的连接。下面描述针对这一问题的解决方案。定时器T380用于在UE中触发周期性RNA更新过程的定时器(T380 refers to the timer that trigger the periodicRNAU procedure in UE)。
(实施例三)
参照图3对实施例三进行具体说明。图3中示出实施例三相关的用户设备UE执行的网络连接方法。
在实施例三中，对处于RRC非激活态的UE而言，如果满足以下条件1和2之一：
条件1：T380到期或因接收到SIB1而触发RNA更新，并且如果UE是支持多USIM卡的UE；
条件2：如果访问类型8和访问类型2的禁止被解除(if barring isalleviated for Access Category′8′or Access Category′2′)，并且上层没有请求RRC继续RRC连接(if upper layers do not request RRC the resumption of anRRC connection)，并且变量pendingRNA-Update的值被设置为真(true)，并且如果UE是支持多USIM卡的UE；
那么，支持多USIM卡的UE的RRC层(或针对网络B的RRC层)向上层或NAS层发送或指示第四指示。即如果处于RRC非激活态的UE满足上述两个条件中的任一个条件，则用户设备的RRC层或针对第二网络的RRC层向上层或NAS层发送或指示第四指示(步骤301)，可选的，启 动第二定时器(发送第四指示和启动第二定时器可交换执行顺序)，可选的，RRC层将继续原因信息rnaUpdate指示上层或者将resumeCause设置为rnaUpdate并指示上层。RRC层接收到来自上层或NAS层的第五指示(步骤302)，可选的，停止第二定时器。所述第四指示用于RRC层向NAS层指示待处理的RNA更新过程或RRC层触发了由RNA更新导致的RRC连接继续过程或者RRC层需要进行RRC连接继续过程。所述第五指示是第四指示的应答。基于所述第五指示，RRC层向网络B发起RRC连接继续过程、或者UE或UE的RRC层将RNA更新设置为待处理RNA过程(步骤303)。在所述第五指示是第四指示的肯定应答的情况下，基于所述第五指示，RRC层向网络B发起RRC连接继续过程，可选的，将resumeCause设置为rnaUpdate，用于指示UE继续这个挂起的RRC连接的原因是RNA更新。在所述第五指示是第四指示的否定应答的情况下，基于所述第五指示，UE或UE的RRC层将RNA更新设置为待处理(pending)RNA过程，例如将变量pendingRNA-Update的值设置为真(true)，表示RNA更新为待处理RNA过程。可选的，当第二定时器到期时，UE或UE的RRC层将RNA更新设置为待处理(pending)RNA过程，例如将变量pendingRNA-Update的值设置为真(true)，表示RNA更新为待处理RNA过程。需要说明的是，第四指示的肯定应答和否定应答可以通过第五指示的不同取值实现，也可以通过不同的指示实现，例如第五指示表示肯定应答，第六指示表示否定应答。
需要说明的是，对于满足条件2的情形，如果RRC接收到第四指示的否定应答，可以不执行上述实施例中描述的接收到第四指示的否定应答需要执行的操作，而是终止RNA更新过程，因为在这种情况下，变量pendingRNA-Update的值已经被设置为真(true)。
与第一定时器类似，第二定时器也可以是禁止定时器，在第二定时器运行期间，RRC层不能再次向上层指示第四指示。
(实施例四)
作为实施例三的替代实施例，对处于RRC非激活态的UE而言，如果满足实施例三所述条件1和2之一，支持多USIM卡的UE将RNA更新设置为待处理RNA过程。然后，UE的RRC层(或针对网络B的RRC层)可以向上层或NAS层发送或指示第六指示。所述第六指示用于RRC层向 NAS层指示待处理的RNA更新过程或RRC层触发了由RNA更新导致的RRC连接继续过程或者RRC层需要进行RRC连接继续过程。可选的，RRC层将继续原因信息rnaUpdate指示上层或者将resumeCause设置为rnaUpdate并指示上层。RRC层接收到来自上层或NAS层的第七指示(所述第七指示可以看作是第六指示的应答)。基于所述第七指示，RRC层向网络B发起RRC连接继续过程，可选的，将resumeCause设置为rnaUpdate，用于指示UE继续这个挂起的RRC连接的原因是RNA更新。
在本公开实施例中，所述resumeCause字段包含在用于请求继续(resumeption)一个挂起(suspended)的RRC连接的RRC连接继续请求消息中，它提供了发送RRC连接继续请求的继续理由(it provides the resumecause for the RRC connenction resume request)
本公开中，多USIM卡的UE是指UE中包含两张或两张以上USIM卡，并且分别接入或访问或注册或驻留到不同或相同的网络。例如，其中一张USIM卡订阅网络A，另一张USIM卡订阅网络B。UE在这两个网络上按照其注册的USIM卡信息或接入信息分别被网络调度或与网络通信。所述支持多USIM卡的UE也可以称为共用一个Tx的UE，或共用一对Rx和Tx的UE。一对Rx和Tx包括一个Rx和一个Tx。
本公开实施例中，RRC、RRC实体、RRC层可互换使用，NAS、NAS实体、NAS层可互换使用，本领域技术人员根据上下文信息可以很容易推断这些词语表示的含义。
本公开的上述实施例中，在RRC因接收到RAN发起的寻呼消息或需要执行RNA更新而需要发起RRC连接继续过程时，也可以不指示上层，而是指示另一个USIM卡对应的RRC，所述指示信息与应答与本公开实施例描述相同或类似，不再累述，本领域技术人员可以根据本公开实施例推导出指示另一个USIM卡对应的RRC实体时执行的操作。
图4是本发明涉及的用户设备UE的简要结构框图。如图4所示，该用户设备UE400包括处理器401和存储器402。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本发明详细描述的由用户设备执行的上述 方法。
另外，运行在根据本公开的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互 替代。

Claims (10)

  1. 一种用户设备执行的网络连接方法，该用户设备工作在第一网络或者支持多USIM卡，所述用户设备执行的网络连接方法包括：
    所述用户设备接收到来自第二网络的RAN(Radio Access Network，无线接入)发起的寻呼消息；
    用户设备的RRC(Radio Resource Control，无线资源控制)层向上层即NAS(Non-access stratum，非接入)层发送或指示第一指示信息；
    NAS层根据所述第一指示信息确定是否指示RRC层针对第二网络发起RRC连接继续过程，
    所述第一指示信息用于指示上层、用户设备或RRC层接收到了RAN发起的寻呼消息或指示上层需要触发RRC连接继续过程。
  2. 根据权利要求1所述的用户设备执行的网络连接方法，其中，
    如果所述寻呼消息或针对所述用户设备的PagingRecord字段中包含原因信息，则将所述原因信息指示给上层即NAS层，NAS层可以基于所述原因信息判断是否指示RRC层或针对第二网络的RRC层发起RRC连接继续过程，
    所述原因信息能用PagingCause字段指示。
  3. 根据权利要求1所述的用户设备执行的网络连接方法，其中，
    如果NAS层决定指示RRC层触发RRC连接继续过程，则能将RRC层指示的PagingCause重新指示给RRC层。
  4. 一种用户设备执行的网络连接方法，该用户设备工作在第一网络或者支持多USIM卡，所述用户设备执行的网络连接方法包括：
    所述用户设备接收到来自第二网络的RAN(Radio Access Network，无线接入)发起的寻呼消息；
    用户设备的RRC层向上层即NAS层发送或指示第二指示；
    NAS层根据第二指示判断是否指示RRC层针对第二网络发起RRC连接继续过程，即NAS层向RRC层发送第三指示；
    如果RRC层接收到第三指示，则触发与第二网络的RRC连接继续过程或RRC层根据接收到的第三指示确定是否触发与第二网络的RRC连接继续过程，
    其中，所述第二指示信息用于指示上层用户设备或RRC接收到了RAN发起的寻呼消息或指示上层RRC层需要触发RRC连接继续过程，
    所述第三指示是第二指示的应答。
  5. 根据权利要求4所述的用户设备执行的网络连接方法，其中，
    如果所述寻呼消息或针对所述用户设备的PagingRecord字段中包含原因信息，则将所述原因信息指示给上层，
    NAS层可以基于所述原因信息向RRC层或针对第二网络的RRC层发送第三指示。
  6. 根据权利要求4所述的用户设备执行的网络连接方法，其中，
    在所述第三指示是所述第二指示的肯定应答的情况下，基于所述第三指示，RRC层针对第二网络发起RRC连接继续过程；
    在所述第三指示是所述第二指示的否定应答的情况下，基于所述第三指示，RRC层向第二网络发送RRC消息，所述RRC消息中包含用于指示用户设备繁忙、Tx(transmitter，发信机)和/或Rx(receiver，接收机)当前不可用或用户设备当前无法或不希望与网络建立或继续RRC连接等信息，使得用户设备或RRC层不与第二网络建立或继续RRC连接。
  7. 根据权利要求4所述的用户设备执行的网络连接方法，其中，
    RRC层能向上层即NAS层发送或指示第二指示之后启动第一定时器，或者在启动第一定时器之后向上层即NAS层发送或指示第二指示，
    如果RRC层接收到来自NAS层的第三指示时，则停止第一定时器，
    在所述第一定时器运行期间，所述用户设备或用户设备针对第二网络的RRC层接收到来自第二网络的RAN发起的寻呼消息时不指示给上层即NAS层。
  8. 一种用户设备执行的网络连接方法，该用户设备支持多USIM卡，所述用户设备处于RRC非激活态，所述用户设备执行的网络连接方法包括：
    如果满足第一条件和第二条件中的任一个条件，则用户设备的RRC层或针对第二网络的RRC层向上层即NAS层发送或指示第四指示；
    RRC层接收到来自上层即NAS层的第五指示；
    基于所述第五指示，RRC层向第二网络发起RRC连接继续过程、或者用户设备或用户设备的RRC层将RNA更新设置为待处理RNA过程，
    其中，
    所述第四指示用于RRC层向NAS层指示待处理的RNA更新过程或RRC层触发了RNA更新过程或RRC层触发了由RNA更新导致的RRC连接继续过程或者RRC层需要进行RRC连接继续过程，
    所述第五指示是第四指示的应答，
    所述第一条件为T380到期或因接收到SIB1而触发RNA更新，并且如果用户设备是支持多USIM卡的用户设备，
    所述第二条件为第一访问类型和第二访问类型的禁止被解除，并且上层没有请求RRC继续RRC连接，并且变量pendingRNA-Update的值被设置为真，并且用户设备是支持多USIM卡的用户设备。
  9. 根据权利要求8所述的用户设备执行的网络连接方法，其中，
    用户设备的RRC层或针对第二网络的RRC层在向上层即NAS层发送或指示第四指示之后启动第二定时器，或者用户设备的RRC层或针对第二网络的RRC层在启动第二定时器之后向上层即NAS层发送或指示第四指示，
    在RRC层接收到来自上层即NAS层的第五指示时，能停止第二定时器。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
PCT/CN2021/103980 2020-07-03 2021-07-01 用户设备执行的网络连接方法以及用户设备 WO2022002194A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010638133.7 2020-07-03
CN202010638133.7A CN113891458A (zh) 2020-07-03 2020-07-03 用户设备执行的网络连接方法以及用户设备

Publications (1)

Publication Number Publication Date
WO2022002194A1 true WO2022002194A1 (zh) 2022-01-06

Family

ID=79012016

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/103980 WO2022002194A1 (zh) 2020-07-03 2021-07-01 用户设备执行的网络连接方法以及用户设备

Country Status (2)

Country Link
CN (1) CN113891458A (zh)
WO (1) WO2022002194A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110214462A (zh) * 2019-04-25 2019-09-06 北京小米移动软件有限公司 寻呼响应方法和装置，寻呼方法和装置
US20200053818A1 (en) * 2018-08-10 2020-02-13 Nokia Technologies Oy Combined rrc inactive resume, rrc rna & nas registration procedure
US10623946B1 (en) * 2019-03-25 2020-04-14 Qualcomm Incorporated Multi-SIM assistance information
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200053818A1 (en) * 2018-08-10 2020-02-13 Nokia Technologies Oy Combined rrc inactive resume, rrc rna & nas registration procedure
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备
US10623946B1 (en) * 2019-03-25 2020-04-14 Qualcomm Incorporated Multi-SIM assistance information
CN110214462A (zh) * 2019-04-25 2019-09-06 北京小米移动软件有限公司 寻呼响应方法和装置，寻呼方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SONY: "Solution: Busy Indication as a paging response", 3GPP DRAFT; S2-1909466 BUSY INDICATOR AS A PAGING RESPONSE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Split, Kr; 20191014 - 20191018, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051795568 *
VIVO, CHINA TELECOM, CHINA UNICOM: "New WID: Support for Multi-SIM devices in Rel-17", 3GPP DRAFT; RP-193263, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Sitges, Spain; 20191209 - 20191212, 12 December 2019 (2019-12-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051840392 *

Also Published As

Publication number Publication date
CN113891458A (zh) 2022-01-04

Similar Documents

Publication Publication Date Title
US11641689B2 (en) Radio resource control resume without context fetch
US9107190B2 (en) Discontinuous reception for multi-component carrier system
AU2019218060B2 (en) Communication method and wireless communication device
JP2019536358A (ja) データ送信／受信装置、方法及び通信システム
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
TW201822561A (zh) 非連續接收的方法和裝置
WO2022117007A1 (zh) 用户设备的连接方法以及用户设备
TW201914350A (zh) 用於尋呼的方法、存取網路設備、終端設備和核心網路設備
WO2022002194A1 (zh) 用户设备执行的网络连接方法以及用户设备
WO2019136676A1 (zh) 在部分带宽上进行半静态调度的装置及方法
WO2022017461A1 (zh) 用户设备、基站及其方法
WO2023104142A1 (zh) 由用户设备执行的方法以及用户设备
JP5466270B2 (ja) 移動通信システムにおける基地局及び制御方法
WO2022194194A1 (zh) 在多个网络连接之间切换网络连接的方法及用户设备
WO2023098668A1 (zh) 用户设备及其方法
WO2023125687A1 (zh) 由用户设备执行的方法及用户设备
WO2022199479A1 (zh) 用户设备及其执行方法
WO2023098654A1 (zh) 用户设备、基站及其方法
WO2021254374A1 (zh) 用户设备及其方法、基站及其方法
WO2023185689A1 (zh) 由用户设备执行的方法以及用户设备
WO2022127864A1 (zh) 用户设备的连接方法以及用户设备
US20230337325A1 (en) Communication method and communication apparatus
WO2024008069A1 (zh) 由用户设备执行的方法以及用户设备
CN110326325B (zh) 数据传输的方法、终端设备和网络设备
CN115604864A (zh) 用于释放rrc连接的方法和用户设备

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

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

Country of ref document: EP

Kind code of ref document: A1