Method and apparatus for providing a general framework for managing SIP custom subscriptions

Abstract

The present disclosure relates to a communication method and system for converging fifth generation (5G) communication systems and technologies for the Internet of Things (IoT), wherein the fifth generation (5G) communication systems support higher data rates than fourth generation (4G) systems. The present disclosure can be applied to smart services based on 5G communication technologies and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, health care, digital education, smart retail, security and safety services. Therefore, embodiments of the present invention disclose a method for providing a general framework for managing SIP custom subscriptions. The method includes sending at least one request with multiple 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 Session Initiation Protocol (SIP). The present disclosure particularly relates to a method and a SIP node that provide a general framework for managing SIP custom subscriptions. Background Art

[0002] In order to meet the demand for increased wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, in 5G communication systems, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed. In addition, in 5G communication systems, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. is underway. In 5G systems, 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 technologies have been developed.

[0003] The Internet is a human-centered connectivity network where humans generate and consume information, and is now developing into 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 as a combination of IoT technology and big data processing technology through connection with cloud servers. IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", and sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart devices, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.

[0005] In the existing SIP-based subscription mechanism, the user requires an event package in the subscription request to subscribe to any event data (e.g., conference data, location data, sensor data, etc.) from the server. According to RFC 3265, the user (subscriber) can have an "Event" header (Event Package) in the subscription request to indicate which event data or event data class the user wants to subscribe to. Figure 1 The present invention is a sequence diagram showing an existing SIP-based subscription mechanism according to the prior art disclosed herein. In step 1-2, a client SIP node (10) sends a SIP subscription request for subscribing to specific event data from a server SIP node (20). The subscription request includes an event package (event report request). In step 3-5, a specific event occurs at the server SIP node (20), and the server SIP node (20) sends a notification SIP notification message (event report) associated with the subscribed specific event data to the client SIP node (10).

[0006] Furthermore, according to the Internet Assigned Numbers Authority (IANA), there are limited event packages available, and there are some servers available in the world that have different types of data available (e.g., location data, sensor data, etc.), but do not have an IANA-registered event package associated with it. For example, if any authorized user wants to subscribe to another user's device location, there is no event package available. Similarly, there is no event package available to subscribe to the data of a temperature sensor by any authorized user. Furthermore, defining and standardizing new event packages requires a lot 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 the location information of VAL users. The location management service allows a VAL server to subscribe to the location information of VAL users. However, there is no standard SIP event package that can be used for a SIP-based subscription mechanism.

[0008] Typically, a user (eg, client SIP node (10), VAL server, user equipment (UE)) may request an event package in a subscription request to subscribe to any event data from a server (eg, server SIP node (20), SEAL server). Summary of the invention

[0009] Technical issues

[0010] There is no mechanism by which a user can subscribe to any data type via SIP, regardless of whether an event package is available. It is therefore desirable to address the above shortcomings or at least provide a useful alternative.

[0011] Solution to the problem

[0012] The main purpose of the embodiments herein is to provide a general framework for managing custom subscriptions, which sends at least one request with multiple parameters to a server via SIP for any data type, regardless of whether an event package is available. The custom subscription is managed by creating a custom subscription, modifying a custom subscription, deleting a custom subscription, notifying a custom subscription, and terminating a custom subscription using multiple parameters.

[0013] Another object of embodiments herein is to provide subscription to a location service associated with a SEAL Location Management Server (SLM-S) via SIP, regardless of whether event packages are available. The SLM-S allows a VAL server to manage location information for VAL users using a number of parameters.

[0014] Therefore, the embodiments herein disclose a method for providing a general framework for managing SIP custom subscriptions. The method includes receiving a SIP message from a client SIP node by a server SIP node to create a SIP custom subscription to custom information, wherein the SIP message includes a create custom subscription request message, wherein the create custom subscription request message includes multiple parameters. In addition, the method includes sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method includes generating a unique subscription identifier by the server SIP node in response to receiving a SIP message for creating a SIP custom subscription to custom information, and starting a subscription expiration timer. In addition, the method includes creating a subscription to custom information by the server SIP node based on a subscription context from a received SIP message. In addition, the method includes assigning a unique subscription identifier to the created custom subscription to custom information by the server SIP node based on the subscription context from the received SIP message. In addition, the method includes sending a SIP message to the client SIP node by the server SIP node, wherein the SIP message includes a create custom subscription response message.

[0015] In one embodiment, the plurality of parameters include an expiration time, a time interval, and other subscription related parameters.

[0016] In one embodiment, a custom subscription response message is created that includes an expiration time, a unique subscription identifier, and other subscription related parameters.

[0017] In one embodiment, the method further comprises configuring, by the client SIP node, a value for an expiration time, wherein before the expiration time, the client SIP node wants to receive the current status of the custom subscription and later notifications. In addition, the method comprises configuring, by the client SIP node, a value for a time interval, wherein the time interval is the time period between two consecutive notifications indicated by the client SIP node. In addition, the method comprises configuring, by the client SIP node, other required parameters according to the subscription data type.

[0018] In one embodiment, the method further comprises reconfiguring the expiration time by the server SIP node, wherein when the value of the expiration time present in the received SIP message is not accepted by the server SIP node, the server SIP node changes the value of the expiration time to a value different from the value present in the received SIP message. In addition, the method comprises starting a subscription expiration timer and a notification interval timer by the server SIP node based on the configuration of the server SIP node.

[0019] In one embodiment, the method further comprises receiving a SIP message from a client SIP node by a server SIP node to modify the created SIP custom subscription to the custom information, wherein the SIP message comprises a modification custom subscription request message, wherein the modification custom subscription request message comprises a unique subscription identifier and a plurality of updated parameters. In addition, the method comprises sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method comprises configuring a plurality of parameters based on the updated plurality of parameters by the server SIP node, and restarting an expiration timer. In addition, the method comprises modifying the created SIP custom subscription to the custom information by the server SIP node based on the SIP message received from the client SIP node, and sending a SIP message to the client SIP node, wherein the SIP message comprises a modification custom subscription response message.

[0020] In one embodiment, modifying the custom subscription response message includes an updated expiration time, a unique subscription identifier, and other subscription related parameters.

[0021] In one embodiment, the method further comprises receiving, by the server SIP node, a SIP message from the client SIP node to delete the created SIP custom subscription to the custom information, wherein the SIP message comprises a delete custom subscription request message, wherein the delete custom subscription request message comprises a unique subscription identifier and an expiration time, wherein the value of the expiration time is zero. In addition, the method comprises sending, by the server SIP node, a response message to the client SIP node in response to receiving the SIP message. In addition, the method comprises deleting, by the server SIP node, the stored SIP custom subscription to the custom information, and a plurality of parameters associated with the SIP message received from the client SIP node. In addition, the method comprises sending, by the server SIP node (200), a SIP message to the client SIP node, wherein the SIP message comprises a delete custom subscription response message, and terminates the expiration time and the time interval, wherein the delete custom subscription response message comprises the unique subscription identifier.

[0022] In one embodiment, the method further comprises sending, by the server SIP node, a SIP message to the client SIP node to notify information, wherein the SIP message comprises a custom subscription notification message, wherein the custom subscription notification message comprises a unique subscription identifier and data to be notified.

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

[0024] In one embodiment, the method further includes sending a SIP message by the server SIP node to the client SIP node to terminate the created SIP custom subscription for the custom information, wherein the SIP message includes a terminate custom subscription message, wherein the terminate custom subscription message includes the unique subscription identifier.

[0025] 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 terminates the subscription expiration timer and the notification interval timer.

[0026] Therefore, the embodiments herein disclose a method for providing a general framework for managing SIP custom subscriptions. The method includes receiving a SIP message from a client SIP node by a server SIP node to create a SIP subscription for location information of multiple users, the SIP message including a create location event subscription request message, the create location event subscription request message including multiple parameters. In addition, the method includes sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method includes storing the received multiple parameters by the server SIP node to create a subscription context. In addition, the method includes generating a unique subscription identifier by the server SIP node in response to receiving a SIP message for creating a SIP subscription to location information, and starting a subscription expiration timer. In addition, the method includes creating a custom subscription to location information of multiple users based on a subscription context by the server SIP node by sending a SIP message to the client SIP node, the SIP message including a create location event subscription response message.

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

[0028] In one embodiment, the Create Location Event Subscription Response message includes an expiration time and a unique subscription identifier.

[0029] In one embodiment, the method further comprises configuring, by the client SIP node, a value for an expiration time, wherein, before the expiration time, the client SIP node wants to receive the current status of the subscription and be notified later. In addition, the method comprises configuring, by the client SIP node, a value for a time interval, which is a time period between two consecutive notifications indicated by the client SIP node. In addition, the method comprises configuring, by the client SIP node, a value for the total number of users for which the client SIP node requires location information. In addition, the method comprises adding, by the client SIP node, a user ID for each user and an integer uniquely representing the user in a user ID list.

[0030] In one embodiment, the method further comprises, in the case where the value of the expiration time present in the received SIP message is unacceptable to the server SIP node, reconfiguring the expiration time by the server SIP node, the server SIP node changing the value of the expiration time to a value different from the value present in the received SIP message. In addition, the method comprises reconfiguring, by the server SIP node, the total number of users for whose client SIP nodes location information is required. In addition, the method comprises adding, by the server SIP node, a user ID for each user from the reconfigured total number of users. In addition, the method comprises starting, by the server SIP node, a subscription expiration timer and a notification interval timer based on the configuration of the server SIP node.

[0031] In one embodiment, the method further comprises receiving a SIP message from a client SIP node by a server SIP node to modify the created SIP subscription for location information of multiple users, wherein the SIP message comprises a modify location event subscription request message, wherein the modify location event subscription request message comprises a unique subscription identifier and multiple updated parameters. In addition, the method comprises sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method comprises configuring multiple parameters based on the updated multiple parameters by the server SIP node, and restarting an expiration timer. In addition, the method comprises modifying the created SIP subscription for location information of multiple users by the server SIP node based on the SIP message received from the client SIP node, and sending a SIP message to the client SIP node, wherein the SIP message comprises a modify location event subscription response message.

[0032] In one embodiment, the Modify Location Event Subscription Response message includes an updated expiration time and a unique subscription identifier.

[0033] In one embodiment, the method further includes receiving a SIP message from a client SIP node by a server SIP node to delete the created SIP subscription for location information of multiple users, the SIP message including a delete location event subscription request message, the delete location event subscription request message including a unique subscription identifier and an expiration time, the value of the expiration time being zero. In addition, the method includes sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method includes deleting the stored SIP subscription for location information of multiple users and a plurality of parameters associated with the SIP message received from the client SIP node by the server SIP node. In addition, the method includes sending a SIP message to the client SIP node by the server SIP node, the SIP message including a delete location event subscription response message, and terminating the expiration time and the time interval.

[0034] In one embodiment, the method further includes sending a SIP message by the server SIP node to the client SIP node to notify location information of multiple users, the SIP message including a location event notification message including a unique subscription identifier and location data to be notified.

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

[0036] In one embodiment, the method further includes sending a SIP message by the server SIP node to the client SIP node to terminate the created SIP subscription to the location information of multiple users, the SIP message including a terminate location event subscription message, the terminate location event subscription message including a unique subscription identifier.

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

[0038] All of the above embodiments may be applied to create / modify / delete / notify / terminate SIP custom subscriptions for custom information (eg, sensor data, satellite data, location data, etc.).

[0039] Therefore, the embodiments herein provide a server SIP node for providing a general framework for managing SIP custom subscriptions. The server SIP includes a subscription controller connected to a processor and a memory. The subscription controller is configured to receive a SIP message from a client SIP node to create a SIP custom subscription to custom information. In addition, the subscription controller is configured to send the response message to the client SIP node in response to receiving the SIP message. In addition, the subscription controller is configured to store the received multiple parameters to create a subscription context. In addition, the subscription controller is configured to generate the unique subscription identifier in response to receiving a SIP message for creating a SIP subscription for location information, and start a subscription expiration timer. In addition, the subscription controller is configured to create a custom subscription for custom information based on the subscription context from the received SIP message, and assign a unique subscription identifier to the created custom subscription, and the SIP message includes a create location event subscription response message.

[0040] Therefore, embodiments herein provide a client SIP node for providing a general framework for managing SIP custom subscriptions. The client SIP 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 a value for an expiration time, wherein before the expiration time, the client SIP node wants to receive the current state of the subscription and later notifications. The subscription controller is configured to set a value for the time interval, which is the time period between two consecutive notifications indicated by the client SIP node. The subscription controller is configured to set a value for the total number of users for which the client SIP node requires location information. The subscription controller is configured to add a user ID for each user and an integer uniquely representing the user in a user ID list.

[0041] According to one aspect of the present disclosure, an embodiment of the present invention provides a method for managing a custom subscription by a server SIP node through a Session Initiation Protocol (SIP), the method comprising: receiving a first SIP message from a client SIP node to request creation of a SIP custom subscription for custom information, wherein the first SIP message comprises at least one parameter for the custom subscription; in response to receiving the first SIP message, sending a response message to the client SIP node; storing the received at least one parameter; generating a unique subscription identifier for identifying the custom subscription; and sending a second SIP message comprising the unique subscription identifier to the client SIP node.

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

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

[0044] In one embodiment, the method further comprises: if the server SIP node cannot accept the value of the expiration time included in the first SIP message, reconfiguring the expiration time for the custom subscription; starting the subscription expiration timer and setting the expiration time of the subscription expiration time to the reconfigured value.

[0045] In one embodiment, the method further includes: receiving a third SIP message from the client SIP node, the third SIP message being used to request deletion of the SIP custom subscription to the custom information, wherein the third SIP message includes the unique subscription identifier and an expiration time, wherein the value of the expiration time is zero; in response to receiving the SIP message, sending a response message to the client SIP node; deleting at least one parameter stored associated with the custom subscription; sending a fourth SIP message to the client SIP node, terminating a subscription expiration timer and a notification interval timer, wherein the fourth SIP message includes the unique subscription identifier.

[0046] In one embodiment, the method further comprises: sending a fifth SIP message to the client SIP node to notify the custom information, wherein the SIP message includes the unique subscription identifier and the data to be notified.

[0047] In one embodiment, wherein the custom information is location information of a plurality of users, and the custom subscription is a subscription to the location information of the plurality of users, and wherein the at least one parameter comprises at least one of an expiration time, a time interval, a total number of users, a list of user identities (IDs) and a unique user number for each user, and a user identity (ID) associated with the client SIP node.

[0048] In one embodiment, the custom information is location information of multiple users, and the custom subscription is a subscription to the location information of multiple users, and the second SIP message further includes an expiration time, a total number of users, and at least one of a user ID list and a unique user number for each user.

[0049] According to one aspect of the present disclosure, an embodiment of the present invention provides a server session initiation protocol (SIP) node for managing SIP custom subscriptions, the server SIP node comprising: a memory; a processor; and a subscription controller operably connected to the memory and the processor, the subscription controller being configured to: receive a first SIP message from a client SIP node to request creation of a SIP custom subscription for custom information, wherein the first SIP message comprises at least one parameter for 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 the second SIP message comprising the unique subscription identifier to the client SIP node.

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

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

[0052] In one embodiment, the subscription controller is further configured to: reconfigure the expiration time for the custom subscription if the server SIP node cannot accept the value of the expiration time included in the first SIP message; start the subscription expiration timer and set the expiration time of the subscription expiration time to the reconfigured value.

[0053] In one embodiment, the subscription controller is further configured to: receive a third SIP message from the client SIP node to request deletion of the SIP custom subscription to the custom information, wherein the third SIP message includes the unique subscription identifier and an expiration time, wherein the value of the expiration time is zero; in response to receiving the SIP message, send a response message to the client SIP node; delete at least one parameter stored associated with the custom subscription; send a fourth SIP message to the client SIP node, the SIP message terminates the subscription expiration timer and the notification interval timer, and the fourth SIP message includes the unique subscription identifier.

[0054] 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, wherein the fifth SIP message includes the unique subscription identifier and the data to be notified.

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

[0056] In one embodiment, the subscription controller is further configured to send a SIP message to the client SIP node to terminate the created SIP custom subscription to the custom information, wherein the SIP message includes a terminate custom subscription message, and the terminate custom subscription message includes a unique subscription identifier.

[0057] According to one aspect of the present disclosure, an embodiment of the present invention provides a client session initiation protocol (SIP) node for providing a framework for managing SIP custom subscriptions, wherein the client SIP node (100) includes: a memory (110); a processor (120); and a subscription controller (140), operably connected to the memory (110) and the processor (120), and configured to: send a SIP message to a server SIP node to perform one of creating, modifying, and deleting a SIP subscription to custom information, wherein the SIP message includes one of a create custom subscription request message, a modify custom subscription request message, and a delete custom subscription request message, wherein each message includes multiple parameters; configure the value of the expiration time, before which the client SIP node wants to receive the current status of the subscription and the time of subsequent notifications; configure the value of the time interval, wherein the time interval is the time period between two consecutive notifications; and configure other required parameters according to the subscription data type.

[0058] In one embodiment, the plurality of parameters include expiration time, time interval, and other subscription related parameters.

[0059] In one embodiment, the subscription controller is further configured to receive a SIP message from the server SIP node (200) to perform one of the following: notify and terminate a custom subscription to custom information, wherein the SIP message includes one of a custom subscription notification message and a terminate custom subscription message.

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

[0061] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including without limitation; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included, interconnected with, containing, contained within, connected or connected to, coupled or connected to, communicating with, cooperating with, intertwined, juxtaposed, proximate, bound to, having, having the property of, and the like. The term "controller" refers to any device, system, or portion thereof that controls at least one operation, which device may be implemented in hardware, firmware, or software, or some combination of at least two of them. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0062] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and included in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-temporary" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-temporary computer-readable media include media in which data can be permanently stored and media in which data can be stored and subsequently rewritten, such as rewritable optical disks or erasable memory devices.

[0063] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0064] Advantageous Effects of the Invention

[0065] The present disclosure provides a general framework for managing custom subscriptions, which sends at least one request with multiple parameters to a server for any type of data through SIP, regardless of whether an event package is available. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0067] Figure 1 is a sequence diagram showing an existing SIP-based subscription mechanism;

[0068] Figure 2A A block diagram of a client SIP node for managing SIP custom subscriptions according to embodiments disclosed herein is shown;

[0069] Figure 2B A block diagram of a server SIP node entity for managing SIP custom subscriptions according to an embodiment disclosed herein is shown;

[0070] Figure 2CA and 2CB Various message formats for managing multiple parameters of a SIP custom subscription according to embodiments disclosed herein are shown;

[0071] Figure 3A is a sequence diagram illustrating various operations for creating a SIP custom subscription according to an embodiment disclosed herein;

[0072] Figure 3B is a sequence diagram illustrating various operations for creating a SIP custom subscription for location information according to embodiments disclosed herein;

[0073] Figure 4A is a sequence diagram illustrating various operations for modifying a SIP custom subscription according to an embodiment disclosed herein;

[0074] Figure 4B is a sequence diagram illustrating various operations for modifying a SIP custom subscription to location information according to embodiments disclosed herein;

[0075] Figure 5A is a sequence diagram illustrating various operations for deleting a SIP custom subscription according to an embodiment disclosed herein;

[0076] Figure 5B is a sequence diagram illustrating various operations for deleting a SIP custom subscription to location information according to an embodiment disclosed herein;

[0077] Fig. 6A is a sequence diagram illustrating various operations for sending notifications of SIP custom subscriptions according to embodiments disclosed herein;

[0078] Figure 6B is a sequence diagram illustrating various operations for sending a notification of a SIP custom subscription for location information according to an embodiment disclosed herein;

[0079] Fig. 7A is a sequence diagram illustrating various operations for terminating a SIP custom subscription according to embodiments disclosed herein; and

[0080] Figure 7B is a sequence diagram illustrating various operations for terminating a SIP custom subscription for location information according to embodiments disclosed herein. DETAILED DESCRIPTION

[0081] Discussed below Figures 1 to 7B , and the various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be construed as limiting the scope of the present disclosure in any way. Those skilled in the art will appreciate that the principles of the present invention can be implemented in any suitably arranged system or device.

[0082] The embodiments herein and their various features and advantageous details will be explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted so as not to unnecessarily obscure the embodiments herein. In addition, the various embodiments described herein do not have to be mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" used herein refers to a non-exclusive or. The examples used herein are intended only to help understand the ways in which the embodiments herein can be practiced, and further enable those skilled in the art to practice the embodiments herein. Therefore, the embodiments should not be interpreted as limiting the scope of the embodiments herein.

[0083] As is conventional in the art, embodiments may be described and illustrated in terms of blocks that perform one or more functions described. These blocks may be referred to herein as managers, units, modules, hardware components, etc., which are 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, hard-wired circuits, etc., and may be optionally driven by firmware. For example, the circuit may be embodied in one or more semiconductor chips, or 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 to perform some functions of the blocks, and by a processor to perform other functions of the blocks. Without departing from the scope of the present disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of the embodiment may be physically combined into more complex blocks.

[0084] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented here are not limited by the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and substitutions in addition to those specifically set forth in the accompanying drawings. Although the terms "first", "second", etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0085] 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 interchangeably and have the same meaning.

[0086] Therefore, the embodiments herein disclose a method for providing a general framework for managing SIP custom subscriptions. The method includes receiving a SIP message from a client SIP node by a server SIP node to create a SIP custom subscription to custom information, wherein the SIP message includes a create custom subscription request message, wherein the create custom subscription request message includes multiple parameters. In addition, the method includes sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method includes generating a unique subscription identifier by the server SIP node in response to receiving a SIP message for creating a SIP subscription to custom information, and starting a subscription expiration timer. In addition, the method includes creating a custom subscription for custom information by the server SIP node based on a subscription context from a received SIP message, and assigning a unique subscription identifier to the created custom subscription, wherein the SIP message includes a create custom subscription response message.

[0087] Therefore, the embodiments herein disclose a method for providing a general framework for managing SIP custom subscriptions. The method includes receiving a SIP message from a client SIP node by a server SIP node to create a SIP subscription for location information of multiple users, the SIP message including a create location event subscription request message, the create location event subscription request message including multiple parameters. In addition, the method includes sending a response message to the client SIP node by the server SIP node in response to receiving the SIP message. In addition, the method includes storing the received multiple parameters by the server SIP node to create a subscription context. In addition, the method includes generating a unique subscription identifier by the server SIP node in response to receiving a SIP message for creating a SIP subscription for location information, and starting a subscription expiration timer. In addition, the method includes creating a custom subscription for location information of multiple users based on the subscription context from the received SIP message by the server SIP node by sending a SIP message to the client SIP node, and assigning a unique subscription identifier to the created custom subscription, the SIP message including a create location event subscription response message.

[0088] Therefore, the embodiments herein provide a server SIP node for providing a general framework for managing SIP custom subscriptions. The server SIP includes a subscription controller connected to a processor and a memory. The subscription controller is configured to receive a SIP message from a client SIP node to create a SIP custom subscription to custom information. In addition, the subscription controller is configured to send a response message to the client SIP node in response to receiving the SIP message. In addition, the subscription controller is configured to store the received multiple parameters to create a subscription context. In addition, the subscription controller is configured to generate a unique subscription identifier in response to receiving a SIP message for creating a SIP subscription to custom information, and start a subscription expiration timer. In addition, the subscription controller is configured to create a SIP custom subscription to custom information based on the subscription context from the received SIP message, and assign a unique subscription identifier to the created custom subscription, and the SIP message includes a create location event subscription response message.

[0089] Therefore, embodiments herein provide a client SIP node for providing a general framework for managing SIP custom subscriptions. The client SIP 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 a value for an expiration time before which the client SIP node wants to receive the current state of the subscription and later notifications. The subscription controller is configured to set a value for a time interval, which is the time period between two consecutive notifications indicated by the client SIP node. The subscription controller is configured to set a value for the total number of users for which the client SIP node requests custom information. The subscription controller is configured to add a user ID for each user and an integer uniquely representing the user in a user ID list.

[0090] Unlike existing methods and systems, the provided method and SIP node provide a general framework to manage custom subscriptions by sending at least one request with multiple parameters to a server SIP node via SIP for any type of data, regardless of whether an event package is available or not in the at least one request.

[0091] Unlike existing methods and systems, the provided method and SIP node provide customized subscription to location management services associated with SLM-S via SIP, regardless of whether event packages are available or unavailable in at least one request received from a VAL server. SLM-S allows the VAL server to manage location information of VAL users using multiple parameters.

[0092] Different from the existing methods and systems, for any type of data, the provided client SIP node sends at least one request with multiple parameters to the server SIP node via SIP to manage custom subscriptions, regardless of whether an event package is available. The custom subscription is managed by using one of the multiple parameters to create a custom subscription, modify a custom subscription, delete a custom subscription, notify a custom subscription, and terminate a custom subscription. Therefore, the provided client SIP node does not require an event package in a SIP message to subscribe to various services associated with the server SIP node.

[0093] Referring now to the drawings, and more particularly to Figures 2A to 7B Preferred embodiments are shown, wherein like reference numerals denote corresponding features consistently throughout the drawings.

[0094] Figure 2A A block diagram of a client SIP node (100) for managing SIP custom subscriptions according to the embodiments disclosed herein is shown. The client SIP node (100) may be, for example but not limited to, a user equipment (UE), a VAL server.

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

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

[0097] The processor (120) communicates 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, which may be general-purpose processors such as a central processing unit (CPU), an application processor (AP), etc., a graphics processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

[0098] The communicator (130) is configured to communicate with external devices (e.g., server SIP node (200)) via one or more networks (e.g., Internet, Wi-Fi, Bluetooth, etc.) and to communicate internally between internal hardware components. The communicator (130) includes electronic circuits dedicated to implementing standards for wired or wireless communication.

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

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

[0101] The SIP message includes one of creating a custom subscription request message, modifying a custom subscription request message, deleting a custom subscription request message, a custom subscription notification message, and terminating a custom subscription message. Each message includes multiple parameters (e.g., expiration time, time interval, total number of users, user identity (ID) list and unique user number of each user, and user identity (ID)).

[0102] The custom subscription request message includes an expiration time, a time interval, a total number of users, a user ID list, and a user ID. The modify custom subscription request message includes a unique subscription identifier and multiple updated parameters. The delete custom subscription request message includes a unique subscription identifier and an expiration time, wherein the value of the expiration time is zero. The custom subscription notification message includes a unique subscription identifier and custom data to be notified. The terminate custom subscription message includes a unique subscription identifier.

[0103] In one embodiment, the subscription controller (140) is configured to set a value for an expiration time before which the client SIP node (100) wants to receive current status and later notifications of the subscription. Furthermore, the subscription controller (140) is configured to set a value for a time interval, wherein a time interval is a period of time between two consecutive notifications indicated by the client SIP node (100). Furthermore, the subscription controller (140) is configured to set a value for 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 uniquely representing the user in a user ID list.

[0104] although Figure 2AVarious hardware components of the client SIP node (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the client SIP node (100) may include fewer or greater numbers of components. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions, thereby providing a general framework for managing SIP custom subscriptions.

[0105] Figure 2B A block diagram of a server SIP node (200) for managing SIP custom subscriptions according to embodiments disclosed herein is shown.

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

[0107] 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 may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (210) may be considered a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not contained in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (210) being non-removable. In some instances, the non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache memory). The memory (210) may be an internal storage unit, or may be an external storage unit of the client SIP node (200), a cloud storage, or any other type of external storage.

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

[0109] The communicator (230) is configured to communicate with external devices (e.g., client SIP node (100)) via one or more networks (e.g., Internet, Wi-Fi, Bluetooth, etc.) and internally between internal hardware components. The communicator (230) includes electronic circuitry dedicated to standards that allow wired or wireless communication.

[0110] The subscription controller (240) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware. For example, the circuitry may be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board.

[0111] In one embodiment, a subscription controller (240) is configured to receive a SIP message from a client SIP node (100) to create a SIP custom subscription for custom information, wherein the SIP message includes a create custom subscription request message, wherein the create custom subscription request message includes a plurality of parameters. In addition, the subscription controller (240) is configured to send a response message to the client SIP node (100) in response to receiving the SIP message. In addition, the subscription controller (240) is configured to store the received plurality of parameters to create a subscription context. In addition, the subscription controller (240) is configured to generate a unique subscription identifier in response to receiving a SIP message for creating a SIP subscription for custom information, and to start a subscription expiration timer. In addition, the subscription controller (240) is configured to assign the unique subscription identifier to the SIP message received from the client SIP node (100). In addition, the subscription controller (240) is configured to create a SIP subscription for custom information of a plurality of users based on the subscription context by sending a SIP message to the client SIP node (100), wherein the SIP message includes a create custom subscription response message. Create a custom subscription response message that includes an expiration date and a unique subscription identifier.

[0112] In addition, the subscription controller (240) is configured to change the expiration time, wherein when the server SIP node (200) cannot accept the value of the expiration time present in the received SIP message, the server SIP node (200) changes the value of the expiration time to a value different from the value present in the received SIP message. In addition, the subscription controller (240) is configured to change the total number of users for which the client SIP node (100) requests location information. In addition, the subscription controller (240) is configured to add a user ID for each user from the reconfigured total number of users. In addition, 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).

[0113] In addition, the subscription controller (240) is configured to receive a SIP message from the client SIP node (100) to modify the created SIP custom subscription for custom information of multiple users, wherein the SIP message includes a modify custom subscription request message, wherein the modify custom subscription request message includes a unique subscription identifier and updated multiple parameters. In addition, the subscription controller (240) is configured to update multiple parameters based on the updated multiple parameters and restart the expiration timer. In addition, the subscription controller (240) is configured to modify the created SIP custom subscription for custom information of multiple users based on the SIP message received from the client SIP node (100), and send a SIP message to the client SIP node (100), wherein the SIP message includes a modify custom subscription response message. The modify custom subscription response message includes the updated expiration time and the unique subscription identifier.

[0114] In addition, the subscription controller (240) is configured to receive a SIP message from the client SIP node (100) to delete the created SIP custom subscription for the custom information of the plurality of users, wherein the SIP message includes a delete custom subscription request message, wherein the delete custom subscription request message includes a unique subscription identifier and an expiration time, wherein the value of the expiration time is zero. In addition, the subscription controller (240) is configured to delete the stored SIP custom subscription for the location information of the plurality of users and a plurality of parameters associated with the SIP message received from the client SIP node (100). In addition, the subscription controller (240) is configured to send a SIP message to the client SIP node (100), wherein the SIP message includes a delete custom subscription response message and terminates the expiration time and the time interval.

[0115] In addition, the subscription controller (240) is configured to notify the client SIP node (100) of a SIP message to notify the customized information of multiple users, wherein the SIP message includes a customized subscription notification message, wherein the customized subscription notification message includes a unique subscription identifier and customized data to be notified. When the client SIP node (100) receives the SIP message from the server SIP node (200), the client SIP node (100) stores the customized data and shares the customized data with at least one user.

[0116] In addition, the subscription controller (240) is configured to send a SIP message to the client SIP node (100) to terminate the created SIP custom subscription for the custom information of the plurality of users, wherein the SIP message includes a terminate custom subscription message, wherein the terminate custom subscription message includes the 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, terminates the subscription expiration timer and the notification interval timer.

[0117] although Figure 2B Various hardware components of the server SIP node (200) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the server SIP node (200) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions, thereby providing a general framework for managing SIP custom subscriptions.

[0118] Figure 2CA and 2CB Various message formats for managing multiple parameters of a SIP custom subscription according to embodiments disclosed herein are shown.

[0119] The least significant bit of a field is represented by the lowest bit in the highest byte of the field. When a field extends beyond one byte, the order of the bit value decreases as the byte number 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 with a length of 1 byte.

[0120] In one embodiment, the Expiration Time information element (202) is used to indicate the duration in seconds until the subscription remains active / the Expiration Time value is an unsigned integer that specifies the duration in seconds that the subscription remains active. The Expiration Time information element is a Type 3 information element with a length of 3 bytes.

[0121] In one embodiment, the time interval information element (203) provides the time (in seconds) between two consecutive notifications from the server SIP node (200) / the expiration time value is an unsigned integer in seconds specifying the duration between two consecutive notifications. The time interval information element is a type 3 information element with a length of 2 bytes.

[0122] 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 with a length of 4 bytes. The subscription identifier contains a number that uniquely identifies the subscription request of the VAL server (100), which may have performed multiple subscriptions.

[0123] In one embodiment, the Number of Users information element (205) identifies the number of users contained in the message. The Number of Users information element is a type 3 information element with a length of 2 bytes. The Number of Users contains a value from 1 to 255. If the IE is used as an optional information element, the value of the Number of Users is contained in byte 2. If used as a mandatory information element, the Number of Users information element is omitted and the value of the Number of Users is contained in byte 1.

[0124] In one embodiment, the VAL User ID is indicated using a User Identity Information Element (206). The User Identity Information Element is a Type 6 Information Element.

[0125] In one embodiment, the VAL User Number (207) contains a unique number assigned to each VAL User ID content. The SLM-S (200) uses this number to send location information for the assigned VAL User ID. The VAL User Number starts at 1 and increases by 1 for each User Identity IE. If the IE is used as an optional IE, the VAL User Number value is contained in byte 4. If used as a mandatory IE, the User Identity IEI is omitted and the VAL User Number value is contained in byte 3. The VAL User ID is contained in bytes 4 to byte n, up to 65535 bytes. If the IE is used as an optional IE, the VAL User ID value is contained in bytes 5 to byte n. If used as a mandatory IE, the User Identity IEI is omitted and the VAL User ID value is contained in bytes 4 to byte n.

[0126] In one embodiment, the user location data information element (208) is used to indicate the current location of the VAL user. The user location data information element is a type 6 information element. The VAL user number contains the unique number specified in the location event subscription request message. The user location is contained in bytes 5 to byte n, up to 65535 bytes.

[0127] In one embodiment, the following process provides the behavior on the server (200) side when different timers expire:

[0128] When the TLM-1 (subscription expiration) timer expires, the SLM-S (200) considers the subscription terminated and deletes all data related to the subscription; and

[0129] When the TLM-2 (Notification Interval) timer expires, the SLM-S (200) checks if there is any notification to be sent. In case there is any pending notification, the SLM-S (200) sends the notification.

[0130] The following subclauses describe the location management message functional definitions and contents. Each message consists of a series of information elements.

[0131] In one embodiment, create location event subscription 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. Table 1 describes the message content.

[0132] [Table 1]

[0133] Information Elements Type / Reference state Format length Create location event subscription request message identifier Message Type (201) M V 1 Expiration time IE Expiration time type (202) M V 3 Time interval type IE Time interval type (203) M V 2 Number of usersIE Number of users (205) M V 1 User Identity IE User identity type (206) M LV-E 4-x

[0134] The SLM-S (200) may decide to support creating, modifying, and deleting subscriptions using only a single request message. In this case, an optional Subscription Identifier IE is added in Table 1. When the VAL server (100) requests to modify or delete a subscription, the VAL server (100) includes the Subscription Identifier IE value. In one embodiment, the information elements specified in Table 1 may be sent via any data format (e.g., XML).

[0135] In one embodiment, Create Location Event Subscription Response Message (201): This message is sent by the SLM-S server (200) to the VAL server (100) as a response to the Create Location Event Subscription Request message. Table 2 describes the message content.

[0136] [Table 2]

[0137]

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

[0139] In one embodiment, the Modify Location Event Subscription Request Message (201) is sent by the VAL server (100) to the SLM-S (200) to request the SLM-S (200) to modify the subscription to the location information of the VAL user specified in the request message. Table 3 describes the message content.

[0140] [Table 3]

[0141]

[0142]

[0143] In one embodiment, the information elements specified in Table 3 may be sent via any data format (eg, XML). In one embodiment, an integer may be used as an information element identification value.

[0144] In one embodiment, the Modify Location Event Subscription 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 Subscription Request Message. Table 4 describes the message content.

[0145] [Table 4]

[0146]

[0147] In one embodiment, the information elements specified in Table 4 may be sent via any data format (eg, XML). In one embodiment, an integer may be used as an information element identification value.

[0148] In one embodiment, the location event subscription deletion request message (201) is sent by the VAL server (100) to the SLM-S (200) to request the SLM-S (200) to delete the subscription to the location information of the VAL user specified in the request message. Table 5 describes the message content.

[0149] [Table 5]

[0150]

[0151]

[0152] In one embodiment, the information elements specified in Table 5 may be sent via any data format.

[0153] In one embodiment, Delete Location Event Subscription Response Message (201): This message is sent by the SLM-S server (200) to the VAL server (100) as a response to the Delete Location Event Subscription Request Message. Table 6 describes the message content.

[0154] [Table 6]

[0155]

[0156] In one embodiment, the information elements specified in Table 6 may be sent via any data format.

[0157] In one embodiment, location event notification message (201): This message is sent by the SLM-S (200) to the VAL server (100) to notify the VAL server (100) of the location information of the VAL user specified in the request message. Table 7 describes the message content.

[0158] [Table 7]

[0159] Information Elements Type / Reference state Format length Location event notification message ID Message Type (201) M V 1 Subscription Identifier IE Subscription Identifier (204) M V 4 Number of usersIE Number of users (205) M V 1 User location data IE User Location Data Type(208) M LV 5-x

[0160] In one embodiment, the information elements specified in Table 7 may be sent via any data format.

[0161] In one embodiment, the Terminate Location Event Subscription Message (201): This message is sent by the SLM-S (200) to the VAL server (100) to notify the VAL server (100) of the termination of the subscription. Table 8 describes the message content.

[0162] [Table 8]

[0163]

[0164]

[0165] In one embodiment, the information elements as specified in Table 1 may be sent via any data format.

[0166] Figure 3A is a sequence diagram illustrating various operations for creating a SIP custom subscription according to embodiments disclosed herein.

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

[0168] Figure 3B is a sequence diagram illustrating various operations for creating a SIP custom subscription to location information according to embodiments disclosed herein.The VAL server acts as a client SIP node (100) while the SLM-S acts as a server SIP node (200).

[0169] At 302b, in order to subscribe to location information of one or more VAL users or VAL UEs, the VAL server (100):

[0170] Generate SIP message requests according to 3GPP TS 24.229 and IETF RFC 3428;

[0171] Set the request URI to the identity of SLM-S (200);

[0172] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0173] In the SIP message request, include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CB In the Create Location Event Subscription Request Message, the VAL server (100):

[0174] Set the Expiration Time IE to the expiration time indicated by the VAL server (100),

[0175] Set the time interval IE to the time period between two consecutive notifications indicated by the VAL server (100),

[0176] The Number of Users IE is set to the total number of VAL users for which the VAL server (100) requests location information,

[0177] Add a User Identity IE for each VAL user. In the User Identity IE:

[0178] Set the VAL user number to an integer that uniquely represents the VAL user in the list of users in the request being sent.

[0179] Set the VAL-user-ID content to the VAL-user-ID of the VAL-user; and

[0180] A SIP message request is sent to the SLM-S (200) according to 3GPP TS 24.229. In one embodiment, the SIP message request to the SLM-S (200) may include an expiration time, a time interval, a user number, a user identity of each user, and other required parameters (e.g., XML or any other data format).

[0181] At 304b to 306b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the create location event subscription request message, SLM-S (200):

[0182] Generate a SIP 200 (OK) response and send it to the VAL server (100);

[0183] Stores all user information contained in the User Identity IE and can change the VAL User Number associated with the VAL User ID;

[0184] storing the expiration time of the subscription as the Expiration Time IE value, and if the Expiration Time value present in the Expiration Time IE is unacceptable to the SLM-S (200), the SLM-S (200) may change the Expiration Time value to a value different from the requested value;

[0185] storing the time interval value as a time interval IE value; and

[0186] generating a unique integer and assigning it as a subscription identifier to a subscription request received from a VAL server (100);

[0187] At 308b, the SLM-S (200) generates a SIP message request according to 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S (200):

[0188] Set the request URI to the identity of the VAL server (100);

[0189] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0190] In the application / vnd.3gpp.location-event MIME body, include Figure 2CA and 2CB The specified create location event subscription response message. In the create location event subscription response message, SLM-S (200):

[0191] Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request,

[0192] Set the Expiration Time IE to the accepted Expiration Time value,

[0193] If for any of the VAL user IDs from the request message, the SLM-S (200) has changed to the associated VAL user number, then the Number of Users IE is set to the total number of VAL users;

[0194] Add a User Identity IE for each VAL user. In the User Identity IE:

[0195] Set VAL User Number to the number assigned to the VAL User ID, and

[0196] Set the VAL-user-ID content to the VAL-user-ID of the VAL-user; and

[0197] A SIP message request is sent to the VAL server (100) according to 3GPP TS 24.229, and a TLM-1 (subscription expiration) timer is started, and the expiration time of the timer is set to the expiration time of the subscription. In one embodiment, the SIP message request to the VAL server (100) may include a subscription identifier, an expiration time, a number of users, a user identity of each user, and other required parameters (e.g., XML or any other data format).

[0198] At 310b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the Create Location Event Subscription Response message, the VAL Server (100):

[0199] Store the subscription identifier IE value;

[0200] Start the TLM-3 (subscription refresh) timer and set the expiration time of the TLM-3 (subscription refresh) timer to 2 / 3 of the expiration time IE value; and

[0201] At TLM-3 (subscription refresh) expiration, based on the VAL user's request, the VAL server (100) may modify the subscription to set a new expiration value.

[0202] Figure 4A is a sequence diagram illustrating various operations for modifying a SIP custom subscription according to embodiments disclosed herein.

[0203] At 402a, the client SIP node (100) generates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a modified custom subscription request message, which contains at least a subscription identifier, an expiration time, a time interval between two consecutive notifications, and other subscription specific data. The client SIP node (100) sends a SIP message to the server SIP node (200). At 404a, the server SIP node (200) sends a SIP 200 (OK) response to the client SIP node (100). At 406a, the server SIP node (200) updates the subscription data and restarts the expiration timer. At 408a, the server SIP node (200) generates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a modified custom subscription response message, which contains at least a unique subscription identifier and an expiration time of the accepted subscription. The server SIP node (200) sends a SIP message to the client SIP node (100). At 410a, the client SIP node (100) sends a SIP 200 (OK) response to the server SIP node (200). The client SIP node (100) restarts the refresh timer.

[0204] Figure 4B is a sequence diagram illustrating various operations for modifying a SIP custom subscription for location information according to embodiments disclosed herein.

[0205] At 402b, in order to modify the subscription to the location information of one or more VAL users or VAL UEs, the VAL server (100):

[0206] Generate SIP message requests according to 3GPP TS 24.229 and IETF RFC 3428;

[0207] Set the request URI to the identity of SLM-S (200);

[0208] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0209] In the SIP message request, include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CBIn the request message for modifying the location event subscription, the VAL server (100):

[0210] Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription.

[0211] Set the Expiration Time IE to the expiration time indicated by the VAL server (100),

[0212] Set the time interval IE to the time period between two consecutive notifications indicated by the VAL server (100),

[0213] The Number of Users IE is set to the total number of VAL users for which the VAL server (100) requests location information,

[0214] Add a User Identity IE for each VAL user. In the User Identity IE:

[0215] Set the VAL user number to an integer that uniquely represents the VAL user in the list of users in the request being sent.

[0216] Set the VAL-user-ID content to the VAL-user-ID of the VAL-user; and

[0217] A SIP message request is sent to the SLM-S (200) according to 3GPP TS 24.229. In one embodiment, the SIP message request to the SLM-S (200) may include a subscription identifier, an expiration time, a timer interval, the number of users, a user identity of each user, and other required parameters (e.g., XML or any other data format).

[0218] At 404b-406b, upon receiving a SIP message having an application / vnd.3gpp.location-event MIME body containing a modify location event subscription request message, SLM-S (200):

[0219] Generate a SIP 200OK response and send it to the VAL server (100);

[0220] If available in the request message, store the information of all users contained in the User Identity IE and may change the VAL User Number associated with the VAL User ID; and

[0221] The expiration time of the subscription is stored as the Expiration Time IE value. If the Expiration Time value present in the Expiration Time IE is unacceptable to the SLM-S (200), the SLM-S (200) may change the Expiration Time value to a value different from the requested value.

[0222] At 408b, the SLM-S (200) generates a SIP message request according to 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S (200):

[0223] Set the request URI to the identity of the VAL server (100);

[0224] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0225] In the application / vnd.3gpp.location-event MIME body, include Figure 2CA and 2CB In the modify location event subscription response message, SLM-S (200):

[0226] Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request,

[0227] Set the Expiration Time IE to the accepted Expiration Time value,

[0228] If for any of the VAL user IDs from the request message, the SLM-S (200) has changed to the associated VAL user number, then the Number of Users IE is set to the total number of VAL users;

[0229] Add a User Identity IE for each VAL user. In the User Identity IE:

[0230] Set VAL User Number to the number assigned to the VAL User ID, and

[0231] Set the VAL user ID content to the VAL user ID of the VAL user;

[0232] Sending a SIP message request to the VAL server (100) according to 3GPP TS 24.229, starting a TLM-1 (subscription expiration) timer, and setting the expiration time of the timer to the expiration time of the subscription; and

[0233] Restart the TLM-1 (subscription expiration) timer and set the expiration time of the timer to the expiration time of the subscription. In one embodiment, the SIP message request to the VAL server (100) may include a subscription identifier, an expiration time, the number of users, a user identity of each user, and other required parameters (e.g., XML or any other data format).

[0234] At 410b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the Modify Location Event Subscription Response message, the VAL Server (100):

[0235] Storing the subscription identifier IE value; and

[0236] Start the TLM-3 (Subscription Refresh) timer and set the expiration time of the TLM-3 (Subscription Refresh) timer to 2 / 3 of the Expiration Time IE value.

[0237] Figure 5A is a sequence diagram illustrating various operations for deleting a SIP custom subscription according to embodiments disclosed herein.

[0238] At 502a, the client SIP node (100) generates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a delete custom subscription request message, which includes at least a subscription identifier and an expiration time value set to a value of 0. The client SIP node (100) sends the SIP message to the server SIP node (200). At 504a, the server SIP node (200) sends a SIP 200 (OK) response to 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) generates a SIP message according to 3GPP TS 24.229 and IETF RFC 3428. The SIP message includes a delete custom subscription response message including at least a unique subscription identifier. The server SIP node (200) sends the SIP message to the client SIP node (100). At 510a, the client SIP node (100) sends a SIP 200 (OK) response to the server SIP node (200).

[0239] Figure 5B is a sequence diagram illustrating various operations for deleting a customized subscription to location information according to embodiments disclosed herein.

[0240] At 502b, in order to delete the subscription to the location information of one or more VAL users or VAL UEs, the VAL server (100):

[0241] Generate SIP message requests according to 3GPP TS 24.229 and IETF RFC 3428;

[0242] Set the request URI to the identity of SLM-S (200);

[0243] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0244] In the SIP message request, include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CB In the request message for deleting location event subscription, the VAL server (100):

[0245] Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription.

[0246] Setting the Expiration Time IE to a value of 0; and

[0247] The SIP message request is sent to the SLM-S (200) according to 3GPP TS 24.229. In one embodiment, the SIP message request to the SLM-S (200) may include a subscription identifier, an expiration time and other required parameters (eg, XML or any other data format).

[0248] At 504b-506b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the delete location event subscription request message, SLM-S (200):

[0249] Generate a SIP 200OK response and send it to the VAL server (100); and

[0250] Delete all information related to the subscription.

[0251] At 508b, the SLM-S (200) generates a SIP message request according to 3GPP TS 24.229 and IETF RFC 3428. In the SIP message, the SLM-S (200):

[0252] Set the request URI to the identity of the VAL server (100);

[0253] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0254] Include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CB In the delete location event subscription response message, SLM-S (200):

[0255] Set the Subscription Identifier IE to the unique subscription identifier assigned to the subscription request,

[0256] Sending a SIP message request to the VAL server (100) according to 3GPP TS 24.229;

[0257] If the TLM-1 (Subscription Expiry) timer is running, stop the timer; and

[0258] If the TLM-2 (Notification Interval) timer is running, stop the timer.In one embodiment, the SIP message request to the VAL server (100) may include a subscription identifier and other required parameters (eg, XML or any other data format).

[0259] At 510b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the delete location event subscription response message, the VAL server (100):

[0260] Deleting subscription-related data; and

[0261] Stops the TLM-3 (subscription refresh) timer.

[0262] Fig. 6A is a sequence diagram illustrating various operations for sending notifications of SIP custom subscriptions according to embodiments disclosed herein.

[0263] At 602a-604a, if the notification interval timer is not running, the server SIP node (200) generates a SIP message according to 3GPPTS 24.229 and IETF RFC 3428. The SIP message includes a notification including at least a subscription identifier and notification data. The server SIP node (200) sends the SIP message to the client SIP node (100). At 606a, the client SIP node (100) sends a SIP 200 (OK) response to the server SIP node (200). The client SIP node (100) stores the data received in the notification and may present it to the user or further share it with other users. The server SIP node (200) starts the notification interval timer.

[0264] Figure 6B is a sequence diagram illustrating various operations for sending notifications of a custom SIP-defined subscription for location information according to embodiments disclosed herein.

[0265] In 602b-604b, in order to notify the VAL server (100) of the location information report, the SLM-S (200):

[0266] If the TLM-2 (Notification Interval) timer is running, the remaining steps can be skipped;

[0267] Generate SIP message requests according to 3GPP TS 24.229 and IETF RFC 6086;

[0268] Set the request URI to the identity of the VAL server (100);

[0269] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0270] In the SIP message request, include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CB The location event notification message specified in; in the location event notification message, SLM-S (200):

[0271] Set the Subscription Identifier IE to a subscription identifier value that uniquely identifies the subscription,

[0272] Set the Number of Users IE to the total number of VAL users for which location information is included in the message

[0273] For each VAL user, a user location data IE including a VAL user number and location information data associated with the VAL user ID;

[0274] Sending a SIP message request to the VAL server (100) according to 3GPP TS 24.229;

[0275] A TLM-2 (Notification Interval) timer is started and the expiration time of the timer is set to the time interval value. In one embodiment, the SIP message request to the VAL server (100) may include a subscription identifier, the number of users, location data for each user, and other required parameters (e.g., XML or any other data format).

[0276] At 606b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the location event notification message, the VAL server (100):

[0277] storing the received location information; and

[0278] This information may be shared with a group or another VAL user or VAL UE.

[0279] Fig. 7A is a sequence diagram illustrating various operations for terminating a SIP custom subscription according to embodiments disclosed herein.

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

[0281] Figure 7B is a sequence diagram illustrating various operations for terminating a SIP custom subscription for location information according to embodiments disclosed herein.

[0282] In 702b-704b, in order to notify the VAL server (100) of the termination of the subscription, the SLM-S (200):

[0283] Generate SIP message requests according to 3GPP TS 24.229 and IETF RFC 6086;

[0284] Set the request URI to the identity of the VAL server (100);

[0285] According to IETF RFC 3841, including the 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" and with the parameters "request" and "explicit";

[0286] In the SIP message request, include the following in the application / vnd.3gpp.location-event MIME body: Figure 2CA and 2CB The termination location event subscription message specified in the termination location event subscription message; in the termination location event subscription message, SLM-S (200):

[0287] Set the subscription ID IE to a subscription ID value that uniquely identifies the subscription;

[0288] A SIP message request is sent to the VAL server (100) according to 3GPP TS 24.229. In one embodiment, the SIP message request to the VAL server (100) may include a subscription identifier and other required parameters (eg, XML or any other data format).

[0289] At 706b, upon receiving the SIP message with the application / vnd.3gpp.location-event MIME body containing the terminating location event subscription message, the VAL server (100):

[0290] Deleting subscription-related data; and

[0291] Stops the TLM-3 (subscription refresh) timer.

[0292] The embodiments disclosed herein may be implemented using at least one hardware device and perform network management functions to control elements.

[0293] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method of an enabler architecture layer SEAL location management server SLM-S, the method being used to manage subscriptions via a session initiation protocol SIP, the method comprising: receiving a first SIP message from a vertical application layer VAL server, wherein the first SIP message is used to request to create the subscription to subscribe to location information through the SIP; In response to receiving the first SIP message, sending a response message to the VAL server; Generate subscription identifier ID information, the subscription ID specifies a unique subscription ID for identifying the subscription; sending a second SIP message including the subscription ID information to the VAL server, and The first SIP message includes expiration time information specifying the expiration time of the subscription and time interval information specifying the time between two consecutive notifications for the subscription, the expiration time information is associated with the subscription expiration timer of the SLM-S, and the time interval information is associated with the notification interval timer of the SLM-S.

2. The method of claim 1, wherein: The first SIP message further includes user ID information, where the user ID information includes an ID of at least one VAL user for whom the location information is requested.

3. The method of claim 1, wherein: The second SIP message also includes information specifying an accepted expiration time.

4. The method of claim 1, further comprising: reconfiguring the expiration time of the subscription in case the SLM-S cannot accept the value of the expiration time information included in the first SIP message; as well as The subscription expiration timer is started, and the expiration time of the subscription expiration timer is set to the value of the reconfigured expiration time.

5. The method of claim 1, further comprising: receiving, from the VAL server, a third SIP message for requesting deletion of the subscription through the SIP, wherein the third SIP message includes the subscription ID 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; and A fourth SIP message is sent to the VAL server, and a subscription expiration timer and a notification interval timer are disabled, wherein the fourth SIP message includes the subscription ID information.

6. The method of claim 1, further comprising: A fifth SIP message is sent to the VAL server to notify the location information, wherein the fifth SIP message includes the subscription ID information and data to be notified.

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

8. An enabler architecture layer SEAL location management server SLM-S, the SLM-S is used to manage subscriptions through the session initiation protocol SIP, the SLM-S comprises: Transceiver; a processor connected to the transceiver, the processor being configured to: receiving a first SIP message from a vertical application layer VAL server, wherein the first SIP message is used to request to create the subscription to subscribe to location information through the SIP; In response to receiving the first SIP message, sending a response message to the VAL server; Generate subscription identifier ID information, the subscription ID information specifying a unique subscription ID for identifying the subscription; as well as sending a second SIP message including the subscription ID information to the VAL server, and The first SIP message includes expiration time information specifying the expiration time of the subscription and time interval information specifying the time between two consecutive notifications for the subscription, the expiration time information is associated with the subscription expiration timer of the SLM-S, and the time interval information is associated with the notification interval timer of the SLM-S.

9. The SLM-S according to claim 8, wherein: The first SIP message further includes user ID information, where the user ID information includes an ID of at least one VAL user for whom the location information is requested.

10. The SLM-S according to claim 8, wherein: The second SIP message also includes information specifying an accepted expiration time.

11. The SLM-S according to claim 8, wherein: The processor is further configured to: reconfiguring the expiration time of the subscription in case the SLM-S cannot accept the value of the expiration time information included in the first SIP message; as well as The subscription expiration timer is started, and the expiration time of the subscription expiration timer is set to the value of the reconfigured expiration time.

12. The SLM-S according to claim 8, wherein: The processor is further configured to: receiving, from the VAL server, a third SIP message for requesting deletion of the subscription through the SIP for specific information, wherein the third SIP message includes the subscription ID 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; and A fourth SIP message is sent to the VAL server, and a subscription expiration timer and a notification interval timer are disabled, wherein the fourth SIP message includes the subscription ID information.

13. The SLM-S of claim 8, wherein: The processor is further configured to: A fifth SIP message is sent to the VAL server to notify the location information, wherein the fifth SIP message includes the subscription ID information and data to be notified.

14. The SLM-S according to claim 13, wherein: The VAL server stores the data in the fifth SIP message and shares the data with at least one VAL user.

15. A vertical application layer (VAL) server for managing subscriptions via a session initiation protocol (SIP), the VAL server comprising: Transceiver; a processor connected to the transceiver, the processor being configured to: Sending a first SIP message to a SEAL location management server SLM-S, wherein the first SIP message is used to request to create the subscription to subscribe to location information through the SIP; receiving, from the SLM-S, a response message in response to the first SIP message; as well as receiving a second SIP message from the SLM-S, the second SIP message including subscription ID information specifying a unique subscription identifier ID for identifying the subscription, and The first SIP message includes expiration time information specifying the expiration time of the subscription and time interval information specifying the time between two consecutive notifications for the subscription, the expiration time information is associated with the subscription expiration timer of the SLM-S, and the time interval information is associated with the notification interval timer of the SLM-S.

Images