Apparatus, system, method and computer-readable medium for cellular system enhancement for support of multi-SIM user equipment

Abstract

To provide multi-SIM (subscriber identity module) UE (user equipment) not negatively impacting operations of a network.SOLUTION: The multi-SIM UE includes: a receiver configured to receive a first SIM; a receiver configured to receive a second SIM; and circuitry configured to receive data from the first SIM, to send a request to a first public land mobile network (PLMN), and to register the electronic device with the first PLMN. The request indicates that the electronic device is a multi-SIM device. The request includes multi-SIM assistance information. The multi-SIM assistance information is for informing the first PLMN about the UE's preference for multi-SIM operations.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is a continuation of U.S. Provisional Patent Application No. 62 / 928,379, filed October 31, 2019. No. 62 / 899,322, filed September 12, 2019; and Claims the benefit of U.S. Provisional Patent Application No. 62 / 858,747, filed June 7, 2019. , the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates generally to wireless communications, and more particularly to 4G and 5G multi-subscriber identity A cellular system is used to support the use of a SIM (Single Interleaved Module) User Equipment (UE). WIRELESS COMMUNICATION SYSTEMS, DEVICES, METHODS AND APPARATUS WITH COMPUTER EXECUTABLE INSTRUCTIONS FOR ENHANCEMENT - Patent application and computer readable media. [Background technology]

[0003] The "Background" discussion provided herein is intended to generally present the context of the present disclosure. As described in this Background section, the present inventors The research, as well as aspects of the description that may not qualify as prior art at the time of filing, Nothing herein is admitted expressly or impliedly as prior art to the invention.

[0004] Previously, multiple SIM UEs were managed by device manufacturers without knowledge of the core network. It is a proprietary solution implemented by various entities and is outside the scope of the 3GPP standard. The behavior of the network components (UE, RAN, and CN) is well defined and known between the various entities. The operation of the cellular network was designed to support various existing multi-SIM UEs. In implementation, different behaviors of different implementations adversely affect the operation of the network and its performance. It may even decrease it. Summary of the Invention

[0005] One exemplary embodiment of the present disclosure provides a first subscriber identity module (SIM) for receiving a receiver configured to receive a first SIM; Receive data from the SIM and send a request to a first public land mobile network (PLMN) to providing an electronic device including circuitry configured to register the electronic device with a PLMN; The request indicates that the electronic device is a multi-SIM device, and the request indicates that the electronic device supports multi-SIM The multi-SIM support information includes a preference of the electronic device for multi-SIM operation. The PLMN then notifies the first PLMN of the received signal.

[0006] One exemplary embodiment of the present disclosure provides a method performed by an electronic device, the method comprising: The method includes receiving data from a first subscriber identity module (SIM), registering the electronic device with a first public land mobile network (PLMN) by sending a request to the first PLMN; and registering the electronic device with the SIM card, the request indicating that the electronic device is a multi-SIM device. wherein the request includes multi-SIM support information, the multi-SIM support information being related to multi-SIM operation; and informing the first PLMN of the device's preferences for the first PLMN.

[0007] An exemplary embodiment of the present disclosure, when executed by an electronic device, receiving data from a first subscriber identity module (SIM) and transmitting the request to a first public land a first PLMN for registering the electronic device with the first PLMN; and providing a non-transitory computer-readable medium including computer-executable instructions for causing a user to indicates that the electronic device is a multi-SIM device, and the request is for multi-SIM support information The multi-SIM support information includes a device preference for multi-SIM operation. The first PLMN is notified.

[0008] This Summary is provided to simplify a selection of concepts that are further described below in the Detailed Description. This Summary is provided to introduce the claimed subject matter in a simplified form. The following statements are not intended to identify essential features and are not intended to limit the scope of the claimed subject matter. Moreover, the claimed subject matter is not intended to be used in any manner that would be construed as being inconsistent with any of the teachings of this disclosure. The present invention is not limited to the limitations that solve any or all of the disadvantages described in the preceding paragraph.

[0009] The scope of the present disclosure is defined in the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. is best understood from [Brief description of the drawings]

[0010] [Figure 1A] FIG. 1A is a system diagram illustrating an example 3GPP architecture. [Figure 1B] FIG. 1B is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1C] FIG. 1C is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1D] FIG. 1D is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1E]FIG. 1E is a system diagram illustrating an example 3GPP architecture. [Figure 1F] FIG. 1F is a system diagram of an example apparatus or device configured for wireless communication. [Figure 1G] FIG. 1G is a system diagram illustrating an example of a computing system for use in a communications network. [Diagram 2] FIG. 2 is a diagram illustrating a non-roaming 5G system architecture according to an example embodiment. [Diagram 3] FIG. 3 is a diagram illustrating a roaming 5G system architecture according to an example embodiment. [Figure 4] FIG. 4 is a diagram illustrating a roaming 5G system architecture according to an example embodiment. [Diagram 5] FIG. 5 illustrates a 5G general registration procedure according to an example embodiment. [Figure 6] FIG. 6 is a diagram illustrating a registration management state model in a UE according to an example embodiment. [Figure 7] FIG. 7 is a diagram illustrating connection management state transitions in a UE according to an example embodiment. [Figure 8] FIG. 8 illustrates a network slice-specific authentication and authorization method according to an exemplary embodiment. [Figure 9] FIG. 9 illustrates a method for UE registration with multiple SIMs according to an example embodiment. [Figure 10] FIG. 10 illustrates a method for partial registration according to an example embodiment. [Figure 11] FIG. 11 illustrates an alternative method for partial registration according to an example embodiment. [Figure 12] FIG. 12 illustrates a method for indirect registration according to an example embodiment. [Figure 13] FIG. 13 illustrates an alternative method of indirect registration according to an example embodiment. [Figure 14]FIG. 14 is a diagram illustrating the RM-INACTIVE registration management state according to an example embodiment. [Figure 15] FIG. 15 illustrates a paging method for multi-SIM operation according to an example embodiment. [Figure 16] FIG. 16 is a diagram illustrating a SIM switching method according to an example embodiment. [Figure 17] FIG. 17 illustrates a multi-SIM configuration GUI according to an example embodiment. [Figure 18] FIG. 18 illustrates an individual SIM configuration GUI according to an example embodiment. [Figure 19] FIG. 19 is a diagram illustrating a 3GPP EPS non-roaming system architecture according to an example embodiment. [Figure 20] FIG. 20 illustrates an EPS attachment procedure according to an exemplary embodiment. [Figure 21] FIG. 21 is a diagram illustrating EPS mobility management (EMM) states according to an example embodiment. [Figure 22] FIG. 22 is a diagram illustrating EPS connection management states according to an example embodiment. [Diagram 23] FIG. 23 illustrates a service request procedure triggered by an EPS network according to an exemplary embodiment. [Figure 24] FIG. 24 illustrates a method of partial attachment according to one exemplary embodiment. [Diagram 25] FIG. 25 illustrates a method of indirect attachment according to one exemplary embodiment. [Figure 26] FIG. 26 illustrates a method for multiple SIM attachment according to an example embodiment. [Figure 27] FIG. 27 is a diagram illustrating the EMM-INACTIVE state according to an example embodiment. [Figure 28] FIG. 28 illustrates a method of page request forwarding for a UE in an ECM-CONNECTED state according to an example embodiment. [Figure 29] FIG. 29 illustrates a method of page request forwarding for a UE in ECM-IDLE state according to one example embodiment. [Diagram 30] FIG. 30 illustrates a method for inactivity registration timer update according to an example embodiment. [Diagram 31] FIG. 31 illustrates a method for error cases resulting from SIM switching according to an example embodiment. [Diagram 32] FIG. 32 illustrates a non-roaming architecture for interworking between 5GS and EPS according to an example embodiment. [Diagram 33] FIG. 33 illustrates another multi-SIM configuration GUI according to an example embodiment. [Diagram 34] FIG. 34 is a diagram illustrating a UE requesting provisioning of a temporary identifier from a core network according to one example embodiment. [Diagram 35] FIG. 35 is a diagram illustrating a multi-SIM UE detecting a paging collision according to an example embodiment. [Diagram 36] FIG. 36 illustrates a procedure for activating and deactivating the registration pause timer according to one example embodiment. [Figure 37] FIG. 37 is a diagram illustrating a UE executing a request for the core network to stop paging the UE according to one example embodiment. [Figure 38] FIG. 38 is a diagram illustrating a core network providing a notification to a UE indicating a missed page according to one example embodiment. [Figure 39] FIG. 39 illustrates a method for a multi-SIM UE to perform indirect registration of an inactive SIM over the user plane of an active SIM according to an example embodiment. [Diagram 40] FIG. 40 illustrates a method for a multi-SIM UE to receive a NAS notification from PLMN2 for SIM2 via the user plane of PLMN1 according to one example embodiment. [Diagram 41] FIG. 41 is a diagram illustrating how a multi-SIM UE provides a user configuration to the core network with preferences for how the user wants the UE to operate for multi-SIM operation according to one example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. The detailed description of the exemplary embodiments is for purposes of illustration only and is therefore not intended to be limiting of the present disclosure. It should be understood that this is not necessarily a limitation on the scope.

[0012] The 3rd Generation Partnership Project (3GPP) is a global initiative to develop and deploy wireless access, core transformers, and other Port network, as well as codec, security and quality of service Develop technical standards for cellular communications network technology, including service capabilities, including operational Recent Radio Access Technology (RAT) standards include WCDMA (commonly known as 3G), LTE (commonly known as 4G), LTE-Advanced standard, and New Radio (NR), also known as "5G." Standard development is expected to continue and include the definition of next generation radio access technologies (new RATs), It is the provision of new flexible wireless access below 7 GHz and new It is expected to include the provision of ultra-mobile broadband wireless access. The access is a new non-backwards compatible wireless access in the new spectrum below 7 GHz. The 3GPP NR 2019-2020 standard is expected to cover a broad set of 3GPP NR use cases with different requirements. The expected range of operating modes is expected to include different modes of operation that can be multiplexed together in the same spectrum to address Ultra-mobile broadband is expected to be used in indoor and hotspot applications, for example. cmWav provides ultra-mobile broadband access opportunities for the hotspots This is expected to include e and mmWave spectrum, particularly for ultra-mobile broadband. The bands are sub-7GHz with cmWave and mmWave specific design optimizations. They are expected to share flexible wireless access and a common design framework.

[0013] 3GPP has identified various use cases that NR is expected to support and has with a wide variety of user experience requirements for speed, latency, and mobility. The use cases fall into the following general categories: Advanced Mobile Broadband eMBB, Ultra-Reliable Low Latency Communications (URLLC), Large-Scale Machine Type Communications (mMT C), network operations (e.g., network slicing, routing, migration and and interworking, energy conservation, and advanced vehicle-to-thing (eV2X) communications. These include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-network (V2N). Vehicle-to-N (V2N), vehicle-to-pedestrian (V2P), and vehicular communication with other entities. For specific services and applications in these categories, For example, monitoring and sensor networks, device remote control, bidirectional remote control, Social Cloud Computing, Video Streaming, Wireless Cloud-Based office, first responder connection, vehicle emergency call, disaster warning, real-time gaming , multi-party video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation These use cases include automation, robotics, and aerial drones. All and other use cases are contemplated herein.

[0014] The following are some points regarding service levels and core network technologies that may appear in the following descriptions: Unless otherwise stated, the acronyms used in this specification are as follows: Refers to the corresponding terms listed in.

[0015] [Table 1-1] [Table 1-2]

[0016] [Table 2-1] [Table 2-2]

[0017] Exemplary Communication Systems and Networks FIG. 1A illustrates a system in which the systems, methods, and apparatus described and claimed herein may be used. 1 illustrates an exemplary communication system 100 that may include a wireless transmit / receive unit ( WTRU) 102a, 102b, 102c, 102d, 102e, 102f, and / or or 102g, which may be referred to generally or collectively as WTRU102 or W The communication system 100 includes a wireless access network (WLAN) 102. Work (RAN) 103 / 104 / 105 / 103b / 104b / 105b, Core Network Work 106 / 107 / 109, Public Switched Telephone Network (PSTN) 108, Internet 1 10, other networks 112, and network services 113. The network service 113 can be, for example, a V2X server, a V2X function, a Pro Se server, ProSe function, IoT services, video streaming, and / or This can include edge computing.

[0018] The concepts disclosed herein may be implemented in any number of WTRUs, base stations, networks, and / or It will be appreciated that the WTRUs 102 may be used in conjunction with any of the network elements. refers to any type of device or device configured to operate and / or communicate in a wireless environment In the example of FIG. 1A, each of the WTRUs 102 may be a handheld wireless communication device. The various types of wireless communication devices are shown in FIG. 1A to FIG. 1E. In this case, each WTRU is configured to transmit and / or receive wireless signals. The present invention may comprise or be included in any type of apparatus or device, Also, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, Pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops , tablets, netbooks, notebook computers, personal computers, Linear sensors, consumer electronics devices, wearable devices such as smart watches or smart clothing devices, medical or eHealth devices, robots, industrial equipment, drones, cars, buses It will be understood that this also includes vehicles such as trucks, trains, or airplanes.

[0019] The communication system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 1A, each base station 114a and 114b is illustrated as a single element. In practice, the base stations 114a and 114b may be any number of interconnected base stations and The base station 114a may include a core network 1 06 / 107 / 109, Internet 110, Network Services 113, and / or other network 112. For ease of understanding, at least one of the WTRUs 102a, 102b, and 102c may be It may be any type of device that is configured to interface with a line. Similarly, the base station 114b is connected to the core network 106 / 107 / 109, the Internet 1 10, other networks 112, and / or network services 113, etc. or to facilitate access to multiple communication networks, remote radio heads ( RRH) 118a, 118b, Transmitting and Receiving Points (TRP) 119a, 119b, and / or at least one of the roadside units (RSUs) 120a and 120b and a wired and / or any type of device configured to wirelessly interface with The RRHs 118a and 118b may be connected to the core network 106 / 107 / 109. , the Internet 110, network services 113, and / or other networks. To facilitate access to one or more communications networks, such as the WLAN 112, WTRU 102c. The device may be any type of device configured to

[0020] TRP119a, 119b are the core network 106 / 107 / 109, the Internet network 110, network services 113, and / or other networks 112, etc. to facilitate access to one or more communication networks. d, any type of device configured to wirelessly interface with at least one of The RSUs 120a and 120b may be a core network 106 / 1 07 / 109, the Internet 110, other networks 112, and / or facilitating access to one or more communications networks, such as the network services 113; The WTRU 102e or 102f must wirelessly interface with at least one of the WTRUs to The base station 11 may be any type of device configured to 4a, 114b are base transceiver stations (BTS), NodeB, eNodeB, Home e NodeB, Home eNodeB, next generation NodeB (gNodeB), satellite, It may be a site controller, an access point (AP), a wireless router, etc.

[0021] The base station 114a includes a base station controller (BSC) 2302, a radio network controller (RNC) 2303, and a other base stations and / or network elements such as RNCs, relay nodes, etc. It may be part of RAN 103 / 104 / 105, which may also include the same. Similarly, the base station 114b may communicate with other base stations and / or RAN 103b / 104b / 105b, which may also include network elements (not shown) The base station 114a may be part of a particular The base station may be configured to transmit and / or receive radio signals within a geographic region. The base station 114b provides wired and / or wireless communications within a particular geographic area, which may be called a cell (not shown). A cell may be further configured to transmit and / or receive a radio signal. For example, the cell associated with base station 114a may be divided into three sectors. Thus, for example, the base station 114a may be divided into three transceivers, e.g. For example, the base station 114a may include one transceiver for each sector of the cell. Multiple-input multiple-output (MIMO) techniques can be employed, so that, for example, each cell of a cell Multiple transceivers may be available for a given connector.

[0022] The base station 114a may communicate with the base station 114b via any suitable wireless communication link (e.g., radio frequency (RF), (e.g., Chromatic Wave, Infrared (IR), Ultraviolet (UV), Visible Light, cmWave, mmWave, etc.) WTRU 102a, via air interface 115 / 116 / 117, 102b, 102c, and 102g. The interfaces 115 / 116 / 117 may support any suitable radio access technology (RAT). It may be established using

[0023] The base station 114b may be connected to any suitable wired (e.g., cable, fiber optic, etc.) or wireless Linear communication links (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave ave, etc.) b, RRH118a and 118b, TRP119a and 119b, and and / or one or more of the RSUs 120a and 120b. The interfaces 115b / 116b / 117b may be established using any suitable RAT. stomach.

[0024] RRH118a, 118b, TRP119a, 119b and / or RSU120a , 120b may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet V, visible light, cmWave, mmWave, etc.) WTRU102c, 102d, 102e, 102f via 5c / 116c / 117c The air interface 115c / 116c / 1 can communicate with one or more 17c may be established using any suitable RAT.

[0025] The WTRU 102 may communicate with any suitable wireless communication link (e.g., RF, microwave, IR, Sidelink communications, which can be ultraviolet UV, visible light, cmWave, mmWave, etc. and communicating with each other via the direct air interface 115d / 116d / 117d of The air interface 115d / 116d / 117d may be configured to communicate with any suitable RAT. can be established using

[0026] The communication system 100 may be a multiple access system, such as CDMA, TDMA, One or more channel access, such as FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and and the WTRU 102a, 102b, 102c, or the RAN 103b / 104b / 105b RRH118a, 118b, TRP119a, 119b and / or RSU120a and 120b and WTRUs 102c, 102d, 102e, and 102f. Universal Mobile Telecommunications System (UMTS), Universal Terrestrial Radio Access (UTRA), and other wireless technologies The technique can be implemented using Wideband CDMA (WCDMA) for air-interface communication. -Face 115 / 116 / 117 and / or 115c / 116c / 117c WCDMA is a standard for High Speed ​​Packet Access (HSPA) and / or or Evolved HSPA (HSPA+). The SPA supports High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink It may include link packet access (HSUPA).

[0027] The base station 114a and the WTRUs 102a, 102b, 102c, and 102g, or RRH118 in RAN103b / 104b / 105b a and 118b, TRP119a and 119b, and / or RSU120a and The WTRUs 102c and 102d may be, for example, Use LTE and / or LTE-Advanced (LTE-A) Interface 115 / 116 / 117 or 115c / 116c / 117c respectively Evolved UMTS Terrestrial Radio Access (E-UTRA) and other wireless networks that can be established The air interface 115 / 116 / 117 or 110 15c / 116c / 117c may implement 3GPP NR technology. LTE and L TE-A technology is based on LTE D2D and / or V2X technologies and interfaces (e.g. Similarly, 3GPP NR technology may include NR V2 X technologies and interfaces (e.g., sidelink communications, etc.).

[0028] The base station 114a and the WTRUs 102a, 102b, 102c, and 102g, or RRH118 in RAN103b / 104b / 105b a and 118b, TRP119a and 119b, and / or RSU120a and and 120b, and WTRUs 102c, 102d, 102e, and 102f. EE802.16 (e.g. Worldwide Interoperability for Microwave WiMAX), CDMA2000, CDMA2000 1X, CDMA 2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-9) 5), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM) (Registered Trademark), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN) Wireless technologies such as the above may be implemented.

[0029] The base station 114c in FIG. 1A may be, for example, a wireless router, a Home NodeB, a Home It can be an eNodeB or an access point, for example in an office, home, vehicle, train, or aircraft. Facilitates wireless connectivity in localized areas such as air, satellite, manufacturing, campus, etc. The base station 114c and the WTRU 102 may utilize any suitable RAT for the purposes of the present invention. For example, the WTRU 102e may be configured to establish a wireless local area network (WLAN). For this purpose, the base station 11 may implement a wireless technology such as IEEE 802.11. 4c and the WTRU 102, e.g., the WTRU 102d, Implementing wireless technologies such as IEEE802.15 to establish wireless personal area networks (WPANs) The base station 114c and the WTRU 102, e.g., the WRTU 102e, can Cellular-based RATs (e.g., WCDMA, CDMA) are used to establish cellular or femtocells. DMA2000, GSM, LTE, LTE-A, NR, etc.) can be used. As shown in FIG. 1A, the base station 114c may have a direct connection to the Internet 110. Therefore, the base station 114c can receive the Internet via the core network 106 / 107 / 109. In some cases, access to the Internet 110 may not be required.

[0030] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , voice, data, messaging, authorization and authentication to one or more of the WTRUs 102; Applications and / or Voice over Internet Protocol (VoIP) A core network may be any type of network configured to provide services. For example, the core network 106 / 107 / 109 may communicate with the 7 / 109 is for call control, billing services, mobile location-based services, and Repaid calls, Internet connections, packet data network connections, Ethernet (registered trademark) provides high-level connectivity, video distribution, etc., and / or user authentication, etc. The security functions of the

[0031] Although not shown in FIG. 1A, RAN103 / 104 / 105 and / or RAN1 03b / 104b / 105b and / or core network 106 / 107 / 109 , RAN103 / 104 / 105 and / or RAN103b / 104b / 105b and Able to communicate directly or indirectly with other RANs employing the same or different RATs For example, the core networks 106 / 107 / 109 are RAN103 / 104 / 105 and / or RAN1, which may utilize wireless technology In addition to being connected to 03b / 104b / 105b, it also uses GSM or NR radio technology. The RAN may also communicate with another RAN (not shown) that uses the same WAN.

[0032] The core network 106 / 107 / 109 also includes a WTRU 102 that is connected to the PSTN 108, A gateway for accessing the Internet 110 and / or other networks 112 The PSTN 108 is a plain old telephone service (PO The Internet 110 may include a circuit-switched telephone network that provides TCP / IP. Transmission Control Protocol (TCP) in the Internet Protocol Suite, User Data Common protocols such as UDP (Universal Datagram Protocol), and Internet Protocol (IP) Interconnected computer networks and devices that use the communications protocol The other networks 112 may include other service providers. (b) includes any wired or wireless communication networks owned and / or operated by any provider. For example, the network 112 may be any type of packet data network. network (e.g. IEEE 802.3 Ethernet network), or RAN103 / 1 Same RAT or different from RAN04 / 105 and / or RAN103b / 104b / 105b Another core network connected to one or more RANs, which may employ different RATs. It may include.

[0033] The WTRUs 102a, 102b, 102c, 102d, and 102e of the communication system 100 Some or all of 102f may include multi-mode capabilities, e.g., W TRUs 102a, 102b, 102c, 102d, 102e, and 102f are different A plurality of transceivers for communicating with different wireless networks via wireless links. For example, the WTRU 102g shown in FIG. 1A may employ a cellular-based wireless technology. and base station 114c, which may employ IEEE 802 wireless technology. The device may be configured to communicate with the

[0034] Although not shown in FIG. 1A, the user equipment may have a wired connection to the gateway. It will be understood that the gateway can be a residential gateway (RG). The RG may provide a connection to the core network 106 / 107 / 109. Many of the concepts contained in the specification relate to a UE that is a WTRU and a It will be appreciated that the present invention may equally be applied to UEs that use a wired connection for Applies to interfaces 115, 116, 117 and 115c / 116c / 117c The same concepts can be applied to wired connections as well.

[0035] FIG. 1B is a system diagram of an example RAN 103 and core network 106. As mentioned above, the RAN 103 employs UTRA radio technology to provide an air interface 115. The RAN 103 may also be in communication with a core network 106. As shown in FIG. N103 may include NodeBs 140a, 140b, and 140c, which The WTRUs 102a, 102b, and 102c communicate with each other via an interface 115. Each of the NodeBs 140a, 140b may include one or more transceivers for transmitting the , and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. The RAN 103 may include any It is recognized that the system may include multiple NodeBs and Radio Network Controllers (RNCs). Let's do it.

[0036] As shown in FIG. 1B, NodeBs 140a and 140b communicate with an RNC 142a. In addition, NodeB 140c can communicate with RNC 142b. NodeBs 140a, 140b, and 140c communicate with each other via Iub interfaces. RNCs 142a and 142b can communicate with each other. RNC 14 and 142b can communicate with each other via the Iur interface. 2a and 142b are connected to respective NodeBs 140a, 140b. In addition, RNC 142a and RNC 140c can be configured to control the RNC 142a and RNC 140c. Each of 142b and 142c controls outer loop power control, load control, admission control, packet switching, and the like. Scheduling, handover control, macro diversity, security functions, data It may also be configured to perform or support other functions, such as encryption.

[0037] The core network 106 shown in FIG. 1B includes a media gateway (MGW) 144. , Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SGS N) 148, and / or Gateway GPRS Support Node (GGSN) 150. Each of the aforementioned elements is illustrated as part of the core network 106, but may include: Any one of these elements may be implemented by an entity other than the core network operator. It will be understood that the information contained herein may be owned and / or operated by any person skilled in the art.

[0038] RNC142a of RAN103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 receive the WTRUs 102a, 102b, and 102c. to facilitate communication between the PSTN and traditional terrestrial communication devices. The WTRUs 102a, 102b, and 102c may be provided with access to a line-switched network. can.

[0039] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may be connected to the WTRUs 102a, 102b. , and the Internet to facilitate communication between 102c and IP-enabled devices. WTRUs 102a, 102b, and 102 c.

[0040] The core network 106 may also be owned and / or operated by other service providers. connected to other networks 112, which may include other wired or wireless networks operated It is possible.

[0041] FIG. 1C is a system diagram of an example RAN 104 and core network 107. As mentioned above, the RAN 104 employs E-UTRA radio technology to provide an air interface. The WTRUs 102a, 102b, and 102c can communicate with each other via the interface 116. The RAN 104 may also be in communication with a core network 107.

[0042] The RAN 104 may include eNodeBs 160a, 160b, and 160c. It will be appreciated that the AN 104 may include any number of eNodeBs. 60a, 160b, and 160c are each connected to the W One or more transceivers for communicating with the TRUs 102a, 102b, and 102c. For example, the eNodeBs 160a, 160b, and 160c may include The eNodeB 160a may implement MO technology. Using multiple antennas to transmit radio signals to a and receive radio signals from it This can be done.

[0043] Each of the eNodeBs 160a, 160b, 160c is associated with a particular cell (not shown). and radio resource management decisions, handover decisions, uplink and / or downlink The system may be configured to handle user scheduling, etc. in the downlink. As shown in FIG. 1C, eNodeBs 160a, 160b, and 160c are connected via an X2 interface. The devices may communicate with each other via an interface.

[0044] The core network 107 shown in FIG. 1C includes a mobility management gateway (MME). 162, a serving gateway 164, and a packet data network (PDN) Each of the aforementioned elements may be part of the core network 107. Although the diagram shows each of these elements as separate entities, any one of these elements may be owned by any entity other than the core network operator. It will be understood that the information contained herein may be owned and / or operated by any of the entities listed above.

[0045] The MME 162 communicates with the eNodeB 160a of the RAN 104 via the S1 interface. , 160b, and 160c, and may function as control nodes. For example, the MME 162 may Authentication, bearer activation / deactivation, WTRU 102a, 102b, and 1 It can be responsible for things like selecting a specific serving gateway during the initial attach of 02c. The MME 162 also communicates with the RAN 104 and other wireless technologies such as GSM or WCDMA. Provides control plane functionality for switching between other RANs (not shown) that employ the same technology. possible.

[0046] The serving gateway 164 communicates with the eN of the RAN 104 via the S1 interface. Each of the power supplies can be connected to the power supplies B160a, B160b, and B160c. The gateway 164 generally communicates between the WTRUs 102a, 102b, and 102c. The Serving Gate can route and forward user data packets. Way 164 also supports anchoring of the user plane during inter-eNodeB handover, When downlink data is available to the WTRUs 102a, 102b, and 102c, Triggering paging during WTRU 102a, 102b, and 102c context The device may also perform other functions such as managing and storing the

[0047] The serving gateway 164 can also connect to a PDN gateway 166. The PDN gateway 166 communicates IP Packet exchange networks such as the Internet 110 are used to facilitate communication between enabled devices. Access to the switched network may be provided to the WTRUs 102a, 102b, 102c.

[0048] The core network 107 may facilitate communication with other networks. For example, the core network 107 may include WTRUs 102a, 102b, and 102c. 108, a circuit-switched network such as the PSTN 108 to facilitate communication between the may be provided to the WTRUs 102a, 102b, and 102c. For example, the core network 107 may include a IP gateways that act as interfaces (for example, IP multimedia subsystems) In addition, the core Network 107 may be owned and / or operated by another service provider. The WTR provides access to the network 112, which may include other wired or wireless networks. U102a, 102b, and 102c.

[0049] FIG. 1D is a system diagram of an example RAN 105 and core network 109. The RAN 105 employs NR radio technology to communicate with the WT over the air interface 117. The RAN 105 can communicate with the RUs 102a and 102b. A non-3GPP interworking function (N3IWF) 199 may communicate with the , and a non-3GPP wireless LAN controller 196 for communicating with the WTRU 102c over the air interface 198. The N3IWF 199 can also communicate with the core network 109. You may believe it.

[0050] The RAN 105 may include gNodeBs 180a and 180b. It will be appreciated that gNodeB 05 may include any number of gNodeBs. 180a and 180b each communicate with the WTRU 102a via the air interface 117. and 102b. When combined access and backhaul connections are used, The same air interface may be used, which may be via one or more gNBs. The gNodeBs 180a and 180b may be a core network 109. Implementing IMO, MU-MIMO, and / or digital beamforming technologies Thus, the gNodeB 180a can transmit a radio signal to the WTRU 102a, for example. Multiple antennas can be used to transmit and receive radio signals. The RAN 105 may employ other types of base stations, such as eNodeBs. It should be appreciated that the RAN 105 may employ multiple types of base stations. For example, the RAN may employ eNodeB and gNodeB.

[0051] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that the F199 may include any number of non-3GPP access points. The 3GPP access point 180c communicates with the WTRU 1 via the air interface 198. 02c。 Non-3GPP access may include one or more transceivers for communicating with 02c. Point 180c communicates with WTRU 102c over air interface 198. The 802.11 protocol can be used for this purpose.

[0052] Each of the gNodeBs 180a and 180b is associated with a particular cell (not shown). Radio resource management decisions, handover decisions, uplink and / or downlink The system may be configured to handle user scheduling, etc., for the network. As shown in the figure, gNodeB 180a and 180b communicate with each other via, for example, the Xn interface. They can communicate with each other.

[0053] The core network 109 shown in FIG. 1D may be a 5G core network (5GC). The core network 109 is a network of customer networks interconnected by a radio access network. The core network 109 can provide multiple communication services to the customers. As used herein, a term refers to a set of entities that perform the functions of a network. The term "core network entity" or "network function" refers to a core network. Refers to any entity that performs one or more functions of a core network. The network entity may be a wireless and / or is stored in the memory of a device or computer system configured for network communication. and the form of computer-executable instructions (software) that are executed on the processor. It is understood that the above may be a logical entity implemented in a multi-threaded manner.

[0054] In the example of FIG. 1D, the 5G core network 109 provides access and mobility management functions. (AMF) 172, Session Management Function (SMF) 174, User Plane Function (UPF ) 176a and 176b, User Data Management Function (UDM) 197, Authentication Server Function ( AUSF) 190, Network Publishing Function (NEF) 196, Policy Control Function (PCF ) 184, Non-3GPP Interworking Function (N3IWF) 199, User Data Repo Each of the aforementioned elements may include a 5G core network 109 Although illustrated as part of the core network, any one of these elements may be It is understood that the information contained herein may be owned and / or operated by entities other than the Company. The 5G core network does not have to consist of all of these elements and may include additional elements, and may be composed of multiple instances of each of these elements. It will also be appreciated that FIG. 1D illustrates network functions directly connecting to each other. However, network functions such as diameter routing agents or message buses are not supported. It should be understood that communication may occur via any routing agent.

[0055] In the example of Figure 1D, the connections between network functions are represented by a set of interfaces or standards. This is achieved through points. Network functions are not affected by other network functions or services. It is modeled, described, or It will be appreciated that the invocation of the network function service may be implemented in the network. Direct connections between functions, messaging exchanges on a message bus, and code for software functions This can be achieved via a loop or the like.

[0056] The AMF 172 may be connected to the RAN 105 via an N2 interface. For example, the AMF 172 may perform registration management, connection management, reachability management, and AMF is responsible for the N2 interface, access authentication, and access authorization. It is responsible for forwarding user plane tunnel configuration information to the RAN 105 via the The AMF172 receives user input from the SMF via the N11 interface. The AMF 172 is generally capable of receiving N1 interface tunnel configuration information. NAS packets are sent to and from the WTRUs 102a, 102b, and 102c via the The N1 interface is not shown in Figure 1D. It hasn't been done yet.

[0057] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF is connected to the PCF184 via the N7 interface and the N4 interface. The SMF 174 may be connected to the UPFs 176a and 176b via an interface. For example, the SMF 174 may function as a session management node, a WTRU 1 IP address assignment for 02a, 102b, and 102c, UPF176a and and management and configuration of traffic steering rules in UPF176b and A It may be responsible for generating downlink data notifications to the MF 172.

[0058] UPF176a and UPF176b are WTRU102a, 102b, and 102 110 to facilitate communication between the device and other devices. The WTRUs 102a, 102b, and 103 provide access to the Power Distribution Network (PDN). UPF176a and UPF176b are also available for other types of The WTRUs 102a, 102b, and 103 provide access to the packet data network of the For example, the other network 112 may be an Ethernet network. network or any type of network that exchanges packets of data. The UPF176a and UPF176b are connected to the SMF174 via the N4 interface. It can receive traffic steering rules from UPF176a and UP F176b is a packet data network that connects to the N6 interface. or by connecting to each other and to other UPFs via the N9 interface. This allows the provision of access to a packet data network. In addition to providing access to the data network, the UPF176 also provides packet routing. Handling and forwarding, policy rule enforcement, and quality of service handling for user plane traffic It can handle downlink packet buffering.

[0059] The AMF 172 is also connected to the N3IWF 199 via the N2 interface, for example. The N3IWF may be used to implement wireless interfaces not defined by 3GPP, for example. The WTRU 102c facilitates a connection between the WTRU 102c and the 5G core network 170 via an interface technology. The AMF will communicate with the N3IWF1 in the same or similar manner as it interacts with the RAN105. You can communicate with 99.

[0060] The PCF184 is connected to the SMF174 via the N7 interface and the N15 interface. It is connected to the AMF172 via the interface and to the application via the N5 interface. The N15 and N5 interfaces can be connected to an application function (AF) 188. Not shown in Fig. 1D. PCF184 is a control for AMF172 and SMF174. The control plane nodes can then provide policy rules to the control plane nodes. PCF184 enables AMF to enforce the N1 interface. to distribute policies to the WTRUs 102a, 102b, and 102c via the W Sends policies for TRUs 102a, 102b, and 102c to AMF 172 The policy may then be enforced at the WTRUs 102a, 102b, and 102c. or may be applied.

[0061] UDR178 can act as a repository of authentication credentials and enrollment information. A UDR can be connected to a network function, so that the network function , you can add, read, and modify data in the repository. For example, The DR178 can be connected to the PCF184 via an N36 interface. Similarly, the UDR178 can be connected to the NEF196 via the N37 interface. The UDR178 can be connected to the UDM197 via the N35 interface. Cut.

[0062] The UDM197 acts as an interface between the UDR178 and other network functions. The UDM 197 allows the UDR 178 to access network functions. For example, the UDM197 can be connected to the AMF172 via the N8 interface. The UDM197 can be connected to the SMF174 via the N10 interface. Similarly, the UDM197 can communicate with the AUSF via the N13 interface. 190. The UDR178 and UDM197 are tightly integrated. good.

[0063] The AUSF190 performs authentication related operations and communicates with the UDM1 through the N13 interface. 78 and then connects to the AMF172 via the N12 interface.

[0064] NEF196 is a 5G Core Network109 capability and service for application The disclosure will be made to Application Function (AF) 188 on the N33 API interface. The NEF can be connected to the AF188 via the N33 interface. , other networks to expose the capabilities and services of the 5G core network 109 can be connected to the function.

[0065] The application function 188 corresponds to the network function of the 5G core network 109. The interaction between the application function 188 and the network function can be This may be done via a direct interface or via the NEF 196. The application function 188 may be considered part of the 5G core network 109. , or outside the 5G core network109 and the mobile network operator The cellular telephone network may be deployed by companies that have business relationships with the cellular telephone network.

[0066] Network slicing is a single-layer technology that is deployed behind an operator's air interface. or multiple "virtual" core networks to support mobile network operators. This is a mechanism that can be used by the The core network can be expanded to support different RANs or different service types. This involves "slicing" the network into one or more virtual networks. The system allows operators to set different requirements, e.g. in the areas of functionality, performance and separation. Customized network to provide optimized solutions for various market scenarios This allows the creation of a network.

[0067] 3GPP is upgrading the 5G core network to support network slicing Network slicing has very diverse and sometimes extreme requirements. A diverse set of 5G use cases (e.g., large-scale IoT, critical communications, virtual 2X, and advanced mobile broadband) It is a good tool that can be used by the datacenter. Each use case has its own specific set of performance, scalability, and availability requirements. When network architectures have this capability, they can efficiently address the needs of a wider range of use cases. It is unlikely to be flexible and scalable enough to be efficiently supported. ,The deployment of new network services needs to be more ,efficient.

[0068] Referring again to FIG. 1D, in a network slicing scenario, the WTRU 102a , 102b, or 102c connect to the AMF172 via the N1 interface. An AMF may be logically part of one or more slices. The AMF comprises a WTRU 102a, 102b, or 102c and one or more UPFs 1 76a and 176b, SMF174, and other network functions. UPF176a and 176b, SMF174, and other Each of the network functions may be part of the same slice or different slices. When they are part of different slices, they are shared by different computing resources. can be isolated from each other in the sense that they can share the same access, security credentials, etc. do.

[0069] The core network 109 may facilitate communication with other networks. For example, the core network 109 is a 5G core network between the 5G core network 109 and the PSTN 108. IP Multimedia Subsystem (IMS) server that acts as an interface to The IP gateway may include or communicate with an IP gateway such as ANetwork109 is a service that facilitates communication via short message service. includes or communicates with a text messaging service (SMS) service center. For example, the 5G core network 109 may include the WTRUs 102a, 102b, and 102c and the server or application function 188. In addition, the core network 170 can easily exchange may include other wired or wireless networks owned and / or operated by the provider. , providing access to the network 112 to the WTRUs 102a, 102b, and 102c. It can be provided.

[0070] The core network described herein and shown in Figures 1A, 1C, 1D, and 1E. Network entities are responsible for the implementation of the standards provided to them in certain existing 3GPP specifications. Although these entities and functions are identified by the names given, in the future, these entities and functions may be identified by other names. The specific entities or functions may be identified in future 3GPP NR specifications. may be combined in future specifications published by 3GPP, including It will be understood that, therefore, the present invention is not limited to the above-described embodiments, and may be modified in various ways without departing from the spirit and scope of the present invention. The specific network entities and functions shown are provided as examples only. The subject matter disclosed and claimed herein is either currently or hereafter defined. It will be appreciated that the present invention may be embodied or implemented in any similar communication system, regardless of whether the system is a .

[0071] FIG. 1E illustrates an exemplary embodiment in which the systems, methods, and devices described herein may be used. A communication system 111 is shown. The communication system 111 includes a wireless transmit / receive unit (WTRU) A , B, C, D, E, F, base station gNB 121, V2X server 124, and roadside unit In practice, the present invention may include RSUs 123a and 123b. The concept presented may be implemented in any number of WTRUs, base stations gNBs, V2X networks, and / or The WTRU A may be applied to one or some or all of the network elements. , B, C, D, E, and F were outside the range of the access network coverage 122. WTRUs A, B, and C form a V2X group, among which WTRUs A is the group lead, and WTRUs B and C are group members.

[0072] WTRU A, B, C, D, E, F are under the access network coverage. At one time, they communicate with each other via Uu interface 129b via gNB 121. (Only B and F are shown under network coverage in Figure 1E). WTRUs A, B, C, D, E, and F are in the access network coverage (e.g., A, C,WTRUs A, B, C, D, E, and F can communicate with each other, and D and E can communicate with each other. When the side is under or outside of network coverage of Link (PC5 or NR PC5) via interfaces 125a, 125b, 128 can communicate directly with each other.

[0073] WTRU A, B, C, D, E, and F are connected to the vehicle-to-network (V2N)126 or sidelink interface 125b to communicate with RSU 123a or 123b. WTRUs A, B, C, D, E, and F can communicate with each other via vehicle-to-infrastructure (V2I) signals. ) interface 127 with the V2X server 124. UA, B, C, D, E, and F are Vehicle-to-Personal (V2P) interfaces 128. The UE can communicate with another UE via the same UE.

[0074] FIG. 1F illustrates a WTRU 102 of the present invention, such as the WTRU 102 of FIG. 1A, FIG. 1B, FIG. 1C, FIG. 1D, or FIG. 1E. Configured for wireless communication and operation according to the systems, methods, and devices described herein FIG. 1F is a block diagram of an example apparatus or device WTRU 102 that may As such, the exemplary WTRU 102 includes a processor 118, a transceiver 120, a transmit / receive Element 122, speaker / microphone 124, keypad 126, display / touch chippad / indicator 128, non-removable memory 130, removable memory 13 2, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripherals The WTRU 102 may include a WTRU 138. It will be understood that the present invention may include, but is not limited to, a transceiver station (BT S), NodeB, Site Controller, Access Point (AP), Home Node eB, Evolved Home NodeB (eNodeB), Home Evolved Node B (HeNB), Home Evolved NodeB Gateway, Next Generation NodeB (gN Node B), and proxy nodes, which may be represented by base stations 114a and 114b. The base stations 114a and 114b and / or nodes may be as illustrated in FIG. 1F. It may include some or all of the elements described herein.

[0075] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital Digital Signal Processors (DSPs), multiple microprocessors, one or more associated with a DSP core Multiple microprocessors, controllers, microcontrollers, and application-specific integrated circuits Circuits (ASIC), Field Programmable Gate Array (FPGA) circuits, any other The processor 118 may be any type of integrated circuit (IC), state machine, or the like. , signal coding, data processing, power control, input / output processing, and / or the WTRU 102 The process may perform any other function that enables the processor to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which includes a transmit / receive element 122. FIG. 1F illustrates a configuration in which the processor 118 and the transceiver 120 are separate components. Although illustrated as components, the processor 118 and transceiver 120 may be integrated into an electronic package. It will be appreciated that it may be integrated into the cage or the chip.

[0076] The UE transmit / receive element 122 transmits / receives signals via the air interface 115 / 116 / 117. 1A), or the air interface 115d / 116d / 117d to transmit a signal to another UE or receive a signal from it. For example, the transmit / receive element 122 may be configured to transmit and / or receive an RF signal. The transmit / receive element 122 may be, for example, an antenna configured to receive a For example, an electronic device configured to transmit and / or receive IR, UV, or visible light signals. The transmit / receive element 122 may be a transmitter / detector for both RF and optical signals. The transmit / receive element 122 may be configured to transmit and receive wireless signals or radio signals. It will be appreciated that the present invention may be configured to transmit and / or receive any combination of line signals. Let it be.

[0077] In addition, although the transmit / receive element 122 is illustrated as a single element in FIG. 1F, it may be implemented as a WTR The WT 102 may include any number of transmit / receive elements 122. More specifically, The RU 102 may employ MIMO technology. Thus, the WTRU 102 may: 2 for transmitting and receiving radio signals via air interface 115 / 116 / 117 One or more transmit / receive elements 122 (eg, multiple antennas) may be included.

[0078] The transceiver 120 modulates and transmits the signals transmitted by the transmit / receive element 122. / may be configured to demodulate the signal received by the receiving element 122. In addition, the WTRU 102 may have multi-mode capabilities. The server 120 is configured to support the WTRU 102 in multiple RATs, e.g., NR and IEEE 802.11. or to enable communication via NR and E-UTRA, or different Communicating with the same RAT via multiple beams to RRHs, TRPs, RSUs, or nodes The system may include multiple transceivers to enable communication between the system and the wireless device.

[0079] The processor 118 of the WTRU 102 controls a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., liquid crystal Liquid crystal display (LCD) display unit or organic light emitting diode (OLED) display unit The processor 1 is coupled to a processor 2 and is capable of receiving user input data therefrom. 18 also includes a speaker / microphone 124, a keypad 126, and / or a User data can be output to a display / touchpad / indicator 128. In addition, the processor 118 may include a non-removable memory 130 and / or a removable The information may be accessed from any type of suitable memory, such as memory 132, and the data may be stored therein. The non-removable memory 130 may be a random access memory (RA M), read-only memory (ROM), hard disk, or any other type of memory The removable memory 132 may include a subscriber identity module (SIM) and a removable storage device. SIM cards, memory sticks, Secure Digital (SD) memory cards, etc. The processor 118 may include a cloud or edge computing platform. WT10000 on a server hosted on a home computer (not shown) or on a Access information from memory that is not physically located on the RU102 and store data in the memory can be stored.

[0080] The processor 118 may receive power from a power source 134 and may also include a power supply 134. The power supply 134 may be configured to distribute and / or control power to the components of the Any suitable device for providing power to the TRU 102 may be used. The source 134 may include one or more dry batteries, solar cells, fuel cells, and the like.

[0081] The processor 118 also generates location information (e.g., longitude, latitude, and latitude). In addition to, or instead of, information from the GPS chipset 136, the WTRU 10 2 is a signal from a base station (e.g., base stations 114a, 114b) to an air interface 115 / Receive location information via 116 / 117 and / or from two or more nearby base stations Its location can be determined based on the timing of the received signals. It will be appreciated that the location information may be obtained by any suitable location determination method. Let's do it.

[0082] The processor 118 may further be coupled to other peripherals 138. provides one or more additional features, functionality, and / or wired or wireless connectivity The software and / or hardware modules may include, for example, The peripherals 138 may include an accelerometer, a biometric (e.g., fingerprint) sensor, eCompass, Satellite Transceiver, Digital Camera (for photo or video), Universal Serial bus (USB) ports or other interconnect interfaces, vibration devices, Levi transceiver, hands-free headset, Bluetooth (registered trademark) module Frequency Modulation (FM) radio units, digital music players, media players, It includes various sensors such as a video game player module, an Internet browser, etc. This can be done.

[0083] The WTRU102 can be used in sensors, appliances, and wearable devices such as smart watches or smart clothing. Wireless devices, medical or eHealth devices, robots, industrial equipment, drones, Contained in a vehicle, such as an automobile, truck, or train, or in any other apparatus or device, such as an airplane The WTRU 102 may include an interconnect interface that may include one of the peripherals 138. Such interfaces may be connected to one or more interconnection interfaces, such as Can be connected to other components, modules, or systems of an apparatus or device do.

[0084] Figure 1G shows the RAN 103 / 104 / 105, the core network 106 / 107 / 109 , the PSTN 108, the Internet 110, other networks 112, or networks 1A, 1C, 1D, etc., a particular node or functional entity of the network service 113. and one or more devices of the communication network shown in FIG. 1E. FIG. 9 is a block diagram of an exemplary computing system 90. The system 90 may comprise a computer or server and is primarily a computer-readable The computer readable instructions may be used to control the operation of such software. The software, wherever and however it is stored or accessed, Such computer readable instructions may be implemented in a form that is readable by a computing system. The program may be executed within a processor 91 to cause the processor 90 to perform operations. 1 is a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor ( DSP), multiple microprocessors, one or more microprocessors associated with the DSP core Processors, Controllers, Microcontrollers, Application Specific Integrated Circuits (ASICs) , Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit The processor 91 may be an integrated circuit (IC), a state machine, etc. data processing, power control, input / output processing, and / or computing system 90 It may perform any other function that enables it to operate in a communications network. Co-processor 81 may perform additional functions or assist processor 91. The processor 91 is an optional processor that can be different from the main processor 91. and / or co-processor 81 may be used to implement the data associated with the methods and apparatus disclosed herein. The system can receive, generate, and process data.

[0085] In operation, the processor 91 fetches, decodes, and executes instructions to perform computing Between other resources via the system bus 80, which is the system's main data transfer path. Such a system bus transfers information in a manner consistent with the configuration of the computing system 90. The system bus 80 typically connects the components and defines the medium for data exchange. The data line is used to send data, the address line is used to send addresses, and the interrupt is used to send data to the system. An example of such a system bus 80 is a PC I (Peripheral Component Interconnect) bus.

[0086] Memory coupled to the system bus 80 includes random access memory (RAM) 82 and and read only memory (ROM) 93. Such memory is used for storing and retrieving information. ROM 93 generally cannot be easily altered. The data stored in the RAM 82 may be read by the processor 91 or other hardware. The RAM 82 and / or R Access to the OM 93 may be controlled by a memory controller 92. The address controller 92 converts the virtual address into a physical address when the instruction is executed. The memory controller 92 can also provide memory conversion functions for the processors in the system. Provides process isolation and memory protection to separate system processes from user processes Thus, a program running in the first mode can execute its own program. can only access memory that is mapped by the process virtual address space, in the virtual address space of another process, unless inter-process memory sharing is configured. You cannot access the memory.

[0087] In addition, the computing system 90 includes a processor 91, a printer 94, a keyboard 95, and a communicates commands to peripherals such as the board 84, mouse 95, and disk drive 85 A peripheral controller 83 may be included to serve the role.

[0088] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the input system 90. Such visual output can include text, graphics, animated graphics, and The visual output may include graphical user interfaces (e.g., The display 86 may be provided in the form of a CRT-based video display. Play, LCD-based flat panel displays, gas plasma-based flat panel displays It can be implemented with a panel display or a touch panel. The controller 96 contains the electronic components necessary to generate the video signal that is sent to the display 86. Includes.

[0089] Further, the computing system 90 may be To enable them to communicate with other nodes or functional entities of the network 1A, 1B, 1C, 1D, and 1E. RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, the Internet 110, the WTRU 102, or other networks 112, etc. It can be used to connect to external communication networks or devices, e.g. wireless The communication circuitry may include a wired or wired network adapter 97. , alone or in combination with the processor 91, the particular devices, nodes, , or may be used to perform the sending and receiving steps of a functional entity.

[0090] Any or all of the devices, systems, methods, and processes described herein may include: Computer-executable instructions (e.g., programs) stored on a computer-readable storage medium The instructions may be embodied in the form of a program code, such as a program code, which may be implemented by a processor, such as processor 118 or 91. When executed by a processor, the processor performs the systems, methods, and It is understood that the present invention relates to performing and / or causing a process to be performed. Any of the steps, operations, or functions described herein may be implemented using wireless and / or wired networks. on a processor of a device or computing system configured for network communication Such a method may be embodied in the form of computer-executable instructions that are executed by a computer. A readable storage medium is any non-transitory (e.g., tangible or physical) method for storing information. Volatile and non-volatile, removable and non-removable, implemented in any method or technology Although such computer-readable storage media includes media, such computer-readable storage media does not include signals. The readable storage medium may be a RAM, a ROM, an EEPROM, a flash memory or any other memory technology. technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage device , magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other desired information, and may be used by a computing system. This includes, but is not limited to, any other tangible or physical media accessible through Not determined.

[0091] (5G System Architecture) FIG. 2 shows a 3GPP 5G LTE network with various entities interacting with each other via the indicated reference points. A non-roaming system architecture is shown. A user equipment (UE) 102 transmits control signaling. To establish a ring and allow the UE 102 to use services from the CN, It is capable of communicating with the Network (CN). Examples of control signalling functions are registration, connection These include connectivity and mobility management, authentication and authorization, and session management.

[0092] The following Network Functions (NFs) in Figure 2 are responsible for the control processes of the CN related to control signaling: He is the main NF in the lane (CP). Access and Mobility Function (AMF) 172: The UE 102 is responsible for registration, connection management, Performs a lot of control plane signaling such as mobility management, access authentication and authorization To do so, the RAN node 105 sends an N1 message to the AMF 172. Session Management Function (SMF) 174: The SMF 174 is responsible for the UE communicating with the Internet or The data network (DN) 208 and other sessions, such as application servers, Related to establishing a PDU session to allow data to be sent to application management related functions. It is responsible for session management. Policy and Control Function (PCF) 184: The PCF 184 manages network behavior. Provides a policy framework for managing enrollment information and making policy decisions do. Authentication Server Function (AUSF) 190: AUSF 190 is a 3GPP and untrusted Supports authentication of the UE for non-3GPP access. Unified Data Management (UDM) 197: UDM 197 is a 3GPP AKA certification credential It supports the generation of user IDs, user identification processing, subscription management, etc. Network Slice Selection Function (NSSF) 216: The NSSF 216 is a Network slice management, such as network slice instance selection and NSSAI management It is involved in aspects of the management of the Radio Access Network (RAN) 105: The RAN node 105 is the control plane A communication access point from the UE 102 to the core network for both communication and user plane communications. Provide access to

[0093] (5G Roaming Architecture) FIG. 3 shows a service-based VPLMN in which the VPLMN is the visited PLMN and the HPLMN is the home PLMN. 5G System Roaming for Local Breakout Scenarios in Service-Based Representation The Security Edge Protection Proxy (SEPP)3 shows the architecture of the 04 enables communication between the VPLMN and the HPLMN.

[0094] Figure 4 shows the 5G system topology for the local breakout scenario in the reference point representation. The following figure shows the timing architecture of the 10GbE ... The AMF of the VPLMN communicates with the AUSF of the HPLMN via the N12 interface. The policy information is transmitted to the HPLMN via the N24 interface. The vPCF and the hPCF may communicate with each other via this interface.

[0095] (5G registration procedure) Before a UE can use the services provided by the CN, the UE must connect to the core network. Figure 5 shows the procedure in TS 23.502 that a UE performs to register with a CN. The 5G general registration procedure is shown below from [2]. The following are noteworthy steps in the general registration procedure: be. In step S500, the UE performs a registration request to indicate what the request is for. Two common types are provided for the UE to first establish registration with the CN. The initial registration is performed by the UE and the CN is notified that the UE is still present. In addition, the UE may also update the registration step during initial registration. In step S510, the CN is provided with an identifier such as a SUCI that the CN uses to authenticate the UE. It is possible. In steps S502, S504, S506, and S508, the AMF If not provided in 00, the UE's SUCI can be obtained. In step S510, the AUSF receives the subscription information and the UDM provided by the AUSF. Authenticate the UE based on the SUCI provided by E. In step S512, the AMF sends a registration acceptance message to the U to indicate the result of the registration procedure. In the case of initial registration, the acceptance message includes a temporary identifier such as 5G-GUTI, List of enabled network slices, DRX parameters, and other information for UE operation The 5G-GUTI identifier identifies the paging request for the UE. Contains the 5G-S-TMSI identifier used for

[0096] (Registration, Attachment, and Radio Resource Control Management States) In 5GS, the UE maintains a managed state to enable communication with the core network. These management states are Registered (RM), Connected (CM), and Radio Resource Control (RRC ) Management state. The management state is maintained in both the UE and the RAN / CN.

[0097] In order for a UE to use the services provided by the CN, the UE must perform an initial registration procedure. Once registered, the UE must register with the CN by executing the , from RM-DEREGISTERED state to RM-REGISTER The UE enters the RM-REGISTERED state with the network. To do so, a periodic registration update must be performed. When in this state, the UE cannot access services provided by the CN. .

[0098] The connection management (CM) state shown in Figure 7 is the connection between the UE and the AMF via the N1 interface. This signaling connection allows the UE and the CN to: Capable of communicating information via the control plane for efficient communication within a 5G system become.

[0099] Finally, the UE also maintains the RRC state with the RAN node and communicates with TS 38 as follows: .300[4]. RRC_IDLE: In this state the UE performs PLMN selection and In addition, the UE enters discontinuous reception (DRX) mode. It can monitor paging requests from the 5GC. RRC_INACTIVE: In this state, the UE is notified that a paging request has been received by the RAN node. It performs functions similar to those of RRC_IDLE, except for the fact that it is initiated by In addition, the UE and RAN nodes must ensure that the UE transitions quickly to the RRC_CONNECTED state. When in this state, the RAN node maintains context information that allows it to Both the control plane connection and the user plane connection between the UE and the 5GC are established for the UE. can be. RRC_CONNECTED: Unicast data transfer between the UE and the This is enabled when both the CP and UP are in the RAN node for the UE. The context information is established between the UE and the RA to enable communication. This is because it is held between the N nodes.

[0100] (5G paging mechanism) Paging is initiated by either the core network or the RAN via CM-IDLE or RR. Pending data destined for the UE in C_IDLE / RRC_INACTIVE state TS 38.304[5] specifies the mechanism for notifying the power supply during periods of inactivity. In order to reduce power consumption, the RRC_IDLE and RRC_INACTIVE states Provides a description of a UE that uses Discontinuous Reception (DRX) when a connection is established. During DRX, the UE is informed of activities in the CN that may require the UE to The UE monitors the Paging Occasion (PO) of the UE. information provided by the UE_ID to know when to monitor paging occasions The calculation is based on the UE_ID, which is the IMSI or 5G-S-TMSI. The network identifier is calculated by modulo 1024 the identifier for the network. On the network side, paging works in 5G similarly to LTE paging shown in Figure 23. do.

[0101] (identifier) Section 5.9.4 of 23.501 includes the 5G Globally Unique Identifier (5G-GUT I) is described. 5G-GUTI is composed as follows: <5G-GUTI>:= <guami><5G-TMSI> Here, GUAMI identifies the assigned AMF, and 5G-TMSI is unique within the AMF. The UE is identified by the The Globally Unique AMF Identifier (GUAMI) shall be constructed as follows: <guami> := <mcc> <mnc><AMF Region ID> MF Set ID><AMF Pointer> The AMF Region ID identifies the region, and the AMF Set ID identifies the It uniquely identifies an AMF Set, and an AMF Pointer points to an AMF within an AMF Set. Identify intentionally. Note 1: AMF Region ID is the same for the same AMF Set in different regions operated by different operators. AMF by allowing IDs and AMF Pointers to be reused More AMFs than can be supported by Set ID and AMF Pointer Dealing with the case where there are many AMFs in the network. NOTE 2: For details on the structure of the GUAMI fields, see TS 23.003

[19] . Please refer to. 5G-S-TMSI will enable more efficient over-the-air signaling procedures (e.g. paging and It is an abbreviated form of GUTI to enable the can be. <5G-S-TMSI>:=<AMF Set ID><AMF Pointer> <5G-TMSI>

[0102] (Slice-specific authentication and authorization) In Release 16 of the 5G system, 3GPP will introduce slice-specific authentication and authorization mechanisms. This procedure is required for the UE to be able to receive the LTE-2000 from a particular slice (i.e., S-NS The network initiates an EAP-based procedure with the UE when it attempts to register to the UE (SAI). The EAP-based authentication procedure allows access to the slice. In order to be able to receive the ​The new procedure is described in references [7] and [8] and is shown in Figure 8. Figure 8 is copied from reference [8].

[0103] (LTE system architecture) Figure 19 shows how a user equipment (UE) can receive Internet services or other operations such as IMS. 3202 to obtain the core network (C The figure shows the 3GPP EPS non-roaming system architecture communicating with the E-UT. The RAN interfaces with the UE via the LTE-Uu interface. The UE communicates with the access network (RAN) via the S1-MME interface. Access to CN by using NAS signaling via E-UTRAN, S1- Data is transmitted and received via E-UTRAN via the U interface.

[0104] The following network functions (NF) in FIG. 19 are briefly described below. Mobility Management Entity (MME): The MME provides NAS signaling to the UE. It provides authentication and authorization for UEs to access the CN, while providing UE mobility. Among the many functions it performs is management. Home Subscriber Server (HSS) 2000: The HSS 2000 provides authentication / authorization of the UE. It also stores the UE subscription information. Serving Gateway (S-GW) 2002: The S-GW 2002 is a gateway that serves both the P-GW and The User Plane (UP) routes and forwards traffic between the UE and the Serves as a mobility anchor point for PDN Gateway (P-GW) 2004: The P-GW 2004 provides the IP address to the UE. and assign addresses to the UE to provide access to packet data networks such as the Internet. to be provided. Policy and Charging Rules Function (PCRF) 2006: Core network policy and billing elements.

[0105] (LTE Attach Procedure) The UE registers with the core network and receives services from the core network that require registration. To use the service, the attach procedure is performed. Figure 20 shows the attach procedure, Several notable steps are highlighted below relative to the initial attachment. In step S2000, the UE sends an attach request to the CN via the eNodeB. In the request, the UE sends the identity (IMSI), the attachment type, the UE core network network performance, UE specific DRX parameters, preferred network behavior, and the The URI provides other message parameters that are specified. In step S2002, the eNodeB selects an appropriate MME and The request is forwarded to the ME. In steps S2004a and S2004b, the MME is required to: Authentication and NAS Security to activate Integrity Protection and NAS Encryption Perform setup. The MME communicates with the HSS to complete this step. From this point on, the NAS signaling is protected for both integrity and encryption. In step S2006, the MME receives the GUTI, the TAI list, and the session management request. The required information, the supported network behavior, the service gap time, and the The ATTACH_ACCEPT() function returns an attach accept, including other message parameters as specified in the ATTACH_ACCEPT() message. In step S2008, the eNodeB returns an attach accept message to the UE. The UE stores the message parameters for future use. There may also be a ring. In step S2010, the UE sends a direct transfer message including an attach complete message. In step S2012, the eNodeB returns an attach complete message. The UE forwards the message to the MME.

[0106] (EPS Mobility Management and Connectivity Management State) The EPS Mobility Management (EMM) states are shown in Figure 21. The UE is initially in the EMM-DER After being in EGISTERED state and successfully connecting to the network, Enters EMM-REGISTERED state. Once registered, the UE can connect to the Internet. and use the services provided by the network, such as making IMS calls. The UE can update the EMM-RE by performing the Tracking Area Update (TAU) procedure. It remains in GISTERED state and can be removed by performing the detach procedure. It can be in the REGISTERED state.

[0107] The EPS connection management states are shown in Figure 22. These states represent the state between the UE and the core network. Indicates the state of the NAS signaling connection. In ECM-IDLE, the UE is ECM-IDLE to ECM-PRESET has no routing connection and performs cell and PLMN selection. The transition to the CONNECTED state is accomplished by the following steps: attach request, tracking area update. This is done for new, service requests, and detach requests.

[0108] (LTE paging and service requests) The UE 102 is in ECM-IDLE state and data is being When available, the MME 162 sends a paging request to the UE 102 as shown in FIG. Then, after performing the service request procedure, the UE 102 sends a page related It can then connect to the core network to receive the attached data. The S-GW 2002 stops paging the UE 102 and the downlink data is The TS 36.304[5] specifies the discontinuous reception ( Calculation of the paging occasion of the UE in the DRX (Dynamic Reception), and determining the paging occasion based on the UE's identity. Based on the calculation, the two UEs They have the same paging occasion and can monitor for paging messages at the same time. The message identifies the recipient of the page using the associated UE identifier.

[0109] (Problem Statement) A UE with multiple USIMs has registrations with more than one operator network. It can be applied to various use cases that take advantage of the 3GPP SA1 work. King Group's MUSIM research, TR 22.834[6], includes multiple USIMs. This disclosure highlights scenarios where use cases may exist. Focus on cases where the technology has common radio and baseband building blocks to support Therefore, the radio and baseband components are not dedicated to a single USIM. This disclosure also addresses dual Rx, single Tx, which is within the scope of the MUSIM research. To provide a solution for the UE.

[0110] The MUSIM SA1 study highlights the potential requirements for multiple USIM UEs. Some of these requirements are: Support for UEs with multiple USIMs in 3GPP systems Support for single Rx, single Tx and dual Rx, single Tx UE implementations port Allows users to configure preferences for services from multiple USIMs MUSIM UE for 3GPP systems use MU with multiple USIMs from the same or different operators. Need to support SIM UE To indicate the type of traffic to the MUSIM UE that triggered the paging procedure 3GPP System 3GPP systems can suspend active communications and terminate communications with multiple USIM UEs. In the case of a communication that has been suspended, the communication can be resumed. 3GPP system has paging collision for paging with multiple USIM UEs Minimize 3GPP systems support multiple USIMs to improve signaling operations. Bar head shall be minimized. MUSIM UE needs to be supported by both 5G and LTE systems. R The terms SIM and USIM (as used in TR 22.834[6]) Please note that the terms are used interchangeably in this disclosure. The terms LTE and EPS are used to refer to multiple USIMs. It should also be noted that the terms are used interchangeably in this disclosure.

[0111] (Use Case 1) A user is traveling internationally from the United States to Asia and has a UE that supports multiple USIMs. For cost reduction purposes, the UE may use a common radio access point shared by the USIM. and baseband components. As a result, only one USIM can be Users cannot activate cellular service while traveling within the destination country. Purchase a USIM card when you arrive to access the service. A mobile USIM card can be used for local voice, The USIM for home use provides services for text, text, and high-speed data, while the USIM for home use provides services for mobile phones, Provides voice and text messages that users may want to receive from family and friends while on the go It is primarily used to

[0112] (Use case 2) Another prominent use case for multiple USIMs is the use of both business and personal subscriptions. The focus is on users who have both services and want to use both on the same device. The user has an enterprise-issued UE with a USIM1 subscription service with operator 1, while The user also has a personal subscription service for USIM2 with operator 2. Depending on the time or the application using the service, USIM1 or USIM2 By subscribing to either IM2, you can receive voice calls from either service and use data services. They hope that they will be able to access the services.

[0113] (assignment) As can be seen from the above use cases, common radio and baseband building blocks are utilized. A multi-SIM UE that uses a LTE network must decide which SIM to serve at any given time. Current implementations of multi-SIM UEs are proprietary and as a result implementations may vary. The UE's behavior may vary. Many actions and This difference in behavior can have a negative impact on the operation of the core network as algorithms and protocols are optimized. Both the 3GPP SA1 and SA2 working groups have We are currently studying issues related to supporting UEs with multiple SIMs.

[0114] In these studies, we standardize multi-SIM UE and corresponding procedures to improve the UE behavior. It provides the core network with knowledge of the optimal behavior of the UE communicating with either network. This work is proposed to enable the operation of multiple SIMs in the UE. The focus is on UE implementations where common radio and baseband components are used to How the UE informs the CN of its multi-SIM capability and whether the UE How does it know when to monitor the paging opportunities associated with page M? , how the UE switches operation from one SIM to another, and how it manages the use of SIMs. How the UE informs the CN when switching and how to minimize paging collisions How the UE provides service type prioritization across multiple SIMs Issues such as whether to use the policy have yet to be decided. In addition, multiple SIM U Support for E is expected in both LTE and 5G systems.

[0115] For UEs operating with multiple SIMs and using common radio and baseband components One major issue that arises is the use of a second SIM while actively communicating with a first SIM. This is a problem of monitoring paging information by the SIM associated with multiple SIMs. When paging opportunities overlap in time, they are called paging collisions. The UE decides to monitor a single paging channel over other paging channels. This decision must be made at the time of the paging opportunity for the inactive SIM. Not monitoring the paging requests may cause the UE to miss pages.

[0116] In some scenarios, paging collisions may occur for multi-SIM UEs. One scenario is when the UE connects to the network with the active SIM. It may be that the SIM is not actively monitoring paging opportunities for the inactive SIM. Because the UEs share a common baseband and radio components, the UE can receive one Connects to a network and monitors paging opportunities associated with that network's SIM If the page is sent for a SIM in another network, the UE cannot receive pages. This is a RAN node that may be used for other purposes. This wastes radio resources in the

[0117] Another cause of paging collisions is when paging occasions for multiple SIMs overlap in time. Again, the UE is associated with one SIM via a single transceiver. Paging opportunities can be monitored and processed. When the UE is close to the other network, the UE has enough time to switch to the other network. No. This again wastes radio resources in the RAN node.

[0118] A multi-SIM UE may monitor paging occasions associated with multiple SIMs. Even if it were possible, the constant switching performed to achieve this would result in a higher power consumption of the UE. This results in lower power consumption and shorter battery life. Furthermore, the UE is The connection may be switched to unavailable and there is no data for the UE. The UE may not be paged. A side effect of frequent switching is that the UE may not be paged. This may create a scenario where collisions occur and the UE may need to conserve battery power. The problem is that the UE cannot enter the DRX cycle immediately.

[0119] (overview) Previously, multiple SIM UEs were managed by device manufacturers without knowledge of the core network. It is a proprietary solution implemented by various entities ( The behavior of the UE, RAN, and CN is well defined and known among the various entities. The operation of the cellular network was designed. Various implementations of existing multi-SIM UEs So, various behaviors can adversely affect the operation of the network and degrade its performance. As a result, MUs from the 3GPP SA1 and SA2 working groups SIM research focuses on architectures, interfaces, and methods to support UEs with multiple SIMs. The IASB is to define the interfaces, procedures, and procedures for implementing the IASB.

[0120] The requirements outlined in the MUSIM study are based on the need for multiple SIMs installed in the UE. UE with shared common radio and baseband components and dual Rx; The focus of the MUSIM work is on single Tx UEs. The UE with IM should provide the best possible service for each of the SIM operations. The central focus of the research is to develop a UE with common radio and baseband components. How can we provide seamless paging monitoring for multiple SIMs? In this disclosure, we address that issue and also the case of dual Rx, single Tx UE. A solution is also proposed for the following: -Multiple SIM UE notifies the core network that it is a multi-SIM device , to enable the UE to provide information about other SIMs installed in the UE Define enhancements to UE registration and attach procedures New registration management for both UE and CN to maintain UE registration state per SIM Defines a state, substate, or mode of behavior Allows paging request forwarding from one PLMN to another to reach the UE Define an enhancement to the existing paging request mechanism to allow SIM switching, where the UE can indicate to the CN that the UE is switching to a different SIM Define the handover procedure and update the UE registration status in the CN and the UE at the same time. - Performed through active PLMN to maintain registration timers for inactive SIMs defines an inactivity registration timer update procedure that After the UE decides to switch to the inactive PLMN, Cell measurements taken for an inactive PLMN when attempting to establish a connection to Define procedures that can provide A new paging opportunity where the paging opportunity is aligned or separated from the paging opportunity of another SIM Defines the procedure by which a UE can request a temporal identifier A procedure by which the UE can request to pause the registration timer, and the CN Define steps that will result in the program also pausing. Defines the procedures by which the UE or CN may provide other information related to the paging process do Define new policies in 5G UE policies to allow multiple SIM configurations and gives the user the ability to initiate manual switching between SIMs through the GUI

[0121] Concept 1: The UE informs the CN that it is a multi-SIM device and Provide CN with the information required to The UE sends a request to the first PLMN to register the second SIM in the second PLMN. believe The UE receives an indication and an identifier for a second SIM to be registered in a second PLMN. include The first PLMN forwards the request to the second PLMN The second PLMN authenticates the UE's SIM credentials and initiates paging for the second SIM. providing the UE with a temporary identifier to be used in the logging request; The UE and the second PLMN update the registration state of the UE for the second SIM. Supplementary features of concept 1: The UE is registered with a first PLMN for a first SIM. The request is either a partial registration / attach or an indirect registration / attach request The UE is registered to a first PLMN and is requesting registration to a second PLMN. This instruction is a multi-SIM instruction The identifier of the second SIM is the following: SUPI (e.g. IMSI), GUTI, 5G-S- Can be one of TMSI or SUCI The temporary identifiers assigned to the second SIM are 5G-GUTI, GUTI, 5G- Can be TMSI, TMSI, or 5G-S-TMSI The first PLMN is an identifier of a network node that supports multi-SIM operation; and an identifier of the first SIM authenticated with the first PLMN. The UE registration state is RM-INACTIVE after successful registration to the second PLMN. or EMM-INACTIVE The first PLMN assigns a second temporary identifier for the second SIM and The registration state of the UE for IM can be stored The UE provides multi-SIM support information to the CN, and the multi-SIM support information is used for paging. Criteria, restricted paging area, paging opportunity separation, number of pages missed before notification, suggested may consist of one or more of the temporary identifiers

[0122] Concept 2: The first PLMN forwards the paging request to the UE through the second PLMN. The first PLMN receives data associated with the first SIM. The first PLMN forwards a paging request to the second PLMN, and the paging request is Contains a temporary ID associated with the first SIM The second PLMN sends a paging request to the UE on the paging occasions that the UE monitors. Send The UE retrieves the paging information and the temporary identifier associated with the first SIM. Receive Supplementary features of concept 2: The UE supports multi-SIM operation The UE has concurrent registration with both the first PLMN and the second PLMN The UE has an inactive registration with the first PLMN The UE has an active registration with a second PLMN The paging request is sent from the first PLMN to the second PLMN with the encrypted NAS content. Sent in The paging occasion is calculated from the temporary identifier of SIM1. Paging occasions are calculated from the temporary identifier of SIM2 Paging information includes the service category of what the page is for and the sound voice calls, SMS messages, or other data (e.g. application data), Control plane signaling, emergency messages, emergency callback, mobile terminated exception data can be classified as Paging information includes the PDU session ID and application associated with the page. Include session ID The UE sends a response through the second PLMN to the first PLMN

[0123] Concept 3: The UE performs the SIM switching procedure. The UE, while connected to the first PLMN, Receive paging information from the The UE shall determine the priority of the paging information based on the service type prioritization indicator provided in the paging information. Based on this, it decides to switch to a second PLMN to retrieve data. The UE notifies the first PLMN to suspend the registration state of the first SIM. The UE and the first PLMN establish a registration state of the first SIM on the UE and the first PLMN. Update the status The UE attempts to establish communication with a second PLMN for the second SIM. Supplementary features of concept 3: Paging information is the service category associated with the data for which the UE is paging A service type priority that may include a policy, PDU session ID, and application ID. Provide prioritization The UE checks the prioritization of service types against its internal policies and finds a match. find The UE sends a registration update request with registration type set to SIM switching The first PLMN activates paging request forwarding for the first SIM. The registration state of the first SIM is RM-INACTIVE in the UE and the first PLMN. Set to VE or EMM-INACTIVE The first PLMN sends a response to the second PLMN from which the UE received the paging request. R Establishing communication with the second PLMN includes registration updates, including SIM switch registration types. This includes sending a new request.

[0124] Concept 4: The UE updates a registration timer of the second PLMN through the first PLMN. The UE is instructed to update the registration timer of the second SIM on the second PLMN. Send a request to the MN The first PLMN forwards the request to the second PLMN The second PLMN updates the registration timer for the second SIM in the second PLMN. do The second PLMN responds to the first PLMN The first PLMN forwards the response to the UE Supplementary features of concept 4: The request may be a registration update, a tracking area update, or an inactivity registration timer update. stomach The request includes a temporary identifier associated with the second SIM. The response may indicate the status of the registration update request, the new value of the registration timer, or the updated TA I can contain lists The response may include an indication that the registration status of the second SIM is no longer valid. R The second PLMN assigns a new temporary identity for the second SIM and sends it to the UE. You can include it in the response

[0125] Concept 5: The UE collects cell measurement information while attached to the second PLMN after the SIM switching procedure. The LTE-2000 will then collect the LTE-2000 and connect directly to the second PLMN upon connection, or to the first PLMN if the connection is unsuccessful. Provide measurements through MN. While the UE attempts to connect to a second PLMN after disconnecting from a first PLMN , Collect cell measurements The UE provides cell measurements to the RAN node after successfully connecting to the second PLMN. R The UE connects to a first PLMN after a failed attempt to connect to a second PLMN and Includes collected measurements and cause codes The first PLMN forwards the measurement and cause code to the second PLMN. Supplementary features of Concept 5: If the UE successfully connects to the second PLMN, the UE transmits cell measurements to the second PLMN. Formatting the MN to RAN node drive test into a minimized report Cell measurements indicate the signal strength of cells belonging to the second PLMN Cell measurements include the location and time the measurement was taken Cell measurements are queued by the UE and sent to the RAN upon a future successful connection. can be sent to the node The UE stores the cell measurements and cause code after the connection to the second PLMN fails. do The cause code may be received from the second PLMN or may be generated by the UE. R The cause code indicates that the RAN node is overloaded and will not accept new registrations. can The cause code indicates that the mobility management node is overloaded and cannot accept new registrations. It can be shown that The cause code indicates that the cell signal strength is not sufficient to maintain a connection with the second PLMN. It can show that it is not strong Cause code indicates that there is no cell available to establish a connection with the second PLMN It can be shown

[0126] Concept 6: The UE shall ensure that the paging occasion is aligned or separated from the paging occasion associated with another SIM. Request a new temporary identifier that is released. The UE is registered to a first PLMN and has an associated paging occasion for a first SIM. A temporary identifier has been received The UE is registered to a second PLMN and has associated paging occasions for the second SIM. A temporary identifier has been received The UE determines that there is a possibility of paging collision between the paging occasions of the two SIMs. R The UE receives a new temporary identifier whose paging occasion is different from the previous paging occasion. Make a request to get Supplementary features of Concept 6: Requests can be, for example, initial registration, mobile registration update, periodic registration update, attach, or may be one of the tracking area update requests The UE requests to assist the network in allocating a new temporary identifier. You can provide parameters in New parameters include, for example, paging criteria, restricted paging area, paging mechanism, separation, multi-SIM indicator, temporary identifier, or multiple paging opportunities. obtain The network shall ensure that the paging occasion is the same as an existing paging occasion, e.g. The temporary identifiers may be assigned to the same or different locations, such as nearby, far away, or different The network assigns multiple temporary identifiers to the UE, corresponding to multiple paging occasions. Can hit

[0127] Concept 7: The UE requests to pause the registration timer associated with the SIM The UE registers with the PLMN and the PLMN starts the registration timer The UE sends a request to activate the registration pause timer CN pauses the registration timer and starts the registration pause timer CN provides response that registration pause timer is active Concept 7 Supplementary Features: Requests can be, for example, initial registration, mobile registration update, periodic registration update, attach, or may be one of the tracking area update requests The UE may provide an expiry value for the registration pause timer The UE shall not attempt to transmit any downlink Can request CN to queue data CN manages the U, e.g. registration state, security context, PDU sessions, etc. Holds a context for E The CN can return a new value for the registration pause timer expiration. The CN provides instructions to queue downlink data for the UE. It is possible to

[0128] Concept 8: The UE or CN provides information about issues related to the paging process The UE has multiple SIM registrations The UE is receiving data from the first SIM The UE receives the page of the second SIM The UE or CN notifies the other of a problem with the paging process. do Concept 8 Supplementary Features: The notification may be a request sent by the UE The request may be, for example, a mobile registration update, a periodic registration update, a tracking area update, or a service It may be one of the service requirements. The UE may provide an indication for the CN to stop paging the UE A notification may be a response sent by a CN The response may be, for example, an instruction to inform the UE that it has missed a previously transmitted page, The time on the page, the tracking or registration area from which the page was submitted, and the service category , phone number, PDU session ID, and application ID. It may contain other information

[0129] Detailed Description As highlighted by the MUSIM study [6], a common radio and baseband Current multi-SIM UE implementations with components can degrade network performance This raises many issues regarding the different UE behaviors. In this case, the UE should use the newly proposed registration request to notify the core network of the support for multi-SIM function. The network communicates to the network and the network provides service prioritization information in the paging message. and enables paging request forwarding to minimize UE switching cycles between SIMs A more integrated solution is proposed that enhances the paging mechanism through With these enhancements, the UE can now switch operations to monitor paging opportunities for each SIM. Instead of requesting the UE to send paging notifications calculated for the active SIM, Just monitor the opportunities and you will receive prioritization information for multiple SIM pages. In addition, the network will be able to use the new SIM switching procedure and the UE registration state Enhancements to the UE to recognize new registration states, sub-states, or modes of operation. This enhancement is intended to allow entities in a cellular system to support the operation of multi-SIM UEs. The solution proposed here is based on the following assumptions: To be designed. 1. UE implementations with multiple SIMs share common radio and baseband components. Several solutions are presented to address dual Rx, single Tx capable UEs. 2. Multiple SIMs can be in the same or different PLMNs (PLMN is a mobile network from the network of different operators (also called operators or MNOs) It is something 3. Optionally, PLMNs may have roaming agreements with each other and may use the roaming rules proposed herein. It can support SIM authentication like 4. Security support for multi-SIM operation between UE and core network has been established 5. Both the UE and the core network must support the multi-SIM functionality proposed in this specification. Support

[0130] However, there may be cases where there is no coordination between mobile network operators or MNOs. In these cases, alternative solutions are presented that do not require coordination between MNOs, and the UE can now The network assigns different temporary identifiers corresponding to different paging occasions to the assigned PO. This and other solutions can also be implemented without MNO coordination. Certain aspects of the solution associated with MNO coordination are presented to address this scenario: Note that it can also be used in scenarios without MNO coordination, e.g. The core network assigns temporary identifiers to the same PO for each MNO. This can be used in the intra-MNO case where multiple SIMs belong to the same MNO. It can be used for.

[0131] The solution to support multi-SIM UE is to support both 5GS and LTE systems. Therefore, this disclosure is intended to provide a method for applying the proposed solution to both 5GS and LTE systems. If a solution is shown for only one system, the solution can be easily adapted to other systems.

[0132] FIG. 9 shows the main steps of the proposed solution for a UE with two SIMs, The solution can be extended to UEs with more than two SIMs. The UE is shown registering to two PLMNs using SIM1 and SIM2. , who has subscriptions to both SIM1 and SIM2 and mainly uses SIM1 to connect to PLMN1 and at the same time registers with PLMN2 for SIM2 for further processing. 1. Request PLMN2 to forward the paging request of U to PLMN1. E uses SIM1 on PLMN1 to receive paging requests for both SIM1 and SIM2. It only needs to monitor the paging occasions associated with IM1. by monitoring only paging occasions associated with SIM2 on PLMN2. Therefore, when the UE is communicating with PLMN2, it sends pages to both SIM1 and SIM2. The UE can receive a request for multiple SIMs, e.g. While you can receive pages for active PL and inactive SIMs, Note that we only monitor paging occasions on the MN. The inter-registration and paging request forwarding features enable the UE to operate in this way: This reduces the power consumption required and still allows receiving pages for multiple SIMs. It is possible.

[0133] Two different LTE systems are used to link SIM1 and SIM2 in each PLMN. Two registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in Figure 9. The registration procedure is the same whether it is for SIM1 or SIM2. First, all paging requests are sent to the UE on the PLMN where the UE is actively registered. In other words, it allows paging requests of inactive SIMs to be received by The request is received during the paging occasion of the active SIM. You can receive pages from multiple SIMs without having to constantly switch connections between LMNs. This solves the paging collision problem mentioned above.

[0134] The SIM switching procedure is performed when the UE establishes communication with an inactive PLMN to respond to paging requests. Complete the request or use the subscription services associated with the inactive SIM. The active PLMN is notified to suspend the registration state of the UE so that Using this procedure, the UE can detect the presence of two SIMs. Switching between subscribed services offered by the UE and which PLMN the UE is active in at any given time It still sends paging requests to any SIM, regardless of whether it is registered This procedure informs the core network of the UE's intention to switch connections between PLMNs. It notifies the network, thereby, what the UE is doing with multiple SIM applications. Solve network problems that you never knew existed.

[0135] Step S900: The UE registers to PLMN1 using SIM1 and performs P The UE provides multi-SIM indication to PLMN1 to inform the UE that Informing PLMN1 that it is a multi-SIM device and the part shown in step S902b UE identifier of SIM2 used in the registration procedure (e.g. SUPI (e.g. IMSI), Multi-SI can provide GUTI, 5G-S-TMSI, or SUCI. The inclusion of the M indication and UE identifier(s) indicates that the UE is to perform the UE initial registration procedure. Supports the case where two SIMs are installed before. This step is for the second SIM Insert IM, download second SIM profile to eSIM, instructions from GUI or through a power cycle event. Step S909: Alternatively, the UE may determine that it is a multi-SIM device. to PLMN 1 separately to initiate the partial registration procedure shown in step S902b. , the UE identifier of SIM2 can be provided to PLMN1. Note that S902a is a different approach to initiating the partial registration procedure. For example, step S902a may be used to determine if two SIMs were installed at different times. In step S902b, the PLMN 1 may transmit the The AMF of PLMN1 registers with the AUSF and and / or UDM to link the two SIMs together. The following information: an indication that partial registration has been requested; that the UE is a multi-SIM device; an indication that SIM1 is authenticated with PLMN1; It can also provide registration instructions, multi-SIM support information, etc. MN2 can store this information in UDM2, while PLMN1 can store the same information in In addition, the information returned to the UE after successful registration (such as the temporary identifier) ​​is stored in UDM1. The UE identifier in this case can be a permanent identifier used to associate the UE with the SIM. It can refer to both permanent and temporary identifiers. Multi-SIM support information is This work is provided to help enhance the paging process for multi-SIM UEs. It is possible. Step S904: As an alternative to partial registration, the UE establishes a registration state with PLMN2. To achieve this, an indirect registration of SIM2 with PLMN2 can be performed through PLMN1. This can be done in either the control plane or the user plane. If the registration is successful, the result will be TS 23.502[2] General Registration, i.e. Temporary Registration. Outlined with allocation of identifiers, network slices, update timers, DRX parameters, etc. As shown in Figure 1, this is the same as the result of the UE establishing a registered state with the core network. However, certain enhancements as proposed below for multi-SIM operation may be required for indirect registration. This registration procedure puts the UE into RM-INACTIVE state and is followed by the general registration procedure. The UE may be provided with a set of temporary identifiers different from those returned by the procedure. as well as the links established by partial registration to enable paging request forwarding. , SIM1 and SIM2 can be linked together on PLMN2. Similarly, indirect registration may be initiated as part of a general registration or may be a separate registration step. Step S900 and S902a (i.e., steps similar to those for indirect registration) It may be started standalone as a . Step S906: After a while, the UE receives a paging request from the PLMN1 to the SIM2. The paging request originates from PLMN2, which forwards the request to PLMN1. The detailed paging information is sent in encrypted NA format to protect the privacy of the UE. Note that a page may be sent from PLMN2 to PLMN1 within an S container. The paging request is found on a paging occasion associated with SIM1 and the UE When the paging information is read, the paging information is associated with SIM2. to allow the user to make a decision about whether to continue processing the paging request. In addition, the UE may perform a service request procedure. and receiving an encrypted NAS container with service prioritization information. Thus, more detailed paging information can be obtained. The ping request is sent by the UE as a NAS indication through the network user plane. may be received. Step S910: The UE needs to perform a "SIM switching" procedure towards PLMN2. PLMN1 knows SIM2 and notifies PLMN1 that it needs to Since PLMN1 has linked information for This procedure assists in changing the registration state of the UE on PLMN1 to RM-INACTIVE. This changes the UE's registration to PLMN1 to indicate that it is temporarily suspended. To achieve this, a new registration state, RM-REGISTERED, is proposed in this solution. , sub-state, or operating mode. The UE's context in PLMN1 is to switch to using SIM2 on PLMN2. The saved context allows the UE to operate back to PLMN1. Other alternatives to the SIM switching procedure have also been proposed, including multi-S The IM UE can notify the network to suspend the registration status of one SIM. As a result, the UE can communicate with another SIM. Then, the network forwards the paging request and filters the paging message to the UE. paging mechanism, such as forwarding data to the UE and buffering downlink data can be changed. Step S912: The UE changes the registration state of SIM2 from RM-INACTIVE to RM- The UE performs a periodic registration update procedure to change the UE to REGISTERED. Cell search, PLMN selection, and RRC connection establishment with RAN2 before performing a regular registration update. Note that it may be necessary to first perform procedures including Upon receiving the paging request, the UE then performs a subroutine to retrieve the data associated with the paging request. Either the Service Request procedure or the PDU Session Establishment procedure can be performed. E may perform service requests as an alternative to periodic registration updates. Step S914: The UE receives a packet for retrieving data associated with the paging request. After completing the session, the UE shall proceed with the step SIM switching procedure. As shown in S1914a, the registration status of SIM2 is temporarily suspended, and then, in step S191 The registration status of SIM1 can be reactivated as shown in 4b.

[0136] Another enhancement not shown in FIG. 9 is that the UE can transmit the inactive S The Inactivity Registration Timer Update procedure can request an update of the registration timer of an IM. The UE is still connected to the active PLMN and therefore the forwarded paging Provides updates to inactive PLMNs that they are able to receive requests. The UE may not be able to establish a connection with the PLMN after the SIM switching procedure. These measurements are taken when a connection is successfully established. , or through another PLMN if the connection is unsuccessful. Cell measurements are used by network operators to determine network coverage, It can be used to improve the cellular coverage of the system if necessary. There are also other enhancements proposed for multi-SIM operation in NO.

[0137] When describing multi-SIM operation, it is important to consider which SIM / PLMN a UE communicates with at any given time. Define terms for use, clearly distinguishing between active and inactive use It is important to note that the terms "primary" and "secondary" are used according to UE policy. This refers to SIM prioritization as outlined by the user via the GUI. These terms refer to which SIM has priority (primary) over other SIMs (secondary) in the UE. The UE usually uses the primary SIM most of the time. The terms "active" and "inactive" refer to the SIM / PL with which the UE is currently communicating. In other words, the UE maintains a connection to the PLMN in which it is "active" and "Inactive" PLMNs have no connection. Using Figure 9 as an example, Explain the use of terms. Primary SIM = SIM1 Secondary SIM = SIM2 Active SIM / PLMN = SIM1 / PLMN1 (for steps 1 to 5), S IM2 / PLMN2 (for steps 6-7) Inactive SIM / PLMN = SIM2 / PLMN2 (for steps 1-5), SIM1 / PLMN1 (for steps 6-7) The terms primary and secondary refer to which UE is connected before it registers to a PLMN, for example. Which PLMNs are active PLMNs and which are inactive PLMNs This can also be applied to PLMNs when it is not initially known whether they will be used.

[0138] The following solution applies if the SIMs are from different operators. While the solution may be adapted to support SIMs from the same operator, For example, the registration procedure applies to the same PLMN and depends on the roaming agreement between the PLMNs. No. The procedure still links the paging requests of SIM1 and SIM2 together, The UE receives the paging request at the paging opportunity of the active SIM. Registration state transitions and SIM switching, whether from one or a different operator In the same operator case, the UE performs the SIM switching procedure Once executed, there is no need to switch connections between PLMNs.

[0139] The following solutions are described within the context of the 5GS, but the solutions may also be applied to the EPS. Please note that, for example, the proposed registration procedure works similarly to the AMF in 5GS. In 5GS, NAS messaging is performed between the UE and the AMF. Note that in EPS, NAS messaging is between the UE and the MME. In EPS, the attach procedure and HSS are the same as those in 5GS. It performs the same functions as the general registration procedure and UDM. The RAN node performs the eN for EPS. odeB and gNodeB for 5GS. Similarly, The proposed RM-INACTIVE state is a new state that can be used in conjunction with EMM-INACTIVE in EPS. The SIM switching procedure is performed in both the EPS and the 5GS in a similar way. and multi-SIM policies or information elements may be incorporated into both systems. The solution in this disclosure is to provide a policy to the UE from the PCF via NAS messaging. This section describes how the EPS can be distributed via IP-based The policy is implemented via procedures or via information elements sent in NAS messages. To illustrate some of these enhancements as they apply to the EPS system, Embodiments are provided for this purpose.

[0140] Different aspects of the LTE system are enhanced to support the use of multi-SIM UEs. The first aspect is an attach procedure that a UE performs to register with a core network. These enhancements to the attachment procedure are proposed, namely partial attachment. , indirect attach, and MUSIM attach. These attachment procedure enhancements are Partial attach includes registration of multiple SIMs used within a mobile phone. registering the secondary SIM with the HSS of the corresponding PLMN which triggers a forwarding of the request to the secondary SIM; Indirect attachment is when a secondary SIM is registered to the MME of the corresponding PLMN and the PD is always connected to the secondary SIM. A default bearer for the N connection can be established. Finally, the MUSIM attach The enhancement allows the UE to perform the attachment procedure for multiple SIMs in a single request. This allows the core network to indicate the need for a secondary SIM. The execution of either a partial or indirect attachment procedure can be triggered.

[0141] In addition, a new registration mode of operation enabled for multi-SIM UEs, i.e. To support EMM-INACTIVE, a new LTE EMM state is added to the UE and It is proposed that a new registration state be added to the MME and the secondary SIM. The UE operating the LTE-1000 is registered to the corresponding PLMN but is not actively connected to that PLMN. Furthermore, the aforementioned enhancement to the attach procedure indicates that a paging request is not Paging request forwarding is enabled. Paging request forwarding is used to send a paging request to an inactive Paging requests for inactive SIMs are forwarded by the active PLMN to the active PLMN. All of these LTE system enhancements are similar to 5G enhancements. and are described in more detail below.

[0142] This disclosure refers to EMM-INACTIVE as a new state in the EMM state model. However, due to the current LTE deployment, the It is noted that it may be more feasible for the state to be a sub-state or mode of operation. This substate or mode of operation is the "inactive" substate of EMM-REGISTERED. The UE and MME may also refer to this as a “active registration” sub-state or mode. It is also noted that separate EMM and ECM states can be maintained for a SIM. sea ​​bream.

[0143] Once the registration state is established for each SIM of a multi-SIM UE, paging The paging request forwarding function is enabled to eliminate the occurrence of collisions. When available to an active SIM, the corresponding PLMN is In an active PLMN, the paging occasion calculation While the UE can receive paging requests for multiple SIMs, it can only receive paging requests for one paging opportunity. The paging information is as follows: , possibly sent via a NAS notification.

[0144] (Multiple SIM registration procedure) E-UTRAN cells may use partial and / or Broadcast whether the UE can connect to an MME that supports indirect attachment The UE can achieve partial and partial attachment to the network via E-UTRAN cells. The E-UTRAN cell shall block this indication before attempting to perform an indirect attach and / or You can check that it is broadcasting.

[0145] Note: This same check can be performed in a 5G system. R-cells may report partial and / or indirect attachment in their system information broadcasts. It can broadcast whether it can connect to the AMF it supports. The UE , perform partial and / or indirect attachment to the network via NR cells. Before attempting to transmit, the NR cell may check that it is broadcasting this indication. do.

[0146] As mentioned above, in this disclosure, to support multi-SIM operation in 5GS, Two registration procedures are proposed. The registration procedure is for the UE to receive services from the 5G network. Partial registration allows a user to transfer a cellular telephone to a secondary PLMN via a primary PLMN. Called by the UE to register a SIM. By performing this registration, the U E is used to transmit all pages when the UE is not actively registered in a secondary PLMN. The secondary PLMN is then instructed to forward the ping request to the UE via the primary PLMN. On the other hand, indirect registration is based on the general registration procedure found in TS 23.502[2]. Complete registration with the secondary PLMN through the primary PLMN as outlined The indirect registration procedure also requires that the UE is in active communication with a secondary PLMN. When no paging request is received from the secondary PLMN, the secondary In both registration procedures, the RM state of the UE with the secondary PLMN is notified. The state transitions from RM-DEREGISTERED to RM-INACTIVE. In the case of registration, the AMF is assigned to serve the UE, and the AMF serves the UE. This differs from a partial registration, which is not allocated for the purpose of

[0147] Similar to the 5G registration procedure, the UE must register To do this, it is necessary to perform an attach procedure with the core network of the LTE system. The UE connection procedure authenticates the UE and establishes a context for the UE to communicate securely with the network. By establishing a SIM card, the UE is registered to the core network. It is proposed that the attach procedure be enhanced to support registration of multiple SIMs. The details are: 1) partial attachment, 2) indirect attachment, and 3) MUSI This article describes an enhancement to M-attach. MUSIM attach is a method to attach multiple attach requests to a single For example, an attach request for the primary SIM and an attach request for the secondary SIM. The MUSIM attach procedure is combined with one or more attach requests. The same can be applied to the

[0148] For all described registration and attachment procedures, the UE Include multi-SIM support information in the corresponding request message (e.g., by a user) The assistance information can be used to leverage existing paging mechanisms for multi-SIM operation. For example, the assistance information may be used by the network to enhance the downlink Whether and when to page the UE when data is available for a particular SIM It is possible to provide prioritization information to inform the user whether to page the user. The information is sent by the network in a timely manner to avoid paging collisions for multiple SIMs. It is possible to provide information on how to assign identifiers corresponding to You can. The multi-SIM support information is explained in more detail below.

[0149] (Partial registration) The UE is primarily connected to the secondary PLMN when the UE's RM state is RM-INACTIVE. Whenever a paging request is received from a PLMN, the UE shall forward all paging requests to the UE through the primary PLMN. This procedure allows the U to perform partial registration to configure the secondary PLMN for E is associated with the active SIM, regardless of the PLMN with which the UE is actively communicating. For a given paging occasion, whether the paging request is for SIM1 or SIM2 All paging requests can be received regardless of whether they are directed to the As a result, the UE must disconnect the network between SIMs to receive the paging request. In fact, this procedure ensures that the UE receives all paging requests. However, the procedure for switching UE between SIMs is different depending on the switching timing. If the timing of the paging request is not aligned with the paging request timing, the paging request may be missed. The page request forwarding feature is a new feature added to UDM. Note that it is possible to derive

[0150] Figure 10 shows a UE initiating a partial registration procedure for SIM2 through PLMN1. Two cases are shown in which partial registration of SIM2 can be done, namely 1. Both S The IM is installed together and the partial registration request is replaced with the initial registration request (this is the same as MUSIM registration). If SIM2 is installed after SIM1 is installed, or if SIM2 is installed after SIM1 is installed, If SIM1 is installed and the UE has already performed initial registration for SIM1.

[0151] Step S1002: The UE registers with the PLMN1 of the SIM1 with the registration type of the initial registration. At this time, only SIM1 is installed in the UE. However, If both SIM1 and SIM2 are installed at the same time, the UE will When registering to your SIM, you must provide the appropriate SIM2 identifier (e.g. SUPI (e.g. IMSI), It may contain a multi-SIM indication with a UTI, 5G-S-TMSI, or SUCI. In this case, the partial registration request is a general registration procedure (TS 2 It is proposed to be integrated as part of the general registration procedure described in 3.502[2]. This procedure is sometimes called MUSIM registration. Additions to the initial registration request are For example, multi-SIM indication, partial enrollment indicator, and one or more SIM2 identification The multi-SIM indicator is a preferred network behavior parameter. may be coded as an option to the Preferably, the partial registration indicator may be incorporated within the registration type parameter. The message indicates which SIM is the primary SIM, which is the secondary SIM, and which is the non- It may further indicate whether the ACK should be used to register to an active PLMN. In this case, processing skips to step S1006. Step S1004: The UE successfully registers SIM1 to PLMN1, and SIM2 registers UE In some cases, the UE may then install a multi-SIM device in PLMN1 after the SIM is installed in PLMN1. and a partial registration to notify that the SIM includes a multi-SIM indication and a SIM2 identifier. A request can be initiated by the UE. The registration type of this request can be partial registration or At this point, the RM status of SIM1 becomes RM- REGISTERED and RM-DERE for SIM2 (with PLMN2) The SIM2 identifier is GISTERED to the UE by PLMN2. It is used to authenticate the SUPI (e.g. IMSI), GUTI, 5G-S-TM A partial registration request is a newly defined procedure. Alternatively, it may be incorporated as part of the general registration process. may be coded as an option in the preferred network behavior parameters or as a standby The multi-SIM indicator may be an on-board indicator. Check and select the appropriate network entity that supports the SIM operation It may be used by network entities for Step S1006: RAN1 connects the previously established N2 interface to SIM1. In case of MUSIM registration, RAN1 forwards the partial registration request to AMF1 via the Selects AMF1 to process the request. Step S1008: The presence of a multi-SIM indication and / or the UE 102 performing partial registration. Due to the fact that AMF1 904 requires multi-SIM indication and partial registration by transmitting the SIM2 identifier to the AUSF2 908 along with the indicator 2. Select and request AUSF2 908 to authenticate UE 102 for M If it was a USIM registration, AMF1 904 would register SIM1 first, then SIM A partial registration request can be sent to PLMN 2. A PLMN has established a routing agreement for forwarding partial registration requests. The AMF in each PLMN It is envisaged that the AUSF may be configured with contact information for other PLMNs. Please note that the communication between AMF1 904 and AUSF2 908 may be, for example, It is also assumed that the SEPPS of the PLMN in question will be secured via the N32 interface. will be done. Step S1010: AMF1 904 forwards the partial registration request to AUSF2 908. and the registration type is set to partial registration or includes a partial registration indicator The M indication may be encoded as an option for preferred network behavior, and the SIM2 identifier, SI AMF1 ID and UE ID indicating that UE with M1 has been authenticated to PLMN1 ID, PLMN2 to which future paging requests for SIM2 can be forwarded In step S1002, the registration type may include the AMF context information of the MN1. The group was set to initial registration for SIM1, but this registration request was for SIM2, Therefore, changing the registration type for this request from initial registration to partial registration is done by AUSF2 9 Note that this is for 08. Alternatively, the registration type can be set as initial registration. A partial registration indicator may be provided in the request. The registration type may be coded as initial registration with partial registration. Step S1012: AUSF2 908 performs authentication of the UE for SIM2; Subscription information can be created or updated in UDM2 910. 0 is for SIM2, which is used to indicate when the paging request is targeted to SIM2 In addition, the UE 102 may be provisioned with a temporary identifier for the SIM2. The RM state of R is changed to R to enable the transfer of paging requests to the UE through PLMN1. The RM state is updated to M-INACTIVE. In this case, the RM state is updated to M-INACTIVE. This may be an indication stored in the subscription data of the UDM to indicate that the user has been subscribed to the service. Step S1014: After AUSF2 authenticates the UE of SIM2, a partial registration acceptance message is sent. The partial registration acceptance message is returned to AMF1. The partial registration acceptance message is a modified registration acceptance message. AUSF2 may receive the following information: an instruction to the UE to receive the temporary identifier assigned to the UE for SIM2 by UDM2; 2. The UE's RM state for RM-DEREGISTERED to RM-INACTIV E, paging forwarded by PLMN1 for SIM1 Acknowledgement of support for receiving a paging request from PLMN1. The acceptance message includes the MME contact information for the SIM2 registration and the registration timer for SIM2. The temporary identifier for the UE can be used when the UE is actively registered in PLMN1. Used to page the UE whenever there is a page for SIM2 while In addition, the default AMF contact information is used when future paging requests are To inform AMF1 that it may come from the default AMF instead of M , may be included in the acceptance message. Step S1016: AMF1 sends a partial registration acceptance message to the UE through RAN1. The accept message contains the information transferred from AUSF2 to AMF1. An indication of successful authentication, a temporary identifier assigned to the UE for SIM2 by UDM2 The UE's RM state for SIM2 changes from RM-DEREGISTERED to RM-INA The notification may include an indication that the SIM has been changed to ACTIVE and a registration timer for SIM2. The temporary identifier for E is the SIM ID while the UE is actively registered in PLMN1. Whenever there is a page for PLMN2, it uses the paging request forwarding function. Alternatively, the AMF1 may be used to page the UE from the PLM A separate temporary identifier for SIM2 that can be used to page the UE on N1. The assignment of this temporary identifier occurs when the associated paging occasion is S It is possible that the paging occasions may overlap with those associated with IM1. Therefore, the UE needs to send one paging message to receive the pages of both SIM1 and SIM2. AMF1 instead allows the UE to monitor only one paging occasion. Maintain the fact that you only need to monitor and receive pages for all SIMs While allowing the UE to use the same temporary identifier for all SIMs associated with it, The UE's RM state for each SIM is updated in the UE, i.e. for SIM1 is RM-REGISTERED and RM-INACTIVE for SIM2 , should be consistent with that of AMF1.

[0152] This procedure involves the UDM assigning a temporary identifier to the UE and the temporary identifier being This temporary identifier is a new type of 5G-GUTI. This 5G-GUTI format must be compatible with the existing 5G-GUTI format. It can be formatted in any way. For example,

[0153] GUAMI can be resolved to UDM / UDR. <mcc>and <mnc>only GUAMI may include<AMF Region ID><AMF Set ID > and<AMF Pointer> The fact that 5G-GUTI does not include UDM It may be shown that the .

[0154] 5G-TMSI in 5G-GUTI is a temporary identity assigned to the UE by UDM. This temporary identifier may be a child, a SUCI or a GPSI. The paging function allows the UE to detect that it is being paged for the associated SIM. It can be included in the message.

[0155] (Partial registration alternative method) This section describes the alternative procedure for the UE to perform partial registration, as shown in Figure 11. We propose.

[0156] Step S1102: The UE registers with the PLMN1 of the SIM1 with a registration type of initial registration. At this time, only SIM1 is installed in the UE. However, If both SIM1 and SIM2 are installed at the same time, the UE will When registering to a SIM card, the multi-SIM indication, partial registration indicator, and proper SIM2 identification are displayed. Prefix (e.g., SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or In this case, the partial registration request is performed to SIM1. It is integrated as part of the general registration procedure (described in TS 23.502[2]) This procedure is sometimes called MUSIM registration. Additions to the registration request include the multi-SIM indication, partial registration indicator, and one The multi-SIM indicator is a preferred SIM identifier. It may be coded as an option in the network behavior parameters or as a stand-alone The partial registration indicator may be a partial registration indicator, and the partial registration indicator may be embedded in the registration type parameter. The message may include information about which SIM is the primary SIM and which is the secondary SIM. Is it a counter SIM and should it be used to register to an inactive PLMN? In this case, the process skips to step S1106. Step S1104: The UE successfully registers SIM1 to PLMN1, and SIM2 registers UE In some cases, the UE may then install a multi-SIM device in PLMN1 after the SIM is installed in PLMN1. and a partial registration to notify that the SIM includes a multi-SIM indication and a SIM2 identifier. A request can be initiated by the UE. The registration type of this request can be partial registration or At this point, the RM status of SIM1 becomes RM- REGISTERED and RM-DERE for SIM2 (with PLMN2) The SIM2 identifier is GISTERED to the UE by PLMN2. It is used to authenticate the SUPI (e.g. IMSI), GUTI, 5G-S-TM A partial registration request is a newly defined procedure. Alternatively, it may be incorporated as part of the general registration process. may be coded as an option in the preferred network behavior parameters or as a standby The multi-SIM indicator may be an on-board indicator. Check and select the appropriate network entity that supports the SIM operation It may be used by network entities for Step S1106: RAN1 connects the previously established N2 interface to SIM1. In case of MUSIM registration, RAN1 forwards the partial registration request to AMF1 via the Selects AMF1 to process the request. Step S1108: AMF1 checks which UDM to use by checking the SIM2 identifier. The SIM2 identifier is used to determine which UDM should be contacted. The MCC and MNC used in the Step S1110: AMF1 transfers the partial registration request to UDM2 and sets partial registration. Registration type, partial registration indicator, multi-SIM indication, preferred network The SIM2 identifier, which may be coded as a behavior option when the UE with SIM1 is connected to the PLMN AMF1 ID and UE ID, PLMN2 are authenticated to SIM The AMF context of PLMN 1 to which future paging requests for In step S1102, the registration type is set to the initial registration of SIM1. However, this registration request is targeted to SIM2, so the initial registration type Note that this is a change from registration to partial registration. Alternatively, the registration type can be The request may be marked as registered or a partial registration indicator may be added to the request. The registration type from step S1102 may be coded as initial registration with partial registration. Step S1112: UDM2 responds to AMF1, and AMF1 responds to the UE. indicates to the UE whether the UE is allowed to be partially registered and authorization is pending The message also indicates to the UE that authentication is in progress. It includes a timer that indicates to the UE how long it must wait to receive the request. If the timer expires before receiving a request to start authentication from the network, the UE shall Ignores requests to perform authentication unless a partial registration request is sent. A temporary identification for SIM2 that is used to indicate when a logging request is targeted to SIM2. In addition, the default AMF contacts can be provisioned to the UE. The information indicates that future paging requests may occur from the default AMF rather than the UDM. may be included in the acceptance message to inform AMF1 that SIM2 has The M state may not be updated or may be updated to a state indicating that authentication is pending. . Step S1114: The AMF transmits the AUSF and slice-specific sector of the UE and PLMN2. This procedure is described in the section entitled "Slice-Specific Authentication and Authorization." The UDM2 provides the functionality of AAA-S 802 in the procedure. UDM2 can provide a temporary identifier to AMF. The AMF can provide the temporary identifier to the UE in an EAP success message. A registration timer for SIM2 may also be provided. , AAA-P 804 are also shown.

[0157] In partial registration, no AMF is assigned to serve the UE, and as a result As a result, the UDM assigns a temporary UE ID to the UE. This temporary UE ID is RM-INACTI It is used to page the UE whenever it is in VE state. The M state is set in the UDM subscription data to indicate that paging request forwarding is enabled. Note that the indication may be stored in the U The DM sends an active PLM with the temporary UE ID that was assigned to the UE during partial registration. In addition, UDM can send paging messages to N AMFs. MAY return the identifier and / or contact information of the default AMF in response to the registration request. This default AMF is available only when the UE is in RM-INACTIVE state with the PLMN. A paging request to the SIM is sent to the AM of the active PLMN where the UE is currently registered. F.

[0158] (Partial Attachment) A multi-SIM UE simply registers its primary SIM to the current PLMN. Partially attach to register other secondary SIMs to their corresponding PLMNs without Figure 24 shows the procedure for part attachment reinforcement. It shows that the minute attach is performed separately from the initial attach of SIM1, e.g. As described below, in the MUSIM attach request, In addition, the partial attachment reinforcement may be performed in step S24 for each SIM. Partially attach multiple secondary SIMs by running S2414 from 06 The partial attach enhancement supports the page request forwarding function in the HSS. Note that a new feature added to allows for the .

[0159] Step S2402: The UE initially attaches to the PLMN1 using the SIM1. PLMN1 is considered the active PLMN and SIM1 is considered the primary SIM This step is performed initially when only SIM1 is installed in the UE. If two or more SIMs are installed in the UE at the same time, one attachment request A combined attach procedure may be performed to register multiple SIMs together in a single request. This combined attach request is called a MUSIM attach and contains the same information as a normal attach request. In addition to the information, it also displays multi-SIM indicators, partial attach indicators, and It may include a suitable SIM identifier (e.g., IMSI, GUTI, etc.). Partial attachment is integrated as part of the attachment procedure from TS 23.401[9]. The multi-SIM indicator is an option in the preferred network behavior parameter. It may be coded or may be a standalone indicator, and the part attachment An indicator may be carried in the Attach Type parameter. Which SIM is the primary SIM, which SIM is the secondary SIM, and which SIM is the inactive P It can further indicate whether the id should be used to register with the LMN. If it is an attach request, the procedure skips to step S2406. Step S2404: After a while, the partial attachment procedure is started. For example, This can be done by inserting a physical SIM and configuring the eSIM through the GUI or AP. Based on a request from an application on the UE through I or by the application This can be done when SIM2 is added to the UE, immediately after the completion of the touch procedure. It is considered a secondary SIM and is associated with PLMN2. PLMN2 is an inactive P The UE then requests a partial attach to PLMN2 through PLMN1. This request includes the multi-SIM indicator and the appropriate SIM identification for each SIM. It can include a multi-SIM identifier (e.g. IMSI, GUTI, etc.). The data may be coded as an option in the preferred network behavior parameters or may be stored in the The multi-SIM indicator may be a standalone indicator. The entity will select the appropriate network configuration to support multi-SIM operation during the attach procedure. Used to check and select a call entity and enable paging request forwarding. It can be done. Step S2406: In response to the partial attach request or the partial attach indication, the PLMN The MME of one SIM must have the appropriate HS to handle the partial attach request for each SIM. The identifiers provided to SIM2 may include the MCC and MNC, or resolve to MCC and MNC used to determine which HSS should be contacted The MME of PLMN1 may determine the core network configuration, roaming agreement, or Due to other mechanisms that support multi-SIM operation, other HSs in different PLMNs may S contact information, so that the MME can Send any partial attach message of the secondary SIM to the default HSS of another PLMN Can be transferred. Step S2408: The MME1 2402 sends a partial attach request to the selected HSS. The request includes a partial attach indicator, a preferred network behavior option, and A multi-SIM indicator, SIM2 identifier, SIM1 identifier, SIM2 identifier, SIM1 identifier, SIM2 identifier, SIM3 identifier, SIM4 identifier, SIM5 identifier, SIM6 identifier, SIM7 identifier, SIM8 identifier, SIM9 identifier, SIM1 identifier, SIM1 identifier, SIM1 identifier, SIM1 identifier, SIM2 ...3 identifier, It includes the MME1 ID and UE ID to show that it has been authenticated to the LMN1. MME1 can see that PLMN2 can forward paging requests to SIM2. It may further provide context information of the MME of PLMN1 that may be used for the The MME in the may be configured to support paging request forwarding, and the UE may The UE then receives the message from the PLMN2. It is possible to forward paging requests to the MME to which the UE is attached in case of mobility. It may be possible. Step S2410: The HSS of the PLMN2 performs authentication of the UE for the SIM2; Information about the UE, such as information obtained from the authentication procedure and information provided by MME1 The HSS2 2404 can also store context information for SIM2. A temporary identifier may be assigned to the UE via PLMN1. Used by HSS2 to identify SIM2's paging requests that will be forwarded to Finally, a UE with SIM2 is registered to PLMN2 but is not active with PLMN2. The EMM state of SIM2 is EMM- In this case, the EMM state is set to INACTIVE. The HSS may store an indication in its subscription data to indicate that the HSS has been Step S2412: The HSS of PLMN2 sends a partial attach procedure indicating the result of the partial attach procedure. The response indicates that SIM2 has been successfully authenticated. indicates a temporary identifier assigned for SIM2 by HSS2, UE EMM state changes from EMM-DEREGISTERED to EMM-INACTIVE Indication of changed paging request forwarded by PLMN1 for SIM1 acknowledgment of support for receiving paging requests from PLMN1; It may contain MME contact information and SIM2 registration timer. If the attach was not accepted, the response will include further information detailing why the attach was not accepted. In addition, the contact information of the default MME can be used to The MME should be aware that the ping request may originate from the default MME instead of the HSS. MAY be included in the acceptance message to notify 1. Step S2414: The MME of PLMN1 notifies the MME about the status of the partial attach procedure. A partial attach acceptance message, which may be a modified attach acceptance message that provides additional information. If the attach procedure is performed for multiple SIMs, the UE returns the There can be separate registration statuses for SIM1 and SIM2. The response message indicates that SIM2 has been successfully authenticated. an indication that SIM2 has been activated; a temporary identifier assigned to SIM2; and the EMM state of the UE for SIM2. The status has changed from EMM-DEREGISTERED to EMM-INACTIVE. It shall contain information returned from the HSS of PLMN2, such as instructions and the registration timer of SIM2. The temporary identifier can be used to forward future pages to SIM2 to PLMN1. In addition, the MME of PLMN1 is used to identify the request for used to page the UE instead of using a temporary identifier assigned by the A separate temporary identifier may be assigned for each SIM2 that may be used. This temporary identifier may be assigned to the SIM1 that may be used. The child allocation is made with the associated paging occasion as the paging occasion associated with SIM1. As a result, the UE may receive both the pages of SIM1 and SIM2. The MME only needs to monitor one paging occasion to receive the paging message. Therefore, the UE only needs to monitor one paging occasion and receive pages for all SIMs. This allows for the same number of SIMs associated with the UE while preserving the fact that The same temporary identifier can be assigned to the UE for each SIM. The UE’s EMM state is updated for each SIM. In this scenario, the EMM state of SIM1 is EMM-REGISTERED and the SI For M2, the MME is EMM-INACTIVE. The EMM state is EMM-REGISTERED for SIM1 and EMM-REGISTERED for SIM2. The MME of PLMN1 is EMM-INACTIVE for SIM1 and SIM2. Each can maintain a separate EMM state.

[0160] (Indirect registration) The indirect registration procedure is a functional combination of the partial registration procedure and the general registration procedure. Both the Paging Registration procedure and the Indirect Registration procedure forward the paging request to the UE through PLMN1. The SIM2 identifier and a multi-SIM instruction for configuring the PLMN2 for use in the same manner as described above are included. However, the indicators for each step are different (i.e., indirect as opposed to partial) and The registration procedure is used to allocate a network slice and provide the UE with UE policy information. Indirect registration also provides additional functionality for the PLMN to access the AMF to serve the UE. Assign.

[0161] Figure 12 shows a UE initiating an indirect registration procedure for SIM2 through PLMN1. Similar to the partial registration procedure, the indirect registration procedure can be combined with the general registration procedure to register the SIMs in one request. You may register both SIM1 (direct registration) and SIM2 (indirect registration) together. This procedure will be explained later. As described below, the indirect registration procedure may be called MUSIM registration. Similarly, the indirect registration procedure may be called the general registration procedure. may be performed separately.

[0162] Step S1202: The UE registers with the PLMN1 of the SIM1 with a registration type of initial registration. At this time, only SIM1 is installed in the UE. However, If both SIMs are installed at the same time, the UE will also detect the PLM of SIM1. Multi-SIM indication, indirect registration indicator, proper SIM2 identification when registering to N1 child (e.g., SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or S In this case, the indirect SIM2 identity may include the SIM ID, ... The registration request is part of the general registration procedure of SIM1, e.g., MUSIM registration. Initial Registration Additions to the request include multi-SIM indication, indirect registration indicator, SIM2 identifier, and P The multi-SIM indicator includes the LMN2 identification information. It may be coded as an option in the behavior parameters or as a stand-alone indicator. The indirect registration indicator may be incorporated within the registration type parameter. The message will tell you which SIM is the primary SIM and which is the secondary SIM. Further indicates whether the IM should be used to register to an inactive PLMN. In this case, the procedure skips to step S1206 and the general registration of SIM1 is completed. Both registration and indirect registration of SIM2 are performed at the same time, or for example, registration of SIM1 and its The registration of SIM1 may be performed sequentially, such as registration of SIM2 after SIM1. Step S1204: The UE successfully registers SIM1 to PLMN1, and SIM2 registers UE In some cases, the UE may then install a multi-SIM device in PLMN1 after the SIM is installed in PLMN1. and including a multi-SIM indication, a SIM2 identifier and a PLMN2 identification information. An indirect registration request can be initiated by the UE to notify the UE of the indirect registration. At this point, the SI M1's RM state is RM-REGISTERED and it is registered to SIM2 (with PLMN2). The SIM2 identifier is RM-DEREGISTERED by PLMN2. It is used to authenticate SIM2 to the UE using SUPI (e.g., IMSI), It can consist of UTI, 5G-S-TMSI, or SUCI. It may be a defined procedure or a general registration procedure with registration type set as indirect registration. It may be incorporated as part of the SIM card or include an indirect registration indicator. The indicator may be encoded as an option in the preferred network behavior parameter. Alternatively, it may be a standalone indicator. The multi-SIM indicator may be During the procedure, check for a suitable network entity that supports multi-SIM operation. This may be used by a network entity to select a Step S1206: RAN1 902 retrieves the previously established N2 interface for SIM1. The MUS interface forwards the general or indirect registration request to the AMF1 904. In case of IM registration, RAN1 902 selects AMF1 904 to process the request. Step S1208: AMF1 904 performs step S1008 in FIG. 10 or FIG. 11. Execute S1014 from to authenticate the UE of SIM2. This step is and PLMN2 completes the UE partial registration procedure for the paging request originating from UDM2. In addition, the contact information in the default AMF is used to forward the The AM may be aware that paging requests may originate from the default AMF rather than the UDM. It may be included in the acceptance message to inform F1. Step S1210a and b: AMF1 sends slice selection subscription data of UE to UDM2 and UDM2 responds with slice selection data to AMF1. Step S1212a and b: AMF1 is taken from Step S1210a and b. Using the slice selection data provided, NSSF1 1202 through NSSF2 1 204. AMF1 executes the Nnssf_NSSelection_Get request. Provides the NSSF2 with the requested NSSAI and other slice-related parameters. F2 will collect the permitted NSSAI and other NSSAI related parameters, as well as the network NRF 302 for AMF1 to select NFs / services for workload slice instances Returns a response containing Step S1214a and b: AMF1 transfers the NRF2 1208 to the NRF1 12 06 to find the appropriate AMF to service the UE's indirect registration request NRF2 obtains a list of potential AMFs in PLMN2 to process the indirect registration request. return. Step S1216: AMF1 forwards the indirect registration request to AMF2, and AMF2 forwards the SIM 2 to perform a general registration procedure for the UE. This general registration procedure also supports multi-SIM directives. , the indirect registration indicator, and the appropriate SIM2 identification received in step S1208. The AMF1 may include a child or temporary identifier. 2, or through UDM2 from step S1208, multi-SIM operation (e.g. AMF2 configuration through a network that supports it (for example, through a roaming agreement) The tact information can be obtained. Upon completion of the general registration procedure, the registration information returned to AMF1 The accept message indicates that SIM2 has been successfully authenticated and that AMF2 has The UE's RM state for SIM2 is RM-D. Indication that the PLMN has changed from EREGISTERED to RM-INACTIVE Confirmation of support for receiving paging requests forwarded by SIM 1 for SIM 1 response, contact information of the MME for receiving paging requests from PLMN1, and A registration timer for SIM2 may be included. The temporary identifier for the UE may be included in the PLM Whenever there is a page for SIM2 while actively registered in N1, It is used to page the UE from the LMN2. Alternatively, the AMF1 may be used instead. A separate temporary address for SIM2 that may be used to page the UE in PLMN1 at This temporary identifier assignment is performed by the associated paging The paging opportunity may overlap with the paging opportunity associated with SIM1. Therefore, the UE needs to send one paging message to receive the pages of both SIM1 and SIM2. AMF1 instead allows the UE to monitor only one paging occasion. Maintain the fact that you only need to monitor and receive pages for all SIMs While allowing the UE to use the same temporary identifier for all SIMs associated with it, The UE's RM state for each SIM is updated in the UE, i.e. for SIM1 is RM-REGISTERED and RM-INACTIVE for SIM2 , should be consistent with that of AMF1. Step S1218: AMF1 sends the registration acceptance message received from AMF2 to RAN1. RAN1 then forwards the registration accept message to the UE. The accept message is the successful authentication of SIM 1, the general registration procedure or the SIM 2 assigned to the UE by AMF1 The UE's RM state for SIM2 is RM-DEREGISTER. Indication of change from ED to RM-INACTIVE and registration for SIM2 The temporary identifier for the UE may include a timer. To page the UE whenever there is a page for SIM2 while Used for.

[0163] An alternative procedure for indirect registration is shown in Figure 13, where AMF1 supports multi-SIM operation. AMF2 is provisioned with AMF2 contact information as part of the Default AMF of PLMN2 for AMF1 to contact in case of chisim support Upon receiving the indirect registration request, AMF1 configures the contact list of PLMN2 as AMF2 can search the AM Another AMF in PLMN2 to serve the UE based on the request forwarded from F1 From that point on, the general registration from TS 23.502[2] will be available. The procedure is followed, but with updates due to changes to support indirect registration.

[0164] Steps S1302 to S1306: These steps are performed for the procedure shown in FIG. These are the same steps that are performed. Step S1308: AMF1 is provisioned with the contact information of AMF2. AMF1 sends an indirect registration of the UE for SIM2 to PLMN2. AMF1 The presence of a SIM instruction or the registration type or indicator is set to indirect registration The indirect registration request is made with the registration type set to indirect registration. , or indirect registration indicator, multi-SIM indication is an option for preferred network behavior , where SIM2 identifier, UE with SIM1 authenticated to PLMN1, AMF1 ID and UE ID indicating that PLMN2 has been It includes the context information of the AMF of PLMN1 to which the paging request can be forwarded. If the request in step S1302 is a general registration request, the AMF 1 Create a new indirect registration request where the type can be set to indirect registration, and include the multi-SIM indication and the SIM Alternatively, the registration type may be set as initial registration. Optionally, an indirect registration indicator may be added to the request. The registration type involves a partial registration. It may be encoded as an initial registration. Step S1310: The general registration procedure from TS 23.502[2] is This is performed against SIM2 of the same device, but supports indirect registration as outlined in Figure 12. The standard is modified to include functionality for Step S1312: AMF1 sends the registration acceptance message received from AMF2 to RAN1. RAN1 then forwards the registration accept message to the UE. The accept message is an indication that authentication of the SIM allocated to the UE for SIM2 by the general registration procedure has been successful; The UE's RM state for SIM2 is RM-DEREGISTERED. RM-INACTIVE for SIM1 by PLMN1. Acknowledgement of support for receiving paging requests forwarded to the PLMN from the MME contact information for receiving the ping request and the registration timer for SIM2. A temporary identifier for the UE may be included when the UE is actively registered in PLMN1. The UE is paged from PLMN2 whenever there is a page for SIM2 while it is registered. Alternatively, AMF1 may instead use PLMN1 to locate the UE. Allocating a separate temporary identifier to SIM2 that can be used for paging This temporary identifier assignment is made when the associated paging occasion is associated with SIM1. Therefore, the UE may not receive the SI Only need to monitor one paging opportunity to receive pages for both M1 and SIM2 Alternatively, AMF1 requires that the UE only monitors one paging occasion, While maintaining the fact that you can receive pages of all SIMs related to the UE All SIMs attached to the SIM card can be assigned the same temporary identifier. The RM status of the UEs that correspond to SIM1 is updated in the UE, i.e., RM-REGIST It is RM-INACTIVE for ERED and SIM2, and is consistent with that of AMF1. It should be.

[0165] The UE supports each SIM in each PLMN, whether the PLMNs are the same or different. In other words, a multi-SIM UE can register First, SIM1 registers with PLMN1, then SIM2 registers with PLMN2, and finally Note that the order of registration to PLMN1 and PLMN2 does not matter. After the SIMs are registered to their respective PLMNs, the UE then primarily For example, it must run on the primary SIM (e.g. SIM1) configured by the user. In this case, the UE can determine the user plane of PLMN1 of SIM2 as Indirect registration can be performed from PLMN1 to PLMN2 via

[0166] Figure 39 shows how a multi-SIM UE transmits data to an inactive SIM via the user plane of the active SIM. This section shows the procedure for performing an indirect registration of a single active SIM. Before performing the indirect registration procedure, the UE For example, SIM1 is registered to PLMN1 and SIM The UE then created a SIM for SIM1 on PLMN1. The UE user performs an indirect registration procedure for SIM2 using the received PDU session. SIM1 is the preferred SIM or the user is completing an important activity SIM2 remains connected to PLMN1 for a certain period of time in order to By configuring the UE to also receive mobile terminated services such as requests may be triggering this procedure.

[0167] Step S3902: The UE transmits PLMN1 and PLMN2 to each SIM. As part of multi-SIM operation, the UE monitors paging messages. to ensure that the registration state of each SIM remains RM-REGISTERED. To achieve this, the system periodically switches communication between the two PLMNs. Step S3904: The UE transmits a data connection to the PLMN1 via the SIM1. Establish a PDU session. One or more PDU sessions can be created. A U-Session is a voice call made by a user of the UE or a call that is interrupted by the user. This can be established for important activities such as important downloads that you do not want to Another PDU session is the Internet PDU session that is established after the UE is registered to the PLMN. Separately, the UE may also be associated with a general connection to the SI Established a PDU session for M2. Step S3906: The SIM1 activity from step S3904 is If it is important to the user, the user may This configuration allows the UE to switch between the two PLMNs. Disable communications with the PL, possibly for a configured period of time, at a configured location, etc. Alternatively, the user of the UE may decide that SIM1 is the primary SIM. SIM1 may be configured as a secondary SIM and SIM2 may be configured as a secondary SIM. The UE decides that the user prefers to remain connected to PLMN1. Step S3908: As a result of the decision made in step S3906, the UE Send an indirect registration request to the N3IWF of PLMN2 via the user plane of MN1. E creates the PDU session created in step S3904 and the indirect registration Access and mobility policies delivered to the UE by the PCF from PLMN2 for The registration message uses the address of the N3IWF2 provisioned in the UE. The request includes the following information: multi-SIM indicator, indirect registration indicator, IM2 identifier, optional time period, location information, downlink data of the UE with PLMN2 whether the UE should buffer the The UE may include, for example, using an external mechanism (e.g., the STUN protocol). The public IP address is obtained through the indirect registration message to N3IWF2. The UE can be assigned a unique IPv6 address or prefix. If so, the UE shall send the address or prefix to the N3IWF in an indirect registration message. 2. Alternatively, the UE may provide, in order to enable the proposed functionality, The UE can also establish a secure tunnel to the N3IWF2. Provided by PLMN2 in NAS notification sent to the UE via the user plane of It may indicate a PDU session ID to associate future paging requests to The PDU Session ID is the name of a PDU session previously established by the UE on PLMN2. It can be a tion. Step S3910: AMF2 receives the PLL signal from the UE through the N3IWF of PLMN2. Processes the registration request. The presence of the multi-SIM indicator indicates that the UE is a multi-SIM device. The indirect registration request is notified to the AMF that the user of the PLMN from which the request originates. indicates that the UE can be reached via the PLMN1. If a time period is provided to indicate a time, the AMF Resets or pauses the recording timer and sets a new pause based on the value provided by the UE. The stop timer can be enabled. AMF2 checks the status of the request, whether the AMF is The time value for pausing registration, PLMN2, is provided to the UE if not provided by the UE. It may contain, among other things, a PDU session ID to associate future paging requests that are forwarded. The indirect registration returns an acceptable acceptance response to the indirect registration.

[0168] The procedure shown in Figure 39 is that PLMN2 sends a page to the UE via the user plane of PLMN1. The UE can forward NAS notifications that may be received from PLMN2. maintain the PDU session established on PLMN1 so that Before releasing the PDU session on PLMN1, the UE must It may be necessary to inform PLMN2 that it is no longer reachable via the user plane If a secure tunnel is created, the UE will continue to use the , a paging request can be received.

[0169] (Indirect Attachment) An alternative to partial attachment in LTE is the indirect attachment enhancement, as shown in Figure 25. Indirect attachment can be considered as an initial attachment procedure, but it does not support multi-SIM operation. In addition to the functionality added to support the In this case, SIM2 through PLMN1 An indirect attachment procedure is performed, which results in context information about SIM2’s registration being The default bearer is also established in the MME of PLMN2 and the SGW and PGW of PLMN2. As with partial attach, indirect attach allows paging request forwarding. As a general attachment procedure performed in step S2502 of FIG. Indirect attachment can also be implemented by assigning an MME to serve the UE. It is.

[0170] Step S2502: The UE transmits the SIM1 to the PLMN1, which is an active PLMN. Perform the attach procedure. This step is performed if only SIM1 is installed in the UE. It may be performed first when two or more SIMs are installed in the UE at the same time. In this case, a combined attach procedure is used to register multiple SIMs together in one attach request. The combined attach request may include a multi-SIM indicator, Attach indicator, appropriate SIM identifier for each SIM (e.g. IMSI, GUTI ), and the identity of PLMN2 when the UE registers to PLMN1 of SIM1. In this case, the indirect attachment is based on the attachment procedure from TS 23.401. It is sometimes integrated as a part of the MUSIM Attach, which will be described later. The indicator may be encoded as an option in the preferred network behavior parameter. The indirect attachment indicator may be a standalone indicator, and the indirect attachment indicator may be The attach type parameter may be carried in the message to indicate which SIM is the primary SIM and which SIM is a secondary SIM and registers to an inactive PLMN The procedure may further indicate what should be used for MUSIM attachment. The request skips to step S2506 and the request is made simultaneously or for example to the registration of SIM1. Then, registration of SIM2 may be performed sequentially. Step S2504: After a while, the indirect attachment procedure is started. For example, This is done by inserting a physical SIM, configuring the eSIM, and then using the GUI to Upon request from an application on E or during the attach procedure by PLMN1 This can be done immediately after completion when SIM2 is added to the UE. SIM2 is a secondary SI M and is associated with PLMN2, which is considered an inactive PLMN. The UE then performs an indirect attach request to PLMN2 through PLMN1. The request includes the multi-SIM indicator, the appropriate SIM identifier for each SIM (e.g., IM SI, GUTI, etc.), and other PLMN identities. The M indicator may also be coded as an option in the preferred network behavior parameters. The multi-SIM indicator may be a standalone indicator. The network entity shall provide appropriate support for multi-SIM operation during the attach procedure. Check and select the appropriate network entities to enable paging request forwarding. It can be used to Step S2506: In response to the indirect attach request or the indirect attach indication, the PLMN The MME of one SIM must have the appropriate MME to handle the indirect attach request for each SIM. The identifiers provided to SIM2 may include the MCC and MNC, or resolves to the MCC and MNC used to determine the MME that should be contacted. The MME of PLMN1 may determine the core network configuration, roaming agreement, or Due to other mechanisms that support multi-SIM operation, other MMs in different PLMNs may E contact information, so that the MME in PLMN1 , the indirect attach request may be forwarded to the corresponding MME. Step S2508: MME1 sends an indirect attach request to the selected MME. The request includes the indirect attach indicator, the multi-SIM indicator, the SIM2 identifier, and and other information required for the connection request. In addition, SIM1 may authenticate with PLMN1. In order to inform the MME of PLMN2 that the SIM has been MME1 may be provided with a UE ID and a UE ID for PLMN2. or a paging request from PLMN1 to SIM1. Further providing context information of the MME of PLMN1 to receive the request for This MME in PLMN1 is configured to support paging request forwarding. and the UE receives the appropriate network entity from PLMN2. Paging to the entity (e.g. the MME to which the UE is attached in case of UE mobility) It may be possible for the MME to forward the request if the UE is attached to PLMN2. During this time, paging requests for SIM1 may be forwarded from PLMN1 to PLMN2. Step S2510: The indirect attach request is The request is processed as outlined in steps 3 through 17 of the 202 Attach procedure. The NAS message response sent by S2006 goes to the RAN node in PLMN2 instead. Note that the received call from this procedure is then rerouted to the MME in PLMN1. The indirect attach acceptance response sent contains the status of the outcome of the procedure. An indication that authentication was successful. The temporary identifier, the UE's EMM state for SIM2 is EMM-DEREGISTERE D to EMM-INACTIVE, PLMN1 indicates that SIM1 Acknowledgement of support for receiving a paging request forwarded for PLMN 1 or MME contact information for receiving paging requests from SIM2 and the registration type of SIM2 If the indirect attach was not accepted, the response is Further information may be included detailing why the request was not accepted. Step S2512: The MME of PLMN1 notifies the MME about the status of the indirect attach procedure. An indirect attach acceptance message, which may be a modified attach acceptance message that provides additional information. If the attach procedure is performed for multiple SIMs, the UE returns the There can be separate registration statuses for S. The response message contains the temporary identifier and S It may contain information returned from the MME of PLMN2, such as an indication of successful authentication of MME2. The temporary identifier assigned to SIM2 is used for SIM2 transferred to PLMN1. In addition, the MME of PLMN1 Instead of using a temporary identifier assigned by PLMN2, the UE is paged. A separate temporary identifier can be assigned for SIM2 that can be used to This temporary identifier assignment is made when the relevant paging occasion is associated with SIM1. As a result, the UE may not be able to use paging occasions for SIM1 and SIM2. Only one paging occasion needs to be monitored to receive both pages of IM2. Alternatively, the MME may decide that the UE only needs to monitor one paging occasion and not all S While maintaining the fact that it can receive IM pages, All SIMs can be assigned the same temporary identifier. Each SIM's EMM The state is updated. In this scenario, the EMM state of SIM1 is EMM-REGISTE RED for SIM1 and EMM-INACTIVE for SIM2. Similarly, PLMN The EMM state in the MME of SIM 1 is EMM-REGISTERED for SIM 1. Finally, the MME of PLMN2 The EMM state in is EMM-INACTIVE for SIM2. Includes SGW2 2504 and PGW2 2506.

[0171] Similar to the indirect registration performed over the user plane in 5G as shown in Figure 39, The attach request may also be sent over the user plane in LTE. This procedure is carried out in a similar manner. However, the messages and entities involved are the same as LTE messages and For example, an indirect registration message is placed in an indirect attach message. The message is then forwarded to the LTE RAN, SGW / PGW, ePDG, and MME. The LTE RAN and SGW / PGW are associated with PLMN1 and The ePDG and MME are associated with PLMN2. The policy is This may come from the Network Discovery Selection Function (ANDSF) policy.

[0172] (MUSIM registration / attachment) Another enhancement of both 5G and LTE systems to support multiple SIMs is MUSIM allows the UE to register multiple SIMs in the same registration or attach request. This is due to the introduction of the registration or attachment procedure. The order is SIM to the same or different PLMN depending on which operator issued the SIM. It can support registration of IMs. For SIMs obtained from the same operator, SIMs may be registered in the same PLMN, and within a PLMN, one for each SIM, A UE context is created. In addition, the UE context is used to forward paging requests. can be linked together to provide optimization when For an active SIM, the UE registers the SIM associated with the active PLMN and then The network allows SIMs from other operators to register with their associated PLMNs. When a SIM registers to a different PLMN, the core network Work can use either the partial or indirect registration / attach procedure described above. FIG. 26 illustrates an example MUSIM attach procedure in more detail. The figure relates to LTE. Note that although the terminology used herein applies to 5G systems, the procedures may also be applied to 5G systems.

[0173] Step S2602: Two SIMs are installed in the MUSIM-enabled UE. M1 is the primary SIM and is associated with PLMN1, SIM2 is the secondary SIM M and associated with PLMN2. The diagram shows only two SIMs, but it is possible to have more than two. The above SIMs may be installed in the UE, and an attach procedure is performed for each installed SIM. It is noted that it is understood that the procedure remains the same except extended to IM. Step S2604: The UE receives the PLMN associated with each installed SIM. The MUSIM performs a MUSIM attach request which results in the MUSIM being registered to the In addition to other data required for the attachment procedure, the multi-SIM indicator and In addition, it is possible to determine how SIMs associated with different PLMNs can be managed. A partial attach indication or an indirect attach indication is sent to inform the MME in PLMN 1 whether to register on the The instructions may be provided either on a per-SIM basis or on a per-SIM basis for all SIMs. The attachment procedure from TS 23.401 may be provided collectively for the IM. If it is enhanced to integrate the MUSIM functionality proposed here, it will be a multi-SIM interface. The indicator may be encoded as an option of a preferred network behavior parameter, or may be a standalone indicator, partial / indirect attachment indicators are The message may be carried in the attach type parameter. which SIM is the primary SIM and which SIM is the secondary SIM and registers to the inactive PLMN It may further indicate what the metric should be used for. Step S2606: The MME of PLMN1 performs an attach procedure of the primary SIM. The UE is authenticated and authorized and a registration context is created on MME1 for SIM1. This procedure also establishes the default QoS for the UE in the SGW and PGW of PLMN1. Since SIM1 is the primary SIM, if the attach is successful, The EMM state of SIM1 in the MME is set to EMM-REGISTERED. Step S2608: The MME of PLMN1 also belongs to the same operator as SIM1. You can register another SIM. If SIM2 belongs to the same operator as SIM1 , the attach procedure is performed for SIM2, and a separate M A registration context for SIM2 is created in the ME. However, the UE context The requests can be linked together to provide optimizations when forwarding paging requests. If the attach is successful, the EMM state of SIM2 is 0 because it is not the primary SIM of the UE. This step is performed for SIM1 belonging to the same PLMN as SIM1. In this particular case, SIM2 is a different PL Since it belongs to MN, step S2608 is skipped. Step S2610: The MME of PLMN1 performs partial access to SIM2 with PLMN2. In step S2604, the UE performs either a touch or an indirect attach. The ATTACH request may provide an indication of which ATTACH request should be performed, or the MME may provide an indication of which ATTACH request should be performed. The touch procedure may be performed by the core network. It may have a system policy that indicates which attachment procedure should be performed. Here, the MME in 1 sets the EMM state of each SIM to EMM-INACTIVE. The EMM state of each SIM in each PLMN is also set to EMM-INACTIVE. The information exchanged between PLMN1 and PLMN2 is the same as previously specified. In order to protect the privacy of the UE, certain information is encrypted in the NAS content. It is possible within the na. Step S2612: The MME of PLMN1 receives all the attach acceptance results of each SIM. The MME of PLMN1 aggregates the data allocated by other PLMNs and returns them to the UE. Instead of using a temporary identifier assigned to each SI that may be used to page the UE, A separate temporary identifier may be assigned for M. The assignment of these temporary identifiers The relevant paging occasion is the paging occasion associated with the primary SIM. As a result, the UE may receive all SI All it has to do is monitor paging opportunities that are close to each other so that it can receive M pages. Alternatively, the MME may assign the same temporary identity to all SIMs associated with the UE. Since a Paging Occasion Identifier can be assigned, the UE only needs to monitor one Paging Occasion. However, you can receive the page for all SIMs. When you receive the attachment acceptance, E sets the appropriate EMM state for each SIM. In this particular case, The EMM state for SIM1 is EMM-REGISTERED, and for SIM2 it is EMM-I It is NACTIVE.

[0174] (5G registration state for multi-SIM operation) New Registration Management (RM) state to support multi-SIM operation in 5GS A new state called RM-INACTIVE is proposed for inactive PLMNs. In addition, the state refers to the RM state of the UE with the This represents the fact that the SIM has been authenticated for the purpose of Any existing UE contexts and PDU sessions in the network will be deleted as if the UE M-REGISTERED, CM-IDLE, and RRC_IDLE or RRC_I Therefore, the UE remains in RM-INACTIVE state. When in the IVE state, it also enters CM-IDLE and RRC_IDLE or RRC Must be in _INACTIVE state.

[0175] The RM-INACTIVE state means the following (see SIM and PLMN in Figure 9): ). The UE is registered to PLMN2 for SIM2 and receives services from PLMN2. For example, voice or IMS calls, SMS messages, etc. The UE is in CM-IDLE state and has not yet established NAS signaling with the PLMN2 core network. Does not have a ring. The UE is not connected to any RAN node in PLMN2, and therefore It is not monitoring paging opportunities from PLMN2 for IM2. When the UE is transferred to PLMN1 by PLMN2, the page The device can receive a request for a call. The AMF (or UDM) of PLMN2 sends a paging request to SIM2 to the PLM The UE can be paged by forwarding to the AMF of N1. · The AMF of PLMN2 does not know the location of the UE. The security context protects NAS messages between the UE and PLMN2. To achieve this, it may be stored in the AMF in PLMN2.

[0176] FIG. 14 shows the RM management state updated to include the RM-INACTIVE state. The UE shall transition from the indicated RM state to the RM-INA state by performing the procedures listed. It is possible to transition to the CTIVE state. RM-DEREGISTERED to RM-INACTIVE state: oPerforming partial registration procedures o Performing the indirect registration procedure From RM-REGISTERED state to RM-INACTIVE state: Performing oSIM switching (e.g. periodic registration renewal) procedures

[0177] The UE can transition from RM-INACTIVE state as follows: RM-INACTIVE to RM-REGISTERED oCompleting the registration process Performing oSIM switching (e.g. periodic registration renewal) procedures RM-INACTIVE to RM-DEREGISTERED o Executing a deregistration procedure (either initiated by the UE or the network) The core network performs periodic registration when the UE is in RM-INACTIVE state. If updates are not performed in a timely manner (e.g., the registration timer (in a multi-SIM policy) , expires before the UE performs a periodic registration update procedure), and initiates a deregistration procedure. can be done. o If a registration renewal request fails

[0178] The UE performs the SIM switching procedure and the switch is accepted by the core network In this case, the UE's RM state transitions from RM-REGISTERED to RM-INACTIVE. However, if the switchover is rejected, the UE RM state changes to RM-DEREGI Transition to STERED.

[0179] In the above description, we have updated the RM state model to include a new state, RM-INACTIVE. However, introducing new states into the state model is a As a result, the new RM-INACTIVE state , as a substate of the RM-REGISTERED state, or D state, because it is different from the RM-INACTIVE state. Both the RM-REGISTERED state indicates that the UE is registered in the core network and This is because it is assumed that the UE can receive services from the core network. RM-INACTIVE has many of the same properties as the RM-REGISTERED state. However, one major difference is that the UE does not receive a page from an inactive PLMN. The UE is not actively monitoring paging opportunities and therefore paging request forwarding is required. RM-INACTIVE is the "inactive registration" substate or RM-R This is sometimes called the EGISTERED mode of operation. The "Active Registration" substate or mode is shown in FIG. 14 and elsewhere in this disclosure. It can replace the M-INACTIVE state.

[0180] (LTE Mobility Management States for Multi-SIM Operation) Similarly, the Enhanced Mobility Management (EMM) state in LTE is a direct descendant of the 5GS registration management state. It provides functionality similar to that of registering secondary SIMs with their corresponding PLMNs. To support the UE in the above, the registration status of those secondary SIMs must be updated to all A new EMM state is proposed to notify the EMM entity of the new state, EMM-IN. ACTIVE means that the secondary SIM is registered to a PLMN, but the UE is not connected to that PLMN. This captures the fact that the UE is not actively communicating with the In MM-REGISTERED state and in ECM-IDLE or ECM-CONN In other words, the UE can be in either the NAS A notification may be received or a page may be received from the core network. Even if the UE is not actively communicating with the PLMN, it may still receive e.g. telephone messages. A UE context may be stored in the PLMN to receive the LTE or short messages. do.

[0181] The EMM-INACTIVE state means the following (SIM and PLMN in Figure 25): reference). The UE is registered to PLMN2 for SIM2 and receives services from PLMN2. For example, voice or IMS calls, SMS messages, etc. The UE is in ECM-IDLE state and has notified the PLMN2 core network of the NAS signaling. Has no nulling. The UE is not connected to any RAN node in PLMN2, and therefore Actively monitor paging requests from RAN nodes in LMN2 to SIM2. do not have. When the UE is transferred to PLMN1 by PLMN2, the page The device can receive a request for a call. The MME (or HSS) of PLMN2 sends a paging request to SIM2 via PLM The UE can be paged by forwarding it to the MME of N1. · The MME of PLMN2 does not know the location of the UE. The security context is stored in the MME of PLMN2 and is transmitted from PLMN2 to the UE. It is used to protect messages to

[0182] Figure 27 shows the EMM state model incorporating the new state EMM-INACTIVE. This state transition model is implemented in both the UE and the MME. The UE is By executing the procedure, the indicated EMM state is changed to the EMM-INACTIVE state. A transition can be made. From EMM-DEREGISTERED state to EMM-INACTIVE state: o Performing a partial attachment procedure oPerforming an indirect attachment procedure From EMM-REGISTERED state to EMM-INACTIVE state: Performing an oSIM switch (e.g. registration update request) procedure

[0183] The UE can transition from EMM-INACTIVE state as follows: From EMM-INACTIVE state to EMM-REGISTERED state: oPerforming the attach procedure Performing an oSIM switch (e.g. registration update request) procedure From EMM-INACTIVE state to EMM-DEREGISTERED state: o Executing a detach procedure (either initiated by the UE or the network) The UE periodically updates the attach timer when in EMM-INACTIVE state. If not, the core network may initiate a detachment procedure. o If a registration renewal request fails

[0184] The UE performs the SIM switching procedure and the switch is accepted by the core network In this case, the UE's EMM state changes from EMM-REGISTERED to EMM-INACTIVE. However, if the switch is rejected, the UE's EMM state transitions to EMM-D. Transition to EREGISTERED.

[0185] In the above explanation, we have updated the EMM state model to include a new state, EMM-INACTIVE. In theory, the proposed new state would be a functional extension of the existing state. New introduced by providing clear delineation and supporting multiple SIM UE However, in practice, the new state is not realized given the existing configuration. This may not be possible. Therefore, the new EMM-INACTIVE state is - As a substate of the REGISTERED state, or in the EMM-REGISTERED state The UE can be considered as a mode of operation within the UE state because both states are It is assumed that the mobile station is registered in the network and can receive services from the core network. Furthermore, many of the characteristics of EMM-INACTIVE are the same as those of EMM-REGIS. The characteristics of the TERED state are similar. However, one main difference is that the UE does not actively monitor paging requests on the active PLMN and therefore Referring back to the example of FIG. 25, the UE receives the (SI M2) is in EMM-REGISTERED state with PLMN2, but not with PLMN1 A "non-AP" requires the PLMN2 to forward any paging requests to the UE through Therefore, the EMM-INACT The IVE enters an “inactive registration” substate or module in the EMM-REGISTERED state. Therefore, this "inactive registration" substate or mode This replaces the EMM-INACTIVE state referenced in FIG. 27 and elsewhere in this disclosure. It can be replaced.

[0186] The EMM state of each SIM in the UE is optimized to reduce power consumption for multi-SIM operation. For example, a PL for each SIM can be combined in the UE to provide a uniform operation. Instead of performing MN and cell selection, a multi-SIM UE performs the SIM switching procedure. When you later try to connect to that PLMN, the active SIM or the target PLMN N, it is possible to minimize power consumption by simply performing PLMN and cell selection. Similarly, certain timers, such as the DRX timer and other NAS timers, can be Table 3 shows an example of a two SIM UE. The table shows the case of two SIMs, where optimization can be achieved based on the EMM state of each SIM. Although the example shows the SIM card, it can be easily extended to support more than two SIM cards. Note that some of the state combinations are EMM-INACT for both SIMs. It is temporary, such as an IVE state, and may occur temporarily during the SIM switching procedure. There is.

[0187] [Table 3]

[0188] (Multi-SIM paging operation) After the UE has registered the registration status of SIM1 and SIM2 and linked them to the corresponding PLMNs Then, a paging request associated with any SIM is sent to the UE on the active PLMN. Within each PLMN, a SIM is sent to inform the PLMN that the SIM belongs to the same UE. In addition, the registration status of each SIM can be stored and linked together. Originating in PLMN2, an LMN, through PLMN1, an active PLMN An example of a page received by the UE is shown. Within PLMN1, the registration state of SIM1 is RM-REGISTERED, and the registration status of SIM2 is RM-INACTIVE (or or "inactive registration" substate or mode of RM-REGISTERED In addition, PLMN1 can forward paging requests from PLMN2 to the UE. Thus, a temporary identifier mapping between SIMs may be maintained.

[0189] Step S1502: The UE detects that the RM state of the UE with the PLMN2 is RM-INACTIV. E, in order to transfer the page of SIM2 to PLMN1, The UE is performing either partial registration or indirect registration in IM2. -REGISTERED and CM-IDLE. The UE is in Multi-cast each PLMN of the SIM to configure the PLMN of the user's preference. Multi-SIM support information can be provided. Please see below for more information on multi-SIM support. Explain in detail. Step S1504: The UE receives a paging device associated with SIM1 or SIM2. For example, the UE receives a temporary identifier and a new SIM ID for SIM1 from the AMF of PLMN1. The question is whether the AM has been provided with a different temporary identifier for SIM1 and SIM2. F assigns temporary identifiers such that the paging occasions calculated from each identifier overlap at the same time. This may assign a time for which the UE needs to monitor paging occasions. Note that, the,R,is minimized. As a result, the UE can use,the,R,and,SIMs that apply to both SIMs. If there are three or more SIMs, A The MF assigns temporary identifiers so that paging occasions do not collide with each other and can be close to each other. In these cases, the UE must monitor multiple paging occasions. may not be possible, but you will still receive pages for all SIMs without paging collisions. Alternatively, the AMF may be the same for all SIMs associated with the UE. A temporary identifier can be assigned so that the UE monitors one paging occasion. That's all you need. Step S1506: If SIM2 is registered in partial registration, the paging request is sent, for example, For example, from a voice or IMS call associated with SIM2 to SIM2 in UDM2 The signal is sent from PLMN2. UDM2 receives the signal from AMF1 in step S1506. 2. The UE sends a pinging request to the UE, which forwards the pinging request to the temporary identifier assigned to SIM2 by PLMN2. The temporary identifier is generated at the end of the partial registration procedure to identify the page to which it is associated. In addition, the service prioritization information is provided to the UE. To inform the UE of whether to switch to PLMN2 or not The service prioritization information may be included in the paging request, such as the service type, The UE may also include additional information identifying the source of the data for which it is paging. The service type can be a voice call, an SMS message, or other data from an application. , Control Plane Signaling, Emergency Messages, Emergency Callback, Mobile Termination Exception De The additional information may be the phone number of the caller or SMS message, The PDU session ID, slice instance ID, or application associated with the data. Alternatively, the additional information may be a user ID for a multi-SIM UE. The paging request may be retrieved only by the UE. and the contents of the NAS notification generated by PLMN2 to SIM2. It can be encapsulated in an encrypted NAS container so that it can be included. A temporary identifier for the service prioritization information and, in some cases, the service type are LMN1 identifies the UE to which the NAS container is to be forwarded and what the page is for It may be unencrypted to allow some instructions to be provided to the UE. The contents of the NAS container of the messaging request are also sent to the PLM UE to retrieve the message. The SMS message may be sent to the UE without connecting to N2. If the M assistance information is provided to PLMN2, PLMN2 decides whether to page the UE. For example, the service prioritization information associated with the page can be determined. However, it is important to users to be reflected in the multi-SIM support information. If not, PLMN2 sends the paging message shown in step S1506. In some cases, the PLMN2 does not transmit the UE identity and service prioritization. It may be configured to forward a paging request message containing only the information. The user has all paging messages filtered by the active PLMN. Therefore, all inactive PLMNs should forward paging requests to Page with only the information required by the active PLMN to filter The second step is to configure the NIC so that it needs to forward the ping request. Step S1508: Alternatively, if SIM2 is registered in an indirect registration, AMF2 Able to receive SIM2's downlink data notification and forward the page to AMF1 The page contains a temporary identifier associated with SIM2 from PLMN2, as well as the page is for and the UE switches to PLMN2 The service prioritization information can be used to determine whether The temporary identifier was provided to the UE at the end of the indirect registration procedure. Similar to step S1506, the paging request includes the service prioritization information and the SM The S message may also include an encrypted NAS container. Step S150 Similar to 6, PLMN2 uses multi-SIM assistance information to send paging messages. whether to forward the paging message to PLMN1 and what information to include in the forwarded paging message The committee can decide whether to include the Step S1510: AMF1 determines whether step S1506 or step S1508 It processes paging requests from either the UE or the UE and generates a NAS notification to the UE. It may contain a temporary identifier for SIM2 and any service prioritization information provided. This notification can be sent by using the encrypted NAS container, so that if provided, only the UE can access the container and If the UE is in CM-IDLE state, A The MF1 generates a paging request message for paging the UE. Step S1512: AMF1 retrieves a page with a temporary identifier associated with SIM2. In other words, as an example, a paging message is sent to the UE via RAN1. The UE identity in the PagingRecord information element of the message is The temporary identifier used is set to the temporary identifier associated with step S1. It may be any of the identifiers specified in 504. In addition, The d information element is the service ID sent by AMF2 in step S1506 or S1508. The service prioritization information may be enhanced to provide service prioritization information. Service type (e.g. voice or IMS call, SMS message, PDU session) Other data for control plane signaling, emergency messages, emergency callbacks, Mobile termination exception data, etc.) and PDU session ID or slice instance It may contain other information such as a page ID to further inform the UE what the page is for. If the UE is in CM-CONNECTED state, AMF1 can The NAS notification from step S1510 is sent to the UE instead of the message. is used to generate paging messages when the UE is in CM-IDLE AMF1 contains the same information as the paging message sent to SIM1. The PLMN2 node notifies the RAN node to page the UE on the paging occasion that was selected. Note that the paging information associated with SIM2 received from AM If F1 assigns a separate temporary identifier to SIM2, AMF1 assigns a separate temporary identifier to SIM2. R to page the UE using the temporary identifier assigned to AMF1. The PagingRecord information element can be sent to the AN node. AMF1 contains a temporary identifier that is assigned to all SIMs in the UE. If the same temporary identifier has been assigned, this temporary identifier is used to page the UE. Used for. Step S1514: The UE reads the paging message and sends the paging message. Based on the temporary identifier of the information element of the UE identity of the page, the page is determined to be for SIM2. The UE identity information element is assigned to SIM2 by PLMN2. contains the temporary identifier assigned to it or one of the temporary identifiers assigned to it in AMF1. If the temporary identifier is shared among all SIMs, the UE shall obtain the temporary identifier when the page applies. It may be necessary to perform a service request procedure to find the SIM that is being used. The message also prompts you to follow the service request procedure to get more information on what to do next. The indicator may include an indicator to notify the UE to perform Otherwise, the UE will automatically send a service request when it determines that the page is for the UE. If the UE is in CM-CONNECTED, The AS notification is processed and the UE decides what to do next by evaluating the service prioritization information. The UE also decides whether to accept the SMS message if it is provided in the NAS container. The UE can then process the SMS message and present the message to the user. There is no need to connect to PLMN2 to extract the message. Step S1516: If the UE is in CM-IDLE, the UE sends a RA to SIM1. The UE then establishes an RRC connection with N1. The UE then connects to the core network to establish a NAS connection. The service request response provides information about what to do next. It provides the UE with more information to receive the temporary identifier and sub-identifier of SIM2 from PLMN2. The service prioritization information may be evaluated to The UE performs the SIM switching procedure to complete the processing of the page and It can be determined that data is to be received from PLMN2. If provided in the S container, the UE can present the message to the user and There is no need to connect to PLMN2 to retrieve the message.

[0190] Figure 15 shows a UE with an active registration with PLMN1 and an inactive registration with PLMN2. 1 shows a case where SIM1 has a paging record and can receive a paging request for SIM2 transferred from PLMN2. Conversely, a UE may be actively registered in PLMN2 and inactively registered in PLMN1. The UE may be registered as inactive and may receive a paging request forwarded from PLMN1. The requirement for forwarding a paging request from an inactive PLMN with a registration is that the UE The objective is to perform either partial registration or indirect registration with the active PLMN.

[0191] Service prioritization information is sent to voice or IMS calls, SMS messages, and other data. data (e.g., mobile terminated data such as Internet data), control plane signaling Downlink, such as emergency messaging, emergency callback, and mobile terminated exception data A service associated with the service that the core network provides to the UE for receiving data. The service type prioritization information can also include such Priority category that specifies the source of such service, e.g. PDU session ID, slice Instance ID, application ID, from family, friends, or service providers Alternatively, the additional information may be related to a multi- It may be a prioritization level configured by the user of the SIM UE. The resulting enumeration, combining types and priority categories, is The PagingRecord information element of the Paging Message is used to make the switching decision. Alternatively, the service type can provide the UE with additional information about how to The device may determine which paging channel is being used to paging the call. The service prioritization information is retrieved by the UE in response to receiving a paging request. This service type prioritization information may be provided by the corresponding PLMN. To help the UE decide whether to switch to a service that is being It may be compared with the service prioritization list.

[0192] Multi-SIM paging operation is supported when the UE is in CM-IDLE with an active PLMN. However, when the UE is in CM-CONNECTED, different A mechanism is needed to allow the active PLMN to communicate with the UE in CM-CONNEC mode. Send a NAS notification to the UE when in TED state to notify it of pending deactivation of an inactive SIM. This NAS notification can be used to notify the UE that a packet from PLMN2 is available. This NA can provide the same information as found in the ping message. The S notification is a trigger event to page the UE when the UE is in CM-IDLE state. In other words, there is a paging request for an inactive SIM. Whenever an active PLMN sends NAS communication to a UE in CM-CONNECTED state, If the UE is in CM-IDLE state, the NAS notification is sent to the UE. brings up the page.

[0193] Multi-SIM paging operation is similar in LTE. As mentioned above, paging The paging request forwarding is performed when the UE accesses the paging occasions associated with those secondary SIMs. Even if the MUSIM UE is not actively monitoring the page for the secondary SIM, This feature is required to successfully perform the attach procedure described above. In the scenario shown in Figure 28, the UE uses the primary SIM. is actively communicating with PLMN1 using a SIM card and is used for a secondary SIM on PLMN2 PLMN2 sends the paging request of the secondary SIM to PLMN1. and PLMN1 informs the UE that there is data for SIM2 on PLMN2. Figure 28 shows this sequence while the UE is in ECM-CONNECTED with PLMN1 of SIM1. Show the scenario.

[0194] Step S2802: SIM1 and SIM2 are installed in the UE, and SIM1 is SIM1 is the primary SIM and SIM2 is the secondary SIM. The UE The 1st generation LTE-2000 is performing either partial or indirect attachment with PLMN2, and the 1st generation LTE-2000 is performing either partial or indirect attachment with PLMN2. The EMM state in the UE for SIM1 is EMM-REGISTERED and EMM-INACTIVE for SIM2. or in the "inactive registration" substate or mode of EMM-REGISTERED) The UE configures the PLMN of the user's preferences for multi-SIM operation. To achieve this, multi-SIM support information can be provided to each PLMN of the SIM. Next, we will explain the multi-SIM support information in more detail. Step S2804: The UE is in ECM-CONNECTED state with respect to SIM1. , receiving data services from PLMN1. Step S2806: Data is available for SIM2 on PLMN2. UE If the PLMN 1 had previously performed a partial attach, the HSS of the PLMN 2 performs a partial attach in step S28. In 06a, the UE forwards the paging request to the MME of PLMN1. If so, the MME of PLMN2 performs the MME of PLMN1 in step S2806b. The paging request is forwarded to the UE's Paging Node B on the PLMN2. indicates that there is data for SIM2, and a temporary identifier assigned to SIM2, PDU session ID, Identifiers, such as application IDs, and / or application names associated with the data for the page application ID, as well as a service category that indicates what the page is for. The paging request may include additional information. A NAS code that contains the content of the generated NAS notification and is encrypted so that only the UE can decrypt it. A temporary identifier and possibly a service category may be encapsulated in a The page service category is used by PLMN1 to identify which UE the container should be forwarded to. The paging request may be unencrypted to allow the user to provide an indication of the page location. The contents of the NAS container also connects the UE to the PLMN2 to retrieve the message. The multi-SIM support information may include an SMS message that may be sent to the UE without requiring the user to If provided to the PLMN2, the PLMN2 uses the information to send paging messages. whether to forward paging messages to PLMN1 and what information to include in the forwarded paging messages You can decide whether to include Step S2810: The MME of the PLMN1 transmits the page received in step S2806. From the authentication request, it generates a NAS notification that contains the encrypted NAS container. Step S2812: The MME of the PLMN 1 sends a NAS notification to the UE. is sent from PLMN2 informing the UE that SIM2 has data available Contains an encrypted NAS container. The information includes a temporary identifier for SIM2, The assigned service category and the PDU session ID and / or application The SMS message can contain other information such as the NAS container ID. When provided to the UE, the UE can present the message to the user, and thus the UE does not need to be connected to PLMN2 to retrieve the SMS message. Step S2814: The UE checks the service category and determines whether the UE is to retrieve data. The service category is voice communication. conversations, SMS messages, or other data (e.g., application data), control programs, Lane signaling, emergency messaging, emergency callback, mobile terminated exception data, etc. The UE shall determine whether the provided service category information is The MME determines that the request needs to be performed and proceeds to send a request to the MME of PLMN1. may be a registration update request or an enhanced TAU request, and the UE may Provide a SIM switch indication to inform PLMN1 that you want to suspend (For example, set the UE state of SIM1 to EMM-INACTIVE). The request is granted. In this case, the MME of PLMN1 sets the EMM state of SIM1 to EMM-INACTIVE. (or the "inactive registration" substate or module of the EMM-REGISTERED state) mode), activate paging request forwarding for SIM1, and enable security con- All UE connections managed by PLMN1, including text and existing PDN connections Upon receiving a registration update or TAU acceptance response, the UE also The EMM state is set inside the application. The SIM switching procedure is done via GUI and API. application or through the UE policy for multi-SIM operation. Note that the command can be started by Step S2816: The MME of PLMN1 repeats the original page count from step S2806. Depending on the source of the paging request, the paging request is sent to either the MME or the HSS of PLMN2. The response indicates that the UE has decided to perform the SIM switching procedure and The MME or HS of PLMN2 must contact the PLMN2 to complete the processing of the message. The MME of PLMN1 can also notify SIM1 of the paging request forwarding. Alternatively, the response may be The page was received, but the user is currently connected to PLMN2 to retrieve the page data. This can include instructions to confirm that the user is not interested in This may occur if the user is on a call and does not want to be interrupted. You can provide this instruction through the UI. Step S2818: Then, the UE performs PLMN selection and reads system information. The UE then performs a cell selection in PLMN2 to attempt to connect to PLMN2. During the process, cell measurement information is collected and sent to the RAN node in PLMN2 when the connection is successful. It may be configured to provide. Step S2820: If the UE successfully connects to the PLMN2, the UE Send a request to update the registration state, such as an attach request or a service request, to update the previously executed Provide a temporary identifier assigned to SIM2 from one of the previously performed attachment procedures. The UE then sends a semaphore command to indicate the data associated with the page from step S2806. If successful, the request may include the identifier sent in step S2806. The UE's EMM state at E2 is transitioned to EMM-REGISTERED (or Disable the "inactive registration" substate or mode of M-REGISTERED), The UE retrieves data associated with the paging request sent in step S2806. Upon receiving the response, the UE also updates its internally stored EMM state Transition to MM-REGISTERED (or "non-EMM-REGISTERED" The UE also disables the "active registration" substate or mode in step S282. 0 to the RAN node of PLMN2. These measurements may be used to assist cell planning for an operator of PLMN2.

[0195] Figure 28 shows a UE in ECM-CONNECTED state with SIM1 in PLMN1. FIG. 29 shows a paging request transmission sent when a PAG is received from an E The same scenario is shown with the UE in CM-IDLE state. In other words, the UE The ECM state in both the MME of PLMN1 and the MME of PLMN2 is ECM-IDLE. If so, the UE is associated with a temporary identifier that was assigned to the UE during the attach procedure. Monitor paging information at selected paging occasions.

[0196] Step S2902: SIM1 and SIM2 are installed in the UE, and SIM1 is SIM1 is the primary SIM and SIM2 is the secondary SIM. The UE The 1st generation LTE-2000 is performing either partial or indirect attachment with PLMN2, and the 1st generation LTE-2000 is performing either partial or indirect attachment with PLMN2. The EMM state in the UE for SIM1 is EMM-REGISTERED and EMM-INACTIVE for SIM2. or in the "inactive registration" substate or mode of EMM-REGISTERED) The UE configures the PLMN of the user's preferences for multi-SIM operation. To achieve this, multi-SIM support information can be provided to each PLMN of the SIM. Next, we will explain the multi-SIM support information in more detail. Step S2904: Since the UE is in ECM-IDLE state, the UE The paging devices associated with SIM1 and SIM2 receive paging requests from The UE receives a temporary identity for SIM1 from the MME of PLMN1. Note that you may have been provided with different temporary identifiers for child and SIM2. Therefore, the MME must ensure that the paging occasions calculated from each identifier do not overlap at the same time. A temporary identifier may be assigned to the UE so that it can monitor paging requests. As a result, the UE only needs to perform one paging If there are more than two SIMs, the MME only needs to monitor the paging opportunities. In some cases, temporary identifiers are assigned to avoid collisions. In these cases, the UE may have to monitor multiple paging opportunities, but will not encounter paging collisions. You can still receive all SIM pages without encountering any other In this case, the MME may assign the same temporary identifier to all SIMs of the UE. This identifier is used to calculate the paging occasion and therefore the UE This minimizes the number of paging occasions that the UE must monitor. Only one paging occasion needs to be monitored and all SIs installed in the UE M's page can be received. Step S2906: Data is available for SIM2 on PLMN2. UE If the PLMN 1 had previously performed a partial attach, the HSS of the PLMN 2 performs a partial attach in step S29. In 06a, the UE forwards the paging request to the MME of PLMN1. If so, the MME of PLMN2 performs the MME of PLMN1 in step S2906b. The paging request is forwarded to the UE's Paging Node B on the PLMN2. A temporary identifier assigned to SIM2 by PLMN2 indicating that there is data to Associated with an identifier, such as a PDU session ID, and / or data for the page The assigned application ID, as well as the service that the page is for The paging request may contain additional information such as the category. Contains the content of the NAS notification generated for IM2, encrypted so that only the UE can decrypt it The temporary identifier and the service category may be encapsulated in a NAS container. identifies to which UE PLMN1 should forward the container and the service category of the page The N of the paging request may be unencrypted to allow the N The contents of the AS container also connects the UE to PLMN2 to retrieve the message. The multi-SIM support information may include an SMS message that may be sent to the UE without If provided to the PLMN2, the PLMN2 uses that information to send paging messages. to PLMN1 and what information to include in the forwarded paging message. You can decide whether to include it. Step S2908: The MME of the PLMN1 transmits the page received in step S2906. The ISP processes information from the request. Step S2910: The MME of PLMN1 transmits the SIM In step S2910a, the RAN node uses the temporary identifier assigned to the UE for The temporary identifier used is stored in the storage device 200 in step S2904. The RAN node then determines whether the UE is monitoring In step S2910b, the UE is paged on the paging occasion that is set by SIM1 and Since both paging occasions for SIM2 are the same, the UE The paging message also indicates what the page is for. The service may include service prioritization information to inform the UE which services are being serviced. Step S2912: Then, the UE reads the paging report and allocates it to SIM2. Based on the presence of the assigned temporary identifier and the service prioritization information, the page The temporary identifier is shared among all SIMs. If so, the UE performs a service request procedure to find the SIM to which the page applies. Paging messages may also provide more information about what to do next. The instruction may include an instruction to inform the UE to perform a service request procedure to retrieve the service information. If the indication is not present, the UE shall determine that the page is for the UE. , may be configured to automatically execute service requests. Step S2914: The UE performs a subroutine to retrieve more information on what to do next. When the SR procedure is performed, the MME of PLMN1 receives the The UE may be provided with information from a forwarded paging request received from the The information includes a temporary identifier associated with the page, the service category of the page, and the status. The received information may include other information received from the call S2906. Steps S2916 to S2922: The UE performs steps S2814 to S2820 in FIG. to complete the processing of the page, attach to PLMN2, and associate it with the paging request. The received data is received.

[0197] An alternative to step S2910a in FIG. 29 is for the MME of PLMN1 to obtain a temporary identity of SIM2. Send a paging request to the RAN node using the temporary identifier of SIM1 instead of the identifier of SIM1. In this alternative approach, the paging information provides more information about what to do next. The SI with an instruction to inform the UE to perform a service request to obtain more information When the UE performs a service request procedure, the MME of PLMN1 information that the page was for SIM2 and the service category of the page The MME of PLMN1 provides any additional information such as It is not possible to provide a temporary identifier for SIM2 with which to align paging occasions. This alternative method can be used if more than two SIMs are used. Alternatively, the MME of PLMN1 may be installed in the UE. Assign the same temporary identifier to use when paging all SIMs in the In this case, the UE only needs to monitor one paging occasion and Go through the service request procedure to find out which SIM the page is for. E manages this by linking together the registration state of all SIMs in the UE, Assign the same temporary identifier to be used for paging the UE regardless of the SIM.

[0198] The paging request forwarding response shown in step S2918 of FIG. 29 indicates that the UE responds to the page. may be sent without performing the SIM switching procedure in case the user does not wish to respond to the This can happen when a user is on an important call and does not want to be interrupted. The user can provide this indication through a GUI on the UE. In these cases 29. The paging request forwarding response is sent when the UE returns the paging request forwarding response after step S2916, not after step S2917. This is sent after executing the service request procedure in step S2914. Received, but the user is currently connecting to PLMN2 to retrieve the page's data. instructions to confirm that they are not interested in

[0199] Paging request forwarding is also performed by the user if the UE has performed an indirect registration over the user plane. FIG. 40 shows the SI over the user plane of PLMN1. 1 shows an example of a multi-SIM UE receiving a NAS notification from PLMN2 for M2. E has already performed indirect registration of SIM2 with PLMN2 via the user plane of PLMN1. The downlink data arrives at AMF2 of SIM2.

[0200] Step S4002: The UE transmits the PLM of the SIM2 via the user plane of the PLMN1. N2. Indirect registration is when PLMN2 is performing an indirect registration with PLMN1. The UE can then forward a paging request for SIM2 to the UE via the ,To configure the PLMN of the user's preferences for multi-SIM operation, SI M. The IM support information will now be described in more detail. Step S4004: Downlink data is available for SIM2 on PLMN2 and AMF2 is notified. AMF2 indicates that the downlink data is To determine whether the criteria are met, the available multi-SI provided by the UE is If the criteria are met, the AMF2 sends the M assistance information to the UE. Otherwise, AMF2 generates a NAS notification for the UE to receive at this point. The UE sends a downlink response that it is not interested in receiving the data or that the UE is currently unavailable. The response is that the data should be buffered. NAS notifications can indicate whether downlink data or SMS messages are related. The PDU session ID associated with the PDU may be included in the Other events that can occur are the control play of the policy updates that AMF2 wants to send to the UE. This can be a notification signaling to perform periodic registration or TAU updates. Minder, update of URSP rules, new timer values ​​that the UE will use, how long the UE This may include the time at which the notification should be responded to, etc. Step S4006: In step S4006a, the AMF2 receives the user play of the PLMN1. The NAS notification is sent to the UE via the N3IWF2 via the PLMN1 then sends a NAS notification to the UE as a result of receiving the NAS notification from PLMN2. or PLMN1 can transmit to the UE if the UE is in CM_IDLE state. For PLMN1, NAS notification from PLMN2 can be E. The mobile terminated data sent by PLMN 1 in step S4006b. Note that the NAS notification or page is associated with SIM1. Step S4008: The UE evaluates the NAS notification received from PLMN1. The AS notification includes the information sent by PLMN2 in step S4006a. Please note that the NAS notification may be generated in step S4006a. Service prioritization information to assist the UE in identifying associated service types. This may include information. Step S4010: The UE receives the mobile-terminated data that triggered the page. In step S4006a, the NAS communication from PLMN2 is transmitted. If the UE determines that the service prioritization information in the UE is important, the UE shall A service request to PLMN2 is performed using one of the following mechanisms: for the UE to send a service request in response to a NAS indication received from PLMN2. The mechanism is to continue using the user plane of PLMN1. remains connected to PLMN1 and SIM2 is connected to PLMN2 via the user plane of PLMN1. The second mechanism can be used by the UE when it wants to receive data. The second mechanism is to switch the UE to PLMN2 and establish a connection with PLMN2. The mechanism is that the UE is not currently receiving service in PLMN1 and is receiving a signal from PLMN2. The NAS notification is then retrieved and the associated data is retrieved from the PLMN2. If you want to continue receiving the signal, for example to make a call using SIM2, the UE It can be used.

[0201] (SIM switching procedure) When the UE receives a page or NAS notification for a SIM in an inactive PLMN, the UE If the UE decides to retrieve data associated with a page, the UE To suspend the active PLMN and allow the UE to establish communication with an inactive PLMN. Then, a SIM switching procedure can be performed to notify the active PLMN. If the switching procedure is successful, the UE's registration state for the active SIM changes to RM-R. The state transitions from EGISTERED to RM-INACTIVE. The network is designed to allow the UE to quickly return to the RM-REGISTERED state. To do this, all UE contexts, including existing PDU sessions and slice allocations, At this point, the UE performs periodic registration updates to the inactive PLMNs. and changes the RM state with the inactive PLMN from RM-INACTIVE to RM-REGI. The UE then transitions to STERED. FIG. 16 shows the UE receiving the paging message of SIM2. The SIM switching procedure performed by switching from PLMN1 to PLMN2 is The SIM switching procedure shown in Figure 16 uses 5G terminology, but the procedure is the same as for the LTE system. Note that this also applies to

[0202] Step S1602: The UE sends a paging message as shown in FIG. Receive and, based on the UE identity field of the PagingRecord information element, If the temporary identifier is shared between the SIMs of the UE, In this case, the UE may not know which SIM the page is for. , the UE collects this information in step S1604 after performing the service request procedure. In addition, the UE may use the new service prioritization field in the PagingRecord information element. Based on the call, the UE is notified that the page corresponds to a voice or IMS call. is configured to prioritize voice or IMS calls and perform the SIM switching procedure Alternatively, the user may manually switch the SIM card via the GUI as shown in Figure 17. The paging message also initiates the downlinking procedure of SIM2. The device may also support SMS messages or notifications of availability of the data. Step S1604: The UE establishes an RRC connection and an NAS connection so as to communicate with the PLMN1. The UE performs a service request procedure to determine which SIM the page is for. and possibly retrieve information about the service category of the page. The UE receives the PDU session ID, spool, and The device instance ID and / or other information such as the application ID are encrypted. The NAS container can also be used to access the SMS page. Based on this information, the UE performs the SIM switching procedure. The decision may be made by the user through a GUI on the UE or possibly This may be triggered by an application or policy on the UE. Step S1606: Then, the UE determines whether the registration type is set to SIM switching or or performing a SIM switch request procedure where the SIM switch indicator is included in the request The SIM switching procedure should be incorporated as a periodic registration update with SIM switching instructions. This request indicates that the UE should suspend its registration and connect to PLMN2 to begin the page transfer. You want to retrieve data associated with a message or a service provided by PLMN2. This is to inform PLMN 1 that you wish to use the service. Step S1608: AMF1 processes the request and updates the RM state of SIM1 to RM-INAC All PDU sessions managed by PLMN1, including existing PDU sessions, are updated to the All UE contexts are updated until the UE performs a registration update and enters the RM-REGISTERED state. The paging request forwarding is held until the Paging Request Forwarding Session has returned. Depending on whether the UDM1 912 and / or AMF1 904 are activated, It will be democratized. Step S1610: AMF1 determines that the RM state of the UE for SIM1 is RM-INAC 2.2.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.1.0 ...1 The message may be a registration deactivation acceptance message. To indicate to the UE that N1 will remain in RM-INACTIVE state for SIM1 It may include a registration timer value. Step S1612: The UE sends the RM-REGISTERED to the SIM1. - Transition its RM state to INACTIVE and, if provided, a registration timer value. If there is no registration timer value, the UE shall use the registration timer provided by the internal configuration in the UE policy. , or a value configured by the user in the GUI. Step S1614: The UE performs PLMN selection, reads system information, and The UE then performs a registration update procedure for SIM2 and performs cell selection for SIM The RM state of SIM2 in the UE may be changed to the registration acceptance message. Upon receiving the RM-INACTIVE message, the UE transitions from RM-INACTIVE to RM-REGISTERED. It is capable of receiving voice or IMS calls from PLMN2.

[0203] (Management of registration timer for inactive SIMs) After the secondary SIM attach procedure is successfully completed, the UE changes the EMM state to EMM -INACTIVE (or the "inactive registration" subtype of EMM-REGISTERED) The corresponding PLMN periodically updates the registration timer to keep the To do this, the UE may need to notify the inactivity registration timer update request. It disconnects from the active PLMN and connects to the secondary PLMN to perform the request. Instead, the registration timer on the secondary PLMN is updated through the active PLMN. The UE can perform a single registration timer update request. This is shown in Figure 30 for the two SIM case, where the active PLMN and the secondary An enhanced TAU request could be used, combining updating of the registration timers in both the remote PLMN and the remote PLMN. As a result, the UE is not required to update the registration timer due to activity on an active PLMN. If there is a separate Inactivity Registration Timer Update (IRTU) request to the secondary PLMN, The procedure shown in FIG. 30 is the same as that shown in FIG. Note that the procedures are for 5G systems and may also be applied to 5G systems. .

[0204] Step S3002: The UE receives a registration type maintained in PLMN1 for SIM1. The MME of PLMN1 sends a TAU request to the MME of PLMN1 to update the A temporary identifier assigned to SIM1 by the PLMN A temporary identifier assigned to SIM2 by SIM1 and other parameters of the TAU request This may include a registration request to the MME of PLMN1 for SIM1 in PLMN1. It also updates the recording timer, as well as forwards the IRTU request to PLMN2 for SIM2. As mentioned above, the multi-SIM indicator also indicates preferred network behavior, etc. Note that the parameters may be integrated into the existing parameters of Step S3004: The MME of PLMN1 performs a TAU request for SIM1, and HSS1 3002 can also assign a new temporary identity to the UE in this slot. can be included in the step. Step S3006: Further, the MME of PLMN1 updates the registration timer of SIM2. The MME of PLMN2 sends an IRTU request to the MME of PLMN2 to The multi-SIM indicator and temporary identifier assigned to SIM2 by N2 Also, the MME of PLMN1 provides location information of the last visited TAI parameter. The UE's location can be communicated via the LTE link, allowing the PLMN2 to track the UE. Note that the IRTU request may be implemented as a TAU request, It may be a standalone request. Step S3008: The MME of PLMN2 performs an IRTU request for SIM2. In step S3006, update the UE context for SIM2 using the information provided. Renew. Step S3010: An IRTU acceptance response with the status of the request is received from the MME of PLMN1. and a new temporary identifier, such as GUTI, may be assigned to the UE for SIM2. Other location-dependent information such as new timer values ​​and updated TAI lists may also be provided. In 5GS, new UE policies can be provided in the response to the UE. PLMN2 also , the registration status of SIM2 is no longer valid and the UE needs to re-register with PLMN2. This information can only be decoded by the UE. The encrypted NAS container may be provided as follows: Step S3012: The MME of PLMN1 sends the TAU accept message to the IRTU accept message. The response is returned to the UE in an encrypted form with the information returned from PLMN2. The NAS container may include a Step S3014: A new temporary identifier is assigned to either SIM1 or SIM2. If so, the UE sends a TAU with an IRTU complete message to the MME of PLMN1. return. Step S3016: If a new temporary identifier is assigned to SIM2, the PLMN The MME of PLMN 1 forwards the IRTU completion message received from the UE to the MME of PLMN 2. do.

[0205] (Providing cell measurements taken from a SIM switching procedure) When the UE attempts to perform a SIM switching procedure in an inactive PLMN, In some cases, it may not be possible to establish a connection with a cell of an inactive PLMN. The cell may be overloaded or the UE may experience coverage holes in inactive PLMNs. In these cases, the UE may be in an area where the cellular coverage is improved. Drive tests through active PLMNs to inactive PLMNs may be used The present invention may proactively provide measurements found in a Minimization of Disturbance (MDT) report. The measurements are further transmitted to the NWDAF of the inactive PLMN for analysis. FIG. 31 shows a case where the SIM switching procedure for connecting to PLMN2 fails and the UE Reconnect to PLMN1 and provide cell measurements and cause codes that are forwarded to PLMN2 The transfer of cell measurements and cause codes is intended to allow the UE to further process the page. It is possible to signal that a

[0206] Step S3102: After receiving the page or NAS notification, the UE The UE performs a SIM switching procedure to disconnect and then attempts to connect to PLMN2. ,collect cell measurements while performing cell selection to attempt to connect to PLMN2; These measurements are then stored and distributed to the various cells belonging to PLMN2. This information may be provided to PLMN2 at some point in the future to help characterize the signal strength of the do. Step S3104: The UE attempts to connect to a cell belonging to PLMN2, but Connections often fail because the cell is overloaded, making it difficult for the cell to maintain a connection. has a relatively low signal power to provide coverage to the UE or there is a nearby cell that provides coverage to the UE. At the same time, the UE collects cell measurements during this process and the UE The cause code for why the UE failed to connect to the cell is provided by the RAN2 node 906. If no cell is available, the UE shall use a cause code to indicate this. The failure may originate from the MME and the corresponding cause code may be configured in the MME Note that the UE may also receive the ACK signal from the Step S3106: The UE cannot connect to a cell belonging to PLMN2 and belongs to PLMN1. Reconnect to the cell that is connected. Step S3108: The UE then sends a SIM switching request to the MME of PLMN1. and provides cell measurements collected for cells in PLMN2. These measurements are It may be provided in an encrypted NAS container so that only the LMN2 can decrypt it. A command to inform the MME of PLMN1 that there is data to be transferred to the MME of MN2. The cause code may also be provided to indicate that the UE is unable to connect to a cell belonging to PLMN2. This cause code may be provided as the reason why the UE attempted to complete the processing of a page request. Informs PLMN2 that it has attempted to establish a connection with a PLMN2 cell but was unable to do so In addition, in step S2806 of FIG. 28, The identifier provided by PLMN2 allows the UE to retrieve the data belonging to this page. This may be included to inform PLMN2 that it was unable to Step S3110: The MME of PLMN1 processes the SIM switching request and switches SIM1 Re-enable the UE context stored in the MME and update the EMM state to EMM-REGIST ERED (or set to "inactive registration" substate in EMM-REGISTERED state) disable the active state or mode) and deactivate paging request forwarding for SIM1. do. Step S3112: The MME of PLMN1 performs the step S3112 of FIG. 28 associated with the page. The encrypted NA received from the UE using the cause code and identifier received in step S2806. This step is conditional and requires that the UE This is only done if you have previously performed an indirect attach of SIM2 with PLMN2. Step S3114: Status of SIM switching with PLMN1 for SIM1 A response is returned to the UE indicating the transfer of cell measurements and cause codes to PLMN2. The status of the transmission may be indicated.

[0207] (Interworking with multi-SIM UE) Multi-SIM UE supports connection to both LTE and 5GS networks. The enhancements proposed herein support the LTE-5G and 5G-5G It is recognized that it may be applied in interworking scenarios involving UE switching back to LTE. Figure 32 shows how the N26 interface connects the MME in LTE to the 5G Non-roaming interworking between 5GS and EPS connecting with AMF in The HSS+UDM3204 also has the S6a and S6b interfaces. These interfaces are connected to the MME and AMF via N8. To support the attach procedure and paging request forwarding functionality proposed in this specification It can be used.

[0208] (Impact of Multi-SIM on 5G UE Policy) Currently, the UE policy stored in the UE is determined by the UE's access network and user rules. Includes ANDSP and URSP policies to assist in making port selection decisions, respectively. UE policies are communicated to the UE by the PCF via AMF and NAS messaging. To support multi-SIM UEs, a new policy is added to the UE policy. It is proposed to introduce a one-way or multi-SIM policy. The proposed policy defines the behavior of UEs with multi-SIM capabilities. An example of an IM policy is shown in Table 4.

[0209] [Table 4]

[0210] Some of the multi-SIM policy information may be pre-provisioned in the UE or or may be determined by the UE or configured by the user via a GUI; The UE may obtain the IEEE 802.11b protocol from the core network, or a combination thereof. A new multi-SIM policy may be added manually by the user or by the installation Then, as shown in Figure 17, A list of multi-SIM policies can be presented in the GUI, such as:

[0211] Alternatively, the multi-SIM policy may allow the UE to register with the core network after successfully registering with the PLMN. The multi-SIM policy that the PCF sends to the UE may be created by the P In other words, the PCF of each PLMN with which the UE communicates may be A multi-SIM policy can then be sent to the UE when it registers with another PLMN. Then, the new multi-SIM policy is added to the UE’s policy, and the GUI shown in Figure 17 appears. It is possible to summarize all PLMNs to which the UE is registered. The user can then Manually assign priorities to PLMNs and other parameters associated with those PLMNs The receipt of the new multi-SIM policy may be configured as described above in this disclosure. , the UE may be triggered to attempt a partial or indirect registration procedure.

[0212] The UE may provide a wireless The UE's radio capabilities can be provided to the core network. Therefore, the core network uses the Paging Request Header to ensure that the UE can receive the Paging Request. The paging strategy used can be adjusted to simultaneously The UE can also minimize the use of resources for one SIM at a time. downlink signaling can only be received for one SIM at a time. Single Rx indicating that it is capable of sending uplink signaling to the network , single Tx capability. UE with dual Rx, single Tx capability can receive downlink signaling from up to two SIMs at a time, Uplink signaling can only be sent to one SIM at a time. The network assigns a multi-SIM policy to the UE based on the radio capabilities of the UE during registration. This allows for consistent network provisioning for multi-SIM UEs. This helps ensure optimal network performance and allows the network to manage paging resources more efficiently. For example, the network can obtain UE paging area information for a particular SIM. By transmitting paging information, it is possible to adapt the paging occasions of single-Rx UEs. Upon receiving the paging area information, the UE may determine whether a potential paging collision exists. Compare the received paging area with the paging areas of another SIM to determine if If there is a potential paging collision, the UE The SIM may request another paging occasion from the network.

[0213] Instead of the UE radio capabilities being included as part of the multi-SIM policy, they are provided to the UE during registration. This may be a separate indicator provided to the core network accordingly. The presence of this data allows the core network to allocate paging opportunities based on the UE's radio performance. For dual Rx capable UEs, the core network A temporary identifier associated with a random paging occasion may be assigned. Single Rx Support For the UE, the core network will handle paging for different SIMs to avoid paging collisions. To adapt the SIM support opportunities, the Multi-SIM Support Information may be used as described below. This can be done.

[0214] Within the multi-SIM policy, the service prioritization list is Depending on the user, which is the primary SIM and which type of service has higher priority and whether the network should page the UE and which type of service is more The UE has a high priority and the network should not page the UE or the UE is Time periods when traffic from IM should be prioritized, multi-SIM traffic such as location information The multi-SIM support information may be configured to indicate a priority of the service. Network optimization for multi-SIM UEs using user preferences from a list Further information to assist the core network in ways to enhance or optimize network operations. The assistance information provides information about which traffic is important to the UE and therefore which traffic is not important to the UE and which traffic is not important to the UE should be ignored by the network by not sending a paging message or to avoid paging collisions. How a network can assign new temporary identifiers to avoid , and which parameters to use when assigning new parameters, Specifies the time for which filtering of paging requests by network is enabled. The core network can be notified.

[0215] The information presented in the service prioritization list is based on the service type information of the paging request. This may be used to assist the UE in making a decision on what to do upon receipt of the service notification. Service type information includes voice calls, SMS messages, other data, control plane signaling, High level information such as emergency message, emergency callback, and mobile termination exception data The UE shall determine whether the service type provided in the paging request is a service A check can be made to see if it matches the service type in the prioritization list. If there is a match, the UE performs a SIM switching procedure to retrieve the data associated with the page. However, the server may decide to retrieve the subpage provided in the paging request. If the service type is not found in the service prioritization list, the UE assumes that it is currently busy. It can respond to a page that says "there is a request" and also enables paging request filtering. This can be done.

[0216] In some cases, the UE may need to know what the page is for in order to make a better decision. For example, calls from family and close friends can be sent via telematics. This is more interesting to users than a call from a marketing rep or a robot caller. Therefore, the prioritization level information can be included in the service prioritization list to determine the services of interest to the user. This information can be used to specify a finer granularity of services with multiple The number of SIMs may be provided by user configuration via the GUI during initial installation. Users can group users such as family, friends, colleagues, acquaintances, and contractors, and then assign them to specific groups. A priority can be assigned to only a group, for example, family and friends. The loops can be organized into priority levels as numbers: level 1, 2, 3, etc.

[0217] The service prioritization list determines whether a page is important to the user. In order to be able to determine the service type category and service The service type category can include both voice calls, SMS messages, other data, control plane signaling, emergency signaling, emergency control It may consist of callbacks, mobile terminated exception data, etc. Different types of service may have different For example, calls from the user's family and friends or from the user's Whether the call is from a contact or from a source that is not your contact Levels 1 and 2 assigned to voice calls and SMS messages to specify whether There may be levels 1, 2, 3, etc. Similarly, other data and control processes for the UE may be Lane signalling, as well as other indications to describe emergency signalling. There may be high and low levels associated with the emergency callback and mobile termination exceptions. There may be one level, as in the case of data. This may refer to a case where the access network has important data for the UE.

[0218] [Table 5]

[0219] As mentioned above, the service type category and the service prioritization level are may be included in the received paging message. The UE may Use a ranked list and use service type categories and prioritization levels Determining whether the data associated with a page is of interest to the user This can help the UE decide how to respond to the page. For example, determines that the data associated with the page is important to the user and Conversely, the UE may decide to perform the procedure if the data is not available to the user. It is not that important and the UE is busy or unreachable. In other cases, the UE can notify the MN of the service type and Presents the user with task and prioritization level information and lets the user decide how to proceed. It is possible to do so.

[0220] Some of the service prioritization levels prioritize voice calls and SMS messages. Some information, such as the ranking level, may not be readily available to the network prior to UE registration. These levels of people with contacts can be accessed by the UE through the application server after UE registration. E may be provided to the network by the user, which can be different as shown in Table 5. A protocol exposed to application servers to allow configuration of priority levels. Alternatively, the user may tag the service with the appropriate level. This information can be dynamically updated during the service request procedure or via the user plane by For example, the GUI may provide a preference for associating a telephone number with a telephone number after a voice call. The UE may then display the indicated priority level of the voice call to the user. The level can be signaled to the core network via the user plane.

[0221] When the user configures the service prioritization list, the UE will Multi-SIM support for multi-SIM policies provided to the core network Multi-SIM support information can be derived from network and paging information. To minimize resource waste, the UE is provided with a service to filter pages. A set of service types and priorities can be provided to the core network. , Other information of the multi-SIM support information is, in order to better avoid paging collision, Provides for requesting different paging opportunities to be monitored among installed SIMs. The assistance information may be configured by a network policy that is sent to the UE. and will be explained in more detail below.

[0222] The multi-SIM support information is provided initially during registration or when the UE notifies the core network of such Whenever it detects the need to notify the core network of necessary information, For example, if a user of a UE uses a particular SIM card for a certain period of time, such as an important voice call, When requesting to use a particular service, the UE shall notify the master in a service request or registration update request. The support information can then be sent to the core network. This is used to filter out pages of services that are not of interest to the user. In this way, the UE can be paged only for the more important services. After the user ends the voice call, the UE shall delete or invalidate the assistance information and transmit it to the core network. The service may enable the call to page the UE for all services.

[0223] Figure 41 illustrates how a multi-SIM UE can configure the UE for multi-SIM operation. How to provide user configuration with preferences for how they want the core network to operate Here is an example of how to provide the SIM card after installing multiple SIMs in the UE and powering on the UE. The GUI prompts the user to configure preferences for the UE to follow. Upon completing the configuration, the UE performs registration for each of the SIMs installed in the UE. Figure 41 shows the registration of one of the SIMs and the user configuration is in the form of a multi-SIM policy. This shows how the data is sent to the network.

[0224] Step S4102: A user installs multiple SIMs in a UE, and upon power-on, The UE prompts the user via the GUI to configure information for multi-SIM operation. The information provided by the user determines how the UE manages multi-SIM operation on the UE. These preferences can be used to specify the user's preferences for The references are incorporated into the service prioritization list for the multi-SIM policy shown in Table 4. The UE then adds the user preferences to the multi-SIM policy. , and provide that policy to the CN to enable enhanced handling of multi-SIM traffic. In addition, the UE may use the SIM identity to derive the multi-SIM policy. Identifier, PLMN ID and name, UE radio capabilities, maximum number of SIMs, and PLMN link The information that can be accessed can be provided to websites, etc. Step S4104: After the user configures the service prioritization list, the UE Table 4 contains information about multi-SIM support including multi-SIM indicators and user configuration. The RAN node sends a registration request to the RAN node using the multi-SIM policy shown in Multi-user to be able to read the instructions and information and take them into account during AMF selection The multi-SIM indicator and multi-SIM support information should also be included in the access stratum message. can be done. Step S4106: Then, the RAN node performs the following based on the presence of the multi-SIM indicator: Based on this, the AMF that supports the multi-SIM UE is selected. Step S4108: The RAN node transmits the registration request to the multi-SIM indicator, the multi-SIM The selected AM along with the SIM support information and the remaining information elements of the multi-SIM policy Transfer to F. Step S4110: The AMF performs UE registration and authentication according to TS 23.502 [2]. During this process, the AMF and PCF provide additional information to the Multi-SIM Policy The AMF can provide temporary network identifier(s) and registration The timer value can be provided and the PCF can determine whether the network supports dual RM-REGIST It can provide whether ERED operation is supported. Dual RM-REGI STERED support allows the network to link together multiple SIMs from a UE. It is shown that this can provide optimization for multi-SIM operation. For example, the network can If the UE requests such a change, it shall temporarily Support may also be provided for the reassignment of a general UE identifier as described in this disclosure. So, you can paging from one SIM to another SIM and other multi-SIM enhanced paging opportunities. The method may include forwarding a request for a link. Step S4112: The AMF returns a registration acceptance response to the UE and Includes updates to the multi-SIM policy that was introduced Step S4114: The UE receives the updated multi-SI from step S4112. The UE updates the multi-SIM configuration internally based on the M policy. Presents the policy to the user through a GUI that shows all updates to the policy and The user may be prompted to review the policy. Step S4116: If the user is prompted and confirms the multi-SIM policy, the UE registers The UE can return a registration completion message to the AMF based on the paging occasion of each SIM. If the UE detects a possibility of paging collision between multiple SIMs based on the Return the indication of the record completion message, and use different paging mechanisms to avoid paging collisions. The AMF may request that a new temporary identifier be assigned to the meeting. E shall use the following additional methods to assist the AMF in allocating new temporary identifiers: Multi-SIM support information can be provided.

[0225] The inclusion of a multi-SIM policy means that it can be used for initial registration, periodic registration renewal, partial registration, indirect Note that this may be provided during any of the registration procedures, whether registration, etc. Multi-SIM support when the entire SIM policy cannot be provided to the network The components of the multi-SIM policy, such as the SIM-ID information, may be provided separately to the core network. In addition, whenever a UE wishes to request special handling of multi-SIM traffic, can also signal multi-SIM support information to the core network. ,Multi-SIM support information in a service request or PDU session establishment or modification procedure The multi-SIM support information may include adding a To inform the core network how to filter paging requests during For this purpose, it may be provided during the SIM switching procedure.

[0226] In LTE, multi-SIM support information is maintained in both the UE and the MME. It can be realized as text information. Table 6 shows the service prioritization list and the multi-S Adding IM support information to the UE's internal information storage as a UE context. This information is stored in the attack database when the UE first registers with the core network. may be included in the filtering procedure or to dynamically enable paging request filtering. Similarly, the MME may provide assistance information to each multi-hop The SIM can be stored in the mobility management context of the UE. Some of the multi-SIM support information may also be stored in the HSS.

[0227] [Table 6-1] [Table 6-2]

[0228] (Multi-SIM UE support for MNOs without coordination) The solutions previously described in this disclosure address paging collisions occurring across two or more SIMs. The solution requires some coordination between MNOs. In some deployments, MNOs There may not be any coordination between the AMFs or MMEs of different MNOs, for example. For these cases, there is no signaling between the network functions of different MNOs. Other solutions to address the paging collision problem faced by multi-SIM UEs include: However, some aspects of the above-described solution are considered in the following Note that this may be applicable in the absence of NO coordination. For example, paging occasions A core network solution for assigning temporary identifiers to multiple SIMs of a UE with aligned SIMs The resolution still applies. This means that the multi-SIM indicator presented below will be This will be detailed when it is introduced. The solution described below is also applicable in the presence of MNO coordination. As an example, in the registration procedure when there is MNO coordination, A paging criterion may be used. The paging criterion is the criterion for determining whether a paging request is forwarded. Used by the core network to decide whether to page the UE after Finally, the following solutions are described for 5GS, but they are not applicable to networks. It may also be applicable to LTE systems with related changes in call entities, procedure names, etc. It is expected that...

[0229] Even in the absence of coordination between MNOs, if a UE communicates with a current MNO and then with another MNO, To avoid network performance degradation when switching communication between the It is still advantageous for the network to recognize multi-SIM UEs. The work operations are based on timers and algorithms that depend on knowledge of the UE state to operate efficiently. cadence-based, when the network does not know what the UE is doing However, these timers and algorithms may not function as intended, resulting in degraded network performance. Therefore, a multi-SIM UE can register with the network and temporarily When the UE decides to switch to another MNO, e.g. Sometimes it is equally important to inform the network of its capabilities. Temporarily unavailable means that the UE is planning to switch to another MNO and the page This refers to the fact that the UE is no longer able to monitor the current Temporarily unavailable until you return to the MNO. The following solution is for those who do not have MNO adjustments How can it address the scenario and help the UE to minimize the occurrence of paging collisions? A particular aspect of the solution is that both SIMs belong to the same MNO. Another aspect that can be applied in the case of a single MNO is the dual Rx, single Tx U Note that the same can be applied to E.

[0230] (UE registration and multi-SIM support information) The UE registration procedure to the core network allows the UE to receive services that require registration. To achieve this, specific parameters are configured between the UE and the CN. There are several variations in the registration procedure, from registration renewal, periodic registration renewal, and emergency registration. These procedures configure the parameters that both the UE and the CN use to communicate with each other. For example, the DRX parameters are used to provide the CN with information to configure the DRX when the UE receives a paging request. It is on for a period of time to monitor for requests and does some other things to help preserve battery power. This helps define a discontinuous receive cycle in which the receive signal is off for a period of time.

[0231] The UE provides information to the core network to assist in avoiding paging collisions. Certain additional parameters are proposed to be added to the registration procedure so that The new parameters are summarized in the following list, grouped together, for multi-SIM Multi-SIM assistance information is sometimes called assistance information, especially when the UE is in the registration suspended state. The paging is optimized to minimize waste of network and paging resources when By adjusting its routing strategy, the core network can better handle multi-SIM traffic. This information may be provided to the core network during the registration procedure to allow for better processing. . Paging Criteria: When a condition or event is met for paging, the network Criteria that specify the specific conditions under which the network will page the UE. Deriving paging criteria based on user configurations found in the service prioritization list. The paging criteria can be selected from a list of service type categories and priority levels. The UE may select a reference network to use when attempting to page the UE. This criterion applies when the UE provides service to another SIM. It is possible that the PO is not being actively monitored because the PO is connected to another MNO for Trigger the CN to filter the transmission of certain pages to the UE for a certain period of time. For example, the above-mentioned service categories may be provided according to which paging request is sent. Used for paging criteria that the UE configures the network to filter whether User phone number, PDU session ID, and application ID, etc. If additional information is provided, the filter can be made finer. Examples include, for example, the associated A call with a phone number, a text message, or a PDU session associated with a user Other data associated with your application ID or application ID (e.g. internet Alternatively, the additional information may include a service type The criteria are different for different service categories. Combinations, such as calls from family, texts from family and best friends, and and other data (e.g. internet data) from a specific PDU session ID. Based on these criteria, the core network may paging the UE only when the link data meets one or more of these criteria; This saves paging resources for data that is not of interest to the user. The paging criteria include the time period, location information, and the time when paging request filtering is applicable. This may include criteria such as the UE status, and other information. Restricted paging area: The UE is connected to another MNO and cannot respond to pages. Restricts the paging area to which the CN sends paging messages if the The parameter specifies the number of UEs that the network can request to be added to the last tracking It can be specified that the UE is only paged within its registration area or its trace area. The meter specifies how many times the network will attempt to page the UE before giving up on the pages. This can even be used to identify networks that are outside the UE's current tracking or registration area. This can help reduce the waste of paging resources in the cell. Upon receiving a mobile registration update including May be provided to indicate that the UE may switch the connection to another MNO. Paging Occasion Separation: The UE provides this parameter to determine the likelihood of potential paging collisions. Based on the detection, the location when the UE requests a new temporary identity (and associated PO). The UE can configure the desired PO separation. The UE can determine whether the associated POs are at a certain distance in time, e.g. For example, based on the number of paging frames, slots, etc. from the currently allocated PO. This packet is used to request the network to provide a new temporary identifier for a short period of time. parameters can be provided or the parameters are used to assign temporary identifiers. To give flexibility to the network, A request for a "different" paging occasion can be expressed as an enumeration of descriptions such as "is different from the paging occasion" and "is different from the paging occasion" in the , may be an indication of a desire for paging occasions to occur at the same period but at different times. Therefore, this may be an indication that a different offset is desired. - Number of missed pages before notification: The value is the number of pages that the CN should wait before notifying the UE. The UE determines the threshold for the number of times that it detects that the UE is a multi-SIM device. This value can be configured during initial registration to inform the CN that it is also an Therefore, values ​​can be set through operator policies or by operator behavior and management applications. It may be operator configured through commands received from the application. Multi-SIM indicator: The UE also displays a multi-SIM indicator similar to the one described above. However, in this case the resulting functionality may be different. In this scenario, the multi-SIM indicator indicates that the CN should and provisioning the UE with a new temporary identifier that meets those criteria. If both SIMs belong to the same MNO, the registration request can be Supports IM and possibly specific network optimizations for multiple SIM registrations To inform the core network that it provides the IMSI or other The multi-SIM indicator and the other SIM With this identifier, the core network assigns a temporary identifier for the current SIM. The paging opportunity may be the same as that of the other SIM, as described above. Therefore, the paging occasions of both SIMs in the UE are aligned. and the UE only needs to monitor one paging occasion. Proposed temporary identifier: UE avoids paging collision with PO of another SIM This parameter can then be used to propose a temporary identifier. The UE may then receive a temporary identity whose paging occasion matches the paging occasion of another SIM of the UE. Alternatively, the UE may propose a child by using a part of the temporary identifier (e.g., The network may propose a temporary identifier (a portion of the ID used to calculate the The remainder may be assigned.

[0232] The UE provides these parameters during initial registration and the CN generates a specific configuration. Similarly, the UE can initialize the parameters used when The UE determines that a potential paging collision exists between the UE and the CN and receives a new temporary identifier from the CN. (and associated PO), then these parameters are passed to the Mobility This can also be included within the registration update or periodic registration update procedure. It shows that the CN provides the specified parameters to the CN, but the parameters are not, for example, It is understood that the data policy may be configured by the CN. CN has requested a new temporary identifier and associated PO using the Security Registration Renewal Procedure. The terms PLMN1 and PLMN2 are used to represent UEs that are in communication with each other, for consistency with other figures in this disclosure. Note that the term is used to represent MNOs that are not coordinated in this way.

[0233] Step S3402: The multi-SIM UE first registers to PLMN1 and The UE then receives the temporary identifier, possibly after disconnecting from PLMN1. The UE registers with LMN2. The UE receives a temporary identifier for SIM2. Step S3404: The UE calculates a paging occasion associated with each SIM. Based on the timing information that the UE has for each PLMN, The UE detects that a paging collision may exist, as shown in Figure 35. Although the timing relationship between the two is asynchronous, the UE must use two It is possible to detect paging collisions by overlapping two timing references together. FIG. 35 shows that even if the superframe timing is not aligned, There is no overlap between paging frames associated with the PLMN and these paging occasions. POs do not necessarily need to overlap to cause paging collisions. Note that if the POs are close enough to each other, the UE can transfer data from one PLMN to another. It may also cause paging collisions because there is not enough time to switch the connection to N. Each time E needs to perform this action, there is a certain latency associated with the step. For example, the UE tunes its radio to the appropriate frequency, performs cell search, PLMN selection, etc. Must. Step S3406: When the UE detects that there is a possibility of a paging collision, then The UE shall send another temporary identifier to the PLMN, which will generate a paging occasion different from the current one. The UE can request one of the following: The proposed parameters may include those listed above. The UE may also Use semi-parameters to allow for certain data such as voice calls and SMS messages In addition, the UE may be configured to track other In order to minimize the waste of paging resources in the registration area, the paging area is , the CN may be configured to restrict the UE to the last tracking or registration area in which it made contact with the CN. The UE may also have the CN provide a new temporary identifier corresponding to another PO, or To have the PO position propose a new temporary identifier that is different from the current PO, multi-SI The UE may include only the M indicator. or information provided in a previous registration acceptance message, such as information provided in a multi-SIM policy By receiving a message or reading the system information, the CN has enabled the multi-SIM feature. It may have been discovered that it supports Step S3408: The AMF sends a registration acceptance message that may include a new temporary identifier. The new temporary identifier may correspond to a different PO at a different position than the previous PO. The UE must time the new PO to ensure that there is no possibility of paging collision. If the UE still detects a paging collision, it checks the timing with the PO of another SIM. If so, the UE repeats step S3406 to obtain another temporary identifier. This time, the UE can use a temporary PO with a different PO that does not cause a paging collision. It may use different values ​​of previously transmitted parameters to attempt to obtain the identifier. Alternatively, the UE may decide to use the PO in another PLMN to avoid paging collisions. A temporary identifier may be proposed.

[0234] The paging criteria determines whether the UE should be paged when the UE activates the registration pause timer. One of the registration steps is to configure the CN to filter when This criterion may be provided by the UE, as will be described in more detail later. During initial registration to statically configure the CN filtering paging request Mobility or periodic registration to dynamically configure the CN of the UE's preferences Alternatively, the criterion may be sent during an update procedure. In a service request, the UE notifies the network when it wants to stop paging the UE for a certain period of time. The criteria may be, for example, whether the UE should be paged when deciding to page the UE. A white or black list of service categories / prioritizations you want CN to filter Criteria may also include, for example, phone numbers, PDU session IDs, and application It can contain more detailed information than is included in the paging message, such as the application ID. .

[0235] The paging criteria is used in UEs with dual Rx, single Tx capability to The CN may page the UE for important data that the UE may want to page. This allows the UE to respond to pages that it may not be interested in. This can reduce the overhead imposed on the UE for In the case of human subscription use, the user can join the team of his / her boss and coworkers during the weekend. You may want to receive calls only from the server and no one else. The paging criteria are , before the start of the weekend to allow calls only from those people. Users can preempt incoming pages and set paging criteria to U for all traffic. You may want to configure E to not page.

[0236] (Request for multiple paging opportunities) The timing relationship between cells of different MNOs is asynchronous and can vary from cell to cell. Therefore, having a single PO will cause paging collisions in some cells but not in others. In these cases, the UE may receive multiple POs without causing paging collisions. The UE must be provisioned with a PO that does not collide with the PO of another SIM. In this case, the UE may prefer to use a per-MNO internal timing scheme. Based on this, it can dynamically determine which of multiple POs will listen for paging requests. Option used if single PO case still results in paging collisions It can be done.

[0237] To request multiple paging occasions, the UE may request a mobility registration update or a periodic A multi-PO indication can be included in one of the registration requests, such as a registration renewal procedure. The desired number of temporary identifiers to be assigned to the UE, or simply the number of temporary identifiers that the UE requires. The UE may specify a flag requesting a number of temporary identifiers to be provided to the core network. The UE can switch to a different PO if the core network supports the desired PO characteristics. Any of the other parameters described herein may be used to assist in allocating temporary identifiers. For example, the paging opportunity separation parameter can be used to A desired separation between multiple POs can be indicated.

[0238] When the UE receives the temporary identifier associated with the PO, the UE can Therefore, the UE can easily move between cells and decide which PO to monitor based on the PO it has. When the UE moves and the PO of one of the SIMs shifts, the UE It can dynamically determine which of multiple POs to monitor for a given UE in response to a page. When the UE responds, the network stops paging the UE in other POs assigned to the UE. The UE may choose to use the 1000 Mbps ... For example, the UE may request multiple temporary identifiers from MNO1 and MNO2. Each UE requests two temporary identities from O2, and the UE receives four allocations regardless of mobility. In this case, the user may request a desired PO separation that can avoid paging collisions between the assigned POs.

[0239] The restricted paging area parameter is introduced by having multiple paging occasions. Multiple paging opportunities are used to offset the paging resource overhead incurred by As mentioned above, the restricted paging area parameter may be used with the request Restricting the area in which a UE is paged to the last known tracking or registration area of ​​the UE This parameter specifies how the CN will respond to the UE if the UE does not respond to the page. To limit paging escalation that can occur when paging a larger area, Since the UE has already requested multiple POs, the restricted paging area parameter By adding a meter, the UE can access the tracking or registration area where it last communicated with the CN. This allows the tracking overhead to be localized, thereby reducing the overhead associated with other tracking and registration areas. This can save paging resources.

[0240] (Simultaneous pages on the same paging occasion) SIMs belong to the same MNO and the CN assigns a temporary identifier to the SIM to correspond to the same PO. If assigned, data is available for both SIMs at the same time, and then the CN During these cases, the paging message page The UE identification record contains a UE identifier that matches the temporary identifier of each of the SIMs. The question arises as to which SIM's UE will complete the processing of the paging request.

[0241] The problem occurs when a UE responding to a paging request has PDU sessions corresponding to both SIMs. By allowing a list of application IDs to be included in the service request sent to the CN, To do this, the identifiers of the other SIMs as well as the different addresses can be easily New parameters are added to the service, including the list of PDU sessions that are activated. It is proposed that new parameters be included in the service request so as not to interfere with existing operations. may be added to the existing parameter list of the service request procedure. The service request returns information about one SIM using existing parameters and new parameters. Provides information about the second SIM with the new data. Multiple instances of this new parameter The inclusion of a 32-bit SIM card can be used to extend support to multiple SIMs. Multiple refers to three or more SIMs. The advantage of adding a new parameter to the service request procedure is ,The aim is to conserve paging resources, and a service ,request is related to two or more SIMs. Inform the CN to stop paging the UE for the attached data.

[0242] For a more integrated solution, the temporary identifier and the PDU session being activated should be The list of options may be combined together and the list of combinations is specified in the service request procedure. In this case, the new parameters can be thought of as a list of key-value pairs. The key part contains a temporary identifier associated with the SIM, and the value part contains the P This solution involves changing the structure of the message format. The list can be expanded to include as many SIMs as the UE supports without requiring So it is more scalable.

[0243] (Registration pause timer) The operation of a multi-SIM UE is to provide services to each SIM installed in the UE. To achieve this, the UE can be programmed to periodically switch its connection between PLMNs. Using this mode of operation as an example, the core network can A mechanism by which a CN can request the suspension of the registration timer it maintains for the state Instead of introducing a new registration state as above, it is proposed to support A registration pause timer may be introduced. The operation of the registration pause timer is For example, the UE may be in a state where the registration pause timer is activated. When a CN is requested to be booted, the registration timer maintained by the CN is paused. The UE performs a mobility registration update or a periodic registration update and activates the pause timer. This may occur when the UE includes a registration pause indicator to restart the UE. Dual operation mode with indicator to show which mode is currently in operation. The device may have a mode.

[0244] The UE shall use the LTE 2016 LTE 2016 LTE- ... A value may be provided to be used for the registration pause timer. This value is used in mobility registration updates or This value may be included in periodic registration updates to allow the CN to pause the registration timer. Upon receipt, the CN shall pause the registration timer and activate the registration pause timer. After some time, the UE can resume the registration pause timer and restart the inactive Figure 36 shows how to disable the registration pause timer and re-enable the registration timer. An example of this activation and deactivation procedure is given below.

[0245] Step S3602: The multi-SIM UE is registered in both PLMN1 and PLMN2. The UE is currently in active communication with PLMN1. Step S3604: The operation programming logic of the UE transfers the connection from PLMN 1 to PLMN The UE decides to switch to LMN2. The UE performs a mobility registration update or a periodic registration. The AMF of PLMN1 sends an update request to the AMF of PLMN1. This request is triggered by the registration pause timer may contain instructions to activate the registration pause timer or may contain an expiration of the registration pause timer. The value of the expiry time can be an operational parameter of the UE, maintained by the UE or defined in the core. Policy configured by the network or programmed by the user through the GUI The UE may also be configured in any other operational metric programmed. Queue any downlink data for the UE while the stop timer is running. CN may provide instructions to request that CN do so. Step S3606: Upon receiving the request, the AMF of PLMN1 pauses the registration timer. The AMF can stop the registration pause timer and activate the registration pause timer. If a registration pause timer is provided, the registration pause timer validity is set using the value provided by the UE. Alternatively, the AMF may require the core network operator to The AMF may use the value configured by the UE's registration state, security configuration, and All existing contexts in the UE, including the context text, and preservation of existing PDU sessions However, the activation of the registration pause timer The CN will not receive downlink data until the UE deactivates the registration pause timer. Do not page the UE for any registrations that are not registered with the CN while the registration pause timer is running. If it requests queue-up of downlink data and the CN is able to do so, the CN In step S3606a, the AMF provides this indication to the SMF to receive any existing Such functionality can be enabled by updating the PDU session. The SMF then buffers any downlink data destined for the UE, which is not shown in the figure. When a policy control request trigger is met, the SM F notifies the PCF of the satisfied conditions, as shown in step S3606b. The AF subscribes to be notified whenever the UE's registration state is suspended. This notification may not be sent to the UE until the suspension is deactivated. It is possible to prevent data that is not transmitted. Step S3608: The AMF sends a registration accept message to the UE, indicating the status of the request. Returns if the request is granted and if AMF has changed the registration pause timer expiry value. If so, AMF includes the new value in the acceptance response. AMF also checks whether the registration pause timer is running. When the CN is queuing up downlink data, the UE's request is accepted. The UE may provide an indication of whether the CN has initiated the deregistration procedure. To keep track of the remaining time that the UE has before, the value returned by the AMF or the value originally provided In other words, the UE starts a timer incorporating the provided value until the UE's registration state is The UE must notify the CN before the retention timer expires so that the UE remains M-REGISTERED. Registration Pause Timer that is maintained must be deactivated. When the UE is active, its registration state is RM-REGISTERED and the connection The UE remains in CM-IDLE state. However, the CN may not page the UE during this time. do not have. Step S3610: The UE disconnects from the PLMN 1 and connects to the PLMN 2. Upon connecting to N2, the UE performs either a mobility registration update or a periodic registration update. to deactivate the Registration Pause timer maintained by the AMF in PLMN2. In the request, the UE may either deactivate the registration pause timer or may include an instruction to set the expiration value to zero. Then, the AMF of PLMN2 , disable the registration pause timer, and re-enable the registration timer. is reset at this point instead of continuing from its previous value when it was paused. If the UE has previously requested the CN to queue up downlink data, The UE receives the data when the user requests a service. maintains a connection with PLMN2 for as long as it requires it to use the services associated with If the UE is in CM-IDLE state when the operational timer expires, the UE It may decide to disconnect from PLMN2 and reconnect to PLMN1. Step S3612: If the UE decides to reconnect to the PLMN1, the UE To deactivate the registration pause timer and re-enable the registration timer, the mobility The UE sends either a registration update or a periodic registration update request to the PLMN1. The expiration time of the registration pause timer must be exceeded in order to trigger the deactivation of the pause timer. An indication or a zero value may be provided. Step S3614: The AMF of PLMN1 deactivates the registration pause timer. The registration timer is then re-enabled. The registration timer expires when the registration timer is paused in step S3606. It may be reset at this point rather than continuing from the previous value when it was stopped. Step S3616: As in step S3608, the AMF of the PLMN1 receives an update request If the request in step S3612 is a service request, the registration acceptance response is returned with the status. If so, the UE can start receiving the queued downlink data. Otherwise, the UE will notify the queued downlink data after this step. A service request can be performed to receive the data. Step S3618: The UE is busy in processing data associated with the PDU session. or the UE may be in a call that remains connected to PLMN2. During these cases, the UE shall not attempt to In these cases, the A of PLMN1 may remain in step S3610 for a long time. The MF may deregister the UE for SIM1.

[0246] As part of the procedure to pause the registration timer, the CN shall also pause paging for the UE. During this suspension period, mobile terminated data for the UE can be buffered. During this time, the CN notices that the UE is not actively listening for paging requests and As a result, the AMF queues up the paging request, as shown in step S3606a of FIG. Instruct the UPF to buffer the mobile terminated data in the UE as shown in NAS signaling and P All security contexts established for a DU session are protected by the UE's CM- The CN and the UE are stored as if they were in the IDLE state. The RM-REGISTERED and CM-IDLE states are maintained for this pause. The INACTIVE state is similar to the RRC_INACTIVE state, but the UE registration and connection management states are Therefore, the UE and CN must be aware of the SIM associated with which the UE is registered. This behavior occurs when the UE is in a registered state and then quickly re-establishes communication after switching to a registered state. When requesting activation of the stop timer, the paging criteria parameters described above shall be included. This can be triggered by

[0247] (UE request to stop paging) In some cases, the UE may be busy using the services of one SIM and then may need to switch to another. A paging message may be sent to a SIM that is not connected to the SIM. The service that triggered the page may be displayed. Instead of allowing the paging to continue, the UE responds to the page with a service request message. In this case, the UE may inform the network that it is busy and stop paging the UE. The service request message is used, for example, to request which service the UE is currently using in another system. What services the UE is running on this current system (e.g. emergency services) Which service the UE is trying to respond to on the current system and the network pages the UE again for the same type of service. It may also include an indication of a timer value to indicate to the network when attempting to The UE receives a NAS notification containing an indication that the UE should respond to the page and the paging cause. When E receives it, the UE checks which services the UE is currently running on other systems ( For example, emergency services), which service the UE is trying to respond to on this current system. which services the UE is not responding to on the current system, and The network will page or notify the UE again for the same type of service. It responds with a NAS Notify response that includes an indication of the timer value to indicate to the network when attempting to transmit. The UE can inform the network of the paging resource. This saves on overhead and the network does not signal to the data source that the UE is busy. For example, a voice call may be nulled instead of attempting to page the UE. In the IoT use case, the information provided to the CN reaches the UE. Update the UE's reachability status on the application server it is trying to reach It can be used for:

[0248] This feature is useful when the UE has dual Rx and single Tx capabilities. As shown in FIG. 37, the UE is in a call with SIM1 and receives a page from SIM2. The UE can send a request to the network of SIM2 to receive the page of the UE. In this case, the UE can inform the network to stop receiving the The UE may be actively receiving downlink data on one of SIMs, and the UE may be There is a gap in the uplink transmission that allows a request message to be sent to the network. This feature allows the UE to have single Rx capability and single Tx capability, and time multiplexing between two SIMs on the same PLMN or between PLMNs of two SIMs. It may also be useful when the UEs can communicate with the same or different MNOs, Note that the procedure will be the same.

[0249] Step S3702: The multi-SIM UE is registered in both PLMN1 and PLMN2. The UE may be configured with dual Rx, single Tx capability or single Rx, single Tx capability. and time multiplexing between the PLMNs of each SIM. In this case, the UE may have dual Rx and has single Tx capability. Step S3704: The UE currently receives downlink data on Rx1 and transmits The system monitors the activity of the Step S3706: PLMN2 receives data for SIM2 and pages the UE Pages are served with service prioritization information that indicates what the page is for. It can include. Step S3708: The UE determines that the UE is busy receiving data from the PLMN1. To make this decision, the UE uses the paging message Checks the service types found in the message against a user-configured service prioritization list. For example, the UE may be in the middle of an important voice call and may need to be paged. The service type of the incoming text message indicates an incoming text message. Configuring the Service Prioritization List to indicate low priority for messages Alternatively, the UE may detect that an incoming text message is pending for SIM2. This is a GUI that indicates that the user has chosen to temporarily ignore the text message. The UE is receiving data on Rx1, so the UE is There may be gaps in time when no UL data is being transmitted on the group Tx. During the gap, the UE can connect to PLMN2, so that the UE can In the above embodiment, a request may be made to notify the AMF of PLMN2 to stop the dialing. Step S3710: When the connection to the PLMN2 is successful, the UE The mobility registration update request can be sent to the It may include instructions to activate or for the UE to activate the Registration Suspend to indicate to the AMF that the UE should temporarily suspend paging Alternatively, the indication may include a time for the CN to initiate paging of the UE. In a service request message with the time to stop and updated multi-SIM support information The UE may also notify the CN of the U- ... Queueing of any downlink data for E may be provided. Then, after the UE re-establishes communication with the CN, the UE can The link data can be extracted. Step S3712: The AMF of PLMN2 returns the status of the request in an acceptance response. As part of the response, the CN shall include the new value of the registration pause timer expiration, as well as the Can any downlink data be queued while the recording pause timer is running? The response may provide information about the status of the request and whether the CN has paged the UE. This may include the time to stop logging.

[0250] The above procedure shows that the UE registers with two PLMNs (or MNOs). This procedure can also be applied to the scenario where all SIMs in a UE belong to the same MNO. Instead of sending a capability registration update request or service request to another PLMN, the UE simply The UE operates in a similar manner, except that it sends the request to a single PLMN.

[0251] When the UE sends a request to the PLMN to stop paging the UE, the UE time to stop paging the UE, service type to page the UE, do not page the UE Informs the PLMN of the service type and whether the UE's data should be buffered. To achieve this, the UE may include multi-SIM support information in the request. Allows the PLMN to filter pages for the UE when it is busy These can be grouped together as additional information that the UE provides to the PLMN to The SIM assistance information may be organized as a policy that the UE provides to the PLMN or may be It is organized as a set of instructions that are sent to the PLMN in a service request or during a registration update request. This is also fine.

[0252] (The core network provides notification of missed pages to the UE) Whenever the core network pages the UE and the UE does not respond, the core network The network keeps track of the time that the UE misses a page and allows the UE to send a The UE can be informed when it will next connect via a 3GPP access, e.g. a non-3GPP access. This feature allows the UE to identify itself as a multi-SIM UE during one of the registration procedures. When the CN is notified or the UE receives information related to multi-SIM operation, such as multi-SIM support information, This can be enabled if one of the parameters described in this specification is enabled. N may be signalled to the UE in response to either the registration request or the service request procedure. The CN also records the time when the page was sent and when the UE did not respond to the page. Registration and / or tracking areas may be provided. Alternatively, the UE may have multiple access points. Access to the access technology, e.g. via 3GPP access and via non-3GPP access If supported, the CN shall provide access control for the UE in the CM-CONNECTED state. This information allows the UE to avoid paging collisions and and / or a problem with the paging process, and the UE is able to To help fix it, you may be able to utilize one of the solutions mentioned above. If the UE belongs to the same MNO and has dual Rx capability, single Tx capability, or single Please note that if you have group Rx capability and single Tx capability, the following procedures may apply: Please note. See FIG.

[0253] Step S3802: The multi-SIM UE is registered in both PLMN1 and PLMN2. If the two SIMs belong to the same MNO, the UE registers both SIMs to the same PLMN. do. Step S3804: The UE is currently receiving downlink data from the PLMN1. . Step S3806: PLMN2 receives data for SIM2 and pages the UE However, the UE does not receive the page because it has received data from PLMN1. or does not respond to the page, e.g. the user is on an important voice call and is interrupted The user may have received a prompt from the UE via the GUI. The UE has received a single Rx signal but has decided to ignore the prompt. It can operate in either single Tx performance, dual Rx performance or single Tx performance. Please note: Step S3808: After a period of time, the UE connects to PLMN2. Step S3810: The UE registers to start receiving services from the PLMN2. The procedure may perform either the registration procedure or the service request procedure. Step S3812: In response to the acceptance, the AMF of the PLMN2 The information on any of the missed pages can be provided to the UE. the time, the tracking and / or registration area from which the page was submitted, and, in some cases, , additional information about the page, such as the service category, as well as, for example, the caller's phone number Number or text message sender, PDU session ID, and / or application Alternatively, the UE may include other more detailed information such as a 3GPP Connecting to multiple access networks, such as 3GPP access and non-3GPP access When this is possible, the CN sends an indication that the UE may be in CM-CONNECTED state. The inform...

Claims

1. 1. An electronic device comprising: a receiver configured to receive a first subscriber identity module (SIM); a receiver configured to receive a second SIM; 1. A circuit comprising: receiving data from the first SIM; A request is sent to a first public land mobile network (PLMN) to transmit the signal to the first PLMN. and circuitry configured to register a child device, the request being received by the electronic Indicates that the device is a multi-SIM device, and the request includes multi-SIM support information. and the multi-SIM support information comprises: The electronic device notifies the first PLMN of its preferences.

2. The multi-SIM support information includes paging criteria, paging occasion separation, proposed temporary one or more of the following: a target identifier, a restricted paging area, and the number of pages missed before notification The electronic device of claim 1 .

3. The paging criteria may include service type category information or service prioritization level. The electronic device of claim 2 , comprising at least one of:

4. The service type category information may include voice calls, SMS messages, other data, control Plain signalling, emergency messages, emergency callbacks or mobile terminated exception data The electronic device of claim 3 comprising one or more of the following:

5. The other data may be internet data, application data, or protocol data.

5. The method of claim 4, further comprising: Electronic devices.

6. The service prioritization level may be a numerical level, a high or low level, or a level related to an emergency.

4. The electronic device of claim 3, comprising attached levels or a single level.

7. the separation of the paging occasions, the proposed temporary identifiers, the restricted paging area; or the number of pages missed before the notification is determined based on the network settings for multi-SIM operation.

3. The electronic device of claim 2, further comprising: a paging mechanism for enhancing a paging mechanism for the electronic device.

8. The user of the device determines how the device operates for the multi-SIM operation. The electronic device of claim 2 , further comprising:

9. The request is sent via a control plane or a user plane as described in claim 1 . Electronic devices.

10. The electronic device of claim 1 , wherein the electronic device is a user equipment (UE).

11. The electronic device is configured to send a second request to a second PLMN; The second request includes an identifier of the second SIM to be associated with the second PLMN. the first PLMN forwards the second request to the second PLMN; The electronic system of claim 1, wherein the second PLMN authenticates the credentials of the second SIM. device.

12. The electronic device may include in the second request a time period, a PDU session identifier, location information, instructions for buffering downlink data, and instructions for the electronic device to 12. The electronic device of claim 11, further comprising an indication that the electronic device is reachable via the surface plane. vinegar.

13. The circuitry receives a temporary ID for use in a paging request from a second PLMN. The electronic device of claim 11 configured to:

14. The circuitry is adapted to update a registration status of the electronic device with respect to the second PLMN. The electronic device of claim 13 configured as follows:

15. The second PLMN also receives a registration status of the electronic device with the second PLMN. The electronic device of claim 13 , further comprising:

16. The identifier of the second SIM is SUPI, IMSI, GUTI, 5G-S-TMS 12. The electronic device of claim 11 , comprising:

17. While the electronic device is actively registered with the first PLMN, The temporary ID for the device is always available whenever there is a page for the second SIM.

14. The electronic device of claim 13, wherein the electronic device is also used to page the electronic device. vinegar.

18. The request may be an initial registration request, a partial registration request, an indirect registration request, a registration update request, an initial attack request, or a combination of the above. The request may be a tracker attachment request, a partial attach request, an indirect attach request, or a tracking area update (TAU) request. The electronic device of claim 1 .

19. 1. A method performed by an electronic device, the method comprising: receiving data from a first subscriber identity module (SIM); A request is sent to a first public land mobile network (PLMN) to transmit the signal to the first PLMN. registering a child device, the request being made if the electronic device is a multi-SIM a multi-SIM device, the request including multi-SIM support information, and The SIM support information is used to configure the device's preferences for multi-SIM operation in accordance with the first SIM support information. and notifying the PLMN of the same.

20. When executed by an electronic device, the electronic device: receiving data from a first subscriber identity module (SIM); a request to a first public land mobile network (PLMN) for connecting the electronic device to the first PLMN; A non-transitory computer program including computer executable instructions for causing a computer to register with a PLMN. A computer readable medium, the request indicating that the electronic device is a multi-SIM device. the request includes multi-SIM support information, and the multi-SIM support information notifies the first PLMN of the device's preference for multi-SIM operation. A non-transitory computer-readable medium.

Images