CN112040503B

CN112040503B - Network configuration equipment and corresponding network configuration method thereof

Info

Publication number: CN112040503B
Application number: CN202010911591.3A
Authority: CN
Inventors: 艾哈迈德·法瑞斯; 穆罕默德·阿里·马哈伊德利
Original assignee: Seli Technology Co ltd
Current assignee: Seli Technology Co ltd
Priority date: 2020-09-02
Filing date: 2020-09-02
Publication date: 2024-04-05
Anticipated expiration: 2040-09-02
Also published as: CN112040503A

Abstract

In a network configuration scheme provided in some embodiments of the present application, a network device may obtain a configuration request about the configuration element, where the configuration request includes a configuration validation time, select a first configuration file associated with identification information of a mobile network operator, then bind the first configuration file to the configuration element corresponding to the configuration request, and mark the configuration validation time to create a second configuration file. Because the corresponding effective time can be set when the first configuration file and the configuration element are bound, a user can send a configuration request in advance to bind before the effective time is configured, so that the creation of the second configuration file is completed, and the service corresponding to the second configuration file is activated when the second configuration file is needed to be used, thereby improving the efficiency.

Description

Network configuration equipment and corresponding network configuration method thereof

Technical Field

The present disclosure relates to the field of information technologies, and in particular, to a network configuration device and a corresponding network configuration method.

Background

Various types of electronic devices are capable of accepting a remote SIM configuration, RSP (Remote SIM Provisioning). The SIM is a subscriber identity module (Subscriber Identity Module), and generally, the specific implementation of the SIM may be any type of configuration element (such as a removable SIM, an embedded SIM, a system on a chip, etc.) on any type of device (such as a smart phone, a wearable device, a tablet computer, an automobile, an unmanned aerial vehicle, an electric appliance, etc.). Based on the SIM, such devices may request and/or accept remote SIM configuration to authenticate and activate services (e.g., mobile data subscription) of the wireless/mobile network (e.g., 3G, EVDO, 4G/LTE, 5G, etc.). Subscribers and users of such services are able to select and purchase connection services or service packages through RSP.

Fig. 1A shows a prior art SM-dp+ based architecture suitable for providing RSP services to consumer devices using embedded SIM ("eSIM") functionality, where the SIM is embedded in the device, or integrated SIM ("ikim") functionality, where the SIM card is integrated directly into the microprocessor of the device, e.g., qualcomm snapdragon 855. Such functions have been defined and standardized by the GSM association ("GSMA"). The present disclosure applies equally to eSIM and ikvi technologies. Thus, eSIM and iksim will be used interchangeably herein. For more information on architecture, systems and procedures for providing RSP services, see specifications of GSMA, e.g., sgp.01 (v.4.0), sgp.11 (v.4.0), sgp.02 (v.4.0), sgp.05 (v.1.1), sgp.21 (v.2.2), sgp.22 (v.2.2.1), sgp.23 (v.1.5), sgp.25 (v.1.0), incorporated by reference in its entirety.

The prior art RSPSM-dp+ based architecture includes a mobile network operator 110A, a subscription manager data preparation + server (SM-dp+) 120A, which is intended for consumer/end user devices 130A, which devices 130A are equipped with configuration elements, such as an embedded/integrated universal integrated circuit card (eUICC/uicc) 140A, and operated by end user 150A. Also shown is RSP subscription manager discovery service (SM-DS) 160A.

RSP uses such architecture, which is mainly provided by mobile network operators (Mobile Network Operator, MNO). In other words, the user may subscribe to and obtain a local connection service, which is provided by a locally available mobile network operator or configuration and provision. To use the RSP architecture with eSIM/eisim enabled devices, operators typically utilize a subscription manager data preparation+ (SM-dp+) module (for consumer esims, illustrated in fig. 1A) to securely configure eSIM devices that are going to consume connection services.

Fig. 2 shows certain functional blocks of the exemplary SM-dp+120a of fig. 1A. Such SM-dp+ functional blocks include: profile package generation 210, profile package protection, profile package binding 230, profile package storage 240, profile package delivery 250, and SM-DS event registration 260. Such SM-dp+ (and similarly SM-DP) may utilize identification information associated with the mobile network operator, such as IMSI, ICCID, authentication key, and/or profile/service description, etc., in order to obtain the first profile. The first configuration information generated thereby is associated with identification information of the mobile network operator, which first configuration files can be used for identifying subscribers of the network service. The first profile may be generated by SM-dp+ or operator/MNO. For example, a Mobile Virtual Network Operator (MVNO) may request SM-dp+ to generate a batch of profiles using a set of IMSIs assigned by MNOs. In case an MNO is used, such a profile can be prepared and shared with SM-dp+ through the ES2+ interface.

The first profile, once available on SM-dp+, can be bound and downloaded to a configuration element (eUICC/eUICC) of the mobile device requesting mobile services. For example, when the provisioning element is an embedded universal integrated circuit card (eUICC), such as eUICC140A of fig. 1A or eUICC140B of fig. 1B. The eUICC has one unique identification information, i.e., EUICC Identification (EID), whereby each eUICC is associated with one EID in a one-to-one correspondence that can be used to identify the different euiccs.

Once bound to a particular EID, the first profile is equivalent to binding a particular eUICC, and a second profile can be generated that is only for a particular eUICC with a particular EID.

The second profile, once downloaded to the eUICC, may be referred to as an "eSIM" for the collection. Once the configuration file is downloaded, the eSIM may enter a disabled or enabled state. Typically, the second configuration is downloaded while the eSIM is activated and billing begins according to the service usage. Even if a device user (e.g., end user 150A of fig. 1A) or a machine in an M2M application turns off an eSIM, a corresponding fee is typically incurred.

In some cases, an end user/subscriber of a device may utilize one or more subscription manager discovery services (e.g., SM-DS160A of fig. 1A) to select from different connection subscriptions/packages provided by different local operators. As shown in fig. 1A, these various home operators are associated with a particular SM-dp+. Once the end user selects a service or package, the package or first profile corresponding to the service is bound to the provisioning element via the associated SM-dp+ and downloaded to the provisioning element (e.g., UICC).

As can be seen from the above, the current RSP architecture has the following problems:

1. the user is limited to selecting a service or package from the mobile network in which the user is currently located to activate content subscribed to in the mobile network in which the user is currently located;

2. the user device has requested a network connection (e.g., over Wi-Fi or other mobile connection) to be able to select and download a second profile to activate eSIM-based mobile subscription; otherwise, the operator must have an advanced configuration system that allows the user to access the restricted mobile internet in order to select and download the second configuration file;

3. usage meter Fei Tong for subscribed services or packages often begins when (or shortly after) the second profile download is complete. The user cannot select a second profile that activates the subscription at some future time.

Today, over 10 billion international passengers cross over the country, moving between different mobile networks/operators, this number also does not include machines, and international passengers and machines need to connect to smart devices (e.g., smartphones, notebook computers, tablet computers, wearable devices that increasingly employ eSIM functionality). Most of these passengers will shut down mobile data roaming for expensive costs. The reason for the increased cost is that "roaming" typically involves payment to three parties, including home networks, visited networks, and transit networks.

At least due to the RSP architecture and protocols described above, international traveler discovery has difficulty in understanding current network connection services in the destination country (often more affordable than roaming). For example, the user may not use the RSP architecture and protocols described above until the destination country is actually present, and can acquire the accessed SM-DS/SM-dp+ to purchase packages/subscriptions and download the second profile needed for service configuration, which affects the network connection of travel (or cross-network travel), reducing efficiency.

In fact, due to these limitations, when a passenger arrives outside the network ("roaming") area (e.g., a foreign airport), the device providing the service may be lacking to view local traffic, e.g., carpooling and/or use other basic applications such as maps or text messages. Due to other inconveniences, the user needs to provide new all user identification details (e.g. name, email, etc.) and other information previously provided, such as information provided to the international travel/reservation platform when booking air tickets and/or booking hotels on the network. This, of course, can lead to redundancy, inconvenience and inefficiency in the user's interfacing transactions.

Based on the above deficiencies, travelers need to acquire mobile data services before being within range of a particular mobile network. In addition, mobile network operators also need to provide improved short-term data services (e.g., MVNOs) on the network that are associated with mobile visitors (e.g., passengers).

Disclosure of Invention

An object of the present application is to provide a network configuration device and a corresponding network configuration method thereof.

To achieve the above object, some embodiments of the present application provide a network configuration apparatus, including:

the interaction module is used for acquiring a configuration request about the configuration element, wherein the configuration request comprises configuration effective time;

the configuration file management module is used for selecting a first configuration file associated with the identification information of the mobile network operator;

and the binding module is used for binding the first configuration file with the configuration element corresponding to the configuration request, marking the configuration effective time and creating a second configuration file.

Further, the profile management module is configured to maintain a profile list, where the profile list includes a first profile associated with identification information of a mobile network operator; and selecting a first available profile associated with the identification information of the mobile network operator from the profile list.

Further, the profile management module is further configured to, after creating the second profile, mark the first profile corresponding to the second profile as unavailable within the configuration validation time.

Further, the interaction module is configured to obtain a configuration request about a configuration element of a mobile device when the configuration element is out of a range of a mobile network provided by a mobile network operator, where a configuration validation time included in the configuration request is an expected time period when the configuration element is in the range of the mobile network.

Further, the interaction module is further configured to determine, through an activation request about the bound configuration element, a second configuration file that should provide a service; and communicating with the mobile network operator, and activating the network service corresponding to the second configuration file of the service to be provided.

Further, the interaction module is further configured to determine, through a shutdown request regarding the bound configuration element, a second configuration file in which the service should be shutdown; and stopping the network service corresponding to the second configuration file of the service to be deactivated by communicating with the mobile network operator, and releasing the binding relationship between the first configuration file corresponding to the second configuration file and the configuration element.

Further, the interaction module is further configured to notify a user of the second configuration file that is in a binding relationship; and downloading the invalid second configuration file to the configuration element corresponding to the second configuration file with the unbinding relation.

Further, the configuration element is an embedded universal integrated circuit card or an integrated universal integrated circuit card.

Further, the network configuration device is a configuration management server comprising a service provider server in communication with the SM-dp+, or the configuration management server is integrated in the SM-dp+.

Further, the network configuration device is a configuration management server comprising a service provider server in communication with the SM-DP, or the configuration management server is integrated in the SM-DP.

Based on another aspect of the present application, there is also provided a network configuration method, including:

acquiring a configuration request about the configuration element, wherein the configuration request comprises configuration effective time;

selecting a first configuration file associated with identification information of a mobile network operator;

binding the first configuration file with the configuration element corresponding to the configuration request, marking the configuration effective time, and creating a second configuration file.

Further, the method further comprises:

maintaining a configuration file list, wherein the configuration file list comprises a first configuration file associated with identification information of a mobile network operator;

Selecting a first profile associated with identification information of a mobile network operator, comprising:

and selecting an available first configuration file associated with the identification information of the mobile network operator from the configuration file list.

Further, after creating the second configuration file, the method further includes:

and marking the first configuration file corresponding to the second configuration file as unavailable in the configuration effective time.

Further, obtaining a configuration request for the configuration element includes:

a configuration request about a configuration element of a mobile device is obtained when the configuration element is outside the range of a mobile network provided by a mobile network operator, wherein the configuration validation time included in the configuration request is an expected time period when the configuration element is within the range of the mobile network.

Further, the method further comprises:

determining a second profile that should provide the service by an activation request with respect to the bound configuration element;

and communicating with the mobile network operator, and activating the network service corresponding to the second configuration file of the service to be provided.

Further, the method further comprises:

determining a second profile for which the service should be deactivated by a request for deactivation of the bound configuration element;

And stopping the network service corresponding to the second configuration file of the service to be deactivated by communicating with the mobile network operator, and releasing the binding relationship between the first configuration file corresponding to the second configuration file and the configuration element.

Further, the method further comprises:

notifying a user of the second configuration file with the unbinding relation, and downloading the invalid second configuration file to a configuration element corresponding to the second configuration file with the unbinding relation.

Further, the network device performing the method is a configuration management server comprising a service provider server in communication with the SM-dp+, or the configuration management server is integrated in the SM-dp+.

Further, the network device performing the method is a configuration management server comprising a service provider server in communication with the SM-DP, or the configuration management server is integrated in the SM-DP.

In a network configuration scheme provided in some embodiments of the present application, a network device may obtain a configuration request about the configuration element, where the configuration request includes a configuration validation time, select a first configuration file associated with identification information of a mobile network operator, then bind the first configuration file to the configuration element corresponding to the configuration request, and mark the configuration validation time to create a second configuration file. Because the corresponding effective time can be set when the first configuration file and the configuration element are bound, the user can send the configuration request in advance to bind before the effective time is configured, thereby completing the creation of the second configuration file, and activating the service corresponding to the second configuration file when the second configuration file is needed to be used.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:

fig. 1A is a block diagram of a prior art SM-dp+ based architecture suitable for configuring data services to eSIM and/or eisim devices;

fig. 1B is a block diagram of a prior art SM-DP based architecture suitable for configuring data services to eSIM and/or iksim devices;

figure 2 is a block diagram of certain functional blocks of the exemplary SM-DP +120A of figure 1A.

Fig. 3 is a flow chart of a method for remotely acquiring mobile data services of an eSIM and/or eisim enabled mobile device outside the range of a mobile network in accordance with some embodiments of the present invention;

FIG. 4 is a flow chart of a method of enabling data functions on a mobile device that has or is acquiring data services of a remote network, according to some embodiments of the invention;

fig. 5A is a block diagram of an improvement over a prior art SM-dp+ based architecture adapted to remotely configure data services from a provisioned mobile network to eSIM and/or ikim devices, according to some embodiments of the present invention;

fig. 5B is a block diagram of an improvement over a prior art SM-dp+ based architecture adapted to remotely configure data services from a provisioned mobile network to eSIM and/or ikim devices, according to some embodiments of the present invention;

Fig. 5C is a block diagram of an improvement over a prior art SM-DP based architecture adapted to remotely configure data services from a provisioned mobile network to eSIM and/or ikim devices, according to some embodiments of the present invention;

fig. 5D is a block diagram of an improvement over the prior art SM-DP based architecture adapted to remotely configure data services from a provisioned mobile network to an eSIM and/or an ikim device;

fig. 6 is a block diagram of certain components of SM-dp++ suitable for configuring data services remotely from a provided mobile network to esims and/or iksim devices in accordance with certain embodiments of the present invention;

FIG. 7 illustrates a manner in which ARSP-based systems manage protected profiles and bound profiles, according to some embodiments of the invention.

FIG. 8 illustrates a manner in which a prior art RSP-based system manages protected profiles and bound profiles;

FIG. 9 is a flowchart of a method for managing protected and bound configuration files in SM-DP++ using data service request information according to some embodiments of the invention;

FIG. 10 is a flowchart of a method of managing activation and deactivation of a bound profile between SP-DP++ and a mobile network in an ARSP architecture according to some embodiments of the present invention;

The same or similar reference numbers in the drawings refer to the same or similar parts.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Some embodiments of the present application provide a network configuration device that includes an interaction module, a profile management module, and a binding module. The interaction module is used for acquiring a configuration request about the configuration element, wherein the configuration request comprises configuration effective time; the configuration file management module is used for selecting a first configuration file associated with the identification information of the mobile network operator; and the binding module is used for binding the first configuration file with the configuration element corresponding to the configuration request, marking the configuration effective time and creating a second configuration file.

In some embodiments of the present application, the profile management module is configured to maintain a profile list, where the profile list includes a first profile associated with identification information of a mobile network operator; and selecting a first available profile associated with the identification information of the mobile network operator from the profile list.

In some embodiments of the present application, the profile management module is further configured to, after creating the second profile, mark the first profile corresponding to the second profile as unavailable within the configuration validation time. Conversely, the first configuration file may be in a usable state beyond the configuration validation time, for example, the configuration validation time is yyyyy year MM month DD day 00: MM month DD day 23 from 00 to YYYY year: 59, the first configuration file is not available for the configuration validation time, if the configuration validation time in the other configuration request coincides with the bound configuration validation time, such as YYYY year MM month DD day 13: MM month DD day 17 from 00 to YYYY year: 59, the first configuration file cannot be bound to the configuration element corresponding to another configuration request.

In some embodiments of the present application, the interaction module is configured to obtain a configuration request about a configuration element of a mobile device when the configuration element is out of a range of a mobile network provided by a mobile network operator, where a configuration validation time included in the configuration request is an expected time period when the configuration element is in the range of the mobile network.

In some embodiments of the present application, the interaction module is further configured to determine, through an activation request regarding the bound configuration element, a second configuration file that should provide the service; and communicating with the mobile network operator, and activating the network service corresponding to the second configuration file of the service to be provided. The second configuration file may be downloaded to the configuration element of the mobile device in advance before activation, and activated after a certain time after the completion of the downloading, or may be activated while the downloading is performed.

In some embodiments of the present application, the interaction module is further configured to determine, by a shutdown request regarding the bound configuration element, a second configuration file for which the service should be shutdown; and stopping the network service corresponding to the second configuration file of the service to be deactivated by communicating with the mobile network operator, and releasing the binding relationship between the first configuration file corresponding to the second configuration file and the configuration element.

In some embodiments of the present application, the interaction module is further configured to notify a user of the second configuration file that is in a binding relationship; and downloading the invalid second configuration file to the configuration element corresponding to the second configuration file with the unbinding relation.

In some embodiments of the present application, the configuration element is an embedded universal integrated circuit card or an integrated universal integrated circuit card.

In some embodiments of the present application, the network configuration device is a configuration management server comprising a service provider server in communication with SM-dp+, or the configuration management server is integrated in SM-dp+.

In some embodiments of the present application, the network configuration device is a configuration management server, the configuration management server comprising a service provider server in communication with the SM-DP, or the configuration management server is integrated in the SM-DP.

In addition, some embodiments of the present application further provide a network configuration method, where the method includes:

In some embodiments of the present application, the method further comprises:

In some embodiments of the present application, after creating the second configuration file, further comprising:

In some embodiments of the present application, obtaining a configuration request for the configuration element includes:

In some embodiments of the present application, the method further comprises:

In some embodiments of the present application, the network device performing the method is a configuration management server, which comprises a service provider server in communication with SM-dp+, or which is integrated in SM-dp+.

In some embodiments of the present application, the network device performing the method is a configuration management server, the configuration management server comprising a service provider server in communication with the SM-DP, or the configuration management server is integrated in the SM-DP

The solution described in the embodiments of the present application may also be a novel platform comprising devices and methods enabling advanced remote SIM configuration (Advanced Remote SIM Provisioning, ARSP). The ARSP can provide advanced protection for open subscription and metering/closed (e.g., limited, short-time, or disposable) connectivity services for eSIM-enabled devices or machines. For example, such connection services may be purchased or subscribed to in advance from a local or foreign network operator, the acquired services may be activated immediately, or the services may be activated at some predetermined/unset time in the future.

For example, a person traveling abroad may purchase a mobile connection in advance (e.g., during a travel reservation phase) for use with their own device (e.g., mobile phone, tablet, notebook, hotspot, etc.) before preparing to go abroad. The service may be activated at the arrival time/date of the selected journey. It is desirable that passengers using different international networks be able to conveniently "subscribe" and pre-configure their device connections before actually locating/acquiring the destination network, unlike the RSP architecture and protocols of the prior art described above. The manner of booking mobile services is the same as other travel services (e.g., flights, hotels, trains, travel insurance, etc.) (booking times, booking tools are the same).

Similarly, any user/machine may simply connect in advance and/or connect on demand only for a particular period of time (e.g., 1 week, 1 month, 1 year) as needed, or another period of time set by the user/machine with particular start and end dates. Certain embodiments of the present invention effectively facilitate configuration of mobile services based on existing systems and protocols while also minimizing consumption of network resources and configuration of files.

The ARSP devices and methods described herein may also be applied to other devices and machines (e.g., networked automobiles, drones, tools, etc.) to connect to a network (if no other network is connected), or to connect to a different (e.g., international) network. This function is particularly suited for short-term travel or non-periodic travel. This allows planning in advance to obtain local/visited network connections at affordable prices without the need to make tedious plans or use expensive international roaming services.

Generally, an ARSP may acquire and connect to configure different devices, and an international traveler/user needs to perform the following operations:

1-look ahead of available connectivity services for eSIM enabled devices in other countries/networks. This may be done either while booking a trip or before connecting to the network.

2-select, subscribe to and/or purchase related connection packages/subscriptions for travel, e.g. mobile data services with upper or unlimited set, the duration may be a predetermined period of time (e.g. 1 week, 1 month) or an exact duration, the arrival Time (TA) may be set as the service start time and the departure Time (TD) as the end time. The process is similar to the way other international travel services (e.g., flights and hotels) are acquired. In some cases, the user may choose whether to take the expense and/or reschedule the program when purchasing the service.

3-download the binding profile of the acquired packages/subscriptions and possess an equivalent travel eSIM for automatic/seamless activation on the fly, configuring the device with travel eSIM functionality (e.g., using QR codes or other similar links, or using applications with necessary rights) to seamlessly connect to the accessed network on the fly.

4-access to the network after arrival at the destination, a travel eSIM is selected (typically using a one-click/selection on the device) to obtain a local connection.

Fig. 3 illustrates an exemplary method of acquiring mobile data services for an eSIM enabled mobile device according to some embodiments of the present invention. In some embodiments, the method may be used to remotely acquire mobile data services outside the range of the mobile network provided. The method of fig. 3 may be performed as part of a typical travel reservation process or other process in which the user has entered identifying information (e.g., name, address, credit card). In step 310, the user accesses a website through a URL using a browser (or similar tool) or uses a mobile application, etc., as a configuration application. The configuration application may be used on the mobile device that is acquiring the data.

In step 320, the application or website may receive an indication that may indicate whether the mobile device that is acquiring the data service is using the configuration application.

In step 330, a configuration application, background service, or script is used to determine whether the mobile device that is acquiring data is eSIM capable. For example, if a mobile device that is acquiring data is using a configuration application, the configuration application may use an API by querying the operating system (e.g., iOS, android) of the mobile device, or by processor instructions to determine if the mobile device has eSIM functionality. In some embodiments, the configuration application may determine whether the mobile device has eSIM functionality by detecting whether an eSIM application is present on the mobile device. In some embodiments, an identifier (e.g., IMEI, model, FCCID, make/model) of the mobile device that is acquiring data may be used to determine whether the mobile device is eSIM capable. For example, if a configuration application is used on a mobile device that is acquiring data, the configuration application may determine the identifier by querying the operating system, using an API, or by processor instructions. In some embodiments, the user may be required to enter the appropriate identifier, for example, if the mobile device that is acquiring the data is not using a configuration application, or if the program determination is unsuccessful.

In step 340, the configuration application presents the user with a packet option. In some embodiments, the data package option is presented only after determining that the mobile device that is acquiring data has eSIM functionality. In some embodiments, the previously booked or concurrently booked travel packages have associated arrival time "TA" and/or departure time "TD" and location information, and the received data is part of the previously booked or concurrently booked travel packages, and based on the received data, the data packet options that the application will present are configured to correspond to one or more mobile networks to be encountered. In some embodiments, the configuration application receives information from a user. For example, if a united states resident is booking european trips in the united kingdom, france, and spanish, data packets corresponding to one or more mobile networks in these countries may be presented for each mobile network to be accessed (e.g., country/region based) within the respective time range (between arrival time TA and departure time TD).

In step 350, the user may select one or more of the presented data packet options, which may be received and/or stored by the configuration application. In some embodiments, the packet options include, for example, travel information (e.g., TA, TD, stay range), service level (e.g., LTE,3G, etc.), service duration (e.g., days, weeks, months), and/or service data volume (1 GB, 40GB, unlimited).

In step 360, the user may provide user identification information (e.g., name, email, credit card, cell phone number) to the configuration application. In some embodiments, the user information is part of a travel package that is reserved in advance or reserved at the time, which may be received/transmitted by the configuration application.

In step 370, the data service request may be sent to a service provider (e.g., "SP" with SM-dp++ functionality, as discussed in detail in fig. 4, 5A-5D, 6, 7, and 9-10). In some embodiments, the transmitted data service request is associated with a secure element. In some embodiments, the data service request is sent when a secure element associated with the data service request is outside the range of a provided mobile network associated with the SP. In some embodiments, the data service request may be sent to the service provider through a configuration application. In some embodiments, the data service request may be sent to the service provider through a server (e.g., a web server) in communication with the configuration application. In certain embodiments, the data service request may include any selected data packet option (e.g., step 350 of fig. 3) and/or travel information (e.g., location, TA, TD, stay range, etc.) (e.g., step 350 of fig. 3) and/or user identification information (e.g., step 360 of fig. 3), and/or a unique identifier (e.g., eUICC) associated with the secure element.

In step 380 (e.g., in response to step 370), the user can receive an activation code (e.g., QR code or URL) from the service provider for configuring the eSIM device. For example, the user may receive an email, SMS, etc. containing an activation code. In some embodiments, an application (e.g., a configuration application) receives an activation code.

Fig. 4 illustrates an exemplary method for enabling data functionality on a mobile device that has/is acquiring remote network data services, according to some embodiments of the invention.

In step 410, the mobile device that is/has acquired the data service may process the activation code (e.g., the activation code received in step 370 of the method of fig. 3). For example, as known in the art, a mobile device that has/is acquiring data services may open a link or process a QR code, downloading an eSIM profile (i.e., the aforementioned second profile) to the mobile device. In some embodiments, the eSIM profile remains inactive at the mobile network operator and is later activated when needed (see, e.g., fig. 10).

In step 420, a previously downloaded eSIM profile (e.g., the profile downloaded in step 410) can be selected on the mobile device. In some embodiments, the eSIM profile is selected on the mobile device after the user enters the roaming network range. In certain embodiments, eSIM profiles are automatically selected based on stored data (e.g., TA, TD, mobile network information) contained in the configuration application. In some embodiments, the automatic selection is based on a comparison with the current state of the mobile device (e.g., roaming, current date/time).

In step 430, the mobile device consumes data related to the obtained data service. The passenger can conveniently "subscribe" or "pre-purchase" and configure the connection of his own device(s) by applying the principles described herein, if a different international network needs to be acquired, before actually locating/acquiring the destination network(s). This may be done simultaneously and/or using the same tools used to book other travel services (e.g., flights, hotels, trains, travel insurance, etc.). For example, a user of a travel reservation website (e.g., expedia) may reserve a certain itinerary, and may add a connection service through the site display (or reset) that may supplement or be part of other travel service bundles. Since the user will determine the date of the trip and provide the customer ID, payment information, location of the trip, etc., such data in the itinerary may be used/extracted to obtain mobile services of the ARSP system. In some embodiments, an application, background service, or script (e.g., executed by a browser) may detect that the associated device has eUICC/eSIM compatibility/functionality. In the event that eUICC/eSIM compatibility/functionality is detected, a mobile service bundle can be provided as described above. In some other cases, the user may be queried as to whether they have compatible devices (e.g., by selecting from a list of known devices). In other cases, if the user does not determine his own device (or the device is different from the device used for subscription), a link may be sent and opened on the desired device to check and confirm its compatibility. After confirming device compatibility, the user may be provided with the option to purchase mobile services.

While the foregoing describes certain use cases (e.g., regarding connection purchases prior to travel), it should be understood that other use cases are also contemplated and are possible (e.g., obtaining intermittent connection service for a particular device or machine within a local network or any other network) without departing from the spirit of the present invention. Certain exemplary embodiments of the present invention are further shown and discussed below, with the understanding that other variations are possible.

The ARSP is capable of dynamically scheduling and assigning a first profile of limited time via advanced SM-dp+ devices and methods, referred to herein as "SM-dp++". SM-dp++ can be deployed efficiently and integrated with existing RSP systems and mobile networks. Figures 5A-5D illustrate four exemplary architectural embodiments for enhancing SM-DP/SM-dp+ techniques. These enhancements are referred to herein as "SM-dp++". Such SM-dp++ architecture is capable of configuring mobile data services (e.g., items 510A-510D in fig. 5A-5D) to devices outside the communication range of the provided mobile network.

Figures 5A and 5B illustrate exemplary architectures for upgrading SM-dp+ based systems, respectively, according to some embodiments of the present invention. On the other hand, fig. 5C and 5D illustrate exemplary architectures for upgrading SM-DP based systems, respectively, according to some embodiments of the present invention. The embodiments in fig. 5A and 5C show enhanced SM-dp++ (item 580A in fig. 5A or item 580C in fig. 5C) enhanced by a "service provider server" or item 570A "sps" in fig. 5A or item 570C in fig. 5C, 570C interfacing with existing SM-dp++ (item 520A) in fig. 5A or SM-DP (item 590C) in fig. 5C. As illustrated in fig. 6, 7, and 9-10, the SPS may enable advanced functions related to profile package scheduling and allocation. In addition to the services provided by the network operator (MNO), these embodiments may also relate to mobile services provided by third party service providers. Such service providers may be referred to as mobile virtual network operators ("MVNOs"). For example, a service provider ("SP") may be an MVNO that owns/controls a service provider server ("SPs") and interacts with an MNO through a standard API. SPS may also interact with a user (mobile device) through an escp interface (interaction may be achieved in a variety of ways: website and/or mobile station/application/store, QR code, SMS, API provided to a third party, etc.).

Alternatively, referring to fig. 5B and 5D, SM-dp++ (item 580B in fig. 5B or item 580D in fig. 5D) may also take the form of an integrated system (e.g., a server) including a service provider server (item 570A in fig. 5A or item 570C in fig. 5C) and SM-dp+ function (item 120A in fig. 1A) or SM-DP function (item 190B in fig. 1B) in one entity.

In this case the mobile network operator will interact directly with the end user. As with the SPS embodiments of fig. 5A and 5C, these integrated SM-dp++ embodiments may enable high-level functions related to profile package scheduling and allocation, as described in fig. 6, 7, and 9-10.

Figure 6 illustrates exemplary functional components of SM-dp++ (e.g., items 580A-D in figures 5A-D) according to some embodiments of the present invention. Here, SM-dp++ functionality is mainly provided by the profile package scheduling and distribution module (item 670 in fig. 6). SM-dp++ may be hardware-based, software-based, non-transitory computer-readable medium-based, and/or include a mixture of hardware, software, and/or non-transitory computer-readable medium elements. As described above, the profile and package scheduling and distribution module may alternatively be incorporated into the SPS (e.g., as shown in fig. 5A or 5C) as part of the SM-dp+ (e.g., as shown in fig. 5B), or as part of the SM-DP (e.g., as shown in fig. 5D).

To utilize the SM-dp++ functionality added above, an international traveler/roamer may perform the procedure described with respect to fig. 3 above. The SM-dp++ function can implement such "advanced" connection subscription and configuration by mapping the first configuration file (which is a valuable resource typically configured for regular long-term subscribers) not only to EIDs (such as SM-dp+ of the prior art) but also to service expiration dates for future connection to external/remote networks. The service expiration date may be derived from a travel itinerary containing a specific date and/or Time of Arrival (TA) and Time of Departure (TD). Alternatively, the service expiration date may be a predetermined period of time, such as 1 week, 1 month, or 1 year, before or after a certain date.

FIG. 7 illustrates a manner in which SM-DP++ technology enables a single first profile (710A) to be used as two separate second profiles (740A, 740B) when associated with information from one or more non-overlapping data service requests (730A, 730B) and one or more secure elements (e.g., UICID 720A or 720B), in accordance with some embodiments of the invention. The data service request information may be travel information such as TA/TD discussed above. The SM-dp++ technology of fig. 7 versus the prior art SM-dp+/SM-DP functionality of fig. 8 has shown that the SM-dp++ technology requires two separate first profiles (810A, 810B) and two different secure element IDs (e.g., eUICCID820A, 820B) in order to generate two separate second profiles (840A, 840B).

Figure 7 shows a comparison of a high-level mapping of SM-dp++ based on scheduling, which may be provided by a profile and package scheduling assignment module, with a high-level mapping of SM-DP/SM-dp+ of the prior art, which lacks the profile and package scheduling module functionality. The advanced SM-dp++ mapping provided by the profile and package scheduling assignment module enables efficient scheduling of valuable mobile network/service resources (i.e., the first profile) to be utilized by many secure elements (e.g., eUICC with multiple EIDs) and, correspondingly, many users. These users may access the same mobile network during non-overlapping time periods. Thus, SM-dp++ may enable sharing and reuse of the first profile, making short-term connectivity services more viable for both MNOs (or MVNOs) and international passengers/users. Typically, more than 94% of short-term users take up to 2 weeks on a trip to a country such as the united states. The SM-dp++ dispatch and first profile "reclamation" functions also facilitate any other/local devices (e.g., wearable devices) that require short-term, intermittent connectivity services rather than regular subscriptions that are typically long-term.

Figure 9 illustrates an exemplary method for implementing certain SM-dp++ functions (e.g., as the profile package scheduling assignment module of figure 6) according to certain embodiments of the present invention. The method of fig. 9 may be used in accordance with any of the architectures described with respect to fig. 5A-5D. In general, to prevent the same first profile from becoming multiple second profiles at the same time, the SP-dp++ function may associate the guideline of the first profile stored/generated/available on SM-dp++ with the expected service expiration/use time (e.g., TA-TD). Thus, SM-dp++ can manage the first profile and the second profile using the received data service request information.

In step 910, a set of first profiles is generated, which are assigned to Service Providers (SPs). The set of first profiles may be generated by the mobile network operator or by using resources provided by the MNO (e.g. by existing SM-dp+ or SM-DP).

In step 920, the SP may receive a set of first profiles (e.g., the first profiles generated in step 910).

In step 930, a service provider (e.g., at the SPS, such as item 570A in fig. 5A or item 570C in fig. 5C) may create and maintain a list of first profiles (e.g., the first profiles received in step 920). In some embodiments, unique guidance information is used to maintain a list of first profiles, e.g., indicators similar to: profile ID, international mobile equipment identity ("IMEI") or other unique information identifying the handset/device, integrated circuit card identifier ("ICCID") or other information associated with the SIM or secure element, international mobile subscriber identity ("IMSI") or other account identifying information, authentication key or other cryptographic information. In some embodiments, a list of first profiles is maintained without storing sensitive profile information, such as an IMSI or authentication key.

In step 940, the SP may receive a data service request. In some embodiments, the data service request is associated with a secure element (e.g., eUICC/uicc). In some embodiments, the data service request may include or specify a valid service period for which the secure element is within range of a particular mobile network operator or other information (see, e.g., step 370 of fig. 3).

In step 950, the SP (e.g., via SPs or integrated SM-dp++) may identify either the unassigned first profile (the first profile that is not associated with any data service request) or the second profile in its maintained list of first profiles, and cannot simultaneously assign the first profile using the information in the received data service request (the "open" second profile). For example, the SP may search the second profile list to identify at least one second profile that is unassigned within a valid service period (e.g., TA/TD) specified by the data service request.

If an open second profile or unassigned first profile is not found, the SP may request one or more new first profiles (e.g., from the mobile network operator) and add any received first profiles to the maintenance list of the first profiles as unassigned first profiles in step 960.

In step 970, when an open second profile or unassigned first profile is identified (e.g., in step 950 or 960), the first profile can be associated with information in the data service request (e.g., a valid service period, such as TA/TD). In the case where the first profile is unassigned, the unassigned first profile will become the second profile. In the case where the second profile is open, the instant data service request will be further associated with the second profile, while any previous data service request information is associated with the second profile.

In step 980 (e.g., in response to receiving the data service request and in response to associating the second profile with the data service request, as in step 940), the SP may send an activation code (e.g., via SPs or integrated SM-dp++) (e.g., step 380 of fig. 3).

Figure 10 illustrates an exemplary method for implementing certain SM-dp++ functions (e.g., as a profile and package scheduling module, see figure 6) according to certain embodiments of the present invention. The method of fig. 10 may be used in accordance with any of the architectures described with respect to fig. 5A-5D and in accordance with the methods of fig. 3, 4, 9. Methods may be used to manage activation and deactivation of a second profile between SM-dp++ and the mobile network of the ARSP architecture. Generally, the SP manages the second profile together with the mobile operator based on the data service request information associated with the second profile (see fig. 9). At a specified time (e.g., TA) at the beginning of the active service period, the mobile network operator can be contacted to activate the eSIM and its second profile. The second profile may be communicated with the mobile network operator through an API. For example, the SPS, application, etc. may contact the mobile network operator through an API provided by the mobile network operator to activate the services of the second profile. Similarly, in some embodiments, at a specified end time of the active service period (e.g., TD), the mobile network operator may be contacted (e.g., through an API provided) to deactivate the eSIM and its second profile. In some embodiments, before disabling, a notification is sent to notify the user that disabling is imminent and/or to allow the user to renew the service.

In step 1010, an eSIM profile can be sent (downloaded) to a device of the user (e.g., via an esip interface), for example, in response to the user processing the activation code (e.g., step 380 of fig. 3 or step 980 of fig. 9). To process the activation code, the user may, for example, scan a QR code or click on a link.

In step 1020, the SP (e.g., via SPs or integrated SM-dp++) may identify any second profile in the maintenance list (or second profile list) of the first profiles that should be serviced. For example, the SP may identify any second profile having data service information (e.g., service expiration, such as TA) corresponding to the current date/time.

In step 1030, the SP, in response to identifying any second profiles that should provide services, may notify the mobile network operator (e.g., through an operator API) to activate the services of the corresponding second profiles.

In step 1040, the SP (e.g., via SPs or integrated SM-dp++) may identify any second profile in the first profile maintenance list (or second profile list) for which the service is due. For example, the SP may identify any second profile having data service information (e.g., service expiration date, such as TD) corresponding to the current date/time.

In step 1050, the SP may notify the user (e.g., via text message, email, phone) of any such expired (or impending expired) service in response to the second profile identifying such service(s).

In step 1060, the SP, in response to identifying any such second profiles for which the service expires, may inform the mobile network operator (e.g., via the operator API) to deactivate the service of the corresponding expired second profile. Although steps may generally be performed in any order, it is preferable to perform step 1050 before step 1060 (when step 1050 is performed/if step 1050 is performed) to better ensure that messages of service expiration are delivered to the user.

In step 1070, to avoid using two identical first profiles simultaneously on the network, the SP (e.g., via SPs or integrated SM-dp++) can download/store a special or "invalid" eSIM/eisim profile to a secure element (e.g., eUICC/iiicc) associated with the expired second profile to replace, deactivate, or delete the previously valid second profile upon expiration of the determined lifetime/allocation of the associated profile (e.g., service validity period). In some embodiments, an application (on a mobile device associated with the secure element) with the appropriate rights replaces a previously valid second profile, or disables or deletes such a profile. Replacement of a previously active second profile with an inactive profile may use SM-DP/SM-dp+ or a simulation thereof, and may utilize over-the-air functions (or a simulation thereof) (e.g., similar to functions available in SM-DP/SM-dp+) to send an instruction to deactivate/delete to the secure element (or second profile) remotely/locally upon expiration of the service. In some embodiments, the secure element (e.g., eSIM/UICC) itself (e.g., an application stored via a SIM) triggers (e.g., upon expiration of a service) the downloading/storing of the invalid configuration file, or an application having access to the secure element (e.g., an application stored or executed on the same device as the UICC/eSIM/ikim) may also trigger the downloading/storing of the invalid configuration file.

In step 1080, the SP, in response to identifying the second profile for any such service expiration, may disassociate the second profile from the corresponding data service information or otherwise delete/remove the corresponding data service information. The second profile may be returned as the unassigned first profile if no corresponding data service information associated with the second profile remains.

While there have been shown and described various novel features of the invention as applied to specific embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the devices and methods described and illustrated may be made. The objects of the present invention can be achieved by those skilled in the art without departing from the spirit of the present invention. Based on the foregoing disclosure and an understanding of the teachings of the present invention, those skilled in the art will recognize that the particular hardware and software processes, as well as the general functions provided and incorporated herein as part of the foregoing drawings and corresponding description, may vary in different embodiments of the present invention. Indeed, the embodiments described in this disclosure may be combined in a variety of ways. Any aspect or feature described for one embodiment may be incorporated into any other embodiment mentioned in this disclosure. Moreover, any of the embodiments described herein may be hardware-based, software-based, non-transitory computer-readable media, and/or a mixture comprising hardware, software, and/or non-transitory computer-readable media elements. Accordingly, the particular system components and processes shown and/or discussed above are for illustrative purposes to facilitate a thorough understanding and appreciation of various aspects and functions of the particular embodiments of the present invention implemented in the apparatus and method embodiments thereof. Those skilled in the art will appreciate that the invention can be practiced by other than the described embodiments, which are presented for purposes of illustration and not of limitation.

Claims

1. A network configuration device, wherein the device comprises:

the interaction module is used for acquiring a configuration request about a configuration element, wherein the configuration request comprises configuration effective time, and the configuration element is an embedded universal integrated circuit card or an integrated universal integrated circuit card;

2. The device of claim 1, wherein the profile management module is configured to maintain a profile list, the profile list including a first profile associated with identification information of a mobile network operator; and selecting a first available profile associated with the identification information of the mobile network operator from the profile list.

3. The device of claim 2, wherein the profile management module is further configured to, after creating a second profile, mark a first profile corresponding to the second profile as unavailable for the configuration validation time.

4. The device of claim 1, wherein the interaction module is configured to obtain a configuration request for a configuration element of a mobile device issued when the configuration element is outside a range of a mobile network provided by a mobile network operator, the configuration request including a configuration validation time that is an expected time period for the configuration element to be within the range of the mobile network.

5. The device of any of claims 1 to 4, wherein the interaction module is further configured to determine, by an activation request for a bound configuration element, a second configuration file that should provide a service; and communicating with the mobile network operator, and activating the network service corresponding to the second configuration file of the service to be provided.

6. The device of any of claims 1 to 4, wherein the interaction module is further configured to determine, by a shutdown request with respect to the bound configuration element, a second profile for which services should be shutdown; and stopping the network service corresponding to the second configuration file of the service to be deactivated by communicating with the mobile network operator, and releasing the binding relationship between the first configuration file corresponding to the second configuration file and the configuration element.

7. The device of claim 6, wherein the interaction module is further configured to notify a user of the unbind second profile; and downloading the invalid second configuration file to the configuration element corresponding to the second configuration file with the unbinding relation.

8. The device of claim 1, wherein the network configuration device is a configuration management server comprising a service provider server in communication with SM-dp+, or the configuration management server is integrated in SM-dp+.

9. The device of claim 1, wherein the network configuration device is a configuration management server comprising a service provider server in communication with the SM-DP or integrated in the SM-DP.

10. A network configuration method, wherein the method comprises:

acquiring a configuration request about a configuration element, wherein the configuration request comprises configuration effective time, and the configuration element is an embedded universal integrated circuit card or an integrated universal integrated circuit card;

11. The method of claim 10, wherein the method further comprises:

12. The method of claim 11, wherein after creating the second configuration file, further comprising:

13. The method of claim 11, wherein obtaining a configuration request for a configuration element comprises:

14. The method of any one of claims 10 to 13, wherein the method further comprises:

15. The method of any one of claims 10 to 13, wherein the method further comprises:

16. The method of claim 15, wherein the method further comprises:

17. The method of claim 10, wherein the network device performing the method is a configuration management server comprising a service provider server in communication with SM-dp+, or the configuration management server is integrated in SM-dp+.

18. The method of claim 10, wherein the network device performing the method is a configuration management server comprising a service provider server in communication with the SM-DP or integrated in the SM-DP.