System information acquisition and paging for user equipment with multiple universal subscriber identity modules

Abstract

This invention discloses a radio device that communicates with a first network and a second network, and has a first connection to the first network. The radio device can receive paging from the second network and determine whether to establish a second connection with the second network, then notify the first network of this selection. The first network can then notify the device to release or suspend the first connection. The device can send release and / or suspension preferences to the first network, such as preferences for processing in idle or inactive modes, paging preferences, and a preferred identifier for the device. The device can then establish the second connection and, for example, monitor paging from the first network during a given paging timing and paging frame.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 943,896, filed December 5, 2019, entitled “System Information Acquisition and Paging for User Equipment with Multiple Universal Subscriber Identity Modules”, and U.S. Provisional Patent Application No. 63 / 061,414, filed August 5, 2020, entitled “SI Acquisition And Paging For Multi-USIM UEs”, the contents of which are incorporated herein by reference. Background Technology

[0003] This disclosure relates to networks, including wireless networks, such as, but not limited to, those networks described by the following criteria:

[0004] • 3GPP TS 38.213, Physical layer procedures for control (Release 15), V15.7.0;

[0005] • 3GPP TS 38.331, Radio Resource Control (RRC) Protocol Specification (Release 15), V15.7.0;

[0006] • 3GPP TS23.501, System Architecture of 5G Systems; Phase 2 (Release 15), V15.6.0;

[0007] • 3GPP TS 38.212, NR; Multiplexing and Channel Coding (Release 15), V15.6.0;

[0008] • 3GPP TS 38.214, NR; Physical layer procedures for data (Release 15), V15.7.0;

[0009] • 3GPP TS 38.304, User Equipment (UE) in Idle Mode and RRC Inactive State

[0010] Procedure (Release 15), V15.4.0;

[0011] • 3GPP TS 38.213, Physical layer procedures for control (Release 16), V16.1.0;

[0012] • 3GPP TS 38.331, Radio Resource Control (RRC) Protocol Specification (Release 16), V16.0.0;

[0013] • 3GPP TS23.501, System Architecture for 5G Systems; Phase 2 (Release 16), V16.4.0

[0014] • 3GPP TS 38.212, NR; Multiplexing and Channel Coding (Release 16), V16.1.0;

[0015] • 3GPP TS 38.214, NR; Physical layer procedures for data (Release 16), V16.1.0;

[0016] • 3GPP TS 38.304, User Equipment (UE) Procedures in Idle Mode and RRC Inactive State (Release16), V16.0.0;

[0017] • 3GPP TS 38.300, NR; General description of NR and NG-RAN; Phase 2 (Release 15), V15.7.0; and

[0018] • 3GPP TS 38.300, NR; General description of NR and NG-RAN; Phase 2 (Release 16), V16.1.0. Summary of the Invention

[0019] The UE behavior and configuration of a UE with multiple USIMs can be adapted such that the monitoring and transmission opportunities associated with an AS procedure performed by one USIM do not overlap in time with the monitoring and transmission opportunities associated with an AS procedure performed by another USIM. The term "AS procedure" in this document refers to a superset of all UE procedures (including NAS procedures) that enable the UE to interact with the network; in this sense, any such procedure requires the use of an AS procedure. The UE can use various methods, such as:

[0020] A method for determining when a conflict will occur based on the UE configuration for multiple USIMs and the SFTD between the PCells of the multiple USIM UEs;

[0021] A method to skip PO to avoid paging conflicts between multiple USIM UEs;

[0022] The rule-based PO skipping method allows the UE to rotate monitoring of its PO's USIM;

[0023] The event-based PO method allows the UE to suspend / resume paging to the network based on the occurrence of a specific event;

[0024] The PO skipping method based on SFN divides the SFN space into regions for monitoring or skipping POs;

[0025] The method of extending the PO by utilizing the additional PDCCH monitoring timing of paging reduces the possibility that the UE will not be able to receive DL due to collisions during its configured PO period;

[0026] A method for UEs to request modifications to their paging configuration to avoid conflicts;

[0027] A method for a UE to request the release or suspension of an RRC connection to a USIM to prevent conflicts with monitoring timing and transmission opportunities associated with an AS procedure performed against another USIM;

[0028] A method for a UE to autonomously release or suspend an RRC connection to a USIM to prevent conflicts with monitoring and transmission opportunities associated with an AS procedure performed against another USIM, wherein the UE can “negotiate” the release / suspension of the configuration to be applied after autonomously releasing / suspending the RRC connection.

[0029] A method for a UE to request modification of the C-DRX configuration of a USIM to prevent conflicts with monitoring timing and transmission opportunities associated with an AS procedure performed by another USIM; and

[0030] A method for providing instructions to the network to inform the network of changes in its DC capabilities resulting from a UE using a shared transceiver to maintain a connection with another network.

[0031] Method for providing multi-USIM auxiliary information to the network during the process of UE using enhanced UE auxiliary information.

[0032] A method for a UE to request the network to stop paging the UE, wherein the request is sent to the network in response to paging; and

[0033] A method for performing paging filtering on the network, wherein the filtering may be based on a list of paging reasons provided to the network by the UE.

[0034] UE can use several methods to perform conflict resolution and recovery, such as:

[0035] Methods for resolving conflicts based on pre-configured rules and / or user preferences;

[0036] A method for performing RACH-based SI acquisition to recover from conflicts with the SI window;

[0037] A method to perform SMS retrieval to recover from a conflict with the PO;

[0038] Perform on-demand paging to recover from conflicts with the PO.

[0039] Network operations can be adapted for UEs with multiple USIMs to allow the release or suspension of an RRC connection with a first network, enabling the UE to establish an RRC connection with a second network. Various techniques can be used. For example, the device can be configured to communicate with the first network and then receive a trigger to establish an RRC connection with the second network. The UE can then transmit an RRC message to the first network to release or suspend the RRC connection with that network. Next, the UE can receive an RRCRelease message to release or suspend the RRC connection with the first network, and then, after doing so, establish an RRC connection with the second network.

[0040] The release or pause request sent from the UE may correspond to the transmission of a UE auxiliary information message related to release preference information, wherein, for example, the preferred RRC state is set to "idle" or "inactive". The UE auxiliary information message may also include an indication of paging preferences.

[0041] The UE can also send a Release Assistance Information (RAI) to the first network and receive a "negotiated" configuration from the first network, thereby releasing or suspending the RRC connection with the first network, including applying the negotiated configuration. The RAI can be sent alone or together with other UE assistance information, such as paging preference information and / or preferred RRC status.

[0042] The negotiated configuration may include a pause configuration with an inactivity time value, and applying this configuration may include starting a timer accordingly. When the timer expires, the UE may release the paused RRC connection with the first network.

[0043] Similarly, the UE can receive a trigger to release or suspend the RRC connection with the second network, stop the inactive timer, and resume the RRC connection with the first network.

[0044] The behavior and configuration of multiple USIMUEs can be adapted so that the monitoring and transmission opportunities associated with an AS procedure performed by one USIM do not overlap in time with the monitoring and transmission opportunities associated with an AS procedure performed by another USIM. For example, a device can be configured to detect an event triggering PO skip activation with the network and transmit an RRC message to activate PO skip with that network. The device can then receive an RRC release message from the network including a pause configuration, suspend the RRC connection with the network, and activate PO skip with the network. Subsequently, the device can detect events triggering PO skip activation with the network and deactivating PO skip with the network.

[0045] The device can be adapted to cause the event-triggered PO to skip activation corresponding to multiple events, such as: determining that a conflict will occur based on the UE configuration for multiple USIMs; detecting one or more paging conflicts; initiating an AS procedure for another USIM; transitioning to the RRC_CONNECTED state for another USIM; transitioning to the RRC_INACTIVE state for another USIM; transitioning to the RRC_IDLE state for another USIM; or configuring a DC for another USIM.

[0046] Requests to skip activation PO from the device can include, for example, a resumption reason set to "po-SkippingActivation".

[0047] For example, the event that triggers the PO to skip activation could be the completion of the AS process of another USIM, the transition of another USIM from RRC_CONNECTED to RRC_IDLE / RRC_INACTIVE, or the release of the DC of another USIM.

[0048] The pause command can correspond to the PO skipping the activation period to trigger a timer start, where the timer start value is sent via a pause configuration signal. The event that triggers the PO to skip activation can be the timer expiring.

[0049] Extended POs can be used to perform paging monitoring. For example, a device can be configured to receive paging configuration in an RRC message that includes an indication of multiple PDCCH monitoring times for paging, and select a non-conflicting PDCCH monitoring time for paging. The device can then monitor paging during the selected PDCCH monitoring time for paging and receive paging during the monitored PDCCH monitoring time for paging.

[0050] The device can be further adapted to send multiple USIM auxiliary information to the network and receive paging configurations via RRC messages that include paging configurations. For example, the device can receive an RRC message that configures an extended PO using, for example, an additionalMonitoringOccasionOfPO parameter with a value greater than 1.

[0051] The device can be configured to send a request to the network to stop paging of the UE. For example, the first device can be configured to communicate with a second device in a first network and receive paging from a third device in the second network. The first device can determine to continue communicating with the second device in the first network and transmit an RRC message to the third device in the second network, the RRC message having an indication to suspend paging of the first device. The first device can then receive an RRC message from the third device in the second network, the RRC message confirming the indication to suspend paging, and continue communicating with the second device in the first network.

[0052] The first device can further determine whether to continue communicating with the second device in the first network based on the "paging reason" received in the paging.

[0053] These operations can occur when the first device is in RRC_INACTIVE mode, where the third device sends a NAS message to a fourth device in the second network, the NAS message including an instruction to suspend paging of the first device. For example, the first device can be a UE, the second and third devices can be gNBs, and the fourth device can be an AMF.

[0054] The first device can be further adapted to resume paging with the second network and transmit an RRC message to a third device, the RRC message including an instruction to resume paging of the first device. The first device can then receive an RRC message from the third device in the second network, the RRC message confirming the instruction to resume paging, and monitor paging from the third device in the second network.

[0055] The purpose of providing this summary is to introduce selected concepts in a simplified form, which are further described in the following detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to addressing any or all of the shortcomings pointed out in any part of this disclosure. Attached Figure Description

[0056] A more detailed understanding can be obtained from the following description, which is given by way of example in conjunction with the accompanying drawings.

[0057] Figure 1 This is a call flow diagram demonstrating the information supply of a sample system.

[0058] Figure 2 This is a timing diagram showing an example SFTD between PCells of multiple USIM UEs.

[0059] Figures 3A-3B It is a timing diagram showing the configuration of multiple USIMs with and without paging conflicts.

[0060] Figures 4A-4D This is a timing diagram illustrating example paging conflicts for various DRX cycle configurations.

[0061] Figure 5 It is a timing diagram showing paging conflicts with C-DRX enabled duration.

[0062] Figure 6 This is a timing diagram of a paging repetition example.

[0063] Figure 7 This is a flowchart of an example algorithm for performing PO skipping every other PO.

[0064] Figure 8 It is a timing diagram showing the PO skipping every other PO.

[0065] Figures 9A-9B It is a timing diagram showing the skipping of PO every other PO when T2 = 2T1.

[0066] Figure 10 This is a flowchart of an example algorithm for performing PO skipping every other PO that supports USIMs with different DRX periods.

[0067] Figure 11 This is a call flow diagram showing an example configuration that the PO skips during the registration process.

[0068] Figure 12 This is a call flow diagram showing an example configuration where the PO skips during the RRC connection restoration process.

[0069] Figure 13 This is a call flowchart in which the UE auxiliary information process informs the network of the expected PO skip configuration.

[0070] Figures 14A-14B It is a sequence diagram showing that the PO skips scenes that occur continuously for variable duration and fixed duration, respectively.

[0071] Figures 15A-15B An example call flow is shown that uses RRC signaling and has an event-based PO skipping with variable duration.

[0072] Figures 16A-16B An example call flow is shown that uses RRC signaling and has a fixed duration for event-based PO skipping.

[0073] Figure 17 This is an example call flow demonstrating event-based PO skipping using NAS signaling with both variable and fixed durations.

[0074] Figure 18This is a timing diagram of an example of SFN-based paging PO skipping.

[0075] Figure 19 This is a timing diagram of an example of SFN-based PO skipping with multiple PO monitoring areas.

[0076] Figure 20 An example of a PO extended by utilizing the additional PDCCH monitoring timing is shown.

[0077] Figure 21 This demonstrates the call flow for a specific PO extension scheme in a sample cell.

[0078] Figure 22 This demonstrates the call flow for a specific PO extension scheme for a sample UE.

[0079] Figure 23 This is a timing diagram for an example paging conflict scenario (where NS > 1) used for multiple USIM UEs.

[0080] Figure 24 This is a signaling diagram illustrating an example paging modification request from a multi-USIM UE attached to two network operating systems, NW1 and NW2.

[0081] Figure 25 This is a call flowchart for an example RRC release / pause request.

[0082] Figure 26 This is an example call flow for the autonomous release / pause of a network RRC connection.

[0083] Figure 27 This is a call flow for an example UE request to stop paging.

[0084] Figure 28 This is a call flow request from an example UE that has paging filtering enabled.

[0085] Figure 29 This is a flowchart of an example algorithm for performing conflict resolution.

[0086] Figure 30 This is a time sequence diagram of an example time period for modification.

[0087] Figure 31 This is a sample user interface that can be used to configure the UE for MUSIM operation.

[0088] Figure 32 This is a sample notification that can be used to inform users that a call needs to be established for a given USIM.

[0089] Figure 33A An example communication system is shown, in which the methods and apparatus described and claimed herein can be specifically embodied.

[0090] Figure 33B This is a block diagram of an example device or apparatus configured for wireless communication.

[0091] Figure 33C This is a system diagram of an exemplary radio access network (RAN) and core network.

[0092] Figure 33D This is another exemplary system diagram of the RAN and core network.

[0093] Figure 33E This is another exemplary system diagram of the RAN and core network.

[0094] Figure 33F This is a block diagram of an exemplary computing system.

[0095] Figure 33G This is a block diagram of another exemplary communication system. Detailed Implementation

[0096] Table 9 in the appendix describes many of the abbreviations used in this article.

[0097] Multiple USIM Overview

[0098] A multi-USIM UE is a UE with two or more SIMs. A dual-SIM UE is a UE with two SIMs. The terms multi-USIM and dual-SIM are used interchangeably in this document.

[0099] Multi-USIM devices are becoming increasingly popular in various countries. Users can have both private and business subscriptions on one device, or two private subscriptions for different services on one device (e.g., using a personal subscription and a "family circle" plan). However, support for multiple USIMs within a device is currently handled in an implementation-specific manner without any support from 3GPP specifications, resulting in a variety of implementations and UE behaviors (e.g., passive dual SIM, dual SIM single standby, dual SIM dual standby, dual SIM dual activity, etc.). Such scenarios can lead to increased complexity for UE vendors, undesirable UE behavior from network vendors or operators, and a degraded user experience.

[0100] Current UE implementations typically support dual-SIM configurations, where the UE time-multiplexes operation between each installed USIM; this is known as TDM-ing or Time Division Multiplexing. Dual-SIM Dual-Standby (DSDS) UEs operate in this manner when called and allocate time for each USIM to communicate with their respective mobile network operator or MNO. These USIMs can belong to the same or different MNOs. These multi-USIM UEs share common radio and baseband components with some common software to enable the UE to switch operation between the two USIMs. A major problem with shared Rx and Tx components is that the UE cannot simultaneously monitor DL ​​services or transmit UL services for two USIMs.

[0101] Some dual-SIM UEs have dual Rx components (one for each USIM) and a shared single Tx component, where the dual-SIM UE performs time-division multiplexing of UL transmissions. With dual Rx components, these UEs can continuously monitor DL ​​traffic, but due to the shared Tx component, the UE still must perform time-division multiplexing of UL traffic. Because the additional Rx component increases cost, these UEs are not as common as single-Rx, single-Tx UEs.

[0102] Another type of multi-USIM UE has a dedicated transceiver available for each installed USIM. These UEs are called Dual SIM Dual Active (DSDA) UEs, but they are less common due to the increased cost of having dual Rx and dual Tx components in the UE. DSDA UEs operate as two UEs, but include some common software to provide operational configurability to the user.

[0103] NR Paging (Release 15)

[0104] Discontinuous Reception for Paging

[0105] The UE can use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The UE monitors one paging opportunity (PO) per DRX cycle. A PO is a set of PDCCH monitoring opportunities and can consist of multiple time slots (e.g., subframes or OFDM symbols) in which paging DCIs can be transmitted. See 3GPP TS 38.213, Physical Layer Procedures for Control (Release 15), V15.7.0. A paging frame (PF) is a radio frame and can contain one or more POs or the start point of a PO.

[0106] In multi-beam operation, the UE assumes that the same paging message and the same short message are repeated in all transmitted beams. Therefore, the selection of the beam used to receive paging messages and short messages depends on the specific UE implementation. For RAN-initiated paging and CN-initiated paging, the paging message is the same.

[0107] When the UE receives a paging message from the RAN, it initiates an RRC connection recovery procedure. If the UE receives a paging message from the CN while in the RRC_INACTIVE state, the UE moves to RRC_IDLE and informs the NAS.

[0108] The paging PF and PO are determined by the following formula:

[0109] The SFN of PF is determined by the following formula:

[0110] (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N)

[0111] The exponent (i_s) (indicating the exponent of PO) is determined by the following formula:

[0112] i_s = floor(UE_ID / N) mod Ns

[0113] The timing of PDCCH monitoring for paging is determined according to the μagingSearchSpace as specified in 3GPP TS 38.213 Release 15, and if configured as specified in 3GPP TS 38.331 Release 15, Radio Resource Control (RRC) Protocol Specification (Release 15), V15.7.0, it is determined according to firstPDCCH-MonitoringOccasionOfPO. When SearchSpaceId=0 is configured for pagingSearchSpace, the timing of PDCCH monitoring for paging is the same as that for RMSI as defined in Clause 13 of TS 38.213.

[0114] When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO starting from the first PDCCH monitoring moment in the PF for paging. For Ns=2, the PO is located in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0115] When a SearchSpaceId other than 0 is configured for pagingSearchSpace, the UE monitors the (i_s+1)th PO. A PO is a set of "S" consecutive PDCCH monitoring opportunities, where "S" is the number of actual SSBs transmitted according to ssb-PositionsInBurst in SIB1. The Kth PDCCH monitoring opportunity for paging in a PO corresponds to the SSB of the Kth transmission. PDCCH monitoring opportunities for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially from zero, starting from the first PDCCH monitoring opportunity for paging in the PF. When firstPDCCH-MonitoringOccasionOfPO exists, the starting PDCCH monitoring opportunity number for the (i_s+1)th PO is the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S.

[0116] Note 1: The PO associated with the PF can start in the PF or after the PF.

[0117] Note 2: The PDCCH monitoring timing for the PO can span multiple radio frames. When a SearchSpaceId other than 0 is configured for the paging-SearchSpace, the PDCCH monitoring timing for the PO can span multiple periods of the paging search space.

[0118] The following parameters are used to calculate PF and i_s above:

[0119] T: The UE's DRX period (if configured by RRC and / or upper layers, T is determined by the shortest DRX value among the UE-specific DRX values ​​and the default DRX value broadcast in the system information. If the UE-specific DRX is not configured by RRC or upper layers, the default value is applied).

[0120] N: Total paging frames in T

[0121] Ns: Paging timing number for PF

[0122] PF_offset: The offset used to determine PF.

[0123] UE_ID: 5G-S-TMSI mod 1024

[0124] The parameters Ns, nAndPagingFrameOffset, and the length of the default DRX period are signaled in SIB1. The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in TS 38.331 Release 15. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DLBWP. For paging in a DL BWP other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0125] If the UE does not have 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE should use UE_ID=0 as the default identity in PF and i_s in the above formula.

[0126] 5G-S-TMSI is a 48-bit string, such as in 3GPP TS 23.501, the system architecture of the 5G system; Phase 2 (Release 15), V15.6.0. 5G-S-TMSI in the above formula should be interpreted as a binary number, where the leftmost bit represents the most significant bit.

[0127] Paging DCI

[0128] The following information is transmitted via DCI format 1_0 with a CRC scrambled by P-RNTI. See Table 1, Paging DCI (Release 15), in the appendix, and Table 2, Short Message Indicator (Release 15), in the appendix. See also 3GPP TS38.212, NR; Multiplexing and Channel Coding (Release 15), V15.6.0.

[0129] PCCH-Config

[0130] The IE DownlinkConfigCommonSIB provides the common downlink parameters for the cell. This IE includes the PCCH-Config field used to provide DRX configuration for the cell. See 3GPP TS 38.331 Release 15, and Code Example 1A - PCCH-Config Field (Release 15) and Code Example 1B - PCCH-Config Field Description (Release 15) in the appendix to this document.

[0131] NR Paging (Release 16)

[0132] Discontinuous Reception for Paging

[0133] The UE can use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The UE monitors one paging opportunity (PO) per DRX cycle. A PO is a set of PDCCH monitoring opportunities and can consist of multiple time slots (e.g., subframes or OFDM symbols) in which paging DCIs can be transmitted (see TS 38.213 Release 16). A paging frame (PF) is a radio frame and can contain one or more POs or the start point of a PO.

[0134] In multi-beam operation, the UE assumes that the same paging message and the same short message are repeated in all transmitted beams. Therefore, the selection of the beam used to receive paging messages and short messages depends on the specific UE implementation. For RAN-initiated paging and CN-initiated paging, the paging message is the same.

[0135] When the UE receives a paging message from the RAN, it initiates an RRC connection recovery procedure. If the UE receives a paging message from the CN while in the RRC_INACTIVE state, the UE moves to RRC_IDLE and informs the NAS.

[0136] The paging PF and PO are determined by the following formula:

[0137] The SFN of PF is determined by the following formula:

[0138] (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N)

[0139] The exponent (i_s) (indicating the exponent of PO) is determined by the following formula:

[0140] i_s = floor(UE_ID / N) mod Ns

[0141] The timing of PDCCH monitoring for paging is determined according to the pagingSearchSpace as specified in TS 38.213 Release 16, and if configured as specified in TS 38.331 Release 16, according to firstPDCCH-MonitoringOccasionOffPO and nrofPDCCH-MonitoringOccasionPerSSB-InPO. When SearchSpaceId=0 is configured for pagingSearchSpace, the timing of PDCCH monitoring for paging is the same as that for RMSI as defined in Clause 13 of TS 38.213 Release 16.

[0142] When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO starting from the first PDCCH monitoring moment in the PF for paging. For Ns=2, the PO is located in the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0143] When a SearchSpaceId other than 0 is configured for pagingSearchSpace, the UE monitors the (i_s+1)th PO. A PO is a set of “S*X” consecutive PDCCH monitoring opportunities, where “S” is the number of actual SSBs transmitted according to ssb-PositionsInBurst in SIB1, and X is nrofpDCCH-MonitoringOccasionPerSSB-InPO (if configured), otherwise equal to 1. The [x*S+K]th PDCCH monitoring opportunity in the PO used for paging corresponds to the Kth transmitted SSB, where x = 0, 1, ..., X-1, K = 1, 2, ..., S. PDCCH monitoring opportunities for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially from zero, starting from the first PDCCH monitoring opportunity for paging in the PF. When `firstPDCCH-MonitoringOccasionOfPO` exists, the initial PDCCH monitoring time of the (i_s+1)th PO is the (i_s+1)th value of the `firstPDCCH-MonitoringOccasionOfPO` parameter; otherwise, it is equal to `i_s*S*X`. If X > 1, then when the UE detects a PDCCH transmission addressing a P-RNTI within its PO, the UE does not need to monitor subsequent PDCCH monitoring times for that PO. A PO associated with a PF can begin within or after the PF. The PDCCH monitoring time of a PO can span multiple radio frames.

[0144] When a SearchSpaceId other than 0 is configured for paging-SearchSpace, the PDCCH monitoring timing for PO can span multiple time periods in the paging search space. Parameters T, N, Ns, PF_offset, and UE_ID are used to calculate the PF and i_s mentioned above.

[0145] T relates to the UE's DRX cycle. If configured by RRC and / or higher layers, T is determined by the shortest DRX value among the UE-specific DRX values ​​and the default DRX value broadcast in the system information. In the RRC_IDLE state, if the UE-specific DRX is not configured by higher layers, the default value is applied.

[0146] N is the total number of paging frames in T.

[0147] Ns is the paging timing number of PF.

[0148] PF_offset is the offset used to determine PF.

[0149] The UE_ID is 5G-S-TMSI mod 1024.

[0150] The parameters Ns, nAndPagingFrameOffset, nrofPDCCH-MonitoringOccasionPerSSB-InPO, and the length of the default DRX cycle are signaled in SIB1. The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in TS 38.331 Release 16. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0151] If the UE does not have 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE should use UE_ID=0 as the default identity in PF and i_s in the above formula.

[0152] 5G-S-TMSI is a 48-bit bit string, as defined in TS23.501 Release 16. 5G-S-TMSI in the above formula should be interpreted as a binary number, where the leftmost bit represents the most significant bit.

[0153] Paging DCI

[0154] Table 3 of the appendix, Paging DCI (Release 16), describes the information that can be transmitted via DCI format 1_0 with a CRC scrambled by P-RNTI. See also Table 4 of the appendix, Short Message Indicators (Release 16), and 3GPP TS 38.212, Release 16.

[0155] PCCH-Config

[0156] The IE DownlinkConfigCommonSIB provides the cell's common downlink parameters. This IE includes the PCCH-Config field used to provide DRX configuration for the cell. See 3GPP TS 38.331 Release 16. See Code Example 2A - PCCH-Config field (Release 16) and Code Example 2B - PCCH Config field description (Release 16) in the appendix.

[0157] Short Message

[0158] Short messages can be transmitted on the PDCCH using the short message field of DCI format 1_0, with or without an associated paging message, via P-RNTI. Table 5 in the appendix describes short messages in 3GPP TS 38.331 Release 16, where bit 1 is the most significant bit.

[0159] System Information Handling

[0160] System information (SI) consists of a MIB and multiple SIBs, which are divided into a minimum SI and other SIs:

[0161] The minimum SI includes the basic information required for initial access and the information used to obtain any other SIs. The minimum SI consists of the following items:

[0162] The MIB contains cell prohibition status information and basic physical layer information of the cell required to receive additional system information (e.g., CORESET#0 configuration). The MIB is broadcast periodically on the BCH.

[0163] οSIB1 defines the scheduling of other system information blocks and contains the information required for initial access. SIB1 is also known as the Remaining Minimum SI (RMSI) and is periodically broadcast on the DL-SCH, or sent in a dedicated manner on the DL-SCH to the UE in the RRC_CONNECTED state.

[0164] • Other SIs encompass all SIBs not broadcast in the minimum SI. These SIBs may be broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (e.g., upon request from a UE in the RRC_IDLE or RRC_INACTIVE state), or sent in a dedicated manner on the DL-SCH to a UE in the RRC_CONNECTED state. Other SIs consist of the following:

[0165] οSIB2 contains cell reselection information primarily related to the serving cell;

[0166] οSIB3 contains information about the serving frequency and neighboring cells within the frequency that are related to cell reselection (including frequency-shared cell reselection parameters and cell-specific reselection parameters);

[0167] οSIB4 contains information about other NR frequencies and inter-frequency adjacent cells related to cell reselection (including frequency-shared cell reselection parameters and cell-specific reselection parameters);

[0168] oSIB5 contains information about E-UTRA frequencies and E-UTRA neighboring cells related to cell reselection (including frequency-shared cell reselection parameters and cell-specific reselection parameters);

[0169] οSIB6 contains ETWS main notifications;

[0170] οSIB7 includes ETWS auxiliary notifications;

[0171] οSIB8 includes CMAS warning notifications;

[0172] οSIB9 contains information related to GPS time and Coordinated Universal Time (UTC).

[0173] Figure 1 An example of system information provision is shown. For a cell / frequency that the UE considers for camping, the UE does not need to obtain the minimum SI content of that cell / frequency from another cell / frequency layer. This does not preclude the UE from applying stored SIs from previously visited cells.

[0174] If the UE cannot determine the full content of the minimum SI of a cell by receiving data from the cell, the UE should consider the cell as prohibited.

[0175] In the case of BA, the UE only obtains the SI on the active BWP.

[0176] Scheduling

[0177] The MIB is mapped onto the BCCH and carried on the BCH, while all other SI messages are mapped onto the BCCH, with all other SI messages dynamically carried on the DL-SCH. The scheduling of the SI message portions of other SIs is indicated by SIB1.

[0178] For UEs in the RRC_IDLE and RRC_INACTIVE states, requests for other SIs trigger a random access procedure, where MSG3 includes an SI request message unless the requested SI is associated with a subset of PRACH resources, in which case MSG1 is used to indicate the other requested SIs. When using MSG1, the smallest granularity of the request is a single SI message (e.g., a set of SIBs), and one RACH preamble and / or PRACH resources can be used to request multiple SI messages, with the gNB acknowledging the request in MSG2. When using MSG3, the gNB acknowledges the request in MSG4.

[0179] Other SIs can be broadcast periodically and for a specific duration. Other SIs can also be broadcast when a UE in the RRC_IDLE / RRC_INACTIVE state requests them.

[0180] For a UE to be allowed to camp on a cell, it must have already obtained the minimum SI from that cell. There may be cells in the system that do not broadcast the minimum SI, therefore the UE cannot camp on these cells.

[0181] SI Modification

[0182] Changes to system information (excluding ETWS / CMAS system information) occur only within specific radio frames, for example, using the concept of a modification period. System information can be transmitted multiple times with the same content within a modification period, as defined by its schedule. The modification period is configured by the system information.

[0183] When the network changes (some) system information, it first notifies the UE about the change; for example, this can be done over the entire modification period. In the next modification period, the network transmits the updated system information. Upon receiving the change notification, the UE obtains the new system information from the beginning of the next modification period. The UE applies the previously obtained system information until it obtains the new system information. See 3GPP TS 38.300, NR; General description of NR and NG-RAN; Phase 2 (Release 15), V15.7.0.

[0184] Public Warning System

[0185] The NR connected to the 5GC supports the Public Warning System (PWS) via system information broadcasting capabilities. The NR is responsible for scheduling and broadcasting warning messages and paging UEs to provide indication that a warning message is being broadcast.

[0186] Earthquake and Tsunami Warning System: ETWS is a public warning system developed to meet regulatory requirements for warning notifications related to earthquakes and / or tsunamis. ETWS warning notifications can be primary notifications (short notifications) or secondary notifications (providing detailed information).

[0187] Commercial Mobile Alert System (CMAS): CMAS is a public alert system developed for delivering multiple concurrent alert notifications.

[0188] Different SIBs are defined for ETWS primary notifications, ETWS secondary notifications, and CMAS notifications. Paging is used to inform the UE about ETWS and CMAS indications. The UE monitors ETWS / CMAS indications during its own paging times for RRC_IDLE and RRC_INACTIVE. The UE monitors ETWS / CMAS indications during any paging time for RRC Connected. Paging indicating ETWS / CMAS notifications triggers the acquisition of system information (without delay to the next modification period). See TS 38.300 Release 15.

[0189] UE Assistance Information

[0190] When configured to do so, the UE can signal to the network via UEAssistanceInformation. For example, to delay budget reporting, the UE can signal that it prefers adjusting the DRX cycle length in connected mode, or that it is experiencing internal overheating. To save power, the UE can signal that it prefers certain DRX parameter values, and / or reduces the maximum number of secondary component carriers, and / or reduces the maximum aggregation bandwidth, and / or reduces the maximum number of MIMO layers, and / or minimizes scheduling offsets K0 and K2. The UE can signal that it does not expect to send or receive any more data in the near future, and in this case, it can provide its preference for transitioning from RRC_CONNECTED to another state, where the indication can express its preferred RRC state, or alternatively, it can cancel a previously indicated preference for transitioning from RRC_CONNECTED to another state. The UE can signal a list of frequencies affected by IDC issues. See TS 38.300 Release 16.

[0191] The UE can express its preference for temporarily reducing the maximum number of secondary component carriers, the maximum aggregation bandwidth, and the maximum number of MIMO layers. The gNB determines whether to comply with the request.

[0192] For sidelinks, the UE can report the SL service mode of periodic services to the NG-RAN.

[0193] Example Challenges

[0194] For cost-efficiency reasons, multi-USIM UEs typically use shared common radio and baseband components across multiple USIMs. Time-division multiplexing (TDM) of these shared components can be used to maintain connectivity with multiple network devices (NWs). However, when AS procedures for multiple USIMs need to be executed simultaneously, "conflicts" can occur, potentially leading to delays, suboptimal execution, or even failure of the AS procedures. In this paper, we consider the impact of such "conflicts" on AS procedures performed by UEs in RRC_IDLE / RRC_INACTIVE modes and propose solutions to resolve these conflicts.

[0195] For example, to maintain connectivity with the NW, a UE in the RRC_IDLE / RRC_INACTIVE state needs to perform SI acquisition and paging procedures. When performing these procedures, the UE monitors the downlink at specific times to receive SI or paging DCI. In multi-beam operation, a set of PDCCH monitoring times is used for SI acquisition and paging reception. One or more PDCCH monitoring times in this set may conflict; for example, partially or completely. When a conflict occurs, the UE will be unable to receive downlink during one or more of these PDCCH monitoring times, which may result in the UE being unable to acquire SI or receive paging DCI.

[0196] Regarding SI acquisition, conflicts can increase the latency associated with obtaining an SI. UEs that cannot perform the SI acquisition process quickly and reliably may be unable to establish / restore an RRC connection when triggered due to an invalid SI. Depending on the event that triggers the process, delaying the RRC connection / restore process until a valid SI is obtained may be unacceptable. Another potential impact is the selection of a suboptimal cell when performing a cell (re)selection procedure. If a UE cannot acquire the MIB or SIB1 of a candidate cell during a cell reselection evaluation procedure, the UE may mistakenly believe that the cell is "banned" for up to 300 seconds. This may lead to the selection of a weaker cell, potentially requiring the UE to continue performing the cell reselection evaluation procedure; or the selection of a cell where the UE can only obtain limited service; for example, initiating an emergency call and receiving ETWS and CMAS notifications.

[0197] Regarding paging, collisions can cause UEs to miss Mobile Termination (MT) calls. This can lead the NW to incorrectly assume a fault has occurred, resulting in unnecessary corrective actions and distortion of call statistics maintained by the NW. For example, the NW might attempt to page the UE in a wider area, increasing signaling load. Furthermore, if subsequent paging attempts also fail, the state machine maintained by the NW may transition to a different state, leading to a state machine mismatch between the UE and the NW. Additionally, since PWS notifications and SI change indications are signaled in short messages transmitted via paging DCI, UEs that cannot monitor paging may miss important ETWS or CMAS messages if they miss a PWS notification; or they may be unaware of SI changes if they miss an SI change indication.

[0198] Conflicts can be isolated or systemic in nature. For example, in a scenario where two USIMs are in RRC_IDLE / RRC_INACTIVE mode, a conflict with the timing of PDCCH monitoring used for SI acquisition can be considered isolated because the event triggering the SI acquisition process is non-periodic and will not persist for an extended period; for example, during cell (re)selection, upon receiving a PWS notification or SI change indication, etc. Scenarios where such conflicts may occur include: when attempting to perform SI acquisition processes for multiple USIMs simultaneously, when attempting to perform an SI acquisition process for one USIM and an idle mode measurement for another USIM, or when attempting to perform an SI acquisition for one USIM and a paging process for another USIM.

[0199] On the other hand, systemic conflicts can persist indefinitely. If we reconsider a scenario where two USIMs are in RRC_IDLE / RRC_INACTIVE mode, such conflicts can occur when the paging configuration for each USIM causes a conflict in the PDCCH monitoring timing for paging. Since POs are periodic by definition, conflicts will recur, potentially causing paging procedures for one or both USIMs to fail. Systemic conflicts can also occur in scenarios where one USIM is in RRC_IDLE / RRC_INACTIVE mode and the other is in RRC_CONNECTED mode. If the service pattern of the USIM in RRC_CONNECTED mode results in high utilization of shared components, conflicts may occur when any AS procedure is initiated for the other USIM, regardless of the periodicity or duration of that AS procedure. This can lead to interruptions in calls established for the USIM in RRC_CONNECTED mode and / or failure of AS procedures for the USIM in RRC_IDLE / RRC_INACTIVE mode.

[0200] Support for multi-USIM UEs is currently handled in an implementation-specific manner, without support from 3GPP specifications. This results in a variety of UE behaviors when handling potentially unreliable and low-power collisions. As the complexity of 5G-capable UEs increases and the market demand for multi-USIM UEs continues to grow, leaving multi-USIM support to implementation-specific scenarios is no longer feasible. Therefore, to ensure that multi-USIM UEs can operate reliably and effectively in 5G networks, it is necessary to standardize UE behaviors associated with TDM sharing of common baseband and radio components; it is also necessary to define new NW behaviors / actions that support these new UE behaviors. For UEs in RRC_IDLE / RRC_INACTIVE modes, this will require enhanced SI and paging procedures, allowing the UE to avoid collisions when they are likely to occur; and allowing the UE to resolve whether and when these collisions actually occur in a predictable and reliable manner.

[0201] Collision Avoidance Scheme

[0202] The UE can determine the possibility of a conflict based on the UE configuration for multiple USIMs; such UE configurations include paging configuration, SMTC configuration, SI-SchedulingInfo configuration, C-DRX configuration, etc.

[0203] The conflict can then be avoided by reconfiguring the UE so that the monitoring and transmission opportunities associated with an AS procedure performed by one USIM do not overlap in time with those associated with an AS procedure performed by another USIM. For scenarios where one of the USIMs is in RRC_CONNECTED mode, this reconfiguration can include suspending or releasing the RRC connection.

[0204] The solutions described in this article are for the general case where USIMs are attached to different networks. However, these solutions can also be applied to scenarios where multiple USIMs are attached to the same network, such as RAN sharing, intra-MNO, and NW slicing use cases. In such scenarios, additional optimizations to these solutions can be applied; for example, selecting the same NW slice and / or the same serving cell or RAN slice for multiple USIMs, selecting the same PO for multiple USIMs, configuring POs close in time so that multiple USIM POs can be monitored with only one wake-up, and so on.

[0205] Method to Determine When a Collision Will Occur

[0206] The UE can determine when a collision will occur based on the configurations of multiple USIMs; these configurations include paging configuration, SMTC configuration, SI-SchedulingInfo configuration, C-DRX configuration, etc. In general, time synchronization between networks cannot be assumed; therefore, when determining when a collision will occur, the UE must consider any non-zero timing offsets that may exist between networks. We define this non-zero timing offset as the SFN and frame timing difference (SFTD) observed between the PCells of the multi-USIM UE, which consists of the following two components:

[0207] ·SFN offset = (SFN PCell_USIMx -SFN PCell_USIMy ) mod 1024, where SFN PCell_USIMx It is USIM x The SFN of the PCell radio frame of the connected NW, and the SFN PCell_USIMy It is USIM y The SFN of the PCell radio frame of the connected NW, where the UE receives the USIM that is closest in time to its received USIM. x The starting point of the PCell radio frame's time.

[0208] ● Where T FrameBoundaryPCell_USIMx Is UE from USIM x The time T at which the PCell of the connected NW receives the start of the radio frame. FrameBoundaryPCell_USIMy Is UE from USIM yThe time at which the PCell of the connected NW receives the start of a radio frame is the time closest to the radio frame received from the PCell. (T) FrameBoundaryPCell -T FrameBoundaryPSCell The unit for ) is Ts.

[0209] Figure 2 This is a timing diagram showing an example SFTD between PCells of multiple USIM UEs.

[0210] When determining whether a paging collision will occur, the UE first calculates the PF and PO for each network based on the paging configuration. Then, it uses the SFTD between the PCells of the multi-USIM UE to offset the PO of one USIM relative to the PO of another USIM to determine if any collision will occur. Figure 3A and Figure 3B As shown.

[0211] In scenarios where two USIMs are configured with the same DRX cycle, for example, T1 = T2, paging conflicts may occur once per DRX cycle. Figure 4A As shown. In a scenario where two USIMs are configured with different DRX cycles, for example, T1≠T2, from the perspective of the USIM with the longer DRX cycle, paging conflicts may occur once per DRX cycle, while from the perspective of the USIM with the shorter DRX cycle, paging conflicts may occur once every 2, 4, or 8 DRX cycles, as shown. Figures 4A-4C As shown. The frequency of collisions depends on the ratio of the DRX cycles of the two USIMs, where the DRX cycle T can be configured as 32, 64, 128, or 256 radio frames. See 3GPP TS 38.331 Release 15. We define the parameter M as follows to represent the frequency at which paging collisions between USIM1 and USIM2 may occur from the perspective of USIM1:

[0212] M = MAX(DIV(T2 / T1), 1)

[0213] A similar approach can be used to determine conflicts with the SI window, which is used to obtain the SI as specified in the SI-SchedulingInfo configuration of a USIM in RRC_IDLE / RRC_INACTIVE mode, the RRM measurement timing as specified in the SMTC configuration of a USIM in RRC_IDLE / RRC_INACTIVE mode, or the activity time as specified in the C-DRX configuration of a USIM in RRC_CONNECTED mode. Figure 5This is an illustration of a scenario where paging conflicts occur between a UE with USIM1 in RRC_IDLE / RRC_INACTIVE mode and a UE with USIM2 in RRC_CONNETCED mode, and the C-DRX enable duration.

[0214] For example, when configuring SearchSpaceId=0 for pagingSearchSpace, a similar method can be applied to determine conflicts by comparing the PDCCH monitoring times corresponding to the paging and RMSI for USIM1 and the PDCCH monitoring times corresponding to the paging and RMSI for USIM2. When configuring a SearchSpaceId other than 0 for pagingSearchSpace, as an example, a similar method can also be applied to determine conflicts by comparing the set of S1 consecutive PDCCH monitoring times corresponding to the S1 transmissions of SSB for USIM1 and the set of S2 consecutive PDCCH monitoring times corresponding to the S2 transmissions of SSB for USIM2, where S1 is determined according to ssb-PositionsInBurst in SIB1 for USIM1, and S2 is determined according to ssb-PositionsInBurst in SIB1 for USIM2.

[0215] PO Skipping

[0216] PO skipping can be used to avoid conflicts with USIMs in RRC_IDLE / RRC_INACTIVE modes. When PO skipping is configured, the UE does not monitor paging during the skipped PO. Configuring PO skipping can also modify network behavior; for example, the network may not page the UE during the skipped PO, or the network may repeat paging messages across multiple POs, etc.

[0217] Rule-Based PO Skipping

[0218] Rule-based PO skipping can be defined as allowing PO skipping for one or more USIMs to avoid paging conflicts. In scenarios where USIMs are configured with the same DRX cycle; for example, T1=T2, a conflict might occur once per DRX cycle, such as... Figure 4A As shown. To avoid paging conflicts, the UE can rotate the USIM monitoring its PO. However, if the network paging the UE during a PO that the UE is not monitoring, the paging will be missed. To ensure that paging is not missed, the network can repeat paging in multiple consecutive POs, thus allowing the UE to select the PO to receive the paging, for example, during the PO used for initial paging transmission; for example, the initial PO, or during the PO used for repeated paging transmission; for example, the repeated PO.

[0219] The UE can inform the network during registration that it is a multi-USIM UE, allowing the network to perform paging repeats only for multi-USIM UEs. The paging repeat period can be defined as nT, where n is the number of USIMs configured for the multi-USIM UE, and T is the DRX period. The parameter n can also be signaled to the network during registration.

[0220] The UE can use NAS signaling to inform the network that it is a multi-USIM UE, and the CN can then inform the RAN of the UE's multi-USIM capability. Alternatively, the UE can use AS signaling to inform the RAN that it is a multi-USIM UE, and the RAN can inform the CN of the UE's multi-USIM capability. The AS signaling used to inform the RAN that it is a multi-USIM UE can be implemented using existing procedures, such as RRC connection establishment, RRC connection restoration, UE auxiliary information, and UE capability transfer. Alternatively, a new RRC procedure can be defined.

[0221] Figure 6 This is an illustration of a scenario where USIM1 and USIM2 are configured with the same DRX period T. The paging repetition period is defined as 2T for each network, and the initial PO offset value τ is given for each DRX period of USIM1 and USIM2, where 0 ≤ τ < 2T. Depending on the value of τ, a conflict (complete or partial) may occur between the POs of the two USIMs.

[0222] In one aspect of this implementation, paging duplication is performed on all multi-USIM UEs, regardless of the value of τ; for example, regardless of whether a paging collision actually occurs. Alternatively, paging duplication can only be performed if the value of τ indicates that a paging collision will actually occur. When using this alternative, UE signaling is required to enable / disable paging duplication. For example, the UE can determine that the value of τ will cause a paging collision and can send an indication to the network to inform it of this. Alternatively, the UE can signal the value of τ or information about the paging configuration of other networks, so that the network can determine whether a paging collision will occur and enable / disable paging duplication accordingly.

[0223] When UE signaling is required to enable / disable PO skipping, if the UE desires CN-managed PO skipping with the RAN node, a multi-USIM UE can include a PO skipping indicator during initial registration. Alternatively, by including the PO skipping indicator during mobility registration updates or periodic registration updates, the UE can perform PO skipping more dynamically. This can be requested at some point after the multi-USIM UE registers for each USIM and after determining the possibility of paging conflicts between USIMs. As another alternative, the PO skipping indicator can be included in a registration completion message sent by the UE after receiving a registration acceptance response.

[0224] In another alternative, the UE can provide the PO skip indicator, parameter n, and any other relevant information to the RAN node via AS signaling. For example, the RRCSetupRequest message is used when performing the RRC connection establishment procedure; the RRCCResumeRequest / RRCResumeRequest1 message is used when performing the RRC connection restoration procedure; or the UEAssistanceInformation message is used when performing the UE assistance information procedure.

[0225] Figure 7 This is a flowchart of an example algorithm in which the UE performs PO skipping every other PO. This algorithm can be used in scenarios where the UE has two USIMs configured with the same DRX period.

[0226] exist Figure 7 In step 1, the UE determines which PO will occur next. Alternatively, the UE can choose to start with USIM1 or USIM2, regardless of which PO will occur next, and proceed to step 2 or step 3 accordingly. This alternative can be used as a simplification to avoid having to determine when the POs will occur in time relative to each other.

[0227] In step 2, if a PO for USIM1 is subsequently generated, the UE sets the PO monitoring flag for USIM1 and clears the PO monitoring flag for USIM2.

[0228] In step 3, if a PO for USIM2 subsequently appears, the UE clears the PO monitoring flag for USIM1 and sets the PO monitoring flag for USIM2. For multi-USIM UEs with more than two USIMs, steps 1 and 3 can be repeated to check for the existence of POs for the additional USIMs.

[0229] In step 4, the UE waits until the next PO occurs.

[0230] In step 5, the UE determines whether to set a PO monitoring flag for the USIM that has (or will have) a PO.

[0231] In step 6, if a PO monitoring flag is set for the USIM, the UE configures a lower layer to perform PO monitoring for the USIM.

[0232] In step 7, if a PO monitoring flag is not set for the USIM, the UE configures a lower layer to skip PO monitoring for the USIM.

[0233] In step 8, the UE switches the state of the PO monitoring tag used for the USIM and returns to step 4.

[0234] Figure 8 This diagram illustrates how to monitor / skip POs based on an algorithm that skips POs every other PO, for scenarios where USIMs are configured with the same DRX period (e.g., T1 = T2). In this example, it is assumed that the PO for USIM1 appears first.

[0235] To ensure that the DRX period is identical for each USIM, network behavior can be constrained to configure the same UE-specific DRX period for all multi-USIM UEs; and UE behavior can be constrained to ensure that the UE always uses the UE-specific DRX period, rather than the shortest of the UE-specific DRX period and the default value broadcast in the SI. In one aspect of the invention, when a UE registers with the network, the network can use NAS signaling to configure the same UE-specific DRX period for all multi-USIM UEs. For example, the core network can select an appropriate DRX period for each USIM UE by returning the appropriate DRX period for the multi-USIM UE in the accepted DRX parameter element of the registration accept message. Alternatively, for scenarios where the DRX periods may differ, the UE can use NAS or RRC signaling to request modification of its DRX period to ensure that the DRX period for each USIM is identical. For UEs in RRC_INACTIVE mode, the CN can provide information to the RAN node about the desired UE-specific DRX period to ensure that this DRX period is identical to the DRX periods of other USIMs.

[0236] In a scenario where two USIMs are configured with different DRX cycles (e.g., T1 ≠ T2), paging conflicts may occur once every M DRX cycles, such as... Figures 4B-4D As shown. For scenarios where T2 = 2T1, applying this algorithm to skip POs every other PO can lead to the following: Figure 9A and Figure 9B The PO is monitored / skipped as shown. If the PO is used for a USIM with a long DRX cycle, such as... Figure 9AIf the paging repetition period is the first to appear, then the PO is skipped, allowing reliable paging reception from both networks assuming a paging repetition period of 2 is configured. However, if the PO is used for a USIM with a shorter DRX period, as shown... Figure 9B If the first occurrence shown in the diagram occurs, a collision will happen, and paging will not be reliably received from either network.

[0237] To mitigate this problem, the algorithm can be modified so that the value of the PO monitoring flag for each USIM is initialized when the first PO for a USIM with a longer DRX cycle occurs. Figure 10 This is a flowchart of an example algorithm, in which the UE executes PO skipping every other PO, which also supports scenarios where T1≠T2.

[0238] Figure 11 This is a signaling diagram used to configure PO skipping during the registration process. Figure 11 In step 1, the UE receives a trigger to register with the NW.

[0239] In step 2, the UE transmits a registration request message to the CN indicating that it is a multi-USIM UE. The UE may also indicate how many USIMs it has configured. The UE may also indicate the preferred DRX period to use. Alternatively, the UE may signal parameters related to the DRX period relationship between USIMs; for example, the ratio of DRX periods. Receiving an indication that the UE is a multi-USIM UE can be used to implicitly indicate that the UE wants to enable PO repeating. Alternatively, the UE may include an explicit PO repeating indication to request the enabling of PO repeating.

[0240] In step 3, the CN performs the registration procedure from TS23.502 and registers the UE as a multi-USIM UE. The CN can also configure its DRX cycle for all multi-USIM UEs as previously mentioned and return that value in the accepted DRX parameter element of the registration acceptance message. If the UE has already included a PO repeat indication, the CN saves it in the UE context maintained for the UE for future use whenever paging the UE is required.

[0241] In step 4, the CN transmits a registration acceptance message to the UE to indicate that the registration request has been accepted. This message may include the following: the DRX period configured by the CN, confirmation that PO repetition is enabled, and that parameter N has been received. This information can also be added to the N2 signaling to inform the RAN node to enable PO repetition and use the configured DRM period.

[0242] In step 5, the UE monitors the paging and performs a PO skip every other PO.

[0243] In step 6, the CN receives the trigger from the paging UE.

[0244] In step 7, the CN transmits a paging message to the gNB and may also provide the gNB with information about the UE's preferred DRX cycle. Furthermore, if the UE has previously configured PO skipping, the CN may inform the gNB to enable PO skipping and provide the parameter N associated with the UE.

[0245] In step 8, the gNB uses paging repeat to page the UE.

[0246] In step 9, the gNB uses the initial PO to page the UE.

[0247] In step 10, the gNB uses a repeated PO to page the UE.

[0248] In step 11, the UE receives a paging message in the initial PO or the repeated PO.

[0249] In step 12, the UE establishes a connection with the network.

[0250] Figure 12 This is a signaling diagram used to configure PO skipping during the RRC connection recovery process.

[0251] exist Figure 12 In step 1, the UE detects an event that triggers its configuration PO skip. The event that triggers PO skip may include determining that a conflict will occur based on the UE configuration for multiple USIMs, detecting one or more paging conflicts, starting an AS procedure for another USIM, transitioning to the RRC_CONNECTED state for another USIM, configuring DC for another USIM, or any combination thereof.

[0252] In step 2, the UE transmits the RRRCResumeRequest / RRCResumeRequest1 message to configure PO skipping.

[0253] In step 3, gNB configuration PO is skipped.

[0254] In step 4, the gNB transmits an RCRelease message including suspendConfig.

[0255] In step 5, upon receiving the RRCLease message, the UE switches to RRC_INACTIVE and skips every other PO. In a scenario where the UE is configured with n USIMs, the UE skips (n-1) POs; that is, only one of every n POs is monitored.

[0256] In step 6, the UE's DL data is forwarded to the gNB.

[0257] In step 7, the gNB uses paging repeat to page the UE. The paging repeat period can be defined as nT, where n is the number of USIMs configured for a multi-USIM UE, and T is the DRX period.

[0258] In step 8, the gNB uses the initial PO to page the UE.

[0259] In step 9, the gNB uses a repeated PO to page the UE.

[0260] In step 10, the UE receives a paging message in the initial PO or the repeated PO.

[0261] In step 11, the UE restores its RRC connection with the network.

[0262] In step 12, the UE receives DL data from the network.

[0263] Figure 13 This is a signaling diagram in which the UE-assisted information process informs the network of the desired PO skip configuration. Figure 13 In step 1, the UE transmits a UEAssistanceInformation message that includes the expected PO skip configuration.

[0264] In step 2, gNB configuration PO is skipped.

[0265] In step 3, the gNB transmits an RCRelease message including suspendConfig.

[0266] In step 4, upon receiving the RRCLease message, the UE switches to RRC_INACTIVE and performs PO skipping every other PO.

[0267] In step 5, the UE's DL data is forwarded to the gNB.

[0268] In step 6, the gNB uses paging repeat to page the UE.

[0269] In step 7, the gNB uses the initial PO to page the UE.

[0270] In step 8, the gNB uses a repeated PO to page the UE.

[0271] In step 9, the UE receives a paging message in the initial PO or the repeated PO.

[0272] In step 10, the UE restores its RRC connection with the network.

[0273] In step 11, the UE receives DL data from the network.

[0274] Using paging repetition increases paging signaling and also increases paging delay. For scenarios where DRX periods differ, paging repetition is unnecessary for USIMs with longer DRX periods. Optimizations can be made for such scenarios to enable paging repetition only for networks with shorter DRX periods. UL control signaling from the UE can be used to instruct the network to request paging repetition for networks with shorter DRX periods.

[0275] In another alternative, paging repetition can be triggered by the network after a paging failure against the UE. The detection event can be based on a count of paging failures; for example, the number of consecutive paging failures exceeds a threshold, the number of paging failures within a specified time interval exceeds a threshold, etc.

[0276] For beam-based paging mechanisms, when SearchSpaceId=0 is configured for pagingSearchSpace, similar skip and repeat methods can also be applied, as an example, to the PDCCH monitoring timings corresponding to paging and RMSI for USIM1 and / or USIM2, respectively.

[0277] For beam-based paging mechanisms, when the SearchSpaceId is configured to be other than 0 for pagingSearchSpace, a similar skip and repeat method can also be applied to a set of S consecutive PDCCH monitoring opportunities corresponding to S transmitted SSBs (e.g., S1 for USIM1 and S2 for USIM2).

[0278] Event-Based PO Skipping

[0279] Event-based PO skipping can be used to suspend paging to a network based on the occurrence of a specific event. Events triggering PO skipping can include determining that a collision will occur based on UE configuration for multiple USIMs, detecting one or more paging collisions, initiating an AS procedure for another USIM, transitioning to an RRC_CONNECTED state for another USIM, configuring a DC for another USIM, etc. PO skipping for a given network can continue for a variable duration until the triggering event ceases to exist; for example, the UE is reconfigured such that collisions will no longer occur for multiple USIMs, an AS procedure for another USIM is completed, a transition from RRC_CONNECTED to RRC_IDLE / RRC_INACTIVE for another USIM, releasing a DC for another USIM, etc. Alternatively, PO skipping for a given network can continue for a fixed duration known to both the UE and the network (e.g., T). PO_SkippingThe PO skip duration can be pre-configured or signaled before the UE initiates a PO skip. In one aspect of this scheme, the PO skip duration is determined by the UE and signaled to the network. In another aspect, the UE optionally signals to the network a preferred PO skip duration, but the final decision on the PO skip duration is made by the network. Figures 14A-14B This demonstrates how the PO skips scenarios where the events last for both variable and fixed durations.

[0280] After an emergency call is made, the UE may need to monitor the paging to ensure it can receive the emergency callback. After an emergency call is made on a network, event-based PO skipping can be used to inform other network UEs that they will not monitor the paging and therefore will not be able to establish an MT call.

[0281] In one implementation of this scheme, RRC signaling is used to perform event-based PO skipping for paging initiated by the CN and / or RAN. When an event triggering PO skip activation occurs, the UE sends a PO skip indication to the network. Once triggered, a PO skip can remain active for a variable or fixed duration. In scenarios where the PO skip remains active for a variable duration, when an event triggering PO skip activation occurs, the UE sends another PO skip indication to the network to indicate that the PO skip should be deactivated. And in scenarios using a fixed duration, the PO skip indication can also indicate the duration for which the PO skip will remain active. The network can treat the PO skip indication as a command to be obeyed. Alternatively, the network can treat the PO skip indication as a request that it can accept or reject. Figures 15A-15B and Figures 16A-16B This is a diagram of the signaling graph, where RRC signaling is used for event-based PO skipping in variable and fixed durations, respectively.

[0282] The network can send a response to the UE to acknowledge receipt of the PO skip indication. In scenarios where the network treats the PO skip indication as a request, the response can indicate whether the request is granted. Furthermore, in scenarios where the PO skip is activated for a fixed duration, the response can be used to signal the skip duration within the PO skip indication or to override the duration requested by the UE.

[0283] PO skip indications can be signaled to the network in the same messages used to establish or restore RRC connections; for example, RRCSetupRequest, RRCResumeRequest, or RRCResumeRequest1. New EstablishmentCause / ResumeCauses (e.g., po-SkippingActivation) can be used to signal to the network a PO skip indication for a UE in RRC_IDLE / RRC_INACTIVE mode. New EstablishmentCause / ResumeCauses (e.g., po-SkippingDeactivation) can also be defined to deactivate PO skipping for scenarios where PO skipping is activated for a variable duration.

[0284] Alternatively, the PO skip indication can be signaled to the network in a separate message transmitted after the RRC connection has been established or restored. In one aspect of the invention, a novel POSkipping message can be used to signal the PO skip indication to the network. And in another aspect of the invention, a UEAssistanceInformation message can be used to signal the PO skip indication to the network. In a third aspect of the invention, the PO skip indication can be provided to the network using one of the registration request procedures (e.g., initialization, mobility registration update, periodic registration update, etc.).

[0285] PO skipping may be transparent to the CN. In this case, the RAN node (e.g., gNB) can buffer any paging requests or DL ​​data received from the CN for UEs in RRC_IDLE or RRC_INACTIVE modes, respectively, until PO skipping ceases to be active. Alternatively, when PO skipping is active, the gNB can provide an indication to the CN to prevent it from performing CN paging for UEs in RRC_IDLE mode, or to prevent it from sending DL data to a gNB intended for UEs in RRC_INACTIVE mode.

[0286] Figure 15A and Figure 15B An example of event-based PO skipping with variable duration using RRC signaling is shown. Figure 15A In step 1, the UE detects an event that triggers PO to skip activation.

[0287] In step 2, the UE transmits the RRCResumeRequest / RRRCResumeRequest1 message, where ResumeCause is set to "po-SkippingActivation" to activate PO skipping.

[0288] In step 3, the gNB activates PO skipping in step 3a, and optionally notifies the CN that PO skipping is activated in step 3b. This notification may provide a time value to indicate how long the CN will buffer the DL data and, upon expiration, send the buffered DL data to the UE.

[0289] In step 4, the gNB transmits an RRCRelease message that includes suspendConfig. Before transmitting RRCResumeRequest / RRCResumeRequest1 in step 2, suspendConfig can be "negotiated," in which case it does not need to be included in the RRCRelease message.

[0290] In step 5, upon receiving the RRCLease message, the UE switches to RRC_INACTIVE and activates PO skip.

[0291] In step 6, the DL data is available to the UE, and if the gNB has informed the CN that PO skipping is activated in step 3b, the CN buffers the DL data in step 6a. When the timer associated with PO skipping expires, in step 6b, the CN transmits the DL data intended for use by the UE to the gNB. The timer may be associated with the value provided in step 3, or it may be provided via network configuration or policy.

[0292] In step 7, if the gNB receives DL data intended for use by the UE from the CN, the gNB buffers the DL data.

[0293] Figure 15A The call process in Figure 15B The process continues. Figure 15B In step 8, the UE detects an event that triggers the PO to skip to activation.

[0294] In step 9, the UE transmits the RRCResumeRequest / RRRCResumeRequest1 message, where ResumeCause is set to "po-SkippingDeactivation" to deactivate the PO skip.

[0295] In step 10, the network deactivates PO skipping in step 10a, and can also notify the CN that PO skipping has been deactivated in step 10b.

[0296] In step 11, if the CN has already buffered any DL data when the PO skip is activated, then as shown in step 11a, the data is sent to the gNB. In step 11b, the gNB sends the DL data to the UE, which was buffered when the PO skip was activated. This data may have already been buffered by the CN or the gNB.

[0297] In step 12, the UE begins UL / DL transmission and reception with the gNB and transmits UL / DL data to / from the CN.

[0298] Figures 16A-16B An example of an event-based PO skipping with fixed duration using RRC signaling is shown.

[0299] In step 1, the UE detects an event that triggers PO to skip activation.

[0300] In step 2, the UE transmits the RRCResumeRequest / RRRCResumeRequest1 message, where ResumeCause is set to "po-SkippingActivation" to activate PO skipping.

[0301] In step 3, the gNB transmits an RRCRelease message that includes suspendConfig. Before transmitting RRCResumeRequest / RRCResumeRequest1 in step 2, suspendConfig can be "negotiated," in which case it does not need to be included in the RRCRelease message.

[0302] In step 4, PO skips activation. In step 4A, the UE receives the RRCRelease message, transitions to RRC_INACTIVE, and begins T... PO_Skipping This activates PO skipping. In step 4B, gNB starts T. PO_Skipping To activate PO skipping, in step 4C, the gNB can notify the CN that PO skipping is activated. This notification can provide a time value to indicate how long the CN will buffer the DL data and send the buffered DL data to the UE upon expiration. Note that this notification can be sent at any time after step 2.

[0303] In step 5, the DL data is available to the UE, and if the gNB has informed the CN PO to skip activation in step 4C, the CN buffers the DL data in step 5A.

[0304] Figure 16A The call process in Figure 16BThe process continues. In step 5B, when the timer associated with the PO skip expires, the CN transmits DL data intended for use by the UE to the gNB. The timer may be associated with the value provided in step 4, or it may be provided via network configuration or policy.

[0305] In step 6, if the gNB receives DL data intended for use by the UE from the CN, the gNB buffers the DL data.

[0306] In step 7, PO skips the time period expiration. In step 7A, T PO_Skipping Upon expiration, the deactivation skipped by the PO is triggered at the UE. In step 7B, T PO_Skipping Upon expiration, the deactivation skipped by the PO is triggered at gNB.

[0307] In step 7C, T PO_Skipping Upon expiration, the deactivation skipped by the PO is triggered at CN.

[0308] In step 8, if the CN has already buffered any DL data while the PO skip is activated, then the data is sent to the gNB as shown in step 8a. Alternatively, if the UE context maintained within the CN indicates that the UE is in CM_IDLE, then the CN may page the UE. In step 8b, the gNB pages the UE.

[0309] In step 9, the UE transmits the RRCResumeRequest / RRRCResumeRequest1 message, wherein the ResumeCause is set as described in section 5.3.2.3 of TS 38.331 Release 15.

[0310] In step 10, the UE begins UL / DL transmission and reception, which may include receiving DL packets buffered by the gNB or CN while the PO skip is activated.

[0311] In step 11, UL / DL data is transmitted to / from the CN.

[0312] In another alternative, the UE can transmit RCResumeRequest / RRCResumeRequest1 to the network to enable T PO_Skipping Restore the RRC connection before the expiration date; then, begin the UL DL transfer as described in steps 9 through 11 of the above process. If in T PO_Skipping The UE cannot resume the connection before the expiration date; for example, due to activity on another USIM, the suspended RRC connection is implicitly released by the UE and the network, and the UE transitions to RRC_IDLE.

[0313] In another implementation of this scheme, NAS signaling (e.g., MICO mode) is used to perform event-based PO skipping for paging initiated by the core network (CN), such as... Figure 15A and Figure 15B As shown.

[0314] Figure 17 This is an example call flow demonstrating event-based PO skipping using NAS signaling and featuring both variable and fixed durations. Figure 17 In step 1, the UE detects an event that triggers PO to skip activation.

[0315] In step 2, the UE performs a mobility registration update and includes a PO skip indication. If the PO skip is for a fixed duration, the duration can also be provided. Note that the PO skip indication can also be included during periodic registration updates or service requests. Alternatively, the UE can request the PO skip function by specifying its MICO mode enable preference and a multi-USIM indicator.

[0316] In step 3, the CN returns a registration acceptance response and confirms that PO skipping is activated at the CN. The CN may also include the duration for which the CN will buffer the DL data of the UE associated with the PO skipping period. This duration may be a value provided by the UE or a value provided by the CN.

[0317] In step 4, when the PO skip is active, the CN buffer is for any DL data received by the UE.

[0318] In step 5, the UE detects an event indicating the end of the PO skip. If the PO skip is configured for a fixed duration, the event can be the expiration of a timer associated with the PO skip period.

[0319] In step 6, the UE sends a mobility registration update to the CN to deactivate the PO skip.

[0320] In step 7, the CN returns a registration acceptance message and confirms that the PO skipped being deactivated in the CN.

[0321] In step 8, any DL data buffered in the CN during the PO skip is sent to the UE, and the UE can resume UL / DL data transmission with the CN.

[0322] SFN-Based PO Skipping

[0323] SFN-based PO skipping can be used to divide the SFN space into regions where POs are monitored or skipped. For example, a starting SFN and an ending SFN can be defined for PO monitoring, such that if a PO falls within this range, the PO is monitored; and if a PO falls outside this range, the PO is skipped.

[0324] SFN-based PO skipping can be used to avoid paging conflicts between multiple USIMs by defining non-overlapping PO monitoring areas for each USIM. The UE will determine the areas where POs should be skipped / monitored to avoid paging conflicts and signal this information to the network. Alternatively, the UE can provide paging configuration information to the network, and the network can determine the areas where POs should be skipped / monitored. In general, SFN synchronization between networks cannot be assumed; therefore, SFN offsets should be considered when determining the appropriate start / end SFN for a given network.

[0325] For example, we can consider a scenario where a multi-USIM UE has two USIMs, the SFN space is divided into two parts, and the SFN offset between NW1 and NW2 is 117. Figure 18 As shown. If we use the SFN number of NW1 as a reference, the start and end SFNs for PO monitoring of NW1 can be defined as 0 and 511, respectively; and the start and end SFNs for PO monitoring of NW2 can be defined as 512 and 1023, respectively. When PO monitoring is to be performed, the UE will signal values ​​0 and 511 to NW1 to indicate the SFN range. When PO monitoring is to be performed, the UE will also signal the start / end SFN values ​​to NW2 to indicate the SFN range. However, instead of directly sending signal notification values ​​512 and 1023, the UE will increase the SFN offset and perform a modulo 1024 operation on the result to convert the start / end SFN into an SFN number for NW2. In this case, this will result in sending signal notification values ​​(512+117)mod1024=629 and (1023+117)mod1024=116 to NW2 when PO monitoring is performed to indicate the SFN range.

[0326] In another implementation of this scheme, the SFN space can be divided such that there are multiple regions within it for a given USIM monitoring PO. Figure 19 This is an illustration of a scenario where a multi-USIM UE has two USIMs, NW1 and NW2, with an SFN offset of 117, and exists in two PO monitoring areas defined for each USIM.

[0327] In the examples above, SFN-based PO skipping is used to avoid paging conflicts between multiple USIMs. However, SFN-based PO skipping can also be used to avoid conflicts between other AS procedures that can be performed on another USIM. For example, when a PO is skipped for the first USIM, SI acquisition, idle mode measurement, etc., can be performed on another USIM without the risk of conflicting with the monitored PO for the first USIM.

[0328] SFN-based PO skipping can be triggered by a request from the UE to the gNB or CN. This request includes an SFN PO skipping indication and the number of SFN areas used to allocate the PO. This mechanism can be used for... Figure 18 The NW1 provides SFN reference timing. Then, the UE can... Figure 18 NW2 makes another request, which includes an SFN PO skip indication and the number of SFN areas used to divide the PO, the same number used for NW1. The UE can then use the SFN offset between NW1 and NW2 to monitor or skip the PO when determining the SFN area.

[0329] The SFN-based PO skipping concept can be viewed from another perspective. Instead of focusing on PO skipping, the concept can be conceived as SFN-based PO area selection. The CN or RAN node can define the PO area within the SFN and assign a different area to each USIM in the UE. This mechanism allows the UE to request a different SFN PO area for each installed USIM to avoid paging conflicts. If the USIMs belong to the same MNO, a single SFN timing reference can be used. However, if the USIMs belong to different MNOs, the UE needs to apply an SFN offset.

[0330] H-SFN-Based PO Skipping

[0331] H-SFN-based PO skipping can be used to define superframes in which POs are skipped. H-SFNs are broadcast by the cell and increment by 1 as the SFN surrounds. In addition to calculating POs and PFs, the UE can also calculate paging superframes (PHs), which refer to superframes in which the UE monitors the paging H-SFN. PHs can be determined based on a formula known to the UE and network as a function of the DRX period, and the UE's identity, where the DRX period can correspond to an extended DRX period greater than 1024. SFN-based regions and H-SFN-based regions can be defined and indicated to the UE separately.

[0332] PO Extension

[0333] To reduce the likelihood of a UE failing to receive a DL due to collisions during its configured PO, the PO can be extended using additional PDCCH monitoring opportunities used for paging. An extended PO can be defined as a set of S*X consecutive PDCCH monitoring opportunities, where S is the number of actual SSBs transmitted according to ssb-PositionsInBurst in SIB1, and X is additionalMonitoringOccasionOfPO (if configured), otherwise equal to 1. This parameter can also be referred to as nrofPDCCH-MonitoringOccasionPerSSB-InPO. The [X*S+K]th PDCCH monitoring opportunity used for paging in the PO corresponds to the Kth transmitted SSB, where x = 0, 1, ..., X-1; and K = 1, 2, ..., S. Figure 20 This is a diagram of the extended PO, where S = 3 and X = 3.

[0334] The network repeats the same paging message and short message during all PDCCH monitoring times, including extended PO, so the UE can monitor any PDCCH monitoring time during extended PO. If a conflict occurs for the selected PDCCH monitoring, the UE can select a PDCCH monitoring time for the same beam in another scan. For example, we can consider... Figure 20 The extended PO is shown. If the UE selects beam 1 as the optimal beam, then PDCCH monitoring times 1, 4, or 7 can be used to receive paging DCI.

[0335] Figure 21 This demonstrates a sample cell-specific PO extension scheme. Figure 21 In step 1, the UE receives system information configuring the extended PO. The extended PO can be indicated using fields in the PCCH-Config information (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO).

[0336] In step 2, the UE monitors paging during a PDCCH monitoring opportunity that does not involve conflict.

[0337] In step 3, the UE receives a paging during the monitored PDCCH monitoring period.

[0338] Cell-specific PO extensions can be used, allowing broadcast signaling to notify the PO configuration of that extension. The PDCCH monitoring timing for these extensions will be available to any UE within the cell.

[0339] Alternatively, UE-specific PO extensions can be used. In this case, dedicated signaling can be used to signal the configuration of the extended PO. In this scenario, PDCCH monitoring of these extensions will only be available for UEs that have already been explicitly configured by the network using the extended PO. Configuration of the extended PO for the UE can be triggered upon receiving an implicit or explicit request from the UE. For example, the UE can provide the network with an indication that it has multiple USIMs configured, which can trigger the network to configure the UE using the extended PO.

[0340] Figure 22 This is a diagram of a UE-specific PO extension scheme.

[0341] exist Figure 22 In step 1, the UE signals to the network multiple USIM assistance information to indicate that it has multiple USIMs configured. This signaling can be achieved using a new RRC message (e.g., multi-USIMAssistanceInformation). Alternatively, the signaling for multiple USIM assistance information can be implemented using a UE assistance information procedure, where the signaling corresponds to the transmission of a UEAssistanceInformation message. Furthermore, in another alternative, the signaling for multiple USIM assistance information can be implemented using a UE capability transfer procedure, where the signaling corresponds to the transmission of a UECapabilityInformation message.

[0342] In step 2, the gNB configures the UE using an extended PO. The extended PO can be indicated using PCCH-Config information where the parameter nrofPDCCH-MonitoringOccasionPerSSB-InPO is greater than 1.

[0343] In step 3, the UE monitors paging during a PDCCH monitoring opportunity that does not involve conflict.

[0344] In step 4, the UE receives a paging during the monitored PDCCH monitoring period.

[0345] In another example, the UE may issue an explicit request to configure an extended PO, where the request is triggered based on the UE's determination that a paging collision will occur or may occur. This request may include information to assist the network in determining the configuration of the extended PO; for example, which PDCCH monitoring time in the pagingSearchSpace should be configured for the extended PO.

[0346] In other implementations, the PO can be extended to include PDCCH monitoring times from another PO defined for the PF. The advantage of this configuration is that it eliminates the need to define additional PDCCH monitoring times beyond those required for paging traditional UEs.

[0347] Paging Modification

[0348] To avoid paging conflicts, the paging configuration of a UE used by one or more networks can be modified. In the following sections, we consider two scenarios. In the first scenario, the UE determines how its paging configuration should be modified and provides the network with an instruction to request modification. In the second scenario, the network determines how its paging configuration should be modified based on auxiliary information signaled from the UE.

[0349] UE-Determined Paging Modification

[0350] To avoid paging conflicts, the UE can provide the network with an indication to request modification of the paging configuration. This indication may include information corresponding to preferred values ​​for one or more parameters used in the paging configuration. Whether the network supports the paging modification request can be signaled to the UE via broadcast or dedicated signaling.

[0351] For scenarios where the number of POs in the PF is greater than 1 (e.g., Ns > 1), the UE can request to monitor different POs in the PF. Figure 23 This is an illustration of a scenario where multiple USIM UEs are configured to monitor POPs (Positions) of two networks. The paging configuration causes the UE to monitor paging during PO1 of USIM1 and PO2 of USIM2; and a collision occurs during the monitored PO. To avoid paging collisions, the UE can request to monitor PO2, PO3, or PO4 of NW1, or PO1 of NW2.

[0352] Note: This example illustrates a complete conflict between PO1 and PO2 for NW1 and NW2 respectively. Partial conflicts can also trigger the UE to execute a paging modification request.

[0353] The UE can signal the index of the requested PO to the network to indicate the desired PO. If a zero-based index is assumed, then for... Figure 23 In the example shown, the UE will send a signaling value of 1, 2 or 3 to request PO2, PO3 or PO4 for NW1 respectively; or send a signaling value of 0 to request PO1 for NW2.

[0354] Alternatively, the UE can signal the number of the initial PDCCH monitoring opportunities for the requested PO, for example, the (requested i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter signaled in the PCCH-Config. If we assume that PDCCH monitoring opportunities used for paging are numbered starting from zero, then for... Figure 23 In the example shown, the UE will send a signaling value of 3, 6, or 9 to request PO2, PO3, or PO4 for NW1, respectively; or send a signaling value of 0 to request PO1 for NW2.

[0355] The UE can also request to monitor POs in different PFs. The (UE_ID mod N) field in the PF calculation assigns the UE to a PF based on the UE_ID. The UE can signal an offset to the network, which is used in the calculation of this field to select different PFs as follows:

[0356] (SFN + PF_offset) mod T = (T div N) * ((UE_ID + offset) mod N)

[0357] An alternative to signaling the offset is to request the use of an alternate UE_ID. This alternate UE_ID can be considered an alias used to determine the PF and PO. And in yet another alternative, the UE can request the use of a different 5G-S-TMSI.

[0358] The UE can also request a modification to the DRX period. Since POs are periodic, requesting a change to the DRX period alone may not avoid all paging collisions. However, changing the DRX period can allow some POs to occur without collisions. Requesting a longer DRX period can also provide the UE with more options for selecting different PFs to monitor; for example, selecting the value of the offset parameter used in the formula above.

[0359] Using the methods described herein, a UE can request modification of one or more paging configuration parameters. Explicit signaling (e.g., RRC signaling) can be used to instruct the network which parameters the UE requests to modify. It can be assumed that parameter values ​​in the current paging configuration are used for parameters not explicitly included in the paging modification request. The paging modification request can be signaled in a separate message (e.g., PagingModificationRequest). Alternatively, the paging modification request can be signaled as part of another message (e.g., as an optional IE within the RRCSetupRequest, RRCResumeRequest, or RRCResumeRequest1 message).

[0360] The network can respond to a paging modification request with an acknowledgment. This acknowledgment may include a field indicating whether the paging request has been accepted. It may also include a field indicating that the paging configuration has been modified with a value different from the value requested by the UE. The acknowledgment can be signaled in a separate message (e.g., a PagingModificationAcknowledgment message). Alternatively, the acknowledgment can be signaled as part of another message (e.g., as an optional IE in an RRRCRease message).

[0361] A sample PagingModification IE that can be used for paging modification requests or paging modification confirmations is shown in Code Example 3A in the appendix. A description of the PagingModification field is shown in Code Example 3B.

[0362] In another alternative, the PF / PO space is divided into multiple zones, for example, 8 zones (1024 / 8 = 128). Then, when the UE or NW detects a potential paging conflict, it can request that the PF / PO be moved to another zone to avoid the conflict. If the MNOs are the same, the NW or UE can perform this operation. If the MNOs are different, the UE will perform this operation because it has timing information for both USIMs. It can then simply request that the UE determine a zone that will not cause a paging conflict.

[0363] Figure 24 This is a signaling diagram illustrating an example paging modification request from a multi-USIM UE attached to two network operating UEs, NW1 and NW2. Figure 24 In step 1, the UE determines that a conflict will occur for the PO configured for NW1 and NW2.

[0364] In step 2, the UE determines how to modify the paging configurations of NW1 and / or NW2 to avoid paging conflicts. The UE may attempt to modify the paging configurations of one or both networks depending on which network supports the paging modification request and the flexibility of the paging configuration for a given network. For example, a network configured to support multiple POs per PF and / or multiple PFs per DRX cycle is more flexible and offers more options for reconfiguring the UE to avoid paging conflicts than a network not configured to support multiple POs per PF and / or multiple PFs per DRX cycle. For illustrative purposes, we assume the UE determines that the paging configuration for NW1 should be modified to avoid paging conflicts.

[0365] In step 3, the UE establishes or restores an RRC connection with NW1 to request modification of the paging configuration. The UE can provide the NW1 with an indication to request modification of the paging configuration using any of the methods described herein. In this example, the indication is provided in a message used to establish / restore an RRC connection (e.g., RRCSetupRequest, RRCResumeRequest, or RRCResumeRequest1). Alternatively, the paging modification request can be implemented using a UE Assistance Information procedure, where the signaling of the paging modification request corresponds to the transmission of a UEAssistanceInformation message. The UEAssistanceInformation message may include preferred values ​​for one or more paging configuration parameters, such as: a preferred PagingCycle, a preferred UE_ID to be used in PO / PF calculations, an index i_s corresponding to a preferred PO monitored in the PF, and an offset to be used in the PF calculations. Example PagingPreference information that may be included in the UEAssistanceInformation message is shown in code examples 6A and 6B in the appendix.

[0366] In step 4, NW1 determines whether to accept the paging modification request from the UE. For illustrative purposes, we assume that NW1 accepts the paging modification request.

[0367] In step 5, NW1 responds to the paging modification request with an acknowledgment. NW1 may provide this acknowledgment using any of the methods described herein. In this example, the acknowledgment is provided in the RRCReconfiguration message. Alternatively, the RRCReconfiguration message may be used to signal the new paging configuration.

[0368] In step 6, the UE applies the modified paging configuration to NW1.

[0369] In step 7, the UE monitors paging during the PO configured for NW1 and NW2.

[0370] In step 8, if triggered, NW1 pages the UE during the PO configured for NW1.

[0371] In step 9, if triggered, NW2 pages the UE during the PO configured for NW2.

[0372] Network-Determined Paging Modification

[0373] To avoid paging collisions, the UE can report network auxiliary information to the network to determine how to modify the paging configuration. This auxiliary information may include one or more parameters corresponding to the PCCH-Config field used to configure paging to other networks. The auxiliary information may also include parameters corresponding to the timing offset between the two networks; for example, the SFTD between the PCells of a multi-USIM UE as described herein. In one aspect of the invention, the network can reconfigure the UE to monitor different POs during a PF. Alternatively, the network can reconfigure the UE to monitor POs in different PFs, wherein the UE uses an offset signaled by the network to determine the PF. The network can reconfigure other paging parameters (e.g., DRX period) to avoid or reduce paging collisions.

[0374] The CN can inform the RAN node that the UE is a MUSIN device and provide the RAN node with the UE_ID of multiple USIMS within the UE. The RAN node can then determine which paging avoidance method to use and configure the UE for the determined method via RRC signaling. Information related to the paging avoidance method used can be shared among RAN nodes via the X2 interface. This sharing can be triggered by events such as handover, cell reselection, RNAU, TAU, and registration.

[0375] RRC Release / Suspend Request

[0376] In a scenario where one of the USIMs is in RRC_CONNECTED mode, the UE may request to release or suspend the RRC connection to prevent (or reduce the likelihood of such a conflict) with monitoring timing and transmission opportunities associated with an AS procedure performed against another USIM.

[0377] RRC messages used to request the release or suspension of an RRC connection may include indications for PO skipping, similar to the event-based PO skipping scheme proposed herein; or they may assist the network in determining parameters for paging configurations that should be used to avoid conflicts with monitoring timings and transmission opportunities associated with another USIM, similar to the paging modification request scheme proposed herein. The RRC message may also include an estimate of the time the UE expects to be away from the network, such as `pauseDuration`, thereby allowing the network to adjust its behavior, such as suspending paging, when the UE is away from the network.

[0378] Figure 25 This is an illustration of a scenario where a multi-USIM UE in RRC_CONNECTED mode of NW1 receives a trigger to establish an RRC connection with NW2. This trigger requires the UE to release / suspend the RRC connection with NW1. Figure 25In step 1, the UE and NW1 are in the RRC_CONNECTED state and are performing UL / DL transmission and reception.

[0379] In step 2, the UE receives a trigger to establish a connection with NW2. The UE optionally determines how to modify the paging configuration of NW1 to avoid paging conflicts. The UE may attempt to modify the paging configuration of one or both networks depending on which network supports the paging modification request and the flexibility of the paging configuration for a given network. For example, a network configured to support multiple POs per PF and / or multiple PFs per DRX cycle is more flexible and provides more options for reconfiguring the UE to avoid paging conflicts than a network not configured to support multiple POs per PF and / or multiple PFs per DRX cycle. For illustrative purposes, we assume the UE determines that the paging configuration for NW1 should be modified to avoid paging conflicts.

[0380] In step 3, the UE requests to release / suspend the connection with NW1. The UE can provide NW1 with an indication to request the PO to skip or modify the paging configuration using any of the methods described herein. Alternatively, this RRC connection release / suspension request can be implemented using a UE Assistance Information procedure, where the request to release / suspension the connection corresponds to the transmission of a UEAssistanceInformation message. The UEAssistanceInformation message may include releasePreference information indicating the preferred state of the UE. The UEAssistanceInformation message may also include an estimate of the time the UE expects to be away from the network; for example, pauseDuration; thereby allowing the network to adjust its behavior, such as suspending paging, when the UE is away from the network. Example ReleasePreforence information that may be included in the UEAssistanceInformation message is shown in code examples 7A and 7B in the appendix. The UEAssistanceInformation message may also include preferred values ​​for one or more paging configuration parameters; these paging configuration parameters include, for example: a preferred PagingCycle, a preferred UE_ID to be used in the PO / PF calculation, an index i_s corresponding to a preferred PO monitored in the PF, and an offset to be used in the PF calculation. Example PagingPreference information that can be included in the UEAssistanceInformation message is shown in code examples 6A and 6B in the appendix.

[0381] In step 4, NW1 determines whether to accept the paging modification request from the UE. For illustrative purposes, we assume that NW1 accepts the paging modification request. NW1 responds to the paging modification request with an acknowledgment. NW1 may provide this acknowledgment using any of the methods described herein. In this example, the acknowledgment is provided in the RRRCRelease message.

[0382] In step 5, the UE applies the modified paging configuration to NW1 and continues to establish an RRC connection with NW2.

[0383] In step 6, the UE and NW2 perform UL / DL transmission.

[0384] Autonomous RRC Release / Suspend

[0385] In scenarios where one of the USIMs is in RRC_CONNECTED mode, the UE can autonomously release or suspend the RRC connection to prevent (or reduce the likelihood of) conflicts with monitoring timing and transmission opportunities associated with an AS procedure performed against another USIM. The UE informs the network of its intention to release / suspend the RRC connection and then autonomously transitions to the desired state. The UE can also provide the network with an estimate of its expected time away from the network; for example, pauseDuration; thus allowing the network to adjust its behavior, such as suspending paging, when the UE is away from the network.

[0386] When a UE performs a state transition, a "negotiated" configuration can be applied. The "negotiated" configuration can be based on Release Assist Information (RAI) that signals the network before the UE performs a voluntary release or suspension of the RRC connection. The RAI can include preferred values ​​for one or more paging configuration parameters, such as: a preferred PagingCycle, a preferred UE_ID to be used in the PO / PF calculation, an index i_s corresponding to a preferred PO monitored in the PF, and an offset to be used in the PF calculation.

[0387] Receiving preference information can be treated as a command by the network, in which case the network applies the values ​​of these preferred parameters when it receives an RRC connection release / pause indication. Alternatively, receiving preference information can be treated as a request by the network, in which case the network can accept, reject, or override the request and provide the UE with a response indicating its decision. Furthermore, in another alternative, the network can respond by providing the UE with a "negotiated" configuration applied when the UE voluntarily releases / pauses the RRC connection.

[0388] For UE transition to RRC_INACTIVE, the "negotiated" configuration can be based on SuspendConfig. See Code Example 4 in the appendix, which shows an example "negotiated" SuspendConfig that has been expanded to optionally include the preferred PagingCycle, the preferred UE_ID to be used in PO / PF calculations, the index i_s corresponding to the preferred PO monitored in the PF, and the offset to be used in the PF calculations.

[0389] For UE transitions to RRC_IDLE, the complete set of parameters in the negotiated SuspendConfig is not applicable. Therefore, the UE can ignore those inapplicable parameters; for example, full-RNTI, short-RNTI, ran-PagingCycle, ran-NotificationAreaInfo, t380, and nextHopChainingCount. Alternatively, a "negotiated" ReleaseConfig can be defined that includes only the parameters applicable to the UE transition to RRC_IDLE. Code example 5 illustrates an example "negotiated" ReleaseConfig.

[0390] In some scenarios, after transitioning to RRC_INACTIVE due to activity on another USIM, the UE may be unable to perform AS procedures such as paging surveillance and RAN-based Notification Area Update (RNAU). This could cause the network to incorrectly assume a failure, potentially leading to unnecessary corrective actions and distortion of call statistics maintained by the network. To prevent this, we recommend releasing the RRC_INACTIVE configuration if the UE does not restore connectivity within the configured duration. In one example, this duration corresponds to the value of timer t380. If the UE does not restore connectivity before t380 expires, the UE releases the RRC_INACTIVE configuration and transitions to RRC_IDLE. The UE state machine maintained by the network also transitions to RRC_IDLE. In another example, a separate timer, inactivityTimer, can be confined to this purpose and will be signaled to the UE as part of the "negotiated" SuspendConfig.

[0391] Figure 26 This is an illustration of a scenario where a multi-USIM UE in RRC_CONNECTED mode of NW1 receives a trigger to establish an RRC connection with NW2. This trigger requires the UE to autonomously release / suspend the RRC connection with NW1.

[0392] exist Figure 26In step 1, the UE and NW1 are in the RRC_CONNECTED state and are performing UL / DL transmission and reception.

[0393] In step 2, the UE signals the RAI to the NW1 to indicate its preference for one or more parameters to apply when it performs an autonomous RRC release / pause. The RAI information can be signaled using a new RRC message (e.g., RRC Release Assistance Information). Alternatively, the signaling of the RAI can be implemented using a UE Assistance Information procedure, where the signaling of the RAI corresponds to the transmission of a UE Assistance Information message. The UE Assistance Information message may include preferred values ​​for one or more paging configuration parameters, such as: a preferred Paging Cycle, a preferred UE_ID to be used in PO / PF calculations, an index i_s corresponding to a preferred PO monitored in the PF, and an offset to be used in the PF calculations. Example Paging Preference information that may be included in the UE Assistance Information message is shown in code examples 6A and 6B in the appendix.

[0394] In step 3, the UE receives a response from NW1 indicating the "negotiated" configuration to be applied when it performs an autonomous RRC release / pause.

[0395] In step 4, the UE receives a trigger to establish a connection with NW2.

[0396] In step 5, the UE sends NW1 to indicate that it will perform an autonomous RRC connection release / pause. This RRC connection release / pause indication can be implemented as an RRCRelease message transmitted from the UE to the network. Alternatively, a new RRC message can be used; for example, RRCReleaseIndication. And in yet another alternative, the RRC connection release / pause indication can be implemented using a UE Assistance Information procedure, where the RRC connection release / pause indication corresponds to the transmission of a UEAssistanceInformation message. The UEAssistanceInformation message may include releasePreference information indicating the UE's preferred state. The UEAssistanceInformation message may also include an estimate of the time the UE expects to be away from the network; for example, pauseDuration; thereby allowing the network to adjust its behavior, such as suspending paging, when the UE is away from the network. Example ReleasePreference information that can be included in the UEAssistanceInformation message is shown in code examples 7A and 7B in the appendix.

[0397] In step 6, the UE transitions to RRC_IDLE / RRC_INACTIVE and applies the "negotiated" configuration. If the UE is in the RRC_INACTIVE state and SuspendConfig includes a non-zero inactivityTimer value, the UE starts the inactivity timer.

[0398] In step 7, the UE establishes an RRC connection with NW2.

[0399] In step 8, the UE and NW2 perform UL / DL transmission.

[0400] In step 9, if the UE is in the RRC_INACTIVE state for NW1, but cannot execute the AS procedure due to the activity of NW2, then when the inactivity timer expires, the UE transitions to the RRC_IDLE state for NW1.

[0401] C-DRX Modification Request

[0402] In scenarios where one of the USIMs is in RRC_CONNECTED mode, the UE can request modifications to the C-DRX configuration to prevent (or reduce the likelihood of) conflicts with monitoring timing and transmission opportunities associated with an AS procedure performed by another USIM.

[0403] Dynamic Capability Signaling

[0404] For certain RAT concurrency scenarios and device capabilities, such as EN-DC+NR SA with dual RX / dual TX devices, one transceiver can be used for the MCG of the first USIM, while another transceiver can be used for the NR SCG of the first USIM or the NR SA cell of another USIM. When the second transceiver is being used for the NR SA cell of another USIM, it may not be able to be used for the NR SCG of the first USIM, thus causing a conflict. To avoid conflicts in such scenarios, the UE can provide an indication to the network to inform the network of the change in its DC capabilities caused by the UE using a shared transceiver to maintain a connection with another network.

[0405] UE Assistance Information Signaling

[0406] When configured to do so, the UE can signal to the network via UEAssistanceInformation as described in TS 38.300 Release 16. We propose that this process can be extended to include UE Assistance Information for multiple USIM UEs. Multiple USIM Assistance Information may include the number of USIMs supported by the UE, the preferred DRX / paging configuration supported in RRC_IDLE / RRC_INACTIVE modes, a list of paging reasons / paging rules for enabling paging filtering, etc. Examples of multiple USIM Assistance Information are shown in Code Examples 6A and 6B in the appendix.

[0407] A UE capable of providing multiple USIM auxiliary information in RRC_CONNECTED mode can initiate this procedure in several situations, including when performing initial access, when paging collisions for monitoring timing and transmission opportunities are determined to occur based on the UE configuration for multiple USIMs, when one or more collisions are detected, when starting an AS procedure for another USIM, when transitioning to the RRC_CONNECTED state for another USIM, when configuring a DC for another USIM, and so on.

[0408] An example procedure for providing multiple USIM auxiliary information can be defined as follows.

[0409] When initiating this process, the UE should:

[0410] 1> If configured to provide multiple USIM auxiliary information:

[0411] 2> If the UE has not transmitted a UEAssistanceInformation message with multiUSIM-Assistance since it was configured to provide multiUSIM-Assistance information; or

[0412] 2> If the current preference

[0413] 3> Initiate the transmission of UEAssistanceInformation messages to provide multiple USIM assistance information.

[0414] The UE should configure the content of the UEAssistanceInformation message as follows:

[0415] 1> If the transmission of a UEAssistanceInformation message is initiated to provide multiple USIM assistance information:

[0416] 2> Include multiUSIMAssistanceInformation in the UEAssistanceInformation message;

[0417] 2> Set numUSIM to the number of USIMs used by the UE;

[0418] 2> Set the pagingCycle to the desired paging cycle;

[0419] 2> Set UE_ID to the expected value of UE_ID to be used in PO and PF calculations;

[0420] 2> Set i_s to the value corresponding to the index of the desired PO;

[0421] 2> Set the offset to a value corresponding to the desired offset to be used in the PF calculation.

[0422] The UE should submit the UEAssistanceInformation message to a lower layer for transmission. See code examples 6A and 6B in the appendix.

[0423] We propose extending the UE auxiliary information procedure to allow multiple USIMs to transition from RRC_CONNECTED to other states to avoid conflicts with monitoring timing and transmission opportunities associated with another USIM. ReleasePreference information can include an estimate of the time the UE expects to be away from the network; for example, pauseDuration. Example ReleasePreference information is shown in code examples 7A and 7B in the appendix. Alternatively, ReleasePreference information can be implemented as a field in the multiple USIM auxiliary information.

[0424] UE Request Network to Stop Paging UE

[0425] In some scenarios, a UE might be busy using services associated with a first USIM and receiving a paging message associated with a second USIM. In this scenario, the UE can request the network associated with the second USIM to stop paging the UE to avoid wasting paging resources. For example, a multi-USIM UE might be receiving a voice call using the service of USIM1 and then receiving a paging message associated with USIM2. Instead of ignoring the paging message associated with USIM2 and wasting network resources, the UE can send an RRC message (e.g., RRCSetupRequest, RRCResumeRequest, or RRCResumeRequest1) to the RAN node of the USIM2 network, informing the network to stop paging the UE.

[0426] In this message, the UE may include the following indication: it informs the network not to page the UE until the UE disables the feature by sending another RRC message to the network. Alternatively, the UE may provide the network with the duration for which it will stop pagering the UE, and the network may resume pagering the UE after that duration expires. Furthermore, the RAN node may need to transmit the UE's preferences to the CN, so that the CN is also aware that pagering the UE has been stopped.

[0427] Figure 27 This is a sample UE request call flow for stopping paging. Figure 27 In step 1, the UE is in use, for example, in the RRC_CONNECTED state with NW1 (USIM1) and in the RRC_IDLE or RRC_INACTIVE state with NW2 (USIM2).

[0428] In step 2, data can be used for USIM2, and NW2 pages the UE. The paging message may include a paging reason.

[0429] In step 3, based on the paging reason, the UE wants to continue using the service of NW1 and sends an RRC message to NW2 indicating that paging of the UE should be temporarily suspended. The UE may also include the duration for which NW2 should suspend paging of the UE. After the duration expires, NW2 may resume paging of the UE. Alternatively, paging may be suspended indefinitely; that is, until the UE sends a request to re-enable paging.

[0430] In step 4, NW2 confirms that it has received a stop paging instruction from the UE. NW2 can provide a new value for the duration and return that value to the UE.

[0431] In step 5, the gNB of NW2 saves the indication and duration in the UE context stored by the gNB for the UE.

[0432] In step 6, if the UE is in the RRC_IDLE or RRC_INACTIVE state, the gNB can send an N2 / NAS message to the CN of NW2, which includes a stop paging indication and a duration.

[0433] In step 7, the UE determines that it wants to receive paging from NW2 and sends an RRC message to NW2 with an indication to resume paging of the UE.

[0434] In step 8, NW2 confirms that it has received a paging recovery instruction from the UE.

[0435] In step 9, the gNB updates the UE context to resume paging.

[0436] In step 10, if the UE is in the RRC_IDLE or RRC_INACTIVE state, the gNB can send an N2 / NAS message to the CN of NW2, including a paging recovery indication.

[0437] In another alternative, the UE can send an RRC message including a busy indication to the RAN node of the USIM2 network to inform the network that the UE will not respond to paging. This message can correspond to an RRCSetupRequest, RRCResumeRequest, or RRCResumeRequest1 message, where the recovery reason is set to a value indicating that the UE is busy, such as "busy indication".

[0438] Network Paging Filtering

[0439] The network can further enhance the paging process by allowing the UE to provide information that the network can use to filter paging requests based on the established paging reason. During this process, the UE sends network assistance information, which provides the network with paging filters to determine whether to page the UE. The UE can provide this assistance information as part of the RRC signaling, and the RAN node informs the CN if necessary.

[0440] A paging filter can be a list of paging reasons that a UE may or may not want to receive a paging message. The scope of a paging filter depends on the granularity of the paging reason. Alternatively, a paging filter can be a set of rules that tells the network whether to page the UE.

[0441] Figure 28 This is a call flow requested by an example UE with paging filtering enabled. Figure 28In step 1, the UE requests to enable paging filtering in the NW2 and sends an RRC message to the gNB of the NW2. In this request, the UE may provide a list of paging reasons for which it might want to be paged. Alternatively, the UE may indicate paging reasons for which it does not want to be paged. In another alternative, the UE may include a list of paging rules indicating what type of DL data it wants to receive paging for. This indication and the list of paging reasons may be part of auxiliary information provided by the UE to the NW2 to enhance multi-USIM operation. The auxiliary information can be provided to the gNB using a UE auxiliary information procedure, where the signaling of the auxiliary information corresponds to the transmission of a UEAssistanceInformation message including paging reasons for which the UE should be paged.

[0442] In step 2, the gNB acknowledges receipt of auxiliary information from the UE. This acknowledgment can be provided using RRC signaling. Alternatively, acknowledgment can be provided by a lower layer that has successfully received a PDU carrying the request.

[0443] In step 3, the gNB can send an N2 / NAS message to the CN of NW2 to enable paging / data filtering for the UE in the CN. If the UE is in the RRC_IDLE state, this message is used to enable paging filtering for the UE in the CN. If the UE is in the RRC_INACTVE state, this message is used to enable data filtering for the UE in the RAN.

[0444] In step 4, some time has passed.

[0445] In step 5, downlink data can be used by the UE in NW2. If CN paging / data filtering is not enabled for the UE, the CN will page the UE by sending a paging request to the gNB if the UE is in the RRC_IDLE state, or the CN will send downlink data to the gNB if the UE is in the RRC_INACTIVE state.

[0446] In step 6, the gNB checks the paging request / downlink data and determines whether the UE should be paged.

[0447] In step 7, if the gNB determines in step 6 that the UE should be paged, then the gNB transmits a paging message to the UE. This paging message may include the paging reason and other information about the paging.

[0448] In step 8, if the gNB determines in step 6 that the UE should not be paged, the gNB may transmit an N2 / NAS message to the CN to indicate that paging requests / downlink data are being filtered and the UE is busy. This message may also be used to enable paging / data filtering for the UE in the CN if the CN was not previously informed in step 3 that the UE expects certain paging requests or downlink data to be filtered.

[0449] In step 9, after a certain period of time, the UE sends an RRC message to disable paging filtering. Alternatively, a timer expiration can be used to disable paging filtering. The value used for the timer can be signaled to the network by the UE. For example, the RRC message transmitted in step 1 of this procedure may optionally include the timer value. If the timer value is not included, the network assumes that paging filtering is enabled until the UE sends an RRC message to disable paging filtering. When a timer is configured, the UE can send an RRC message to disable paging filtering before the timer expires.

[0450] In step 10, if paging filtering was previously enabled, the gNB can send an N2 / NAS message to disable paging filtering.

[0451] Collision Resolution Scheme

[0452] In this section, we define a class of schemes that can be used to resolve conflicts. These schemes are applicable to scenarios where the UE determines that a conflict has occurred (or is about to occur). The UE can determine when a conflict has occurred or when a conflict will occur based on UE configurations for multiple USIMs and / or feedback from lower layers of access public radio and baseband components, where UE configurations include, for example, paging configurations, SMTC configurations, SI-SchedulingInfo configurations, C-DRX configurations, etc. The proposed schemes include a description of the actions taken by the UE to resolve the conflict; for example, determining which AS procedure to execute, and a description of subsequent UE actions that can be taken to adequately recover from the conflict. The conflict resolution schemes described in this section can be used alone or in combination with the conflict avoidance schemes described herein.

[0453] Rule-Based Collision Resolution

[0454] For scenarios where conflicts have already occurred or are about to occur, rule-based conflict resolution methods can be used. When a conflict occurs, the UE uses a set of rules to determine which AS procedure to execute. These rules can be defined based on standards, user preferences, and / or network configuration.

[0455] For example, priorities can be assigned to different AS procedure types. When a conflict occurs, the UE executes the AS procedure with the higher priority. Table 6 in the appendix (Priority Ranking Based on AS Procedures) is an example of how AS procedures for UEs in the RRC_IDLE / RRC_INACTIVE state can be prioritized. In this example, the MIB / SIB1 measurements and reads performed as part of the cell (re)selection procedure and PLMN selection procedure are determined based on the priority of the respective procedure.

[0456] Alternatively, priority can be based on the action the UE is performing, regardless of the procedure for which that action is being performed. For the example shown in Table 7 of the Appendix (Priority Ranking Based on UE Actions), readings of MIB / SIB1 as part of a cell (re)selection procedure are given the same priority as when performing an SI acquisition for the serving cell; and all measurements are performed with the same priority, regardless of the procedure for which those measurements are being performed.

[0457] Priority can also be based on the USIM that triggered the process. The priority of the USIM can be determined based on user preferences (e.g., assigned by the user via a UE application) or based on the physical slot in which the USIM is inserted. USIM-based priority can be used alone or in combination with other priority ranking schemes described herein.

[0458] For example, an iterative method can be executed, where process-based priority sorting is performed first. And when multiple USIMs with the same priority are being executed simultaneously, USIM-based priority sorting can be used to break down processes such as... Figure 29 The connections shown.

[0459] Prioritization can be based on the RRC state of the USIM against which the AS procedure is executed. For example, an AS procedure executed against a USIM in the RRC_CONNECTED state can be given a higher priority than an AS procedure executed against a USIM in the RRC_IDLE / RRC_INACTIVE state. Different priorities can also be assigned to the RRC_IDLE and RRC_INACTIVE states, allowing an AS procedure executed against a USIM in RRC_INACTIVE mode to have a higher priority than an AS procedure executed against a USIM in RRC_IDLE mode, or vice versa.

[0460] Furthermore, in another aspect of this scheme, AS procedures that need to transition to RRC_CONNECTED mode (e.g., RRC connection establishment / recovery) can be given higher priority than idle mode procedures (e.g., paging, SI acquisition, PLMN selection, cell (re)selection). If another USIM is already in RRC_CONNECTED mode, the priority of the service establishing or recovering an RRC connection for it can be considered when determining which USIM / AS procedure to give higher priority. For example, an RRC connection establishment procedure with an EstablishmentCause equal to "emergency" or "highPriorityAccess" can have higher priority than an AS procedure used for a USIM in RRC_CONNECTED state.

[0461] You can also consider the RAT that is currently performing the AS process for it. For example, the NR process can be given higher priority than LTE, WCDMA, GSM, etc., as shown in Table 8 of the appendix (Priority Ranking Based on RAT).

[0462] Following a conflict, the UE can take actions to recover from it. For example, if the SI acquisition procedure was not performed due to the conflict, the UE can perform the RACH-based SI acquisition procedure described herein. In scenarios where the PO is missed due to the conflict, the UE can perform the SMS acquisition procedure described herein to ensure that the UE does not miss PWS notifications and / or SI change indications. An on-demand paging procedure can also be performed to ensure that the UE does not miss MT calls and / or data.

[0463] RACH-Based SI Acquisition

[0464] If the UE is unable to monitor the DL during the SI window due to a conflict, a RACH-based SI acquisition procedure can be used, where the requested SIB is provided in the RACH response; for example, Msg4, Msg2, or MsgB. The UE can trigger a RACH-based SI acquisition procedure when the AS procedure for another USIM is completed. UE configurations for multiple USIMs (e.g., paging configuration, SMTC configuration, SI-SchedulingInfo configuration, C-DRX configuration, etc.) can be used to determine when a RACH-based SI acquisition should be performed to avoid conflicts with monitoring timing and transmission opportunities associated with an AS procedure performed for another USIM.

[0465] In one example, a 4-step RACH procedure is used, where Msg3 includes an indication of the requested SIB. This indication can be included in an RRC message transmitted as part of Msg3. Therefore, the Msg4 response provided by the network includes the requested SIB.

[0466] In another example, a 4-step RACH procedure is used, however only steps 1 and 2 are employed. The mapping between the SIB and the preamble and / or RACH timing allows Msg1 to implicitly indicate the requested SIB, which is provided by the network in the Msg2 response. Alternatively, this mapping could be between the SI message and the preamble and / or RACH timing. In this case, the Msg2 response includes the SIB configured for the requested SI message.

[0467] In yet another example, a two-step RACH procedure is used, where MsgA includes an indication of the requested SIB provided by the network in the MsgB response.

[0468] Short Message Acquisition

[0469] Short messages are used to provide the UE with an indication of an SI modification that will occur in the next modification period. If the UE is unable to monitor the paging DCI during its PO period due to a conflict, it may miss this indication. Depending on the UE and network configuration, the modification period can consist of multiple DRX cycles, such as... Figure 30 As shown, the UE monitors one PO every DRX cycle.

[0470] From a network perspective, additional POs can be configured and monitored by other UEs. If a UE is unable to monitor paging DCI during its configured PO due to a conflict, it can monitor a PO configured for another UE to receive short messages.

[0471] SI change indications can be repeated within the preceding modification period. If the network is configured such that the SI change indication is repeated in all POs during the preceding modification period, the UE will be able to receive the SI change indication, provided that it can monitor at least one of its configured POs to receive short messages during the modification period.

[0472] To prevent the UE from unnecessarily monitoring additional POs, the UE can monitor additional POs only if it cannot monitor all of its POs that appear during the modification period. In this scenario, the UE can choose to monitor any PO that appears after its last configured PO during the modification period. If the UE cannot monitor any POs during the modification period when receiving SMS messages, the UE should obtain SIB1 to get the value label of the SIB being broadcast in the serving cell to ensure that its SIB is still valid; for example, the value label of the SIB broadcast by the serving cell matches the value label of the SIB being used by the UE. If the value label of a given SIB does not match, the UE should obtain the modified SIB from the network.

[0473] If the network is configured such that the SI change indication is not repeated across all POs during the preceding modification period, the UE may miss the SI change indication if it misses any PO during that modification period. In this scenario, the UE can choose to monitor any POs that appear after the missed PO. And if the UE cannot monitor any POs that appear during the DRX period, the UE should obtain SIB1 to get the value label of the SIB being broadcast in the serving cell to ensure that its SI is still valid, and subsequently obtain any modified SIBs from the network.

[0474] Short messages are also used to provide PWS notifications to the UE. UEs with ETWS or CMAS functionality that are in the RRC_IDLE or RRC_INACTIVE state need to monitor for indications regarding PWS notifications during their own paging time in each DRX cycle. If a PO is missed due to a conflict, the UE can monitor for PWS notifications in any PO that appears after the missed PO in its DRX cycle.

[0475] On-Demand Paging

[0476] To ensure the UE does not miss MT calls and / or data, the UE can perform an on-demand paging procedure, whereby the UE (re)establishes an AS connection with the network used for USIM when a configured number of POs are missed due to paging conflicts. The network can configure on-demand paging for the UE based on indications that the UE is configured with multiple USIMs or on explicit requests from the UE. The number of missed POs used to control when the on-demand paging procedure is performed can be cell-specific and broadcast as part of the SI, or UE-specific and signaled using dedicated signaling.

[0477] When (re)establishing an AS connection for on-demand paging, a new EstablishmentCause / ResumeCause (e.g., onDemandPaging) can be used to indicate this to the network. Upon (re)establishing the connection, if there is pending MT data for the UE, the network will begin UL / DL transmission. If not, the network can release or suspend the RRC connection.

[0478] User Interface

[0479] exist Figure 31This paper proposes a user interface that users can use to configure a UE for MUSIM operation. For example, the user interface can be used to enable / disable a given USIM. In one example, checkboxes are used to indicate the enabled / disabled status of a given USIM. The user interface can also be used to assign priorities to USIMs, where the assigned priorities can be used to determine when to ignore paging for a given network or when to perform rule-based conflict resolution as described herein. In one example, text boxes can be used to assign priorities to a given USIM. Priorities can be assigned numerical values, such as 1, 2, 3, as enumerated values; for example, high, medium, low, etc.

[0480] The user interface can also be used to provide notifications to users when an MT or MO call needs to be resumed / established for a given USIM; and users can provide a response to accept or reject the request to resume / establish the call. The notification may also include metadata related to the MT / MO call; for example, to inform the user of the associated service, paging reason, etc. For example, if a UE communicating with network 1 via USIM1 receives a paging request for network 2 via USIM2, a notification informing the user of the call on USIM 2 can be provided, such as... Figure 32 As shown. The user can then accept or reject incoming calls to USIM2.

[0481] In another example, if the UE communicates with network 1 via USIM1, and an application running on the UE needs to send / receive data to network 2 via USIM2, a notification can be provided to the network informing the user that a connection to USIM2 needs to be established / restored. Similar to... Figure 32 The notification shown can be used to allow users to accept / reject calls to USIM2.

[0482] Example Environment

[0483] The 3rd Generation Partnership Project (3GPP) has developed technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, including studies on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE Advanced. 3GPP has begun working on the standardization of next-generation cellular technologies known as New Radio (NR) (also called “5G”). The development of the 3GPP NR standard is expected to include the definition of next-generation radio access technologies (New RATs), which are anticipated to include new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. This flexible radio access is expected to include new non-backward-compatible radio access in the new spectrum below 6 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with different needs. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectrum, which will provide opportunities for ultra-mobile broadband access for applications such as indoor spaces and hotspots. Specifically, it is expected that ultra-mobile broadband and flexible radio access below 6 GHz will share a common design framework, while having specific design optimizations for centimeter waves and millimeter waves.

[0484] 3GPP has identified a variety of use cases that NR is expected to support, resulting in diverse user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high-bandwidth access indoors, broadband access in congested areas, 50+ Mbps everywhere, ultra-low-cost broadband access, mobile broadband in vehicles); critical communications; massive machine-type communications; network operations (e.g., network slicing, routing, migration and interworking, energy saving); and enhanced vehicle-to-everything (eV2X) communications, which may include any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle-to-other-entity communications. Specific services and applications within these categories include, for example: surveillance and sensor networks, remote device control, two-way remote control, personal cloud computing, video streaming, cloud-based wireless offices, first responder connectivity, automotive electronic calling, disaster alerts, real-time gaming, multi-person video calling, autonomous driving, augmented reality, haptic internet, and virtual reality, among others. This document considers all of these and other use cases.

[0485] Figure 33AAn embodiment of an example communication system 100 is illustrated, in which the methods and apparatus described and claimed herein may be specifically embodied. As shown, the example communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f and / or 102g (which may generally or commonly be referred to as WTRU 102), radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and a V2X server (or ProSe function and server) 113. However, it should be understood that any number of WTRUs, base stations, networks and / or network elements are contemplated in the embodiments disclosed herein. Each of WTRU 102a, 102b, 102c, 102d, 102e, 102f, and 102g can be any type of device or apparatus configured to operate and / or communicate in a wireless environment. While each of WTRU 102a, 102b, 102c, 102d, 102e, 102f, and 102g... Figures 33A-33E While described as a handheld wireless communication device, it should be understood that, in the context of the diverse use cases envisioned for 5G wireless communication, each WTRU may include or be embodied as any type of device or apparatus configured to transmit and / or receive wireless signals, including, by way of example only, user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cellular phone, personal digital assistant (PDA), smartphone, laptop, tablet computer, netbook, notebook computer, personal computer, wireless sensor, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical devices or e-health devices, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains, or airplanes).

[0486] The communication system 100 may also include base stations 114a and 114b. Base station 114a may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112). Base station 114b may be any type of device configured to wired and / or wirelessly interface with at least one of RRHs (Remote Radio Headers) 118a and 118b, TRPs (Transmit and Receive Points) 119a and 119b, and / or RSUs (Roadside Units) 120a and 120b to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or V2X servers (or ProSe functions and servers) 113). RRH 118a and 118b can be any type of device configured to wirelessly interface with at least one of WTRU 102c to facilitate access to one or more communication networks, such as core network 106 / 107 / 109, Internet 110, and / or other network 112. TRP 119a and 119b can be any type of device configured to wirelessly interface with at least one of WTRU 102d to facilitate access to one or more communication networks, such as core network 106 / 107 / 109, Internet 110, and / or other network 112. RSU 120a and 120b can be any type of device configured to wirelessly interface with at least one of WTRU 102e or 102f to facilitate access to one or more communication networks, such as core network 106 / 107 / 109, Internet 110, other network 112, and / or V2X server (or ProSe function and server) 113. By way of example, base stations 114a and 114b can be transceiver base stations (BTS), Node B, evolved Node B, home Node B, home evolved Node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0487] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographical area, which may be referred to as a cell (not shown). Base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, for example, one transceiver per sector of the cell. In one implementation, base station 114a may employ multiple-input multiple-output (MIMO) technology, thus enabling the use of multiple transceivers for each sector of the cell.

[0488] Base station 114a can communicate with one or more of WTRUs 102a, 102b, and 102c via air interfaces 115 / 116 / 117, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115 / 116 / 117.

[0489] Base station 114b can communicate with one or more of RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a and 120b via wired or air interfaces 115b / 116b / 117b. These wired or air interfaces can be any suitable wired communication link (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115b / 116b / 117b.

[0490] RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a, 120b can communicate with one or more of WTRU 102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115c / 116c / 117c.

[0491] WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g can communicate with each other via air interface 115d / 116d / 117d (not shown in the attached figures), which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115d / 116d / 117d.

[0492] More specifically, as noted above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 103 / 104 / 105 and WTRU 102a, 102b, 102c or RRH 118a, 118b, TRP 119a, 119b and RSU 120a, 120b and WTRU 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0493] In one implementation, base station 114a and WTRUs 102a, 102b, 102c or RRH 118a, 118b in RAN 103b / 104b / 105b, TRP 119a, 119b and / or RSU 120a, 120b, and WTRUs 102c, 102d can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE Advanced (LTE-A) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. In the future, air interfaces 115 / 116 / 117 can implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and V2X technologies and interfaces (such as sidelink communication). 3GPP NR technology includes NR V2X technologies and interfaces (such as sidelink communication).

[0494] In one implementation, base station 114a in RAN 103 / 104 / 105 and WTRU 102a, 102b, 102c or RRH 118a, 118b, TRP 119a, 119b and / or RSU 120a, 120b, and WTRU 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b can implement radio technologies such as IEEE 802.16 (e.g., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0495] Figure 33ABase station 114c can be, for example, a wireless router, a home node B, a home evolution node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas such as commercial locations, homes, vehicles, and campuses. In one embodiment, base station 114c and WTRU 102e can implement radio technologies (such as IEEE 802.11) to establish a wireless local area network (WLAN). In one embodiment, base station 114c and WTRU 102d can implement radio technologies (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114c and WTRU 102e can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish picocells or femtocells. Figure 33A As shown, base station 114b can have a direct connection to the Internet 110. Therefore, base station 114c does not need to access the Internet 110 via core network 106 / 107 / 109.

[0496] RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b can communicate with core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. For example, core network 106 / 107 / 109 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication.

[0497] Although not in Figure 33A As shown, but it should be understood that RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs using the same RAT as or a different RAT than RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b. For example, in addition to being connected to RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b, which may be utilizing E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) using GSM radio technology.

[0498] Core networks 106 / 107 / 109 can also act as gateways for WTRUs 102a, 102b, 102c, 102d, and 102e to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs, which may use the same RAT as RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0499] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities. For example, WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 33A The WTRU 102e shown can be configured to communicate with a base station 114a that can employ cellular-based radio technology and with a base station 114c that can employ IEEE 802 radio technology.

[0500] Figure 33B This is a block diagram of an example apparatus or device (such as WTRU 102) configured for wireless communication according to the embodiments shown herein. Figure 33B As shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that, while remaining consistent with the implementation, WTRU 102 may include any sub-combination of the foregoing elements. Additionally, the implementation envisions that base stations 114a and 114b and / or the nodes that base stations 114a and 114b may represent (such as, but not limited to, transceiver stations (BTS), Node B, site controllers, access points (APs), home Node B, evolved home Node B (eNodeB), home evolved Node B (HeNB), home evolved Node B gateways, and proxy nodes, etc.) may include... Figure 33B The elements described herein, as well as some or all of the elements described herein.

[0501] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 33B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0502] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 115 / 116 / 117. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and receive both RF signals and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0503] Furthermore, although the transmitting / receiving element 122 is in Figure 33B While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interfaces 115 / 116 / 117.

[0504] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 may have multi-mode capability. Therefore, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via various RATs such as UTRA and IEEE 802.11.

[0505] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from the aforementioned components. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. Furthermore, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132), and store data in any type of suitable memory. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, a Memory Stick, a Secure Digital (SD) memory card, etc. In one implementation, processor 118 can access memory information that is never physically located on WTRU 102 (such as on a server or home computer (not shown)) and store the data in that memory.

[0506] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0507] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interfaces 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that, while remaining consistent with the implementation, the WTRU 102 may acquire location information using any suitable location determination method.

[0508] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral device 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, and so on.

[0509] WTRU 102 can be implemented in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, or vehicles (such as cars, trucks, trains, or airplanes). WTRU 102 can be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces (such as interconnect interfaces that may include one of the peripheral devices 138).

[0510] Figure 33C This is a system diagram of RAN 103 and core network 106 according to one implementation scheme. As mentioned above, RAN 103 can communicate with WTRUs 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. Figure 33C As shown, RAN 103 may include nodes B 140a, 140b, and 140c, each of which may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 115. Nodes B 140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a and 142b. It should be understood that RAN 103 may include any number of nodes B and RNCs while remaining consistent with the implementation scheme.

[0511] like Figure 33CAs shown, nodes B 140a and 140b can communicate with RNC 142a. Additionally, node B 140c can communicate with RNC 142b. Nodes B 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 142a and 142b can be configured to control its connected corresponding node B 140a, 140b, or 140c. Furthermore, each of RNCs 142a and 142b can be configured to perform or support other functionalities such as outer-loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.

[0512] Figure 33C The core network 106 shown may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0513] RNC 142a in RAN 103 can connect to MSC 146 in core network 106 via the IuCS interface. MSC 146 can connect to MGW 144. MSC 146 and MGW 144 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment.

[0514] RNC 142a in RAN 103 can also connect to SGSN 148 in core network 106 via IuPS interface. SGSN 148 can connect to GGSN 150. SGSN 148 and GGSN 150 can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

[0515] As described above, core network 106 can also be connected to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0516] Figure 33DThis is a system diagram of RAN 104 and core network 107 according to one implementation scheme. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0517] RAN 104 may include evolved Nodes B 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of evolved Nodes B while remaining consistent with the implementation scheme. Evolved Nodes B 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one implementation, evolved Nodes B 160a, 160b, and 160c may implement MIMO technology. Therefore, evolved Node B 160a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0518] Each of the evolved Nodes B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, etc. Figure 33D As shown, evolution nodes 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0519] Figure 33D The core network 107 shown may include a mobility management gateway (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0520] The MME 162 can connect to each of the evolved nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

[0521] Serving Gateway 164 can connect to each of the evolved Nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface. Serving Gateway 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. Serving Gateway 164 can also perform other functions, such as anchoring the user plane during handover between evolved Nodes B, triggering paging when downlink data is available to WTRUs 102a, 102b, and 102c, managing and storing the context of WTRUs 102a, 102b, and 102c, etc.

[0522] Service gateway 164 can also be connected to PDN gateway 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0523] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108, or can communicate with such an IP gateway. Furthermore, core network 107 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0524] Figure 33E This is a system diagram of RAN 105 and core network 109 according to one implementation scheme. RAN 105 may be an access service network (ASN) that communicates with WTRU 102a, 102b, and 102c via air interface 117 using IEEE 802.16 radio technology. As will be discussed further below, the different functional entities of WTRU 102a, 102b, and 102c, and the communication links between RAN 105 and core network 109 can be defined as reference points.

[0525] like Figure 33EAs shown, RAN 105 may include base stations 180a, 180b, 180c and ASN gateway 182; however, it should be understood that RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the implementation scheme. Base stations 180a, 180b, and 180c may each be associated with a specific cell in RAN 105 and may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 117. In one implementation, base stations 180a, 180b, and 180c may implement MIMO technology. Therefore, base station 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. Base stations 180a, 180b, and 180c may also provide mobility management functions such as handover triggering, tunnel establishment, radio resource management, traffic classification, Quality of Service (QoS) policy enforcement, etc. ASN Gateway 182 can be used as a service aggregation point and can be responsible for paging, subscriber profile caching, routing to core network 109, etc.

[0526] The air interface 117 between WTRUs 102a, 102b, and 102c and RAN 105 can be defined as an R1 reference point implementing the IEEE 802.16 specification. Furthermore, each of WTRUs 102a, 102b, and 102c can establish a logical interface (not shown) with the core network 109. The logical interface between WTRUs 102a, 102b, and 102c and the core network 109 can be defined as an R2 reference point, which can be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0527] The communication link between each of base stations 180a, 180b, and 180c can be defined as an R8 reference point, which includes protocols for facilitating WTRU handover and data transmission between the base stations. The communication link between base stations 180a, 180b, and 180c and ASN gateway 182 can be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of WTRUs 102a, 102b, and 102c.

[0528] like Figure 33EAs shown, RAN 105 can be connected to core network 109. The communication link between RAN 105 and core network 109 can be defined as an R3 reference point, which includes, for example, protocols for facilitating data transmission and mobility management capabilities. Core network 109 may include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, and Accounting (AAA) server 186, and a gateway 188. Although each of the foregoing elements is depicted as part of core network 109, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0529] MIP-HA manages IP addresses and enables WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. MIP-HA 184 provides WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110), facilitating communication between WTRUs 102a, 102b, and 102c and IP-enabled devices. AAA server 186 handles user authentication and user service support. Gateway 188 facilitates interoperability with other networks. For example, gateway 188 provides WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108), facilitating communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. In addition, gateway 188 can provide WTRU 102a, 102b, 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0530] although Figure 33E Although not shown, it should be understood that RAN 105 can connect to other ASNs, and core network 109 can connect to other core networks. The communication link between RAN 105 and other ASNs can be defined as an R4 reference point, which may include protocols for coordinating the mobility of WTRUs 102a, 102b, and 102c between RAN 105 and other ASNs. The communication link between core network 109 and other core networks can be defined as an R5 reference point, which may include protocols for facilitating interoperability between the home core network and the visited core network.

[0531] The content described herein and in Figure 33A , Figure 33C , Figure 33D and Figure 33EThe core network entities shown are identified by the names given to these entities in certain existing 3GPP specifications; however, it should be understood that these entities and functions may be identified by other names in the future, and some entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Therefore, in Figure 33A The specific network entities and functions described and illustrated in -E are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or to be defined in the future.

[0532] Figure 33F This is a block diagram of the example computing system 90, which can specifically illustrate... Figure 33A , Figure 33C , Figure 33D and Figure 33E The diagram illustrates one or more devices in a communication network, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other networks 112. The computing system 90 may include a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. These computer-readable instructions may be executed within a processor 91 to enable the computing system 90 to function. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to function within the communication network. Coprocessor 81 is an optional processor, distinct from main processor 91, that can perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 can receive, generate, and process data relating to the methods and apparatus disclosed herein.

[0533] In operation, processor 91 fetches instructions, decodes and executes them, and transfers information to and from other resources via the main data transfer path (system bus 80) of the computing system. This system bus connects components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0534] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. This type of memory includes circuitry that allows information to be stored and retrieved. ROM 93 typically contains stored data that cannot be easily modified. Data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 provides address translation functionality, translating virtual addresses into physical addresses as instructions are executed. The memory controller 92 also provides memory protection functionality that isolates processes within the system and separates system processes from user processes. Therefore, a program running in first mode can only access memory mapped through its own process virtual address space; it cannot access memory in another process's virtual address space unless inter-process memory sharing is configured.

[0535] In addition, the computing system 90 may include a peripheral device controller 83 responsible for passing instructions from the processor 91 to peripheral devices such as printer 94, keyboard 84, mouse 95 and disk drive 85.

[0536] A display 86, controlled by a display controller 96, is used to display visual output generated by a computing system 90. This visual output may include text, graphics, animated graphics, and video. The visual output can be provided in the form of a graphical user interface (GUI). The display 86 can be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touchpad. The display controller 96 includes the electronic components required to generate the video signals sent to the display 86.

[0537] Additionally, the computing system 90 may include a communication circuit system, such as a network adapter 97, which can be used to connect the computing system 90 to an external communication network, such as... Figures 33A-33EThe RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other networks 112 are used to enable the computing system 90 to communicate with other nodes or functional entities in these networks. A communication circuitry system, either separately or in conjunction with the processor 91, can be used to perform the transmit and receive steps of certain means, nodes, or functional entities described herein.

[0538] Figure 33G An embodiment of an exemplary communication system 111 is illustrated, which may specifically embody the methods and apparatus described herein and protected by the claims. As shown, the example communication system 111 may include Wireless Transmit / Receive Units (WTRUs) A, B, C, D, E, F, a base station, a V2X server, and RSUs A and B; however, it should be understood that the embodiments disclosed herein contemplate any number of WTRUs, base stations, networks, and / or network elements. One or more or all WTRUs A, B, C, D, E may be outside the network's range (e.g., outside the cell coverage boundary as shown by the dashed line in the figure). WTRUs A, B, C form a V2X group, with WTRU A as the group leader and WTRUs B and C as group members. WTRUs A, B, C, D, E, F may communicate via a Uu interface or a sidelink (PC5) interface.

[0539] It should be understood that any or all of the apparatuses, systems, methods, and processes described herein can be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), cause the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein can be implemented in the form of such computer-executable instructions that execute on a processor of an apparatus or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented using any non-transitory (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical disc storage devices, magnetic tape cartridges, magnetic tape, disk storage devices or other magnetic storage devices, or any other tangible or physical medium that can be used to store desired information and is accessible by a computing system.

[0540]

[0541]

[0542]

[0543]

[0544]

[0545]

[0546]

[0547]

[0548]

[0549]

[0550]

[0551]

[0552]

[0553]

[0554]

[0555]

[0556]

[0557]

[0558]

[0559]

[0560]

[0561]

[0562]

[0563]

[0564]

Claims

1. An apparatus for wireless communication, comprising a processor, a memory, and communication circuitry, the apparatus in communication with a first network and a second network via the communication circuitry, the apparatus further comprising a plurality of universal subscriber identity modules, the apparatus further comprising computer-executable instructions stored in the memory that, when executed by the processor, cause the apparatus to: establish a first connection with the first network, the first connection being a radio resource control (RRC) connection; detect a paging message from the second network, the paging message being a trigger to establish a second connection with the second network, the second connection being an RRC connection; establish the second connection with the second network in response to the paging message; and send a paging response to the second network, wherein the instructions further cause the apparatus to send one or more of the following to the second network: 1) an indication of one or more paging causes in which the apparatus is interested in receiving a paging message; and 2) an indication of one or more paging causes in which the apparatus is not interested in receiving a paging message.

2. The apparatus of claim 1, wherein the instructions further cause the apparatus to send one or more of the following to the second network: paging preference information including a preferred apparatus identifier; a period in which the apparatus does not monitor for paging; and a busy indication.

3. The apparatus of claim 2, wherein the instructions further cause the apparatus to monitor for paging from the second network during a paging occasion (PO) and a paging frame (PF) based on the preferred apparatus identifier.

4. The apparatus of claim 1, wherein: the paging response comprises a busy indication; the instructions further cause the apparatus to receive an acknowledgement from the second network that the busy indication was received and to continue using the connection with the first network. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​

Images