Method and apparatus for providing a generic framework for managing custom subscriptions over SIP

Abstract

The present disclosure relates to a communication method and system for fusing a fifth generation (5G) communication system with Internet of Things (IoT) technology to support higher data rates beyond the fourth generation (4G) system. The present disclosure can be applied to intelligent services based on the 5G communication technology and IoT related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, retail, security, and safety related services. Thus, an embodiment of the present disclosure discloses a method for providing a generic framework for managing custom subscriptions via SIP. The method includes sending at least one request including a plurality of parameters to a server SIP node for any type of data via SIP, regardless of whether an event package is available.

Description

[Technical field]

[0001] The present disclosure relates to the session initiation protocol (SIP), and in particular to a method and a SIP node for providing a generic framework for managing custom subscriptions over SIP. [Background technology]

[0002] Since the commercialization of the 4G communication system, efforts have been made to develop improved 5G or pre-5G communication systems to meet the growing demand for wireless data traffic. Therefore, 5G or pre-5G communication systems are also called "Beyond 4G Networks" or "Post LTE Systems". It is considered that the 5G communication system will be embodied in a higher frequency (mmWave) band, for example, the 60 GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of wireless waveforms and extend the transmission distance, beamforming, massive multi-input multi-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam forming, and large scale antenna technologies are being discussed in the 5G communication system. In addition, in the 5G communication system, development is underway to improve the system network based on advanced small cells, cloud Radio Access Networks (cloud RAN), ultra-dense networks, device to device (D2D) communications, wireless backhauls, moving networks, cooperative communications, CoMP (Coordinated Multi-Points), receiver interference cancellation, etc.In the 5G system, hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access techniques have been developed.

[0003] The Internet is currently evolving from a human-centered connected network where humans generate and consume information to the Internet of Things (IoT) where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, combining IoT technology with big data processing technology through connection to cloud servers. To realize the IoT, technological elements such as "sensing technology," "wired and wireless communication and network infrastructure," "service interface technology," and "security technology" are required, so sensor networks, M2M (Machine to Machine) communication, MTC (Machine Type Communication), etc. have been researched recently. Such an IoT environment can provide intelligent Internet technology services that create new value in human life by collecting and analyzing data generated between connected things. Through the fusion and combination of existing information technology (IT) and various industrial applications, the IoT may be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communication (MTC), and M2M communication can be implemented by beamforming, MIMO, and array antennas. The application of cloud Radio Access Networks (RANs) as the aforementioned big data processing technology is also considered as an example of the fusion of 5G technology and IoT technology.

[0005] In the existing SIP-based subscribe mechanism, a user requests an event package in a subscribe request to subscribe to event data (e.g., conference data, location data, sensor data, etc.) from a server. According to RFC3265, a user (subscriber) can have exactly one event header (event package) in a subscribe request, which indicates the event data or event data class to which the user wants to subscribe. FIG. 1 is a sequence diagram showing the existing SIP-based subscribe mechanism according to the prior art disclosed in this specification. In steps 1-2, a client SIP node 10 sends a SIP SUBSCRIBE request to subscribe to specific event data from a server SIP node 20. The subscribe request includes an event package (event report request). In steps 3-5, a specific event occurs in the server SIP node 20, and the server SIP node 20 sends a notification SIP NOTIFY message (event report) associated with the subscribed specific event data to the client SIP node 10.

[0006] Additionally, there are limited useful event packages according to the Internet Assigned Numbers Authority (IANA), and there are some servers in the world that have other types of useful data (e.g., location data, sensor data, etc.) that do not have an IANA-registered event package associated with them. For example, if any authorized user wants to subscribe to another user's device location, there is no useful event package. Similarly, there is no useful event package for any authorized user to subscribe to temperature sensor data. Also, defining and standardizing new event packages requires a significant amount of time.

[0007] In another example, the service enabler architecture layer (SEAL) provides services that can be used by multiple vertical applications. One such service provided by SEAL is a location management service that allows a Vertical Application Layer (VAL) server to manage location information of VAL users. The location management service allows a VAL server to subscribe to location information of VAL users. However, there is no useful standard SIP event package that can be used with a SIP-based subscription mechanism.

[0008] In general, a user (e.g., client SIP node 10, VAL server, user equipment (UE)) can request an event package in a subscribe request to subscribe to any event data from a server (e.g., server SIP node 20, SEAL server). Summary of the Invention [Problem to be solved by the invention]

[0009] Regardless of whether an event package is useful, there is no mechanism by which a user can subscribe to any type of data via SIP. It would therefore be desirable to address the aforementioned shortcomings or at least provide a useful alternative. [Means for solving the problem]

[0010] The primary objective of the embodiments herein is to provide a general framework for managing custom subscriptions by sending at least one request including multiple parameters to a server for any type of data over SIP, regardless of whether an event package is available. Custom subscriptions are managed using the multiple parameters by creating a custom subscription, modifying a custom subscription, deleting a custom subscription, notifying a custom subscription, and terminating a custom subscription.

[0011] Another objective of an embodiment of the present invention is to provide a subscription to a location management service associated with a SEAL location management server (SLM-S) via SIP, regardless of whether an event package is available. The SLM-S allows the VAL server to manage the location information of a VAL user using multiple parameters.

[0012] Accordingly, embodiments herein disclose a method for providing a generic framework for managing custom subscriptions over SIP. The method includes an operation of a server SIP node receiving a SIP message from a client SIP node to create a custom subscription over SIP for custom information, the SIP message including a custom subscription creation request message, the custom subscription creation request message including a plurality of parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node generating a unique subscription identifier and starting a subscription expiration timer in response to receiving the SIP message to create the custom subscription over SIP for the customization information. The method further includes an operation of the server SIP node creating a subscription for the custom information based on a subscription context from the received SIP message. The method further includes an operation of the server SIP node assigning the unique subscription identifier to the created custom subscription for the custom information based on a subscription context from the received SIP message. The method further includes an act of the server SIP node sending a SIP message to the client SIP node, the SIP message including a custom subscription creation response message.

[0013] In one embodiment, the parameters include an expiration date, a time interval, and other subscription-related parameters.

[0014] In one embodiment, the custom subscription creation response message includes an expiration time, a unique subscription identifier, and other subscription-related parameters.

[0015] In one embodiment, the method further includes an operation of the client SIP node configuring an expiration value, the expiration value being the time until which the client SIP node wishes to receive the current status and subsequent notifications of a custom subscription. Additionally, the method includes an operation of the client SIP node configuring a time interval value, the time interval being the period between two successive notifications indicated by the client SIP node. Additionally, the method includes an operation of the client SIP node configuring other required parameters depending on the type of subscription data.

[0016] In one embodiment, the method further includes an operation of the server SIP node reconfiguring an expiration time, where if the expiration time value present in the received SIP message is not accepted by the server SIP node, the server SIP node changes the expiration time value to a value different from that present in the received SIP message. Additionally, the method includes an operation of the server SIP node starting a subscription expiration timer and a notification interval timer based on the server SIP node's configuration.

[0017] In one embodiment, the method further includes an operation of the server SIP node receiving a SIP message from the client SIP node to modify the created custom subscription via SIP for the custom information, the SIP message including a custom subscription modification request message, the custom subscription modification request message including a unique subscription identifier and updated parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node configuring parameters and restarting an expiration timer based on the updated parameters. The method further includes an operation of the server SIP node modifying the created custom subscription via SIP for the custom information based on the SIP message received from the client SIP node, and sending a SIP message to the client SIP node, the SIP message including a custom subscription modification response message.

[0018] In one embodiment, the custom subscription modification response message includes an updated expiration date, a unique subscription identifier, and other subscription-related parameters.

[0019] In one embodiment, the method further includes an operation of the server SIP node receiving a SIP message from the client SIP node to delete the created custom subscription via SIP for the custom information, the SIP message including a custom subscription delete request message, the custom subscription delete request message including a unique subscription identifier and an expiration time, the expiration time value being zero. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node deleting the stored custom subscription via SIP for the custom information and a plurality of parameters associated with the SIP message received from the client SIP node. The method further includes an operation of the server SIP node 200 sending a SIP message to the client SIP node, the SIP message including a custom subscription delete response message, the expiration time and the time interval expired, the custom subscription delete response message including a unique subscription identifier.

[0020] In one embodiment, the method further comprises an operation of the server SIP node sending a SIP message to the client SIP node to notify the information, the SIP message including a custom subscription notification message, the custom subscription notification message including a unique subscription identifier and the data to be notified.

[0021] In one embodiment, when the client SIP node receives a SIP message from the server SIP node, the client SIP node stores the data and shares the data with at least one user.

[0022] In one embodiment, the method further includes an operation of the server SIP node sending a SIP message to the client SIP node to terminate the created custom subscription via SIP for the custom information, the SIP message including a custom subscription termination message, the custom subscription termination message including a unique subscription identifier.

[0023] In one embodiment, when the client SIP node receives a SIP message from the server SIP node, the client SIP node deletes the created custom subscription and ends the subscription expiration timer and the notification interval timer.

[0024] Accordingly, embodiments herein disclose a method for providing a generic framework for managing custom subscriptions over SIP. The method includes an operation of a server SIP node receiving a SIP message from a client SIP node to create a subscription over SIP for location information of a plurality of users, the SIP message including a location event subscribe creation request message, the location event subscribe creation request message including a plurality of parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node storing the received plurality of parameters to create a subscription context. The method further includes an operation of the server SIP node generating a unique subscription identifier and starting a subscription expiration timer in response to receiving the SIP message to create the subscription over SIP for location information. The method further includes an operation of the server SIP node creating a custom subscription for location information of a plurality of users based on the subscription context by sending a SIP message to the client SIP node, the SIP message including a location event subscribe creation response message.

[0025] In one embodiment, the plurality of parameters includes an expiration date, a time interval, a total number of users, a list of user IDs, and user IDs associated with the client SIP node.

[0026] In one embodiment, the location event subscribe create response message includes an expiration time and a unique subscription identifier.

[0027] In one embodiment, the method further includes an operation of the client SIP node configuring an expiration value, the expiration being a time until which the client SIP node desires to receive a current status of the subscription and subsequent notifications. The method further includes an operation of the client SIP node configuring a time interval value, the time interval being a period between two successive notifications indicated by the client SIP node. The method further includes an operation of the client SIP node configuring a value for a total number of users who have requested the location information. The method further includes an operation of the client SIP node adding a user ID for each user and an integer that uniquely represents the user in the list of user IDs.

[0028] In one embodiment, the method further includes an operation of the server SIP node reconfiguring an expiration time, where an expiration time value present in the received SIP message is not accepted by the server SIP node, and the server SIP node changes the expiration time value to a value different from the value present in the received SIP message. Further, the method includes an operation of the server SIP node reconfiguring a total number of users for which a client SIP node has requested location information. Further, the method includes an operation of the server SIP node adding a user ID for each user from the reconfigured total number of users. Further, the method includes an operation of the server SIP node starting a subscription expiration timer and a notification interval timer based on the server SIP node's configuration.

[0029] In one embodiment, the method further includes an operation of the server SIP node receiving a SIP message from the client SIP node to modify the created subscription via SIP for location information of a plurality of users, the SIP message including a location event subscribe modify request message, the location event subscribe modify request message including a unique subscription identifier and updated parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node configuring parameters based on the updated parameters and restarting the expiration timer. The method further includes an operation of the server SIP node modifying the created subscription via SIP for location information of a plurality of users based on the SIP message received from the client SIP node and sending a SIP message to the client SIP node, the SIP message including a location event subscribe modify response message.

[0030] In one embodiment, the location event subscribe modify response message includes an updated expiration date and a unique subscription identifier.

[0031] In one embodiment, the method further includes an operation of the server SIP node receiving a SIP message from the client SIP node to delete the created subscription via SIP for location information of a plurality of users, the SIP message including a location event subscribe delete request message, the location event subscribe delete request message including a unique subscription identifier and an expiration time, the expiration time value being 0 (zero). The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node deleting the stored subscription via SIP for location information of a plurality of users and a plurality of parameters associated with the SIP message received from the client SIP node. The method further includes an operation of the server SIP node sending a SIP message to the client SIP node, the SIP message including a location event subscribe delete response message, expiring the expiration time and the time interval.

[0032] In one embodiment, the method further comprises an operation of the server SIP node sending a SIP message to the client SIP node to notify a plurality of users of the location information, the SIP message comprising a location event notification message, the location event notification message comprising a unique subscription identifier and the location data to be notified.

[0033] In one embodiment, when the client SIP node receives a SIP message from the server SIP node, the client SIP node stores location data and shares the location data with at least one user.

[0034] In one embodiment, the method further includes an operation of the server SIP node sending a SIP message to the client SIP node to terminate the created subscription via SIP for location information of a plurality of users, the SIP message including a location event subscribe end message, the location event subscribe end message including a unique subscription identifier.

[0035] In one embodiment, upon receiving a SIP message from the server SIP node, the client SIP node deletes the created subscription and ends the subscription expiration timer and the notification interval timer.

[0036] All the above embodiments are applicable for creating / modifying / deleting / notifying / terminating custom subscriptions via SIP for custom information (eg, sensor data, satellite data, location data, etc.).

[0037] Accordingly, embodiments herein provide a server SIP node for providing a generic framework for managing custom subscriptions over SIP. The server SIP node includes a subscription controller coupled to a processor and a memory. The subscription controller is configured to receive a SIP message from the client SIP node and create a custom subscription over SIP for the custom information. The subscription controller is further configured to send a response message to the client SIP node in response to receiving the SIP message. The subscription controller is further configured to store the received parameters to generate a subscription context. The subscription controller is further configured to generate a unique subscription identifier in response to receiving the SIP message to create a subscription over SIP for the location information and start an expiration timer for the subscription. The subscription controller is further configured to create a custom subscription over SIP for the custom information based on a subscription context from the received SIP message and assign a unique subscription identifier to the created custom subscription, the SIP message including a location event subscribe create response message.

[0038] Accordingly, embodiments herein provide a client SIP node for providing a generic framework for managing custom subscriptions over SIP. The client SIP node includes a subscription controller coupled to a processor and a memory. The subscription controller is configured to send a SIP message to the server SIP node. The subscription controller is configured to set an expiration value, the expiration being a time until which the client SIP node desires to receive a current status of the subscription and subsequent notifications. The subscription controller is configured to set a time interval value, the time interval being a period between two successive notifications indicated by the client SIP node. The subscription controller is configured for the client SIP node to set a value for a total number of users for which the location information is required. The subscription controller is configured to add a user ID for each user and an integer that uniquely represents the user among a list of user IDs.

[0039] According to one aspect of the disclosure, one embodiment of the present invention provides a method for managing a custom subscription via SIP by a server Session Initiation Protocol (SIP) node, the method including operations of receiving a first SIP message from a client SIP node requesting creation of a custom subscription via SIP for custom information, where the first SIP message includes at least one parameter of the custom subscription; sending a response message to the client SIP node in response to receiving the first SIP message; storing the received at least one parameter; generating a unique subscription identifier for identifying the custom subscription; and sending a second SIP message to the client SIP node including the unique subscription identifier.

[0040] In one embodiment, the at least one parameter includes at least one of an expiration date, a time interval, and at least one other subscription-related parameter, wherein the time interval is a period between two successive notifications of a custom subscription.

[0041] In one embodiment, the second SIP message further includes at least one of an accepted expiration time and at least one other subscription-related parameter.

[0042] In one embodiment, the method further includes an operation of reconfiguring the custom subscription expiration time if an expiration time value included in the first SIP message is not accepted by the server SIP node; and an operation of starting the subscription expiration timer and setting an expiration time of the subscription expiration time to the reconfigured value.

[0043] In one embodiment, the method further includes the operations of receiving a third SIP message from the client SIP node requesting deletion of the custom subscription via SIP to the custom information, where the third SIP message includes the unique subscription identifier and an expiration time, the expiration time value being 0 (zero); sending a response message to the client SIP node in response to receiving the SIP message; deleting the stored at least one parameter associated with the custom subscription; and sending a fourth SIP message to the client SIP node and ending a subscription expiration timer and a notification interval timer, where the fourth SIP message includes the unique subscription identifier.

[0044] In one embodiment, the method further comprises an operation of sending a fifth SIP message to the client SIP node to notify the custom information, the SIP message including a unique subscription identifier and data to be notified.

[0045] In one embodiment, the custom information is location information of a plurality of users, the custom subscription is a subscription to location information of the plurality of users, and the at least one parameter includes at least one of an expiration date, a time interval, a total number of users, a list of user IDs including a unique user number for each user, and a user ID associated with the client SIP node.

[0046] In one embodiment, the custom information is location information of a plurality of users, the custom subscription is a subscription to location information of the plurality of users, and the second SIP message includes at least one of an expiration date, a total number of users, and a list of user IDs including a unique user number for each user.

[0047] According to one aspect of the disclosure, an embodiment of the present invention provides a server SIP node for managing custom subscriptions over a Session Initiation Protocol (SIP), the server SIP node including: a memory; a processor; and a subscription controller operatively connected to the memory and the processor and configured to: receive, from a client SIP node, a first SIP message requesting creation of a custom subscription over SIP for custom information, where the first SIP message includes at least one parameter of the custom subscription; in response to receiving the first SIP message, send a response message to the client SIP node; store the received at least one parameter; generate a unique subscription identifier for identifying the custom subscription; and send a second SIP message to the client SIP node including the unique subscription identifier.

[0048] In one embodiment, the at least one parameter includes at least one of an expiration date of the custom subscription, a time interval, and at least one other subscription-related parameter, wherein the time interval is a period between two successive notifications of the custom subscription.

[0049] In one embodiment, the second SIP message further includes at least one of an accepted expiration time and at least one other subscription-related parameter.

[0050] In one embodiment, the subscription controller is further configured to: reconfigure an expiration time of the custom subscription if an expiration time value included in the first SIP message is not accepted by the server SIP node; and start the subscription expiration timer and set the expiration time of the subscription expiration timer to the reconfigured value.

[0051] In one embodiment, the subscription controller is further configured to: receive from the client SIP node, via SIP for the custom information, a third SIP message requesting deletion of the custom subscription, the third SIP message including a unique subscription identifier and an expiration time, the expiration time value being 0 (zero); in response to receiving the SIP message, send a response message to the client SIP node; delete the stored at least one parameter associated with the custom subscription; and send a fourth SIP message to the client SIP node, the SIP message ending a subscription expiration timer and a notification interval timer, the fourth SIP message including the unique subscription identifier.

[0052] In one embodiment, the subscription controller is further configured to send a fifth SIP message to the client SIP node to notify the custom information, the fifth SIP message including a unique subscription identifier and data to be notified.

[0053] In one embodiment, the client SIP node stores the data and shares the data with at least one user when the client SIP node receives the fifth SIP message from the server SIP node.

[0054] In one embodiment, the subscription controller is further configured to send a SIP message to the client SIP node to terminate the created custom subscription via SIP for the custom information, the SIP message including a custom subscription termination message including a unique subscription identifier.

[0055] According to one aspect of the present disclosure, an embodiment of the present invention provides a client SIP node 100 for providing a framework for managing custom subscriptions via Session Initiation Protocol (SIP), the client SIP node 100 including: a memory 110; a processor 120; and a subscription controller 140 operatively connected to the memory 110 and the processor 120, configured to: send SIP messages to a server SIP node to create, modify, or delete a subscription via SIP for custom information, the SIP messages including one of a custom subscription creation request message, a custom subscription modification request message, and a custom subscription deletion request message, each message including a number of parameters; configure an expiration value, the expiration being a time until which the client SIP node wishes to receive a current status of the subscription and subsequent notifications; configure a time interval value, the time interval being a period between two successive notifications; and configure other required parameters depending on the type of the subscription data.

[0056] In one embodiment, the parameters include an expiration date, a time interval, and other subscription-related parameters.

[0057] In one embodiment, the subscription controller is further configured to receive a SIP message from the server SIP node 200 to perform one of notifying and terminating a custom subscription to the custom information, the SIP message including one of a custom subscription notification message and a custom subscription termination message.

[0058] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following description, while indicating preferred embodiments and numerous specific details thereof, is given by way of illustration and not by way of limitation. Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications.

[0059] Before setting forth the detailed description below, it may be desirable to set forth definitions of certain words and phrases used throughout this patent document. The terms "include" and "comprise," along with their derivatives, mean an open-ended inclusion. The term "or" is an inclusive term meaning and / or. The phrases "associated with", "associated therewith" and derivatives thereof mean include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, and the like. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a device may be implemented in hardware, firmware, or software, or a combination of at least two of these. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0060] Moreover, various functions described below may be implemented or supported by one or more computer programs, each of which is comprised of computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sequences of instructions, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, such as source code, object code, executable code, etc. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media include media that can store data permanently and media that can store data and later be overwritten, such as rewritable optical disks or erasable memory devices.

[0061] Definitions of other specific words and phrases are provided throughout this patent document, and those of skill in the art should understand that in many cases, if not most cases, such definitions apply to prior and future uses of the words and phrases so defined. Effect of the Invention

[0062] The present disclosure provides a generic framework for managing custom subscriptions by sending at least one request containing multiple parameters via SIP to a server for any type of data, regardless of whether an event package is available.

[0063] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent similar parts and in which: [Brief description of the drawings]

[0064] [Figure 1] FIG. 1 is a sequence diagram illustrating an existing SIP-based subscription mechanism. [Figure 2A] 1 illustrates a block diagram of a client SIP node for managing custom subscriptions over SIP according to one embodiment as disclosed herein. [Figure 2B] 1 illustrates a block diagram of a server SIP node entity for managing custom subscriptions over SIP according to one embodiment as disclosed herein. [Figure 2CA] 1 illustrates various message formats for multiple parameters managing custom subscriptions over SIP according to one embodiment as disclosed herein. [Figure 2CB] 1 illustrates various message formats for multiple parameters managing custom subscriptions over SIP according to one embodiment as disclosed herein. [Figure 3A] FIG. 2 is a sequence diagram illustrating various operations for creating a custom subscription over SIP according to one embodiment as disclosed herein. [Figure 3B] FIG. 2 is a sequence diagram illustrating various operations for creating a custom subscription over SIP for location information according to one embodiment as disclosed herein. [Figure 4A]FIG. 2 is a sequence diagram illustrating various operations for modifying a custom subscription over SIP according to one embodiment as disclosed herein. [Figure 4B] FIG. 2 is a sequence diagram illustrating various operations for modifying a custom subscription over SIP for location information according to one embodiment as disclosed herein. [Figure 5A] FIG. 2 is a sequence diagram illustrating various operations for deleting a custom subscription over SIP according to one embodiment as disclosed herein. [Figure 5B] FIG. 2 is a sequence diagram illustrating various operations for deleting a custom subscription over SIP for location information according to one embodiment as disclosed herein. [Figure 6A] FIG. 2 is a sequence diagram illustrating various operations for sending a notification of a custom subscription over SIP according to one embodiment as disclosed herein. [Figure 6B] FIG. 2 is a sequence diagram illustrating various operations for sending a notification of a custom subscription over SIP for location information according to one embodiment as disclosed herein. [Figure 7A] FIG. 2 is a sequence diagram illustrating various operations for terminating a custom subscription over SIP according to one embodiment as disclosed herein. [Figure 7B] FIG. 2 is a sequence diagram illustrating various operations for terminating a custom subscription over SIP for location information according to one embodiment as disclosed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0065] 1-7B described below, and the various embodiments used to illustrate the principles of the present disclosure in this patent document, are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0066] The embodiments of the present specification and various features and advantageous details thereof will be more fully described with reference to the non-limiting embodiments illustrated in the accompanying drawings and embodied in the following description. Descriptions of known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments of the present specification. In addition, the various embodiments described herein are not necessarily mutually exclusive, since some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended to enable an understanding of how the embodiments of the present specification can be implemented and to enable those skilled in the art to realize the embodiments of the present specification. Therefore, the above examples should not be interpreted as limiting the scope of the embodiments of the present specification.

[0067] As is common in the art, the embodiments may be described and illustrated in terms of described functions or blocks performing functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., may be physically implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc., and may be selectively driven by firmware. The circuits may be implemented, for example, in one or more semiconductor chips, or may be implemented on a substrate support, such as a printed circuit board. The circuits constituting the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware performing some functions of the blocks and a processor performing other functions. Each block of the embodiments may be physically separated into two or more interacting separate blocks without departing from the scope of the disclosure. Similarly, the blocks of the embodiments may be combined into physically more complex blocks without departing from the scope of the disclosure.

[0068] The attached drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented in this specification are not limited by the attached drawings. Therefore, the present disclosure should be interpreted as extending to any alternatives, equivalents, and substitutes in addition to those specifically described in the attached drawings. Here, terms such as first, second, etc. may be used to describe various elements, but such elements should not be limited by these terms. These terms are usually used only to distinguish one element from another element.

[0069] Throughout this disclosure, the terms "client", "client SIP node", "VAL server (client)" and "VAL server" are used interchangeably and have the same meaning. The terms "server", "server SIP node", "SLM-S (server)" and "SLM-S" are used in combination and have the same meaning.

[0070] Accordingly, embodiments herein disclose a method for providing a generic framework for managing custom subscriptions over SIP. The method includes an operation of a server SIP node receiving a SIP message from a client SIP node to create a custom subscription over SIP for custom information, the SIP message including a custom subscription creation request message, the custom subscription creation request message including a plurality of parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node generating a unique subscription identifier and starting a subscription expiration timer in response to receiving the SIP message to create a subscription over SIP for the custom information. The method further includes an operation of the server SIP node creating a subscription for the information based on a subscription context from the received SIP message and assigning a unique subscription identifier to the created custom subscription, the SIP message including a custom subscription creation response message.

[0071] Accordingly, embodiments herein disclose a method for providing a generic framework for managing custom subscriptions over SIP. The method includes an operation of a server SIP node receiving a SIP message from a client SIP node to create a subscription over SIP for location information of a plurality of users, the SIP message including a location event subscribe creation request message, the location event subscribe creation request message including a plurality of parameters. The method further includes an operation of the server SIP node sending a response message to the client SIP node in response to receiving the SIP message. The method further includes an operation of the server SIP node storing the received plurality of parameters to generate a subscription context. The method further includes an operation of the server SIP node generating a unique subscription identifier and starting a subscription expiration timer in response to receiving the SIP message to create the subscription over SIP for location information. The method further includes an operation of the server SIP node creating custom subscriptions for location information of a plurality of users based on subscription context from the received SIP message by sending a SIP message to the client SIP node, the SIP message including a location event subscribe creation response message, and assigning a unique subscription identifier to the created custom subscription.

[0072] Accordingly, embodiments herein provide a server SIP node for providing a generic framework for managing custom subscriptions over SIP. The server SIP node includes a subscription controller coupled to a processor and a memory. The subscription controller is configured to receive a SIP message from the client SIP node and generate custom information over SIP for custom information. The subscription controller is further configured to send a response message to the client SIP node in response to receiving the SIP message. The subscription controller is further configured to store a plurality of received parameters to generate a subscription context. The subscription controller is further configured to generate a unique subscription identifier in response to receiving the SIP message to create a subscription over SIP for custom information and start a subscription expiration timer. The subscription controller is further configured to create a custom subscription over SIP for custom information based on the subscription context from the received SIP message and assign a unique subscription identifier to the created custom subscription, the SIP message including a location event subscribe create response message.

[0073] Accordingly, embodiments herein provide a client SIP node for providing a generic framework for managing custom subscriptions over SIP. The client SIP node includes a subscription controller coupled to a processor and a memory. The subscription controller is configured to send a SIP message to a server SIP node. The subscription controller is configured to set an expiration value, the expiration being a time until which the client SIP node desires to receive a current status of a subscription and subsequent notifications. The subscription controller is configured to set a time interval value, the time interval being a period between two successive notifications indicated by the client SIP node. The subscription controller is configured to set a value for a total number of users for which the client SIP node has requested custom information. The subscription controller is configured to add a user ID for each user and an integer that uniquely represents the user to the list of user IDs.

[0074] Unlike existing methods and systems, the method and SIP node provided above provides a generic framework for managing custom subscriptions by sending at least one request having multiple parameters to a server SIP node via SIP for any type of data, regardless of whether an event package is available in at least one request.

[0075] Unlike existing methods and systems, the provided method and SIP node provide a custom subscription to a location management service associated with an SLM-S via SIP whether an event package is available in at least one request received from a VAL server, and the SLM-S allows the VAL server to manage location information of a VAL user using multiple parameters.

[0076] Unlike existing methods and systems, the provided client SIP node manages custom subscriptions by sending at least one request including multiple parameters to a server SIP node for any type of data via SIP, regardless of whether an event package is available. The custom subscriptions are managed by creating a custom subscription, modifying a custom subscription, deleting a custom subscription, notifying a custom subscription, and terminating a custom subscription using the multiple parameters. Therefore, the provided client SIP node does not need an event package in a SIP message to subscribe to various services associated with the server SIP node.

[0077] Referring now to the drawings, in which like reference numerals indicate corresponding features consistently throughout the drawings, and more particularly to Figures 2A-7B, a preferred embodiment is shown.

[0078] 2A illustrates a block diagram of a client SIP node 100 for managing custom subscriptions over SIP according to one embodiment as disclosed herein. The client SIP node 100 can be, for example, but not limited to, a user equipment (UE), a VAL server.

[0079] In one embodiment, the client SIP node 100 includes a memory 110 , a processor 120 , a communicator 130 , and a subscription controller 140 .

[0080] In one embodiment, the memory 110 is configured to store configurations of a number of parameters. The parameters include an expiration date, a time interval, a total number of users, a list of user IDs, and user IDs associated with the client SIP node 100. The memory 110 stores instructions executed by the processor 120. The memory 110 may include a non-volatile storage element. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memory. Additionally, the memory 110 may be considered a non-transitory storage medium in some examples. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagating signal. However, the term "non-transitory" should not be interpreted as the memory 110 being non-removable. In certain examples, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or cache). The memory 110 may be an internal storage device, or may be an external storage device of the client SIP node 100, cloud storage, or any other type of external storage device.

[0081] The processor 120 is in communication with the memory 110, the communicator 130, and the subscription controller 140. The processor 120 is configured to execute instructions stored in the memory 110 and perform various processes. The processor may include one or more processors and may be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics-specific processor such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI)-specific processor such as a neural processing unit (NPU).

[0082] Communicator 130 is configured to communicate internally between internal hardware components and with external devices (e.g., server SIP node 200) over one or more networks (e.g., the Internet, Wi-Fi, Bluetooth, etc.). Communicator 130 includes standard-specific electronic circuitry that enables wired or wireless communication.

[0083] The subscription controller 140 may be implemented by processing circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. The circuitry may, for example, be embodied in one or more semiconductor chips, or may be implemented on a substrate support, such as a printed circuit board.

[0084] In one embodiment, the subscription controller 140 is configured to send SIP messages to the server SIP node 200 to create / modify / delete custom subscriptions (subscriptions to locations) via SIP for custom information of multiple users (e.g., location information, sensor information, etc.). Further, the subscription controller 140 is configured to receive SIP messages from the server SIP node 200 to notify / terminate the created custom subscriptions via SIP for custom information of multiple users.

[0085] The SIP message includes one of a create custom subscription request message, a modify custom subscription request message, a delete custom subscription request message, a custom subscription notify message, and a terminate custom subscription message, each of which includes a number of parameters (e.g., expiration time, time interval, total number of users, a list of user IDs with a unique user number for each user, and the user ID).

[0086] The custom subscription request message includes an expiration date, a time interval, a total number of users, a list of user IDs, and a user ID. The custom subscription modification request message includes a unique subscription identifier and a number of updated parameters. The custom subscription deletion request message includes a unique subscription identifier and an expiration date. The expiration date has a value of 0 (zero). The custom subscription notification message includes a unique subscription identifier and custom data to be notified. The custom subscription termination message includes a unique subscription identifier.

[0087] In one embodiment, the subscription controller 140 is configured to set a value of an expiration time, the expiration time being the time until which the client SIP node 100 wishes to receive the current status of the subscription and subsequent notifications. Furthermore, the subscription controller 140 is configured to set a value of a time interval, the time interval being the period between two successive notifications indicated by the client SIP node 100. Furthermore, the subscription controller 140 is configured to set a value of a total number of users for which the client SIP node 100 requests location information. Furthermore, the subscription controller 140 is configured to add a user ID of each user and an integer that uniquely represents the user in the list of user IDs.

[0088] 2A illustrates various hardware components of the client SIP node 100, it should be understood that other embodiments are not so limited. In other embodiments, the client SIP node 100 may include fewer or more components. Additionally, the labels or names of the components are used for descriptive purposes only and do not limit the scope of the present disclosure. One or more components may be coupled together to perform the same or substantially similar functions to provide a generic framework for managing custom subscriptions via SIP.

[0089] FIG. 2B illustrates a block diagram of a server SIP node 200 for managing custom subscriptions over SIP according to one embodiment as disclosed herein.

[0090] In one embodiment, the server SIP node 200 includes a memory 210 , a processor 220 , a communicator 230 , and a subscription controller 240 .

[0091] In one embodiment, the memory 210 is configured to store configurations of a plurality of parameters. The memory 210 stores instructions to be executed by the processor 220. The memory 210 may include a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, flash memory, or a form of electrically programmable memory (EPROM) or electrically erasable and programmable (EEPROM) memory. Furthermore, the memory 210 may be considered a non-transitory storage medium in some examples. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagating signal. However, the term "non-transitory" should not be interpreted as the memory 210 being non-movable. In certain examples, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or cache). The memory 210 may be an internal storage device or may be an external storage device of the client SIP node 200, cloud storage, or any other type of external storage device.

[0092] Processor 220 is in communication with memory 210, communicator 230, and subscription controller 240. Processor 220 is configured to execute instructions stored in memory 210 and perform various processes. The processor may include one or more processors and may be a general-purpose processor such as a central processing unit (CPU), an application processor (AP), a graphics-specific processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI)-specific processor such as a neural processing unit (NPU).

[0093] Communicator 230 is configured to communicate internally between internal hardware components and with external devices (e.g., client SIP node 100) over one or more networks (e.g., the Internet, Wi-Fi, Bluetooth, etc.). Communicator 230 includes standard-specific electronic circuitry that enables wired or wireless communication.

[0094] The subscription controller 240 may be implemented by processing circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, and the like, and may optionally be driven by firmware, which may, for example, be embodied in one or more semiconductor chips or may be implemented on a substrate support, such as a printed circuit board.

[0095] In one embodiment, the subscription controller 240 is configured to receive a SIP message from the client SIP node 100 to create a custom subscription via SIP for the custom information, the SIP message including a custom subscription creation request message, the custom subscription creation request message including a plurality of parameters. Furthermore, the subscription controller 240 is configured to send a response message to the client SIP node 100 in response to receiving the SIP message. Furthermore, the subscription controller 240 is configured to store the received plurality of parameters to create a subscription context. Furthermore, the subscription controller 240 is configured to generate a unique subscription identifier in response to receiving the SIP message to create a subscription via SIP for the custom information and to start a subscription expiration timer. Furthermore, the subscription controller 240 is configured to assign the unique subscription identifier to the SIP message received from the client SIP node 100. Furthermore, the subscription controller 240 is configured to create a subscription via SIP for the custom information of the plurality of users based on the subscription context by sending a SIP message to the client SIP node 100, the SIP message including a custom subscription creation response message. The custom subscription creation response message includes an expiration time and a unique subscription identifier.

[0096] Further, the subscription controller 240 is configured to change the expiration time, and if the expiration time value present in the received SIP message is not accepted by the server SIP node 200, the server SIP node 200 changes the expiration time value to a value different from the value present in the received SIP message. Further, the subscription controller 240 is configured to change the total number of users for which the client SIP node 100 requests location information. Further, the subscription controller 240 is configured to add the user ID of each user from the reconstructed total number of users. Further, the subscription controller 240 is configured to start a subscription expiration timer and a notification interval timer based on the configuration of the server SIP node 200.

[0097] Further, the subscription controller 240 further includes an operation of receiving a SIP message from the client SIP node 100 to modify the created custom subscription via SIP for the custom information of the plurality of users, the SIP message including a custom subscription modification request message, the custom subscription modification request message including the unique subscription identifier and the updated plurality of parameters. Further, the subscription controller 240 is configured to configure the plurality of parameters and restart the expiration timer based on the updated plurality of parameters. Further, the subscription controller 240 is configured to modify the created custom subscription via SIP for the custom information of the plurality of users based on the SIP message received from the client SIP node 100 and send a SIP message to the client SIP node 100, the SIP message including a custom subscription modification response message. The custom subscription modification response message includes the updated expiration date and the unique subscription identifier.

[0098] Further, the subscription controller 240 is configured to receive a SIP message from the client SIP node 100 to delete the created custom subscription via SIP for the custom information of a plurality of users, the SIP message including a custom subscription deletion request message, the custom subscription deletion request message including a unique subscription identifier and an expiration time, the expiration time value being 0 (zero). Further, the subscription controller 240 is configured to delete the stored custom subscription via SIP for the location information of a plurality of users and a plurality of parameters associated with the SIP message received from the client SIP node 100. Further, the subscription controller 240 is configured to send a SIP message to the client SIP node 100, the SIP message including a custom subscription deletion response message, expiration time and time interval expiration.

[0099] Further, the subscription controller 240 is configured to notify the client SIP node 100 of the custom information of the multiple users with a SIP message, the SIP message including a custom subscription notification message, the custom subscription notification message including a unique subscription identifier and the custom data to be notified. The client SIP node 100 stores the custom data when the client SIP node 100 receives the SIP message from the server SIP node 200, and shares the custom data with at least one user.

[0100] Further, the subscription controller 240 is configured to send a SIP message to the client SIP node 100 to terminate the created custom subscription via SIP for the custom information of a plurality of users, the SIP message including a custom subscription termination message, the custom subscription termination message including a unique subscription identifier. When the client SIP node 100 receives the SIP message from the server SIP node 200, the client SIP node 100 deletes the created custom subscription and terminates a subscription expiration timer and a notification interval timer.

[0101] 2B illustrates various hardware components of the server SIP node 200, it should be understood that other embodiments are not so limited. In other embodiments, the server SIP node 200 may include fewer or more components. Additionally, the labels or names of the components are used for descriptive purposes only and do not limit the scope of the present disclosure. One or more components may be coupled together to perform the same or substantially similar functions to provide a generic framework for managing custom subscriptions via SIP.

[0102] 2CA and 2CB illustrate various message formats for multiple parameters managing custom subscriptions over SIP according to one embodiment as disclosed herein.

[0103] The least significant bit of a field is represented by the lowest numbered bit of the highest numbered octet of the field. When a field extends across one or more octets, the order of bit values ​​gradually decreases as the number of octets increases. The purpose of the message type information element 201 is to identify the type of message. The message type information element is a type 3 information element of length one octet.

[0104] In one embodiment, the expiration information element 202 is used to indicate the duration in seconds for which the subscription remains active. The expiration value is an unsigned integer that specifies the time in seconds for which the subscription remains active. The expiration information element is a type 3 information element of length 3 octets.

[0105] In one embodiment, the time interval information element 203 is for providing the time (in seconds) between two successive notifications from the server SIP node 200 / The expiration value is an unsigned integer specifying the duration in seconds between two successive notifications. Said time interval information element is a type 3 information element of length 2 octets.

[0106] In one embodiment, the subscription identifier information element 204 uniquely identifies the event subscription. The subscription identifier information element is a type 3 information element of length 4 octets. The subscription identifier contains a number that uniquely identifies a subscription request to the VAL server 100, which may have performed multiple subscriptions.

[0107] In one embodiment, the Number of Users information element 205 identifies the number of users included in the message. The Number of Users information element is a Type 3 information element of length 2 octets. The Number of Users includes values ​​from 1 to 255. The Number of Users value is included in octet 2 if the IE is used as an optional information element. If used as a mandatory information element, the Number of Users information element is omitted and the Number of Users value is included in octet 1.

[0108] In one embodiment, a user identity information element 206 is used to indicate the VAL user ID. The user identity information element is a type 6 information element.

[0109] In one embodiment, the VAL User Number 207 includes a unique number assigned to each VAL User ID content. The SLM-S 200 uses this number to transmit the location information of the assigned VAL User ID. The VAL User Number starts at 1 and increments by 1 for each User Identification IE. The VAL User Number value is included in octet 4 if the IE is used as an optional IE. If used as a mandatory IE, the User Identification IEI is omitted and the VAL User Number value is included in octet 3. The VAL User ID is included in octets 4 to n, with a maximum value of 65535 octets. The VAL User ID value is included in octets 5 to n if the IE is used as an optional IE. If used as a mandatory IE, the User Identification IEI is omitted and the VAL User ID value is included in octets 4 to n.

[0110] In one embodiment, the User Location Data information element 208 is used to indicate the current location of a VAL user. The User Location Data information element is a Type 6 information element. The VAL User Number contains a unique number specified in the Location Event Subscribe Request message. The user location is contained in octet 5 to octet n, with a maximum value of 65535 octets.

[0111] In one embodiment, the following procedures provide server 200 side actions upon expiration of different timers: When the TLM-1 (subscription expiration) timer expires, the SLM-S200 considers the subscription to have ended and deletes all data related to the subscription; and When the TLM-2 (notification interval) timer expires, the SLM-S200 checks if any notifications are pending to be sent. The SLM-S200 sends the notification if there are any notifications pending.

[0112] The following subsections provide definitions and content for the Location Management Message Functions listed above. Each message contains a series of information elements.

[0113] In one embodiment, a create location event subscribe request message 201: this message is sent by the VAL server 100 to the SLM-S 200 to request the SLM-S 200 to create a subscription to the location information of the VAL user specified in the request message. The contents of the message are shown in Table 1.

[0114] [Table 1]

[0115] The SLM-S 200 may decide to support creation, modification, and deletion of subscriptions using only a single request message. In such a case, an optional subscription identifier IE is added to Table 1. The VAL server 100 includes the subscription identifier IE value when the VAL server 100 requests to modify or delete a subscription. In one embodiment, the information elements specified in Table 1 can be transmitted via any data format (e.g., XML).

[0116] In one embodiment, a location event subscribe create response message 201: This message is sent by the SLM-S server 200 to the VAL server 100 as a response to the location event subscribe create request message. The contents of the message are shown in Table 2.

[0117] [Table 2]

[0118] In one embodiment, the information elements specified in Table 2 may be transmitted in any data format (eg, XML). In one embodiment, an integer may be used as the information element identity value.

[0119] In one embodiment, a modify location event subscribe request message 201: this message is sent by the VAL server 100 to the SLM-S 200 to request the SLM-S 200 to modify the location information subscription of the VAL user specified in the request message. The contents of the message are shown in Table 3.

[0120] [Table 3]

[0121] In one embodiment, the information elements specified in Table 3 may be transmitted in any data format (eg, XML). In one embodiment, integers may be used as information element identification values.

[0122] In one embodiment, a modify location event subscribe response message: this message is sent by the SLM-S server 200 to the VAL server 100 as a response to the modify location event subscribe request message. The contents of the message are shown in Table 4.

[0123] [Table 4]

[0124] In one embodiment, the information elements specified in Table 4 may be transmitted in any data format (eg, XML). In one embodiment, integers may be used as information element identification values.

[0125] In one embodiment, a delete location event subscribe request message 201: this message is sent by the VAL server 100 to the SLM-S 200 to request the SLM-S 200 to delete the subscription to location information of the VAL user specified in the request message. The contents of the message are shown in Table 5.

[0126] [Table 5]

[0127] In one embodiment, the information elements specified in Table 5 may be transmitted in any data format.

[0128] In one embodiment, a delete location event subscribe response message 201: This message is sent by the SLM-S server 200 to the VAL server 100 in response to the delete location event subscribe request message. The contents of the message are shown in Table 6.

[0129] [Table 6]

[0130] In one embodiment, the information elements specified in Table 6 may be transmitted in any data format.

[0131] In one embodiment, a location event notify message 201: This message is sent by the SLM-S 200 to the VAL server 100 to inform the VAL server 100 about the location information of the VAL user specified in the request message. The contents of the message are shown in Table 7.

[0132] [Table 7]

[0133] In one embodiment, the information elements specified in Table 7 may be transmitted in any data format.

[0134] In one embodiment, a terminate location event subscribe message 201: this message is sent by the SLM-S 200 to the VAL server 100 to inform the VAL server 100 of the end of the subscription. The contents of the message are shown in Table 8.

[0135] [Table 8]

[0136] In one embodiment, the information elements specified in Table 1 may be transmitted in any data format.

[0137] FIG. 3A is a sequence diagram illustrating various operations for creating a custom subscription over SIP according to one embodiment as disclosed herein.

[0138] In 302a, the client SIP node 100 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription creation request message that includes at least an expiration time (i.e., TLM-1), a time interval between two successive notifications (i.e., TLM-2), and other subscription-specific data. The client SIP node 100 sends the SIP message towards the server SIP node 200. In 304a, the server SIP node 200 sends a SIP 200 (OK) response towards the client SIP node 100. In 306a, the server SIP node 200 stores the received subscription data, generates a unique subscription identifier, and starts an expiration timer. In 308a, the server SIP node 200 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription creation response message that includes at least a unique subscription identifier and an expiration time for which the subscription was accepted. The server SIP node 200 sends the SIP message towards the client SIP node 100. At 310a, the client SIP node 100 sends a SIP 200 (OK) response towards the server SIP node 200. The client SIP node 100 starts a subscribe refresh timer (i.e., TLM-3).

[0139] 3B is a sequence diagram illustrating various operations for creating a custom subscription over SIP for location information according to one embodiment as disclosed herein, where the VAL server acts as a client SIP node 100 and the SLM-S acts as a server SIP node 200.

[0140] At 302b, to subscribe to location information of one or more VAL users, the VAL server 100: Creates SIP message requests according to 3GPP TS 24.229 and IETF RFC 3428; Set the request-URI to the identity of the SLM-S200; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" as described above, along with the parameters "require" and "explicit" in accordance with IETF RFC 3841; In the SIP message request, the location event subscribe create request message specified in Figures 2CA and 2CB is included in the application / vnd.3gpp.location-event MIME body. In the location event subscribe create request message, the VAL server 100: Set the expiration date IE to the expiration date indicated by the VAL server 100; Set the time interval IE to the time period between two successive notifications as indicated by the VAL server 100; The Number of Users IE is set by the VAL server 100 to the total number of VAL users requesting location information; and Add a user identity IE for each VAL user. In the user identity IE: Set the VAL user number to an integer that uniquely represents the VAL user among the list of users of the request being sent, Setting the VAL user ID content to the VAL user ID of the VAL user; and Send a SIP message request towards SLM-S 200 according to 3GPP TS 24.229. In one embodiment, the SIP message request directed towards SLM-S 200 may include an expiration time, a time interval, a number of users, a user identification for each user, and other required parameters (e.g., in XML or any other data format).

[0141] In 304b to 306b, when the SLM-S 200 receives a SIP message having an application / vnd.3gpp.location-event MIME body including a location event subscribe creation request message, the SLM-S 200: Generate a SIP 200 (OK) response and send it to the VAL server 100; Stores all user information contained in the User Identification IE and can change the VAL User Number associated with the VAL User ID; store the subscribe expiration time in the expiration time IE value, and if the expiration time value present in the expiration time IE is not acceptable to the SLM-S200, the SLM-S200 may change the expiration time value to a value different from the requested value; Store the time interval value in the Time Interval IE Value, Generate and assign a unique integer as a subscription identifier to the subscription request received from the VAL server 100; At 308b, the SLM-S 200 creates a SIP message request according to 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S 200: Set the request-URI to the identity of the VAL server 100; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" as described above, with the parameters "require" and "explicit" in accordance with IETF RFC 3841; Include the location event subscribe create response message specified in Figures 2CA and 2CB in the application / vnd.3gpp.location-event MIME body. In the location event subscribe create response message, the SLM-S 200: Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request; Set the Expiration IE to the accepted expiration value, If the SLM-S200 changes the VAL user number associated with any of the VAL User IDs from the request message, it sets the Number of Users IE to the total number of VAL users; and Add a User Identity IE for each VAL user. In the User Identity IE: Set the number of VAL users assigned to the VAL user ID, Setting the VAL User ID Content to the VAL User ID of the VAL User; and Send a SIP message request towards the VAL server 100 according to 3GPP TS 24.229, start timer TLM-1 (subscription expiration time) and set the timer expiration time to the subscription expiration time. In one embodiment, the SIP message request to the VAL server 100 may include the subscription identifier, the expiration time, the number of users, the user identification of each user, and other required parameters (e.g., in XML or any other data format).

[0142] At 310b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body containing a location event subscribe create response message, the VAL server 100: Store the subscription identifier IE value; Start timer TLM-3(Subscription Refresh) and set the expiration time of the TLM-3(Subscription Refresh) timer to 2 / 3 of the Expiration IE value; and At the expiration time of TLM-3 (subscription refresh), based on the request of the VAL user, the VAL server 100 can modify the subscription to set a new expiration value.

[0143] FIG. 4A is a sequence diagram illustrating various operations for modifying a custom subscription over SIP according to one embodiment as disclosed herein.

[0144] In 402a, the client SIP node 100 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription modification request message including at least a subscription identifier, an expiration date, a time interval between two successive notifications, and other subscription-specific data. The client SIP node 100 sends the SIP message towards the server SIP node 200. In 404a, the server SIP node 200 sends a SIP 200 (OK) response towards the client SIP node 100. In 406a, the server SIP node 200 updates the subscription data and restarts the expiration timer. In 408a, the server SIP node 200 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription modification response message including at least a unique subscription identifier and an accepted expiration date for the subscription. The server SIP node 200 sends the SIP message towards the client SIP node 100. At 410a, the client SIP node 100 sends a SIP 200 (OK) response towards the server SIP node 200. The client SIP node 100 restarts the refresh timer.

[0145] FIG. 4B is a sequence diagram illustrating various operations for modifying a custom subscription over SIP for location information according to one embodiment as disclosed herein.

[0146] At 402b, to modify subscriptions to location information of one or more VAL users, the VAL server 100: Constructs a SIP message request in accordance with 3GPP TS 24.229 and IETF RFC 3428; Set the request-URI to the identity of the SLM-S200; Include an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" as described above, along with the parameters "require" and "explicit" in accordance with IETF RFC 3841; The SIP message request includes a location event subscribe modify request message as specified in Figures 2CA and 2CB in an application / vnd.3gpp.location-event MIME body; in the location event subscribe modify request message, the VAL server 100: Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription; Set the expiration date IE to the expiration date indicated by the VAL server 100; Set the time interval IE to the time period between two successive notifications as indicated by the VAL server 100; The Number of Users IE is set by the VAL server 100 to the total number of VAL users requesting location information; and Add a user identity IE for each VAL user. In the user identity IE: Setting the VAL user number to an integer that uniquely represents the VAL user among the list of users of the request being sent, and Setting the VAL user ID content to the VAL user ID of the VAL user; and Send a SIP message request towards SLM-S 200 according to 3GPP TS 24.229. In one embodiment, the SIP message request directed to SLM-S 200 may include a subscription identifier, an expiration time, a time interval, a number of users, a user identification for each user, and other required parameters (e.g., in XML or any other data format).

[0147] In 404b to 406b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body including a location event subscribe modification request message, the SLM-S 200: Generate a SIP200(OK) response and send it to the VAL server 100; If useful in the request message, store any user information contained in the User Identification IE and may modify the VAL User Number associated with the VAL User ID; and The expiration time of the subscription is stored in the Expiry Time IE value, and if the expiration time value present in the Expiry Time IE is not acceptable to the SLM-S200, the SLM-S200 can change the expiration time value to a value different from the requested value.

[0148] At 408b, the SLM-S 200 creates a SIP message request according to 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S 200: Set the request-URI to identify the VAL server; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" with the parameters "require" and "explicit" in accordance with IETF RFC 3841; Include the location event subscribe modification response message as specified in Figures 2CA and 2CB in the application / vnd.3gpp.location-event MIME body. Fixes In the response message, the SLM-S200: Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request; Set the Expiration Date IE to the accepted expiration date value, If the SLM-S200 changes the VAL user number associated with any of the VAL User IDs from the request message, it sets the Number of Users IE to the total number of VAL users; and For each VAL user, add a User Identity IE. For the User Identity IE: Set the number of VAL users assigned to the VAL user ID, and Set the content of the VAL user ID to the VAL user ID of the VAL user, Sending a SIP message request towards the VAL server 100 according to 3GPP TS 24.229, starting timer TLM-1 (subscription expiration time) and setting the timer expiration time to the subscription expiration time; and Restart timer TLM-1 (subscription expiration) and set the timer expiration to the subscription expiration. In one embodiment, the SIP message request to the VAL server 100 may include the subscription identifier, the expiration date, the number of users, the user identification of each user, and other required parameters (e.g., in XML or any other data format).

[0149] At 410b, a location event subscribe Fixes Upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body containing a response message, the VAL server 100: Stores the subscription identifier IE value; and Start timer TLM-3(subscription refresh) and set the expiration time of the TLM-3(subscription refresh) timer to 2 / 3 of the expiration time IE value.

[0150] FIG. 5A is a sequence diagram illustrating various operations for deleting a custom subscription over SIP according to one embodiment as disclosed herein.

[0151] At 502a, the client SIP node 100 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription deletion request message including at least a subscription identifier and an expiration value set to a value 0 (zero). The client SIP node 100 sends the SIP message towards the server SIP node 200. At 504a, the server SIP node 200 sends a SIP 200 (OK) response towards the client SIP node 100. At 506a, the server SIP node 200 deletes the subscription data and also deletes the expiration timer and the notification interval timer. At 508a, the server SIP node 200 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription deletion response message including at least a unique subscription identifier. The server SIP node 200 sends the SIP message toward the client SIP node 100. The client SIP node 100 sends a SIP 200 (OK) response toward the server SIP node 200 at 510a.

[0152] FIG. 5B is a sequence diagram illustrating various operations for deleting a custom subscription over SIP for location information according to one embodiment as disclosed herein.

[0153] At 502b, to delete location information of one or more VAL users, the VAL server 100: Creates SIP message requests according to 3GPP TS 24.229 and IETF RFC 3428; Set the request-URI to the identity of the SLM-S200; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" with the parameters "require" and "explicit" in accordance with IETF RFC 3841; In the SIP message request, include the location event subscribe remove request message specified in Figures 2CA and 2CB in the application / vnd.3gpp.location-event MIME body. delete In the request message, the VAL server 100: Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription; Set the Expiration Date IE to the value 0 (zero); and Send a SIP message request towards SLM-S 200 according to 3GPP TS 24.229. In one embodiment, the SIP message request to SLM-S 200 may include a subscription identifier, an expiration date, and other required parameters (e.g., in XML or any other data format).

[0154] In 504b to 506b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body including a location event subscribe removal request message, the SLM-S200: Generate and send a SIP 200 (OK) response towards the VAL server 100; and Delete all information related to your subscription.

[0155] At 508b, the SLM-S 200 creates a SIP message request in accordance with 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S 200: Set the request-URI to the identity of the VAL server 100; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" with the parameters "require" and "explicit" in accordance with IETF RFC 3841; Include the location event subscribe remove response message specified in Figures 2CA and 2CB in the application / vnd.3gpp.location-event MIME body. In the location event subscribe remove response message, the SLM-S 200: Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request; sending a SIP message request towards the VAL server 100 according to 3GPP TS 24.229; Interrupts the TLM-1 (Subscribe Expiry) timer if it is running, and Pause the TLM-2 (notification interval) timer if it is running. In one embodiment, the SIP message request directed to the VAL server 100 may include the subscription identifier and other required parameters (e.g., in XML or any other data format).

[0156] At 510b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body containing a location event subscribe remove response message, the VAL server 100: Delete your subscription-related data; and Timer TLM-3 (Subscription Refresh) Interrupt the timer.

[0157] FIG. 6A is a sequence diagram illustrating various operations for sending a notification of a custom subscription over SIP according to one embodiment as disclosed herein.

[0158] In 602a-604a, if the notification interval timer is not running, the client SIP node 100 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a notification that includes at least a subscription identifier and notification data. The server SIP node 200 sends the SIP message towards the client SIP node 100. In 606a, the client SIP node 100 sends a SIP 200 (OK) response towards the server SIP node 200. The client SIP node 100 stores the data received in the notification and can present it to the user or even share it with other users. The server SIP node 200 starts the notification interval timer.

[0159] FIG. 6B is a sequence diagram illustrating various operations for sending a notification of a custom subscription over SIP for location information according to one embodiment as disclosed herein.

[0160] In 602b to 604b, to inform the VAL server 100 about the location information report, the SLM-S 200: If the TLM-2 (notification interval) timer is running, the remaining steps may be skipped; Creates SIP message requests according to 3GPP TS 24.229 and IETF RFC6086; Set the request-URI to the identity of the VAL server 100; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" with the parameters "require" and "explicit" in accordance with IETF RFC 3841; In the SIP message request, the location event notification message specified in Figures 2CA and 2CB is included in the application / vnd.3gpp.location-event MIME body. In the location event notification message, the SLM-S 200: Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription; Set the Number of Users IE to the total number of VAL users whose location information is included in the message; and for each VAL user, including a User Location Data IE containing the number of VAL users and location information data associated with the VAL User ID; Sending a SIP message request towards the VAL server 100 according to 3GPP TS 24.229; Start a TLM-2 (notification interval) timer and set the timer expiration to the value of the time interval. In one embodiment, the SIP message request to the VAL server 100 may include a subscription identifier, the number of users, location data of each user, and other required parameters (e.g., in XML or any other data format).

[0161] At 606b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body containing a location event notification message, the VAL server 100: storing the received location information; and We may share such information with a group or other VAL User or VAL UE.

[0162] FIG. 7A is a sequence diagram illustrating various operations for terminating a custom subscription over SIP according to embodiments as disclosed herein.

[0163] In steps 702a-704a, the client SIP node 100 creates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a custom subscription termination message that includes at least a subscription identifier. The server SIP node 200 sends the SIP message toward the client SIP node 100. In step 706a, the client SIP node 100 sends a SIP 200 (OK) response toward the server SIP node 200. The client SIP node 100 deletes the subscription-related data and also deletes all timers.

[0164] FIG. 7B is a sequence diagram illustrating various operations for terminating a custom subscription over SIP for location information according to one embodiment as disclosed herein.

[0165] In 702b to 704b, to notify the VAL server 100 of the end of the subscription, the SLM-S 200: Creates SIP message requests according to 3GPP TS 24.229 and IETF RFC6086; Set the request-URI to the identity of the VAL server 100; including an accept-contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.seal" with the parameters "require" and "explicit" in accordance with IETF RFC 3841; In the SIP message request, the SLM-S 200 includes a location event subscribe end message as specified in Figures 2CA and 2CB in an application / vnd.3gpp.location-event MIME body. In the location event subscribe end message, the SLM-S 200: Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription; The SIP message request is sent according to 3GPP TS 24.229 towards the VAL server 100. In one embodiment, the SIP message request to the VAL server 100 may include a subscription identifier and other required parameters (e.g., in XML or any other data format).

[0166] At 706b, upon receiving a SIP message with an application / vnd.3gpp.location-event MIME body containing a location event subscribe end message, the VAL server 100: Delete your subscription-related data; and Timer TLM-3 (Subscription Refresh) Interrupt the timer.

[0167] The embodiments disclosed herein may be implemented using at least one hardware device to perform network management functions for controlling said elements.

[0168] Although the present disclosure has been described in various embodiments, various changes and modifications may be suggested to those skilled in the art, and the present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. [Explanation of symbols]

[0169] 10 Client SIP Nodes 20 Server SIP Node 100 VAL Server 110 Memory 120 processors 130 Communicator 140 Subscription Controller 200 SLM-S servers 201 location event notify message 202 Expiry Information Element 203 Time Interval Information Element 204 Subscription Identifier Information Element 205 Information Elements 206 User Identity Information Element 207 VAL User Number 208 User Location Data Information Element 210 Memory 220 Processor 230 Communicator 240 Subscription Controller

Claims

1. A method for managing subscriptions via a Session Initiation Protocol (SIP) in a service enabler architecture layer (SEAL) location management server (SLM-S), comprising: receiving a first SIP message from a Vertical Application Layer (VAL) server requesting creation of the subscription for subscribing to location information via SIP; sending a response message to the VAL server in response to receiving the first SIP message; generating subscription identifier information specifying a unique subscription identifier (ID) for identifying the subscription; and sending a second SIP message including the subscription identifier information to the VAL server; the first SIP message includes expiration information specifying an expiration time of the subscription and time interval information specifying a time between two successive notifications for the subscription; the second SIP message further includes information specifying an approved expiration date for the subscription; The method, wherein the expiration information is associated with a subscription expiration timer for the SLM-S, and the time interval information is associated with a notification interval timer for the SLM-S.

2. The method of claim 1 , wherein the first SIP message further includes user identity information including an identity of at least one VAL user for which the location information is requested.

3. resetting the expiration time for the subscription if the value of the expiration time information included in the first SIP message is not approved by the SLM-S; and The method of claim 1 , further comprising starting the subscription expiration timer and setting the reset expiration value to an expiration time of the subscription expiration timer.

4. receiving a third SIP message from the VAL server via the SIP requesting deletion of the subscription, the third SIP message including the subscription identifier information and an expiration time set to a value of 0; sending a response message to a VAL server in response to receiving the third SIP message; deleting at least one parameter associated with the subscription; and 2. The method of claim 1, further comprising the step of: sending a fourth SIP message to the VAL server to disable a subscription expiration timer and a notification interval timer, the fourth SIP message including the subscription identifier information.

5. The method of claim 2 , further comprising the step of: sending a fifth SIP message to the VAL server for notifying the location information, the fifth SIP message including the subscription identifier information and data to be notified.

6. The method of claim 5 , wherein the VAL server stores the data in the fifth SIP message and shares the data with the at least one VAL user.

7. In a Service Enabler Architecture Layer (SEAL) location management server (SLM-S) for managing subscriptions via a Session Initiation Protocol (SIP), said SLM-S comprises: Transceiver; A processor coupled to the transceiver, the processor comprising: receiving a first SIP message from a vertical application layer (VAL) server requesting creation of the subscription for subscribing to location information via SIP; In response to receiving the first SIP message, sending a response message to the VAL server; generating subscription identifier information specifying a unique subscription identifier (ID) for identifying the subscription; and configured to send a second SIP message including the subscription identifier information to the VAL server; the first SIP message includes expiration information specifying an expiration time for the subscription and time interval information specifying a time between two successive notifications for the subscription; the second SIP message further includes information specifying an approved expiration date for the subscription; The expiration information is associated with a subscription expiration timer for the SLM-S, and the time interval information is associated with a notification interval timer for the SLM-S.

8. The SLM-S of claim 7, wherein the first SIP message further includes user identity information including an identity of at least one VAL user for which the location information is requested.

9. The processor, resetting an expiration time for the subscription if the value of the expiration time information included in the first SIP message is not approved by the SLM-S; The SLM-S of claim 7, further configured to: start the subscription expiration timer; and set the subscription expiration timer to an expiration value of the reset expiration time.

10. The processor: receiving a third SIP message from the VAL server via the SIP requesting deletion of the subscription, the third SIP message including the subscription identifier information and an expiration time set to a value of 0; In response to receiving the third SIP message, sending a response message to the VAL server; Deleting at least one parameter associated with the subscription; The SLM-S of claim 7, further comprising: sending a fourth SIP message to the VAL server, the fourth SIP message being configured to disable a subscription expiration timer and a notification interval timer, the fourth SIP message including the subscription identifier information.

11. The SLM-S of claim 8, further comprising a step of sending a fifth SIP message to the VAL server to notify the location information, the fifth SIP message including the subscription identifier information and the data to be notified.

12. The SLM-S of claim 11, wherein the VAL server stores the data in the fifth SIP message and shares the data with the at least one VAL user.

13. A Vertical Application Layer (VAL) server for managing subscriptions via a Session Initiation Protocol (SIP), comprising: Transceiver; A processor coupled to the transceiver, the processor comprising: sending a first SIP message to a SEAL (Service Enabler Architecture Layer) SLM-S (SEAL location management server) requesting creation of the subscription for subscribing to the location information via SIP; receiving a response message from the SLM-S in response to the first SIP message; and configured to receive from the SLM-S a second SIP message including subscription identifier information specifying a unique subscription identifier for identifying the subscription; the first SIP message includes expiration information specifying an expiration time for the subscription and time interval information specifying a time between two successive notifications for the subscription; the second SIP message further includes information specifying an approved expiration date for the subscription; The expiration information is associated with a subscription expiration timer for the SLM-S, and the time interval information is associated with a notification interval timer for the SLM-S. VAL Server.

Images