Method and systems for handling triggers based on vertical application layer service area id

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure describes a method (300a and 300b), location management server and location management client installed in a Vertical Application Layer (VAL) User Equipment (UE) for handling triggers based on VAL service area ID. The method (300a) comprises receiving location reporting trigger to activate location reporting procedure for obtaining location information of VAL User Equipment (UE) from location management client installed in the VAL UE, wherein location reporting trigger includes triggering criteria based on a VAL service area ID. Subsequently, method comprises of converting VAL service area ID into its geographical location or area based on a look up table, wherein the look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. Finally, the method comprises of sending a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.

Description

METHOD AND SYSTEMS FOR HANDLING TRIGGERS BASED ON VERTICAL APPLICATION LAYER SERVICE AREA IDThe present disclosure relates to wireless communication. Particularly, but not exclusively, the present disclosure relates to method and systems for handling triggers based on Vertical Application Layer (VAL) service area ID.5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.5G-core (5GC) exposes the network to standard Application Programming Interface (APIs) for enabling third-party applications to tap the potential of network features. External third party applications such as industries, platform developers, and designers, may use the standard APIs for building network-aware (5G-enabled) applications, which establish a bidirectional communication with the 5GC, retrieving network statistics, but also triggering specific policies and commands to the network. The above-mentioned exposure capability is materialised through the Service Based Architecture (SBA), adopted by the 5GC network. 3rd Generation Partnership Project (3GPP) introduced the concept of Vertical Application Enablers (VAEs) in Rel. 16, enabling the efficient use and deployment of vertical apps over 3GPP systems. The specifications and the architecture are based on the notion of the VAE layer that interfaces with one or more Vertical apps. VAEs communicate via network-based interfaces that are well-defined and version-controlled. The focus of VAEs is to provide key capabilities, such as message distribution, service continuity, application resource management, dynamic group management and vertical app server APIs over the 5G system capabilities. Service Enabler Architecture Layer (SEAL) specifies northbound APIs for its individual services enabling flexible integration with vertical applications. A 3rd Generation Participation Project (3GPP) Technical Specifications (TS) 23.434 specifies a functional architecture for SEAL and procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. To ensure efficient use and deployment of vertical applications over 3GPP systems, SEAL services include specifications such as group management, configuration management, location management, identity management, key management, network resource management, notification management, network slice capability enablement, data delivery, application data analytics enablement, and the like.As part of the SEAL location management service, the concept of Vertical Application Layer (VAL) service area is introduced. The VAL service area refers to a geographical area served by a VAL server. The VAL server may have more than one VAL service area defined. These VAL service areas are configured by the VAL server to the location management server and are assigned with a unique identifier. When the VAL service area configurations are in place, then the VAL server may use a VAL service area ID (unique identifier) as part of the location information in SEAL APIs that are requiring location information. These VAL service area configurations may be updated by the VAL server in-order to modify the geographical area associated with the VAL service area ID. Upon updating the VAL service area configurations, the SEAL server internally manages the updates such as mapping the VAL service area ID to new / modified service area information and the like, without the VAL server requiring to re-invoke the APIs or update existing subscriptions, where the updated VAL service area ID are being used. As VAL service area ID maps to updated geographical area information, VAL servers may keep using the same old VAL service ID. Procedures for configuring the VAL service area ID and the usage of VAL service area ID is specified in 3GPP.3GPP specified in TS 23.434, that location reporting trigger information flow may carry triggering criteria based on the VAL service area ID, when the information flow is from VAL server to the location management server. Through this trigger, the VAL server may request the location management server to send the location report of a VAL user equipment (UE) when it satisfies the specified triggering criteria. However, the VAL client or SEAL client do not have any knowledge of the VAL service area ID and cannot determine whether VAL client or SEAL client meet the VAL service area ID based criteria or not. 3GPP specified in TS 23.434 does not defined a procedure on handling VAL service area ID based triggering criteria for location reporting of the VAL UE by location management server. Also, the triggers that may be set based on the VAL service area ID are not specified in 3GPP specified in TS 23.434.A Personal IoT Network (PIN) comprises PIN Elements (PINE) that communicate using a PIN direct connection or a direct network connection and is managed locally (using a PIN Element with Management Capability (PEMC)). The PIN Element with Gateway Capability (PEGC) is a PIN element that provides connectivity to and from a fifth generation (5G) network for other PIN Elements, or to serve as a relay for the communication between the PIN Elements. There could be more than one PEGC available at the time of creation of the PIN and a PIN server or the PEMC can distribute a load among these PEGCs when the PIN elements join the PIN.3GPP TS 23.542, clause 8.5.4.2.1 illustrates a procedure for configuring a new PIN element, when requesting to join, with a default PEGC and one or more backup PEGCs. This procedure assumes that more than one PEGCs are serving the PIN when the PIN element is requesting to join the PIN. As part of the PIN join response, the PIN element is informed of the details of the default PEGC and the back up PEGC. With this mechanism, the PIN element is made aware as to which PEGC it has to fall-back in case of default PEGC failure.There could be scenarios where the PIN admin or PIN owner might configure the PIN to contain more than one PEGCs based on the schedule such as, peak hours where more PIN elements are expected to join the PIN. During these hours, more PEGCs can be made available. In this case, the existing procedure can be applied for the new PIN elements joining the PIN to inform them about the default and back up PEGCs. But for PIN elements that are already part of the PIN, there are no mechanisms available to notify them about the availability of back up PEGCs. Hence, there is a need for a method for notifying PIN elements which are currently part of the PIN about the backup PEGC availability when a new PEGC becomes available, and a method for notifying PIN elements which are currently part of the PIN about the unavailability of the PEGC which is currently assigned as back up PEGC or default PEGC for the PIN elements and if there is a new PEGC available to serve as back up PEGC or default PEGC.The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.The present disclosure tries to address the aforesaid problem associated with handling the VAL service area ID based triggering criteria for location reporting of the VAL UE, and the usage of the VAL service area ID as a triggering criteria.In an embodiment, the present disclosure relates to a method for handling triggers based on Vertical Application Layer (VAL) service area ID. The method comprising receiving a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE. The location reporting trigger includes a triggering criteria based on a VAL service area ID. Subsequently, the method comprises of converting the VAL service area ID into its geographical location or area based on a look up table. The look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. Finally, the method comprises of sending a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.In an embodiment, the present disclosure relates to a method for handling triggers based on Vertical Application Layer (VAL) service area ID. The method comprising receiving location reporting configuration update request comprising a geographical area based trigger corresponding to a VAL service area ID based trigger. Subsequently, the method comprises. Subsequently, the method comprises of sending a reply with location reporting configuration update response with an update result. Finally, the method comprises of storing location reporting configuration.In another embodiment, the present disclosure relates to a location management server for handling triggers based on Vertical Application Layer (VAL) service area ID. The location management server comprising a processor and a memory. The memory stores processor-executable instructions, which, on execution, cause the processor to receive a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE. The location reporting trigger includes a triggering criteria based on a VAL service area ID. Subsequently, the processor is configured to convert the VAL service area ID into its geographical location or area based on a look up table. The look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. Finally, the processor is configured to send a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.In another embodiment, the present disclosure relates to a location management client installed in a Vertical Application Layer (VAL) User Equipment (UE) for handling triggers based on VAL service area ID. The location management client comprising a processor and a memory. The memory stores processor-executable instructions, which, on execution, cause the processor to receive location reporting configuration update request comprising a geographical area based trigger corresponding to a VAL service area ID. Subsequently, the processor is configured to send a reply with location reporting configuration update response with an update result. Finally, the processor is configured to store location reporting configuration.In another embodiment, the present disclosure relates to a method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN. The method comprising receiving a message from one or more PEGC's, indicating its connection with the PIN. The method further comprises determining an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. The method further comprises updating a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The method further comprises sending at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.In another embodiment, the present disclosure relates to a Personal IOT Network (PIN) Element with Management Capability (PEMC) of a PIN for notifying PIN Elements (PINEs) about an update in PIN Element with Gateway Capability (PEGC) availability. The PEMC comprising a processor and a memory. The memory stores processor-executable instructions, which, on execution, cause the processor to receive a message from one or more PEGC's, indicating its connection with the PIN. The processor is further configured to determine an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. The processor is further configured to update a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The processor is further configured to send, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.In another embodiment, the present disclosure relates to a method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN. The method comprising sending a message indicating its connection with the PIN. The method further comprises receiving an updated dynamic PIN profile. The PEMC determines an availability of each of the one more PEGC's of the PIN based on the message received from the PEGC and updates a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The method further comprises sending at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.In another embodiment, the present disclosure relates to a Personal IOT Network (PIN) Element with Gateway Capability (PEGC) for notifying PIN Elements (PINEs) about an update in PEGC availability. The PEGC comprising a processor and a memory. The memory stores processor-executable instructions, which, on execution, cause the processor to send, to a PIN Element with Management Capability (PEMC) of a PIN, a message from one or more PEGC's, indicating its connection with the PIN. The processor is further configured to receive, from the PEMC, an updated dynamic PIN profile. The PEMC determines an availability of each of the one more PEGC's of the PIN based on the message received from the PEGC and updates a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The processor is further configured to send, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.In another embodiment, the present disclosure relates to a method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN. The method comprising receiving, by a PIN server, a message from one or more PEGC's, indicating its connection with the PIN. The method further comprises determining, by the PIN server, an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. The method further comprises updating, by the PIN server, a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The method further comprises sending, by the PIN server to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.In another embodiment, the present disclosure relates to a Personal IOT Network (PIN) server of a PIN for notifying PIN Elements (PINEs) about an update in PIN Element with Gateway Capability (PEGC) availability. The PIN server comprising a processor and a memory. The memory stores processor-executable instructions, which, on execution, cause the processor to receive a message from one or more PEGC's, indicating its connection with the PIN. The processor is further configured to determine an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. The processor is further configured to update a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's. The processor is further configured to send, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.Embodiments of the present disclosure provides methods and apparatus for using VAL service area as part of the triggering criteria in the location reporting trigger.Embodiments of the present disclosure provides a way for the PIN elements to be notified about the change in default PEGC or backup PEGC.The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and methods in accordance with embodiments of the present subject matter are now described below, by way of example only, and with reference to the accompanying figures.Figs. 1a and 1b illustrate a sequence diagram for handling triggers based on Vertical Application Layer (VAL) service area ID, in accordance with some embodiments of the present disclosure.Fig. 2a illustrates a detailed block diagram of a location management server, in accordance with some embodiments of the present disclosure.Fig. 2b illustrates a detailed block diagram of a location management client, in accordance with some embodiments of the present disclosure.Figs. 3a and 3b show flowcharts illustrating a method for handling triggers based on Vertical Application Layer (VAL) service area ID, in accordance with some embodiments of the present disclosure.Fig. 4 is a block diagram of an exemplary system for implementing embodiments consistent with the present disclosure.Fig. 5 illustrates a general environment for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN, in accordance with some embodiments of the present disclosure.Figs. 6a-e illustrate a sequence diagram for dynamically notifying PEGC availability in a PIN, in accordance with some embodiments of the present disclosure.Fig. 7a illustrates a detailed block diagram of a PIN Element with Management Capability (PEMC), in accordance with some embodiments of the present disclosure.Fig. 7b illustrates a detailed block diagram of a PEGC, in accordance with some embodiments of the present disclosure.Fig. 7c illustrates a detailed block diagram of a PIN server, in accordance with some embodiments of the present disclosure.Figs. 8a-c show flowcharts illustrating a method for dynamically notifying PEGC availability in a PIN, in accordance with some embodiments of the present disclosure.Fig. 9 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises쪋 a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.Service Enabler Architecture Layer (SEAL) specifies northbound APIs for its individual services enabling flexible integration with vertical applications. A 3rd Generation Participation Project (3GPP) Technical Specifications (TS) 23.434 specifies a functional architecture for SEAL and procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. To ensure efficient use and deployment of vertical applications over 3GPP systems, SEAL services include specifications such as group management, configuration management, location management, identity management, key management, network resource management, notification management, network slice capability enablement, data delivery, application data analytics enablement, and the like.As part of the SEAL location management service, the concept of Vertical Application Layer (VAL) service area is introduced. The VAL service area refers to a geographical area served by a VAL server. The VAL server may have more than one VAL service area defined. These VAL service areas are configured by the VAL server to the location management server and are assigned with a unique identifier. When the VAL service area configurations are in place, then the VAL server may use a VAL service area ID (unique identifier) as part of the location information in SEAL APIs that are requiring location information. These VAL service area configurations may be updated by the VAL server in-order to modify the geographical area associated with the VAL service area ID. Upon updating the VAL service area configurations, the SEAL server internally manages the updates such as mapping the VAL service area ID to new / modified service area information and the like, without the VAL server requiring to re-invoke the APIs or update existing subscriptions, where the updated VAL service area ID are being used. As VAL service area ID maps to updated geographical area information, VAL servers may keep using the same old VAL service ID. Procedures for configuring the VAL service area ID and the usage of VAL service area ID is specified in 3GPP.3GPP specified in TS 23.434, that location reporting trigger information flow may carry triggering criteria based on the VAL service area ID, when the information flow is from VAL server to the location management server. Through this trigger, the VAL server may request the location management server to send the location report of a VAL user equipment (UE) when it satisfies the specified triggering criteria. However, the VAL client or SEAL client do not have any knowledge of the VAL service area ID and cannot determine whether VAL client or SEAL client meet the VAL service area ID based criteria or not. Currently, no procedure is defined on how the location management server handles the VAL service area ID based triggering criteria for location reporting from VAL UE. Location management server cannot forward the VAL service area ID based triggering criteria to the location management client since they do not have any knowledge about the VAL service area ID. Also, what are the triggers that may be set based on the VAL service area ID is not specified.The present disclosure proposes system and method for handling triggers based on VAL service area ID. In the present invention, a SEAL location management server converts the VAL service area ID based triggers received from a VAL server to a geographical area-based triggers and include the geographical area-based triggers in a location reporting configuration update request to the SEAL location management client. Basically, the SEAL location management server replaces the VAL service area ID(s) present in the location reporting trigger with the corresponding values mapped by the VAL server while configuring the VAL service area IDs with the SEAL location management server.As used herein, 'SEAL client' refers to an entity that provides the client side functionalities corresponding to the specific SEAL service.As used herein, 'VAL service' refers to a generic name for any service offered by the VAL service provider to their VAL users.As used herein, 'SEAL service' refers to a generic name for a common service (e.g., group management, configuration management, location management) that may be utilized by multiple vertical applications.As used herein, 'VAL server' refers to a generic name for the server application function of a specific VAL service.As used herein, 'SEAL server' refers to an entity that provides the server-side functionalities corresponding to the specific SEAL service.Clause 9.3.2.4 of 3GPP TS 23.434 specifies the location reporting trigger information flow as below:Table 1 below describes information flow from the location management client or VAL server to the location management server for triggering a location reporting procedure in accordance with the embodiments of the present disclosure.Information elementStatusDescriptionIdentityM(See NOTE　1)Identity of the requesting authorized VAL user or VAL UE or VAL serverIdentityM(See NOTE　1)Identity of the requested VAL user or VAL UEVAL service IDOIdentity of the VAL service for which the location reporting trigger is set.Immediate Report IndicatorO(See NOTE　2)Indicates whether an immediate location report is requiredRequested location informationO(See NOTE　2)Identifies what location information is requestedTriggering criteriaO(See NOTE　2)Identifies when the requesting client / VAL server is expecting to receive the location report from the requested VAL user / VAL UE. It may include VAL service Area ID based criteria when this information flow is from VAL server to the location management server. The triggering may be e.g., SAI changes, ECGI changes, RAT changes.Minimum time between consecutive reportsOsee (NOTE　2)Defaults to 0 if absent otherwise indicates the interval time between consecutive reportsEndpoint informationOInformation of the endpoint of the requesting VAL server to which the location report notification has to be sent. It is provided if Immediate Report Indicator is set to required.NOTE 1: The identity of the requesting VAL user / UE / VAL server and the requested VAL user / UE should belong to the same VAL service.NOTE 2: At least one of these rows shall be present.Before using the VAL service area ID in the triggering criteria request, a VAL server may have configured mapping of VAL service area IDs and its corresponding geographical location information with the location management server. After configuring the VAL service area IDs at the location management server, the VAL server may include the VAL service area IDs as part of the triggering criteria in the location reporting trigger information flow (Clause 9.3.2.4).Currently there is no procedure mentioned on what should the location management server do upon receiving the VAL service area ID based triggering criteria in the location reporting trigger from the VAL server. If the location management server just forwards the received location reporting trigger information which includes the VAL service area ID based triggering criteria to the SEAL location management client, then receiving SEAL location management client cannot evaluate the triggers based on the VAL service area ID since it does not have the VAL service area ID configuration information with it.In an embodiment, the present disclosure overcomes this problem by proposing that the SEAL location management server converts the VAL service area ID based triggers received from the VAL server to the geographical area-based triggers and include the geographical area-based triggers in the location reporting trigger request to the SEAL location management client. Particularly, the SEAL location management server replaces the VAL service area ID with the corresponding values mapped by the VAL server while configuring the VAL service area IDs with the SEAL location management server.In an embodiment, an exemplary procedure for location reporting configuration update is described. The location management server may update the location reporting configuration information and inform the location management client of the update ones at any time by triggering the location reporting configuration update procedure. As shown, the procedure for location reporting configuration update includes several steps.In step 1, based on the local configurations or the location information request from other entities (e.g., another location management client, VAL server) or if the VAL server updates the geographical location information of existing VAL service area ID and if a triggering criteria corresponding to the updated VAL service area ID is present, then the location management server may update the location reporting configuration and may inform the updated location reporting information to a location management client.In step 2, the location management server sends location reporting configuration update request message to the location management client(s) which includes the updated location reporting configuration. For example, the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches UE location report. This message may be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. If the location reporting trigger from VAL server includes the triggering criteria based on the VAL service area ID, then the location management server may convert those triggers into geographical area-based triggers while sending it to the location management client. In the present disclosure, different location management clients may be given different location reporting criteria.In step 3, the location management client(s) respond with the location reporting configuration update response to the location management server with the updated result.In step 4, the location management client stores or updates the new location reporting configuration received in step 2.In an embodiment an exemplary first procedure for handling the VAL service area ID based triggering criteria is described. The present disclose consist of pre-conditions followed by several steps for location management server handling the VAL service area ID based triggering criteria. The first pre-condition includes VAL server requiring to configure the location reporting trigger including the triggering criteria based on the VAL service area ID. The second pre-condition is the VAL server may have already configured the mapping of VAL service area IDs and the corresponding geographical location at the location management server.The steps for handling the VAL service area ID based triggering criteria includes:In step 1, the VAL server sends a location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client and this location reporting trigger includes the triggering criteria based on the VAL service area ID.In step 2, the location management server checks whether VAL server is authorized to send a location reporting trigger.In step 3, when the location reporting trigger as received in step 1 includes the triggering criteria based on the VAL service area ID, then the location management server converts that trigger into corresponding geographical location (mapped with the VAL service area ID) based trigger and constructs the location reporting configuration update request to the location management client accordingly.In step 4, the location management server sends the location reporting configuration update request to the location management client which includes the converted geographical area-based trigger corresponding to the VAL service area ID based trigger as received in step 1.In step 5, the location management client(s) may reply with location reporting configuration update response to the location management server with the update result.In step 6, the location management client stores or updates the new location reporting configuration received in step 4.In an embodiment, an exemplary second procedure for handling the VAL service area ID updates is disclosed. The present disclosure consist of pre-conditions followed by several steps for handling the VAL service area ID updates. The first pre-conditions include the VAL server requiring to update the VAL service area identifier configuration. The second pre-condition indicates the VAL server has already configured the location reporting trigger based on the VAL service area Identifier.The steps to handle the VAL service area ID updates includes:In step 1, the VAL server updates the existing VAL service area identifier configuration by following the procedure as described in clause 9.3.13.4.In step 2, the location management server checks whether if there are any existing location reporting triggers based on the updated VAL service area identifier(s) configured at any of the SEAL location management client and if configures, continue with the rest of the steps.In step 3, the location management server sends the location reporting configuration update request to the location management client(s) which may be earlier configured with the location reporting configuration, and which includes the trigger criteria based on the updated VAL service identifier as in step 1.In step 3, the location management clients reply with location reporting configuration update response to the location management server with the update result.In step 5, the location management client stores or updates the new location reporting configuration received in step 4.The present disclosure provides several triggers based on the VAL service area which may be set by the VAL server. The triggers may include, but not limited to, any change in the VAL service area, enter a particular VAL service area, exit a particular VAL service area, and the like.In an embodiment, the present disclosure provides several conditions when the location management server updates the location reporting configuration of the SEAL location management client. The first condition is, when the VAL server sends a new location reporting trigger for a particular SEAL location management client, and this carries the triggering criteria based on the VAL service area ID. A second condition being, whenever the VAL server updates the values of already configured VAL service area ID, and location reporting triggering criteria are present based on these VAL service area IDs, the location management server may send the updated location reporting triggers by location reporting configuration update request.The detail conversion procedure is given below:In case the VAL server has configured the following VAL service area IDs mapped with the corresponding geographical location at the location management server:VAL_Service_Area_ID1: Geographical Area 1 specified by polygon-area and ellipsoid-arc-area.VAL_Service_Area_ID2: Geographical Area 2 specified by polygon-area and ellipsoid-arc-area.Wherein, the polygon-area and ellipsoid-arc-area are defined in 3GPP TS 23.032 or may be defined in any other format (e.g., tracking area, cell ID etc).VAL server sends a location reporting trigger with the following criteria:Report location when the UE enters VAL_Service_Area_ID1Report location when the UE exits VAL_Service_Area_ID2On receiving the above location reporting trigger, the location management server replaces the VAL service area ID based trigger to the corresponding geographical area as below and send it to the Location management client as part of location reporting configuration update:Report location when the UE enters Geographical Area 1Report location when the UE exits Geographical Area 2.Currently, a Personal IoT Network (PIN) comprises PIN elements that communicate using a PIN direct connection or a direct network connection and is managed locally (using a PIN element with management capability). The PIN element with gateway capability is a PIN element that provides connectivity to and from a fifth generation (5G) network for other PIN Elements, or to serve as a relay for the communication between the PIN Elements. There could be more than one PEGC available at the time of creation of the PIN and a PIN server or the PEMC can distribute a load among these PEGCs when the PIN elements join the PIN.3GPP TS 23.542, clause 8.5.4.2.1 illustrates a procedure for configuring a new PIN element, when requesting to join, with a default PEGC and one or more backup PEGCs. This procedure assumes that more than one PEGCs are serving the PIN when the PIN element is requesting to join the PIN. So in the PIN join response, the PIN element gets to know the details of the default PEGC and the back up PEGC. With this mechanism, the PIN element knows to which PEGC it has to fall-back in case of default PEGC failure.There could be scenarios where the PIN admin or PIN owner might configure the PIN to contain more than one PEGCs based on the schedule like peak hours where more PIN elements are expected to join the PIN. During these hours, more PEGCs can be made available. In this case, the existing procedure can be applied for the new PIN elements joining the PIN to inform them about the default and back up PEGCs. But for PIN elements that are already part of the PIN, there is no mechanism available to notify them about the availability of back up PEGCs. Hence, following issues need to be addressed:Case 1: How the PIN elements which are currently part of the PIN are notified about the backup PEGC availability when the new PEGC becomes available.Case 2: How the PIN elements which are currently part of the PIN are notified about the unavailability of the PEGC which is currently assigned as back up PEGC for the PIN elements and if there is a new PEGC available to serve as back up PEGC.Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.The principal object of embodiments herein is to disclose systems and methods for notifying PIN elements about the available back up PEGC.The following abbreviations and definitions are referred to herein:3GPP: 3rd Generation Participation Project5GC: 5G Core NetworkD2D: Device to DeviceFQDN: Fully Qualified Domain NamePEGC: PIN Element with Gateway CapabilityPEMC: PIN Element with Management CapabilityPIN: Personal IoT NetworkPIN-E: PIN ElementProSe: Proximity ServicesQoS: Quality of ServiceUE: User EquipmentPIN (Personal IoT Network): Personal IoT Networks (PINs) provide local connectivity between UEs and / or non-3GPP devices. A Personal IoT Network (PIN) comprises of PIN Elements (PINE) that communicate using PIN Direct Connection or direct network connection and is managed locally (using a PIN Element with Management Capability).PINE (PIN Element): PIN Elements are UEs and / or non-3GPP devices which form part of the PIN.PEMC (PIN Element with Management Capability): These are PIN Elements, which have the capability to provide means for an authorized administrator to configure and manage a PIN.PEGC (PIN Element with Gateway Capability): PIN Elements with Gateway Capability provide means to PIN elements to register and access 5G network services. It can also help in communication between two PIN elements that are not within the range to use direct communication.ProSe: ProSe (Proximity Services) is a D2D (Device-to-Device) technology that allows LTE devices to detect each other and to communicate directly.PIN-ID: Unique identifier associated with a PIN.The PIN Elements with Gateway Capability provide means to PIN elements to register and access 5G network services. It can also help in communication between 2 PIN elements that are not within the range to use direct communication. In the PIN, there can be more than one PINE can be assigned with the role of PEGC and each would be serving a set of PINE. If any of the PEGC goes down or crashes it is necessary to assign its role to another PINE and start serving the PINEs which was being served by the old PEGC.In some cases, the PIN elements would have been configured with the default PEGC and available list of back up PEGCs which they can use to communicate in case of failure of default PEGC when the PIN elements are joining the PIN. The PINE with PEGC role may become unavailable for the following reasons:A) The UE on which PEGC is running may run out of power or crash,B) Schedule time to act as PEGC expired, orC) any other implementation specific reason.At the time when the PEGC becomes unavailable, it might be a default PEGC for some of the PIN elements and back up PEGC for some PIN elements. So when this PEGC becomes unavailable and new PIN element takes the role of PEGC, all the PIN elements for which the PEGC is serving as default and back up PEGC needs to be notified about its unavailability and the details of the PIN element which is taking the role of PEGC.In some cases, there might be only one PEGC serving all the PIN elements in the PIN and there is no other PEGC available. In these cases following are possible:Admin or owner of the PIN may configure a new PIN element and assign it with PEGC role in addition to the existing PEGC in order to load balance or to meet the KPIs configured for the PIN; (or)A new PIN element may register / join the PIN with PEGC capabilities or existing PIN element may upgrade its capabilities to act as PEGC.In this scenario, the PIN server or PEMC may decide to notify the existing PIN elements about the availability of new PEGC which can be considered as back up PEGC for the PIN elements when the default PEGC becomes unavailable. When the new PEGC is made available, the PIN management entity whether it be PEMC or PIN server shall include the information about the new PIN element which is assigned with the role of PEGC and also the details of the previous PIN element which was assigned with the role of PEGC. If this information is available then it will be helpful is notifying only the relevant PIN elements. PIN elements details could be the PIN element Identifier, PIN identifier etc. For example, if PEGC-2 is taking the role of PEGC replacing PEGC-1, then this information shall be available in the PIN status notification so that PEMC / PEGC-2 / PEMC can notify only the relevant PIN elements for which this change is applicable.Notifying or signaling the required PIN elements can be achieved by sending a notification to the PIN elements carrying the updated PIN client profile information elements to contain the details of the new PEGC which can serve as back up PEGC or the PIN elements can be notified when the PIN client profile is updated with the details of back up PEGC available or default PEGC available. Corresponding information elements (e.g., Default PEGC, Backup PEGCs list or the like) in the PIN dynamic profile and PIN client profile can be updated with details of new PEGC availability.In an embodiment when the PIN is currently being served by one PEGC (PEGC-1) and new PIN element PEGC-2 joins the PIN at later point. The dynamic PIN profile gets updated to contain the details of PEGC-2 and also the list of PIN elements for which it can be a backup PEGC.Following are the pre-conditions:PEGC-1 PIN element is currently the PEGC of the PIN and no other PIN element is assigned with the role of PEGC,Dynamic information about the PIN is available at the PIN Management server, andPEGC-2 has the capability to perform the role of PEGC.Following are steps:1) PEMC, PEGC-1, PEGC-2, PINE-1, PINE-2, PINE-3 all are part of same PIN. PEGC-1 is currently the PEGC of the PIN.2) PEGC-2 joins the PIN using the existing procedure specified in 3GPP TR 23.700-78. While joining it indicates that it can act as PEGC and is authorized by the PIN server / PEMC to be PEGC. The PIN server or PEMC delivers the updated PIN profile and PIN dynamic profile information containing the details of the PIN to the PEGC-2.3) Once the PEGC-2 successfully registered with PIN and assigned with the role of PEGC, the PEMC signals or notifies all or certain PIN elements of the PIN about the availability of PEGC which can be the backup PEGC for the PIN elements. The existing PIN elements can be notified by sending the notification request explicitly or by changing the PIN profile or PIN client profile information and they get notified of the changes to the PIN profile or PIN client profile.In an embodiment when the PIN is currently being served by one PEGC (PEGC-1) and new PIN element PEGC-2 joins the PIN at later point. The dynamic PIN profile gets updated to contain the details of PEGC-2 and also the list of PIN elements for which it can be a backup PEGC.Following are the pre-conditions:1) PEGC-1 PIN element is currently the PEGC of the PIN and no other PIN element is assigned with the role of PEGC2) Dynamic information about the PIN is available at the PIN Management server3) PEGC-2 has the capability to perform the role of PEGCFollowing are steps:1) PEMC, PEGC-1, PEGC-2, PINE-1, PINE-2, PINE-3 all are part of same PIN. PEGC-1 is currently the PEGC of the PIN.2) PEGC-2 joins the PIN using the existing procedure specified in 3GPP TR 23.700-78. While joining, the PEGC-2 indicates that it can act as PEGC and is authorized by the PIN server / PEMC to be PEGC. The PIN server or PEMC delivers the updated PIN profile and PIN dynamic profile information containing the details of the PIN to the PEGC-2.3) Once the PEGC-2 successfully registered with PIN and assigned with the role of PEGC, the PEGC-2 signals or notifies all or certain PIN elements of the PIN about the availability of PEGC which can be the backup PEGC for the PIN elements.In an embodiment when the PIN is currently being served by one PEGC (PEGC-1) and the new PIN element PEGC-2 joins the PIN at later point. The dynamic PIN profile gets updated to contain the details of PEGC-2 and also the list of PIN elements for which it can be a backup PEGC.Following are the pre-conditions:1) PEGC-1 PIN element is currently the PEGC of the PIN and no other PIN element is assigned with the role of PEGC.2) Dynamic information about the PIN is available at the PIN Management server.3) PEGC-2 has the capability to perform the role of PEGC.Following are steps:1) PEMC, PEGC-1, PEGC-2, PINE-1, PINE-2, PINE-3 all are part of same PIN. PEGC-1 is currently the PEGC of the PIN.2) PEGC-2 joins the PIN using the existing procedure specified in 3GPP TR 23.700-78. While joining, the PEGC indicates that it can act as PEGC and is authorized by the PIN server / PEMC to be PEGC. The PIN server or PEMC delivers the updated PIN profile and PIN dynamic profile information containing the details of the PIN to the PEGC-2.3) Once the PEGC-2 successfully registered with PIN and assigned with the role of PEGC, the PIN server signals or notifies all or certain PIN elements of the PIN about the availability of PEGC which can be the backup PEGC for the PIN elements.In an embodiment, case 2 is applicable when the PIN is configured with multiple PEGCs already and the PIN elements are configured with the default PEGC and list of back up PEGCs. In this scenario when the PEGC becomes unavailable it might have been configured as default PEGC for some PIN elements and as back up PEGC for some PIN elements. When a new PEGC becomes available in the place of an unavailable PEGC, it is required to notify the PIN elements for which the new PEGC is configured as back up PEGC replacing the older one. Options described for Case 1 can be re-used for these cases also.8.5.4.2.1 PIN configuration with default and backup PEGCsFigure 8.5.4.2.1-1 illustrates a procedure for configuring a new PIN Element, when requesting to join, with a default PEGC and one or more backup PEGCs. Also configuring the PIN elements which are already part of the PIN with the details of the new PEGC(s) availability if required.Pre-conditions:1) The PEMC is pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server.2) The PEMC is authorized to access the PIN server.3) The PEMC has registered to the PIN server.4) The PEMC has requested and has been authorized by the PIN server to create a PIN.5) The required KPIs of the PIN have been configured.6) PINE-1, PINE-2, PINE-3, PEGC-A and PEGC-B have registered to the PEMC and PIN server. PINE-3 has already joined the PIN and is already is the member of the PIN.7) PINE-1, PINE-2, PEGC-A and PEGC-B have subscribed with the PEMC for the PIN status as specified in clause 8.5.X.2.1.In an embodiment where there are multiple PEGC configurations for a PIN, following are steps:In step 1, the PEGCs (e.g., PEGC-A and PEGC-B) shall join the PIN by sending PIN management PINE join into PIN requests to the PEMC. The PIN Client Profile information (supported PIN roles, supported PEGC KPIs, Supported PEGC schedule, UE location) shall be included in the requests. The PEMC shall use this information to determine whether multiple PEGCs are needed to meet the required KPIs of the PIN and which PIN elements (e.g., PEGC-A and PEGC-B) are able to serve as PEGCs. The PEMC shall configure multiple PEGCs (e.g., PEGC-A and PEGC-B) with a role of PEGC if needed. The PEMC shall then send a PIN profile update to the PIN server informing the PIN server that of the multiple PEGCs.In step 2, when PINEs (e.g., PINE-1) send a PIN management PINE join into PIN request to the PEMC, PIN Client Profile information (application client KPIs, application client schedule, UE location) shall be included in the request. The PEMC shall use this information and the PEGC information the PEMC received in step 1 to determine the optimal default and backup PEGCs for the PINE. For example, PEMC assigns PEGC-A as the default PEGC for PINE-1, and PEGC-B as the backup PEGC for PINE-1.In step 3, the PEMC shall send a default PEGC (e.g., PEGC-A) PIN status notification to update its local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.In step 4, the PEMC shall send any backup PEGCs (e.g., PEGC-B) PIN status notification to update their local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC.In step 5, the PEMC shall return a PIN management PINE join into PIN response to PINE-1. The response shall include updated PIN client profile information informing the PINE that it shall use a specified PEGC (e.g., PEGC-A) as its default PEGC, and a specified PEGC (e.g., PEGC-B) as its backup PEGC.In step 6, the PEMC shall send a PIN profile update to the PIN server informing the PIN server of a PEGC (e.g., PEGC-A) serving as the default PEGC for a PINE (e.g., PINE-1) and any PEGCs (e.g., PEGC-B) serving as backup PEGCs for a PINE.In step 7, the PEMC determines whether the PEGC information (default, backup) shared earlier to the PIN elements, which are already part of the PIN need to be updated and if required it notifies the PIN elements about the changes or updates of the PEGC information. This notification or request shall carry the updated PIN dynamic profile information containing the PEGC list information which needs to be used by the PINE-3 or just the updated PEGC list information to be used by the PINE-3. PEMC also notifies the PEGCs about the PIN elements which are authorized to relay the communication via them.In step 8, steps 2 to 6 may be repeated for any additional PINEs joining the PIN. For example, based on PIN client profile information provided by PINE-2, the PEMC configures PEGC-B to serve as the default PEGC for PINE-2 and PEGC-A to serve as the backup PEGC for PINE-2.In an embodiment, a procedure for configuring existing PIN Elements with updated PEGC list information when new PEGC becomes available, includes the following pre-conditions:1. The PEMC is registered and authorized to access the PIN server.2. The required KPIs of the PIN have been configured.3. PINE-1, PINE-2 and PEGC-A have registered to the PEMC and PIN server and are part of the PIN.4. PINE-1, PINE-2, PEGC-A have subscribed with the PEMC for the PIN status as specified in clause 8.5.9.3.2 of 3GPP TS 23.542In step 1, the PEGC-B PIN element joins the PIN as specified 8.5.8.2.1 of 3GPP TS 23.542. In step 2, the PEMC determines the list of PIN elements that can use PEGC-B as default PEGC to relay the PIN traffic and the list of PIN elements that can utilize PEGC-B as back up PEGC and notifies this information to the PEGC-B via PIN status notification. In step 3, the PEMC notifies the PEGC-A about the availability of PEGC-B. In steps 4 & 5, the PEMC notifies the PIN elements PINE-1 and PINE-2 if there is a change in the PEGC configuration determined in step 2. In step 6, the PEMC notifies the PIN server about the availability of PEGC-B.The various actions in methods may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 1-FIG. 3 may be omitted.The embodiment disclosed herein describes systems and methods for notifying PIN elements about an available back up a PEGC. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.Fig. 1aillustrates a sequence diagram for handling triggers based on Vertical Application Layer (VAL) service area ID, in accordance with some embodiments of the present disclosure.With reference to Fig. 1a, the environment 100a comprises of a VAL server 101, a location management server 103 and, a location management client 109 installed in a VAL UE 105. In one embodiment, the location management client 109, may be a standalone system.The operation for handling triggers based VAL service area ID is explained with reference to Fig. 1a. A pre-condition to performing this procedure or operation is that there is a requirement at the VAL server 101 to configure the location reporting trigger including the triggering criteria based on the VAL service area ID. Location reporting of a VAL UE 105 may be requested by a second location management client or by the VAL server 101 itself. A location reporting may be necessitated for assisting with operations such as, without limitation to, geo-fencing, location based notification, proximity marketing, asset tracking, location based authentication and fleet management. A triggering criteria may identify when a requesting client / VAL server is expecting to receive the location report from a requested VAL user / VAL UE. It may include VAL service area ID based criteria when this information flow is from VAL server 101 to the location management server 103. The triggering may be caused due to, for e.g., without limiting to, changes in Service Area Identifier (SAI) changes, changes in E-UTRAN Cell Global Identifier (ECGI) or changes in Radio Access Technology (RAT). A further pre-condition is that, the VAL server 101 may have configured the mapping of VAL service area IDs and their corresponding geographical location / areas at the location management server 109 in the form of a look up table.Furthermore, the steps for performing this procedure are as follows:At step 111a, the location management server 103 receives a location reporting trigger to activate a location reporting procedure from the VAL server 101 for obtaining location information of the VAL UE 105 from the location management client 109. The location reporting trigger includes a triggering criteria based on a VAL service area ID. A triggering criteria may identify when a requesting client / VAL server may expect to receive the location report from a requested VAL user / VAL UE, for e.g., if a location reporting is necessitated for the purpose of geo-fencing, then a location report may be requested for a VAL UE as long as the VAL UE is inside a geographical area or location corresponding to the a VAL service area ID. In another embodiment, a VAL service area ID based trigger may be one of: a change in VAL service area of a VAL UE, a VAL UE entering a particular VAL service area, a VAL UE exiting a particular VAL service area.At step 113a, the location management server 103 checks whether VAL server 101 is authorized to send a location reporting trigger. If the VAL server 101 is found to be valid, then at step 115a, the location management server 103 converts the VAL service area ID into its geographical location or area based on the look up table. In an embodiment, the look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. If the location reporting trigger as received in step 111a includes a triggering criteria based on the VAL service area ID, then the location management server 103 converts the trigger into its corresponding geographical location mapped with the VAL service area ID. Subsequently, the location management server 103 constructs a location reporting configuration update request.At step 117a the location management server 103 sends a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID, to the location management client 109. The geographical area based trigger refers to the converted geographical area based trigger corresponding to the VAL service area ID based trigger as received in Step 113a.At step 119a the location management client 109 replies to the request received at step 117a with a location reporting configuration update response to the location management server 103 with the update result.At step 121a, the location management client 109, stores the new location reporting configuration received in step 117a.The above process may be explained by way of an exemplary scenario. This exemplary scenario, is not to be construed as a limitation:A first VAL server may have configured the following VAL service area IDs mapped with their corresponding geographical location at a first location management server:VAL_Service_Area_ID1: Geographical Area 1 specified by polygon-area and ellipsoid-arc-areaVAL_Service_Area_ID2: Geographical Area 2 specified by polygon-area and ellipsoid-arc-areaThe VAL server sends a location reporting trigger with the following criteria:Report location when the UE enters VAL_Service_Area_ID1Report location when the UE exits VAL_Service_Area_ID2The location management server receives the above location reporting trigger and replaces the VAL service area ID based trigger to the corresponding geographical area as depicted below.Report location when the UE enters Geographical Area 1Report location when the UE exits Geographical Area 2The converted location reporting trigger is then below to the Location management client as part of location reporting configuration update.As used herein, the terms "polygon-area" and "ellipsoid-arc-area" refer to polygon-area and ellipsoid-arc-area as defined in 3GPP TS 23.032.Fig. 1billustrates a sequence diagram for handling triggers based on Vertical Application Layer (VAL) service area ID, in accordance with some embodiments of the present disclosure.With reference to Fig. 1b, the environment 100b comprises of the location management server 103 and the location management client 109 installed in the VAL UE 105. In one embodiment, the location management server 103 and the location management client 109 form a system. In another embodiment, at least one of the location management server 103 or location management client 109 may be part of the system.The operation for handling triggers based VAL service area ID is explained with reference to Fig. 1b. In an embodiment, the location management server 103 may update the location reporting configuration information and inform the location management client 109 of the update at any time by triggering the location reporting configuration update procedure.At step 111b, the location management server 103 updates the location reporting configuration. This may be due to a request from a VAL server or request from a communication network entity or local configuration update. In other words, if there is triggering criteria corresponding to an updated VAL service area ID, based on updates in local configuration of the location management server 103 or an update based on location information requested from other entities (e.g., another location management client or VAL server) or based on the VAL server updating the geographical location information of the existing VAL service area ID, then the location management server 103 updates the location reporting configuration and informs the updated location reporting information to the location management client 109.At step 113b, the location management server 103 sends location reporting configuration update request based on the updated location reporting configuration to the to the location management client 109. The location management server 103 sends location reporting configuration update request message to the location management client(s). The request includes the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message may be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. If the updated location reporting trigger from a VAL server 101 includes the triggering criteria based on the VAL service area ID, then the location management server 103 converts the triggers into geographical area based triggers while sending it to the location management client 109. In an embodiment, different location management clients may be given different location reporting criteria.At step 115b, the location management server 103 receives a reply with the updated location reporting configuration response from the location management client 109. The reply includes the updated location reporting configuration response with an update result.At step 117b, the location management client 109 updates the location reporting configuration previously stored. In another embodiment, the location management client 109 stores the updated location reporting configuration received at step 113b.Fig. 2a illustrates a detailed block diagram of the location management server 103 in accordance with some embodiments of the present disclosure.The location management server 103 for handling triggers based on VAL service area ID includes an Input-Output (I / O) interface 201a, a processor 203a, and a memory 205a. In the present embodiment, data 207a is stored within the memory 205a.The I / O interface 201a is configured to receive the location reporting trigger (comprising a triggering criteria based on a VAL service area ID) and location reporting configuration update response. The I / O interface 201a is configured to send the location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID and the location reporting configuration update request based on the updated location reporting configuration. The I / O interface 201a employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory 205a is communicatively coupled to the processor 203a of the location management server 103. The memory 205a, also, stores processor-executable instructions which cause the processor 203a to execute the instructions for handling triggers based on VAL service area ID. The memory 205a includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor 203a includes at least one data processor for handling triggers based on VAL service area ID. The processor 203a may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data 207a includes, for example, a look up table 209a and miscellaneous data 211a. The look up table 209a comprises a mapping between the plurality of VAL service area ID's and their corresponding geographical locations or areas.In an embodiment, an exemplary look up table is depicted below (Table 2). Th exemplary look up table is not to be construed as a limitation.VAL service Area:Geographical Service Area:VAL service Area 1Geographical Service Area 1VAL service Area 2Geographical Service Area 2VAL service Area 3Geographical Service Area 3In an embodiment, the geographical service area correspond to a set of latitude and longitude coordinates indicating a geographical area.The miscellaneous data 211a stores data, including meta data, and temporary files, generated by the units of the location management server 103 for performing the various functions of the location management server 103.In the embodiment of the present disclosure, the data 207a in the memory 205a are processed by the one or more units 213a (also, referred as units) of the location management server 103. In the embodiment, the one or more units 213a may be implemented as software virtual network functions. In another embodiment, the one or more units 213a may be implemented as dedicated hardware units (e.g., circuits). As used herein, the term unit refers to, for example, an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable　System-on-Chip (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In one embodiment of the present disclosure, the one or more units 213a are communicatively coupled to the processor 203a for handling triggers based on VAL service area ID. The one or more units 213a when configured with the functionality defined in the present disclosure results in a novel hardware.In one implementation, the one or more units 213a include, but are not limited to, a transceiver 215a, a conversion unit 217a, and an updating unit 219a. The one or more units 213a, also, includes miscellaneous units 221a to perform various miscellaneous functionalities of the location management server 103.In an embodiment, the transceiver 215a is configured to receive a location reporting trigger to activate a location reporting procedure from the VAL server 101 for obtaining location information of the VAL UE 105 from the location management client 109. The location reporting trigger includes a triggering criteria based on a VAL service area ID. A triggering criteria may identify when a requesting client / VAL server may expect to receive the location report from a requested VAL user / VAL UE, for e.g., if a location reporting is necessitated for the purpose of geo-fencing, then a location report may be requested for a VAL UE as long as the VAL UE is inside a geographical area or location corresponding to the a VAL service area ID. In another embodiment, a VAL service area ID based trigger may be one of: a change in VAL service area of a VAL UE, a VAL UE entering a particular VAL service area, a VAL UE exiting a particular VAL service area.The transceiver 215a is configured to check whether VAL server 101 is authorized to send a location reporting trigger.If the VAL server 101 is found to be valid, then the conversion unit 217a converts the VAL service area ID into its geographical location or area based on the look up table 209a. In an embodiment, the look up table 209a comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. If the location reporting trigger as received by the transceiver 215a, includes a triggering criteria based on the VAL service area ID, then the conversion unit 217a converts the trigger into its corresponding geographical location mapped with the VAL service area ID.Subsequently, the transceiver 215a is configured to construct a location reporting configuration update request and sends a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID, to the location management client 109. The geographical area based trigger refers to the geographical area based trigger, converted by the conversion unit 217a, corresponding to the VAL service area ID based trigger.The transceiver 215a receives from the location management client 109 a location reporting configuration update response with the update result as a reply to the location reporting configuration update request sent to the location management client 109.In an embodiment, the updating unit 219a is configured to store the new location reporting configuration received in step 117a.In another embodiment, the updating unit 219a, may update the location reporting configuration information and inform the location management client 109 of the update at any time by triggering the location reporting configuration update procedure. The updates in the location reporting configuration may be due to a request from a VAL server or request from a communication network entity or local configuration update. In other words, if there is triggering criteria corresponding to an updated VAL service area ID, based on updates in local configuration of the location management server 103 or an update based on location information requested from other entities (e.g., another location management client or VAL server) or based on the VAL server updating the geographical location information of the existing VAL service area ID, then the updating unit 219a updates the location reporting configuration and informs the updated location reporting information to the location management client 109.The transceiver 215a, sends the location reporting configuration update request based on the updated location reporting configuration to the to the location management client 109. The transceiver 215a sends location reporting configuration update request message to the location management client(s). The request includes the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message may be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. If the updated location reporting trigger from a VAL server includes the triggering criteria based on the VAL service area ID, then the conversion unit 217a converts the triggers into geographical area based triggers while sending it to the location management client 109. In an embodiment, different location management clients may be given different location reporting criteria.The transceiver 215a, receives a reply with the updated location reporting configuration response from the location management client 109. The reply includes the updated location reporting configuration response with an update result.Fig. 2billustrates a detailed block diagram of the location management client 109 in accordance with some embodiments of the present disclosure.The location management client 109 for handling triggers based on VAL service area ID includes an Input-Output (I / O) interface 201b, a processor 203b, and a memory 205b. In the present embodiment, data 207b is stored within the memory 205b. In an embodiment, the location management client 109 may be installed in the VAL UE 105. In another embodiment, the location management client 109, may be a standalone system.The I / O interface 201b is configured to receive the location reporting configuration update request, the updated location reporting configuration update request and sends the location reporting configuration update response and the updated location reporting configuration update response. The I / O interface 201b employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory 205b is communicatively coupled to the processor 203b of the location management client 109. The memory 205b, also, stores processor-executable instructions which cause the processor 203b to execute the instructions for handling triggers based on VAL service area ID. The memory 205b includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor 203b includes at least one data processor for handling triggers based on VAL service area ID. The processor 203b may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data 207b includes, for example, a location reporting configuration 209b and miscellaneous data 211b. The location reporting configuration 209b maybe stored or updated based on subsequent steps.Miscellaneous data 211b: The miscellaneous data 211b stores data, including meta data, and temporary files, generated by the units of the location management client 109 for performing the various functions of the location management client 109.In the embodiment of the present disclosure, the data 207b in the memory 205b are processed by the one or more units 213b (also, referred as units) of the location management client 109. In the embodiment, the one or more units 213b may be implemented as software virtual network functions. In another embodiment, the one or more units 213b may be implemented as dedicated hardware units (e.g., circuits). As used herein, the term unit refers to, for example, an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable　System-on-Chip (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In one embodiment of the present disclosure, the one or more units 213b are communicatively coupled to the processor 203b for handling triggers based on VAL service area ID. The one or more units 213b when configured with the functionality defined in the present disclosure results in a novel hardware.In one implementation, the one or more units 213b include, but are not limited to, a transceiver 215b, a storing unit 217b, and an updating unit 219b. The one or more units 213b, also, includes miscellaneous units 221b to perform various miscellaneous functionalities of the location management client 109.The transceiver 215b is configured to receive the location reporting configuration update request comprising the geographical area based trigger corresponding to the VAL service area ID, from the location management server 103.In response to the request, the transceiver 215b sends the location reporting configuration update response to the location management server 103 with the update result.The storing unit 217b stores the new location reporting configuration received by the transceiver 21 5b.In another embodiment, the transceiver 215b receives from the location management server 103, location reporting configuration update request based on the updated location reporting configuration. The request includes the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message may be received over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. In an embodiment, different location management clients may receive different location reporting criteria.The transceiver 215b sends a reply to the location management server 103 comprising of the updated location reporting configuration response. The reply includes the updated location reporting configuration response with an update result.The updating unit 219b, may be configured to update the location reporting configuration 209b previously stored, based on the updated location reporting configuration received.Fig. 3a illustrates a flowchart illustrating a method 300a for handling triggers based on VAL service area ID, in accordance with some embodiments of the present disclosure.The method 300a may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method 300a is described is not intended to be construed as a limitation, and any number of the described method operation steps may be combined in any order to implement the method. Additionally, individual operation steps may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.At operation step 301a, the processor 203a of the location management server 103 receives a location reporting trigger to activate a location reporting procedure from the VAL server 101 for obtaining location information of the VAL UE 105 from the location management client 109. The location reporting trigger includes a triggering criteria based on a VAL service area ID. A triggering criteria may identify when a requesting client / VAL server may expect to receive the location report from a requested VAL user / VAL UE, for e.g., if a location reporting is necessitated for the purpose of geo-fencing, then a location report may be requested for a VAL UE as long as the VAL UE is inside a geographical area or location corresponding to the a VAL service area ID. In another embodiment, a VAL service area ID based trigger may be one of: a change in VAL service area of a VAL UE, a VAL UE entering a particular VAL service area, a VAL UE exiting a particular VAL service area.At operation step 303a, the processor 203a of the location management server 103 converts the VAL service area ID into its geographical location or area based on the look up table. In an embodiment, the look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas. If the location reporting trigger as received in operation step 303a includes a triggering criteria based on the VAL service area ID, then the processor 203a of the location management server 103 converts the trigger into its corresponding geographical location mapped with the VAL service area ID. Subsequently, the processor 203a of the location management server 103 constructs a location reporting configuration update request.At operation step 305a, the processor 203a of the location management server 103 sends a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID, to the location management client 109. The geographical area based trigger refers to the converted geographical area based trigger corresponding to the VAL service area ID based trigger as received in operation step 303a.Subsequently, the method 300a comprises of the processor 203a of the location management server 103 receiving from the location management client 109, a replies to the request sent at operation step 305a with a location reporting configuration update response, with the update result.Subsequently, the method 300a comprises of the processor 203a of the location management server 103 updating the location reporting configuration. This may be due to a request from the VAL server 101 or request from a communication network entity or local configuration update. In other words, if there is triggering criteria corresponding to an updated VAL service area ID, based on updates in local configuration of the location management server 103 or an update based on location information requested from other entities (e.g., another location management client or VAL server) or based on the VAL server updating the geographical location information of the existing VAL service area ID, then the processor 203a of the location management server 103 updates the location reporting configuration and informs the updated location reporting information to the location management client 109.Subsequently, the method 300a comprises of the processor 203a of the location management server 103 sending location reporting configuration update request based on the updated location reporting configuration to the to the location management client 109. The processor 203a of the location management server 103 sends location reporting configuration update request message to the location management client(s). The request includes the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message may be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. If the updated location reporting trigger from the VAL server 101 includes the triggering criteria based on the VAL service area ID, then the location management server 103 converts the triggers into geographical area based triggers while sending it to the location management client 109. In an embodiment, different location management clients may be given different location reporting criteria.Subsequently, the method 300a comprises of the processor 203a of the location management server 103 receiving a reply with the updated location reporting configuration response from the location management client 109. The reply includes the updated location reporting configuration response with an update result.Fig. 3b illustrates a flowchart illustrating a method 300a for handling triggers based on VAL service area ID, in accordance with some embodiments of the present disclosure.The method 300b may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method 300b is described is not intended to be construed as a limitation, and any number of the described method operation steps may be combined in any order to implement the method. Additionally, individual operation steps may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.At operation step 301b, the processor 203b of the location management client 109 receives from the location management server 103, the location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.At operation step 303b, the processor 203b of the location management client 109, replies to the request received at operation step 301b with a location reporting configuration update response to the location management server 103 with the update result.At operation step 305b, the processor 203b of the location management client 109, stores the new location reporting configuration received in operation step 301b.The method 300b further comprises of, receiving by the processor 203b of the location management client 109 location reporting configuration update request based on the updated location reporting configuration from the location management server 103. The request includes the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message may be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. In an embodiment, different location management clients may be given different location reporting criteria.The method 300b further comprises of, sending by the processor 203b of the location management client 109 a reply with the updated location reporting configuration response to the location management server 103. The reply includes the updated location reporting configuration response with an update result.The method 300b further comprises of, the processor 203b of the location management client 109 updating the location reporting configuration previously stored. In another embodiment, the processor 203b of the location management client 109 stores the updated location reporting configuration.In some embodiments, Fig. 4 illustrates a block diagram of an exemplary computer system 400 for implementing embodiments consistent with the present disclosure. In some embodiments, the computer system 400 may be the VAL server 101 or the location management server 103 or the location management client 109 or the VAL UE 105 having installed the location management client 109. The computer system 400 comprises a processor (also referred as a processor 402 in this Fig. 4) that is used for handling triggers based on VAL service area ID. The processor 402 may include at least one data processor for executing program components for executing user or system-generated business processes. The processor 402 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The processor 402 may be disposed in communication with input devices 410 and output devices 411 via I / O interface 401. The I / O interface 401 may employ communication protocols / methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), High-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE), WiMax, or the like), etc.Using the I / O interface 401, computer system 400 may communicate with input devices 410 and output devices 411.In some embodiments, the processor 402 may be disposed in communication with a communication network 409 via a network interface 403. The network interface 403 may communicate with the communication network 409. The network interface 403 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc. Using the network interface 403 and the communication network 409, the computer system 400 may communicate with one or more communication network entities.In an embodiment, when the computer system 400 corresponds to the VAL server 101, the computer system 400 may be in communication with at least one of: the location management server 103, the location management client 109 and the VAL UE 105 having installed the location management client 109, using the network interface 403 and the communication network 409.In an embodiment, when the computer system 400 corresponds to the location management server 103, the computer system 400 may be in communication with at least one of: the VAL server 101, the location management client 109 and the VAL UE 105 having installed the location management client 109, using the network interface 403 and the communication network 409.In an embodiment, when the computer system 400 corresponds to the location management client 109, the computer system 400 may be in communication with at least one of: the VAL server 101 and the location management server 103, using the network interface 403 and the communication network 409.In an embodiment, when the computer system 400 corresponds to the VAL UE 105 having installed the location management client 109, the computer system 400 may be in communication with at least one of: the VAL server 101 and the location management server 103, using the network interface 403 and the communication network 409.The communication network 409 may be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network 409 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), etc., to communicate with each other.Further, the communication network 409 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc. In some embodiments, the processor 402 may be disposed in communication with a memory 405 (e.g., Random Access Memory (RAM), ROM, etc. not shown in Fig. 4) via a storage interface 404. The storage interface 404 may connect to memory 405 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fibre channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The memory 405 may store a collection of program or database components, including, without limitation, a user interface 406, an operating system 407, a web browser 408 etc. In some embodiments, the computer system　400 may store user / application data, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.Operating system　407　may facilitate resource management and operation of computer system　400. Examples of operating systems include, without limitation, APPLE®MACINTOSH®OS X®, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION®(BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX®DISTRIBUTIONS (E.G., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM®OS / 2®, MICROSOFT®WINDOWS®(XP®, VISTA® / 7 / 8, 10 etc.), APPLE®IOS®, GOOGLETMANDROIDTM, BLACKBERRY®OS, or the like. User interface　406　may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to computer system　400, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple®Macintosh®operating systems' Aqua®, IBM®OS / 2®, Microsoft®Windows®(e.g., Aero, Metro, etc.), web interface libraries (e.g., ActiveX®, Java®,　Javascript®, AJAX, HTML, Adobe®Flash®, etc.), or the like.　The computer system　400　may implement web browser　408　stored program components. Web browser　408　may be a hypertext viewing application, such as MICROSOFT®INTERNET EXPLORER®, GOOGLETMCHROMETM, MOZILLA®FIREFOX®, APPLE®SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 408 may utilize facilities such as AJAX, DHTML, ADOBE®FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. The computer system 400　may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ACTIVEX®, ANSI®C++ / C#, MICROSOFT®, NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT®exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 400 may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE®MAIL, MICROSOFT®ENTOURAGE®, MICROSOFT®OUTLOOK®, MOZILLA®THUNDERBIRD®, etc.Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD), Read-Only Memory (ROMs), Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.Fig. 5 illustrates a general environment for dynamically notifying PEGC availability in a PIN.The general environment comprises of a Personal IOT Network (PIN) 50. The PIN 500 comprises of a PIN Element with Management Capability (PEMC) 501, a PEGC-A 502, a PEGC-B 503, one or more PINE's 504 and a PIN Server 505.In an embodiment, the one or more PEGC's may be in communication with the one or more PINE's by using, without limitation to, WLAN communication or Bluetooth communication or any non-3G PP communication .In some embodiments, the PEGC-A 502 and the PEGC-B 503 may be referred to as one or more PEGC's. Each of the one or more PEGC's, the PEGC-A 502 and the PEGC-B 503 may be the PEGC 700 as described in Fig. 7b.In an embodiment, the one or more PINE's 504 may include the PEMC 501, the one or more PEGC's, which is inclusive of the PEGC-A 502 and the PEGC-B 503.In an embodiment, in a first scenario, the PEGC-A 502 may be a default PEGC for one or more PINE's 504 of the PIN 500. The PEGC-B 503 may then join the PIN 500 and may be assigned the role of back-up PEGC subsequently.In another embodiment, in a second scenario, the PEGC-A 502 may be a default PEGC for one or more PINE's 504 of the PIN 500. The PEGC-A 502, may leave the PIN 500 and subsequently, PEGC-B 503 may be assigned the role of the default PEGC.In another embodiment, in a third scenario, the PEGC-A 502 may be a default PEGC for one or more PINE's 504 of the PIN 500. The PEGC-A 502, may become temporarily unavailable due to, without limitation to, power outage or a crash, or temporary maintenance activity or other implementation specific reason. In such a scenario, a PEGC-B 503 may be assigned the role of the default PEGC.In another embodiment, in a fourth scenario, each of the one or more PEGC's may be assigned as a default PEGC to a first set of the one or more PINE's 504 and as a backup PEGC to a second set of the one or more PINE's 504, based on an update an update in the dynamic PIN profile.In all the above scenarios, an update in the dynamic PIN profile, which comprises of a mapping of the one or more PINE's 504 of the PIN 500 and their corresponding default PEGC's and their corresponding backup PEGC'S, may be dynamically notified to the one or more existing PINE's 504 of the PIN 500 by the method disclosed in the following embodiments / as described herein.Fig. 6a illustrates a sequence diagram for notifying PEGC availability in the PIN.The operation for notifying PEGC availability in the PIN is explained with reference to Fig. 6a. A pre-condition to performing this procedure or operation is that PEGC-A 502 is currently the default PEGC of the PIN 500 and no other PINE is assigned as a back-up PEGC, that dynamic PIN profile is available at the PEMC 501 and that PEGC-B 503 has the capability to perform the role of a PEGC. The PEGC-B 503 is registered with the PIN 500 by a PIN registration request message.Furthermore, the steps for performing this procedure are as follows:At step 603a, the PEMC 501, receives a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 503 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (not indicated in Fig. 6a. However, a similar procedure as followed for PEGC-B (described below) may be followed for the case when PEGC-A 502 leaves the PIN 500. A PEGC-A 502 leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PEMC 501 its capability to perform the role of a PEGC.At step 605a, the PEMC 501 determines availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the PEMC 501 then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.At step 607a, based on the availability of each of the one more PEGC's determined at step 605a, the PEMC 501 updates the dynamic PIN profile. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's 504 and as a backup PEGC to a second set of the one or more PINE's 504. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PINE'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.At step 609a, the PEMC 501, sends a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the PEMC 501, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 6b illustrates another sequence diagram for notifying PEGC availability in the PIN.The operation for notifying PEGC availability in the PIN 500 is explained with reference to Fig. 6b. A pre-condition to performing this procedure or operation is that PEGC-A 502 is currently the default PEGC of the PIN 500 and no other PINE is assigned as a back-up PEGC, that dynamic PIN profile is available at the PEMC 501 and that PEGC-B 503 has the capability to perform the role of a PEGC. The PEGC-B 503 is registered with the PIN 500 by a PIN registration request message.Furthermore, the steps for performing this procedure are as follows:At step 603b, the PEGC-B 503 sends a message to the PEMC 501, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 503 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (not indicated in Fig. 6a. However, a similar procedure as followed for PEGC-B (described below) may be followed for the case when PEGC-A 502 leaves the PIN 500. A PEGC-A 502 leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PEMC 501 its capability to perform the role of a PEGC.At step 605b, the PEMC 501 determines availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the PEMC 501 then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.At step 607b, based on the availability of each of the one more PEGC's determined at step 605b, the PEMC 501 updates the dynamic PIN profile. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PINE's. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.At step 609b, the PEMC 501 sends a notification to the PEGC-B 503 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile.At step 611b, the PEGC-B 503, sends a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment the PEGC-B 503, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 6c illustrates another sequence diagram for notifying PEGC availability in the PIN.The operation for notifying PEGC availability in the PIN is explained with reference to Fig. 6c. A pre-condition to performing this procedure or operation is that PEGC-A 502 is currently the default PEGC of the PIN 500 and no other PINE is assigned as a back-up PEGC, that dynamic PIN profile is available at the PEMC 501 and that PEGC-B 503 has the capability to perform the role of a PEGC. The PEGC-B 503 is registered with the PIN 500 by a PIN registration request message.Furthermore, the steps for performing this procedure are as follows:At step 603c, the PIN server 505, receives a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 503 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (not indicated in Fig. 6a. However, a similar procedure as followed for PEGC-B (described below) may be followed for the case when PEGC-A 502 leaves the PIN 500. A PEGC-A 502 leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PIN server 505 its capability to perform the role of a PEGC.At step 605c, the PIN server 505 determines availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the PIN server 505 then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.At step 607c, based on the availability of each of the one more PEGC's determined at step 605c, the PIN server 505 updates the dynamic PIN profile. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PEGC'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.At step 609c, PIN server 505, sends a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the PIN server 505, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 6d illustrates another sequence diagram a method 600d, for dynamically notifying PEGC availability in a PIN with multiple PEGC configurations.At step 1 of the method 600d, two or more PEGC's (for, e.g., as depicted herein, PEGC-A and PEGC-B) may join the PIN 500 by sending a PIN join request message to the PEMC 501. PIN client profile information (which may include, without limitation to, supported PIN roles, supported PEGC KPIs, supported PEGC schedules, User Equipment (UE location) may e included in the join request message. The PEMC 501 may use the PIN Client Profile information to determine whether multiple PEGCs are required to meet the required KPIs of the PIN 500 and which PINE's (or, e.g., as depicted herein, PEGC-A and PEGC-B) would be able to serve as default PEGCs or backup PEGC's. In an embodiment, the PEMC 501 may configure multiple PEGCs (or, e.g., as depicted herein, PEGC-A and PEGC-B) with the role of default PEGC if required based on the PIN client profile information. The PEMC 501 may then send a dynamic PIN profile update to the PIN server 505, indicating the usage of multiple PEGCs as the default PEGC.At step 2 of the method 600d, one or more PINEs 504 (for e.g., as depicted herein, PINE-1) may send aPIN management PINE join into PIN requestto the PEMC 501 which includes the PIN client profile information (which may include without limitation to, application client KPIs, application client schedule, UE location etc). The PEMC 501 may use the PIN client profile information and the PEGC's PIN client profile information received at step 1 of the method 600d, to determine the default and backup PEGCs for the PINE (PINE-1). For example, the PEMC 501 may assign PEGC-A 502 as the default PEGC for PINE-1, and PEGC-B 503 as the backup PEGC for PINE-1.At step 3 of the method 600d, the PEMC 501 may send to the default PEGC / PEGC's (e.g., PEGC-A), a PIN status notification, requesting it to update its local PIN profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC (e.g., PEGC-A).At step 4 of the method 600d, the PEMC 501 may send the backup PEGC / PEGC's (e.g., PEGC-B), a PIN status notification, requesting it to update its local PIN Profile information to reflect that a PINE (e.g., PINE-1) is authorized to relay PIN communications via the PEGC (e.g., PEGC-A).At step 5 of the method 600d, the PEMC 501 may send aPIN management PINE join into PINresponse to the PINE-1. The response may include updated PIN client profile information, including information regarding the PEGC that has been assigned as the default PEGC and the backup PEGC (here, PEGC-A and PEGC-B respectively).At step 6 of the method 600d, the PEMC 501 may send adynamic PIN profile updateto the PIN server 505, informing the PIN server 505 of the PEGC (e.g., PEGC-A) serving as the default PEGC for a PINE (e.g., PINE-1) and any PEGCs (e.g., PEGC-B) serving as the backup PEGCs for the PINE (e.g., PINE-1).At step 7 of the method 600d, the PEMC 501, determines whetherdynamic PIN profileinformation sent to the one or more PINE's (which are already part of the PIN 500) needs to be updated. In the case that the PEMC 501 determines that there is a requirement for it to update the dynamic PIN profile, then the PEMC 501 notifies the PIN elements about the updates in the PEGC information. This notification may comprise of the updated dynamic PIN profile information containing the PEGC information which needs to be used by the PINE-3, which is an existing PINE in the PIN 500, or only the updated PEGC list information to be used by the PINE-3. The PEMC 501 also notifies the one or more PEGCs of the PIN elements which are authorized to relay communication through them.At step 8 of the method 600d, steps 2 to 6 of the method 600d may be repeated for any additional PINEs joining the PIN 500. For example, based on PIN client profile information provided by PINE-2, the PEMC 501 may configure PEGC-B to serve as the default PEGC for PINE-2 and PEGC-A to serve as the backup PEGC for PINE-2.Fig. 6e illustrates another sequence diagram for notifying PEGC availability in the PIN.Fig. 6e illustrates a method 600e for configuring existing one or more PINE's 504 with updated PEGC list information in a scenario where a new PEGC becomes available. A pre-condition to performing this method is that the PEMC 501 is registered and authorized to access the PIN server 505, that the required KPIs of the PIN 500 have been configured, that PINE-1, PINE-2 and PEGC-A 502, as depicted in Fig. 6e, have been registered to the PEMC 501 and the PIN server 505 and are part of the PIN 500, and that the PINE-1, PINE-2, PEGC-A 502 have subscribed with the PEMC 501 for the PIN status as specified in clause 8.5.9.3.2 of 3GPP TS 23.542.At step 1 of the method 600e, the PEGC-B 503 joins the PIN 500 as specified 8.5.8.2.1 of 3GPP TS 23.542.At step 2 of the method 600e, the PEMC 501 determines the list of PINE's that can use PEGC-B 503 as the default PEGC to relay the PIN traffic and the list of PIN elements that can utilize PEGC-B 503 as the back up PEGC and notifies this information to the PEGC-B 503 via PIN status notification message.At step 3 of the method 600e, the PEMC notifies the PEGC-A 502 about the availability of PEGC-B 503.At step 4 and step 5 of the method 600e, the PEMC 501 notifies the PINE-1 and PINE-2 respectively if there is a change in the PEGC configuration determined in step 2 of the method 600e.At step 6 of the method 600e, the PEMC 501 notifies the PIN server 505 about the availability of PEGC-B 503.Fig. 7a illustrates a detailed block diagram of a PEMC 501, in accordance with some embodiments of the present disclosure.The PEMC 501 for dynamically notifying PEGC availability in the PIN 500 includes an Input-Output (I / O) interface 701a, a processor 703a, and a memory 705a. In the present embodiment, data 707a is stored within the memory 705a.The I / O interface 701a is configured to receive a message from one or more PEGC's indicating its connection with the PIN 500. The I / O interface 701a is configured to send a notification indicating the updated dynamic PIN profile. The I / O interface 701a employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory 705a is communicatively coupled to the processor 703a of the PEMC 501. The memory 705a, also, stores processor-executable instructions which cause the processor 703a to execute the instructions for dynamically notifying PEGC availability in the PIN 500. The memory 705a includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor 703a includes at least one data processor for dynamically notifying PEGC availability in the PIN 500. The processor 703a may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data 707a includes, for example, the dynamic PIN profile 709a and miscellaneous data 711a. The dynamic PIN profile 709a comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.The miscellaneous data 711a stores data, including meta data, and temporary files, generated by the units of the PEMC 501 for performing the various functions of the PEMC 501.In the embodiment of the present disclosure, the data 707a in the memory 705a are processed by the one or more units 713a (also, referred as units) of the PEMC 501. In the embodiment, the one or more units 713a may be implemented as software virtual network functions. In another embodiment, the one or more units 713a may be implemented as dedicated hardware units (e.g., circuits). As used herein, the term unit refers to, for example, an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable　System-on-Chip(PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In one embodiment of the present disclosure, the one or more units 713a are communicatively coupled to the processor 703a for dynamically notifying PEGC availability in the PIN 500. The one or more units 713a when configured with the functionality defined in the present disclosure results in a novel hardware.In one implementation, the one or more units 713a include, but are not limited to, a transceiver 715a, an availability determining unit 717a, and an updating unit 719a. The one or more units 713a, also, includes miscellaneous units 721a to perform various miscellaneous functionalities of the PEMC 501.In an embodiment, the transceiver 715a is configured to receive a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message).In an embodiment, the availability determining unit 717a is configured to determine availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the availability determining unit 717a then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.In an embodiment, the updating unit 719a is configured update the dynamic PIN profile based on the availability of each of the one more PEGC's determined by the availability determining unit 717a. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's 504 and as a backup PEGC to a second set of the one or more PINE's 504. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PEGC'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.The transceiver 715a may then be configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the transceiver 715a, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them, from the transceiver 715a. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 7billustrates a detailed block diagram of a PEGC, in accordance with some embodiments of the present disclosure.Fig. 7billustrates a detailed block diagram of a PEGC 700, in accordance with some embodiments of the present disclosure.The PEGC 700 for dynamically notifying PEGC availability in the PIN 500 includes an Input-Output (I / O) interface 701b, a processor 703b, and a memory 705b. In the present embodiment, data 707b is stored within the memory 705b.The I / O interface 701b is configured to send and receive communication. The I / O interface 701b employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory 705b is communicatively coupled to the processor 703b of the PEGC 700. The memory 705b, also, stores processor-executable instructions which cause the processor 703b to execute the instructions for dynamically notifying PEGC availability in the PIN 500. The memory 705b includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor 703b includes at least one data processor for dynamically notifying PEGC availability in the PIN 500. The processor 703b may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data 707b includes, for example, the dynamic PIN profile 709b and miscellaneous data 711b. The dynamic PIN profile 709b comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.The miscellaneous data 711b stores data, including meta data, and temporary files, generated by the units of the PEGC 700 for performing the various functions of the PEGC 700.In the embodiment of the present disclosure, the data 707b in the memory 705b are processed by the one or more units 713b (also, referred as units) of the PEGC 700. In the embodiment, the one or more units 713b may be implemented as software virtual network functions. In another embodiment, the one or more units 713b may be implemented as dedicated hardware units (e.g., circuits). As used herein, the term unit refers to, for example, an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable　System-on-Chip(PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In one embodiment of the present disclosure, the one or more units 713b are communicatively coupled to the processor 703b for dynamically notifying PEGC availability in the PIN 500. The one or more units 713b when configured with the functionality defined in the present disclosure results in a novel hardware.In one implementation, the one or more units 713b include, but are not limited to, a transceiver 715b and miscellaneous units 717b to perform various miscellaneous functionalities of the PEGC 700.In an embodiment, the transceiver 715b is configured to send a message indicating its connection with the PIN 500, to at least one of the PEMC 501 and the PIN server 505. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message). In an embodiment, the message indicating PEGC's connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the transceiver 715b may indicate to the PEMC 501 its capability to perform the role of a PEGC.The transceiver 715b may then be configured to receive a notification indicating the updated dynamic PIN profile from one of: the PEMC 501 or the PIN server 500. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile.In an embodiment, the transceiver 715b is configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. In an embodiment the transceiver 715b, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 7cillustrates a detailed block diagram of a PIN server 505, in accordance with some embodiments of the present disclosure.The PIN server 505 for dynamically notifying PEGC availability in the PIN 500 includes an Input-Output (I / O) interface 701c, a processor 703c, and a memory 705c. In the present embodiment, data 707c is stored within the memory 705c.The I / O interface 701c is configured to receive a message from one or more PEGC's indicating its connection with the PIN 500. The I / O interface 701c is configured to send a notification indicating the updated dynamic PIN profile. The I / O interface 701c employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory 705c is communicatively coupled to the processor 703c of the PIN server 505. The memory 705c, also, stores processor-executable instructions which cause the processor 703c to execute the instructions for dynamically notifying PEGC availability in the PIN 500. The memory 705c includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor 703c includes at least one data processor for dynamically notifying PEGC availability in the PIN 500. The processor 703c may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data 707c includes, for example, the dynamic PIN profile 709c and miscellaneous data 711c. The dynamic PIN profile 709c comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.The miscellaneous data 711c stores data, including meta data, and temporary files, generated by the units of the PIN server 505 for performing the various functions of the PIN server 505.In the embodiment of the present disclosure, the data 707c in the memory 705c are processed by the one or more units 713c (also, referred as units) of the PIN server 505. In the embodiment, the one or more units 713c may be implemented as software virtual network functions. In another embodiment, the one or more units 713c may be implemented as dedicated hardware units (e.g., circuits). As used herein, the term unit refers to, for example, an Application Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable　System-on-Chip(PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In one embodiment of the present disclosure, the one or more units 713c are communicatively coupled to the processor 703c for dynamically notifying PEGC availability in the PIN 500. The one or more units 713c when configured with the functionality defined in the present disclosure results in a novel hardware.In one implementation, the one or more units 713c include, but are not limited to, a transceiver 715c, an availability determining unit 719c, and an updating unit 719a. The one or more units 713c, also, includes miscellaneous units 721c to perform various miscellaneous functionalities of the PIN server 505.In an embodiment, the transceiver 715c is configured to receive a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message).In an embodiment, the availability determining unit 719c is configured to determine availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the availability determining unit 719c then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC, to the one or more PINE's 504.In an embodiment, the updating unit 719a is configured update the dynamic PIN profile based on the availability of each of the one more PEGC's determined by the availability determining unit 719c. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PEGC'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.The transceiver 715c may then be configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the transceiver 715a, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them, from the transceiver 715c. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 8a shows a flowchart illustrating a method for dynamically notifying PEGC availability in a PIN.The method 800a may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method 800a is described is not intended to be construed as a limitation, and any number of the described method operation steps may be combined in any order to implement the method. Additionally, individual operation steps may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.At operation step 801a, the processor 703a of the PEMC 501, is configured to receive a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PEMC 501 its capability to perform the role of a PEGC.At operation step 803a, the processor 703a of the PEMC 501, is configured to determine availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the processor 703a, then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.At operation step 805a, the processor 703a of the PEMC 501, is configured to update the dynamic PIN profile based on the availability of each of the one more PEGC's determined at step 803a. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PEGC'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.At operation step 807a, the processor 703a of the PEMC 501, is configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the PEMC 501, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them, from the processor 703a of the PEMC 501. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 8b shows a flowchart illustrating a method for dynamically notifying PEGC availability in the PIN.The method 800b may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method 800b is described is not intended to be construed as a limitation, and any number of the described method operation steps may be combined in any order to implement the method. Additionally, individual operation steps may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.At operation step 801b, the processor 703b of the PEGC 700, is configured to send a message indicating its connection with the PIN 500, to at least one of the PEMC 501 and the PIN server 505. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PEMC 501 its capability to perform the role of a PEGC.At operation step 803b, the processor 703b of the PEGC 700, is configured to receive a notification indicating the updated dynamic PIN profile from one of: the PEMC 501 or the PIN server 500. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile.At operation step 805b, the processor 703b of the PEGC 700, is configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment the PEGC-B 503, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.Fig. 8c shows a flowchart illustrating a method for dynamically notifying PEGC availability in the PIN.The method 800c may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method 800c is described is not intended to be construed as a limitation, and any number of the described method operation steps may be combined in any order to implement the method. Additionally, individual operation steps may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.At operation step 801c, the processor 703a of the PIN server 505, is configured to receive a message from one or more PEGC's, indicating its connection with the PIN 500. The connection with the PIN 500 may correspond to one of: the PEGC-B 502 joining the PIN 500 or the PEGC-A 502 leaving the PIN 500 (the following steps are described for the scenario in which a PEGC joins the PIN 500. However, a similar procedure may be followed for a scenario in which a PEGC leaves the pin 500. A PEGC leaving may be indicated via a PIN leaving message). In an embodiment, the message from one or more PEGC's, indicating its connection with the PIN 500, may be a PIN join request message, using the existing procedure specified in 3GPP TR 23.700-78. At the time of joining the PIN 500, the PEGC-B 503 may indicate to the PIN server 505 its capability to perform the role of a PEGC.At operation step 803c, the processor 703a of the PIN server 505, is configured to determine availability of each of the one more PEGC's based on the message received from respective one or more PEGC's. After having received the connection indication message from the PEGC-B 503, the processor 703a, then determines availability of each of the one or more PEGC's so as to determine which of the one or more PEGC's can be assigned the role of default PEGC or as a backup PEGC to the one or more PINE's 504.At operation step 805c, the processor 703a of the PIN server 505, is configured to update the dynamic PIN profile based on the availability of each of the one more PEGC's determined at step 803c. Updating the dynamic PIN profile comprises of assigning each of the one or more PEGC's currently available, as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's. In an embodiment, a PEGC may act as the default PEGC for the first set of PINE's while acting as a backup PEGC for the second set of PEGC'S. The dynamic PIN profile comprises of a mapping of the one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S. In an embodiment, a PINE of the one or more PINES's 504 may have more than one backup PEGC.At operation step 807c, the processor 703a of the PIN server 505, is configured to send a notification to the one or more PINE's 504 indicating the updated dynamic PIN profile. In an embodiment, the notification indicating the updated dynamic PIN profile, comprises of the updated dynamic PIN profile. As the one or more PINE's 504 is inclusive of the one or more PEGC's (which is in-turn inclusive of the PEGC-A 502 and the PEGC-B 503), the notification indicating the updated dynamic PIN profile may also be received by the one or more PEGC's. In an embodiment the PIN server 505, may send a notification to the one more PINE's 504 indicating the update in the PEGC details (corresponding to the respective default PEGC or back-up PEGC assigned to them) assigned to each of the one or more PINE's 504.In another embodiment, only a sub-set of the one or more PINE's 504 may receive the notification indicating updated dynamic PIN profile or updated PEGC details based on whether or not there is a change in the dynamic PIN profile corresponding to them or whether there is a change in the PEGC details assigned to them, from the processor 703a of the PIN server 505. The sub-set of the one or more PINE's 504 for which there are no changes in the dynamic PIN profile corresponding to them or for which there are no changes in the in the PEGC details assigned to them, may not receive the notification indicating updated dynamic PIN profile.In some embodiments, Fig. 9 illustrates a block diagram of an exemplary computer system 900 for implementing embodiments consistent with the present disclosure. In some embodiments, the computer system 900 may be the PEMC 501, the PEGC-A 502, the PEGC-B 503, the one or more PINE's 504, the PIN server 505 or the PEGC 700. The computer system 900 comprises a processor (also referred as a processor 902 in this Fig. 9) that is used for PEGC availability in the PIN 500. The processor 902 may include at least one data processor for executing program components for executing user or system-generated business processes. The processor 902 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The processor 902 may be disposed in communication with input devices 910 and output devices 911 via I / O interface 901. The I / O interface 901 may employ communication protocols / methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), High-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE), WiMax, or the like), etc.Using the I / O interface 901, computer system 900 may communicate with input devices 910 and output devices 911.In some embodiments, the processor 902 may be disposed in communication with a communication network 909 via a network interface 903. The network interface 903 may communicate with the communication network 909. The network interface 903 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc. Using the network interface 903 and the communication network 909, the computer system 900 may communicate with one or more communication network entities.In an embodiment, when the computer system 900 corresponds to the PEMC 501, the computer system 900 may be in communication with at least one of: the PEGC-A 502, the PEGC-B 503, the one or more PINE's 504, the PIN server 505 and the PEGC 700, using the network interface 903 and the communication network 909.In an embodiment, when the computer system 900 corresponds to the PEGC-A 502, the computer system 900 may be in communication with at least one of: the PEMC 501, the PEGC-B 503, the one or more PINE's 504, the PIN server 505 and the PEGC 700, using the network interface 903 and the communication network 909.In an embodiment, when the computer system 900 corresponds to the PEGC-B 503, the computer system 900 may be in communication with at least one of: the PEMC 501, the PEGC-A 502, the one or more PINE's 504, the PIN server 505 and the PEGC 700, using the network interface 903 and the communication network 909.In an embodiment, when the computer system 900 corresponds to the one or more PINE's 504, the computer system 900 may be in communication with at least one of: the PEMC 501, the PEGC-A 502, the PEGC-B 503, the PIN server 505 and the PEGC 700, using the network interface 903 and the communication network 909.In an embodiment, when the computer system 900 corresponds to the PIN server 505, the computer system 900 may be in communication with at least one of: the PEMC 501, the PEGC-A 502, the PEGC-B 503, the one or more PINE's 504and the PEGC 700, using the network interface 903 and the communication network 909.In an embodiment, when the computer system 900 corresponds to the PEGC 700, the computer system 900 may be in communication with at least one of: the PEMC 501, the PEGC-A 502, the PEGC-B 503, the one or more PINE's 504 and the PIN server 505, using the network interface 903 and the communication network 909.The communication network 909 may be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network 909 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), etc., to communicate with each other.Further, the communication network 909 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc. In some embodiments, the processor 902 may be disposed in communication with a memory 905 (e.g., Random Access Memory (RAM), ROM, etc. not shown in Fig. 9) via a storage interface 904. The storage interface 904 may connect to memory 905 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fibre channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The memory 905 may store a collection of program or database components, including, without limitation, a user interface 906, an operating system 907, a web browser 908 etc. In some embodiments, the computer system　900 may store user / application data, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.Operating system　907　may facilitate resource management and operation of computer system　900. Examples of operating systems include, without limitation, APPLE®MACINTOSH®OS X®, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION®(BSD), FREEBSD®, NETBSD®, OPENBSD, etc.), LINUX®DISTRIBUTIONS (E.G., RED HAT®, UBUNTU®, KUBUNTU®, etc.), IBM®OS / 2®, MICROSOFT®WINDOWS®(XP®, VISTA® / 7 / 8, 10 etc.), APPLE®IOS®, GOOGLETMANDROIDTM, BLACKBERRY®OS, or the like. User interface　906　may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to computer system　900, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, Apple®Macintosh®operating systems' Aqua®, IBM®OS / 2®, Microsoft®Windows®(e.g., Aero, Metro, etc.), web interface libraries (e.g., ActiveX®, Java®,　Javascript®, AJAX, HTML, Adobe®Flash®, etc.), or the like.　The computer system　900　may implement web browser　908　stored program components. Web browser　908　may be a hypertext viewing application, such as MICROSOFT®INTERNET EXPLORER®, GOOGLETMCHROMETM, MOZILLA®FIREFOX®, APPLE®SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 908 may utilize facilities such as AJAX, DHTML, ADOBE®FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. The computer system 900　may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ACTIVEX®, ANSI®C++ / C#, MICROSOFT®, NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT®exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 900 may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE®MAIL, MICROSOFT®ENTOURAGE®, MICROSOFT®OUTLOOK®, MOZILLA®THUNDERBIRD®, etc.Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD), Read-Only Memory (ROMs), Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.Some of the clauses are mentioned below.[1]: A method for handling triggers based on Vertical Application Layer (VAL) service area ID, comprising: receiving, by a location management server from a VAL server, a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE, wherein the location reporting trigger includes a triggering criteria based on a VAL service area ID; converting, by the location management server, the VAL service area ID into its geographical location or area based on a look up table, wherein the look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas; and sending, by the location management server to the location management client, a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.[2]: The method as described in [1], further comprising: receiving, by the location management server from the location management client, a reply with location reporting configuration update response with an update result.[3]: The method as described in [1], further comprising: updating, by the location management server, location reporting configuration based on one of: request from a VAL server, request from a communication network entity or local configuration update; sending, by the location management server to the location management client, location reporting configuration update request based on the updated location reporting configuration; and receiving, by the location management server from the location management client, a reply with the updated location reporting configuration response with an update result.[4]: A method for handling triggers based on Vertical Application Layer (VAL) service area ID, comprising: receiving, by a location management client installed in a VAL User Equipment (UE) from a location management server, location reporting configuration update request comprising a geographical area based trigger corresponding to a VAL service area ID based trigger; sending, by the location management client to the location management server, a reply with location reporting configuration update response with an update result; and storing, by the location management client, location reporting configuration.[5]: The method as described in [4], further comprising: receiving, by the location management client from the location management server, location reporting configuration update request based on an updated location reporting configuration; sending, by the location management client to the location management server, a reply with the updated location reporting configuration response with an update result; and updating, by the location management client, location reporting configuration.[6]: A location management server for handling triggers based on Vertical Application Layer (VAL) service area ID, comprising: a processor; and a memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to: receive, from a VAL server, a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE, wherein the location reporting trigger includes a triggering criteria based on a VAL service area ID; convert the VAL service area ID into its geographical location or area based on a look up table, wherein the look up table comprises a mapping between a plurality of VAL service area ID's and their corresponding geographical locations or areas; and send, to the location management client, a location reporting configuration update request comprising a geographical area based trigger corresponding to the VAL service area ID.[7]: The location management server as described in [6], further configured to: receive, from the location management client, a reply with location reporting configuration update response with an update result.[8]: The location management server as described in [6], further configured to: update location reporting configuration based on one of: request from a VAL server, request from a communication network entity or local configuration update; send, to the location management client, location reporting configuration update request based on the updated location reporting configuration; and receive, from the location management client, a reply with the updated location reporting configuration response with an update result.[9]: A location management client installed in a Vertical Application Layer (VAL) User Equipment (UE) for handling triggers based on VAL service area ID, comprising of: a processor; and a memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to: receive, from a location management server, location reporting configuration update request comprising a geographical area based trigger corresponding to a VAL service area ID; send, to the location management server, a reply with location reporting configuration update response with an update result; and store location reporting configuration.

[0010] : The location management client as described in [9], further configured to: receive, from the location management server, location reporting configuration update request based on an updated location reporting configuration; send, to the location management server, a reply with the updated location reporting configuration response with an update result; and update location reporting configuration.

[0011] : A method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN, comprising:receiving, by a PIN Element with Management Capability (PEMC), a message from one or more PEGC's, indicating its connection with the PIN;determining, by the PEMC, an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's;updating, by the PEMC, a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsending, by the PEMC to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0012] : The method as described in

[0011] , wherein the connection with the PIN corresponds to one of: the PEGC leaving the PIN, or the PEGC joining the PIN.

[0013] : The method as described in

[0011] , wherein updating the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's comprises of:assigning each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0014] : The method as described in

[0011] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.

[0015] : A Personal IOT Network (PIN) Element with Management Capability (PEMC) of a PIN for notifying PIN Elements (PINEs) about an update in PIN Element with Gateway Capability (PEGC) availability, comprising of:a processor; anda memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:receive a message from one or more PEGC's, indicating its connection with the PIN;determine an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's;update a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsend, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0016] : The PEMC as described in

[0015] , wherein the connection with the PIN corresponds to one of: the PEGC leaving the PIN, or the PEGC joining the PIN.

[0017] : The PEMC as described in

[0015] , wherein the processor configured to update the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's, is configured to:assign each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0018] : The PEMC as described in

[0015] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.

[0019] : A method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN, comprising:sending, by a PEGC to a PIN Element with Management Capability (PEMC) of a PIN, a message indicating its connection with the PIN;receiving, by the PEGC from the PEMC, an updated dynamic PIN profile,wherein the PEMC determines an availability of each of the one more PEGC's of the PIN based on the message received from the PEGC and updates a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsending, by the PEGC to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0020] : The method as described in

[0019] , wherein the connection with the PIN corresponds to one of: the PEGC leaving the PIN, or the PEGC joining the PIN.

[0021] : The method as described in

[0019] , wherein updating the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's comprises of:assigning each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0022] : The method as described in

[0019] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.

[0023] : A Personal IOT Network (PIN) Element with Gateway Capability (PEGC) for notifying PIN Elements (PINEs) about an update in PEGC availability, comprising of:a processor; anda memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:send, to a PIN Element with Management Capability (PEMC) of a PIN, a message from one or more PEGC's, indicating its connection with the PIN;receive, from the PEMC, an updated dynamic PIN profile,wherein the PEMC determines an availability of each of the one more PEGC's of the PIN based on the message received from the PEGC and updates a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsend, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0024] : The PEGC as described in

[0023] , wherein the connection with the PIN corresponds to one of: the PEGC leaving the PIN, or the PEGC joining the PIN.

[0025] : The PEGC as described in

[0023] , wherein updating the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's comprises of:assigning each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0026] : The PEGC as described in

[0023] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.

[0027] : A method for dynamically notifying Personal IOT Network (PIN) Element with Gateway Capability (PEGC) availability in a PIN, comprising:receiving, by a PIN server, a message from one or more PEGC's, indicating its connection with the PIN;determining, by the PIN server, an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's;updating, by the PIN server, a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsending, by the PIN server to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0028] : The method as described in

[0027] , wherein updating the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's comprises of:assigning each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0030] : The method as described in

[0027] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.

[0031] : A Personal IOT Network (PIN) server of a PIN for notifying PIN Elements (PINEs) about an update in PIN Element with Gateway Capability (PEGC) availability, comprising of:a processor; anda memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:receive a message from one or more PEGC's, indicating its connection with the PIN;determine an availability of each of the one more PEGC's based on the message received from respective one or more PEGC's;update a dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's; andsend, to one or more PINE's of the PIN, at least one of: a notification indicating the updated dynamic PIN profile, wherein the notification indicates change in PEGC availability and a notification indicating the change in the PEGC availability.

[0032] : The PIN server as described in

[0031] , wherein the connection with the PIN corresponds to one of: the PEGC leaving the PIN, or the PEGC joining the PIN.

[0033] : The PIN server as described in

[0031] , wherein the processor configured to update the dynamic PIN profile of the PIN based on the availability of each of the one more PEGC's, is configured to:assign each of the one or more PEGC's as at least one of: a default PEGC to a first set of the one or more PINE's and as a backup PEGC to a second set of the one or more PINE's.

[0034] : The PIN server as described in

[0031] , wherein the dynamic PIN profile comprises of a mapping of one or more PINE's of the PIN and their corresponding default PEGC's and their corresponding backup PEGC'S.With respect to the use of substantially any plural and singular terms herein, those having skill in the art may translate from the plural to the singular and from the singular to the plural as is appropriate to the context or application. The various singular or plural permutations may be expressly set forth herein for sake of clarity.One or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which a software (program) readable by an information processing apparatus may be stored. The information processing apparatus includes a processor and a memory, and the processor executes a process of the software. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include RAM, ROM, volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.The described operations may be implemented as a method, a system, or an article of manufacture using at least one of standard programming and engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a "non-transitory computer readable medium", where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., Programmable ROM (PROMs), Electrically Erasable PROM (EEPROMs), ROMs, RAMs, Dynamic RAM (DRAMs), Static RAM (SRAMs), Flash Memory, firmware, programmable logic, etc.), etc. Further, non-transitory computer-readable media include all computer-readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), ASIC, etc.).Some of the advantages of the present disclosure are listed below.In existing systems, there is no mechanism for location management server to handle the VAL service area ID based triggering criteria for location reporting from VAL UE. The present disclosure gives an advantage by disclosing a method for Location management servers to handle VAL service area ID based triggering criteria by reporting the location of VAL UE.Also, in existing systems there are no mechanisms for PIN elements which are currently part of the PIN to be notified about the backup PEGC availability when the new PEGC becomes available and there are also no mechanism for PIN elements which are currently part of the PIN are notified about the unavailability of the PEGC which is currently assigned as back up PEGC for the PIN elements and if there is a new PEGC available to serve as back up PEGC. The present gives an advantage by disclosing a method for PIN elements that are already part of the PIN to know the changes in the default and backup PEGC in cases where a new PEGC takes over the PEGC role or an existing PEGC relinquishes its PEGC role.The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise.The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.When a single device or article is described herein, it will be readily apparent that more than one device or article (whether or not they cooperate) may be used in place of a single device or article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device or article may be used in place of the more than one device, or article, or a different number of devices or articles may be used instead of the shown number of devices or programs. At least one of the functionalities and the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality or features. Thus, other embodiments of the invention need not include the device itself.The illustrated operations of FIGS. 3a and 3b show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.

Claims

1.A method performed by a location management server for handling triggers based on Vertical Application Layer (VAL) service area ID, the method comprising:receiving, from a VAL server, a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE, wherein the location reporting trigger contains a triggering criteria based on a VAL service area ID;converting the location reporting trigger containing criteria based on the VAL service area ID into geographical area based trigger; andtransmitting, to the location management client, a location reporting configuration update request comprising the geographical area based trigger converted from the location reporting trigger.2.The method of claim 1, further comprising:receiving, from the location management client, a reply with location reporting configuration update response with an update result.3.The method of claim 1, further comprising:updating location reporting configuration based on at least one of: request from a VAL server, request from a communication network entity or local configuration update;transmitting, to the location management client, location reporting configuration update request based on the updated location reporting configuration; andreceiving, from the location management client, a reply with the updated location reporting configuration response with an update result.4.The method of claim 1,wherein a conversion from the location reporting trigger to the geographical area based trigger is performed based on a lookup table comprising a mapping between a plurality of VAL service area IDs and corresponding geographical areas.5.A method performed by a location management client installed in a vertical application layer (VAL) user equipment (UE) for handling triggers based on VAL service area ID, the method comprising:receiving, from a location management server, location reporting configuration update request comprising a geographical area based trigger converted from a VAL service area ID based trigger;transmitting, to the location management server, a reply with location reporting configuration update response with an update result; andstoring location reporting configuration.6.The method of claim 5, further comprising:receiving, from the location management server, location reporting configuration update request based on an updated location reporting configuration; andtransmitting, to the location management server, a reply with the updated location reporting configuration response with an update result; andupdating location reporting configuration.7.A location management server for handling triggers based on Vertical Application Layer (VAL) service area ID, the location management server comprising of:a transceiver; anda processor configured to:receive, from a VAL server, a location reporting trigger to activate a location reporting procedure for obtaining location information of a VAL User Equipment (UE) from a location management client installed in the VAL UE, wherein the location reporting trigger contains a triggering criteria based on a VAL service area ID,convert the location reporting trigger contacting criteria based on the VAL service area ID into geographical area based trigger, andtransmit, to the location management client, a location reporting configuration update request comprising the geographical area based trigger converted from the location reporting trigger.8.The location management server of claim 7,wherein the processor is further configured to:receive, from the location management client, a reply with location reporting configuration update response with an update result.9.The location management server of claim 7,wherein the processor is further configured to:update location reporting configuration based on at least one of: request from a VAL server, request from a communication network entity or local configuration update;transmit, to the location management client, location reporting configuration update request based on the updated location reporting configuration; andreceive, from the location management client, a reply with the updated location reporting configuration response with an update result.10.The location management server of claim 7,wherein a conversion from the location reporting trigger to the geographical area based trigger is performed based on a lookup table comprising a mapping between a plurality of VAL service area IDs and corresponding geographical areas.11.A location management client installed in a Vertical Application Layer (VAL) User Equipment (UE) for handling triggers based on VAL service area ID, the location management client comprising of:a transceiver; anda processor configured to:receive, from a location management server, location reporting configuration update request comprising a geographical area based trigger corresponding to a VAL service area ID,transmit, to the location management server, a reply with location reporting configuration update response with an update result, andstore location reporting configuration.12.The location management client of claim 11,wherein the processor is further configured to:receive, from the location management server, location reporting configuration update request based on an updated location reporting configuration, andsend, to the location management server, a reply with the updated location reporting configuration response with an update result, andupdate location reporting configuration.

Images