WO2007128343A1 - SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL - Google Patents

SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL Download PDF

Info

Publication number
WO2007128343A1
WO2007128343A1 PCT/EP2006/061980 EP2006061980W WO2007128343A1 WO 2007128343 A1 WO2007128343 A1 WO 2007128343A1 EP 2006061980 W EP2006061980 W EP 2006061980W WO 2007128343 A1 WO2007128343 A1 WO 2007128343A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
bearer
support
core network
indication
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.)
Ceased
Application number
PCT/EP2006/061980
Other languages
English (en)
Inventor
Niklas Lundin
Tomas HOLMSTRÖM
J. Javier PASTOR BALBÁS
Justus Petersson
Hans RÖNNEKE
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/EP2006/061980 priority Critical patent/WO2007128343A1/fr
Publication of WO2007128343A1 publication Critical patent/WO2007128343A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to a communication system supporting communication of packet data and which comprises a number of nodes of different categories comprising a number of core network nodes communicating with mobile user stations over one or more radio access networks and capable of communicating with policy handling nodes .
  • Said mobile user stations and core network nodes and possibly policy and/or service handling nodes comprise respective bearer service managing means.
  • the invention also relates to a core network packet data support node adapted to handle communication with mobile user stations over a radio access network and other core network nodes and/or other nodes, for example policy and/or service handling nodes, and it comprises bearer service managing means.
  • the invention relates to a mobile user station supporting communication of packet data which comprises bearer service managing means adapted to communicate with core network packet data support nodes.
  • the invention relates to a policy and/or service handling node adapted to be in communication with core network nodes of a core network and comprising a bearer service managing means. Still further the invention relates to a method in a communications system supporting communication of packet data which comprises a number of core network nodes. Particularly the invention relates to establishment of a bearers with a specific QoS.
  • GPRS Global System for Mobile communications
  • PDP Packet Radio Service
  • a packet data support node acting as a gateway for example a GGSN
  • NIB Network Initiated Bearer
  • NIB network initiated bearer set-up
  • a system is needed through which NIB can be implemented also in networks in which one or more nodes do not support NIB.
  • a system is needed through which NIB can be implemented optimally from a system point of view or a network point of view even if some node or equipment or mobile user station does not support NIB.
  • a system is needed through which an operator can introduce NIB independently of any other operator.
  • NIB dependent features can be introduced in an easy manner.
  • a system is needed through which all nodes which are affected by a session will have knowledge of whether the NIB procedure is or can be used and about how they should behave in case it is used as well as if it is not used.
  • a system is needed through which, with due regard to mobility, information as to whether a NIB is or can be used should be maintained, i.e. also when there is a change of for example packet data support node, for example SGSN (Service GPRS Support Node) , or at Inter SGSN Routing Area Update procedures.
  • packet data support node for example SGSN (Service GPRS Support Node)
  • SGSN Service GPRS Support Node
  • a system is needed in which NIB can be introduced without affecting all categories of packet data support nodes .
  • a packet data support node through which one or more of the above mentioned objects can be achieved, i.e. as sisting in fulfilling of one or more above mentioned objects, is also needed.
  • a mobile user station or a user equipment is needed through which one or more of the above mentioned objects can be achieved as well as a policy/server handling node, such as for example a PCRF or similar, application function or other external node, i.e. not forming part of the core network.
  • Still further a method is needed through which one or more of the above mentioned objects can be achieved.
  • a communication system as initially referred to in which at least a number of nodes are adapted to support network initiated bearer set-up, whereby all nodes affected by a session are adapted to, directly or indirectly, provide at least one of said other nodes affected by a particular new, also called current, session, with information about whether it supports network initiated bearer set-up or not upon occurrence of a particular respective activating event, the bearer service managing means of the respect ive nodes involved in the new , current , session being adapted to distribute information about the support of network initiated bearer set-up, thus enabling a negotiation procedure as to whether network initiated bearer set-up shall be used or not for the new or current session.
  • An indirect indication may for example consists in no indication at all being provided which hence indirectly indicates that the node does not support NIB, or vice versa.
  • indirect indication means that an indication received from a node inherently indicates that also preceding nodes directly or indirectly have provided an indication to that node.
  • Particularly network initiated bearer set-up is only used or initiated if all nodes affected by a new or current session, at least as far as NIB is concerned, have provided an indication that network initiated bearer set-up is supported by the respective node for that session.
  • the core network nodes and the mobile user station node respectively comprise a session handling means comprising a data structure with a number of bearers with one or more different characteristics, for example QoS, for each of a number of IP addresses and which is in communication with said bearer service managing means .
  • a session handling means comprising a data structure with a number of bearers with one or more different characteristics, for example QoS, for each of a number of IP addresses and which is in communication with said bearer service managing means .
  • each session always has one IP address, even if there are several PDPs on the session; IP address is an attribute on session; QoS is a PDP attribute and all PDPs of a session have the same IP address.
  • said session handling means are adapted to provide or generate a network initiated bearer set-up support indication.
  • Such a support indication may comprise a specific, selected message.
  • Such a support indication may also comprise an information element (or more information elements) adapted to be included in a data field in an existing, conventional
  • the NIB support indication is provided in a container information element which is adapted to be transferred from one node to another transparently through at least one intermediate node category.
  • the container information element comprises a protocol Configuration Option Field (PCO) .
  • PCO protocol Configuration Option Field
  • Such an information element is generally present in all Session Management (SM) messages such as for example Create PDP Context Request/Response, Modified PDP Context Request/Response and Delete PDP Context Request/Response.
  • SM Session Management
  • the container information element particularly a PCO, is additionally used to initiate or trigger bearer setup in a network node, for example a core network node or an external node such as a PCRF or similar.
  • a core network node of a first category comprises a serving packet data support node, for example an SGSN
  • a core network node of a second category may comprise a gateway packet data support node, such as a GGSN.
  • the activation event for a first category core network node comprises reception of a primary bearer activation/creation request, for example an activate PDP context request, including a network initiated bearer support indication from a mobile user station.
  • the activation event for a second category core network node may comprise reception of a request for creation of a primary- bearer, for example a create PDP context request, including a network initiated bearer activation support indication from a first category core network node, from for example an SGSN.
  • the activation event for a second category core network node comprises reception of a request for creation of a primary bearer including a network initiated bearer activation support indication in such a container element from a mobile user station, transparently transferred to it via a first category- core network node, for example an SGSN.
  • SGSN is not affected by the new or current session as far as NIB is concerned. This is extremely advantageous insofar that any SGSN related procedures will then be unaffected by the introduction of network initiated bearers .
  • SGSN related procedures are for example mobility management using Inter SGSN RAU (ISRAU), SRNS Relocation, PS Handover procedures etc.
  • Particularly at least core network nodes of said second category and/or policy or service handling nodes comprise decision means for deciding if a bearer set-up is to be initiated by the network, e.g. by said policy and/or service handling node, or by said second category core network node, and to forward, directly or indirectly, a decision outcome or a use indication to a respective core network node affected by the new session or to the mobile user station respectively .
  • Particularly all affected or all core network nodes comprise bearer indication decision means for determining if network initiated bearer set-up is to be implemented for a particular session or not unless a PCO container is used.
  • Particularly- said bearer initiation decision means are adapted to be initiated if a decision is received from another node indicating that the network initiated bearer is to be used as far as that other node is concerned.
  • the outcome of the decision in said core network node is directly or indirectly provided to another core network node or to be mobile user station if also said node decides that NIB should be used.
  • Particularly existing, or conventional, messages for example bearer response or acceptance messages are modified or extended to include a decision outcome. Even more particularly the decision outcome is provided in a policy or service related rule installation message modified or extended to include information about the decision outcome.
  • the support indication may e.g. comprise a NIB flag.
  • a PDP context primary
  • a positive decision outcome (use indication) for NIB set-up is provided in a core network node at least of a second category and eventually a policy/service handling node or some other external node as well as the mobile station, the second category core network node or the policy/service handling is adapted to initiate secondary PDP context set-ups during said session, i.e. NIB is implemented throughout the session.
  • a PCO container is used and there is a SGSN change, from an old SGSN functioning differently from a new SGSN as far as NIB support is concerned support and use information has to be updated.
  • a first category core network nodes for example SGSNs
  • SGSNs are seen as nodes affected by a new or current session for the purposes of NIB
  • information has to be provided from a new SGSN as to whether it supports NIB or not to the concerned GGSN, which means that the network or the system will be kept updated as far as NIB support is concerned for the session.
  • PCO containers are used, the SGSNs are seen as not affected.
  • a core network packet data support node as initially referred to is therefore also provided which is adapted to support NIB (by itself or another internal or external network node; internal is here meant a core network node) . It further comprises information generating and distribution means adapted to provide a support indication as to whether, for a given session, (or in general, in which case only use indications are related to the new or current session) network initiated bearer set-up is supported, to be provided to another core network node or to an external, for example policy and/or service handling, node, and further it comprises decision and enabling means adapted to determine if, for the given session, network initiated bearer set-up is to be used and enabled.
  • the information generating and distribution means are comprised by or communicate with IP session handling means comprising a data structure for a number of bearers with one or more different characteristics, for example QoSs, for each IP address.
  • the information generating and distributing means are adapted to provide a support indication upon occurrence or reception of an activating event from a mobile user station or from another core network node, particularly of another category (unless in case of a routing area update) .
  • the support indication particularly comprises a number of parameters, for example a specific information element which for example may be provided in an existing, conventional message sent during a primary bearer set-up, or for creation of a primary bearer such as for example a primary PDP context.
  • the information generating and distributing means may be separate means in communication with the bearer managing means, or be comprised by said bearer managing means.
  • the distribution may relate to a distribution to the bearer managing means for further distribution therefrom to another node or a direct distribution to another node.
  • the activating event particularly depends on the category of the node and it may comprise a support indication received from a mobile user station that network initiated bearer set- up is supported.
  • the node may comprise an SGSN or similar.
  • the node comprises a GGSN.
  • the activating event may then, in the latter case, comprise reception of a support indication from an SGSN or a support indication comprising a PCO container from a mobile user station.
  • the support indication is provided from an SGSN as an information element in an extended or modified message, e.g. a create PDP context request, or from a mobile user station as a PCO container transparently forwarded by SGSN.
  • the activating event normally (unless for an inter SGSN routing area update) comprises reception of a support indication from a mobile station.
  • the packet data support node may also comprise a CGSN (Combined GPRS Support Node) .
  • the bearer service managing means (in an GGSNor CGSN) are adapted to provide the support indication to a policy service handling node or some other external node and to receive a use indication about use of a network initiated bearer set-up from said policy or service handling node, which for example may be a PCRF, in an extended or modified conventional message from such a node, for example a rule installation message.
  • the bearer service managing means of an external node or a core network node of a second category or a first category are adapted to, in communication with the decision or enabling means, include a network initiated bearer use indication in a message towards a mobile user station, e.g. as an information element in an extended or modified message to a core network packet data support node of another category, for example an SGSN. It may also be included in a PCO.
  • the core network packet data support node is adapted to update a decision as to use network initiated bearer set-up or not for a current session if the current session is adapted due to change from one packet data support node handling the session to another of the same category, e.g. from an old SGSN to another, new, SGSN not supporting or supporting NIB, differently from the old SGSN.
  • a mobile user station as initially referred to is also provided which is adapted to support network initiated bearer set-up. It comprises information generating an distributing means adapted to provide a support indication as to whether, for a given new or current session, network initiated bearer set-up is supported, and, directly or in communication with said bearer service managing means, provide a support indication to a core network packet data support node affected by the new or current session at initiation of a bearer for said session.
  • a bearer is here meant a primary or first bearer, such that if all nodes affected by a new or current session (at least as far as NIB is necessarily concerned) can be implemented for subsequent or secondary bearers, for example secondary PDP contexts.
  • the expression affected by a session means all nodes affected by the session, unless the PCO concept is used, which is extremely advantageous in that some nodes, SGSNs, will not be affected.
  • the information generating and distributing means are adapted to directly or via the bearer managing means, unless the same means provide the support indication, include the support indication in a bearer creation request message to be sent to a core network packet data support node.
  • the information generating and distributing means are adapted to generate an indication by providing an information element, for example a flag, including the information element in a conventional bearer creation request, for example an activate primary PDP context request intended for example for an SGSN or similar.
  • the information generating and distributing means are adapted to generate an indication by providing an information element e.g. a flag, in a container, for example a PCO container, intended for a GGSN or similar and adapted to be transparent for any intermediate SGSN.
  • a policy and/or service handling application node adapted to be in communication with core network nodes of a core network as initially referred to is also provided which is adapted to support network initiated bearer set-up and which comprises decision means adapted to determine whether NIB is to be used for a particular new or current session at the occurrence of an activation event and to, if it is decided that NIB is to be used, provide a use indication for the session to a core network node (and/or if NIB is not be used) .
  • the use indication comprises a flag.
  • the activation event may comprise reception of a support indication that NIB is supported from a core network node indicating a new bearer.
  • a policy and/or service control rule installation message is extended or modified to include the use indication.
  • a method as initially referred to comprises the steps of: providing a support indication in a mobile user station indicating of a mobile user station supports network initiated bearer set-up (or not) at initiation of a bearer creation procedure for a session; distributing the support indication to a core network node affected by the session in communication with the mobile user station, if the received indication indicates support for NIB
  • a support indication is provided; an indication is, preferably not provided if there is no support
  • the expression "necessarily affected” is used to include two different implementations, namely when a PCO container, in which case SGSNs are not necessarily affected and the case with an information element in a message w hen SGSNs necessarily are affected.
  • the step of providing a support indication comprises, in the mobile user station: providing information in an information element as to whether the mobile user station supports NIB in a message sent to a core network node upon initiating a bearer creation procedure for a session (SGSN necessarily affected) .
  • the method comprises the step of, in each core network node affected by the session, at least as far as NIB is concerned; upon reception of a support indication from the mobile user station or a preceding core network node respectively that it supports NIB; providing information in an information element as to whether or if the node itself supports NIB; including the information in a respective conventional message to the subsequent core network node or to an external node if it is the subsequent node upon initiation of the primary bearer creation procedure.
  • the step of providing a support indication in a mobile user station comprises; forwarding information in an information container, for example a PCO container; sending the PCO container transparently through any core network packet data support node, providing or having the functionality of an SGSN, to a core network packet data node having the functionality of a gateway packet data support node, for example a GGSN, hence leaving any SGSN or similar node unaffected by the session for NIB or bearer set-up procedures.
  • an information container for example a PCO container
  • sending the PCO container transparently through any core network packet data support node, providing or having the functionality of an SGSN, to a core network packet data node having the functionality of a gateway packet data support node, for example a GGSN, hence leaving any SGSN or similar node unaffected by the session for NIB or bearer set-up procedures.
  • the method comprises the step of; initiating a new bearer context, for example requesting a secondary PDP context, during the new or current session in a core network node directly or according to rules received from a policy and/or service handling node or another external node by sending a PCO container containing parameters to be modified or updated, directly to the mobile user station leaving any SGSN unaffected, i.e. transparently through any GGSN.
  • a new bearer context for example requesting a secondary PDP context
  • the method comprises the step of initiating a new bearer context, for example requesting a secondary PDP context of the session by using existing messages towards a mobile user station.
  • BY existing messages are meant messages normally used in bearer as context creation response procedures .
  • the method may also comprise the steps of, upon changing from one, old, packet data support node to another, new , node of the same category, e.g. from one SGSN to another (ISRAU); providing a new support indication in the new node as to whether, or if, it supports NIB; distributing the (if any) new support indication to the nodes affected by the session subsequently; making a new decision in the respective affected nodes as to use NIB or not for the remainder of the new or current session.
  • an existing bearer can also be modified. It is possible to modify e.g. UL-TFT, GBR, MBR, QoS etc.
  • Fig. 1 is a block diagram of a system implementing the inventive concept according to a first embodiment
  • Fig. 2 is a schematical block diagram of a system in which the inventive concept is implemented according to a second embodiment
  • Fig. 3 is a sequence diagram illustrating the signalling sequence in a system as described with reference to Fig. 1,
  • Fig. 4 is a sequence diagram describing the procedure, in a system as in Fig. 1, when there is a change, or routing area update, from one SGSN to another,
  • Fig. 5 is a simplified sequence diagram describing the signalling in an implementation as described with reference to Fig. 2,
  • Fig. 6 is a flow diagram describing the procedure in an SGSN BS Manager upon occurrence of an activating event in the SGSN
  • Fig. 7 is a flow diagram describing the procedure upon occurrence of an activating event in a GGSN
  • Fig. 8A describes a procedure in a GGSN at reception of a rule installation message with a use indication from a PCRF
  • Fig. 8B describes a procedure in an SGSN at reception of a create PDP context response with a use indication from a GGSN
  • Fig. 9 describes a procedure in a GGSN at reception of a use indication from an external node to initiate NIB.
  • a solution is provided allowing for NIB capability negotiation among affected nodes in a network. If a mobile user station, e.g. a UE supports the NIB capability, it should indicate so for example in the primary PDP Context Activation procedure as part of the request message. Generally also the SGSN (except for embodiments as described for example with reference to Figs. 2 and 5) should provide a support indication (if it does support and/or does not support NIB, e.g.
  • GGSN should inform about its support to an external node, for example a PCRF as discussed above. If a GGSN provides a support indication to a PCRF, this inherently also includes information about the UE and the SGSN supporting
  • a UE (which has received no activating event) ) . If a UE has advertised that it supports NIB, it should normally get information back stating whether the rest of the affected or implicated nodes support NIB or not, or rather if NIB should be used for the current session.
  • Fig. 1 is a schematical block diagram describing an implementation of the inventive concept in a communication system according to a first embodiment. It should be clear that nodes that are not directly involved in the session as far as NIB is concerned as well as functions and means respective nodes that are not involved or affected, are not shown for reasons of clarity.
  • UE 10 comprises a bearer service manager (BS MGR) 11, for example as described in 3GPP TS 23.107.
  • the bearer managing means 11 communicates with a session handler 12 comprising a data structure with one or more PDP contexts. There may be different PDPs for different QoSs having the same IP address here M IP addresses wherein the session here is supposed to belong to, or have, IP address X.
  • the session handler 12 communicates with NIB support information means 14 also denoted information generating and distributing means, indicating if NIB is supported (or not) to the session handler 12 in communication with the bearer service managing means 11, wherein a NIB support indication
  • NIB support information means 14 can be said to be a data holding means connected one- to-one to the session handler IP CAN "object"; an "extracted” or “clarified” attribute for the NIB support flag.) If a positive NIB support indication is provided from UE 10, to SGSN 20 , also comprising a BS MGR 21, a session handler 22, PDP holding means 23 and NIB support information means 24, i.e. in SGSN 20 an activating event occurs, it is established also in SGSN 20 whether NIB is supported (or not) .
  • a NIB support indication is introduced and piggy-backed onto an existing, conventional message, particularly a create PDP context request for example as an information element which is forwarded by BS managing means 21 to BS managing means 31 of GGSN 30. Since this support indication acts as an activating event for GGSN 30, it is established in GGSN whether NIB is supported (or not) thereby by means of session handler 32, PDP holding means 33 and NIB support information means 34. If NIB is to be supported, a NIB support indication is included in, preferably, an existing message to be sent to bearer service manager 41 of, here, a PCRF 40.
  • PCRF 40 comprises network policy holding means 46, and decision means 45 for making a decision whether NIB can be used (or not), i.e. if NIB should be enabled or not for secondary bearers of the concerned new or current session. If yes, a NIB use indication is introduced in an existing message, here particularly a PCRF rule installation message, to be forwarded to the BS managing means 31 of GGSN 30. If a NIB use indication is received from PCRF 40, a decision is also made in GGSN decision means 35 to enable NIB based on the node configuration 26. A NIB use indication may then be forwarded to SGSN in an activate PDP context response and, in the decision means 25 of SGSN 20 it is established whether the NIB use indication should be forwarded. If yes, an activate PDP context response is provided to UE 10 including the use indication, i.e. the final decision. The decision whether to use NIB or not is now taken by all nodes in a consistent way.
  • a NIB use indication is
  • NIB indication is removed, for example a NIB flag is cleared in an IP CAN (Connectivity Access Network) session context.
  • IP CAN Connection Access Network
  • the NIB negotiation is then terminated and a NIB cannot be initiated in PCRF or GGSN.
  • PCRF or a similar node is optional, depending on implementation.
  • Fig. 2 is a block diagram similar to that of Fig. 1 describing another implementation.
  • the UE 1Oi corresponds to UE 10 of Fig. 1
  • GGSN 3Oi corresponds to GGSN 30 of Fig. 1
  • PCRF 4Oi corresponds to PCRF 40 of Fig. 1, therefore means and functions are denoted using the same reference numerals, but with an index 1.
  • PCO fields are used for activation and negotiation of NIB which means that SGSN is unaffected since a PCO container can be forwarded transparently by SGSN.
  • PCO is a transparent container forwarded by SGSN between UE and GGSN. If using the PCO concept, no mobility management procedures are affected by
  • the Protocol Configuration Option (PCO) field is an information element that is present in all SM (Session Management) messages such as Create PDP Context Request/Response, Modify PDP Context Request/Response and Delete PDP Context Request/Response.
  • the PCO IE Information Element
  • P-CSCF address Call Session Control Function
  • IMS Internet Multimedia Subsystem
  • DNS Domain Name Server
  • a PCO container is used as an explicit indication or information element in the SM procedure it can be used not only to indicate support for NIB but with advantage also to trigger an actual NIB in a most particular embodiment. Everything concerning NIB can be done without affecting SGSN at all, everything being handled between the UE and the GGSN normally residing in the Home PLMN
  • the UE 1Oi particularly indicates NIB (SNRPCA) , (Secondary Network Request for PDP Context Activation) capability in a PCO at a first (primary) PDP activation and GGSN 3Oi indicates, also in the PCO, back to the UE 1Oi which model to use, i.e. network initiated bearers or normal UE initiated bearers .
  • the GGSN 3Oi sends an indication together with essential parameters (UL-TFT (UpLink Traffic Flow Template) , DL-TFT (DownLink Traffic Flow Template) , QoS (Quality of Service) ) to the UE 10i, in a PCO using a GGSN initiated PDP Modification procedure.
  • UL-TFT UpLink Traffic Flow Template
  • DL-TFT DownLink Traffic Flow Template
  • QoS Quality of Service
  • the GGSN uses the PCO and the PDP modification procedure.
  • the PCO here contains an indication of "UL-TFT update" .
  • the maximum size of a PCO is 253 octets. If the size of the parameters in messages as discussed above would exceed that number, this can be handled in different manners.
  • the parameters, UL-TFT, DL-TFT, QoS can be compressed using a general scheme or a specific scheme. Alternatively a segmentation of the parameters may be done and multiple consecutive PDP context modification messages could be sent to the UE. Thus, in such embodiments any SGSN related procedures are completely unaffected by the introduction of NIB. It is an advantage that an operator can introduce NIB independently of any other operator.
  • NIB is a sequence diagram illustrating the embodiment as exemplified with reference to the block diagram in Fig. 1.
  • General for the embodiments is that the negotiation of the NIB support should be done the first time that an MS or a UE will establish a PDP context towards a GGSN for a specific APN (Access Point Name).
  • APN Access Point Name
  • a modification to the conventional PDP Context Activation procedure is done in order to advertise NIB support. It is supposed that an MS or a UE sends a Primary PDP Context Request to an SGSN, which includes a NIB support indication (if NIB supported) , 1. This can be done in different manners, it is possible to indicate NIB support only or NIB support or not NIB support or in some cases, however less plausible, it might be possible to only indicate that no NIB support is provided. This also applies for use indications .
  • the NIB support indication may be piggy-backed onto, or a new IE (Information Element) , in the messages used to activate the PDP contexts, Activate Primary PDP Context Request message towards SGSN according to 3GPP TS 23.060.
  • a NIB support indication is provided in an information element.
  • SGSN then creates a Create PDP Context Request message including an indication of the NIB support for both the SGSN and the UE (on condition that also SGSN supports NIB and a NIB support indication has been received from the MS), 2. This message is sent to GGSN which processes the message and realizes that it is a new (primary) PDP context establishment.
  • GGSN If also GGSN supports NIB, it adds an indication relating to NIB support for GGSN, but inherently also for MS, and SGSN, in a new PDP context indication to PCRF, 3. In this case it is PCRF that makes a decision as to whether NIB should be used or not and communicates a NIB use indication in e.g. a PCC (Policy Control and Charging) Rule installation to GGSN, 4. GGSN may then include (possibly after a decision also made in GGSN) the NIB use indication in a Create PDP Context Request message sent to SGSN, 5.
  • PCC Policy Control and Charging
  • the signalling sequences 6-9 comprise conventional messages sent for Radio Access Bearer Set-up, 6, Invoke Trace, 7, Update PDP Context Request/Response, 8,9, which will not be further discussed herein.
  • the SGSN (possibly after making a decision) includes the NIB use indication in an Activate PDP Context Accept message to be sent to the MS, hence informing the MS about the final decision, 10.
  • the NIB negotiation is handled by PCRF.
  • the NIB negotiation is handled by GGSN which means that PCRF is not involved and steps 3,4 referred to above do not need any NIB negotiation support.
  • a new SGSN should inform other affected nodes (affected by NIB) (i.e. directly only one other affected node) whether it can support NIB (or not) .
  • an MS (or a UE) starts an ISRAU procedure, 21. This is not further described since it corresponds to known, conventional ISRAU signalling.
  • the new SGSN then sends an update PDP Request to GGSN wherein, if NIB is supported by the new SGSN, an SGSN NIB support flag or NIB support indication is provided in an information element included in the update PDP Request, 22.
  • GGSN sends an update session to PCRF possibly with an indication as to NIB support, 23.
  • the new, updated decision is then forwarded to the rest of the nodes (subsequently, node by node) participating in the PDP context operations, namely GGSN, SGSN and MS, first as an Update Session Acknowledgment with an indication as to use or not to use NIB from PCRF to GGSN, 25, as an Update PDP Context Response with an indication as to use NIB or not from GGSN to the new SGSN, 26, and finally as an Update PDP Context Response with an indication as to use NIB or not from the new SGSN to the UE, 27, which returns an update PDP Context Response, 28 , to the new SGSN.
  • the ISRAU procedure is then finalized or stopped, 29. This serves the purpose of keeping the network updated as to whether NIB is supported or not also when there is a change of SGSNs. It should be noted that such a procedure is not required if a PCO is used for indicating NIB support and use.
  • a change procedure is thus provided amongst the nodes affected by the NIB procedure which assures a common up-to-date knowledge among the nodes as to whether NIB is supported or not.
  • a NIB support indication is provided at starting a first or a primary bearer, and at e.g. ISRAU. By using it, all the affected nodes will have the knowledge of whether the NIB procedure is used all the time and then of how they should behave.
  • Fig. 5 is a simplified sequence diagram describing the messaging in an implementation based on the use of a PCO for support/use indication. It is here supposed that an MS sends an activate primary PDP context request with a PCO including a NIB support indication (if NIB is supported) to an SGSN, l f , which transparently forwards a create PDP context request with the PCO containing the NIB support indication to GGSN, 2 ' . GGSN sends a new PDP context indication with the PCO with a NIB support indication (on condition that also GGSN supports NIB) to PCRF, 3 f . PCRF sends a PCC rule installation as in Fig.
  • GGSN sends a PDP context response with a NIB use indication in the PCO, on condition that GGSN decided that NIB should be used, to SGSN, 5 f , which simply creates an activate PDP context accept including the PCO with the NIB use indication to the MS, 10'.
  • Steps 6-9 are not illustrated since they correspond to the steps of Fig. 3, in order to make the transparency in the SGSN more clear.
  • Figs. 6, 7, 8A, 8B describe how the NIB indication, particularly the NIB flag, is negotiated such as to be consistent in all nodes, namely an SGSN (Fig. 6) , a GGSN (Fig. 7) and PCRF (SGSN and GGSN respectively, Fig. 8A, 8B) .
  • Fig. 6 it is supposed that an activate PDP context request is received in SGSN from a UE, 100. It is then examined whether the request message comprises a NIB support indication, 101. If not, an IP CAN session is created and a PDP, if it does not already exist, and a create PDP context request are forwarded to GGSN.
  • the NIB flag is set to "No" in the IP CAN session.
  • NIB support is here not indicated which means that for the session NIB will not be implemented, 102A. If however a NIB support indication is included in the activate PDP context message from the UE, it is examined if NIB is enabled in the SGSN node configuration, 102. If not, it is proceeded with step 102A described above. If NIB is enabled in the node itself also, it is established if there exists an IP CAN session for the IP address/APN, 103.
  • an IP CAN session and a PDP are created and a create PDP context request including a NIB support indication is forwarded to GGSN, 103A.
  • the NIB flag in the NIB support information means (the IP CAN session context) is set to "Yes", (it is preliminary since it is not known whether all subsequent nodes support NIB) .
  • the activation request has to be a secondary PDP context request which should not be used in NIB negotiation, or if NIB is used, since it comes from the UE node. Therefore the incoming PDP context request is to be rejected, 104, since it is not a primary PDP context activation request and it is not the first request for the particular IP address.
  • Fig. 7 is a flow diagram similar to that of Fig. 6 but for a GGSN and the procedure particularly mainly takes place in the BS managing means.
  • a create PDP context request is received in GGSN from SGSN concerning a particular IP address, 200. It is then established whether there is a NIB support indication included in the message, 201. If not, an IP CAN session is created and the NIB flag in the IP CAN session is set to "No" and a PDP is created, if it does not already exist. The new PDP context indication is forwarded to PCRF.
  • NIB support is hence not indicated in the message, 201A.
  • NIB support indication included in the message, it is established if NIB ia enabled in the node configuration of the GGSN itself, 202. If not, it is proceeded with step 201A as described above. If however NIB is enabled in GGSN, it is established if it already exists an IP CAN session for the particular IP address or APN, 203. If not, an IP CAN session and a PDP are created and a new PDP context indication is forwarded to the PCRF; NIB support is indicated in the message and the NIB flag is set to "Yes" in the NIB support information means (IP CAN session context), 203A.
  • the create PDP context is a secondary- create PDP context request which is not used in NIB mode, cf. step 104 of Fig. 6.
  • the incoming PDP context request is hence rejected, 204.
  • Fig. 8B describes the corresponding, subsequent procedure in SGSN.
  • a create PDP context response is received from GGSN, 400. It is then examined if a NIB use indication is set, 401. If not, the NIB flag is cleared in the NIB support information means (IP CAN session context), i.e. it is set to "No" (if it was enabled in SGSN), 401A. If yes, as well as if not, i.e. in both cases an activate PDP context response is forwarded to the UE or mobile station using the same NIB indication as received in the message, 402. Thus information also has been provided to the mobile station or UE whether NIB should be implemented for the remainder of the session or not and all nodes will have the same consistent information. It should be clear that these flow diagrams do not cover the procedure when a PCO container is used, since then SGSN is unaffected, which however was more thoroughly described with reference to Fig. 5 above .
  • Fig. 9 is a flow diagram illustrating how a NIB indication can be used in GGSN to determine if a NIB is to be initiated. It is thus supposed that a rule installation or creation is received in GGSN from PCRF, 500. The IP CAN session is then examined to see if there is a PDP with the QoS class indicated in the rule, i.e. if there is a PDP matching the QoS class, 501. If not, it is examined if the NIB flag is set to "Yes" in the IP CAN session, 502; if yes, it is established whether a modification of existing PDP is needed, 501A; if yes, a modification of existing PDP is initiated, 501B.
  • step 501 If on the other hand, the outcome of the examination in step 501 was "No", an initiation of a new secondary PDP context with the QoS class indicated in the rule is started, 503. This can be done either using specific messages, a modified message from GGSN according to 3GPP TS 29.060 and SGSN to UE according to 3GPP TS 24.008, or alternatively using the PCO concept as described earlier.
  • the GGSN sends an indication together with the essential parameters UL-TFT, DL- TFT and Qos to the UE in a PCO using the GGSN initiated PDP modification procedure transparently for the SGSN.
  • step 501B if a service is to be added to an existing PDP GBR (Guaranteed Bitrate) and/or UL-TFT (the addresses in the filter) (and DL-TFT; which is locally adjusted in GGSN and hence need to be sent to UE) .
  • GBR is only- changed if it is a real-time service.
  • MBR Maximum Bitrate
  • the PCO concept can be implemented not only for the initiation procedure but also for the actual NIB initiation procedure where a secondary PDP context is initiated within GGSN or in PCRF or an application function communicating with the PCRF comprising a Proxy Call Session Control Function (P-CSCF) in the IMS. This does however not form part of the actual negotiation procedure .
  • P-CSCF Proxy Call Session Control Function

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention porte sur un système de communication prenant en charge une communication de données par paquets et comprenant un certain nombre de noeuds de réseau central (20, 30) capables de communiquer avec des noeuds de traitement de stratégies et/ou de services (40) et des stations utilisateurs mobiles (10) sur des réseaux d'accès radio. Les stations utilisateurs mobiles (10) et les noeuds de réseau central (20, 30) comprennent des moyens de gestion de services de porteuses respectifs (11;21;21). Les noeuds précités (10,20,30,40) sont conçus pour prendre en charge une configuration de porteuse déclenchée par réseau, les noeuds attribués par une session donnée étant conçus pour fournir, directement ou indirectement, à au moins l'un des autres noeuds, des informations indiquant s'ils prennent en charge ou non une configuration de porteuse initialisée par réseau (NIB) lorsqu'un événement déclenchant respectif particulier se produit. Les moyens de gestion des services de porteuse respectives des noeuds attribués par une nouvelle session sont conçus pour distribuer lesdites informations sur la prise en charge de la NIB par les noeuds respectifs, autorisant ainsi une procédure de négociation entre les noeuds (10,20,30,40) pour déterminer si la NIB doit être prise en charge ou non pendant la nouvelle session et si les informations sont cohérentes dans les noeuds (10,20,30,40).
PCT/EP2006/061980 2006-05-02 2006-05-02 SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL Ceased WO2007128343A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2006/061980 WO2007128343A1 (fr) 2006-05-02 2006-05-02 SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2006/061980 WO2007128343A1 (fr) 2006-05-02 2006-05-02 SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL

Publications (1)

Publication Number Publication Date
WO2007128343A1 true WO2007128343A1 (fr) 2007-11-15

Family

ID=37697941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2006/061980 Ceased WO2007128343A1 (fr) 2006-05-02 2006-05-02 SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L'ÉTABLISSEMENT D'UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL

Country Status (1)

Country Link
WO (1) WO2007128343A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100009690A1 (en) * 2008-06-17 2010-01-14 Qualcomm, Incorporated Managing network-initiated quality of service setup in mobile device and network
WO2010033872A3 (fr) * 2008-09-19 2010-05-06 Qualcomm Incorporated Qualité de service initialisée par réseau et dispositif mobile
WO2011162781A1 (fr) * 2010-06-21 2011-12-29 Qualcomm Incorporated Procédé et appareil pour le transfert de contextes de qos pendant un transfert entre technologies d'accès radio dans un système de communications sans fil
US8787172B2 (en) 2010-06-21 2014-07-22 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system
US8908636B2 (en) 2010-06-21 2014-12-09 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003030490A2 (fr) * 2001-09-27 2003-04-10 Nokia Corporation Procede et noeud de reseau pour assurer la securite dans un reseau d'acces radio
US20040071126A1 (en) * 2002-10-15 2004-04-15 Gabriel Ramos-Escano Method, network node and system for managing interfaces in a distributed radio access network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003030490A2 (fr) * 2001-09-27 2003-04-10 Nokia Corporation Procede et noeud de reseau pour assurer la securite dans un reseau d'acces radio
US20040071126A1 (en) * 2002-10-15 2004-04-15 Gabriel Ramos-Escano Method, network node and system for managing interfaces in a distributed radio access network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Impacts of mechanisms for operator controlled QoS in a GPRS IP-CAN", 3GPP TSG SA WG2 ARCHITECTURE - SA2#51, no. S2-060676, 13 February 2006 (2006-02-13) - 17 February 2006 (2006-02-17), Denver, USA, pages 1 - 5, XP007901698, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_51_Denver/Docs/> [retrieved on 20070208] *
ERICSSON: "Operator Controlled QoS", 3GPP TSG SA WG2 ARCHITECTURE - SA2#50, no. S2-060049, 16 January 2006 (2006-01-16) - 20 January 2006 (2006-01-20), Budapest, Hungary, pages 1 - 5, XP007901697, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_50_Budapest/Docs/> [retrieved on 20070208] *

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8204505B2 (en) 2008-06-17 2012-06-19 Qualcomm Incorporated Managing network-initiated quality of service setup in mobile device and network
KR101254055B1 (ko) * 2008-06-17 2013-04-15 퀄컴 인코포레이티드 모바일 통신 디바이스에 대한 리소스 할당 관리를 위한 방법들 및 장치들
WO2009155365A3 (fr) * 2008-06-17 2010-05-27 Qualcomm Incorporated Gestion d'établissement de qualité de service à l'initiative du réseau dans un dispositif et un réseau mobile
CN102067693A (zh) * 2008-06-17 2011-05-18 高通股份有限公司 管理移动装置和网络中网络起始的服务质量设定
US20100009690A1 (en) * 2008-06-17 2010-01-14 Qualcomm, Incorporated Managing network-initiated quality of service setup in mobile device and network
JP2011524726A (ja) * 2008-06-17 2011-09-01 クゥアルコム・インコーポレイテッド モバイルデバイスとネットワークにおいてネットワーク始動のサービス品質セットアップを管理すること
RU2476029C2 (ru) * 2008-09-19 2013-02-20 Квэлкомм Инкорпорейтед Качество обслуживания, инициированное сетью и мобильным устройством
CN102160450A (zh) * 2008-09-19 2011-08-17 高通股份有限公司 网络和移动设备发起的服务质量
WO2010033872A3 (fr) * 2008-09-19 2010-05-06 Qualcomm Incorporated Qualité de service initialisée par réseau et dispositif mobile
US9094943B2 (en) 2008-09-19 2015-07-28 Qualcomm Incorporated Network and mobile device initiated quality of service
CN102160450B (zh) * 2008-09-19 2016-05-04 高通股份有限公司 网络和移动设备发起的服务质量
WO2011162781A1 (fr) * 2010-06-21 2011-12-29 Qualcomm Incorporated Procédé et appareil pour le transfert de contextes de qos pendant un transfert entre technologies d'accès radio dans un système de communications sans fil
US8787172B2 (en) 2010-06-21 2014-07-22 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system
US8908636B2 (en) 2010-06-21 2014-12-09 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system
US9344947B2 (en) 2010-06-21 2016-05-17 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system
US9924402B2 (en) 2010-06-21 2018-03-20 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system

Similar Documents

Publication Publication Date Title
KR100879811B1 (ko) 이동전화가 발신하는 호출들에서 안내들을 제공하는 기술
US8787313B2 (en) Method, network system and destination network for transmitting QoS during a handover process between systems
EP1620979B1 (fr) Procede, systeme et element de reseau pour l&#39;autorisation d&#39;une transmission de donnees
CN100488284C (zh) 一种3gpp演进网络中漫游用户数据路由优化方法
US8532033B2 (en) Selective RAB assignment
US7525938B2 (en) Session control in a communication system
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
US20100182953A1 (en) Method for informing home subscriber server of storing packet data network gateway address information
AU2002246300A1 (en) Technique for providing announcements in mobile-originated calls
CN108366380A (zh) 一种支持多归属协议数据单元会话的策略控制方法及装置
EP3549314B1 (fr) Mise en oeuvre qos opportuniste
CN101577970B (zh) 一种无线资源释放的方法
US7436827B2 (en) Data bearers in a communication system
CN100471329C (zh) 一种核心网感知用户端接入类型的方法及系统
CN101351053A (zh) 动态业务流的处理方法
WO2007128343A1 (fr) SYSTÈME, APPAREIL ET PROCÉDÉ PERMETTANT de NÉGOCIER L&#39;ÉTABLISSEMENT D&#39;UNE PORTEUSE DÉCLENCHÉE PAR RÉSEAU DANS UN RÉSEAU SANS FIL
CN105580425A (zh) 用于数据连接的按需QoS
US8295269B1 (en) Technique for informing network of voice traffic
CN101137203A (zh) 建立用户平面的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06754956

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06754956

Country of ref document: EP

Kind code of ref document: A1