Apparatus and method for managing events in a communication system

Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system beyond a 4th-Generation (4G) system supporting higher data rates with a technology for Internet of Things (IoT). The disclosure can be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. A user equipment (UE) is provided. The UE includes a transceiver and at least one processor, wherein the at least one processor controls the transceiver to transmit a first message requesting an event to an open intermediary server, receive event-related information from the open intermediary server in response to the first message, transmit a second message requesting the event to a profile providing server based on the event-related information, and receive information related to event processing from the profile providing server in response to the second message.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus in which a profile server registers or deletes events from at least one open intermediary server. More specifically, this disclosure relates to a method and apparatus for downloading and installing a communication service to a terminal to establish communication in a communication system.

[0002] This disclosure relates to a method and apparatus for online downloading, installation and management of files in a communication system. Background Technology

[0003] To meet the increased demand for wireless data traffic since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter-wave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have also been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0004] The internet, as a human-centric network in which humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged as a combination of IoT technology and big data processing technology connected to cloud servers. Due to the need for technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology for IoT implementation, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied. Such an IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination of existing information technology (IT) with various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0005] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence of 5G and IoT technologies. Summary of the Invention

[0006] Technical issues

[0007] With the development of wireless communication systems, various services can be provided as described above, and correspondingly, solutions for efficiently providing these services are needed.

[0008] The above information is presented as background information only to aid in understanding this disclosure. No determination or assertion is made as to whether any of the foregoing content can be applied to this disclosure as prior art.

[0009] Solution to the problem

[0010] According to one aspect of this disclosure, a method performed by a server in a wireless communication system is provided. The method includes: receiving from a mobile network operator a first message including an embedded universal integrated circuit card (eUICC) identifier and information about an open intermediary server; generating an event based on the first message; registering the event in at least one open intermediary server based on the first message; receiving from a UE (user equipment) a second message for requesting the event; and executing an event corresponding to an event identifier included in the second message.

[0011] In embodiments of this disclosure, the method further includes: sending a request message to at least one open intermediary server to request the deletion of the event when the event identifier is unidentifiable, and receiving a response message from at least one open intermediary server including the deletion result of the event.

[0012] In embodiments of this disclosure, at least one open intermediary server includes a first open intermediary server and a second open intermediary server, and the first message includes first information about the first open intermediary server and second information about the second open intermediary server.

[0013] In embodiments of this disclosure, sending a request message for requesting the deletion of an event includes: identifying a list of open intermediary servers in which the event is registered based on an event identifier, and, if it is identified that the same event has been registered in a first open intermediary server and a second open intermediary server, sending a request message for requesting the deletion of the event to the first open intermediary server and the second open intermediary server.

[0014] In embodiments of this disclosure, the method further includes: sending a third message to at least one open intermediary server based on a first message, and receiving a fourth message including an event registration result from at least one open intermediary server.

[0015] In embodiments of this disclosure, the method further includes: determining, based on a first message, whether there exists an information list of at least one alternative open intermediary server, and sending a message to a specific open intermediary server within the information list of at least one alternative open intermediary server to request event registration.

[0016] In embodiments of this disclosure, the method further includes: determining whether there is an information list of at least one root open intermediary server if there is no information list of at least one alternative open intermediary server, and sending a message for requesting event registration to all open intermediary servers in the information list of at least one root open intermediary server.

[0017] In embodiments of this disclosure, the information regarding the open intermediary server includes at least one of a fully qualified domain name (FQDN) and an object identifier IP address.

[0018] According to another aspect of this disclosure, a server is provided. The server includes: a transceiver configured to transmit and receive at least one signal; and a controller configured to be coupled to the transceiver, wherein the controller is configured to: receive a first message from a mobile network operator including an eUICC identifier and information about an open intermediary server; generate an event based on the first message; register the event in at least one open intermediary server based on the first message; receive a second message from a user equipment (UE) for requesting the event; and execute an event corresponding to an event identifier included in the second message.

[0019] Various embodiments of this disclosure may provide a method and apparatus in which a terminal selects a communication service in a communication system in order to connect to communication.

[0020] Various embodiments of this disclosure may provide a method and apparatus in which a terminal downloads a profile for communication connection online, installs the profile, and manages the profile.

[0021] Various embodiments of this disclosure can provide a method and apparatus in which a terminal can efficiently download events in a communication system.

[0022] Various embodiments of this disclosure may provide a method and apparatus in which a terminal accesses at least one open intermediary server and obtains events assigned to the terminal.

[0023] Various embodiments of this disclosure may provide a method and apparatus in which, when a terminal accesses at least one open intermediary server or profile providing server, event information and information (SM-DS Info) of at least one open intermediary server accessed for event acquisition are notified.

[0024] Various embodiments of this disclosure may provide a method and apparatus in which a profile-providing server registers the same event in at least one open intermediary server.

[0025] Various embodiments of this disclosure may provide a method and apparatus in which a profile-provided server deletes events registered in at least one open intermediary server.

[0026] Various embodiments of this disclosure may provide a method and apparatus for exchanging messages between an open mediation server (SM-DS) and a profile providing server (SM-DP+).

[0027] To address the aforementioned problems, this disclosure provides a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station, processing the received first control signal, and transmitting a second control signal generated based on the processing to the base station.

[0028] According to another aspect of this disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller, wherein the controller controls the transceiver to send a first message requesting an event to an open intermediary server, receives event-related information from the open intermediary server in response to the first message, sends a second message requesting the event to a profile providing server based on the event-related information, and receives information related to event processing from the profile providing server in response to the second message.

[0029] According to another aspect of this disclosure, a profile providing server is provided in a wireless communication system. The profile providing server includes a transceiver and a controller, wherein the controller controls the transceiver to generate events and receive event registration request messages for at least one open intermediary server from an operator server, and controls the transceiver to generate events corresponding to the request messages and register the events in at least one open intermediary server.

[0030] According to another aspect of this disclosure, an open intermediary server is provided in a wireless communication system. The open intermediary server includes a transceiver and a controller, wherein the controller controls the transceiver to receive event registration request messages from a profile providing server or another open intermediary server to register events, and to register events in response to the event registration request messages, and wherein the events are associated with events generated by the profile providing server.

[0031] According to another aspect of this disclosure, a profile providing server is provided in a wireless communication system. The profile providing server includes a transceiver and a controller, wherein the controller controls the transceiver to receive event request messages from a terminal, determines the validity of event-related information included in the event request messages, and controls the transceiver to transmit information about event processing based on the determination of the validity of the event-related information.

[0032] The technical topics pursued in this disclosure may not be limited to those described above, and other technical topics not mentioned will be clearly understood by those skilled in the art from the following description.

[0033] Other aspects, advantages, and distinctive features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings.

[0034] Beneficial effects of the invention

[0035] The aspects of this disclosure at least address the aforementioned problems and / or disadvantages, and at least provide the following advantages. Accordingly, one aspect of this disclosure is to provide a method and apparatus for downloading and installing a communication service to a terminal, thereby connecting to communication in a communication system.

[0036] Another aspect of this disclosure is to provide a bundle or file that is installed in one device and can be sent and installed to another device via one of a variety of available options.

[0037] Additional aspects will be set forth in part in the description which follows, and will also be apparent in part from the description, or may be learned by practice of the presented embodiments.

[0038] According to various embodiments of this disclosure, a terminal in a communication system can request an event to be registered in at least one open intermediary server.

[0039] According to various embodiments of this disclosure, a profile providing server in communication can generate events upon request from an operator server, and can register the corresponding events in at least one open intermediary server.

[0040] According to another aspect of this disclosure, a profile providing server is provided in a communication system. When requesting an open intermediary server registration event, the profile providing server includes a message configured to request a third open intermediary server to register an event corresponding to that event after the open intermediary server registration event.

[0041] According to various embodiments of this disclosure, when an open intermediary server in a communication system requests a profile providing server or another open intermediary server to register an event, and if a message requesting a third open intermediary server to register the event is included, the open intermediary server may register the event, generate another event corresponding to the event, and then register the event with the requested third open intermediary server.

[0042] According to various embodiments of this disclosure, when a terminal in a communication system accesses an open mediation server or a profile providing server and requests an event, the terminal can provide information about the previously accessed open mediation server (SM-DS Info) to assist in deleting unnecessary events. Attached Figure Description

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

[0044] Figure 1 This is a diagram illustrating a method of connecting a user equipment (UE) to a mobile communication network using a general-purpose integrated circuit card (UICC) with a fixed profile installed thereon, according to an embodiment of the present disclosure;

[0045] Figure 2 This is a diagram illustrating the connection between a UE, an open mediation server, and a profile providing server according to an embodiment of this disclosure;

[0046] Figure 3 This is a diagram illustrating the message exchange process when an open intermediary server operates in conjunction with at least one profile providing server according to an embodiment of the present disclosure;

[0047] Figure 4 This is a diagram illustrating the message exchange process when a profile providing server operates in conjunction with at least one or more open intermediary servers according to an embodiment of this disclosure;

[0048] Figure 5 This is a diagram illustrating a message exchange process according to an embodiment of the present disclosure when a UE operates in conjunction with at least one root open intermediary server and a profile provides a server operating in conjunction with at least one or more alternative open intermediary servers;

[0049] Figure 6 This is a flowchart illustrating a process according to embodiments of the present disclosure for registering events by a profile providing server or an open intermediary server (i.e., an RSP server (SM-XX)) and requesting event registration from another open intermediary server;

[0050] Figure 7 This is a diagram illustrating the components of a UE according to an embodiment of the present disclosure;

[0051] Figure 8 This is a diagram illustrating the components of a server 800 provided in a summary document according to an embodiment of the present disclosure; and

[0052] Figure 9 This is a diagram illustrating the components of an open mediation server 900 according to an embodiment of the present disclosure.

[0053] Throughout the accompanying drawings, the same reference numerals are used to denote the same elements. Detailed Implementation

[0054] The following description, provided with reference to the accompanying drawings, is intended to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these are to be considered exemplary only. Accordingly, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and constructions may be omitted.

[0055] The terms and words used in the following description and claims are not limited to their literal meaning, but are used by the inventors only to enable a clear and consistent understanding of this disclosure. Accordingly, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is provided for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.

[0056] It should be understood that the singular forms “a,” “an,” and “the” include plural indicators unless the context explicitly specifies otherwise. Thus, for example, referring to “component surface” includes referring to one or more such surfaces.

[0057] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. In the drawings, identical or corresponding elements have the same reference numerals.

[0058] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the embodiments described below in conjunction with the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in a variety of different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0059] Here it will be understood that each box in a flowchart illustration, and combinations of boxes in a flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create parts for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium, which can instruct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of manufacture including instruction parts that implement the functions specified in one or more flowchart boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide operations for implementing the functions specified in one or more flowchart boxes.

[0060] Furthermore, each box in the flowchart diagram may represent a module, code segment, or code section, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions mentioned in the boxes may appear out of order. For example, two boxes shown consecutively may actually execute substantially concurrently, or these boxes may sometimes execute in reverse order, depending on the functions involved.

[0061] As used herein, a “cell” refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, a “cell” is not always limited to software or hardware. A “cell” can be configured to be stored in addressable memory or to execute one or more processors. Therefore, a “cell” includes, for example, software elements, object-oriented software elements, class elements or task elements, procedures, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a “cell” can be combined into a smaller number of elements or “cells”, or divided into a larger number of elements or “cells.” Furthermore, elements and “cells” can be implemented to reproduce one or more CPUs within a device or secure multimedia card.

[0062] The specific terms used in the following description are provided to aid in understanding this disclosure, and the use of these specific terms may be changed to other forms without departing from the technical spirit of this disclosure.

[0063] First, the terminology used in this disclosure is defined.

[0064] A Universal Integrated Circuit Card (UICC) is a smart card inserted into a mobile communication terminal and used; it is also called a UICC card. A UICC may include an access control module for accessing a mobile operator's network. Examples of access control modules include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), and an IP Multimedia Service Identity Module (ISIM). A UICC that includes a USIM is often referred to as a USIM card. Similarly, a UICC that includes a SIM module is often referred to as a SIM card.

[0065] The terms “SIM card,” “UICC card,” “USIM card,” and “UICC including ISIM” disclosed in this disclosure may be used as having the same meaning in this disclosure. For example, even for a SIM card, this technology application may be equivalently applied to a USIM card, an ISIM card, or a regular UICC card.

[0066] A SIM card can store a mobile communication subscriber's personal information and can perform subscriber authentication and traffic security key generation when accessing a mobile communication network, thereby enabling secure mobile communication use.

[0067] At the time of this disclosure, SIM cards are typically manufactured as dedicated cards for a specific mobile operator during card manufacturing, at the request of that operator. Authentication information for network access to that operator (e.g., Universal Subscriber Identity Module (USIM) application, International Mobile Subscriber Identity (IMSI), K-value, OPC value, etc.) is pre-loaded onto the card and shipped. Thus, the manufactured SIM card is delivered to the corresponding mobile operator and provided to subscribers. Subsequently, if necessary, the installation, modification, and deletion of applications within the UICC can be managed using technologies such as over-the-air (OTA). Subscribers can use the network and application services of the corresponding mobile operator by inserting the UICC card into their own mobile communication terminal. When changing terminals, by moving the UICC card from the existing terminal to the new terminal and inserting it, the authentication information, mobile phone number, and personal phone book stored in the UICC card can be used unchanged in the new terminal.

[0068] However, for mobile communication terminal users, SIM cards are inconvenient for receiving services from other mobile operators. Physically obtaining a SIM card to receive services from a mobile operator is inconvenient. For example, when traveling to another country, obtaining a local SIM card to receive local mobile communication services is inconvenient. Roaming services alleviate this inconvenience to some extent, but the costs are relatively high, and there's the issue of not being able to receive services if there's no contract between mobile operators.

[0069] Meanwhile, this inconvenience can be largely resolved when the SIM module is remotely downloaded and installed on the UICC card. For example, the SIM module for the mobile communication service a user wants to use at the desired time can be downloaded to the UICC card. This UICC card can also be used by downloading and installing multiple SIM modules and selecting only one. This UICC card can be fixed to the terminal or not. Specifically, a UICC fixed to the terminal is called an embedded UICC (UICC). Generally, an eUICC refers to a UICC card fixed to the terminal and capable of remotely downloading and selecting SIM modules. In this disclosure, UICC cards capable of remotely downloading and selecting SIM modules are collectively referred to as eUICCs. For example, among UICC cards capable of remotely downloading and selecting SIM modules, UICC cards fixed to or not fixed to the terminal are collectively referred to as eUICCs. Furthermore, the downloaded SIM module information is commonly used as the term "eUICC profile," or more simply as "profile."

[0070] The terminology used in this disclosure will be described below.

[0071] In this disclosure, the UICC is a smart card inserted into and used in a mobile communication terminal, and personal information (such as network access authentication information, phonebook, and SMS for mobile communication subscribers) is stored in the UICC. When accessing a mobile communication network (such as GSM, WCDMA, LTE, etc.), the UICC refers to a chip that enables secure mobile communication by performing subscriber authentication and traffic security key generation. Depending on the type of mobile communication network accessed by the subscriber, the UICC is loaded with communication applications (such as Subscriber Identity Module (SIM), Universal SIM (USIM), and IP Multimedia SIM (ISIM)) and can provide advanced security features for loading various applications (such as e-wallets, ticketing, e-passports, etc.).

[0072] In this disclosure, eUICC (embedded UICC) is a security module in the form of a chip embedded in a terminal, rather than a removable type that can be plugged into and removed from the terminal. The eUICC can use over-the-air (OTA) download and installation profiles. The eUICC can be named a UICC whose profile can be downloaded and installed.

[0073] In this disclosure, the method for downloading and installing a profile using OTA technology in an eUICC can be applied to removable UICCs that can be inserted into and removed from a terminal. For example, embodiments of this disclosure can be applied to UICCs that can use OTA technology to download and install profiles.

[0074] In this disclosure, the term UICC can be used interchangeably with SIM, and the term eUICC can be used interchangeably with eSIM.

[0075] In this disclosure, a profile can mean that applications, file systems, authentication key values, etc., stored in UICC are packaged as software.

[0076] In this disclosure, a USIM profile may have the same meaning as a profile, or it may mean that the information included in the USIM application within the profile is packaged in software form.

[0077] In this disclosure, enabling a profile on a terminal means changing the profile's state to an enabled state and configuring the terminal to receive communication services through the mobile operator providing the profile. A profile in an enabled state can be referred to as an "enabled profile".

[0078] In this disclosure, disabling a profile on a terminal means changing the profile's state to a disabled state and configuring the terminal to not receive communication services through the mobile operator providing the profile. A profile in a disabled state can be referred to as a "disabled profile".

[0079] In this disclosure, deleting a profile on a terminal can mean changing the profile's state to a deleted state and configuring the terminal so that the profile is no longer enabled or disabled. A profile in a deleted state can be referred to as a "deleted profile".

[0080] In this disclosure, enabling, disabling, or deleting profiles on a terminal can mean the following: merely marking each profile as about to be enabled, disabled, or deleted, without immediately changing the state of each profile to enabled, disabled, or deleted, and then changing the state of each profile to enabled, disabled, or deleted after the terminal or its UICC performs a specific operation (e.g., performing a refresh or reset command). Marking a specific profile as a predetermined state (about to be enabled, disabled, or deleted) is not necessarily limited to displaying one predetermined state of a profile. It is also possible to display one or more profiles with the same or different predetermined states, to display one profile with one or more predetermined states, or to display one or more profiles with one or more predetermined states that are equivalent to or different from each other.

[0081] Furthermore, when the terminal displays one or more predetermined states of any profile, the two displays can be combined into one. For example, when a profile is marked as to be disabled and to be deleted, the profile can also be combined and displayed as to be disabled and deleted.

[0082] Furthermore, the operation of displaying a predetermined state of one or more profiles on the terminal can be performed sequentially or simultaneously. Additionally, the operation of displaying a predetermined state of one or more profiles on the terminal and subsequently changing the actual profile state can be performed sequentially or simultaneously.

[0083] In this disclosure, a profile provisioning server includes functions for generating profiles, encrypting generated profiles, generating profile remote management commands, or encrypting generated profile remote management commands, and can be represented as subscription manager data preparation (SM-DP), subscription manager data preparation enhancement (SM-DP+), an off-card entity of a profile domain, a profile encryption server, a profile creation server, a profile provisioner (PP), a profile provider, and a profile provisioning credential (PPC) holder (PPC holder).

[0084] In this disclosure, the profile management server may be represented as a subscriptionmanager secure routing (SM-SR), a subscriptionmanager secure routing enhancement (SM-SR+), an off-card entity of the eUICC profile manager or a profile management credential (PMC) holder (PMC holder), and an eUICC manager (EM).

[0085] When a profile providing server is mentioned in this disclosure, it can also refer to a combination of the functions of a profile management server. Therefore, in various embodiments of this disclosure, i.e., as described below, the operation of the profile providing server is also possible within the profile management server. Clearly, the operation of the profile management server or SM-SR can be described in the same manner as being performed within the profile providing server.

[0086] In this disclosure, an open intermediary server can be represented as a subscriptionmanager discovery service (SM-DS), a discovery service (DS), a root open intermediary server (root SM-DS), and an alternative open intermediary server (alternative SM-DS). An open intermediary server can receive event registration requests (register event requests or event registration requests) from one or more profile providing servers or open intermediary servers. Furthermore, one or more open intermediary servers can be used in combination. In this case, a first open intermediary server can receive event registration requests from a second open intermediary server and a profile providing server.

[0087] In this disclosure, the profile providing server and the open intermediary server can be collectively referred to as a "remote SIM provisioning (RSP) server". The RSP server can be represented as a subscription manager XX (SM-XX).

[0088] In this disclosure, eSIM capability may be collectively referred to as “Remote SIM Provisioning Capability or RSP Capability”.

[0089] As used in this disclosure, the term "terminal" refers to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transceiver unit (WTRU), mobile node, mobile device, or other terms. Various embodiments of a terminal include cellular phones, smartphones with wireless communication capabilities, personal digital assistants (PDAs) with wireless communication capabilities, wireless modems, portable computers with wireless communication capabilities, photographic devices (such as digital cameras) with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback home appliances with wireless communication capabilities, internet-connected home appliances capable of wirelessly accessing and browsing the internet, and portable units or terminals combining these capabilities. Furthermore, a terminal may include, but is not limited to, machine-to-machine (M2M) terminals and machine-type communication (MTC) terminals / devices. In this disclosure, a terminal may be referred to as an electronic device.

[0090] In this disclosure, the electronic device may have a built-in UICC with downloadable and installable profiles. When the UICC is not embedded in the electronic device, a UICC physically separate from the electronic device can be inserted into and connected to the electronic device. For example, a UICC in card form can be inserted into the electronic device. The electronic device may include a terminal, and in this case, the terminal may be a terminal that includes a UICC with downloadable and installable profiles. The UICC may be embedded in the terminal, and when the terminal and the UICC are separated, the UICC can be inserted into and connected to the terminal. The UICC with downloadable and installable profiles may be referred to as, for example, an eUICC.

[0091] In this disclosure, a terminal or electronic device may include software or an application installed on the terminal or electronic device for controlling a UICC or eUICC. The software or application installed on the terminal or electronic device for controlling a UICC or eUICC may be referred to as, for example, a local profile assistant (LPA).

[0092] In this disclosure, a profile identifier may refer to a factor that matches a profile ID, integrated circuit card ID (ICCID), match ID, event ID, activation code, activation code token, command code, command code token, signed command code, unsigned command code, ISD-P, or profile domain (PD). The profile ID may indicate a unique identifier for each profile. The profile ID may also include the address of a profile providing server (SM-DP+) that can index the profile. Furthermore, the profile ID may also include the signature of the profile providing server (SM-DP+).

[0093] In this disclosure, the eUICC identifier (eUICC ID) can be a unique identifier for the eUICC embedded in the terminal, and can be referred to as the EID. Furthermore, when a supply profile is pre-loaded in the eUICC, the eUICC ID can be the profile ID of the corresponding supply profile. Additionally, as in embodiments of this disclosure, when the terminal and the eUICC chip are not separate, the eUICC ID can be the terminal ID. Furthermore, the eUICC ID can refer to a specific security domain of the eUICC chip.

[0094] In this disclosure, a profile container may be referred to as a profile field. A profile container may be a security field.

[0095] In this disclosure, the Application Protocol Data Unit (APDU) can be a message used for communication between the terminal and the eUICC. Furthermore, the APDU can be a message used for communication between the PP or PM and the eUICC.

[0096] In this disclosure, the Profile Provisioning Certificate (PPC) can be a means of mutual authentication, profile encryption, and signing between the profile providing server and the eUICC. The PPC may include a symmetric key, a Shamir Adleman (RSA) certificate and private key, an Elliptic Curve Cryptography (ECC) certificate and private key, a root certification authority (CA), and one or more of a certificate chain. Furthermore, when multiple profile providing servers exist, different PPCs for each of the multiple profile providing servers can be stored in the eUICC or used.

[0097] In this disclosure, a Profile Management Certificate (PMC) can be a means of mutual authentication between the profile management server and the eUICC, as well as for encrypting and signing transmitted data. The PMC may include a symmetric key, an RSA certificate and private key, an ECC certificate and private key, a root CA, and one or more certificate chains. Furthermore, when multiple profile management servers exist, different PMCs for each of the multiple profile management servers can be stored in the eUICC or used.

[0098] In this disclosure, AID can be an application identifier. This value can be a separator that distinguishes different applications within eUICC.

[0099] In this disclosure, an event can be a generic term for profile download, remote profile management, or other profile or eUICC management / processing commands. An event may be named a Remote SIM Provisioning Operation (RSP Operation) or an event log, and each event may be referred to as including data comprising at least one of the following: a corresponding event identifier (Event ID or EventID) or matching identifier (Matching ID or MatchingID), the address (FQDN, IP address, or URL) of the profile providing server (SM-DP+) or open intermediary server storing the event, a signature of the profile providing server (SM-DP+) or open intermediary server (SM-DS), and a digital certificate of the profile providing server (SM-DP) or open intermediary server (SM-DS). Data corresponding to an event may be referred to as an activation code or command code. Part or all of the process used to use the command code may be referred to as an "activation code processing procedure," "command code processing procedure," "activation code procedure," "command code procedure," "Local Profile Assistant Application Programming Interface (LPA API) procedure," "LPA API procedure," or "LPA API processing procedure." Profile download may be used interchangeably with profile installation. Furthermore, event type can also be used as a term to indicate whether a specific event is a profile download, remote profile management (e.g., deletion, enabling, disabling, replacing, updating, etc.), or other profile or eUICC management / processing commands, and can be named operation type, operation class, event request type, event class, event request class, etc. As for arbitrary event identifiers (EventID or MatchingID), the path from which the terminal obtains the corresponding event identifier (EventID or MatchingID) or the purpose of use (EventID source or MatchingID source) can be specified.

[0100] In this disclosure, the term "package" can be used interchangeably with "profile" or as a term to indicate a data object of a specific profile, and can be named Profile TLV or Profile Package TLV. When a profile package is encrypted using encryption parameters, it can be named Protected Profile Package (PPP) or Protected Profile Package TLV (PPP TLV). When a profile package is encrypted using encryption parameters that can only be decrypted by a specific eUICC, it can be named Bound Profile Package (BPP) or Bound Profile Package TLV (BPP TLV). A Profile Package TLV can be a dataset representing information that constitutes a profile in TLV (Label, Length, Value) format.

[0101] In this disclosure, Local Profile Management (LPM) may be named Profile Local Management, Local Management, Local Management Command, Local Command, Local Profile Management Data Packet (LPM Data Packet), Profile Local Management Data Packet, Local Management Data Packet, Local Management Command Data Packet, or Local Command Data Packet. LPM can be used to update the status (enable, disable, or delete) of a specific profile or to update the content of a specific profile (e.g., profile nickname or profile summary information (profile metadata), etc.) via software installed in a terminal. LPM may include one or more local management commands. In this case, for each local management command, the target profile for each local management command may be the same or different.

[0102] In this disclosure, Remote Profile Management (RPM) may be named Profile Remote Management, Remote Management, Remote Management Command, Remote Command, Remote Profile Management Data Packet (RPM Data Packet), Profile Remote Management Data Packet, Remote Management Data Packet, Remote Management Command Data Packet, and Remote Command Data Packet. RPM can be used to update the status of a specific profile (enabled, disabled, or deleted) or to update the content of a specific profile (e.g., profile nickname or profile summary information (profile metadata), etc.). RPM may include one or more remote management commands. In this case, for each remote management command, the target profile for each remote management command may be the same or different.

[0103] In this disclosure, a certificate or digital certificate may indicate a digital certificate used in mutual authentication based on asymmetric keys, which includes a pair of public keys (PK) and a secret key (SK). Each certificate includes one or more public keys (PK), a public key identifier (PKID) corresponding to each public key, and an identifier and digital signature of the certificate issuer (CI) that issued the corresponding certificate.

[0104] In addition, certificate issuers can be named certificate issuers, certificate authorities (CAs), certification authorities, etc.

[0105] In this disclosure, the public key (PK) and the public key identifier (PKID) are used interchangeably and have the same meaning as: a certificate containing a specific public key or a corresponding public key, a portion of a specific public key or a portion of a certificate containing a corresponding public key, the result of an operation on a specific public key (e.g., a hash) and the result of an operation on a certificate containing a corresponding public key (e.g., a hash), the result of an operation on a portion of a specific public key (e.g., a hash) and the result of an operation on a certificate containing a corresponding public key (e.g., a hash), or storage space where data is stored.

[0106] In this disclosure, the association between certificates can be termed a certificate chain or certificate hierarchy when a certificate issued by one certificate issuer (primary certificate) is used to issue another certificate (secondary certificate), or when a secondary certificate is used to jointly issue a third or higher-level certificate. In this case, the CI certificate used for the initial certificate issuance is the root certificate, top-level certificate, root CI, root CI certificate, root CA, or root CA certificate.

[0107] In this disclosure, "mobile operator" can refer collectively to all enterprises, business supporting systems (BSS), operational supporting systems (OSS), point-of-sale (POS) terminals, and other IT systems that provide communication services to terminals. Furthermore, in this disclosure, "communication operator" is not limited to referring to only one specific enterprise entity providing communication services, and "communication operator" can be used as a term to refer to a group or association (association or consortium) of one or more enterprises, or to represent a representative of such group or association. Additionally, in this disclosure, a mobile operator can be named an operator (Op or OP.), mobile network operator (MNO), service provider (SP), profile owner (PO), etc., and each mobile operator can be configured or assigned at least one name and / or object identifier (OID). When a mobile operator refers to a group or association or representative of more than one enterprise entity, the name or unique identifier of any group or association or representative can be a name or unique identifier shared by all entities affiliated with the respective group or association, or all entities cooperating with the representative.

[0108] In this disclosure, AKA can indicate authentication and key negotiation, and can indicate the authentication algorithm used to access 3GPP and 3GPP2 networks.

[0109] In this disclosure, K is the cryptographic key value stored in eUICC for the AKA authentication algorithm.

[0110] In this disclosure, OPc is a parameter value used for the AKA authentication algorithm that can be stored in eUICC.

[0111] In this disclosure, NAA is a network access application, and may be an application (such as USIM or ISIM) stored in UICC for accessing the network. NAA may be a network access module.

[0112] In this disclosure, indicators can be used to indicate the need for or lack of any function, configuration, or operation, or they can be used to indicate the corresponding function, configuration, or operation itself. Furthermore, in this disclosure, indicators can be represented in various forms, such as strings or alphanumeric strings, operators representing true / false (Boolean values ​​TRUE or FALSE), bitmaps, arrays, etc. Other expressions with the same meaning can be used interchangeably.

[0113] In describing this disclosure, detailed descriptions of relevant known functions or configurations will be omitted if it is determined that such detailed descriptions may unnecessarily obscure the essential points of this disclosure.

[0114] Figure 1 This is a diagram illustrating a method for connecting a UE to a mobile communication network using a UICC with a fixed profile installed thereon, according to an embodiment of the present disclosure.

[0115] Reference Figure 1 The UICC 120 can be inserted into the UE 110. For example, the UICC 120 can be removable or can be pre-built into the UE.

[0116] A UICC with a fixed profile means that the "access information" available to a specific mobile operator is fixed. For example, the access information could be the IMSI as a subscriber identifier and a K or Ki value that needs to be authenticated with the network along with the IMSI.

[0117] According to various embodiments, the UE 110 can use the UICC 120 to perform authentication with the mobile operator's authentication processing system (e.g., Home Location Register (HLR) or AuC). For example, the authentication process can be an authentication and key agreement (AKA) process. When authentication is successful, the UE can use mobile communication services, such as telephone calls or mobile data usage on the mobile operator's network 130 using the mobile communication system.

[0118] Figure 2 This is a diagram illustrating the connection between a UE, an open mediation server, and a profile providing server according to an embodiment of this disclosure.

[0119] Reference Figure 2 UE 250 can connect to the first open intermediary server 260, the second open intermediary server 263 and the third open intermediary server 265 respectively using links 211, 213 and 215.

[0120] For example, the addresses (FQDN, IP address, or URL) of the first open mediation server 260, the second open mediation server 263, and the third open mediation server 265 can be stored in the UE 250 or in the eUICC included in the UE 250. In this case, the first open mediation server 260, the second open mediation server 263, and the third open mediation server 265 can be referred to as the root open mediation server (root SM-DS).

[0121] Furthermore, when only the address of the first open intermediary server 260 is stored in the UE 250 or the eUICC included in the UE, the address of the second open intermediary server 263 can be notified to the UE through the first open intermediary server 260. For this purpose, the second open intermediary server 263 can register its own address with the first open intermediary server 260 via link 221. In this case, the first open intermediary server 260 and the second open intermediary server 263 can be referred to as the root open intermediary server (root SM-DS) and the alternative open intermediary server (alternate SM-DS), respectively.

[0122] Furthermore, when only the address of the first open intermediary server 260 is stored in the UE 250 or the eUICC included in the UE, the address of the second open intermediary server 263 can be notified to the UE through the first open intermediary server 260. Additionally, the address of the third open intermediary server 265 can be notified to the UE through the second open intermediary server 263. For this purpose, the second open intermediary server 263 can register its own address with the first open intermediary server 260 via link 221, and the third open intermediary server 265 can register its own address with the second open intermediary server 263 via link 223. In this case, the first open intermediary server 260 can be referred to as the root open intermediary server (root SM-DS), and the second open intermediary server 263 and the third open intermediary server 265 are alternative intermediary servers (alternate SM-DS).

[0123] Furthermore, when only the addresses of the first open intermediary server 260 and the third open intermediary server 265 are stored in the UE 250 or the eUICC included in the UE, the address of the second open intermediary server 263 can be notified to the UE through the first open intermediary server 260 or the third open intermediary server 265. In this case, the first open intermediary server 260 and the third open intermediary server 265 can be referred to as the root open intermediary server (root SM-DS), and the second open intermediary server 263 is the alternative open intermediary server (alternate SM-DS).

[0124] like Figure 2As shown, the first open intermediary server 260 can connect to the first profile providing server 270 via link 201. For example, the first profile providing server 270 can generate specific events, and the generation of the corresponding events can be registered with the first open intermediary server 260 via link 201.

[0125] like Figure 2 As shown, the first profile providing server 270 can connect to the first open intermediary server 260 and the second open intermediary server 263 via links 201 and 207, respectively. For example, the first profile providing server 270 can generate specific events and can register the generation of events with the first open intermediary server 260 and the second open intermediary server 263 via links 201 and 207, respectively.

[0126] like Figure 2 As shown, the second profile providing server 273 can be indirectly connected to the first open intermediary server 260 via the second open intermediary server 263. For example, when a specific event is generated and its generation is registered with the second open intermediary server 263 via link 203, the second profile providing server 273 can request that the generation and the registration of the generation be forwarded to the first open intermediary server 260. In this case, the second profile providing server 273 can make a request including information from the first open intermediary server 260. In this case, the second open intermediary server 263 can re-register the event of the second profile providing server 273 with the first open intermediary server 260 via link 221. The information from the first open intermediary server 260 provided by the second profile providing server 273 may include at least one of the following information.

[0127] Forwarding indicator

[0128] The fully qualified domain name (FQDN) of the open intermediary server will be forwarded.

[0129] The forwarded information will be a unique object identifier (object ID or OID) of the open mediation server.

[0130] The IP address of the open intermediary server will be forwarded.

[0131] The URL forwarded is used to invoke specific functions of the Open Mediation Server.

[0132] like Figure 2As shown, the third profile providing server 275 can be indirectly connected to the first open intermediary server 260 through the third open intermediary server 265 and the second open intermediary server 263. For example, when a specific event is generated and its generation is registered in the third open intermediary server 265 via link 205, the third profile providing server 275 can request that the generation and its registration be sequentially forwarded to the second open intermediary server 263 and the first open intermediary server 260. In this case, the third profile providing server 275 can request this while including information from both the second open intermediary server 263 and the first open intermediary server 260. In this case, the third open intermediary server 265 can re-register the event of the third profile providing server 275 in the second open intermediary server 263 via link 223.

[0133] like Figure 2 As shown, the second profile providing server 273 can be indirectly connected to the first open intermediary server 260 to the third open intermediary server 265 via the second open intermediary server 263. For example, when a specific event is generated and the generation of the corresponding event is registered in the second open intermediary server 263 via link 203, the second profile providing server 273 can request that the generation and the registration of the generation be forwarded to the first open intermediary server 260 to the third open intermediary server 265. In this case, the second profile providing server 273 can request this while including information from the first open intermediary server 260 to the third open intermediary server 265. In this case, the second open intermediary server 263 can re-register the events of the second profile providing server 273 in the first open intermediary server 260 via link 221. Furthermore, the second open intermediary server 263 can re-register the events of the second profile providing server 273 in the third open intermediary server 265 via link 223.

[0134] Please refer to later Figures 3 to 4 The document describes the detailed operation and message exchange process between UE 250, first open intermediary server 260, second open intermediary server 263, third open intermediary server 265, first profile providing server 270, second profile providing server 273 and third profile providing server 275 according to various embodiments.

[0135] Figure 3 This is a diagram illustrating the message exchange process when an open intermediary server operates in conjunction with at least one profile providing server according to an embodiment of the present disclosure.

[0136] Reference Figure 3In operation 3001, UE 250 may display a device information code (DIC) on its display, including the eUICC ID (EID) of the eUICC in UE 250 and information about at least one or more open mediation servers that the UE can access. The DIC may be in the form of a user-readable string or a QR code. The open mediation server provided by UE 250 may be a root open mediation server, and the information of the open mediation server may include at least one of the following:

[0137] Open intermediary server FQDN

[0138] A unique object identifier (object ID or OID) for an open mediation server.

[0139] Open the IP address of the intermediary server

[0140] In operation 3002, UE 250 can provide DIC to the operator's point of sale (PoS) 300. Various methods, such as QR code scanning and user input, can be used as input methods via the operator's PoS 300. The operator's PoS 300 can obtain the eUICC ID (EID) of the eUICC in UE 250 and information about at least one or more root open intermediary servers that the UE can access from the provided DIC.

[0141] In operation 3003, the operator's PoS 300 can send the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the UE to the operator server 303. Regarding the method by which the operator server 303 obtains the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the UE, it should be noted that methods other than those described in operations 3001, 3002, and 3003 can be used. For example, by using the eUICC ID, a request can be made to a third server to obtain information about root open intermediary servers supported by the UE. Furthermore, the operator may already possess information about root open intermediary servers corresponding to the eUICC ID.

[0142] In operation 3004, the operator server 303 may request the generation of an event from the first profile providing server 270. In this case, the event generation request may include at least one of the eUICC ID (EID) of the eUICC in the UE 250 and information about open intermediary servers supported by the UE. There may be at least one or more pieces of information about open intermediary servers. For example, the event generation request in operation 3004 may include an event generation request message sent by the operator server 303 to the first profile providing server 270, including at least one of the eUICC ID (EID) of the eUICC in the UE 250 and the root SM-DS address of the first root open intermediary server 260 where event generation will be registered, and the first profile providing server 270 responding with an event generation response message to notify the operator server 303 of the event generation result. For ease of illustration, Figure 3 Operation 3004 is represented using only the eUICC identifier (EID) and the address of the first open intermediary server 260. However, it should be noted that event generation includes the exchange of an event generation request message and an event generation response message as described above, wherein the event generation request message may include at least one or more of the aforementioned factors (i.e., the eUICC ID and at least one or more open intermediary server addresses). Clearly, these considerations also apply to the figures described later.

[0143] In operation 3005, the first profile providing server 270 can register the generated event with the first root open intermediary server 260. For example, the event registration in operation 3005 may include the first profile providing server 270 sending an event registration request message (register event request) to the first root open intermediary server 260, including an event ID (Matching ID), the eUICC ID (EID) of the eUICC in the UE 250, the address (SM-DP+ address) of at least one or more profile providing servers 270, and a forwarding indicator configured as "false," and the first root open intermediary server 260 responding with an event registration response message (register event response) to notify the first profile providing server 270 of the event registration result. For ease of drawing, Figure 3Operation 3005 is represented as using only the eUICC identifier (EID) and event identifier (MatchingID). However, it should be noted that event registration includes the exchange of an event registration request message (register event request) and an event registration response message (register event response) as described above, wherein the event registration request message (register event request) may include one or more of at least the aforementioned factors (i.e., event ID, eUICC ID, profile-providing server address, and forwarding indicator). Furthermore, it should be noted that the forwarding indicator may be omitted, and in this case, the first open intermediary server 260 may assume "false" as the default value for the forwarding indicator. Clearly, these considerations also apply to the figures described later.

[0144] In operation 3006, UE 250 may send a message requesting an event to the first open intermediary server 260. For example, the event request in operation 3006 may use a UE authentication request message (authentication client request) that includes the eUICC ID (EID) of the eUICC in UE 250. The first open intermediary server 260, having already received the event request message in operation 3006, may reply to UE 250 with an event list. For example, the event list may include a list of events that have been registered so far using the eUICC in UE 250 as a target. Furthermore, the event list may include event-related information. For example, the event-related information may include at least one of the address of the first profile providing server 270 and an event identifier (MatchingID). For example, the response to the event list in operation 3006 may use a UE authentication response message (authentication client response).

[0145] Next, in operation 3007, UE 250 may send a message requesting an event from the first profile providing server 270. For example, the event request in operation 3007 may use a UE authentication request message (authentication client request) that includes at least one or more of the following: the eUICC ID (EID) of the eUICC in UE 250, the event ID (MatchingID) received in operation 3007, and information from the first open intermediary server 260 that has received the event. In operation 3007, UE 250 and the first profile providing server 270 may perform an RSP operation (profile installation or remote management) corresponding to the event ID (MatchingID). For example, operation 3007 may also include one or more message exchanges between UE 250 and the first profile providing server 270, and the first message from the first profile providing server 270 to UE 250 may be a UE authentication response message (authentication client response).

[0146] Furthermore, it can be determined that the event ID (MatchingID) provided by UE 250 to the first profile providing server 270 is unrecognizable and is an event ID that can be processed. In this case, the first profile providing server 270 can notify UE 250 of a message indicating that the event ID received in operation 3007 is unrecognizable. For example, this message can be a UE authentication response message (authentication client response) including an error reason. Furthermore, the error reason included in this message can be a string or a numeric string representing "rejected event ID (rejected MatchingID)".

[0147] Since it is determined in operation 3007 that the processing of the event has been completed or the event ID (MatchingID) is unidentifiable, in operation 3009, the first profile providing server 270 can request the removal of the event from the first root open intermediary server 260. At this time, the first profile providing server 270 can request the removal of the event from the first root open intermediary server 260 using information (i.e., FQDN or IP address) that the UE has already received from the first root open intermediary server 260 regarding the event provided in operation 3007. For example, operation 3009 may include the first profile providing server 270 sending an event removal request message (removal event request) to the first root open intermediary server 260, including at least one or more of the eUICC ID (EID) and event ID (MatchingID) of the eUICC in the UE 250, and the first root open intermediary server 260 responding with an event removal response message (removal event response) to notify the first profile providing server 270 of the event removal result.

[0148] Figure 4 This is a diagram illustrating the message exchange process when a profile providing server operates in conjunction with at least one or more open intermediary servers according to an embodiment of this disclosure.

[0149] Reference Figure 4 UE 250 may display a Device Information Code (DIC) on its display, including the eUICC ID (EID) of the eUICC in UE 250 and information about at least one open mediation server that the UE can access. The DIC may be in the form of a user-readable string or a QR code. The open mediation server provided by UE 250 may be a root open mediation server, and the information of the open mediation server may include at least one of the following.

[0150] Open intermediary server FQDN

[0151] A unique object identifier (object ID or OID) for an open mediation server.

[0152] Open the IP address of the intermediary server

[0153] In operation 4002, UE 250 can provide DIC to operator PoS 300. Various methods, such as QR code scanning and user input, can be used as input methods via operator PoS 300. Operator PoS 300 can obtain the eUICC ID (EID) of the eUICC in UE 250 and information about at least one or more root open intermediary servers that the UE can access from the provided DIC.

[0154] In operation 4003, the operator's PoS 300 can send the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the operator server 303. Regarding the method by which the operator server 303 obtains the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the UE, it should be noted that methods other than those described in operations 4001, 4002, and 4003 can be used. For example, by using the eUICC ID, a request can be made to a third server to obtain information about root open intermediary servers supported by the UE. Furthermore, the operator may already possess information about at least one or more root open intermediary servers corresponding to the eUICC ID.

[0155] In operation 4004, the operator server 303 may request the generation of an event from the first profile providing server 270. In this case, the operator server 303 may include at least one of the eUICC ID (EID) of the eUICC in the UE 250 and information about open intermediary servers supported by the UE in the event generation request. When at least one or more pieces of information about open intermediary servers supported by the UE 250 are available from the operator server 303, the operator server 303 may selectively include some or all of the corresponding information in the event generation request. The request may include at least one or more pieces of information about open intermediary servers. For example, the event generation request in operation 4004 may include an event generation request message sent by the operator server 303 to the first profile providing server 270, including at least one of the eUICC ID (EID) of the eUICC in the UE 250 and the root SM-DS address of the first root open intermediary server 260 that will register event generation, and the first profile providing server 270 responding with an event generation response message to notify the operator server 303 of the event generation result. For ease of drawing, Figure 4Operation 4004 is represented using only the eUICC identifier (EID) and the address of the first open intermediary server 260. However, it should be noted that event generation includes the exchange of an event generation request message and an event generation response message as described above, wherein the event generation request message may include at least one or more of the aforementioned factors (i.e., the eUICC ID and at least one or more open intermediary server addresses). Clearly, these considerations also apply to the figures described later.

[0156] When the operator server 303 includes information about at least one or more open intermediary servers in the event generation request message during operation 4004, the first profile provider server 270 can perform the operation of registering the generated event in the open intermediary server.

[0157] In operation 4005, the first profile providing server 270 can register the generated event with the first root open intermediary server 260 using the first open intermediary server information included in the event generation request message of operation 4004. For example, the event registration in operation 4005 may include the first profile providing server 270 sending an event registration request message (register event request) to the first root open intermediary server 260, including an event ID (MatchingID), the eUICC ID (EID) of the eUICC in the UE 250, the address (SM-DP+ address) of at least one or more profile providing servers 270, and a forwarding indicator configured as "false," and the first root open intermediary server 260 responding with an event registration response message (register event response) to notify the first profile providing server 270 of the event registration result. For ease of illustration, Figure 4 Operation 4005 is represented as using only the eUICC ID (EID) and event identifier (MatchingID). However, it should be noted that event registration includes the exchange of an event registration request message (register event request) and an event registration response message (register event response) as described above, wherein the event registration request message (register event request) may include at least one or more of the aforementioned factors (i.e., event ID, eUICC ID, profile-providing server address, and forwarding indicator). Furthermore, it should be noted that the forwarding indicator may be omitted, and in this case, the first open intermediary server 260 may assume "false" as the default value for the forwarding indicator. Clearly, these considerations also apply to the figures described later.

[0158] In operation 4006, the first profile providing server 270 can register the generated event with the second open intermediary server 263 by using the second open intermediary server information included in the event generation request message of operation 4004. For example, the event request of operation 4006 may include an event registration request message (register event request) sent by the first profile providing server 270 to the second open intermediary server 263, including an event ID (MatchingID), the eUICC ID (EID) of the eUICC in the UE 250, the address (SM-DP+ address) of at least one or more profile providing servers 270, and a forwarding indicator configured as "false", and the first open intermediary server 260 responds with an event registration response message (register event response) to notify the first profile providing server 270 of the event registration result. For ease of drawing, Figure 4 Operation 4006 is represented as using only the eUICC identifier (EID) and event identifier (MatchingID). However, it should be noted that event registration includes the exchange of an event registration request message (register event request) and an event registration response message (register event response) as described above, wherein the event registration request message (register event request) may include at least one or more of the aforementioned factors (i.e., event ID, eUICC ID, profile-providing server address, and forwarding indicator). Furthermore, it should be noted that the forwarding indicator may be omitted, and in this case, the second root open intermediary server 263 may assume "false" as the default value for the forwarding indicator. Clearly, these considerations also apply to the figures described later.

[0159] In operation 4007, UE 250 may send a message requesting an event to the first open intermediary server 260. For example, the event request in operation 4007 may use a UE authentication request message (authentication client request) that includes the eUICC ID (EID) of the eUICC in UE 250. The first open intermediary server 260, having already received the event request message in operation 4007, may reply to UE 250 with an event list. For example, the event list may include a list of events that have been registered so far using the eUICC in UE 250 as a target. Furthermore, the event list may include event-related information. For example, the event-related information may include at least one of the address of the first profile providing server 270 and an event identifier (MatchingID). For example, the response to the event list in operation 4007 may use a UE authentication response message (authentication client response).

[0160] In operation 4008, UE 250 can request events from the second root open mediation server 263 and can receive a list of events. When there is already a duplicate event in the list of previously received but unprocessed events (i.e., the event information includes the address of the same profile providing server and the event identifier), UE 250 can discard the duplicate event.

[0161] Next, in operation 4009, UE 250 may send a message requesting an event to the first profile providing server 270. For example, the event request in operation 4009 may use a UE authentication request message (authentication client request), which includes at least one or more of the following: the eUICC ID (EID) of the eUICC in UE 250, the event ID (MatchingID) received in operation 4007 or operation 4008, information from the first open intermediary server 260 that has received the event, and information from the second open intermediary server 263 that has received a duplicate event. In operation 4009, UE 250 and the first profile providing server 270 may perform an RSP operation (profile installation or remote management) corresponding to the event ID (MatchingID). For example, operation 4009 may also include one or more message exchanges between UE 250 and the first profile providing server 270, and the first message from the first profile providing server 270 to UE 250 may be a UE authentication response message (authentication client response).

[0162] Furthermore, in operation 4009, it can be determined that the event ID (MatchingID) provided by UE 250 to the first profile providing server 270 is unrecognizable and is an event ID that can be processed. In this case, the first profile providing server 270 can notify UE 250 of a message indicating that the event ID received in operation 4009 is unrecognizable. For example, this message can be a UE authentication response message (authentication client response) including an error reason. Furthermore, the error reason included in this message can be a string or a numeric string representing "rejected event ID (rejected MatchingID)".

[0163] Since it was determined in operation 4009 that the processing of the event has been completed or the event ID (MatchingID) is unrecognizable, in operation 4010, the first profile providing server 270 can request the removal of the event from the first root open intermediary server 260. At this time, the first profile providing server 270 can request the removal of the event from the first root open intermediary server 260 by using information (i.e., FQDN or IP address) that the UE has already received from the first root open intermediary server 260 regarding the event provided in operations 4007 to 4008. For example, operation 4010 may include the first profile providing server 270 sending an event deletion request message (delete event request) to the first root open intermediary server 260, which is instructed by information received by the open intermediary server that has received the event received in operation 4009, including at least one or more of the eUICC ID (EID) and event ID (MatchingID) of the eUICC in UE 250, and the first root open intermediary server 260 responding with an event deletion response message (delete event response) to notify the first profile providing server 270 of the event deletion result.

[0164] In operation 4011, when it is identified in operation 4011 that the same event, other than that of the first open intermediary server 260, has been registered in the second open intermediary server 263, the first profile providing server 270 may request the removal of the event from the second open intermediary server 263. For example, the first profile providing server 270 may identify a list of open intermediary servers that have registered the event with the event ID (MatchingID). As another example, the first profile providing server 270 may identify a list of other open intermediary servers that have registered the event based on information from the second open intermediary server 263 that has received the duplicate event provided by the UE 250 in operation 4009. For example, operation 4011 may include sending an event deletion request message (delete event request) from the first profile providing server 270 to the second root open intermediary server 263, including at least one or more of the eUICC ID (EID) and event ID (MatchingID) of the eUICC in UE 250, and the second root open intermediary server 263 responding with an event deletion response message (delete event response) to notify the first profile providing server 270 of the event deletion result.

[0165] Figure 5 This is a diagram illustrating the message exchange process when a UE operates in conjunction with at least one root open intermediary server according to an embodiment of the present disclosure, and the profile provides a message exchange process when a server operates in conjunction with at least one or more alternative open intermediary servers.

[0166] Reference Figure 5UE 250 may display a Device Information Code (DIC) on its display, including the eUICC ID (EID) of the eUICC in UE 250 and information about at least one or more open mediation servers that the UE can access. The DIC may be in the form of a user-readable string or a QR code. The open mediation server provided by UE 250 may be a root open mediation server, and the information of the open mediation server may include at least one of the following.

[0167] Open intermediary server FQDN

[0168] A unique object identifier (object ID or OID) for an open mediation server.

[0169] Open the IP address of the intermediary server

[0170] In Operation 5002, UE 250 can provide a DIC to the operator PoS 300. Various methods, such as QR code scanning and user input, can be used as input methods via the operator PoS 300. The operator PoS 300 can obtain the eUICC ID (EID) of the eUICC in UE 250 and information about at least one or more root open intermediary servers that the UE can access from the provided DIC.

[0171] In operation 5003, the operator's PoS 300 can send the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the operator server 303. Regarding the method by which the operator server 303 obtains the eUICC ID (EID) of the eUICC in the UE 250 and information about at least one or more root open intermediary servers accessible to the UE, it should be noted that methods other than those described in operations 5001, 5002, and 5003 can be used. For example, by using the eUICC ID, a request can be made to a third server to obtain information about root open intermediary servers supported by the UE. Furthermore, the operator may already possess information about at least one or more root open intermediary servers corresponding to the eUICC ID.

[0172] In operation 5004, the operator server 303 may request the generation of an event from the second profile provided by the server 273. In this case, the event generation request may include at least one of the following: the eUICC ID (EID) of the eUICC in the UE 250, information about open intermediary servers supported by the UE, and information about alternative open intermediary servers in which the second profile provides information on which the server 273 should register the event. When at least one or more pieces of information about open intermediary servers supported by the UE 250 are available from the operator server 303, the operator server 303 may selectively include some or all of the corresponding information in the event generation request. The request may include at least one or more pieces of information about open intermediary servers. The request may include at least one or more pieces of information about alternative open intermediary servers.

[0173] For example, the event generation request of operation 5004 may include an event generation request message sent by the operator server 303 to the second profile providing server 273, including the eUICC ID (EID) of the eUICC in UE 250, the root SM-DS address of the root open intermediary server 260 registered for event generation, and at least one of the alternative open intermediary servers 263, and the second profile providing server 273 responding with an event generation response message to notify the operator server 303 of the event generation result. For ease of drawing, Figure 5 Operation 5004 is represented by using only the eUICC identifier (EID), the address of the root open intermediary server 260, and the address of the alternative open intermediary server 263. However, it should be noted that event generation includes the exchange of an event generation request message and an event generation response message as described above, wherein the event generation request message may include at least one or more of the aforementioned factors (i.e., the eUICC ID and at least one or more open intermediary server addresses). Clearly, these considerations also apply to the figures described later.

[0174] When the operator server 303 includes information about at least one or more alternative open intermediary servers in the event generation request message in operation 5004, the first profile providing server 270 can perform the operation of the event generated in the alternative open intermediary server 263.

[0175] In operation 5005, the first profile providing server 270 can register the generated first event with the alternative open intermediary server 263 by using the alternative open intermediary server information included in the event generation request message of operation 5004. For example, the event registration in operation 5005 may include the first profile providing server 270 sending an event registration request message (register event request) to the alternative open intermediary server 263, including at least one or more of the following: a first event ID (MatchingID), the eUICC ID (EID) of the eUICC in UE 250, the address (SM-DP+ address) of at least one or more profile providing servers 273, the address (root SM-DS address) of the root open intermediary server, and a forwarding indicator configured as "true", and the alternative open intermediary server 263 responding with an event registration response message (register event response) to notify the second profile providing server 273 of the event registration result. For ease of drawing, Figure 5 Operation 5005 is represented as using only the eUICCID (EID), the first event identifier (MatchingID), and the address of the root open intermediary server. However, it should be noted that event registration includes the exchange of an event registration request message (register event request) and an event registration response message (register event response) as described above, wherein the event registration request message (register event request) may include at least one or more of the aforementioned factors (i.e., event ID, eUICC ID, profile providing server address, root open intermediary server address, and forwarding indicator). Furthermore, it should be noted that the forwarding indicator may be omitted, and in this case, the root open intermediary server 260 may assume "false" as the default value for the forwarding indicator. Clearly, these considerations also apply to the figures described later.

[0176] In operation 5006, alternative open intermediary server 263 can re-register the first event with root open intermediary server 260 based on the forwarding indicator configured as "true" in operation 5005 or the address of root open intermediary server 260. Alternatively, when there is no information in operation 5005 regarding alternative open intermediary servers in which the event will be re-registered, but there is information regarding root open intermediary server 250 in which the event will be re-registered, the first event can be re-registered with root open intermediary server 260. For example, the re-registration of the first event in operation 5006 may include the alternative open intermediary server 263 sending an event registration request message (registration event request) to the root open intermediary server 260, comprising at least one or more of the following: a modulated first event ID (MatchingIDa), the eUICC ID (EID) of the eUICC in the UE 250, the address of the alternative open intermediary server 263, and a forwarding indicator configured as "false", and the root open intermediary server 260 responding with an event registration response message (registration event response) to notify the alternative open intermediary server 263 of the event registration result. For example, the modulated first event ID (MatchingIDa) may be the same value as the first event ID (MatchingID).

[0177] In Operation 5007, UE 250 may send a message requesting an event to Root Open Mediation Server 260. For example, the event request in Operation 5007 may use a UE authentication request message (authentication client request) that includes the eUICC ID (EID) of the eUICC in UE 250.

[0178] In operation 5008, the root open mediation server 260 can respond to UE 250 with an event list. For example, the event list may include a list of events that have been registered so far using eUICC in UE 250 as the target. In addition, the event list may include event-related information.

[0179] Reference Figure 5 This section describes an example of responding with information related to the first event re-registered in operation 5006. For example, the re-registered first event information included in the event list may include at least one or more of the address of the alternative open mediation server 263 and the modulated first event ID (MatchingIDa).

[0180] In addition, responses to the event list in Operation 5008 can use UE authentication response messages (authentication client responses).

[0181] For example, the order in which events are listed in the event list can follow the chronological order in which each event was registered in the root open mediation server 260.

[0182] In operation 5009, UE 250 may send a message requesting re-registration of the first event to the alternative open intermediary server 263. For example, the event request in operation 5009 may use a UE authentication request message (authentication client request) that includes at least one or more of the eUICC ID of the eUICC in UE 250 and the modulated first event ID (MatchingIDa) received in operation 5008.

[0183] In operation 5010, the alternative open mediation server 263 can respond to UE 250 with an event list. For example, the event list may include a list of events that have been registered so far using eUICC in UE 250 as the target. In addition, the event list may include event-related information.

[0184] exist Figure 5 The following describes an example of responding using information related to the first event registered in Operation 5005. For example, the first event-related information included in the event list may include at least one of the address of server 273 provided in the second profile and the first event ID (MatchingID). Furthermore, the response to the event list in Operation 5010 may use a UE authentication response message (authentication client response).

[0185] Next, in operation 5011, UE 250 can send a message requesting an event to the second profile providing server 273. For example, the event request in operation 5011 can use a UE authentication request message (authentication client request), which includes at least one or more of the following: the eUICC ID (EID) of the eUICC in UE 250, the first event ID (MatchingID) received in operation 5010, information about the alternative open intermediary server 263 that has received the first event, and information about the root open intermediary server 260 that has received the re-registration of the first event. At this time, the information of the open intermediary servers included can be included in the order of access or the reverse order until the first event is received. In operation 5011, UE 250 and the second profile providing server 273 can perform an RSP operation (profile installation or remote management) corresponding to the event ID (MatchingID). For example, operation 5011 may also include one or more message exchanges between UE 250 and second profile providing server 273, and the first message that the second profile providing server 273 replies to UE 250 may be a UE authentication response message (authentication client response).

[0186] Furthermore, in operation 5011, it can be determined that the first event ID (MatchingID) provided by UE 250 to the second profile providing server 273 is unrecognizable and is an event ID that can be processed. In this case, the second profile providing server 273 can notify UE 250 of a message indicating that the event ID received in operation 5011 is unrecognizable. For example, this message can be a UE authentication response message (authentication client response) including an error reason. Furthermore, the error reason included in this message can be a string or a numeric string representing "rejected event ID (rejected MatchingID)".

[0187] Since it is determined in operation 5011 that the processing of the event has been completed or the event ID (MatchingID) is unrecognizable, in operation 5012, the second profile providing server 273 can request the removal of the event from the alternative open intermediary server 263 where the corresponding event has been registered. At this time, the second profile providing server 273 can request the removal of the event from the alternative open intermediary server 263 by using information (i.e., FQDN or IP address) of the alternative open intermediary server 263 for which the UE has received the event provided in operation 5010. Furthermore, the removal request may include information (i.e., FQDN or IP address) of the root open intermediary server 260 for which the first event for re-registration was provided by the UE 250 in operation 5010. For example, operation 5012 may include the second profile providing server 273 sending an event deletion request message (delete event request) to an alternative open intermediary server 263, as indicated by information received by the open intermediary server that received the first event received in operation 5010. The message includes at least one or more of the following: the eUICC ID (EID) of the eUICC in UE 250, the event ID (MatchingID), and information that the root open intermediary server 260 has received the re-registered first event. The root open intermediary server 260 responds with an event deletion response message (delete event response) to notify the first profile providing server 270 of the event deletion result.

[0188] In operation 5013, since the processing of the first event has been completed, the alternative open intermediary server 263 can request the removal of the re-registered first event from the root open intermediary server 260. The alternative open intermediary server 263 can use information from the root open intermediary server 260, which has received the re-registered first event sent in operation 5012, to identify the open intermediary server that registered the re-registered first event to be deleted. For example, operation 5013 may include the alternative open intermediary server 263 sending an event deletion request message (delete event request) including at least one or more of the eUICC ID (EID) of the eUICC in UE 250 and the modulated first event ID (MatchingIDa), and replying with an event deletion response message (delete event response) to notify the alternative open intermediary server 263 of the event deletion result.

[0189] at the same time, Figure 5 The illustration shows two open intermediary servers, 263 and 260, used for event re-registration. It should be noted that three or more open intermediary servers can be used. For example, in event registration processing, open intermediary server 263 can re-register an event with another root open intermediary server (not shown). In this case, the alternative open intermediary server 263 can determine the root open intermediary server (not shown) for re-registering the event by using information from one or more alternative open intermediary servers included in the previously executed event registration request message. When the event registration request message includes another alternative open intermediary server (not shown) for re-registering the event, the root open intermediary server (not shown) where the event was re-registered can re-register the re-registered event with the corresponding open intermediary server. Furthermore, when the event registration message of the root open intermediary server does not contain information about an alternative open intermediary server for re-registering the event, but the event registration message of the root open intermediary server contains information about a root open intermediary server for re-registering the event, the alternative open intermediary server (not shown) can re-register the event with the corresponding root open intermediary server 260.

[0190] also, Figure 5 Examples similar to those above Figure 4 The example combines this with other applications. Clearly, events generated by the profile-providing server are registered in the alternative open mediation server, and then the alternative open mediation server is re-registered two or more times in two or more root open mediation servers, enabling the UE to be notified of the re-registration via both the root open mediation server and the alternative open mediation server.

[0191] Figure 6This is a flowchart illustrating an embodiment of the present disclosure of a process for registering events with a profile providing server or an open intermediary server (i.e., an RSP server (SM-XX)) and requesting event registration from another open intermediary server.

[0192] Reference Figure 6 In operation 6001, the RSP server can begin operations.

[0193] In Operation 6003, the RSP server can receive event registration requests. When the RSP server is a profile provider server, it can send the corresponding request from the carrier server. When the RSP server is an open mediation server, it can send the corresponding request from another open mediation server or profile provider server.

[0194] In Operation 6005, the RSP server can generate or register the requested event. When the RSP server is a profile provider server, it can generate the event and generate an event ID (MatchingID). When the RSP server is an open mediation server, it can register the event by including at least one of the event ID (MatchingID) included in the request message and the UE's eUICC ID.

[0195] In operation 6007, the RSP server can determine whether a list of at least one or more alternative open intermediary servers exists in the event registration request message. For example, if a list of alternative open intermediary servers exists, the RSP server can proceed to operation 6009. Furthermore, if a list of alternative open intermediary servers does not exist, the RSP server can proceed to operation 6011.

[0196] In operation 6009, the RSP server may request event registration from a specific open intermediary server within the list of alternative open intermediary servers. When the RSP server is a profile provider server, the event registration request message may include the event ID (MatchingID) generated in operation 6005 and its own address (i.e., the profile provider server address), at least one of the alternative open intermediary servers for re-registering the event, and the root open intermediary server for re-registering the event. The list of alternative open intermediary servers for re-registering the event may not include information about the open intermediary server requesting the re-registration of the current event.

[0197] Furthermore, in operation 6009, when the RSP server is an open intermediary server, the RSP server can generate a modulated event ID (MatchingIDa) and store the generated event ID in conjunction with the event registered in operation 6005. Next, the RSP server can include at least one of the modulated event ID (MatchingIDa), its own address (i.e., the address of the open intermediary server), a list of candidate open intermediary servers for re-registering the event, and a list of root open intermediary servers for re-registering the event, to request event registration. The list of candidate open intermediary servers for re-registering the event may not include information about the open intermediary server requesting the re-registration of the current event. In operation 6011, the RSP server can determine whether at least one or more root open intermediary server information lists exist in the event registration request message. For example, if a root open intermediary server information list exists, the RSP server can proceed to operation 6013. Furthermore, if no candidate open intermediary server information list exists, the RSP server can proceed to operation 6015 to complete the event registration and wait for another operation.

[0198] In operation 6013, the RSP server can request event registration from all open intermediary servers in the root open intermediary server information list. When the RSP server is a profile provider server, the event registration request message can include one of the event ID (MatchingID) generated in operation 6005 and its own address (i.e., the profile provider server address). Furthermore, when the RSP server is an open intermediary server in operation 6013, the RSP server can generate a modified event ID (MatchingIDa) and store the generated event ID in conjunction with the events registered in operation 6005. The RSP server can then request event registration simultaneously, including at least one of the modified event ID (MatchingIDa) and its own address (i.e., the address of the open intermediary server).

[0199] Figure 7 This is a diagram illustrating the components of a UE 250 according to an embodiment of the present disclosure.

[0200] Reference Figure 7 UE 700 may include a transceiver 710 and at least one processor 720. Furthermore, UE 700 may include a UICC 730. For example, the UICC 730 may be inserted into UE 700, or it may be an eUICC embedded in UE 700.

[0201] According to various embodiments of this disclosure, transceiver 710 can send and receive signals, information, data, etc. with profile providing server 800 or open intermediary server 900.

[0202] For example, transceiver 710 according to various embodiments can send a first message of a request event to open mediation server 900.

[0203] According to various embodiments, transceiver 710 can receive event-related information from open mediation server 800 in response to a first message.

[0204] According to various embodiments, transceiver 710 can send a second message requesting an event to profile providing server 800 based on event-related information.

[0205] For example, the open mediation server 900 according to various embodiments may include a root open mediation server and alternative open mediation servers.

[0206] According to various embodiments, transceiver 710 can send a third message requesting an event to a second open intermediary server based on second event-related information received from a first open intermediary server.

[0207] According to various embodiments, transceiver 710 can receive information related to the first event from a second open intermediary server in response to a third message.

[0208] According to various embodiments, transceiver 710 can send a second message requesting an event to profile providing server 800 based on information related to the first event.

[0209] For example, the second message according to various embodiments may also include at least one of information related to the acquisition path of information related to the first event and information related to a second open intermediary server that has already responded with information related to the first event.

[0210] Furthermore, the third message according to various embodiments may also include information related to the acquisition path of information related to the second event, and at least one of a first open intermediary server that has already responded with information related to the second event.

[0211] Furthermore, according to various embodiments, transceiver 710 can receive information related to event processing from profile providing server 800 in response to a second message.

[0212] For example, information related to event processing received from the profile-providing server 800 according to various embodiments may include information indicating that event processing has failed.

[0213] Information related to event handling received from the profile providing server 800 according to various embodiments may include information related to profile installation or remote management.

[0214] According to various embodiments, the controller 720 can control the overall operation of the UE 700. According to the various embodiments of this disclosure as described above, the controller 720 can control the overall operation of the UE 700.

[0215] For example, according to various embodiments, the controller 720 can identify the event handling exception list and determine whether to process the event based on the event-related information received from the open mediation server 900 and the event handling exception list.

[0216] Furthermore, according to various embodiments, the controller 720 can control the transceiver 710 to send a second message requesting an event to the profile providing server 800 based on determining whether to process the event through control of the transceiver 710 and event-related information. It can also receive event-related information from the profile providing server 800 in response to the second message and can update the event processing exception list based on the event-related information. For example, when the event-related information received from the profile providing server 800 includes information indicating event processing failure, at least one controller 720 according to various embodiments can add the event-related information to the event processing exception list.

[0217] According to various embodiments, the UICC 730 can download and install files. Furthermore, the UICC 730 can manage files.

[0218] The UICC 730 can operate under the control of the controller 720. Alternatively, the UICC 730 may include a processor or controller for installing a profile, or an application may be installed therein. A portion of the application may be installed in the controller 720.

[0219] Meanwhile, UE 700 may also include a memory (not shown) that can store data such as basic programs, application programs, and configuration information for the operation of UE 700. Furthermore, the memory may include at least one storage medium selected from flash memory, hard disk, multimedia microcard, card-type memory (e.g., SD or XD memory), magnetic storage, magnetic disk, optical disk, random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), programmable read-only memory (PROM), and electrically erasable programmable read-only memory (EEPROM). Furthermore, controller 720 can perform various operations using various programs, content, data, etc., stored in the memory.

[0220] Figure 8This is a diagram illustrating the components of a server 800 provided in a brief description according to an embodiment of the present disclosure.

[0221] Reference Figure 8 According to the profiles of various embodiments, server 800 may include transceiver 810 and at least one processor (or controller 820).

[0222] According to various embodiments of this disclosure, transceiver 810 can send and receive signals, information, data, etc., with UE 700 or open intermediary server 900. For example, transceiver 810 can send information related to file installation or remote management to UE.

[0223] For example, transceiver 810 according to various embodiments can receive event request messages from UE 700.

[0224] For example, an event request message according to various embodiments may include event-related information, and the event-related information according to various embodiments may be based on information received by the UE 700 from the open mediation server 900.

[0225] Meanwhile, controller 820 is a component for overall control of the profile providing server 800. According to various embodiments of the present disclosure as described above, controller 820 can control the overall operation of the profile providing server 800.

[0226] For example, according to various embodiments, the controller 820 can determine the validity of event-related information including an event request message received from the UE 700, and based on the determination of the validity of the event-related information, can control the transceiver 820 to send information related to event processing to the UE.

[0227] For example, when event-related information is available, event-related information according to various embodiments may include information related to profile installation or remote management.

[0228] Furthermore, when event-related information is invalid, event-related information according to various embodiments may include information indicating event processing failure.

[0229] According to various embodiments, the controller 820 can control the transceiver 810 to send an event deletion request message to the open mediation server when event processing is complete.

[0230] The event request message according to various embodiments of this disclosure may also include at least one of information related to the acquisition path of event-related information and information related to the open mediation server 900.

[0231] According to various embodiments of this disclosure, the controller 820 can send an event deletion request message to the open intermediary based on at least one of information related to the acquisition path of the event and information related to the open intermediary server 900. The transceiver can be controlled to send the message to the server 900.

[0232] Meanwhile, the profile providing server 800 may also include a memory (not shown) and may store data such as basic programs, application programs, and configuration information for the operation of the profile providing server 800. Furthermore, the memory may include at least one storage medium selected from flash memory, hard disk, multimedia microcard, card-type memory (e.g., SD or XD memory), magnetic storage, magnetic disk, optical disk, RAM, SRAM, ROM, PROM, and EEPROM. Additionally, the controller 820 may use various programs, content, data, etc., stored in the memory to perform various operations.

[0233] Figure 9 This is a diagram illustrating the components of an open mediation server 900 according to an embodiment of the present disclosure.

[0234] Reference Figure 9 The open mediation server 900, according to various embodiments, may include a transceiver 910 and a controller 920.

[0235] According to various embodiments of this disclosure, transceiver 910 can send and receive signals, information, data, etc., with UE 700 or profile providing server 800. For example, transceiver 910 can send event-related information to UE. For example, transceiver 910 can receive event request messages from UE.

[0236] For example, an event request message according to various embodiments may include event-related information, and the event-related information according to various embodiments may be based on information received by the UE 700 from another open intermediary server (not shown).

[0237] Meanwhile, controller 920 is a component for overall control of open mediation server 900. According to various embodiments of this disclosure as described above, controller 920 can control the overall operation of open mediation server 900.

[0238] For example, controller 920 according to various embodiments of the present disclosure may include transceiver 910 receiving event registration request messages from profile providing server 800 or another open intermediary server (not shown) in order to register events.

[0239] According to various embodiments, the controller 920 can register events in response to an event registration request message.

[0240] According to various embodiments, the registered events can be associated with events generated by the profile-providing server 800.

[0241] For example, when transceiver 910 receives an event registration request message from another open intermediary server, the event to be registered may be an event obtained by modulating an event generated by a profile provider server.

[0242] According to various embodiments, the controller 920 can control the transceiver 910 to receive event deletion request messages from the profile providing server 800, and based on the event deletion request messages, can delete the registered events.

[0243] The event registration request message, according to various embodiments, may include information related to the time of event disruption.

[0244] For example, one or more controllers 920 according to various embodiments may delete an event based on information related to the time of the event destruction.

[0245] The event registration request message, according to various embodiments, may include information related to the event deletion notification.

[0246] For example, according to various embodiments, the controller 920 can control the transceiver 910 to notify the profile providing server 800 of event deletion based on information related to the event deletion notification.

[0247] Meanwhile, the open intermediary server 900 may also include a memory (not shown) and may store data such as basic programs, application programs, and configuration information for the operation of the open intermediary server 900. Furthermore, the memory may include at least one storage medium selected from flash memory, hard disk, multimedia microcard, card-type memory (e.g., SD or XD memory), magnetic storage, magnetic disk, optical disk, RAM, SRAM, ROM, PROM, and EEPROM. Additionally, the controller 920 may use various programs, content, data, etc., stored in the memory to perform various operations.

[0248] In the detailed embodiments described above, elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form is suitably chosen for the presented situation, and this disclosure is not limited to elements represented in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

[0249] Although specific embodiments have been described in the detailed description of this disclosure, various modifications and changes can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be defined as limited to the embodiments of this disclosure, but should be defined by the appended claims and their equivalents.

[0250] It should be understood that the various embodiments of this disclosure and the terminology used therein are not intended to limit the technical features set forth herein to the particular embodiments, but rather to include various variations, equivalents, and / or substitutions of the corresponding embodiments. Regarding the description of the drawings, similar reference numerals may be used to denote similar or related elements. It should be understood that the singular form of a noun corresponding to an item may include one or more things unless the relevant context explicitly indicates otherwise. As used herein, each of phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” may include all possible combinations of the items listed together in the corresponding one of the phrases. As used herein, terms such as “first,” “second,” “the first,” and “the second” may be used simply to distinguish the corresponding element from another element and do not limit these elements in other respects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as “coupled to another element (e.g., a second element),” “coupled to another element (e.g., a second element),” “connected to another element (e.g., a second element),” or “connected to another element (e.g., a second element),” whether or not the terms “operationally” or “communically” are used, it means that the element can be coupled to the other element directly (e.g., wired), wirelessly, or via another element (e.g., a third element).

[0251] As used herein, the term "module" can include a unit implemented in hardware, software, or firmware, and is used interchangeably with other terms such as "logic," "logic block," "component," or "circuit." A "module" can be the smallest unit, or a portion thereof, of a single integrated component suitable for performing one or more functions. For example, according to embodiments of this disclosure, a "module" can be implemented as an application-specific integrated circuit (ASIC).

[0252] The various embodiments described herein can be implemented as software (e.g., a program) including instructions stored in a machine-readable storage medium (e.g., internal or external memory). The machine is a device that can invoke stored instructions from the storage medium and operate according to the invoked instructions, and may include a terminal (e.g., a first terminal 230 or a second terminal 230) according to various embodiments. When the instructions are executed by a processor, the processor can perform the function corresponding to the instructions, whether or not one or more other components are used under the processor's control. The instructions may include code generated by a compiler or code executable by an interpreter.

[0253] Machine-readable storage media may be provided in the form of non-transitory storage media. Here, the term "non-transitory" simply means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between the location in the storage medium where data is stored semi-permanently and the location in the storage medium where data is stored temporarily.

[0254] Methods according to various embodiments of this disclosure can be included in and provided therein in a computer program product. The computer program product can be traded as a product between a seller and a buyer. The computer program product can be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)) or via an app store (e.g., the Play Store). TM The computer program product may be distributed online (e.g., downloaded or uploaded) or directly between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium (such as the memory of a manufacturer's server, an app store's server, or a relay server).

[0255] According to various embodiments of this disclosure, each of the above-described elements (e.g., a module or program) may include a single entity or multiple entities. According to various embodiments of this disclosure, one or more of the above-described elements may be omitted, or one or more other elements may be added. Alternatively or additionally, multiple elements (e.g., modules or programs) may be integrated into a single element. In this case, according to various embodiments of this disclosure, the integrated element may still perform one or more functions of each of the multiple elements in the same or similar manner as performed by a corresponding element of the multiple elements prior to integration. According to various embodiments of this disclosure, operations performed by a module, program, or other element may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0256] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a server in a wireless communication system, the method comprising: Receive a first message from the mobile network operator, including an embedded universal integrated circuit card (eUICC) identifier, first information about a first open intermediary server, and second information about a second open intermediary server; An event is generated based on the first message; Register the event in the first open intermediary server based on the first message; Register the event in the second open intermediary server based on the first message; Receive a second message from the user equipment (UE) for requesting the event, the second message including an event identifier for the event, wherein the event is associated with the first open mediation server; Execute the event based on the second message; Identify whether the event identical to the one being executed is registered in the second open mediation server; as well as If an event identical to the one executed is registered in the second open intermediary server, a request message is sent to the second open intermediary server to request the deletion of the event identical to the one executed.

2. The method according to claim 1, further comprising: If the event identifier is unrecognizable, a request message for requesting the deletion of the event is sent to at least one open intermediary server; as well as Receive a response message from the at least one open intermediary server, including the deletion result of the event.

3. The method according to claim 1, further comprising: A third message is sent to at least one open intermediary server based on the first message; as well as Receive a fourth message, including the event registration result, from the at least one open intermediary server.

4. The method of claim 1, wherein the identification includes identifying an event registered that is the same as the event being performed, based on an event identifier in the second open intermediary server.

5. The method according to claim 1, further comprising: Based on the first message, determine whether there is a list of at least one alternative open intermediary server; as well as Send a message requesting event registration to a specific open intermediary server within the information list of at least one alternative open intermediary server.

6. The method according to claim 5, further comprising: In the absence of the information list of at least one alternative open intermediary server, determine whether there is an information list of at least one root open intermediary server. as well as Send a message requesting event registration to all open intermediary servers in the information list of the at least one root open intermediary server.

7. The method according to claim 1, wherein, Information about open mediation servers includes at least one of a fully qualified domain name (FQDN) and an object identifier IP address.

8. A server, comprising: A transceiver is configured to transmit and receive at least one signal; as well as A controller is configured to be coupled to the transceiver, wherein the controller is configured to: Receive a first message from the mobile network operator, including an embedded universal integrated circuit card (eUICC) identifier, first information about a first open intermediary server, and second information about a second open intermediary server. An event is generated based on the first message. Register the event in the first open intermediary server based on the first message. Register the event in the second open intermediary server based on the first message. The user equipment (UE) receives a second message requesting the event, the second message including an event identifier for the event, wherein the event is associated with the first open mediation server. The event is executed based on the second message. Identify whether the event identical to the one executed is registered in the second open mediation server, and If an event identical to the one executed is registered in the second open intermediary server, a request message is sent to the second open intermediary server to request the deletion of the event identical to the one executed.

9. The server according to claim 8, wherein, The controller is also configured to: If the event identifier is unrecognizable, a request message for deleting the event is sent to at least one open intermediary server. Receive a response message from the at least one open intermediary server, including the deletion result of the event.

10. The server according to claim 8, wherein, The controller is also configured to: Based on the first message, a third message is sent to at least one open intermediary server, and Receive a fourth message, including the event registration result, from the at least one open intermediary server.

11. The server according to claim 8, wherein, The controller is also configured to identify, based on the event identifier in the second open mediation server, that the same event as the executed event has been registered.

12. The server according to claim 8, wherein, The controller is also configured to: Based on the first message, determine whether there is a list of at least one alternative open intermediary server, and Send a message requesting event registration to a specific open intermediary server within the information list of the at least one alternative open intermediary server.

13. The server according to claim 12, wherein, The controller is also configured to: If the information list of at least one alternative open intermediary server does not exist, determine whether the information list of at least one root open intermediary server exists, and Send a message requesting event registration to all open intermediary servers in the information list of the at least one root open intermediary server.

14. The server according to claim 8, wherein, Information about open mediation servers includes at least one of a fully qualified domain name (FQDN) and an object identifier IP address.

Images