FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
THE PATENTS RULES, 2003
COMPLETE
SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR MANAGING MESSAGES IN A NETWORK
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed
2
RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material,
which is subject to intellectual property rights such as but are not limited to,
copyright, design, trademark, integrated circuit (IC) layout design, and/or trade
5 dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates
(hereinafter referred as owner). The owner has no objection to the facsimile
reproduction by anyone of the patent document or the patent disclosure, as it
appears in the Patent and Trademark Office patent files or records, but otherwise
reserves all rights whatsoever. All rights to such intellectual property are fully
10 reserved by the owner.
FIELD OF INVENTION
[0002] The present disclosure generally relates to systems and methods for
cell identification (ID) barring, thereby restricting users from sending and receiving
15 messages in a network. More particularly, the present disclosure relates to a system
and a method for managing messages in the network.
BACKGROUND OF THE INVENTION
[0003] The following description of the related art is intended to provide
20 background information pertaining to the field of the disclosure. This section may
include certain aspects of the art that may be related to various features of the
present disclosure. However, it should be appreciated that this section is used only
to enhance the understanding of the reader with respect to the present disclosure,
and not as admission of the prior art.
25 [0004] In cellular mobile systems, access to a network is performed via a
shared resource medium, known as a random access channel (RACH). In case a
user equipment (UE) initiates a voice call, the UE first contacts the network via the
RACH and subsequently receives a traffic channel allocation. In order to prevent
UEs from accessing an overloaded cell, various features have been provided as a
30 part of the third generation partnership project (3GPP). However, conventional
systems are complex and do not provide an efficient system for handling messages.
SYSTEM AND METHOD FOR MANAGING MESSAGES IN A NETWORK
3
[0005] There is, therefore, a need in the art to provide a system and a method
that can mitigate the problems associated with the prior arts.
SUMMARY
5 [0006] In an exemplary embodiment, A method for cell identification (ID)
barring to restrict one of plurality of users from sending and receiving messages in
a network by a short message service function (SMSF) is described. The method
comprises receiving a mobile originating/mobile terminating (MO/MT) request
from one user of the plurality of users. The request includes a general public
10 subscription identifier (GPSI) of the user. The method further comprises
determining whether the user is included in a global whitelist using a data structure
global whitelisting (DS-GW) flag. When the DS-GW flag is set to true, the user is
included in the global whitelist and when the DS-GW flag is set to false, the user is
not included in the global whitelist. The method comprises on determining that the
15 user is included in the global whitelist, allowing the MO/MT message and on
determining that the user is not included in the global whitelist, deriving a public
land mobile network (PLMN) identification (ID) from the MO/MT request. The
PLMN-ID include combination of a mobile country code (MCC), a mobile network
code (MNC), a tracking area code (TAC). The method further comprises verifying
20 whether the MO/MT message is barred in a defined cell ID from a plurality of cell
IDs in the PLMN using a data structure-cell blacklisted (DS-CELLB). The method
comprises on determining that the MO/MT message is barred in the defined cell ID
from plurality of cell IDs in the PLMN, barring the MO/MT message. On
determining that the MO/MT message is not barred in the defined cell ID from the
25 plurality of cell IDs in the PLMN, allowing the MO/MT message.
[0007] In some embodiments, the method further comprises creating a
dynamic counter for counting a number of MO/MT blocking due to the
management blocking for each profile value, wherein the dynamic counter is used
for home subscribers and international roamers.
30 [0008] In some embodiments, the dynamic counter is created based on one
of an originating PLMN for MO, a terminating PLMN for MT, per international
4
roamer PLMN to provide the values for MO attempted, MT attempted, MO success,
MT success, activation attempted, activation success, MO blocked, MT blocked,
context get and combination.
[0009] In some embodiments, the method further comprises determining
5 whether the PLMN is whitelisted, or block listed for the MO/MT request by using
a data structure-public land mobile network whitelisted (DS-PLMNW) or a data
structure-public land mobile network blacklisted (DS- PLMNB).
[0010] In another exemplary embodiment, a system for cell identification
(ID) barring to restrict one of plurality of users from sending and receiving
10 messages in a network is described. The system comprises a short message service
function (SMSF). The SMSF is configured to receive a mobile originating/mobile
terminating (MO/MT) request from one user of the plurality of users. The request
includes a general public subscription identifier (GPSI) of the user. The SMSF is
further configured to determine whether the user is included in a global whitelist
15 using a data structure global whitelisting (DS-GW) flag. When the DS-GW flag is
set to true, the user is included in the global whitelist and when the DS-GW flag is
set to false, the user is not included in the global whitelist. The SMSF is configured
to allow the MO/MT message on determining that the user is included in the global
whitelist and derive a public land mobile network (PLMN) identification (ID) from
20 the MO/MT request on determining that the user is not included in the global
whitelist. The PLMN-ID include combination of a mobile country code (MCC), a
mobile network code (MNC), a tracking area code (TAC). The SMSF is configured
to verify whether the MO/MT message is barred in a defined cell ID from a plurality
of cell IDs in the PLMN using a data structure-cell blacklisted (DS-CELLB). The
25 SMSF is configured to verify whether the MO/MT message is barred in the defined
cell ID from plurality of cell IDs in the PLMN using a data structure-cell blacklisted
(DS-CELLB). On determining that the MO/MT message is barred in the defined
cell ID from plurality of cell IDs in the PLMN, the SMSF is configured to bar the
MO/MT message. The SMSF is configured to allow the MO/MT message on
30 determining that the MO/MT message is not barred in the defined cell ID from
plurality of cell IDs in the PLMN.
5
[0011] In some embodiments, the SMSF is configured to create a dynamic counter
for counting a number of MO/MT blocking due to the management blocking for
each profile value. The dynamic counter is used for home subscribers and
international roamers.
5 [0012] In some embodiments, the dynamic counter is created based on one
of an originating PLMN for MO, a terminating PLMN for MT, per international
roamer PLMN to provide the values for MO attempted, MT attempted, MO success,
MT success, activation attempted, activation success, MO blocked, MT blocked,
context get and combination.
10 [0013] In some embodiments, the SMSF is configured to determine whether
the PLMN is whitelisted, or block listed for the MO/MT request by using a data
structure-public land mobile network whitelisted (DS-PLMNW) or a data structurepublic land mobile network blacklisted (DS- PLMNB).
[0014] In yet another exemplary embodiment, a short message service
15 function (SMSF) is described. The SMSF is configured to receive a mobile
originating/mobile terminating (MO/MT) request from one user of the plurality of
users. The request includes a general public subscription identifier (GPSI) of the
user. The SMSF is further configured to determine whether the user is included in
a global whitelist using a data structure global whitelisting (DS-GW) flag. The
20 SMSF is configured to allow the MO/MT message on determining that the user is
included in the global whitelist and derive a public land mobile network (PLMN)
identification (ID) from the MO/MT request on determining that the user is not
included in the global whitelist. The PLMN-ID include combination of a mobile
country code (MCC), a mobile network code (MNC), a tracking area code (TAC).
25 The SMSF is configured to verify whether the MO/MT message is barred in a
defined cell ID from a plurality of cell IDs in the PLMN using a data structure-cell
blacklisted (DS-CELLB). The SMSF is configured to verify whether the MO/MT
message is barred in the defined cell ID from plurality of cell IDs in the PLMN
using a data structure-cell blacklisted (DS-CELLB). On determining that the
30 MO/MT message is barred in the defined cell ID from plurality of cell IDs in the
PLMN, the SMSF is configured to bar the MO/MT message. The SMSF is
6
configured to allow the MO/MT message on determining that the MO/MT message
is not barred in the defined cell ID from plurality of cell IDs in the PLMN.
[0015] In some embodiments, the SMSF is configured to create a dynamic
counter for counting a number of MO/MT blocking due to the management
5 blocking for each profile value. The dynamic counter is used for home subscribers
and international roamers.
[0016] In some embodiments, the dynamic counter is created based on one
of an originating PLMN for MO, a terminating PLMN for MT, per international
roamer PLMN to provide the values for MO attempted, MT attempted, MO success,
10 MT success, activation attempted, activation success, MO blocked, MT blocked,
context get and combination.
[0017] In some embodiments, the SMSF is configured to determine whether
the PLMN is whitelisted, or block listed for the MO/MT request by using a data
structure-public land mobile network whitelisted (DS-PLMNW) or a data structure15 public land mobile network blacklisted (DS- PLMNB).
[0018] The foregoing general description of the illustrative embodiments
and the following detailed description thereof are merely exemplary aspects of the
teachings of this disclosure and are not restrictive.
OBJECTS OF THE INVENTION
20 [0019] It is an object of the present disclosure to provide a system and a
method that provides an efficient way to handle logical barring of various devices
from sending and receiving messages in a network.
[0020] It is an object of the present disclosure to provide a system and a
method that facilitates barring of selective users in a defined cell-identification (ID)
25 of a public land mobile network (PLMN).
[0021] It is an object of the present disclosure to provide a system and a
method that is directed towards barring of cell IDs in certain pre-defined areas and
provides a flexible solution to block certain cell-IDs in the PLMN from using
message related services.
30 [0022] It is an object of the present disclosure to provide a system and a
method where a short message service function (SMSF) verifies if a mobile
7
originating/mobile terminating (MO/MT) message is barred in a defined cell-ID in
the PLMN.
[0023] It is an object of the present disclosure to provide a system and a
method that enhances the security and tracing related aspects associated with the
5 devices.
BRIEF DESCRIPTION OF DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the
10 disclosed methods and systems which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each
15 component. It will be appreciated by those skilled in the art that disclosure of such
drawings includes the disclosure of electrical components, electronic components,
or circuitry commonly used to implement such components.
[0025] FIG. 1 illustrates an exemplary network architecture (100) of a
proposed system (108), in accordance with an embodiment of the present
20 disclosure.
[0026] FIG. 2 illustrates an exemplary block diagram (200) of a proposed
system (108), in accordance with an embodiment of the present disclosure.
[0027] FIG. 3 illustrates an exemplary flow diagram (300) of a mobile
originating (MO) request, in accordance with an embodiment of the present
25 disclosure.
[0028] FIG. 4 illustrates an exemplary computer system (400) in which or
with which the embodiments of the present disclosure may be implemented.
[0029] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
30
BRIEF DESCRIPTION OF THE INVENTION
8
[0030] In the following description, for explanation, various specific details
are outlined in order to provide a thorough understanding of embodiments of the
present disclosure. It will be apparent, however, that embodiments of the present
disclosure may be practiced without these specific details. Several features
5 described hereafter can each be used independently of one another or with any
combination of other features. An individual feature may not address all of the
problems discussed above or might address only some of the problems discussed
above. Some of the problems discussed above might not be fully addressed by any
of the features described herein.
10 [0031] The ensuing description provides exemplary embodiments only and
is not intended to limit the scope, applicability, or configuration of the disclosure.
Rather, the ensuing description of the exemplary embodiments will provide those
skilled in the art with an enabling description for implementing an exemplary
embodiment. It should be understood that various changes may be made in the
15 function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
[0032] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one
of ordinary skill in the art that the embodiments may be practiced without these
20 specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the embodiments in unnecessary detail. In other instances, well-known
circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail to avoid obscuring the embodiments.
25 [0033] Also, it is noted that individual embodiments may be described as a
process that is depicted as a flowchart, a flow diagram, a data flow diagram, a
structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can be performed in
parallel or concurrently. In addition, the order of the operations may be re-arranged.
30 A process is terminated when its operations are completed but could have additional
steps not included in a figure. A process may correspond to a method, a function, a
9
procedure, a subroutine, a subprogram, etc. When a process corresponds to a
function, its termination can correspond to a return of the function to the calling
function or the main function.
[0034] The word “exemplary” and/or “demonstrative” is used herein to
5 mean serving as an example, instance, or illustration. For the avoidance of doubt,
the subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
10 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive like the term
“comprising” as an open transition word without precluding any additional or other
elements.
15 [0035] Reference throughout this specification to “one embodiment” or “an
embodiment” or “an instance” or “one instance” means that a particular feature,
structure, or characteristic described in connection with the embodiment is included
in at least one embodiment of the present disclosure. Thus, the appearances of the
phrases “in one embodiment” or “in an embodiment” in various places throughout
20 this specification are not necessarily all referring to the same embodiment.
Furthermore, the particular features, structures, or characteristics may be combined
in any suitable manner in one or more embodiments.
[0036] The terminology used herein is to describe particular embodiments
only and is not intended to be limiting the disclosure. As used herein, the singular
25 forms “a”, “an”, and “the” are intended to include the plural forms as well, unless
the context indicates otherwise. It will be further understood that the terms
“comprises” and/or “comprising,” when used in this specification, specify the
presence of stated features, integers, steps, operations, elements, and/or
components, but do not preclude the presence or addition of one or more other
30 features, integers, steps, operations, elements, components, and/or groups thereof.
10
As used herein, the term “and/or” includes any combinations of one or more of the
associated listed items.
[0037] The various embodiments throughout the disclosure will be
explained in more detail with reference to FIGs. 1-4.
5 [0038] FIG. 1 illustrates an exemplary network architecture (100) of a
proposed system (108), in accordance with an embodiment of the present
disclosure.
[0039] As illustrated in FIG. 1, one or more computing devices (104-1, 104-
2…104-N) may be connected to the proposed system (108) through a network
10 (106). A person of ordinary skill in the art will understand that the one or more
computing devices (104-1, 104-2…104-N) may be collectively referred as
computing devices (104) and individually referred as a computing device (104). A
person of ordinary skill in the art will understand that the one or more users (102-
1, 102-2…102-N) may be collectively referred as users (102) and individually
15 referred as a user (102). Further, the computing devices (104) may also be referred
as a user equipment (UE) (104) or as UEs (104) throughout the disclosure. One or
more users (102-1, 102-2…102-N) may provide one or more requests to the system
(108). In an embodiment, the one or more requests may be based on a mobile
originating (MO) or a mobile terminating (MT) message.. The mobile originating
20 (MO) may refer to user equipment initiating a communication session or action, for
example, request (call or message) being sent from the user equipment. The request
is originated at the user end. The mobile terminating (MT) may refer
communication session or action directed towards a user equipment, for example,
the request (call or message) being sent to the user equipment. The message is
25 terminated at the user end.
[0040] In an embodiment, the computing device (104) may include, but not
be limited to, a mobile, a laptop, etc. Further, the computing device (104) may
include one or more in-built or externally coupled accessories including, but not
limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard.
30 Furthermore, the computing device (104) may include a mobile phone, smartphone,
virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-
11
purpose computer, a desktop, a personal digital assistant, a tablet computer, and a
mainframe computer. Additionally, input devices for receiving input from the user
(102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be
used.
5 [0041] In an embodiment, the system (108) may receive the one or more
requests from the users (102) via the computing devices (104). The system (108)
may be interchangeably referred as a short message service function (SMSF) node.
The system (108) may include one or more data structures for maintaining a
whitelist subscriber list and a blocklist subscriber list based on the one or more users
10 (102). In an embodiment, the whitelist subscriber list and the blocklist subscriber
list may be updated by the system (108) on a regular basis. The system (108) may
facilitate a cell-identification (ID) barring mechanism for both the MO and the MT
message associated with the UE (104) via the one or more data structures.
[0042] In an embodiment, the system (108) may derive the cell-ID, a public
15 land mobile network (PLMN), and a general public subscription identifier (GPSI)
information from the received one or more requests at the time of the UE (104)
attachment in the network (106).
[0043] In an embodiment, the system (108) may generate one or more
profiles based on the UE (104) attachment in the network (106).
20 [0044] In an embodiment, the system (108) may generate one or more
statistics associated with the cell-ID barring mechanism.
[0045] In an embodiment, the system (108) may generate a management
blocking mechanism associated with the one or more requests.
[0046] Further, in an embodiment, the system (108) may generate one or
25 more call data records (CDRs) associated with the management blocking
mechanism and the cell-ID barring mechanism.
[0047] Although FIG. 1 shows exemplary components of the network
architecture (100), in other embodiments, the network architecture (100) may
include fewer components, different components, differently arranged components,
30 or additional functional components than depicted in FIG. 1. Additionally, or
alternatively, one or more components of the network architecture (100) may
12
perform functions described as being performed by one or more other components
of the network architecture (100).
[0048] FIG. 2 illustrates an exemplary block diagram (200) of a proposed
system (108), in accordance with an embodiment of the present disclosure.
5 [0049] Referring to FIG. 2, in an embodiment, the system (108) may include
one or more processor(s) (202). The one or more processor(s) (202) may be
implemented as one or more microprocessors, microcomputers, microcontrollers,
digital signal processors, central processing units, logic circuitries, and/or any
devices that process data based on operational instructions. Among other
10 capabilities, the one or more processor(s) (202) may be configured to fetch and
execute computer-readable instructions stored in a memory (204) of the system
(108). The memory (204) may be configured to store one or more computerreadable instructions or routines in a non-transitory computer readable storage
medium, which may be fetched and executed to create or share data packets over a
15 network service. The memory (204) may comprise any non-transitory storage
device including, for example, volatile memory such as random-access memory
(RAM), or non-volatile memory such as erasable programmable read only memory
(EPROM), flash memory, and the like.
[0050] In an embodiment, the system (108) may include an interface(s)
20 (206). The interface(s) (206) may comprise a variety of interfaces, for example,
interfaces for data input and output devices (I/O), storage devices, and the like. The
interface(s) (206) may facilitate communication through the system (108). The
interface(s) (206) may also provide a communication pathway for one or more
components of the system (108). Examples of such components include, but are not
25 limited to, processing engine(s) (208) including a data parameter engine (212), and
a database (210).
[0051] In an embodiment, the processing engine(s) (208) may be
implemented as a combination of hardware and programming (for example,
programmable instructions) to implement one or more functionalities of the
30 processing engine(s) (208). In examples described herein, such combinations of
hardware and programming may be implemented in several different ways. For
13
example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage
medium and the hardware for the processing engine(s) (208) may comprise a
processing resource (for example, one or more processors), to execute such
5 instructions. In the present examples, the machine-readable storage medium may
store instructions that, when executed by the processing resource, implement the
processing engine(s) (208). In such examples, the system may comprise the
machine-readable storage medium storing the instructions and the processing
resource to execute the instructions, or the machine-readable storage medium may
10 be separate but accessible to the system and the processing resource. In other
examples, the processing engine(s) (208) may be implemented by electronic
circuitry.
[0052] In an embodiment, the processor (202) may receive one or more
requests via the data parameter engine (212). The one or more requests may be
15 received from users (102) via computing devices (104). The processor (202) may
store the one or more requests in the database (210).
[0053] In an embodiment, the processor (202) may include one or more data
structures for maintaining a whitelist subscriber list and a blocklist subscriber list.
The whitelist subscriber list and the blocklist subscriber list may be updated by the
20 processor (202) on a regular basis. The processor (202) may facilitate a cell-ID
barring mechanism for both an MO and an MT message associated with the
computing device (104) via the one or more data structures.
[0054] In an embodiment, the processor (202) may derive the cell-ID,
PLMN, and GPSI information from the received one or more requests at the time
25 of the UE (104) attachment in a network (106).
[0055] In an embodiment, the processor (202) may generate one or more
profiles based on the UE (104) attachment in the network (106).
[0056] In an embodiment, the processor (202) may generate one or more
statistics associated with the cell-ID barring mechanism.
30 [0057] In an embodiment, the processor (202) may generate a management
blocking mechanism associated with the one or more requests.
14
[0058] Further, in an embodiment, the processor (202) may generate one or
more CDRs associated with the management blocking mechanism and the cell-ID
barring mechanism.
[0059] Although FIG. 2 shows exemplary components of the system (108),
5 in other embodiments, the system (108) may include fewer components, different
components, differently arranged components, or additional functional components
than depicted in FIG. 2. Additionally, or alternatively, one or more components of
the system (108) may perform functions described as being performed by one or
more other components of the system (108).
10 [0060] FIG. 3 illustrates an exemplary flow diagram (300) of an MO
message, in accordance with an embodiment of the present disclosure.
[0061] As illustrated in FIG. 3, the flow diagram (300) of an MO request
may include the following steps. In an embodiment, similar steps may be used by
an MT request.
15 [0062] At step 302: The disclosed system (108) may receive an MO request
from a user (102). The MO request may include the GPSI of the user (102).
[0063] At step 304: The system (108) may determine if the user (102) is
included in a global whitelist.
[0064] At step 306: Based on a positive determination received from step
20 304, the system (108) may allow the MO request/message to be delivered.
[0065] At step 308: Based on a negative determination received from step
304, the system (108) may derive the PLMN from the MO request.
[0066] At step 310: The system (108) may determine if the PLMN is
whitelisted for the MO request. Based on a positive determination, the system (108)
25 may continue with step 306.
[0067] At step 312: Based on a negative determination from step 310, the
system (108) may determine if PLMN is block listed for the MO request.
[0068] At step 314: Based on a positive determination from step 312, the
MO request may be barred.
30 [0069] At step 316: Based on a negative determination from step 312, the
system (108) may determine if cell-ID is block listed for the MO request. Based on
15
the positive determination, the MO request may be barred at step 314. Based on a
negative determination, the system (108) may continue with step 306.
[0070] In an embodiment, the system/SMSF (108) may facilitate cell-ID
barring for both MO and MT messages with the help of four internal data structures.
5 Two of the data structures may be used for maintaining a list of all whitelisted
subscribers (GPSI used as UE identifier), and the rest for maintaining a list of all
block-listed PLMN or cell-IDs. These data structures may be populated at the time
of whitelisting or block-listing provisioning. The data structures may be as follows:
10 Key -> GPSI
Value -> Global whitelisting flag, Message Type (MO/MT/Both), DS-PLMNW
[0071] In an embodiment, the SMSF (108) may use a DS-GW data structure
15 to check if a defined GPSI is globally whitelisted. If the SMSF (108) finds that the
GPSI is globally whitelisted, then it may allow the MO/MT message. If not, the
SMSF (108) may query the DS-PLMNW data structure for that GPSI. In an
example, the DS-PLMNW may refer to collection of cell IDs that are whitelisted in
PLMN.
20
Key -> PLMN
Value -> Message Type (MO/MT/Both)
[0072] In an embodiment, the SMSF (108) may use the DS-PLMNW data
25 structure to check if a defined GPSI is whitelisted in the PLMN from which the
SMSF (108) receives the MO message or to which SMSF (108) is about to forward
the MT message. If the GPSI is whitelisted for that PLMN, the SMSF (108) may
allow the MO/MT message. If not, the SMSF (108) may go on to query the DSPLMNB data structure for block listing.
30
Key -> PLMN
Value -> PLMN blocklisting flag, Message Type (MO/MT/Both), DS-CELLB
DS-GW
DS-PLMNW
DS-PLMNB
16
[0073] In an embodiment, the SMSF (108) may use a DS-PLMNB to verify
if the MO/MT messages are barred for that PLMN. If the SMSF (108) finds that
PLMN is barred for a short message service (SMS), the message may be barred
5 straightaway. If not, the SMSF (108) may query a DS-CELLB for message barring
in the cell-ID. In an example, the DS-CELLB is a database or repository of cell IDs
that are blacklisted for various reasons including, but are not limited to, lost/stolen
device, unauthorized access, regulatory compliance including location based
restrictions, and public safety. The DS-CELLB may be created and maintained by
10 service providers or can be shared from state authorities maintaining the DSCELLB. In an example, the DS-PLMNB may refer to collection of cell IDs that
are blacklisted in PLMN.
Key -> Cell-Id
15 Value -> Message Type (MO/MT/Both)
[0074] In an embodiment, the SMSF (108) may use a DS-CELLB to verify
if the MO/MT messages are barred in a defined cell-ID in the PLMN. If the SMSF
(108) finds that the UE cell-ID is barred for an SMS, the message may be barred
20 straightaway. If not, the SMSF (108) may allow the MO/MT message. Further, the
SMSF (108) may be able to provide a range of cell IDs per PLMN for which
MO/MT may be blocked. The user (102) may provide the list of cell IDs in possible
ways, but not limited to, individual cell IDs, i.e. an Evolved UMTS Terrestrial
Radio Access Network (E-UTRAN) cell identifier (ECI) / new radio cell identity
25 (NCI), list of cell IDs (ECI/NCI), mobile country code (MCC) + mobile network
code (MNC) + type allocation code (TAC) + ECI/ NCI individual list of
MCC+MNC+TAC+ECI/NCI.
[0075] In an embodiment, the SMSF (108) may derive the cell-ID, PLMN,
and GPSI information from an activation request received at the time of UE (104)
30 attachment in 5G network. Further, the SMSF (108) may generate following
statistics as well.
DS-CELLB
17
 Total number of blocked messages
 Total number of blocked MO messages
 Total number of blocked MT messages
 Number of blocked messages for the PLMN
5  Number of blocked MO messages for the PLMN
 Number of blocked MT messages for the PLMN
 Number of blocked messages for the cell-ID
 Number of blocked MO messages for the cell-ID
 Number of blocked MT messages for a cell-ID
10  Total number of whitelisted messages
 Total number of whitelisted MO messages
 Total number of whitelisted MT messages
 Number of whitelisted messages for the subscriber (GPSI)
 Number of whitelisted MO messages for the subscriber (GPSI)
15  Number of whitelisted MT messages for the subscriber (GPSI)
 Number of whitelisted messages in a PLMN for the subscriber
 Number of whitelisted MO messages in a PLMN for the subscriber
 Number of whitelisted MT messages in a PLMN for the subscriber.
[0076] In an embodiment, the SMSF (108) may provide the range of cell20 IDs per PLMN for which MO/MT may be blocked. The SMSF (108) may provide
the whitelisting functionalities based on mobile station integrated services digital
network (MSISDN) and/or a command line interface (CLI) and an ability to create
CDRs for blocking. Appropriate commands may be available for supporting above
functions for both individual provisioning as well as bulk provisioning.
25 Provisioning may include Create/Modify/Append/Delete All/Delete Partial
depending upon the user requirements. The SMSF (108) may also provide logging
functionality for blocking and corresponding counters may be available for cell-ID
based blocking. The cell-ID based blocking feature may not impact existing
features and functions of the SMSF (108). Further, the management blocking
18
feature may be supported that may relate to a group of pre-defined users (102) in
any cell-ID.
[0077] In an embodiment, the management blocking may also be known as
a unified data manager (UDM) profile based blocking. The SMSF (108) may
5 interact with the UDM to get the SMS profile of the subscriber, which may include
fields such as, but not limited to,
“mtSmsSubscribed”/“mtSmsBarringAll”/“mtSmsBarringRoaming”/“moSmsSubs
cribed”/“moSmsBarringAll”/“moSmsbarringRoaming.” The SMSF (108) may
have a capability to honour the blocking based on the subscriber UDM profile. For
10 the purpose, the SMSF (108) may provide a user configurable runtime flag to enable
or disable the “management blocking” feature. In case “mtSmsSubscribed” is set to
“False” or “mtSmsBarringAll” is set to “True,” then the SMSF (108) may not allow
the MT SMS for the subscriber. Similarly, if “moSmsSubscribed” is set to “False”
or “moSmsBarringAll” is set to “True,” then the SMSF (108) may not allow the
15 MO SMS for the subscriber. In case the subscriber is currently roaming (serving
PLMN is not matching the subscriber permanent identifier (SUPI)/international
mobile subscriber identity (IMSI) and if “mtSmsBarringRoaming” is set to “True,”
then also the MT SMS may not be allowed for the subscriber.
[0078] Similarly, if the subscriber is roaming and “moSmsbarringRoaming”
20 is set to “True,” then MO SMS may not be allowed by the SMSF (108). These rules
for blocking may not require any specific list of MSISDN/CLI to be created and
rather may only be dependent upon the fact that the “management blocking” feature
is enabled. In an embodiment, the SMSF (108) may subscribe to the UDM to get
the latest subscriber profile, which may be used for making the blocking decision
25 for management blocking feature. In case profile is not available at the SMSF (108),
then the SMSF (108) may fetch the profile from the UDM and also subscribe to a
profile change from the UDM before making the blocking decision.
[0079] In an embodiment, the SMSF (108) may also write the CDRs for
management blocking similar to the CDRs to be written for the cell-ID based
30 blocking bit with a different status code for identifying the management blocking.
Also, the SMSF (108) may create the counter for number of MO/MT blocking due
19
to the management blocking (separately) for each profile value and may be separate
for international roamers as well. The counter may be a dynamic counter to count a
number of MO/MT responsive to a management blocking feature for profiles. The
SMSF (108) may create an extensible data record (XDR)/appropriate logs/alerts
5 based on a threshold level. Further, the SMSF (108) may ensure that the
“management blocking” feature flag at the SMSF (108) instance and cluster level
survives the restart. The SMSF (108) may include the flag value as a part of a
backup and restore operations.
[0080] In an embodiment, the SMSF (108) may provide a flag which by
10 default may be set to false based on a blocking mechanism sent towards vProbe or
not. It may be understood that vProbe may be an XDR analytical solution. In case
the flag is false, the SDR for blocking may not be sent towards vProbe. In case the
flag is true, the SDRs generated for blocking may be sent towards vProbe. Further,
the SDR may be able to distinguish between various types of blocking depending
15 upon a use case. As an example for cell-ID blocking, specific code may be given,
whereas for management blocking for MO SMS, another status code may be
provided.
[0081] In an exemplary embodiment, the PLMN (MCC+MNC) home user
(or a specific list of MSISDN/IMSI) may not be able to send the message towards
20 specific country code (B Party starting from specific CC).
[0082] In an exemplary embodiment, any user (102) (or a specific list of
MSISDN/IMSI) currently roaming into a specific PLMN (MCC+MNC) may not
be able to send the message towards a specific country code (B Party starting from
specific CC).
25 [0083] In an exemplary embodiment, the PLMN (MCC+MNC) home user
(or a specific list of MSISDN/IMSI) may not be able to receive the message from a
specific country code (A Party starting from specific CC).
[0084] In an exemplary embodiment, any user (102) (or a specific list of
MSISDN/IMSI) currently roaming into specific PLMN (MCC+MNC) may not be
30 able to receive a message from a specific country code (A Party starting from
specific CC).
20
[0085] In an embodiment, the CDR may be written by the SMSF (108)
based on the whitelisting and the block listing. The new CDR files may not be
required to be created but rather the existing CDR files may be used i.e. CDR file
used for International roamers may be used for holding the International roamer
5 blocking CDRs as well. Similarly, the CDR file used for subscribers may be used
for holding the blocking CDR for the subscribers.
[0086] In an embodiment, the use cases may survive a restart of a single
SMSF instance or a complete cluster restart. Further, the SMSF (108) may provide
the mechanism to backup and restore lists in case needed. Auto backup (scheduled)
10 may not be possible along with a manual restore function.
[0087] In an embodiment, the SMSF (108) may provide the appropriate
SDR records for cell-ID blocking and for a special use case blocking scenario. The
SMSF (108) may also audit the feature at regular intervals and in case of
unavailability of the feature, the SMSF (108) may be able to create appropriate logs
15 and generate an appropriate alert.
[0088] In an embodiment, the SMSF (108) may be enhanced to provide the
support for dynamic counters that are generated based on a combination of fields
such as, but not limited to, an originating PLMN (for MO), a terminating PLMN
(for MT), Per International roamer PLMN to provide the values for MO Attempted,
20 MT Attempted, MO Success, MT Success, Activation Attempted, Activation
Success, MO Blocked, MT Blocked, Context Get, etc. These dynamic counters may
be used for not only monitoring a granular performance per PLMN (for both home
subscribers and international roamers), they may also be converted to key
performance indicators (KPIs) for monitoring. These dynamic counters may be
25 integrated with an integrated performance management (IPM) module directly to
maximize benefits associated.
[0089] FIG. 4 illustrates an exemplary computer system (400) in which or
with which embodiments of the present disclosure may be implemented.
[0090] As shown in FIG. 4, the computer system (400) may include an
30 external storage device (410), a bus (420), a main memory (430), a read-only
memory (440), a mass storage device (450), a communication port(s) (460), and a
21
processor (470). A person skilled in the art will appreciate that the computer system
(400) may include more than one processor and communication ports. The
processor (470) may include various modules associated with embodiments of the
present disclosure. The communication port(s) (460) may be any of an RS-232 port
5 for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit
or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other
existing or future ports. The communication ports(s) (460) may be chosen
depending on a network, such as a Local Area Network (LAN), Wide Area Network
(WAN), or any network to which the computer system (400) connects
10 [0091] In an embodiment, the main memory (430) may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art.
The read-only memory (440) may be any static storage device(s) e.g., but not
limited to, a Programmable Read Only Memory (PROM) chip for storing static
information e.g., start-up or basic input/output system (BIOS) instructions for the
15 processor (470). The mass storage device (450) may be any current or future mass
storage solution, which can be used to store information and/or instructions.
Exemplary mass storage solutions include, but are not limited to, Parallel Advanced
Technology Attachment (PATA) or Serial Advanced Technology Attachment
(SATA) hard disk drives or solid-state drives (internal or external, e.g., having
20 Universal Serial Bus (USB) and/or Firewire interfaces).
[0092] In an embodiment, the bus (420) may communicatively couple the
processor(s) (470) with the other memory, storage, and communication blocks. The
bus (420) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended
(PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for
25 connecting expansion cards, drives, and other subsystems as well as other buses,
such a front side bus (FSB), which connects the processor (470) to the computer
system (400).
[0093] In another embodiment, operator and administrative interfaces, e.g.,
a display, keyboard, and cursor control device may also be coupled to the bus (420)
30 to support direct operator interaction with the computer system (400). Other
operator and administrative interfaces can be provided through network
22
connections connected through the communication port(s) (460). Components
described above are meant only to exemplify various possibilities. In no way should
the aforementioned exemplary computer system (400) limit the scope of the present
disclosure.
5 [0094] While considerable emphasis has been placed herein on the preferred
embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made in the preferred embodiments without departing from
the principles of the disclosure. These and other changes in the preferred
embodiments of the disclosure will be apparent to those skilled in the art from the
10 disclosure herein, whereby it is to be distinctly understood that the foregoing
descriptive matter is to be implemented merely as illustrative of the disclosure and
not as a limitation.
ADVANTAGES OF THE INVENTION
15 [0095] The present disclosure provides an efficient way to handle logical
barring of various devices from sending and receiving messages in a network.
[0096] The present disclosure facilitates barring of selective users in a
defined cell-identification (ID) of a public land mobile network (PLMN).
[0097] The present disclosure is directed towards barring of cell IDs in
20 certain pre-defined areas and provides a flexible solution to block certain cell IDs
in the PLMN from using message related services.
[0098] The present disclosure provides a system and a method where a short
message service function (SMSF) verifies if a mobile originating/mobile
terminating (MO/MT) message is barred in a defined cell-ID in the PLMN.
25 [0099] The present disclosure provides a secured and robust communication
system.
[00100] The present disclosure provides a system and a method that enhances
the security and tracing related aspects associated with the devices.
23
WE CLAIM:
1. A method for cell identification (ID) barring to restrict one of plurality of
users (102) from sending and receiving messages in a network by a short
5 message service function (SMSF) (108), the method comprising:
receiving a mobile originating/mobile terminating (MO/MT) request
from a user (102) of the plurality of users (102), wherein the request includes
a general public subscription identifier (GPSI) of the user (102);
responsive to the MO/MT request, determining whether the user
10 (102) is included in a global whitelist using a data structure global
whitelisting (DS-GW) flag, wherein when the DS-GW flag is set to true, the
user (102) is included in the global whitelist and when the DS-GW flag is
set to false, the user (102) is not included in the global whitelist;
on determining that the user (102) is included in the global whitelist,
15 allowing MO/MT message;
on determining that the user (102) is not included in the global
whitelist, deriving a public land mobile network (PLMN) identification (ID)
from the MO/MT request, wherein the PLMN-ID comprises a mobile
country code (MCC), a mobile network code (MNC), and a tracking area
20 code (TAC);
verifying whether the MO/MT message is barred in a defined cell ID
from a plurality of cell IDs in the PLMN using a data structure-cell
blacklisted (DS-CELLB); and
on determining that the MO/MT message is barred in the defined cell
25 ID from the plurality of cell IDs in the PLMN, barring the MO/MT message,
or on determining that the MO/MT message is not barred in the defined cell
ID from the plurality of cell IDs in the PLMN, allowing the MO/MT
message.
30 2. The method of claim 1 further comprising creating a dynamic counter for
counting a number of MO/MT blocking based on a management blocking
24
parameter for MO/MT blocking for each profile, wherein the dynamic
counter is used for home subscribers and international roamers.
3. The method of claim 1, wherein the dynamic counter is created based on
5 one of an originating PLMN for MO, a terminating PLMN for MT, per
international roamer PLMN to provide the values for MO attempted, MT
attempted, MO success, MT success, activation attempted, activation
success, MO blocked, MT blocked, context get and combination.
10 4. The method of claim 1 further comprising determining whether the PLMN
is whitelisted or block listed for the MO/MT request by using a data
structure-public land mobile network whitelisted (DS-PLMNW) or a data
structure-public land mobile network blacklisted (DS- PLMNB).
15 5. A system for cell identification (ID) barring to restrict one of plurality of
users (102) from sending and receiving messages in a network, the system
comprising a short message service function (SMSF) (108), the SMSF (108)
is configured to:
receive a mobile originating/mobile terminating (MO/MT) request
20 from a user (102) of the plurality of users (102), wherein the request includes
the a general public subscription identifier (GPSI) of the user (102);
responsive to the MO/MT request, determine whether the user (102)
is included in a global whitelist using a data structure global whitelisting
(DS-GW) flag, wherein when the DS-GW flag is set to true, the user (102)
25 is included in the global whitelist and when the DS-GW flag is set to false,
the user (102) is not included in the global whitelist;
on determining that the user (102) is included in the global whitelist,
allow MO/MT message;
on determining that the user (102) is not included in the global
30 whitelist, derive a public land mobile network (PLMN) identification (ID)
from the MO/MT request, wherein the PLMN-ID include combination of a
25
mobile country code (MCC), a mobile network code (MNC), a tracking area
code (TAC);
verify whether the MO/MT message is barred in a defined cell ID
from a plurality of cell IDs in the PLMN using a data structure-cell
5 blacklisted (DS-CELLB); and
on determining that the MO/MT message is barred in the defined cell
ID from the plurality of cell IDs in the PLMN, bar the MO/MT message, or
configure the SMSF (108) to allow the MO/MT message on determining
that the MO/MT message is not barred in the defined cell ID from the
10 plurality of cell IDs in the PLMN.
6. The system of claim 5, the SMSF (108) is configured to create a dynamic
counter for counting a number of MO/MT blocking based on management
blocking parameter for each profile, wherein the dynamic counter is used
15 for home subscribers and international roamers.
7. The system of claim 5, wherein the dynamic counter is created based on one
of an originating PLMN for MO, a terminating PLMN for MT, per
international roamer PLMN to provide the values for MO attempted, MT
20 attempted, MO success, MT success, activation attempted, activation
success, MO blocked, MT blocked, context get and combination.
8. The system of claim 5, the SMSF (108) is configured to determine whether
the PLMN is whitelisted or block listed for the MO/MT request by using a
25 data structure-public land mobile network whitelisted (DS-PLMNW) or a
data structure-public land mobile network blacklisted (DS- PLMNB).
9. A short message service function (SMSF) (108), the SMSF (108) is
configured to:
26
receive a mobile originating/mobile terminating (MO/MT) request
from a user (102) of the plurality of users (102), wherein the request includes
a general public subscription identifier (GPSI) of the user (102);
determine whether the user (102) is included in a global whitelist
5 using a data structure global whitelisting (DS-GW) flag, wherein when the
DS-GW flag is set to true, the user (102) is included in the global whitelist
and when the DS-GW flag is set to false, the user (102) is not included in
the global whitelist;
on determining that the user (102) is included in the global whitelist,
10 allow MO/MT message;
on determining that the user (102) is not included in the global
whitelist, derive a public land mobile network (PLMN) identification (ID)
from the MO/MT request, wherein the PLMN-ID include combination of a
mobile country code (MCC), a mobile network code (MNC), a tracking area
15 code (TAC);
verify whether the MO/MT message is barred in a defined cell ID
from a plurality of cell IDs in the PLMN using a data structure-cell
blacklisted (DS-CELLB); and
on determining that the MO/MT message is barred in the defined cell
20 ID from the plurality of cell IDs in the PLMN, bar the MO/MT message,
wherein the SMSF (108) is configured to allow the MO/MT message on
determining that the MO/MT message is not barred in the defined cell ID
from the plurality of cell IDs in the PLMN.
25 10. The SMSF (108) of claim 9, the SMSF (108) is configured to: create a
dynamic counter for counting a number of MO/MT blocking due to
management blocking for each profile value, wherein the dynamic counter
is used for home subscribers and international roamers.
30 11. The SMSF (108) of claim 9, wherein the dynamic counter is created based
on one of an originating PLMN for MO, a terminating PLMN for MT, per
27
international roamer PLMN to provide the values for MO attempted, MT
attempted, MO success, MT success, activation attempted, activation
success, MO blocked, MT blocked, context get and combination.
5 12. The SMSF (108) of claim 9, the SMSF (108) is configured to determine
whether the PLMN is whitelisted, or block listed for the MO/MT request by
using a data structure-public land mobile network whitelisted (DSPLMNW) or a data structure-public land mobile network blacklisted (DSPLMNB).
10
13. A computer program product comprising a non-transitory computerreadable medium comprising instructions that, when executed by one or
more processors, cause the one or more processors to execute a method for
cell identification (ID) barring to restrict one of plurality of users (102) from
15 sending and receiving messages in a network by a short message service
function (SMSF) (108), the method comprising:
receiving a mobile originating/mobile terminating (MO/MT) request
from a user (102) of the plurality of users (102), wherein the request includes
a general public subscription identifier (GPSI) of the user (102);
20 responsive to the MO/MT request, determining whether the user
(102) is included in a global whitelist using a data structure global
whitelisting (DS-GW) flag, wherein when the DS-GW flag is set to true, the
user (102) is included in the global whitelist and when the DS-GW flag is
set to false, the user (102) is not included in the global whitelist;
25 on determining that the user (102) is included in the global whitelist,
allowing MO/MT message;
on determining that the user (102) is not included in the global
whitelist, deriving a public land mobile network (PLMN) identification (ID)
from the MO/MT request, wherein the PLMN-ID include combination of a
30 mobile country code (MCC), a mobile network code (MNC), a tracking area
code (TAC);
28
verifying whether the MO/MT message is barred in a defined cell ID
from a plurality of cell IDs in the PLMN using a data structure-cell
blacklisted (DS-CELLB); and
on determining that the MO/MT message is barred in the defined cell
5 ID from the plurality of cell IDs in the PLMN, barring the MO/MT message,
or on determining that the MO/MT message is not barred in the defined cell
ID from the plurality of cell IDs in the PLMN, allowing the MO/MT
message.