FIELD OF THE INVENTION:
The present invention relates to operation in a networking environment and in particular relates to
accessing of services in the telecommunication network.
BACKGROUND OF THE INVENTION:
In today world’s ever-growing commitments and hectic schedule, a user often forgets carrying
pocket sized devices such as mobile phones. Going by the level of professional or social
commitments these days, even a single call or communication missed by the user can play havoc
with a user’s professional or social life. To meet such exigencies, call-forwarding acts as one of the
solution that can enable the user in receiving incoming phone calls at somebody else’s mobile
device, provided that the user has activated such option at his mobile device in favour of a
preferred MSISDN that is separate from the user’s MSISDN.
However, activating the call forwarding mechanism always requires a user’s interaction with the
user’s mobile device or somebody else’s interaction whosoever is in possession of the user’s
mobile device, and cannot be availed when the user’s mobile device is physically isolated from any
human being. In addition, during the activation, the call forwarding mechanism also requires a
prior contemplation of a preferred MSISDN at which incoming calls shall be directed and
accordingly mandatorily requires a prior intimation of the contemplated MSISDN to the network.
Accordingly, the aforesaid intimation is repeatedly required, every-time a new MSISDN is
contemplated for forwarding the calls. Moreover, the call-forwarding mechanism holds applicable
for only receiving the incoming calls and does not enable outgoing calls or any other services to be
accessed in the user’s name.
A possible solution to address aforesaid problems of call forwarding mechanism may be cloning or
virtualizing the user’s SIM based on user-instructions, causing storage of said cloned SIM at the
network end, i.e. at any network node, for a later access by any other separate mobile device that
operates a different SIM. Accordingly, one may be enabled to avail all applicable
telecommunication and data services as associated with the user’s SIM through the other mobile
device having a different SIM. However, said solution leads to a large amount of replication of data
at the network-end and proves burdensome to the processing capabilities of the network as well the
2
other mobile device that will have to adopt such cloned or virtualized SIM while accessing
services.
Accordingly, there has been a long felt need for a mechanism that not only leads to an on--the-fly
or a remote access of the user’s own mobile device services through any other mobile device
operating in the telecommunication network, but also does not lead to burdening of any network
node or the mobile device.
SUMMARY OF THE INVENTION:
This summary is provided to introduce a selection of concepts in a simplified format that are
further described in the detailed description of the invention. This summary is not intended to
identify key or essential inventive concepts of the claimed subject matter, nor is it intended for
determining the scope of the claimed subject matter.
Accordingly, in accordance with the purposes of the invention, the present invention as embodied
and broadly described herein provides a method and system for enabling a service-access across
different mobile devices in a telecommunication network. The system is configured to: create a
profile of a subscriber-user based on the user’s request received through a device, receive another
request from at least one other device to access said created profile, and based on authenticating
said other mobile device, authorize said other device towards availing at least one
telecommunication-network related service in accordance with said profile.
At least by virtue of aforesaid, the subscriber-user of a mobile device is enabled to use any other
mobile device any time to avail telecommunication services and other ancillary services associated
with subscriber-user’s account, after having registered once a user-centric profile that indicates a
type of services as applicable to the user. The profile as registered can be logged in and logged off
easily through other mobile devices, thereby providing a remote access. In addition, the profile
registration does not lead to any additional data generation or duplication of data either at the
mobile device or at the network’s end, and accordingly implementable through the existing
processing capabilities of the mobile devices and the network servers.
To further clarify advantages and features of the present invention, a more particular description of
the invention will be rendered by reference to specific embodiments thereof, which is illustrated in
the appended drawings. It is appreciated that these drawings depict only typical embodiments of
the invention and are therefore not to be considered limiting of its scope. The invention will be
described and explained with additional specificity and detail with the accompanying drawings.
3
BRIEF DESCRIPTION OF FIGURES:
These and other features, aspects, and advantages of the present invention will become better
understood when the following detailed description is read with reference to the accompanying
drawings in which like characters represent like parts throughout the drawings, wherein:
Figure 1 shows a flow chart corresponding to an embodiment of the invention;
Figure 2 shows a detailed internal construction of the system in accordance with the
embodiment of the present invention;
Figure 3 illustrates an implementation of the system illustrated in Figure 2 in a computingenvironment;
Figure 4 shows an exemplary control flow diagram in accordance with Fig. 1;
Figure 5 shows another exemplary control-flow diagram in accordance with Fig. 1;
Figure 6 depicts an exemplary application in accordance with the embodiments as described
in the preceding figures;
Figure 7 depicts another exemplary application in accordance with the embodiments as
described in the preceding figures;
Figure 8 depicts yet another exemplary application in accordance with the embodiments as
described in the preceding figures;
Figure 9 depicts yet another exemplary application in accordance with the embodiments as
described in the preceding figures; and
Figure 10 depicts yet another exemplary application in accordance with the embodiments as
described in the preceding figures;
Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity
and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the
method in terms of the most prominent steps involved to help to improve understanding of aspects
of the present invention. Furthermore, in terms of the construction of the device, one or more
components of the device may have been represented in the drawings by conventional symbols,
and the drawings may show only those specific details that are pertinent to understanding the
embodiments of the present invention so as not to obscure the drawings with details that will be
readily apparent to those of ordinary skill in the art having benefit of the description herein.
4
DETAILED DESCRIPTION:
For the purpose of promoting an understanding of the principles of the invention, reference will
now be made to the embodiment illustrated in the drawings and specific language will be used to
describe the same. It will nevertheless be understood that no limitation of the scope of the invention
is thereby intended, such alterations and further modifications in the illustrated system, and such
further applications of the principles of the invention as illustrated therein being contemplated as
would normally occur to one skilled in the art to which the invention relates.
It will be understood by those skilled in the art that the foregoing general description and the
following detailed description are exemplary and explanatory of the invention and are not intended
to be restrictive thereof.
Reference throughout this specification to “an aspect”, “another aspect” or similar language means
that a particular feature, structure, or characteristic described in connection with the embodiment is
included in at least one embodiment of the present invention. Thus, appearances of the phrase “in
an embodiment”, “in another embodiment” and similar language throughout this specification may,
but do not necessarily, all refer to the same embodiment.
The terms "comprises", "comprising", or any other variations thereof, are intended to cover a nonexclusive
inclusion, such that a process or method that comprises a list of steps does not include
only those steps but may include other steps not expressly listed or inherent to such process or
method. Similarly, one or more devices or sub-systems or elements or structures or components
proceeded by "comprises... a" does not, without more constraints, preclude the existence of other
devices or other sub-systems or other elements or other structures or other components or
additional devices or additional sub-systems or additional elements or additional structures or
additional components.
Unless otherwise defined, all technical and scientific terms used herein have the same meaning as
commonly understood by one of ordinary skill in the art to which this invention belongs. The
system, methods, and examples provided herein are illustrative only and not intended to be
limiting.
Embodiments of the present invention will be described below in detail with reference to the
accompanying drawings.
Now referring to Figure 1, it can be seen that the present invention provides a method for enabling
a service-access across different mobile devices in a telecommunication network. The method
5
comprises creating (step 102) a profile of a subscriber-user based on a request received from said
user’s mobile device or any other computing device (e.g. laptop, tablet, desktop computer) on
behalf of said user or said user’s mobile device. In an example, the profile may include references
to services as applicable to the user and other details specific to the user-subscription with a mobile
network operator. Accordingly, soon upon the user-input is received, such references may be
extracted with respect to the subscriber identity module (SIM) or MSISDN associated with the
subscriber-user. Thereafter, the profile gets constructed, and becomes active.
Further, the method comprises receiving (step 104) another request from another mobile device to
access said created profile. Such access-request may also be a request sent through any other
computing device (e.g. laptop, tablet, desktop computer) on behalf of the other mobile device. Such
another request is accompanied with a pre-defined password to authenticate said other user,
wherein password may have been set during the creation of the profile in step 102. Accordingly,
the method proceeds with the authentication of the other mobile device based on the provided
password. Based on authenticating said other mobile device, the method further comprises
authorizing (step 106) said other mobile device towards availing at least one telecommunicationnetwork
related service in accordance with said profile, as a part of accessing the profile. More
specifically, the other mobile device becomes eligible to access telecommunication services related
to the user’s mobile device as per the user-specific subscription rules within the profile.
Fig. 2 illustrates a detailed internal construction of a system 200 in accordance with the
embodiment of the present invention. The system 200 includes a processing module 202 that
performs the steps 102 and 106, while a receiving module discharges the step 204. Further,
memory 206 may be provided to store the data of the profile and other ancillary data. Likewise,
there may be other modules within the system 200 that facilitate the operational interconnection
between the processing module 202 and the receiving module 204 and performing other ancillaryfunctions.
Referring to figure 3, yet another typical hardware configuration of the system 200 in the form of a
computer system 300 is shown. The computer system 300 can include a set of instructions that can
be executed to cause the computer system 300 to perform any one or more of the methods
disclosed. The computer system 300 may operate as a standalone device or may be connected, e.g.,
using a network, to other computer systems or peripheral devices.
In a networked deployment, the computer system 300 may operate in the capacity of a server or as
a client user computer in a server-client user network environment, or as a peer computer system in
6
a peer-to-peer (or distributed) network environment. The computer system 300 can also be
implemented as or incorporated across various devices, such as a personal computer (PC), a tablet
PC, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a
desktop computer, a communications device, a wireless telephone, a land-line telephone, a web
appliance, a network router, switch or bridge, or any other machine capable of executing a set of
instructions (sequential or otherwise) that specify actions to be taken by that machine. Further,
while a single computer system 300 is illustrated, the term "system" shall also be taken to include
any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets,
of instructions to perform one or more computer functions.
The computer system 300 may include a processor 302 e.g., a central processing unit (CPU), a
graphics processing unit (GPU), or both. The processor 302 may be a component in a variety of
systems. For example, the processor 302 may be part of a standard personal computer or a
workstation. The processor 302 may be one or more general processors, digital signal processors,
application specific integrated circuits, field programmable gate arrays, servers, networks, digital
circuits, analog circuits, combinations thereof, or other now known or later developed devices for
analysing and processing data The processor 302 may implement a software program, such as code
generated manually (i.e., programmed).
The computer system 300 may include a memory 304, such as a memory 304 that can
communicate via a bus 308. The memory 304 corresponds to the memory 206 of the previous Fig.
2 and may be a main memory, a static memory, or a dynamic memory. The memory 304 may
include, but is not limited to computer readable storage media such as various types of volatile and
non-volatile storage media, including but not limited to random access memory, read-only
memory, programmable read-only memory, electrically programmable read-only memory,
electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the
like. In one example, the memory 304 includes a cache or random access memory for the processor
302. In alternative examples, the memory 304 is separate from the processor 302, such as a cache
memory of a processor, the system memory, or other memory. The memory 304 may be an
external storage device or database for storing data. Examples include a hard drive, compact disc
("CD"), digital video disc ("DVD"), memory card, memory stick, floppy disc, universal serial bus
("USB") memory device, or any other device operative to store data. The memory 304 is operable
to store instructions executable by the processor 302. The functions, acts or tasks illustrated in the
figures or described may be performed by the programmed processor 302 executing the
instructions stored in the memory 304. The functions, acts or tasks are independent of the particular
type of instructions set, storage media, processor or processing strategy and may be performed by
7
software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in
combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel
processing and the like.
As shown, the computer system 300 may or may not further include a display unit 310, such as a
liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid
state display, a cathode ray tube (CRT), a projector, a printer or other now known or later
developed display device for outputting determined information. The display 310 may act as an
interface for the user to see the functioning of the processor 302, or specifically as an interface with
the software stored in the memory 304 or in the drive unit 316.
Additionally, the computer system 300 may include an input device 312 configured to allow a user
to interact with any of the components of system 300. The input device 312 may be a number pad,
a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote
control or any other device operative to interact with the computer system 300.
The computer system 300 may also include a disk or optical drive unit 316. The disk drive unit 316
may include a computer-readable medium 322 in which one or more sets of instructions 324, e.g.
software, can be embedded. Further, the instructions 324 may embody one or more of the methods
or logic as described. In a particular example, the instructions 324 may reside completely, or at
least partially, within the memory 304 or within the processor 302 during execution by the
computer system 300. The memory 304 and the processor 302 also may include computer-readable
media as discussed above.
The present invention contemplates a computer-readable medium that includes instructions 324 or
receives and executes instructions 324 responsive to a propagated signal so that a device connected
to a network 326 can communicate voice, video, audio, images or any other data over the network
326. Further, the instructions 324 may be transmitted or received over the network 326 via a
communication port or interface 320 or using a bus 308. The communication port or interface 320
may be a part of the processor 302 or may be a separate component. The communication port 320
may be created in software or may be a physical connection in hardware. The communication port
320 may be configured to connect with a network 326, external media, the display 310, or any
other components in system 300, or combinations thereof. The connection with the network 326
may be a physical connection, such as a wired Ethernet connection or may be established
wirelessly as discussed later. Likewise, the additional connections with other components of the
8
system 300 may be physical connections or may be established wirelessly. The network 326 may
alternatively be directly connected to the bus 308.
The network 326 may include wired networks, wireless networks, Ethernet AVB networks, or
combinations thereof. The wireless network may be a cellular telephone network, an 802.11,
802.16, 802.20, 802.1Q or WiMax network. Further, the network 326 may be a public network,
such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize
a variety of networking protocols now available or later developed including, but not limited to
TCP/IP based networking protocols.
In an alternative example, dedicated hardware implementations, such as application specific
integrated circuits, programmable logic arrays and other hardware devices, can be constructed to
implement various parts of the system 300.
Applications that may include the systems can broadly include a variety of electronic and computer
systems. One or more examples described may implement functions using two or more specific
interconnected hardware modules or devices with related control and data signals that can be
communicated between and through the modules, or as portions of an application-specific
integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware
implementations.
The system described may be implemented by software programs executable by a computer
system. Further, in a non-limited example, implementations can include distributed processing,
component/object distributed processing, and parallel processing. Alternatively, virtual computer
system processing can be constructed to implement various parts of the system.
The system is not limited to operation with any particular standards and protocols. For example,
standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP,
HTML, HTTP) may be used. Such standards are periodically superseded by faster or more efficient
equivalents having essentially the same functions. Accordingly, replacement standards and
protocols having the same or similar functions as those disclosed are considered equivalents
thereof.
In the following paragraphs, a detailed description about exemplary implementation of the
invention and a control flow within such exemplary implementation has been provided. It should
however, be understood that there may be other analogous implementations related to claimed
method and system that need not strictly follow the components, steps and sequence of steps as
9
described in the following paragraphs. Thus, the following explanation shall be strictly interpreted
as one of the many conceivable exemplary implementations of the claimed subject matter, and the
scope of the claims is intended to be restricted only on the basis of the claim language and its
equivalents.
Figure 4 describes exemplary control-flow diagram 400 associated with the flow chart of Fig. 1.
More specifically, Fig. 4 presents examples with respect to the step 102 of Fig. 1.
At step 402, which denotes the step 102 of Fig. 1, the subscriber-user sends the request for profile
creation through a network node say a mobile switching centre (MSC) 406 that corresponds to a
corresponding mobile network operator. The request is sent through a mobile device having an
active Subscriber Identity module (SIM). Said request is received by the system 200 that may be
either implemented in any network node belonging to the user’s mobile network operator.
Accordingly, a profile gets created by the system 200 pertaining to the subscriber-user and is stored
within a system database 408 via step 402 a. In other example, the request in the present step may
also be sent to the system 200 by a computing device on behalf of the mobile device.
The profile comprises information related to a number of telecommunication-network related
services as allowed to be accessed by the subscriber-user through his network-subscription.
Moreover, the information in the profile is also related to the user’s selected scheme of availing the
network subscription, say a particular tariff plan selected in respect of phone calls and SMS, a
particular data usage plan as opted by the user for accessing internet, or any other conceivable
scheme of availing the telecommunication-network services. To name a few, the services entitled
to the user may include a mobile-device originated call, a mobile device terminated call, a mobile
device originated SMS, a mobile device terminated SMS, and internet data-access.
In an example, the request in the present step 402 is sent by through a network-interface such as
IVR, SMS, USSD, and a web-browser that operate within the subscriber-user’s mobile device or
the computing device that may send the request on behalf of the subscriber-user’s mobile device.
At step 404, which also denotes the step 102 of Fig.1, the user further updates the profile as has
been created in the step 402. The same includes setting up of a password to later enable a secure
access of said profile by the subscriber-user through the mobile device as referred in step 102 and
the other mobile define as referred in step 104 of Fig. 1. Optionally, the profile-update as
contemplated by the user further comprises defining a first section including a number of MSISDN
associated with the mobile devices having an active SIM that are separate from the mobile device
used in step 402 to send the request. The intention behind providing said number of MSISDN is to
10
restrict the profile-access by said MSISDN only. For example, such preferred MSISDN may be
associated with family members, friends, office colleagues of the subscriber-user. Accordingly, it is
quite conceivable that in case a number of profiles have been instructed to be created by a number
of subscriber-users, then said profiles may comprise one or more identical MSISDN within their
first section. Again, the present step 404 may be performed through the subscriber-user’s mobile
device or any other computing device as operated by the subscriber-user.
Further, the first section within the profile may further include a unique identifier associated with
the profile itself. The purpose behind provision of such unique identifier, as also elaborated later, is
to enable the system 200 in quickly identifying a particular profile desired to be accessed, out of a
number of created profiles. Such provision may be especially advantageous where a large number
of profiles have been created within the system 200 and it may be desired to rather identify each of
such profiles through a special character, rather the traversing a 10 digit code of the MSISDN
associated with profile for the purposed of identification.
Further, the profile may optionally comprise creation of a second section, wherein the second
section comprises a selection of one or more telecommunication services as planned to be accessed
by the other mobile devices or other MSISDNs. In an example, such number of MSISDN may be
equivalent to the MSISDNs as have been provided in the first section and accordingly fetched from
the first section. As a result of the association in the second section, the user may further decide a
preferential order of access of one or more of said services by the mobile devices corresponding to
such other MSISDN. In example, the user can define a preference, wherein the incoming call
otherwise destined for the MSISDN of the subscriber-user shall be received at a particular
MSISDN-1. If MSISDN-1, which is otherwise eligible for accessing the profile, has not accessed
the profile, then the incoming call is routed to another MSISDN-2 and so on to a MSISDN-3 in
case MSISDN-2 is not available. Similar rationale may be applicable in terms of other services
such incoming SMS, incoming MMS or any other type of multimedia or non-multimedia based
notifications.
Likewise, the association in the second section also helps the subscriber user in defining a scheme,
wherein one or more telecommunication network services are accessible by MSISDNs (e.g. one or
more MSISDNs defined in the first section) based on a type of entity attempting to communicate
with said subscriber-user. In example, the user can define a preference wherein the incoming call
from a specific caller (e.g. office colleague), otherwise destined for the subscriber-user, shall be
received at a particular MSISDN-1. If said incoming call has been triggered by another specific
caller (say family friend), the MSISDN-2 may be given preference ahead of MSISDN-1. Similar
11
rationale may be applicable to the other services such as incoming SMS, incoming MMS or any
other type of multimedia or non-multimedia based notifications.
Further, the association in the second section may also help the subscriber user in designating
specific service to be executed by a particular MSISDN. For example, MSISDN-1 may be used for
only receiving the incoming calls, MSISDN-2 may be used for only executing the outgoing calls,
MSISDN-3 may only be used for internet browsing.
Further, the profile includes a third section formed as a part of the profile-update request and
includes the subscriber-user’s permitted time-schedule of access of one or more of the
telecommunication-network services by said other mobile device. For example, MSISDN-1 may be
permitted to access the profile and consequently the services between 1 to 3 PM, the MSISDN-2
may be allowed between 3PM till 5PM and so on.
Further, the profile-update request as contemplated during the step 404 may also be a request that is
sent after an elapse of certain time since the creation of profile in step 402 and not necessarily
succeed the step 402. In other example, such profile-update request as sent at later stages comprises
a request for inclusion of additional MSISDN of other mobile devices in said first section, deletion
of MSISDN of one or more other mobile devices as present in the first section, inclusion of
additional services in the second section with respect to each of said other mobile devices, deletion
of services in the second section with respect to each of said other mobile devices, and
modification of the proposed time schedule in the third section.
Once the steps 402 and/or the steps 404 have been completed, the subscriber user may either isolate
the mobile-device from the network (e.g. by extracting the corresponding SIM out of the mobile
device) or may keep it in an active state. If maintained within the active state, the subscriber-user
may keep on using the mobile device normally. Nonetheless, as may be observed from the
forthcoming description, the subscriber-user by virtue of steps 402 and 404 becomes authorized to
access the services as entitled to him through using another mobile device having a different
MSISDN than the subscriber-user’s own MSISDN.
Further, the subscriber-user’s mobile device or any other computing device may be additionally
used to even deactivate or temporarily suspend the created profile to cause a discontinuation of the
access of said profile from any other MSISDN. Accordingly, such deactivation restores an
otherwise genuinely available exclusive right of the subscriber-user’s mobile device to access the
telecommunication network services.
12
Figure 5 describes another exemplary control-flow diagram 500 associated with the Fig. 1. More
specifically, Fig. 5 illustrates examples with respect to step 104 and 106 of Fig. 1.
Under step 502, which exemplifies step 104, a profile-access request is received from the other
mobile device (that is different from the subscriber-user’s mobile device) after having been routed
via the MSC 506 that is currently associated with the other mobile device. The request from such
other mobile device is also triggered through a network-interface located therein, for example,
SMS, USSD, a web-browser, etc. Moreover, said request from other mobile device is accompanied
with the provision of the password as had been set during the creation of the profile. Accordingly,
upon having accessed the profile, the same password may be used to log off as and when required.
Further, the request in the present step may also be sent to the system 200 by a computing device
acting on behalf of the other mobile device.
Under step 504, which exemplifies step 106, upon having been authenticated by the system 200,
the other mobile device gets authorized towards availing the telecommunication service in
accordance with the created profile. In case the stored profile has a first section, then the presence
of other mobile device’s MSISDN in the first section is also ascertained, in addition to the
password, for the purposes of authentication.
As a result of such authorization, the system 200 instructs a home location register HLR)
associated with the subscriber-user’s mobile device to forward incoming calls and other profile
settings destined for the subscriber-user’s mobile device to a designated module that is in-built
within the system 200. The module may comprise the processor 202 in operable interconnection
with a transceiver module. Such module is further triggered by the system 200 to direct the
forwarded incoming calls at the MSISDN associated with the other mobile device via
corresponding network node.
Likewise, as a result of the authorization, the system 200 instructs the SMS centre (SMSC)
associated with said subscriber-user’s mobile device to forward incoming SMS destined for the
subscriber-user’s mobile device to the aforesaid module. The system 200 further triggers such
module to direct said incoming SMS to said other mobile device’s MSISDN via a corresponding
short message switching centre or a network node.
Further, going back to step 502, the request may also include a request from the other mobile
device to update the profile. In other words, the other mobile device may be also entitled to update
the profile in the same manner as the subscriber-user is entitled through own mobile-device. In
other example, the update from the other mobile device may be restricted to updating the profile
13
with respect to self-details only. For example, the other mobile device may only be allowed to
update the type of service, time schedule of access of service as originally allocated to itself within
the profile.
As will be apparent from the forthcoming disclosure of Fig 6-10, any outgoing request (outgoing
call, outgoing SMS, internet browsing, etc.) from the other mobile device during the course of
accessing the aforesaid profile will be considered as if said outgoing request has originated from
the subscriber-user’s mobile device.
As may be understood, said outgoing request originating from the other mobile device may also be
optionally accompanied with an identifier. For example, an outgoing call request from the other
mobile device to a destination MSISDN may be “# ”, such that the
presence of identifier enables routing of the outgoing request to the system 200 that further
ascertains identity of a ‘particular’ profile to be accessed by the ‘other’ mobile device out of the
plurality of profiles.
In addition, within the outgoing request, the aforesaid identifier “#” may act as a primary identifier
and may be succeeded with a secondary identifier, say a numeral 1, 2, 3. Such scenario is
especially relevant in case the MSISDN of the other mobile device is mentioned within the first
section of multiple created profiles and the secondary identifier may be used to quickly identify a
particular profile intended to be accessed among the multiple created profiles.
Fig. 6 illustrates an exemplary application 600 of the process and system 200 depicted in Fig. 1 and
2, wherein a specific scenario such as “outgoing call” as originating from the other mobile device
has been considered. The MSISDN associated with other mobile device has been represented by
T1, while the MSISDN associated with the subscriber-user has been represented with U1. In
addition, the mobile switching center (MSC) corresponding to the other mobile device has been
referred as MSC A, while the MSC currently associated with the intended call recipient is MSC B.
At step 602, an outgoing call originates from T1.
At step 604, the MSC A sends an initial address message (IAM) comprising the T1 as the
originating MSISDN and a B number (called party number) as the destination MSISDN to the
system 200. The request may be prefixed with a primary identifier, say “#” or a combination of
primary and secondary identifier.
14
At step 606, the system 200 receives the IAM from the T1 and refers the records stored in the inbuilt
database 408 to ascertain a particular profile based on the identifier(s). Based on the
ascertained profile, a corresponding subscriber-user MSISDN ‘U1’ is further ascertained. However,
in case the profile to be accessed has no associated secondary identifier, then the profile is
ascertained based on the MSISDN digits of T1, and the password as has been earlier provided.
At step 608, the system 200 is communicated the U1 as the MSISDN to replace T1 within the
IAM. However, in case no map has been found in step 504, then T1 remains un-substituted within
the IAM. In other scenario, an error message may be displayed and the process gets terminated
instantly.
At step 610, the updated IAM is sent to the MSC B that is currently associated MSC with the
destination MSISDN or the intended call recipient.
Fig. 7 illustrates an exemplary application 700 of the process and system depicted in Fig. 1 and 2,
which depicts a specific scenario such as “incoming call” as originating from a third party caller
mobile device’s MSISDN dialed in favor of U1. The call gets routed through a corresponding MSC
B that is currently associated with the caller.
At step 702, a call from a caller and destined for U1 originates.
At step 704, an IAM with a caller party MSISDN as ‘A’ and the recipient party MSISDN as ‘U1’
reaches the system 200, due to the fact that subscriber-user profile is in an active condition.
However, had the profile been inactive, the IAM would have been directly routed to an MSC
corresponding with U1.
At step 706, the system 200 checks the profile stored in the database 408 as well the active one or
more “other mobile devices” that are currently accessing the stored profile.
At step 708, the system 200 gets acquainted about the active state of T1 as a sole other mobile
device accessing the profile. In other scenario, the system 200 after having referred the first section
decides T1 as the right candidate out of other MSISDNs in the first section. In yet another example,
system 200 also considers the caller identity to decide that only T1 is authorized to attend the call
on behalf of U1 with respect to the particular caller. Such decisions may also be made based upon
the settings in the other sections of the profile, say second and third. Accordingly, the system
database 408 informs the system 200 about T1 as the appropriate ‘other mobile device’.
15
At step 708, the system 200 substitutes U1 with T1 in the IAM as the appropriate recipient of the
call.
Fig. 8 illustrates an exemplary application 800 of the process and system depicted in Fig. 1 and 2,
wherein a specific scenario such as “SMS as originating from T1” and destined for a third party
mobile device has been considered.
As step 802, the SMS is generated from T1 to be sent via the MSC A that is currently associated
with T1.
At step 804, the MSC A generates a mobile originating forward short message (MO FSM)
comprising T1 as the originating MSISDN and a B number as the destination MSISDN to a
corresponding short message service center i.e. SMSC A. The B number within the request may be
pre-fixed with the primary identifier, say “#”, or a combination of primary and secondary
identifiers.
At step 806, the system 200 receives a short message delivery signal through short message peer to
peer mechanism (SMPP Deliver SM) from the SMSC A, due to the fact the that T1 has sent the
message while accessing the profile. Had profile not been accessed, then the control would have
been directly passed to step 814 from the SMSC A.
At step 808, the system 200 upon having received the trigger from SMSC A refers the profiles
stored in the in-built database to ascertain the profile that maps with the identifier(s) and further
ascertains a corresponding subscriber-user MSISDN ‘U1’. However, in case the secondary
identifier is not associated with the profile, then the profile is ascertained based on combination of
the MSISDN digits of T1 and the password as has been earlier provided.
At step 810, the system 200 is communicated U1 as the MSISDN to replace T1. However, in case
no map has been found in step 806, then T1 remains un-substituted. In other option, an error may
be displayed and the process terminates instantly.
At step 812, the system 200 prepares a short message peer to peer (SMPP) submit SM signal to
direct the SMS to be delivered to the recipient via the SMSC A, wherein the originating
number/MSISDN has been substituted as U1.
At step 814, upon having received the signal SMPP submit SM signal, the SMSC A generates a
mobile terminal forward short message i.e. MT FSM based on the MO FSM of step 802 and
accordingly directs the message to be sent to B via the MSC B.
16
Fig. 9 illustrates an exemplary application 900 of the process and system depicted in Fig. 1 and 2.
A specific scenario has been considered wherein “incoming SMS” as originating from a third party
caller mobile device’s MSISDN i.e. B number, is directed in favor of U1.
At step 902, a mobile originated forward short message (MO FSM) as originated from B gets
routed through a corresponding MSC B to a SMSC or MSC associated with U1.
At step 904, the SMSC generates a trigger i.e. mobile terminated (MT) message that comprises the
source and destination MSISDN as A and U1, respectively. However, the MT message is sent to
the system 200 due to the fact that subscriber-user profile is in active condition.
At step 906, the system 200 checks the profile stored in the database 408 as well the active one or
more “other mobile devices” that are accessing the stored profile.
At step 908, the system 200 gets acquainted about the active state of T1 as a sole ‘other mobile
device accessing the profile. In other scenario, the system 200 after having referred the first section
decides T1 as the right candidate out of other MSISDNs in the first section. In yet another example,
system 200 also considers the caller identity to decide that that only T1 is authorized to receive the
SMS on behalf of U1 with respect to the particular caller. Such decisions may also be made based
upon the settings in the other sections of the profile, say second and third. Accordingly, the
database 408 informs the system 200 about T1 as the appropriate ‘other mobile device’.
At step 910, the system 200 prepares a short message peer to peer (SMPP) submit SM signal to
direct the SMS to be delivered to the recipient via the SMSC, wherein the destination MSISDN U1
has been substituted by T1.
At step 912, upon having received the signal SMPP submit SM signal having the destination
MSISDN as T1, the SMSC generates a mobile terminal forward short message i.e. MT FSM based
on the MO FSM as received in step 802 and accordingly directs the message to be sent to T1 via an
MSC A that is currently associated with T1.
Fig. 10 illustrates an exemplary application 1000 of the process and system depicted in Fig. 1 and
2, wherein a specific request such as “internet browsing request” as originating from T1 is
processed so as to consider such request as having been originated from U1.
17
At step 1002, the T1 is configured by default with an access point name (APN) for such service.
However, in case T1 is a non-internet enabled mobile device, then such configuration may never
happen and accordingly the process will terminate at the present stage.
At step 1004, T1 through MSC A sends a packet data request to a corresponding SGSN.
At step 1006, the SGSN creates a packet data protocol (PDP) context in respect of T1 and sends it
to the database 408 for verification.
At step 1008, the database 408 of the system receives the PDP context as created and the system
200 looks out for a relevant profile. Based upon having located the profile and settings therein, a
fresh PDP context gets created in term of U1 and is communicated to a Gateway GPRS support
node (GGSN). The creation of the PDP context for U1 is based on verifying whether T1 has been
authorized as per the settings in the profile, for example rules as the second and third section of the
profile, to access internet.
However, in step 1008, in case T1 is found not authorized to access internet as per the settings in
the profile or the system 200 is all-together not able to ascertain any profile with respect to T1, then
either the context remains created in favor of T1 and forwarded to GGSN, or the process terminates
instantly.
At step 1010, the GGSN, upon having received the context signal of U1, initiates data packet
broadcast through a GPRS tunneling protocol (GTP) and directs the same back to the SGSN.
At step 1012, the SGSN forwards the received packet-data broadcast to the T1 via the MSC A.
Accordingly, T1 is enabled to perform internet browsing as part of accessing services on behalf of
U1.
It may be understood that while the operation in exemplary implementations in Fig. 4 to 10 has
been depicted in terms of the ISUP/SS7 protocol, the present subject matter may be contemplated
as being executable over other analogously known technologies/protocols such as 4G/SIP.
Overall, in view of the aforesaid, the present invention as described by claimed subject matter
ensures that a subscriber-user is enabled to use other mobile device having a different MSISDN to
avail the telecommunication network services that are otherwise associated with the subscriberuser’s
bona-fide subscriber-identity module (SIM). Moreover, since the profile creation is a onetime
executed process, the subscriber-user does not have to configure the profile repeatedly
through his mobile device and may simply remotely access the telecommunication services as
18
applicable to his SIM through any other mobile device having transceiver capabilities in the
telecommunication network. As aforesaid, the profile is facilitated to be accessed with least
hassles, e.g. by requesting-sending takes place through an SMS together with provision of predefined
password.
As a result, the subscriber-user is prevented from separately authorizing every other mobile device
for accessing the services associated with the subscriber-user’s MSISDN as the one time created
profile may be accessed over a long period of time through any other mobile device based on a
common one or more passwords. Moreover, not only the profile is remotely upgradable either
through the subscriber-user’s own mobile device or the other mobile device or any computing
device, but may also be remotely suspended or deactivated by subscriber-user through his own
mobile device or any computing device, as and when required.
Overall, not only an on-the-fly access of services is possible, but also an additional revenue, which
otherwise would have been lost due to physical separation of the mobile device from the
subscriber, may be accrued to the mobile network operator. Further, during the remote access by
the other mobile device, the expenditure associated with the availing of telecommunication services
is accounted in terms of the subscriber-user only.
Further, since the profile creation merely amounts to creation of an indication or a data reference to
the services as applicable for the subscriber-user, the profile creation as per the present subject
matter does not lead to creation of any data or data generation at the network, thereby leaving a
least footprint upon the network or the mobile device owing to the present invention. Such features
enable even legacy network servers and mobile devices to implement the present subject matter
without requiring any significant upgradation.
While specific language has been used to describe the disclosure, any limitations arising on account
of the same are not intended. As would be apparent to a person in the art, various working
modifications may be made to the method in order to implement the inventive concept as taught
herein.
The drawings and the forgoing description give examples of embodiments. Those skilled in the art
will appreciate that one or more of the described elements may well be combined into a single
functional element. Alternatively, certain elements may be split into multiple functional elements.
Elements from one embodiment may be added to another embodiment. For example, orders of
processes described herein may be changed and are not limited to the manner described herein.
19
Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all
of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts
may be performed in parallel with the other acts. The scope of embodiments is by no means limited
by these specific examples. Numerous variations, whether explicitly given in the specification or
not, such as differences in structure, dimension, and use of material, are possible. The scope of
embodiments is at least as broad as given by the following claims.
Benefits, other advantages, and solutions to problems have been described above with regard to
specific embodiments. However, the benefits, advantages, solutions to problems, and any
component(s) that may cause any benefit, advantage, or solution to occur or become more
pronounced are not to be construed as a critical, required, or essential feature or component of any
or all the claims.

WE CLAIM:
1. A method of enabling a service-access across different mobile devices in a telecommunication
network, said method comprises:
creating (step 102) a profile of a subscriber-user based on said user’s request
received through a device;
receiving (step 104) another request from at least one other device to access said
created profile; and
based on authenticating said other device, authorizing (step 106) said other device
towards availing at least one telecommunication-network related service in accordance with
said profile.
2. The method as claimed in claim 1, wherein said device and said other device is at least one of:
a mobile device; and
a non-mobile computing device operating on behalf of a mobile device.
3. The method as claimed in claim 1, wherein said created profile comprises information related to
said telecommunication-network related services accessible by said user through a networksubscription
and said user’s selected scheme of availing the network subscription.
4. The method as claimed in claim 3, wherein said services entitled to said user comprise at least
one of a mobile-device originated call, a mobile device terminated call, a mobile device originated
SMS, a mobile device terminated SMS, and internet data-access .
5. The method as claimed in claim 3, wherein said profile further comprises at least one of:
a first section comprising said user-provided one or more MSISDN associated with said other
devices for restricting access of said profile to said other devices as present in the first section;
a second section comprising at least one service selected out of said services by said user,
wherein said second section is associated with said other device and denotes one or more
applicable-services for said other device; and
a third section comprising said user-proposed time-schedule of access of one or more of said
services by said other device.
6. The method as claimed in claim 1 and 5, wherein said first section of a plurality of created
profiles corresponding to a plurality of subscriber-users comprises one or more MSISDN identical
to said plurality of profiles.
21
7. The method as claimed in claim 5, wherein said second section further comprises at least one of:
a preferential order of access of one or more said services by said one or more other devices
corresponding to one or more MSISDN provided in the first section; and
a scheme of access of one or more said services by said one or more other devices based on
a type of entity attempting to communicate with said subscriber-user.
8. The method as claimed in claim 1, wherein said request as received from the user’s device or
said profile-access request received from the other device is executed through a network-interface
located therein, said interface comprising at least one of: IVR, SMS, USSD, and a web-browser.
9. The method as claimed in preceding claims, wherein the request as received from said user’s
device comprises a request to set a password to later enable authentication of said other device
based on said set password, and wherein said other device sends said profile-access request or a
request to log off said profile based on the password.
10. The method as claimed in claim 1, wherein said other device is enabled towards availing said at
least one telecommunication-network related service in accordance with said profile through
accomplishing at least one of:
instructing a home location register associated with said user’s device to forward incoming
calls destined for said user’s device to a designated module and further triggering said module to
direct said forwarded incoming calls at said other device’s MSISDN;
instructing an SMS centre or a designated network node associated with said user’s device
to forward incoming SMS destined for said user’s device to a designated-module and further
triggering said module to direct said incoming SMS at said other device’s MSISDN; and
considering an outgoing-request originating from said other device to avail said at least one
telecommunication-network related service as a network-usage request from said subscriber-user.
11. The method as claimed in claim 10, wherein said consideration is based on verifying a presence
of at least one pre-defined identifier in said outgoing request.
12. The method as claimed in claim 6 and 10, wherein said outgoing request originating from said
other device is associated with access of a specific profile among a plurality of profiles based on
presence of a pre-defined identifier within the outgoing request.
13. The method as claimed in claim 1, wherein said authorizing further comprises enabling said
other device to update said created profile.
22
14. The method as claimed in claim 5, further comprises updating the created profile based on a
request received either from said other device or said user’s device, said profile-update request
comprising at least one of:
a request for inclusion of additional MSISDN of other devices in said first section;
a request for deletion of MSISDN of one or more other devices as present in said first
section;
a request for inclusion of additional services in said second section with respect to each of
said other devices;
a request for deletion of services in said second section with respect to each of said other
devices;
a request for modification of said proposed time schedule in said third section.
15. The method as claimed in preceding claims, further comprising deactivating said profile based
on a profile-deactivation request received from said subscriber-user’s device to dis-continue the
access of said profile from said other devices.
16. A system (200) for enabling a service-access across different mobile devices in a
telecommunication network, said system comprising:
a processing module (202) for creating profile of a subscriber-user based on said user’s
request received through a device; and
a receiving module (204) for receiving a request from at least one other device to access
said profile;
said processing module (202) authorizing said other device towards availing at least one
telecommunication-network related service in accordance with said profile, wherein said
processing module (202) authorizes said other device upon having authenticated said other device.