DESC:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEM AND METHOD FOR DETERMINING LAST LOCATION OF A USER EQUIPMENT DURING GRACEFUL SHUTDOWN
2. APPLICANT(S)
Name Nationality Address
JIO PLATFORMS LIMITED INDIAN Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
3. PREAMBLE TO THE DESCRIPTION
The following specification particularly describes the invention and the manner in which it is to be performed.

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 dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after 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 reserved by the owner.
TECHNICAL FIELD
[0002] The present disclosure relates generally to the field of wireless communication network. More particularly, the present disclosure relates to a system and a method for determining last location of a user equipment (UE) in call detail record (CDR) during graceful shutdown.
DEFINITION
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] The expression ‘Graceful shutdown’ used hereinafter in the specification refers to a structured and coordinated approach for deactivating network components, ensuring minimal disruption and maintaining service quality as much as possible..
[0005] The expression ‘Call Detail Record (CDR)’ used hereinafter in the specification refers to a data record that provides detailed information about a telecommunications transaction or session. CDRs are primarily used for billing, monitoring, and analyzing network activity. They contain detailed information about network events and transactions, such as calls, data sessions, and messaging activities.
[0006] The expression ‘Serving Call Session Control Function (SCSCF)’ used hereinafter in the specification refers to a component in the IP Multimedia Subsystem (IMS) architecture used in modern telecommunications networks, including 4G long-term evolution (LTE) and 5G. SCSCF handles initiation, modification, and termination of multimedia sessions, ensuring that calls and sessions are properly set up and maintained. Further, SCSCF manages control of ongoing sessions, including handling requests for changes, such as transferring a call or adding participants.
[0007] These definitions are in addition to those expressed in the art.
BACKGROUND
[0008] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0009] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. Further, 6G successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (IoT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.
[0010] As the wireless technologies are advancing, there is a need to cope up with the 5G requirements and delivering a high level of service to the customers. A telecommunication network requires routers for managing network traffic in the network, forwarding the data packets to their intended IP addresses, and allowing multiple user devices to use the same internet connection. A provider edge (PE) router is a router between a network service provider's area and areas administered by other network service providers. During a graceful shutdown, the PE routers need to be shut down or reset when the maintenance of PE routers in the telecommunication network is planned. For example, the PE router may shutdown and removed from service in response to, e.g., upgrading of certain hardware or rebooting of the router following a software upgrade. There is a need to determine the last location of the user equipment (UE), during the graceful shutdown, especially when the user is moving from one location to a new location during an outgoing call. The determined last location of the user is further stored in call detail records (CDRs) of the network and is used to resume the call with the new location.
[0011] The CDRs are generated by the calls conducted over telecommunication network elements and interfaces. The CDRs are used to maintain/record various attributes of a voice call or other telecommunication transaction (e.g., text message) that pass through those telecommunication network elements. The generated CDRs are used for various purposes by a network operator, such as billing, analytics, logging, law enforcement and investigations etc. The analysis of the CDR data provides insights into the voice call monitoring, such as inbound calls, outbound calls, dropped calls, abandoned calls, and unanswered calls. The CDR data helps the network operators to track details of various telecommunication activities of the network subscribers so that the network operator make necessary changes to improve productivity and efficiency at all service levels.
[0012] The stored last location of the UE in the CDR is used to restore the ongoing call services for the user at the new location during the graceful shutdown. Therefore, determining the last location of the UE during the graceful shutdown is becoming crucial day by day.
[0013] The traditional techniques generally determine an incorrect last location of the UE during the graceful shutdown are thus inefficient.
SUMMARY
[0014] In an exemplary embodiment, a method for determining a last location of a user equipment (UE) during a graceful shutdown is disclosed. The method includes receiving, by a receiving unit, a user request to provide the last location of the UE. Responsive to receiving the user request, the method includes generating at least one notification signal to be received at a first terminal unit and a second terminal unit respectively. The method further includes communicating, by the first terminal unit, the received at least one notification signal to a first party. The method further includes receiving, by the first terminal unit, at least one first information header corresponding to the UE from the first party. The method further includes communicating, by the second terminal unit, the at least one received notification signal to a second party. The method further includes receiving, by the second terminal unit, at least one second information header corresponding to the UE from the second party. The method further includes determining the last location of the UE based on the received at least one first information header and the at least one second information header.
[0015] In an embodiment, the method further includes storing, in a database, the determined last location of the UE in a call detail record (CDR) of a communication network.
[0016] In some embodiments, the first party and the second party comprise a serving call session control function (SCSCF) module.
[0017] In some embodiments, the at least one notification signal is a bidirectional BYE signal.
[0018] In some embodiments, the at least one first information header comprises a first P-Access-Network-Info (PANI) header and the at least one second information header comprises a second PANI header.
[0019] In an exemplary embodiment, a system for determining the last location of the UE in the communication network during the graceful shutdown is disclosed. The system includes a receiving unit, a first terminal unit, and a second terminal unit. The receiving unit is configured to receive a user request from a user to provide the last location of the UE. The provisioning unit is configured to cooperate with the receiving unit to receive the user request and is further configured to generate at least one notification signal. The first terminal unit is configured to cooperate with the provisioning unit to receive the at least one generated notification signal and is further configured to communicate the received at least one notification signal to a first party and receive at least one first information header corresponding to the UE from the first party. The second terminal unit is configured to cooperate with the provisioning unit to receive the at least one generated notification signal and is further configured to communicate the at least one received notification signal to a second party and to receive at least one second information header from corresponding to the UE the second party. The provisioning unit is further configured to determine the last location of the UE based on the at least one first information header and the at least one second information header.
[0020] In an embodiment, the system includes a database to store the determined last location of the UE in a call detail record (CDR) of the communication network.
[0021] In an exemplary embodiment, a user equipment communicatively coupled with a system in a communication network is disclosed. The coupling comprises steps of receiving, by the system, a connection request. The coupling further comprises sending, by the system, an acknowledgment of the connection request to the user equipment. The coupling comprises transmitting a plurality of signals in response to the connection request, the system is configured for determining a last location of the user equipment in the communication network during a graceful shutdown. The system includes a receiving unit, a first terminal unit, and a second terminal unit. The receiving unit is configured to receive a user request from a user to provide the last location of the UE. The provisioning unit is configured to cooperate with the receiving unit to receive the user request and is further configured to generate at least one notification signal. The first terminal unit is configured to cooperate with the provisioning unit to receive the at least one generated notification signal and is further configured to communicate the received at least one notification signal to a first party and receive at least one first information header corresponding to the UE from the first party. The second terminal unit is configured to cooperate with the provisioning unit to receive the at least one generated notification signal and is further configured to communicate the at least one received notification signal to a second party and to receive at least one second information header corresponding to the UE from the second party. The provisioning unit is further configured to determine the last location of the UE based on the at least one first information header and the at least one second information header.
[0022] 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.
OBJECTIVES
[0023] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0024] An objective of the present disclosure is to provide a system and a method for determining last location of a UE in a call detail record (CDR) during a graceful shutdown.
[0025] Another objective of the present disclosure is to provide a system and a method which determine an accurate position/location of the UE and store in the CDR during the graceful shutdown.
[0026] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0027] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0028] FIG. 1 illustrates an exemplary network architecture for implementing a system for determining a last location of a user equipment (UE) in a communication network during a graceful shutdown, in accordance with embodiments of the present disclosure.
[0029] FIG. 2 illustrates an exemplary architecture of the system for determining the last location of the UE in the communication network during the graceful shutdown, in accordance with embodiments of the present disclosure.
[0030] FIG. 3 illustrates an exemplary block diagram of the system for determining the last location of the UE in the communication network during the graceful shutdown, in accordance with an embodiment of the disclosure.
[0031] FIG. 4 illustrates a flowchart of a method for determining the last location of the UE in the communication network during the graceful shutdown, in accordance with an embodiment of the disclosure.
[0032] FIG. 5 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.
[0033] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100 – Network Architecture
102-1, 102-2…102-N – Users
104-1, 104-2…104-N – User Equipments
106 – Network
200 – System
202 - eNodeB
204 - Serving Gateway (S-GW)
206 - Packet Data Network (PDN) Gateway (P-GW)
208 - Access Session Border Controller (A-SBC)
210 - Breakout Gateway Control Function (BGCF)
212 - Media Gateway Control Function (MGCF)
214 - IBCF (Interconnect Border Control Function)/ ISBC (Interconnect Session Border Controller)
216 - ICSCF (Interconnect Call Session Control Function)
218 - Provisioning Unit
220 - Originating Application Server (Orig-AS) (Second Terminal Unit)
222 - Terminating Application Server (Term-AS) (First Terminating Unit)
230 - SCSCF-Orig module
230A - Input Module of SCSCF-Orig module
230B - Output Module of SCSCF-Orig module
232 - SCSCF-Term module
232A - Input module of SCSCF-Term module
232B - Output module of SCSCF-Term module
302 – Receiving Unit
304 – Memory
306 – A Plurality of Interfaces
310 – Processing Unit
312 – Database
510 – External Storage Device
520 – Bus
530 – Main Memory
540 – Read Only Memory
550 – Mass Storage Device
560 – Communication Port
570 – Processor
DETAILED DESCRIPTION
[0034] In the following description, for the purposes of explanation, various specific details are set forth 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 can each be used independently of one another or with any combination of other features. An individual feature may not address any 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. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0035] 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 function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0036] 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, 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 in order to avoid obscuring the embodiments.
[0037] 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. 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 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.
[0038] The word “exemplary” and/or “demonstrative” is used herein to 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 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.
[0039] 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 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.
[0040] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular 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 features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0041] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0042] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The 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 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 is a hardware processor.
[0043] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and now sixth generation (6G), and more such generations are expected to continue in the forthcoming time.
[0044] Radio Access Technology (RAT) refers to the technology used by mobile devices/ User Equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
[0045] While considerable emphasis has been placed herein on the components and component parts of 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 embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0046] In communication, a graceful shutdown period is essential for maintaining service quality, protecting data, and ensuring that network changes or maintenance activities are carried out effectively and with minimal impact on users. The graceful shutdown period refers to a planned and controlled process of deactivating or rebooting network equipment, such as provider edge (PE) routers, with minimal service disruption. Unlike an abrupt shutdown, which might cause immediate service interruptions or data loss, the graceful shutdown involves a systematic approach to ensure that:
• Active connections or services are handled appropriately, either by transferring them to other operational equipment or providing adequate notice to users.
• Any data in transit or pending transactions are completed or safely stored before shutdown.
• Users experience minimal service disruption, and necessary adjustments are made to redirect their services smoothly during the shutdown.
[0047] During the graceful shutdown period, the provider edge (PE) routers need to be shut down or reset when the maintenance of PE routers in the telecommunication network is planned. During the graceful shutdown, it is crucial to track and manage the transition of active sessions, particularly when the user equipment (UE) is in motion. For instance, consider a scenario where a user, hereafter referred to as "User A," is engaged in an active telephone call while traveling from one geographic location to another. During the shutdown of the PE router currently servicing User A, a significant challenge arises in maintaining the continuity of the call as User A moves to a new location. To address this challenge, the system must accurately determine the last known location of the UE prior to the initiation of the graceful shutdown. This is achieved through the Call Detail Record (CDR) associated with the UE. The CDR contains pertinent data including the UE’s most recent location and session details.
[0048] For example, User A is traveling, and his call is being managed by a specific PE router. As the network administrator initiates the graceful shutdown of this PE router, the system extracts the last recorded location of User A from the CDR. For example, if User A’s last known location is near “Location X” and they are en route to “Location Y,” the network must utilize this information to ensure the uninterrupted continuation of the call.
[0049] Thus, there is a need to determine the last location of the user equipment (UE) during the graceful shutdown, specially when the user is moving from one location to a new location. The last location of the UE in the Call Detail Record (CDR) is used to restore the ongoing call services for the user at the new location during the graceful shutdown. Therefore, determining the last location of the UE during the graceful shutdown is becoming crucial day by day.
[0050] Traditional techniques for determining the accurate last location of the UE during the graceful shutdown are prone to determine an accurate location of the UE. These exhibit limitations in real-time implementations, rendering them inadequate for ensuring precise location tracking and seamless service continuity. Consequently, these traditional approaches are considered inefficient, as they fail to effectively address the challenges associated with maintaining service quality and accurate location tracking during the graceful shutdown of network components.
[0051] Accordingly, there is a need for a system and a method that facilitates an efficient and accurate approach in determining the last location of the UE in the CDR during the graceful shutdown.
[0052] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing an improved system and a method for determining the last location of the UE in the CDR during the graceful shutdown.
[0053] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0054] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (200) for determining a last location of a user equipment (UE) (104) in a communication network (106) during a graceful shutdown, in accordance with embodiments of the present disclosure.
[0055] Referring to FIG. 1, the system (200) is connected to the network (106), which is further connected to one or more user equipments (104-1, 104-2, ... 104-N). A person of ordinary skill in the art will understand that the one or more user equipments may be collectively referred as user equipment 104). One or more users (102-1, 102-2…102-N) may provide one or more requests to the system (200). 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 referred as a user (102).
[0056] In an embodiment, the user equipment (104) may include, but not be limited to, a mobile, a laptop, etc. Further, the user equipment (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. Furthermore, the user equipment (104) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-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.
[0057] In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, Sixth Generation (6G) network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and/or with the system (200). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0058] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0059] In an embodiment, the system (200) is configured to collect, analyze, and share the data received from user equipment 104 via the communication network 106.
[0060] 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, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).
[0061] FIG. 2 illustrates an exemplary architecture of the system (200) for determining the last location of the UE (104) during the graceful shutdown, in accordance with embodiments of the present disclosure.
[0062] In a Long-Term Evolution (LTE) Radio Access Network (RAN), the UE (104) establishes a communication session with an enhanced Node B (eNodeB) (214). The LTE RAN is integrated with an Evolved Packet Core (EPC) network (not explicitly shown in FIG. 1). The EPC network serves as a critical component in managing and controlling radio access within the LTE RAN. The EPC network facilitates various functions critical to mobile communications, including user data management, session management, and network mobility. The EPC network includes various components such as home subscriber server (HSS), serving gateway (S-GW) (204), packet data network (PDN) Gateway (P-GW) (206), and mobility management entity (MME). The HSS is a central database that has been inherited from the Universal Mobile Telecommunications System (UMTS) and the Global System for Mobile Communication (GSM). The HSS serves as a repository for storing critical subscriber-related data. It maintains comprehensive information about all subscribers of the network operator, including user profiles, subscription data, and authentication information.
[0063] The S-GW (204) handles user data traffic between the LTE RAN and a Packet Data Network (PDN). It acts as a gateway that routes and forwards data packets to and from the user equipment (UE) (104). The S-GW (204) also maintains the bearer paths for data sessions and manages user plane functions such as packet buffering and forwarding. The P-GW (206) communicates with the packet data networks using a service gateway interface. For example, the interface is S5 interface or S8 interface. S5 interface carries both user plane and control plane traffic and is used to manage data sessions for users. S8 interface is an extension of the S5 interface. It is used for communication between the S-GW and the P-GW when these elements are in different networks, such as when roaming between different network operators or between a home network and a visited network. The P-GW (206) serves as the interface between the EPC network and external packet data networks, such as the Internet or private networks. It is responsible for providing connectivity to external data networks, enforcing policy control, and managing data session contexts. The P-GW performs functions such as IP address allocation, packet filtering, and Quality of Service (QoS) enforcement. Each PDN is identified by an access point name (APN). The P-GW (206) performs the same role as a gateway general packet radio services (GPRS) support node (GGSN) and the serving GPRS support node (SGSN) with UMTS and GSM. The S-GW (204) acts as a router, and forwards data between the eNodeB (202) and the P-GW (206). In an aspect, the eNodeB (202) and the S-GW (204) are connected with an S1u (S1-U) interface. The S1-U is a reference point between E-UTRAN and the serving GW for the per bearer user plane tunneling and inter eNodeB path switching during handover. The S1-U is for the user plane. The MME controls the high-level operation of the mobile using signaling messages and HSS. The MME handles signaling and control functions related to user mobility, session management, and network access. The MME is responsible for user authentication, bearer path management, and tracking area updates. The MME manages the signaling between the LTE RAN and the EPC network, facilitating efficient handovers, maintaining user sessions, and ensuring proper network access control.
[0064] A Policy and Charging Rule Function (PCRF) is a component that is responsible for policy control decision-making, as well as for controlling the flow-based charging functionalities. The PCRF is tasked with making decisions regarding network policies, such as QoS parameters, service priorities, and access control rules. It evaluates user requests and network conditions to enforce policies that ensure efficient resource utilization and adherence to service agreements. The PCRF also manages charging rules for network services based on data flow. It interacts with the Policy Control Enforcement Function (PCEF) embedded within the P-GW to apply and enforce these charging rules. The decisions of the PCRF are critical in determining how users are billed for network usage, including data consumption, service type, and duration.
[0065] The P-GW (206) interfaces with other packet data networks, e.g., the IMS network. The IMS network is configured to deliver multimedia communications services such as voice, video and text messaging over IP networks and thus is configured to interface with another network node. The P-GW (206) serves as a gateway between the LTE network and external packet data networks, such as the Internet or other IP-based networks. A proxy call session control function (P-CSCF) node acts as an entry point of the IMS network. The UE (104) is registered with the P-CSCF node.
[0066] Within the P-GW 206, the PCEF enforces the charging and policy decisions made by the PCRF. It applies the specified rules to user data flows, ensuring that network policies are adhered to, and that billing is accurately executed according to the defined rules. The IMS network is configured to interface with various network nodes, including the P-GW and UE. This integration ensures seamless communication and interoperability between different network elements and service platforms. The P-CSCF is the initial contact point for the UE when establishing a session or initiating a call within the IMS network. It handles signaling messages, session establishment, and routing of communications to appropriate network nodes. The UE (104) must be registered with the P-CSCF to access IMS services. The registration process ensures that the IMS network recognizes the UE and can participate in multimedia communications.
[0067] Within the IMS network, several types of session initiation protocol (SIP) servers, known as CSCF, are used to process SIP signaling packets in the IMS network domain. The CSCF are responsible for SIP session control, user authentication, call routing, and controlling the generation of call detail records (CDRs). The P-CSCF receives and processes registration requests from the UE (104) and then forwards them to the Interrogating Call Session Control Function (I-CSCF). The P-CSCF also directs SIP signaling messages to the Serving Call Session Control Function (SCSCF). Upon receiving the INVITE request from an originating UE, the P-CSCF includes the user location and/or UE Time Zone and/or User Closed Subscriber Group (CSG) information obtained from the access network in the PANI header and sends the INVITE request towards the next hop. Further, upon receiving the ACK request from the originating UE, the P-CSCF inserts the user location and/or UE Time Zone and/or User CSG information provided by the access network in the response confirmation, and this is routed towards the terminating side. The P-CSCF includes the user location and/or UE Time Zone and/or User CSG information obtained from the access network in the PANI header and sends the BYE request towards the next hop. Upon receiving the SIP response from originating UE, the P-CSCF inserts the user location and/or UE Time Zone and/or User CSG information obtained from the access network into the response and send the response towards the next CSCF.
[0068] The P-CSCF resides in an access session border controller (A-SBC) (208) that is a network function that secures voice over IP (VoIP) infrastructures. The P-GW 206 may be configured to couple with the A-SBC (208) using Sgi/Gm interface or reference point. The SGi interface transports the User plane data from the UEs towards IMS as well as other application functions. The SGi reference point, performs User plane generic IP interfacing, breaking out the user IP data from the EPC plane towards the application functions (IMS, Internet, etc.). The Gm reference point represents the 1st hop in SIP signalling between the UE and the IMS network represented by the P-CSCF. The Gm reference point provides a secure SIP signalling channel, independent of the access network level security. In an aspect, the A-SBC (208) is configured to communicate with the at least one SCSCF module (230, 232) using a Mw reference point. The Mw reference point allows the communication and forwarding of signalling messaging between the CSCFs, e.g. during registration and session control. The A-SBC acts as the entry point for SIP messages from external networks and ensures that the communications are secure and correctly formatted. The A-SBC also manages the interworking of incompatible signaling messages and media flows between end devices or application servers (AS) and the IMS network.
[0069] The I-CSCF (216) serves as an intermediary that interrogates the HSS to determine the address of the appropriate SCSCF for handling a given SIP initiation request. It ensures that the request is routed to the correct SCSCF based on subscriber information and network configuration. The I-CSCF (216) interconnects with an interconnect session border controller (I-SBC) (214) that addresses the boundary requirements where network service provides interconnect and exchange inbound and outbound SIP sessions. The I-CSCF (216) addresses the signaling and media flow requirements between different networks and facilitates inbound and outbound SIP sessions. The I-CSCF (216) also integrates with the Interconnect Border Control Function (IBCF), Inter-working Function (IWF), and Transition Gateway (TrGW) for seamless interoperability and connectivity. The I-CSCF (216) interconnects with the I-SBC (214) using an Mx reference point that allows the communication and forwarding of signalling messages between a CSCF/BGCF and the IBCF, e.g. during session establishment.
[0070] The I-SBC addresses the signaling and media boundary requirements at the points where different network service providers interconnect. The I-SBC facilitates the exchange of inbound and outbound SIP sessions between interconnecting networks, ensuring compatibility and managing the flow of signaling and media traffic. The IBCF provides control over the border between different network domains, managing the flow of SIP signaling and ensuring the adherence to network policies and security protocols. The IWF is responsible for translating and adapting signaling messages and media flows between different protocols and network domains. It ensures interoperability between diverse network technologies and enables seamless communication across different network infrastructures. The TrGW manages the transition between different types of network technologies or service platforms. It handles the adaptation and integration of services as they move between different network environments, ensuring continuity and consistency of service. The SCSCF is the central node within the signaling plane of the IMS network. The SCSCF handles SIP registrations from mobile users, processing SIP signaling for session management, and routing calls based on policy and user profiles. The SCSCF performs critical functions such as call routing, session establishment, and maintaining user session states.
[0071] A Breakout Gateway Control Function (BGCF) (210) is a SIP proxy server that includes routing functionality based on mobile customer telephone numbers. The BGCF (210) provides breakout functionality in the IMS network which allows communication between different networks, such as a packet-switched (PS) network and a circuit-switched (CS) network. The BGCF (210) determines the next hop for routing the SIP message. This determination may be based on information received in the signalling protocol, administrative information, and/or database access. For PSTN /CS (Circuit Switched) Domain terminations, the BGCF (210) determines the network in which PSTN/CS Domain breakout is to occur and within the network where the breakout is to occur, the BGCF (210) selects the MGCF. In an aspect, the BGCF (210) is connected to the at least one SCSCF module (230) using a reference point (Mi). The reference point (Mi) allows the Serving CSCF (SCSCF module) to forward the session signalling to the BGCF (210) for the purpose of interworking to the circuit switched networks.
[0072] The BGCF (210) analyzes incoming SIP requests and determines the appropriate network to route the call. For instance, when a call is intended for a destination in the circuit-switched network, the BGCF (210) ensures that the call is routed correctly to that network. The BGCF (210) is used for routing calls from the IMS network to a phone in the CS network, e.g., the public switched telephone network (PSTN) or public land mobile network (PLMN). The BGCF (210) forwards the signaling to the selected PSTN/PLMN network with the help of a media gateway control function (MGCF) (212). In an aspect, the BGCF (210) is connected to the MGCF (212) using a reference point (Mj). The reference point (Mj) allows the BGCF (210) to exchange session signalling message with the MGCF (212) for the purpose of interworking to the circuit switched networks, or for transit scenarios. The MGCF (212) is a network element that interfaces between the IMS network and circuit-switched networks. The MGCF (212) acts as a gateway to the PSTN/CS network over the IMS network. The MGCF is responsible for handling the media path and ensuring proper connectivity and media flow between the two network domains. The MGCF works in conjunction with the BGCF to facilitate the breakout of calls from the IMS network to external networks. The BGCF forwards signaling messages to the MGCF, establishing and maintaining the call connection with the circuit-switched network (106).
[0073] In an implementation, to determine the last location of the UE (104) in the CDR during the graceful shutdown, a notification signal is generated by at least one SCSCF module (230, 232) of a provisioning unit (218).
[0074] In an aspect, the notification signal ensures that accurate location information is recorded in the CDRs even if the network is undergoing the graceful shutdown. This helps in maintaining accurate records and facilitates proper tracking of the UE's last known location. In an example, the notification signal is a BYE signal. In an example, the BYE signal is a SIP message used to indicate the termination of an active SIP session or call. In an aspect, the SIP BYE message is used in both normal and abnormal session termination cases. When a session is no longer needed or needs to be ended, the BYE message is sent to all parties involved in the call to signal that the session should be terminated. The BYE signal may trigger the updating of CDRs to reflect the termination of the session and capture the final status or location of the UE before the shutdown. Upon receiving the BYE signal, the network components involved in the session will terminate the session and perform any necessary cleanup activities. Additionally, the provisioning unit or other network elements may update the CDRs to reflect the accurate status and final location of the UE (104) as recorded during the session termination.
[0075] As shown in FIG. 2, the provisioning unit (218) includes two SCSCF modules (230, 232) named as a SCSCF-Orig module (230) and a SCSCF-Term module (232) respectively.
[0076] The SCSCF-Orig module (230) is designated as the "Originating" SCSCF in the network architecture. It primarily handles the session control functions associated with the initiating side of a call or session. In an embodiment, the SCSCF-Orig module (230) serves as a first party (A-party), and the SCSCF-Term module (232) serves as a second party (B-party). In an example, the SCSCF-Orig module (230) includes an input module (230A) and an output module (230B). The input module (230A) receives and processes incoming SIP signaling messages from the network or user equipment (UE). It manages the initiation and setup of SIP sessions by analyzing and interpreting the incoming requests. The input module (230A) facilitates the reception of requests related to call establishment, registration, and other session initiation activities. The output module (230B) is configured to generate and send the SIP signaling responses and messages to other network entities or UE. The output module (230B) ensures that the responses to incoming requests are properly formatted and transmitted. The output module (230B) manages the delivery of SIP responses and session control messages, facilitating communication with other network components.
[0077] The SCSCF-Term module (232) functions as the "Terminating" SCSCF. The SCSCF-Term module (232) manages the session control functions related to the receiving or terminating side of a call or session. For example, the SCSCF-Term module (232) includes an input module (232A) and an output module (232B). The input module (232A) receives SIP signaling messages from the network or UE related to the termination or management of ongoing sessions. The output module (232B) generates and sends SIP signaling messages related to the termination of sessions. The output module (232B) ensures that termination messages, such as BYE signals, are properly formatted and transmitted to the relevant network entities or UE. In an example, the SCSCF-Term module (232) is configured to transmit the generated BYE signal to a first terminal unit (Term-AS) (222) and a second terminal unit (Orig-AS) (220). In an example, the first terminal unit (Term-AS) (222) is a converged telephony application server (CTAS). In another example, the second terminal unit (Orig-AS (220)) is the CTAS. In an aspect, the CTAS may insert a P-Access-Network-Info (PANI) header field in a message transmitted to the CSCF. The PANI header contains information about the access network that a user's handset is using to connect to the internet. The CSCF or CTAS may then use the information in the PANI header to retrieve user-related information.
[0078] In an operative aspect, the SCSCF-Term module (232) is configured to generate the BYE signal and communicate with the SCSCF-Orig module (230). The input module (232A) of the SCSCF-Term module (232) is configured to communicate the BYE signal (as shown in FIG. 2, an outgoing direction) towards the first party (A-party). In an example, the input module (232A) of the SCSCF-Term module (232) is configured to transmit the generated BYE signal towards the Orig-AS (220) and the Term-AS (222). The first terminal unit (the Term-AS (222)) is configured to receive the at least one generated notification signal (generated BYE signal) and is further configured to communicate the received at least one notification signal to the first party (SCSCF-Orig module (230). The first terminal unit (the Term-AS (222)) is configured to receive at least one first information header corresponding to the UE from the first party. In some embodiments, the at least one first information header includes a first P-Access-Network-Info (PANI) header. By sending the BYE signal to the SCSCF-Orig module (230) ensures that the initiating side of the session is notified of the termination. This communication is essential for proper session teardown and ensuring that all involved network components are updated about the session's end. The input module (232A) of the SCSCF-Term module (232) is specifically configured to handle the outgoing BYE signal. The input module (232A) is responsible for transmitting this signal towards the Orig-AS (220) and Term-AS (222), which are key network entities involved in the session. The BYE signal is transmitted to ensure proper delivery and reception by the destination network elements. This includes encapsulating the signal with appropriate headers and routing it through the network. Upon receiving the BYE signal from the SCSCF-Term module (232), the Orig-AS (220) assumes that the signal originates from the B-party (i.e., the terminating party). The Orig-AS (220) is configured to wait for a response message after receiving the BYE signal. This response is crucial for confirming the termination and completing all necessary procedures.
[0079] The second terminal unit is configured to cooperate with the provisioning unit to receive the at least one generated notification signal and is further configured to communicate the at least one received notification signal to a second party and to receive at least one second information header corresponding to the UE from the second party. In some embodiments, the at least one second information header includes a second PANI header.
[0080] In such a condition, Orig-AS (220) assumes that the received BYE signal is coming from the B-party and waits for at least a response message. In an example, the at least one response message is a P-Access-Network-Info (PANI) header (second information header). The PANI header is a specialized SIP header used primarily in the context of IMS (IP Multimedia Subsystem) networks to provide additional information about the network access environment of the UE. The PANI header provides additional information about the access network used by the UE during the session. The PANI header is used to convey network access information and helps in accurately updating the session records and CDRs. The PANI header is part of the response that confirms the receipt and processing of the BYE signal. The PANI header carries information about the access network used by the UE to establish and maintain a session. This information includes details about the type of network and the specific access technologies involved. The PANI header typically includes one or more fields that describe the access network attributes. The specific fields and formats are defined by relevant standards and specifications for IMS networks.
[0081] In an operative aspect, the output module (230B) of the SCSCF-Orig module (230) is configured to generate the BYE signal (as shown in an outgoing direction) from the output module (230B) towards the Orig-AS (220). In an example, the output module (230B) of the SCSCF-Orig module (230) is configured to transmit the generated BYE signal towards the Orig-AS (220) and the Term-AS (222). In an aspect, the first party (A-party) 230 and the Orig-AS (220) may be configured to provide a number of services (for example S1, S2) to each other. In an example, the S1 represents service 1, and S1 represents service 2. The first party (A-party) 230 and the Orig-AS (220) may be configured to exchange a number of dialogues (D1, D2) over an ISC (IMS Service Control) interface to provide the services. In an example, the D1 denotes dialogue 1 and D2 denotes dialogue 2.
[0082] In such condition, the Term-AS (222) assumes that the received BYE signal is coming from the first party (A-party) 230 and waits for at least a response message. In an example, the at least one response message is a first P-Access-Network-Info (PANI) header (first information header).
[0083] In an aspect, each of the received first PANI header and the second PANI header includes at least a location of the UE (104) during the calling session. The Term-AS (222) and Orig-AS (220) are configured to determine the correct last location of the UE (104) based on the received first PANI header and the second PANI header. The correct last location of the UE (104) gets stored in the CDR for resuming the ongoing call services of the user. In an aspect, the received first PANI header includes at least a location of the UE (104) during the calling session (may be service S2). In an aspect, the received second PANI header includes at least a location of the UE (104) during the other calling session (may be service S1). In an example, the first PANI header for Service S2 contains a PANI-ID of 12345, indicating that the UE was located at Latitude X and Longitude Y (place Z) on October 1, 2024, at 10:00:00 UTC, with a session ID of S2-XYZ. In contrast, the second PANI header for Service S1 has a PANI-ID of 67890, showing that the UE was located at Latitude P and Longitude Q (place Y) on the same day, October 1, 2024, at 14:30:00 UTC, with a session ID of S1-ABC. In an aspect, the operator may be able to determine an exact location of the UE by analyzing the first PANI header and the second PANI header. The Term-AS (222) and Orig-AS (220) utilize this information to determine the most recent location of the UE, which is Y, based on the Second PANI Header's later timestamp. This location data is then stored in the CD) to ensure seamless continuity in the ongoing call services.
[0084] The Term-AS (222) and the Orig-AS (220) use the location information from the PANI header to determine the exact last known location of the UE (104). This helps ensure that the user's location is accurately recorded and managed even as the session transitions or is terminated. The Term-AS (222) processes session termination requests and manages related operations. It uses the information in the PANI header to update the session details, including the last known location of the UE (104). During session termination or network interactions, the Term-AS (222) integrates the location data from the PANI header to maintain accurate records of where the UE was situated.
[0085] The Orig-AS (220) handles the initial setup and management of the session. It also relies on the PANI header to record and process location information, particularly when establishing or updating session details. The Orig-AS (220) ensures that the location data provided in the PANI header is used to maintain accurate and up-to-date session information, which is crucial for managing user sessions effectively.
[0086] The correct last location of the UE (104), as determined from the PANI header, is stored in the CDRs. This record includes comprehensive details about the session, including the user's final location. Storing accurate location information in CDRs is essential for various operational aspects, such as billing, customer service, and network management. It also ensures that ongoing call services can be resumed or managed correctly if the user transitions between different network states or locations. By maintaining the correct location data in the CDRs, the network can facilitate the resumption of ongoing call services or manage user mobility more effectively. This ensures continuity of service and accurate billing or service provision based on the user's last known location.
[0087] The provisioning unit (218) determines the last known location of the UE (104) during or after a calling session. The first information header may refer to the header or another SIP header that provides specific details about the network access or session context. The first information header contains vital information such as the network type and access technology used by the UE (104). The second information header may include additional contextual data relevant to the session. The second information header might be a SIP header that contains details such as the location or identification of the network access point or any other relevant session information.
[0088] The provisioning unit (218) receives at least one first information header and at least one second information header as part of the session signaling or communication process. These headers provide detailed information about the session and network conditions. In an aspect, the provisioning unit (218) parses the received headers to extract relevant data. This involves identifying and retrieving specific pieces of information related to the UE’s location and network access. The extracted information is analyzed to determine the UE’s last known location. This involves correlating data from both the first and second information headers to establish a comprehensive view of the UE's location and network context. In an example, the provisioning unit (218) integrates the information from the first and second headers to accurately determine the UE’s location. For example, the PANI header provides network access details, while the second header might offer location coordinates or other relevant data. The integrated information is validated to ensure accuracy. This might involve cross-referencing with other network records or data sources to confirm the UE's last known location. The determined last location of the UE (104) is stored in the CDRs. The recorded location helps in resuming or managing ongoing call services. If the UE (104) transitions between different network states or locations, the stored location data ensures seamless service continuity and accurate session handling.
[0089] In an embodiment, the capturing the last user location information and/or UE Time Zone of one specific party (originating or terminating) at session release is required by operator (e.g. for legal purpose), and such information is not available at the time the SIP BYE is received, a CTF (Charging Trigger Function) shall delay the Debit / Reserve Units Request until the reception of SIP 200 OK acknowledging the SIP BYE. Otherwise, the CTF shall trigger Debit / Reserve Units Request once the SIP BYE request has been received. SIP 200 OK acknowledging a SIP BYE message (only when last user location information of originating/ terminating party is required by operator for legal purpose).
[0090] In another embodiment, the SIP session is released by receiving a SIP BYE message. The S-CSCF forwards the SIP BYE message to the IMS-GWF (IMS Gateway Function) /AS (Application Server) (for example, Orig-AS (220), Term-AS (222)). Upon receiving the SIP BYE message, the IMS-GWF/AS forwards the SIP BYE request to the UE. In case there is an ongoing online control session, and the IMS-GWF/AS is configured to wait for SIP 200 OK acknowledging SIP BYE, the counter of used granted units is stopped. The release is acknowledged by SIP 200 OK forwarded to the IMS-GWF/AS by the S-CSCF.
[0091] In case there is an ongoing online control session, the IMS-GWF/AS sends a Reserve Units Request [Terminate] reporting charging information (e.g. user location received in SIP 200 OK) together with the used granted units. The OCS sends a Reserve Units Response. The online Credit-Control session is terminated. The final SIP 200 OK answer to the SIP BYE message is forwarded.
[0092] FIG. 3 illustrates an exemplary block diagram (300) of the system (200) for determining the last location of the UE in the communication network during the graceful shutdown, in accordance with an embodiment of the disclosure.
[0093] As shown in FIG. 3, the system (200) includes various modules and components, such as a receiving unit (302), a memory (304), the provisioning unit (218), and a processing unit (310), in accordance with embodiments of the present disclosure.
[0094] The receiving unit (302) is configured to receive a user request from a user to provide the last location of the UE. For example, the receiving unit (302) is a user interfacing unit, facilitating interaction between the user and the system. In an aspect, the system (200) is configured to transfer the last location of the UE in the communication network during the graceful shutdown. For example, the user request may include details such as the user device’s identification (e.g., IMEI (International Mobile Equipment Identity) number) and the purpose of the request (e.g., to obtain the last known location of the UE during the graceful shutdown process).
[0095] The processing unit (310) is configured to cooperate with the receiving unit (302) and receive the request. Upon receiving the request, the processing unit (310) establishes a connection with the provisioning unit (218). The processing unit (310) actively collaborates with the receiving unit to confirm the details of the user request, ensuring that all necessary parameters (such as the IMEI number) are accurately specified. Upon receiving the user request, the processing unit (310) is configured to generate at least one notification signal. In an example, the at least one generated notification signal is the bidirectional BYE signal.
[0096] The first terminal unit (Term-AS) (222) is configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal. The first terminal unit (Term-AS) (222) is further configured to communicate the received at least one notification signal to the first party (230). The first terminal unit (Term-AS) (222) receives the at least one first information header corresponding to the UE from the first party (230). In some embodiments, the at least one first information header comprises the first PANI header.
[0097] In an aspect, the first party (230) includes a serving call session control function (SCSCF) module.
[0098] The second terminal unit (Orig-AS) (220) is configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal. The second terminal unit (Orig-AS) (220) is further configured to communicate the at least one received notification signal to the second party (232). The second terminal unit (Orig-AS) (220) receives the at least one second information header corresponding to the UE from the second party (232). In an aspect, the second party (232) includes a serving call session control function (SCSCF) module.
[0099] The provisioning unit (218) is further configured to determine the last location of the UE based on the at least one first information header and the at least one second information header.
[00100] The processing unit (310) is configured to fetch and execute computer-readable instructions stored in the memory 304. The processing unit (310) may be implemented as microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. The processing unit (310) may be configured to fetch and execute computer-readable instructions stored in the memory 304 of the system (200). The memory 304 may store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed for determining the last location of the UE in the communication network during the graceful shutdown. The memory 304 may comprise 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.
[00101] Referring to FIG. 3, the system (200) may include various input output (I/O) interface(s) 306. The interface(s) 306 may comprise a variety of interfaces, such as interfaces for data input and output devices (I/O devices), storage devices, and the like. The interface(s) 306 may facilitate communication to/from the system (200) and provide a communication pathway for one or more components of the system (200). Examples of such components include, but are not limited to, the processing unit (310), other modules, and a database 312.
[00102] In an embodiment, the database 312 may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processing unit (310) or the system (200). The database 312 may store the determined last location of the UE in a call detail record (CDR) of the communication network. In an embodiment, the database 312 may be separate from the system (200).
[00103] In an exemplary embodiment, the present discloser discloses a user equipment that is communicatively coupled with the system in the communication network. The coupling comprises steps of receiving, by the system, a connection request. The coupling further comprises sending, by the system, an acknowledgment of the connection request to the user equipment. The coupling comprises transmitting a plurality of signals in response to the connection request, the system is configured for determining the last location of the user equipment in the communication network during a graceful shutdown.
[00104] FIG. 4 illustrates a flowchart of a method (400) for determining the last location of the UE in the communication network during the graceful shutdown, in accordance with an embodiment of the disclosure.
[00105] At step (402), the receiving unit (302) receives a request from a user for determining the last location of the UE (104). In an aspect, the user is an operator, law enforcement authority, or a network service provider. This request might be initiated due to various needs such as network management, user service requests, or regulatory compliance. The receiving unit (302) processes the user request to initiate the location determination procedure.
[00106] At step (404), responsive to receiving the user request, the provisioning unit (218) generates at least one notification signal. This signal is meant for delivery to two distinct terminal units: a first terminal unit and a second terminal unit. The notification signal informs these units about the shutdown and the need to gather location information. In an embodiment, this notification signal is a bidirectional BYE signal, which is commonly used to signal the termination of a session or communication. The BYE signal indicates that the shutdown process has started and requests the relevant parties to prepare for or respond to the shutdown.
[00107] At step (406), the first terminal unit receives the notification signal generated by the provisioning unit (218). The first terminal unit (Term-AS) (222) is configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal. The first terminal unit (Term-AS) (222) is further configured to communicate the received at least one notification signal to the first party (230). The first terminal unit (Term-AS) (222) is a converged telephony application server (CTAS). The first terminal unit (Term-AS) (222) may be a network entity responsible for managing or overseeing the UE’s communication sessions, such as a network node or a specific service component involved in the shutdown process. In an aspect, the first party (230) comprises a serving call session control function (SCSCF) module.
[00108] At step (408), the first terminal unit (Term-AS) (222) receives the at least one first information header corresponding to the UE from the first party (230). In an aspect, the at least one first information header includes the first PANI header. The at least one first information header contains details relevant to the shutdown and the location of the UE. It provides data for identifying the UE’s last known activity or session state, which is crucial for accurate location determination.
[00109] At step (410), the second terminal unit (Orig-AS) (220) is configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal. The second terminal unit (Orig-AS) (220) is further configured to communicate the at least one received notification signal to the second party (232). In an aspect, the second party (232) comprises a serving call session control function (SCSCF) module, which manages the signaling and control of communication sessions. This step ensures that the SCSCF module and other involved entities are notified about the shutdown and are able to participate in the location determination process.
[00110] At step (412), the second terminal unit receives the at least one second information header corresponding to the UE from the second party (232) in response to the notification signal. In an aspect, the at least one second information header comprises the second PANI header. The at least one second information header provides additional data necessary for determining the UE’s final location, contributing to the comprehensive understanding of the UE’s last known state within the network.
[00111] At step (414), using information headers (the at least one first information header and the at least one second information header) received from both the first terminal unit and the second terminal unit, the provisioning unit (218) determines the final location of the UE (104). The information headers may include the PANI header, which contains detailed network access and location information. By analyzing these headers, the provisioning unit (218) can accurately determine the last known location of the UE within the communication network.
[00112] In an embodiment, the method involves storing the determined final location of the UE (104) within the CDR of the communication network in the database.
[00113] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented.
[00114] As shown in FIG. 5, the computer system may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port 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 port(s) (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[00115] The main memory (530) may be random-access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device (550) includes, but is 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 Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[00116] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.
[00117] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[00118] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
[00119] The present disclosure provides technical advancement related to network management and user location tracking. This advancement addresses the limitations of existing solutions by ensuring the accurate recording of a user’s last known location, even during a graceful shutdown scenario caused by the network components. The disclosure involves a method for correcting location data in Call Detail Records (CDRs) that would otherwise be inaccurate in such shutdown cases. These inventive aspects significantly improve the accuracy and reliability of user location information. The present system/method enhances the integrity of location data reporting, resulting in more precise location tracking and improved network management.
TECHNICAL ADVANTAGES
[00120] As is evident from the above, the present disclosure provides a technically advanced solution by providing a system and a method for determining last location of a user equipment (UE) (102) in call detail record (CDR) during a graceful shutdown.
[00121] In an implementation, the SCSCF-Term module (232) is configured to generate the BYE signal and communicate towards a first terminal unit (Term-AS) (222) and towards the SCSCF-Orig module (230). The output module (230B) of the SCSCF-Orig module (230) is configured to communicate the BYE signal in an outgoing direction (S1 interface) towards the A-party. The input module (232A) of the SCSCF-Term module (232) is configured to transmit the generated BYE signal towards the Orig-AS (220) and the Term-AS (222). The Term-AS (222) assumes that the received BYE signal is coming from the A-party and waits for at least a response message. In an example, the at least one response message is a P-Access-Network-Info (PANI) header.
[00122] In a similar way, the Orig-AS (220) assumes that the received BYE signal is coming from B-party and waits for at least a response message. In an example, the at least one response message is a P-Access-Network-Info (PANI) header.
[00123] The Term-AS (222) and Orig-AS (220) is configured to determine the correct last location of the UE (104) based on the received PANI header. The correct last location of the UE (104) get stored in the CDR for resuming the ongoing call services of the user.
[00124] Thus, the present invention provides a simplified and an efficient solution for accurately determining the last location of the UE (104) during the graceful shutdown. Therefore, the overall reliability the telecommunication network will be increased.
,CLAIMS:Claims
We claim:
1. A method (400) for determining a last location of a user equipment (UE) (104) in a communication network (106) during a graceful shutdown, the method (400) comprising:
receiving (402), by a receiving unit (302), a user request to provide the last location of the UE (104);
responsive to receiving the user request, generating (404), by a provisioning unit (218), at least one notification signal to be received at a first terminal unit (222) and a second terminal unit (220);
communicating (406), by the first terminal unit (222), the received at least one notification signal to a first party (230);
receiving (408), by the first terminal unit (222), at least one first information header corresponding to the UE (104) from the first party (230);
communicating (410), by the second terminal unit (220), the at least one received notification signal to a second party (232);
receiving (412), by the second terminal unit (220), at least one second information header corresponding to the UE (104) from the second party (232); and
determining (414), by the provisioning unit (218), the last location of the UE (104) based on the at least one first information header and the at least one second information header.

2. The method (400) as claimed in claim 1, further comprising storing, in a database (312), the determined last location of the UE (104) in a call detail record (CDR) of the communication network (106).

3. The method (400) as claimed in claim 1, wherein the first party (230) and the second party (232) comprise a serving call session control function (SCSCF) module.

4. The method (400) as claimed in claim 1, wherein the at least one notification signal is a bidirectional BYE signal.

5. The method (400) as claimed in claim 1, wherein the at least one first information header comprises a first P-Access-Network-Info (PANI) header and the at least one second information header comprises a second PANI header.

6. A system (200) for determining a last location of a user equipment (UE) (104) in a communication network (106) during a graceful shutdown, the system (200) comprising:
a receiving unit (302) configured to receive a user request to provide the last location of the UE (104);
a provisioning unit (218) configured to cooperate with the receiving unit (302) to receive the user request and is further configured to generate at least one notification signal;
a first terminal unit (222) configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal and is further configured to:
communicate the received at least one notification signal to a first party (230); and
receive at least one first information header corresponding to the UE (104) from the first party (230); and
a second terminal unit (220) configured to cooperate with the provisioning unit (218) to receive the at least one generated notification signal and is further configured to:
communicate the at least one received notification signal to a second party (232); and
receive at least one second information header corresponding to the UE (104) from the second party (232);
wherein the provisioning unit (218) is further configured to determine the last location of the UE (104) based on the at least one first information header and the at least one second information header.

7. The system (200) as claimed in claim 6, includes a database (312) to store the determined last location of the UE (104) in a call detail record (CDR) of the communication network (106).

8. The system (200) as claimed in claim 6, wherein the first party (230) and the second party (232) comprise a serving call session control function (SCSCF) module.

9. The system (200) as claimed in claim 6, wherein the at least one notification signal is a bidirectional BYE signal.

10. The system (200) as claimed in claim 6, wherein the at least one first information header comprises a first P-Access-Network-Info (PANI) header and the at least one second information header comprises a second PANI header.

11. A user equipment (104) communicatively coupled with a system (200) in a communication network (106), the coupling comprises steps of:
receiving, by the system (200), a connection request;
sending, by the system (200), an acknowledgment of the connection request to the user equipment (104); and
transmitting a plurality of signals in response to the connection request, wherein the system (200) is configured for determining a last location of the user equipment (UE) (104) in the communication network (106) during a graceful shutdown as claimed in claim 6.