WO2008074782A1 - Support d'urgence dans un système de communication - Google Patents

Support d'urgence dans un système de communication Download PDF

Info

Publication number
WO2008074782A1
WO2008074782A1 PCT/EP2007/064081 EP2007064081W WO2008074782A1 WO 2008074782 A1 WO2008074782 A1 WO 2008074782A1 EP 2007064081 W EP2007064081 W EP 2007064081W WO 2008074782 A1 WO2008074782 A1 WO 2008074782A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
bearer
emergency
data
user equipment
Prior art date
Application number
PCT/EP2007/064081
Other languages
English (en)
Inventor
Jani R. Manninen
Marko Akselin
Asko Haapapuro
Original Assignee
Nokia Corporation
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 Nokia Corporation filed Critical Nokia Corporation
Publication of WO2008074782A1 publication Critical patent/WO2008074782A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present invention generally relates to emergency support in a communication system.
  • the present invention relates to handling of emergency data in a packet-switched domain of a communication system, especially an evolved mobile communication system.
  • Universal Mobile Telecommunication System UMTS is dealt with and promoted, among others, by the Third Generation Partnership Project (3GPP) .
  • 3GPP Third Generation Partnership Project
  • IMS IP Multimedia Subsystem
  • CS circuit-switched
  • PS packet-switched
  • emergency scenarios i.e. situations in which a user (or user equipment) is in an emergency and thus needs to initiate an emergency call, naturally represent a topic inherent in the framework of a communication systems. Therefore, concepts for providing emergency services are also under consideration for recent standardization approaches .
  • IP multimedia subsystem IMS concepts for providing emergency services (emergency sessions) are defined in the technical specification "3GPP TS 23.167, V7.2.0" of September 2006. In this regard, it is defined that a user equipment being capable of circuit-switched connections shall use the CS domain for emergency services. That is, according to existing systems
  • a user equipment is assumed to effect an emergency network access using the CS domain.
  • a proxy call state control function P-CSCF shall use policy and charging control procedures to ensure that the use of bearer resources in a connectivity network is for emergency services only, thus enforcing a valid usage of emergency bearer resources.
  • This improvement has been submitted as change request "23.167 CR 0046" at the 3GPP TSG-SA WG2 meeting on October 23-27, 2006 (document no. S2-063774) .
  • Fig. 1 of the attached drawings there is shown a schematic overview of a conventional communication system according to current IMS specifications. It can be gathered from Fig. 1 that a terminal equipment, hereinafter referred to as user equipment UE, is connected with an IMS network via an IP-Connectivity Access Network (IP-CAN) .
  • IP-CAN IP-Connectivity Access Network
  • the connection between UE and IMS may be considered to be based on a bearer.
  • the IP-CAN part including both CS and PS domains or only a PS domain, represents a collection of network entities and interfaces providing an underlying IP transport connectivity between the UE and IMS entities.
  • IP-Connectivity Access Network General Packet Radio Service GPRS may be mentioned.
  • the UE Via the IP- CAN the UE is connected with a proxy call state control function P-CSCF of the IMS network.
  • the P-CSCF is connected with a serving call state control function S-CSCF and an emergency call state control function E- CSCF.
  • the P-CSCF is responsible for detecting a request for an emergency service (emergency session) and for forwarding the emergency request to the E-CSCF.
  • the E-CSCF is responsible for routing the emergency request to an emergency center, e.g. public safety answering point
  • Such a routing may be accomplished by means of location information and additional other information in the emergency request, e.g. type of emergency service.
  • the communication between user equipment UE and IMS network is effected on a single connection, and is directed to a single proxy node P- CSCF. That is, both voice/data calls of conventional communication services and dedicated calls of emergency services have the same target address, i.e. the same P- CSCF address.
  • the above object may for example be accomplished by a method of data flow filtering.
  • this could particularly comprise a method of emergency data flow filtering to a dedicated emergency bearer.
  • this could particularly comprise a method of emergency access triggering based on flow filtering, wherein an accordingly filtered emergency data flow may be directed to a dedicated emergency bearer after emergency access is completed.
  • the above object may for example be accomplished by an apparatus (or user equipment) for data flow filtering, exemplarily for emergency data flow filtering to a dedicated emergency bearer and/or for emergency access triggering based on flow filtering, wherein an accordingly filtered emergency data flow may be directed to a dedicated emergency bearer after emergency access is completed.
  • an apparatus or user equipment for data flow filtering, exemplarily for emergency data flow filtering to a dedicated emergency bearer and/or for emergency access triggering based on flow filtering, wherein an accordingly filtered emergency data flow may be directed to a dedicated emergency bearer after emergency access is completed.
  • the above object may for example be accomplished by a system comprising an apparatus (or user equipment) according to an aspect of the present invention.
  • the above object may for example be accomplished by a computer program, circuit arrangement or the like for carrying out a method according to an aspect of the present invention and/or for operating an apparatus (or network element) according to an aspect of the present invention to carry out the respective method/s.
  • Embodiments of the present invention allow an apparatus such as a user equipment or network element to distinguish normal calls (e.g. normal IMS VoIP calls) and emergency calls (e.g. emergency VoIP calls). Thereby, it may be facilitated to filter/direct a respective call to a respectively dedicated bearer, e.g. to filter/direct an emergency VoIP call to a dedicated emergency SAE bearer.
  • the bearer may already be assigned to the apparatus or may be assigned upon demand.
  • Embodiments of the present invention are for example applicable to use cases with legacy restrictions between a modem and an application. Such legacy restrictions could for example exist in a case where the application, e.g. IMS application, is located in an external device, e.g. personal computer or the like, which is connected to and uses the modem for network connection. Another exemplary case could be that the application is located within the modem, and an IP socket interfaces is used between the application and the modem functions.
  • Embodiments of the present invention provide a solution to the above problems and drawbacks, which are both easy to implement and to incorporate into existing systems.
  • embodiments of the present invention basically relate to (cellular) radio access and to procedures of layer 2 (according to the ISO OSI reference model) , especially in an environment of SAE/LTE/EUTRAN systems.
  • aspects of the present invention may include one or more of the following properties:
  • a traffic flow template or flow filter for an emergency case i.e. an emergency TFT
  • an emergency TFT a traffic flow template or flow filter for an emergency case
  • FIG. 1 shows a schematic overview of a conventional communication system
  • Fig. 2 shows a schematic overview of a communication system according to an embodiment of the present invention
  • Fig. 3 shows a flow chart of a method according to an embodiment of the present invention
  • Fig. 4 shows a signaling diagram of a method according to an embodiment of the present invention
  • Fig. 5 shows a schematic block diagram of an apparatus according to an embodiment of the present invention, which is adapted for acting as a user equipment, and
  • Fig. 6 shows a schematic block diagram of an apparatus according to another embodiment of the present invention, which is adapted for acting as a user equipment.
  • the present invention is described in relation to an example of 3GPP network specifications, especially to SAE, LTE and/or EUTRAN network concepts.
  • an emergency service is taken as an example for the subsequent description.
  • the description of the embodiments given herein specifically refers to terminology which is directly related thereto. Although the present invention is particularly beneficial for deployment in such systems, such terminology is only used in the context of the presented examples, and does not limit the invention in any way.
  • the present invention is based on the assumption that separate bearers may exist for different kinds of calls/requests. Namely, it is assumed that a dedicated emergency (SAE) bearer for emergency services may exist separately from a default (SAE) bearer for communication services.
  • SAE dedicated emergency
  • a dedicated emergency bearer may be assigned to a user equipment either preemptively during network attachment in parallel with a default bearer, or preemptively after network attachment and default bearer assignment, or on an on-demand basis after network attachment and default bearer assignment.
  • the user equipment receives from a network side, among others, a traffic flow template (TFT) for an emergency service.
  • TFT traffic flow template
  • a data flow may be filtered to a dedicated bearer and a network connection using said bearer may be initiated.
  • Fig. 2 shows a schematic overview of a communication system according to an embodiment of the present invention .
  • a communication system differs from the conventional one according to Fig. 1 in that a user equipment UE has two connections with an IMS network which represents an example for any conceivable application network.
  • the user equipment is connected with a proxy call state control function P-CSCF via a connection using a default bearer, e.g. a default SAE bearer (including radio bearer part and access bearer part) .
  • the P-CSCF is connected with a serving call state control function S- CSCF, and is responsible for handling communication traffic, e.g. IMS VoIP calls, from/to the user equipment UE.
  • the user equipment is connected with an emergency proxy call state control function EP-CSCF, which is an example for a dedicated special-purpose P- CSCF, using an emergency bearer, e.g. an IMS emergency SAE bearer (including radio bearer part and access bearer part) .
  • the EP-CSCF is connected with an emergency call state control function E-CSCF, and is responsible for handling dedicated special-purpose traffic, e.g. IMS emergency calls, from/to the user equipment UE.
  • the EP- CSCF is aware, for example by utilizing a location retrieval function LRF (not shown) , which E-CSCF serves the location of the user equipment, which in case of a mobile user equipment such as a mobile phone may vary.
  • LRF location retrieval function
  • emergency traffic/data from the user equipment UE may be routed via the EP-CSCF and an appropriate E- CSCF to an emergency center, e.g. public safety answering point PSAP, or a breakout gateway control function BGCF (not shown in Fig. 2) .
  • an emergency center e.g. public safety answering point PSAP, or a breakout gateway control function BGCF (not shown in Fig. 2) .
  • the responsibility for handling emergency requests has been transferred from a general-purpose P-CSCF to a special-purpose EP-CSCF.
  • the user equipment here has two connections, i.e. two separate bearers, as an interface with an IMS network via an IP- CAN network.
  • the user equipment during initial network access receives two P-CSCF addresses from the network; one for IMS communication traffic/data, i.e. that of the P-CSCF, and one for emergency IMS traffic/data, i.e. that of the EP-CSCF.
  • the user equipment during initial network access receives traffic flow templates TFT from the network.
  • traffic flow templates TFTs may be provided, one for each bearer, i.e. one for each service or call type.
  • a traffic flow template TFT as used herein constitutes a currently specified implementation example of a mapping of traffic/data to a secondary packet data protocol (PDP) context in case of more than one PDP context being associated with a single PDP address.
  • PDP packet data protocol
  • a traffic flow template includes packet filters and corresponding filter parameters, it may be utilized for data flow filtering purposes.
  • any other means shall also be covered thereby, which is suitable for traffic/context mapping and/or traffic flow filtering.
  • a dedicated emergency bearer may be assigned to the user equipment during network attachment in parallel with the default bearer, or preemptively after network attachment and default bearer assignment, or on an on-demand basis after network attachment and default bearer assignment.
  • the user equipment in IDLE state i.e. after network attachment, may thus already have an emergency bearer assigned and consequently also a traffic flow template for an emergency service.
  • the emergency TFT may be used as an emergency flow filter at the user equipment side, as it has a one-to-one mapping between emergency bearer and EP-CSCF address.
  • the user equipment in IDLE state i.e. after network attachment, has a traffic flow template for an emergency service, i.e. an emergency TFT, and may not yet have an emergency bearer assigned may, but only at least one for a communication service.
  • the user equipment may though be aware of the fact that an emergency bearer is to be assigned on- demand, i.e. when an emergency call is to be initiated.
  • the network may assign the emergency bearer either based on an emergency access request or based on emergency data sent on a default bearer.
  • an emergency call would have to be started on a default bearer , an emergency TFT would be available (that is, it needs to be available prior to network access and it may be replaced with a new one as assigned together with a dedicated emergency bearer setup during network access), and the emergency TFT having a one-to- one mapping between the newly assigned emergency bearer and the EP-CSCF address would be used to continue the emergency call via the emergency bearer. Details of the above-mentioned cases will be described herein below.
  • flow filtering at the user equipment is performed by using a type of a (SAE) bearer contained in respective flow filters, e.g. respective traffic flow templates.
  • SAE a type of a
  • an IMS emergency bearer is used.
  • an identification of an appropriate TFT may be based on a target address of traffic/data concerned.
  • an emergency TFT may be identified to be the appropriate TFT if an IP packet with the address of the EP-CSCF is processed.
  • a TFT may be identified as an emergency TFT for example on the basis of a TFT type contained therein or a TFT container in a NAS PDU, i.e.
  • a non-access stratum packet data unit with which the traffic flow template is supplied from the network to the user equipment.
  • a respective access request to a control plane entity of the user equipment may be triggered by use of a respective flow filter, e.g. traffic flow template.
  • a respective flow filter e.g. traffic flow template.
  • an emergency access request may be triggered to a mobility management (MM) layer, in case of a GPRS-based IP-CAN to a GMM layer, and further to a radio resource control (RRC) layer.
  • MM mobility management
  • RRC radio resource control
  • only one emergency flow filter e.g. one emergency traffic flow template
  • a new flow filter e.g. traffic flow template
  • the current one is to be replaced with the new one in order to maintain consistency in flow filtering.
  • a state of the user equipment changes, e.g. from (LTE) ACTIVE to (LTE) IDLE, or when a dedicated bearer such as an emergency (SAE) bearer is released
  • SAE emergency
  • the address of the emergency proxy node EP-CSCF as well as the flow filters, e.g. traffic flow templates, will be updated, either periodically and/or if required (i.e. dynamically) , so that the user equipment always has a matching flow filter (or TFT) to the current EP-CSCF address .
  • Fig. 3 shows a flow chart of a method according to an embodiment of the present invention. The thus illustrated method may be performed at a user equipment of a system configuration according to Fig. 2.
  • step Sl of Fig. 3 traffic data in the exemplary form of an IP packet is received at a flow filtering unit of the user equipment UE.
  • the IP data may originate from upper layers, e.g. from the application layer e.g. implementing IP multimedia (IMS) services.
  • the IP data may originate either from an application unit within the user equipment, e.g. using an IP socket procedure, or from an application unit outside of the user equipment, e.g. in a processing device (personal computer, desktop computer, laptop computer, etc.) connected with the user equipment, for which the user equipment serves as a (LTE-capable) modem for network connection .
  • a processing device personal computer, desktop computer, laptop computer, etc.
  • step S2 of Fig. 3 a bearer for transmitting the received IP data via the network is determined, and in step S3 of Fig. 3, a network connection for transmitting the IP data using the bearer determined in step S2 is initiated.
  • a network access cause for the data to be transmitted is specified, wherein the bearer is determined in a second step S2-2 on basis of the specified network access cause.
  • Specifying a network access cause comprises a step S2-1-1, in which a target (IP) address of the IP data is compared with flow filters, e.g. traffic flow templates, available at the user equipment UE. Subsequently, in step S2-1-2, a flow filter, e.g. traffic flow template, with which the target address of the data matches, is identified to be appropriate.
  • IP target address of the IP data
  • flow filters e.g. traffic flow templates
  • an emergency TFT does not have a network access cause (which may also be referred to as setup cause or establishment cause) as a parameter, but the flow filtering process may request emergency access by identifying the TFT as emergency TFT and knowing that this TFT requires priority access.
  • the target address of the IP data is the EP-CSCF address, thus an emergency TFT is identified to be the appropriate TFT, i.e. YES in step
  • step S2-1-2 That is, the network access cause is specified to be (IMS) emergency. Accordingly, the process advances to step S2-2, in which an emergency bearer is determined as the bearer for transmitting the emergency IP data.
  • IMS IMS
  • step S2-1-2 i.e. normal IP communication data to be handled by a default TFT (network access cause is not (IMS) emergency)
  • TFT network access cause
  • IMS network access cause
  • step S3 to which the process advances after bearer determination, i.e. emergency bearer determination, network connection initiation according to the illustrated embodiment is performed by mapping the IP data to the determined emergency bearer (S3-1), and by triggering an emergency access request to the network (i.e. IP-CAN, e.g. eNB/aGW) (S3-2), which indicates the determined emergency bearer to be used for the network connection.
  • emergency access request may be considered to comprise cell association to a network element with radio resource management functionality and a layer 3 registration to a network element with mobility management functionality (cf . Fig. 4) .
  • a target address of data to be transmitted is associated with a certain bearer and/or a certain network access cause.
  • Fig. 4 shows a signaling diagram of a method according to an embodiment of the present invention.
  • a user equipment UE is exemplarily split up in several entities representing different functions and/or layers. Namely, a packet data convergence protocol entity denoted by PDCP, which may - but is not required to - exemplarily represent a flow filtering unit of a user plane of the user equipment, and a mobility management entity denoted by MM and a radio resource control entity denoted by RRC exemplarily represent a control plane of the user equipment.
  • PDCP packet data convergence protocol entity
  • MM mobility management entity
  • RRC radio resource control entity
  • the user equipment represented by PDCP, MM and RRC is connected with a network element denoted by eNB (abbreviation for evolved Node_B, i.e. a network element having radio resource management functionality) , which in turn is connected with a gateway node denoted by aGW (abbreviation for access gateway, i.e. a network element having mobility management functionality.
  • eNB abbreviation for evolved Node_B, i.e. a network element having radio resource management functionality
  • GW abbreviation for access gateway, i.e. a network element having mobility management functionality.
  • FIG. 4 schematically illustrates a system according to an embodiment of the present invention, wherein such a system may comprise a combination of UE (PDCP, MM, RRC) and eNB as well as a combination of UE (PDCP, MM, RRC) and eNB and aGW.
  • the user equipment has completed its network attachment, has been assigned a default (SAE) bearer, and has not yet been assigned an emergency (SAE) bearer, but has available an emergency flow filter (e.g. emergency TFT) .
  • SAE safety bearer
  • SAE emergency bearer
  • an emergency flow filter e.g. emergency TFT
  • step S400 of Fig. 4 the PDCP receives IP data having a target IP address to the emergency proxy node EP-CSCF. That is, the IP data represents emergency application data.
  • the user equipment in particular the PDCP, performs a traffic flow filtering procedure in step S401.
  • the PDCP first checks IP headers (including target address) against flow filters and, if a matching IMS emergency flow filter is found, then requests emergency access.
  • this traffic flow filtering may be represented by steps S2 and S3 of Fig. 3, thus resulting in the triggering of an emergency access request.
  • the UE or PDCP requests connection establishment from MM, while indicating emergency information for example as a network access cause or some indication specified for that purpose (step S402) .
  • the MM then starts a network connection setup, i.e. a transition from (LTE) IDLE state to (LTE) ACTIVE state, by requesting connection from RRC, while indicating emergency information for example as a network access cause or some indication specified for that purpose (step S403) .
  • the RRC executes a CELL ASSOCIATION procedure, again with emergency access indication in order to ensure a prioritized handling of this procedure by the network (i.e. eNB and aGW, for example) .
  • the MM gets an intermediate indication about connection establishment proceeding in the form of a confirmation message from the RRC entity.
  • a service request message requesting emergency service is transmitted from the network element eNB to the network element aGW in the exemplary form of a NAS PDU (non-access stratum packet data unit) .
  • the network element aGW responds in step S406 by generating and sending a NAS response is generated in aGW to the network element eNB.
  • the NAS response is affirmative in that the requested service is indicated to be accepted.
  • the UE in particular the RRC entity thereof, receives a NAS PDU with an indication of service acceptance, which is forwarded in step S408 from the RRC entity to the MM entity by means of a message representing a response to the preceding service request.
  • the MM entity In response to the affirmative service request response, the MM entity effects a transition of the user equipment from (LTE) IDLE state into (LTE) ACTIVE state. In step S409, the MM indicates to the PDCP that the UE has been transferred to ACTIVE state. Thenceforward, the user equipment is able to establish a network connection using a (SAE) bearer.
  • SAE SAE
  • the emergency data is first sent on the previously assigned default (SAE) bearer.
  • SAE policy control and rules function
  • PCRF policy control and rules function
  • UPE user plane entity
  • an emergency (SAE) bearer already exists in step S409 of Fig. 4.
  • the emergency data is sent on that dedicated emergency (SAE) bearer .
  • the PDCP entity of the user equipment may continue with processing data transmission by applying the emergency TFT to the user emergency data.
  • the IP emergency data is transmitted from the user equipment towards the EP-CSCF (not shown in Fig. 4) specified as target address using the assigned emergency bearer (step S410 of Fig. 4) .
  • step S401 of Fig. 4 is for specifying a network access cause, thus ensuring a proper handling of emergency data, since the interface between upper layers including an application layer and the PDCP entity is a true IP interface.
  • the PDCP entity can not handle additional parameters (other than those contained in the IP header, as for example target address) , like access cause, which thus have to be determined and provided by the PDCP itself.
  • FIG. 5 shows a schematic block diagram of an apparatus according to an embodiment of the present invention, which is adapted for acting as user equipment UE in the above sense.
  • An apparatus or user equipment comprises a user plane part and a control plane part.
  • the user plane comprises a flow filtering unit which is configured to perform flow filtering according to steps S2 and S3 of Fig. 3 and/or according to step S401 of Fig. 4.
  • the flow filtering unit comprises a bearer determination unit configured to perform bearer determination according to step S2 of Fig. 3 and a connection initiating unit configured to perform network connection initiation according to step S3 of Fig. 3.
  • the flow filtering unit is connected with a traffic handling unit which is for example configured to manage P-CSCF addresses (including a current EP-CSCF address) and to manage flow filters including maintaining a single updated flow filter or traffic flow template.
  • PDCP packet data convergence protocol
  • the PDCP unit according to Fig. 4 in particular the flow filtering unit thereof, is further connected with an application unit of the present apparatus or user equipment.
  • the application unit accommodates upper layers (e.g. above layer 2), and is for example configured to generate IMS application data including IMS emergency data for transmission over a network.
  • the user plane of the present apparatus or user equipment is connected with the control plane, in particular a mobility management unit MM thereof.
  • the mobility management unit MM is connected with a radio resource control unit RRC of the control plane, which in turn constitutes an external interface of the apparatus or user equipment UE.
  • RRC radio resource control unit
  • the apparatus or user equipment, in particular the RRC unit thereof is connected with a network element such as an evolved Node B.
  • Fig. 5 The interactions and messages between the individual units and entities depicted in Fig. 5 may be gathered from the diagrams of Figs. 3 and 4. Such a processing is particularly applicable when the interface between the application unit and the flow filtering unit is based on IP socket.
  • Fig. 6 shows a schematic block diagram of an apparatus according to another embodiment of the present invention, which is adapted for acting as user equipment UE in the above sense.
  • the present embodiment according to Fig. 6 essentially differs in that the application unit is not located in the apparatus or user equipment, but outside thereof.
  • the application unit which accommodates upper layers (e.g. above layer 2) and is for example configured to generate IMS application data including IMS emergency data for transmission over a network, is located at a personal computer PC.
  • a personal computer PC is only one non-limiting example for external devices connected to the UE, where the application unit may be located. Rather, it may be located in any external device which is connected to the UE, and which uses the UE as modem for network access.
  • the information about the second proxy node address i.e. the address of the emergency proxy node EP-CSCF, has to be forwarded to the application unit.
  • the application unit is enabled to define the EP-CSCF address as the target address of IP emergency data, thus allowing a proper flow filtering thereof according to embodiments of the present invention at the apparatus or user equipment according to Fig. 6.
  • Fig. 6 The interactions and messages between the individual units and entities depicted in Fig. 6 may be gathered from the diagrams of Figs. 3 and 4. Such a processing is particularly applicable when the application unit requests emergency access for emergency data from the apparatus or user equipment serving as a modem.
  • the present invention is not limited to devices and/or systems with this denomination. Rather, these terms merely serve for illustrative purpose.
  • the present invention and all its aspects and options may as well be applied to any other terminal equipment and network elements providing similar or equivalent functions, regardless of their denominations.
  • the present invention as a matter of course also covers respective network elements exemplarily eNB and respective access gateway elements aGW, which are adapted to cooperate with the illustrated user equipments UE in order to implement the illustrated methods.
  • respective functional elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • method steps and functions likely to be implemented as software code portions and being run using a processor at one of the entities are software code independent and can be specified using any known or future developed programming language such as e.g. Java, C++, C, and Assembler.
  • Method steps and/or devices or means likely to be implemented as hardware components at one of the entities are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS, CMOS, BiCMOS, ECL, TTL, etc, using for example ASIC components or DSP components, as an example.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to those skilled in the art.
  • a communication device or terminal may for example be any device by means of which a user may access a network and/or a server of such network; this implies mobile as well as non-mobile devices and networks, independent of the technology platform on which they are based; only as an example, it is noted that terminals operated according to principles standardized by the 3 rd Generation Partnership Project 3GPP and known for example as UMTS terminals (Universal Mobile Telecommunication System) are particularly suitable for being used in connection with the present invention, nevertheless terminals conforming to standards such as GSM (Global System for Mobile communications) or IS-95 (Interim Standard 95) may also be suitable;
  • GSM Global System for Mobile communications
  • IS-95 Interim Standard 95
  • networks referred to in this connection may comprise mobile and fixed network sections independent of the type of technology on which the networks are operated, for example those networks operate on the basis of the Internet Protocol IP, independent of the protocol version (IPv4 or IPv6), or on the basis of any other packet protocol such as User Datagram Protocol UDP, etc.
  • IP Internet Protocol
  • IPv4 or IPv6 protocol version
  • UDP User Datagram Protocol
  • - devices can be implemented as individual devices, devices may also be implemented as a module configured to accomplish interoperability with other modules constituting an entire apparatus, e.g. a module device may be represented as a chipset or chip card e.g. insertable and/or connectable to an apparatus such as a mobile phone, or a module may be realized by executable code stored to a mobile phone or other device for execution upon invocation.
  • a module device may be represented as a chipset or chip card e.g. insertable and/or connectable to an apparatus such as a mobile phone, or a module may be realized by executable code stored to a mobile phone or other device for execution upon invocation.
  • the present invention generally also comprises respective computer programs as well as circuit arrangements for carrying out the aspects of the method/s and/or for operating hardware to carry out the aspects of the above method/s.
  • a flow filtering uses traffic flow templates to determine an access reason (e.g. emergency), when a transition from
  • IDLE state to ACTIVE state is needed at a user equipment.
  • traffic flow templates are provided to the user equipment by the network.
  • an emergency TFT is always available at the user equipment.
  • a data flow e.g. emergency data flow
  • a dedicated bearer e.g. emergency bearer
  • a traffic flow template i.e. a flow filter
  • the control plane of the user equipment is able to establish a connection and to put the user equipment in ACTIVE state for an emergency session.
  • a flow filtering unit (which may exemplarily be represented by a PDCP, or a layer on top of a PDCP or any kind of adapter) is used to detect a target address based on a traffic flow template, when the user equipment tries to access an emergency node.
  • the flow filtering unit or the PDCP requests a connection from a mobility management unit MM of the control plane with an emergency indication
  • the mobility management unit MM requests a connection from a radio resource control unit RRC of the control plane with a dedicated access/establishment cause. That is, the specified access/establishment cause applies for the signal between flow filtering unit or PDCP and MM, between MM and RRC, and between RRC/UE and the network (i.e. a network element).
  • a bearer for transmitting data to be transmitted via a network is determined, and that a network connection for transmitting the data using the determined bearer is initiated.

Landscapes

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

Abstract

La présente invention concerne des moyens, notamment des procédés, des appareils, des éléments réseau, des systèmes et des programmes informatiques, permettant un filtrage de flux de données en particulier, mais pas uniquement, pour des données d'urgence. En particulier, selon l'invention, un support destiné à la transmission de données via un réseau, est déterminé, et une connexion réseau destinée à la transmission des données au moyen du support déterminé, est amorcée.
PCT/EP2007/064081 2006-12-21 2007-12-17 Support d'urgence dans un système de communication WO2008074782A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US87615706P 2006-12-21 2006-12-21
US60/876,157 2006-12-21

Publications (1)

Publication Number Publication Date
WO2008074782A1 true WO2008074782A1 (fr) 2008-06-26

Family

ID=39183058

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/064081 WO2008074782A1 (fr) 2006-12-21 2007-12-17 Support d'urgence dans un système de communication

Country Status (1)

Country Link
WO (1) WO2008074782A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2523524A1 (fr) * 2010-01-06 2012-11-14 NTT DoCoMo, Inc. Procédé de communication mobile, n ud de commande d'appel, n ud de commande de priorité et n ud de gestion mobile
EP3094153A1 (fr) * 2015-05-13 2016-11-16 LG Electronics Inc. Procédé de configuration de porteuse pour envoyer et recevoir des données dans un système de communication sans fil et appareil prenant en charge ce procédé
EP3185593A1 (fr) * 2015-12-22 2017-06-28 Intel IP Corporation Système et procédé de positionnement d'emplacement de plan d'utilisateur sécurisé en cas d'urgence
EP3370393A1 (fr) * 2008-07-04 2018-09-05 Samsung Electronics Co., Ltd. Procédé pour prendre en charge un appel d'urgence dans un système de communication mobile

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002003718A2 (fr) * 2000-04-10 2002-01-10 Nokia Corporation Services de telephonie dans des reseaux ip
WO2002089515A1 (fr) * 2001-04-27 2002-11-07 Nokia Corporation Procede et systeme permettant d'etablir des sessions d'urgence dans des cas exceptionnels

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002003718A2 (fr) * 2000-04-10 2002-01-10 Nokia Corporation Services de telephonie dans des reseaux ip
WO2002089515A1 (fr) * 2001-04-27 2002-11-07 Nokia Corporation Procede et systeme permettant d'etablir des sessions d'urgence dans des cas exceptionnels

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP-3RD GENERATION PARTNERSHIP PROJECT: "3GPP TS 23.167 v7.3.0 (2006-12); Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) emergency sessions (Release 7)", 11 December 2006 (2006-12-11), XP002474169, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/html-info/23167.htm> [retrieved on 20080327] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3370393A1 (fr) * 2008-07-04 2018-09-05 Samsung Electronics Co., Ltd. Procédé pour prendre en charge un appel d'urgence dans un système de communication mobile
EP2523524A1 (fr) * 2010-01-06 2012-11-14 NTT DoCoMo, Inc. Procédé de communication mobile, n ud de commande d'appel, n ud de commande de priorité et n ud de gestion mobile
EP2523524A4 (fr) * 2010-01-06 2013-10-23 Ntt Docomo Inc Procédé de communication mobile, n ud de commande d'appel, n ud de commande de priorité et n ud de gestion mobile
EP3094153A1 (fr) * 2015-05-13 2016-11-16 LG Electronics Inc. Procédé de configuration de porteuse pour envoyer et recevoir des données dans un système de communication sans fil et appareil prenant en charge ce procédé
US10616901B2 (en) 2015-05-13 2020-04-07 Lg Electronics Inc. Method of configuring bearer for sending and receiving data in wireless communication system and apparatus supporting the method
EP3185593A1 (fr) * 2015-12-22 2017-06-28 Intel IP Corporation Système et procédé de positionnement d'emplacement de plan d'utilisateur sécurisé en cas d'urgence

Similar Documents

Publication Publication Date Title
US20080153454A1 (en) Emergency service in a communication system
EP2255557B1 (fr) Procédé d&#39;optimisation de connexion à un réseau de données par paquets (pdn) d&#39;un équipement utilisateur
EP2908583B1 (fr) Procédé de traitement de recherche de mobile et procédé permettant de relayer des données de liaison descendante
US8855052B2 (en) Attention commands enhancement
EP2469894B1 (fr) Procédé et système pour réaliser une localisation d&#39;urgence
CN110741678A (zh) 一种切换业务承载网络的方法、设备及计算机存储介质
EP2297985B1 (fr) Procede de soutien d appel d urgence dans un systeme de communication mobile
EP2056570A1 (fr) Session et média liés à une commande commune
US20100182912A1 (en) Method, system, and devices for informing a terminal about failure in resource reservation
WO2008110215A1 (fr) Procédé et appareil pour réaliser un branchement local dans un réseau mobile
US8195120B2 (en) Precedence and preemption extension for remote terminals
US20170311151A1 (en) Mobile communication system, communication control device, mobility management entity, and mobile communication method
US10716159B2 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
US10291579B2 (en) Method for recovering IPV6 fault in mobile communication network and PCRF
US8335485B2 (en) Call routing
US8885608B2 (en) Mobile communication method
WO2008074782A1 (fr) Support d&#39;urgence dans un système de communication
US11303761B2 (en) Service data flow processing method and related device
EP2934063A1 (fr) Procédé d&#39;initiation de signalisation, appareil et dispositif passerelle
EP2836036A1 (fr) Dispositif de commande de communication et procédé de commande de communication
CN101557610A (zh) 承载处理方法、系统和装置
EP3796715A1 (fr) Procédé de communication et système avec temporisateur p-cscf d&#39;urgence/indication de modification de porteuse
US10609604B2 (en) Handover from WiFi to mobile network
EP3297304A1 (fr) Système de communication mobile, dispositif de commande de communication, entité de gestion de mobilité, et procédé de communication mobile
US8873562B2 (en) Apparatus and method for media data classification in mobile communication system

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: 07857711

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: 07857711

Country of ref document: EP

Kind code of ref document: A1