Sign In to Follow Application
View All Documents & Correspondence

“Method Of Handling Multiple Pdn/Pdp Disconnection Requests On The Same Apn”

Abstract: ABSTRACT The various embodiments herein disclose a method of handling multiple packet data network (PDN)/ packet data protocol (PDP) disconnection requests on the same access point name (APN). According to an embodiment of the present invention, a method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment having multiple connections with a single Access Point Name (APN), comprising steps of receiving, by a network, signaling message from the UE user to disconnect all PDN/ PDP connections for the APN; where the signaling request includes an information element (IE), checking whether the IE is set in the signaling message, and disconnecting, by the network, one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections. Figure 5

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
07 May 2015
Publication Number
47/2016
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
ip.bangalore@foxmandal.com
Parent Application
Patent Number
Legal Status
Grant Date
2022-09-06
Renewal Date

Applicants

SAMSUNG R&D INSTITUTE INDIA – BANGALORE PRIVATE LIMITED
# 2870, ORION Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanakundi Circle, Marathahalli Post, Bangalore -560037, Karnataka, India

Inventors

1. GIRI, Sailesh Kumar
Employed at Samsung R&D Institute India – Bangalore Private Limited, having its office at, # 2870, ORION Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanakundi Circle, Marathahalli Post, Bangalore -560037, Karnataka, India
2. ii) SIVAPURAM, Jaya Prakash
Employed at Samsung R&D Institute India – Bangalore Private Limited, having its office at, # 2870, ORION Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanakundi Circle, Marathahalli Post, Bangalore -560037, Karnataka, India
3. KAURA, Ricky
Communications House, South Street, Staines-upon-Thames, Surrey, TW18 4QE, UK., Staines-Upon-Thames, GBR

Specification

DESC:FORM 2
THE PATENTS ACT, 1970
[39 of 1970]
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(Section 10; Rule 13)

METHOD OF HANDLING MULTIPLE PDN/PDP DISCONNECTION REQUESTS ON THE SAME APN

SAMSUNG R&D INSTITUTE INDIA – BANGALORE PRIVATE LIMITED,
#2870, Orion Building, Bagmane Constellation Business Park,
Outer Ring Road, Doddanekundi Circle,
Marathahalli Post, Bangalore – 560037,
Karnataka, India,
an Indian Company

The following Specification particularly describes the invention and the manner in which it is to be performed

RELATED APPLICATION

The present invention claims benefit of the Indian Provisional Application No. 2334/CHE/2015 titled "METHOD OF HANDLING MULTIPLE PDN/PDP DISCONNECTION REQUESTS ON THE SAME APN” by Samsung R&D Institute India – Bangalore Private Limited, filed on 7th May 2015, which is herein incorporated in its entirety by reference for all purposes.

FIELD OF THE INVENTION

The present invention generally relates to wireless communication systems. The present invention more particularly relates to a method of handling multiple packet data network (PDN)/ packet data protocol (PDP) disconnection requests on a same Access Point Name (APN).

BACKGROUND OF THE INVENTION

As per the 3GPP Spec 24.301/24.008, a User Equipment (UE)/ Mobile Station (MS) has multiple packet data network (PDN)/ packet data protocol (PDP) connections (i.e. multiple default bearers) on a same access point name (APN). Consider, a scenario where the UE/MS requests a PDN/PDP connection with PDN/PDP Type as IPv4v6 and due to network limitation such as network uses single addressing per bearer, the network accepts only one IP version (say IPv6) and sends ESM Failure Cause #52 in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST. In such a case UE/MS again requests for a new PDN/PDP connection with the non-accepted PDN/PDP Type (IPv4 in this case). So, two default/primary bearers are established on the same APN but with different PDN/PDP Types.

During PDN/PDP disconnection, since 2 bearers are active, UE/MS will first send PDN/PDP disconnection request for the first connection and a separate PDN/PDP disconnection request for the second connection. In these kinds of scenarios, where UE/MS has multiple PDN/PDP connections to the same APN and UE/MS wants to disconnect from the APN, it has to send PDN/PDP disconnect request for each of the existing PDN/PDP connections on the APN. Therefore, the current approach is inefficient as it requires separate PDN/PDP disconnection requests for all PDNs/PDPs.

According to the current 3GPP standard 24.301, the section 6.2.2 states: IP address allocation via NAS signaling, which states: If the UE/MS requests PDN type IPv4v6, but the operator uses single addressing per bearer, e.g. due to interworking with nodes of earlier releases, the network shall override the PDN type requested by the UE/MS to a single IP version only. In the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE, the network shall set the PDN type value to either "IPv4" or "IPv6" and the ESM cause value to #52 for "single address bearers only allowed". The UE/MS should subsequently request another PDN connection for the other IP version using the UE/MS requested PDN connectivity procedure to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated.

According to the current 3GPP standard 24.301, the section 5.10 states: Multiple-PDN support, which states: All simultaneous active PDN connections of a UE/MS that are associated with the same APN shall be provided by the same packet data network gateway (P-GW).

According to the current 3GPP standard 24.008, the section 6.1.3.1 states: PDP context activation, which states: If the MS requests PDP type IPv4/v6, but the operator uses single addressing per PDP context due to interworking with nodes of earlier releases, the network shall override the PDP type requested by setting the PDP type in the ACTIVATE PDP CONTEXT ACCEPT message sent to the MS to a single address PDP type. In the ACTIVATE PDP CONTEXT ACCEPT message sent to the MS, the network sets the PDP type number to either "IPv4 address" or "IPv6 address" and the SM cause to #52, "single address bearers only allowed" (see sub-clause 6.1.3.1.1). The MS should subsequently request another PDP context for the other PDP type to the same APN with a single address PDP type (IPv4 or IPv6) other than the one already activated.

Currently, when the UE/ MS has multiple default bearers on an APN and wishes to disconnect from that APN, then the UE/ MS has to send PDN/PDP Disconnect Request for each of the existing PDN/PDP Connections separately. Thus, there is a need for a method which prevents the User Equipment from sending multiple PDN/PDP disconnection requests to disconnect from the PDNs/PDPs associated with the same APN.

The above mentioned shortcomings, disadvantages and problems are addressed herein and which will be understood by reading and studying the following specification.

SUMMARY OF THE INVENTION

The various embodiments herein disclose a method of handling multiple packet data network (PDN)/ packet data protocol (PDP) disconnection requests on the same access point name (APN).

According to an embodiment of the present invention, a method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment having multiple connections with a single Access Point Name (APN), comprising steps of receiving, by a network, signaling message from the UE user to disconnect all PDN/ PDP connections for the APN; where the signaling request includes an information element (IE), checking whether the IE is set in the signaling message, and disconnecting, by the network, one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections.

According to an embodiment of the present invention, the signaling message comprises one of a PDN DISCONNECT REQUEST message and a DEACTIVATE PDP CONTEXT REQUEST message. According to another embodiment of the present invention, the information element is at least one of a Boolean information element (IE) and additional bearer entity IE.

According to another embodiment of the present invention, the Boolean IE comprises an indication of a disconnect from the one or more PDNs for LTE, and a disconnect from the one or more PDPs for UMTS. According to another embodiment of the present invention, the additional IE is one of, but not limited to, a Linked Default EPS Bearer Identity for LTE, a Linked Transaction Identifier for UMTS, and the like.

According to another embodiment of the present invention, the network validates values present in the Linked Default EPS Bearer identity if the EPS bearer identity present in the Linked EPS bearer identity IE and Linked Default EPS bearer identity IE belongs to the same APN, both EPS bearer identity values do not belong to the same APN, then the network can disconnect only bearer-id present in Linked EPS bearer identity IE, and the value of the EPS Bearer identity is present in a preset value range.

According to another embodiment of the present invention, the network validates values present in the Linked Transaction Identifier if a Netscape Server Application Programming Interface (NSAPI) value present in Linked Transaction identifier IE and a Transaction identifier IE belong to the same APN, If both Linked Transaction identifier IE and a Transaction identifier IE values belong to same APN, and the value is present in a preset NSAPI value range.

According to another embodiment of the present invention, the network disconnects only the NSAPI present in Transaction identifier IE if both Linked Transaction identifier IE and Transaction identifier IE values do not belong to same APN and the value present in the Linked Transaction identifier is ignored. According to another embodiment of the present invention, the method further comprises sending, by UE, a separate signaling message for disconnecting a non-accepted PDNs and non-accepted PDPs, if the information element is not set.

According to yet another embodiment of the present invention, a system of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests, comprising a user equipment (UE) having multiple connections with a single Access Point Name (APN) that transmits PDN/ PDP disconnection requests, and a network adapted for receiving a signaling message from the UE user to disconnect one or more PDN/ PDP connections for the APN; where the signaling request includes an information element (IE), checking whether the IE is set in the signaling message, and disconnecting the one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections.

The foregoing has outlined, in general, the various aspects of the invention and is to serve as an aid to better understanding the more complete detailed description which is to follow. In reference to such, there is to be a clear understanding that the present invention is not limited to the method or application of use described and illustrated herein. It is intended that any other advantages and objects of the present invention that become apparent or obvious from the detailed description or illustrations contained herein are within the scope of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The other objects, features and advantages will occur to those skilled in the art from the following description of the preferred embodiment and the accompanying drawings in which:

Figure 1 is a schematic flow diagram depicting a network accepting multiple PDN disconnections on same APN for LTE network, according to an embodiment of the present invention.

Figure 2 is a schematic flow diagram depicting a network accepting multiple PDP disconnections on same APN for UMTS network, according to an embodiment of the present invention.

Figure 3 is a schematic flow diagram depicting a network accepting multiple PDN disconnections on same APN for LTE network, according to another embodiment of the present invention.

Figure 4 is a schematic flow diagram depicting a network accepting multiple PDP disconnections on same APN for UMTS network, according to another embodiment of the present invention.

Figure 5 is a schematic chart illustrating a method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment having multiple connections with a single Access Point Name (APN), according to an embodiment of the present invention.

Although specific features of the present invention are shown in some drawings and not in others. This is done for convenience only as each feature may be combined with any or all of the other features in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a method of handling multiple packet data network (PDN)/ packet data protocol (PDP) disconnection requests on the same access point name (APN). In the following detailed description of the embodiments of the invention, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.

The specification may refer to “an”, “one” or “some” embodiment(s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.

As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence or addition of one or more other features integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations and arrangements of one or more of the associated listed items.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The present invention provides a method of handling multiple packet data network (PDN)/ packet data protocol (PDP) disconnection requests on the same access point name (APN). The herein below described method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests has been described with respect to a user equipment (UE). But the request for disconnecting all the PDN/ PDP connections can be received by a mobile station (MS) handling one or more UEs present within its coverage region, without departing from the scope of the invention.

According to an embodiment of the present invention, a method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment (UE) having multiple connections with a single Access Point Name (APN) is described herein. According to the present invention, the method comprises step of receiving, by a network, signaling request message from the UE user to disconnect all PDN/ PDP connections for the APN, wherein the signaling request includes an information element (IE). The UE can be having one or more PDN or PDP connections with one or more bearers over APN. When the UE wishes to disconnect from all PDN/ PDP connections, then the UE can transmit the signal request message to the network to disconnect all the PDN/ PDP connections with the APN. The network can receive the signaling request message from the UE for disconnecting all the PDN/ PDP connections, wherein the signaling request includes an information element (IE).

In an embodiment of the present invention, the signaling request message can be one of, but not limited to, PDN DISCONNECT REQUEST message, DEACTIVATE PDP CONTEXT REQUEST message, and the like. PDN DISCONNECT REQUEST message, and DEACTIVATE PDP CONTEXT REQUEST messages are the standard messages for disconnection of the PDN/ PDP connection, and the person having ordinarily skilled in the art can understand the function, and message structure of the PDN DISCONNECT REQUEST message, DEACTIVATE PDP CONTEXT REQUEST messages, and hence not described in detail.

In an embodiment of the present invention, the information element (IE) can be at least one of, but not limited to, a Boolean information element (IE), an additional bearer entity IE, and the like. In another embodiment of the present invention, the Boolean IE comprises an indication to disconnect from the one or more PDNs for LTE network. In another embodiment of the present invention, the Boolean IE comprises an indication to disconnect from the one or more PDPs for UMTS network. In yet another embodiment of the present invention, the additional IE is one of a Linked Default evolved packet system (EPS) Bearer Identity for LTE network. In yet another embodiment of the present invention, the additional IE is one of a Linked Transaction Identifier for UMTS network.

Further, the method comprises checking whether the IE is set in the signaling request message. Upon receiving the signaling request message along with IE, the network validates whether the IE is being set or not.

In an embodiment of the present invention, the network validates values present in the Linked Default EPS Bearer identity for LTE network if the EPS bearer identity present in the Linked EPS bearer identity IE and Linked Default EPS bearer identity IE belongs to the same APN, both EPS bearer identity values do not belong to the same APN, then the network can disconnect only bearer-id present in Linked EPS bearer identity IE, and the value of the EPS Bearer identity is present in a preset value range.

In another embodiment of the present invention, the network validates values present in the Linked Transaction Identifier for UMTS network if a Netscape Server Application Programming Interface (NSAPI) value present in Linked Transaction identifier IE and a Transaction identifier IE belong to the same APN, if both Linked Transaction identifier IE and a Transaction identifier IE values belong to same APN, and the value is present in a preset NSAPI value range.

Further, the method comprises disconnecting, by the network, one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections. Upon validating, if the network identifies that the IE is being set, then the network can disconnect all the existing PDN/ PDP connections for the APN of the UE. For disconnecting all the PDN/ PDP connections, the UE need not to send any additional messages to the network and all the existing PDN/ PDP connections for the APN can be disconnected by setting up of IE in the signaling request message.

In an embodiment of the present invention, the network disconnects only the NSAPI present in Transaction identifier IE if both Linked Transaction identifier IE and Transaction identifier IE values do not belong to same APN and the value present in the Linked Transaction identifier is ignored.

According to the present invention, if the information element (IE) is not set in the signaling request message, then the method further comprises the UE sending a separate signaling message for disconnecting a non-accepted PDNs and non-accepted PDPs.

The present invention allows the network to identify the PDN/ PDP connections for the APN of the UE. If the user of the UE wishes to disconnect all the PDN/ PDP connections, then the IE present in the signaling request message can be set and sent to the network. The network can receive the signaling request message along with the IE, validates whether the IE is being set or not.

If the IE is set, then the network can disconnect all the existing PDN/ PDP connections for the APN of the UE. If the IE is not set, then the UE has to send separate messages to the network for disconnecting all the PDN/ PDP connections.

According to an embodiment of the present invention, the signaling request message along with IE can be transmitted by the mobile station (MS) to the network, wherein the MS can comprise of one or more UEs within its coverage region. Based on the signaling request message along with IE received, the network can validate whether the IE is being set or not. If the IE is set, then the network can disconnect all the PDN/ PDP connections for the APN of the MS. If all the PDN/ PDP connections of the MS are disconnected, then PDN/ PDP connections of all the UEs present in the MS are also disconnected for the APN, and thereby not requiring transmitting of either the signaling request message or PDN/ PDP disconnection request message by the individual UEs of the MS.

Figure 1 is a schematic flow diagram 100 depicting a network accepting multiple PDN disconnections on same APN for LTE network, according to an embodiment of the present invention. The flow diagram 100 depicts communication between user equipment (UE) 102 and a network 104 over LTE, wherein the UE 102 can transmit a Boolean information element (IE) in a signaling request message to disconnect from all PDNs. According to the flow diagram 100, at step 106, the UE 102 transmits a PDN DISCONNECT REQUEST message to the network 104, wherein the Boolean IE has been set as true, which indicates that UE wishes to disconnect from all the PDNs. At the network 104, multiple PDNs are active on APN1 for the UE 102. In an embodiment of the present invention, the Boolean IE has been set as true by indicating a Boolean value as 1 and the Boolean IE can be set as false by indicating the Boolean value as 0, without departing from the scope of the invention. The person having ordinarily skilled in the art can understand that Boolean values can be used to set whether to disconnect all PDNs or not, without departing from the scope of the invention.

Upon receiving the PDN DISCONNECT REQUEST along with the IE being set as true, the network 104 identifies that Boolean IE has been set and thus indicates that all the PDNs associated with the APN has to be deactivated. Based on the set Boolean IE, at step 108, the network 104 transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message to the UE 102, wherein the network has set the IE for disconnecting from all the PDNs as true indicating that the network has identified the Boolean IE transmitted by the UE 102 and the network 104 has disconnected all the PDNs. Upon receiving the DEACTIVATE EPS BEARER CONTEXT REQUEST message from the network 104, at step 110, the UE 102 can transmit DEACTIVATE EPS BEARER CONTEXT ACCEPT message to the network 104 and disconnects from all the PDNs of the APN.

In an embodiment of the present invention, if the network 104 identifies that the Boolean IE has not been set, then the network 104 can transmit DEACTIVATE EPS BEARER CONTEXT REQUEST along with disconnecting from all the PDNs as false, indicating that the network cannot disconnect all the PDNs of the APN from the UE. Therefore, at such instance, the UE 102 has to transmit separate PDN DISCONNECT REQUEST for the non-accepted PDN type.

The structure for PDN DISCONNECT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
9.2 M V 1/2
EPS bearer identity EPS bearer identity
9.3.2 M V 1/2
Procedure transaction identity Procedure transaction identity
9.4 M V 1
PDN disconnect request message identity Message type
9.8 M V 1
Linked EPS bearer identity Linked EPS bearer identity
9.9.4.6 M V 1/2
Disconnect from all PDNs Disconnect from all PDNs
9.9.4.18 M V 1/2
27 Protocol configuration options Protocol configuration options
9.9.4.11 O TLV 3-253

The structure for DEACTIVATE EPS BEARER CONTEXT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
9.2 M V 1/2
EPS bearer identity EPS bearer identity
9.3.2 M V 1/2
Procedure transaction identity Procedure transaction identity
9.4 M V 1
Deactivate EPS bearer context request message identity Message type
9.8 M V 1
ESM cause ESM cause
9.9.4.4 M V 1
Disconnect from all PDNs Disconnect from all PDNs
9.9.4.18 M V 1/2
Spare Octet Spare half octet 9.9.2.9 M V 1/2
27 Protocol configuration options Protocol configuration options
9.9.4.11 O TLV 3-253
37 T3396 value GPRS timer 3
9.9.3.16B O TLV 3

Figure 2 is a schematic flow diagram 200 depicting a network accepting multiple PDP disconnections on same APN for UMTS network, according to an embodiment of the present invention. The flow diagram 200 depicts communication between a mobile station (MS) 202 and a network 204 over UMTS, wherein the MS 202 can transmit a Boolean information element (IE) in a signaling request message to disconnect from all PDPs. According to the flow diagram 200, at step 206, the MS 202 transmits a DEACTIVATE PDP CONTEXT REQUEST message to the network 204, wherein the Boolean IE has been set as true, which indicates that the MS 202 wishes to disconnect from all the PDPs. At the network 204, multiple PDPs are active on APN1 for the MS 202. In an embodiment of the present invention, the Boolean IE has been set as true by indicating a Boolean value as 1 and the Boolean IE can be set as false by indicating the Boolean value as 0, without departing from the scope of the invention. The person having ordinarily skilled in the art can understand that Boolean values can be used to set whether to disconnect all PDPs or not, without departing from the scope of the invention.

Upon receiving the DEACTIVATE PDP CONTEXT REQUEST message along with the IE being set as true, the network 204 identifies that Boolean IE has been set and thus indicates that all the PDPs associated with the APN has to be deactivated. Based on the set Boolean IE, at step 208, the network 204 transmits a DEACTIVATE PDP CONTEXT ACCEPT message to the MS 202, wherein the network 204 has set the IE for disconnecting from all the PDPs as true indicating that the network 204 has identified the Boolean IE transmitted by the MS 202 and the network 204 has disconnected all the PDPs.

In an embodiment of the present invention, if the network 204 identifies that the Boolean IE has not been set, then the network 204 can transmit DEACTIVATE PDP CONTEXT ACCEPT message along with disconnecting from all the PDPs as false, indicating that the network cannot disconnect all the PDPs of the APN from the MS 202. Therefore, at such instance, the MS 202 has to transmit separate DEACTIVATE PDP CONTEXT REQUEST message for the non-accepted PDP type.

The structure for DEACTIVATE PDP CONTEXT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
10.2 M V 1/2
Transaction identifier Transaction identifier
10.3.2 M V 1/2– 3/2
Deactivate PDP context request message identity Message type
10.4 M V 1
SM cause SM cause
10.5.6.6 M V 1

Disconnect from all PDPs Disconnect from all PDPs
10.5.6.7 M V
1/2
Spare Octet Spare half octet
10.5.1.8 M V 1/2
9- Tear down indicator Tear down indicator
10.5.6.10 O TV 1
27 Protocol configuration options Protocol configuration options
10.5.6.3 O TLV 3 – 253
35 MBMS protocol configuration options MBMS protocol configuration options 10.5.6.15 O TLV 3 - 253

The structure for DEACTIVATE PDP CONTEXT ACCEPT message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
10.2 M V 1/2
Transaction identifier Transaction identifier
10.3.2 M V 1/2– 3/2
Deactivate PDP context accept message identity Message type
10.4 M V 1
Disconnect from all PDPs Disconnect from all PDPs
10.5.6.7 M V 1/2
Spare Half Octet Spare half octet
10.5.1.8 M V 1/2
27 Protocol configuration options Protocol configuration options
10.5.6.3 O TLV 3 – 253
35 MBMS protocol configuration options MBMS protocol configuration options 10.5.6.15 O TLV 3 - 253

The present flow diagram 200 has been described with respect to mobile station (MS), wherein the mobile station (MS) transmits request message along with Boolean IE to disconnection PDPs. Thus, all the PDPs are disconnected by the network for all user equipment’s (UEs) present in the coverage region of the MS. In another embodiment of the present invention, one or more UEs can separately transmit request messages to the network to disconnect all PDPs.

The herein abovementioned figures describe using Boolean value as IE in the signal request messages for disconnecting all PDNs/ PDPs. In an alternate approach of the present invention, linked default evolved packet system (EPS) bearer identity can be used as information element (IE) for disconnecting all PDNs from the UE/ MS. According to the present approach, the IE indicates that a Linked Default EPS bearer identity has to be disconnected along with the Linked EPS bearer identity. The value present in Linked Default EPS Bearer identity can be considered as valid if below conditions are met:
• EPS bearer identity present in Linked EPS bearer identity IE & Linked Default EPS bearer identity IE should belong to same APN.
• If both EPS bearer identity values do not belong to the same APN, then the network can disconnect only bearer-id present in Linked EPS bearer identity IE. In this case, the value present in Linked Default EPS bearer identity can be ignored.
• The value should be valid EPS Bearer identity value i.e. any value in range ‘5-11’ are treated as valid. All other values are treated as invalid & can be ignored when received.

When accepted, the network should deactivate Linked Default EPS bearer identity locally.

Figure 3 is a schematic flow diagram 300 depicting a network accepting multiple PDN disconnections on same APN for LTE network, according to another embodiment of the present invention. The flow diagram 300 depicts communication between user equipment (UE) 302 and a network 304 over LTE, wherein the UE 302 can transmit a linked default EPS bearer identity as information element (IE) in a signaling request message to disconnect from all PDNs. According to the flow diagram 300, at step 306, the UE 302 transmits a PDN DISCONNECT REQUEST message to the network 304, wherein the IE comprises linked EPS bearer identity for PDN1 and linked default EPS bearer identity for PDN2, which indicates that UE 302 wishes to disconnect from PDN2. At the network 304, PDN1 and PDN2 are active on APN1 for the UE 302. In an embodiment of the present invention, a predetermined value has been set to the IE, wherein the predetermined value refers to particular PDN and the UE 302 wishes to disconnect with respect to the particular PDN.

Upon receiving the PDN DISCONNECT REQUEST along with the IE, the network 304 identifies the linked default EPS bearer identity present in the IE belongs to PDN2 and thus indicates that PDN2 associated with the APN has to be deactivated. Based on the set IE, at step 308, the network 304 transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message to the UE 302 along with IE, wherein the IE comprises linked EPS bearer identity for PDN1 and linked default EPS bearer identity for PDN2 for disconnecting UE 302 from PDN2. Upon receiving the DEACTIVATE EPS BEARER CONTEXT REQUEST message from the network 304, at step 310, the UE 302 can transmit DEACTIVATE EPS BEARER CONTEXT ACCEPT message to the network 304 and disconnects from all the PDNs of the APN.

In an embodiment of the present invention, if the network 304 identifies that the value mentioned in the IE for the particular PDN sent in PDN DISCONNECT REQUEST and the DEACTIVATE EPS BEARER CONTEXT REQUEST message are not matching, then the UE 302 has to transmit PDN DISCONNECT REQUEST for second PDN again.

The structure for PDN DISCONNECT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
9.2 M V 1/2
EPS bearer identity EPS bearer identity
9.3.2 M V 1/2
Procedure transaction identity Procedure transaction identity
9.4 M V 1
PDN disconnect request message identity Message type
9.8 M V 1
Linked EPS bearer identity Linked EPS bearer identity
9.9.4.6 M V 1/2
Linked Default EPS bearer identity Linked EPS bearer identity
9.9.4.18 M V 1/2
27 Protocol configuration options Protocol configuration options
9.9.4.11 O TLV 3-253

The structure for DEACTIVATE EPS BEARER CONTEXT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
9.2 M V 1/2
EPS bearer identity EPS bearer identity
9.3.2 M V 1/2
Procedure transaction identity Procedure transaction identity
9.4 M V 1
Deactivate EPS bearer context request message identity Message type
9.8 M V 1
ESM cause ESM cause
9.9.4.4 M V 1
Linked Default EPS bearer identity Linked EPS bearer identity
(9.9.4.18) M V 1/2
Spare Octet Spare half octet 9.9.2.9 M V 1/2
27 Protocol configuration options Protocol configuration options
9.9.4.11 O TLV 3-253
37 T3396 value GPRS timer 3
9.9.3.16B O TLV 3

In another alternate approach of the present embodiment, linked transaction identifier can be used as information element (IE) for disconnecting all PDPs from the UE/ MS. According to the present approach, the IE indicates the Netscape Server Application Programming Interface (NSAPI) that requires to be disconnected along with Transaction identifier IE. The value present in Linked Transaction identifier is considered as valid if below conditions are met:
• NSAPI value present in Linked Transaction identifier IE & Transaction identifier IE should belong to same APN.
• If both Linked Transaction identifier IE & Transaction identifier IE values do not belong to same APN, then network can disconnect only the NSAPI present in Transaction identifier IE. In this case value present in Linked Transaction identifier can be ignored.
• The value should be valid Netscape Server Application Programming Interface (NSAPI) value i.e. any value in range ‘5-11’ are treated as valid. All other values are treated as invalid & can be ignored when received.

When accepted, network should deactivate Linked Transaction identity locally

Figure 4 is a schematic flow diagram 400 depicting a network accepting multiple PDP disconnections on same APN for UMTS network, according to another embodiment of the present invention. The flow diagram 400 depicts communication between a mobile station (MS) 402 and a network 404 over UMTS, wherein the MS 402 can transmit a linked transaction identifier as an information element (IE) in a signaling request message to disconnect from all PDPs. According to the flow diagram 400, at step 406, the MS 402 transmits a DEACTIVATE PDP CONTEXT REQUEST message to the network 404, wherein the IE comprises transaction identifier for PDP1 and linked transaction identifier for PDP2, which indicates that UE 402 wishes to disconnect from PDP2. At the network 404, PDP1 and PDP2 are active on APN1 for the MS 402. In an embodiment of the present invention, a predetermined value has been set to the IE, wherein the predetermined value refers to particular PDP and the UE 402 wishes to disconnect with respect to the particular PDP.

Upon receiving the DEACTIVATE PDP CONTEXT REQUEST message along with the IE, the network 404 identifies the linked transaction identifier present in the IE belongs to PDP2 and thus indicates that PDP2 associated with the APN1 has to be deactivated. Based on the linked transaction identifier present in the IE, at step 408, the network 404 transmits a DEACTIVATE PDP CONTEXT ACCEPT message to the MS 402, wherein the network 404 has set the IE for disconnecting from the PDP2 and thus the network 204 disconnects PDP2 from the MS 402.

In an embodiment of the present invention, if the network 404 identifies that the value mentioned in the IE for the PDP2 sent in DEACTIVATE PDP CONTEXT REQUEST and the DEACTIVATE PDP CONTEXT ACCEPT message are not matching, then the UE 402 has to transmit PDP DISCONNECT REQUEST for PDP2 again.

The structure for DEACTIVATE PDP CONTEXT REQUEST message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
10.2 M V 1/2
Transaction identifier Transaction identifier
10.3.2 M V 1/2– 3/2
Deactivate PDP context request message identity Message type
10.4 M V 1
SM cause SM cause
10.5.6.6 M V 1
Linked Transaction identifier Transaction identifier
10.5.6.7 M LV 2– 3
9- Tear down indicator Tear down indicator
10.5.6.10 O TV 1
27 Protocol configuration options Protocol configuration options
10.5.6.3 O TLV 3 – 253
35 MBMS protocol configuration options MBMS protocol configuration options 10.5.6.15 O TLV 3 - 253

The structure for DEACTIVATE PDP CONTEXT ACCEPT message is as follows:
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator
10.2 M V 1/2
Transaction identifier Transaction identifier
10.3.2 M V 1/2– 3/2
Deactivate PDP context accept message identity Message type
10.4 M V 1
Linked Transaction identifier Transaction identifier
10.5.6.7 M LV 2– 3
27 Protocol configuration options Protocol configuration options
10.5.6.3 O TLV 3 – 253
35 MBMS protocol configuration options MBMS protocol configuration options 10.5.6.15 O TLV 3 - 253

The present flow diagram 400 has been described with respect to mobile station (MS), wherein the mobile station (MS) transmits request message along with IE to disconnect with particular PDPs. Thus, the particular PDPs are disconnected by the network for all user equipment’s (UEs) present in the coverage region of the MS. In another embodiment of the present invention, one or more UEs can separately transmit request messages to the network to disconnect particular PDPs.

Figure 5 is a schematic chart 500 illustrating a method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment having multiple connections with a single Access Point Name (APN), according to an embodiment of the present invention. According to the flow chart 500, at step 502, a network receives a signaling message from the UE user to disconnect all PDN/ PDP connections for the APN, wherein the signaling request includes an information element (IE). Further, at step 504, the method comprises the network checking whether the IE is set in the signaling message. Further, at step 506, the method comprises the network disconnecting one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections.

The present embodiments have been described with reference to specific example embodiments; it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. Furthermore, the various devices, modules, and the like described herein may be enabled and operated using hardware circuitry, for example, complementary metal oxide semiconductor based logic circuitry, firmware, software and/or any combination of hardware, firmware, and/or software embodied in a machine readable medium. For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits, such as application specific integrated circuit.

Although the embodiments herein are described with various specific embodiments, it will be obvious for a person skilled in the art to practice the invention with modifications. However, all such modifications are deemed to be within the scope of the claims. It is also to be understood that the following claims are intended to cover all of the generic and specific features of the embodiments described herein and all the statements of the scope of the embodiments which as a matter of language might be said to fall there between.

,CLAIMS:
CLAIM:
We Claim:

1. A method of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests from a User Equipment (UE) having multiple connections with a single Access Point Name (APN), comprising:
receiving, by a network, a signaling message from the UE user to disconnect one or more PDN/ PDP connections for the APN; where the signaling request includes an information element (IE);
checking whether the IE is set in the signaling message; and
disconnecting, by the network, the one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections.

2. The method of claim 1, wherein the signaling message comprises one of a PDN DISCONNECT REQUEST message and a DEACTIVATE PDP CONTEXT REQUEST message.

3. The method of claim 1, wherein information element is at least one of a Boolean information element (IE) and an additional bearer entity IE.

4. The method of claim 3, wherein the Boolean IE comprises an indication to:
disconnect from the one or more PDNs for long term evolution (LTE); and
disconnect from the one or more PDPs for universal mobile telecommunication system (UMTS).

5. The method of claim 3, wherein the additional IE is one of:
a Linked Default EPS Bearer Identity for LTE; or
a Linked Transaction Identifier for UMTS.

6. The method of claim 5,wherein the network validates values present in the Linked Default EPS Bearer identity if:
the EPS bearer identity present in the Linked EPS bearer identity IE and Linked Default EPS bearer identity IE belongs to the single APN;
both EPS bearer identity values do not belong to the single APN, then the network disconnects only bearer-id present in the Linked EPS bearer identity IE; and
the value of the EPS Bearer identity is present in a preset value range.

7. The method of claim 5,wherein the network validates values present in the Linked Transaction Identifier if:
a Netscape Server Application Programming Interface (NSAPI) value is present in Linked Transaction identifier IE and a Transaction identifier IE belong to the same APN;
both Linked Transaction identifier IE and a Transaction identifier IE value belong to same APN; and
the value is present in a preset NSAPI value range.

8. The method of claim 7, wherein the network disconnects the NSAPI present in the transaction identifier IE if both linked transaction identifier IE and transaction identifier IE values do not belong to the single APN and the value present in the linked transaction identifier is ignored.

9. The method of claim 1, further comprising:
sending, by the UE, a separate signaling message for disconnecting a non-accepted PDNs and non-accepted PDPs, if the information element is not set.

10. A system of handling Packet Data Network (PDN)/ Packet Data Protocol (PDP) disconnection requests, comprising:
a user equipment (UE) having multiple connections with a single Access Point Name (APN) that transmits PDN/ PDP disconnection requests; and
a network adapted for:
receiving a signaling message from the UE user to disconnect one or more PDN/ PDP connections for the APN; where the signaling request includes an information element (IE);
checking whether the IE is set in the signaling message; and
disconnecting the one or more PDN/PDP connections for the APN if the IE is set without requiring an additional request message from the UE to disconnect the PDN/ PDP connections.

11. The system of claim 10, wherein the signaling message comprises one of a PDN DISCONNECT REQUEST message and a DEACTIVATE PDP CONTEXT REQUEST message.

12. The system of claim 10, wherein information element is at least one of a Boolean information element (IE) and an additional bearer entity IE.

Dated this the 3rd day of November 2015

Signature

KEERTHI J S
Patent agent
Agent for the applicant

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 2334-CHE-2015-IntimationOfGrant06-09-2022.pdf 2022-09-06
1 SRIB-20140925-010_Provisional Specification_Filed with IPO on 7th May 2015.pdf 2015-05-15
2 2334-CHE-2015-PatentCertificate06-09-2022.pdf 2022-09-06
2 SRIB-20140925-010_Drawings_Filed with IPO on 7th May 2015.pdf 2015-05-15
3 POA_Samsung R&D Institute India-new.pdf 2015-05-15
3 2334-CHE-2015-PETITION UNDER RULE 137 [05-09-2022(online)].pdf 2022-09-05
4 2334-CHE-2015-PETITION UNDER RULE 137 [20-05-2022(online)].pdf 2022-05-20
4 2334-CHE-2015 POWER OF ATTORNEY 13-07-2015.pdf 2015-07-13
5 2334-CHE-2015-Written submissions and relevant documents [20-05-2022(online)].pdf 2022-05-20
5 2334-CHE-2015 FORM-1 13-07-2015.pdf 2015-07-13
6 2334-CHE-2015-FORM-26 [04-05-2022(online)].pdf 2022-05-04
6 2334-CHE-2015 CORRESPONDENCE OTHERS 13-07-2015.pdf 2015-07-13
7 Drawing [03-11-2015(online)].pdf 2015-11-03
7 2334-CHE-2015-Correspondence to notify the Controller [02-05-2022(online)].pdf 2022-05-02
8 Description(Complete) [03-11-2015(online)].pdf 2015-11-03
8 2334-CHE-2015-US(14)-HearingNotice-(HearingDate-05-05-2022).pdf 2021-12-15
9 2334-CHE-2015-FER_SER_REPLY [15-05-2020(online)].pdf 2020-05-15
9 REQUEST FOR CERTIFIED COPY [08-02-2016(online)].pdf_12.pdf 2016-02-08
10 2334-CHE-2015-FORM 3 [15-05-2020(online)].pdf 2020-05-15
10 REQUEST FOR CERTIFIED COPY [08-02-2016(online)].pdf 2016-02-08
11 2334-CHE-2015-FORM-26 [15-05-2020(online)].pdf 2020-05-15
11 Form-18(Online).pdf 2016-09-26
12 2334-CHE-2015-FER.pdf 2019-11-15
12 Form-2(Online).pdf 2016-09-30
13 2334-CHE-2015-FORM 13 [25-10-2019(online)].pdf 2019-10-25
13 REQUEST FOR CERTIFIED COPY [19-05-2017(online)].pdf 2017-05-19
14 2334-CHE-2015-FORM 13 [25-10-2019(online)].pdf 2019-10-25
14 REQUEST FOR CERTIFIED COPY [19-05-2017(online)].pdf 2017-05-19
15 2334-CHE-2015-FER.pdf 2019-11-15
15 Form-2(Online).pdf 2016-09-30
16 2334-CHE-2015-FORM-26 [15-05-2020(online)].pdf 2020-05-15
16 Form-18(Online).pdf 2016-09-26
17 REQUEST FOR CERTIFIED COPY [08-02-2016(online)].pdf 2016-02-08
17 2334-CHE-2015-FORM 3 [15-05-2020(online)].pdf 2020-05-15
18 2334-CHE-2015-FER_SER_REPLY [15-05-2020(online)].pdf 2020-05-15
18 REQUEST FOR CERTIFIED COPY [08-02-2016(online)].pdf_12.pdf 2016-02-08
19 2334-CHE-2015-US(14)-HearingNotice-(HearingDate-05-05-2022).pdf 2021-12-15
19 Description(Complete) [03-11-2015(online)].pdf 2015-11-03
20 2334-CHE-2015-Correspondence to notify the Controller [02-05-2022(online)].pdf 2022-05-02
20 Drawing [03-11-2015(online)].pdf 2015-11-03
21 2334-CHE-2015 CORRESPONDENCE OTHERS 13-07-2015.pdf 2015-07-13
21 2334-CHE-2015-FORM-26 [04-05-2022(online)].pdf 2022-05-04
22 2334-CHE-2015 FORM-1 13-07-2015.pdf 2015-07-13
22 2334-CHE-2015-Written submissions and relevant documents [20-05-2022(online)].pdf 2022-05-20
23 2334-CHE-2015 POWER OF ATTORNEY 13-07-2015.pdf 2015-07-13
23 2334-CHE-2015-PETITION UNDER RULE 137 [20-05-2022(online)].pdf 2022-05-20
24 2334-CHE-2015-PETITION UNDER RULE 137 [05-09-2022(online)].pdf 2022-09-05
24 POA_Samsung R&D Institute India-new.pdf 2015-05-15
25 SRIB-20140925-010_Drawings_Filed with IPO on 7th May 2015.pdf 2015-05-15
25 2334-CHE-2015-PatentCertificate06-09-2022.pdf 2022-09-06
26 SRIB-20140925-010_Provisional Specification_Filed with IPO on 7th May 2015.pdf 2015-05-15
26 2334-CHE-2015-IntimationOfGrant06-09-2022.pdf 2022-09-06

Search Strategy

1 searchstrategy_15-11-2019.pdf

ERegister / Renewals

3rd: 30 Nov 2022

From 07/05/2017 - To 07/05/2018

4th: 30 Nov 2022

From 07/05/2018 - To 07/05/2019

5th: 30 Nov 2022

From 07/05/2019 - To 07/05/2020

6th: 30 Nov 2022

From 07/05/2020 - To 07/05/2021

7th: 30 Nov 2022

From 07/05/2021 - To 07/05/2022

8th: 30 Nov 2022

From 07/05/2022 - To 07/05/2023

9th: 01 May 2023

From 07/05/2023 - To 07/05/2024

10th: 02 May 2024

From 07/05/2024 - To 07/05/2025

11th: 02 May 2025

From 07/05/2025 - To 07/05/2026