GB2534920A

GB2534920A - Network subscription for a new device

Info

Publication number: GB2534920A
Application number: GB1501974.8A
Authority: GB
Inventors: Mohamed Yousri Ebrahim Ezzat Hanno Kareem; Wontner Edmund; Abdel Rahman Soliman Soliman Shadoufa Mohamed
Original assignee: Vodafone IP Licensing Ltd
Current assignee: Vodafone IP Licensing Ltd
Priority date: 2015-02-06
Filing date: 2015-02-06
Publication date: 2016-08-10
Also published as: GB201501974D0; US20180242380A1; WO2016124884A1; EP3254486A1; US11089639B2

Abstract

A method and system for initiating a network configuration for a new device and for managing devices comprises, receiving an indication that the device has connected with a subscriber network, determining the subscriber network identity and determining the first subscriber module identifier (e.g. details of SIM held within device). The device is then provided with a web landing page specific to a set of parameters including the subscriber network identity and the first subscriber module identifier, wherein the web landing page initiates network configuration for the device. This allows a network operator to tailor the configuration process for each device based on device properties, country or region etc while still providing a simple out of the box experience to the user.

Description

NETWORK SUBSCRIPTION FOR A NEW DEVICE

Field of the Invention

The present invention relates to a method and system for initiating the configuration of mobile devices so that they may subscribe to a subscriber network.

Background of the Invention

Consumer Device Manufacturers or Original Equipment Manufacturers (OEMs) who produced devices that require mobile connectivity would like to make it easier for their customers to connect to a network (e.g. the internet) shortly after acquiring the device. OEMs may distribute their devices to many different countries. One way of providing their customers with a simple "out of the box" experience is to ship devices with a traditional SIM that will immediately work in the end user's country. This requires purchasing SIMs from different companies (OpCos) specific to each country or region and so requires a prediction of how many devices will be sold in each country. This prediction can be difficult because the reaction of the market to each device may be different, especially in light of alternative options provided by competitors.

Additionally, devices may be re-shipped between countries and so the devices may contain a SIM that is not suitable for the eventual country. As a result, re-shipping devices to another country may lead to SIMs that don't work (and can result in a very negative customer experience) or require devices to be shipped back to a factory to un-pack the devices, remove the wrong SIM, install a correct SIM, pack the devices and then ship them to the new country.

This can lead to additional costs and lost time for the OEM.

One possible solution is to provide OEMs with SIMs that can work in any country and that preferably provide data services within the same price margin of the target country as a country-specific SIM (e.g. www.worldsim.com). However, this can raise a number of technical and legal challenges because of the following requirements: There are different legal requirements for consumer registration in each country; There is a legal requirement to be able to intercept communication (legal interception); There are different content filtering rules for consumers in each country; The internet break out experience in each country is different; The top-up and billing aspects of operating companies (OpCos) is different from each other so a top-up voucher 20 from one OpCo will not work in any other OpCo; and The customer care, SIM swap, and all legal and technical aspects for OpCos are built specifically to support the SIMs of that OpCo and any minor change in these systems will be very expensive and will take a lot of time to complete.

Therefore, there is required a method and system that overcomes these problems. -3 -

Summary of the Invention

Against this background there is provided a method and system that allow products or devices (e.g. tablets, e-readers, laptop computers, vehicle communication systems, home automation systems, etc.) that require network connectivity (e.g. to a subscriber network or internet connectivity over a cellular network) to be delivered to customers together with a SIN or other subscriber module.

The devices may have a subscriber identity that can switch or transform from an initial identity to a final identity (manually or automatically). This may be by swapping the subscriber module or by using a single subscriber module with a transformable identifier. When the end user powers the device for the first time (or powers on or connects a further time before subscriber identity transformation, for example) then it connects to a local subscriber network (e.g. a local cellular network). As the subscriber identity has not yet transformed then this initial connection may be a roaming connection, for example (the initial subscriber module identifier may include a subscriber network identifier different to local subscriber network that the SIM is in communication with).

The user may have previcusly connected but the process may not have completed for some reason. Therefore, the process may restart from where it left off. For example, the SIM may still have its initial identity (not yet transformed).

Upon initial connection (or reconnection before the process completes and/or with the SIM having its initial identity) the device may make a request to register the user or other indication that the device has connected with a subscriber network, access a network (e.g. the subscriber network or the internet) or request to become a subscriber of the network. Together with or within this received indication or request is included the initial or first subscriber network identifier (e.g. 'MST of the initial SIM identitifier). Other information may be included such as a unique identifier of the device (e.g. IMET).

The first subscriber network identifier may be registered within a system fcr managing devices or may be included in a range of identities provided to the system in advance. This information may be registered together with the subscriber network identity (e.g. a particular OpCo). Particular identifiers (or ranges of identifiers) may be associated with a particular web landing page (or instructions for configuring or building a web landing page). Therefore, when the indication or request is received the system can determine what particular web landing page to send to the device. Preferably, this web landing page only needs to be sent once (i.e. before transformation) to initiate network configuration of the device. Network configuration may involve different steps or processes for each OpCo (or for different countries where particular OpCos operate). These different steps may be included in the functionality of the web landing page.

For example in Spain, transformation of the subscriber identity of the device may require a physical replacement of the subscriber module or SIM. Therefore, the web landing page that matches parameters derived from the device and/or message can provide instructions to the user to visit a store to replace the SIM. In other countries the subscriber module is allowed to be transformable within the device (i.e. no replacement is needed as the device can transform the subscriber module from a first subscriber module identifier to a second subscriber module identifier) with no or few user details being required or registered. In some countries the user's name or other specific details are required or registered before this transformation is allowed.

Therefore, the web landing page can be configured to meet specific local requirements that match the subscriber network (and/or country) where the device will operate.

According to a first aspect there is provided a method 10 and system for initiating a network configuration for a device, the method comprising the steps of: receiving from a device an indication that the device has connected with, request to access, register with and/or become a subscriber of a subscriber network; determining the subscriber network identity; determining a first (or only) subscriber module identifier; providing the device with a web landing page specific to a set of parameters including the subscriber network identity and the first subscriber module identifier, wherein the web landing page initiates network configuration for the device. Therefore, one web landing page can be customised or made for a particular device that uses a first subscriber module identifier (or group cf devices with a particular set of first subscriber module identifiers) and particular subscriber network. Therefore, the network configuration can be tailored for a particular device type, network where the device will operate, and/or country of operation. This can aid usability of the device and simplify the set-up procedure. This can be further beneficial before subscriber identity transformation as the registration procedure may operate whilst the device is effectively roaming and a simplified set-up will require less data or time on a roaming network. Initiating the network configuration may start a procedure for configuring the device to access the network and may also proceed to complete the configuration enabling network access. Providing access to the subscriber network and network configuration may comprise registering the device and/or user with the subscriber network. The indication received from the device may be an explicit or implicit request to become a subscriber. For example, the request may take the form of a brief signal or message that the device has been initiated and connected to the network (communicate with a network base station) for the first time, at a time before registration as a subscriber to the network has taken place and/cr before transformation of the subscriber identity (e.g. SIN identity).

Preferably, the subscriber network access request or indication of connection is received over that same subscriber network. The subscriber network identity may be determined from the carrier details. The subscriber network identity may be determined from the subscriber module of the device. If the indication or request was made over a different network then access may be denied (or registration may fail).

Optionally, the method may further comprise the step of determining a unique device identifier, wherein the set of parameters further includes the unique device identifier and/or the country of the subscriber network. In other words, the particular web landing page may be matched against device id (or determined to fall within a range of device ids), device id (or determined to fall within a range of device ids), first subscriber module identifier (or determined to fall within a range of first subscriber module identifiers) and subscriber network (that the device is connected to). An advantage of checking the device id is that this can also be used tc prevent a user for taking the subscriber module identifier (e.g. SIM) from the supplied device and installing it in another device (perhaps to take advantage of a low data rate tariff). When the device id doesn't match any stored id or range of ids then an error message may replace the web landing page (or a web landing page is provided that prevents configuration of the device 10 with the network or prevents registration, for example).

Preferably, the provided web landing page may indicate an action to be taken by a user to transform the subscriber identity from the first subscriber module identifier to the 15 second subscriber module identifier.

Optionally, the device may have a subscriber identity transformable from the first subscriber module identifier to a second subscriber module identifier. The connection is initiated with the first subscriber module identifier. Therefore, at this stage the device is effectively roaming and so not yet a subscriber to the network over. However, this at least provides connectivity to provide the web landing page and subsequent subscription and/or registration.

Preferably, the method may further comprise the step of subscribing the device to the subscriber network by transforming the subscriber identity from the first subscriber module identifier to the second subscriber module identifier, wherein the second subscriber module identifier belongs to (or contains an identifier of) the subscriber network.

Optionally, the indicated action may be replacement of a subscriber module. In other words, the web landing page may prompt the user to physically change or swap their subscriber module (e.g. SIM). This may be done by themselves or within a store (the user may be prompted to visit a store). In a store environment the store may carry out identity and other checks and register the user and/or device, for example.

Optionally, the subscriber identity of the device may be stored within a subscriber module that has a transformable subscriber module identifier. This may be a transformable subscriber module (e.g. SIM) that stores more than one identifier.

Optionally, initiating the network configuration of the device may further comprise the step of transforming the subscriber module identifier within the subscriber module from the first subscriber module identifier to the second subscriber module identifier. The subscriber module may receive a signal or command to transform whilst remaining installed within the device. This may be part of a registration process (with the subscriber network) or separate from this process. No physical replacement of the subscriber module (e.g. SIM) is required in this embodiment.

Optionally, the method may further comprise the step of preventing the web landing page from being provided to the device if the subscriber module identifier has transformed from the first subscriber module identifier to the second subscriber module identifier. Therefore, a check can be made to confirm that the transformation hasn't taken place before the web landing page is provided. This check can be made at any point but preferably directly after the indication or request to subscribe to the network is received.

Preferably, the provided web landing page may provide any one or more of: a user registration facility to access the network; functionality to transform a subscriber module identity of the device from the first subscriber module identifier to the second subscriber module identifier; pricing information for accessing the network; information in a language specific to a country of the first subscriber network; instructions for configuring the device to subscribe to the subscriber network; and logic to configure the device to subscribe to the subscriber network. The web landing page may include other information or functionality. Preferably, the web landing 20 page is displayed on a browser of the device.

Preferably, the step of providing the device with a web landing page may further comprise the steps of configuring the web landing page by modifying a template landing page.

This simplifies the building of the page. However, different versions of the web landing page may be stored and selected instead.

Preferably, configuring the web landing page may further comprise the step of determining a set of configuration instructions. Scripts, configuration files, database parameters or other elements may form the configuration instructions, for example.

-10 -Optionally, the set of configuration instructions may be selected based on the first subscriber module identifier falling within a range of subscriber module identifiers.

Preferably, the subscriber module identifier of the device may be an IMSI. Other identifiers may be used.

Preferably, the method may further comprise the step of 10 registering the device with an operating company of the subscriber network. The use may also be registered with the device.

Preferably, the device may be registered with the 15 operating company via the landing page. This may be achieved over the internet, for example.

Preferably, the web landing page initiates or enables access to the internet over the subscriber network.

The method described above may be implemented as a system (computer, network, server or group of computers) that implement the method or any described variation in the method.

According to a second aspect there is provided a system for managing a plurality of devices (preferably, each device having a subscriber identity transformable from a first subscriber module identifier to a second subscriber module 30 identifier), the system comprising logic configured to: receive data defining one or more first subscriber module identifiers; store a set of one or more parameters including the data defining the one or more first subscriber module identifiers and a subscriber network identity; receive a configuration of a web landing page; and associate the configuration of the web landing page with the stored set of one or more parameters. This system may provide an interface for receiving the data and a data store for saving the data, parameters, web landing page(s) and configurations. The configuration of the web landing page may be used to configure one or more template landing pages or may be multiple versions (with different attributes) of web landing pages themselves, for example.

Preferably, the logic may be further configured to: receive data defining one or more device identifiers and the stored set of parameters may further include the data defining the one or more device identifiers.

Advantageously, the logic may be further configured to: receive from a device an indication that the device has connected with to subscribe to or otherwise access a subscriber network, wherein the device has a first subscriber module identifier; match details of the received indication including at 25 least the subscriber network and the first subscriber module identifier of the device with the stored set of parameters; and serve a web landing page to the device configured according to a configuration associated with the matched set of parameters. The indication or request may be an explicit or implicit request to access the network. For example, it may be a message or communication received from the device including data or information about the device where the -12 -response is the web landing page configured to match the parameters. The indication cr request may include other data or information (e.g. user registration details). The indication or request may be carried by a radio access network (RAN), for example.

Preferably, the details of the received indication to be matched with the stored set of parameters may further include a device identifier (e.g. IMEI, WiFi identifier, MAC 10 address, etc).

Optionally, the logic may be further configured to transform the subscriber module identifier within a subscriber module of the device from the first subscriber module identifier to the seccnd subscriber module identifier. The transformation may be achieved directly or indirectly from the logic (e.g. the device carries out the transformation prompted by the logic).

Preferably, the logic may be further configured to register the device using the web landing page. Some subscriber networks or countries require that successful registration must occur before the transformation can take place.

Preferably, the configuration of the web landing page may be a set of customisation settings for a template web landing page. Alternatively, separate complete stored landing pages may be selected and served. In other words, the initialisation of the network configuration and/or the network configuration procedure itself may be customised by providing a specific web landing page to the device dependent on its particular paramaters.

-13 -According to a third aspect, there is provided a method for managing a plurality of devices (preferably, each device having a subscriber identity transformable from a first subscriber module identifier to a second subscriber module identifier), the method comprising the steps of: receiving data defining one or more first subscriber module identifiers; storing a set of one or more parameters including the 10 data defining the one or more first subscriber module identifiers and a subscriber network identity; receiving a configuration of a web landing page; and associating the configuration of the web landing page with the stored set of one or more parameters.

Optionally, the method way further comprise the steps of: receiving from a device an indication that the device has connected with or made a request to subscribe to a subscriber network, wherein the device has a first subscriber module identifier; matching details of the indication or request including at least the subscriber network and the first subscriber module identifier of the device with the stored set of parameters; and serving a web landing page to the device configured according to a configuration associated with the matched set of parameters.

The methods described above may be implemented as a computer program comprising program instructions to operate a computer. The computer program may be stored on a computer-readable medium.

-14 -The computer system may include a processor such as a central processing unit (CPU). The processor may execute logic in the form of a software program. The computer system may include a memory including volatile and non-volatile storage medium. A computer-readable medium may be included to store the logic or program instructions. The different parts of the system may be connected using a network (e.g. wireless networks and wired networks). The computer system may include one or more interfaces. The computer system may contain a suitable operating system such as UNIX, Windows (RTM) or Linux, for example.

It should be noted that any feature described above may 15 be used with any particular aspect or embodiment of the invention.

Brief description of the Figures

The present invention may be put into practice in a number of ways and embodiments will now be described by way of example only and with reference to the accompanying drawings, in which: FIG. 1 shows a flowchart of a method for initiating a 25 network configuration for a device; FIG. 2 shows a flowchart of a method for managing a plurality of devices; FIG. 3 shows a schematic diagram of a system for managing a plurality of devices, given by way of example 30 only; FIG. 4 shows a sequence diagram of a method for providing a device with a web landing page, according to an example; -15 -FIG. 5 shows a sequence diagram of a portion of the method of figure 4 in further detail; and FIG. 6 shows a screen-shot of an example web landing page.

It should be noted that the figures are illustrated for simplicity and are not necessarily drawn to scale. Like features are provided with the same reference numerals.

Detailed description of the preferred embodiments

List of abbreviations UE User Equipment which is the device RAN Radio Access Network SGSN Serving GPRS Support Node (this node normally belongs to the OpCo where the SIM is located) GGSN Gateway GPRS Support Node (this node normally belongs to a coordinating OpCo such as Vodafone) API Application Programming Interface MSP Multiservice Proxy GLP Global Landing Page PDCP Packet Data Convergence Protocol RANAP Radio Access Network Application Part Figure 1 shows a flowchart (at a high level) of a method 10 for initiating a network configuration for a device. At step 20 a message is received that requests access to the network. This message may be received over a Radio Access Network (RAN) operated by a subscriber network (e.g. an operating company or OpCo). Whilst figure 1 shows a request being made at step 20, this may also be an indication that the device has connected to the network. At step 30 a first subscriber mcdule identifier is determined. This is an initial identity cr identifier (e.g. number) of a -16 -subscriber module that is transformable from a first identity to a second identity. In this example, the subscriber module is a SIM.

The subscriber network identity (or OpCo) over which the request is received is determined at step 40. At step 50 the device is provided with a web landing page that is specific to the combination of the determined subscriber module identifier (initial identity) and the determined subscriber network identity. Other parameters may also be matched to provide a specific web landing page for that combination. The web landing page may be presented on a screen of the device in a brcwser or in another form. The web landing page initiates network configuration of the device.

Figure 2 shows a flowchart of a method 200 for managing a plurality of devices. In particular, managing the plurality of device involves setting up configurations of devices or providing facilities for configuring those devices, to access a network such as the internet. At step 210 data is received describing the first or initial subscriber module identifier. This may be a single identifier, a range of identifiers, or a plurality of separate identifiers, for example. At step 220 these subscriber module identifier(s) and a subscriber network identity are included in a set of parameters that are stored.

At step 230 a configuration of a web landing page is received. This is associated with the particular stored set of parameters at step 240. In other words, particular web landing page configurations are stored or associated with -17 -particular parameters that include at least one or more first subscriber module identifiers and a subscriber network identity (over which a request to access a network is received according to method 10).

Figure 3 shows a schematic diagram of a system 100 for implementing method 200. One or more devices 110 each include a SIM 120 that is transferable from a first subscriber module identifier (ID1) to a second subscriber module identifier (ID2). Each of these IDs in their separate SIMs 120 are different and unique. When a device 110 having a subscriber module identifier before transformation is first powered on and connects to a subscriber network 130 then this device 110 sends a request to access a network such as the internet. This request is received by a server 140 which may be a simple out of the box experience (SOBS) control engine (SCE) 140. The SCE 140 may also contain or be in communication with a database for storing parameters and configuration parameters for web landing pages described with reference to figure 2.

A user or operator within in an OpCo may add SIM identifiers 160, configuration details for web landing pages and templates for the web landing page 180 as a data input 190, which may be stored in the database 150. This same system 100 may then be used to process requests to access the network according to the method 10 described with reference to figure 1.

The SCE 140 has the ability to integrate multiple Operating Companies (OpCos) and at the same time and the ability to integrate to multiple SIM transformation -18 -services, which allow SIMs 120 to transform from using one OpCo (e.g. a Global OpCo) to another OpCo (e.g. local OpCo).

Once the configuration cf the device 110 has been initiated then the SIM transformation may take place. Transforming the SIM from a global to a local SIM allows the ruse of the local OpCo legal interception, content filtering, support and billing systems in this way provides a more consistent user experience, customizable per OpCo and 10 per device, with the same tariff options, across different SIM assets which may belong to different OpCos.

Different operating companies may also specify their own marketing or technical messages in their own language to 15 the customer using the global and local SIM attributes together in a single platform.

The following describes at a high level the various triggers that occur within the process for initiating the 20 network connection.

1. When the SIMs (e.g. machine-to-machine SIMs) are manufactured, the SIM manufacturer produces a return file, which is sent to a provisioning system of GDSP so that the SIMs may be pre-provisioned cn a group HLR. This allows the network elements to be ready for the new group SIMs so that they accept a connection from the device whenever the device tries to establish a connection. Furthermore, a target local SIM (i.e. the SIM after transformation) may be pre-provisioned on the target HLRs of the local OpCo.

2. When a customer buys a device, turns it on, and decide to view connection options, they will click on a button in a browser (this is the trigger to establish the Packet Switching Connection which connects to the RAN), and -19 -retrieve a first page of the GLP. The first page of the GLP allows the customer to see an available offer or plan. The particular offer or plan that is waiting for the customer may depend on a particular commercial proposition specific to the device and SIM and also on the country where the customer is currently located (or local OpCo).

3. If the customer wishes to proceed with the offer and configure their device accordingly, then they may be required to follow legal steps of registering on the GLP (this may be different for each country). Once registration is completed (or any other local requirements), the SCE may allocate a target local SIM for the customer and may display the information about the target local SIM that is allocated to the customer on the GLP (i.e. completing registration may be a trigger an allocating of the destination/target local SIM).

4. The final page on the GLP may display the SIM information, has a button to start the SIM transformation (the actual text displayed tc the customer may be 'activate', for example). Once the customer clicks on the activate' button, then SCE will send an API call to G&W to start the actual SIM transformation (so the customer clicking on that button is the trigger to start SIM transformation process). The SIM transformation process may include C&D sending multiple binary messages to the device, which will activate a client on the SIM that is responsible for transforming the SIM. Once the SIM is transformed, it will be able to connect to the local network using the destination/target local SIM because the local destination SIMs were pre-provisioned as part of step 1.

Therefore, accepting the offer leads the customer to be prompted for and/or provide the registration details, assigns a local target SIM and initiates SIM transformation.

-20 -Figure 4 shows a sequence diagram of an example method leading to the display of the web landing page on the device. The following steps occur: 1. End user presses the power button and the UE begins to power on; 2. UE is switched on and requests the pin code of the of SOBE SIM card (GDSP SIM); 3. End user inserts pin code; 4. UE opens browser and starts a new data connection to the RAN, over PDCP; 5. RAN sends the user data tc the selected SGSN, over RANAP (the user data in this example is the standard set of attributes required to establish a packet switching connection in GSM); 6. SGSN uses the SOBE APN and selects the 90128 GGSN as the gateway. This triggers the PEP context activation and an IP is assigned to the GDSP SIM; 7. The 90128 GGSN sends a RADIUS Accounting-Request to the MSP, which is acting as an AAA accounting server. The RADIUS accounting traffic includes the IP of the device, the IMSI (GDSP SIM) and IMEI which allows the SCE to identify the correct commercial proposition or parameters associated with the connecting device so that the correct web landing page is generated or selected; 8. MSP fetches the information for header enrichment from the GDSP, using a SOAP interface. To fetch the information, the MSP uses the IP address that was received Accounting-Request message of the RADIUS interface. In this step, MSP may get more information about the device (including the OpCo which the SIM is connecting from, and this information -21 -is used later on in step 15) from GDSP and may send this information to a web or global landing page generator (GLP); 9. SGSN sends user data to the 90128 GGSN, using the assigned IP address as source IP address; 10. User data reaches the MSP; 11. MSP checks if the destination URL of the incoming HIT? request is white listed. Since the device has recently opened the browser, then the URL might be www.***.com, www.apple.com or something similar (depends on the device), for example. The Database of whitelisted URLs is maintained in MSP and is configured by the operational teams; 12. MSP sets the destination URL to the GLP; 13. Depending on configuration, the MSP platform may strip the HTTP request of some headers; 14. Depending on configuration, the MSP platform may do header enrichment using the information that is stored in the local database for the incoming IP address; 15. MSP sends the HTTP traffic to the GLP; 16. A global landing pages is returned; and 20 17. The global or web landing page is displayed in the UE.

The association between the user-experience (or response to the request) to be provided to a specific SIM and the actual traffic happens at run time when the customer traffic actually reaches the GLP. This relies on the configuration of the SCE 140. The configuration of the SCE 140 can happen as early as required in the process by specifying the product name and the countries where the product will work, and then a batch of Group SIMs may be 30 added or stored (this is possible once the group SIMs are manufactured and sent to the OEM). The device identifiers (e.g. IMEIs) may be added to the SCE 140 (once the devices are manufactured, and ideally before shipping the devices -22 -from the factory). All configurations can happen well in advance of the devices becoming available in the market, which reduces the need to implement manual activities when the devices arrive to the shops.

SCE 140 captures the information about where the device is connecting from in the database 150 and is able to detect when the customer switches country (e.g. the subscriber identity module transforms) in the middle of a registration process. The first and second subscriber identity module may include network and/or country identifiers that may be different pre and post transformation.

Displaying the web landing page (Step 16 in the above 15 sequence) relies on the SCE 140. In one example implementation, further functions of the SCE 140 may include: An http request coming in from the MSP, may be mapped to an intercepting servlet, which may in turn forward it to a controller, which may retrieves any or all information such as IMSI, IMEI, ICCID, etc. from the request, and construct DeviceDetails (shown in figure 5). DeviceDetails may then be used as a parameter to getNextPage() call to SCE 140.

In this example, this may be done in GLPServlet as follows: DeviceDetails deviceDetails = new DeviceDetails(); deviceDetails.setDevicelMEl(request.getHeader("imei")); deviceDetails.setSimIMSI(request.getHeader("imsi")); deviceDetails.setServing0pcoId(request.getHeader("Servingopco-id")); -23 -deviceDetails.setServing0pcoCode(request.getHeader("Servingopco-code")); Various jsp pages in the GLP may be loaded dynamically, 5 based on the user requested actions. This may follow the sequence shown in figure 5.

The MSP may also provide a white-listing feature which allows backend services on the devices to reach its target and the customer does NOT see the results of these backend services. For example, Device X may send a message to its servers to check if the device is stolen or not, and the SCE 140 may allow this traffic tc work normally by white-listing the target IP on MSP.

The above interactions preferably occur before SIM transformation (while the SIM is still a GDSP SIM -ID1). Once SIM transformation happens, the SIM becomes a local SIM (ID2) and will go to the local OpCo landing page directly like other normal OpCo SIMs, without passing through the above process or the SCE 140.

Figure 6 shows a screen shot of an example web landing page. This figure highlights features that may be customised including text, images, data tariffs, buttons and functions.

As will be appreciated by the skilled person, details of the above embodiment may be varied without departing from 30 the scope of the present invention, as defined by the appended claims.

For example, other parameters may be included when matching a web landing page or configuring a web landing -24 -page. Instead of registering the pre-transform subscriber module identifier (SIM ID), the post-transformation subscriber module identifier (or range of post-transform identifiers) may be used as the stored parameters or to determine and serve the web landing page (or otherwise configure the web landing page). The web landing page may have different offers for different devices and/or OpCos. For example, the different offers may include any one or more of free data for a pericd of time (e.g. one week), a specific data quota (e.g. 100MB per month), pricing plan for data (e.g. £1/LOMB), etc. Many combinations, modifications, or alterations to the features of the above embodiments will be readily apparent to the skilled person and are intended to form part of the invention. Any of the features described specifically relating to one embodiment or example may be used in any other embodiment by making the appropriate changes.

Claims

-25 -CLAIMS: 1. A method for initiating a network configuration for a device, the method comprising the steps of: receiving from a device an indication that the device has connected with a subscriber network; determining the subscriber network identity; determining a first subscriber module identifier; providing the device with a web landing page specific to a set of parameters including the subscriber network identity and the first subscriber module identifier, wherein the web landing page initiates network configuration for the device.
2. The method of claim 1, wherein the indication is received over the subscriber network.
3. The method of claim 1 or claim 2 further comprising the step of determining a unique device identifier, wherein the 20 set of parameters further includes the unique device identifier and/or the country of the subscriber network.
4. The method according to any previous claim, wherein the device has a subscriber identity transformable from the first subscriber module identifier to a second subscriber module identifier.
5. The method of claim 4 further comprising the step of subscribing the device to the subscriber network by transforming the subscriber identity from the first subscriber module identifier to the second subscriber module identifier, wherein the second subscriber module identifier belongs to the subscriber network.

-26 -
6. The method according to claim 4 or claim 5, wherein the provided web landing page indicates an action to be taken by a user to transform the subscriber identity from the first subscriber module identifier to the second subscriber module identifier.
7. The method of claim 6, wherein the indicated action is replacement of a subscriber module.
8. The method of claim 4 or claim 5, wherein the subscriber identity of the device is stored within a subscriber module that has a transformable subscriber module identifier.
9. The method of claim 8, wherein initiating the network configuration of the device further comprises the step of transforming the subscriber module identifier within the subscriber module from the first subscriber module identifier to the second subscriber module identifier.
10. The method according to any of claims 4 to 9 further comprising the step of preventing the web landing page from being provided to the device if the subscriber module identifier has transformed from the first subscriber module identifier to the second subscriber module identifier.
11. The method according to any previous claim wherein the provided web landing page provides any one or more of: a user registration facility to access the network; functionality to transform a subscriber module identity of the device from the first subscriber module identifier to a second subscriber module identifier; -27 -pricing information for accessing the network; information in a language specific to a country of the first subscriber network; instructions for configuring the device to subscribe to 5 the subscriber network; and logic to configure the device to subscribe to the subscriber network.
12. The method according to any previous claim, wherein the 10 step of providing the device with a web landing page further comprises the steps of configuring the web landing page by modifying a template landing page.
13. The method of claim 12, wherein configuring the web landing page further comprises the step of determining a set 15 of configuration instructions.
14. The method of claim 13, wherein the set of configuration instructions is selected based on the first subscriber module identifier falling within a range of 20 subscriber module identifiers.
15. The method according to any previous claim, wherein the subscriber module identifier of the device is an IMSI.
16. The method according to any previous claim further comprising the step of registering the device with an operating company of the subscriber network.
17. The method of claim 16, wherein the device is registered with the operating company via the landing page.

-28 -
18. The method according to any previous claim, wherein the web landing page enables access to the internet over the subscriber network.
19. A system for managing a plurality of devices, the system comprising logic configured to: receive data defining one or more first subscriber module identifiers; store a set of one or more parameters including the 10 data defining the one or more first subscriber module identifiers and a subscriber network identity; receive a configuration of a web landing page; and associate the configuration of the web landing page with the stored set of one or more parameters.
20. The system of claim 19, wherein each device has a subscriber identity transformable from a first subscriber module identifier to a second subscriber module identifier.
21. The system of claim 19 cr claim 20, wherein the logic is further configured to: receive data defining one or more device identifiers and the stored set of parameters further includes the data defining the one or more device identifiers.
22. The system according to any of claims 19 to 21, wherein the logic is further configured to: receive from a device an indication that the device has connected with a subscriber network, wherein the device has 30 a first subscriber module identifier; match details of the received indication including at least the subscriber network and the first subscriber module -29 -identifier of the device with the stored set of parameters; and serve a web landing page to the device configured according to a configuration associated with the matched set 5 of parameters.
23. The method of claim 22, wherein the details of the received indication to be matched with the stored set of parameters further include a device identifier.
24. The system according to any of claims 19 to 23, wherein the logic is further configured to transform a subscriber module identifier within a subscriber module of the device from the first subscriber module identifier to the second subscriber module identifier.
25. The system according to any of claims 19 to 24, wherein the logic is further configured to register the device using the web landing page.
26. The system according to any of claims 19 to 25, wherein the configuration of the web landing page is a set of customisation settings for a template web landing page.
27. A method for managing a plurality of devices comprising the steps of: receiving data defining one or more first subscriber module identifiers; storing a set of one or more parameters including the 30 data defining the one or more first subscriber module identifiers and a subscriber network identity; receiving a configuration of a web landing page; and -30 -associating the configuration of the web landing page with the stored set of one or more parameters.
28. The method of claim 27 further comprising the steps of: receiving from a device an indication that the device has connected with a subscriber network, wherein the device has a first subscriber module identifier; matching details of the received indication including at least the subscriber network and the first subscriber 10 module identifier of the device with the stored set of parameters; and serving a web landing page to the device configured according to a configuration associated with the matched set of parameters.