Integrating satellite navigation signal assisted GNSS framework in network and user equipment

Abstract

The present disclosure introduces a method (1100) for a user equipment (UE) (102). The UE (102) is configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite. The method (1100) includes receiving (1102) a request to provide Global Navigation Satellite System (GNSS) capability information from a location server. The method (1100) includes providing (1104) the GNSS capability information including NavIC capability information to the location server. The NavIC capability information comprises location information corresponding to the UE. The method (1100) includes sending (1106) a request for assistance data to the location server. Further, the method (1100) includes receiving (1108) the assistance data from the location server. The assistance data is selected from at least one of: NavIC L1 almanac data, NavIC L1 ephemeris data, NavIC L1 ionospheric error data, NavIC L1 clock data, or NavIC L1 orbit data.

Description

INTEGRATING SATELLITE NAVIGATION SIGNAL ASSISTED GNSSFRAMEWORK IN NETWORK AND USER EQUIPMENTRESERVATION 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 (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF PRESENT DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to a field of communication systems, and specifically to a system and a method for integrating navigation communication.BACKGROUND OF PRESENT DISCLOSURE

[0003] 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.

[0004] In the 5thGeneration (5G) era, Global Navigation Satellite System (GNSS) integrity now extends to critical fields such as rail and maritime transportation, Unmanned Autonomous Vehicles (UAVs), autonomous driving, and Vehicle-To-Anything (V2X) communications to reduce safety risks, prevent accidents, and avoid erroneous legal decisions that could lead to liability issues. GNSS integrity has become equally essential for other mission-critical applications where positioning errors could cause harm, including emergency response services, electronic health (e-health), and various industrial Internet of Things (loT) scenarios.

[0005] Each use case involves specific integrity requirements based on different metrics. Integrity Risk (IR) measures the probability that the position error exceeds theallowed limit without triggering an alarm. The Alert Limit (AL) defines the maximum permissible position error for the application, while Time to Alert (TTA) specifies the duration that a position error may exceed the alert limit before an alarm must be raised. By meeting these integrity requirements, GNSS can support safer and more reliable positioning across applications that depend on precise, error-free location data.

[0006] There is, therefore, a need in the art to provide an improved mechanism by overcoming the deficiencies of the prior art(s).OBJECTS OF PRESENT DISCLOSURE

[0007] This section is provided to introduce certain objects and 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 object of the present disclosure relates to a system and a method for integrating Navigation with Indian Constellation (NavIC) LI band assistance in 5thGeneration (5G) and 4thGeneration (4G) cellular networks and User Equipment (UE).

[0009] An object of the present disclosure relates to a method for UE capability indication of NavIC LI SPS message decoding capability for 5G NR and 4G LTE devices. The method includes, including NavIC LI capability information in the normative work of cellular network positioning specifications and ensuring that the capability information is compatible with existing GNSS assistance data configuration mechanisms.

[0010] Another object of the present disclosure relates to a method for UE capability indication of GNSS positioning Ionospheric correction neQuick2 model support capability for 5G NR and 4G LTE devices. Further, the method includes including neQuick2 capability information in the normative work of cellular network positioning specifications and ensuring that the capability information is compatible with existing GNSS assistance data configuration mechanisms.

[0011] Yet another object of the present disclosure relates to a method for UE capability indication of NavIC LI specific clock model support capability for 5G NR and 4G LTE devices. Further, the method includes, including NavIC LI Clock model2 capability information in the normative work of cellular network LPP positioning specifications and ensuring that the capability information is compatible with existing GNSS assistance data configuration mechanisms.

[0012] Yet another object of the present disclosure relates to a method for integrating NavIC LI updated Ionospheric correction Klobuchar model assistance in cellular network positioning specifications. The method includes incorporating NavIC LI Klobuchar model assistance data into LPP positioning protocol specifications and extending existing A-GNSS assistance data configuration mechanisms to support NavIC LI SPS signals.

[0013] Yet another object of the present disclosure relates to a method for integrating NavIC LI new Ionospheric correction NeQuick model assistance in cellular network positioning specifications. Further, the method includes incorporating NavIC LI new NeQuick model assistance data into LPP positioning protocol specifications and extending existing A-GNSS assistance data configuration mechanisms to support NavIC LI band signals.

[0014] Yet another object of the present disclosure relates to a method for integrating new NavIC LI specific Clock model assistance in cellular network positioning specifications. Further, the method includes incorporating NavIC LI clock model assistance data into LPP positioning protocol specifications and extending existing A-GNSS assistance data configuration mechanisms to support NavIC LI band signals

[0015] Yet another object of the present disclosure relates to a method for integrating new NavIC LI Almanac model assistance in cellular network positioning specifications. Further, the method includes incorporating new NavIC LI Almanac model assistance data into LPP positioning protocol specifications and extending existing A-GNSS assistance data configuration mechanisms to support NavIC LI band signals.

[0016] Yet another object of the present disclosure relates to a method for updating existing NavIC GridModel to NavIC LI timing information in cellular network positioning specifications. Further, the method includes incorporating NavIC LI ITOW and TOI timing parameters into existing NavIC GridModel IE under LPP positioning protocol specifications and extending existing A-GNSS assistance data configuration mechanisms to support NavIC LI band signals.SUMMARY

[0017] An aspect of the present disclosure relates to a user equipment (UE) configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite. The UE may include a memory that stores an instruction. The UE may include a processor that is configured to execute the instruction stored in the memory to receive, from a location server, a request to provide Global Navigation Satellite System (GNSS) capabilityinformation. The processor may provide, to the location server, the GNSS capability information including NavIC capability information. The NavIC capability information includes location information corresponding to the UE. The processor may send, to the location server, a request for assistance data. Further, the processor may receive, from the location server, the assistance data. The assistance data is selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

[0018] In an embodiment, the location information may include at least one of a location parameter or a location measurement corresponding to the UE.

[0019] In an embodiment, the GNSS capability information may include at least one of: a positioning type, a band of GNSS support, an ionospheric model supported by the UE, navigation data supported by the UE, or Almanac supported by the UE.

[0020] In an embodiment, the UE may be configured to be operatively connected with the location server via a cellular network.

[0021] In an embodiment, the location server may include at least one of: an Evolved Serving Mobile Location Center (E-SMLC) server, a Location Management Function (LMF) server, or a Secure User Plane for Location (SUPL) Location Platform (SLP).

[0022] In an embodiment, the UE may be configured to communicate with a NavIC receiver, the NavIC receiver being configured to communicate with a base station that forms part of a wireless network through a New Radio Positioning Protocol A (NRPPa). The NavIC receiver may receive location related information from the base station using the NRPPa.

[0023] In an embodiment, the base station may communicate with the UE through at least one of: a Long Term Evolution (LTE) network or a New Radio (NR) network.

[0024] In an embodiment, the NavIC capability information may include NavIC LI frequency band reception capability information of the UE.

[0025] In an embodiment, the NavIC capability information includes a NavIC LI frequency band information included in GNSS-FrequencylD information element (IE).

[0026] In an embodiment, the NavIC capability information may include a NavIC L 1 frequency band included in GNSS-SignallD IE.

[0027] An aspect of the present disclosure relates to a method for a user equipment (UE). The UE is configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite. The method may include receiving, from a location server, a request to provide Global Navigation Satellite System (GNSS) capability information. The method may include providing, to the location server, the GNSS capability informationincluding NavIC capability information. The NavIC capability information includes location information corresponding to the UE. Further, the method may include sending, to the location server, a request for assistance data. Furthermore, the method may include receiving, from the location server, the assistance data. The assistance data may be selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

[0028] In an embodiment, the location information may include at least one of a location parameter or a location measurement corresponding to the UE.

[0029] In an embodiment, the GNSS capability information may include at least one of: a positioning type, a band of GNSS support, an ionospheric model supported by the UE, navigation data supported by the UE, or Almanac supported by the UE.

[0030] In an embodiment, the UE may be configured to be operatively connected with the location server via a cellular network.

[0031] In an embodiment, the location server may include at least one of: an Evolved Serving Mobile Location Center (E-SMLC) server, a Location Management Function (LMF) server, or a Secure User Plane for Location (SUPL) Location Platform (SLP).

[0032] In an embodiment, the UE may be configured to communicate with a NavIC receiver. The NavIC receiver may be configured to communicate with a base station that forms part of a wireless network through a New Radio Positioning Protocol A (NRPPa). The NavIC receiver may receive location related information from the base station using the NRPPa.

[0033] In an embodiment, the base station may communicate with the UE through at least one of: a Long Term Evolution (LTE) network or a New Radio (NR) network.

[0034] In an embodiment, the NavIC capability information includes NavIC LI frequency band reception capability information of the UE.

[0035] In an embodiment, the NavIC capability information includes a NavIC LI frequency band information included in GNSS-FrequencylD information element (IE) or GNSS-SignallD IE.

[0036] An aspect of the present disclosure relates to a non-transitory computer- readable medium that stores instructions that are executable by one or more processors of a user equipment (UE). The UE may be configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite, to perform a method. The method may include receiving, from a location server, a request to provide Global Navigation Satellite System (GNSS) capability information. The method may include providing, to the locationserver, the GNSS capability information including NavIC capability information. The NavIC capability information may include location information corresponding to the UE. The method may include sending, to the location server, a request for assistance data. Further, the method may include receiving, from the location server, the assistance data. The assistance data is selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0038] FIG. 1A illustrates an example schematic representation (100A) of integration of a Navigation with Indian Constellation (NavIC) LI band, in accordance with an embodiment of the present disclosure.

[0039] FIG. IB illustrates an exemplary block diagram (100B) of a user equipment (UE) (102) to communicate with the NavIC satellite, in accordance with an embodiment of the present disclosure.

[0040] FIGs. 2A and 2B illustrate a schematic representation (200A) and a graphical representation (200B) of Global Navigation Satellite Systems (GNSS) Time to First Fix (TTFF) for a standalone and assisted system, in accordance with an embodiment of the present disclosure.

[0041] FIG. 3 illustrates a schematic representation (300) of frequency bands of second-generation NavIC signals, in accordance with embodiments of the present disclosure.

[0042] FIG. 4 illustrates a schematic representation (400) of a LTE Positioning Protocol (LPP) positioning protocol in 4G and 5G, in accordance with embodiments of the present disclosure.

[0043] FIG. 5 illustrates a schematic representation (500) of LPP configuration, in accordance with embodiments of the present disclosure.

[0044] FIG. 6 illustrates a sequence representation (600) of the LPP capability transfer procedure, in accordance with embodiments of the present disclosure.

[0045] FIG. 7 illustrates a sequence representation (700) of the LPP capability indication procedure, in accordance with embodiments of the present disclosure.

[0046] FIG. 8A illustrates a schematic representation (800A) of the LPP common assistance data transfer procedure, in accordance with embodiments of the present disclosure.

[0047] FIG. 8B illustrates a schematic representation (800B) of the LPP generic assistance data transfer procedure, in accordance with embodiments of the present disclosure.

[0048] FIG. 9 illustrates a schematic representation (900) of UE to indicate and exchange NavIC LI band capability information with 3GPP 5G, 4G networks, in accordance with embodiments of the present disclosure.

[0049] FIG. 10 illustrates a schematic representation (1000) of a battery life and accuracy of various positioning methods used in wireless systems across the industry, in accordance with embodiments of the present disclosure.

[0050] FIG. 11 illustrates an example flow diagram of a method (1100) for the UE being configured to communicate with the NavIC satellite, in accordance with an embodiment of the present disclosure.

[0051] FIG. 12 illustrates an exemplary computer system (1200) in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.

[0052] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0053] 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 can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0054] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, theensuing 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.

[0055] 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 to avoid obscuring the embodiments.

[0056] 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.

[0057] 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 in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0058] 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 oneembodiment” 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.

[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of 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 and all combinations of one or more of the associated listed items.

[0060] FIG. 1A illustrates an example schematic representation (100A) of the integration of a Navigation with Indian Constellation (NavIC) LI band, in accordance with an embodiment of the present disclosure.

[0061] Referring to FIG. 1, the present disclosure aims to establish mechanisms enabling the integration of Navigation with Indian Constellation (NavIC) LI in mobile devices, building on the New Radio (NR) and Long-Term Evolution (LTE) shared Layered Positioning Protocol (LPP) specification. Major procedural updates in the Stage 3 specifications include enhancements to the Global Navigation Satellite System (GNSS) assistance data elements. For instance, in the ionospheric model, updates are made to the KlobucharModelParameter, which currently uses an 8-bit 2’s complement representation for fields such as alfa2, alfa3, beta2, and beta3. Given the NavIC LI Interface Control Document (ICD) specifies higher word lengths for these fields. Additionally, a new NeQuick2 model is introduced, replacing the existing NeQuickModelParameter based on the Galileo GNSS model. The NeQuick model defined for NavIC LI in ICD represents three dynamic subregions specific to the subcontinent, with parameters that vary based on MODIPmax, MODIPmin, mLonmax, and mLonmin values, leading to the proposal of a new NeQuickModel2Parameter aligned with NavIC LI specifications.

[0062] Further updates apply to the Navigation Model. The NavIC LI Standard Positioning Service (SPS) clock model supports higher precision word lengths for fields such as navicLl-Toec, navicLl-af2, navicLl-afl, navicLl-afD, and navicLl-Tgd, similar to the NavIC L5 clock model. Additional parameters, including navicLI-iscLIPorS, navicLl-iscLID, and navicLl-RSF, are also introduced. To incorporate these, a new clock model IE (NavIC-ClockModel2) is proposed within the LPP framework. Additionally, an evolved orbit model is introduced for NavIC LI, as specified in the NavIC LI ICD. Since it differs from the NavIC L5 model (NavModel-NavIC-KeplerianSet in LPP), a new IE (NavModel-NavIC- KeplerianSet2) is proposed to support NavIC LI GNSS assistance.

[0063] For the Almanac Model, a new NavIC LI Almanac IE is introduced, incorporating the NavIC LI SPS Almanac model, which defines higher precision word lengths for fields like AlmE, AlmOMEGADOT, and AlmafO shared with the NavIC L5 Almanac model — along with a specific field, inclination iO. Accordingly, a new Almanac model IE, AlmanacNavIC-AlmanacSet2, is proposed in LPP. The NavIC- GridModelParameter also receives updates, introducing ITOW and TOI as optional fields. NavIC LI SPS messages employ a unique timing convention using these fields, enabling Ll- only receivers to interpret NavIC GridModelParam values without relying on NavIC L5 timing assumptions. Additional updates are made to the GNSS Assistance Data Request Elements, GNSS Capability Information Elements, e.g., GNSS-FrequencylD information element (IE) and GNSS-SignallD IE, and common GNSS information Elements, such as, Navic LI almanac data, ephemeris data, ionospheric Error data, NavIC LI clock data, NavIC LI orbit data, and the like. These comprehensive updates collectively enable NavIC LI assistance in cellular networks, enhancing positioning accuracy and performance in critical mobile device applications.

[0064] FIG. IB illustrates an exemplary block diagram (100B) of a user equipment (UE) (102) to communicate with the NavIC satellite, in accordance with an embodiment of the present disclosure.

[0065] Referring to FIG. IB, the UE (102) may include a processor (104), a memory (106), and an interface(s) 108. The processor (104) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that manipulate data based on operational instructions. Among other capabilities, the processor (104) may be configured to fetch and execute computer-readable instructions stored in the memory (106) of the UE (102). The memory (106) may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share data packets over a network service. The memory (106) may include any non-transitory storage device, including, for example, a volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read-Only Memory (EPROM), a flash memory, and the like.

[0066] In an embodiment, the interface(s) (108) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (108) may facilitate communication of the system (102) with various devices coupled to the UE (102). The interface(s) (108) may also provide a communication pathway for one or more components of the UE (102). Examples of such components include, but are not limited to, processing engine(s) (110), sensor module(s), and a database (112). The database (112) may include data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) (HO).

[0067] In an embodiment, the processing engine(s) (110) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (110). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (110) may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (104) may comprise a processing resource (for example, the processor (104)), to execute such instructions. In the present examples, the machine -readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (110). In such examples, the UE (102) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the UE (102) and the processing resource. In other examples, the processing engine(s) (110) may be implemented by an electronic circuitry.

[0068] Further, the processing engine(s) (110) may include a receiving module 114, a providing module 116, a sending module 118, a receiving module 120, and other module(s) 122. The other module(s) 122 may implement functionalities that supplement applications / functions performed by the processing engine(s) 110.

[0069] The receiving module 114 may receive a request from a location server to provide Global Navigation Satellite System (GNSS) capability information.

[0070] The providing module 116 may provide to the location server the GNSS capability information including NavIC capability information. The NavIC capability information may include location information corresponding to the UE.

[0071] The sending module 118 may send to the location server a request for assistance data.

[0072] The receiving module 120 may receive the assistance data from the location server. The assistance data may be selected from at least one of : NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

[0073] FIGs. 2A and 2B illustrate a schematic representation (200A) and a graphical representation (200B) of Global Navigation Satellite Systems (GNSS) Time to First Fix (TTFF) for a standalone and assisted system, in accordance with an embodiment of the present disclosure.

[0074] The present disclosure pertains to the field of the GNSS, specifically focusing on the integration of NavIC LI band assistance within cellular network positioning specifications for 3rd Generation Partnership Project (3GPP) 5thGeneration (5G) and 4thGeneration (4G) systems. GNSS positioning involves using time-of-arrival measurements from multiple satellite signals to estimate distances to the satellites, enabling mobile devices to determine their location. Examples of GNSS include BeiDou (BDS), Galileo, GLONASS, and Global Positioning System (GPS). Assisted GNSS (A-GNSS) enhances GNSS performance by improving the time-to-first-fix (TTFF), which is the time it takes for a device to acquire a satellite fix. A-GNSS achieves this by delivering necessary data to the device via a radio network, bypassing the slower satellite link and warming up the receiver for a quicker fix.

[0075] The Navigation with Indian Constellation (NavIC), also known as the Indian Regional Navigation Satellite System (IRNSS), is an autonomous satellite navigation system. The primary goal of NavIC is to provide Positioning, Navigation, and Timing (PNT) services to users within its service area. NavIC is designed to provide a position accuracy of less than 20 meters (2o) and timing accuracy better than 50 nanoseconds (2o) within its coverage area.

[0076] The NavIC constellation is fully operational within the service region, with satellites 1A, IB, 1C, ID, IE, IF, 1G, and II continuously visible for 24 hours. While currently serving a regional area, NavIC can be expanded to provide global coverage in the future by adding more satellites to the constellation. NavIC’ s satellite services are utilized across a wide range of sectors, including terrestrial, aerial, and marine transportation, location-based services (LBS), personal mobility, resource monitoring, surveying and geodesy, scientific research, time dissemination and synchronization, and safety-of-life alert dissemination. The NavIC provides two types of services: the Standard Positioning Service (SPS), an open service without encryption, and the Restricted Service (RS), an authorized service withencryption. Additionally, NavIC disseminates one-way disaster warning messages to users within the region.

[0077] FIG. 3 illustrates a schematic representation (300) of frequency bands of second-generation NavIC signals, in accordance with embodiments of the present disclosure.

[0078] Referring to FIG. 3, the first generation of Navigation with Indian Constellation (NavIC) satellites operates in the L5 and S bands, a protected frequency specifically assigned to the system. The second generation of NavIC satellites will incorporate LI band signals in addition to the existing bands, expanding the services provided. These second-generation satellites are being developed to meet the increasing demands of the navigation sector for enhanced positioning, navigation, and timing (PNT) services.

[0079] The NVS-01 satellite, part of the second generation of NavIC satellites. The addition of the LI navigation band significantly improves PNT services for civilian users and facilitates greater interoperability with other Global Navigation Satellite Systems (GNSS). To support the wider adoption and commercial use of NavIC signals for navigation applications, the NavIC Signal-in-Space Interface Control Document (ICD) for Standard Positioning Service (SPS) in the LI frequency was released. This document provides critical information about the NavIC signal-in-space, promoting research and development and aiding the commercial utilization of NavIC signals in navigation-based applications.

[0080] FIG. 4 illustrates a schematic representation (400) of a LTE Positioning Protocol (LPP) positioning protocol in 4G and 5G, in accordance with embodiments of the present disclosure.

[0081] Referring to FIG. 4, the LPP (LTE Positioning Protocol) enables positioning within 4G and 5G networks, outlining specific functions for network elements (NEs). UE (402) terminates the LPP protocol and manages positioning-related processes, reporting its capabilities to the LMF (Location Management Function). In UE-assisted modes, it provides measurement results in LMF mode and positioning calculation results in UE mode. gNodeB (404) terminates New Radio Positioning Protocol A (NRPPa) protocol over the N2 interface to facilitate NRPPa-related location message exchange, conducts positioning measurements, and reports results to the LMF (406). In uplink E-CID-based positioning, the gNodeB supplies information, such as SS-RSRP and RSRQ, for serving and neighbouring cells. AMF (Access and Mobility Management Function) Functionality (408) receives and manages location requests from the UE, GMLC (Gateway Mobile Location Centre), or AMF, facilitates LMF selection, coordinates positioning interactions, and forwards messages amongthe LMF, gNodeB, UE, and other entities. The LMF (406) handles positioning requests from the AMF, sends results to the AMF (408), and chooses positioning methods, either single or hybrid. The LMF (406) controls measurements, computes assistance data for the UE, calculates positioning information, and estimates accuracy. UDM (Unified Data Management) (410) functionality stores user positioning subscription information and routing details. GMLC (412), acting as a LCS client (414), processes location requests, retrieves UE longitude and latitude, manages subscriber data, service data, subscriptions, SP data, charging, and value-added service authentication. The LCS (Location Services) client (414) functionality located within or outside the PLMN, submits location requests with QoS parameters to retrieve data on UEs. In an embodiment, positioning requests can originate from different NEs, including the UE, AMF (408), or GMLC (412). If initiated by the UE, the request is sent to the gNodeB (404) over the NR-Uu interface, then forwarded to the AMF (408) via the N2 interface. The AMF (408) directs the request to the LMF (406) over the NL1 interface. Upon receiving it, the LMF (406) sends assistance data to the UE, retrieves measurement data, and calculates the position. If initiated by the AMF (408), the result is sent to the requesting entity (either the UE or the GMLC (412)) upon completion. Ionospheric Correction Models in GNSS Systems rely on ionospheric correction models to counter positioning errors caused by the ionosphere. For single-frequency positioning, models such as Klobuchar or NeQuick G are applied based on broadcasted coefficients that describe ionospheric behaviour. The NeQuick model, particularly adapted for Galileo singlefrequency corrections, uses parameters from Galileo satellites and the modified dip latitude of the user location.

[0082] The NavIC LI satellites employ Klobuchar and NeQuick models to enhance positioning capabilities. However, NavIC LI transponders use models that differ from the 3GPP LPP specifications. NavIC LI Klobuchar models use higher-precision parameters, while the NeQuick model differs in structure from the LPP-defmed model, helping to mitigate ionospheric delay-a major source of GNSS positioning error.

[0083] High-accuracy orbit and clock models support all GNSS systems, including NavIC, GPS, GLONASS, Galileo, and BeiDou, essential for accurate positioning, navigation, and timing services. Variation in orbit and clock quality across GNSS generations affects positioning quality, with new NavIC LI clock and orbit models increasing positioning accuracy. Such models provide precise satellite location and clock data, critical for enhancing positioning.

[0084] GNSS almanacs provide satellite constellation information, including orbital parameters, health status, and positions, aiding GNSS receivers in acquiring signals and performing initial satellite fixation. NavIC LI almanac data now include long-term satellite position and clock data, which are essential for tasks that need coarse accuracy, like satellite visibility assessment.

[0085] Key almanac details such as specifying satellite status, including tracking issues, svHealth: GNSS-specific satellite health indicator, interpreted based on the GNSS ID, ionospheric model that is essential for single-frequency receivers to correct for ionospheric error. Time information that provides time-related correction factors, such as converting GPS to UTC, helps to reduce device power consumption.

[0086] FIG. 5 illustrates a schematic representation (500) of LPP configuration, in accordance with embodiments of the present disclosure.

[0087] Referring to FIG. 5, the purpose of the procedures that are grouped together in this clause is to enable the transfer of capabilities from the target device (502) to a location server (504). Capabilities in this context refer to positioning and protocol capabilities related to LPP and the positioning methods supported by LPP. FIG. 5 represents LPP configuration for control- and user-plane positioning in Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or Next Generation Radio Access Network (NG-RAN).

[0088] A reference source (506) may send GNSS signals (B), such as GPS or Galileo signals, to the target device / Positioning Reference Unit (PRU) (502) for satellite-based positioning. The target device / PRU (502) may represents the UE or Supplicant / Subscriber Equipment Terminal (SET). The target device (502) may receive GNSS signals (B) from satellites, and LTE / NR radio signals (A) from a base station (eNodeB / NG-RAN). The target device (502) may perform measurements (A, B, or combined A+B) to estimate location of the target device (502). A reference source, for example, eNodeB / NG-RAN may provide LTE or 5G NR radio signals (A) to assist with positioning, especially when GNSS signals are weak (e.g., indoors). The location server (an Evolved Serving Mobile Location Center (E- SMLC) (504), a Location Management Function (LMF) server, or a Secure User Plane for Location (SUPL) Location Platform (SLP) may collect measurement data or computed location from the target device via LPP (LTE Positioning Protocol). The location server (504) may also send assistance data to help improve positioning accuracy. The location server (504) may include, for example, E-SMLC for LTE systems, LMF for 5G NR systems, and SLP for Secure Location Platform services.

[0089] A LTE Positioning Protocol (LPP) may represent a communication protocol that may allow exchange of positioning data between the target device (502) and the location server (504).

[0090] FIG. 6 illustrates a sequence representation (600) of the LPP capability transfer procedure, in accordance with embodiments of the present disclosure.

[0091] Referring to FIG. 6, the server (LMF) sends a Requestcapabilities message to a target (602). A server (604) may indicate the types of capability needed. The target (UE) (602) responds with a ProvideCapabilities message to the server (604). The capabilities shall correspond to any capability types specified in step 1. The ProvideCapabilities message may include the endTransaction IE set to TRUE. The ProvideCapabilities message may include, for example, Positioning Type: GNSS, GNSS support: NavIC LI I, Q, & I+Q, Ionospheric Models supported: Updated Klobuchar, New NeQuick2, NavigationData supported: OrbitType: NavIKep lerianSet2, ClockType: NavICClockModel2, Almanac supported: New NavICAlmanacSet2) .

[0092] FIG. 7 illustrates a sequence representation (700) of the LPP capability indication procedure, in accordance with embodiments of the present disclosure.

[0093] Referring to FIG. 7, a target User Equipment (UE) (702) transmits a ProvideCapabilities message to a server (704), with the endTransaction Information Element (IE) set to TRUE. Upon receiving a Requestcapabilities message, the target device (702) generates a ProvideCapabilities message as a response. The target device (702) follows specific steps in crafting this response. First, for each positioning method requested within the capabilities inquiry, if the target device (702) supports the given positioning method, the response message must include the device's capabilities for that method. The IE LPP- TransactionlD in the response message is set to match the LPP-TransactionlD in the received RequestCapabilities message, ensuring consistency in transaction identification. The target device (702) then delivers the response message to the lower communication layers for transmission.

[0094] During the transmission of the LPP ProvideCapabilities message, the target device (702) adheres to a defined process. When triggered to send the ProvideCapabilities message, the target device (702) includes each applicable positioning method’s capabilities by setting the corresponding IE with the device’s capabilities. If Observed Time Difference of Arrival (OTDOA) capabilities are to be specified, the IE supportedBandListEUTRA is included in the message. Once the message is structured with all relevant information, the target device (702) forwards the response to the lower layers for transmission.

[0095] FIG. 8A illustrates a schematic representation (800A) of the LPP common assistance data transfer procedure, in accordance with embodiments of the present disclosure. FIG. 8B illustrates a schematic representation (800B) of the LPP generic assistance data transfer procedure, in accordance with embodiments of the present disclosure.

[0096] Referring to FIGs. 8A and 8B, a target (802) sends a RequestAssistanceData message to a server (804). The server (804) responds with a ProvideAssistanceData message to the target containing assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. The server (804) may also provide any not requested information that it considers useful to the target. If step 3 does not occur, this message shall set the endTransaction IE to TRUE. The server (804) may transmit one or more additional ProvideAssistanceData messages to the target containing further assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. The server may also provide any not requested information that it considers useful to the target. The last message shall include the endTransaction IE set to TRUE.

[0097] The NavIC LI A-GNSS by extending the existing LPP framework has impacts on the stage 2 and stage 3 specifications respectively. Necessary NavIC LI SPS assistance data information needs to be introduced in the stage 3 specification based on the existing GNSS framework. Ionospheric models represent the integration including support for the Klobuchar model, NeQuick model, and new NeQuick2 model for ionospheric delay corrections. These models help in mitigating the ionospheric delay, which is a significant source of error in GNSS positioning. Navigation models represent the introduction of new NavIC LI clock and orbit models that enhance the accuracy of positioning services. These models provide precise satellite position and clock information, which are crucial for accurate GNSS positioning. Almanac Data represents new NavIC LI almanac data elements that are included to provide long-term satellite position and clock information. Almanac data is essential for receiver tasks that require coarse accuracy, such as determining satellite visibility. Assistance data represents updates to GNSS assistance data request elements and GNSS capability information elements are made to support NavIC LI. This includes the introduction of new data elements and modifications to existing ones to accommodate NavIC LI assistance data.

[0098] FIG. 9 illustrates a schematic representation (900) of UE to indicate and exchange NavIC LI band capability information with 3GPP 5G, 4G networks, in accordance with embodiments of the present disclosure.

[0099] Referring to FIG. 9, the 5G positioning process happens as depicted in figure below. The given present disclosure focuses on updating the 5G and 4G positioning specifications focusing on step 3 and step 5 of the positioning protocol to enable NavIC LI band integration to 3GPP positioning protocol.

[0100] A. Enabling UE to indicate and exchange NavIC LI band capability information with 3GPP 5G, 4G networks: The IE A-GNSS-Provide-Capabilities is used by the target device to indicate its capability to support A-GNSS and to provide its A-GNSS location capabilities (e.g., GNSSs and assistance data supported) to the location server.

[0101] A. l. Introduction of NavIC LI band support to 3GPP cellular positioning system requires the capability called GNSS-SupportList to be updated with NavIC LI components. A.2. Further the Capabilities also include the details of Assistance Data specific to a particular GNSS constellation to be defined and updated in LPP (LTE positioning protocol) specification.

[0102] A. l. Introduction of new components to GNSS-Supportlist: As the NavIC LI consists of a Pilot channel hence Inphase(I) and Quadrature(Q) components of NavIC LI need to be distinguishable separately. The present disclosure introduces following NavIC LI SPS-specific capabilities to the specifications:

[0103] A.2. New Assistance Data components to AssistanceDataSupportList: This present disclosure proposes following GNSS capability information elements updates for supporting NavIC LI band GNSS assistance a. New Ionospheric model support indication towards• NavIC LI neQuick2 b. New NavigationModel support indication towards• NavIC LI NavICClockModel2• NavIC LI OrbitModel

[0104] The present disclosure proposes an extension to the currently defined GNSS- NavigationModelSupport IE as it is limited to 8 bits for both OrbitModelSupport and ClockModelSupport indication and all 8 bits have been already assigned to legacy GNSS models.

[0105] B. New GNSS assistance data elements for NavIC LI signals. This present disclosure proposes new NavIC LI specific models for elements of GNSS- CommonAssistData and GNSS-GenericAssistData respectively.The following specification updates are proposed:

[0106] The present disclosure proposes following updates to GNSS Assistance Data Elements - B.l: LPP Common Assistance Data Support updates o Ionospheric model a. Updates to Klobuchar model defined in 3GPP specifications would be required to support NavIC LI band as the prcision of some elements for NavIC LI band messages are much higher than the ones supported by current LPP definitions. This improves the accuracy and performance of the position fix using NavIC LI band positioning signals. b. Introduction of new neQuick2 model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of neQuickModel in 3GPP positioning protocol.B.2: LPP Generic Assistane Data Support updates o Navigation Model a. Introduction of new NavIC LI clock model model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of Navigation model in 3GPP positioning protocol (as per NavIC LI ICD o Introduction of new NavIC LI orbit model model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of orbit model in 3GPP positioning protocol. o Almanac a. Introduction of new NavIC LI Almanac IE model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of Almanac in 3GPP positioning protocol (as per NavIC LI ICD. o Update to NavIC GridModel a. This present disclosure proposes that the GridModel defined for the 5° grid and corresponding elements across the map for NavIC lonopheric correctionsin NavIC L5 work needs to be updated to ensure compatibility with the UEs supporting NavIC LI only GNSS reception.6.5.2 A-GNSS Positioning6.5.2. 1 GNSS Assistance DataA-GNS S-Provide AssistanceDataThe IE A-GNSS-ProvideAssistanceData is used by the location server to provide assistance data to enable UE-based and UE-assisted A-GNSS. It may also be used to provide GNSS positioning specific error reasons.GNSS-CommonAssistData: The IE GNSS-CommonAssistData is used by the location server to provide assistance data which can be used for any GNSS.B.1 : New Ionospheric models and extentions to LPP IESThis present disclosure proposes following GNSS Ionospheric model updates for supporting NavIC LI band GNSS assistance a. Extension to existing Klobuchar model to enable higher word length NavIC LI parameters■ Update KlobucharModelParameter b. New neQuick Model definition to enable NavIC LI neQUick assistance■ NavIC LI NeQuickModel2Parameter

[0107] GNSS-IonosphericModel: The IE GNSS-IonosphericModel is used by the location server to provide parameters to model the propagation delay of the GNSS signals through the ionosphere. Proper use of these fields allows a single frequency GNSS receiver to remove parts of the ionospheric delay from the pseudo range measurements. Three Ionospheric Models are supported: The Klobuchar model, the NeQuick model, and the klobucharModel2.

[0108] GNSS-GenericAssistData: The IE GNSS-GenericAssistData is used by the location server to provide assistance data for a specific GNSS. The specific GNSS for which the provided assistance data are applicable is indicated by the IE GNSS ID and (if applicable) by the IE SBAS ID. Assistance for up to 16 GNSSs can be provided.

[0109] B.2: New Navigation models and extentions to LPP IEsThis present disclosure proposes following updates for supporting NavIC LI band GNSS assistance o Navigation Model a. Introduction of new NavIC LI clock model model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LIband signals are different frm the current definitions of Navigation model in 3GPP positioning protocol (as per NavIC LI ICD. b. Introduction of new NavIC LI orbit model model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of orbit model in 3GPP positioning protocol (as per NavIC LI ICD.

[0110] The IE GNSS-NavigationModel is used by the location server to provide precise navigation data to the GNSS capable target device. In response to a request from a target device for GNSS Assistance Data, the location server determines whether to send the navigation model for a particular satellite to a target device based upon factors like the T-Toe limit specified by the target device and any request from the target device for DGNSS (see also GNSS-Differential Corrections). GNSS Orbit Model can be given in Keplerian parameters or as state vector in Earth-Centered Earth-Fixed coordinates, dependent on the GNSS-ID and the target device capabilities. The meaning of these parameters is defined in relevant ICDs of the particular GNSS and GNSS specific interpretations apply. For example, GPS and QZSS use the same model parameters but some parameters have a different interpretation.[oni] B.3: New Almanac model addition to LPP IES. This present disclosure proposes introduction of new NavIC LI Almanac IE model specific to NavIC LI band signals is required as the neQUick odel and word length used by NavIC LI band signals are different frm the current definitions of Almanac in 3GPP positioning protocol (as per NavIC LI ICD. Almanac Parameters Definitions.

[0112] GNSS-Almanac: The IE GNSS-Almanac is used by the location server to provide the coarse, long-term model of the satellite positions and clocks. The meaning of these parameters is defined in relevant ICDs of the particular GNSS and GNSS specific interpretations apply. For example, GPS and QZSS use the same model parameters but some parameters have a different interpretation. GNSS-Almanac is useful for receiver tasks that require coarse accuracy, such as determining satellite visibility. The model is valid for up to a few weeks, typically. Since it is a long-term model, the field should be provided for all satellites available in the GNSS constellation (i.e., not only for SVs visible at the reference location and including SVs flagged as unhealthy in almanac). The completeAlmanacProvided field indicates whether or not the location server provided almanacs for the complete GNSS constellation.

[0113] B.4: Update to NavIC GridModelParameter: The disclosure proposes that theGridModel defined for the 5° grid and corresponding elements across the map for NavIC lonopheric corrections in NavIC L5 work needs to be updated to ensure compatibility with the UEs supporting NavIC LI only GNSS reception.

[0114] FIG. 10 illustrates a schematic representation (1000) of a battery life and accuracy of various positioning methods used in wireless systems across the industry, in accordance with embodiments of the present disclosure.

[0115] Referring to FIG. 10, including NavIC LI in 3GPP standards will significantly reduce the time to first fix (TTFF) and improve the GDOP for location services, ensuring reliable accuracy for devices connected to cellular networks. FIG. 10 depicts the Battery life and Accuracy of various positioning methods used in wireless systems across industry. As observed Assisted-GNSS improves both the Battery life as well as the accuracy of GNSS positioning by considerable margin. This can be a game changer for various applications, from public safety to emergency response and beyond, as it brings indigenous navigation system to the forefront of global standards. The future of accurate, real-time GNSS positioning closer than ever.

[0116] Emergency Location Based Services (LBS) - Enhanced positioning accuracy for emergency responders, enabling quicker and more precise location tracking in urban and rural areas.

[0117] Government regulation such as E911 and the promise of location-based services (LBS) are the biggest drivers for integrating positioning capability into mobile phones. Cellular standards for GNSS assistance data exist for both control plane and user plane protocols. These protocols carry information that help the integrated GNSS receiver to improve its sensitivity, speed up signal acquisition, and especially reduce the time to first fix.

[0118] With the introduction of regional Navigation satellite constellation, the particular region has opened up new avenues for deploying reliable LBS by enabling mobile phone support to the given navigation system.

[0119] Tracking of inventory items while outdoor transportation, tracking of pets and loved ones in unknown regions heavily rely upon the accuracy of the GNSS location of the tracking device. The GNSS tracking is a battery intensive application and hence many trackers trade-off the battery life by turning off the GNSS tracking intermittently. Every time the GNSS is turned ON again it takes some time before the location accuracy is tuned back to a reliable figure. This is where the proposed GNSS assistance form cellular networks turns out to be a game changer. The assistance information provided by network ensures that theGNSS location is highly accurate even when the device GNSS comes back from sleep to a warm OR cold start.

[0120] The Unmanned Aerial Vehicles (UAVs) commonly referred to as Drones require precise positioning information in three dimensions continuously to enable correct flight path and avoiding collisions.

[0121] The precise Ionospheric correction models used by NavIC LI satellites and their quick assistance data provided by cellular networks which are used for UAV connectivity can enable easily accessible and effective positioning solution in geography.

[0122] Enhanced GNSS support for navigation systems in vehicles, improving route planning and traffic management. Similar to UAVs, V2X communication based automated driving requires precise positioning information with least latency for effective operations. NavIC El based positioning aided by cellular network positioning assistance can play a pivotal role in enabling a cost effective omnipresent solution for this use case.

[0123] Better synchronization of network elements, leading to improved service quality and reduced latency in cellular networks. The NavIC LI rubidium clock is important because it helps to overcome the clock failures that affected the first generation of navigation satellites. The new clocks are domestically designed and developed, and they supplement the imported atomic clocks in the next generation of navigation satellites.

[0124] FIG. 11 illustrates an example flow diagram of a method (1100) for the UE being configured to communicate with the NavIC satellite, in accordance with an embodiment of the present disclosure.

[0125] At step (1102), the method (1100) includes receiving, from a location server, a request to provide Global Navigation Satellite System (GNSS) capability information. The method, at step (1104) may include providing, to the location server, the GNSS capability information including NavIC capability information. The NavIC capability information comprises location information corresponding to the UE.

[0126] At step (1106), the method facilitates sending, to the location server, a request for assistance data.

[0127] Further, at step (1108), the method includes receiving, from the location server, the assistance data, the assistance data being selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

[0128] FIG. 12 illustrates an exemplary computer system (1200) in which or with which embodiments of the present disclosure may be utilized in accordance with embodiments of the present disclosure.

[0129] In an embodiment, the computer system (1200) may include a navigation GNSS receiver sub-system (1280) and a cellular transceiver sub-system (1290). As shown in FIG. 12, the computer system (1200) may include an external storage device (1210), a bus (1220), a main memory (1230), a read-only memory (1240), a mass storage device (1250), a communication port(s) (1260), and a processor (1270). A person skilled in the art will appreciate that the computer system (1200) may include more than one processor (1270) and communication ports (1260). The processor (1270) may include various modules associated with embodiments of the present disclosure. The communication port(s) (1260) 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 ports(s) (1260) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (1200) connects.

[0130] In an embodiment, the main memory (1230) may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The readonly memory (1240) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (1270). The mass storage device (1250) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0131] In an embodiment, the bus (1220) may communicatively couple the processor(s) (1270) with the other memory, storage, and communication blocks. The bus (1220) may be, e.g., a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), 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 (1270) to the computer system (1200).

[0132] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (1220) to support directoperator interaction with the computer system (1200). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (1260). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (1200) limit the scope of the present disclosure.

[0133] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0134] The present disclosure provides Navigation Indian Constellation (NavIC) band assistance to cellular network positioning specifications to enhance positioning accuracy, navigation reliability, and timing precision for civilian users.

[0135] The present disclosure facilitates to leverage second-generation NavIC satellite services with LI band support to provide improved interoperability with other Global Navigation Satellite Systems (GNSS), leading to more robust and consistent performance in diverse environments.

[0136] The present disclosure facilitates to integrate NavIC LI band assistance information to cellular network positioning.

[0137] The present disclosure facilitates to enable a wide range of use cases by providing faster and more accurate positioning for cellular devices, thereby enhancing Location-Based Services (LBS).

[0138] The present disclosure facilitates to improve drone flight operations through quicker NavIC GNSS acquisition and higher positional accuracy, while offering superior tracking performance with improved accuracy and extended battery life for applications such as inventory management, and tracking of children, pets, and other assets.

Claims

We Claim1. A user equipment (UE) (102) configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite (506), the UE (102) comprising: a memory storing an instruction; and a processor configured to execute the instruction stored in the memory to: receive, from a location server (504), a request to provide Global Navigation Satellite System (GNSS) capability information; provide, to the location server (504), the GNSS capability information including NavIC capability information, the NavIC capability information comprising location information corresponding to the UE; send, to the location server (504), a request for assistance data; and receive, from the location server (504), the assistance data, the assistance data being selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

2. The UE (102) as claimed in claim 1, wherein the location information comprises at least one of a location parameter or a location measurement corresponding to the UE.

3. The UE (102) as claimed in claim 1, wherein the GNSS capability information comprises at least one of: a positioning type, a band of GNSS support, an ionospheric model supported by the UE, navigation data supported by the UE, or Almanac supported by the UE.

4. The UE (102) as claimed in claim 1, wherein the UE is configured to be operatively connected with the location server via a cellular network.

5. The UE (102) as claimed in claim 1, wherein the location server (504) comprises at least one of: an Evolved Serving Mobile Location Center (E-SMLC) server, a Location Management Function (LMF) server, or a Secure User Plane for Location (SUPL) Location Platform (SLP).

6. The UE (102) as claimed in claim 1, wherein the UE (102) is configured to communicate with a NavIC receiver, the NavIC receiver being configured to communicate with a base station that forms part of a wireless network through a New Radio Positioning Protocol A (NRPPa), and wherein the NavIC receiver receives location related information from the base station using the NRPPa.

7. The UE (102) as claimed in claim 6, wherein the base station communicates with the UE through at least one of: a Long Term Evolution (LTE) network or a New Radio (NR) network.

8. The UE (102) as claimed in claim 1, wherein the NavIC capability information comprises NavIC LI frequency band reception capability information of the UE.

9. The UE (102) as claimed in claim 1, wherein the NavIC capability information comprises a NavIC LI frequency band information included in GNSS-FrequencylD information element (IE).

10. The UE (102) as claimed in claim 1, wherein the NavIC capability information comprises a NavIC LI frequency band included in GNSS-SignallD IE.

11. A method (1100) for a user equipment (UE) (102), the UE (102) being configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite (506), the method (1100) comprising: receiving (1102), from a location server (504), a request to provide Global Navigation Satellite System (GNSS) capability information; providing (1104), to the location server (504), the GNSS capability information including NavIC capability information, the NavIC capability information comprising location information corresponding to the UE; sending (1106), to the location server (504), a request for assistance data; and receiving (1108), from the location server (504), the assistance data, the assistance data being selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

12. The method (1100) as claimed in claim 11, wherein the location information comprises at least one of a location parameter or a location measurement corresponding to the UE.

13. The method (1100) as claimed in claim 11, wherein the GNSS capability information comprises at least one of: a positioning type, a band of GNSS support, an ionospheric model supported by the UE, navigation data supported by the UE, or Almanac supported by the UE.

14. The method (1100) as claimed in claim 11, wherein the UE is configured to be operatively connected with the location server via a cellular network.

15. The method (1100) as claimed in claim 11, wherein the location server comprises at least one of: an Evolved Serving Mobile Location Center (E-SMLC) server, a Location Management Function (LMF) server, or a Secure User Plane for Location (SUPL) Location Platform (SLP).

16. The method (1100) as claimed in claim 11, wherein the UE is configured to communicate with a NavIC receiver, the NavIC receiver being configured to communicate with a base station that forms part of a wireless network through a New Radio Positioning Protocol A (NRPPa), and wherein the NavIC receiver receives location related information from the base station using the NRPPa.

17. The method (1100) as claimed in claim 16, wherein the base station communicates with the UE through at least one of: a Long Term Evolution (LTE) network or a New Radio (NR) network.

18. The method (1100) as claimed in claim 11, wherein the NavIC capability information comprises NavIC LI frequency band reception capability information of the UE.

19. The method (1100) as claimed in claim 11, wherein the NavIC capability information comprises a NavIC LI frequency band information included in GNSS-FrequencylD information element (IE) or GNSS-SignallD IE.

20. A non-transitory computer-readable medium storing instructions that are executable by one or more processors of a user equipment (UE) configured to communicate with at least one Navigation Indian Constellation (NavIC) satellite (506), to perform a method (1100), the method (1100) comprising: receiving (1102), from a location server (504), a request to provide GlobalNavigation Satellite System (GNSS) capability information; providing (1104), to the location server (504), the GNSS capability information including NavIC capability information, the NavIC capability information comprising location information corresponding to the UE; sending (1106), to the location server (504), a request for assistance data; and receiving (1108), from the location server (504), the assistance data, the assistance data being selected from at least one of: NavIC LI almanac data, NavIC LI ephemeris data, NavIC LI ionospheric error data, NavIC LI clock data, or NavIC LI orbit data.

Images