FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR SYNCHRONIZING AN INTERNATIONAL MOBILE SUBSCRIBER IDENTIFIER (IMSI)
THREAD BINDING”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR SYNCHRONIZING AN INTERNATIONAL MOBILE SUBSCRIBER IDENTIFIER (IMSI) THREAD BINDING
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding.
BACKGROUND
[0002] The following description of the related art is intended to provide 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 admissions of the prior art.
[0003] In any multi-threaded system architecture, cases of thread lock contention or deadlock arise if complex scenarios are not properly handled by the system or program. Data access contention leads to a shrinking of system performance as numerous CPU cycles are wasted in scheduling kernel threads as per application contextual needs. In general, multithreaded applications handle requests or responses concurrently for related or independent flows, and hence, synchronized data access for a particular and multiple flows being handled in parallel is very crucial to system performance and stability. Further, it becomes more challenging when the number of requests, responses, and users to be served concurrently increases in huge numbers. Further, this requirement is applicable for any node, such as the SIB network node in the IMS architecture, which handles the traffic for multiple users (or subscribers), wherein a particular user is identified uniquely in the network by an identifier named International Mobile Subscriber Identity (IMSI). SIB, which is a multithreaded application, is required to handle network message flow traffic for network users. Due to complex network scenarios, SIB may also receive multiple network messages at the same time for a particular user and is required to handle these messages as per standard message collision rules and procedural steps. When a particular user's network message flows are handled by multiple threads, there may be cases of

thread contention for handling the user data/information, deadlock case if thread order of handling the user messages flow is out of order, race conditions or multiple procedure collisions for the same user and the effect may also be applicable for other users as thread(resource) may contend over each other for user data access.
[0004] By contending for thread lock, the resource may take more time than necessary as some of the threads are waiting for other threads to unlock the critical data part, thereby increasing the procedure flow time unnecessarily for that user and other users as well. Another issue is that system resources are not properly utilised by this method. Further simultaneous handling of a particular user flow message may produce undesired results as the flows are not synchronized in the network.
[0005] So, to mitigate and optimally handle above mentioned points in SIB (S-CSCF, I-CSCF, B-GCF) user specific thread binding technique is used in which each user (which is identified uniquely by IMSI) is handled by particular fixed thread in the system.
[0006] Thus, there exists an imperative need in the art to provide a method and system for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding.
SUMMARY OF THE DISCLOSURE
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding. The method comprises receiving, by a transceiver unit at a System Information Block (SIB) from a user equipment (UE), a user registration request comprising at least an International Mobile Subscriber Identifier (IMSI). The method further comprises identifying, by a processing unit at the SIB, a target resource thread from a set of pre-stored resource threads, the target resource thread associated with a target resource thread identifier. The method further comprises transmitting, by the transceiver unit from the SIB, the target resource thread identifier to at least the UE associated with the user registration request, and a Home Subscriber Server (HSS). The method

further comprises receiving, by the transceiver unit at the SIB, a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name. The method further comprises extracting, by an extraction unit at the SIB, the target thread based on the target resource thread identifier and at least one of the service route header and the user name. The method further comprises assigning, by the processing unit at the SIB, the target thread to the message flow request. The method further comprises synchronising, by the processing unit, the IMSI thread binding based on the assigning of the target thread to the message flow associated with the IMSI.
[0009] In an exemplary aspect of the present disclosure, the message flow request is received from one of the UE and the HSS, wherein the message flow request comprising the service route header is received at the SIB from the UE, and the message flow request comprising the user name is received at the SIB from the HSS.
[0010] In an exemplary aspect of the present disclosure, the method further comprises transmitting from the SIB to the HSS, the target resource thread ID via an Attribute Value Pair (AVP).
[0011] Another aspect of the present disclosure may relate to a system for synchronizing an IMSI thread binding. The system further comprises a transceiver unit configured to receive, at a System Information Block (SIB) from a user equipment (UE), a user registration request comprising at least an International Mobile Subscriber Identifier (IMSI). The system further comprises a processing unit connected to at least the transceiver unit and the processing unit is configured to identify, at the SIB, a target resource thread from a set of pre-stored resource threads, the target resource thread associated with a target resource thread identifier. The transceiver unit is further configured to transmit, from the SIB, the target resource thread identifier to at least the UE associated with the user registration request, and a Home Subscriber Server (HSS). The transceiver unit is further configured to receive, at the SIB, a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name. The system further comprises an extraction unit connected to at least the transceiver unit and the processing unit, the extraction unit configured to extract the target thread based on the target resource thread identifier and at least one of the service route header and the user name. The processing unit is further configured to assign, at the SIB, the target thread to the message flow request. The processing unit is further configured

to synchronise, the IMSI thread binding based on the assigning of the target thread to the message flow associated with the IMSI.
[0012] Another aspect of the present disclosure may relate to a user equipment (UE) for synchronizing a IMSI thread binding, the user equipment comprises a memory and a processor coupled to the memory. The processor is configured to transmit to a system, a user registration request comprising at least an International Mobile Subscriber Identifier (IMSI), and receive from the system, a response comprising the synchronised the IMSI thread binding. Further, the response is received based on identifying, by the system, a target resource thread from a set of pre-stored resource threads and the target resource thread is associated with a target resource thread identifier. Further, the response is received based on transmitting, by the system, the target resource thread identifier to at least the UE associated with the user registration request, and a Home Subscriber Server (HSS) [310]. Further, the response is received based on receiving, by the system, a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name. Further, the response is received based on extracting, by the system, the target thread based on the target resource thread identifier and at least one of the service route header and the user name. Further, the response is received based on assigning, by the system, the target thread to the message flow request.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding the instructions include executable code which, when executed by a one or more units of a system, causes a transceiver unit of the system to receive, at a System Information Block (SIB) from an user equipment (UE), a user registration request comprising at least an International Mobile Subscriber Identifier (IMSI). Further, executable code which, when executed causes a processing unit of the system to identify, at the SIB, a target resource thread from a set of pre-stored resource threads, the target resource thread associated with a target resource thread identifier. Further, executable code which, when executed causes the transceiver unit to transmit, from the SIB, the target resource thread identifier to at least the UE associated with the user registration request, and a Home Subscriber Server (HSS), and receive, at the SIB, a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name. Further, executable code which, when executed causes an extraction unit of the system

to extract the target thread based on the target resource thread identifier and at least one of the service route header and the user name. Further, executable code which, when executed causes the processing unit to assign, at the SIB, the target thread to the message flow request, and synchronise, the IMSI thread binding based on the assigning the target thread to the message flow associated with the IMSI.
OBJECTS OF THE DISCLOSURE
[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding.
[0016] It is another object of the present disclosure to provide quick access to a user data for one or more message flows.
[0017] It is another object of the present disclosure to provide a system and method for resource optimization by reducing a resource contention.
[0018] It is another object of the present disclosure to provide a system and method for synchronization of the flow of user messages.
[0019] It is yet another object of the present disclosure to provide a solution to remove deadlock/resource contention from the network and provide resource optimization as resource contention is reduced.
DESCRIPTION OF THE DRAWINGS
[0020] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in 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. Also, the embodiments shown in the
figures are not to be construed as limiting the disclosure, but the possible variants of the method
and system according to the disclosure are illustrated herein to highlight the advantages of the
5 disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings
includes disclosure of electrical components or circuitry commonly used to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
10 (5GC) network architecture.
[0022] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. 15
[0023] FIG. 3 illustrates an exemplary block diagram of a system [300] for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding, in accordance with exemplary implementations of the present disclosure.
20 [0024] FIG. 4 illustrates a method flow diagram for synchronizing an International Mobile
Subscriber Identifier (IMSI) thread binding in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 5A illustrates another exemplary method flow diagram [500A] of registration of
25 the user equipment (UE) in the method for synchronizing an International Mobile Subscriber
Identifier (IMSI) thread binding in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 5B illustrates another exemplary method flow diagram [500B] for transmission of
30 subsequent message from the UE in the method for synchronizing an International Mobile
Subscriber Identifier (IMSI) thread binding in accordance with exemplary implementations of the present disclosure.
7

[0027] FIG. 5C illustrates another method flow diagram [500C] of origination of subsequent message from the HSS in the method for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding in accordance with exemplary implementations of the present disclosure. 5
[0028] FIG. 6 illustrates an architecture of System Information Block (SIB) for implementation of system for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding, in accordance with exemplary implementations of the present disclosure.
10 [0029] The foregoing shall be more apparent from the following more detailed description of
the disclosure.
DETAILED DESCRIPTION
15 [0030] In the following description, for the purposes of explanation, various specific details
are set forth 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 described hereafter may each be used independently of one another or with any combination of other features. An individual feature
20 may not address any of the problems discussed above or might address only some of the
problems discussed above.
[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
25 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 function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
30 [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 specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
8

[0033] Also, it is noted that individual embodiments may be described as a process which 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
5 the operations may be performed in parallel or concurrently. In addition, the order of the
operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0034] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an
10 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 known to those of ordinary skill in the art. Furthermore, to the extent
15 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—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
20 [0035] As used herein, a “processing unit” or “processor” or “operating processor” includes
one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a
25 microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
30
[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing
9

the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital
assistant, tablet computer, wearable device or any other computing device which is capable of
implementing the features of the present disclosure. Also, the user device may contain at least
5 one input means configured to receive an input from at least one of a transceiver unit, a
processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0037] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
10 readable medium including any mechanism for storing information in a form readable by a
computer or similar machine. For example, a computer-readable medium includes read-only
memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to
15 perform their respective functions.
[0038] As used herein “interface” or “user interface refers to a shared boundary across which
two or more separate components of a system exchange information or data. The interface may
also be referred to a set of rules or protocols that define communication or interaction of one
20 or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
[0039] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a
25 special purpose processor, a conventional processor, a digital signal processor (DSP), a
plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
30 [0040] As used herein, a “Serving-Call Session Control Function (S-CSCF)” may refer to a
central node that controls call/session setup and teardown for a specific IP Multimedia Subsystem (IMS) subscription. Further S-CSCF may maintain a session state and performs tasks like routing, authentication, billing, etc.
10

[0041] As used herein, an “Interrogating-Call Session Control Function (I-CSCF)” may refer an entry point for external requests into the IMS network. Further, the I-CSCF may query a Home Subscriber Server (HSS) to determine which S-CSCF to route the request to, and then may forward the request accordingly. 5
[0042] As used herein, a “Border Gateway Control Function (B-GCF)” may refer to a gateway that controls interconnection between different networks (e.g., IMS and PSTN/CS). Further, the B-GCF may perform tasks like protocol conversion, routing, billing, and may also acts as an entry point for incoming requests from external networks.
10
[0043] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
15
[0044] As discussed in the background section, in multi-threaded system architectures, issues like thread lock contention, deadlocks, and data access contention may arise if not properly handled, thereby leading to degraded system performance as CPU cycles are wasted on scheduling threads. As, the synchronized data access is crucial for managing concurrent
20 requests and responses, especially as the number of users and traffic increases. When multiple
threads process a user's messages, problems may occur like thread contention for user data, deadlocks due to out-of-order message handling, and race conditions, which increases processing times and lead to inefficient resource utilization and unsynchronized user flows. The current known solutions have several shortcomings. The present disclosure aims to
25 overcome the above-mentioned and other existing problems in this field of technology by
providing method and system of synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding.
[0045] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
30 (5GC) network architecture, in accordance with exemplary implementation of the present
disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
11

Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection
Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository
Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management
(UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
5 network (DN) [130], wherein all the components are assumed to be connected to each other in
a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0046] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system
10 that connects user equipment (UE) [102] to the core network (CN) and provides access to
different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
[0047] Access and Mobility Management Function (AMF) [106] is a 5G core network function
15 responsible for managing access and mobility aspects, such as UE registration, connection, and
reachability. It also handles mobility management procedures like handovers and paging.
[0048] Session Management Function (SMF) [108] is a 5G core network function responsible
for managing session-related aspects, such as establishing, modifying, and releasing sessions.
20 It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address
allocation and QoS enforcement.
[0049] Service Communication Proxy (SCP) [110] is a network function in the 5G core
network that facilitates communication between other network functions by providing a secure
25 and efficient messaging service. It acts as a mediator for service-based interfaces.
[0050] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens. 30
[0051] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
12

[0052] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
5 [0053] Network Exposure Function (NEF) [118] is a network function that exposes capabilities
and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0054] Network Repository Function (NRF) [120] is a network function that acts as a central
10 repository for information about available network functions and services. It facilitates the
discovery and dynamic registration of network functions.
[0055] Policy Control Function (PCF) [122] is a network function responsible for policy
control decisions, such as QoS, charging, and access control, based on subscriber information
15 and network policies.
[0056] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 20
[0057] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
[0058] User Plane Function (UPF) [128] is a network function responsible for handling user
25 data traffic, including packet routing, forwarding, and QoS enforcement.
[0059] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services. 30
[0060] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for synchronizing an International Mobile Subscriber Identifier
13

(IMSI) thread binding, utilising the system [300]. In another implementation, the computing
device [200] itself implements the method for synchronizing the International Mobile
Subscriber Identifier (IMSI) thread binding using one or more units configured within the
computing device [200], wherein said one or more units are capable of implementing the
5 features as disclosed in the present disclosure.
[0061] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a processor [204] coupled with bus [202] for processing information. The processor [204] may be, for example, a general-purpose
10 microprocessor. The computing device [200] may also include a main memory [206], such as
a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such
15 instructions, when stored in non-transitory storage media accessible to the processor [204],
render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
20
[0062] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED
25 (OLED) display, etc. for displaying information to a computer user. An input device [214],
including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to
30 the processor [204], and for controlling cursor movement on the display [212]. This inputs
device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
14

[0063] The computing device [200] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic
which in combination with the computing device [200] causes or programs the computing
device [200] to be a special-purpose machine. According to one implementation, the techniques
5 herein are performed by the computing device [200] in response to the processor [204]
executing one or more sequences of one or more instructions contained in the main memory
[206]. Such instructions may be read into the main memory [206] from another storage
medium, such as the storage device [210]. Execution of the sequences of instructions contained
in the main memory [206] causes the processor [204] to perform the process steps described
10 herein. In alternative implementations of the present disclosure, hard-wired circuitry may be
used in place of or in combination with software instructions.
[0064] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication
15 coupling to a network link [220] that is connected to a local network [222]. For example, the
communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a
20 compatible LAN. Wireless links may also be implemented. In any such implementation, the
communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0065] The computing device [200] can send messages and receive data, including program
25 code, through the network(s), the network link [220] and the communication interface [218].
In the Internet example, a server [230] might transmit a requested code for an application
program through the Internet [228], the ISP [226], the local network [222], the host [224] and
the communication interface [218]. The received code may be executed by the processor [204]
as it is received, and/or stored in the storage device [210], or other non-volatile storage for later
30 execution.
[0066] Referring to FIG. 3, an exemplary block diagram of a system [300] for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at
15

least one transceiver unit [302], at least one processing unit [304] and at least one extraction
unit [306]. Further, the system [300] is in connection with a Home Subscriber Server (HSS)
[310] and System Information Block (SIB) [308]. Also, all of the components/ units of the
system [300] are assumed to be connected to each other unless otherwise indicated below. As
5 shown in the figures all units shown within the system [300] should also be assumed to be
connected to each other. Also, in Fig. 1 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
10 [0067] The system [300] is configured for synchronizing an International Mobile Subscriber
Identifier (IMSI) thread binding with the help of the interconnection between the components/units of the system [300].
[0068] Further, in accordance with the present disclosure, it is to be acknowledged that the
15 functionality described for the various components/units can be implemented interchangeably.
While specific embodiments may disclose a particular functionality of these units for clarity, it
is recognized that various configurations and combinations thereof are within the scope of the
disclosure. The functionality of specific units as disclosed in the disclosure should not be
construed as limiting the scope of the present disclosure. Consequently, alternative
20 arrangements and substitutions of units, provided they achieve the intended functionality
described herein, are considered to be encompassed within the scope of the present disclosure.
[0069] In order to synchronize the IMSI thread binding, the transceiver unit [302] is configured
to receive, at the System Information Block (SIB) [308] from a user equipment (UE) [102], a
25 user registration request comprising at least an International Mobile Subscriber Identifier
(IMSI).
[0070] The present disclosure encompasses that the SIB [308] is a block that is broadcasted by
a base station of a cellular network to provide an essential information to the UE [102]. The
30 essential information may include but not limited to one or more cell-specific parameters, one
or more network configuration details and one or more other relevant data. also, the SIB [308] is periodically broadcasted by the base station and are received by the UE [102] within a cell coverage.
16

[0071] The present disclosure encompasses that the user registration request is a request from the UE [102] to connect to the cellular network (for example 5G network). The user registration request may comprise an essential information that include but not limited to IMSI and other relevant data depending on the type of cellular network. 5
[0072] The present disclosure encompasses that the IMSI is a unique identifier that is assigned
to each subscriber in a GSM (Global System for Mobile Communications) or UMTS (Universal
Mobile Telecommunications System) network. Further IMSI include a Mobile Country Code
(MCC), a Mobile Network Code (MNC) and a Mobile Subscriber Identification Number
10 (MSIN).
[0073] The processing unit [304] is connected to at least the transceiver unit [302]. The
processing unit [304] is configured to identify, at the SIB [308], a target resource thread from
a set of pre-stored resource threads, the target resource thread associated with a target resource
15 thread identifier.
[0074] The present disclosure encompasses that the target resource thread refers to a specific thread or process that may be responsible for handling one or more tasks such as managing one or more resources, data transmission or any other network-related functions. 20
[0075] The present disclosure encompasses that the transceiver unit [302] is further configured to transmit from the SIB [308] to the HSS [310] the target resource thread ID via an Attribute Value Pair (AVP).
25 [0076] As used herein, the Attribute-Value Pair (AVP) is a data structure used to store and
transmit subscriber information. The AVP may consist of an attribute i.e., a unique identifier for a specific piece of information (e.g., "IMSI", "MSISDN", "UE-IP-Address"), a value i.e., a corresponding value for the attribute (e.g., the actual IMSI number, MSISDN number, or UE IP address).
30
[0077] Further, in IMSI binding, the AVP may be used to associate a subscriber's IMSI with other relevant information, such as a UE-IP-Address, an access point name (APN), a Quality of Service (QoS) profile and an authentication data.
17

[0078] The present disclosure encompasses that the pre-stored resource threads are threads or
processes that have been previously defined and configured within the system [300]. The pre-
stored resource threads are stored in memory or in one or more configuration files that are
extracted as and when required. The pre-stored resource threads may handle one or more
5 network-related functions such as handling one or more network protocols, one or more
managing connections, and a processing data.
[0079] The present disclosure encompasses that the target resource thread identifier is a unique
identifier associated with a specific target resource thread. The target resource thread identifier
10 may allow the processing unit [304] to quickly identify and select an appropriate resource
thread from the set of pre-stored resource threads.
[0080] Thereafter, the transceiver unit [302] is further configured to transmit from the SIB
[308], the target resource thread identifier to at least the UE [102] associated with the user
15 registration request, and the Home Subscriber Server (HSS) [310].
[0081] The present disclosure encompasses that the HSS [310] serves as a central database which stores a subscriber-related information and one or more authentication credentials for the subscriber. 20
[0082] The transceiver unit [302] is further configured to receive, at the SIB [308], a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name.
25 [0083] For example: the message flow request (such as short message service (SMS))
associated with the International Mobile Subscriber Identity (IMSI) comprises following:
- the Service Route Header: SRH@example.com
- the user name: ABC.
30 [0084] The present disclosure encompasses that the transceiver unit [302] is further configured
to transmit from the SIB [308] to the UE [102], the target resource thread identifier via a service route header.
18

[0085] The present disclosure encompasses that the message flow request is received from one of the UE [102] and the HSS [310], wherein the message flow request comprising the service route header is received at the SIB [308] from the UE [102], and the message flow request comprising the user name is received at the SIB [308] from the HSS [310]. 5
[0086] The present disclosure encompasses that the service route header is a header that specifies a route or a path that the message shall follow with the network. The service route header includes an information about one or more intermediate network nodes, one or more protocols to be used and other routing details.
10
[0087] Further, the extraction unit [306] is connected to at least the transceiver unit [302] and the processing unit [304], the extraction unit [306] configured to extract the target thread based on the target resource thread identifier and at least one of the service route header and the user name from the message flow request.
15
[0088] The processing unit [304] is further configured to assign, at the SIB [308], the target thread to the message flow request and synchronise, the IMSI thread binding based on the assigning of the target thread to the message flow associated with the IMSI. The present disclosure encompasses that the IMSI thread binding refers to linking or association of the
20 thread with the IMSI which ensures that the correct target resource thread is identified and
assigned to the message flow.
[0089] The present disclosure encompasses that the synchronization refers to a coordination of the assignment of the target thread with the IMSI thread binding to ensure that the one or more
25 resources allocated to handle the message flow request associated with a specific IMSI are
synchronized with resource designated for one or more operations related to that IMSI. In other words, synchronization ensures that the assignment of the one or more resources aligns with the handling of one or more tasks specific to each subscriber, thereby optimizing performance and resource utilization.
30
[0090] Referring to Figure 4, an exemplary method flow diagram [400] for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system
19

[300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0091] At step [404], the method comprises receiving, by a transceiver unit [302] at a System
5 Information Block (SIB) [308] from a user equipment (UE) [102], a user registration request
comprising at least an International Mobile Subscriber Identifier (IMSI).
[0092] The present disclosure encompasses that the SIB [308] is a block that is broadcasted by
a base station of a cellular network to provide an essential information to the UE [102]. The
10 essential information may include but not limited to one or more cell-specific parameters, one
or more network configuration details and one or more other relevant data. also, the SIB [308] is periodically broadcasted by the base station and are received by the UE [102] within a cell coverage.
15 [0093] The present disclosure encompasses that the user registration request is a request from
the UE [102] to connect to the cellular network (for example 5G network). The user registration request may comprise an essential information that include but not limited to IMSI and other relevant data depending on the type of cellular network.
20 [0094] The present disclosure encompasses that the IMSI is a unique identifier that is assigned
to each subscriber in a GSM (Global System for Mobile Communications) or UMTS (Universal Mobile Telecommunications System) network. Further IMSI include a Mobile Country Code (MCC), a Mobile Network Code (MNC) and a Mobile Subscriber Identification Number (MSIN).
25
[0095] At step [406], the method comprises identifying, by a processing unit [304] at the SIB [308], a target resource thread from a set of pre-stored resource threads, the target resource thread associated with a target resource thread identifier.
30 [0096] The present disclosure encompasses that the target resource thread refers to a specific
thread or process that may be responsible for handling one or more tasks such as managing one or more resources, data transmission or any other network-related functions.
The present disclosure encompasses that the pre-stored resource threads are threads or processes that have been previously defined and configured within the system [300]. The pre-20

stored resource threads are stored in memory or in one or more configuration files that are extracted as and when required. The pre-stored resource threads may handle one or more network-related functions such as handling one or more network protocols, one or more managing connections, and a processing data. 5
[0097] The present disclosure encompasses that the target resource thread identifier is a unique identifier associated with a specific target resource thread. The target resource thread identifier may allow the processing unit [304] to quickly identify and select an appropriate resource thread from the set of pre-stored resource threads.
10
[0098] For example, wherein the target resource thread identifier: 0x5678, the received IMSI: 1234567 and the set of pre-stored resource threads comprises resource 1: IP Address: 192.168.1.1, Port: 80 and resource 2: IP Address: 192.168.1.2, Port: 443. Then the target resource thread from the set of pre-stored resource threads, associated with the target resource
15 thread identifier for synchronizing the IMSI thread binding has a unique identifier of 0x5678,
which is associated with the IMSI 1234567. Further, the target resource thread may have a name (such a thread 1) and may have a priority (such as High) and is associated with the target resource from set of pre-stored resource threads of (i.e., one of the resource 1 and resource 2).
20 [0099] At step [408], the method comprises transmitting, by the transceiver unit [302] from
the SIB [308], the target resource thread identifier to at least the UE [102] associated with the user registration request, and a Home Subscriber Server (HSS) [310].
[0100] The present disclosure encompasses that the HSS [310] serves as a central database
25 which stores a subscriber-related information and one or more authentication credentials for
the subscriber.
[0101] At step [410], the method comprises receiving, by the transceiver unit [302] at the SIB,
a message flow request associated with the IMSI, wherein the message flow request comprises
30 at least one of a service route header and a user name.
[0102] The present disclosure encompasses that the message flow request is received from one of the UE [102] and the HSS [310]. The message flow request comprising the service route
21

header is received at the SIB [308] from the UE [102]. The message flow request comprising the user name is received at the SIB [308] from the HSS [310].
[0103] At step [412], the method comprises extracting, by an extraction unit [306] at the SIB
5 [308], the target thread based on the target resource thread identifier and at least one of the
service route header and the user name.
[0104] The present disclosure encompasses that the service route header is a header that
specified a route or a path that the message shall follow with the network. The service route
10 header includes an information about one or more intermediate network nodes, one or more
protocols to be used and other routing details.
[0105] The present disclosure encompasses that the method further comprises transmitting
from the SIB [308] to the HSS [310], the target resource thread ID via an Attribute Value Pair
15 (AVP).
[0106] The present disclosure encompasses that the method further comprises transmitting from the SIB [308] to the UE [102], the target resource thread identifier via a service route header. 20
[0107] At step [414], the method comprises assigning, by the processing unit [304] at the SIB [308], the target thread to the message flow request.
[0108] At step [416], the method comprises synchronising, by the processing unit [304], the
25 IMSI thread binding based on the assigning the target thread to the message flow associated
with the IMSI.
[0109] The present disclosure encompasses that the IMSI thread binding refers to linking or
association of the thread with the IMSI which ensures that the correct target resource thread is
30 identified and assigned to the message flow.
[0110] The present disclosure encompasses that the synchronization refers to a coordination of the assignment of the target thread with the IMSI thread binding to ensure that the one or more resources allocated to handle the message flow request associated with a specific IMSI are
22

synchronized with resource designated for one or more operations related to that IMSI. In other words, synchronization ensures that the assignment of the one or more resources aligns with the handling of one or more tasks specific to each subscriber, thereby optimizing performance and resource utilization. 5
[0111] The method [400] terminates at step [418].
[0112] Referring to FIG. 5A, another exemplary method flow diagram [500A] of registration of the user equipment (UE) [102] in the method for synchronizing an International Mobile
10 Subscriber Identifier (IMSI) thread binding in accordance with exemplary implementations of
the present disclosure is shown. The process of registration initiates upon receiving of a new request from the UE [102]. The new request includes the IMSI, and the new request is received at the System Information Block (SIB) [308]. Thereafter, based on the IMSI, thread ID T3 is selected from a thread pool. Additionally, the thread ID is transmitted from SIB [308] to Home
15 Subscriber Server (HSS) [310] via the Attribute Value Pair (AVP). Further, the SIB [308]
transmits a service route that include a thread ID for mapping to the UE [102].
[0113] Referring to FIG. 5B, another exemplary method flow diagram [500B] for transmission of subsequent message from the UE [102] in the method for synchronizing an International
20 Mobile Subscriber Identifier (IMSI) thread binding in accordance with exemplary
implementations of the present disclosure is shown. The UE [102] transmits a subsequent request (i.e. message flow request) that includes the service route header with thread ID (i.e. thread identifier). Further based on the service route header, the thread ID T3 is selected from the thread pool at the SIB [308]. As used herein, thread pool is a group of pre-instantiated and
25 idle threads that stand ready to receive any operation or task.
[0114] Referring to FIG. 5C, yet another method flow diagram [500C] of origination of
subsequent message from the HSS [310] in the method for synchronizing an International
Mobile Subscriber Identifier (IMSI) thread binding in accordance with exemplary
30 implementations of the present disclosure is shown. The HSS [310] transmits the subsequent
request that includes the user name that is extracted on the basis of target resource thread identifier, to the SIB [308]. Further based on the user name, thread ID T3 is selected from the thread pool.
23

[0115] FIG. 6 illustrates an architecture of System Information Block (SIB) for implementation of system for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding, in accordance with exemplary implementations of the present disclosure. 5
[0116] The architecture [600] facilitate in delivering a business services logic. Moreover, the
architecture [600] may be hosted on multiple servers i.e. service logic may be hosted on of five
server and a system management function may be hosted on 2 servers. Further, the architecture
[600] provides one or more features such as an automatic failover and switchover (i.e.
10 automatic switching to a backup node in case of a failure for ensuring a continuous operation),
a call continuity feature (i.e. one or more ongoing sessions are maintained even during a failover operation).
[0117] In FIG. 6, five servers are depicted, i.e. Server 1, Server 2, Server 3, Server 4 and Server
15 5. Further, the number of servers are not limited to five and any number of servers may be used
to implement the present solution. Further, Server 1 and Server 2 are management servers which are responsible for an overall management of a network and corresponding services. Furthermore, the Server 3, Server 4 and Server 5 handles a set of processes related to a payload processing and execution of a service logic.
20
[0118] For example, the Server 1 and Server 2 manage a set of processes with facilitation of an Availability Controller (AC) which handles a high availability and a failover operation. Further, the Server 1 and Server 2 handles the set of processes with facilitation of a System Manager (SM) which manages one or more system management functions and acts an interface
25 for interacting with a network management system. Further, the Server 1 and Server 2 handles
the set of processes with facilitation of a log manager (LM) that generates and manages one or more system logs. Further, the Server 1 and Server 2 handles the set of processes with facilitation of a load distributor (LDA) that distributes a load amount among a set of service instances. Further, Server 1 and Server 2 handles the set of processes with facilitation of a
30 process handler (PH) that manages a peer heartbeat and a routing logic for the network.
[0119] For example, the Server 3, Server 4 and Server 5 handles a set of processes with facilitation of a payload availability controller (PAC) that manages a high availability and a failover operation for one or more application services. Further, the Server 3, Server 4 and
24

Server 5 handles the set of processes with facilitation of a log manager (LM) for generates and manages one or more system logs. Further, the Server 3, Server 4 and Server 5 handles the set of processes with facilitation of a service processor (SP) that manages a business service logic.
5 [0120] Further, both the Server 1 and the Server 2 includes a data storage unit [602, 604] for
storing a data related to one or more subscribers.
[0121] The present disclosure further discloses a user equipment (UE) [102] for synchronizing a IMSI thread binding, the user equipment comprises a memory and a processor coupled to the
10 memory. The processor is configured to transmit to a system [300], a user registration request
comprising at least an International Mobile Subscriber Identifier (IMSI), and receive from the system [300], a response comprising the synchronised the IMSI thread binding. Further, the response is received based on identifying, by the system [300], a target resource thread from a set of pre-stored resource threads and the target resource thread is associated with a target
15 resource thread identifier. Further, the response is received based on transmitting, by the system
[300], the target resource thread identifier to at least the UE [102] associated with the user registration request, and a Home Subscriber Server (HSS) [310]. Further, the response is received based on receiving, by the system [300], a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a
20 user name. Further, the response is received based on extracting, by the system [300], the target
thread based on the target resource thread identifier and at least one of the service route header and the user name. Further, the response is received based on assigning, by the system [300], the target thread to the message flow request.
25 [0122] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding the instructions include executable code which, when executed by a one or more units of a system [300], causes a transceiver unit [302] of the system [300] to receive, at a System Information Block (SIB) [308] from a user equipment (UE) [102], a user
30 registration request comprising at least an International Mobile Subscriber Identifier (IMSI).
Further, executable code which, when executed causes a processing unit [304] of the system [300] to identify, at the SIB [308], a target resource thread from a set of pre-stored resource threads, the target resource thread associated with a target resource thread identifier. Further, executable code which, when executed causes the transceiver unit [302] to transmit, from the
25

SIB [308], the target resource thread identifier to at least the UE [102] associated with the user
registration request, and a Home Subscriber Server (HSS) [310] and receive, at the SIB [308],
a message flow request associated with the IMSI, wherein the message flow request comprises
at least one of a service route header and a user name. Further, executable code which, when
5 executed causes an extraction unit [306] of the system [300] to extract the target thread based
on the target resource thread identifier and at least one of the service route header and the user
name. Further, executable code which, when executed causes the processing unit [304] to
assign, at the SIB [308], the target thread to the message flow request, and synchronise, the
IMSI thread binding based on the assigning the target thread to the message flow associated
10 with the IMSI.
[0123] For example, the method and system [300] for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding may be implemented in the 5G network to ensure a seamless communication and efficient resource allocation, wherein each subscriber is
15 identified by the IMSI. The transceiver unit [302] of the system [300] receives the user
registration request that includes the IMSI from the UE [102]. Thereafter, via the processing unit [304], the target resource thread is identified from the set of pre-stored resources threads. Also, the target resource thread is associated with a target resource thread identifier. Further, upon identification of the target resource thread, the transceiver unit [302] transmits the target
20 resource thread identifier to the UE [102] that is associated with the user registration request
and to the HSS [310]. Thereafter, the message flow request associated with the IMSI is received and the message flow request comprises the service route header and the user name. Further, via the extraction unit [306] of the system [300], the target thread is extracted based on the target resource thread identifier, service route header and user name. Thereafter, the processing
25 unit [304] assigns the target thread to the message flow request. Lastly, the IMSI thread binding
synchronised based on the assigning the target thread to the message flow associated with the IMSI. Additionally, the resource is assigned at a registration time in the method [400] and system [300] of the present disclosure which enables fast access to user data for message flows for enhancing the responsiveness and efficiency of communication processes, further resource
30 utilization is also optimized, and one or more user message flows are synchronized, with later
flow messages queued and handled by the same resource, ensuring consistent and orderly communication management.
26

[0124] For another example, the method and system may be implemented in the following
stages, firstly when the user registration request including the IMSI is received at the SIB [308],
a thread is selected from the pre-existing thread pool. This thread selection process ensures
efficient resource utilization. The selected thread ID is then transmitted in the server Attribute-
5 Value Pair (AVP) to the Home Subscriber Server (HSS) [310] and in the service route header
to the User Equipment (UE) [102]. This ensures that both the network's authentication server
and the user device are aware of the assigned thread for future communication. Further, when
the subsequent message flow requests are received from the UE [102] with the same route
header as earlier sent by the SIB [308], the thread data is extracted, and the thread data is
10 associated with that route header. Similarly, when message flow requests are received from the
HSS [310], the thread data is extracted based on the user name. Thereafter, these extracted thread identifiers are then used to assign the requests to the corresponding threads for further processing. Furthermore, if any requests are received from the same user while the processing unit [304] is processing earlier requests from that user, they are queued in the thread. This
15 queuing mechanism ensures synchronization within the network, preventing conflicts or
inconsistencies in handling multiple requests from the same user simultaneously. Hence, the present disclosure describes the method and system that effectively synchronizes IMSI thread binding, ensuring efficient resource allocation and orderly processing of communication requests within the network.
20
[0125] As is evident from the above, the present disclosure provides a technically advanced solution for synchronizing an International Mobile Subscriber Identifier (IMSI) thread binding. The present solution provides seamless communication and efficient resource allocation, wherein the resource assigning is done at the registration time of the UE [102], which enables
25 fast access to user data for message flows for enhancing the responsiveness and efficiency of
communication processes, further resource utilization is also optimized and one or more user message flows are synchronized, with later flow messages queued and handled by the same resource, ensuring consistent and orderly communication management.
30 [0126] While considerable emphasis has been placed herein on the disclosed implementations,
it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to
27

those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method [400] for synchronizing an International Mobile Subscriber Identifier (IMSI)
thread binding, the method comprising:
- receiving, by a transceiver unit [302] at a System Information Block (SIB) [308] from a user equipment (UE) [102], a user registration request comprising at least an International Mobile Subscriber Identifier (IMSI);
- identifying, by a processing unit [304] at the SIB [308], a target resource thread from a set of pre-stored resource threads and the target resource thread is associated with a target resource thread identifier;
- transmitting, by the transceiver unit [302] from the SIB [308], the target resource thread identifier to at least the UE [102] associated with the user registration request, and a Home Subscriber Server (HSS) [310];
- receiving, by the transceiver unit [302] at the SIB [308], a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name;
- extracting, by an extraction unit [306] at the SIB [308], the target thread based on the target resource thread identifier and at least one of the service route header and the user name;
- assigning, by the processing unit [304] at the SIB [308], the target thread to the message flow request; and
- synchronising, by the processing unit [304], the IMSI thread binding based on the assigning the target thread to the message flow associated with the IMSI.
2. The method [400] as claimed in claim 1, wherein the message flow request is received
from one of the UE [102] and the HSS [310], wherein:
the message flow request comprising the service route header is received at the SIB [308] from the UE [102], and
the message flow request comprising the user name is received at the SIB [308] from the HSS [310].
3. The method [400] as claimed in claim 1, the method further comprises transmitting
from the SIB [308] to the HSS [310], the target resource thread ID via an Attribute
Value Pair (AVP).

4. The method [400] as claimed in claim 1, the method further comprises transmitting from the SIB [308] to the UE [102], the target resource thread identifier via a service route header.
5. A system [300] for synchronizing a IMSI thread binding, the system [300] comprises:
- a transceiver unit [302], wherein the transceiver unit [302] is configured to:
• receive, at a System Information Block (SIB) [308] from a user equipment (UE)
[102], a user registration request comprising at least an International Mobile
Subscriber Identifier (IMSI);
- a processing unit [304] connected to at least the transceiver unit [302], wherein the
processing unit [304] is configured to:
• identify, at the SIB [308], a target resource thread from a set of pre-stored resource
threads, the target resource thread associated with a target resource thread
identifier;
wherein the transceiver unit [302] is further configured to:
transmit, from the SIB [308], the target resource thread identifier to at least the UE
[102] associated with the user registration request, and a Home Subscriber Server (HSS)
[310];
receive, at the SIB [308], a message flow request associated with the IMSI, wherein the
message flow request comprises at least one of a service route header and a user name;
and
• an extraction unit [306] connected to at least the transceiver unit [302]and the
processing unit [304], the extraction unit [306] configured to extract the target
thread based on the target resource thread identifier and at least one of the service
route header and the user name,
wherein the processing unit [304] is further configured to:
assign, at the SIB [308], the target thread to the message flow request; and synchronise, the IMSI thread binding based on the assigning the target thread to the message flow associated with the IMSI.
6. The system [300] as claimed in claim 5, wherein the message flow request is received
from one of the UE [102] and the HSS [310], wherein:
the message flow request comprising the service route header is received at the SIB [308] from the UE [102], and

the message flow request comprising the user name is received at the SIB [308] from the HSS [310].
7. The system [300] as claimed in claim 5, wherein the transceiver unit [302] is further configured to transmit from the SIB [308] to the HSS [310] the target resource thread ID via an Attribute Value Pair (AVP).
8. The system [300] as claimed in claim 5, wherein the transceiver unit [302] is further configured to transmit from the SIB [308] to the UE [102] the target resource thread identifier via a service route header.
9. A user equipment (UE) [102] for synchronizing a IMSI thread binding, the user equipment comprises:

- a memory; and
- a processor coupled to the memory, wherein the processor is configured to:
o transmit to a system [300], a user registration request comprising at least an
International Mobile Subscriber Identifier (IMSI), and o receive from the system [300], a response comprising the synchronised the IMSI
thread binding,
wherein the response is received based on:
identifying, by the system [300], a target resource thread from a set of pre-stored resource threads and the target resource thread is associated with a target resource thread identifier,
transmitting, by the system [300], the target resource thread identifier to at least the UE [102] associated with the user registration request, and a Home Subscriber Server (HSS) [310],
receiving, by the system [300], a message flow request associated with the IMSI, wherein the message flow request comprises at least one of a service route header and a user name,
extracting, by the system [300], the target thread based on the target resource thread identifier and at least one of the service route header and the user name, and
assigning, by the system [300], the target thread to the message flow request.