KR20220142318A - Method and apparatus for managing events in a wireless communication system - Google Patents

Abstract

The present invention relates to a communication technique that combines a 5G communication system with an IoT technology to support a higher data transmission rate after a 4G system, and a system thereof. The present invention can be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on a 5G communication technology and an IoT-related technology. Various embodiments of the present invention provide a method for a communication connection by allowing a terminal to select a communication service in a wireless communication system and a device thereof.

Description

METHOD AND APPARATUS FOR MANAGING EVENTS IN A WIRELESS COMMUNICATION SYSTEM

Various embodiments of the present disclosure relate to a method and apparatus for providing event confirmation information for an event registered by an opening mediation server.

Various embodiments of the present disclosure relate to a method and apparatus for issuing, registering, and updating an event confirmation identifier for a terminal and an opening intermediary server for event confirmation.

Various embodiments of the present disclosure relate to a method and apparatus for a profile server to register and delete an event in at least one or more open intermediary servers.

Various embodiments of the present disclosure relate to a method and an apparatus for communication connection by downloading and installing a communication service in a terminal in a communication system.

Various embodiments of the present disclosure relate to a method and apparatus for downloading, installing, and managing an online profile in a communication system.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE system after (Post LTE) system. In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, in the 5G communication system, beamforming, massive MIMO, full dimensional MIMO, FD-MIMO ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , device to device communication (D2D), wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, advanced coding modulation (ACM) methods such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), and advanced access technologies such as filter bank multi carrier (FBMC), NOMA (non-orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans generate and consume information, to an IoT (internet of things, Internet of Things) network that exchanges and processes information between distributed components such as things. IoE (internet of everything) technology, in which big data processing technology through connection with cloud servers, etc., is combined with IoT technology, is also emerging. In order to implement the IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, a machine to machine , M2M), and MTC (machine type communication) are being studied. In the IoT environment, intelligent IT (internet technology) services that create new values in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of a cloud radio access network (cloud RAN) as the big data processing technology described above is an example of the convergence of 5G technology and IoT technology.

As described above, as various services can be provided according to the development of mobile communication systems, a method for effectively providing these services is required.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus for a terminal to select a communication service and establish a communication connection in a communication system.

According to various embodiments of the present disclosure, it is possible to provide a method and an apparatus for downloading, installing, and managing an online profile for a terminal to establish a communication connection in a communication system.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus by which a terminal can efficiently download an event in a communication system.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus in which a terminal accesses at least one or more opening intermediary servers and checks the presence or absence of an event assigned to the terminal.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus in which a terminal accesses at least one or more opening intermediary servers and acquires an event assigned to the terminal.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus for a profile providing server to register the same event with at least one or more open mediation servers.

According to various embodiments of the present disclosure, it is possible to provide a method and an apparatus for selecting whether to provide an event confirmation function when a profile providing server registers an event with at least one or more opening intermediary servers.

According to various embodiments of the present disclosure, it is possible to provide a method and apparatus for a profile providing server to delete an event in which at least one or more opening intermediary servers are registered.

According to various embodiments of the present disclosure, it is possible to provide a method of exchanging messages between a terminal, an open mediation server (SM-DS), and a profile providing server (SM-DP+).

The present invention for solving the above problems is a control signal processing method in a wireless communication system, the method 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.

In a wireless communication system according to various embodiments of the present disclosure, a terminal includes: a transceiver; and at least one or more processors; Including, wherein the at least one processor transmits a first message requesting event confirmation to the opening mediation server, receives event confirmation related information from the opening mediation server in response to the first message, and the event confirmation related information Based on the , it is possible to control the transceiver to transmit a second message for requesting an event to the opening mediation server, and to receive information related to event processing from the opening mediation server in response to the second message.

In a wireless communication system according to various embodiments of the present disclosure, a terminal includes: a transceiver; and at least one or more processors; Including, wherein the at least one processor transmits a first message for requesting an event to the opening mediation server, receives event-related information from the opening mediation server in response to the first message, and based on the event-related information , it is possible to control the transceiver to transmit a second message for requesting an event to the profile providing server, and to receive information related to event processing from the profile providing server in response to the second message.

In a wireless communication system according to various embodiments of the present disclosure, a profile providing server includes: a transceiver; and at least one or more processors; Including, wherein the at least one processor controls the transceiver to receive an event generation and event registration request message to at least one or more opening intermediary servers from a business server, generating an event corresponding to the request message, and opening at least one or more The transceiver can be controlled to register an event with the mediation server.

In a wireless communication system according to various embodiments of the present disclosure, an opening intermediary server includes a transceiver; and at least one or more processors; Including, wherein the at least one processor may control the transceiver to receive an event registration request message from a profile providing server or other opening intermediary server to register an event, and in response to the event registration request message, the event can be registered, and the event may be related to an event generated by the profile providing server.

In a wireless communication system according to various embodiments of the present disclosure, a profile providing server includes: a transceiver; and at least one or more processors; Including, wherein the at least one processor controls the transceiver to receive the event request message from the terminal, determines the validity of the event-related information included in the event request message, and based on the determination of the validity of the event-related information , it is possible to control the transceiver to transmit information related to event processing to the terminal.

The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those of ordinary skill in the art to which the present invention belongs from the description below. will be able

According to various embodiments, in a communication system, a terminal may request an event registered in at least one or more opening intermediary servers.

According to various embodiments, in the communication system, the terminal may request event confirmation for an event registered in at least one or more opening intermediary servers.

According to various embodiments, in the communication system, the profile providing server may generate an event according to the request of the business operator server and register the corresponding event in at least one or more opening intermediary servers.

According to various embodiments, in the communication system, the profile providing server generates an event according to the request of the operator server, registers the corresponding event in at least one or more opening mediation servers, and the opening mediation server uses the event confirmation function for the event. can allow

According to various embodiments, when the profile providing server in the communication system requests to register an event to the opening mediation server, after the opening mediation server registers the event, it sends a message requesting to register the event corresponding to the event with the third opening mediation server. may include

According to various embodiments, the terminal in the communication system may provide an event confirmation identifier when requesting event confirmation by accessing the opening intermediary server.

According to various embodiments, in the communication system, the opening intermediary server may provide an event confirmation identifier to the terminal.

1 is a diagram illustrating a method for a terminal to connect to a mobile communication network using a UICC having a fixed profile mounted thereon, according to various embodiments of the present disclosure.
2 is a diagram illustrating an example of connection to a terminal, an opening mediation server, a profile providing server, and a service provider according to various embodiments of the present disclosure;
3 is a diagram illustrating an example of a message exchange procedure in which a profile providing server registers event generation with an opening intermediary server according to various embodiments of the present disclosure.
4 is a diagram illustrating an example of a message exchange procedure in which a profile providing server registers event generation successively in a plurality of open intermediary servers according to various embodiments of the present disclosure.
5 is a diagram illustrating an example of a message exchange procedure when an event confirmation identifier issuance or registration operation is performed between a terminal and an opening intermediary server according to various embodiments of the present disclosure;
6 is a diagram illustrating another example of a message exchange procedure when an event confirmation identifier issuance or registration operation is performed between a terminal and an opening intermediary server according to various embodiments of the present disclosure;
7 is a diagram illustrating another example of a message exchange procedure when an event check operation is performed using an event check identifier of a terminal and an open intermediary server according to various embodiments of the present disclosure.
8 is a diagram illustrating another example of a message exchange procedure when an event check operation is performed during a mutual authentication process using an event check identifier of a terminal and an opening intermediary server according to various embodiments of the present disclosure.
9 is a diagram illustrating components of a terminal according to an embodiment of the present disclosure.
10 is a diagram illustrating components of a profile providing server according to an embodiment of the present disclosure.
11 is a diagram illustrating components of an open mediation server according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring the gist of the present disclosure by omitting unnecessary description.

For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals.

Advantages and features of the present disclosure, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only the present embodiments allow the disclosure of the present disclosure to be complete, and common knowledge in the art to which the present disclosure belongs It is provided to fully inform those who have the scope of the disclosure, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible for the instructions stored in the flowchart block(s) to produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in the blocks to occur out of order. For example, it is possible that two blocks shown in succession are actually performed substantially simultaneously, or that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA or ASIC, and '~ unit' performs certain roles. However, '-part' is not limited to software or hardware. '~unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Thus, as an example, '~' denotes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card.

Specific terms used in the following description are provided to help the understanding of the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

In the present disclosure, modifiers such as first and second referencing terms may be used to distinguish each term from each other in describing embodiments. Terms modified by modifiers such as the first and the second may refer to different objects. However, terms modified by modifiers such as the first and the second may refer to the same object. That is, modifiers such as the first and the second may be used to refer to the same object from different viewpoints. For example, modifiers such as 1st, 2nd, etc. may be used to distinguish the same object in terms of a function or an operation. For example, the first user and the second user may refer to the same user.

First, terms used in the present disclosure are defined.

A UICC (Universal Integrated Circuit Card) is a smart card that is inserted into a mobile communication terminal and used, and is also called a UICC card. The UICC may include an access control module for accessing a network of a mobile communication service provider. Examples of the access control module include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), and an IP Multimedia Service Identity Module (ISIM). A UICC including a USIM is usually called a USIM card. Similarly, a UICC including a SIM module is commonly referred to as a SIM card.

The terms “SIM card”, “UICC card”, “USIM card”, and “UICC including ISIM” disclosed in the present disclosure may be used as the same meaning in the present disclosure. That is, even for a SIM card, the technical application can be equally applied to a USIM card, an ISIM card, or a general UICC card.

The SIM card stores personal information of mobile communication subscribers, and performs subscriber authentication and traffic security key generation when accessing a mobile communication network to enable safe mobile communication use.

At the time of proposing the present disclosure, a SIM card is generally manufactured as a dedicated card for a specific mobile communication operator at the request of a specific mobile communication operator during card manufacturing, and authentication information for network access of the corresponding operator, for example, USIM (Universal Subscriber Identity Module) application, IMSI (International Mobile Subscriber Identity), K value, OPc value, etc. are loaded on the card in advance and shipped. Therefore, the manufactured SIM card is delivered by the mobile communication service provider and provided to subscribers, and if necessary, installation, modification, and deletion of applications within the UICC can be performed using technologies such as OTA (Over The Air). have. Subscribers can use the network and application services of the mobile communication operator by inserting the UICC card into their own mobile communication terminal. Mobile phone numbers and personal phone books can be used as they are in the new terminal.

However, the SIM card is inconvenient for a mobile communication terminal user to receive services from other mobile carriers. A user of a mobile communication terminal has the inconvenience of having to physically obtain a SIM card in order to receive a service from a mobile communication service provider. For example, when traveling to another country, in order to receive a local mobile communication service, it is inconvenient to obtain a local SIM card. In the case of roaming service, the inconvenience is solved to some extent, but there is a problem that the fee is relatively high, and the service cannot be received if there is no contract between the telecommunication companies.

On the other hand, when the SIM module is remotely downloaded and installed on the UICC card, this inconvenience can be largely solved. That is, the SIM module of the mobile communication service that the user wants to use at a desired time can be downloaded to the UICC card. Such a UICC card can also be used by downloading and installing a plurality of SIM modules, and selecting and using only one SIM module among them. Such a UICC card may or may not be fixed to the terminal. In particular, a UICC that is fixed to a terminal and used is called an eUICC (embedded UICC). In general, the eUICC refers to a UICC card that is used by being fixed to the terminal and can be selected by downloading a SIM module remotely. In the present disclosure, a UICC card that can be remotely downloaded and selected a SIM module is collectively referred to as an eUICC. That is, among UICC cards that can be remotely downloaded and selected by downloading a SIM module, UICC cards that are fixed or not fixed to the terminal are collectively used as eUICCs. In addition, the downloaded SIM module information is collectively used as the term eUICC profile or, more simply, profile.

Hereinafter, the terms used in the present disclosure will be described in more detail.

In the present disclosure, UICC is a smart card inserted into a mobile communication terminal to store personal information such as network access authentication information, phone book, and SMS of a mobile communication subscriber, so that when accessing a mobile communication network such as GSM, WCDMA, LTE, etc., the subscriber It refers to a chip that enables secure mobile communication by performing authentication and traffic security key generation. UICC is loaded with communication applications such as SIM (Subscriber Identification Module), USIM (Universal SIM), and ISIM (IP Multimedia SIM) depending on the type of mobile communication network the subscriber accesses. It is possible to provide a high-level security function for mounting various application applications.

In the present disclosure, an eUICC (embedded UICC) is a security module in the form of a chip embedded in a terminal, not a removable type that can be inserted and removed from the terminal. eUICC can be installed by downloading a profile using OTA (Over The Air) technology. The eUICC can be named as a UICC that can download and install a profile.

In the present disclosure, the method of downloading and installing a profile using OTA technology in the eUICC may be applied to a removable UICC that can be inserted and removed from a terminal. That is, according to an embodiment of the present disclosure, it may be applied to a UICC that can be installed by downloading a profile using OTA technology.

In this disclosure, the term UICC may be used interchangeably with SIM, and the term eUICC may be used interchangeably with eSIM.

In the present disclosure, a profile may mean that an application, a file system, an authentication key value, etc. stored in the UICC are packaged in software form.

In the present disclosure, a USIM Profile may have the same meaning as a profile or may mean that information included in a USIM application within the profile is packaged in a software form.

In the present disclosure, the operation of enabling the profile by the terminal means an operation of changing the state of the profile to the enabled state and setting the terminal to receive a communication service through the communication service provider that provided the profile can do. An activated profile may be expressed as an “enabled profile”.

In the present disclosure, the operation of the terminal disabling the profile means the operation of changing the state of the corresponding profile to the disabled state and setting the terminal not to receive a communication service through the communication service provider that provided the profile. can do. A profile in a deactivated state may be expressed as a “disabled profile”.

In the present disclosure, the operation of the terminal to delete a profile may mean an operation of changing the state of the corresponding profile to the deleted state and setting the terminal to no longer enable or disable the corresponding profile. A profile in a deleted state may be expressed as a “deleted profile”.

In the present disclosure, the operation of the terminal to enable, disable, or delete a profile is performed by setting the state of each profile to an enabled state, a disabled state, or a deleted state (deleted). Instead of changing immediately, each profile is first marked as to be enabled, to be disabled, or to be deleted, and the terminal or the UICC of the terminal is After performing a specific operation (for example, performing a refresh (REFRESH) or reset (RESET) command), each profile is changed to an enabled state, a disabled state, or a deleted state. It can also mean action. Marking a specific profile as intended (i.e., to be enabled, to be disabled, or to be deleted) must be performed only once per profile. It is not limited to displaying the expected status of one or more profiles, each with the same or different predetermined status, a single profile with one or more predetermined statuses, or one or more profiles each with one or more identical or different predetermined status It is also possible to display the status.

In addition, when the terminal displays one or more predetermined statuses for an arbitrary profile, the two indications may be combined into one. For example, if a certain profile is marked as to be disabled and to be deleted, the profile may also be combined to be marked as disabled and deleted.

Also, the operation of the terminal indicating the scheduled status for one or more profiles may be performed sequentially or simultaneously. In addition, the operation of the terminal displaying the scheduled state for one or more profiles and then changing the actual profile state may be performed sequentially or simultaneously.

In the present disclosure, the profile providing server generates a profile, encrypts the generated profile, generates a profile remote management command, or includes a function to encrypt the generated profile remote management command, and SM-DP (Subscription Manager Data Preparation) , SM-DP+ (Subscription Manager Data Preparation plus), off-card entity of Profile Domain, Profile Encryption Server, Profile Creation Server, Profile Provider (Profile Provisioner, PP), Profile Provider (Profile Provider), PPC holder (Profile Provisioning Credentials) holder) can be expressed as

In the present disclosure, the profile management server is SM-SR (Subscription Manager Secure Routing), SM-SR+ (Subscription Manager Secure Routing Plus), off-card entity of eUICC Profile Manager or PMC holder (Profile Management Credentials holder), EM (eUICC Manager) ) can be expressed as

When referring to the profile providing server in the present disclosure, it may also refer to a combination of the functions of the profile management server. Therefore, in various embodiments of the present disclosure, that is, in the following description, the operation of the profile providing server is also possible in the profile management server. Likewise, it goes without saying that the operation described for the profile management server or SM-SR may be performed by the profile providing server.

In the present disclosure, the opening mediation server may be expressed as a Subscription Manager Discovery Service (SM-DS), a Discovery Service (DS), a root opening mediation server (Root SM-DS), and an alternative opening mediation server (Alternative SM-DS). The opening mediation server may receive an event registration request (Register Event Request, Event Register Request) from one or more profile providing servers or opening mediation servers. In addition, one or more opening mediation servers may be used in combination. In this case, the first opening mediation server may receive an event registration request from the second opening mediation server as well as the profile providing server.

In the present disclosure, the profile providing server and the opening intermediary server may be collectively referred to as 'RSP (Remote SIM Provisioning) server'. The RSP server may be expressed as SM-XX (Subscription Manager XX).

In the present disclosure, the eSIM function (eSIM Capability) may be collectively referred to as 'Remote SIM Provisioning Capability (or RSP Capability)'.

The term 'terminal' used in this disclosure is a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (Subscriber Unit) , subscriber station (SS), wireless device, wireless communication device, wireless transmit/receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal include a cellular phone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, and a digital camera having a wireless communication function. devices, gaming devices with wireless communication capabilities, music storage and playback appliances with wireless communications capabilities, Internet appliances with wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. have. In addition, the terminal may include a machine to machine (M2M) terminal and a machine type communication (MTC) terminal/device, but is not limited thereto. In the present disclosure, a terminal may be referred to as an electronic device.

In the present disclosure, the electronic device may have a built-in UICC that can download and install a profile. When the UICC is not embedded in the electronic device, the UICC physically separated from the electronic device may be inserted into the electronic device and connected to the electronic device. For example, the UICC in the form of a card may be inserted into the electronic device. The electronic device may include a terminal, and in this case, the terminal may be a terminal including a UICC that can be installed by downloading a profile. The UICC may be embedded in the terminal, and when the terminal and the UICC are separated, the UICC may be inserted into the terminal, and may be inserted into the terminal and connected to the terminal. A UICC that can be installed by downloading a profile may be referred to as eUICC, for example.

In the present disclosure, the terminal or electronic device may include software or an application installed in the terminal or electronic device to control the UICC or eUICC. Software or an application installed in a terminal or electronic device to control the UICC or eUICC may be referred to as, for example, a Local Profile Assistant (LPA).

In the present disclosure, the profile identifier is a profile identifier (Profile ID), ICCID (Integrated Circuit Card ID), Matching ID, event identifier (Event ID), activation code (Activation Code), activation code token (Activation Code Token), command code ( Arguments that match Command Code, Command Code Token, Signed Command Code, Unsigned Command Code, ISD-P, or Profile Domain (PD) may be referred to as The profile identifier (Profile ID) may indicate a unique identifier of each profile. The profile identifier may further include the address of the profile providing server (SM-DP+) that can index the profile. In addition, the profile identifier may further include a signature of the profile providing server (SM-DP+).

In the present disclosure, the eUICC identifier (eUICC ID) may be a unique identifier of the eUICC embedded in the terminal, and may be referred to as an EID. In addition, if a provisioning profile is pre-loaded in the eUICC, it may be an identifier (Profile ID of Provisioning Profile) of the corresponding provisioning profile. Also, when the terminal and the eUICC chip are not separated as in the embodiment of the present disclosure, it may be a terminal ID. In addition, it may refer to a specific secure domain of the eUICC chip.

In the present disclosure, a profile container (Profile Container) may be called a profile domain (Profile Domain). The profile container may be a security domain.

In the present disclosure, an application protocol data unit (APDU) may be a message for the terminal to interwork with the eUICC. In addition, the APDU may be a message for the PP or PM to interwork with the eUICC.

In the present disclosure, Profile Provisioning Credentials (PPC) may be a means used for mutual authentication, profile encryption, and signature between the profile providing server and the eUICC. PPC may include one or more of a symmetric key, a Rivest Shamir Adleman (RSA) certificate and a private key, an elliptic curved cryptography (ECC) certificate and a private key, a root certification authority (CA), and a certificate chain. can In addition, when there are a plurality of profile providing servers, different PPCs for each of the plurality of profile providing servers may be stored or used in the eUICC.

In the present disclosure, Profile Management Credentials (PMC) may be a means used for mutual authentication and transmission data encryption and signature between the profile management server and the eUICC. The PMC may include one or more of a symmetric key, an RSA certificate and a private key, an ECC certificate and a private key, a root CA, and a certificate chain. In addition, when there are a plurality of profile management servers, different PMCs for each of the plurality of profile management servers can be stored or used in the eUICC.

In the present disclosure, the AID may be an application identifier. This value may be a delimiter that distinguishes different applications within the eUICC.

In the present disclosure, an event may be a general term for profile download, remote profile management, or other profile or eUICC management/processing commands. The event (Event) may be named as a remote SIM provisioning operation (Remote SIM Provisioning Operation, or RSP operation, or RSP operation) or event record, and each event (Event) corresponds to an event identifier (Event Identifier) , Event ID, EventID) or matching identifier (Matching Identifier, Matching ID, MatchingID) and the address (FQDN, IP Address, or URL), the signature of the profile providing server (SM-DP+) or the opening mediation server (SM-DS), and at least one digital certificate of the profile providing server (SM-DP+) or the opening mediation server (SM-DS) It can be referred to as data that Data corresponding to the event may be referred to as an activation code or a command code. Part or all of the procedure for using a command code may be referred to as “activation code processing procedure” or “command code processing procedure” or “activation code procedure” or “command code procedure” or “LPA API (Local Profile Assistant Application Programming Interface)” or “ It may be referred to as "LPA API procedure" or "LPA API processing procedure". Profile Download may be mixed with Profile Installation. Event Type may also be used as a term to indicate whether a particular event is a profile download, remote profile management (eg delete, enable, disable, replace, update, etc.) or other profile or eUICC management/processing command. and can be named as an operation type (Operation Type or OperationType), an operation classification (Operation Class or OperationClass), an event request type (Event Request Type), an event classification (Event Class), an event request class (Event Request Class), etc. . As for an arbitrary event identifier (EventID or MatchingID), a path or usage purpose (EventID Source or MatchingID Source) from which the terminal obtained the corresponding event identifier (EventID or MatchingID) may be designated.

In the present disclosure, event checking may be a generic term for an operation in which the terminal checks the presence or absence of an event registered for the eUICC of the terminal in the opening intermediary server. Event confirmation may be performed between the terminal and the opening intermediary server without a mutual authentication process or during a mutual authentication process.

In the present disclosure, the event checking identifier (Event Checking ID, ECID) may be a generic term for an identifier provided by the terminal to the opening mediation server in order to check the existence of an event registered in the opening mediation server. The event confirmation identifier may be generated based on the address of the opening intermediary server and the eUICC identifier of the terminal. The event identification identifier may be generated by at least one of a terminal, an opening mediation server, a profile providing server, and a service provider. In the present disclosure, a profile package may be used interchangeably with a profile or a term indicating a data object of a specific profile, and may be named as Profile TLV or Profile Package TLV. When the profile package is encrypted using an encryption parameter, it may be named as a Protected Profile Package (PPP) or a Protected Profile Package TLV (PPP TLV). When the profile package is encrypted using an encryption parameter that can only be decrypted by a specific eUICC, it may be named as a Bound Profile Package (BPP) or a Bound Profile Package TLV (BPP TLV). The profile package TLV may be a data set expressing information constituting a profile in a TLV (Tag, Length, Value) format.

In the present disclosure, Local Profile Management (LPM) includes Profile Local Management, Local Management, Local Management Command, Local Command, and Local Profile Management Package. (LPM Package), a Profile Local Management Package, a Local Management Package (LOCAL MANAGEMENT PACKAGE), a Local Management Command Package, and a Local Command Package. LPM changes the status (Enabled, Disabled, Deleted) of a specific profile through software installed in the terminal, or the contents of a specific profile (eg, a profile nickname (Profile Nickname), or profile summary information (Profile Metadata), etc.) ) can be used for updating. The LPM may include one or more local management commands. In this case, the target profile of each local management command may be the same or different for each local management command.

In the present disclosure, remote profile management (Remote Profile Management, RPM) is Profile Remote Management, Remote Management, Remote Management Command, Remote Command, Remote Profile Management Package (RPM Package), a Profile Remote Management Package, a Remote Management Package, a Remote Management Command Package, and a Remote Command Package. RPM changes the status (Enabled, Disabled, Deleted) of a specific profile or changes (updates) the contents of a specific profile (eg, a profile nickname (Profile Nickname), or profile summary information (Profile Metadata), etc.) can be used for The RPM may include one or more remote management commands. In this case, the target profile of each remote management command may be the same or different for each remote management command.

In the present disclosure, a certificate (Certificate) or digital certificate (Digital Certificate) is an asymmetric key (Asymmetric Key)-based mutual authentication consisting of a pair of a public key (PK) and a secret key (SK) ) may represent a digital certificate used for Each certificate includes one or more public keys (PK), a public key identifier (PKID) corresponding to each public key, and an identifier of the certificate issuer (CI) that issued the corresponding certificate. (Certificate Issuer ID) and digital signature (Digital Signature) may be included.

In addition, the certificate issuer may be named as a certification issuer, a certificate authority (CA), a certification authority, and the like.

In the present disclosure, a public key (PK) and a public key identifier (PKID) are a specific public key or a certificate including the corresponding public key, or a part of a specific public key or a certificate including the corresponding public key. A portion, or a result of an operation of a specific public key (eg, Hash), or a value of an operation result (eg, Hash) of a certificate including the corresponding public key (eg, Hash), or a portion of a specific public key The same meaning refers to the operation result (eg, hash) value, the operation result (eg, hash) value of a part of the certificate including the public key, or the storage space in which data is stored. can be mixed.

In the present disclosure, certificates (primary certificate) issued by one certificate issuer are used to issue another certificate (secondary certificate), or secondary certificates are used to jointly issue tertiary or higher certificates In this case, the correlation between the certificates can be named as a Certificate Chain or Certificate Hierarchy, and in this case, the CI certificate used to issue the first certificate is the , Root CI, Root CI Certificate, Root CA, Root CA Certificate, and the like.

In the present disclosure, a mobile operator may represent a business that provides a communication service to a terminal, and a business supporting system (BSS), an operational supporting system (OSS), a POS terminal of the communication operator. (point of sale terminal), and other IT systems may be collectively referred to. In addition, in the present disclosure, the telecommunication service provider is not limited to expressing only one specific business entity that provides a communication service, but a group or association (association or consortium) of one or more businesses or a term referring to an agency representing the group or association may be used as In addition, in the present disclosure, a telecommunication operator may be named as an operator (operator or OP or Op.), a mobile network operator (MNO), a service provider (or SP), a profile owner (PO), and the like. In addition, each carrier may set or be assigned at least one name and/or an object identifier (OID) of the carrier. If a telecommunications carrier refers to a group or association or agency of one or more entities, the name or unique identifier of any group or association or agency is shared by all entities belonging to that group or association or all entities working with such entity. It can be a name or a unique identifier.

In the present disclosure, AKA may indicate authentication and key agreement, and may indicate an authentication algorithm for accessing 3GPP and 3GPP2 networks.

In the present disclosure, K is an encryption key value stored in the eUICC used for the AKA authentication algorithm.

In the present disclosure, OPc is a parameter value that may be stored in the eUICC used for the AKA authentication algorithm.

In the present disclosure, NAA is a network access application (Network Access Application) application program, and may be an application program such as USIM or ISIM stored in UICC to access a network. The NAA may be a network access module.

In the present disclosure, an indicator may be used for expressing that an arbitrary function, setting, or operation is necessary or not required, or may also be used for a purpose of expressing the corresponding function, setting, or operation itself. In addition, in the present disclosure, the marker may be expressed in various forms such as a character string or an alphanumeric string, an operator representing true/false (boolean - TRUE or FALSE), a bitmap, an array, etc. Other expressions with meaning can be mixed.

And, in describing the present disclosure, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted.

1 is a diagram illustrating a method of connecting a terminal to a mobile communication network using a UICC having a fixed profile mounted on the terminal according to various embodiments of the present disclosure.

As shown in FIG. 1 , the UICC 120 may be inserted into the terminal 110 . For example, the UICC 120 may be removable or may be pre-built in the terminal.

The fixed profile of UICC loaded with a fixed profile means that 'access information' that can connect to a specific carrier is fixed. For example, the access information may be a K or Ki value required to authenticate to the network together with an IMSI as a subscriber identifier and a subscriber identifier.

The terminal 110 according to various embodiments may perform authentication with an authentication processing system (eg, home location register (HLR) or AuC) of a mobile communication company using the UICC 120 . For example, the authentication process may be an Authentication and Key Agreement (AKA) process. When the authentication is successful, the terminal can use a mobile communication service such as a phone call or use of mobile data using the network 130 of the mobile communication company of the mobile communication system.

2 is a diagram illustrating an example of connection to a terminal, an opening mediation server, a profile providing server, and a service provider according to various embodiments of the present disclosure;

As shown in FIG. 2 , the eSIM 211 may be mounted in the terminal 210 , and a profile (not shown) may be installed in the eSIM 211 . Also, the LPA 212 may be installed in the terminal 210 . The eSIM 211 may be controlled by the LPA 212 . The user 200 may install a profile in the eSIM 211 of each terminal or control the installed profile through the LPA 212 .

The user 200 may receive a communication service from a service provider (hereinafter referred to as "communication service provider" or "operator", 240 ). To this end, a profile (not shown) of the operator 240 may be installed in the terminal 210 .

The operator 240 may be connected to the profile server 230 , and the LPA 212 of the terminal 210 may be connected to the profile server 230 and the opening intermediary server 220 . 2 shows a case in which each of the profile server 230 and the opening mediation server 220 is configured as a single server for convenience, however, one or more profile servers (SM-DP+) may be included in the server configuration according to implementations and embodiments. , one or more open mediation servers (SM-DS) that assist in the creation of a connection between a specific profile server and the terminal may be included in the server configuration. It should be noted that the configuration of various servers as described above may be briefly represented as a single profile server in the drawings below.

Detailed operations and messages of the user 200, the operator 240, the terminal 210, the eSIM 211, the LPA 212, the profile server 230, and the opening intermediary server 220 according to an embodiment of the present disclosure The exchange procedure will be described in detail with reference to the drawings to be described later.

The address (FQDN, IP Address, or URL) of the opening intermediary server 220 may be stored in the terminal 210 to the LPA 221 or the eSIM 211 .

As shown in FIG. 2 , the opening mediation server 220 may be connected to the profile providing server 230 . For example, the profile providing server 230 may generate a specific event and register the generation of the corresponding event with the opening mediation server 220 . The information provided by the profile providing server 230 to the opening mediation server 220 to register event generation may include at least one of the following.

- forwarding indicator

- Address of the profile providing server (FQDN, or Fully Qualified Domain Name)

- Unique object identifier (Object ID, or OID) of the profile providing server

- IP address of the profile providing server

- Event identifier (EventID or MatchingID) created on the profile providing server

- The eSIM identifier (hereinafter eUICC identifier or EID) targeted by the event generated in the profile providing server

- Identifier of whether to allow the use of the event check function for the event (EventCheckingSupport)

- The event checking identifier (Event Checking ID, or ECID) associated with the eUICC identifier to be used when checking the above event

Detailed operation and message exchange procedure between the user 200 , the terminal 210 , the eSIM 211 , the LPA 212 , the opening intermediary server 220 , the profile providing server 230 , and the operator 240 according to various embodiments will be looked into in detail later.

3 is a diagram illustrating an example of a message exchange procedure in which a profile providing server registers event generation with an opening intermediary server according to various embodiments of the present disclosure.

As shown in FIG. 3 , in step 3001, the operator 350 may instruct the profile providing server 330 to generate an event corresponding to at least one of a remote management command of a profile for download or a profile installed in the terminal. . In this case, the operator 350 may selectively include at least one of the following information in the event generation command.

- Identifier (eUICC ID, EID) of the eUICC in the terminal (not shown) targeted by the event

- At least one opening mediation server address (SM-DS Address) to register the event information created in the opening mediation server

- Identifier of whether the opening brokerage server allows the use of the event check function for the event (EventCheckingSupport)

In step 3001 , the profile providing server 330 may generate an event according to the request of the operator 350 .

In step 3002 , the event generated by the profile providing server 330 may be registered with the opening mediation server 310 . For example, the event registration step of step 3002 may include transmitting an event registration request message (Register Event Request) selectively including at least one or more of the following information to the opening brokerage server 310 .

- Event identifier (EventID or MatchingID)

- Identifier (eUICC ID, EID) of the eUICC in the terminal (not shown),

- Address of at least one or more profile providing server 330 (SM-DP+ Address)

- Forwarding Indicator set to 'False'

- Identifier of whether to allow the use of the event check function (EventCheckingSupport)

- Event Checking ID

In step 3003, the opening mediation server 310 may register the event requested by the profile providing server 330. In this case, the opening intermediary server 310 may store the event identifier provided in step 3002, the profile providing server address, and the profile providing server unique object identifier (Object ID, or OID).

If the profile providing server 320 permits the use of the event confirmation function in step 3002, or if the event confirmation function is permitted by the contract terms between the profile providing server 320 and the opening mediation server 310, the opening brokerage in step 3004 The server 310 may selectively generate an event confirmation identifier (ECID) corresponding to an eUICC identifier (EID) in a terminal (not shown) delivered by the profile providing server 330 . Also, the opening intermediary server 310 may recycle an event confirmation identifier (ECID) previously associated with the corresponding eUICC identifier (EID) or use an event confirmation identifier (ECID) provided by the profile providing server 330 .

In step 3004, the opening intermediary server 310 may store the event by connecting the event confirmation identifier (ECID) and the eUICC identifier (EID) in the terminal (not shown).

In step 3005, the opening mediation server 310 may return an event registration response message (Register Event Response) to notify the profile providing server 330 of the event registration result.

4 is a diagram illustrating an example of a message exchange procedure in which a profile providing server registers event generation successively in a plurality of open intermediary servers according to various embodiments of the present disclosure.

As shown in FIG. 4 , in step 4001, the operator 450 may instruct the profile providing server 430 to generate an event corresponding to at least one of a remote management command of a profile for download or a profile installed in the terminal. . In this case, the operator 450 may selectively include at least one of the following information in the event generation command.

- Identifier (eUICC ID, EID) of the eUICC in the terminal (not shown) targeted by the event

- At least one opening mediation server address (SM-DS Address) to register the event information created in the opening mediation server

- Identifier of whether the opening brokerage server allows the use of the event check function for the event (EventCheckingSupport)

In step 4001 , the profile providing server 430 may generate an event according to the request of the operator 450 .

In step 4002 , the event generated by the profile providing server 430 may be registered in the alternative opening mediation server 420 . For example, the event registration step of step 4002 may include transmitting an event registration request message (Register Event Request) selectively including at least one or more of the following information to the alternative brokerage server 420. .

- Event identifier (EventID1 or MatchingID)

- Identifier (eUICC ID, EID) of the eUICC in the terminal (not shown),

- Address of at least one or more profile providing server 430 (SM-DP+ Address)

- Forwarding Indicator set to 'True'

- Identifier of whether to allow the use of the event check function (EventCheckingSupport)

- Event Checking ID

In step 4003, the alternative opening mediation server 420 may register the event requested by the profile providing server 430. In this case, the alternative opening intermediary server 420 may store the event identifier provided in step 3002, the profile providing server address, and the profile providing server unique object identifier (Object ID, or OID). Also, in step 4003, the alternative opening intermediary server 420 may generate a new event identifier 2 (EventID2).

In step 4004 , the alternative opening mediation server 420 may register the generated event with the opening mediation server 410 . For example, the event registration step of step 4004 may include transmitting an event registration request message (Register Event Request) selectively including at least one or more of the following information to the opening brokerage server 410 .

- Event identifier (EventID2)

- Identifier (eUICC ID, EID) of the eUICC in the terminal (not shown)

- Address of at least one or more profile providing server 430 (SM-DP+ Address)

- Forwarding Indicator set to 'False'

- Identifier of whether to allow the use of the event check function (EventCheckingSupport)

- Event Checking ID

In step 4005, the opening mediation server 410 may register the event requested by the alternative opening mediation server 420. In this case, the opening mediation server 420 may store the event identifier 2 provided in step 4004, the alternate opening mediation server address, and the alternate opening mediation server unique object identifier (Object ID, or OID). In step 4002, the profile providing server 430 permits the use of the event confirmation function, or the event confirmation function is permitted by the contract terms between the profile providing server 420 and the opening mediation server 410 and the alternative opening mediation server 420. In this case, in step 4006, the opening mediation server 410 may selectively generate an event confirmation identifier (ECID) corresponding to the eUICC identifier (EID) in the terminal (not shown) delivered by the alternative opening mediation server 420 . Also, the opening intermediary server 410 may recycle an event confirmation identifier (ECID) previously associated with the corresponding eUICC identifier (EID) or use an event confirmation identifier (ECID) provided by the profile providing server 430 .

In step 4006, the opening intermediary server 410 may store the event by connecting the event confirmation identifier (ECID) and the eUICC identifier (EID) in the terminal (not shown).

In step 4007 , the opening mediation server 410 may return an event registration response message (Register Event Response) to notify the alternative opening mediation server 420 of the event registration result. Also, after receiving the response message in step 4008 , the alternative opening intermediary server 420 may return a Register Event Response message to notify the profile providing server 270 .

5 is a diagram illustrating an example of a message exchange procedure when an event confirmation identifier issuance or registration operation is performed between a terminal and an opening intermediary server according to various embodiments of the present disclosure;

In the embodiment of FIG. 5 , the terminal 510 may be mixed with an LPA (not shown) or an eSIM (not shown).

In step 5001 , the LPA (not shown) of the terminal 510 may acquire information of at least one or more opening intermediary servers 530 stored in the eSIM (not shown) or the LPA (not shown) in the terminal 510 . For example, step 5001 may be performed by first booting of the terminal, rebooting, inputting a profile installation command by a user, performing a profile remote management command confirmation by a user, and the like. In step 5001, the information of the opening intermediary server may selectively include at least one or more of the following.

- At least one open intermediary server address

- Event identification identifier (ECID) that can be used for the above-mentioned opening intermediary server

In this case, the terminal 510 may not have an opening intermediary server address, and an event confirmation identifier usable for the corresponding opening intermediary server may not exist, or an event confirmation identifier may exist but may not be valid.

The event confirmation identifier may be stored together with the issue date, expiration date, and expiration date, and may not be valid when the period expires. In addition, the available number of use of the event confirmation identifier may be specified, and if the number of uses is exceeded, it may not be valid.

If the terminal 510 supports the event confirmation or acquisition function through the opening mediation server and has acquired the address of at least one opening mediation server 530 in step 5001, the LPA of the terminal 510 is the opening mediation server in step 5002. A TLS connection may be established with the 530 .

If the LPA of the terminal 510 supports the event confirmation function, but does not obtain an event confirmation identifier that is currently available for the opening mediation server 530 in step 5001, the terminal 510 in step 5003 is the opening mediation server 530. and mutual authentication for event acquisition. At this time, mutual authentication is performed by using an asymmetric key consisting of a pair of a public key (PK) and a secret key (SK) by the eSIM (or eUICC) of the terminal 510 and the opening intermediary server. It may be a certificate-based mutual authentication that authenticates each other.

The terminal 510 may transmit a request for acquiring an event related to the eSIM mounted on the terminal 510 to the opening intermediary server 530 in step 5004 of the mutual authentication process. Before transmitting the request, the eSIM may authenticate the opening intermediary server 530 . The request may optionally include at least one of the following information.

- eUICC identifier (EID)

- Event identifier (EventID or MatchingID)

- Identifier supporting the event confirmation function of the terminal 510

- Request to issue event confirmation identifier (EcidRequest)

- eUICC signature generated with eUICC's private key

- eUICC certificate and higher certificate

- Identifier supporting the signature verification function of the opening intermediary server

Some or all of the information may be transmitted by being included in eUICC information (euiccInfo) or terminal information (deviceInfo).

In step 5004, the opening intermediary server 530 may authenticate the eUICC by verifying the eUICC identifier, the eUICC signature, and the eUICC certificate.

In step 5005, when the opening intermediary server 530 supports the event confirmation function, it may generate an event confirmation identifier (ECID) corresponding to the eUICC identifier (EID). The opening mediation server 530 may create a new event confirmation identifier or reuse an event confirmation identifier stored previously. Also, the opening intermediary server 530 may connect and store the current eUICC identifier (EID) and the event confirmation identifier (ECID). The event confirmation identifier generation may be selectively performed when an event confirmation identifier issuance request (EcidRequest) is received from the terminal 510 in step 5004, and is opened without a new event confirmation identifier issuance request (EcidRequest) of the terminal 510 It may be selectively performed at the judgment of the intermediary server 530 .

In step 5005, the opening intermediary server 530 may set and store at least one of an issuance date, an effective period, an effective date, and a usable number of the event confirmation identifier. In addition, the event identification identifier may be invalid due to the expiration of the period or exceeding the number of uses, and in this case, a new event identifier may be created.

In step 5005, the opening intermediary server 530 may search for a registered event corresponding to the requested eUICC identifier (EID) or eUICC identifier (EID) and the event identifier.

In step 5006, the opening mediation server 530 may return an event request response message. In this case, the event request response message may selectively include at least one or more of the following.

- Event list: Event identifier (Event ID or Matching ID) and RSP server address, event list may be empty

- Whether the event check function is supported

- event identification identifier

- Event confirmation identifier validity conditions (expiration period, effective date, next event confirmation identifier issuance required date, next event acquisition request required date, number of uses, etc.)

In step 5003, when the terminal 510 transmits that it can verify the signature of the opening intermediary server 530 through the identification of the opening intermediary server signature verification function support identifier, the opening intermediary server 530 transmits some or all of the information. It can be signed with the private key of the opening intermediary server (530).

In step 5006, when there is no event corresponding to the eUICC identifier of the terminal 510 and the requested event identifier, the opening mediation server 530 may recognize an incorrect event identifier and return an error. At this time, if the mutual authentication process is successfully performed, at least one of whether the event check function is supported or an event check identifier may be selectively returned together with an error message.

In step 5007 , the terminal 510 may verify if the signature of the opening mediation server 530 is included in the reply value of the opening mediation server 530 . If the verification fails, the terminal 510 may stop the process and display an error to the user (not shown). When verifying the signature of the opening intermediary server 530, the terminal 510 may proceed to step 5008 if the verification is successful.

In step 5008 , the terminal 510 may store the currently returned address of the open intermediary server 530 and the returned event confirmation identifier in the terminal 510 . In this case, the returned information may be stored in an LPA (not shown) installed in the terminal 510 or an eSIM (or eUICC, not shown) installed in the terminal 510 .

6 is a diagram illustrating another example of a message exchange procedure when an event confirmation identifier issuance or registration operation is performed between a terminal and an opening intermediary server according to various embodiments of the present disclosure;

In the embodiment of FIG. 6 , the terminal 610 may be mixed with LPA (not shown) or eSIM (not shown).

In step 6001 , the LPA (not shown) of the terminal 610 may acquire information of at least one or more opening intermediary servers 630 stored in the eSIM (not shown) or the LPA (not shown) in the terminal 610 . For example, step 6001 may be performed by first booting of the terminal, rebooting, inputting a profile installation command by a user, performing a profile remote management command confirmation by a user, and the like. In step 6001, the information of the opening intermediary server may selectively include at least one or more of the following.

- At least one open intermediary server address

- Event identification identifier (ECID) that can be used for the above-mentioned opening intermediary server

In this case, the terminal 610 may not have an opening intermediary server address, and an event confirmation identifier usable for the corresponding opening intermediary server may not exist, or an event confirmation identifier may exist but may not be valid.

The event confirmation identifier may be stored together with the issue date, expiration date, and expiration date, and may not be valid when the period expires. In addition, the available number of use of the event confirmation identifier may be specified, and if the number of uses is exceeded, it may not be valid.

In step 6002, the terminal 610 may generate an event confirmation identifier. In this case, the terminal 610 may generate an event identifier when the event identifier is invalid or does not exist in step 6001 .

If the terminal 610 supports the event confirmation or acquisition function through the opening mediation server, and acquiring the address of at least one opening mediation server 630 in step 6001, the LPA of the terminal 610 in step 6003 is the opening mediation server It is possible to establish a TLS connection with the 630 .

In step 6004, the terminal 610 may perform a mutual authentication process for acquiring an event with the opening intermediary server 630. At this time, mutual authentication is performed by using an asymmetric key consisting of a pair of a public key (PK) and a secret key (SK) by the eSIM (or eUICC) of the terminal 610 and the opening intermediary server. It may be a certificate-based mutual authentication that authenticates each other.

The terminal 610 may transmit a request for acquiring an event related to the eSIM mounted on the terminal 610 to the opening intermediary server 630 in step 6005 of the mutual authentication process. Before transmitting the request, the eSIM may authenticate the opening intermediary server 630 . The request may optionally include at least one of the following information.

- eUICC identifier (EID)

- Event identifier (EventID or MatchingID)

- Identifier supporting the event confirmation function of the terminal 610

- event identification identifier

- Event confirmation identifier validity conditions (expiration period, effective date, number of uses, etc.)

- eUICC signature generated with eUICC's private key

- eUICC certificate and higher certificate

- Identifier supporting the signature verification function of the opening intermediary server

Some or all of the information may be transmitted by being included in eUICC information (euiccInfo) or terminal information (deviceInfo).

In step 6005, the opening intermediary server 630 may authenticate the eUICC by verifying the eUICC identifier, the eUICC signature, and the eUICC certificate.

In step 6006, if the opening mediation server 630 supports the event confirmation function, the current eUICC identifier (EID) and the event confirmation identifier (ECID) may be connected and stored. In addition, when the event confirmation identifier transmitted by the terminal 610 is a value that cannot be used by the opening intermediary server 630 (eg, duplicate ECID existence, etc.), the opening intermediary server 630 may generate a new event confirmation identifier. The opening intermediary server 630 may store at least one of an issuance date, an effective period, an effective date, and a usable number of the event confirmation identifier together.

In step 6006, the opening intermediary server 630 may search for a registered event corresponding to the requested eUICC identifier (EID) or eUICC identifier (EID) and the event identifier.

In step 6007, the opening mediation server 630 may return an event request response message. In this case, the event request response message may selectively include at least one or more of the following.

- Event list: Event identifier (Event ID or Matching ID) and RSP server address, event list may be empty

- Whether the event check function is supported

- event identification identifier

- Event confirmation identifier validity conditions (expiration period, effective date, next event confirmation identifier issuance required date, next event acquisition request required date, number of uses, etc.)

In step 6004, when the terminal 610 transmits that it can verify the signature of the opening intermediary server 630 through the identification of the opening intermediary server signature verification function support identifier, the opening intermediary server 630 transmits some or all of the information. It can be signed with the private key of the opening intermediary server (630).

When there is no event corresponding to the eUICC identifier of the terminal 610 and the requested event identifier in step 6006, the opening intermediary server 630 may recognize an incorrect event identifier and return an error. At this time, if the mutual authentication process is successfully performed, at least one of whether the event check function is supported or an event check identifier may be selectively returned together with an error message.

In step 6008 , the terminal 610 may verify if the signature of the opening mediation server 630 is included in the reply value of the opening mediation server 630 . If the verification fails, the terminal 610 may stop the process and display an error to the user (not shown). When verifying the signature of the opening intermediary server 630, the terminal 610 may proceed to step 6009 if the verification is successful.

In step 6009 , the terminal 610 may store the currently returned address of the opening intermediary server 630 and the returned event confirmation identifier in the terminal 610 . In this case, the returned information may be stored in an LPA (not shown) installed in the terminal 610 or an eSIM (or eUICC, not shown) installed in the terminal 610 .

7 is a diagram illustrating another example of a message exchange procedure when an event check operation is performed using an event check identifier of a terminal and an open intermediary server according to various embodiments of the present disclosure.

In the embodiment of FIG. 7 , the terminal 710 may be mixed with LPA (not shown) or eSIM (not shown).

In step 7001, the LPA (not shown) of the terminal 710 may acquire information of at least one or more opening intermediary servers 730 stored in the eSIM (not shown) or LPA (not shown) in the terminal 710 . For example, step 7001 may be performed by first booting the terminal, rebooting, inputting a profile installation command by a user, performing a profile remote management command confirmation by a user, and the like. In step 7001, the information of the opening intermediary server may selectively include at least one or more of the following.

- At least one open intermediary server address

- Event identification identifier (ECID) that can be used for the above-mentioned opening intermediary server

In this case, the terminal 710 may not have an address of the opening brokerage server, and an event confirmation identifier that can be used in the corresponding opening mediation server may not exist, or an event confirmation identifier may exist but may not be valid.

The event confirmation identifier may have the issuance date, validity period, validity date, next event confirmation identifier issuance required date or next event acquisition request required date stored together, and may not be valid when the period has expired. In addition, the available number of use of the event confirmation identifier may be specified, and if the number of uses is exceeded, it may not be valid. In addition, if the required date for issuing the next event confirmation identifier is exceeded, the terminal may proceed directly to step 7007 to issue the event confirmation identifier. In addition, when the required date of the next event acquisition request is exceeded, the terminal may proceed to step 7007 to request the event acquisition, and at this time, may also proceed with the issuance of the event confirmation identifier.

If the terminal 710 supports the event confirmation or acquisition function through the opening mediation server, and acquiring the address of at least one opening mediation server 730 in step 7001, the LPA of the terminal 710 in step 7002 is the opening mediation server A TLS connection may be established with the 730 .

In step 7003, the terminal 710 may transmit an event confirmation request for checking whether an event exists to the opening mediation server 730. In this case, the event confirmation request may include an event confirmation identifier connected to the opening mediation server 730 . In addition, the event confirmation request may optionally include a new event confirmation identifier issuance request (EcidRequest).

In step 7004, the opening mediation server 730 may search whether an event related to the event confirmation identifier exists. Also, the opening mediation server 730 may verify the validity of the corresponding event confirmation identifier. In addition, when the event confirmation identifier requested from the terminal 710 in step 7003 is valid, the opening intermediary server 730 selectively generates a new event confirmation identifier and eUICC identifier (EID) connected to the existing valid event confirmation identifier and a new event A confirmation identifier can be concatenated and stored. The generation of a new event identifier may be selectively performed when receiving a new event confirmation identifier issuance request (EcidRequest) from the terminal 710, and without a new event confirmation identifier issuance request (EcidRequest) of the terminal 710, the opening intermediary server ( 730) may be selectively performed.

In addition, the opening intermediary server 730 may set and store at least one of the issuance date, the valid period, the valid date, and the available number of times of the newly created event confirmation identifier, and may discard the existing event confirmation identifier.

In step 7005, the opening intermediary server 730 may selectively return at least one of the following to the terminal 710 according to the result of the event presence or absence search and event confirmation identifier verification performed in step 7004.

- Event Existence Identifier: Event exists or does not exist

- Event Confirmation Identifier Valid Identifier (noECID): Event Confirmation Identifier is not valid

- New event identification identifier (newECID)

- Conditions for validity of new event confirmation identifier (expiration period, effective date, next event confirmation identifier issuance required date, next event acquisition request required date, number of uses, etc.)

If the opening mediation server 730 does not support the event check function, the opening mediation server 730 may return an error indicating that the function is not supported.

In step 7006, the terminal 710 may check the reply of the opening intermediary server 730. When it is confirmed that the event does not exist in the reply of step 7005 or an error is returned, the terminal 710 may end the process. In addition, when a new event confirmation identifier is returned in the reply of step 7005 , the terminal 710 may store the currently returned address of the open intermediary server 730 and the returned event confirmation identifier in the terminal 710 . In this case, the returned information may be stored in an LPA (not shown) installed in the terminal 710 or an eSIM (or eUICC, not shown) installed in the terminal 710 . If an event exists in the reply of step 7005 or it is confirmed that the event confirmation identifier provided by the terminal 710 to the opening intermediary server 730 is invalid in step 7003, the terminal 710 acquires an event or updates the event confirmation identifier The following steps can be taken for

In step 7007 , the terminal 710 may establish a TLS connection with the opening intermediary server 730 . In this case, if the TLS connection established in step 7002 is valid, the terminal 710 and the opening intermediary server 730 may continue to use the existing TLS connection and may not perform step 7007.

In step 7008, the terminal 710 may perform a mutual authentication process with the opening intermediary server 730 for acquiring an event or issuing an event confirmation identifier. In this case, the mutual authentication is an asymmetric key consisting of a pair of a public key (PK) and a secret key (SK) between the eSIM (or eUICC) of the terminal 710 and the opening intermediary server 730. It may be a certificate-based mutual authentication that authenticates each other using

The terminal 710 may transmit a request for acquiring an event related to the eSIM mounted on the terminal 710 to the opening intermediary server 730 in step 7009 of the mutual authentication process. Before transmitting the request, the eSIM may authenticate the opening intermediary server 730 . The request may optionally include at least one of the following information.

- eUICC identifier (EID)

- Event identifier (EventID or MatchingID)

- Identifier supporting the event confirmation function of the terminal 510

- Request to issue event confirmation identifier (EcidRequest)

- eUICC signature generated with eUICC's private key

- eUICC certificate and higher certificate

- Identifier supporting the signature verification function of the opening intermediary server

Some or all of the information may be transmitted by being included in eUICC information (euiccInfo) or terminal information (deviceInfo).

In step 7009, the opening intermediary server 730 may authenticate the eUICC by verifying the eUICC identifier, the eUICC signature, and the eUICC certificate.

In step 7010, the opening mediation server 730 may search for a registered event corresponding to the requested eUICC identifier (EID) or eUICC identifier (EID) and the event identifier.

In step 7010, if the opening mediation server 730 supports the event confirmation function, it may generate an event confirmation identifier (ECID) corresponding to the eUICC identifier (EID). The event confirmation identifier generation may be selectively performed when an event confirmation identifier issuance request (EcidRequest) is received from the terminal 710 in step 7008, and is opened without a new event confirmation identifier issuance request (EcidRequest) of the terminal 710 It may be selectively performed at the judgment of the intermediary server 730 .

The opening intermediary server 730 may create a new event confirmation identifier, or reuse the previously stored event confirmation identifier. Also, the opening intermediary server 730 may connect and store the current eUICC identifier (EID) and the event confirmation identifier (ECID).

In step 7010, the opening intermediary server 730 may set and store at least one of an issuance date, an effective period, an effective date, and a usable number of the event confirmation identifier. In addition, the event identification identifier may become invalid due to the expiration of the period or exceeding the number of uses, and in this case, a new event identifier may be created.

In step 7011, the opening mediation server 730 may return an event request response message. In this case, the event request response message may selectively include at least one or more of the following.

- Event list: Event identifier (Event ID or Matching ID) and RSP server address, event list may be empty

- Whether the event check function is supported

- event identification identifier

- Event confirmation identifier validity conditions (period, number of uses, etc.)

In step 7008, when the terminal 710 transmits that it can verify the signature of the opening mediation server 730 through the identifier for verifying the signature verification function of the opening mediation server, the opening mediation server 730 transmits some or all of the information. It can be signed with the private key of the opening intermediary server 730 .

In step 7012 , the terminal 710 may verify if the signature of the opening mediation server 730 is included in the reply value of the opening mediation server 730 . If the verification fails, the terminal 710 may stop the process and display an error to the user (not shown). When verifying the signature of the opening intermediary server 730, the terminal 710 may optionally proceed to step 7013 if the verification is successful.

In step 7013 , the terminal 710 may store the currently returned address of the opening intermediary server 730 and the returned event confirmation identifier in the terminal 710 . In this case, the returned information may be stored in an LPA (not shown) installed in the terminal 710 or an eSIM (or eUICC, not shown) installed in the terminal 710 .

In step 7014, the terminal 710 may perform an event by accessing the RSP server (profile providing server or alternative opening intermediary server) using the returned event list information.

8 is a diagram illustrating another example of a message exchange procedure when an event check operation is performed during a mutual authentication process using an event check identifier of a terminal and an opening intermediary server according to various embodiments of the present disclosure.

In the embodiment of FIG. 8 , the terminal 810 may be mixed with LPA (not shown) or eSIM (not shown).

In step 8001 , the LPA (not shown) of the terminal 810 may acquire information of at least one or more opening intermediary servers 830 stored in the eSIM (not shown) or the LPA (not shown) in the terminal 810 . For example, step 8001 may be performed by first booting the terminal, rebooting, inputting a profile installation command by a user, performing a profile remote management command confirmation by a user, and the like. In step 8001, the information of the opening mediation server may selectively include at least one or more of the following.

- At least one open intermediary server address

- Event identification identifier (ECID) that can be used for the above-mentioned opening intermediary server

In this case, the terminal 810 may not have an address of the opening brokerage server, and there may be no event confirmation identifier available for the corresponding opening brokerage server, or an event confirmation identifier may exist but may not be valid.

The event confirmation identifier may be stored together with the issue date, expiration date, and expiration date, and may not be valid when the period expires. In addition, the available number of use of the event confirmation identifier may be specified, and if the number of uses is exceeded, it may not be valid.

If the terminal 810 supports the event confirmation or acquisition function through the opening mediation server, and acquiring the address of at least one opening mediation server 830 in step 8001, the LPA of the terminal 810 is the opening mediation server in step 8002. A TLS connection may be established with the 830 .

In step 8003, the terminal 810 may perform a mutual authentication process for acquiring an event with the opening intermediary server 830. At this time, mutual authentication is performed by using an asymmetric key consisting of a pair of a public key (PK) and a secret key (SK) by the eSIM (or eUICC) of the terminal 810 and the opening intermediary server. It may be a certificate-based mutual authentication that authenticates each other.

The terminal 810 may transmit the InitiateAuthentication request of the terminal 810 to the opening intermediary server 830 in step 8004 of the mutual authentication process, and the request may optionally include at least one of the following values. can

- Event identification identifier (ECID) to check the existence of an event

- A random number value (euiccChallenge) generated by the eSIM mounted on the terminal 810

- eSIM information (euiccInfo or euiccInfo1) mounted on the terminal 810

- RSP function information supported by the LPA (not shown) installed in the terminal 810

- Opening brokerage server (830) address

The event identification identifier (ECID) is included in at least one of information on the eSIM (euiccInfo or euiccInfo1) installed in the terminal 810 or RSP function information supported by the LPA (not shown) installed in the terminal 810, or independently It may be included in the mutual authentication start request message.

In step 8005, the opening mediation server 830 may search whether an event related to the event identification identifier exists. Also, the opening mediation server 830 may verify the validity of the corresponding event confirmation identifier.

In step 8006, the opening intermediary server 830 may reply to the terminal 810 by selectively including at least one of the following in the InitiateAuthentication response according to the result of the event check and event confirmation identifier verification performed in step 8005. can

- Event Existence Identifier: Event exists or does not exist

- Event Confirmation Identifier Valid Identifier: Event Confirmation Identifier is invalid

If the opening mediation server 830 does not support the event check function, the opening mediation server 830 may return an error indicating that the function is not supported. The reply value may be signed with the private key of the opening intermediary server 830, and the opening intermediary server 830 may selectively include at least one of a signature, a certificate capable of verifying the signature, and a certificate chain.

In step 8007, the terminal 810 may check the reply of the opening intermediary server 830. If verification of the signature or certificate of the opening intermediary server 830 fails in response to step 8006, it is confirmed that an event does not exist, or an error is returned, the terminal 810 may end the process. In step 8007, verification of the signature and certificate of the opening intermediary server 830 was successful, an event exists in the reply of step 8006, or the event confirmation identifier provided by the terminal 810 to the opening intermediary server 830 in step 8004 is If it is confirmed that it is not valid, the terminal 810 may perform the following steps to obtain an event or update an event confirmation identifier.

The terminal 810 may transmit a request for acquiring an event related to the eSIM mounted on the terminal 810 to the opening intermediary server 830 in step 8008 of the mutual authentication process. Before transmitting the request, the eSIM may authenticate the opening intermediary server 830 . The request may optionally include at least one of the following information.

- eUICC identifier (EID)

- Event identifier (EventID or MatchingID)

- Identifier supporting the event confirmation function of the terminal 810

- eUICC signature generated with eUICC's private key

- eUICC certificate and higher certificate

- Identifier supporting the signature verification function of the opening intermediary server

Some or all of the information may be transmitted while being included in eUICC information (euiccInfo2) or terminal information (deviceInfo).

In step 8008, the opening intermediary server 830 may authenticate the eUICC by verifying the eUICC identifier, the eUICC signature, and the eUICC certificate.

In operation 8009, the opening mediation server 830 may search for a registered event corresponding to the requested eUICC identifier (EID) or eUICC identifier (EID) and the event identifier.

In step 8009, if the opening mediation server 830 supports the event confirmation function, it may generate an event confirmation identifier (ECID) corresponding to the eUICC identifier (EID). The opening intermediary server 830 may create a new event confirmation identifier or reuse the previously stored event confirmation identifier. Also, the opening intermediary server 830 may connect and store the current eUICC identifier (EID) and the event confirmation identifier (ECID).

In step 8009, the opening intermediary server 830 may set and store at least one of an issuance date, an effective period, an effective date, and a usable number of the event confirmation identifier. In addition, the event identification identifier may be invalid due to the expiration of the period or exceeding the number of uses, and in this case, a new event identifier may be created.

In step 8010, the opening mediation server 830 may return an event request response message. In this case, the event request response message may selectively include at least one or more of the following.

- Event list: Event identifier (Event ID or Matching ID) and RSP server address, event list may be empty

- Whether the event check function is supported

- event identification identifier

- Event confirmation identifier validity conditions (period, number of uses, etc.)

In step 8003 (step 8004 or step 8008), when the terminal 810 transmits that it can verify the signature of the opening intermediary server 830 through the opening intermediary server signature verification function support identifier, the opening intermediary server 830 is Part or all of the information may be signed with the private key of the opening intermediary server (830).

In step 8011 , the terminal 810 may verify when the signature of the opening mediation server 830 is included in the reply value of the opening mediation server 830 . If the verification fails, the terminal 810 may stop the process and display an error to the user (not shown). When verifying the signature of the opening intermediary server 830, the terminal 810 may optionally proceed to step 8012 if the verification is successful.

In step 8012 , the terminal 810 may store the currently returned address of the opening intermediary server 830 and the returned event confirmation identifier in the terminal 810 . In this case, the returned information may be stored in an LPA (not shown) installed in the terminal 810 or an eSIM (or eUICC, not shown) installed in the terminal 810 .

In step 8013, the terminal 810 may perform an event by accessing the RSP server (profile providing server or alternative opening intermediary server) using the returned event list information.

9 is a diagram illustrating components of a terminal according to an embodiment of the present disclosure.

As shown in FIG. 9 , the terminal 900 may include a transceiver 910 and a controller 920 . Also, the terminal 900 may include a UICC 930 . For example, the UICC 930 may be inserted into the terminal 900 , and may be an eUICC embedded in the terminal 900 .

The transceiver 910 according to various embodiments transmits and receives signals, information, data, etc. according to various embodiments of the present disclosure with the profile providing server 1000 of FIG. 10 or the opening mediation server 1100 of FIG. 11 . can

For example, the transceiver 910 according to various embodiments may transmit a first message requesting an event to the opening mediation server 1100 .

The transceiver 910 according to various embodiments may receive event related information from the opening mediation server 1100 in response to the first message.

The transceiver 910 according to various embodiments may transmit a second message requesting an event to the profile providing server 1000 based on the event related information.

For example, the opening mediation server 1100 according to various embodiments may include a first opening mediation server and a second opening mediation server.

The transceiver 910 according to various embodiments may transmit a third message for requesting an event to the second opening mediation server based on the second event related information received from the first opening mediation server.

The transceiver 910 according to various embodiments may receive the first event related information from the second opening mediation server in response to the third message.

The transceiver 910 according to various embodiments may transmit the second message requesting an event to the profile providing server 1000 based on the first event related information.

For example, the second message according to various embodiments includes at least one or more of information related to the acquisition path of the first event-related information and information related to the second opening mediation server that has returned the first event-related information. may include more.

In addition, the third message according to various embodiments further includes at least one or more of information related to the acquisition path of the second event-related information and information related to the first opening mediation server to which the second event-related information is returned. can do.

The transceiver 910 according to various embodiments may receive information related to event processing from the profile providing server 1000 in response to the second message.

For example, the information related to the event processing received from the profile providing server 1000 according to various embodiments may include information indicating an event processing failure.

According to various embodiments, information related to event processing transmitted from the profile providing server 1000 may include information related to profile installation or remote management.

The control unit 920 may include at least one or more processors, and hereinafter, the control unit may be used in combination with a processor.

The processor 920 according to various embodiments may control the overall operation of the terminal 900 . The processor 920 may control the overall operation of the terminal 900 according to various embodiments of the present disclosure as described above.

For example, at least one processor 920 according to various embodiments checks the event processing exception list, and based on the event-related information received from the opening mediation server 1100 and the event processing exception list, the event can decide whether to process

In addition, at least one processor 920 according to various embodiments controls the transceiver 910 to send the event to the profile providing server 1000 based on a determination of whether to process the event and the event related information. may transmit the second message requesting , receive information related to the event processing from the profile providing server 1000 in response to the second message, and receive the event processing-related information based on the event processing-related information The handling exception list can be updated. For example, when the information related to the event processing received from the profile providing server 1000 includes information indicating an event processing failure, the at least one processor 920 according to various embodiments includes the event processing exception list You can add the event related information to .

The UICC 930 according to various embodiments may download a profile and install the profile. Also, the UICC 930 may manage a profile.

The UICC 930 may operate under the control of the processor 920 . Alternatively, the UICC 930 may include a processor or a controller for installing a profile, or an application may be installed. A part of the application may be installed in the processor 920 .

Meanwhile, the terminal 900 may further include a memory (not shown), and may store data such as a basic program, an application program, and setting information for the operation of the terminal 900 . In addition, the memory is a flash memory type (Flash Memory Type), a hard disk type (Hard Disk Type), a multimedia card micro type (Multimedia Card Micro Type), card type memory (eg, SD or XD memory, etc.), magnetic Memory, magnetic disk, optical disk, RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), PROM (Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read- Only Memory) may include at least one storage medium. In addition, the processor 920 may perform various operations using various programs, contents, data, etc. stored in the memory.

10 is a diagram illustrating components of a profile providing server according to an embodiment of the present disclosure.

The profile providing server 1000 according to various embodiments may include a transceiver 1010 , a controller 1020 , and a memory 1030 .

The transceiver 1010 according to various embodiments may transmit and receive signals, information, data, etc. according to various embodiments of the present disclosure with the terminal 900 of FIG. 9 or the opening mediation server 1100 of FIG. 11 . . For example, the transceiver 1010 may transmit information related to profile installation or remote management to the terminal.

For example, the transceiver 1010 according to various embodiments may receive an event request message from the terminal 900 .

For example, the 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 terminal 900 from the opening brokerage server 1100. can

Meanwhile, the control unit 1020 is a component for controlling the profile providing server 1000 as a whole. The control unit 1020 may include at least one processor, and hereinafter, the control unit may be used in combination with a processor.

The processor 1020 may control the overall operation of the profile providing server 1000 according to various embodiments of the present disclosure as described above.

For example, at least one processor 1020 according to various embodiments determines the validity of the event-related information including the event request message received from the terminal 1000, and based on the validity determination of the event-related information, The transceiver 1010 may be controlled to transmit information related to event processing to the terminal.

For example, when the event-related information is valid, the event processing-related information according to various embodiments may include profile installation or remote management-related information.

In addition, when the event-related information is invalid, the event processing-related information according to various embodiments may include information indicating an event processing failure.

At least one processor 1020 according to various embodiments may control the transceiver 1010 to transmit an event deletion request message to the opening brokerage server when event processing is completed.

The event request message according to various embodiments of the present disclosure may further include at least one of information related to an acquisition path of event related information and information related to the opening mediation server 1100 .

At least one processor 1020 according to various embodiments of the present disclosure transmits an event deletion request message based on at least one of information related to the acquisition path of the event related information and information related to the opening mediation server 1100. The transceiver may be controlled to transmit to the server 1100 .

Meanwhile, the memory 1030 of the profile providing server 1000 may store data such as a basic program, an application program, and setting information for the operation of the profile providing server 1000 . In addition, the memory is a flash memory type (Flash Memory Type), a hard disk type (Hard Disk Type), a multimedia card micro type (Multimedia Card Micro Type), card type memory (eg, SD or XD memory, etc.), magnetic Memory, magnetic disk, optical disk, RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), PROM (Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read- Only Memory) may include at least one storage medium. In addition, the processor 1020 may perform various operations using various programs, contents, data, etc. stored in the memory.

11 is a diagram illustrating components of an open mediation server according to an embodiment of the present disclosure.

The opening mediation server 1100 according to various embodiments may include a transceiver 1110 , a control unit 1120 , and a memory 1130 .

The transceiver 1110 according to various embodiments may transmit and receive signals, information, data, etc. according to various embodiments of the present disclosure with the terminal 900 of FIG. 9 or the profile providing server 1000 of FIG. 10 . . For example, the transceiver 1110 may transmit event related information to the terminal. For example, the transceiver 1110 according to various embodiments may receive an event request message from the terminal.

For example, the event request message according to various embodiments may include event-related information, and the event-related information according to various embodiments may include information received by the terminal 900 from another opening intermediary server (not shown). can be based

On the other hand, the control unit 1120 is a component for generally controlling the opening mediation server (1100). The control unit 1120 may include at least one or more processors. Hereinafter, the control unit may be used in combination with a processor.

The processor 1120 may control the overall operation of the opening mediation server 1100 according to various embodiments of the present disclosure as described above.

For example, at least one processor 1120 according to various embodiments of the present disclosure may include the transceiver 1110 to receive an event registration request message from the profile providing server 1000 or another opening intermediary server (not shown) in order to register an event. ) can be controlled.

At least one processor 1120 according to various embodiments may register the event in response to an event registration request message.

The registered event according to various embodiments may be related to an event generated by the profile providing server 1000 .

For example, when the transceiver 1110 receives the event registration request message from the other open intermediary server, the registered event may be an event generated by the profile providing server.

At least one processor 1120 according to various embodiments may control the transceiver 1110 to receive an event deletion request message from the profile providing server 1000, and based on the event deletion request message, the Registered events can be deleted.

The event registration request message according to various embodiments may include information related to an event destruction time.

For example, the one or more processors 1120 according to various embodiments may delete the event based on information related to the discard time of the event.

The event registration request message according to various embodiments may include information related to an event deletion notification.

For example, at least one processor 1120 according to various embodiments may control the transceiver 1110 to notify the profile providing server 1000 of event deletion based on information related to the event deletion notification. have.

Meanwhile, the memory 1130 of the opening mediation server 1100 may store data such as a basic program, an application program, and setting information for the operation of the opening mediation server 1100 . In addition, the memory is a flash memory type (Flash Memory Type), a hard disk type (Hard Disk Type), a multimedia card micro type (Multimedia Card Micro Type), card type memory (eg, SD or XD memory, etc.), magnetic Memory, magnetic disk, optical disk, RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), PROM (Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read- Only Memory) may include at least one storage medium. In addition, the processor 1120 may perform various operations using various programs, contents, data, etc. stored in the memory.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural component, and even if the component is expressed in plural, it is composed of a singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents.

The various embodiments of the present disclosure and the terms used therein are not intended to limit the technology described in the present disclosure to a specific embodiment, but should be understood to include various modifications, equivalents, and/or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for like components. The singular expression may include the plural expression unless the context clearly dictates otherwise. In this disclosure, expressions such as "A or B", "at least one of A and/or B", "A, B or C" or "at least one of A, B and/or C", etc., refer to all of the items listed together. Possible combinations may be included. Expressions such as “first”, “second”, “first” or “second” can modify the corresponding components regardless of order or importance, and are only used to distinguish one component from another. The components are not limited. When an (eg, first) component is referred to as being “connected (functionally or communicatively)” or “connected” to another (eg, second) component, that component is It may be directly connected to the component or may be connected through another component (eg, a third component).

The term “module” used in the present disclosure includes a unit composed of hardware, software, or firmware, and may be used interchangeably with terms such as, for example, logic, logic block, component, or circuit. A module may be an integrally formed part or a minimum unit or a part of one or more functions. For example, the module may be configured as an application-specific integrated circuit (ASIC).

Various embodiments of the present disclosure are provided as software (eg, a program) including instructions stored in a machine-readable storage media (eg, an internal memory or an external memory) readable by a machine (eg, a computer). A device is a device capable of calling a command stored from a storage medium and operating according to the called command, and a terminal (eg, the first terminal 210 or the second terminal 210) according to various embodiments. ) When the instruction is executed by a processor, the processor may directly or use other components under the control of the processor to perform a function corresponding to the instruction. It may contain code generated or executed by

The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' means that the storage medium does not include a signal and is tangible, and does not distinguish that data is semi-permanently or temporarily stored in the storage medium.

Methods according to various embodiments disclosed in the present disclosure may be provided by being included in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product may be distributed in the form of a machine-readable storage medium (eg, compact disc read only memory (CD-ROM)) or online through an application store (eg, Play Store™). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server.

Each of the components (eg, a module or a program) according to various embodiments may be composed of a singular or a plurality of entities, and some sub-components of the aforementioned sub-components may be omitted, or other sub-components may be various. It may be further included in the embodiment. Alternatively or additionally, some components (eg, a module or a program) may be integrated into a single entity to perform the same or similar functions performed by each corresponding component prior to integration. According to various embodiments, operations performed by a module, program, or other component may be sequentially, parallel, repetitively or heuristically executed, or at least some operations may be executed in a different order, omitted, or other operations may be added. can

Claims (1)

A control signal processing method in a wireless communication system, comprising:
Receiving a first control signal transmitted from the base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images