EP1912385B1 - Système et procédé afin de désactiver des sessions IP de priorités moindres - Google Patents

Système et procédé afin de désactiver des sessions IP de priorités moindres Download PDF

Info

Publication number
EP1912385B1
EP1912385B1 EP06122310A EP06122310A EP1912385B1 EP 1912385 B1 EP1912385 B1 EP 1912385B1 EP 06122310 A EP06122310 A EP 06122310A EP 06122310 A EP06122310 A EP 06122310A EP 1912385 B1 EP1912385 B1 EP 1912385B1
Authority
EP
European Patent Office
Prior art keywords
mobile device
sessions
session
priority
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP06122310A
Other languages
German (de)
English (en)
Other versions
EP1912385A1 (fr
Inventor
Jeff Wirtanen
M. Khaledul Islam
Jin Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to EP06122310A priority Critical patent/EP1912385B1/fr
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Priority to DE602006008800T priority patent/DE602006008800D1/de
Priority to AT06122310T priority patent/ATE441273T1/de
Priority to EP11177120A priority patent/EP2387184A3/fr
Priority to PCT/CA2007/001795 priority patent/WO2008046194A1/fr
Priority to KR1020117025891A priority patent/KR20110125679A/ko
Priority to AU2007312905A priority patent/AU2007312905A1/en
Priority to JP2009531701A priority patent/JP5145343B2/ja
Priority to BRPI0719192-8 priority patent/BRPI0719192B1/pt
Priority to KR1020097009627A priority patent/KR101117935B1/ko
Priority to CA2666368A priority patent/CA2666368C/fr
Priority to CN2007800455518A priority patent/CN101563950B/zh
Priority to EP07855419A priority patent/EP2078409B1/fr
Publication of EP1912385A1 publication Critical patent/EP1912385A1/fr
Priority to HK08111496.8A priority patent/HK1118407A1/xx
Application granted granted Critical
Publication of EP1912385B1 publication Critical patent/EP1912385B1/fr
Priority to HK10102614.0A priority patent/HK1136144A1/xx
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the application relates generally to wireless communication, and more particularly to IP sessions.
  • the GPRS serving nodes include an SGSN (Serving GPRS Support Node) and a GGSN (Gateway GPRS Support Node).
  • SGSN Serving GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • Such communication exchange between the mobile device and the corresponding node involve communication exchange between the mobile device and the SGSN.
  • Communication exchanges such as user plane communication (i.e. IP data traffic) between the mobile device and the SGSN node use one or more PDP contexts.
  • PDP contexts There may be many PDP contexts depending on how many different applications of the mobile device are communicating over PDP contexts. However, the number of PDP contexts for the mobile device may be limited by the number of PDP contexts supported in the routing area in which the mobile device resides. Different routing areas may support different numbers of PDP contexts.
  • the mobile device moves from a first routing area supporting a plurality of PDP contexts to a second routing area supporting fewer PDP contexts.
  • the SGSN will deactivate PDP contexts such that the mobile device does not have more PDP contexts than are supported by the second routing area.
  • the mobile device cannot predict which PDP contexts will be deactivated. This can result in a poor user experience, especially if a PDP context being used for a voice call is deactivated.
  • Another example of poor user experience is if a PDP context being used for IP Modem/Tethered Modem is deactivated.
  • EP 1 686 752 discloses a method for achieving multimedia priority services, which sets up priority service classes for the user equipment (UE) using multimedia services.
  • Another existing approach is found in WO 03/017522 which describes how combined session and resource tracking in a mobile node (MN) and/or base station in dynamic network resource environment can be used to control reactions to resource shortage.
  • MN mobile node
  • WO 2005/084061 relates to a method for managing radio resources allocated by the radio network controller of a UTRAN radio access network.
  • a method in a mobile device comprising: determining a respective priority for each of a plurality of Internet Protocol 'IP' sessions of the mobile device, the respective priorities indicating which of the plurality of IP sessions of the mobile device should be maintained and which of the plurality of IP sessions of the mobile device should be deactivated if the mobile device moves into an area that supports a maximum number of IP sessions per mobile device that is fewer than how many IP sessions are established for the mobile device; and transmitting an indication of each respective priority to a wireless network.
  • a computer readable medium having computer executable instructions stored thereon for execution on a processor so as to implement the method summarised above.
  • a mobile device comprising: a wireless access radio adapted to communicate with a wireless network; an IP session priority function adapted to: determine a respective priority for each of a plurality of IP sessions of the mobile device, the respective priorities indicating which of the plurality of IP sessions of the mobile device should be maintained and which of the plurality of IP sessions of the mobile device should be deactivated if the mobile device moves into an area that supports a maximum number of IP sessions per mobile device that is fewer than how many IP sessions are established for the mobile device; and transmit an indication of each respective priority to the wireless network.
  • a method in a wireless network maintaining a plurality of IP sessions for a mobile device; receiving an indication of a respective priority for each of the plurality of IP sessions; and upon determining that at least one of the plurality of IP sessions of the mobile device is to be deactivated due to the mobile device moving into an area supporting fewer IP sessions for the mobile device than are established for the mobile device, deactivating an IP session of the mobile device that is indicated to be of lower priority than at least one other of said plurality of IP sessions.
  • a computer readable medium having computer executable instructions stored thereon for execution on a processor so as to implement the method summarised above.
  • a wireless network comprising an IP session function adapted to: maintain a plurality of IP sessions for a mobile device; receive an indication of a respective priority for each of the plurality of IP sessions; and upon determining that at least one of the plurality of IP sessions of the mobile device is to be deactivated due to the mobile device moving into an area supporting fewer IP sessions for the mobile device than are established for the mobile device, deactivate an IP session of the mobile device that is indicated to be of lower priority.
  • the wireless network 100 has a first routing area 30 and a second routing area 40. There may be other routing areas, but they are not shown for simplicity. Each routing area has at least one RNC (Radio Network Controller).
  • the first routing area 30 has a first RNC 31 and a second RNC 32 while the second routing area 40 has a single RNC 41.
  • Each RNC 31,32,41 is associated with a respective RNC Id.
  • the first RNC 31 and the second RNC 32 of the first routing area 30 have an RNC Id 31a and an RNC Id 32a, respectively, while the single RNC 41 of the second routing area 40 has an RNC Id 41a.
  • Each cell (not shown) within an RNC (via a Node B) is associated with an RAI (Routing Area Identification) in a hierarchal fashion.
  • An RAI may include one or more cells and span across RNCs.
  • each RAI is a combination of a country code, a network code, and a routing area code. RAIs may differ for other wireless networks.
  • each RNC 31,32,41 is coupled to an SGSN (Serving General Packet Radio Service Support Node) 50, which in turn is coupled to a GGSN (Gateway GPRS Support Node) 60, which in turn is coupled to a PDN (Packet Data Network) 70.
  • the PDN 70 may for example be an Internet.
  • the SGSN 50 has an IP session function 51 coupled to a processor 52 and may have other components, but they are not shown for simplicity.
  • the wireless network 100 is shown with a single mobile device, namely the mobile device 10. There may be other mobile devices, but they are not shown for simplicity.
  • FIG 1B shown is a block diagram of the mobile device 10 shown in Figure 1A .
  • the mobile device 10 has a processor 12, which is coupled to a wireless access radio 11, an IP session priority function 13, applications 14, and a user interface 15.
  • the mobile device 10 may have other components, but they are not shown for sake of simplicity.
  • the mobile device 10 is currently positioned within the first routing area 31. However, the mobile device 10 may move to another routing area such as the second routing area 40 as indicated by a moving arrow 19.
  • the mobile device 10 is adapted to communicate with the wireless network 100 using its wireless access radio 11. Such communication may for example be voice communication, electronic messaging, or any other appropriate form of communication supported by the applications 14. At least some communication with the wireless network 100 is over one or more IP sessions between the mobile device 10 and the SGSN 50.
  • a PDP (Packet Data Protocol) session is an example of an IP session.
  • Different routing areas may support different number of IP sessions for a given mobile device. This may for example depend on the RNC of the routing area, or may alternatively depend on any other limitation of the wireless network.
  • the first routing area is assumed to support three IP sessions for the mobile device 10 while the second routing area 40 is assumed to support only a single IP session for the mobile device 10.
  • the mobile device 10 is assumed to have three established IP sessions while in the first routing area.
  • two of the three IP sessions will be deactivated since the second routing area supports only a single IP session.
  • the SGSN 50 deactivates the two IP sessions, but this may be triggered by signaling from the RNC.
  • the IP session priority function 13 implements a method in the mobile device 10 so as to determine a respective priority for each of the IP sessions and to transmit an indication of each respective priority to the wireless network 100.
  • the SGSN 50 receives the indication of the respective priority for each IP session.
  • the IP session function 51 implements a method in the SGSN 50 so as to deactivate an IP session that is indicated to be of lower priority upon determining that at least one IP session is to be deactivated due to the mobile device 10 moving into a routing area supporting fewer IP sessions than are established for the mobile device. In the event that more than one IP session is to be deactivated, then more than one IP session that is indicated to be of lower priority is deactivated. Accordingly, IP sessions that are not deactivated are those indicated by the mobile device 10 to be of greater priority. Further details of the methods are provided later with reference to Figures 2 through 5 .
  • an IP session is indicated to be of "lower" priority when its priority is generally indicated as being lower than other IP sessions. In some implementations, this is the IP session with the lowest priority.
  • An IP session indicated as having a lower priority may not be a low priority IP session per se, but is nonetheless indicated as having a lower priority than other IP sessions.
  • the mobile device 10 may move back to a routing area supporting more IP sessions, such as the first routing area 30. In this event, the mobile device 10 may choose to reestablish those IP sessions that were deactivated. In some implementations, it is up to the mobile device 10 to reestablish an IP session, for example by transmitting an Activate PDP context request message to the SGSN 50 of the wireless network 100. In response to the Activate PDP context request message, the SGSN 50 may establish an IP session for the mobile device 10. In some implementations, the mobile device 10 automatically initiates the IP session to be reestablished. In other implementations, a user of the mobile device 10 provides input, for example using the user interface 15, so as to initiate the IP session to be reestablished. In other implementations, the wireless network 100 initiates the IP session to be reestablished. For example, the wireless network 100 may send a Request PDP context Activation message to the mobile device 100. Other implementations are possible.
  • each routing area has a single RNC, such is the case with the second routing area 40.
  • the number of IP sessions supported for a given mobile device is currently limited by the RNC. Therefore, while the limiting factor is actually the RNC, the routing area can typically be regarded as the limiting factor.
  • a routing area might have more than one RNC, such is the case with the first routing area 30. Therefore, it is possible for a routing area to support a different number of PDP contexts for a mobile device depending on where in the routing area the mobile device resides. This is the case in which the routing area cannot be regarded as the limiting factor.
  • routing areas as limiting the number of IP sessions for a mobile device
  • area limits the number of IP sessions for the mobile device.
  • the "area” may be a routing area, a portion of a routing area as defined for example by an RNC Id, a network, a cell id, or any other area in which the number of IP sessions supported for a mobile device is limited.
  • the Connected/Active state CELL_DCH, CELL_FACH
  • the Idle state CELL_PCH, URA_PCH, IDLE
  • the routing area is known to the mobile device while in the Idle state; however, the RNC id is typically not known. While in the Idle state, a mobile device moves to the Connected/Active state in order to find out its serving RNC id. This may waste battery life, etc. Therefore, in some implementations, the number of IP sessions supported is considered for a routing area irrespective of whether this is the lowest level of granularity.
  • the IP session priority function 13 of the mobile device 10 is implemented as software and is executed on the processor 12. However, more generally, the IP session priority function 13 may be implemented as software, hardware, firmware, or any appropriate combination thereof. In the illustrated example, the IP session priority function 13 is shown as a single component. However, more generally, the IP session priority function 13 may be implemented as one or more components. An example in which the IP session priority function 13 includes more than one component is described below.
  • the IP session priority function 13 includes a NAS (Non Access Stratum) and an AS (Access Stratum).
  • the NAS includes a session management layer and manages IP sessions.
  • the NAS may for example initiate an Activate PDP context request message to be sent to the SGSN 50.
  • the AS manages an air interface of the wireless access radio and includes a respective RAB (Radio Access Bearer) for each active IP session.
  • An RAB is an identifier for an RF (Radio Frequency) pipe. There may be dormant IP sessions without respective RABs.
  • the AS may for example initiate a service request message to be sent to the RNC.
  • the IP session function 51 of the wireless network 100 there are many possibilities for the IP session function 51 of the wireless network 100.
  • the IP session function 51 is implemented as software and is executed on the processor 52.
  • the IP session function 51 may be implemented as software, hardware, firmware, or any appropriate combination thereof.
  • the IP session function 51 is shown as a single component of the SGSN 50.
  • the IP session function 51 may be implemented as one or more components and may be implemented as part of, or separate from, the SGSN 50.
  • the one or more components may be distributed throughout the wireless network 100, or reside in a common location. Other implementations are possible.
  • the wireless network 100 is a UMTS (Universal Mobile Telecommunications System) network.
  • the wireless network 100 may be any wireless network in which there are areas supporting different numbers of IP sessions.
  • FIG. 1C shown is a block diagram of another mobile device 80 that may implement any of the methods described herein. It is to be understood that the mobile device 80 is shown with very specific details for example purposes only.
  • a processing device (a microprocessor 128) is shown schematically as coupled between a keyboard 114 and a display 126.
  • the microprocessor 128 controls operation of the display 126, as well as overall operation of the mobile device 80, in response to actuation of keys on the keyboard 114 by a user.
  • the mobile device 80 has a housing that may be elongated vertically, or may take on other sizes and shapes (including clamshell housing structures).
  • the keyboard 114 may include a mode selection key, or other hardware or software for switching between text entry and telephony entry.
  • a communications subsystem 170 In addition to the microprocessor 128, other parts of the mobile device 80 are shown schematically. These include: a communications subsystem 170; a short-range communications subsystem 102; the keyboard 114 and the display 126, along with other input/output devices including a set of LEDS 104, a set of auxiliary I/O devices 106, a serial port 108, a speaker 111 and a microphone 112; as well as memory devices including a flash memory 116 and a Random Access Memory (RAM) 118; and various other device subsystems 120.
  • the mobile device 80 may have a battery 121 to power the active elements of the mobile device 80.
  • the mobile device 80 is in some embodiments a two-way radio frequency (RF) communication device having voice and data communication capabilities.
  • the mobile device 80 in some embodiments has the capability to communicate with other computer systems via the Internet.
  • RF radio frequency
  • Operating system software executed by the microprocessor 128 is in some embodiments stored in a persistent store, such as the flash memory 116, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element.
  • system software, specific device applications, or parts thereof may be temporarily loaded into a volatile store, such as the RAM 118.
  • Communication signals received by the mobile device 80 may also be stored to the RAM 118.
  • a personal information manager (PIM) application module 130C may also be installed on the mobile device 80 during manufacture.
  • the PIM application is in some embodiments capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items.
  • the PIM application is also in some embodiments capable of sending and receiving data items via a wireless network 110.
  • the data items managed by the PIM application are seamlessly integrated, synchronized and updated via the wireless network 110 with the device user's corresponding data items stored or associated with a host computer system.
  • additional software modules illustrated as another software module 130N, may be installed during manufacture.
  • the communication subsystem 170 includes a receiver 150, a transmitter 152 and one or more antennas, illustrated as a receive antenna 154 and a transmit antenna 156.
  • the communication subsystem 170 also includes a processing module, such as a digital signal processor (DSP) 158, and local oscillators (LOs) 160.
  • DSP digital signal processor
  • LOs local oscillators
  • the communication subsystem 170 of the mobile device 80 may be designed to operate with the Mobitex TM , DataTAC TM or General Packet Radio Service (GPRS) mobile data communication networks and also designed to operate with any of a variety of voice communication networks, such as Advanced Mobile Phone Service (AMPS), Time Division Multiple Access (TDMA), Code Division Multiple Access CDMA, Personal Communications Service (PCS), Global System for Mobile Communications (GSM), etc.
  • AMPS Advanced Mobile Phone Service
  • TDMA Time Division Multiple Access
  • CDMA Code Division Multiple Access
  • PCS Personal Communications Service
  • GSM Global System for Mobile Communications
  • Other types of data and voice networks, both separate and integrated, may also be utilized with the mobile device 80.
  • Network access may vary depending upon the type of communication system. For example, in the Mobitex TM and DataTAC TM networks, mobile devices are registered on the network using a unique Personal Identification Number (PIN) associated with each device. In GPRS networks, however, network access is typically associated with a subscriber or user of a device. A GPRS device therefore typically has a subscriber identity module, commonly referred to as a Subscriber Identity Module (SIM) card, in order to operate on a GPRS network.
  • SIM Subscriber Identity Module
  • the mobile device 80 may send and receive communication signals over the communication network 110.
  • Signals received from the communication network 110 by the receive antenna 154 are routed to the receiver 150, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to-digital conversion of the received signal allows the DSP 158 to perform more complex communication functions, such as demodulation and decoding.
  • signals to be transmitted to the network 110 are processed (e.g., modulated and encoded) by the DSP 158 and are then provided to the transmitter 152 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 110 (or networks) via the transmit antenna 156.
  • the DSP 158 provides for control of the receiver 150 and the transmitter 152. For example, gains applied to communication signals in the receiver 150 and the transmitter 152 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 158.
  • a received signal such as a text message or web page download
  • the communication subsystem 170 is input to the microprocessor 128.
  • the received signal is then further processed by the microprocessor 128 for an output to the display 126, or alternatively to some other auxiliary I/O devices 106.
  • a device user may also compose data items, such as e-mail messages, using the keyboard 114 and/or some other auxiliary I/O device 106, such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device.
  • the composed data items may then be transmitted over the communication network 110 via the communication subsystem 170.
  • a voice communication mode In a voice communication mode, overall operation of the device is substantially similar to the data communication mode, except that received signals are output to a speaker 111, and signals for transmission are generated by a microphone 112.
  • Alternative voice or audio I/O subsystems such as a voice message recording subsystem, may also be implemented on the mobile device 80.
  • the display 126 may also be utilized in voice communication mode, for example, to display the identity of a calling party, the duration of a voice call, or other voice call related information.
  • the short-range communications subsystem 102 enables communication between the mobile device 80 and other proximate systems or devices, which need not necessarily be similar devices.
  • the short-range communications subsystem may include an infrared device and associated circuits and components, or a Bluetooth TM communication module to provide for communication with similarly-enabled systems and devices.
  • FIG. 2 shown is a flowchart of an example method of indicating priority of IP sessions to a wireless network.
  • This method may be implemented by a mobile device, for example by the IP session priority function 13 of the mobile device 10 shown in Figures 1A and 1B , or by the mobile device 80 shown in Figure 1C .
  • the mobile device determines a respective priority for each of a plurality of IP sessions.
  • the mobile device transmits an indication of each respective priority to a wireless network.
  • the mobile device may transmit the indication to the wireless network. Examples are provided with reference to Figures 3A through 3C .
  • the mobile device transmits a message having the indication of each respective priority.
  • the mobile device transmits a plurality of messages. Each message provides a dynamic update of the respective priority of at least one of the IP sessions.
  • the plurality of messages may be of varying type, or of the same type.
  • the mobile device transmits the at least one message to the wireless network upon an event triggering a priority level update. Other implementations are possible.
  • the message is an RAU (Routing Area Update) request message.
  • the RAU request message may for example be sent periodically, upon the mobile device crossing a routing area boundary, or when the mobile device transitions from an idle state to a standby state such as when the mobile device is powered on.
  • the message may be sent by the mobile device to the wireless network either to request an update of its location file or to request an IMSI attach for non-GPRS services.
  • the RAU request message is also sent whenever there is an active voice call, irrespective of whether there is data to send.
  • the RAU request message is provided with the indication as a new field to convey PDP context priority. Referring to Figure 4A , shown is a table of example message content of the RAU request message.
  • the table has columns labeled as IEI 81, Information Element 82, Type 83, Presence 84, Format 85, and length 86.
  • the table has a plurality of fields 91 including a "PDP context priority" field, which is the new field to convey PDP context priority.
  • the "PDP context priority" field has an IEI value, which may for example be 38.
  • the message is a Modify PDP Context Accept message.
  • This message may be sent by the mobile device to the wireless network to acknowledge the modification of an active PDP context.
  • the Modify PDP Context Accept message is provided with the indication as a new field to convey PDP context priority.
  • FIG 4B shown is a table of example message content of the Modify PDP Context Accept message.
  • the table has columns labeled as IEI 81, Information Element 82, Type 83, Presence 84, Format 85, and length 86.
  • the table has a plurality of fields 92 including a "PDP context priority" field, which is the new field to convey PDP context priority.
  • the "PDP context priority" field has an IEI value, which may for example be 38.
  • the message is an Activate PDP (Packet Data Protocol) Request message.
  • the Activate PDP Request message may for example be sent when the mobile device is requesting a PDP session to be activated or when the mobile device is to activate a new NSAPI (Network Service Access Point Identifier).
  • the Activate PDP context request message is provided with the indication as a new field to convey PDP context priority.
  • the new field conveys PDP context priority of the new PDP context and/or existing PDP contexts. By conveying PDP context priority of the existing PDP contexts, changes to the priority of the existing PDP contexts can be conveyed. Other implementations are possible.
  • the message is a PDP Status Request message.
  • the PDP Status Request message may for example be sent when the mobile device is requesting status of a PDP session.
  • the PDP Status Request message is provided with the indication as a new field to convey PDP context priority.
  • the message is a Deactivate PDP context request message.
  • the Deactivate PDP context request message may for example be sent when the mobile device is deactivating a PDP context. This message may be sent to request deactivation of an active PDP context or an active MBMS context.
  • the Deactivate PDP context request message is provided with the indication as a new field to convey PDP context priority.
  • the Deactivate PDP context request message does not include the indication as a field, as deactivating a PDP context serves as an implicit indication that the priority of the PDP context is lower than other PDP contexts. Referring to Figure 4C , shown is a table of example message content of the Deactivate PDP context request message.
  • the table has columns labeled as IEI 81, Information Element 82, Type 83, Presence 84, Format 85, and length 86.
  • the table has a plurality of fields 93 including a "PDP context priority" field, which is the new field to convey PDP context priority.
  • the "PDP context priority" field has an IEI value, which may for example be 38.
  • the message is a PDP Service Request message.
  • the PDP Service Request message may for example be sent when the mobile device is requesting service for an existing PDP context.
  • the PDP Service Request message is provided with the indication as a new field to convey PDP context priority.
  • the message is a priority update message.
  • the priority message may be any appropriate message capable of carrying the indication of each respective priority. The priority message may for example be sent whenever the mobile device determines that a priority updated is to be executed.
  • the priority update message is a Modify PDP Context Request message sent from the mobile device to the wireless network.
  • the Modify PDP Context Request message is provided with the indication as a new field to convey PDP context priority.
  • the priority update message is a Modify PDP Context Priority message.
  • Example messages have been provided above for the message having the indication of each respective priority.
  • the messages are based on messages defined in 3GPP (3rd Generation Partnership Project) TS 24.008 V7.5.0 with appropriate modification for including the indication of each respective priority. Other implementations are possible.
  • the indication includes a respective numerical priority level for each of a plurality of different IP session types. For instance, if there is a first IP session for modem communication, a second IP session for WAP (Wireless Application Protocol) communication, and a third IP session for push email, then the indication may for example be (1,3,2). In this case, the first IP session for modem communication has the highest priority level while the second IP session for WAP communication has the lowest priority level.
  • the indication is an ordered set of priority levels corresponding to IP sessions that may be maintained. For example, the mobile device may be informed of IP sessions that have been established by way of a message such as an RAU accept message. In response to the message, the mobile device may transmit a message such as an RAU accept with an indication of an ordered set of priority levels corresponding to the IP sessions that have been established.
  • the indication includes an order of priority. For instance, if there is a first IP session for modem communication, and a second IP session for VoIP (Voice over IP), then the indication may for example be (Identifier for the first IP session, Identifier for the second IP session). In this case, the first IP session for modem communication is indicated as having a higher priority than the second IP session for VoIP.
  • the PDP context priority information element shown in the illustrated example is a specific implementation for the indication for example purposes only. The purpose of the PDP context priority information element is to indicate the priority of each PDP context which can be identified by NSAPI.
  • the priority may be used by the wireless network to determine which PDP contexts to deactivate for issues such as resource limitations.
  • the PDP context status information element is a type 4 information element with a minimum length of 3 octets and 10 octets length maximal. Further restriction on the length may be applied, for example the number of PDP contexts activated.
  • the PDP context status information element is coded according to a coding scheme. In some implementations, the coding scheme includes the numeric number of PDPs. In some implementations, the number of PDPs is preceded by the IEI (information element identifier) for the data field.
  • the table of Figure 5A has entries for encoding the 1 st priority NSAPI, the second priority NSAPI, ..., and the 11 th priority NSAPI.
  • the entries are encoded according to the encoding scheme outlines in the table of Figure 5B .
  • the indication identifies the type priority such as for an "Always On" IP Session compared to a short term duration IP Session such as for Internet browsing. Certain types of IP Sessions may implicitly be regarded as having a higher priority than others. Other implementations are possible.
  • the event triggering a priority level update.
  • the event is a change to the IP sessions.
  • the event is user input specifying that there should be a priority level update.
  • the event is a predefined schedule indicating that a priority level update is to be executed.
  • the event is dependent upon the type of message being transmitted, examples of which have been provided above. Other implementations are possible.
  • the mobile device may determine the respective priority for each IP session. Examples are presented with reference to Figures 6A and 6B .
  • the mobile device accepts user input for determining the respective priority for each IP session. Accordingly, the mobile device determines the respective priority for each IP session based on the user input.
  • the mobile device maintains a record of a predefined priority level for each IP session of a predefined type. Accordingly, the mobile device determines the respective priority for each IP session based on the record.
  • Other implementations are possible.
  • FIG. 7 shown is a flowchart of an example method of deactivating IP sessions that are indicated to be of lower priority.
  • This method may be implemented by a wireless network, for example by the IP session function 51 of the wireless network 100 shown in Figure 1A .
  • the wireless network maintains IP sessions for a mobile device.
  • the mobile device indicates to the wireless network the priority of IP sessions.
  • the wireless network receives an indication of a respective priority for each IP session.
  • the wireless network upon determining that at least one of the IP sessions is to be deactivated due to the mobile device moving into a routing area supporting fewer IP sessions than are established for the mobile device, the wireless network deactivates an IP session that is indicated to be of lower priority. In the event that more than one IP session is to be deactivated, then more than one IP session that is indicated to be of lower priority is deactivated. Accordingly, IP sessions that are not deactivated are those indicated by the mobile device to be of greater priority.
  • the wireless network may for example receive the indication as it is transmitted by the mobile device using any one or more of the implementations described above.
  • IP sessions may for example include any of an Always-On IP session, an IM (Instant Messaging) IP session, a WAP (Wireless Application Protocol) IP session, an MMS (Multimedia Messaging Service) IP session, a DUN (Dial-Up Networking) IP session, an LBS (Location Base Services) IP session, IP Modem IP session, and a PTT (Push-to-Talk) IP session.
  • the nature of the IP sessions is implementation specific and typically depends on the wireless network.
  • the wireless network is a UMTS network and each IP session is part of a respective PDP (Packet Data Protocol) context.
  • PDP Packet Data Protocol

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Hardware Redundancy (AREA)
  • Communication Control (AREA)

Claims (22)

  1. Un procédé dans un dispositif mobile (10, 80) comprenant :
    la détermination (2-1) d'une priorité respective pour chaque session d'une pluralité de sessions Internet Protocol, ci-après dénommé IP, du dispositif mobile (10, 80), les priorités respectives indiquant lesquelles des sessions de la pluralité de sessions IP du dispositif mobile (10, 80) doivent être maintenues et lesquelles des sessions de la pluralité de sessions IP du dispositif mobile (10, 80) doivent être désactivées si le dispositif mobile (10, 80) est déplacé vers une zone qui accepte un nombre maximum de sessions IP par dispositif mobile (10, 80) qui est inférieur au nombre de sessions IP qui sont établies pour le dispositif mobile (10, 80), et
    la transmission (2-2) d'une indication de chaque priorité respective à un réseau sans fil (100).
  2. Le procédé selon la revendication 1 où la transmission (2-2) de l'indication de chaque priorité respective au réseau sans fil (100) comprend :
    la transmission (3A-1) d'au moins un message au réseau sans fil, le au moins un message comprenant l'indication de chaque priorité respective.
  3. Le procédé selon la revendication 2 où le au moins un message comprend l'un quelconque ou une combinaison de :
    un message de demande de mise à jour de zone de routage « RAU »,
    un message d'acceptation de modification de contexte de protocole de données par paquets « PDP »,
    un message de demande d'activation de protocole de données par paquets « PDP », un message de demande d'état de PDP,
    un message de désactivation de PDP,
    un message de demande de service de PDP, et/ou
    un message de mise à jour de priorité.
  4. Le procédé selon la revendication 2 ou 3 où la transmission (3A-1) du au moins un message au réseau sans fil (100) comprend :
    la transmission (3B-1) d'une pluralité de messages, chaque message de la pluralité de messages fournissant une mise à jour dynamique de la priorité respective d'au moins une session de la pluralité de sessions IP.
  5. Le procédé selon la revendication 2 ou 3 où la transmission (3A-1) du au moins un message au réseau sans fil (100) comprend :
    la transmission (3C-1) du au moins un message au réseau sans fil en cas d'événement déclenchant une mise à jour de niveau de priorité.
  6. Le procédé selon la revendication 5 où l'événement déclenchant la mise à jour de niveau de priorité comprend une modification dans la pluralité de sessions IP.
  7. Le procédé selon l'une quelconque des revendications 1 à 6 comprenant en outre :
    l'acceptation (6A-1) d'une entrée utilisateur,
    où la détermination (2-1) de la priorité respective pour chaque session de la pluralité de sessions IP est basée sur l'entrée utilisateur.
  8. Le procédé selon l'une quelconque des revendications 1 à 6 comprenant en outre :
    l'entretien (6B-1) d'un enregistrement d'un niveau de priorité prédéfini pour chaque session IP d'un type prédéfini,
    où la détermination (2-1) de la priorité respective pour chaque session de la pluralité de sessions IP est basée sur l'enregistrement.
  9. Le procédé selon l'une quelconque des revendications 1 à 8 où la pluralité de sessions IP comprend l'une quelconque ou toute combinaison de : une session IP toujours connectée, une session IP de messagerie instantanée « IM », une session IP de protocole pour des applications sans fil « WAP », une session IP de service de messagerie multimédia « MMS », une session IP de mise en réseau par connexion téléphonique « DUN », une session IP de services de localisation « LBS », une session IP de modem IP et/ou une session IP de conversation par bouton-poussoir « PTT ».
  10. Le procédé selon l'une quelconque des revendications 1 à 9 où chaque session de la pluralité de sessions IP fait partie d'un contexte de PDP respectif.
  11. Un support lisible par ordinateur possédant en mémoire des instructions exécutables par ordinateur pour exécution sur un processeur (12) d'un dispositif informatique (10, 80) de façon à mettre en oeuvre le procédé selon l'une quelconque des revendications 1 à 10.
  12. Un dispositif mobile (10, 80) comprenant :
    un système radio d'accès sans fil (11) adapté de façon à communiquer avec un réseau sans fil (100),
    une fonction de priorité de session IP (13) adapté de façon à :
    déterminer (2-1) une priorité respective pour chaque session d'une pluralité de sessions IP du dispositif mobile (10, 80), les priorités respectives indiquant lesquelles des sessions de la pluralité de sessions IP du dispositif mobile (10, 80) doivent être maintenues et lesquelles des sessions de la pluralité de sessions IP du dispositif mobile (10, 80) doivent être désactivées si le dispositif mobile (10,80) est déplacé vers une zone qui accepte un nombre maximum de sessions IP par dispositif mobile qui est inférieur au nombre de sessions IP qui sont établies pour le dispositif mobile (10, 80), et
    transmettre (2-2) une indication de chaque priorité respective au réseau sans fil.
  13. Le dispositif mobile (10, 80) selon la revendication 12 où la fonction de priorité de session IP comprend :
    une strate de non-accès destinée à gérer des sessions IP, et
    une strate d'accès, ci-après dénommée AS, destinée à gérer une interface hertzienne ou le système radio d'accès sans fil, l'AS comprenant un circuit support d'accès radio respectif pour chaque session IP qui est active.
  14. Un procédé dans un réseau sans fil (100) comprenant :
    l'entretien (7-1) d'une pluralité de sessions IP pour un dispositif mobile (10, 80),
    la réception (7-2) d'une indication d'une priorité respective pour chaque session de la pluralité de sessions IP, et
    après la détermination qu'au moins une session de la pluralité de sessions IP du dispositif mobile (10, 80) doit être désactivée du fait du déplacement du dispositif mobile (10, 80) vers une zone acceptant moins de sessions IP par dispositif mobile (10,80) que ne sont établies pour le dispositif mobile (10, 80), la désactivation (7-3) d'une session IP du dispositif mobile (10, 80) qui est indiquée comme étant d'une priorité plus basse qu'au moins une autre des sessions de ladite pluralité de sessions IP.
  15. Le procédé selon la revendication 14 où la réception (7-2) de l'indication de la priorité respective pour chaque session de la pluralité de sessions IP comprend :
    la réception (3A-1) d'au moins un message du dispositif mobile (10, 80), le au moins un message comprenant l'indication de chaque priorité respective.
  16. Le procédé selon la revendication 15 où le au moins un message comprend l'un quelconque ou une combinaison de :
    un message de demande de RAU,
    un message d'acceptation de modification de contexte de PDP,
    un message de demande d'activation de PDP,
    un message de demande d'état de PDP,
    un message de désactivation de PDP,
    un message de demande de service de PDP, et/ou
    un message de mise à jour de priorité.
  17. Le procédé selon la revendication 15 ou 16 où la réception (3A-1) d'au moins un message du dispositif mobile (10, 80) comprend :
    la réception (3B-1) d'une pluralité de messages, chaque message de la pluralité de messages fournissant une mise à jour dynamique de la priorité respective d'au moins une session de la pluralité de sessions IP.
  18. Le procédé selon l'une quelconque des revendications 14 à 17 où la pluralité de sessions IP comprend l'une quelconque ou toute combinaison de : une session IP toujours connectée, une session IP IM, une session IP WAP, une session IP MMS, une session IP DUN, une session IP LBS, une session IP de modem IP et/ou une session IP PTT.
  19. Le procédé selon l'une quelconque des revendications 14 à 18 où chaque session de la pluralité de sessions IP fait partie d'un contexte de PDP respectif.
  20. Un support lisible par ordinateur possédant en mémoire des instructions exécutables par ordinateur pour exécution sur un processeur (52) d'un dispositif ou système informatique de façon à mettre en oeuvre le procédé selon l'une quelconque des revendications 14 à 19.
  21. Un réseau sans fil (100) comprenant une fonction de session IP (51) adaptée de façon à :
    entretenir (7-1) une pluralité de sessions IP pour un dispositif mobile (10, 80),
    recevoir (7-2) une indication d'une priorité respective pour chaque session de la pluralité de sessions IP, et
    après la détermination qu'au moins une session de la pluralité de sessions IP du dispositif mobile (10, 80) doit être désactivée du fait du déplacement du dispositif mobile (10, 80) vers une zone acceptant moins de sessions IP par dispositif mobile (10, 80) que ne sont établies pour le dispositif mobile (10, 80), désactiver (7-3) une session IP du dispositif mobile (10, 80) qui est indiquée comme étant d'une priorité plus basse.
  22. Le réseau sans fil selon la revendication 21 comprenant en outre :
    un noeud de support du service général de radiocommunications en mode paquet de desserte (50), ci-après dénommé noeud SGSN, pour la réception de l'indication de la priorité respective pour chaque session de la pluralité de sessions IP,
    où le noeud SGSN 50 comprend la fonction de session IP.
EP06122310A 2006-10-13 2006-10-13 Système et procédé afin de désactiver des sessions IP de priorités moindres Active EP1912385B1 (fr)

Priority Applications (15)

Application Number Priority Date Filing Date Title
DE602006008800T DE602006008800D1 (de) 2006-10-13 2006-10-13 System und Verfahren zum Beenden von IP-Verbindungen niedrigerer Priorität
AT06122310T ATE441273T1 (de) 2006-10-13 2006-10-13 System und verfahren zum beenden von ip- verbindungen niedrigerer priorität
EP06122310A EP1912385B1 (fr) 2006-10-13 2006-10-13 Système et procédé afin de désactiver des sessions IP de priorités moindres
EP07855419A EP2078409B1 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions ip de priorité inférieure
KR1020117025891A KR20110125679A (ko) 2006-10-13 2007-10-10 낮은 우선순위의 ｉｐ 세션들을 비활성화하기 위한 시스템 및 방법
AU2007312905A AU2007312905A1 (en) 2006-10-13 2007-10-10 System and method for deactivating IP sessions of lower priority
JP2009531701A JP5145343B2 (ja) 2006-10-13 2007-10-10 低優先度のｉｐセッションの切断に対するシステムと方法
BRPI0719192-8 BRPI0719192B1 (pt) 2006-10-13 2007-10-10 Método em um dispositivo móvel, meio que pode ser lido em computador, dispositivo móvel, método em uma rede sem fio e rede sem fio para desativação de sessões de ip deprioridade baixa
EP11177120A EP2387184A3 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions IP de priorité inférieure
CA2666368A CA2666368C (fr) 2006-10-13 2007-10-10 Systeme et procede pour desactiver des sessions ip de priorite inferieure
CN2007800455518A CN101563950B (zh) 2006-10-13 2007-10-10 用于去激活具有较低优先级的ip会话的方法和装置
PCT/CA2007/001795 WO2008046194A1 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions ip de priorité inférieure
KR1020097009627A KR101117935B1 (ko) 2006-10-13 2007-10-10 낮은 우선순위의 ｉｐ 세션들을 비활성화하기 위한 시스템 및 방법
HK08111496.8A HK1118407A1 (en) 2006-10-13 2008-10-16 System and method for deactivating ip sessions of lower priority
HK10102614.0A HK1136144A1 (en) 2006-10-13 2010-03-12 Device and method for deactivating ip sessions of lower priority

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP06122310A EP1912385B1 (fr) 2006-10-13 2006-10-13 Système et procédé afin de désactiver des sessions IP de priorités moindres

Publications (2)

Publication Number Publication Date
EP1912385A1 EP1912385A1 (fr) 2008-04-16
EP1912385B1 true EP1912385B1 (fr) 2009-08-26

Family

ID=37459376

Family Applications (3)

Application Number Title Priority Date Filing Date
EP06122310A Active EP1912385B1 (fr) 2006-10-13 2006-10-13 Système et procédé afin de désactiver des sessions IP de priorités moindres
EP11177120A Withdrawn EP2387184A3 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions IP de priorité inférieure
EP07855419A Active EP2078409B1 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions ip de priorité inférieure

Family Applications After (2)

Application Number Title Priority Date Filing Date
EP11177120A Withdrawn EP2387184A3 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions IP de priorité inférieure
EP07855419A Active EP2078409B1 (fr) 2006-10-13 2007-10-10 Système et procédé pour désactiver des sessions ip de priorité inférieure

Country Status (11)

Country Link
EP (3) EP1912385B1 (fr)
JP (1) JP5145343B2 (fr)
KR (2) KR101117935B1 (fr)
CN (1) CN101563950B (fr)
AT (1) ATE441273T1 (fr)
AU (1) AU2007312905A1 (fr)
BR (1) BRPI0719192B1 (fr)
CA (1) CA2666368C (fr)
DE (1) DE602006008800D1 (fr)
HK (2) HK1118407A1 (fr)
WO (1) WO2008046194A1 (fr)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2279634B1 (fr) * 2008-05-09 2018-03-07 BlackBerry Limited Procédés et appareil pour accorder la priorité à une assignation d une session de paquets de données pour une pluralité d applications d un dispositif de communication mobile
US20100254334A1 (en) * 2009-04-06 2010-10-07 Qualcomm Incorporated Setting up a communication session within a wireless communications system
BRPI1010599B1 (pt) * 2009-05-13 2021-03-16 Apple Inc método para pausar e continuar a transmissão de comunicação a um nó móvel, método para controlar as transmissões de comunicação a um nó móvel e rede de comunicações
US20110038372A1 (en) 2009-08-12 2011-02-17 Research In Motion Limited Accommodating Hybrid IPv4v6 Network Support
US8768295B2 (en) * 2010-02-18 2014-07-01 Alcatel Lucent Method of handling a change to bearer control mode
JP5574944B2 (ja) * 2010-12-21 2014-08-20 三菱電機株式会社 無線中継装置および無線中継方法
KR101272928B1 (ko) 2011-11-29 2013-06-11 현대자동차주식회사 차량용 히치리시버 장치
CN104160762B (zh) 2012-03-08 2019-03-15 三星电子株式会社 用于控制无线通信系统中的服务的方法
GB2501110A (en) * 2012-04-12 2013-10-16 Nec Corp Packet based emergency connection management
SE541941C2 (en) 2015-12-04 2020-01-07 Icomera Ab Dynamic traffic shaping for communication networks in moving vehicles, such as trains
SE1650680A1 (en) 2016-05-19 2017-11-20 Icomera Ab Wireless communication system
SE540574C2 (en) 2016-07-14 2018-10-02 Icomera Ab Train communication system with silent compartments
SE542673C2 (en) 2016-07-22 2020-06-23 Icomera Ab Wireless communication system for vehicles using both trackside wlan and cellular network communication
JP6905431B2 (ja) * 2017-09-12 2021-07-21 株式会社日立国際電気 無線通信装置
EP3756414B1 (fr) * 2018-03-23 2023-02-22 Samsung Electronics Co., Ltd. Procédés, terminal et entité de réseau pour la gestion d'une procédure de demande de service dans un réseau de communication
CN113661771A (zh) * 2019-04-11 2021-11-16 索尼集团公司 多用户标识无线通信设备的寻呼的通信间隙
AU2019461885A1 (en) * 2019-08-12 2021-03-25 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Session establishment method and apparatus
US11323387B2 (en) * 2020-05-18 2022-05-03 Juniper, Networks, Inc. Prioritized communication session establishment in computer networks
SE2151550A1 (en) 2021-12-17 2023-06-18 Icomera Ab Wireless communication system for moving vehicles, such as trains, with improved prioritization

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5420985A (en) * 1992-07-28 1995-05-30 Texas Instruments Inc. Bus arbiter system and method utilizing hardware and software which is capable of operation in distributed mode or central mode
US7050445B1 (en) * 1997-07-30 2006-05-23 Bellsouth Intellectual Property Corporation System and method for dynamic allocation of capacity on wireless networks
US6463062B1 (en) * 1997-11-19 2002-10-08 At&T Corp. Integrating switching and facility networks using ATM
EP1024676A1 (fr) * 1999-01-31 2000-08-02 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Système de communication, procédés de gestion d'un système de communication et équipement mobile d'usager
FI107674B (fi) * 1999-08-30 2001-09-14 Nokia Mobile Phones Ltd Menetelmä tiedonsiirron optimoimiseksi pakettikytkentäisessä langattomassa tiedonsiirtojärjestelmässä
US6571095B1 (en) * 1999-12-30 2003-05-27 Nokia Internet Communications Inc. System and method for providing address discovery of services in mobile networks
US20010026538A1 (en) * 2000-01-10 2001-10-04 Jorg Bruss Method and system for exchange of multicall capabilities between terminal and network
JP3771420B2 (ja) * 2000-04-19 2006-04-26 富士通株式会社 交換局装置，基地局制御装置及びマルチコール通話呼数変更方法
US6738361B1 (en) * 2000-05-31 2004-05-18 Nokia Ip Inc. Method, apparatus and computer program for IP traffic prioritization in IP networks
EP1176766A1 (fr) * 2000-07-24 2002-01-30 Lucent Technologies Inc. Réseau de télécommunications avec accords de qualité de service basée sur la priorité
EP1421710B1 (fr) * 2001-08-16 2017-11-15 QUALCOMM Incorporated Procédés, dispositif de communication mobile et station de base dans un un système de communication ayant des ressources de communication partagées
JP2004363730A (ja) * 2003-06-02 2004-12-24 Mitsubishi Electric Corp システム間ハンドオーバ方式及び携帯端末及びシステム
CN100550881C (zh) * 2003-12-11 2009-10-14 华为技术有限公司 一种实现多媒体优先业务的方法
JP2007520131A (ja) * 2004-01-28 2007-07-19 フランス テレコム Ｕｔｒａｎ無線アクセスネットワークにおける無線リソース管理方法、コアネットワークサービスノード、および無線アクセスネットワーク制御装置

Also Published As

Publication number Publication date
ATE441273T1 (de) 2009-09-15
EP2078409B1 (fr) 2012-06-27
AU2007312905A1 (en) 2008-04-24
WO2008046194A1 (fr) 2008-04-24
EP2078409A1 (fr) 2009-07-15
BRPI0719192A2 (pt) 2014-02-04
EP2078409A4 (fr) 2009-09-02
HK1136144A1 (en) 2010-06-18
KR101117935B1 (ko) 2012-02-29
EP2387184A3 (fr) 2011-11-30
HK1118407A1 (en) 2009-02-06
CN101563950A (zh) 2009-10-21
CA2666368A1 (fr) 2008-04-24
CN101563950B (zh) 2013-05-15
CA2666368C (fr) 2013-11-19
JP5145343B2 (ja) 2013-02-13
BRPI0719192B1 (pt) 2019-12-10
JP2010506516A (ja) 2010-02-25
EP1912385A1 (fr) 2008-04-16
DE602006008800D1 (de) 2009-10-08
KR20110125679A (ko) 2011-11-21
KR20090069188A (ko) 2009-06-29
EP2387184A2 (fr) 2011-11-16

Similar Documents

Publication Publication Date Title
EP1912385B1 (fr) Système et procédé afin de désactiver des sessions IP de priorités moindres
US20080089303A1 (en) System and method for deactivating IP sessions of lower priority
US8315162B2 (en) System and method for determining that a maximum number of IP sessions have been established
JP5171913B2 (ja) Ｉｐセッションの最大数が確立されていることを決定するシステムおよび方法
EP1912386B1 (fr) Système et procédé de gestion de sessions IP basé sur le nombre de sessions supporté
US8687586B2 (en) System and method for managing IP sessions based on how many IP sessions are supported
AU2011265423B2 (en) System and method for deactivating IP sessions of lower priority
CA2598378C (fr) Systeme et methode pour determiner qu'un nombre maximal de sessions ip ont ete etablies

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20061013

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AXX Extension fees paid

Extension state: AL

Payment date: 20061013

Extension state: RS

Payment date: 20061013

Extension state: HR

Payment date: 20061013

Extension state: MK

Payment date: 20061013

Extension state: BA

Payment date: 20061013

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1118407

Country of ref document: HK

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602006008800

Country of ref document: DE

Date of ref document: 20091008

Kind code of ref document: P

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1118407

Country of ref document: HK

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091226

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091228

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091207

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091031

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20100527

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091013

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091013

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100227

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006008800

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006008800

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012560000

Ipc: H04L0012700000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006008800

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN, DE

Effective date: 20140925

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006008800

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012560000

Ipc: H04L0012700000

Effective date: 20140926

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006008800

Country of ref document: DE

Owner name: BLACKBERRY LIMITED, WATERLOO, CA

Free format text: FORMER OWNER: RESEARCH IN MOTION LTD., WATERLOO, ONTARIO, CA

Effective date: 20140925

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006008800

Country of ref document: DE

Representative=s name: MERH-IP MATIAS ERNY REICHL HOFFMANN PATENTANWA, DE

Effective date: 20140925

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231027

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231025

Year of fee payment: 18

Ref country code: DE

Payment date: 20231027

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006008800

Country of ref document: DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602006008800

Country of ref document: DE

Owner name: MALIKIE INNOVATIONS LTD., IE

Free format text: FORMER OWNER: BLACKBERRY LIMITED, WATERLOO, ONTARIO, CA