WO2010105485A1 - 一种注销紧急呼叫用户的方法和*** - Google Patents
一种注销紧急呼叫用户的方法和*** Download PDFInfo
- Publication number
- WO2010105485A1 WO2010105485A1 PCT/CN2009/075989 CN2009075989W WO2010105485A1 WO 2010105485 A1 WO2010105485 A1 WO 2010105485A1 CN 2009075989 W CN2009075989 W CN 2009075989W WO 2010105485 A1 WO2010105485 A1 WO 2010105485A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- emergency call
- bearer
- logout
- mme
- emergency
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
Definitions
- the present invention relates to emergency call technology under System Long Term Evolution (SAE) access, and more particularly to a method and system for canceling an emergency call user.
- SAE System Long Term Evolution
- the IP Multimedia Subsystem is the core of the new generation communication network. Its distinctive feature is the use of the Session Initiation Protocol (SIP) system, which is independent of access and has multiple media service control. Separation of functions from bearer capabilities, separation of calls and sessions, separation of applications and services, separation of services from networks, and integration of mobile and Internet services.
- SIP Session Initiation Protocol
- the emergency call (EMC) service under IMS can be built on the general packet radio service (GPRS) network and the system architecture evolution (SAE) network. Provide unified emergency call control.
- GPRS general packet radio service
- SAE system architecture evolution
- the user equipment (UE, User Equipment) is executed by accessing the SAE network.
- the architecture diagram of the EMC service includes: the SAE network part, the Policy Charging Control (PCC) part, the Location Service (LCS), and the IMS emergency service part.
- PCC Policy Charging Control
- LCS Location Service
- the SAE network part is used to provide the underlying bearer management and mobility management functions, and the network elements of the part mainly include: an enhanced radio base station (eNodeB), a mobility management entity (MME, Mobility Management Entity), and a system long-term evolution gateway.
- eNodeB enhanced radio base station
- MME mobility management entity
- SAE GW System Architecture Evolution Gateway
- the S AE GW is a functional entity of the user plane, and is used for data routing processing of the user plane, and is divided into a service gateway (S-GW, Serving GW) and packet data.
- S-GW Service gateway
- Serving GW Packet Data Network GW
- P-GW Packet Data Network GW
- the PCC part is used to establish effective policy and charging control in the underlying bearer layer and the upper layer service layer.
- the network elements in this part mainly include: Policy and Charging Rules Function (PCRF, Policy and Charging Rules Function) Entity and Policy and Billing Entity (PCEF, Policy and Charging Enforcement Function) entity.
- PCRF Policy and Charging Rules Function
- PCEF Policy and Charging Enforcement Function
- the LCS part is used to provide the location service and the address of the Public Safety Access Point (PSAP) for emergency calls.
- the network elements of this part mainly include: Location Require Function (LRF) entity and gateway mobile positioning center (GMLC, Gateway Mobile Location Center).
- LRF Location Require Function
- GMLC Gateway Mobile Location Center
- the IMS emergency service part is used to control and process the emergency call session.
- the network elements of this part mainly include: Home Subscriber Server (HSS), Call Session Control Function (CSCF).
- HSS Home Subscriber Server
- CSCF Call Session Control Function
- the HSS mainly manages the user's subscription data and is located in the home network.
- the CSCF is the core network element that controls the session process, including: Proxy CSCF (P-CSCF, Proxy-CSCF), Query CSCF (I-CSCF, Interrogating-CSCF), Serving CSCF (S-CSCF, Serving-CSCF), Emergency CSCF (E-CSCF, Emergency-CSCF).
- P-CSCF Proxy CSCF
- Proxy-CSCF Proxy-CSCF
- I-CSCF Interrogating-CSCF
- S-CSCF Serving CSCF
- E-CSCF Emergency-CSCF
- the E-CSCF is the session control center of the emergency call, which determines which public safety answer point (
- the UEs under the SAE access sometimes work in restricted mode, that is, the UE is restricted in service; in this case, the normal network attachment and service establishment request initiated by the UE will be rejected by the network.
- restricted mode it is usually required that the UE in the restricted mode can also initiate an emergency call; therefore, the Evolved Packet System (EPS) studied in the 3rd Generation Partnership Project (3GPP) is urgent.
- EPS Evolved Packet System
- 3GPP 3rd Generation Partnership Project
- the emergency bearer is set up, that is, the UE initiates an emergency attach request, and the emergency identifier that is carried is used to inform the bearer network that the current attachment is for emergency call; after the bearer network receives the emergency attach request of the UE, it passes an emergency access point name (E-APN). , Emergency Access Point Name ) , to establish a default bearer dedicated to emergency calls, this default bearer is mainly used for signaling control.
- E-APN Emergency Access Point Name
- the so-called emergency call that is, the UE carries the emergency identity in the normal call request message, indicating that the call request is an emergency call.
- the UE Different from the establishment of the default bearer used for signaling control, when the UE initiates an emergency call, it also needs to establish a Dedicated Bearer for carrying voice, that is, a user plane bearer for voice media transmission. Indicates that the bearer is a bearer with a fixed quality of service (QoS) requirement that is different from the default bearer.
- QoS quality of service
- the establishment of the bearer may be established by the bearer network through the control of the PCC, or may be established by the UE by itself.
- the bearer network establishes the designated bearer for the UE through the control of the PCC, it indicates that the establishment of the bearer involves the participation of the dynamic PCC; if the UE indicates the bearer network establishment by itself, the bearer network uses the static PCC policy to establish the designated bearer for the UE.
- the so-called dynamic PCC refers to the primary policy control entity in the PCC.
- the PCRF establishes, changes, and releases the specified EPS bearer according to the indication of the application function point (AF, Application Function) during the SIP session.
- the P-CSCF that processes the SIP signaling dynamically communicates with the PCRF as an AF, and dynamically binds the session of the SIP layer and the bearer of the EPS layer through the PCRF, so that the P-CSCF can be based on
- the request of the SIP session notifies the PCRF to establish, change, and release the media resource (ie, the bearer of the underlying voice), and the PCRF further notifies the P-GW to perform the establishment, change, and release of the specific bearer.
- the P-GW reports the change of the bearer to the MME through the S-GW.
- the so-called static PCC means that the PCRF does not establish, change, and release the EPS bearer according to the indication of the AF during the SIP session; but only establishes, changes, and releases the EPS bearer by using the static emergency call policy data stored by itself. Even not deploying PCRF, but only at P-GW (PCEF)
- PCRF P-GW
- the establishment, change, and release of the emergency bearer for the emergency call are controlled by the UE.
- the UE controls the establishment and release of the specified bearer according to the establishment and release process of the SIP signaling in the emergency session.
- Steps 201-202 The UE initiates an emergency attach request to the eNodeB, and the eNodeB selects the served MME for the UE, and forwards the emergency attach to the MME. request.
- Step 203-206 the MME sends a home subscriber server to the home network ( HSS , Home
- Subscriber Server initiates a location update operation, and the HSS looks up the UE's user data to send to
- Steps 207-212 The MME initiates a process of creating a default bearer, and the P-GW establishes a default bearer for the UE according to the policy and the charging decision information of the PCRF.
- Steps 213 ⁇ 215 establishing a voice bearer between the eNodeB and the UE.
- Steps 216-218 the MME notifies the S-GW of the identifier and address of the eNodeB served by the UE. If the P-GW is not specified by the HSS, the MME sends a location update request to the HSS, and the notification is sent.
- the HSS is the address information of the P-GW served by the UE, and the information is updated by the HSS.
- Step 301 The UE initiates an emergency call to the EPS network, and the emergency call is routed to the E-CSCF.
- Step 302 The E-CSCF requests the LRF to be allocated by sending a location query request to the LRF.
- the PSAP of the UE service is the PSAP of the UE service.
- Step 303 The LRF sends a location query request to the MME to query the current location information of the UE.
- RAN Radio Access Network
- Step 305 The LRF allocates a PSAP to the UE according to the location information of the UE.
- Step 306 the LRF returns the location information of the UE to the E-CSCF, and returns the corresponding PSAP address.
- the E-CSCF routes the emergency call to the PSAP and establishes a call until the call process ends.
- Steps 309 ⁇ 311 the E-CSCF requests the LRF to subscribe to the UE location change, and the LRF returns a response to the location request; the LRF may also cancel the subscription to the UE location change to the MME.
- the EPS network needs to allow the UE to continue to attach for a period of time, and retain some emergency resources allocated for the UE, such as the default bearer used for signaling control. . That is to say, the EPS network needs to have a certain time delay in deregistering the behavior of the emergency attached UE. The requirement is based on the following reasons:
- the UE may initiate an emergency call again within a predictable time, in order to avoid repeated emergency attachment, confirmation in restricted mode, possible authentication, etc. It is necessary for the UE to continue to attach to the EPS network and maintain some emergency resources allocated by the EPS network for the UE to speed up processing;
- the PSAP may call back the UE within a predictable time. If the UE has been logged off by the EPS network, the callback will not be performed.
- the EPS network needs to log out of the UE for a period of time after the UE has used the emergency service.
- the UE automatically logs out to the EPS network for emergency attachment.
- the UE's self-deregistration behavior depends on the development of the terminal manufacturer or the requirements of the operator.
- the EPS network actively cancels the attachment of the UE to the EPS network.
- the emergency service is different from other services and is a non-billing service, it is expected that the active cancellation of the UE that is urgently attached to the EPS network is not guaranteed.
- the EPS network actively deregisters the UE, which usually refers to the MME actively deregistering the UE that is urgently attached.
- the MME actively logs out the UE, it needs to have a suitable When is the time.
- the MME cannot directly learn the initiation and release actions of the emergency call of the IMS service layer. Therefore, the MME can only log off the urgently attached UE by other means, for example, the MME requires the S-GW/P-GW to be absent.
- the bearer After a period of actual data flow, the bearer is actively released, and the MME deregisters the UE. Alternatively, the MME can do this by setting a logout timer.
- the use of the logout timer in the prior art to log off the emergency attached UE may result in the following situation: The UE is still in an emergency call when the logout timer time expires, so that the logout operation causes the ongoing emergency call to be forced. Interrupted. Summary of the invention
- the present invention provides a method for deregistering an emergency call user, the method comprising:
- the mobility management entity MME determines that the emergency call of the UE ends according to the received message, the MME starts the offload timer;
- the MME logs out the UE from the EPS network when the logout timer expires.
- the receiving the message is a release message indicating the bearer, and the starting the deregistration timer is specifically: the MME determines that the emergency call of the UE ends according to the release message of the specified bearer, and determines that the UE is an emergency attach Or when in restricted mode, the logout timer is started.
- the received message is an idle RRC-IDLE message controlled by the radio resource, and the start-up revocation timer is specifically:
- the received message is a periodic tracking area update TAU request message, where the startup logout timer is specifically: Determining, by the MME, an emergency call termination of the UE according to the periodic TAU request message, and starting a logout timer when determining that the UE is in an emergency attach or in a restricted mode.
- the method further includes:
- the MME starts the logout timer after the UE is successfully attached to the emergency, and cancels the logout timer after indicating that the bearer is created.
- the creation and release of the indicated bearer is implemented by a policy charging control PCC entity, or by the UE control.
- the present invention also provides a method for canceling an emergency call user, the method further comprising: after the UE is urgently attached to the EPS network, the MME sends a logout timer to the UE by using an attach response;
- the UE starts a logout timer when the emergency call ends, and logs out from the EPS network when the logout timer time arrives.
- the present invention also provides a system for canceling an emergency call user, the system comprising: a user terminal for emergency attaching to an EPS network, and performing an emergency call;
- a mobility management entity configured to: when the user terminal is urgently attached to the EPS network, and determine that the emergency call of the user terminal ends according to the received message, start a logout timer; when the time to wait for the logout timer arrives, the user is The terminal is logged off from the EPS network.
- the received message is a release message indicating a bearer, or an RRC-IDLE message, or a periodic TAU request message.
- the mobility management entity is further configured to: after the user terminal is urgently attached to the EPS network, send the logout timer to the user terminal by using an attach response; correspondingly, the user terminal is further configured to: when the emergency call ends, A logout timer is initiated and deregistered from the EPS network when the logout timer time arrives.
- the present invention also provides a method for deregistering an emergency call user, the method comprising: when the UE completes an emergency call, the packet data network gateway P-GW is based on the received release The voice-bearing message of the emergency call user releases the voice bearer, and checks whether the condition for releasing the signaling bearer is satisfied. If yes, the log-out timer located in the P-GW is started, and when the log-out timer expires, the emergency call is released. Signaling bearer.
- the condition for the check release signaling bearer is: the voice bearer on the emergency public data network PDN connection on the P-GW is completely released.
- the message received by the P-GW to release the voice bearer of the emergency call user is initiated from the UE or initiated from the PCC.
- the initiating the logout timer, when the logout timer expires, releasing the signaling bearer of the emergency call specifically includes the following steps:
- the logout timer is started.
- the P-GW releases all non-voice bearers on the emergency PDN connection, and notifies the network element associated with the EPS network to cancel the emergency call.
- the present invention also provides a system for canceling an emergency call user, the system comprising: a user terminal for emergency attaching to an EPS network, and performing an emergency call;
- the packet data gateway P-GW is configured to release the voice bearer according to the received message of the voice bearer of the released emergency call user when the user terminal is urgently attached to the EPS network, and check whether the condition for releasing the signaling bearer is satisfied, if the condition is met.
- the deactivation timer located in the P-GW is started, and when the logout timer expires, the signaling of the emergency call is released.
- the method and system for canceling an emergency call user provided by the present invention, when the UE is urgently attached to the EPS network, and the MME determines that the emergency call of the UE ends according to the received message, the MME starts the logout timer, and at the logout timing When the device time arrives, the UE is logged out of the EPS network.
- the invention solves the problem that the existing cancellation method is easy to cause the emergency call to be interrupted; and the invention can delay releasing the emergency call resources allocated to the UE to ensure that the UE does not need to initiate the second emergency call within a predictable time. Repeating the process of emergency attach and the like; the present invention also enables the emergency call center to call back to the UE in a predictable time, so that the UE cannot be called back. happening. DRAWINGS
- FIG. 1 is a structural diagram of a UE performing an EMC service by accessing a SAE network in the prior art
- FIG. 2 is a flowchart of establishing an emergency bearer by a UE in the prior art
- FIG. 3 is a flow chart of a UE initiating an emergency call in the prior art
- FIG. 4 is a flow chart of a method for canceling an emergency call user according to the present invention.
- FIG. 5 is a flowchart of a logout method according to Embodiment 1 of the present invention.
- FIG. 6 is a flowchart of a logout method according to Embodiment 2 of the present invention.
- FIG. 7 is a flowchart of a logout method according to Embodiment 3 of the present invention.
- FIG. 9 is a flowchart of a logout method according to Embodiment 5 of the present invention.
- FIG. 10 is a flowchart of a logout method according to Embodiment 6 of the present invention.
- FIG. 11 is a schematic structural diagram of a system for canceling an emergency call user according to the present invention
- FIG. 12 is a flowchart of a logout method according to Embodiment 7 of the present invention. detailed description
- a method for canceling an emergency call user provided by the present invention mainly includes the following steps:
- Step 401 When the UE is urgently attached to the EPS network, and the MME determines, according to the received message, that the emergency call of the UE ends, the MME starts the logout timer.
- the message received by the MME in the present invention may be a release message indicating a bearer, or may be a radio resource control IDLE (RRC-IDLE) message, or may be a periodic tracking area update (TAU, Tracking Area). Update) Request message.
- RRC-IDLE radio resource control IDLE
- TAU Tracking Area
- Update Update
- the logout timer is pre-configured on the MME, and the duration of the logout timer can be set according to actual needs.
- Step 402 The MME logs out the UE from the EPS network when the logout timer expires. After waiting for the duration of the logout timer, the MME releases the emergency bearer allocated for the UE, including notifying the eNodeB to release the UE's air interface connection, thereby deregistering the UE from the EPS network.
- the following describes the deregistration method of the bearer as an example.
- a dynamic PCC is deployed in this embodiment, that is, the creation and release of the bearer is controlled by the PCC entity, and the implementation is implemented.
- the logout method of the example mainly includes the following steps:
- Step 501 The UE sends an emergency attach request to the EPS network, where the emergency attach request is delivered to the MME.
- Step 502 The MME creates a default bearer for the emergency call for the UE, and the bearer is mainly used for signaling control.
- the creation process of the default bearer is prior art and will not be described here.
- Step 503 After the default bearer is created, the MME sends an attach response to the UE.
- Step 504 After sending an attach response to the UE, the MME starts a logout timer for the emergency attached UE.
- Step 505 The UE initiates an emergency call of the SIP to the P-CSCF/E-CSCF, and negotiates necessary information such as the media type with the calling peer through the P-CSCF/E-CSCF.
- Step 506 After the UE performs media negotiation with the calling peer, the P-CSCF instructs the PCRF to establish a corresponding designated bearer for the UE according to the result of the negotiation.
- the PCRF determines appropriate policy data according to the configuration data of the emergency call (for example: The QoS level of the emergency call is issued to the P-GW for execution; the P-GW performs the policy delivered by the PCRF, creates a corresponding specified bearer, and carries the creation event of the specified bearer in the specified bearer creation message through the S-GW.
- the creation event reported to the MME carries identification information that identifies that the designated bearer is created for an emergency call.
- Step 507 After receiving the specified bearer creation event reported by the P-GW through the S-GW, the MME determines that the specified bearer is created for the emergency call according to the reported identifier information, and detects that the UE associated with the specified bearer is The UE that is urgently attached, or the UE in the restricted mode; further checks that the logout timer has been started for the UE, and performs the cancel operation of the logout timer.
- the MME may be based on the emergency APN provided when the UE is urgently attached, or the emergency identifier set by the MME in the context of the UE after the UE is urgently attached, or the emergency call level in the QoS parameter of the context of the UE. And determining that the UE is an emergency attached UE.
- the MME may determine whether the UE is located in the restricted area according to the current area of the UE, the restricted area list sent from the HSS, and the like.
- the MME may also set a restricted identifier in the context of the UE to indicate that the UE is a UE in the restricted mode after initially determining that the UE is restricted.
- starting the logout timer in step 504 can ensure that the UE is logged off by the timer set in step 504 even if the subsequent UE initiates the emergency call without success and indicates that the bearer creation and release process does not occur. . If the corresponding logout timer is canceled in step 507, it can be ensured that the timer started in step 504 does not interrupt a long emergency call that the UE is in, so that the emergency call of the UE is not limited by the duration of the logout timer. .
- an emergency call is established between the UE and the calling peer until the emergency call ends.
- Step 510 After the emergency call between the UE and the calling peer ends, the P-CSCF requests the PCRF to release the specified bearer for the emergency call for the UE according to the indication of the SIP signaling; the PCRF according to the indication of the P-CSCF, and the emergency call.
- the P-GW is required to release the specified bearer established for the UE, and the P-GW releases the corresponding specified bearer, and the release event of the specified bearer is carried in the specified bearer release message by the S-GW.
- Step 511 After receiving the specified bearer release event reported by the P-GW through the S-GW, the MME Determining that the specified bearer is created for an emergency call according to the reported information and the context information of the UE that is stored by the UE, and detecting that the UE associated with the specified bearer is an emergency attached UE, or a UE in the restricted mode; It is further checked that the logout timer has been canceled for the UE and the logout timer is started again for the UE.
- Step 512 When the logout timer time set on the MME arrives, the MME decides to cancel the emergency attached UE.
- Step 513 The MME notifies the S-GW/P-GW to release the emergency bearer allocated to the UE.
- Step 514 the MME cancels the UE, and includes notifying the eNodeB to release the air interface connection of the UE.
- the MME may start to start according to the situation when receiving the establishment and release of the specified bearer allocated for the UE. Or cancel the logout timer of the UE.
- the UE When only the static PCC is used, the UE will control the establishment of the designated bearer for the emergency call, and the UE deregistration method in this case is as shown in FIG. 6.
- the difference between the embodiment 2 shown in FIG. 6 and the first embodiment shown in FIG. 5 is only to indicate that the creation and release process of the bearer is initiated by the UE.
- the EPS network When the UE initiates an emergency call, the EPS network is required to create a specified bearer according to the 200 OK message of the SIP session.
- the emergency call is released, the EPS network is required to release the specified bearer according to the BYE message of the SIP session.
- Step 606 After performing media negotiation with the calling peer, the UE initiates a setup request indicating the bearer to the MME.
- the MME requests the S-GW/P-GW to create a corresponding designated bearer according to the configuration of the emergency call policy data.
- Step 610 After the emergency call ends, the UE requests the MME to release the specified bearer established according to the BYE indication of the SIP session, and the MME further requests the S-GW/P-GW to release the corresponding designated bearer.
- the MME can obtain a notification according to the situation when receiving the message indicating the establishment and release of the bearer allocated for the UE, and further, according to whether the UE is urgently attached, or whether it is a restricted mode, and Whether the logout timer is started for the UE, and the logout timer for starting or canceling the UE is determined.
- the UE is in the connected state (EMM-CONNECTED) during the actual emergency call; when the UE is inactive after a period of emergency call, it will go into the idle state (EMM-IDLE).
- EMM-CONNECTED the connected state
- EMM-IDLE the idle state
- the MME can determine the end of the emergency call of the UE according to the information that the UE is switched from the connection state to the idle state, thereby turning on the logout timer, and canceling the UE after the logout timer expires.
- the MME can learn that the UE transitions from the connected state to the idle state according to the received RRC-IDLE message.
- the specific UE logout process as shown in Figure 7, mainly includes the following steps:
- Step 701 The UE is urgently attached to the EPS network to create a default bearer.
- Step 702 The UE initiates an emergency call until the call ends.
- Step 703 After the UE ends the emergency call for a period of time, the UE transits from the connected state to the idle state, and the eNodeB learns that the UE enters the idle state.
- Step 704 The eNodeB sends an RRC-IDLE message to the MME, to notify the MME that the UE enters an idle state.
- Step 705 After receiving the RRC-IDLE message, the MME detects that the UE corresponding to the message is an urgently attached UE, or a UE in the restricted mode, and starts a logout timer for the UE.
- Step 706 ⁇ 708 after the period of time, the UE's logout timer expires, and the MME releases the emergency bearer established by the UE, and the UE is logged off from the EPS network.
- the MME may also learn that the UE transitions from the connected state to the idle state according to the received periodic TAU request message.
- the corresponding UE deregistration process is as shown in FIG. 8.
- the difference between the fourth embodiment shown in FIG. 8 and the third embodiment shown in FIG. 7 is that the MME is not waiting for the eNodeB to send.
- the RRC-IDLE message but waiting for the UE to periodically send a TAU request message after entering the idle state, initiates a logout timer for the UE according to a method similar to that of FIG. 7, and cancels the UE after the logout timer time arrives.
- the MME may directly log off the UE without setting a logout timer, and the specific implementation process is as shown in FIG. 9.
- the reason for this is based on: The UE has entered the idle state from the connection state for a certain period of time. This time is controlled by a timer. It is assumed that this time can meet the needs of the deferred logout user in the emergency call, and the UE can be received. The UE is logged out after the TAU request is sent.
- the essence of the fifth embodiment shown in FIG. 9 is that the MME does not specifically set a logout timer for deregistering the emergency call UE, but achieves the same purpose by borrowing a timer from which the UE enters the idle state from the connected state.
- the MME can log out the urgently attached UE according to the setting of the logout timer, and can use the implicit logout.
- the so-called implicit deregistration means that the behavior of the MME to deregister the UE is not notified to the UE.
- the MME indicates that the eNodeB releases the air interface resource allocated for the UE, but the eNodeB does not send the logout message to the UE.
- the UE When the UE is deregistered by the method of implicit deregistration, since the UE does not receive the logout message, the state maintained by the UE itself is inconsistent with the actual state of the network. This situation may cause the UE to mistakenly consider the problem of network signal quality and re-attempt to attach to the network, thereby wasting resources of the UE and the network.
- the sixth embodiment of the present invention provides a method for the UE to perform its own EPS network logout according to the logout timer sent by the MME. As shown in FIG. 10, the method mainly includes the following steps: Step 1001: The UE sends an emergency attach to the MME. request.
- Step 1002 The MME creates a default bearer for the UE.
- Step 1003 The MME sends an attach response to the UE, and carries a logout timer in the attach response.
- the duration of the logout timer may be the same as or different from the logout timer of the MME.
- Step 1004 After the UE attaches successfully, the MME may start a logout timer for the UE according to the network policy, and cancel the logout timer after creating the specified bearer.
- Step 1005 The UE initiates an emergency call, and after the call is a period of time, the emergency call ends.
- Step 1006 The MME restarts the logout timer when the UE is informed that the emergency call is over, and releases the emergency bearer allocated to the UE when the logout timer expires, and the UE is logged off.
- Step 1007 When the UE emergency call ends, the offending timer is started according to the BYE message of the SIP session.
- Step 1008 After the logout timer time on the UE arrives, the UE actively initiates the logout. It should be noted that if the logged-off timer is also set on the MME, and the MME's logout timer works first, the MME may use the implicit logout method to cancel the UE; afterwards, the UE revokes itself and can modify its own state to Logout.
- setting the logout timer on the UE has the same effect: if the UE is currently in the restricted cell and is in the emergency attach state, when the UE moves to the normal cell, the UE even finds out because the UE is currently in an emergency attach state. The new cell will not initiate the logout emergency attach and initiate the normal attach process.
- the setting of the timer ensures that after the UE moves to the normal cell for a period of time, the UE can log out from the state of emergency attachment and attach normally to enjoy normal service. If the UE always moves back and forth between a restricted cell and a normal cell, the timer set on the UE can avoid the ping-pong effect of frequent handover.
- the logout timer set on the UE may be appropriately smaller than the logout timer set by the network.
- the deregistration timer can be restricted to be started when the UE is urgently attached.
- the UE moves to a new cell and the timer expires, the UE is triggered to log off the emergency attachment and initiate normal attachment, so that the UE moves from the restricted cell to the new one.
- the normal attachment mode it is possible to switch to the normal attachment mode relatively quickly. For the case where the UE stays in the same cell (restricted cell), after the logout timer expires, the UE only logs out the emergency attachment, and does not attempt to re-initiate. Emergency attachment.
- the present invention also provides a system for revoking an emergency call user.
- the system is composed of a user terminal 10 and a mobility management entity 20.
- the user terminal 10 is configured to urgently attach to the EPS network and perform an emergency call.
- the mobile management entity 20 is configured to: when the user terminal 10 is urgently attached to the EPS network, and determine that the emergency call of the user terminal 10 ends according to the received message, start the logout timer; when the time to wait for the logout timer arrives, the user terminal 10 is EPS network cancellation.
- the message received by the mobility management entity 20 in the present invention is a release message indicating a bearer, or an RRC-IDLE message, or a periodic TAU request message.
- the mobility management entity 20 is further configured to: after the user terminal 10 is urgently attached to the EPS network, send the logout timer to the user terminal 10 by using an attach response; correspondingly, the user terminal 10 is further configured to start the logout when the emergency call ends. Timer, and when the logout timer expires,
- an announcing timer for controlling and triggering a logout event may also be provided on the P-GW.
- a method for setting a logout timer on the P-GW may be that the P-GW detects the usage of the voice bearer of the UE. When the voice bearers have all been released, the P-GW starts the logout timer.
- the voice bearer is usually carried by the Guaranteed Bit Rate (GBR). Therefore, checking the usage of the GBR bearer can be understood as checking the usage of the voice bearer, that is, checking whether the emergency call ends.
- GBR Guaranteed Bit Rate
- FIG. 12 illustrates a method for the foregoing P-GW to trigger an MME to log off an emergency attached UE by setting a logout timer, including the following steps:
- Step 1201 The UE is urgently attached to the EPS network to create a default bearer.
- Step 1202 The UE initiates an emergency call until the call ends.
- Step 1203 The UE or the PCRF notifies the P-GW to release the voice bearer of the emergency call, and the P-GW releases the corresponding 7-load after receiving the notification.
- the P-CSCF When there is a dynamic PCC, the P-CSCF notifies the P-GW to release the voice bearer through the PCRF; when there is no dynamic PCC, the UE notifies the P-GW to release the voice bearer.
- Step 1204 The P-GW determines whether the emergency call has ended according to whether there is a voice bearer on the emergency PDN connection: When receiving the voice bearer release request message in step 1203, the P-GW checks the number of voice bearers on the emergency PDN connection, when P When the GW detects that all voice packets are released on the emergency PDN connection, the P-GW starts a logout timer for the PDN connection for the UE.
- Step 1205 When the logout timer expires, the P-GW releases all non-voice bearers on the emergency PDN connection, and then triggers the release of the emergency PDN connection. These released non-verbal bearers are usually signalling bearers.
- Step 1206 The P-GW notifies the MME to release the non-voice bearer; the MME determines that all bearers on the emergency PDN connection are released, and the MME releases the emergency PDN connection.
- Step 1207 If the MME detects that all PDN connections of the UE are released, and the MME triggers an implicit logout for the UE, the UE may not be notified to log off the UE from the network.
- Step 1208 optionally, the MME notifies the UE of the logout event by air interface signaling.
- the de-registration timer set on the P-GW may be initially attached to the UE, and the MME requests the S-GW/P-GW to transmit the P-GW to the P-GW when the default bearer is created for the UE, or may be set by the P-GW. Or set up through the operation and maintenance system.
- the present invention further provides a system for canceling an emergency call user, the system comprising: a user terminal and a packet data gateway. among them, The user terminal is used for emergency attachment to the EPS network and performs an emergency call.
- the packet data gateway is configured to release the voice bearer according to the received voice bearer message of the released emergency call user when the user terminal is urgently attached to the EPS network, and check whether the condition for releasing the signaling bearer is satisfied, and if yes, the start is located at the P- The logout timer in the GW; when the logout timer expires, the signaling bearer of the emergency call is released.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Emergency Management (AREA)
- Environmental & Geological Engineering (AREA)
- Public Health (AREA)
- Mobile Radio Communication Systems (AREA)
Description
一种注销紧急呼叫用户的方法和*** 技术领域
本发明涉及***长期演进( SAE )接入下的紧急呼叫技术, 尤其涉及一 种注销紧急呼叫用户的方法和***。 背景技术
IP多媒体子***( IMS , IP Multimedia Subsystem )是新一代通信网络 的核心,其显著特点是采用了会话发起协议( SIP, Session Initiation Protocol ) 体系, 通信与接入无关, 且具备多种媒体业务控制功能与承载能力分离, 呼叫与会话分离, 应用与服务分离, 业务与网络分离, 以及移动网与英特 网业务融合等多种功能。
由于 IMS与接入无关的特点, IMS下的紧急呼叫 (EMC, Emergency Call )业务, 可以建设在通用无线分组业务(GPRS, General Packet Radio Service ) 网络和***长期演进( SAE, System Architecture Evolution ) 网络 上, 提供统一的紧急呼叫控制。
现有技术中用户终端 ( UE, User Equipment )通过接入 SAE网络执行
EMC业务的架构图, 如图 1所示, 该架构包括: SAE网络部分、 策略计费 控制( PCC, Policy Charging Control )部分、位置服务( LCS , Location Service ) 部分和 IMS紧急业务部分。
其中, SAE 网络部分用以提供底层的承载管理和移动性管理功能, 该 部分的网元主要包括:增强的无线基站(eNodeB )、移动性管理实体(MME, Mobility Management Entity ) 和***长期演进网关 ( SAE GW , System Architecture Evolution Gateway )。 S AE GW为用户面的功能实体, 用于进行 用户面的数据路由处理, 分为服务网关( S-GW , Serving GW )和分组数据
网网关 (P-GW, Packet Data Network GW ) 两种。
PCC部分用以在底层承载层和上层业务层建立有效的策略、计费控制, 该部分的网元主要包括: 策略和计费规则功能( PCRF, Policy and Charging Rules Function ) 实体和策略和计费执行功能(PCEF, Policy and Charging Enforcement Function ) 实体。
LCS 部分用以为紧急呼叫提供位置服务和公共安全接入点 (PSAP , Public Safety Access Point )的地址, 该部分的网元主要包括: 位置请求功能 ( LRF, Location Require Function ) 实体和网关移动定位中心 (GMLC, Gateway Mobile Location Center )。
IMS 紧急业务部分用以控制和处理紧急呼叫的会话, 该部分的网元主 要包括: 归属用户服务器(HSS, Home Subscriber Server ), 呼叫会话控制 功能( CSCF, Call Session Control Function )。 HSS主要管理用户的签约数 据, 位于归属网。 CSCF是控制会话过程的核心网元, 包括: 代理 CSCF ( P-CSCF, Proxy-CSCF )、 查询 CSCF ( I-CSCF, Interrogating-CSCF )、 服 务 CSCF( S-CSCF, Serving-CSCF )、紧急 CSCF( E-CSCF, Emergency-CSCF )。 其中, E-CSCF为紧急呼叫的会话控制中心, 其决定紧急呼叫路由到哪个公 共安全应答点 (PSAP, Public Safety Answer Point )»
SAE接入下的 UE有时会工作在受限制模式下, 即 UE被限制服务; 在 这种情况下, UE发起的正常网络附着和业务建立请求, 将会被网络拒绝。 然而,实际应用中通常要求受限制模式下的 UE也能够发起紧急呼叫;因此, 在第三代合作伙伴计划 ( 3GPP, 3rd Generation Partnership Project )研究的 演进分组***(EPS, Evolved Packet System )对紧急呼叫的支持中, 促使 受限制模式下的 UE能够紧急附着(Emergency Attach )到 EPS网络, 并建 立专门用于紧急呼叫的紧急 载( Emergency Bearer )。
对于一个受限制模式下的 UE, 其实现紧急呼叫需要执行建立紧急承载
和发起紧急呼叫的操作。 所谓建立紧急承载, 即 UE发起紧急附着请求, 并 通过携带的紧急标识告知承载网络当前附着是为了拨打紧急电话; 承载网 络接收 UE 的紧急附着请求后, 通过一个紧急接入点名称 (E-APN , Emergency Access Point Name ) , 来建立一个专门用于紧急呼叫的缺省承载, 这个缺省承载主要用于信令控制。所谓紧急呼叫, 即 UE通过在正常的呼叫 请求消息中携带紧急标识, 表明该呼叫请求是一个紧急呼叫。
区别于用于信令控制的缺省承载的建立, UE发起紧急呼叫时, 还需要 建立一个用于承载语音的指明承载( Dedicated Bearer ), 即用于语音媒体传 输的用户面承载。 指明承载是区别于缺省承载的一个具有固定服务质量 ( QoS, Quality of Service )要求的承载。 指明承载的建立, 可以是承载网 络通过 PCC的控制为 UE建立, 也可以是 UE自行指示承载网络建立的。 如果是承载网络通过 PCC的控制为 UE建立指明承载, 则指明承载的建立 会有动态 PCC的参与; 如果是 UE自行指示承载网络建立, 则承载网络采 用静态 PCC策略来为 UE建立指明承载。
所谓动态 PCC, 是指 PCC中的主要策略控制实体 PCRF在 SIP会话过 程中根据应用功能点(AF, Application Function )的指示建立、 变更、 释放 指定的 EPS承载。在 SIP会话建立、释放的过程中,处理 SIP信令的 P-CSCF 作为一个 AF与 PCRF动态交流,通过 PCRF将 SIP层的会话和 EPS层的承 载动态地进行绑定,这样 P-CSCF可以根据 SIP会话的要求通知 PCRF进行 媒体资源 (即底层的语音等承载) 的建立、 变更、 释放, 而 PCRF进一步 通知 P-GW执行具体的承载的建立、 变更、 释放。 在 P-GW执行承载建立、 变更、 释放的过程中, P-GW将通过 S-GW向 MME上报承载的变化情况。
所谓静态 PCC, 是指 PCRF不依据 SIP会话过程中 AF的指示来建立、 变更、 释放 EPS承载; 而仅仅凭借自身所存储的静态紧急呼叫策略数据来 建立、变更、释放 EPS承载。甚至于不部署 PCRF, 而仅仅在 P-GW ( PCEF )
上部署紧急呼叫的策略数据。 在这种情况下, 用于紧急呼叫的紧急承载的 建立、 变更、 释放, 是由 UE来控制的。 UE根据紧急会话中 SIP信令的建 立、 释放过程来控制指明承载的建立和释放。
现有技术中 UE建立紧急承载的过程如图 2所示, 主要包括以下步骤: 步骤 201~202, UE向 eNodeB发起紧急附着请求, 由 eNodeB为 UE选 择服务的 MME, 并向该 MME转发紧急附着请求。
步骤 203-206 , MME 向归属网的归属用户服务器 ( HSS , Home
Subscriber Server )发起位置更新的操作, HSS查找 UE的用户数据发送给
MME。
步骤 207~212, MME发起创建缺省承载的流程, 由 P-GW根据 PCRF 的策略和计费决策信息为 UE建立缺省承载。
步骤 213~215 , eNodeB与 UE之间建立语音承载。
步骤 216~218, MME通知 S-GW为 UE服务的 eNodeB的标识、 地址; 如果 P-GW不是 HSS指定的, 那么 MME向 HSS发送位置更新请求, 通知
HSS为 UE所服务的 P-GW的地址信息, 由 HSS更新该信息。
现有技术中 UE发起紧急呼叫的流程,如图 3所示,主要包括以下步骤: 步骤 301 , UE向 EPS网络发起紧急呼叫, 紧急呼叫被路由到 E-CSCF。 步骤 302, E-CSCF通过向 LRF发送位置查询请求, 请求 LRF分配为
UE服务的 PSAP。
步骤 303 , LRF向 MME发送位置查询请求,查询 UE的当前位置信息。 步骤 304, MME从无线接入网 (RAN, Radio Access Network )侧获取 用户的当前位置, 返回给 LRF。
步骤 305 , LRF根据 UE的位置信息为 UE分配 PSAP。
步骤 306, LRF向 E-CSCF返回 UE的位置信息, 并返回相应的 PSAP 地址。
步骤 307~308, E-CSCF即将紧急呼叫路由给 PSAP, 并且建立通话, 直到通话过程结束。
步骤 309~311 , E-CSCF向 LRF请求对 UE位置变化的订阅, LRF返回 位置请求的响应; LRF也可以向 MME取消对 UE位置变化的订阅。
对于受限制模式下的 UE附着到 EPS网络, 发起紧急呼叫后, EPS网 络需要允许 UE在一段时间内继续附着,并保留为 UE分配的一些紧急资源, 如用于信令控制的缺省承载等。也就是说, EPS网络注销紧急附着 UE的行 为, 需要具有一定的时间延迟性, 这种需求是基于如下的理由:
A、 当 UE发起第一次紧急呼叫后, 在可预期的时间内, UE有可能再 次发起紧急呼叫, 为了避免重复的紧急附着、 对受限制模式下的确认、 可 能的认证等不必要的步骤,有必要让 UE继续附着在 EPS网络,并保持 EPS 网络为 UE分配的一些紧急资源, 以加速处理;
B、 当 UE发起第一次紧急呼叫后, 在可预期的时间内, PSAP可能回 呼该 UE, 如果 UE已经被 EPS网络注销, 则回呼将无法进行。
然而, 对于受限制模式下的 UE, 也不需要一直附着在 EPS网络, 因为 这样会造成资源的浪费。 出于此目的, EPS网络需要在 UE使用完紧急服务 后一段时间内注销 UE。
关于受限制模式下的 UE附着到 EPS网络, 使用完紧急服务后, 如何 从 EPS网络注销的问题, 有以下几种选择:
a、 UE自行注销到 EPS网络的紧急附着。 UE自行注销行为取决于终端 厂商的开发或运营商的要求。
b、 EPS网络主动注销 UE到 EPS网络的附着。
然而, 由于紧急服务区别于其他业务, 是非计费业务, 期望紧急附着 到 EPS网络的 UE主动注销是不可保证的。 EPS网络主动注销 UE, 通常指 MME主动注销紧急附着的 UE。 但是, MME主动注销 UE, 需要有一个适
当的时机。 由于在现有技术下, MME无法直接获知 IMS业务层的紧急呼 叫的发起、释放动作, 因此 MME只能凭借其他手段来注销紧急附着的 UE, 比如: MME要求 S-GW/P-GW在没有实际的数据流的一段时间后, 主动释 放承载, 进而 MME注销该 UE。 或者, MME可以通过设置一个注销定时 器来进行。 然而, 现有技术中采用注销定时器来注销紧急附着的 UE, 会导 致以下的情况发生: 注销定时器时间时间到达的时候 UE还正在紧急通话 中, 从而注销操作使得正在进行的紧急呼叫被迫中断。 发明内容
有鉴于此, 本发明的主要目的在于提供一种注销紧急呼叫用户的方法 和***, 以解决现有的注销方法容易导致紧急呼叫中断的问题。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供了一种注销紧急呼叫用户的方法, 该方法包括:
在用户终端 UE紧急附着到演进分组*** EPS网络, 且移动管理实体 MME才艮据接收的消息确定所述 UE的紧急呼叫结束时, 所述 MME启动注 销定时器;
所述 MME在注销定时器时间到达时, 将所述 UE从 EPS网络注销。 所述接收的消息为指明承载的释放消息, 所述启动注销定时器具体为: 所述 MME根据所述指明承载的释放消息确定所述 UE的紧急呼叫结 束,并在确定所述 UE是紧急附着或者处于受限制模式时,启动注销定时器。
所述接收的消息为无线资源控制的空闲 RRC-IDLE消息, 所述启动注 销定时器具体为:
所述 MME根据所述 RRC-IDLE消息确定所述 UE的紧急呼叫结束,并 在确定所述 U E是紧急附着或者处于受限制模式时, 启动注销定时器。
所述接收的消息为周期性跟踪区域更新 TAU请求消息, 所述启动注销 定时器具体为:
所述 MME根据所述周期性 TAU请求消息确定所述 UE的紧急呼叫结 束,并在确定所述 UE是紧急附着或者处于受限制模式时,启动注销定时器。
在 UE紧急附着到 EPS网络之后, 该方法进一步包括:
所述 MME在 UE紧急附着成功后启动所述注销定时器,并在指明承载 创建完成后取消所述注销定时器。
所述指明承载的创建和释放由策略计费控制 PCC实体控制实现, 或由 所述 UE控制实现。
本发明还提供了一种注销紧急呼叫用户的方法, 该方法进一步包括: 在 UE紧急附着到 EPS网络后, 所述 MME将注销定时器通过附着响 应发送给所述 UE;
所述 UE在紧急呼叫结束时,启动注销定时器,并在所述注销定时器时 间到达时, 从所述 EPS网络注销。
本发明还提供了一种注销紧急呼叫用户的***, 该***包括: 用户终端, 用于紧急附着到 EPS网络, 并执行紧急呼叫;
移动管理实体, 用于在所述用户终端紧急附着到 EPS网络, 并根据接 收的消息确定所述用户终端的紧急呼叫结束时, 启动注销定时器; 待注销 定时器时间到达时, 将所述用户终端从 EPS网络注销。
所述接收的消息为指明承载的释放消息、 或 RRC-IDLE消息、 或周期 性 TAU请求消息。
所述移动管理实体还用于在用户终端紧急附着到 EPS网络后, 将所述 注销定时器通过附着响应发送给所述用户终端; 相应的, 所述用户终端还 用于在紧急呼叫结束时, 启动注销定时器, 并在所述注销定时器时间到达 时, 从所述 EPS网络注销。
本发明还提供了一种注销紧急呼叫用户的方法, 该方法包括: 所述 UE完成紧急呼叫时, 分组数据网网关 P-GW根据接收到的释放
紧急呼叫用户的语音承载的消息释放语音承载, 检查释放信令承载的条件 是否满足, 如果满足, 启动位于 P-GW 中的注销定时器, 当注销定时器时 间到达时, 释放所述紧急呼叫的信令承载。
所述检查释放信令承载的条件是: 所述 P-GW 上的紧急公共数据网 PDN连接上语音承载全部释放完毕。
所述 P-GW接收到的释放紧急呼叫用户的语音承载的消息是从所述 UE 发起或者从 PCC发起的。
所述启动注销定时器, 当注销定时器时间到达时, 释放所述紧急呼叫 的信令承载具体包括以下步骤:
注销定时器启动, 当注销定时器时间到达的时候, P-GW释放该紧急 PDN连接上所有非语音承载, 并且通知 EPS网络相关的网元注销所述的紧 急呼叫。
本发明还提供了一种注销紧急呼叫用户的***, 该***包括: 用户终端, 用于紧急附着到 EPS网络, 并执行紧急呼叫;
分组数据网关 P-GW, 用于在所述用户终端紧急附着到 EPS 网络时, 根据接收到的释放紧急呼叫用户的语音承载的消息释放语音承载, 检查释 放信令承载的条件是否满足, 如果满足, 启动位于 P-GW中的注销定时器, 当注销定时器时间到达时, 释放所述紧急呼叫的信令^载。
本发明所提供的一种注销紧急呼叫用户的方法和***,在 UE紧急附着 到 EPS网络, 且 MME才艮据接收的消息确定 UE的紧急呼叫结束时, MME 启动注销定时器, 并在注销定时器时间到达时, 将 UE从 EPS网络注销。 通过本发明, 解决了现有的注销方法容易导致紧急呼叫中断的问题; 且本 发明能够延期释放分配给 UE的紧急呼叫资源,以保证在可预期的时间内如 果 UE发起第二次紧急呼叫无需重复执行紧急附着等过程;本发明也使得在 可预期的时间内紧急呼叫中心回呼该 UE能够实现,不至于无法回呼 UE的
情况。 附图说明
图 1为现有技术中 UE通过接入 SAE网络执行 EMC业务的架构图; 图 2为现有技术中 UE建立紧急承载的流程图;
图 3为现有技术中 UE发起紧急呼叫的流程图;
图 4为本发明一种注销紧急呼叫用户的方法流程图;
图 5为本发明实施例一的注销方法流程图;
图 6为本发明实施例二的注销方法流程图;
图 7为本发明实施例三的注销方法流程图;
图 8为本发明实施例四的注销方法流程图;
图 9为本发明实施例五的注销方法流程图;
图 10为本发明实施例六的注销方法流程图;
图 11为本发明一种注销紧急呼叫用户的***的组成结构示意图; 图 12为本发明实施例七的注销方法流程图。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 本发明所提供的一种注销紧急呼叫用户的方法, 如图 4所示, 主要包 括以下步骤:
步骤 401 , 在 UE紧急附着到 EPS网络, 且 MME根据接收的消息确定 UE的紧急呼叫结束时, MME启动注销定时器。
本发明中所指 MME接收的消息可以是指明承载的释放消息,也可以是 无线资源控制的空闲(RRC-IDLE, Radio Resource Control IDLE )消息, 还 可以是周期性跟踪区域更新 ( TAU, Tracking Area Update )请求消息。 当然, 本发明的消息并不仅限于上述所举,对于其他类型的能够确定为 UE紧急呼
叫结束后的消息, 也属于本发明所要保护的范围。
注销定时器是预先配置在 MME上的,且注销定时器的时长可以才艮据实 际需要进行设置。
步骤 402, MME在注销定时器时间到达时, 将 UE从 EPS网络注销。 在等待了注销定时器的时长后, MME释放为 UE分配的紧急承载, 包 括通知 eNodeB释放 UE的空口连接, 从而将 UE从 EPS网络注销。
下面以指明承载的释放消息为例, 对上述的注销方法进行详细阐述, 如图 5所示, 该实施例中部署了动态 PCC, 即指明承载的创建和释放是由 PCC实体控制实现, 该实施例的注销方法主要包括以下步骤:
步骤 501 , UE向 EPS网络发送紧急附着请求, 该紧急附着请求传递到 MME。
步骤 502, MME为 UE创建用于紧急呼叫的缺省承载, 这个承载主要 用于信令控制。 缺省承载的创建过程为现有技术, 在此不再赘述。
步骤 503 , 缺省承载创建完成后, MME向 UE发送附着响应。
步骤 504, MME在向 UE发送附着响应后, 启动对该紧急附着 UE的 注销定时器。
步骤 505 , UE 向 P-CSCF/E-CSCF发起 SIP 的紧急呼叫, 并通过 P-CSCF/E-CSCF与呼叫对端协商媒体类型等必要信息。
步骤 506, UE与呼叫对端进行媒体协商后, P-CSCF根据协商的结果, 指示 PCRF为 UE建立对应的指明承载; PCRF根据对紧急呼叫的配置数据, 决策适当的策略数据 (比如: 用于紧急呼叫的 QoS等级), 发放给 P-GW执 行; P-GW执行 PCRF下发的策略, 创建对应的指明承载, 并通过 S-GW将 该指明承载的创建事件携带在指明承载创建消息中上报给 MME。 在向 MME上报的创建事件中,携带有标识该指明承载是为紧急呼叫而创建的标 识信息。
步骤 507, MME在收到 P-GW通过 S-GW上报的指明承载创建事件后, 根据上报的标识信息判定该指明承载是为紧急呼叫而创建的, 并检测到该 指明承载所关联的 UE是紧急附着的 UE, 或是受限制模式下的 UE; 进而 检查已经为该 UE启动了注销定时器, 并执行该注销定时器的取消操作。
在本步骤中, MME可以根据 UE紧急附着时所提供的紧急 APN、或者 UE紧急附着后 MME在该 UE的上下文中所设置的紧急标识、 或 UE的上 下文的 QoS参数中的紧急呼叫等级等信息, 确定该 UE是一个紧急附着的 UE。 MME可以根据 UE的当前区域, 以及从 HSS下发的限制区域列表等 确定 UE是否位于受限制区域。 MME也可以在初始判断 UE是受限制后, 在 UE的上下文中设置一个受限制标识来表明该 UE是一个受限制模式下的 UE。
需要指出的是, 在步骤 504中启动注销定时器, 能够保证即使后续 UE 发起紧急呼叫没有成功, 并且指明承载的创建和释放过程没有发生, 也能 保证通过步骤 504设置的定时器将 UE注销掉。而在步骤 507中取消对应的 注销定时器,能够保证在步骤 504中启动的定时器不会打断 UE正在进行的 一个较长的紧急呼叫, 使得 UE的紧急通话不受注销定时器的时长限制。
步骤 508~509, UE与呼叫对端之间建立紧急通话,直到紧急通话结束。 步骤 510, UE和呼叫对端的紧急通话结束后, P-CSCF根据 SIP信令的 指示, 要求 PCRF为 UE释放前述建立的用于紧急呼叫的指明承载; PCRF 根据 P-CSCF的指示, 以及紧急呼叫与指明承载的绑定关系,要求 P-GW释 放前述为 UE建立的指明承载; P-GW释放对应的指明承载, 并通过 S-GW 将该指明承载的释放事件携带在指明承载释放消息中上报给 MME。在上报 的指明承载的释放事件中, 具有足够的信息能让 MME 可以根据所保存的 UE的承载上下文, 识别该指明承载是为紧急呼叫而创建。
步骤 511 , MME在收到 P-GW通过 S-GW上报的指明承载释放事件后,
根据上报的信息和自身所存储的 UE 的上下文信息判定该指明承载是为紧 急呼叫而创建的, 并检测到该指明承载所关联的 UE是紧急附着的 UE, 或 是受限制模式下的 UE; 进而检查已经为该 UE取消了注销定时器, 并为该 UE再次启动注销定时器。
步骤 512, 当 MME上设置的注销定时器时间到达时, MME决定注销 该紧急附着的 UE。
步骤 513 , MME通知 S-GW/P-GW释放为 UE分配的紧急承载。
步骤 514, MME注销 UE, 包括通知 eNodeB释放 UE的空口连接。 在图 5所示的本发明实施例一中,负责为 UE建立指明承载是动态 PCC, 在此情况下 MME可以在收到为 UE分配的指明承载的建立、释放消息的时 候, 根据情况确定启动或取消该 UE的注销定时器。
当仅使用静态 PCC的时候, UE将自行控制建立用于紧急呼叫的指明 承载, 在这种情况下的 UE注销方法如图 6所示。 图 6所示实施例二与图 5 所示实施例一的区别仅仅在于指明承载的创建、 释放过程是由 UE来发起 的。 UE发起紧急呼叫的时候, 根据 SIP会话的 200 OK消息, 要求 EPS网 络创建指明承载; 在紧急呼叫释放的时候, 根据 SIP会话的 BYE消息, 要 求 EPS网络释放指明承载。
图 6所示流程与图 5的区别在于:
步骤 606, UE在和呼叫对端进行媒体协商后, 向 MME发起指明承载 的建立请求; MME根据自身紧急呼叫策略数据的配置, 要求 S-GW/P-GW 创建相应的指明承载。
步骤 610, UE在紧急呼叫结束后, 根据 SIP会话的 BYE指示, 要求 MME释放前述建立的指明承载, MME进一步要求 S-GW/P-GW释放相应 的指明承载。
图 6中的其他操作步骤与图 5中的相应操作类似, 在此不再赘述。
通过图 5和图 6所示的流程, MME能够在收到为 UE分配的指明承载 的建立、 释放的消息时根据情况获得通知, 进而根据 UE是否是紧急附着、 或是否是受限制模式, 以及是否为 UE启动了注销定时器的情况,确定启动 或取消该 UE的注销定时器。
UE在实际的紧急通话过程中, 处于连接状态 ( EMM-CONNECTED ); 当 UE紧急通话结束一段时间后不活动, 将转入空闲状态 (EMM-IDLE )。 这种从连接状态到空闲状态的转换,其时间是由在 UE上设置的一个连接状 态转空闲状态的定时器来控制的。 从而, MME可以根据 UE由连接状态转 换到空闲状态这一信息确定 UE的紧急呼叫结束,进而开启注销定时器, 并 在注销定时器时间到达后注销 UE。 在该过程中, MME 可以根据接收的 RRC-IDLE消息, 获知 UE由连接状态转换到空闲状态。 具体的 UE注销流 程, 如图 7所示, 主要包括以下步骤:
步骤 701 , UE紧急附着到 EPS网络, 创建缺省承载。
步骤 702, UE发起紧急呼叫, 直到通话结束。
步骤 703 , UE结束紧急呼叫一段时间后, 从连接状态转入空闲状态, eNodeB获知 UE进入空闲状态。
步骤 704, eNodeB向 MME发送 RRC-IDLE消息, 通知 MME该 UE 进入空闲状态。
步骤 705 , MME在收到 RRC-IDLE消息后, 检测消息对应的 UE是紧 急附着的 UE, 或是受限制模式下的 UE, 并启动针对该 UE的注销定时器。
步骤 706~708, —段时间后, 该 UE的注销定时器时间到达, MME释 放为 UE建立的紧急承载, 将 UE从 EPS网络注销。
在实际应用中 MME还可以根据接收的周期性 TAU请求消息,获知 UE 由连接状态转换到空闲状态。 对应的 UE注销流程, 如图 8所示, 图 8所示 实施例四与图 7所示实施例三的区别在于 MME不是等候 eNodeB发送的
RRC-IDLE消息, 而是等候 UE在进入空闲状态后, 周期性发送 TAU请求 消息时,根据与图 7类似的方法来启动针对 UE的注销定时器,并在注销定 时器时间到达后注销 UE。
另外,作为本发明的另一种实现, 当 MME收到 UE发送的周期性 TAU 请求消息后, MME可以不设置注销定时器而直接注销该 UE, 具体实现流 程如图 9所示。 这样做的理由是基于: UE从连接状态进入空闲状态已经有 一定的时间, 这个时间是由一个定时器控制的, 假定这个时间可以满足紧 急呼叫中延期注销用户的需求, 则可以在收到 UE发送的 TAU请求后就注 销该 UE。 图 9所示实施例五的实质是 MME不专门设置用于注销紧急呼叫 UE的注销定时器, 而是通过借用 UE从连接状态进入空闲状态的定时器来 实现相同的目的。
由 MME根据注销定时器的设置来注销紧急附着的 UE, 可以采用隐式 注销。 所谓隐式注销, 是指 MME注销 UE的行为不通知给 UE。 MME指 示 eNodeB释放为 UE分配的空口资源, 但是 eNodeB不向 UE发送注销消 息。
当采用隐式注销的方法来注销 UE的时候,由于 UE没有收到注销消息, 因此 UE自身所维护的状态和网络实际的状态不一致。这种情况可能会导致 UE误认为是网络信号质量的问题, 而重新尝试附着到网络, 从而浪费 UE 和网络的资源。
针对该问题,本发明的实施例六提供一种 UE根据 MME发送的注销定 时器执行自身的 EPS网络注销的方法, 如图 10所示, 主要包括以下步骤: 步骤 1001 , UE向 MME发送紧急附着请求。
步骤 1002 , MME为 UE创建缺省承载。
步骤 1003 , MME向 UE发送附着响应, 并在该附着响应中携带注销定 时器。 该注销定时器的时长可以与 MME的注销定时器一致, 也可以不同。
步骤 1004, MME可以根据网络策略, 在 UE附着成功后, 为该 UE启 动注销定时器, 并在创建指明承载后取消注销定时器。
步骤 1005 , UE发起紧急呼叫, 通话一段时间后, 结束紧急呼叫。
步骤 1006, MME在获知 UE紧急通话结束的情况下, 重新启动注销定 时器, 并在注销定时器时间到达时,释放为 UE分配的紧急承载, 注销 UE。
步骤 1007, UE紧急呼叫结束时, 根据 SIP会话的 BYE消息, 启动注 销定时器。
步骤 1008 , 当 UE上的注销定时器时间到达后, 由 UE主动发起注销。 需要指出的是,如果 MME上也设置了注销定时器, 并且 MME的注销 定时器先工作, 则 MME可以采用隐式注销的方法注销该 UE; 随后 UE自 行注销, 可将自身的状态修改为已注销。
进一步地, 在 UE上设置注销定时器还有这样的效果: 如果 UE当前位 于受限制的小区, 处于紧急附着状态, 当 UE移动到正常的小区时候, 由于 UE当前是紧急附着状态, UE即使发现了新的小区, 也不会主动发起注销 紧急附着, 再发起正常附着的过程。 定时器的设置, 保证了 UE移动到正常 小区一段时间后, UE能够从紧急附着的状态注销从而正常附着以享受正常 服务。 如果 UE总是在一个受限小区和正常小区之间来回移动, 则 UE上所 设置的定时器可以避免频繁切换的乒乓效应。
为了保证 UE从受限制小区切换到正常小区时,不至于等待很长的时间 才发起正常附着, UE上所设置的注销定时器可以适当地小于网络所设置的 注销定时器。 进一步地可以限制这个注销定时器在 UE紧急附着时候启动, 在 UE移动到新的小区时并且定时器时间到达后触发 UE注销紧急附着并发 起正常附着,从而使得 UE从受限制小区移动到新的正常小区后, 能够比较 快地切换到正常附着模式。而对于 UE—直停留在同一个小区(受限制小区 ) 的情况, 注销定时器时间到达后, UE仅注销紧急附着, 而不试图重新发起
紧急附着。
为实现上述本发明注销紧急呼叫用户的方法, 本发明还提供了一种注 销紧急呼叫用户的***, 如图 11所示, 该***由用户终端 10和移动管理 实体 20组成。 其中, 用户终端 10, 用于紧急附着到 EPS网络, 并执行紧 急呼叫。 移动管理实体 20, 用于在用户终端 10紧急附着到 EPS网络, 并 根据接收的消息确定用户终端 10的紧急呼叫结束时, 启动注销定时器; 待 注销定时器时间到达时, 将用户终端 10从 EPS网络注销。 本发明中移动管 理实体 20接收的消息为指明承载的释放消息、 或 RRC-IDLE消息、 或周期 性 TAU请求消息。
此外,移动管理实体 20还用于在用户终端 10紧急附着到 EPS网络后, 将注销定时器通过附着响应发送给用户终端 10; 相应的, 用户终端 10还用 于在紧急呼叫结束时, 启动注销定时器, 并在注销定时器时间到达时, 从
EPS网络注销。
另外, 作为本发明的另一种实现方式, 用以控制和触发注销事件的注 销定时器, 也可以设置在 P-GW上。
P-GW上设置注销定时器的方法,可以是 P-GW检测 UE的语音承载的 使用情况, 当这些语音承载已经全部被释放时, P-GW启动注销定时器。 由 于紧急呼叫下, 语音承载通常用保证比特率( GBR, Guaranteed Bit Rate ) 承载, 因此检查 GBR承载的使用情况, 可以理解为检查语音承载的使用情 况, 即检查紧急呼叫是否结束。 当注销定时器时间到达后, P-GW将该 UE 的非语音承载释放, 由于非语音承载通常用于信令承载, 而且承载的释放 将通知到 MME; 在 MME收到承载释放消息后, MME检测该 UE已经没 有任何承载信息 (信令承载-非 GBR承载、 语音承载 - GBR承载), 从而 释放公用数据网 (PDN, Public Data Networks )连接, 进一步触发针对该 UE的注销事件。
图 12描述了上述 P-GW通过设置注销定时器, 以触发 MME注销紧急 附着的 UE的方法, 包括以下步骤:
步骤 1201 , UE紧急附着到 EPS网络, 创建缺省承载。
步骤 1202, UE发起紧急呼叫, 直到通话结束。
步骤 1203 , UE或者 PCRF通知 P-GW释放紧急呼叫的语音承载, P-GW 收到通知后释放相应的 7 载。
当存在动态 PCC时, P-CSCF通过 PCRF通知 P-GW释放该语音承载; 当不存在动态 PCC时, UE通知 P-GW释放该语音承载。
步骤 1204, P-GW根据紧急 PDN连接上是否存在语音承载判断紧急通 话是否已结束: 当收到步骤 1203的语音承载释放请求消息时, P-GW检查 紧急 PDN连接上的语音承载数量, 当 P-GW检测到紧急 PDN连接上语音 载全部释放时, P-GW为 UE启动针对该 PDN连接的注销定时器。
步骤 1205 , 当注销定时器时间到达时, P-GW释放该紧急 PDN连接上 所有非语音承载, 并进而触发该紧急 PDN连接的释放。 这些被释放的非语 音承载通常是信令承载。
步骤 1206, P-GW向 MME通知释放非语音承载; MME判断紧急 PDN 连接上的所有承载均被释放, MME释放该紧急 PDN连接。
步骤 1207, 若 MME检测到该 UE的所有 PDN连接均释放, MME触 发针对该 UE的隐式注销, 即可以不通知 UE从而将 UE从网络注销。
步骤 1208, 可选地, MME通过空口信令通知 UE该注销事件。
在 P-GW上设置的注销定时器, 其值可以在 UE初始附着,且 MME要 求 S-GW/P-GW为 UE创建默认承载时传递给 P-GW,也可以由 P-GW自行 设置, 或者通过运营维护***来设置。
对应上述注销定时器设置在 P-GW的实现方式, 本发明还提供了一种 注销紧急呼叫用户的***, 该***包括: 用户终端和分组数据网关。 其中,
用户终端, 用于紧急附着到 EPS网络, 并执行紧急呼叫。 分组数据网关, 用于在用户终端紧急附着到 EPS网络时, 根据接收到的释放紧急呼叫用户 的语音承载的消息释放语音承载, 检查释放信令承载的条件是否满足, 如 果满足, 启动位于 P-GW 中的注销定时器; 当注销定时器时间到达时, 释 放紧急呼叫的信令承载。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。
Claims
1、 一种注销紧急呼叫用户的方法, 其特征在于, 该方法包括: 在用户终端 UE紧急附着到演进分组*** EPS网络, 且移动管理实体 MME才艮据接收的消息确定所述 UE的紧急呼叫结束时, 所述 MME启动注 销定时器;
所述 MME在注销定时器时间到达时, 将所述 UE从 EPS网络注销。
2、 根据权利要求 1所述注销紧急呼叫用户的方法, 其特征在于, 所述 接收的消息为指明承载的释放消息, 所述启动注销定时器具体为:
所述 MME根据所述指明承载的释放消息确定所述 UE的紧急呼叫结 束,并在确定所述 UE是紧急附着或者处于受限制模式时,启动注销定时器。
3、 根据权利要求 1所述注销紧急呼叫用户的方法, 其特征在于, 所述 接收的消息为无线资源控制的空闲 RRC-IDLE消息, 所述启动注销定时器 具体为:
所述 MME根据所述 RRC-IDLE消息确定所述 UE的紧急呼叫结束,并 在确定所述 U E是紧急附着或者处于受限制模式时, 启动注销定时器。
4、 根据权利要求 1所述注销紧急呼叫用户的方法, 其特征在于, 所述 接收的消息为周期性跟踪区域更新 TAU请求消息, 所述启动注销定时器具 体为:
所述 MME根据所述周期性 TAU请求消息确定所述 UE的紧急呼叫结 束,并在确定所述 UE是紧急附着或者处于受限制模式时,启动注销定时器。
5、 根据权利要求 1、 2、 3或 4所述注销紧急呼叫用户的方法, 其特征 在于, 在 UE紧急附着到 EPS网络之后, 该方法进一步包括:
所述 MME在 UE紧急附着成功后启动所述注销定时器,并在指明承载 创建完成后取消所述注销定时器。
6、 根据权利要求 5所述注销紧急呼叫用户的方法, 其特征在于, 所述
指明承载的创建和释放由策略计费控制 PCC实体控制实现, 或由所述 UE 控制实现。
7、 一种注销紧急呼叫用户的方法, 其特征在于, 该方法进一步包括: 在 UE紧急附着到 EPS网络后, 所述 MME将注销定时器通过附着响 应发送给所述 UE;
所述 UE在紧急呼叫结束时,启动注销定时器,并在所述注销定时器时 间到达时, 从所述 EPS网络注销。
8、 一种注销紧急呼叫用户的***, 其特征在于, 该***包括: 用户终端, 用于紧急附着到 EPS网络, 并执行紧急呼叫;
移动管理实体, 用于在所述用户终端紧急附着到 EPS网络, 并根据接 收的消息确定所述用户终端的紧急呼叫结束时, 启动注销定时器; 待注销 定时器时间到达时, 将所述用户终端从 EPS网络注销。
9、 根据权利要求 8所述注销紧急呼叫用户的***, 其特征在于, 所述 接收的消息为指明承载的释放消息、 或 RRC-IDLE消息、 或周期性 TAU请 求消息。
10、 根据权利要求 8或 9所述注销紧急呼叫用户的***, 其特征在于, 所述移动管理实体还用于在用户终端紧急附着到 EPS网络后, 将所述注销 定时器通过附着响应发送给所述用户终端; 相应的, 所述用户终端还用于 在紧急呼叫结束时, 启动注销定时器, 并在所述注销定时器时间到达时, 从所述 EPS网络注销。
11、 一种注销紧急呼叫用户的方法, 其特征在于, 该方法包括: 所述 UE完成紧急呼叫时, 分组数据网网关 P-GW根据接收到的释放 紧急呼叫用户的语音承载的消息释放语音承载, 检查释放信令承载的条件 是否满足, 如果满足, 启动位于 P-GW 中的注销定时器, 当注销定时器时 间到达时, 释放所述紧急呼叫的信令承载。
12、 根据权利要求 11所述的方法, 其特征在于, 所述检查释放信令承 载的条件是: 所述 P-GW上的紧急公共数据网 PDN连接上语音承载全部释 放完毕。
13、 根据权利要求 12所述的方法, 其特征在于, 所述 P-GW接收到的 释放紧急呼叫用户的语音承载的消息是从所述 UE发起或者从 PCC发起的。
14、 根据权利要求 12或 13所述的方法, 其特征在于, 所述启动注销 定时器, 当注销定时器时间到达时, 释放所述紧急呼叫的信令承载具体包 括以下步骤:
注销定时器启动, 当注销定时器时间到达的时候, P-GW释放该紧急 PDN连接上所有非语音承载, 并且通知 EPS网络相关的网元注销所述的紧 急呼叫。
15、 一种注销紧急呼叫用户的***, 其特征在于, 该***包括: 用户终端, 用于紧急附着到 EPS网络, 并执行紧急呼叫;
分组数据网关 P-GW, 用于在所述用户终端紧急附着到 EPS 网络时, 根据接收到的释放紧急呼叫用户的语音承载的消息释放语音承载, 检查释 放信令承载的条件是否满足, 如果满足, 启动位于 P-GW中的注销定时器, 当注销定时器时间到达时, 释放所述紧急呼叫的信令^载。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910080378.6 | 2009-03-20 | ||
CN200910080378 | 2009-03-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010105485A1 true WO2010105485A1 (zh) | 2010-09-23 |
Family
ID=42739160
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/075989 WO2010105485A1 (zh) | 2009-03-20 | 2009-12-24 | 一种注销紧急呼叫用户的方法和*** |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2010105485A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114071658A (zh) * | 2020-07-29 | 2022-02-18 | 大唐移动通信设备有限公司 | 一种终端设备的注册方法及装置 |
WO2023061347A1 (zh) * | 2021-10-14 | 2023-04-20 | 维沃移动通信有限公司 | 通话处理方法、装置、电子设备及存储介质 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008074669A1 (en) * | 2006-12-21 | 2008-06-26 | Nokia Corporation | Emergency service in a communication system |
CN101227352A (zh) * | 2007-01-15 | 2008-07-23 | 华为技术有限公司 | 用户终端紧急注册到ip连接接入网络的方法及*** |
-
2009
- 2009-12-24 WO PCT/CN2009/075989 patent/WO2010105485A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008074669A1 (en) * | 2006-12-21 | 2008-06-26 | Nokia Corporation | Emergency service in a communication system |
CN101227352A (zh) * | 2007-01-15 | 2008-07-23 | 华为技术有限公司 | 用户终端紧急注册到ip连接接入网络的方法及*** |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114071658A (zh) * | 2020-07-29 | 2022-02-18 | 大唐移动通信设备有限公司 | 一种终端设备的注册方法及装置 |
CN114071658B (zh) * | 2020-07-29 | 2023-09-01 | 大唐移动通信设备有限公司 | 一种终端设备的注册方法及装置 |
WO2023061347A1 (zh) * | 2021-10-14 | 2023-04-20 | 维沃移动通信有限公司 | 通话处理方法、装置、电子设备及存储介质 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10601638B2 (en) | Methods and apparatuses for facilitating P-CSCF restoration when a P-CSCF failure has occurred | |
JP4545436B2 (ja) | ネットワーク識別される非常セッションを取り扱う方法及びシステム | |
CN101841793B (zh) | 一种注销紧急呼叫用户的方法和*** | |
AU2001258380A1 (en) | Method and system for handling a network-identified emergency session | |
JP5383854B2 (ja) | 通信システム、移動局及び通信方法 | |
WO2008046319A1 (fr) | Procédé et système pour assurer la continuité d'un appel vocal lors de la gestion d'une affaire urgente | |
JPWO2016185962A1 (ja) | 移動通信システム、通信制御装置、移動管理エンティティ及び移動通信方法 | |
WO2010108350A1 (zh) | 附着状态改变方法、装置以及用户设备 | |
WO2011020273A1 (zh) | 一种紧急业务的处理方法和*** | |
WO2010105485A1 (zh) | 一种注销紧急呼叫用户的方法和*** | |
JP5865161B2 (ja) | 通信制御装置及び通信制御方法 | |
JP5337889B2 (ja) | 移動局及び通信方法 | |
WO2010127530A1 (zh) | 一种ip多媒体子***业务的建立方法及*** | |
WO2012130126A1 (zh) | 基于ims的控制切换方法及*** | |
JP5841468B2 (ja) | VoLTEサービスの通信規制方法およびシステム | |
WO2010127529A1 (zh) | 一种ip多媒体子***业务的建立方法及*** | |
WO2011054270A1 (zh) | 一种实现位置区域更新的方法及*** | |
WO2016185964A1 (ja) | 移動通信システム、通信制御装置、移動管理エンティティ及び移動通信方法 | |
WO2010099691A1 (zh) | 控制用户设备接入的方法、移动性管理网元和用户设备 | |
WO2011020401A1 (zh) | 一种传输区域信息的方法及*** | |
JP2008092599A (ja) | ネットワーク識別される非常セッションを取り扱う方法及びシステム | |
JP2015122561A (ja) | ネットワーク装置、無線基地局、ユーザ装置及び移動通信方法 |
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: 09841768 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: 09841768 Country of ref document: EP Kind code of ref document: A1 |