Method and system for managing incoming calls in embedded subscriber identity module devices

Abstract

A server for managing an incoming call in an embedded subscriber identity module (eSIM) network is configured to receive, from a mobile network operator (MNO), a first MSISDN number of a first eSIM profile of a plurality of eSIM profiles in an electronic device to obtain an operating state associated with the first eSIM profile. The server is further configured to, in response to receiving a first mobile station integrated service digital network (MSISDN) number, determine that an operational state associated with the first eSIM profile is inactive. The server is further configured to, in response to determining that the operational state associated with the eSIM profiles is inactive, send a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles whose operational state is active to the MNO.

Description

Technical Field

[0001] The present disclosure relates generally to the field of wireless communications, and more particularly to methods and systems for managing incoming calls in an embedded subscriber identity module (eSIM) device having multiple eSIM profiles. Background Art

[0002] Traditionally, eSIM enables a device user to acquire any number of eSIM profiles across operators, which are known to his / her contacts through any corresponding Mobile Station Integrated Services Digital Network (MSISDN) number, and activate one eSIM profile at a time, either manually or automatically, within the embedded Universal Integrated Circuit Card (eUICC) based on coverage, cost, or geographic area. This can lead to the following issues.

[0003] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above information might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0004] Technical issues

[0005] From the network perspective, when the originating network attempts to establish a call to an eUICC user with N profiles (MSISDN numbers), N-1 call attempts result in call failures because only one profile will be active within the eUICC and thus precious network resources (radio bearers at the originating leg and trunk circuits between the core network) are wasted.

[0006] From the user's perspective, when a contact of the user attempts to call the eSIM user on an MSISDN number for which the profile is inactive, there is no mechanism to directly connect the call on any active eSIM profile (and therefore, active MSISDN number) within the user's eUICC.

[0007] Here, "Mobile Station Integrated Services Digital Network" is introduced as an explanation (full name) of MSISDN. In the relevant field, "MSISDN" also refers to other explanations, such as "Mobile Station International Subscriber Directory Number" and "Mobile Subscriber ISDN Number".

[0008] eSIM is an emerging field that provides mechanisms for protecting multiple subscription profiles and implementing the appropriate profile based on subscription costs and connection quality. The current generation of smartphones are equipped with an eUICC hardware element that can store many eSIM profiles, and at any point in time, one eSIM profile can be active within the eUICC element.

[0009] When making a phone call to an eSIM user with multiple eSIM profiles and multiple corresponding MSISDN numbers, the call will be successfully connected only if the eSIM profile corresponding to the called MSISDN number is active or the feature of call forwarding to the active number is set manually or automatically. If the feature of call forwarding is not set, the call will fail. Alternatively, if the feature of call forwarding is set, the user must bear the additional cost of call forwarding for receiving calls on active numbers.

[0010] Technical Solution

[0011] This summary is provided to introduce some concepts in a simplified format that will be further described in the detailed description of the present disclosure. This summary is neither intended to identify key or essential elements of the present disclosure nor to determine the scope of the present disclosure.

[0012] According to one aspect of the present disclosure, a method for managing incoming calls in an embedded subscriber identity module (eSIM) device having multiple eSIM profiles, performed by a mobile network operator (MNO), includes: receiving an incoming call directed to a second electronic device from a first electronic device on a first mobile station integrated services digital network (MSISDN) number of a first eSIM profile among multiple eSIM profiles in the second electronic device; sending the first MSISDN number to a server to obtain an operating state associated with the first eSIM profile; receiving a response from the server based on an inactive operating state associated with the first eSIM profile, the response including a second MSISDN number associated with a second eSIM profile among the multiple eSIM profiles whose operating state is active; and in response to receiving the response, routing the incoming call on a second MSISDN number of the second eSIM profile whose operating state is active.

[0013] According to another aspect of the present disclosure, a method for managing incoming calls in an eSIM network performed by a server includes: receiving a first MSISDN number of a first eSIM profile among multiple eSIM profiles in an electronic device from an MNO to obtain an operating state associated with the first eSIM profile, and in response to receiving the first MSISDN number, determining that the operating state associated with the first eSIM profile is inactive. The server is configured to include multiple eSIM profiles and provide an operating state associated with each of the multiple eSIM profiles. The method also includes: in response to determining that the operating state associated with the eSIM profile is inactive, sending a second MSISDN number associated with a second eSIM profile among the multiple eSIM profiles whose operating state is active to the MNO.

[0014] According to another aspect of the present disclosure, an MNO for managing incoming calls in an eSIM device having multiple eSIM profiles includes a processor configured to enable the MNO to: receive an incoming call directed to a second electronic device from a first electronic device on a first MSISDN number of a first eSIM profile among multiple eSIM profiles in a second electronic device; send the first MSISDN number to a server to obtain an operating status associated with the first eSIM profile; receive a response from the server based on an inactive operating status associated with the first eSIM profile, the response including a second MSISDN number associated with a second eSIM profile among the multiple eSIM profiles whose operating status is active; and in response to receiving the response, route the incoming call on a second MSISDN number of the second eSIM profile whose operating status is active.

[0015] According to another aspect of the present disclosure, a server for managing incoming calls in an eSIM network includes a processor configured to cause the server to: receive a first MSISDN number of a first eSIM profile in a plurality of eSIM profiles in an electronic device from an MNO to obtain an operating state associated with the first eSIM profile. The MNO is configured to send the first MSISDN number when an incoming call directed to a second electronic device is received from a first electronic device on the first MSISDN number. The processor is also configured to, in response to receiving the first MSISDN number, cause the server to determine that the operating state associated with the first eSIM profile is inactive. The server is configured to include a plurality of eSIM profiles and provide an operating state associated with each of the plurality of eSIM profiles. The processor is also configured to, in response to determining that the operating state associated with the eSIM profile is inactive, cause the server to send a second MSISDN number associated with a second eSIM profile whose operating state is active in the plurality of eSIM profiles to the MNO.

[0016] According to another aspect of the present disclosure, a server for providing a connection to an eSIM in an electronic device includes a processor configured to cause the server to: receive an eSIM profile from the electronic device, wherein the eSIM profile corresponds to an MSISDN number; associate the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile; and register the MSISDN number at the server through an OTP authentication mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0018] Figure 1An environment for managing incoming calls in an embedded subscriber identity module (eSIM) device having multiple eSIM profiles according to an embodiment of the present disclosure is shown;

[0019] Figure 2 An environment for providing a connection to an eSIM in an electronic device according to an embodiment of the present disclosure is shown;

[0020] Figure 3 An operational flow chart depicting a process for managing incoming calls in an eSIM device with multiple eSIM profiles according to an embodiment of the present disclosure is shown;

[0021] Figure 4 An operational flow chart depicting a process for providing a connection to an eSIM in an electronic device according to an embodiment of the present disclosure is shown;

[0022] Figure 5 A schematic block diagram of a depiction server according to an embodiment of the present disclosure is shown;

[0023] Figure 6 A flow chart is shown depicting a method for managing incoming calls in an eSIM device having multiple eSIM profiles according to an embodiment of the present disclosure;

[0024] Figure 7 A flow chart depicting a method implemented at a server for managing incoming calls in an eSIM network according to an embodiment of the present disclosure is shown;

[0025] Figure 8 A flow chart depicting a method implemented at a server for providing a connection to an eSIM in an electronic device is shown according to an embodiment of the present disclosure;

[0026] Fig. 9 A process for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown;

[0027] Fig.10 A process for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown.

[0028] Fig.11 An example of a block diagram of a system for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown;

[0029] Fig.12 An example of the operation of an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown;

[0030] Fig.13 An example of the operation of the third server according to an embodiment of the present disclosure is shown;

[0031] Fig.14 The flow of establishing a call connection with an activated MSISDN according to an embodiment of the present disclosure is shown;

[0032] Fig.15 A signal flow chart for acquiring multiple profiles in an electronic device according to an embodiment of the present disclosure is shown;

[0033] Fig.16 A signal flow diagram for activating one of a plurality of profiles according to an embodiment of the present disclosure is shown;

[0034] Fig.17 shows a signal flow diagram for authenticating a profile according to an embodiment of the present disclosure;

[0035] Fig.18 shows a signal flow diagram between an MNO and an HLR / HSS according to an embodiment of the present disclosure;

[0036] Fig.19 shows a signal flow diagram related to a mechanism for MNO to provide opt-in for eSIM connection according to an embodiment of the present disclosure;

[0037] Fig. 20 shows a signal flow diagram related to a mechanism for acquiring an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure;

[0038] Fig.21 shows a signal flow diagram related to a mechanism for connecting to an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure;

[0039] Fig. 22 A signal flow chart related to a mechanism executed when a third server fails to find an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure is shown;

[0040] Fig.23 An example of a process for acquiring a profile according to an embodiment of the present disclosure is shown;

[0041] Fig.24 An example of an architecture according to an embodiment of the present disclosure is shown; and

[0042] Fig.25 An example of a 5G network and an always-connected server interface according to an embodiment of the present disclosure is shown.

[0043] Furthermore, those skilled in the art will appreciate that the elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. For example, a flow chart illustrates a method in terms of the most salient operations involved to help improve understanding of various aspects of the present disclosure. Furthermore, with respect to the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details relevant to understanding the embodiments of the present disclosure so as not to obscure the drawings with details that would be apparent to one of ordinary skill in the art having the benefit of the description herein.

[0044] The same reference numerals are used throughout the drawings to denote the same elements. DETAILED DESCRIPTION

[0045] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these details are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

[0046] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0047] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0048] In various examples of the present disclosure described below, a hardware method will be described as an example. However, since various embodiments of the present disclosure may include techniques utilizing both hardware-based methods and software-based methods, they are not intended to exclude software-based methods.

[0049] As used herein, terms related to combining (e.g., combining, grouping, combining, aggregating, uniting, integrating, unifying) refer to terms referring to signals (e.g., packets, messages, signals, information, signaling), terms referring to resources (e.g., segments, symbols, time slots, subframes, radio frames, subcarriers, resource elements (REs), resource blocks (RBs), bandwidth parts (BWPs), opportunities), terms used to refer to any operating state (e.g., steps, operations, procedures), terms referring to data (e.g., packets, messages, user flows, information, bits, symbols, codewords), terms referring to channels, terms referring to network entities (e.g., distributed units (DUs), radio units (RUs), central units (CUs), control planes (CU-CPs), user planes (CU-UPs), O-DUs (O-RAN DUs), O-RUs (O-RAN RUs), O-CU-UPs (O-RAN CU-CPs), O-CU-CPs (O-RAN DUs), and O-RAN The terms CU-CP) and components of a device or apparatus are shown only for the convenience of description in the present disclosure. Therefore, the present disclosure is not limited to those terms described below, and other terms with the same or equivalent technical meanings may be used for this purpose. In addition, as used herein, terms such as "~module", "~unit", "~component", "~main body", etc. may refer to a structure or unit of at least one shape for processing a specific function.

[0050] In addition, throughout the present invention, expressions such as 'above' or 'below' may be used to determine whether a specific condition is met or satisfied, but they are merely descriptions for expressing examples and are not intended to exclude the meaning of 'greater than or equal to' or 'less than or equal to'. Respectively, a condition described as "greater than or equal to" may be replaced with an expression such as "above", a condition described as "less than or equal to" may be replaced with an expression such as "below", and a condition described as "greater than or equal to and less than" may be replaced with "above and less than or equal to". In addition, hereinafter, 'A' to 'B' means at least one of the elements from A (including A) to B (including B). hereinafter, 'C' and / or 'D' means including at least one of 'C' or 'D', i.e. {'C', 'D', or 'C' and 'D'}.

[0051] The present disclosure uses terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), Scalable Radio Access Network (xRAN), Open Radio Access Network (O-RAN), etc.) to describe various embodiments, but they are merely examples for explanation, and various embodiments of the present disclosure can be easily modified and applied thereto even in other communication systems.

[0052] To promote an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe these embodiments. It will be understood, however, that no limitation of the scope of the present disclosure is intended thereby, and such changes and further modifications in the illustrated systems and such further applications of the principles of the present disclosure as illustrated therein are deemed to be within the ordinary scope of those skilled in the art to which the present disclosure relates.

[0053] Those skilled in the art will understand that both the foregoing general description and the following detailed description are illustrative of the present disclosure and are not intended to be limiting.

[0054] Reference throughout this specification to "on one hand," "on the other hand," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases "in an embodiment," "in another embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0055] The terms "comprises", "comprising" or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process or method that includes a list of operations includes not only those operations but may also include other operations not expressly listed or inherent to such process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises..." do not exclude the presence of other devices or other subsystems or other elements or other structures or other components or additional devices or additional subsystems or additional elements or additional structures or additional components, without more constraints.

[0056] Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs.The systems, methods, and examples provided herein are illustrative only and not limiting.

[0057] Figure 1 An environment 100 for managing incoming calls in an embedded subscriber identity module (eSIM) device with multiple eSIM profiles according to an embodiment of the present disclosure is shown. The environment 100 may include a mobile network operator (MNO) 102, a server 104, a first electronic device 106, and a second electronic device 108. The second electronic device 108 may be an eSIM device with multiple eSIM profiles. Each eSIM profile may be associated with an eSIM. Examples of the first electronic device 106 and the second electronic device 108 may include, but are not limited to, smartphones and mobile phones with multiple eSIMs.

[0058] In one embodiment, the MNO 102 may receive an incoming call from the first electronic device 106. The incoming call may be directed to the second electronic device 108. Additionally, on the second electronic device 108, the incoming call may be directed to a first MSISDN number of a first eSIM profile among a plurality of eSIM profiles in the second electronic device 108.

[0059] After receiving the incoming call, MNO 102 may send the first MSISDN number to server 104 to obtain an operational status associated with the first eSIM profile. When the incoming call for the first eSIM is received, the operational status may indicate whether the first eSIM is active or inactive. Server 104 may receive the first MSISDN number of the first eSIM profile.

[0060] In response to receiving the first MSISDN number, the server 104 may determine that the operating state associated with the first eSIM profile is inactive. The server 104 may include multiple eSIM profiles and an operating state associated with each of the multiple eSIM profiles. The server 104 may send a response including a second MSISDN number associated with a second eSIM profile to the MNO 102. The second eSIM profile may be among the multiple eSIM profiles whose operating state is active. Subsequently, the MNO 102 may receive a response including the second MSISDN number using the second eSIM whose operating state is active.

[0061] In response to receiving the second MSISDN number, the MNO 102 may route the incoming call on the second MSISDN number of the second eSIM profile whose operational state is active.

[0062] Figure 2 A system 200 for providing a connection to an eSIM in an electronic device according to an embodiment of the present disclosure is shown. The eSIM may include an MSISDN number, and the eSIM may be associated with an eSIM profile that may be stored at the server 104.

[0063] According to an embodiment of the present disclosure, the server 104 may receive an eSIM profile from an electronic device. The eSIM profile may be a profile of an eSIM and may be associated with an MSISDN number. In one embodiment, the electronic device may include multiple eSIM profiles, so that the electronic device may be an eSIM device configured to deploy multiple eSIMs in the electronic device. In addition, the server 104 may store the eSIM profile in an embedded universal integrated circuit card (eUICC) element by scanning an MNO subscription card and deriving an SM-DP+ address and securely connecting to the correct SM-DP+ to download the MNO profile.

[0064] After receiving the eSIM profile, the server 104 may associate the eSIM profile with the MSISDN number. The association may be performed using an eUICC key associated with the eSIM profile. The eSIM profile may be stored at the server 104, corresponding to a unique eUICC identification (ID). The server 104 may track the operational state of the eSIM profile. The operational state may be one of an active state and an inactive state. The eSIM profile may include an MSISDN number, and an eSIM associated with an eSIM profile including an operational state as an active state may receive an incoming call on the MSISDN number associated with the eSIM at the electronic device. In one embodiment, in the case where it is determined that the eSIM is inactive and the electronic device includes another eSIM having another eSIM profile with an active state and another MSISDN number stored at the server 104, the server 104 may find another MSISDN number corresponding to the unique eUICC ID within the eSIM profile.

[0065] In response to associating the eSIM profile, the server 104 may register the MSISDN number at the server 104 through a one-time password (OTP) authentication mechanism. The OTP mechanism may be used to confirm whether the MSISDN number is authentic and belongs to the user of the eSIM. The OTP mechanism may be executed whenever the user activates the eSIM profile for the first time. For all MSISDN numbers, the server 104 may perform periodic OTP authentication to confirm that each MSISDN number may include a valid subscription with A MNOs. In one embodiment, upon determining that the subscription with the MNO is inactive, the server 104 may be configured to delete the MSISDN number.

[0066] Figure 3 1 is a flowchart of an operation according to an embodiment of the present disclosure, which depicts a process 300 for managing incoming calls in an eSIM device having multiple eSIM profiles. The eSIM device may be such as Figure 1 The second electronic device 108 shown has multiple eSIM profiles. The multiple eSIM profiles in the second electronic device 108 may indicate that the second electronic device 108 may enable multiple eSIMs, so that the second electronic device 108 may receive incoming calls on multiple MSISDN numbers associated with the multiple eSIM profiles. Incoming calls may be managed by the MNO 102 by deciding whether to route the calls. The MNO 102 may decide whether to route the incoming calls when communicating with the server 104, such as Figure 1 Server 104 may be interchangeably referred to as an always-connected server.

[0067] At operation 302, process 300 may include receiving an incoming call at MNO 102 from first electronic device 106, such as Figure 1 The incoming call may be directed to the second electronic device 108. More specifically, the first electronic device 106 may make an incoming call on a first MSISDN number associated with a first eSIM profile among a plurality of profiles in the second electronic device 108.

[0068] At operation 304, process 300 may include, upon receiving an incoming call directed to the first MSISDN number, sending, by the MNO 102, the first MSISDN number to a service control function (SCF). The SCF may be a network element that contains service logic. The service logic may implement the behavior desired by the MNO 102. The first MSISDN number may be intended to be sent to the server 104 via the SCF in order to verify the operational state of the first eSIM profile to which the first MSISDN number is associated. The operational state of the first eSIM may be one of an active state and an inactive state. In addition, process 300 may include sending, by the SCF, the first MSISDN number to the server 104. The SCF may send the first MSISDN number in the form of a message "Get_active MSISDN number".

[0069] At operation 306, process 300 may include receiving, by server 104, a first MSISDN number sent by MNO 102 via the SCF. Server 104 may communicate with the SCF to receive the first MSISDN number.

[0070] At operation 308, process 300 may include an operation of determining, by server 104, that an operational state associated with a first eSIM profile is inactive. Server 104 may include a plurality of eSIM profiles having an operational state associated with each of the plurality of eSIM profiles. When a plurality of eSIMs in second electronic device 108 are activated for the first time, the plurality of eSIM profiles may be added to server 104 by a user of the plurality of eSIMs. In addition, process 300 may include an operation of determining a second eSIM profile having an operational state as active from among a plurality of eSIM profiles stored at server 104 associated with second electronic device 108. To determine the second eSIM profile having an active state, process 300 may include obtaining an eUICC ID associated with the plurality of eSIM profiles using the first MSISDN number as a key.

[0071] In addition, process 300 may include obtaining a second MSISDN number associated with the second eSIM profile by using the eUICC ID as a key, the operation state of the second MSISDN number being active. The first MSISDN number and the second MSISDN number may be stored in an MSISDN number database in server 104.

[0072] At operation 310, process 300 may include sending a response to MNO 102. The response may include a second MSISDN number associated with a second eSIM profile to MNO 102, the operational state of the second eSIM profile being active. Server 104 may send the response to MNO 102 via the SCF.

[0073] At operation 312 , process 300 may include an operation of receiving a response from server 104 , the response including a second MSISDN number associated with a second eSIM profile whose operational state is active.

[0074] At operation 314, process 300 may include an operation of routing the incoming call on a second MSISDN number of a second eSIM profile whose operational state is active. MNO 102 may send the first MSISDN number to server 104 so that if it is determined that the operational state of the first eSIM profile is inactive, the incoming call may be routed by MNO 102 to a second MSISDN number having a second eSIM profile whose operational state is active. Routing the incoming call to the second eSIM profile may include connecting the first electronic device 106 to the second MNO at the second MSISDN number of the second eSIM profile.

[0075] Figure 4 An operational flow chart according to an embodiment of the present disclosure is shown, which depicts a process 400 for providing a connection to an eSIM in an electronic device. The eSIM may include an MSISDN number, and the eSIM may be associated with an eSIM profile that may be stored at a server 104. In one embodiment, the electronic device may include multiple eSIMs with an operational state. The operational state may be one of an active state and an inactive state. The electronic device may receive an incoming call only when the eSIM profile in the electronic device includes an active state.

[0076] At operation 402, process 400 may include an operation of downloading an eSIM profile associated with an MNO at an electronic device. The eSIM may be downloaded by connecting the electronic device to an SM-DP+ address associated with the MNO. To connect to the SM-DP+ address, the electronic device may scan the MNO subscription and derive the SM-DP+ address.

[0077] At operation 404, process 400 may include an operation of activating, via the electronic device, an eSIM profile associated with the electronic device. The eSIM profile may be activated using an eSIM manager in the electronic device.

[0078] At operation 406, process 400 may include an operation of receiving, by the server, an eSIM profile from an electronic device. The eSIM profile may correspond to an MSISDN number. In addition, the process may include associating, by the server 104, the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile. The eSIM profile may be stored at the server 104 corresponding to the unique eUICCID. The server 104 may track the operational state of the eSIM profile. The operational state may be one of an active state and an inactive state.

[0079] At operation 408, process 400 may include an operation of creating, via the electronic device, at server 104, a table for storing MSISDN numbers associated with the eSIM profile. The electronic device may update the profile status, and a pop-up window may appear on the user interface requesting the eSIM user to update the table with an appropriate MSISDN number corresponding to the eSIM profile.

[0080] At operation 410, process 400 may include an operation of generating an OTP by server 104 in response to receiving the MSISDN number, and server 104 may send the OTP to an electronic device including an eSIM profile having the MSISDN number. Process 400 may also include an operation of receiving the OTP from the electronic device via the MSISDN number by server 104 and verifying the OTP, and server 104 may mark the MSISDN number as active in a table associated with the eSIM profile.

[0081] Figure 5 A schematic block diagram 500 depicting a server 104 according to an embodiment of the present disclosure is shown. The server 104 may be a remote server configured to store a plurality of eSIM profiles, operational states of the plurality of eSIM profiles, and a plurality of MSISDN numbers associated with the plurality of eSIM profiles. The operational state may be one of an active state and an inactive state. The server 104 may communicate with the MNO 102 to share the MSISDN number corresponding to the eSIM profile whose operational state is the active state.

[0082] Server 104 may include processor 502, memory 504, data 506, module 508, resource 510, display unit 512, and communication engine 514. In an embodiment, processor 502, memory 504, data 506, module 508, resource 510, display unit 512, and communication engine 514.

[0083] The server 104 may be one or more of hardware, software, logic-based programs, configurable hardware, etc. In an example, the processor 502 may be a single processing unit or multiple units, all of which may include multiple computing units. The processor 502 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, processor cores, multi-core processors, multiprocessors, state machines, logic circuits, application-specific integrated circuits, field programmable gate arrays, and / or any device that manipulates signals based on operational instructions. In other capabilities, the processor 502 may retrieve and / or execute computer-readable instructions and / or data stored in the memory 504.

[0084] In one example, memory 504 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and / or dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, hard disk, optical disk, and / or magnetic tape). Memory 504 may include data 506. Data 506 serves, among other things, as a repository for storing data processed, received, and generated by one or more of processor 502, memory 504, module 508, resource 510, display unit 512, communication engine 514, and authorization engine 516.

[0085] Module 508 may include, among other things, routines, programs, objects, components, data structures, etc. that perform specific tasks or implement data types. Module 508 may also be implemented as a signal processor, a state machine, a logic circuit, and / or any other device or component that manipulates signals based on operational instructions.

[0086] In addition, module 508 can be implemented in hardware as instructions executed by at least one processing unit (e.g., processor 502) or a combination thereof. The processing unit can be a general-purpose processor that executes instructions to cause a general-purpose processor to perform operations, or the processing unit can be dedicated to perform the desired functions. In another aspect of the present disclosure, module 508 can be machine-readable instructions (software) that can perform any of the described functions when executed by the processor / processing unit.

[0087] In some embodiments, module 508 may be machine-readable instructions (software) that, when executed by processor 502 / processing unit, perform any of the described functions.

[0088] Resources 510 may be physical and / or virtual components of server 104 that provide inherent capabilities and / or contribute to the performance of server 104. Examples of resources 510 may include, but are not limited to, memory (e.g., memory 504), power supply units (e.g., batteries), display units (e.g., display unit 512), etc. In addition to processor 502 and memory 504, resources 510 may also include power supply units / battery units, network units, etc.

[0089] The display unit 512 may display various types of information (e.g., media content, multimedia data, text data, etc.) to the server 104. The display unit 512 may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, a plasma cell display, an electronic ink array display, an electronic paper display, a flexible LCD, a flexible electrochromic display, and / or a flexible electrowetting display.

[0090] The communication engine 514 may receive a first MSISDN number of a first eSIM profile in a plurality of eSIM profiles in the electronic device. The first MSISDN number may be received from the MNO 102 to obtain an operational status associated with the first eSIM profile via the SCF. In an embodiment, the MNO 102 may send the first MSISDN number when receiving an incoming call from the first electronic device 106 directed to the second electronic device 108 on the first MSISDN number connected to the MNO 102, such as Figure 1 shown.

[0091] In response to receiving the first MSISDN number, the processor 502 may determine that the operating state associated with the first eSIM profile is inactive. To obtain the operating state, the processor 502 may use the first MSISDN number as a key to obtain the eUICC IDs associated with the plurality of eSIM profiles. In addition, the processor 502 may obtain a second MSISDN number associated with the second eSIM profile whose operating state is active by using the eUICC ID as a key.

[0092] In response to determining that the operating state associated with the eSIM profile is inactive, the communication engine 514 can send a second MSISDN number associated with a second eSIM profile whose operating state is active to the MNO 102 via the SCF. In response to receiving the second MSISDN with an active state, the MNO 102 can route the incoming call from the first electronic device 106 to the second eSIM.

[0093] In an embodiment of the present disclosure, the communication engine 514 may receive an eSIM profile from an electronic device. The eSIM profile may correspond to an MSISDN number. In addition, the processor 502 may associate the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile. The eSIM profile may be stored at the server 104 corresponding to a unique eUICC ID. The processor 502 may track the operating state of the eSIM profile. The operating state may be one of an active state and an inactive state.

[0094] The processor 502 may also create a table for storing MSISDN numbers associated with the eSIM profile based on a command from the user. The processor 502 may receive an update associated with the profile status. The processor 502 may generate an OTP in response to receiving the MSISDN number. The communication engine 514 may send the OTP to an electronic device including an eSIM profile with the MSISDN number. The communication engine 514 may receive the OTP from the electronic device via the MSISDN number and verify the OTP. The processor 502 may mark the MSISDN number as active in a table associated with the eSIM profile.

[0095] Figure 6 1 is a flow chart depicting a method 600 for managing incoming calls in an eSIM device having multiple eSIM profiles according to an embodiment of the present disclosure. In an embodiment, the method 600 may be performed by the MNO 102 and the server 104. Figures 1 to 5 The details of the present disclosure are explained in detail in the description of Figure 6 There is no detailed explanation in the description.

[0096] At operation 602 , method 600 includes an operation of receiving an incoming call from a first electronic device directed to a second electronic device on a first MSISDN number of a first eSIM profile among a plurality of eSIM profiles of the second electronic device.

[0097] At operation 604 , method 600 includes an operation of sending the first MSISDN number to a server to obtain an operational status associated with the first eSIM profile.

[0098] In operation 606, method 600 includes the following operation: if the operating state associated with the first eSIM profile is inactive, receiving a response from the server, the response including a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles, the operating state of the second eSIM profile being active.

[0099] At operation 608 , method 600 includes an operation of routing the incoming call on a second MSISDN number of a second eSIM profile whose operational state is active, in response to receiving the response.

[0100] Figure 7 A flow chart depicting a method 700 implemented at a server for managing incoming calls in an eSIM network according to an embodiment of the present disclosure is shown. In an embodiment, the method 700 may be performed by the server 104 and the MNO 102. Figures 1 to 6 The details of the present disclosure are explained in detail in the description of Figure 7 There is no detailed explanation in the description.

[0101] At operation 702, method 700 includes the following operations: receiving a first MSISDN number of a first eSIM profile among multiple eSIM profiles in an electronic device from an MNO to obtain an operating state associated with the first eSIM profile, wherein the MNO sends the first MSISDN number when an incoming call directed to a second electronic device is received from the first electronic device on the first MSISDN number.

[0102] At operation 704 , method 700 includes the operation of determining, in response to receiving the first MSISDN number, that an operating state associated with a first eSIM profile is inactive, wherein the server includes a plurality of eSIM profiles and an operating state associated with each of the plurality of eSIM profiles.

[0103] At operation 706 , method 700 includes the following operation: in response to determining that the operating state associated with the eSIM profile is inactive, sending a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles whose operating state is active to the MNO.

[0104] Figure 8 800 is shown, which depicts a method 800 implemented at a server for providing a connection to an eSIM in an electronic device, according to an embodiment of the present disclosure. In an embodiment, the method 700 may be performed by the server 104. Figures 1 to 7 The details of the present disclosure are explained in detail in the description of Figure 8 There is no detailed explanation in the description.

[0105] At operation 802 , method 800 includes an operation of receiving an eSIM profile from an electronic device, wherein the eSIM profile corresponds to an MSISDN number.

[0106] At operation 804 , method 800 includes an operation of associating the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile.

[0107] At operation 806, method 800 includes an operation of registering the MSISDN number at the server through an OTP authentication mechanism.

[0108] The first electronic device 910 described below may correspond to Figure 1 The second electronic device 920 described below may correspond to Figure 1 The first server 931 and the second server 932 described below may correspond to Figure 1 The third server 933 described below can be connected with Figure 1 Related to server 104.

[0109] Fig. 9 A process for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown.

[0110] refer to Fig. 9 , the first electronic device 910 may be used by user A. Three profiles (or eSIM profiles) may be used by user B. The second electronic device 920 may have three profiles. For example, profile #1 to profile #3 may correspond to MSISDN #1 to MSISDN #3, respectively.

[0111] The first electronic device 910 may dial MSISDN#3. The first electronic device 910 may request a telephone connection to the first server 931 through MSISDN#3. The first server 931 may be referred to as an originating mobile network operator (MNO) network server. The first server 931 may send an initial detection point (DP) message to a service control function (SCF) 934. The initial DP message may include information about MSISDN#3. For example, the SCF 934 may be a network element containing service logic that implements the behavior desired by the MNO.

[0112] The SCF 934 obtains (or gets / obtains) the active MSISDN from the third server 933. For example, the third server 933 may be referred to as an "always connected server". In the profile of the second electronic device 920, profile #2 (or MSISDN #2) may be activated. In the profile of the second electronic device 920, the remaining profiles (e.g., MSISDN #1 and MSISDN #3) may be deactivated. The SCF 934 may receive (or obtain) information about the MSISDN #2 corresponding to the activated profile #2 from the third server 933. The SCF 934 may instruct the first server 931 to connect to MSISDN #2. The first server 931 may perform call routing to the second server 932 via MSISDN #2. Depending on the embodiment, the MNO for the first server 931 and the MNO for the second server 932 may be distinguished.

[0113] The second server 932 may page the MSISDN#2 to the second electronic device 920. The second server 932 may receive a paging response message about the MSISDN#2 from the second electronic device 920. The second server 932 may request a telephone connection from the first server 931 through the MSISDN#2. The first server 931 may provide a telephone connection to the first electronic device 910 through the MSISDN#2. User A of the first electronic device 910 and user B of the second electronic device 920 may communicate through the first server 931 and the second server 932 through the call connection.

[0114] Fig.10 A process for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown.

[0115] refer to Fig.10 , the second electronic device 920 may include an eUICC 1001, a local profile assistance (LPA) 1002, and an always-connected client 1003. MSISDN#1 may be in a deactivated state, and MSISDN#2 may be in an active state. The always-connected client 1003 may send information about an activated MSISDN (or information about an activated number) to a third server 933. The third server 933 may update the information about the activated MSISDN.

[0116] For example, the first electronic device 910 may call MSISDN#1 among a plurality of profiles (or MSISDNs) of the second electronic device 920. Since MSISDN#1 is disabled, the call connection may fail.

[0117] The MNO network 1030 may request an activated MSISDN for MSISDN#1 from the third server 933. For example, the MNO network 1030 may include Fig. 9 The first server 931 and the second server 932.

[0118] The third server 933 may provide information about the activated MSISDN (e.g., information about MSISDN#2) to the MNO network 1030. The MNO network 1030 may attempt a phone connection through MSISDN#2. The second electronic device 920 may send a connection response message to the MNO network 1030 through MSISDN#2. The MNO network 1030 may establish a call connection between the first electronic device 910 and the second electronic device 920 based on the connection response message.

[0119] Fig.11 An example of a block diagram of a system for making a call connection with an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown. The components shown may be composed of circuits.

[0120] refer to Fig.11 , the second electronic device 920 may include an always-connected client, an eSIM, an LPA, and an eSIM manager. The always-connected client may include information about an AUTH_process (authentication process) handler and a profile ID to MSISDN list. The second electronic device 920 (eg, always-connected client) may be connected to a third server 933 through a client interface.

[0121] The third server 933 may include data storage, interface processing program, user eSIM profile management and operator query processing program. The data storage may include (or store) information about the eUICC to MSISDN list and / or information about the MSISDN to eUICC mapping.

[0122] The MNO network 1030 may include an open service access gateway, a service control part (SCP), a home location register (HLR) / home subscriber server (HSS), and a call processing unit. The MNO network 1030 may receive information about the activated MSISDN from the third server 933 .

[0123] Fig.12 An example of the operation of an electronic device having multiple MSISDNs according to an embodiment of the present disclosure is shown.

[0124] refer to Fig.12, the second electronic device 920 may operate based on multiple profiles (or eSIM profiles). The second electronic device 920 may download multiple profiles from an eSIM profile server. For example, an eSIM profile server may be referred to as a Subscription Manager-Data Preparation+ (SM-DP+).

[0125] For example, the second electronic device 920 may operate based on three user profiles. The user of the second electronic device 920 may select and activate one of the three profiles. The eSIM manager may select and activate one of the three profiles based on user input. The second electronic device 920 may use an always-connected client to store the MSISDN corresponding to the profile and the status of the profile. The second electronic device 920 may use an always-connected client to update information about the profile, the MSISDN corresponding to the profile, and the status of the profile to the third server 933.

[0126] Fig.13 An example of the operation of the third server according to an embodiment of the present disclosure is shown.

[0127] refer to Fig.13 , the third server 933 can obtain the MSISDN number and the eUICC (or eUICC identifier EID). The third server 933 can use a one-time password (OTP) mechanism to authenticate the MSISDN and store the MSISDN in an active state. The third server 933 can create a reverse mapping of the MSISDN to the EID.

[0128] When the MNO network 1030 queries the active MSISDN by transmitting the dialed MSISDN, it can retrieve the corresponding eUICC ID and use the table as a key to return the active MSISDN. When the MNO network 1030 can query the active MSISDN by sending the dialed MSISDN, it obtains the corresponding eUICC ID and can return the active MSISDN using the corresponding eUICC ID as a key.

[0129] Fig.14 The flowchart of establishing a call connection with an activated MSISDN according to an embodiment of the present disclosure is shown.

[0130] At operation 1410, the second electronic device 920 may obtain multiple eSIM profiles from the MNO. For example, the second electronic device 920 may obtain multiple eSIM profiles and store them in the eUICC element. This may be done by scanning the MNO subscription card and deriving the SM-DP+ address and securely connecting to the correct SM-DP+ to download the MNO profile.

[0131] At operation 1420, the second electronic device 920 may update the profile information and activate the profile. The second electronic device 920 (or the user of the second electronic device 920) may activate the MNO eSIM profile using an "eSIM manager" that launches the always-connected client 1003 to update the profile status. A pop-up window may appear on the screen of the second electronic device 920, asking the user to update the table with the appropriate MSISDN number corresponding to the MNO profile.

[0132] At operation 1430, the third server 933 authenticates and updates the eUICC to MSISDN mapping and activity status. For example, when the user key in the MSISDN number corresponds to the currently active profile (or eSIM profile), the always connected client 1003 can update the table with the MSISDN number and can trigger a message to the third server 933, which passes the eUICC ID (EID) and the MSISDN number as parameters for creating the user MSISDN table using the eUICC ID as a key. Before updating the table, the third server 933 can use the OTP authorization method (or OTP authorization mechanism) to confirm that the sent MSISDN is authentic and belongs to the user (or eSIM user). This operation can be repeated every time the user activates the profile for the first time. For all MSISDN numbers, the third server 733 can perform periodic OTP authentication to confirm that all MSISDN numbers have a valid subscription to the MNO, and it can delete the MSISDN when the subscription to the MNO is inactive.

[0133] At operation 1440, the third server 933 may create and update the MSISDN to EID table. For example, after creating the eSIM user information, the third server may create a table of MSISDN numbers and eUICC IDs, and the table may be used by the MNO to query active MSISDN numbers.

[0134] At operation 1450, the first electronic device 910 may initiate a call on the second electronic device 920 using MSISDN#1. For example, the user of the first electronic device 910 is Alex. The user of the second electronic device 920 is Syam. Syam knows Alex through a number associated only with MSISDN#1.

[0135] At operation 1460, the third server may get (or obtain) the active MSISDN (e.g., MSISDN#2). For example, the MNO network 1030 may collect the dialed digits and may send a query to the service control part SCP by passing MSISDN#1. The SCP may send a query to the third server 933 (through its OSA gateway for connecting to the third party server) to send the active MSISDN number of the eUICC belonging to MSISDN#2.

[0136] At operation 1470, the third server 933 may return information about MSISDN#1 to the MNO network 1030. For example, the third server 933 may obtain the eUICC ID (EID) corresponding to MSISDN#2, and may query the MSISDN DB using the EID as a key to obtain the active MSISDN for the EID. The third server 933 may send it back to the MNO network 1030. If there is no record in the DB, the third server 933 may send back the same number.

[0137] At operation 1480 , the MNO network 1030 may connect the call to the second electronic device 920 using the MSISDN# 2 .

[0138] At operation 1490, Syam is able to connect to Alex even though he dialed MSISDN#2 which is inactive within AlexeUICC using the active MSISDN#1.

[0139] Fig.15 A signal flow diagram for acquiring multiple profiles in an electronic device according to an embodiment of the present disclosure is shown.

[0140] refer to Fig.15 , the second electronic device 920 may obtain (or acquire / acquire) profile #1 (or eSIM profile #1) from MNO #1. The second electronic device 920 may download profile #1 from the local profile assistance LPA. The LPA may send a "download_order" message to the SM-DP+. The SM-DP+ may send a "confirm_order" message to the LPA. The "confirm_order" message may include information about profile #1. The LPA may store profile #1 (or eSIM profile #1) based on the information about profile #1.

[0141] The second electronic device 920 may obtain (or acquire / acquire) profile #2 (or eSIM profile #2) from MNO #2. The second electronic device 920 may download profile #2 from LPA. LPA may send a "download_order" message to SM-DP +. SM-DP + may send a "confirm_order" message to LPA. The "confirm_order" message may include information about profile #2. LPA may store profile #2 (or eSIM profile #2) based on the information about profile #2.

[0142] Fig.16 A signal flow diagram for activating one of a plurality of profiles according to an embodiment of the present disclosure is shown.

[0143] refer to Fig.16 , the second electronic device 920 may download profile #1 from the local profile assistant LPA. The LPA may download profile #1 from the SM-DP+. After downloading profile #1, the LPA may store profile #1. The LPA may start "always connect client". The LPA may create and update "profile_info_table".

[0144] The "always connect client" may request to enter the MSISDN. The second electronic device (or the eSIM manager of the second electronic device) 920 may send information to the "always connect client" on MSISDN#1. The "always connect client" may update the "profile_info_table" with the MSISDN and may set the profile status to "IN_ACTIVE". This may be repeated each time the user of the second electronic device downloads a new profile (or eSIM profile). Fig.16 The process described in .

[0145] Fig.17 A signal flow diagram for authenticating a profile according to an embodiment of the present disclosure is shown.

[0146] refer to Fig.17, the second electronic device 920 may request to activate profile #1 to the "always connect client". The "always connect client" may request to create "eSIM_user_info (eSIM user information)", and the "eSIM_user_info" is related to MSISDN #1. The third server 933 may generate an OTP. The third server 933 may send (or transmit) the OTP to the second electronic device 920 (e.g., MSISDN #1). The second electronic device 920 may confirm the OTP. For example, the second electronic device 920 may send a message to confirm the OTP.

[0147] The third server 933 may verify the OTP and may create 'eSIM_user_info' using the EID as a key. For example, MSISDN#1 may be marked as active and other profiles within the EID may be set to "In_Active". The third server 933 may create and update the MSISDN to EID table. This may be repeated each time the user of the second electronic device activates a new profile (or eSIM profile). Fig.17 The process described in .

[0148] Fig.18 A signal flow diagram between an MNO and an HLR / HSS according to an embodiment of the present disclosure is shown.

[0149] refer to Fig.18 , the MNO (or the MNO business support system BSS) may equip the HLR / HSS with an “always_eSIM_connect trigger”. For example, the MNO may send an “arm_tigger” message to the HLR / HSS. The “arm_tigger” message may include information about the SCP address. Based on the message, the HLR / HSS may update the “TDP_list” with the TDP name and SCP address. The HLR / HSS may send a “confirm_TDP” message to the MNO.

[0150] Fig.19 A signal flow diagram related to a mechanism for an MNO to provide opt-in for eSIM connectivity according to an embodiment of the present disclosure is shown.

[0151] refer to Fig.19 , the MNO may provide options to the user, such as the user may be connected to the national number only, or the user may be connected to both the national number and the international number of the called party's other active number.

[0152] For example, user #1 may subscribe to an "always connect service". User #1's electronic device may send a message to subscribe to the "always connect service". User #1 may select an option of the "always connect service" to connect only to national numbers. The message may include a parameter "Subscribe_Always_conn_svc", where the "national" field is set to Y (yes) and the "international" field is set to N (no).

[0153] The BSS (or MNO) receives a message from the electronic device of user #1. Based on receiving the message from the electronic device of user #1, the BSS may send an "update_subscriber_info_all_conn_svc (update subscriber information all connection services)" message to the HLR / HSS. The "update_subscriber_info_all_conn_svc" message may include information for updating "subscriber_info (subscriber information)".

[0154] The HLR / HSS may update 'subscriber_info' (or 'sub_info') based on the 'update_subscriber_info_all_conn_svc' message received from the BSS. The 'always conn' field of 'subscriber_info' is set to 'National'.

[0155] For example, user #2 may subscribe to an "always connect service". User #2's electronic device may send a message to subscribe to the "always connect service". User #2 may select the option of the "always connect service" for connecting to both national and international numbers. The message may include a parameter "Subscribe_Always_conn_svc", where the "national" field is set to Y (yes) and the "international" field is also set to Y (yes).

[0156] The BSS (or MNO) receives a message from the electronic device of user #2. Based on receiving the message from the electronic device of user #2, the BSS may send an "update_subscriber_info_all_conn_svc" message to the HLR / HSS. The "update_subscriber_info_all_conn_svc" message may include information for updating "subscriber_info".

[0157] The HLR / HSS may update the "subscriber_info" (or "sub_info") based on the "update_subscriber_info_all_conn_svc" message received from the BSS. The "always conn" field of "subscriber_info" is set to "National+International".

[0158] Fig. 20 A signal flow diagram related to a mechanism for acquiring an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure is shown.

[0159] Reference Fig. 20 , the caller may attempt to connect to MSISDN#1 associated with user B. The MNO (or mobile switching center MSC) may send an initial DP (detection point) message to the SCF (or SCP). The SCF may send a "Get_active_MSISDN" message to the third server 933. The third server may use the MSISDN to EID mapping table to obtain the eUICC ID, EID based on the "Get_active_MSISDN" message. The third server may obtain the active MSISDN from the "e_sim_user_db (eSIM user detection point)". The third server may send a "return" message to the SCF. The "return" message may include information about MSISDN#2. The SCF may send a "connect" message to the MNO (or MSC).

[0160] Fig.21 A signal flow diagram related to a mechanism for connecting to an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure is shown.

[0161] refer to Fig.21, the first electronic device 910 of user A can dial the second electronic device 920 of user B. The MNO can send an "intitial DP" message to the service control function SCF. The "intitial DP" message may include information about MSISDN#1 and information about the service key. The SCF can send a "get_active_MSISDN" message to the third server 933. Based on the "get_active_MSISDN" message, the third server 933 uses MSISDN#1 as a key to obtain the eUICC ID, EID. The third server 933 can use the EID key to obtain the active MSISDN. For example, the active MSISDN may be MSISDN#2.

[0162] The third server 933 may send a "Response" message to the SCF. The SCF may send a "Connect" message to the MNO. Fig.21 According to the process of the embodiment described in , user A can call user B on MSISDN#1 (or through MSISDN#1), and can be connected to user B on (or through) MSISDN#2.

[0163] Fig. 22 A signal flow diagram related to a mechanism performed when a third server fails to find an active MSISDN number using any MSISDN number according to an embodiment of the present disclosure is shown.

[0164] refer to Fig. 22 , the first electronic device 910 of user A can dial the second electronic device 920 of user B. The MNO can send an "intitial DP" message to the service control function SCF. The "intitial DP" message may include information about MSISDN#1 and information about the service key. The SCF can send a "get_active_MSISDN" message to the third server 933. Based on the "get_active_MSISDN" message, the third server 933 uses MSISDN#1 as a key to obtain the eUICC ID, EID. The third server 933 can use the EID key to obtain the active MSISDN. For example, the active MSISDN may be MSISDN#2.

[0165] For example, the third server 933 may not find the user information of MSISDN#1. The third server may send back the same MSISDN. The MNO may try to connect the call using MSISDN#1, regardless of whether the MSISDN is active.

[0166] Fig.23An example of a process for acquiring a profile according to an embodiment of the present disclosure is shown.

[0167] See also Fig.23 , SIM providers can provide eSIM to device providers. Device providers can manufacture devices with eSIM (i.e., eSIM devices). Users can purchase eSIM devices. Users (or users' electronic devices) can request activation of eSIM from operators. Based on the request, the operator can send USIM information to a profile server (e.g., SM-DP+ or SM-DS). Users can download eSIM profiles from profile servers.

[0168] Fig.24 An example of an architecture according to an embodiment of the present disclosure is shown.

[0169] refer to Fig.24 , the architecture can be configured based on CAMEL (Concise Application Message Exchange Language). The architecture may include a service layer and a network layer. The service layer may include at least one application server APPSE and an "always connect server" (or a third server 933). At least one APPSE and the "always connect server" may be connected to the "In platform (Intelligent network platform)" through an OSA gateway, and the "In platform" includes an SCP related to the global mobile communication system service control function gsmSCF. The SCP may be connected to the serving GPRS support node SGSN, the mobile switching center MSC, and the call session control function CSCF.

[0170] Fig.25 An example of a 5G network and an always-connected server interface according to an embodiment of the present disclosure is shown.

[0171] refer to Fig.25 , the service-based architecture SBA of the 5G core network is related to the network exposure function NEF. NEF can operate based on the neural network exchange format Nnef. Network operators can include NEF. The "always connect server" (one of multiple services related to NEF) can be configured based on the REST API.

[0172] For example, a method for managing incoming calls in an embedded subscriber identity module (eSIM) device having multiple eSIM profiles, performed by a mobile network operator (MNO), includes receiving an incoming call directed to a second electronic device from a first electronic device on a first mobile station integrated services digital network (MSISDN) number of a first eSIM profile among multiple eSIM profiles in a second electronic device.

[0173] For example, the method includes sending a first MSISDN number to a server to obtain an operational status associated with a first eSIM profile.

[0174] For example, the method includes receiving a response from a server based on an inactive operating state associated with a first eSIM profile, the response including a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles whose operating state is active.

[0175] For example, the method includes: in response to receiving the response, routing the incoming call on a second MSISDN number of a second eSIM profile whose operating state is active.

[0176] For example, the MNO and the server communicate with each other via a Service Control Function (SCF).

[0177] For example, routing the incoming call to the second eSIM profile includes connecting the first electronic device to the second MNO on a second MSISDN number of the second eSIM profile.

[0178] For example, a method for managing incoming calls in an eSIM network performed by a server includes receiving a first MSISDN number of a first eSIM profile among multiple eSIM profiles in an electronic device from a mobile network operator (MNO) to obtain an operating state associated with the first eSIM profile.

[0179] For example, the method includes, in response to receiving the first MSISDN number, determining that an operational state associated with the first eSIM profile is inactive.

[0180] For example, the server is configured to include a plurality of eSIM profiles and provide an operational status associated with each of the plurality of eSIM profiles.

[0181] For example, the method includes: in response to determining that the operating state associated with the eSIM profile is inactive, sending a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles whose operating state is active to the MNO.

[0182] For example, the MNO is configured to route the incoming call from the first electronic device to the second eSIM in response to receiving the second MSISDN number having an active status.

[0183] For example, sending the second MSISDN number is based on obtaining an embedded universal integrated circuit card (eUICC) identity (ID) associated with multiple eSIM profiles using the first MSISDN number as a key, and obtaining, by the server, a second MSISDN number associated with the second eSIM profile by using the eUICCID as a key, the operation state of the second MSISDN number being active.

[0184] For example, the method includes updating an operating state of the eSIM profile to an active state in response to determining that a user switches the electronic device to an eSIM profile.

[0185] For example, the method includes downloading an eSIM profile associated with the MNO by connecting the electronic device to a SM-DP+ address associated with the MNO.

[0186] For example, the method includes, after downloading, at the electronic device, an eSIM profile associated with the MNO, identifying that an eSIM profile associated with the electronic device is activated.

[0187] For example, the method includes creating a table of eSIM profiles for storing MSISDN numbers associated with the eSIM profiles.

[0188] For example, the method includes updating a table based on marking the MSISDN number as active in the table associated with the eSIM profile.

[0189] For example, the eSIM profile is downloaded from the SM-DP+ associated with the MNO.

[0190] For example, activating one of multiple eSIM profiles.

[0191] For example, remaining eSIM profiles among the plurality of eSIM profiles are deactivated.

[0192] For example, the method includes activating an eSIM profile associated with the electronic device.

[0193] For example, the method includes creating a table of eSIM profiles at a server for storing MSISDN numbers associated with the eSIM profiles.

[0194] For example, creating a table at the server includes: generating a one-time password (OTP) in response to receiving the MSISDN number, sending the OTP to a second electronic device including the eSIM profile and the MSISDN number, receiving the OTP from the second electronic device via the MSISDN number and verifying the OTP, and marking the MSISDN number as active in a table associated with the eSIM profile.

[0195] For example, a mobile network operator (MNO) for managing incoming calls in an eSIM device having multiple eSIM profiles, the MNO includes a processor.

[0196] For example, the processor is configured to cause the MNO to receive an incoming call from the first electronic device directed to the second electronic device on a first Mobile Station Integrated Services Digital Network (MSISDN) number of a first eSIM profile among a plurality of eSIM profiles in the second electronic device.

[0197] For example, the processor is configured to cause the MNO to send the first MSISDN number to the server to obtain an operational status associated with the first eSIM profile.

[0198] For example, the processor is configured to cause the MNO to receive a response from the server based on the inactive operating state associated with the first eSIM profile, the response including a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles whose operating state is active.

[0199] For example, the processor is configured to, in response to receiving the response, cause the MNO to route the incoming call on a second MSISDN number of a second eSIM profile whose operational state is active.

[0200] For example, the server includes a plurality of eSIM profiles and provides an operational status associated with each of the plurality of eSIM profiles.

[0201] For example, the MNO and the server communicate with each other via a Service Control Function (SCF).

[0202] For example, the processor is configured to cause the MNO to connect the first electronic device to the second MNO on a second MSISDN number of the second eSIM profile.

[0203] For example, a server for managing incoming calls in an eSIM network includes a processor.

[0204] For example, the processor is configured to cause the server to receive, from the MNO, a first MSISDN number of a first eSIM profile among a plurality of eSIM profiles in the electronic device to obtain an operating status associated with the first eSIM profile.

[0205] For example, the MNO is configured to send the first MSISDN number when an incoming call directed to the second electronic device is received from the first electronic device on the first MSISDN number.

[0206] For example, the processor is configured to, in response to receiving the first MSISDN number, cause the server to determine that the operational state associated with the first eSIM profile is inactive.

[0207] For example, the server is configured to include a plurality of eSIM profiles and provide an operational status associated with each of the plurality of eSIM profiles.

[0208] For example, the processor is configured to cause the server to send a second MSISDN number associated with a second eSIM profile whose operating state is active among the plurality of eSIM profiles to the MNO in response to determining that the operating state associated with the eSIM profile is inactive.

[0209] For example, the MNO is configured to route the incoming call from the first electronic device to the second eSIM in response to receiving the second MSISDN number having an active status.

[0210] For example, the processor is configured to cause the server to send the second MSISDN number based on obtaining an embedded universal integrated circuit card (eUICC) ID associated with multiple eSIM profiles using the first MSISDN number as a key, and obtaining a second MSISDN number associated with the second eSIM profile whose operating state is active by using the eUICC ID as a key.

[0211] For example, a server for providing a connection to an eSIM in an electronic device, the server comprising a processor.

[0212] For example, the processor is configured to cause the server to receive an eSIM profile from the electronic device, wherein the eSIM profile corresponds to an MSISDN number.

[0213] For example, the processor is configured to cause the server to associate the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile.

[0214] For example, the processor is configured to cause the server to register the MSISDN number at the server through an OTP authentication mechanism.

[0215] For example, the processor is configured to cause the server to update the operation state of the eSIM profile to an active state in response to determining that the user switches the electronic device to the eSIM profile.

[0216] For example, the processor is configured to cause the server to download an eSIM profile associated with the MNO at the electronic device by connecting the electronic device to the SM-DP+ address associated with the MNO.

[0217] For example, the processor is configured to cause the server to activate, via the electronic device, an eSIM profile associated with the electronic device.

[0218] For example, the processor is configured to cause the server to create a table of eSIM profiles at the server via the electronic device, the table being used to store MSISDN numbers associated with the eSIM profiles.

[0219] For example, the processor is configured to cause the server to generate a one-time password (OTP) in response to receiving the MSISDN number.

[0220] For example, the processor is configured to cause the server to send the OTP to a second electronic device including an eSIM profile having an MSISDN number.

[0221] For example, the processor is configured to cause the server to receive an OTP from the second electronic device through the MSISDN number and verify the OTP; and

[0222] The MSISDN number is marked as active in the table associated with the eSIM profile.

[0223] For example, the processor is further configured to cause the server to update a table associated with the eSIM profile based on marking the MSISDN number as active in the table.

[0224] For example, the processor is further configured to cause the server to identify subscription information associated with the electronic device.

[0225] For example, the processor is further configured to identify, based on the subscription information, whether each of the plurality of eSIM profiles is associated with a national MSISDN number.

[0226] Although specific language has been used to describe the present disclosure, it is not intended to impose any limitations thereon. It is apparent to those skilled in the art that various work modifications may be made to the method to realize the inventive concept as taught herein. The accompanying drawings and the foregoing description provide examples of embodiments. It will be appreciated by those skilled in the art that one or more of the elements described may be well combined into a single functional element. Alternatively, some elements may be divided into multiple functional elements. Elements from one embodiment may be added to another embodiment.

[0227] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods as described herein. For example, a processor (e.g., a baseband processor) as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described herein. For another example, a circuit associated with a UE, a base station, a network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described herein.

[0228] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0229] The methods according to various embodiments described in the claims and / or the specification of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0230] When implemented by software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in such a computer-readable storage medium (e.g., a non-transitory storage medium) are configured to be executed by one or more processors in an electronic device. One or more programs include instructions that cause the electronic device to perform the method according to the embodiments described in the claims or description of the present disclosure.

[0231] Such a program (e.g., software module, software) may be stored in a random access memory, a non-volatile memory including flash memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage device, a compact disk-ROM (CD-ROM), a digital versatile disk (DVD), other types of optical storage devices, or a magnetic tape cassette. Alternatively, it may be stored in a memory configured with a combination of some or all of the above. In addition, the corresponding component memories may be provided in multiple quantities.

[0232] In addition, the program can be stored in an attachable storage device that can be accessed via a communication network, such as, for example, the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a communication network configured with a combination thereof. Such a storage device can access the apparatus for executing the embodiments of the present disclosure through an external port. In addition, the apparatus for executing the embodiments of the present disclosure can access a separate storage device on a communication network.

[0233] In the above-mentioned specific embodiments of the present disclosure, the components included therein may be expressed in singular or plural form, depending on the specific embodiments proposed. However, for ease of description, such singular or plural expressions may be appropriately selected for the context presented, and the present disclosure is not limited to singular forms or plural elements. Therefore, an element expressed in plural form may be formed by a singular element, or an element expressed in singular form may be formed by a plurality of elements.

[0234] While specific embodiments have been described in the detailed description of the present disclosure, it goes without saying that various modifications are possible without departing from the scope of the present disclosure.

Claims

1. A method for managing incoming calls in an eSIM network, performed by a server, the method comprising: receiving a first MSISDN number of a first eSIM profile from a plurality of eSIM profiles in the electronic device from a mobile network operator (MNO) to obtain an operational status associated with the first eSIM profile, responsive to receiving the first MSISDN number, determining that the operational state associated with the first eSIM profile is inactive, wherein the server is configured to include the plurality of eSIM profiles and provide the operating status associated with each of the plurality of eSIM profiles; and In response to determining that the operational state associated with the eSIM profile is inactive, sending a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles to the MNO, the operational state of the second eSIM profile being active.

2. The method of claim 1, wherein the MNO is configured to, in response to receiving the second MSISDN number having the active status, route the incoming call from the first electronic device to the second eSIM.

3. The method according to claim 1, wherein: Sending the second MSISDN number is based on: obtaining an embedded universal integrated circuit card (eUICC) identity (ID) associated with the plurality of eSIM profiles using the first MSISDN number as a key; and The second MSISDN number associated with the second eSIM profile is obtained by the server by using the eUICC ID as a key, the operation state of the second MSISDN number being active.

4. The method according to claim 1, further comprising: In response to determining that the user switches the electronic device to the eSIM profile, the operation state of the eSIM profile is updated to an active state.

5. The method according to claim 1, further comprising: after downloading, at the electronic device, an eSIM profile associated with the MNO, identifying that the eSIM profile associated with the electronic device is activated; as well as A table of the eSIM profile is created to store the MSISDN number associated with the eSIM profile.

6. The method according to claim 5, wherein: Creating the table at the server includes: In response to receiving the MSISDN number, generating a one-time password (OTP); sending the OTP to a second electronic device including the eSIM profile having the MSISDN number; receiving the OTP from the second electronic device via the MSISDN number and verifying the OTP; and The MSISDN number is marked as active in the table associated with the eSIM profile.

7. The method according to claim 6, further comprising: The table is updated based on marking the MSISDN number as active in the table associated with an eSIM profile.

8. The method according to claim 5, wherein: Downloading the eSIM profile from a SM-DP+ associated with the MNO.

9. The method according to claim 1, further comprising: identifying subscription information associated with the electronic device, and Based on the subscription information, identifying whether each of the plurality of eSIM profiles is associated with a national MSISDN number.

10. The method according to claim 1, wherein: One of the plurality of eSIM profiles is activated, and The remaining eSIM profiles among the multiple eSIM profiles are deactivated.

11. A server for managing incoming calls in an eSIM network, the server comprising a processor configured to cause the server to: receiving, from the MNO, a first MSISDN number of a first eSIM profile of a plurality of eSIM profiles in the electronic device to obtain an operational status associated with the first eSIM profile, wherein the MNO is configured to send the first MSISDN number upon receiving the incoming call directed to the second electronic device on the first MSISDN number from the first electronic device; responsive to receiving the first MSISDN number, determining that the operational state associated with the first eSIM profile is inactive, in, the server being configured to include the plurality of eSIM profiles and to provide the operational status associated with each of the plurality of eSIM profiles; as well as In response to determining that the operational state associated with the eSIM profile is inactive, sending a second MSISDN number associated with a second eSIM profile of the plurality of eSIM profiles to the MNO, the operational state of the second eSIM profile being active.

12. The server according to claim 11, wherein: The MNO is configured to, in response to receiving the second MSISDN number having the active status, route the incoming call from the first electronic device to the second eSIM.

13. The server according to claim 11, wherein: The processor is further configured to cause the server to send the second MSISDN number based on: obtaining an embedded universal integrated circuit card (eUICC) ID associated with the plurality of eSIM profiles using the first MSISDN number as a key; as well as The second MSISDN number associated with the second eSIM profile is obtained by using the eUICC ID as a key, the operation state of the second MSISDN number being active.

14. The server according to claim 11, wherein: The processor is further configured to cause the server to: receiving an eSIM profile from the electronic device, wherein the eSIM profile corresponds to an MSISDN number; associating the eSIM profile with the MSISDN number by using an eUICC key associated with the eSIM profile; and The MSISDN number is registered at the server through an OTP authentication mechanism.

15. The server according to claim 14, wherein: The processor is further configured to, in response to determining that a user switches the electronic device to the eSIM profile, cause the server to update the operation state of the eSIM profile to the active state.

Images