Method for handling imsi offset value and network entity thereof

Abstract

A method of handling (alternative) IMSI values for MUSIM UEs supporting paging timing conflict control in EPS networks is presented. For MUSIM UEs and EPS supporting paging timing conflict control, the MUSIM UE and network can request and negotiate an IMSI offset for the IMSI value of one of the USIM cards through the TAU or attach procedure. When lower layer failure occurs, the network can not successfully receive the tracking area update complete (or attach complete) message from the UE, so the network can not know which IMSI value the UE will use. Therefore, the network needs to use both possible (alternative) IMSI values when deriving the paging timing of the UE until one of the (alternative) IMSI values is considered invalid.

Description

Technical Field

[0001] The disclosed embodiments generally relate to wireless communication systems, and more specifically to processing alternative International Mobile Subscriber Identity (IMSI) values ​​for MUSIM UEs in EPS networks to support paging timing conflict control. Background Technology

[0002] Wireless communication networks have grown exponentially over the years. Long-term evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs due to simplified network architecture. LTE systems, also known as 4G systems, also provide seamless integration with legacy wireless networks such as GSM, CDMA, and the Universal Mobile Telecommunications System (UMTS). In LTE systems, the evolved universal terrestrial radio access network (E-UTRAN) comprises multiple evolved Node Bs (eNodeBs or eNBs) that communicate with multiple mobile stations known as user equipment (UEs). The 3rd generation partner project (3GPP) networks typically include a hybrid of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) committee has decided to focus future NGMN activities on defining the end-to-end requirements for 5G new radio (NR) systems. Base stations in a 5G NR system are called Next Generation Node-B (gNodeB or gNB).

[0003] The Non-Access Stratum (NAS) is used to transmit non-radio signaling between the UE and the Mobility Management Function (MME) or Access and Mobility Management Function (AMF) for LTE / NR access. NAS signaling connections can be established via the Attach process in 4G / LTE or the registration process in 5G / NR, which includes UE subscription and identification. The Universal Subscriber Identity Module (USIM) is one of several software applications residing in the UE, referred to as the Universal Integrated Circuit Card (UICC). As smartphones and services become more affordable, their users tend to use different mobile subscriptions (i.e., USIM cards) to meet travel, business, and personal needs. Many UEs now support multiple USIM cards (MUSIM) for simultaneous registration and operation on different USIMs. The International Mobile Subscriber Identity (IMSI) is used to interconnect with other networks in any mobile network. This unique 15-digit International Mobile Identity (IMSI) identifier, contained within the mobile device, allows roaming on mobile service operator networks. The IMSI is stored in the UICC and can be accessed via a USIM application.

[0004] In 4G paging, the timing is determined based on the IMSI (e.g., paging timing), and the UE monitors paging based on the "paging timing" derived from the IMS. However, for a MUSIM UE, the paging timings of multiple USIM cards may be the same. Therefore, if the MUSIM UE has only one set of radio frequency (RF) modules, it will not be able to monitor paging for two USIM cards. To address this issue, a feature supporting "paging timing conflict control" was introduced. The MUSIM UE and the network can request and negotiate an "IMSI Offset" for the IMSI value of one of the USIM cards via the TAU or attach process, allowing the paging timing of that USIM card to differ from the paging timings of other USIM cards within the same MUSIM UE. If the UE has already assigned an acceptable "IMSI Offset" value, the UE uses an "alternate IMSI value" to derive the paging timing. The "alternate IMSI value" is derived from both the "IMSI value" and the "alternate IMSI value". If the UE does not assign an acceptable "IMSI offset" value, the UE uses the "IMSI" value to deduce the paging timing.

[0005] However, if a low-level fault occurs before the network successfully receives a message tracking area update completion (or attachment completion), the network does not know whether the UE uses the "paging timing" derived from the previous (alternate) IMSI value before the attachment / TAU process or the "paging timing" derived from the (alternate) IMSI value after the attachment / TAU process to monitor paging.

[0006] Seeking solutions. Summary of the Invention

[0007] A method is proposed for handling (alternative) IMSI values ​​for MUSIM UEs supporting paging timing conflict control in EPS networks. For MUSIM UEs and EPS supporting paging timing conflict control, the MUSIM UE and the network can request and negotiate an IMSI offset for one of the USIM cards via TAU or attach process, allowing the paging timing of that USIM card to differ from that of other USIM cards in the same MUSIM UE. If the UE has already assigned an acceptable "IMSI offset" value, the UE uses an "alternative IMSI value" to derive the paging timing. The "alternative IMSI value" is derived from both the "IMSI value" and the "alternative IMSI value". If the UE has not assigned an acceptable "IMSI offset" value, the UE uses the "IMSI value" to derive the paging timing. When a low-level fault occurs, the network may fail to receive the Tracking Area Update Complete (or Attach Complete) message from the UE, and therefore the network does not know which (alternative) IMSI value the UE will use to derive the paging timing. Therefore, when deriving the paging sequence of the UE, the network needs to use two possible (alternative) IMSI values ​​until one of the (alternative) IMSI values ​​is deemed invalid.

[0008] In one embodiment, in a wireless communication network, a network entity receives a Tracking Area Update (TAU) request message from a User Equipment (UE). The UE supports multiple universal subscriber identity modules (MUSIM). The network entity determines whether the TAU request message includes an IMSI offset value requested by the UE for the USIM card. The network entity sends a Tracking Area Update Acceptance message to the UE. The TAU Acceptance message may or may not include the accepted IMSI offset value for the USIM card in response to the TAU Acceptance message. When the network does not receive a Tracking Area Update Complete message from the UE, the network entity uses both the previous (alternate) IMSI value and the updated (alternate) IMSI value of the USIM card to determine two paging sequences (paging timings). The network entity uses the determined paging sequences to page the UE.

[0009] In one embodiment, a method for processing IMSI values ​​is proposed. The method includes a network entity receiving a TAU request message from a UE in a wireless communication network; sending a TAU acceptance message to the UE, wherein the TAU acceptance message includes or does not include a negotiated IMSI offset value in response to the tracking area update request message; and when the network entity has not received a TAU completion message from the UE, determining a paging timing by considering both a previously valid IMSI parameter and a valid updated IMSI parameter to page the UE.

[0010] In another embodiment, a network entity for IMSI value processing is provided. This network entity includes a receiver for receiving a TAU request message from a UE via the network entity in a wireless communication network. The network entity includes a transmitter for sending a TAU acceptance message to the UE, wherein the TAU acceptance message includes or does not include a negotiated IMSI offset value in response to the TAU request message. The network entity further includes a paging processing circuit module for pageing the UE when the network entity has not received a TAU completion message from the UE, by determining the paging timing by considering both a previously valid IMSI parameter and a valid updated IMSI parameter.

[0011] This invention proposes an IMSI value processing method and its network entity, which achieves the beneficial effect of resolving paging timing conflicts.

[0012] Other embodiments and beneficial effects are described in the detailed description below. This summary is not intended to define the invention. The invention is defined by the claims. Attached Figure Description

[0013] The accompanying drawings illustrate embodiments of the invention, wherein the same numbers indicate the same components.

[0014] Figure 1 According to a novel aspect, user equipment and evolved packet systems or 5GS networks that process IMSI values ​​for MUSIM UEs to support paging timing conflict control features are illustrated.

[0015] Figure 2 This is a simplified block diagram of the UE and network entities according to various embodiments of the present invention.

[0016] Figure 3 An example is shown that can be used to derive the content of the IMSI for paging timing.

[0017] Figure 4 The diagram illustrates different scenarios in which the UE and network use the TAU / attach process to request and negotiate IMSI offset values.

[0018] Figure 5 According to a novel aspect, an embodiment of processing the IMSI offset value of a MUSIM UE for supporting paging timing conflict control in an EPS network is shown.

[0019] Figure 6 According to a novel aspect, another embodiment of processing the IMSI offset value of a MUSIM UE for supporting paging timing conflict control in an EPS network is shown.

[0020] Figure 7This is a flowchart of a method for processing the IMSI value of a MUSIM UE for supporting paging timing conflict control in an EPS network, according to a novel aspect of the present invention. Detailed Implementation

[0021] Reference is now made to some embodiments of the present invention, examples of which are described in the accompanying drawings.

[0022] Figure 1 A novel aspect is illustrated in schematic diagram 100 of user equipment and evolved packet system or 5GS processing IMSI values ​​for MUSIM UEs to support paging timing conflict control features. In a 3GPP network, multiple base stations (e.g., gNBs or eNBs) communicate with multiple mobile stations referred to as user equipment (UEs). Orthogonal Frequency Division Multiple Access (OFDMA) is chosen for its robustness to multipath fading, higher spectral efficiency, and bandwidth scalability as a downlink (DL) radio access scheme. The Physical Downlink Control Channel (PDCCH) is used for downlink scheduling. The Physical Downlink Shared Channel (PDSCH) is used for downlink data. Similarly, the Physical Uplink Control Channel (PUCCH) is used to carry uplink control information. The Physical Uplink Shared Channel (PUSCH) is used for uplink data. In addition, the physical random-access channel (PRACH) is used for contention-free RACH. On the other hand, NAS layer connections are used to transmit non-radio signaling between the UE and the MME or AMF for access.

[0023] exist Figure 1In this context, UE 101 supports MUSI to simultaneously attach / register and operate with EPS / 5GS 110 via different USIM cards. Two or more different USIMs can register to the same EPS, the same 5GS, different EPS, different 5GS, or one or more EPS and one or more 5GS, or even a network that is neither an EPS nor a 5GS. In 4G paging, timing (e.g., paging timing) is determined based on IMSI, and the UE monitors paging on the paging timing derived from the IMSI. However, for a MUSIM UE, multiple USIM cards may have the same paging timing. Therefore, if the MUSIM UE has only one set of RF modules, it will not be able to monitor paging for two USIM cards. To address this issue, a feature supporting "paging timing conflict control" is introduced. The MUSIM UE and the network can request and negotiate an "IMSI offset" for the IMSI value of one of the USIM cards via TAU or the attach process, allowing the paging timing of that USIM card to differ from the paging timings of other USIMs within the same MUSIM UE. (If the UE has already assigned an accepted “IMSI offset” value, the UE uses the “alternate IMSI value” to derive the paging timing. The “alternate IMSI value” is derived from the “IMSI value” and the “alternate IMSI value”. If the UE has not assigned an accepted “IMSI offset” value, the UE uses the “IMSI value” to derive the paging timing.)

[0024] exist Figure 1 In the example, in step 121, UE 101 performs the attach process with EPS 110 on both USIM1 and USIM2 (USIM1 and USIM2 may be attached to the same or different PLMNs). In step 122, UE 101 monitors and responds to paging from EPS 110 on both USIM1 and USIM2. However, UE 101 discovers that the paging timings of USIM1 and USIM2 are the same, and it needs to indicate the IMSI offset value of one of the USIMs (e.g., USIM1) to the network via the TAU process. In step 131, UE 101 includes the IMSI offset value in the "Requested IMSI Offset" IE in the TAU Request message and sends it to the network. In step 132, the network includes the "Negotiated IMSI Offset" IE in the TAU Accept message and sends it to UE 101. In step 133, UE 101 sends a TAU Complete message to the network to acknowledge the received "Negotiated IMSI Offset" IE.

[0025] However, if a low-level fault occurs before the network successfully receives the message tracing area update completion, the network does not know whether UE 101 has received the TAU acceptance message. Therefore, (assuming that the UE has not yet been assigned an IMSI offset value before the TAU process, and that the network assigns an IMSI offset value to the UE in the TAU acceptance message during the TAU process), the network does not know whether UE 101 monitors paging using the paging timing (paging sequence) derived from the original IMSI value without offset or using the paging timing (paging opportunity) derived from an IMSI value with offset (i.e., an alternative IMSI value). According to a novel aspect, when a UE needs to be paged, the network uses two (alternative) IMSI values ​​to determine the paging sequence, for example, the paging opportunity for UE 101, until one of the (alternative) IMSI values ​​can be considered invalid by the network.

[0026] Figure 2 This is a simplified block diagram 200 of wireless devices 201 and 211 according to embodiments of the present invention. For wireless device 201 (e.g., network entity MME), antennas 207 and 208 transmit and receive radio signals. An RF transceiver module 206 (including a transmitter and a receiver) coupled to the antennas receives RF signals from the antennas, converts the RF signals into baseband signals, and sends them to processor 203. The RF transceiver module 206 also converts the baseband signals received from processor 203 into RF signals and sends them to antennas 207 and 208. Processor 203 processes the received baseband signals and invokes different functional modules and circuits to perform functional features in wireless device 201. Memory 202 stores program instructions and data 210 to control the operation of device 201.

[0027] Similarly, for wireless device 211 (e.g., user equipment), antennas 217 and 218 transmit and receive RF signals. An RF transceiver module 216 is coupled to the antennas, receives RF signals from the antennas, converts the RF signals into baseband signals, and sends them to processor 213. The RF transceiver module 216 also converts baseband signals received from processor 213 into RF signals and sends them to antennas 217 and 218. Processor 213 processes the received baseband signals and invokes different functional modules and circuits to execute functional features in UE 211. Memory 212 stores program instructions and data 220, as well as multiple USIM cards 225 to control the operation of UE 211.

[0028] Wireless devices 201 and 211 also include several functional modules and circuits that can be implemented and configured to perform embodiments of the present invention. Figure 2In the example, wireless device 201 is an MME including a NAS signaling connection processing module 205, a paging module 204, a mobility management module 209, and control and configuration circuitry 221. Wireless device 211 is a UE including a connection processing module 215, a registration module 214 (for attach and TAU processing), a paging and mobility processing module 219, and control and configuration circuitry 231. Note that a wireless device can be both a transmitting and receiving device. Different functional modules and circuitry can be implemented and configured through software, firmware, hardware, and any combination thereof. When executed by processors 203 and 213 (e.g., via executable program code 210 and 220), the functional modules and circuitry allow MME 201 and UE 211 to perform embodiments of the present invention.

[0029] In one example, MME 201 establishes a NAS signaling connection with UE 211 via NAS signaling connection processing circuitry 205, pages the UE via paging module 204, performs mobility and handover management via mobility management module 209, and provides control and configuration information to the UE via control and configuration circuitry 221. UE 211 registers with the network via registration module 214, establishes a signaling connection via connection processing circuitry 215, monitors paging via paging and mobility processing module 219, and obtains configuration information via control and configuration circuitry 231. In one example, the MUSIM UE and the network can request and negotiate an IMSI offset for the IMSI value of one of the USIM cards through the TAU process, allowing the paging timing of that USIM card to differ from the paging timing of other USIMs of the same MUSIM UE. In a novel aspect, when a low-level fault occurs during the TAU process, the network uses two (alternative) IMSI values ​​to determine the paging timing (e.g., the paging timing of the MUSIM UE) until one of the (alternative) IMSI values ​​can be considered invalid by the network.

[0030] Figure 3An example of the contents of an IMSI that can be used to derive paging timing is shown. An IMSI consists of three parts: Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Station Identification Number (MSIN). The IMSI is stored in the USIM card and used for identification during the attach and TAU processes, as well as for determining the paging timing (paging timing) for the network. A MUSIM UE is a UE with multiple valid USIMs or valid Stand-alone Non-Public Network (SNPN) subscriptions, each capable of initiating and maintaining a separate registration state with the PLMN / SNPN via 3GPP access using the identifiers and certificates associated with those USIMs, and each capable of supporting one or more (N1)NAS signaling connection releases, paging indications for voice services, paging request rejection, paging timing conflict control, and paging restrictions. For a MUSIM UE, each USIM card has its own IMSI value, and the paging timings determined based on the corresponding IMSI values ​​for different USIM cards may be the same. Therefore, a MUSIM UE that supports "paging timing conflict control" needs to indicate the IMSI offset value of one of the USIM cards to the network, so that the paging timing of that USIM card can be changed to a different timing, that is, different from the paging timing of other USIM cards in the same MUSIM UE.

[0031] For MUSIM-enabled UEs, if the UE needs to indicate an IMSI offset value to the network, the UE should include the IMSI offset value in the requested IMSI offset IE in the attach request message. If the MUSIM-enabled UE includes the requested IMSI offset IE in the attach request message, and if the MME supports paging timing conflict control, the MME should include the negotiated IMSI offset IE in the attach accept message. The MME should store the IMSI offset value and use it in calculating the alternative IMSI, which is used to derive the paging timing. If the MUSIM-enabled UE does not include the requested IMSI offset IE in the attach request message, the MME will erase any alternative IMSI stored for that UE (if available). If the attach accept message contains the negotiated IMSI offset IE, the MUSIM-enabled UE should forward the IMSI offset value to the lower layer. If the attach accept message does not include the negotiated IMSI offset IE, the MUSIM-enabled UE should instruct the lower layer to erase any IMSI offset values ​​(if available).

[0032] Similarly, the Tracking Area Update (TAU) process can be initiated by the UE and used to indicate to the network that a MUSIM-enabled UE needs to use an IMSI offset value to derive different paging timings. When a MUSIM-enabled UE needs to request an IMSI offset value for deriving different paging timings, the UE in EMM-registered status should initiate the Tracking Area Update process by sending a Tracking Area Update Request message to the MME. For a MUSIM-enabled UE, if the UE supports paging timing conflict control and needs to indicate an IMSI offset value to the network, the UE should include the IMSI offset value in the requested IMSI offset IE in the Tracking Area Update Request message. If the MUSIM-enabled UE has already included the requested IMSI offset IE in the Tracking Area Update Request message, and if the MME supports paging timing conflict control, the MME includes the negotiated IMSI offset IE in the Tracking Area Update Accept message. The MME will store the IMSI offset value and use it in calculating the Alternate IMSI, which is used to derive the paging timing. If the UE has not yet included the requested IMSI offset IE in the Tracking Area Update Request message, the MME will erase any stored alternative IMSI used by the UE (if available). If the negotiated IMSI offset IE is included in the Tracking Area Update Accept message, a MUSIM-enabled UE should forward the IMSI offset value to the lower layer. If the negotiated IMSI offset IE is not included in the Tracking Area Update Accept message, a MUSIM-enabled UE should instruct the lower layer to erase any IMSI offset values ​​(if available). If the Tracking Area Update Accept message includes a Globally Unique Temporary Identity (GUTI) or a negotiated IMSI offset IE, the UE will return a Tracking Area Update Complete message to the MME to acknowledge receipt of the GUTI or the negotiated IMSI offset IE.

[0033] The UE and network use a negotiated IMSI offset, also known as the accepted IMSI offset, to determine the paging timing (the paging timing is derived from an alternative IMSI value, which is derived from 1. the IMSI value and 2. the accepted IMSI offset value). The UE and MME use the accepted IMSI offset to calculate the alternative IMSI value, which is determined based on the IMSI value stored by the UE, as follows: Alternate IMSI value = [MCC][MNC][(MSIN value + accepted IMSI offset) mod (MSIN address space)], where the MCC, MNC, and MSIN values ​​are the UE's IMSI fields as defined in TS 23.003. The MME uses the alternative IMSI value to calculate the UE identification index value. The MME sends the UE identification index value to the RAN in the paging message (see TS 36.413) for the RAN to derive the paging timing according to TS 36.304. The UE uses the alternative IMSI value to determine the paging timing as specified in TS 36.304. If no IMSI offset value exists, the original IMSI value stored in the USIM is used to determine the paging timing.

[0034] Figure 4 This illustrates different scenarios where the UE and network use the TAU / Attach process to request and negotiate IMSI offset values. If a low-level fault occurs before the network receives the Tracking Area Update Acceptance (or Attach Acceptance) message, three different scenarios exist. In scenario #1, the negotiated IMSI offset value #1-1 (indicated in the Negotiated IMSI Offset IE) has been assigned to the UE in the Tracking Area Update Acceptance (or Attach Acceptance) message, and the UE already has another assigned negotiated IMSI offset value #1-2 (indicated in the Negotiated IMSI Offset IE). In scenario #2, no negotiated IMSI offset value has been assigned to the UE in the Tracking Area Update Acceptance (or Attach Acceptance) message, but the UE already has an assigned negotiated IMSI offset value #2-1 (indicated in the Negotiated IMSI Offset IE). In scenario #3, the negotiated IMSI offset value #3-1 (indicated in the Negotiated IMSI Offset IE) has been assigned to the UE in the Tracking Area Update Acceptance (or Attach Acceptance) message, but the UE already has no assigned negotiated IMSI offset value.

[0035] For all three scenarios, in one scenario, the UE has successfully received the Tracking Area Update Acceptance (or Attach Acceptance) message, but the Tracking Area Update Completion (or Attach Completion) has not been transmitted to the network. Therefore, after the TAU / Attach process, the UE will use the updated (alternate) IMSI value (i.e., for scenario #1: consider using IMSI offset value #1-1 to determine paging timing; for scenario #2: do not consider using IMSI offset value to determine paging timing; for scenario #3: consider using IMSI offset value #3-1 to determine paging timing). Note that the updated (alternate) IMSI value is also called the updated IMSI parameter. In another scenario, the UE has not yet received the Tracking Area Update Acceptance (or Attach Acceptance) message, therefore, before the TAU / Attach process, the UE will use the previous (alternate) IMSI value (i.e., for scenario #1: consider using IMSI offset value #1-2 to determine paging timing; for scenario #2: consider using IMSI offset value #2-1 to determine paging timing; for scenario #3: do not consider using IMSI offset value to determine paging timing). Please note that the previous (alternative) IMSI value is also referred to as the previous IMSI parameter.

[0036] For scenario #1, the UE can deduce the paging timing using either IMSI offset value #1-1 or IMSI offset value #1-2, and the network cannot determine which value the UE will use. For scenario #2, the UE can deduce the paging timing using either IMSI offset value #2-1 or the IMSI value stored in the USIM, and the network cannot determine which value the UE will use. For scenario #3, the UE can deduce the paging timing using either IMSI offset value #3-1 or the IMSI value stored in the USIM, and the network cannot determine which value the UE will use. Therefore, when deduce the paging timing for the UE, the network needs to consider two possible (alternative) IMSI values ​​that the UE might use.

[0037] Figure 5An embodiment of processing IMSI offset values ​​for a MUSIM UE supporting paging timing conflict control in an EPS network is illustrated according to a novel aspect. UE 501 is a MUSIM UE, defined as a UE with multiple valid USIMs. In step 511, UE 501 performs an attach process with EPS network 502 for USIM1 and USIM2. USIM1 stores the original IMSI1 value, and USIM2 stores the original IMSI2 value. IMSI1 and IMSI2 are used to derive paging timing, e.g., paging opportunities. At some point, UE 501 discovers that the paging opportunities derived from IMSI1 and IMSI2 for USIM1 and USIM2 are the same, therefore UE 501 will not be able to monitor paging for both USIM cards. Since UE 501 and EPS 502 support paging timing conflict control, UE 501 can use the TAU process to request an IMSI offset value for one of the USIM cards, e.g., USIM1.

[0038] In step 521, UE 501 sends a Tracking Area Update Request message to EPS 502 via USIM1. The Tracking Area Update Request message includes the IMSI offset requested by the UE for USIM1. In step 522, EPS 502 sends a Tracking Area Update Accept message back to UE 501. The Tracking Area Update Accept message includes the NW Accept (negotiated) IMSI offset for USIM1. However, due to a low-level fault, UE 501 may fail to receive the Tracking Area Update Accept message. If this is the case, UE 501 continues to use the previous IMSI value without applying the IMSI offset. UE 501 will not send a Tracking Area Update Complete message to the network. On the other hand, if UE 501 successfully receives the Tracking Area Update Accept message, in step 523, UE 501 applies the negotiated IMSI offset to derive the paging timing for USIM1. Furthermore, in step 524, UE 501 sends a Tracking Area Update Complete message to EPS 502. However, due to a low-level fault, EPS 502 failed to receive the tracking area update complete message (step 531).

[0039] Therefore, in step 532, the MME of EPS 502 needs to consider two possible IMSI values ​​to determine the paging timing of USIM1. As mentioned above... Figure 4 As shown, in all three different scenarios, the UE can use two (alternative) IMSI values ​​to deduce the paging timing, and the network is unaware of which (alternative) IMSI value the UE uses. Figure 5In one embodiment, in step 541, the MME sends a paging message to UE 501 using a paging timing derived from a previous IMSI value (e.g., before the TAU process). In step 542, the MME sends a paging message to UE 501 using a paging timing derived from an updated IMSI value (e.g., assuming the TAU process was successful). In step 551, UE 501 uses one of the (alternative) IMSI values ​​for monitoring paging, depending on the circumstances. In step 561, UE 501 attempts to establish a connection with the network in response to the paging. Because the network uses two (alternative) IMSI values ​​to determine the paging timing of USIM1, the UE can receive paging on USIM1 regardless of which (alternative) IMSI value the UE uses for monitoring paging timing.

[0040] Figure 6 Another embodiment of processing the IMSI offset value of MUSIMUE supporting paging timing conflict control in an EPS network is shown, according to a novel aspect. Figure 6 The steps from 611 to 632 are similar to Figure 5 Steps 511 to 532 in the text. However, in Figure 6 In one embodiment, the network uses two (alternative) IMSI values ​​to determine the paging timing of USIM1 until one of the values ​​can be considered invalid by the network. In step 641, the network uses the first (alternative) IMSI value to determine the paging timing and sends a paging message to UE 502. In step 651, UE 601 uses the first (alternative) IMSI value to monitor paging and is able to receive paging messages. In step 661, UE 601 attempts to establish a connection with the network in response to the paging message. Therefore, the network knows that the second (alternative) IMSI value is invalid, and the network can continue to page the UE on USIM1 using the first (alternative) IMSI value (step 662). On the other hand, if the UE does not respond to a paging message using the first IMSI value, for example, after a certain amount of time, the network can switch to paging with the second (alternative) IMSI value determining the paging timing. If the UE responds to the paging message, the network knows that the first (alternative) IMSI value is invalid, and the network can continue to page the UE on USIM1 using the second (alternative) IMSI value.

[0041] In an alternative embodiment, when the alternative IMSI value changes or is deleted, the network assigns a new GUTI. If the UE responds to a paging call using the new GUTI, the network may consider the alternative IMSI value associated with the old GUTI invalid. Similarly, if the UE responds to a paging call using the old GUTI, the network may consider the alternative IMSI value associated with the new GUTI invalid.

[0042] Figure 7This is a flowchart of a method for processing the IMSI value of a MUSIM UE supporting paging timing conflict control in an EPS network according to a novel aspect of the present invention. In step 701, a network entity in the wireless communication network receives a Tracking Area Update (TAU) request message from a user equipment (UE). The UE supports multiple Universal Subscriber Identity Modules (MUSIMs). In step 702, the network entity sends a Tracking Area Update Acceptance message to the UE. The TAU Acceptance message includes or excludes a negotiated IMSI offset value in response to the TAU Request message. In step 703, when the network has not received a Tracking Area Update Complete message from the UE, the network entity determines the paging timing by considering the validity of previously valid and updated IMSI parameters and then paging the UE.

[0043] While the invention has been described in conjunction with specific embodiments for illustrative purposes, it is not limited thereto. Therefore, various modifications, adaptations, and combinations of the features of the described embodiments can be made without departing from the scope of the invention as set forth in the claims.

Claims

1. A method for processing International Mobile Subscriber Identity (IMI) offset values, comprising: In wireless communication networks, network entities receive tracking area update request messages from user equipment that has previous International Mobile Subscriber Identity (IMSI) parameters and old Globally Unique Temporary Identifier (GUID). Send a Tracking Area Update Acceptance Message to the user equipment, wherein the Tracking Area Update Acceptance Message includes a negotiated International Mobile Subscriber Identity Offset and a new Globally Unique Temporary Identifier, in response to the Tracking Area Update Request Message; as well as When the network entity does not receive a Tracking Area Update Complete message from the user equipment, it determines the paging timing by considering both the validity of the previous International Mobile Subscriber Identity (IMSI) parameter and the validity of the updated IMSI parameter.

2. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The network entity and the user equipment support paging timing conflict control.

3. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, Before the network entity sends the Tracking Area Update Acceptance Message, the previous International Mobile Subscriber Identity (IMSI) parameter is either a replacement IMSI value or the original IMSI value stored in the Universal Subscriber Identity Module (USB).

4. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The updated International Mobile Subscriber Identity (IMSI) parameter is the replacement IMSI value after the network entity applies the negotiated IMSI offset value in the Tracking Area Update Acceptance message.

5. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter is a first alternative IMSI value derived from the first negotiated IMSI offset value, and the updated IMSI parameter is a second alternative IMSI value derived from the negotiated IMSI offset value included in the tracking area update acceptance message.

6. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter is an alternative IMSI value derived from the first negotiated IMSI offset value.

7. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter was the original IMSI value stored in the Universal Subscriber Identity Module (UMI) card, and the updated IMSI parameter was an alternative IMSI value derived from the negotiated IMSI offset value included in the Tracking Area Update Acceptance message.

8. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, The network entity uses a determined paging timing derived from the previous International Mobile Subscriber Identity (IMSI) parameter or the updated IMSI parameter or both to page the user equipment until one of the previous IMSI parameter or the updated IMSI parameter is deemed invalid.

9. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 8, characterized in that, If a network entity pagees a user equipment using a paging timing derived from another International Mobile Subscriber Identity (IMSI) parameter and the network entity receives a paging response from the user equipment, the network entity considers an IMSI parameter invalid.

10. The method for processing International Mobile Subscriber Identity (IMI) offset values ​​according to claim 1, characterized in that, Because a low-level fault occurred before the network entity received the Tracking Area Update Complete message, the network entity did not receive the Tracking Area Update Complete message from the user equipment.

11. An International Mobile Subscriber Identity Offset Value (IMO) processing network entity, comprising: A receiver is used to receive tracking area update request messages from user equipment with previous International Mobile Subscriber Identity parameters and old Globally Unique Temporary Identifiers via network entities in a wireless communication network. A transmitter is configured to send a Tracking Area Update Acceptance message to the user equipment, wherein the Tracking Area Update Acceptance message includes a negotiated International Mobile Subscriber Identity (IMSI) offset and a new Globally Unique Temporary Identifier (GUID), in response to the Tracking Area Update Request message; and The paging processing circuit module, when the network entity has not received a Tracking Area Update Complete message from the user equipment, is used to determine the paging timing by considering both the validity of the previous International Mobile Subscriber Identity (IMSI) parameter and the validity of the updated IMSI parameter.

12. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The network entity and the user equipment support paging timing conflict control.

13. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, Before the network entity sends the Tracking Area Update Acceptance Message, the previous International Mobile Subscriber Identity (IMSI) parameter is either a replacement IMSI value or the original IMSI value stored in the Universal Subscriber Identity Module (USB).

14. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The updated International Mobile Subscriber Identity (IMSI) parameter is the replacement IMSI value after the network entity applies the negotiated IMSI offset value in the Tracking Area Update Acceptance message.

15. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter is a first alternative IMSI value derived from the first negotiated IMSI offset value, and the updated IMSI parameter is a second alternative IMSI value derived from the negotiated IMSI offset value included in the tracking area update acceptance message.

16. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter is an alternative IMSI value derived from the first negotiated IMSI offset value.

17. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The previous International Mobile Subscriber Identity (IMSI) parameter was the original IMSI value stored in the Universal Subscriber Identity Module (UMI) card, and the updated IMSI parameter was an alternative IMSI value derived from the negotiated IMSI offset value included in the Tracking Area Update Acceptance message.

18. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, The network entity uses a determined paging timing derived from the previous International Mobile Subscriber Identity (IMSI) parameter or the updated IMSI parameter or both to page the user equipment until one of the previous IMSI parameter or the updated IMSI parameter is deemed invalid.

19. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 18, characterized in that, If a network entity pagees a user equipment using a paging timing derived from another International Mobile Subscriber Identity (IMSI) parameter and the network entity receives a paging response from the user equipment, the network entity considers an IMSI parameter invalid.

20. The International Mobile Subscriber Identity Offset Value Processing Network Entity according to claim 11, characterized in that, Because a low-level fault occurred before the network entity received the Tracking Area Update Complete message, the network entity did not receive the Tracking Area Update Complete message from the user equipment.

Images