Apparatus, system, method, and computer-readable medium for enhancing a cellular system to support a multi-SIM user device

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, the various behaviors of various implementations have an adverse impact on the operation of the network and may even degrade its performance.

Summary of the Invention

[0005] An exemplary embodiment of the present disclosure provides an electronic device including a receiver configured to receive a first subscriber identity module (SIM), a receiver configured to receive a second SIM, and a circuit configured to receive data from the first SIM and transmit a request to a first public land mobile network (PLMN) to register the electronic device with the first PLMN, where the request indicates 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.

[0006] An exemplary embodiment of the present disclosure provides a method executed by an electronic device, the method including receiving data from a first subscriber identity module (SIM) and transmitting a request to a first public land mobile network (PLMN) to register the electronic device with the first PLMN, where the request indicates 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.

[0007] An exemplary embodiment of the present disclosure, when executed by an electronic device, causes the electronic device to receive data from a first subscriber identity module (SIM), transmit a request to a first public land mobile network (PLMN), and transmit the electronic device to be registered with the first PLMN. ​​​​​​​​​​​​​​ providing a non-transitory computer-readable medium including computer-executable instructions, the claim indicating that the electronic device is a multi-SIM device, the claim including multi-SIM support information and the multi-SIM support information indicating a preference of the device for multi-SIM operation to a first PLMN.

[0008] This summary is provided to introduce a selected simplification of concepts that are further described in form below for implementing the following invention. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Further, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure. The scope of the present disclosure is best understood from the following detailed description of the exemplary embodiments when read in conjunction with the accompanying drawings.

[0009]

Brief Description of the Drawings

[0010]

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 1E

Figure 1F

Figure 1G

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

[0011] The scope 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, therefore, it should be understood that it does not necessarily limit the scope of the present disclosure.

[0012] The Third Generation Partnership Project (3GPP) is developing technical specifications for cellular communication network technologies, including radio access, core transport networks, as well as service capabilities related to codecs, security, and quality of service. Recent radio access technology (RAT) specifications include WCDMA (registered trademark) (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced specifications, and New Radio (NR), also referred to as "5G". The development of 3GPP NR specifications continues and is expected to include the definition of next-generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to consist of new non-backward-compatible radio access in new spectrum below 7 GHz, including different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different requirements. ​​​​​ This is achievable. Ultra-mobile broadband is expected to provide opportunities for ultra-mobile broadband access, for example, for indoor applications and hotspots, including cmWave and mmWave spectrums. In particular, ultra-mobile broadband is expected to share a common design framework with flexible wireless access below 7 GHz, using cmWave- and mmWave-specific design optimizations. cmWav provides opportunities for ultra-mobile broadband access for indoor applications and hotspots. It is expected to include cmWav and mmWave spectrums. In particular, ultra-mobile broadband is expected to share a common design framework with flexible wireless access below 7 GHz, using cmWave- and mmWave-specific design optimizations. This is achievable. Ultra-mobile broadband is expected to provide opportunities for ultra-mobile broadband access, for example, for indoor applications and hotspots, including cmWave and mmWave spectrums. In particular, ultra-mobile broadband is expected to share a common design framework with flexible wireless access below 7 GHz, using cmWave- and mmWave-specific design optimizations. It is expected to share a common design framework with flexible wireless access below 7 GHz, using cmWave- and mmWave-specific design optimizations.

[0013] 3GPP has identified various use cases that NR is expected to support and has also addressed diverse user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. 3GPP has identified various use cases that NR is expected to support and has also addressed diverse user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. 3GPP has identified various use cases that NR is expected to support and has also addressed diverse user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. 3GPP has identified various use cases that NR is expected to support and has also addressed diverse user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. 3GPP has identified various use cases that NR is expected to support and has also addressed diverse user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), network operation (e.g., network slicing, routing, handover, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication, which may include any of vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle communication with other entities. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. Specific services and applications within these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connections, vehicle emergency reporting, disaster warnings, real-time gaming, multi-party video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and home automation. It includes automation, robots, and aerial drones, etc. All of these use cases and other use cases are considered in this specification.

[0014] Next is a list of acronyms related to service levels and core network technologies that may appear in the following description. Unless otherwise specified, the acronyms used in this specification refer to the corresponding terms listed below and point to the corresponding terms listed below.

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

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

[0017] (Exemplary Communication Systems and Networks) Figure 1A shows an exemplary communication system 100 in which the systems, methods, and apparatuses described and claimed in this specification are used. The communication system 100 can include wireless transmit / receive units ( WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, which can generally or collectively be referred to as WTRU 102 or W TRU(s) 102. The communication system 100 includes a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 1 ​​10. It can include other networks 112 and network services 113.113. This is possible. The network service 113 can include, for example, a V2X server, a V2X function, a Pro Se server, a ProSe function, an IoT service, video streaming, and / or edge computing, etc.

[0018] It will be understood that the concepts disclosed herein can be used with any number of WTRUs, base stations, networks, and / or or network elements. Each of the WTRUs 102 can be any type of device or apparatus configured to operate and / or communicate in a wireless environment. In the example of FIG. 1A, each of the WTRUs 102 is illustrated in FIGS. 1A - 1E as a handheld wireless communication device. In the various use cases contemplated for wireless communication, each WTRU can comprise, or be included in, any type of device or apparatus configured to transmit and / or receive wireless signals, and these include, by way of example only, user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, home electronics, wearable devices such as smartwatches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, vehicles such as cars, buses or trucks, trains, or airplanes, etc. It is understood to include such.

[0019] The communication system 100 can also include base stations 114a and 114b. ​​​。In the example of FIG. 1A, each base station 114a and 114b is illustrated as a single element 。In reality, base stations 114a and 114b can include any number of interconnected base stations and / or network elements. Base station 114a is configured to wirelessly interface with at least one of WTRUs 102a, 102b, and 102c in order to facilitate access to one or more communication networks such as core network 1 06 / 107 / 109, Internet 110, network service 113, and / or another network 112. Similarly, base station 114b is configured to interface, either wired and / or wirelessly, with at least one of remote radio heads (RRHs) 118a, 118b, transmit and receive points (TRPs) 119a, 119b, and / or roadside units (RSUs) 120a and 120b in order to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 1 10, another network 112, and / or network service 113. The RRHs 118a, 118b are configured to wirelessly interface with at least one of WTRUs 102, e.g., WTRU 102c, in order to facilitate access to one or more communication networks such as core network 106 / 107 / 109 、Internet 110, network service 113, and / or another network 112.

[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 It may be configured to transmit and / or receive wireless signals within a geographical area. Similarly, the base station 114b may be configured to transmit and / or receive wired and / or wireless signals within a specific geographical area, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, for example, base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. Base station 114a may employ multiple-input multiple-output (MIMO) technology and, thus, for example, may utilize multiple transceivers for each sector of the cell. Base station 114a may communicate with one or more of WTRU102a, 102b, 102c, and 102g via air interfaces 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interfaces 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0022]

[0023] Base station 114b may communicate with RRH118a and 118b, TRP119a and 119b, and via wired or air interfaces 115b / 116b / 117b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). 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 WTRU102c, 102d, 102e, and 102f are user wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA). wireless technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) can be implemented, which can establish air interfaces 115 / 116 / 117 and / or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0027] The base station 114a of RAN103 / 104 / 105 and WTRU102a, 102b, 102c, and 102g, or the RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b of RAN103b / 104b / 105b and WTRU102c, 102d can implement wireless technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using, for example, Long-Term Evolution (LTE) and / or LTE-Advanced (LTE-A). The air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and / or V2X technologies and interfaces (e.g., The base station 114a of RAN103 / 104 / 105 and WTRU102a, 102b, 102c, and 102g, or the RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b of RAN103b / 104b / 105b and WTRU102c, 102d can implement wireless technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using, for example, Long-Term Evolution (LTE) and / or LTE-Advanced (LTE-A). The air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and / or V2X technologies and interfaces (e.g., The base station 114a of RAN103 / 104 / 105 and WTRU102a, 102b, 102c, and 102g, or the RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b of RAN103b / 104b / 105b and WTRU102c, 102d can implement wireless technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using, for example, Long-Term Evolution (LTE) and / or LTE-Advanced (LTE-A). The air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and / or V2X technologies and interfaces (e.g., The base station 114a of RAN103 / 104 / 105 and WTRU102a, 102b, 102c, and 102g, or the RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b of RAN103b / 104b / 105b and WTRU102c, 102d can implement wireless technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using, for example, Long-Term Evolution (LTE) and / or LTE-Advanced (LTE-A). The air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and / or V2X technologies and interfaces (e.g., The base station 114a of RAN103 / 104 / 105 and WTRU102a, 102b, 102c, and 102g, or the RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b of RAN103b / 104b / 105b and WTRU102c, 102d can implement wireless technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using, for example, Long-Term Evolution (LTE) and / or LTE-Advanced (LTE-A). The air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and / or V2X technologies and interfaces (e.g., For example, it may include sidelink communication, etc. Similarly, 3GPP NR technology may include NR V2 X technology and interfaces (e.g., sidelink communication, etc.).

[0028] The base stations 114a of RAN103 / 104 / 105 and WTRUs 102a, 102b, 102c, and 102g, or the RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b of RAN103b / 104b / 105b, and WTRUs 102c, 102d, 102e, and 102f may implement radio technologies such as IE EE802.16 (e.g., Worldwide Interoperability for Microwave Access (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), GSM Enhanced Data Rate for GSM Evolution (EDGE), GSM EDGE (GERAN) etc.

[0029] The base station 114c in FIG. 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT, for example, to facilitate wireless connections in localized areas such as offices, homes, vehicles, trains, airplanes, satellites, manufacturing, campuses, etc. The base station 114c and the WTRU 102, for example, the WTRU 102e, may implement radio technologies such as IEEE802.11 to establish a wireless local area network (WLAN). Similarly, the base station 11 ​​​​​4c and WTRU 102, e.g., WTRU 102d, can implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). Base station 114c and WTRU 102, e.g., WRTU 102e, can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a pico or femto cell. As shown in FIG. 1A, base station 114c can have a direct connection to the Internet 110. Thus, base station 114c may not need to access the Internet 110 via the core network 106 / 107 / 109. FIG. 1A RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b can communicate with core network 106 / 107 / 109, which can be any type of network configured to provide voice, data, messaging, permission and authentication, applications, and / or voice over Internet protocol (VoIP) services to one or more of WTRU 102. For example, core network 106 / 107 / 109 can provide call control, billing services, mobile location-based services, prepaid call, Internet connection, packet data network connection, Ethernet (registered trademark) connection, video distribution, etc., and / or execute high-level security functions such as user authentication. Although not shown in FIG. 1A, RAN 103 / 104 / 105 and / or RAN 1

[0030]

[0031] 03b / 104b / 105b ​​​​​​​​​​03b / 104b / 105b and / or core network 106 / 107 / 109 may communicate directly or indirectly with RAN103 / 104 / 105 and / or RAN103b / 104b / 105b and with other RANs employing the same or different RATs. For example, core network 106 / 107 / 109 may communicate with another RAN (not shown) employing GSM or NR radio technology, in addition to being connected to RAN103 / 104 / 105 and / or RAN1 03b / 104b / 105b, which may utilize E-UTRA radio technology.

[0032] Core network 106 / 107 / 109 may also function as a gateway for WTRU102 to access PSTN108, the Internet 110, and / or other network 112. PSTN108 may include a circuit-switched telephone network that provides traditional telephone services (POTS). The Internet 110 may include an interconnected computer network and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet protocol suite. Other network 112 may include a wired or wireless communication network owned and / or operated by other service providers and may include, for example, any type of packet data network (e.g., an IEEE802.3 Ethernet network), or RAN103 / 1 Another core network connected to one or more RANs that may employ the same RAT as 04 / 105 and / or RAN103b / 104b / 105b or a different RAT may include.

[0033] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f of communication system 100 may include multimode functionality. For example, the W TRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different radio links. For example, the WTRU 102g shown in Figure 1A may be configured to communicate with a base station 114a that may employ cellular-based radio technology and a base station 114c that may employ IEEE 802 radio technology.

[0034] Although not shown in Figure 1A, it will be understood that the user equipment may be capable of making a wired connection to a gateway. The gateway may be a residential gateway (RG). The RG may provide a connection to the core network 106 / 107 / 109. It will be understood that many of the concepts included in this specification may equally apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c can equally apply to a wired connection.

[0035] Figure 1B is a system diagram of an exemplary RAN103 and core network 106. As described above, RAN103 employs UTRA radio technology for the air interface It can communicate with WTRUs 102a, 102b, and 102c via 115. RAN 103 can also communicate with core network 106. As shown in FIG. 1B, RA N 103 can include NodeBs 140a, 140b, and 140c, which are air Each may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via interface 115. NodeBs 140a, 140b And 140c may each be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a, 142b. It should be recognized that RAN 103 may include any Number of NodeBs and radio network controllers (RNCs). It should be recognized that RAN 103 may include any Number of NodeBs and radio network controllers (RNCs).

[0036] As shown in FIG. 1B, NodeBs 140a, 140b can communicate with RNC 142a. In addition, NodeB 140c can communicate with RNC 142b. NodeBs 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 14 2a and 142b can be configured to control their respective connected NodeBs 140a, 140b And 140c. In addition, each of RNCs 142a and 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet s cheduling, handover control, macro diversity, security functions, data Encryption, etc. Encryption, etc. Encryption, etc. may also be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data

[0037] The core network 106 shown in FIG. 1B includes a media gateway (MGW) 144 , a mobile switching center (MSC) 146, a serving GPRS support node (SGS N) 148, and / or a gateway GPRS support node (GGSN) 150 . Although each of the foregoing elements is illustrated as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0038] The RNC 142a of the RAN 103 may be connected to the MSC 146 of the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, and 102c to facilitate communication between the WTRUs 102a, 102b, and 102c and conventional terrestrial communication devices.

[0039] The RNC 142a of the RAN 103 may also be connected to the SGSN 148 of the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, and 102c to facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

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

[0041] Figure 1C is a system diagram of an exemplary RAN 104 and core network 107. As described above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c via an air interface 116. The RAN 104 may also communicate with the core network 107.

[0042] The RAN 104 may include eNodeBs 160a, 160b, and 160c, although it should be appreciated that the RAN 104 may include any number of eNodeBs. Each of the eNodeBs 1 60a, 160b, and 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c via the air interface 116. For example, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, the eNodeB 160a, for example, may use multiple antennas to transmit and receive radio signals to / from the WTRU 102 a. Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, etc. As shown in Figure 1 C, the eNodeBs 160a, 160b, 160c may be connected via an X2 interface

[0043] to each other and may be connected to the core network 107 via an S1 interface. to each other and may be connected to the core network 107 via an S1 interface. They can communicate with each other via the base.

[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) gateway 166. Each of the foregoing elements is shown as part of the core network 107, but it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0045] The MME 162 may be connected to each of the eNodeBs 160a , 160b, and 160c of the RAN 104 via the S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attach of the WTRUs 102a, 102b, and 102c, etc. The MME 162 may also provide control plane functions for switching between the RAN 104 and another RAN (not shown) that employs another radio technology such as GSM or WCDMA.

[0046] The serving gateway 164 can be connected to each of the eNodeBs 160a, 160b, and 160c of the RAN 104 via the S1 interface. The serving gateway 164 can generally route and transfer user data packets between the WTRUs 102a, 102b, and 102c. The serving gateway Way 164 may also perform other functions such as anchoring the user plane during handover between eNodeBs, triggering paging when downlink data is available to WTRUs 102a, 102b, and 102c, and managing and storing the contexts of WTRUs 102a, 102b, and 102c.

[0047] The serving gateway 164 may also be connected to the PDN gateway 166, and the PDN gateway 166 may provide access to a packet switched network such as the Internet 110 to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0048] The core network 107 may facilitate communication with other networks. For example, the core network 107 may provide access to a circuit switched network such as the PSTN 108 to facilitate communication between WTRUs 102a, 102b, and 102c and conventional terrestrial communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide access to a network 112 that may include other wired or wireless networks owned and / or operated by other service providers to WTRUs 102a, 102b, and 102c.

[0049] ​​​​​​​​​​​​​Figure 1D is a system diagram of an exemplary RAN 105 and core network 109 . The RAN 105 can communicate with WT RU 102a and 102b via the air interface 117 by adopting the NR radio technology . The RAN 105 can also communicate with the core network 109 . The non-3GPP interworking function (N3IWF) 199 can adopt the non-3GPP radio technology to communicate with the WTRU 102c via the air interface 198 . The N3IWF 199 can also communicate with the core network 109 .

[0050] The RAN 105 can include gNodeB 180a and 180b. It will be understood that the RAN 105 can include any number of gNodeBs . Each of the gNodeB 180a and 180b can include one or more transceivers for communicating with the WTRU 102a and 102b via the air interface 117. When the integrated access and backhaul connection is used, the same air interface may be used between the WTRU and the gNodeB, which may be the core network 109 via one or more gNBs . The gNodeB 180a and 180b can implement MIMO, MU-MIMO, and / or digital beamforming technology . Thus, the gNodeB 180a can use a plurality of antennas to transmit wireless signals to and receive wireless signals from, for example, the WTRU 102a . It should be recognized that the RAN 105 can adopt other types of base stations such as, for example, eNodeB. It is also understood that the RAN 105 can adopt multiple types of base stations . . . ​​​​​For example, the RAN can employ an eNodeB and a gNodeB.

[0051] The N3IWF199 may include a non-3GPP access point 180c. The N3IW F199 may be understood to include any number of non-3GPP access points. The non 3GPP access point 180c may include one or more transceivers for communicating with the WTRU1 02c via the air interface 198. The non-3GPP access point 180c may use the 802.11 protocol to communicate with the WTRU102c via the air interface 198.

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

[0053] The core network 109 shown in FIG. 1D may be a 5G core network (5GC). The core network 109 can provide a number of communication services to customers interconnected by a radio access network. The core network 109 includes several entities that perform core network functions. As used herein, the term "core network entity" or "network function" refers to any entity that performs one or more functions of the core network. Such core A network entity can be a logical entity implemented in the form of computer-executable instructions (software) stored in the memory of a device or computer system configured for network communication, such as system 90 shown in FIG. 1G and / or stored in the memory of a device or computer system configured for network communication and executed on its processor. It is understood that it can be a logical entity implemented in the form of computer-executable instructions (software) stored in the memory of a device or computer system configured for network communication and executed on its processor. It is understood that it can be a logical entity implemented in the form of computer-executable instructions (software) stored in the memory of a device or computer system configured for network communication and executed on its processor.

[0054] In the example of FIG. 1D, the 5G core network 109 includes an access and mobility management function (AMF) 172, a session management function (SMF) 174, user plane functions (UPF ) 176a and 176b, a user data management function (UDM) 197, an authentication server function ( AUSF) 190, a network exposure function (NEF) 196, a policy control function (PCF ) 184, a non-3GPP interworking function (N3IWF) 199, and a user data repository (UDR) 178. Each of the foregoing elements is shown as part of the 5G core network 109, but it is understood that any one of these elements may be owned and / or operated by an entity other than the core network operator. It is understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, or may be composed of multiple instances of each of these elements. FIG. 1D shows the network functions directly connected to each other, but it should be understood that the network functions can communicate through a diameter routing agent or any routing agent such as a message bus. It is understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, or may be composed of multiple instances of each of these elements. FIG. 1D shows the network functions directly connected to each other, but it should be understood that the network functions can communicate through a diameter routing agent or any routing agent such as a message bus. It is also understood that FIG. 1D shows the network functions directly connected to each other, but it should be understood that the network functions can communicate through a diameter routing agent or any routing agent such as a message bus. It should be understood that the network functions can communicate through a diameter routing agent or any routing agent such as a message bus.

[0055] In the example of FIG. 1D, the connections between network functions are a set of interfaces or standards is achieved through a point. The network function can be modeled, described, or implemented as a set of services that are called or invoked by other network functions or services. It should be understood that the invocation of network function services can be achieved through direct connections between network functions, message exchanges on a message bus, software function calls, etc. The call of the network function service can be achieved through direct connections between network functions, message exchanges on a message bus, software function calls, etc. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D.

[0056] AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D. AMF172 may be connected to RAN105 via the N2 interface and may function as a control node. For example, AMF172 can be responsible for registration management, connection management, reachability management, access authentication, and access authorization. AMF can play a role in transferring user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 can generally route and transfer NAS packets between WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D.

[0057] SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and may be connected to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, and UPF176a and SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and may be connected to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, and UPF176a and SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and may be connected to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, and UPF176a and SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and may be connected to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, and UPF176a and SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and may be connected to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 can be responsible for session management, IP address allocation for WTRU102a, 102b, and 102c, and UPF176a and ​​Manage and configure traffic steering rules in UPF176b, and Can play a role in generating downlink data notifications to AMF172.

[0058] UPF176a and UPF176b facilitate communication between WTRU102a, 102b, and 102 c and other devices, such as accessing a packet data network (PDN) like the Internet 110 to WTRU102a, 102b, and 102 c. UPF176a and UPF176b can also provide access to other types of packet data networks to WTRU102a, 102b, and 102 c. For example, another network 112 can be an Ethernet network or any type of network that exchanges packets of work or data. UPF176a and UPF176b can receive traffic steering rules from SMF174 via the N4 interface. UPF176a and UPF 176b can provide access to the packet data network by connecting to the packet data network via the N6 interface or by connecting to each other and other UPFs via the N9 interface . In addition to providing access to the packet data network, UPF176 can be responsible for packet routing and forwarding, policy rule enforcement, service quality processing of user plane traffic, and downlink packet buffering. AMF172 can also be connected to N3IWF199 via, for example, the N2 interface .

[0059] AMF172 can also be connected to N3IWF199 via, for example, the N2 interface This may also be the case. The N3IWF can facilitate the connection between the WTRU 102c and the 5G core network 170 via, for example, a radio interface technology not defined by 3GPP. The AMF can communicate with the N3IWF 199 in the same or a similar way as it communicates with the RAN 105. This may also be the case. The N3IWF can facilitate the connection between the WTRU 102c and the 5G core network 170 via, for example, a radio interface technology not defined by 3GPP. The AMF can communicate with the N3IWF 199 in the same or a similar way as it communicates with the RAN 105.

[0060] The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies. The PCF 184 can be connected to the SMF 174 via the N7 interface, to the AMF 172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. The PCF 184 can provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, enabling the control plane nodes to enforce these rules. The PCF 184 can send policies for the WTRU 102a, 102b, and 102c to the AMF 172 so that the AMF can distribute the policies to the WTRU 102a, 102b, and 102c via the N1 interface. The WTRU 102a, 102b, and 102c can then enforce or apply the policies.

[0061] The UDR 178 can function as a repository for authentication credentials and subscription information. The UDR can be connected to network functions, as a result of which the network functions can add, read, and modify data in the repository. For example, the UDR 178 can be connected to the PCF 184 via the N36 interface. The UDR 178 can function as a repository for authentication credentials and subscription information. The UDR can be connected to network functions, as a result of which the network functions can add, read, and modify data in the repository. For example, the UDR 178 can be connected to the PCF 184 via the N36 interface. The UDR 178 can function as a repository for authentication credentials and subscription information. The UDR can be connected to network functions, as a result of which the network functions can add, read, and modify data in the repository. For example, the UDR 178 can be connected to the PCF 184 via the N36 interface. The UDR 178 can function as a repository for authentication credentials and subscription information. The UDR can be connected to network functions, as a result of which the network functions can add, read, and modify data in the repository. For example, the UDR 178 can be connected to the PCF 184 via the N36 interface. Similarly, the UDR 178 can be connected to the NEF 196 via the N37 interface. It can be done, and UDR178 can be connected to UDM197 via the N35 interface. It can be done.

[0062] UDM197 can function as an interface between UDR178 and other network functions. UDM197 can allow access to UDR178 for network functions. For example, UDM197 can be connected to AMF172 via the N8 interface, UDM197 can be connected to SMF174 via the N10 interface. Similarly, UDM197 can be connected to AUSF 190 via the N13 interface. UDR178 and UDM197 can be closely integrated. That's fine.

[0063] AUSF190 performs authentication-related operations, connects to UDM1 78 via the N13 interface, and connects to AMF172 via the N12 interface.

[0064] NEF196 exposes the capabilities and services of the 5G core network 109 to the application function (AF) 188. The exposure can be done on the N33 API interface. NEF can be connected to AF188 via the N33 interface and can be connected to other network functions to expose the capabilities and services of the 5G core network 109. It can be done.

[0065] The application function 188 can communicate with the network functions of the 5G core network 109. The communication between the application function 188 and the network functions can be done directly via an interface or via NEF196. The application function 188 may be regarded as part of the 5G core network 109 or may be deployed by an enterprise having a business relationship with a mobile network operator and located outside the 5G core network 109.

[0066] Network slicing is a mechanism that can be used by a mobile network operator to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation. or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types that are executed across a single RAN. Network slicing enables the operator to create customized networks optimized to provide solutions for various market scenarios that require diverse requirements, for example, in the fields of functionality, performance, and isolation.

[0067] 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. 3GPP is designing the 5G core network to support network slicing. Network slicing is an excellent tool that network operators can use to support a set of diverse 5G use cases (for example, massive IoT, critical communications, V2X, and advanced mobile broadband) that are very diverse and sometimes require extreme requirements. Without using network slicing technology, when each use case has its own specific set of performance, scalability, and availability requirements, the network architecture will be less effective in meeting the needs of a wider range of use cases. It may not be flexible and scalable enough to support efficiently in terms of rate. Furthermore it is necessary to make the introduction of new network services more efficient.

[0068] Referring again to FIG. 1D, in a network slicing scenario, the WTRU 102a , 102b, or 102c can be connected to the AMF 172 via the N1 interface. The AMF may logically be part of one or more slices. The AMF can coordinate the connection or communication between the WTRU 102a, 102b, or 102c and one or more UPFs 1 76a and 176b, the SMF 174, and other network functions. Each of the UPFs 176a and 176b, the SMF 174, and other network functions may be part of the same slice or different slices . When they are part of different slices, they can be separated from each other in the sense that they can utilize different computing resources, security authentication information, etc.

[0069] The core network 109 can facilitate communication with other networks. For example, the core network 109 may include or communicate with an IP gateway such as an IP Multimedia Subsystem (IMS) server that functions as an interface between the 5G core network 109 and the PSTN 108. For example, the core network 109 may include or communicate with a Short Message Service (SMS) service center that facilitates communication via the Short Message Service. For example, the 5G core network 109 can communicate with the WTRU 102a, 102b, and ​ The exchange of non-IP data packets between 102c and the server or application function 188 can be facilitated. Additionally, the core network 170 can include other wired or wireless networks owned and / or operated by other service providers, and can provide access to network 112 to WTRU102a, 102b, and 102c.

[0070] The core network entities described herein and shown in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to those entities in certain existing 3GPP specifications. However, in the future, those entities and functions may be identified by other names, and certain entities or functions may be combined in future 3GPP specifications, including 3GPP NR specifications, published by 3GPP. Accordingly, the specific network entities and functions described and shown in FIGS. 1A, 1B, 1C, 1D, and 1E are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein can be implemented or realized in any similar communication system, whether currently defined or to be defined in the future.

[0071] FIG. 1E shows an exemplary communication system 111 in which the systems, methods, and apparatuses described herein can be used. The communication system 111 can include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the communication system 111 can include additional or fewer components than those shown in FIG. 1E. ​​​​​​​​​​​​​​​​The concepts that follow are applicable to any number of WTRUs, base stations gNB, V2X networks, and / or other network elements. One or some or all of WTRUs A , B, C, D, E, and F may be outside the coverage of access network 122 . WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0072] WTRUs A, B, C, D, E, F can communicate with each other via the Uu interface 129b through gNB121 when they are under the coverage of the access network (only B and F are shown under the network coverage of Figure 1E). When WTRUs A, B, C, D, E, F are under or outside the coverage of the access network (e.g., A, C, WTRUs A, B, C, D, E, F can communicate with each other, and D and E are shown outside the network coverage of Figure 1 E), they can communicate directly with each other via the sidelink (PC5 or NR PC5) interfaces 125a, 125b, 128. When WTRUs A, B, C, D, E, and F are outside the coverage of the access network (e.g., A, C, WTRUs A, B, C, D, E, F can communicate with each other, and D and E are shown outside the network coverage of Figure 1

[0073] E), they can communicate directly with each other via the sidelink (PC5 or NR PC5) interfaces 125a, 125b, 128. WTRUs A, B, C, D, E, and F can communicate with RSU123a or 123b via the vehicle-to-network (V2N) 126 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F can communicate with the V2X server 124 via the vehicle-to-infrastructure (V2I ) interface 127. WTR U A, B, C, D, E, and F can communicate with another UE via the vehicle-to-person (V2P) interface 128. ​

[0074] Figure 1F is a block diagram of an exemplary apparatus or device WTRU102 configured for wireless communication and operation by the systems, methods, and apparatuses described in this specification. As shown in Figure 1F, an exemplary WTRU102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touch pad / indicator 128, a non-removable memory 130, a removable memory 13 2, a power supply 134, a global positioning system (GPS) chipset 136, and other peripheral devices 13 8. It will be understood that the WTRU102 can include any sub-combination of the foregoing elements. Also, without limitation, among others, base stations 114a and 114b, and / or nodes, such as, but not limited to, transceiver stations (BTSs), Node Bs, site controllers, access points (APs), Home Node Bs, evolved Home Node Bs (eNodeBs), Home evolved Node Bs (HeNBs), Home evolved Node B gateways, next generation Node Bs (gNodeBs), and proxy nodes, can represent some or all of the elements illustrated in Figure 1F and described herein. The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, discrete hardware components, or any other suitable entity configured to perform the functions described herein. circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, discrete hardware components, or any other suitable entity configured to perform the functions described herein. The transceiver 120 can be configured to transmit and receive wireless signals. The transmit / receive element 122 can be configured to facilitate, via the transceiver 120, the transmission and reception of wireless signals.

[0075] The speaker / microphone 124 can be configured to provide an audio interface between the WTRU102 and the user. The keypad 126 can be configured to provide an input interface between the WTRU102 and the user. The display / touch pad / indicator 128 can be configured to provide a visual and / or touch input interface between the WTRU102 and the user. a circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. FIG. 1F illustrates the processor 118 and the transceiver 120 as separate components, but it will be understood that the processor 118 and the transceiver 120 may be integrated into an electronic package or chip. The transmit / receive element 122 of the UE may transmit signals to or receive signals from a base station (e.g., the base station 114a of FIG. 1A) via the air interface 115 / 116 / 117, or to or from another UE via the air interface 115d /

[0076] 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. The transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF signals and optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals or wired signals.

[0077] ​​​​​​In addition, although the transmit / receive element 122 is shown as a single element in FIG. 1F, the WTR U102 can include any number of transmit / receive elements 122. More specifically, the WT RU102 can employ MIMO technology. Accordingly, the WTRU102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interfaces 115 / 116 / 117.

[0078] The transceiver 120 can be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU102 can have a multi-mode function. Accordingly, the transceiver 120 can include multiple transceivers to enable the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, or NR and E-UTRA, or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0079] The processor 118 of the WTRU102 is coupled to the speaker / microphone 124, keypad 126, and / or display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad / indicator 128. In addition, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. The processor 118 can access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server hosted by a cloud or edge computing platform or a home computer (not shown). The processor 118 can receive power from a power source 134 and can be configured to distribute and / or control power to other components of the WTRU 102. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can include one or more dry cell batteries, solar cells, fuel cells, and the like. The processor 118 can also be coupled to a GPS chipset 136 configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the

[0080] WTRU 102 can obtain location information from a base station (e.g., base stations 114a, 114b) via an air interface 115 / 117. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can include one or more dry cell batteries, solar cells, fuel cells, and the like.

[0081] The processor 118 can also be coupled to a GPS chipset 136 configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 can obtain location information from a base station (e.g., base stations 114a, 114b) via an air interface 115 / 117. Receive location information via 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. The WTRU10 2 can understand that it can obtain location information by any suitable positioning method. will be.

[0082] The processor 118 can further be coupled to other peripheral devices 138, and the other peripheral devices can include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connections. For example, the peripheral devices 138 can include an accelerometer, biometrics (e.g., fingerprint) sensors, an e-compass, a satellite transceiver, a digital camera (for photos or videos), a universal serial bus (USB) port or other interconnect interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and various other sensors. can be.

[0083] The WTRU102 can be included in wearable devices such as sensors, home appliances, smartwatches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, vehicles such as automobiles, trucks, trains, or other devices or equipment such as airplanes. The WTRU102 can be interconnected via one or more interconnect interfaces, such as an interconnect interface that includes one of the peripheral devices 138. It can be connected to other components, modules, or systems of the device or apparatus as well.

[0084] FIG. 1G is a block diagram of an exemplary computing system 90 that can embody one or more devices of the communication network shown in FIGS. 1A, 1C, 1D, 106 / 107 / 109 of the core network, PSTN 108, Internet 110, other network 112, or network service 113, such as a particular node or functional entity as shown in FIGS. 1E. The computing system 90 can include a computer or a server and can be mainly controlled by computer-readable instructions, which can be in the form of software regardless of the location or means where such software is stored or accessed. Such computer-readable instructions can be executed within a processor 91 to cause the computing system 90 to perform operations. The processor 9 1 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor ( DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC) a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 can perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. That is, the processor 91 can execute signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. 1 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 can perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 can perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. That is, the processor 91 can execute signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91 that can execute additional functions or assist the processor 91. The processor 91 and / or the coprocessor 81 can receive, generate, and process data related to the methods and apparatuses disclosed herein.

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

[0086] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such a memory includes circuitry that enables the storage and retrieval of information. The ROM 93 generally contains stored data that cannot be easily changed. The data stored in the RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to the RAM 82 and / or the ROM 93 may be controlled by a memory controller 92. The memory controller 92 translates virtual addresses to physical addresses when instructions are executed. A response conversion function can be provided. The memory controller 92 can also separate the processes in the system and provide a memory protection function that separates the system process from the user process. Therefore, a program running in the first mode can access only the memory mapped by its own process virtual address space and cannot access the memory within the virtual address space of another process unless memory sharing between processes is set. In addition, the computing system 90 can include a peripheral device controller 83 that serves to communicate instructions to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85 from the processor 91. The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output can include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 can be implemented as a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components necessary to generate the video signal sent to the display 86. Furthermore, the computing system 90 can perform functions such as processing and storing input data,

[0087] retrieving and outputting stored data, communicating with other devices or systems, and controlling the operation of the computing system 90 itself.

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

[0089] Furthermore, the computing system 90 can perform functions such as to enable communication with other nodes or functional entities of the network of computing system 90 is used to connect to external communication networks or devices such as the RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, WTRU 102, or other network 112 shown in FIGS. 1A, 1B, 1C, 1D, and 1E and may include a communication circuit such as a wireless or wired network adapter 97 for connection to the external communication network or device. The communication circuit can be used, either alone or in combination with the processor 91, to perform the transmission and reception steps of the specific apparatus, node, or functional entity described herein.

[0090] Any or all of the apparatus, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor such as processor 118 or 91, cause the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions executed on a processor of an apparatus or computing system configured for wireless and / or wired network communication. The computer-readable storage medium may be implemented by any non-transitory (e.g., tangible or physical) method or technology for storing information, volatile and non-volatile, removable and non-removable, media. including a medium, but such a computer-readable storage medium does not include a signal. A computer- readable storage medium includes RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other tangible or physical medium that can be used to store the desired information and can be accessed by a computing system, but is not limited to these.

[0091] (5G System Architecture) Figure 2 shows a 3GPP 5G non-roaming system architecture in which various entities interact with each other via reference points. The user equipment (UE) 102 can communicate with the core network (CN) to establish a control signaling link and enable the UE 102 to use services from the CN. Examples of control signaling functions include registration, connection and mobility management, authentication and authorization, session management, etc.

[0092] The following network functions (NFs) in Figure 2 are the main NFs within the control plane (CP) of the CN related to control signaling. · Access and Mobility Function (AMF) 172: The UE 102 sends N1 messages to the AMF 172 via the RAN node 105 to perform many control plane signaling such as registration, connection management, mobility management, access authentication and authorization. · Session Management Function (SMF) 174: The SMF 174 is responsible for the UE to access the ​is for establishing a PDU session to enable sending data to a data network (DN) 208 such as an application server and other session management-related functions, and is responsible for session management related to this. · Policy and Control Function (PCF) 184: The PCF 184 provides a policy framework such as managing network behavior, accessing subscription information, and making policy decisions. · Authentication Server Function (AUSF) 190: The AUSF 190 supports the authentication of the UE for 3GPP and non-trusted non-3GPP access. · Unified Data Management (UDM) 197: The UDM 197 supports the generation of 3GPP AKA authentication credentials, user identification processing, subscription management, etc. · Network Slice Selection Function (NSSF) 216: The NSSF 216 is involved in aspects of network slice management such as selecting a network slice instance for the UE and managing the NSSAI. · Radio Access Network (RAN) 105: The RAN node 105 provides communication access from the UE 102 to the core network for both control plane communication and user plane communication.

[0093] (5G Roaming Architecture) Figure 3 shows a 5G system roaming architecture for a local breakout scenario in a service-based representation where the VPMLN is the visited PLMN and the HPLMN is the home PLMN. The Security Edge Protection Proxy (SEPP) 3 04 enables communication between the VPLMN and the HPLMN.

[0094] ​​​​​​​​​​​Figure 4 shows the 5G system architecture for the local breakout scenario in the reference point representation. In this figure, SEPP is not shown for clarity. The AMF of the VPLMN can communicate with the AUSF of the HPLMN via the N12 interface to authenticate the UE from the HPLMN. Policy information may be communicated between the vPCF and the hPCF via the N24 interface. (For clarity, SEPP is not shown in this figure.) The AMF of the VPLMN can communicate with the AUSF of the HPLMN via the N12 interface to authenticate the UE from the HPLMN. Policy information may be communicated between the vPCF and the hPCF via the N24 interface. (5G Registration Procedure) Before the UE can use the services provided by the CN, the UE needs to register with the core network. Figure 5 shows the 5G general registration procedure from TS 23.502 [2] that the UE executes to register with the CN. The following are the notable steps of the general registration procedure.

[0095] (5G Registration Procedure) Before the UE can use the services provided by the CN, the UE needs to register with the core network. Figure 5 shows the 5G general registration procedure from TS 23.502 [2] that the UE executes to register with the CN. The following are the notable steps of the general registration procedure. In step S500, the UE provides a registration type to indicate what the request is for. Two common types are the initial registration performed by the UE to establish registration with the CN initially, and the periodic registration update performed at periodic intervals to notify the CN that the UE still exists. In addition, the UE can provide the CN with an identifier such as the SUCI that the CN uses to authenticate the UE in step S510 during the initial registration. In step S500, the UE provides a registration type to indicate what the request is for. Two common types are the initial registration performed by the UE to establish registration with the CN initially, and the periodic registration update performed at periodic intervals to notify the CN that the UE still exists. In addition, the UE can provide the CN with an identifier such as the SUCI that the CN uses to authenticate the UE in step S510 during the initial registration. In steps S502, S504, S506, S508, the AMF can obtain the SUCI of the UE if it was not provided in step S500. In steps S502, S504, S506, S508, the AMF can obtain the SUCI of the UE if it was not provided in step S500. In step S510, the AUSF authenticates the UE based on the subscription information provided by the UDM and the SUCI provided by the UE. In step S510, the AUSF authenticates the UE based on the subscription information provided by the UDM and the SUCI provided by the UE. In step S512, the AMF sends a registration acceptance message indicating the result of the registration procedure to the UE. Return to E. In the case of initial registration, the acceptance message includes a temporary identifier such as a 5G-GUTI, a list of authorized network slices, DRX parameters, and other relevant data for UE operation. The 5G-GUTI identifier includes the 5G-S-TMSI identifier used to identify paging requests for the UE.

[0096] (Registration, Connection, and Radio Resource Control Management State) In 5GS, the UE maintains a management state to enable communication with the core network. These management states consist of a registration (RM), connection (CM), and radio resource control (RRC ) management state. The management state is maintained in both the UE and the RAN / CN.

[0097] To use the services provided by the CN, the UE needs to register with the CN by performing an initial registration procedure. Once registered, the UE changes from the RM-DEREGISTERED (deregistered) state to the RM-REGISTER ED state as shown in Figure 6. The UE needs to perform periodic registration updates to maintain the RM-REGISTERED state with the network. When the UE is in the RM-DEREGISTERED state, the UE cannot access the services provided by the CN.

[0098] The connection management (CM) state shown in Figure 7 represents the NAS signaling connection between the UE and the AMF via the N1 interface. This signaling connection enables the UE and the CN to communicate information via the control plane for efficient communication within the 5G system.

[0099] Finally, the UE also maintains the RRC state with the RAN node as described in TS 38 .300 [4]. · RRC_IDLE: A UE in this state performs PLMN selection, receives broadcast system information, and performs cell reselection. In addition, the UE can enter the discontinuous reception (DRX) mode and monitor paging requests from the 5GC. · RRC_INACTIVE: A UE in this state performs functions similar to those of RRC_IDLE, except that the fact that paging requests are initiated by the RAN node. In addition, the UE and the RAN node maintain context information that enables the UE to quickly transition to the RRC_CONNECTED state. When in this state, both the control plane connection and the user plane connection between the RAN node and the 5GC are established for the UE. · RRC_CONNECTED: Unicast data transfer with the UE is enabled when the UE is in this state. This is because both the CP and the UP are established between the RAN node and the CN for the UE, and other context information is maintained between the UE and the RAN node to enable communication.

[0100] (5G Paging Mechanism) Paging refers to the 5GS mechanism by which either the core network or the RAN notifies a UE in the CM-IDLE or RRC_IDLE / RRC_INACTIVE state of pending data addressed to the UE. TS 38.304 [5] reduces power consumption during the inactive period for the RRC_IDLE state and the RRC_INACTIVE state ​​​​​​​​​​​Provide an explanation of a UE that uses discontinuous reception (DRX) at times. The UE is during DRX to be notified of activities in the CN that may request the UE to establish a connection and monitors paging opportunities (POs). The UE performs calculations based on the information provided by the system information received by the UE and the UE_ID to know when to monitor the paging opportunities. The UE_ID is calculated by a modulo operation of the identifier to 1024 from an identifier for the UE such as an IMSI or 5G-S-TMSI. On the network side, paging functions in 5G in the same way as LTE paging shown in FIG. 23 . .

[0101] (Identifier) Section 5.9.4 of 23.501 describes the 5G globally unique identifier (5G-GUT I). The 5G-GUTI is configured as follows. <5G-GUTI> := <guami><5G-TMSI> Here, the GUAMI identifies the assigned AMF, and the 5G-TMSI uniquely identifies the UE within the AMF. The global unique AMF ID (GUAMI) shall be configured as follows. <guami> := <mcc> <mnc><AMF Region ID> <A MF Set ID> <AMF Pointer> The AMF Region ID identifies the region, the AMF Set ID uniquely identifies the AMF Set within the AMF region, and the AMF Pointer uniquely identifies the AMF within the AMF set. in the AMF region, and the AMF Pointer uniquely identifies the AMF within the AMF set. Note 1: The AMF Region ID allows the operator to reuse the same AMF Set ID and AMF Pointer in different regions, to handle a larger number of AMFs in the network than can be supported by the AMF Set ID and AMF Pointer. in the network. Note 2: For details of the structure of the fields of the GUAMI, see TS 23.003

[19] . The 5G-S-TMSI is a shortened form of the GUTI to enable more efficient radio signaling procedures (e.g., during paging and service requests), and is defined as follows. <5G-S-TMSI> := <AMF Set ID> <AMF Pointer> <5G-TMSI>

[0102] (Slice-specific authentication and authorization) In Release 16 of the 5G system, 3GPP agreed to add slice-specific authentication and authorization capabilities. This procedure enables the network to initiate an EAP-based procedure with the UE when the UE attempts to register for a particular slice (i.e., S-NSSAI). The EAP-based authentication procedure requires the UE to provide user ID and associated network credentials to be permitted access to the slice. ​​​​​​​​​​It is based on. The new procedure is described in References [7] and [8] and shown in Figure 8. It is shown. Figure 8 is copied from Reference [8].

[0103] (LTE System Architecture) Figure 19 shows the 3GPP EPS non-roaming system architecture in which a User Equipment (UE) communicates with a Core Network (CN) via an E-UTRAN 3202 to obtain other operator services such as Internet services or IMS. The E-UTRAN is a Radio Access Network (RAN) that interfaces with the UE via an LTE-Uu interface. The UE accesses the CN by using NAS signaling via the S1-MME interface through the E-UTRAN and transmits and receives data via the S1-U interface through the E-UTRAN. interface through the E-UTRAN. interface through the E-UTRAN. interface through the E-UTRAN. interface through the E-UTRAN.

[0104] The following network functions (NFs) in Figure 19 are briefly described below. · Mobility Management Entity (MME): The MME provides NAS signaling to the UE, authenticates and authorizes the UE to access the CN, and manages UE mobility among many functions it performs. · Home Subscriber Server (HSS) 2000: The HSS 2000 provides UE authentication / authorization and stores UE subscription information. · Serving Gateway (S-GW) 2002: The S-GW 2002 functions as a mobility anchor point for the UE in the user plane (UP) that routes and forwards traffic between the P-GW and · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. · Packet Data Network Gateway (P-GW) 2004: The P-GW 2004 assigns an IP address to the UE. Allocate a bearer and provide access to a packet data network such as the Internet to the UE to. · Policy and Charging Rules Function (PCRF) 2006: Core network policy and charging elements.

[0105] (LTE attach procedure) The UE registers with the core network and executes an attach procedure to use services from the core network that require registration. Figure 20 shows the attach procedure, and several notable steps are highlighted below in relation to the initial attach. At step S2000, the UE sends an attach request to the CN via the eNodeB. In the request, the UE provides an identifier (IMSI), attach type, UE core network performance, UE-specific DRX parameters, preferred network behavior, and other message parameters shown in [9]. At step S2000, the UE sends an attach request to the CN via the eNodeB. In the request, the UE provides an identifier (IMSI), attach type, UE core network performance, UE-specific DRX parameters, preferred network behavior, and other message parameters shown in [9]. In the request, the UE provides an identifier (IMSI), attach type, UE core network performance, UE-specific DRX parameters, preferred network behavior, and other message parameters shown in [9]. work performance, UE-specific DRX parameters, preferred network behavior, and other message parameters shown in [9]. are provided. At step S2002, the eNodeB selects an appropriate MME and forwards the request to the selected MME. At step S2002, the eNodeB selects an appropriate MME and forwards the request to the selected MME. At steps S2004a and S2004b, the MME performs authentication and NAS security setup to activate mandatory integrity protection and NAS encryption. The MME communicates with the HSS to complete this step. From this point on, NAS signaling is protected for both integrity and encryption. At steps S2004a and S2004b, the MME performs authentication and NAS security setup to activate mandatory integrity protection and NAS encryption. The MME communicates with the HSS to complete this step. From this point on, NAS signaling is protected for both integrity and encryption. At steps S2004a and S2004b, the MME performs authentication and NAS security setup to activate mandatory integrity protection and NAS encryption. The MME communicates with the HSS to complete this step. From this point on, NAS signaling is protected for both integrity and encryption. At steps S2004a and S2004b, the MME performs authentication and NAS security setup to activate mandatory integrity protection and NAS encryption. The MME communicates with the HSS to complete this step. From this point on, NAS signaling is protected for both integrity and encryption. At step S2006, the MME returns an attach acceptance containing a GUTI, TAI list, session management request information, supported network behavior, service gap time, and other message parameters as shown in [9] to the attach request. At step S2006, the MME returns an attach acceptance containing a GUTI, TAI list, session management request information, supported network behavior, service gap time, and other message parameters as shown in [9] to the attach request. to the attach request. In step S2008, the eNodeB returns an attach acceptance message to the UE , and the UE saves the message parameters for future use. There may also be relevant RRC signaling rings. In step S2010, the UE returns a direct transfer message including an attach complete message . The eNodeB transfers the attach complete message to the MME in step S2012 .

[0106] (EPS Mobility Management and Connection Management States) The EPS mobility management (EMM) state is shown in Figure 21. The UE is initially in the EMM-DER EGISTERED (deregistered) state and enters the EMM-REGISTERED state after successfully connecting to the network . Once registered, the UE can continue to use services provided by the network, such as accessing the Internet and making IMS calls . The UE can remain in the EMM-RE GISTERED state by performing a tracking area update (TAU) procedure and can enter the EMM-DE REGISTERED state by performing a detach procedure .

[0107] The EPS connection management state is shown in Figure 22. These states indicate the state of the NAS signaling connection between the UE and the core network . In ECM-IDLE, the UE does not have a NAS signaling connection and performs cell and PLMN selection . The transition from ECM-IDLE to the ECM-CONNECTED state occurs for the following procedures: attach request, tracking area update , service request, and detach request .

[0108] (LTE Paging and Service Request) When UE102 is in the ECM - IDLE state and data is available in the core network of UE102 when available, the MME162 sends a paging request to UE102 as shown in FIG. 23. Then, after UE102 executes the service request procedure, it can connect to the core network to receive the data attached to the page. Thereafter, the S - GW 2002 stops paging UE102 and downlink data is transferred to UE102 via the user plane. TS 36.304[5] describes the calculation of the paging opportunity for a UE in discontinuous reception ( DRX) and how the paging opportunity is calculated based on the UE's identifier. Based on that calculation, two UEs can have the same paging opportunity and monitor the paging message simultaneously. The paging message identifies the recipient of the page using the associated UE identifier. (Problem Statement) UEs with multiple USIMs can be applied to various use cases that utilize the advantage of having registrations with two or more operator networks. The TR 22.834[6] of the 3GPP SA1 working group's MUSIM study highlights scenarios where use cases with multiple USIMs can exist. This disclosure focuses on the case where the UE has common radio and baseband components to support multiple USIMs. Thus, the radio and baseband components cannot be dedicated to a single USIM only. This disclosure also provides a solution for dual Rx, single Tx UEs that are within the scope of the MUSIM study.

[0109] (Problem Statement) UEs with multiple USIMs can be applied to various use cases that utilize the advantage of having registrations with two or more operator networks. The TR 22.834[6] of the 3GPP SA1 working group's MUSIM study highlights scenarios where use cases with multiple USIMs can exist. This disclosure focuses on the case where the UE has common radio and baseband components to support multiple USIMs. Thus, the radio and baseband components cannot be dedicated to a single USIM only. This disclosure also provides a solution for dual Rx, single Tx UEs that are within the scope of the MUSIM study. UEs that are within the scope of the MUSIM study. This disclosure focuses on the case where the UE has common radio and baseband components to support multiple USIMs. Thus, the radio and baseband components cannot be dedicated to a single USIM only. This disclosure also provides a solution for dual Rx, single Tx UEs that are within the scope of the MUSIM study. Thus, the radio and baseband components cannot be dedicated to a single USIM only. This disclosure also provides a solution for dual Rx, single Tx UEs that are within the scope of the MUSIM study. Thus, the radio and baseband components cannot be dedicated to a single USIM only. This disclosure also provides a solution for dual Rx, single Tx UEs that are within the scope of the MUSIM study. This disclosure also provides a solution for dual Rx, single Tx UEs.

[0110] ​The MUSIM SA1 study highlights the potential requirements of multiple USIM UEs. These are some of these requirements as follows. · Support for UEs with multiple USIMs in 3GPP systems · Support for UE implementations with single Rx, single Tx and dual Rx, single Tx ports · MUSIM UEs that enable the user to configure service preferences from multiple USIMs · The 3GPP system should support MUSIM UEs with multiple USIMs from the same or different operators · 3GPP systems to indicate traffic types to MUSIM UEs that triggered paging procedures · The 3GPP system should be able to suspend active communications and resume suspended communications in communications with multiple USIM UEs · The 3GPP system should minimize paging collisions for paging multiple USIM UEs · The 3GPP system should minimize signaling overhead by supporting multiple USIMs · MUSIM UEs should be supported in both 5G and LTE systems Note that the terms SIM and USIM (as used in TR 22.834 [6]) are used interchangeably in this disclosure. Additionally, the term multi-SIM is used to refer to multiple USIMs. Also note that the terms LTE and EPS are used interchangeably in this disclosure.

[0111] (Use Case 1) ​​​​​​​​​​The user is traveling overseas from the United States to Asia and has a UE that supports multiple USIMs. For cost reduction purposes, the UE is implemented using a common radio and baseband component that the USIMs share access to. As a result, only one USIM can be active at a time. The user purchases a USIM upon arrival to access cellular services while traveling within the destination country. The mobile USIM provides services for local voice, text, and high-speed data, while the home USIM is mainly used to provide voice and text that the user may want to receive from family and friends while traveling.

[0112] (Use Case 2) Another prominent use case for using multiple USIMs centers around users who have both business and personal subscription services and want to use both services on the same device. The user has a company-issued UE with a subscription service for USIM1 with Operator 1, while the user also has a personal subscription service for USIM2 with Operator 2. The user wants to be able to receive voice calls from either service and access data services by subscribing to either USIM1 or USIM2, depending on the time or the application using the service.

[0113] (Problem) As can be seen from the above use cases, a multi-SIM UE that utilizes a common radio and baseband component must determine which SIM to service at any given time. The current implementations of multi-SIM UEs are proprietary, and as a result, the implementations vary However, the behavior of the UE may vary. Based on the knowledge of the CN regarding the behavior of the UE, many operations and algorithms are optimized, so this difference in behavior may have an adverse impact on the operation of the core network. Both the 3GPP SA1 and SA2 working groups are currently studying issues related to the support of UEs with multiple SIMs. In these studies, it has been proposed to standardize multi-SIM UEs and the corresponding procedures to provide the core network with knowledge of the UE's behavior and enable optimal operation of the UE communicating with any network. This research focuses on UE implementations where common radio and baseband components are used to support multiple SIMs in the UE. It is not yet determined how the UE notifies the CN of multi-SIM performance, how it knows when to monitor paging opportunities associated with the pages of any SIM, how the UE switches its operation from one SIM to another, how the UE notifies the CN when switching the use of SIMs, how to minimize paging collisions, and what policies the UE uses to provide service type prioritization among multiple SIMs. In addition, the support of multi-SIM UEs is expected in both LTE and 5G systems. One of the main problems regarding UEs that operate with multiple SIMs and use common radio and baseband components is the issue of monitoring paging information by the UE of the second SIM when communicating actively with the first SIM. This is the paging related to multiple SIMs.

[0114] In their research, they aim to standardize multi-SIM UEs and the corresponding procedures to provide the core network with knowledge of the UE's behavior and enable optimal operation of the UE communicating with any network. This research focuses on UE implementations where common radio and baseband components are used to support multiple SIMs in the UE. It is not yet determined how the UE notifies the CN of multi-SIM performance, how it knows when to monitor paging opportunities associated with the pages of any SIM, how the UE switches its operation from one SIM to another, how the UE notifies the CN when switching the use of SIMs, how to minimize paging collisions, and what policies the UE uses to provide service type prioritization among multiple SIMs. In addition, the support of multi-SIM UEs is expected in both LTE and 5G systems. One of the main problems regarding UEs that operate with multiple SIMs and use common radio and baseband components is the issue of monitoring paging information by the UE of the second SIM when communicating actively with the first SIM. This is the paging related to multiple SIMs. It is not yet determined how the UE notifies the CN of multi-SIM performance, how it knows when to monitor paging opportunities associated with the pages of any SIM, how the UE switches its operation from one SIM to another, how the UE notifies the CN when switching the use of SIMs, how to minimize paging collisions, and what policies the UE uses to provide service type prioritization among multiple SIMs. In addition, the support of multi-SIM UEs is expected in both LTE and 5G systems. One of the main problems regarding UEs that operate with multiple SIMs and use common radio and baseband components is the issue of monitoring paging information by the UE of the second SIM when communicating actively with the first SIM. This is the paging related to multiple SIMs. It is not yet determined how the UE notifies the CN of multi-SIM performance, how it knows when to monitor paging opportunities associated with the pages of any SIM, how the UE switches its operation from one SIM to another, how the UE notifies the CN when switching the use of SIMs, how to minimize paging collisions, and what policies the UE uses to provide service type prioritization among multiple SIMs.

[0115] One of the main problems regarding UEs that operate with multiple SIMs and use common radio and baseband components is the issue of monitoring paging information by the UE of the second SIM when communicating actively with the first SIM. This is the paging related to multiple SIMs. One of the main problems regarding UEs that operate with multiple SIMs and use common radio and baseband components is the issue of monitoring paging information by the UE of the second SIM when communicating actively with the first SIM. The paging opportunities that overlap in time are called paging collisions. With a single transceiver the UE has to decide to monitor a single paging channel via another paging channel [6]. This decision may cause the UE to miss a page if it is not monitoring the paging request at the time of the paging opportunity of the non-active SIM.

[0116] In some scenarios, paging collisions may occur in a multi-SIM UE. One scenario may be that when the UE is connected to the network of the active SIM, the UE is not actively monitoring the paging opportunities of the non-active SIM. Since the UE shares common baseband and radio components, the UE can be connected to only one network at a time and monitor the paging opportunities associated with the SIM of that network. If a page is sent for the SIM of another network, the UE cannot receive the page. This wastes radio resources at the RAN node that can be used for other purposes.

[0117] Another cause of paging collisions is when the paging opportunities of multiple SIMs overlap in time. Again, the UE can monitor and process the paging opportunities associated with one SIM using a single transceiver. When the paging opportunities overlap or are close, the UE does not have enough time to switch the connection to another network. This also wastes radio resources at the RAN node as before.

[0118] A multi-SIM UE can monitor the paging opportunities associated with multiple SIMs. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power. Even if possible, certain switches that are executed to achieve this result in higher power consumption and shorter battery life of the UE. Furthermore, the UE may switch the connection to unavailable most of the time, and if there is no data for the UE, the UE may not be paged. The side effect of frequent switching may create a scenario of paging collision, and the UE may not be able to enter the DRX cycle to conserve battery power.

[0119] (Overview) Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs. Multiple SIM UEs so far are outside the scope of 3GPP specifications with proprietary solutions implemented by device manufacturers without knowledge of the core network. The behavior of various entities (UE, RAN, and CN) is well-defined, and the operation of the cellular network known among various entities is designed. In various implementations of existing multiple SIM UEs, various behaviors may affect the operation of the network and even degrade its performance. As a result, the MU SIM research from the 3GPP SA1 and SA2 working groups is to define the architecture, interfaces, and procedures for supporting UEs with multiple SIMs.

[0120] The requirements described in the MUSIM research focus on UEs with common radio and baseband components shared by multiple SIMs installed in the UE, as well as dual Rx, single Tx UEs. Then, the goal of the MUSIM work is that UEs with multiple SIMs provide the best possible service for each of the SIM operations. The requirements described in the MUSIM research focus on UEs with common radio and baseband components shared by multiple SIMs installed in the UE, as well as dual Rx, single Tx UEs. Then, the goal of the MUSIM work is that UEs with multiple SIMs provide the best possible service for each of the SIM operations. The requirements described in the MUSIM research focus on UEs with common radio and baseband components shared by multiple SIMs installed in the UE, as well as dual Rx, single Tx UEs. Then, the goal of the MUSIM work is that UEs with multiple SIMs provide the best possible service for each of the SIM operations. The requirements described in the MUSIM research focus on UEs with common radio and baseband components shared by multiple SIMs installed in the UE, as well as dual Rx, single Tx UEs. Then, the goal of the MUSIM work is that UEs with multiple SIMs provide the best possible service for each of the SIM operations. and. The central focus of the research is that the UE has a common radio and baseband component How to provide seamless paging monitoring for multiple SIMs In this disclosure, to address that problem, and also for the case of dual Rx, single Tx UE Solutions are also proposed. Specifically, the solution consists of the following · Enable multiple SIM UEs to notify the core network that they are multi-SIM devices and provide information about other SIMs installed in the UE Define enhancements to the UE registration and attach procedures · Define new registration management states, sub-states, or modes of operation for both the UE and the CN to maintain the registration status of the UE for each SIM · Define enhancements to the existing paging request mechanism to enable paging request transfer from one PLMN to another to reach the UE · Define SIM switching procedures that allow the UE to indicate to the CN that it is switching to another SIM, and at the same time update the registration status of the UE in the CN and the UE · Define non-active registration timer update procedures executed through the active PLMN to maintain the registration timer of non-active SIMs · Define procedures that allow the UE to provide cell measurement values obtained for a non-active PLMN when the UE attempts to establish a connection to the non-active PLMN after deciding to switch to the non-active PLMN · Define procedures that allow the UE to request a new timing identifier where the paging opportunity is aligned or separated from the paging opportunity of another SIM · In a procedure where the UE can request a suspension of the registration timer, the CN pages the UE ​​​​​​​Define the procedures that will also be suspended · Define the procedures that the UE or CN can provide for other information related to the paging process to do · Define a new policy in the 5G UE policy to enable the configuration of multiple SIMs and give the user the function to start manual switching between SIMs through the GUI

[0121] Concept 1: The UE notifies the CN that it is itself a multi-SIM device and provides the CN with information regarding another SIM to do · The UE sends a request to the first PLMN to register the second SIM with the second PLMN to believe · The UE includes the instructions and identifiers for the second SIM to be registered with the second PLMN to contain · The first PLMN forwards the request to the second PLMN · The second PLMN authenticates the UE's SIM qualification information and provides the UE with a temporary identifier used for paging requests for the second SIM to do · The UE and the second PLMN update the UE's registration status for the second SIM Supplementary features of Concept 1: · The UE is registered with the first PLMN for the first SIM · The request is either a partial registration / attach or an indirect registration / attach request · The UE is registered with the first PLMN and requests registration with the second PLMN · This instruction is a multi-SIM instruction · The identifier of the second SIM can be one of the following SUPI (e.g., IMSI), GUTI, 5G-S- TMSI, or SUCI · The temporary identifier assigned to the second SIM can be 5G-GUTI, GUTI, 5G- TMSI, TMSI, or 5G-S-TMSI · The first PLMN includes the identifier of the network node supporting multi-SIM operation, and the identifier of the first SIM authenticated in the first PLMN. · After successfully registering with the second PLMN, the registration state of the UE is RM-INACTIVE or EMM-INACTIVE. · The first PLMN can assign a second temporary identifier for the second SIM and save the registration state of the UE for the second SIM. · The UE provides multi-SIM support information to the CN, and the multi-SIM support information can be composed of one or more of paging criteria, restricted paging areas, paging opportunity separation, the number of pages missed before notification, and the proposed temporary identifier.

[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 the paging request to the second PLMN, and the paging request includes the temporary ID associated with the first SIM. · The second PLMN sends the paging request to the UE at the paging opportunity being monitored by the UE. · The UE extracts the paging information and receives the temporary identifier associated with the first SIM. Supplementary features of Concept 2: · The UE supports multi-SIM operation. · The UE has simultaneous 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 the second PLMN. · The paging request is an encrypted NAS container from the first PLMN to the second PLMN. Transmitted by Na · The paging opportunity is calculated from the temporary identifier of SIM1 · The paging opportunity is calculated from the temporary identifier of SIM2 · The paging information includes the service category for which the page is for, such as voice call, SMS message, or other data (e.g., application data), control plane signaling, emergency message, emergency callback, mobile terminal exception data etc. and can be classified · The paging information includes the PDU session ID and application session ID associated with the page · The UE sends a response to the first PLMN through the second PLMN

[0123] Concept 3: The UE executes the SIM switching procedure · While connected to the first PLMN, the UE receives paging information related to the data associated with the second SIM · Based on the service type prioritization indicator provided in the paging information, the UE determines to switch to the second PLMN to retrieve the data · The UE notifies the first PLMN to temporarily suspend the registration status of the first SIM · The UE and the first PLMN update the registration status of the first SIM on the UE and the first PLMN · The UE attempts to establish communication with the second PLMN for the second SIM Supplementary features of Concept 3: · The paging information may include the service category, PDU session ID, and application ID associated with the data for which the UE is paging, providing service type prioritization ​​​​​·The UE checks the service type prioritization against the internal policy and finds a match finds ·The UE sends a registration update request with the registration type set for SIM switching ·The first PLMN activates the paging request transfer of the first SIM ·The registration state of the first SIM is set to RM - INACTIVE or EMM - INACTIVE in the UE and the first PLMN ·The first PLMN sends a response to the second PLMN where the UE received the paging request sends ·Establishing communication with the second PLMN includes sending a registration update request including the SIM switching registration type including

[0124] Concept 4: The UE updates the registration timer of the second PLMN through the first PLMN ·The UE sends a request to the first PLMN to update the registration timer of the second SIM on the second PLMN sends ·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 updates ·The second PLMN returns a response 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 inactive registration timer update may ·The request includes a temporary identifier associated with the second SIM ·The response can include the status of the registration update request, the new value of the registration timer, or the updated TA I list ·The response can include an indication that the registration state of the second SIM is no longer valid may · The second PLMN allocates a new temporary identifier for the second SIM and can include it in the response to the UE

[0125] Concept 5: While connected to the second PLMN after the SIM switching procedure, the UE collects cell measurement information and provides the measurement values directly to the second PLMN upon connection, or, if the connection fails, through the first PLMN · After disconnecting from the first PLMN and while attempting to connect to the second PLMN, the UE collects cell measurement values · After successfully connecting to the second PLMN, the UE provides the cell measurement values to the RAN node · After a failed attempt to connect to the second PLMN, the UE connects to the first PLMN and includes the collected measurement values and the cause code · The first PLMN transfers the measurement values and the cause code to the second PLMN Supplementary features of Concept 5: · If the UE successfully connects to the second PLMN, the UE formats the cell measurement values into a minimized drive test report to the RAN node of the second PLMN · The cell measurement values indicate the signal strength of the cells belonging to the second PLMN · The cell measurement values include the location and time at which the measurements were taken · The cell measurement values are queued by the UE and can be sent to the RAN node when a future connection is successful · The UE stores the cell measurement values and the cause code after a failed connection to the second PLMN · The cause code can be received from the second PLMN or generated by the UE · The cause code indicates that the RAN node is overloaded and does not accept new registrations ​​​​​​​​​​can · The cause code can indicate that the mobility management node is overloaded and does not accept new registrations and so on · The cause code can indicate that the signal strength of the cell is not strong enough to maintain a connection with the second PLMN · The cause code can indicate that there is no available cell to establish a connection with the second PLMN

[0126] Concept 6: The UE requests a new temporary identifier whose paging opportunity is aligned or separated from the paging opportunity associated with another SIM · The UE is registered with the first PLMN and has received a temporary identifier associated with the paging opportunity of the first SIM · The UE is registered with the second PLMN and has received a temporary identifier associated with the paging opportunity of the second SIM · The UE determines that there may be a paging collision between the paging opportunities of the two SIMs · The UE makes a request to obtain a new temporary identifier whose paging opportunity is different from the previous paging opportunity Supplementary features of Concept 6: · The request may be, for example, one of an initial registration, a mobile registration update, a periodic registration update, an attach, or a tracking area update request · The UE may provide parameters in the request to assist the network in allocating a new temporary identifier · The new parameters may be, for example, paging criteria, restricted paging areas, paging opportunity separation, multi-SIM indicators, temporary identifiers, or multiple paging opportunities and so on ​​​​​​​​​​· The network can assign a paging opportunity that is, for example, the same as an existing paging opportunity, nearby, far away, or assign a different temporary identifier · The network can assign a plurality of temporary identifiers corresponding to a plurality of paging opportunities to the UE · The network can assign a plurality of temporary identifiers corresponding to a plurality of paging opportunities to the UE · The network can assign a plurality of temporary identifiers corresponding to a plurality of paging opportunities to the UE

[0127] Concept 7: · The UE requests to temporarily stop the registration timer associated with the SIM · The UE is registered with the PLMN and the PLMN starts the registration timer · The UE sends a request to activate the registration suspension timer · The CN temporarily stops the registration timer and starts the registration suspension timer · The CN provides a response indicating that the registration suspension timer is active Supplementary features of Concept 7: · The request can be, for example, one of an initial registration, a mobile registration update, a periodic registration update, an attach, or a tracking area update request · The request can be, for example, one of an initial registration, a mobile registration update, a periodic registration update, an attach, or a tracking area update request · The UE can provide the expiration value of the registration suspension timer · The UE can request the CN to queue any downlink data for the UE while the registration suspension timer is running · The UE can request the CN to queue any downlink data for the UE while the registration suspension timer is running · The CN retains the context for the UE, such as the registration state, security context, PDU session, etc. · The CN retains the context for the UE, such as the registration state, security context, PDU session, etc. · The CN can return a new value for the expiration of the registration suspension timer · The CN can provide an instruction to queue downlink data for the UE · The CN can provide an instruction to queue downlink data for the UE

[0128] Concept 8: · The UE or the CN provides information about issues related to the paging process · The UE has registrations for multiple SIMs · The UE is receiving data of the first SIM. · The UE receives a page of the second SIM. · The UE or the CN notifies the other of the UE or the CN of problems associated with the paging process. Do. Supplementary features of Concept 8: · The notification may be a request sent by the UE. · The request may be, for example, one of a mobile registration update, a periodic registration update, a tracking area update, or a service request. · The UE may provide an instruction for the CN to stop paging the UE. · The notification may be a response sent by the CN. · The response may include, for example, an instruction to notify the UE that a previously sent page was missed, the time of that page, the tracking or registration area where the page was sent, and other information about the page such as the service category, phone number, PDU session ID, and application ID. can be included.

[0129] Detailed description As emphasized by the MUSIM study [6], current multi-SIM UE implementations with common radio and baseband components raise many problems related to different UE behaviors that can degrade network performance. To solve such problems, a more integrated solution is proposed that enhances the paging mechanism by having the UE communicate with the core network using newly proposed registration requests to support multi-SIM functionality, having the network provide service priority information in paging messages, enabling paging request forwarding, and minimizing the UE switching cycle between SIMs. With these enhancements, instead of requiring the UE to switch its operation to monitor the paging opportunities for each SIM, the UE can receive paging opportunity prioritization information for multiple SIMs by only monitoring the paging opportunities calculated for the active SIM. In addition, the network can recognize the new registration state, sub-state, or mode of operation of the UE through the new SIM switching procedure and enhancements to the UE registration state. This enhancement enables entities within the cellular system to have knowledge of the operation of the multi-SIM UE. The solutions proposed herein are designed based on the following assumptions. 1. UE implementations with multiple SIMs share common radio and baseband components, and several solutions are presented to address dual Rx, single Tx capable UEs. 2. The multiple SIMs are from the same or different PLMNs (PLMNs refer to the networks of different operators, also called mobile network operators or MNOs). 3. Optionally, the PLMNs can have roaming agreements with each other and support SIM authentication as proposed herein. 4. Security support for multi-SIM operation between the UE and the core network is established. 5. Both the UE and the core network support the multi-SIM functionality proposed herein. However, there may be cases where there is no coordination between mobile network operators or MNOs. In these cases, alternative solutions that do not require coordination between MNOs are presented, and the UE is currently 1. UE implementations with multiple SIMs share common radio and baseband components, and several solutions are presented to address dual Rx, single Tx capable UEs. 2. The multiple SIMs are from the same or different PLMNs (PLMNs refer to the networks of different operators, also called mobile network operators or MNOs). 3. Optionally, the PLMNs can have roaming agreements with each other and support SIM authentication as proposed herein. 4. Security support for multi-SIM operation between the UE and the core network is established. 5. Both the UE and the core network support the multi-SIM functionality proposed herein.

[0130] However, there may be cases where there is no coordination between mobile network operators or MNOs. In these cases, alternative solutions that do not require coordination between MNOs are presented, and the UE is currently ​​​​​​​​Different temporary identifiers corresponding to paging opportunities different from the assigned PO can be requested from the network. This solution and other solutions are also presented to address the MNO - uncoordinated scenario. Note that some aspects of the solutions associated with MNO coordination can also be used in the MNO - uncoordinated scenario. For example, a core network that assigns temporary identifiers associating the same PO to multiple SIMs can be used when there is no MNO coordination. This can be utilized when multiple SIMs belong to the same MNO. The solutions to support multi - SIM UEs are required for both 5GS systems and LTE systems. Therefore, the present disclosure applies the proposed solutions to both 5GS systems and LTE systems. If a solution is shown for only one system, the solution can be easily applied to the other system. Figure 9 shows the main procedures of the proposed solution for a UE with two SIMs, and the solution can be extended to UEs with three or more SIMs. This figure shows a UE that registers with two PLMNs using different SIMs, SIM1 and SIM2. The UE has service subscriptions for both SIM1 and SIM2, mainly communicates with PLMN1 using SIM1, and at the same time registers with PLMN2 for SIM2 and requests PLMN2 to forward paging requests for SIM2 to PLMN1. Thus, the UE only needs to monitor the paging opportunities associated with SIM1 on PLMN1 to receive paging requests for both SIM1 and SIM2. Similarly, the UE can receive paging requests for both SIMs by monitoring the paging opportunities associated with SIM2 on PLMN2. can receive paging requests for both SIMs by monitoring the paging opportunities associated with SIM2 on PLMN2. For a UE with multiple SIMs, when multiple SIMs belong to the same MNO, a core network that assigns the same PO - associated temporary identifier to multiple SIMs can be used. This can be utilized when multiple SIMs belong to the same MNO.

[0131] Solutions to support multi - SIM UEs are required for both 5GS systems and LTE systems. Therefore, the present disclosure applies the proposed solutions to both 5GS systems and LTE systems. If a solution is shown for only one system, the solution can be easily applied to the other system. If a solution is shown for only one system, the solution can be easily applied to the other system. If a solution is shown for only one system, the solution can be easily applied to the other system.

[0132] Figure 9 shows the main procedures of the proposed solution for a UE with two SIMs, but the solution can be extended to UEs with three or more SIMs. This figure shows a UE that registers with two PLMNs using different SIMs, SIM1 and SIM2. The UE has service subscriptions for both SIM1 and SIM2, mainly communicates with PLMN1 using SIM1, and at the same time registers with PLMN2 for SIM2 and requests PLMN2 to forward paging requests for SIM2 to PLMN1. The solution can be extended to UEs with three or more SIMs. This figure shows a UE that registers with two PLMNs using different SIMs, SIM1 and SIM2. The UE has service subscriptions for both SIM1 and SIM2, mainly communicates with PLMN1 using SIM1, and at the same time registers with PLMN2 for SIM2 and requests PLMN2 to forward paging requests for SIM2 to PLMN1. The UE has service subscriptions for both SIM1 and SIM2, mainly communicates with PLMN1 using SIM1, and at the same time registers with PLMN2 for SIM2 and requests PLMN2 to forward paging requests for SIM2 to PLMN1. and requests PLMN2 to forward paging requests for SIM2 to PLMN1 for further processing. Thus, the UE only needs to monitor the paging opportunities associated with SIM1 on PLMN1 to receive paging requests for both SIM1 and SIM2. Similarly, the UE can receive paging requests for both SIMs by monitoring the paging opportunities associated with SIM2 on PLMN2. by monitoring only the paging opportunities associated with SIM2 on PLMN2 so that when the UE is communicating with PLMN2, paging requests for both SIM1 and SIM2 can be received. The UE can receive pages for multiple SIMs, for example active SIMs as well as non-active SIMs, while noting that it is monitoring only the paging opportunities on the active PLMN. The mutual registration and paging request transfer functions between PLMNs enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs. and non-active SIMs, while noting that it is monitoring only the paging opportunities on the active PLMN. The mutual registration and paging request transfer functions between PLMNs enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs. MN, while noting that it is monitoring only the paging opportunities on the active PLMN. The mutual registration and paging request transfer functions between PLMNs enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs. MN, while noting that it is monitoring only the paging opportunities on the active PLMN. The mutual registration and paging request transfer functions between PLMNs enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs. enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs. enable the UE to operate in this way, thereby reducing the required power consumption and still being able to receive pages for multiple SIMs.

[0133] To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs. To link SIM1 and SIM2 in each PLMN, two different registration procedures, namely the partial registration procedure and the indirect registration procedure, are proposed in FIG. 9. These registration procedures, regardless of whether they are for SIM1 or SIM2, enable all paging requests to be received by the UE on the PLMN on which the UE is actively registered. In other words, paging requests for non-active SIMs are received during the paging opportunities of active SIMs. This solution solves the problem of paging collisions as described above because the UE can receive pages for multiple SIMs without the need to frequently switch connections between different PLMNs.

[0134] The SIM switching procedure is such that the UE establishes communication with a non-active PLMN to complete the processing of paging requests or uses the subscribed services associated with the non-active SIM. The SIM switching procedure is such that the UE establishes communication with a non-active PLMN to complete the processing of paging requests or uses the subscribed services associated with the non-active 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 if it were the result of the UE establishing a registration state with the core network. However, specific enhancements such as those proposed below for multi-SIM operation are applicable to indirect registration. This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). However, specific enhancements such as those proposed below for multi-SIM operation are applicable to indirect registration. This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). This registration procedure can put the UE in the RM-INACTIVE state and provide the UE with a set of temporary identifiers different from those returned from the general registration procedure. The procedure can link SIM1 and SIM2 together on PLMN2, similar to the link established by partial registration to enable paging request forwarding. Similar to partial registration, indirect registration may be initiated as part of general registration or stand-alone as a separate registration step (i.e., similar to steps S900 and S902a but for indirect registration). Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page Step S906: After a while, the UE receives a paging request for SIM2 from PLMN1. The paging request is sent from PLMN2, which forwarded the request to PLMN1. Note that detailed paging information can be sent from PLMN2 to PLMN1 within an encrypted NAS container to protect the UE's privacy. The paging request is found in the paging opportunity associated with SIM1, and when the UE reads the paging channel, the paging information is associated with SIM2. The paging information can include service type prioritization of the page to enable the UE to decide whether to continue processing the paging request. In addition, the UE can execute a service request procedure and receive an encrypted NAS container with service prioritization information to obtain more detailed paging information. Alternatively, the forwarded page The aging requirement may be received by the UE as a NAS notification through the user plane of the network. It may be received. Step S910: The UE notifies PLMN1 that it is necessary to execute the "SIM switching" procedure for PLMN2. PLMN1 recognizes SIM2 and has the linked information for SIM2, so PLMN1 assists the UE in executing the SIM switching. This procedure changes the registration state of the UE on PLMN1 to RM - INACTIVE, which indicates that the registration of the UE with PLMN1 is temporarily suspended for the purpose of the new registration state, sub - state, or operating mode of the RM - REGISTERED state proposed by this solution. The context of the UE in PLMN1 is retained for SIM1 to enable the UE to switch to using SIM2 on PLMN2. With the saved context, the UE can quickly resume operation when it returns to PLMN1. Other alternatives for the SIM switching procedure are also proposed, and the multi - SIM UE can notify the network to suspend the registration state of one SIM, as a result of which the UE can communicate with another SIM. During the suspension of the registration state, the paging mechanism can be changed, such as the network forwarding paging requests, filtering paging messages to the UE, and buffering downlink data. ... ... ... ... ... ... ... ... ... ... ... ... ... ... Step S912: The UE executes a periodic registration update procedure to change the registration state of SIM2 from RM - INACTIVE to RM - REGISTERED. Before executing the periodic registration update, the UE performs cell search, PLMN selection, and establishment of an RRC connection with RAN2. ... ... Note that it may be necessary to first execute procedures including etc. When receiving a registration acceptance response, then, the UE can execute either a service request procedure or a PDU session establishment procedure to retrieve the data associated with the paging request. The UE may execute a service request as an alternative to periodic registration updates. Step S914: After the UE completes the session to retrieve the data associated with the paging request, the UE can suspend the registration state of SIM2 as shown in step S1914a by executing a SIM switching procedure, and then reactivate the registration state of SIM1 as shown in step S191 4b.

[0136] Other enhancements not shown in Figure 9 are the inactive registration timer update procedure in which the UE can request an update of the registration timer of an inactive SIM through the active PLMN. This procedure provides the update that the UE is still connected to the active PLMN and can therefore receive the transferred paging request to the inactive PLMN. Another enhancement is to enable the UE to collect cell measurement information while attempting to establish a connection with the PLMN after a SIM switching procedure. These measurements can be provided to the PLMN either when the connection establishment is successful or, if the connection is not successful, through another PLMN. The cell measurements can be used by the network operator to determine the network coverage and, if necessary, improve the cellular coverage of the system. There are also other enhancements proposed for multi-SIM operation in a non-adjusted MNO.

[0137] When explaining multi-SIM operation, it is important to clearly distinguish which SIM / PLMN the UE is actively using at which point in time. Define the terms for use to clearly distinguish which SIM / PLMN the UE is actively using at which point in time. This is important. The terms "primary" and "secondary" refer to SIM prioritization as outlined by the UE policy or by the user via the GUI. These terms indicate which SIM has a higher priority (primary) than the UE's other SIM (secondary). The UE typically uses the primary SIM most of the time. The terms "active" or "inactive" refer to the SIM / PLMN that the UE is currently communicating with. In other words, the UE maintains a connection to the "active" PLMN and does not have a connection to the "inactive" PLMN. Using Figure 9 as an example, the use of the terms is explained below. · Primary SIM = SIM1 · Secondary SIM = SIM2 · Active SIM / PLMN = SIM1 / PLMN1 (in the case of steps 1 - 5), SIM2 / PLMN2 (in the case of steps 6 - 7) · Inactive SIM / PLMN = SIM2 / PLMN2 (in the case of steps 1 - 5), SIM1 / PLMN1 (in the case of steps 6 - 7) The terms "primary" and "secondary" can also be applied to PLMNs, for example, when it is not initially known which PLMN will be the active PLMN and which will be the inactive PLMN before the UE registers with the PLMN. The following solutions apply when the SIMs are from different operators. However, the solutions may be adapted to support SIMs from the same operator. · Primary SIM = SIM1 · Secondary SIM = SIM2 · Active SIM / PLMN = SIM1 / PLMN1 (for steps 1 - 5), SIM2 / 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" can also be applied to PLMNs, for example, when it is not initially known which PLMN will be the active PLMN and which will be the inactive PLMN before the UE registers with the PLMN. The following solutions apply when the SIMs are from different operators. However, the solutions may be adapted to support SIMs from the same operator. The terms "primary" and "secondary" can be applied to PLMNs, for example, when it is not initially known which PLMN will be the active PLMN and which will be the inactive PLMN before the UE registers with the PLMN. That is, which PLMN is the active PLMN and which is the inactive PLMN. It can also be applied.

[0138] The following solutions apply when the SIMs are from different operators. However, the solutions may be adapted to support SIMs from the same operator. However, the solutions may be adapted to support SIMs from the same operator. No. For example, the registration procedure is applied to the same PLMN and depends on the roaming agreement between PLMNs. It does not. The procedure still links the paging requests of SIM1 and SIM2 together, and the UE receives the paging request at the paging opportunity of the active SIM. Regardless of whether the SIMs are from the same or different operators, the registration state transition and SIM switching procedures remain the same. In the case of the same operator, the UE does not need to switch the connection between PLMNs after executing the SIM switching procedure. The following solutions are described in the context of 5GS, but it should be noted that the solutions can also be applied to EPS. For example, the proposed registration procedure can be executed in the EPS MME, which functions similarly to the 5GS AMF. In 5GS, NAS messaging is between the UE and the AMF, and in EPS, it should be noted that NAS messaging is between the UE and the MME. In EPS, the attach procedure and the HSS perform functions similar to the general registration procedure and the UDM in 5GS, respectively. The RAN nodes are eNodeB for EPS and gNodeB for 5GS. Similarly, the RM - INACTIVE state proposed herein for 5GS can be a new state such as EMM - INACTIVE in EPS. The SIM switching procedure can also be executed in both EPS and 5GS, and the multi - SIM policy or information elements can be incorporated into both systems. The solutions in this disclosure describe how policies can be delivered from the PCF to the UE via NAS messaging. In EPS, IP - based policies are delivered from the ANDSF server.

[0139] The following solutions are described in the context of 5GS, but it should be noted that the solutions can also be applied to EPS. For example, the proposed registration procedure can be executed in the EPS MME, which functions similarly to the 5GS AMF. In 5GS, NAS messaging is between the UE and the AMF, and in EPS, it should be noted that NAS messaging is between the UE and the MME. In EPS, the attach procedure and the HSS perform functions similar to the general registration procedure and the UDM in 5GS, respectively. The RAN nodes are eNodeB for EPS and gNodeB for 5GS. Similarly, the RM - INACTIVE state proposed herein for 5GS can be a new state such as EMM - INACTIVE in EPS. The SIM switching procedure can also be executed in both EPS and 5GS, and the multi - SIM policy or information elements can be incorporated into both systems. The solutions in this disclosure describe how policies can be delivered from the PCF to the UE via NAS messaging. In EPS, IP - based policies are delivered from the ANDSF server. The policy can be distributed to the U via a procedure or via an information element transmitted within an NAS message When applied to an EPS system, embodiments are provided to illustrate some of these enhancements

[0140] Different aspects of the LTE system are enhanced to support the use of multi-SIM UEs The first aspect is applied to the attach procedure that the UE executes to register with the core network These enhancements to the attach procedure are proposed, namely partial attach , indirect attach, and MUSIM attach. These attach procedure enhancements include the registration of the multi-SIM used within the UE . Partial attach registers the secondary SIM with the HSS of the corresponding PLMN that triggers the paging request transfer originating from the HSS. On the other hand , indirect attach registers the secondary SIM with the MME of the corresponding PLMN and can always establish a default bearer for the PDN connection . Finally, with the MUSIM attach enhancement, the UE can indicate to the core network the need to execute the attachment procedure for multiple SIMs in a single request, thereby triggering the execution of either the partial or indirect attachment procedure for the secondary SIM .

[0141] In addition, a new registration mode of operation enabled for multi-SIM UEs, namely EMM-INACTIVE, a new LTE EMM state is proposed to be added to the UE and the MME . This new registration state means that the UE operating with the secondary SIM is registered with the corresponding PLMN but is not actively connected to that PLMN . ​​​​Indicates that it has not continued. Furthermore, by the above-described attachment procedure enhancement, paging requirements transfer is enabled. Paging request transfer refers to the process in which a paging request for an inactive SIM by a non-active PLMN is transferred to the active PLMN in order to page the UE. All of these LTE system enhancements are the same as the 5G enhancements and will be described in more detail below. The present disclosure refers to EMM-INACTIVE as a new state in the EMM state model, but it should be noted that for the current LTE configuration, it may be more feasible to be a sub-state or mode of operation within the EMM-REGISTERED state. This sub-state or mode of operation may be referred to as the "inactive registration" sub-state or mode of EMM-REGISTERED. It should also be noted that the UE and the MME can maintain separate EMM and ECM states for each SIM. Once the registration state is established for each of the SIMs of the multi-SIM UE, the function of paging request transfer is enabled to eliminate the occurrence of paging collisions. When data is available on an inactive SIM, the corresponding PLMN transfers the paging request to the UE through the active PLMN. Within the active PLMN, the calculation of the paging opportunity is such that the UE can receive paging requests for multiple SIMs while only needing to monitor for one paging opportunity. The paging information can be sent, in some cases, via NAS notifications as described below.

[0142]

[0143]

[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]. As outlined, a complete registration with the secondary PLMN is performed through the primary PLMN. The indirect registration procedure also causes all paging requests to be forwarded to the primary PLMN when the UE is not actively communicating with the secondary PLMN. Notify the secondary PLMN. In both registration procedures, the RM state of the UE with the secondary PLMN transitions from RM-DEREGISTERED to RM-INACTIVE. In the case of indirect registration, the AMF is assigned to serve the UE, which is different from a partial registration where the AMF is not assigned to serve the UE. As in the 5G registration procedure, the UE needs to perform an attach procedure with the core network of the LTE system in order to be able to receive services from the network. The attach procedure authenticates the UE and establishes a context for the UE to communicate securely with the network,

[0147] thereby registering the UE with the core network. In the case of multi-SIM, it is proposed that the attach procedure be enhanced to support the registration of multiple SIMs. In this specification, 1) partial attachment, 2) indirect attachment, and 3) enhanced MUSIM attachment are described. MUSIM attachment combines multiple attachment requests into a single request, for example, an attachment request for the primary SIM and one or more attachment requests for the secondary SIM. The MUSIM attachment procedure can also be applied similarly to the 5G system. For all the registration and attach procedures described, the UE uses the information configured in the UE

[0148] ​​​​​Multi-SIM support information can be included in a corresponding request message (e.g., by a user). The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below. The support information can be used by the network to enhance the existing paging mechanism for multi-SIM operation. For example, the support information can provide prioritization information for notifying whether and when to page the UE when downlink data is available for a specific SIM. Further, the support information can provide information on how the network can assign identifiers corresponding to paging opportunities to avoid paging collisions among multiple SIMs. Multi-SIM support information will be described in more detail below.

[0149] (Partial registration) The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. The UE performs partial registration mainly to configure the secondary PLMN so that all paging requests are transferred to the UE through the primary PLMN whenever the RM state of the UE with the secondary PLMN is RM - INACTIVE. By this procedure, the UE can receive all paging requests for paging opportunities associated with the active SIM, regardless of whether the paging request is for SIM1 or SIM2, regardless of the PLMN with which the UE is actively communicating. As a result, the UE does not need to switch the network connection between SIMs. In fact, this procedure guarantees that the UE receives all paging requests, but the procedure for switching the UE between SIMs may miss paging requests if the switching timing is not aligned with the timing of the paging requests. Note that the split registration enhancement enables the page request transfer function to originate from the UDM, which is a new function added to the UDM. It should be noted that it is possible to originate from

[0150] Figure 10 shows a UE that starts the partial registration procedure for SIM2 through PLMN1. The figure shows two cases in which partial registration of SIM2 can be performed, namely 1. Both S IMs are installed together and the partial registration request is part of the initial registration request (which is called MUSIM registration) or 2. When SIM2 is installed after SIM1 is installed and the UE has already performed the initial registration of SIM1. installed and the UE has already performed the initial registration of SIM1. installed, and the UE has already performed the initial registration of SIM1.

[0151] Step S1002: The UE registers with the PLMN1 of 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 simultaneously, the UE may include a multi-SIM indication with an appropriate SIM2 identifier (e.g., SUPI (e.g., IMSI), G UTI, 5G-S-TMSI, or SUCI) when the UE registers with the PLMN1 of SIM1. In this case, it is proposed that the partial registration request be integrated as part of the general registration procedure (general registration procedure described in TS 2 3.502[2]) performed for SIM1. This procedure may be called MUSIM registration. The addition to the initial registration request is, as described above, to include a multi-SIM indication, a partial registration indicator, and one or more SIM2 identifiers. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator. as above, to include a multi-SIM indication, a partial registration indicator, and one or more SIM2 identifiers. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator. Often, the partial registration indicator may be incorporated within the registration type parameter. The message may further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and which should be used to register to the non active PLMN. In this case, the process skips to step S1006. Step S1004: After the UE successfully registers to PLMN1 of SIM1 and SIM2 is installed in the UE and the UE is a multi-SIM device, in some cases, a partial registration request may be initiated by the UE to notify that it includes a multi-SIM indication and a SIM2 identifier. The registration type of this request may be a partial registration or a partial registration indicator may be provided. At this point, the RM state of SIM1 is RM- REGISTERED, and for SIM2 (with PLMN2), it is RM-DERE GISTERED. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI. The partial registration request may be a newly defined procedure or may be incorporated as part of the general registration procedure. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand alone indicator. The multi-SIM indicator can be used by the network entity to check and select an appropriate network entity that supports multi-SIM operation during the registration procedure. Step S1006: RAN1 uses the previously established N2 interface for SIM1 Transfer the partial registration request to AMF1 via the base. In the case of MUSIM registration, RAN1 selects AMF1 to process the request. Step S1008: Due to the presence of the multi-SIM indication and / or the fact that UE102 requests partial registration AMF1 904 selects AUSF2 908 and requests it to authenticate UE102 for SIM2 by sending the SIM2 identifier to AUSF2 908 along with the multi-SIM indication and the partial registration indicator. If the request was a M USIM registration, AMF1 904 first registers SIM1 and then can send a partial registration request for SIM 2. It is assumed that an roaming agreement is established between PLMN1 and PLMN2, and the AMF within each PLMN may be configured using the contact information of the AUSF of the other PLMN to transfer the partial registration request. Note that the communication between AMF1 904 and AUSF2 908 may also be assumed to be secured via the N32 interface through the corresponding PLMN's SEPPS. Step S1010: AMF1 904 transfers the partial registration request to AUSF2 908 and may include the registration type set for partial registration, or the multi-SI M indication including the partial registration indicator, which may be encoded as an option for the preferred network behavior, the SIM2 identifier, the AMF1 ID and UE ID indicating that the UE with SIM1 has been authenticated for PLMN1, and the PL MN1 AMF context information that PLMN2 can transfer future paging requests for SIM2. In step S1002, the registration type was set for the initial registration of SIM1, but this registration request is for SIM2, so ​​​​​​Note that the change from the initial registration of this request to the partial registration is for AUSF2 9 08. Alternatively, the registration type may be set as the initial registration, and a partial registration indicator may be provided in the request. The registration type in step S1002 may be encoded as an initial registration with partial registration. Step S1012: AUSF2 908 can perform the authentication of the UE for SIM2 and create or update the subscription information in UDM2 910. UDM2 91 0 is used to provision UE102 with a temporary identifier for SIM2 to indicate when the paging request is targeted at SIM2. In addition, the RM state of SIM2 is updated to RM - INACTIVE to enable the transfer of paging requests to the UE through PLMN1. The RM state in this case can be an indication saved in the subscription data of the UDM to indicate that the paging request transfer is enabled. Step S1014: After AUSF2 authenticates the UE of SIM2, a partial registration acceptance message is returned to AMF1. The partial registration acceptance message may be a modified registration acceptance message. AUSF2 includes the following information in the acceptance message, namely, an indication that the authentication of SIM2 was successful, the temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM - DEREGISTERED to RM - INACTIVE, a confirmation response of support for receiving paging requests transferred for SIM1 by PLMN1, the contact information of the MME for receiving paging requests from PLMN1, and the registration timer of SIM2. ​​​​​​​​​​It is possible. The temporary identifier for the UE is used to page the UE whenever there is a page for SIM2 while the UE is actively registered with PLMN1. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of UDM. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of UDM. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message includes an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. Step S1016: AMF1 forwards the partial registration acceptance message to the UE through RAN1, including the information returned from AUSF2 to AMF1. The acceptance message may include an indication of successful authentication of SIM2, a temporary identifier assigned to the UE for SIM2 by UDM2, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-ACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 using the paging request forwarding function whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity occurs overlapping with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. AMF1 may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs. However, it is possible to assign the same temporary identifier to all SIMs associated with the UE. The RM state of the UE for each SIM is updated by the UE, i.e., RM-REGISTERED for SIM1 and RM-INACTIVE for SIM2, which should match that of AMF1. This procedure proposes that the UDM assigns a temporary identifier to the UE and the temporary identifier is provided to the UE. This temporary identifier may be a new type of 5G-GUTI. This 5G-GUTI can be formatted in a way that is compatible with the existing 5G-GUTI format. For example, RM-REGISTERED and RM-INACTIVE for SIM2 should match that of AMF1. should match that of AMF1.

[0152] This procedure proposes that the UDM assigns a temporary identifier to the UE and the temporary identifier is provided to the UE. This temporary identifier may be a new type of 5G-GUTI. This 5G-GUTI can be formatted in a way that is compatible with the existing 5G-GUTI format. For example, This temporary identifier may be a new type of 5G-GUTI. This 5G-GUTI can be formatted in a way that is compatible with the existing 5G-GUTI format. For example, This 5G-GUTI can be formatted in a way that is compatible with the existing 5G-GUTI format. For example, For example,

[0153] The GUAMI can be resolved by the UDM / UDR. <mcc>and <mnc>only may also include. The fact that GUAMI does not include <AMF Region ID>, <AMF Set ID>, and <AMF Pointer> may indicate that the 5G-GUTI has been allocated by the UDM .

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

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

[0156] Step S1102: The UE registers with PLMN1 of SIM1 with the registration type of initial registration. At this time, only SIM1 is installed in the UE. However, if both SIM1 and SIM2 are installed simultaneously, when the UE registers with PLMN1 of SIM1, the UE can include a multi-SIM indication, a partial registration indicator, and an appropriate SIM2 identifier (e.g., SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI). In this case, it is proposed that the partial registration request be integrated as part of the general registration procedure (the general registration procedure described in TS 23.502[2]) to be executed for SIM1. This procedure may be called MUSIM registration. The addition to the initial registration request is, as described above, a multi-SIM indication, a partial registration indicator, and 1 ​​​​​​​​or including a plurality of SIM2 identifiers. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter, or may be a stand-alone indicator, and the partial registration indicator may be incorporated within the registration type parameter. The message can further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and whether it should be used to register with a non-active PLMN. In this case, the process skips to step S1106. It may be encoded as an option of the priority network behavior parameter, or may be a stand-alone indicator. The partial registration indicator may be incorporated within the registration type parameter. The message can further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and whether it should be used to register with a non-active PLMN. In this case, the process skips to step S1106. It may be encoded as an option of the priority network behavior parameter, or may be a stand-alone indicator. The partial registration indicator may be incorporated within the registration type parameter. The message can further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and whether it should be used to register with a non-active PLMN. In this case, the process skips to step S1106. The message can further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and whether it should be used to register with a non-active PLMN. In this case, the process skips to step S1106. Step S1104: After the UE successfully registers with PLMN1 of SIM1 and SIM2 is installed in the UE, in some cases, since the UE is a multi-SIM device and includes a multi-SIM indication and SIM2 identifier, a partial registration request may be initiated by the UE to notify this. The registration type of this request may be partial registration, or a partial registration indicator may be provided. At this point, the RM state of SIM1 is RM-REGISTERED, and for SIM2 (accompanied by PLMN2), it is RM-DEREGISTERED. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI. The partial registration request may be a newly defined procedure or may be incorporated as part of the general registration procedure. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator. The multi-SIM indicator checks and selects an appropriate network entity that supports multi-SIM operation during the registration procedure. After the UE successfully registers with PLMN1 of SIM1 and SIM2 is installed in the UE, in some cases, since the UE is a multi-SIM device and includes a multi-SIM indication and SIM2 identifier, a partial registration request may be initiated by the UE to notify this. After the UE successfully registers with PLMN1 of SIM1 and SIM2 is installed in the UE, in some cases, since the UE is a multi-SIM device and includes a multi-SIM indication and SIM2 identifier, a partial registration request may be initiated by the UE to notify this. The registration type of this request may be partial registration, or a partial registration indicator may be provided. At this point, the RM state of SIM1 is RM-REGISTERED, and for SIM2 (accompanied by PLMN2), it is RM-DEREGISTERED. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or SUCI. The partial registration request may be a newly defined procedure or may be incorporated as part of the general registration procedure. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator. The multi-SIM indicator checks and selects an appropriate network entity that supports multi-SIM operation during the registration procedure. The multi-SIM indicator checks and selects an appropriate network entity that supports multi-SIM operation during the registration procedure. which can be used by a network entity for Step S1106: RAN1 transfers a partial registration request to AMF1 via the previously established N2 interface for SIM1. In the case of MUSIM registration, RAN1 selects AMF1 to process the request. Step S1108: AMF1 determines which UDM to connect to by examining the SIM2 identifier. The SIM2 identifier may include the MCC and MNC used to determine the UDM to be contacted for this purpose. Step S1110: AMF1 transfers the partial registration request to UDM2, and the registration type set for the partial registration, or the partial registration indicator, multi-SIM indication may be encoded as options for the priority network behavior, and may include the SIM2 identifier, the AMF1 ID and UE ID indicating that the UE with SIM1 has been authenticated for PLMN1, and the context information of the AMF of PLMN1 that can transfer future paging requests for PLMN2 to SIM 2, etc. In step S1102, the registration type was set for the initial registration of SIM1, but this registration request is for SIM2, so it should be noted that this is a change from the initial registration of the registration type to a partial registration. Alternatively, the registration type may be set as the initial registration, and a partial registration indicator may be added to the request. The registration type from step S1102 may be encoded as an initial registration with partial registration. registration. Note that this is a change from the initial registration of the registration type to a partial registration. Alternatively, the registration type may be set as the initial registration, and a partial registration indicator may be added to the request. The registration type from step S1102 may be encoded as an initial registration with partial registration. Step S1112: UDM2 responds to AMF1, and AMF1 responds to the UE. The response indicates to the UE whether the UE is permitted to be partially registered and indicates to the UE that the authentication is pending. The message also indicates from the network to start the authentication for It includes a timer that indicates to the UE how long it needs to wait until it receives a request. If the timer expires before the UE receives a request to start authentication from the network work, the UE ignores the request to perform authentication unless it sends a partial registration request. UDM2 can provision the UE with a temporary identifier for SIM2 that is used to indicate when a paging request targets SIM2. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. The RM state of SIM2 may not be updated or may be updated to a state indicating that authentication is pending Step S1114: The AMF starts slice-specific authentication with the UE and the AUSF of PLMN2. This procedure is described in the section entitled "Slice-Specific Authentication and Authorization". UDM2 can provide the function of AAA-S 802 in the procedure. UDM2 can provide a temporary identifier to the UE by providing the temporary identifier to the AMF. The AMF can provide the temporary identifier to the UE in the EAP success message. Also, a registration timer for SIM2 may be provided. FIG. 8 also shows AAA-P 804.

[0157] In partial registration, there is no AMF assigned to provide services to the UE, and as a result, the UDM assigns a temporary UE ID to the UE. This temporary UE ID is valid while there is activity of the UE and corresponds to the non-active PLMN and RM-INACTI ​​​​​​​​​​​​​​It is used to page the UE at any time when in the VE state. In this case, R The M state may be an indication saved in the subscription data of the UDM to indicate that paging request forwarding is enabled. In this case, note that the U DM of the non-active PLMN can send a paging message to the AMF of the active PLM N with a temporary UE ID assigned to the UE during partial registration. In addition, the UDM can return the identifier and / or contact information of the default AMF in response to the partial registration request. This default AMF can be used to send a paging request for the SIM when the UE is in the PLMN and RM-INACTIVE state to the AM F of the active PLMN where the UE is currently registered. (Partial attachment) UEs using multi-SIM can use partial attachment enhancements to register other secondary SIMs to their corresponding PLMNs without registering the primary SIM to the current PLMN only . Figure 24 shows the procedure for partial attachment enhancement. This figure shows that partial attachment is performed separately from the initial attachment of SIM1. However, for example, as described later, in a MUSIM attachment request, it may also be combined as one attachment procedure

[0158] (Partial attachment) UEs using multi-SIM can use partial attachment enhancements to register other secondary SIMs to their corresponding PLMNs without registering the primary SIM to the current PLMN only . Figure 24 shows the procedure for partial attachment enhancement. This figure shows that partial attachment is performed separately from the initial attachment of SIM1. However, for example, as described later, in a MUSIM attachment request, it may also be combined as one attachment procedure . In addition, partial attachment enhancement can support partially attaching multiple secondary SIMs by executing steps S24 06 to S2414 for each SIM. Note that partial attachment enhancement enables the paging request forwarding function to be derived from the HSS, which is a new function added to the HSS . In addition, partial attachment enhancement can support partially attaching multiple secondary SIMs by executing steps S24 06 to S2414 for each SIM. Note that partial attachment enhancement enables the paging request forwarding function to be derived from the HSS, which is a new function added to the HSS . . .

[0159] Step S2402: The UE first attaches to PLMN1 using SIM1. PLMN1 is considered the active PLMN, and SIM1 is considered the primary SIM. This step may be performed first when only SIM1 is installed in the UE. If two or more SIMs are installed in the UE simultaneously, a combined attach procedure may be performed to register multiple SIMs together with a single attach request. This combined attach request, called a MUSIM attach, may include, in addition to the information of a normal attach request, a multi-SIM indicator, a partial attach indicator, and appropriate SIM identifiers (e.g., IMSI, GUTI, etc.) of each SIM. In this case, the partial attach is integrated as part of the attach procedure from TS 23.401 [9]. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator, and the partial attach indicator may be carried in the attach type parameter. The message can further indicate which SIM is the primary SIM, which SIMs are secondary SIMs, and which should be used to register to non-active PLMNs. In the case of a combined attach request, the procedure skips to step S2406. Step S2404: After a while, a partial attach procedure is initiated. For example, this may be done based on a request from an application on the UE through the GUI or API through the configuration of the eSIM by inserting a physical SIM, or when SIM2 is added to the UE immediately after the completion of the attach procedure by PLMN1. SIM2 is the secondary SIM. SIM. SIM. SIM. SIM. Step S2404: After a while, a partial attach procedure is initiated. For example, this may be done based on a request from an application on the UE through the GUI or API through the configuration of the eSIM by inserting a physical SIM, or when SIM2 is added to the UE immediately after the completion of the attach procedure by PLMN1. SIM2 is the secondary SIM. SIM. is regarded as a candidate SIM and is associated with PLMN2. PLMN2 is an inactive P LMN. Then the UE performs a partial attach request to PLMN2 through PLMN1. This request can include a multi-SIM indicator and appropriate SIM identifiers (e.g., IMSI, GUTI, etc.) for each SIM. The multi-SIM indicator can be encoded as an option of the priority network behavior parameter or can be a stand-alone indicator. The multi-SIM indicator is used by the network entity to check and select an appropriate network entity that supports multi-SIM operation during the attach procedure and can be used to enable paging request transfer. Step S2406: In response to the partial attach request or partial attach indication, the MME of PLMN1 selects an appropriate HSS to process the partial attach request for each SIM. The identifier provided for SIM2 may include MCC and MNC, or may be resolved to the MCC and MNC used to determine the HSS to be contacted. The MME of PLMN1 may be provisioned with contact information of other HSSs of different PLMNs due to core network configuration, roaming agreement, or other mechanisms that support multi-SIM operation. As a result, the MME can transfer any partial attach message of those candidate SIMs to the default HSS of other PLMNs. Step S2408: MME1 2402 sends the partial attach request to the selected HSS. The request includes a partial attach indicator, an option of the priority network operation ​ A multi-SIM indicator that can be encoded, a SIM2 identifier, a UE with SIM1 is in P including an MME1 ID and a UE ID for indicating that it has been authenticated with respect to PLMN1, etc. MME1 can further provide context information of the MME of PLMN1 where PLMN2 can transfer a paging request for SIM2. This MME in PLMN1 can be configured to support paging request transfer, and transfer a paging request to an appropriate network entity (e.g., the MME to which the UE attaches in the case of UE mobility) from PLMN2 so that the UE can receive the page. It may be possible. Step S2410: The HSS of PLMN2 performs authentication of the UE for SIM2, and can store context information about the UE, such as information obtained from the authentication procedure and information provided by MME1. HSS2 2404 can also assign a temporary identifier to the UE for SIM2, and this identifier can be used by HSS2 to identify paging requests for SIM2 that will be forwarded to the UE through PLMN1. Finally, to indicate that the UE with SIM2 is registered with PLMN2 but not communicating actively with PLMN2, the EMM state of SIM2 is set to EMM-INACTIVE in HSS2. The EMM state in this case can be an indication stored in the subscription data of the HSS to indicate that paging request transfer is enabled. Step S2412: The HSS of PLMN2 returns a partial attach acceptance response indicating the result of the partial attach procedure to the MME of PLMN1. The response indicates that the authentication of SIM2 has been successful. Step S2410: The HSS of PLMN2 performs authentication of the UE for SIM2, and can store context information about the UE, such as information obtained from the authentication procedure and information provided by MME1. The HSS2 2404 can also assign a temporary identifier to the UE for SIM2, and this identifier can be used by HSS2 to identify paging requests for SIM2 that will be forwarded to the UE through PLMN1. Finally, to indicate that the UE with SIM2 is registered with PLMN2 but not communicating actively with PLMN2, the EMM state of SIM2 is set to EMM-INACTIVE in HSS2. This EMM state in this case can be an indication stored in the subscription data of the HSS to indicate that paging request transfer is enabled. Step S2412: The HSS of PLMN2 returns a partial attach acceptance response indicating the result of the partial attach procedure to the MME of PLMN1. The response indicates that the authentication of SIM2 has been successful. Step S2412: The HSS of PLMN2 returns a partial attach acceptance response indicating the result of the partial attach procedure to the MME of PLMN1. The response indicates that the authentication of SIM2 has been successful. Indication, the temporary identifier assigned for SIM2 by HSS2, for SIM2 Indication that the EMM state of the UE has changed from EMM-DEREGISTERED to EMM-INACTIVE Indication that the paging request transferred for SIM1 by PLMN1 Confirmation response for support to receive, for receiving a paging request from PLMN1 The contact information of the MME, and the registration timer of SIM2 can be included. If the partial attach is not accepted, the response can include further information detailing the reason why the attach was not accepted In addition, the contact information of the default MME can be included in the acceptance message to notify MME 1 that there is a possibility that future paging requests may originate from the default MME instead of the HSS Step S2414: The MME of PLMN1 may return a modified attach acceptance message that provides additional information regarding the status of the partial attach procedure, a partial attach acceptance message to the UE. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM The response message can include an indication that the authentication of SIM2 was successful, the temporary identifier assigned to SIM2, the indication that the EMM state of the UE of SIM2 has changed from EMM-DEREGISTERED to EMM-INACTIVE, and information returned from the HSS of PLMN2 such as the registration timer of SIM2 The temporary identifier is used to identify future paging requests for SIM2 transferred to PLMN1. In addition, the MME of PLMN1 uses the temporary identifier assigned by PLMN2 instead, for paging the UE can be used. The temporary identifier is used to identify future paging requests for SIM2 transferred to PLMN1. In addition, the MME of PLMN1 uses the temporary identifier assigned by PLMN2 instead, for paging the UE A separate temporary identifier can be assigned for the possible SIM2. This temporary identifier assignment may be such that the associated paging opportunity overlaps with the paging opportunity associated with SIM1. As a result, the UE may only need to monitor one paging opportunity to receive paging for both SIM1 and SIM2. The MME, alternatively, can maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs, while assigning the same temporary identifier to all SIMs associated with the UE. The EMM state of the UE for each SIM is updated. In this scenario, the EMM state of SIM1 is EMM-REGISTERED, and for SIM2 it is EMM-INACTIVE. Similarly, the EMM state in the MME of PLMN1 is EMM-REGISTERED for SIM1 and EMM-INACTIVE for SIM2. The MME of PLMN1 can maintain separate EMM states for SIM1 and SIM2 respectively.

[0160] (Indirect registration) The indirect registration procedure is a functional combination of the partial registration procedure and the general registration procedure. Both the partial registration procedure and the indirect registration procedure include multi-SIM indications and SIM2 identifiers for configuring PLMN2 to forward paging requests to the UE via PLMN1. However, the indicators for each procedure are different (i.e., indirect as opposed to partial), and the indirect registration procedure provides additional functionality of the PLMN for allocating network slices and providing UE policy information to the UE. Indirect registration also assigns an AMF to serve the UE.

[0161] Figure 12 shows a UE that starts the indirect registration procedure for SIM2 through PLMN1. Note that Similar to the partial registration procedure, the indirect registration procedure can be integrated with the general registration procedure to register both SIM 1 (direct registration) and SIM2 (indirect registration) together in one request. This procedure can be called MUSIM registration, as described below. Similarly, the indirect registration procedure can be executed separately from the general registration procedure.

[0162] Step S1202: The UE registers with PLMN1 of SIM1 with the registration type of initial registration. At this time, only SIM1 is installed in the UE. However, if both SIM1 and SIM2 are installed simultaneously, the UE may also include, when the UE registers with PLMN1 of SIM1, a multi-SIM indication, an indirect registration indicator, an appropriate SIM2 identifier (e.g., SUPI (e.g., IMSI), GUTI, 5G-S-TMSI, or S UCI), and the identification information of PLMN2. In this case, the indirect registration request for SIM2 is part of the general registration procedure of SIM1, e.g., MUSIM registration. The addition to the initial registration request is to include a multi-SIM indication, an indirect registration indicator, a SIM2 identifier, and the identification information of P LMN2. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or may be a stand-alone indicator, and the indirect registration indicator may be incorporated into the registration type parameter. The message further indicates which SIM is the primary SIM, which SIM is the secondary S IM, and which should be used to register with the non-active PLMN. behavior parameter or may be a stand-alone indicator, and the indirect registration indicator may be incorporated into the registration type parameter. The message further indicates which SIM is the primary SIM, which SIM is the secondary S IM, and which should be used to register with the non-active PLMN. IM, and which should be used to register with the non-active PLMN. IM, and which should be used to register with the non-active PLMN. ​​This can be done. In this case, the procedure skips to step S1206, and both the general registration of SIM1 and the indirect registration of SIM2 are executed simultaneously, or may be executed consecutively, for example, the registration of SIM1 followed by the registration of SIM2. After the UE has successfully registered with PLMN1 of SIM1 and SIM2 is installed in the UE, in some cases, since the UE is a multi-SIM device and needs to notify the multi-SIM indication, SIM2 identifier, and identification information of PLMN2, an indirect registration request can be initiated by the UE. The registration type of this request may be indirect registration, or an indirect registration indicator may be provided. At this point, the RM state of SIM1 is RM-REGISTERED, and for SIM2 (accompanied by PLMN2), it is RM-DEREGISTERED. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (for example, IMSI), GUTI, 5G-S-TMSI, or SUCI. The indirect registration request may be a newly defined procedure, or may be part of the general registration procedure with the registration type set as indirect registration, or may be incorporated including the indirect registration indicator. The multi-SIM indicator may be encoded as an option for the priority network behavior parameter and may be a stand-alone indicator. The multi-SIM indicator can be used by the network entity to check and select the appropriate network entity that supports multi-SIM operation during the registration procedure. Step S1204: After the UE has successfully registered with PLMN1 of SIM1 and SIM2 is installed in the UE, in some cases, since the UE is a multi-SIM device and needs to notify the multi-SIM indication, SIM2 identifier, and identification information of PLMN2, an indirect registration request can be initiated by the UE. The registration type of this request may be indirect registration, or an indirect registration indicator may be provided. At this point, the RM state of SIM1 is RM-REGISTERED, and for SIM2 (accompanied by PLMN2), it is RM-DEREGISTERED. The SIM2 identifier is used by PLMN2 to authenticate SIM2 for the UE and may consist of SUPI (for example, IMSI), GUTI, 5G-S-TMSI, or SUCI. The indirect registration request may be a newly defined procedure, or may be part of the general registration procedure with the registration type set as indirect registration, or may be incorporated including the indirect registration indicator. The multi-SIM indicator may be encoded as an option for the priority network behavior parameter and may be a stand-alone indicator. The multi-SIM indicator can be used by the network entity to check and select the appropriate network entity that supports multi-SIM operation during the registration procedure. Step S1206: RAN1 902 performs the previously established N2 i Transfer general or indirect registration requests to AMF1 904 via the interface. MUS In the case of IM registration, RAN1 902 selects AMF1 904 to process the request. Step S1208: AMF1 904 executes steps S1008 to S1014 in FIG. 10 or FIG. 11 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. from S1014 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. from S1014 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. from S1014 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. from S1014 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. from S1014 to authenticate the UE of SIM2. This step completes the partial registration procedure of the UE for SIM2 and enables PLMN2 to transfer paging requests originating from UDM2 to the UE. In addition, the contact information of the default AMF may be included in the acceptance message to notify AMF1 that future paging requests may originate from the default AMF instead of the UDM. Steps S1210a and b: AMF1 requests the UE's slice selection subscription data from UDM2, and UDM2 responds with the slice selection data to AMF1. Steps S1210a and b: AMF1 requests the UE's slice selection subscription data from UDM2, and UDM2 responds with the slice selection data to AMF1. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1212a and b: AMF1 uses the slice selection data retrieved from steps S1210a and b to execute an Nnssf_NSSelection_Get request to NSSF2 1204 through NSSF1 1202. AMF1 provides the requested NSSAI and other slice-related parameters to NSSF2. NSSF2 returns a response including the permitted NSSAI and other NSSAI-related parameters, as well as the NRF 302 for the AMF1 to select the NF / service of the network slice instance. Steps S1214a and b: AMF1 queries NRF2 1208 to NRF1 1206 to find an appropriate AMF to serve the UE's indirect registration request. NRF2 returns a list of potential AMFs within PLMN2 to process the indirect registration request. Steps S1214a and b: AMF1 queries NRF2 1208 to NRF1 1206 to find an appropriate AMF to serve the UE's indirect registration request. NRF2 returns a list of potential AMFs within PLMN2 to process the indirect registration request. Steps S1214a and b: AMF1 queries NRF2 1208 to NRF1 1206 to find an appropriate AMF to serve the UE's indirect registration request. NRF2 returns a list of potential AMFs within PLMN2 to process the indirect registration request. Return. Step S1216: AMF1 transfers the indirect registration request to AMF2, and AMF2 executes the general registration procedure of the UE using SIM 2. This general registration procedure may also include multi-SIM indication, indirect registration indicator, and the appropriate SIM2 identifier or temporary identifier received in step S1208. AMF1 may obtain the contact information of AMF2 through NRF 2 from step S1214, or through UDM2 from step S1208, through a network configuration that supports multi-SIM operation (e.g., through a roaming agreement). Upon completion of the general registration procedure, the registration acceptance message returned to AMF1 indicates that the authentication of SIM2 was successful, the temporary identifier assigned to the UE for SIM2 by AMF2, the indication that the RM state of the UE for SIM2 has changed from RM-D REGISTERED to RM-INACTIVE, confirmation of support for receiving paging requests transferred for SIM1 by PLMN 1, the contact information of the MME for receiving paging requests from PLMN1, and the registration timer for SIM2. The temporary identifier for the UE is used to page the UE from PLMN 2 whenever there is a page for SIM2 while the UE is actively registered with PLMN N1. Alternatively, AMF1 may assign a separate temporary identifier to SIM2 that can be used to page the UE with PLMN1 instead. This assignment of the temporary identifier may be such that the associated paging opportunity overlaps with the paging opportunity associated with SIM1. Thus, ... ... ... ... ... ... ... Thus, the UE only needs to monitor one paging opportunity to receive pages of both SIM1 and SIM2. AMF1, as an alternative, maintains the fact that the UE only needs to monitor one paging opportunity and can receive pages of all SIMs, while assigning the same temporary identifier to all SIMs associated with the UE. The RM state of the UE for each SIM is updated at the UE, i.e., RM-REGISTERED for SIM1 and RM-INACTIVE for SIM2, which should match that of AMF1. Step S1218: AMF1 returns the registration acceptance message received from AMF2 to RAN1, and RAN1 forwards the registration acceptance message to the UE. The acceptance message may include an indication of successful authentication of SIM2, a general registration procedure, or a temporary identifier assigned by AMF1 to the UE for SIM2, an indication that the RM state of the UE for SIM2 has been changed from RM-DEREGISTERED to RM-INACTIVE, and a registration timer for SIM2. The temporary identifier for the UE is used to page the UE whenever there is a page for SIM2 while the UE is actively registered with PLMN1.

[0163] An alternative procedure for indirect registration is shown in FIG. 13. AMF1 is provisioned with the contact information of AMF2 as part of the support for multi-SIM operation. AMF2 is configured as the default AMF of PLMN2 for AMF1 to contact in the case of multi-SIM support. When receiving an indirect registration request, AMF1 contacts the contact list of PLMN2. ​​​​​​​​​​​​​​​​Search for the subscription and directly transfer the indirect registration request to AMF2. AMF2 serves the UE based on the request transferred from AM F1 and selects another AMF within PLMN2. From that point on, the general registration procedure from TS 23.502 [2] is executed, with updates due to changes to support indirect registration.

[0164] Steps S1302 to S1306: These steps are the same steps as those executed for the procedure shown in FIG. 12. Step S1308: AMF1 is provisioned with the contact information of AMF2 and sends the indirect registration of the UE for SIM2 to PLMN2. AMF1 makes this decision based on the presence of the multi-SIM indication, or whether the registration type or indicator is set to indirect registration. The indirect registration request may be encoded with the registration type set to indirect registration, or an indirect registration indicator, and the multi-SIM indication as an option for the preferred network behavior, including the SIM2 identifier, the AMF1 ID and UE ID indicating that the UE with SIM1 has been authenticated to PLMN1, and the context information of the AMF of PLMN1 to which PLMN2 can transfer future paging requests for SIM2. If the request in step S1302 is a general registration request, AMF1 generates a new indirect registration request with the registration type that can be set to indirect registration, and provides both the multi-SIM indication and the SIM2 identifier. Alternatively, the registration type may be set as an initial registration, or an indirect registration indicator may be added to the request. The registration type may be encoded as an initial registration with partial registration. Step S1310: The general registration procedure from TS 23.502[2] is executed for SIM2 on PLMN2, but is modified to include functionality to support indirect registration as outlined in Figure 12. Step S1312: AMF1 returns the registration acceptance message received from AMF2 to RAN1, and RAN1 forwards the registration acceptance message to the UE. The acceptance message can include an indication that the authentication of SIM2 was successful, a temporary identifier assigned to the UE for SIM2 by the general registration procedure, an indication that the RM state of the UE for SIM2 has changed from RM-DEREGISTERED to RM-INACTIVE, a confirmation response for support to receive paging requests forwarded by PLMN1 for SIM1, the contact information of the MME to receive paging requests from PLMN1, and the registration timer of SIM2. The temporary identifier for the UE is used to page the UE from PLMN2 whenever there is a page for SIM2 while the UE is actively registered with PLMN1. Alternatively, AMF1 can assign a separate temporary identifier to SIM2 that can be used to page the UE in PLMN1 instead. This assignment of the temporary identifier can be such that the associated paging opportunity overlaps with the paging opportunity associated with SIM1. Thus, the UE only needs to monitor one paging opportunity to receive pages for both SIM1 and SIM2. Alternatively, AMF1 can maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs, while ​​​​​​​​​​​​​​​​​The same temporary identifier can be assigned to all attached SIMs. For each SIM The RM state of the corresponding UE is updated at the UE, i.e., RM-REGIST ERED for SIM1 and RM-INACTIVE for SIM2, which should be consistent with that of AMF1.

[0165] Regardless of whether the PLMNs are the same or different, the UE can perform indirect registration after registering each SIM with the respective PLMN. In other words, the multi-SIM UE first registers SIM1 with PLMN1, then SIM2 with PLMN2, and finally performs indirect registration. Note that the order of registration with PLMN1 and PLMN2 is irrelevant. After the SIMs are registered with the respective PLMNs, the UE can then decide to operate mainly on one of the SIMs, e.g., the primary SIM (e.g., SIM1) configured by the user. In this case, the UE can perform indirect registration from PLMN1 to PLMN2 via the user plane of SIM2's PLMN1.

[0166] FIG. 39 shows the procedure for a multi-SIM UE to perform indirect registration of a non-active SIM via the user plane of the active SIM. Before performing the indirect registration procedure, the UE has registered individually with the corresponding PLMNs, e.g., registered SIM1 with PLMN1 and SIM2 with PLMN2. Next, the UE uses the PDU session created for SIM1 on PLMN1 to perform the indirect registration procedure for SIM2. The user of the UE makes SIM1 the preferred SIM, or the user completes important activities ​​​​​​​remain connected to PLMN1 for a certain period of time and at the same time page SIM2 The UE may be configured to trigger this procedure so that it can also receive mobile terminal services such as paging requests.

[0167] Step S3902: The UE separately registers with PLMN1 and PLMN2 for each SIM. As part of the multi-SIM operation, the UE monitors the paging messages and periodically switches the communication between the two PLMNs to ensure that the registration status of each SIM remains RM-REGISTERED. Step S3904: The UE establishes a PDU session on PLMN1 for SIM1 to establish a data connection. One or more PDU sessions may be created. One of the PDU sessions may be established for important activities such as a voice call made by the user of the UE or an important download that the user does not want to be interrupted. Another PDU session may be associated with a general connection to the Internet established after the UE is registered with the PLMN. Separately, the UE also establishes a PDU session for SIM2 on PLMN2. Step S3906: If the SIM1 activity from Step S3904 is important to the user of the UE, the user can configure it via the GUI so that the service of SIM1 is not interrupted. With this configuration, the UE disables the switched communication between the two PLMNs and remains connected to PLMN1 for a configured time period, configured location, etc., in some cases. Alternatively, the user of the UE can set SIM1 as the primary S It may be configured such that IM is present and SIM2 is a secondary SIM. As a result, the UE makes a decision to prefer to keep the user connected to PLMN1. Step S3908: As a result of the decision made in step S3906, the UE sends an indirect registration request to the N3IWF of PLMN2 via the user plane of PLMN1. The UE uses the PDU session created in step S3904 and the address of N3IWF2 provisioned to the UE by the PCF from PLMN2 for sending the indirect registration. The registration message includes, in the request, the following information, namely, the multi-SIM indicator, the indirect registration indicator, the SIM2 identifier, an optional time period, location information, whether PLMN2 should buffer the UE's downlink data, that the UE is reachable via the user plane of PLMN1, etc. The UE can obtain its public IP address through an external mechanism (e.g., the STUN protocol) and provide the address of the indirect registration message to N3IWF2. If the UE is assigned a unique IPv6 address or prefix, the UE can provide the address or prefix to N3IWF2 in the indirect registration message. Alternatively, the UE can establish a secure tunnel to N3IWF2 to enable the proposed functionality. The UE can also indicate the PDU session ID for associating future paging requests provided by PLMN2 in NAS notifications sent to the UE via the user plane of PLMN1. The PDU session ID is the PDU session previously established by the UE on PLMN2. It may be a scenario. Step S3910: AMF2 processes the registration request received from the UE through N3IWF of PLMN2. The presence of the multi-SIM indicator notifies the AMF that the UE is a multi-SIM device, and the indirect registration request indicates that it can reach the UE via the user plane of the PLMN that is the source of this request. If a time period is provided to indicate a certain time while the UE remains connected to PLMN1, the AMF may reset or pause the registration timer associated with SIM2 and enable a new pause timer based on the value provided by the UE. AMF2 may return an acceptance response for the indirect registration that includes the status of the request, the time value for which the AMF pauses the UE's registration, the PDU session ID associated with the future paging request to be transferred to the UE if not provided by PLMN2, etc. ... ... ... ... ... ... ... ... ...

[0168] The procedure shown in Figure 39 enables PLMN2 to transfer a paging request to the UE via the user plane of PLMN1. The UE is assumed to maintain the PDU session established on PLMN1 so that it can receive NAS notifications that may be received from PLMN2. Before releasing the PDU session on PLMN1, the UE may need to notify PLMN2 that it can no longer be reached via the user plane of PLMN1. If a secure tunnel is created, the UE can receive paging requests as long as the secure tunnel is valid. ... ... ... ... ... ...

[0169] (Indirect Attach) As shown in Figure 25, an alternative to partial attach in LTE is enhanced indirect attach. 。Indirect attach can be considered as an initial attach procedure, but in addition to the functions added to support multi-SIM operation, it can be executed indirectly from a different PLMN instead of directly on the home PLMN. In this case, an indirect attach procedure is executed for SIM2 through PLMN1. As a result, the context information regarding the registration of SIM2 is established at the MME of PLMN2, and the default bearer can also be created at the SGW and PGW of PLMN2. Similar to the case of partial attach, indirect attach can be incorporated as a general attach procedure executed in step S2502 of FIG. 25 that enables paging request transfer. Indirect attach also allocates an MME to provide services to the UE. ーte. In this case, an indirect attach procedure is executed for SIM2 through PLMN1. As a result, the context information regarding the registration of SIM2 is established at the MME of PLMN2, and the default bearer can also be created at the SGW and PGW of PLMN2. Similar to the case of partial attach, indirect attach can be incorporated as a general attach procedure executed in step S2502 of FIG. 25 that enables paging request transfer. In this case, an indirect attach procedure is executed for SIM2 through PLMN1. As a result, the context information regarding the registration of SIM2 is established at the MME of PLMN2, and the default bearer can also be created at the SGW and PGW of PLMN2. Similar to the case of partial attach, indirect attach can be incorporated as a general attach procedure executed in step S2502 of FIG. 25 that enables paging request transfer. Indirect attach also allocates an MME to provide services to the UE.

[0170] Step S2502: The UE executes an attach procedure for SIM1 to PLMN1, which is the active PLMN. This step may be executed first when only SIM1 is installed in the UE. When two or more SIMs are installed in the UE simultaneously, a combined attach procedure may be executed to register multiple SIMs together with one attach request. This combined attach request can include a multi-SIM indicator, an indirect attach indicator, appropriate SIM identifiers for each SIM (e.g., IMSI, GUTI, etc.), and the identification information of PLMN2 when the UE registers to PLMN1 of SIM1. In this case, indirect attach may be integrated as part of the attach procedure from TS 23.401 and may be referred to as MUSIM attach as described later. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter. This step may be executed first when only SIM1 is installed in the UE. When two or more SIMs are installed in the UE simultaneously, a combined attach procedure may be executed to register multiple SIMs together with one attach request. This combined attach request can include a multi-SIM indicator, an indirect attach indicator, appropriate SIM identifiers for each SIM (e.g., IMSI, GUTI, etc.), and the identification information of PLMN2 when the UE registers to PLMN1 of SIM1. In this case, indirect attach may be integrated as part of the attach procedure from TS 23.401 and may be referred to as MUSIM attach as described later. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter. This combined attach request can include a multi-SIM indicator, an indirect attach indicator, appropriate SIM identifiers for each SIM (e.g., IMSI, GUTI, etc.), and the identification information of PLMN2 when the UE registers to PLMN1 of SIM1. In this case, indirect attach may be integrated as part of the attach procedure from TS 23.401 and may be referred to as MUSIM attach as described later. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter. or a stand-alone indicator, and the indirect attach indicator may be carried by an attach type parameter. The message can further indicate which SIM is the primary SIM, which SIM is the secondary SIM, and which should be used for registration to a non-active PLMN. The procedure skips to step S2506 of the MUSIM attach request, and the request may be executed simultaneously or sequentially, for example, registration of SIM1 followed by registration of SIM2. Step S2504: After a while, the indirect attach procedure is started. For example, this can be done by inserting a physical SIM, through the eSIM configuration, based on a request from an application on the UE through the GUI, or immediately after completion of the attach procedure by PLMN1 when SIM2 is added to the UE. SIM2 is considered a secondary SIM and is associated with PLMN2, which is considered a non-active PLMN. The UE then executes an indirect attach request from PLMN1 to PLMN2. This request can include a multi-SIM indicator, the appropriate SIM identifier for each SIM (e.g., IMSI, GUTI, etc.), and identification information of other PLMNs. The multi-SIM indicator may be encoded as an option of the priority network behavior parameter or be a stand-alone indicator. The multi-SIM indicator is used by a network entity to check and select the appropriate network entity that supports multi-SIM operation during the attach procedure and enable paging request transfer. 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 that time, the paging request of SIM1 may be transferred from PLMN1 to PLMN2. Step S2510: The indirect attach request is processed as outlined in steps 3 to 17 of the E-UTRAN 3 of the 202 attach procedure. The NAS message response sent in step S2006 is re-routed to the MME of PLMN1 instead of going to the RAN node of PLMN2. Note that the indirect attach acceptance response received from this procedure contains the status of the result of the procedure. The response may include an indication that the authentication of SIM2 was successful, a temporary identifier assigned for SIM2 by MME2 2502, an indication that the UE's EMM state for SIM2 has been changed from EMM-DEREGISTERED to EMM-INACTIVE, a confirmation response for support to receive the paging request transferred for SIM1 by PLMN1, the contact information of the MME to receive the paging request from PLMN1, and the registration timer of SIM2. If the indirect attach is not accepted, the response may include further information detailing the reason why the attach was not accepted. an indication that the authentication of SIM2 was successful, a temporary identifier assigned for SIM2 by MME2 2502, an indication that the UE's EMM state for SIM2 has been changed from EMM-DEREGISTERED to EMM-INACTIVE, a confirmation response for support to receive the paging request transferred for SIM1 by PLMN1, the contact information of the MME to receive the paging request from PLMN1, and the registration timer of SIM2. If the indirect attach is not accepted, the response may include further information detailing the reason why the attach was not accepted. an indication that the authentication of SIM2 was successful, a temporary identifier assigned for SIM2 by MME2 2502, an indication that the UE's EMM state for SIM2 has been changed from EMM-DEREGISTERED to EMM-INACTIVE, a confirmation response for support to receive the paging request transferred for SIM1 by PLMN1, the contact information of the MME to receive the paging request from PLMN1, and the registration timer of SIM2. If the indirect attach is not accepted, the response may include further information detailing the reason why the attach was not accepted. an indication that the authentication of SIM2 was successful, a temporary identifier assigned for SIM2 by MME2 2502, an indication that the UE's EMM state for SIM2 has been changed from EMM-DEREGISTERED to EMM-INACTIVE, a confirmation response for support to receive the paging request transferred for SIM1 by PLMN1, the contact information of the MME to receive the paging request from PLMN1, and the registration timer of SIM2. If the indirect attach is not accepted, the response may include further information detailing the reason why the attach was not accepted. Step S2512: The MME of PLMN1 may return an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 an indirect attach acceptance message to the UE, which may be a modified attach acceptance message providing additional information regarding the status of the indirect attach procedure. If the attach procedure is executed for multiple SIMs, there may be separate registration statuses for each SIM. The response message may include information returned from the MME of PLMN2, such as the temporary identifier and an indication of successful authentication of SIM2. The temporary identifier assigned to SIM2 is transferred to PLMN1 for SIM2 It is used to identify future paging requests. In addition, the MME of PLMN1 may allocate a separate temporary identifier for SIM2 that can be used to page the UE instead of using the temporary identifier allocated by PLMN2. This allocation of the temporary identifier may be such that the associated paging opportunity may overlap with the paging opportunity associated with SIM1. As a result, the UE may only need to monitor one paging opportunity to receive pages for both SIM1 and SIM2. The MME may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs, while allocating the same temporary identifier to all SIMs associated with the UE. The EMM state of the UE for each SIM is updated. In this scenario, the EMM state of SIM1 is EMM-REGISTERED, and for SIM2 it is EMM-INACTIVE. Similarly, the EMM state in the MME of PLMN1 is EMM-REGISTERED for SIM1 and EMM-INACTIVE for SIM2. Finally, the EMM state in the MME of PLMN2 is EMM-INACTIVE for SIM2. Figure 25 also includes SGW2 2504 and PGW2 2506. As shown in Figure 39, similar to the indirect registration performed via the user plane in 5G, the indirect attach request may also be sent via the user plane in LTE. This procedure will be executed in a similar manner, but the messages and entities involved will be LTE messages. The MME may alternatively maintain the fact that the UE only needs to monitor one paging opportunity and can receive pages for all SIMs, while allocating the same temporary identifier to all SIMs associated with the UE. The EMM state of the UE for each SIM is updated. In this scenario, the EMM state of SIM1 is EMM-REGISTERED, and for SIM2 it is EMM-INACTIVE. Similarly, the EMM state in the MME of PLMN1 is EMM-REGISTERED for SIM1 and EMM-INACTIVE for SIM2. Finally, the EMM state in the MME of PLMN2 is EMM-INACTIVE for SIM2. Figure 25 also includes SGW2 2504 and PGW2 2506. The EMM state of SIM1 is EMM-REGISTERED, and for SIM2 it is EMM-INACTIVE. Similarly, the EMM state in the MME of PLMN1 is EMM-REGISTERED for SIM1 and EMM-INACTIVE for SIM2. Finally, the EMM state in the MME of PLMN2 is EMM-INACTIVE for SIM2. Figure 25 also includes SGW2 2504 and PGW2 2506. The EMM state in the MME of PLMN1 is EMM-REGISTERED for SIM1 and EMM-INACTIVE for SIM2. Finally, the EMM state in the MME of PLMN2 is EMM-INACTIVE for SIM2. Figure 25 also includes SGW2 2504 and PGW2 2506. Finally, the EMM state in the MME of PLMN2 is EMM-INACTIVE for SIM2. Figure 25 also includes SGW2 2504 and PGW2 2506. Figure 25 also includes SGW2 2504 and PGW2 2506.

[0171] As shown in Figure 39, similar to the indirect registration performed via the user plane in 5G, the indirect attach request may also be sent via the user plane in LTE. This procedure will be executed in a similar manner, but the messages and entities involved will be LTE messages. ​​​​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. Although the terms are used, it should be noted that the procedures can also be applied to 5G systems.

[0173] Step S2602: Two SIMs are installed in the MUSIM - compliant UE. SI M1 is the primary SIM, associated with PLMN1, and SIM2 is the secondary SI M, associated with PLMN2. Although the figure shows only two SIMs, three or more SIMs may be installed in the UE, and it should be noted that the procedures remain the same except that the attach procedure is extended to each installed S IM. Step S2604: The UE executes a MUSIM attach request to register with the PLMN associated with each installed SIM. The request can include, among other data required for the attach procedure, a multi - SIM indicator and the identifiers of each SIM. In addition, either a partial attach indication or an indirect attach indication may be provided to notify the MME of PLMN1 how to register the SIMs associated with different PLMNs. This indication may be provided per SIM or collectively for all SIMs. If the attach procedure from TS 23.401 is enhanced to integrate the MUSIM functionality proposed here, the multi - SIM indicator may be encoded as an option of the preferred network behavior parameters, or be a stand - alone indicator, and the partial / indirect attach indicator may be carried in the attach type parameter. The message indicates which SIM is the primary SIM and which SIM is the secondary SIM, and to register with a non - active PLMN or not. can further indicate whether it should be used for Step S2606: The MME of PLMN1 executes the attach procedure for the primary SIM The UE is authenticated and authorized, and a registration context is created on MME1 of SIM1 This procedure can also create default bearers 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 can also register other SIMs belonging to the same operator as SIM1 If SIM2 belongs to the same operator as SIM1 an attach procedure is executed for SIM2, and a registration context for SIM2 is created in a separate MME from the registration context of SIM1. However, the UE context can be linked together to provide optimization when forwarding paging requests. If the attach is successful, the EMM state of SIM2 becomes EMM-INACTIVE because it is not the primary SIM of the UE. This step may be repeated for multiple SIMs belonging to the same PLMN as SIM1. In this particular case, since SIM2 belongs to a different PLMN step S2608 is skipped. Step S2610: The MME of PLMN1 executes either a partial attach or an indirect attach for SIM2 with PLMN2. The UE may provide an indication of which attach request to execute in step S2604, or the MME may be configured as to which attach procedure to execute, or the core network ​​​​​​​​​It may have a system policy indicating which attachment procedure should be executed. PLMN The MME of 1 sets the EMM state of each SIM to EMM - INACTIVE here. The EMM state of each SIM of each PLMN is also set to EMM - INACTIVE. The information exchanged between PLMN1 and PLMN2 is the same as previously specified and may be within the NAS container encrypted for specific information to protect the privacy of the UE. It can be within. Step S2612: The MME of PLMN1 aggregates all attachment acceptance results of each SIM and returns them to the UE. Instead of using the temporary identifiers assigned by other PLMNs, the MME of PLMN1 can assign a separate temporary identifier for each SIM that can be used to page the UE. The assignment of these temporary identifiers is such that the associated paging opportunities can be duplicates or close to the paging opportunities associated with the primary SIM. As a result, the UE only needs to monitor paging opportunities close to each other so as to be able to receive pages for all SIMs. Alternatively, the MME can assign the same temporary identifier to all SIMs associated with the UE, so that the UE only needs to monitor one paging opportunity but can receive pages for all SIMs. When receiving an attachment acceptance, the UE sets the appropriate EMM state for each SIM. In this particular case, the EMM state of the UE for SIM1 is EMM - REGISTERED and for SIM2 is EMM - INACTIVE.

[0174] (5G registration status for multi - SIM operation)​​​​​ To support multi-SIM operation in 5GS, a new Registration Management (RM) state is proposed. The new state, called RM-INACTIVE, refers to the RM state of a UE with an...

Claims

An electronic device comprising a first subscriber identity module (SIM) and a second SIM, wherein the first SIM is associated with a first network, the second SIM is associated with a second network, and the electronic device is: Sending a request to the first network to register the electronic device, the request indicating that the electronic device is a multi-SIM device, the request including a subscriber identifier associated with the first network, the request including a multi-SIM policy, the multi-SIM policy notifying the first network of the capabilities of the electronic device for multi-SIM operation; Receiving a page from the second network and determining to switch to the second network based on the receipt of the page from the second network; Sending an instruction to the first network to switch to the second network; An electronic device configured to transition to a CM-IDLE state and an RRC_IDLE state in the first network.

2. The multi-SIM policy is: An instruction that the electronic device can send service prioritization information that can be used by the first network to determine whether to send a paging message to the electronic device; An instruction that the electronic device can receive service type information in the paging message, or The electronic device according to claim 1, comprising one or more of an instruction that the electronic device can provide an identifier that can be used to determine a paging opportunity.

3. Configured to receive information for configuring the electronic device for multi-SIM operation, the information being: An instruction that the first network can receive service prioritization information that can be used by the first network to determine whether to send a paging message to the electronic device; An instruction that the first network can send service type information in the paging message to the electronic device, or The electronic device according to claim 1, comprising one or more of an instruction that the first network supports the transmission of an identifier that can be used to determine a paging opportunity.

4. The electronic device according to claim 1, configured to send a SIM switching request to the first network, wherein the SIM switching request indicates to the first network that the electronic device connects to the second network.

5. The electronic device according to claim 4, wherein the SIM switching request includes service prioritization information for requesting the core network of the first network to filter paging requests for the electronic device.

6. The electronic device according to claim 1, configured to receive a paging message from the first network, wherein the paging message includes service type information indicating what the paging message is for.

7. Receiving a paging message from a first network, responding to the received paging message, sending the request to the first network, wherein the request includes an indication that the electronic device is busy, the electronic device according to claim 1.

8. The electronic device according to claim 7, wherein the request indicating that the electronic device is busy includes service prioritization information for notifying the core network of the first network to filter paging requests for the electronic device.

9. Sending a request to the first network to provide a new identifier for calculating a paging opportunity, receiving a response from the first network, the received response including a new identifier, configured to calculate a paging opportunity using the new identifier, the electronic device according to claim 1.

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

11. An electronic device including a first subscriber identity module (SIM) and a second SIM, wherein the first SIM is associated with a first network, the second SIM is associated with a second network, and the electronic device is Send a request to the first network to register the electronic device, the request indicating that the electronic device is a multi-SIM device, the request including a subscriber identifier associated with the first network, the request including a multi-SIM policy, the multi-SIM policy notifying the first network of the capabilities of the electronic device for multi-SIM operation, Receive a page from the second network and switch to the second network based on receiving the page from the second network, Send an indication to the first network that the electronic device is switching to the second network, An electronic device configured to transition to a CM-IDLE state and an RRC_IDLE state in the first network.

12. A method executed on an electronic device including a first subscriber identity module (SIM) and a second SIM, the first SIM associated with a first network, the second SIM associated with a second network, the method comprising: Send a request to the first network to register the electronic device, the request indicating that the electronic device is a multi-SIM device, the request including a subscriber identifier associated with the first network, the request including a multi-SIM policy, the multi-SIM policy notifying the first network of the capabilities of the electronic device for multi-SIM operation, Receive a page from the second network and switch to the second network based on receiving the page from the second network, Send an indication to the first network that the electronic device is switching to the second network, Including transitioning to a CM-IDLE state and an RRC_IDLE state in the first network. A method.

13. The multi-SIM policy is: An indication that the electronic device can send service prioritization information that can be used by the first network to determine whether to send a paging message to the electronic device, An indication that the electronic device can receive service type information within a paging message, or The method according to claim 12, comprising one or more instructions that the electronic device can provide an identifier that can be used to determine a paging opportunity.

14. Comprising receiving information configuring the electronic device for multi-SIM operation, the information an instruction that the first network can receive service prioritization information that can be used by the first network to determine whether to send a paging message to the electronic device, an instruction that the first network can send service type information within a paging message to the electronic device, or The method according to claim 12, comprising one or more instructions that the first network can send an identifier that can be used to determine a paging opportunity.

15. The method according to claim 12, comprising sending a SIM switching request to the first network, the SIM switching request indicating to the first network that the electronic device connects to the second network.

16. The method according to claim 15, wherein the SIM switching request includes service prioritization information for requesting that a core network of the first network filter paging requests for the electronic device.

17. The method according to claim 12, comprising receiving a paging message from the first network, the paging message including service type information indicating what the paging message is for.

18. Receiving a paging message from a first network, responding to the paging message by sending the request to the first network, the request including an indication that the electronic device is busy, the method according to claim 12.

19. The method according to claim 18, wherein the request indicating that the electronic device is busy includes service prioritization information for notifying a core network of the first network to filter paging requests for the electronic device.

20. Sending a request to the first network to provide a new identifier for calculating a paging opportunity, Receiving a response from the first network, the received response including a new identifier, The method according to claim 12, comprising calculating a paging opportunity using the new identifier.

Images