English:
[0001] Machine-to-machine communications are ever increasingly becoming a part of modern life. In this regard, machines such as intelligent cars, global positioning satellite (GPS) devices, smart utility power meters, etc., are examples of machines that communicate with other machines in everyday life. Many of these machine-to-machine communications rely on communications over a cellular network. A telephony number may therefore be assigned to such a machine, regardless of whether the machine ever actually uses the network.
[0003] Fig. 2 is a flow chart depicting a technique to assign a telephony number to a mobile telephony device and provision a telephony network based on this assignment according to an example implementation.
[0004] Fig. 3 is a schematic diagram of a Global System for Mobile communications (GSM) mobile application part (MAP) and associated network components according to an example implementation.
[0005] Fig. 4 is a flow chart depicting a technique to initialize the telephony network of Fig. 3 prior to a mobile telephony device attaching to the telephony network according to an example implementation.
[0006] Fig. 5 is a flow chart depicting a technique performed by a workflow manager of the MAP of Fig. 3 in response to a mobile telephony device attaching to the telephony network according to an example implementation.
[0007] Fig. 6 is a flow chart depicting an allocation performed by the workflow manager of the MAP of Fig. 3 according to an example implementation.
[0008] Fig. 7 is a flow chart depicting a technique performed by the workflow manager of the MAP of Fig. 3 to provision the telephony network according to an example implementation.
[0009] Fig. 8 is a flow chart depicting a technique performed by the workflow manager of the MAP of Fig. 3 to handover a newly attached mobile telephony device to the telephony network and recycle the telephony number assigned to the mobile telephony device when the device detaches from the network according to an example implementation.
[0010] Referring to Fig. 1, in accordance with example implementations, one or multiple mobile telephony devices 114 (herein called the "mobile devices 114") may use a telephony/Internet protocol (IP) network 170 (herein called the "telephony network 170") for purposes of communicating voice and/or data with processor-based machines as well as other mobile and landline-based telephony devices.
[0011] For the non-limiting examples that are disclosed herein, the telephony network 170 may be a Global System for Mobile communications (GSM) network; and as non-limiting examples, the mobile devices 114 may be any of a number of different end telephony devices that use the telephony network 170 for voice and/or data communications, such as handheld personal wireless communication devices (smartphones, cellular telephones and so forth) that include human- operated user interfaces (touchscreens, keypads, etc.); modems that are connected to processor-based machines, such as portable or desktop computers; cellular access points; communication modules (GSM modules, as a non-limiting example) that are employed by, in general, any machine (processor-based machines, for example) for purposes of effecting machine-to-machine communications or machine-to-human communications; and so forth. As non-limiting examples, machines that may use the mobile devices 114 include motor vehicles (that include various diagnostic sensors, for example); global positioning satellite (GPS) devices; smart utility power meters; sensors; etc. Moreover, a given mobile device 114 may or may not have voice capabilities, depending on the particular implementation.
[0012] Although mobile devices are discussed below, the techniques and systems that are disclosed herein may likewise apply to any electronic device (a network printer, for example) that uses a telephony network for purposes of data and/or voice communications.
[0014] Traditionally, a SIM card may be pre -provisioned with a telephony number, such as a mobile subscriber integrated services digital network (MSISDN) number, for example, before the SIM card 115 is used for the first time. The MSISDN number identifies a subscription for using the telephony network 170. The MSISDN is traditionally the dialable, or routable, number that is dialed by another telephony device to reach the corresponding subscriber for purposes of voice channel communications. Traditionally, the MSISDN number is a fifteen digit number which has three components to direct the routing of a call: a country code; a number planning area or national destination code; and a subscriber identification.
[0015] MSISDN numbers are increasingly becoming scarce resources, especially in view of the ever increasing number of machine-based telephony devices that are being manufactured and are being assigned MSISDN numbers. A conventional GSM subscriber provisioning model involves associating a given set of IMSI numbers with a corresponding set of MSISDN numbers such that these MSISDN numbers are provisioned into the GSM network before the SIM cards having the IMSI numbers are distributed in the retail channel. This traditional provisioning model therefore allocates one MISIDN number per IMSI number, even if the associated SIM card is never used (i.e., even if the associated mobile device 114 never attaches to a telephony network).
[0016] In accordance with example implementations that are disclosed herein, the number of MSISDN numbers allocated for the mobile devices 114 may be significantly smaller than the number of mobile devices 114, as the MSISDN numbers are assigned from a pool of recycled/recyclable MSISDN numbers. Therefore, mobile devices 114 that actually use the telephony network 170 are assigned MSISDN numbers from this pool; and MSISDN numbers of mobile devices 114 that were once using but are no longer using the telephony network 170 return to the pool for assignment to other mobile devices 114.
[0017] Therefore, the number of MSISDN numbers that are allocated for the mobile devices 114 is kept relatively small to preserve the MSISDN resources. Thus, due to the recycling of the MSISDN numbers, a relatively limited number of MSIDSN numbers are used, while allowing the mobile devices 114 to benefit from basic cellular functionalities, such as authentication, authorization, billing, traceability, roaming and geolocalization. Thus, the mobile devices 114 may leverage on existing telephony infrastructure while imparting a limited impact.
[0018] As a non-limiting example of such a mobile device 114, a given mobile device 114 may be a GSM module of a sensor that relatively infrequently powers up (i.e., "wakes up") and transmits acquired sensor data over the network 170. In this manner, the mobile device 114 for this example may be employed for machine-to-machine communications in which the device 114 communicates sensor data over the telephony network 170 with another machine, which may be, for example, a processor-based server (for example) that analyzes and/or reports the acquired sensor data to end users or other machines.
[0019] In accordance with example implementations, for purposes of further limiting the impact of the mobile devices 114 on the relatively limited number of available MSISDN numbers, the MSISDN numbers available for the mobile devices 114 are non-dialable, or non- routable, numbers. In this manner, by being a non-routable number, the MSISDN number does not consume an MSISDN number that permits mobile telephony devices to conduct voice channel communications. The choice of a non-routable number may be available because relatively few countries make use of all of the digits that are potentially available in the MSISDN number for their numbering plans. Therefore, these digits may be used to create unique but non- routable MSISDN numbers. For example, the subscriber identification portion of the MSISDN number may not be used in a given country. Therefore, as a non-limiting example, the mobile devices 114 may share the same country code and number planning area/national destination code, while using the subscriber identification portion of the MSISDN number to specifically identify the different mobile devices 114. As a non-limiting example, the subscriber identification portion codes for the different mobile devices 114 may be derived from the corresponding IMSI numbers. Although the MSISDN number may be a non-routable number, a mobile device 114 that is assigned to a non-routable MSISDN number may still, however, conduct data communications over the telephony network 170.
[0020] In accordance with some example implementations, a given mobile device 114 may be used for voice communications while not using traditional voice channels for these communications. For example, in accordance with some example implementations, the mobile device 114 may be a portable, or handheld, human-operated device, which is used for purposes of voice communications. These communications, however, occur using data path communications, such as Voice over Internet Protocol (VoIP), communications; and as such, the mobile device 114 does not rely on a dialable, or routable MSISDN number.
[0021] Thus, the mobile devices 114 may use their non-routable MSISDN numbers to communicate, because data channels of the telephony network 170 may be used for data and/or voice communication purposes. As non-limiting examples, such data services are Short Message Service (SMS), Unstructured Supplemental Services Data (USSD) and General Packet Radio Services (GPRS), may be used for purposes of permitting the mobile devices 114 to communicate data over the telephony network 170, without the devices 114 being assigned dialable, or routable, MSISDN numbers. The SMS data service may use a short message service center (SMSC), for purposes of sending short messages, commonly called "text messages," between the mobile devices 114. In general, the SMSC may temporarily store a short message for an unavailable recipient telephony device and then subsequently forward the short message to the recipient telephony device when the recipient telephony device becomes available.
[0022] Unlike the SMS data service, the USSD data service allows a real time data connection, which permits the mobile device 114 to communicate with the service provider's computers for such purposes of location based content services, services to configure the mobile device 114, and so forth. The GPRS service is a packet switched data service and may particularly be useful if a given mobile device 114 employs VoIP communications.
[0023] In accordance with other example implementations, one or multiple MSISDN numbers that are assignable to the mobile devices 114 may be routable numbers. In other words, for these implementations, the mobile devices 114 may be assigned MSISDN numbers, which may be called by other telephony devices for purposes of establishing voice channel communications over the telephony network 170.
[0024] In accordance with example implementations, a routable or non-routable and the telephony network 170 is provisioned accordingly in response to the device 114 attaching to the network 170. In this context, the mobile device 114 "attaches" to the telephony network 170 when the device 114 has connected to the network 170, and the network 170 has authenticated the identification credentials (e.g., the IMSI number and the subscriber authentication key) of the mobile device 114. In this manner, referring to Fig. 2 in conjunction with Fig. 1, in accordance with example implementations, a technique 200 includes determining (decision block 204) whether a mobile device 114 has attached to the telephony network 170 and allocating (block 208) production parameters for the mobile device 114, including an assigned telephony number (an MSISDN number, for example), pursuant to block 208. In general, a "production parameter" refers to any parameter that is used to activate the SIM card 115 of the mobile device 114 and/or support the use case of the mobile device 114. In this context, the "use case" refers to the type or category of subscription for the mobile device 114. As non-limiting examples, the use case may refer to a prepaid subscription, a postpaid subscription, a modem subscription, and so forth. As non-limiting examples, the production parameters may include the MSISDN number, the IMSI number, an SMS center (SMSC) identity, etc.
[0025] Next, the technique 200 includes provisioning (block 212) the allocated production parameters for the mobile device 114 and restarting the mobile device 114, pursuant to block 216, which causes the mobile device 114 to detach from the telephony network 170 for purposes of allowing the mobile device 114 to subsequently reattach to the network 170 so that the mobile device 114 may furnish its new credentials (telephone number, keys, etc) to begin a session on the telephony network 170. In this context, a "session" refers to the mobile device's access to the telephony network 170 based on the credentials (telephony number, etc.) that have been assigned to the mobile device 114. As an example, the mobile device 114 may be restarted by the telephony network 170 communicating an SMS or USSD Notify message to a user of the mobile device 114 to instruct the user to restart the mobile device 114. As another example, a SEVI-based applet on the mobile device 114 may be remotely activated by the telephony network 170 to restart the mobile device 114. In some implementations, the mobile device 114 is forced (block 220) to reattach to the telephony network 170 to begin the session on the telephony network 18. As a non-limiting example, the telephony network 170 may send one or multiple messages (GSM mobile application part (MAP) messages, for example) to cancel the attachment of the mobile device 114, which causes the mobile device 114 to reattach. When a determination is made (decision block 224) that the mobile device 114 has subsequently detached from the telephony network 170, the telephony number that is assigned to the mobile device 114 is returned to the pool of available telephony numbers, or recycled, pursuant to block 228.
[0026] Referring back to Fig. 1, the telephony network 170 may communicate with the mobile devices 114 via various base stations 117 that communicate wirelessly (via wireless links 103) with the mobile devices 114. As described further herein, the telephony network 170 includes a workflow manager 160 for such purposes as assigning the MSISDN numbers, recycling the MSISDN numbers and provisioning the telephony network 170 for the mobile devices 114 that are attached to the telephony network 170.
[0027] In general, the workflow manager 160 may be a processor-based machine, in accordance with example implementations. In this manner, the workflow manager 160 may include one or multiple processors 162 (one or multiple central processing units (CPUs), for example) and a memory 164 (a non-transitory memory, such as a semiconductor memory, a magnetic storage -based memory and/or an optical storage-based memory, as non-limiting examples), which may store one or multiple sets of machine executable instructions for purposes of causing the processor(s) 162 to perform one or more of the techniques (such as technique 200 described above) that are disclosed herein. As also depicted in Fig. 1, the telephony network 170 may include a carrier provisioning platform 150, which is the platform (processor-based platform, for example) that the particular wireless carrier uses for provisioning the network 170.
[0028] As also depicted in Fig. 1, one or multiple physical machines 130 may be coupled to the telephony network 170 for such purposes as conducting machine-to-machine communications with the mobile devices 114; communicating plans and profiles for the mobile devices 114 to the telephony network 170; etc. As depicted in Fig. 1, a given physical machine 130 may include one or multiple processors 134 (one or more multiple central processing units (CPUs), for example) and a memory 136 that stores one or multiple sets of machine executable program instructions 140, which when executed by the processor(s) 134 cause the physical machine 130 to communicate with a given mobile device 114; communicate plans and profiles for a given mobile device 114 to the telephony network 170; etc. The memory 136 may be a non-transitory memory, such as a semiconductor memory, a magnetic storage-based memory and/or an optical storage-based memory, as non-limiting examples.
[0029] Referring to Fig. 3, in accordance with some example implementations, the workflow manager 160 may be part of a GSM mobile application part (MAP) 300. In general, the GSM MAP 300 is a network that includes and connects a distributed computer infrastructure of the GSM network, such as a home location register (HLR) 304, an authentication center 305, a USSD gateway 308 and an SMS gateway 314. In general, the HLR 304 is a database that contains subscription information for the mobile devices 114 and the current locations of the mobile devices 114; and the authentication center 305 is a database of identification and authentication information for the subscribers.
[0030] As also depicted in Fig. 3, the GSM Map 300 may include an Over-The-Air (OTA) gateway 314, which permits the wireless communication with and downloading of information to the SIM cards 115 (Fig. 1) of the mobile devices 114. All of the above-described components of the GSM MAP 300 communicate with the workflow manager 160, as further described herein. Moreover, the workflow manager 160 communicates with a given attached mobile device 114 via a signal transfer point (STP) 384; and the workflow manager 160 may also communicate with the carrier provisioning platform 150, as further described below.
[0031] In general, a SIM vendor 350 may use a SIM manager 354 for purposes of generating SIM output files for the inventory of SIM cards 115 (see Fig. 1) for the mobile devices 114. In this context, a "SIM output file" refers to an electronic file that contains data, which describes the parameters (keys, credentials, ciphering key generating algorithm, IMSI, etc) of a corresponding SIM card 115, which are to be provisioned on the telephony network 170. Moreover, as depicted in Fig. 3, one or multiple physical machines 130 may communicate with the workflow manager 160 for purposes of loading various international mobile subscriber identity (IMSI)/MSISDN plans and profiles to be used to provision the telephony network 170 for the inventory of SIM cards 115.
[0032] Certain provisioning measures are undertaken before any of the mobile devices 114 attach to the telephony network 170 for the first time. More specifically, referring to Fig. 4 in conjunction with Fig. 3, in accordance with example implementations, a technique 400 includes loading (block 404) SIM output files into the inventory of SIM output files for SIM cards 115 that may potentially be used by the mobile devices 114. Next, according to the technique 400, machine-to-machine IMSI/MSISDN plans and profiles are loaded into the inventory, pursuant to block 408. Using the loaded inventory, the workflow manager 160 provisions the SIMs in the HLR 304 using such provisioning parameters as the IMSI number and the authentication keys (k). When dynamic IMSI routing is employed, the workflow manager 160 also updates (block 416) routing tables in the carrier provisioning platform 150.
[0033] Referring to Fig. 5 in conjunction with Fig. 3, in accordance with some implementations, the workflow manager 160 performs a technique 220 when a mobile device 114 attaches to the telephony network 170. Pursuant to the technique 220, the workflow manager 160 determines (decision block 504) whether a mobile device 114 has attached to the telephony network 170, and if so, the workflow manager 160 uses the authentication center 305 to authenticate the mobile device 114. This authentication may involve the authentication center 305 comparing a signal response transmittal by the mobile device 114 with a signal response that is calculated by the center 305. If the workflow manager 160, based on signaling received from the authentication center 305, determines (decision block 508) that the mobile device 114 has been authenticated, then the workflow manager 160 retrieves (block 512) the corresponding provisioning profile from the HLR 304 and retrieves (block 516) the subscriber status and location from the HLR 304.
[0035] Referring to Fig. 6 in conjunction with Fig. 3, in accordance with some example implementations, the workflow manager 160 performs a technique 600 for purposes of allocating production parameters (MSISDN, IMSI, SMSC identity, as non-limiting examples) for the determined use case for the mobile device 114. Pursuant to the technique 600, the workflow manager 160 first determines (block 604) the production parameters and consults (block 608) with the mobile device 114 and possibly the carrier provisioning platform 150 to allocate parameters for the use case for the mobile device 114.
[0036] Referring to Fig. 7 in conjunction with Fig. 3, the workflow manager 160 next performs a technique 700 to provision the telephony network 170, pursuant to block 704, and determine (decision block 708) whether the IMSI number that is stored on the SIM card 115 should be updated. In this manner, if the IMSI number is to be updated, the workflow manager 160 may, in accordance with some implementations, update (block 712) the SIM card 115 using the OTA gateway 314. More specifically, the update of the profile on the SIM card 115 may be performed using OTA communication techniques to update Elementary Files (EF) on the SIM card 115, such as IMSI and SMSC EFs, as non-limiting examples.
[0037] After the telephony network 170 has been provisioned, the workflow manager 160 hands over the mobile device 114 to the telephony network 170 so that the mobile device 114 may thereafter communicate with telephony devices (machine-based device, personal telephony, etc.) using the telephony network 170; and thereafter, the workflow manager 160 takes the appropriate measures to recycle the assigned MSISDN number, as depicted in Fig. 8.
[0038] In this regard, referring to Fig. 8 in conjunction with Fig. 3, in accordance with example implementations, the workflow manager 160 performs a technique 800 in which the workflow manager 160 sends (block 804) an SMS message with the newly-assigned MSISDN telephony number to the mobile device 114, pursuant to block 804. It is noted that at this point, although the telephony network 170 is provisioned for the mobile device 114, the mobile device 114 is not yet allowed to access the network 170 for general communication purposes. As depicted in Fig. 8, the technique 800 includes using the workflow manager 160 to restart the mobile device 114, pursuant to block 808, and thereafter, forcing the mobile device 114 to reattach to the telephony network 170, pursuant to block 812. As discussed above, the mobile device 114 may be restarted in a number of different ways, such as through the use of a message to instruct a user of the mobile device 114 to restart the mobile device 114 or through the activation of a SIM applet of the mobile device 114. When the mobile device 114 reattaches to the telephony network 170, the mobile device 114 receives the SMS message with the assigned MSISDN telephony number (sent in block 804) and may thereafter begin a session on the telephony network 170 in which the mobile device 114 may communication with other telephony devices.
[0039] As depicted by decision block 816, in accordance with some implementations, the workflow manager 160 thereafter monitors the connection status of the mobile device 114 to the telephony network 170 to detect when the mobile device 114 has detached from the telephony network 107. Upon detecting that the mobile device 114 has detached from the telephony network 170, the workflow manager 160 recycles the MSISDN number that was assigned to the mobile device 114, pursuant to block 820. Thus, in accordance with example implementations, the MSISDN telephony numbers of a pool of MSISDN telephony numbers for the mobile devices 114 may be used and reused, i.e., recycled, such that when a given mobile device 114 detaches from the telephony network 170, the assigned MSISDN number returns to the pool of recycled MSISDN numbers to be assigned to another mobile device 114 that subsequently attaches to the telephony network 170.
[0040] Other implementations are contemplated and are within the scope of the appended claims. For example, in accordance with other implementations, the telephony network may be a telephony network (a Code Division Multiple Access (CDMA) telephony network, as a non- limiting example) other than a GSM network.
[0041] It is noted that a limited number of implementations have been disclosed herein. Those skilled in the art, having the benefit of this disclosure, will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations.

中文:
[0001]机器与机器的通信正在不断地日益成为现代生活的一部分。在这方面,诸如智能汽车、全球定位卫星(GPS)设备、智能公用功率表等的机器是在日常生活中与其他机器通信的机器的示例。这些机器与机器通信中的许多依赖于蜂窝网络上的通信。因此,电话号码可以被指派到此类机器,不管所述机器是否究竟实际使用所述网络。
[0003]图2是描绘了依据示例实现方式的用于把电话号码指派到移动电话设备并且基于这个指派来提供电话网络的技术的流程图。
[0004]图3是依据示例实现方式的全球移动通信系统(GSM)移动应用部分(MAP)以及关联的网络部件的示意图。
[0005]图4是描绘了依据示例实现方式的用于在移动电话设备附连到电话网络之前初始化图3的电话网络的技术的流程图。
[0006]图5是描绘了依据示例实现方式的响应于移动电话设备附连到电话网络而由图3的MAP的工作流程管理器执行的技术的流程图。
[0007]图6是描绘了依据示例实现方式的由图3的MAP的工作流程管理器执行的分配的流程图。
[0008]图7是描绘了依据示例实现方式的由图3的MAP的工作流程管理器执行的用于提供电话网络的技术的流程图。
[0009]图8是依据示例实现方式的由图3的MAP的工作流程管理器执行的用于把新附连的移动电话设备移交到电话网络并且当所述设备从所述网络分离时使被指派到所述移动电话设备的电话号码再循环的技术的流程图。
[0010]参考图1,依据示例实现方式,一个或多个移动电话设备114(在此被称为“移动设备114”)可以为了与基于处理器的机器以及其他移动和基于陆上线路的电话设备通信语音和/或数据的目的而使用电话/互联网协议(IP)网络170(在此被称为“电话网络170”)。
[0011]对于在此公开的非限制性示例,电话网络170可以是全球移动通信系统(GSM)网络;以及作为非限制性示例,移动设备114可以是针对语音和/或数据通信使用电话网络170的多个不同的终端电话设备中的任一个,诸如:包括人类操作的用户接口(触摸屏、键区等)的手持式个人无线通信设备(智能电话、蜂窝电话等);被连接到基于处理器的机器(诸如,便携式或台式计算机)的调制解调器;蜂窝接入点;为了实现机器与机器通信或机器与人类通信的目的通常由任何机器(例如,基于处理器的机器)使用的通信模块(作为非限制性示例,GSM模块);等等。作为非限制性示例,可使用移动设备114的机器包括:机动车(其例如包括各种诊断传感器);全球定位卫星(GPS)设备;智能公用功率表;传感器等。此外,依赖于特定实现方式,给定移动设备114可以或可以不具有语音能力。
[0012]尽管移动设备在下面被讨论,但在此公开的技术和系统可以同样适用于为了数据和/或语音通信的目的使用电话网络的任何电子设备(例如,网络打印机)。
[0014]传统上,例如在SIM卡115被第一次使用之前,SIM卡可以被预先提供有电话号码,诸如,移动订户综合服务数字网络(MSISDN)号码。MSISDN号码标识用于使用电话网络170的订阅。MSISDN传统上是可拨打或可路由的号码,该号码被另一个电话设备为了语音信道通信的目的拨打以到达对应的订户。传统上,MSISDN号码是15位数字,其具有三个组分来导向呼叫的路由:国家代码;号码规划区域或国家目的地代码;以及订户标识。
[0015]MSISDN号码正在日益成为稀缺的资源,特别是由于正在被制造且正在被指派有MSISDN号码的不断增加数量的基于机器的电话设备。传统的GSM订户提供模型涉及:把给定组的IMSI号码与对应组的MSISDN号码相关联,使得这些MSISDN号码在具有IMSI号码的SIM卡被分发在零售渠道中之前被提供到GSM网络中。因此,这个传统的提供模型针对每IMSI号码分配一个MSISDN号码,即使关联的SIM卡从未被使用(即,即使关联的移动设备114从未附连到电话网络)。
[0016]依据在此公开的示例实现方式,当MSISDN号码被从再循环/可再循环MSISDN号码的池中指派时,为移动设备114分配的MSISDN号码的数量可以比移动设备114的数量少很多。因此,实际使用电话网络170的移动设备114被从这个池中指派MSISDN号码;并且曾经使用但不再使用所述电话网络170的移动设备114的MSISDN号码返回到所述池以用于指派到其他移动设备114。
[0017]因此,为移动设备114分配的MSISDN号码的数量被保持得相对少,以保持MSISDN资源。因此,由于MSISDN号码的再循环,在允许移动设备114从基本蜂窝功能(诸如,认证、授权、计费、可跟踪性、漫游和地理定位)受益的同时,使用相对有限数量的MSISDN号码。因此,移动设备114在施加有限影响的同时,可以利用现有电话基础设施。
[0018]作为此类移动设备114的非限制性示例,给定移动设备114可以是传感器的GSM模块,其相对不频繁地上电(即“唤醒”)并通过所述网络170传送所获取的传感器数据。以这种方式,用于这个示例的移动设备114可以被用于机器与机器的通信,其中所述设备114通过电话网络170与另一个机器通信传感器数据,该另一个机器例如可以是向终端用户或其他机器分析和/或报告所获取的传感器数据的基于处理器的服务器(例如)。
[0019]依据示例实现方式,为了进一步限制移动设备114对相对有限数量的可用MSISDN号码的影响的目的,可用于移动设备114的MSISDN号码是不可拨打或不可路由的号码。以这种方式,通过作为不可路由号码,MSISDN号码不消耗允许移动电话设备进行语音信道通信的MSISDN号码。不可路由号码的选择是可能是可用的,这是因为相对少的国家针对其编号计划利用MSISDN号码中潜在可用的所有数字。因此,这些数字可以被用于创建唯一但不可路由的MSISDN号码。例如,在给定的国家内可能不使用MSISDN号码的订户标识部分。因此,作为非限制性示例,移动设备114可以共享相同的国家代码和号码规划区域/国家目的地代码,同时使用MSISDN号码的订户标识部分来具体标识不同的移动设备114。作为非限制性示例,用于不同移动设备114的订户标识部分代码可以是从对应的IMSI号码导出的。尽管MSISDN号码可以是不可路由号码,然而被指派到不可路由MSISDN号码的移动设备114仍然可以通过电话网络170进行数据通信。
[0020]依据一些示例实现方式,给定移动设备114可以被用于语音通信,而不把传统的语音信道用于这些通信。例如,依据一些示例实现方式,移动设备114可以是便携式或手持式人类操作设备,其被用于语音通信的目的。然而,这些通信使用数据路径通信(诸如,基于互联网的语音协议(VoIP)通信)而发生;并且由此,移动设备114不依赖于可拨打或可路由的MSISDN号码。
[0021]因此,移动设备114可以使用其不可路由MSISDN号码来进行通信,这是因为电话网络170的数据信道可以被用于数据和/或语音通信的目的。作为非限制性示例,此类数据服务是:短消息服务(SMS)、非结构化补充服务数据(USSD)以及通用分组无线电服务(GPRS),可以被用于如下目的:允许移动设备114在所述设备114未被指派有可拨打或可路由MSISDN号码的情形下通过电话网络170传送数据。SMS数据服务为了在移动设备114之间发送短消息(通常被称为“文本消息”)的目的而可以使用短消息服务中心(SMSC)。通常,SMSC可以针对不可用的接收者电话设备临时存储短消息,并且然后,当接收者电话设备变为可用时,把短消息随后转发到接收者电话设备。
[0022]不同于SMS数据服务,USSD数据服务允许实时数据连接,其允许移动设备114为了基于位置的内容服务、配置移动设备114的服务等等这样的目的与服务提供者的计算机进行通信。GPRS服务是分组交换数据服务,并在给定移动设备114使用VoIP通信的情形下可以特别有用。
[0023]依据其他示例实现方式,可指派到移动设备114的一个或多个MSISDN号码可以是可路由的号码。换言之,对于这些实现方式,移动设备114可以被指派有MSISDN号码,其可以由其他电话设备为了通过电话网络170建立语音信道通信的目的而呼叫。
[0024]依据示例实现方式,可路由或不可路由MSISDN号码(取决于实现方式)被指派到给定移动设备114,并且相应地,响应于所述设备114附连到网络170而提供电话网络170。在这个背景下,当设备114已连接到网络170并且网络170已认证移动设备114的标识证书(例如,IMSI号码和订户认证密钥)时,移动设备114“附连”到电话网络170。以这种方式,参考图2结合图1,依据示例实现方式,技术200包括:确定(判决框204)是否移动设备114已附连到电话网络170,并且依据框208,为移动设备114分配(框208)生产参数,其包括所指派的电话号码(例如,MSISDN号码)。通常,“生产参数”是指被用于激活移动设备114的SIM卡115和/或支持移动设备114的使用情况的任何参数。在这个背景下,“使用情况”是指用于移动设备114的订阅的类型或类别。作为非限制性示例,使用情况可以指代预付费订阅、后付费订阅、调制解调器订阅等。作为非限制性示例,生产参数可以包括MSISDN号码、IMSI号码、SMS中心(SMSC)身份等。
[0025]接下来,技术200包括:为移动设备114提供(框212)所分配的生产参数,并且依据框216,重新启动移动设备114,这使移动设备114为了如下目的而从电话网络170分离:允许移动设备114随后重新附连到网络170,使得移动设备114可以配备其新证书(电话号码、密钥等)来在电话网络170上开始会话。在这个背景下,“会话”是指移动设备基于已被指派到移动设备114的证书(电话号码等)对电话网络170的访问。作为示例,移动设备114可以通过下述操作而被重新启动:所述电话网络170把SMS或USSD通知消息传送到移动设备114的用户来指示该用户重新启动移动设备114。作为另一个示例,移动设备114上的基于SIM的小应用程序(applet)可以被电话网络170远程激活以重新启动移动设备114。在一些实现方式中,迫使(框220)移动设备114重新附连到电话网络170以在电话网络18上开始会话。作为非限制性示例,电话网络170可以发送一个或多个消息(例如,GSM移动应用部分(MAP)消息)以取消移动设备114的附连,这使移动设备114重新附连。当移动设备114已随后从电话网络170分离的确定被做出(判决框224)时,将被指派到移动设备114的电话号码返回到可用电话号码的池,或者依据框228,再循环该电话号码。
[0026]再次参考图1,电话网络170可以经由各种基站117与移动设备114通信,基站117(经由无线链路103)与移动设备114无线通信。如在此进一步描述的,电话网络170包括用于诸如下述各项的目的的工作流程管理器160:指派MSISDN号码、再循环MSISDN号码、以及针对被附连到电话网络170的移动设备114提供电话网络170。
[0027]通常,依据示例实现方式,工作流程管理器160可以是基于处理器的机器。以这种方式,工作流程管理器160可以包括一个或多个处理器162(例如,一个或多个中央处理单元(CPU))以及存储器164(作为非限制性示例,非瞬变存储器,诸如,半导体存储器、基于磁存储的存储器和/或基于光学存储的存储器),该存储器164可以为了如下目的而存储一组或多组机器可执行指令:使(一个或多个)处理器162执行在此公开的技术(诸如,以上描述的技术200)中的一个或多个。还如图1中所描绘的,电话网络170可以包括:载体提供平台150,其是特定无线载体用于提供网络170的平台(例如,基于处理器的平台)。
[0028]还如图1中所描绘的,一个或多个物理机器130可以为了诸如下述各项的目的而被耦合到电话网络170:与移动设备114进行机器与机器的通信;把针对移动设备114的计划和配置文件传送到电话网络170等。如图1中所描绘的,给定物理机器130可以包括一个或多个处理器134(例如,一个或多个中央处理单元(CPU))以及存储器136,该存储器136存储一组或多组机器可执行程序指令140,所述机器可执行程序指令140在由(一个或多个)处理器134执行时使物理机器130执行下述操作:与给定移动设备114通信;把针对给定移动设备114的计划和配置文件传送到电话网络170等。作为非限制性示例,存储器136可以是非瞬变存储器,诸如,半导体存储器、基于磁存储的存储器和/或基于光学存储的存储器。
[0029]参考图3,依据一些示例实现方式,工作流程管理器160可以是GSM移动应用部分(MAP)300的一部分。通常,GSM MAP 300是包括且连接GSM网络的分布式计算机基础设施(诸如,归属位置寄存器(HLR)304、认证中心305、USSD网关308和SMS网关314)的网络。通常,HLR 304是包含针对移动设备114的订阅信息以及移动设备114的当前位置的数据库;以及认证中心305是用于订户的标识和认证信息的数据库。
[0030]还如图3中所描绘的,GSM Map 300可以包括:空中(OTA, Over-The-Air)网关314,其允许与移动设备114的SIM卡115(图1)无线通信并且下载信息到无线设备114的SIM卡115(图1)。GSM MAP 300的所有以上描述的部件与工作流程管理器160通信,如在此进一步描述的。此外,工作流程管理器160经由信号传输点(STP)384与给定的所附连的移动设备114通信;并且工作流程管理器160还可以与载体提供平台150通信,如以下进一步描述的。
[0031]通常,SIM供应商350可以出于生成用于移动设备114的SIM卡115(参见图1)的目录的SIM输出文件的目的而使用SIM管理器354。在这个背景下,“SIM输出文件”是指包含数据的电子文件,该数据描述了对应SIM卡115的参数(密钥、证书、密码密钥生成算法、IMSI等),该参数将被提供在电话网络170上。此外,如图3中所描述的,一个或多个物理机器130可以为了如下目的而与工作流程管理器160通信:加载各种国际移动订户身份(IMSI)/MSISDN计划和配置文件以用于为SIM卡115的目录提供电话网络170。
[0032]在移动设备114中的任一个第一次附连到电话网络170之前采取某些提供措施。更具体地,参考图4结合图3,依据示例实现方式,技术400包括:把SIM输出文件加载(框404)到可由移动设备114潜在地使用的SIM卡115的SIM输出文件的目录中。接下来,根据技术400,依据框408,将机器与机器IMSI/MSISDN计划和配置文件加载到目录中。使用所加载的目录,工作流程管理器160使用诸如IMSI号码和认证密钥(k)之类的提供参数来在HLR 304中提供SIM。当动态IMSI路由被使用时,工作流程管理器160还更新(框416)载体提供平台150中的路由表。
[0033]参考图5结合图3,依据一些实现方式,当移动设备114附连到电话网络170时,工作流程管理器160执行技术220。依据技术220,工作流程管理器160确定(判决框504)是否移动设备114已附连到电话网络170,并且如果是,则工作流程管理器160使用认证中心305来认证所述移动设备114。这个认证可以涉及:认证中心305把由移动设备114传送的信号响应与由中心305计算出的信号响应相比较。如果工作流程管理器160基于从认证中心305接收的信令确定(判决框508)移动设备114已被认证,则工作流程管理器160从HLR 304检索(框512)对应的提供配置文件,并从HLR 304检索(框516)订户状态和位置。
[0035]参考图6结合图3,依据一些示例实现方式,工作流程管理器160为了下述目的而执行技术600:为针对移动设备114的所确定的使用情况分配生产参数(作为非限制性示例,MSISDN、IMSI、SMSC身份)。依据技术600,工作流程管理器160首先确定(框604)所述生产参数,并与移动设备114以及可能地与载体提供平台150商议(框608)来为针对移动设备114的使用情况分配参数。
[0036]参考图7结合图3,工作流程管理器160接下来执行技术700,以依据框704提供电话网络170,并确定(判决框708)在SIM卡115上存储的IMSI号码是否应被更新。以这种方式,如果IMSI号码将被更新,则依据一些示例实现方式,工作流程管理器160可以使用OTA网关314来更新(框712)所述SIM卡115。更具体地,SIM卡115上配置文件的更新可以使用OTA通信技术而执行,以在SIM卡115上更新基本文件(EF),诸如,作为非限制性示例,IMSI和SMSC EF。
[0037]在电话网络170已被提供之后,工作流程管理器160把移动设备114移交给电话网络170,使得所述移动设备114此后可以使用电话网络170与电话设备(基于机器的设备、个人电话等)通信;并且此后,工作流程管理器160采取适合的措施来再循环所指派的MSISDN号码,如图8中所描绘的。
[0038]在这方面,参考图8结合图3,依据示例实现方式,工作流程管理器160执行技术800,其中,依据框804,工作流程管理器160采用新指派的MSISDN电话号码把SMS消息发送(框804)到移动设备114。要注意的是:在这一点上,尽管为移动设备114提供了电话网络170,但所述移动设备114尚未被允许为了一般通信目的而访问网络170。如图8中所描绘的,技术800包括:依据框808,使用工作流程管理器160重新启动移动设备114,并且此后,依据框812,迫使移动设备114重新附连到电话网络170。如以上所讨论的,移动设备114可以是采用多个不同方式重新启动的,诸如,通过使用消息来指示移动设备114的用户重新启动移动设备114,或通过激活移动设备114的SIM小应用程序。当移动设备114重新附连到电话网络170时,移动设备114采用所指派的MSISDN电话号码(在框804中所发送的)接收SMS消息,且此后可以在电话网络170上开始会话,其中移动设备114可以与其他电话设备通信。
[0039]如判决框816所描绘的,依据一些实现方式,工作流程管理器160此后监控移动设备114与电话网络170的连接状态,以检测所述移动设备114何时已从电话网络107分离。在检测到移动设备114已从电话网络170分离时,工作流程管理器160依据框820使被指派到移动设备114的MSISDN号码再循环。因此,依据示例实现方式,用于移动设备114的MSISDN电话号码池中的MSISDN电话号码可以被使用和重新使用(即,再循环),使得当给定移动设备114从电话网络170分离时,所指派的MSISDN号码返回到将被指派到另一个移动设备114的再循环MSISDN号码的池,所述另一个移动设备114后续附连到电话网络170。
[0040]其他的实现方式也可被考虑并且在所附权利要求的范围之内。例如,依据其他实现方式,电话网络可以是除GSM网络外的电话网络(作为非限制性示例,码分多址(CDMA)电话网络)。
[0041]要注意的是:在此已公开了有限数量的实现方式。从这个公开中受益的本领域技术人员将从中认识到众多的修改和变化。意图是,所附权利要求覆盖所有此类修改和变化。