WO2008086754A1 - Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur - Google Patents

Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur Download PDF

Info

Publication number
WO2008086754A1
WO2008086754A1 PCT/CN2008/070098 CN2008070098W WO2008086754A1 WO 2008086754 A1 WO2008086754 A1 WO 2008086754A1 CN 2008070098 W CN2008070098 W CN 2008070098W WO 2008086754 A1 WO2008086754 A1 WO 2008086754A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency
network
network element
bearer
request message
Prior art date
Application number
PCT/CN2008/070098
Other languages
English (en)
Chinese (zh)
Inventor
Wenfu Wu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008086754A1 publication Critical patent/WO2008086754A1/fr

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 an Internet Multimedia Subsystem (IMS: IP Multimedia Subsystem) emergency service technology, and more particularly to a method for urgently registering an IP-Connectivity Access Network (IP-CAN) with a User Equipment (UE).
  • IMS Internet Multimedia Subsystem
  • IP-CAN IP-Connectivity Access Network
  • UE User Equipment
  • IMS emergency services use IP-CAN and IMS systems to provide users with emergency services, such as 110 alarm services and 119 fire alarm services.
  • emergency services such as 110 alarm services and 119 fire alarm services.
  • the IP-CAN network may include: a Global Packet Radio System (GPRS), a Universal Mobile Telecommunication System (UMTS), and a System Architecture Evolution (SAE) network.
  • GPRS Global Packet Radio System
  • UMTS Universal Mobile Telecommunication System
  • SAE System Architecture Evolution
  • FIG. 1 is a schematic flowchart of a method for UE to urgently register to a GPRS network in the prior art.
  • a global mobile communication system radio access network/enhanced data rate GSM evolution technology GERAN, GSM/EDGE Radio Access Network
  • UTRAN universal terrestrial radio access network
  • UMTS Territorial Radio Access Network a global mobile communication system radio access network/enhanced data rate GSM evolution technology
  • UTRAN Universal terrestrial radio access network
  • UMTS Territorial Radio Access Network UMTS Territorial Radio Access Network
  • the wireless access part, the Serving GPRS Supporting Node (SGSN) is used to implement functions such as route forwarding, mobility management, session management, and user information storage.
  • SGSN Serving GPRS Supporting Node
  • the gateway general packet radio service support node (GGSN, Gateway) GPRS Supporting Node) is the interface between the GPRS network and the external network, and is also responsible for Realize the transmission of user plane data.
  • GGSN Gateway
  • GPRS Supporting Node is the interface between the GPRS network and the external network, and is also responsible for Realize the transmission of user plane data.
  • SIM Subscriber Identity Module
  • the subscription data is obtained in the register (HLR, Home Location Register).
  • the method shown in Figure 1 is defined by the Third Generation Partnership Project (3GPP, Third Generation Partnership Project) TR23.867, which includes the following steps:
  • Step 101 The UE sends an attach request message to the SGSN, where the message carries an emergency indication bit to indicate that the request is an emergency registration request.
  • Step 102 The SGSN accepts the emergency attach request of the UE, and sends an attach accept message to the UE.
  • Step 103 After receiving the attach accept message, the UE sends an attach complete message to the SGSN. After the above steps 101 to 103, the UE is urgently attached to the GPRS network, and the UE initiates an emergency bearer setup request to the GPRS network to complete the establishment of the emergency bearer.
  • Step 104 The UE sends an Activate Packet Data Protocol (PDP) Context Request message to the SGSN, requesting the SGSN to establish an emergency payload.
  • PDP Packet Data Protocol
  • Step 105 The SGSN creates a PDP context used by the IMS emergency service, and sends a PDP context request message to the GGSN, requesting the GGSN to create a PDP context used by the IMS emergency service.
  • the PDP context used by the IMS emergency service is called the emergency PDP context.
  • Step 106 After receiving the Create PDP Context Request message, the GGSN creates an emergency PDP context, and returns a Create PDP Context Response message to the SGSN.
  • Step 107 The SGSN initiates radio bearer establishment to the GERAN/UTRAN to establish a radio bearer.
  • Steps 108 to 109 After the radio bearer is established, if the quality of service (QoS, Quality If the parameter changes, the SGSN sends a Modify PDP Context Request message to the GGSN, and the GGSN returns a Modify PDP Context Response message to the SGSN. If the QoS parameters have not changed, steps 108 and 109 may be omitted, so the figure is shown by a broken line. .
  • QoS Quality of service
  • Step 110 The SGSN sends an Activate PDP Context Accept message to the UE.
  • the method flow of the UE in the prior art to urgently register to the GPRS network is ended.
  • the inventor of the present application finds in the process of implementing the present invention that when the UE initiates an emergency attach, it means that the UE can only perform IMS emergency services, and accordingly, the UE initiates the emergency attach procedure only when performing IMS emergency services. Therefore, after the UE initiates an emergency attach, an emergency bearer must be created for the UE.
  • the UE emergency attach and emergency bearer creation in the prior art are implemented in the two message interaction steps of steps 101 to 103 and steps 104 to 108, respectively, resulting in the creation of an emergency load in the GPRS network. The delay is relatively large, and the message interaction process is cumbersome.
  • the method for urgently registering a UE into an IP-CAN network disclosed in the embodiment of the present invention provides a method for creating an IMS emergency service bearer while the UE is urgently registered to the IP-CAN network, thereby shortening the creation of an emergency. The delay of the bearer.
  • the system for urgently registering the UE into the IP-CAN network disclosed in the embodiment of the present invention provides a system for creating an IMS emergency service bearer while the UE is urgently registered to the IP-CAN network, thereby shortening the delay for creating an emergency bearer. .
  • the first network element on the network side which is applicable to the system for emergency registration of the UE to the IP-CAN network, which is disclosed in the embodiment of the present invention, provides the same type of emergency registration to the IP-CAN network in the UE.
  • the first network element on the network side of the IMS emergency service bearer is created, which shortens the delay for creating an emergency bearer.
  • the second network element on the network side which is applicable to the UE for emergency registration to the IP-CAN network, disclosed in the embodiment of the present invention, provides a network for creating an IMS emergency service bearer while the UE is urgently registered to the IP-CAN network.
  • the second network element on the side shortens the delay for creating an emergency bearer.
  • a method for a UE to register an IP-CAN to an IP-connected access network including:
  • the network side network element in the IP-CAN network receives the emergency registration request message sent by the UE; the network side network element in the IP-CAN network creates an emergency bearer corresponding to the emergency registration request.
  • a system for UEs to urgently register to an IP-CAN network including:
  • a UE configured to send an emergency registration request message
  • the network side network element is configured to create an emergency bearer according to the emergency registration request message.
  • a network-side first network element is used in a system for UE to register urgently into an IP-CAN network, including:
  • the first interface module is configured to receive an emergency registration request message from the UE, where the first bearer creation module is configured to create an emergency bearer according to the emergency registration request message.
  • a second network element on the network side is used in the system for urgently registering the UE into the IP-CAN network, including:
  • a second interface module configured to receive a request message from the first network element on the network side, and send a corresponding response message to the first network element on the network side;
  • the second bearer creation module is configured to create a corresponding emergency commitment according to the request message And returning, by using the second interface module, a corresponding response message to the first network element on the network side.
  • the UE sends an emergency registration request message to the network side network element in the IP-CAN network; when the network side network element in the IP-CAN network receives the received
  • the emergency registration request message of the UE is received, the emergency registration request is accepted and an emergency bearer corresponding to the emergency registration request is created, so that the UE can create an IMS emergency service bearer while urgently registering to the IP-CAN network, thereby reducing Delay and message interaction created by emergency bearers in IP-CAN networks.
  • FIG. 1 is a schematic flowchart of a method for a UE to urgently register to a GPRS network in the prior art
  • FIG. 2 is an exemplary flowchart of a method for an UE to urgently register to an IP-CAN network according to the present invention
  • FIG. 3 is an emergency of a UE according to Embodiment 1 of the present invention
  • FIG. 4 is a schematic flowchart of a method for a UE to urgently register to a SAE network according to Embodiment 2 of the present invention
  • FIG. 5 is a schematic flowchart of a method for an UE to urgently register to a SAE network according to Embodiment 3 of the present invention
  • FIG. 6 is a schematic flow chart of a method for a UE to urgently register to a SAE network according to Embodiment 4 of the present invention
  • FIG. 7 is a schematic flowchart of a method for an UE to urgently register to a SAE network according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic flowchart of a method for an UE to urgently register to a GPRS/UMTS network according to Embodiment 6 of the present invention
  • FIG. 9 is a structural diagram of a system for an emergency registration of a UE to an IP-CAN network according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a first network element on a network side in the system shown in FIG. 9.
  • FIG. 11 is a schematic structural diagram of a second network element on a network side in the system shown in FIG. Mode for carrying out the invention
  • FIG. 2 is an exemplary flowchart of a method for UE to urgently register to an IP-CAN network according to the present invention. Referring to Figure 2, the method includes the following steps:
  • Step 201 The UE sends a request message indicating an emergency registration to a network side network element in the IP-CAN network.
  • Step 202 When the network side network element in the IP-CAN network receives the request message indicating the emergency registration from the UE, create an emergency bearer corresponding to the emergency registration request.
  • the emergency bearer represents the bearer used by the IMS emergency service, and the bearer includes the bearer between the relevant network elements in the core network and the radio bearer between the core network and the radio access network.
  • the network side network element in the IP-CAN network includes a first network element on the network side and a second network element on the network side, and the emergency bearer between the related network elements in the core network is established on the first network element and the network on the network side. Between the second network elements on the side. After the first network element on the network side receives the emergency registration request message from the UE, the manner of establishing an emergency bearer between the related network elements in the core network may include the following:
  • the first way is:
  • the first network element on the network side creates an emergency user context and an emergency payload context, and sends a request message indicating that an emergency bearer is created to the second network element on the network side;
  • the second network element on the network side creates a tight request message according to the representation to create an emergency bearer.
  • the emergency bearer context, the policy of the emergency bearer and the policy and charging control (PCC) are executed, and the PCC rule is executed, and the bearer response message is returned to the first network element on the network side.
  • PCC policy and charging control
  • the second way is:
  • the first network element on the network side creates an emergency user context, and forwards the received request message indicating emergency registration to the second network element on the network side;
  • the second network element on the network side creates an emergency bearer context, obtains the PCC rule of the emergency bearer according to the request message indicating the emergency registration, and executes the PCC rule to return an emergency registration accept message to the first network element on the network side.
  • the third way is:
  • the first network element on the network side creates an emergency user context and an emergency PDP context, and sends a request message indicating that an emergency PDP context is created to the second network element on the network side;
  • the second network element on the network side creates an emergency PDP context according to the request message indicating that the emergency PDP context is created, acquires the PCC rule of the emergency bearer, and executes the PCC rule, and returns a create PDP context response message to the first network element on the network side.
  • the request message box indicating the emergency registration is referred to as an emergency registration request message
  • the request message tube indicating the creation of the emergency bearer is referred to as an emergency bearer creation request message, which will indicate that the emergency PDP context is created.
  • the request message cartridge is called an emergency PDP context creation request message.
  • the method shown in Figure 2 can be applied to IP-CAN networks such as GPRS, UMTS and SAE.
  • the SAE network is a new evolutionary network architecture that 3GPP is studying.
  • the evolved packet core network includes a mobility management entity (MME, Mobility Management Entity), a user plane entity (UPE, User Plane Entity), and a user plane error point between different access systems (IASA, Inter Access).
  • MME mobility management entity
  • UPE User Plane Entity
  • IASA Inter Access
  • System Anchor also features functional entities.
  • the MME is responsible for mobility management of the control plane, including user context management, mobility state management, assigning user temporary identity, etc., and the MME corresponds to a control plane part of the internal SGSN of the current GPRS/UMTS system;
  • the UPE is responsible for initiating paging for downlink data, managing and storing IP bearer parameters, and intra-network routing information in an idle state, and the UPE corresponds to a data plane portion of the internal SGSN and the GGSN of the current GPRS/UMTS system;
  • the 3GPP Anchor logical function entity is the user plane anchor between the 2G/3G access system and the Long Term Evolution (LTE) access system.
  • the SAE Anchor logical function entity is the 3GPP interface. The user is in the wrong point between the system and the non-3GPP access system.
  • the MME and UPE separation architecture may be adopted, that is, the MME and the UPE are respectively set up. Between the MME and the UPE, the MME and the UPE are in the same physical entity, which is denoted as MME/UPE.
  • the MME is an independent entity, and the UPE and the IASA are located in the same entity and are recorded as UPE/IASA.
  • the MME corresponds to the first network element on the network side
  • the UPE/IASA corresponds to the second network element on the network side.
  • SM session management
  • the MME and the UPE/IASA use the first method to establish an emergency bearer between the relevant network elements in the core network;
  • the MME and the UPE/IASA use the second method to establish an emergency bearer between related NEs in the core network.
  • the radio bearer setup procedure under this architecture may be initiated by the MME entity or by the UPE/IASA entity.
  • the MME and the UPE are in the same entity, and the IASA is a separate entity.
  • the MME/UPE corresponds to the first network element on the network side
  • the IASA corresponds to the upper network element.
  • the session management function is implemented in the MME/UPE entity.
  • the MME/UPE and the IASA use the first method to establish an emergency bearer between the related network elements in the core network.
  • the radio bearer establishment procedure in the architecture is performed by the MME/ The UPE entity initiates.
  • the SGSN corresponds to the first network element on the network side
  • the GGSN corresponds to the second network element on the network side.
  • the SGSN and the GGSN use the third method to establish an emergency bearer between the related network elements in the core network, and the radio bearer establishment process is initiated by the SGSN.
  • the embodiments illustrate specific embodiments of the technical solution of the present invention for a GPRS/UMTS network.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the architecture of the evolved network SAE is separated from the MME and the UPE.
  • the session management function is implemented in the MME entity, and the MME controls the establishment of the emergency bearer, and the radio bearer establishment procedure is initiated by the MME entity.
  • the emergency registration process in the actual application may further include other steps not described in this embodiment, which are not described in this embodiment. For the steps, refer to the prior art and implement the technical solution according to the embodiment, and details are not described herein again.
  • FIG. 3 is a schematic flowchart of a method for an UE to urgently register to a SAE network according to Embodiment 1 of the present invention. Referring to Figure 3, the method includes the following steps:
  • Step 301 The UE sends an emergency registration request message to the MME.
  • the UE may notify the MME in the following manners, and the request message sent by the UE to the MME is an emergency registration request message:
  • the UE carries an Emergency Indicator in the Attach Request message sent to the MME, or carries the emergency indicator in the Tracking Area Update Request (TAU) message sent to the MME. , or in other requests that can notify the MME that the request message sent is an urgent registration request message
  • the emergency indicator is carried in the interest.
  • the emergency attachment type indicates that an attach request message is an urgent registration request message
  • the UE sets the attachment type of the attach request message in the attach request message sent to the MME. For emergency attachment.
  • the emergency update type indicates that a certain tracking area update request message is an urgent registration request message, and the UE sets the tracking area in the tracking area update request message sent to the MME.
  • the update type of the update request message is an urgent update.
  • the emergency tracking area update request message indicates an urgent registration request
  • the UE sends the emergency tracking area update request message to the MME.
  • the UE may also notify the core network that the request initiated by the UE is an emergency registration request by other feasible means.
  • Step 302 After receiving the emergency registration request message sent by the UE, the MME creates an emergency user context and an emergency context, and notifies the corresponding UPE/IASA to create an emergency payload.
  • the MME may set an emergency identifier in the user context and the load context to identify that the user context is an emergency user context, and the load is an emergency load.
  • the emergency indicator bit may be used as the emergency identifier, or a type indicating that the user context is the emergency user context may be defined, and the emergency user context type is used as the emergency identifier; in the bearer context, a specific access may be used.
  • APN Access Point Name
  • a globally dedicated emergency APN is used as an emergency identifier
  • an emergency indicator can also be used as an emergency identifier. It is also possible to define a type indicating that the bearer context is an emergency bearer, and the emergency bearer type is used as an emergency identifier.
  • the MME determines the UPE/IASA used to create the emergency bearer.
  • the MME can determine the UPE/IASA used to create an emergency bearer in the following ways:
  • the MME can determine the used UPE/IASA according to the specific APN.
  • UPE/IASA The way UPE/IASA is used:
  • the MME queries the corresponding UPE/IASA from the DNS server according to the specific APN, and queries the obtained UPE/IASA. Determine the UPE/IASA used to create the emergency bearer.
  • DNS Domain Name Server
  • the specific APN may be sent by the UE to the MME in the emergency registration request message, or when the MME determines that the request message sent by the UE is an emergency registration message, the APN is selected to identify an emergency bearer.
  • an emergency may be configured inside the MME.
  • the UPE/IASA used by the bearer is used by the MME to determine the UPE/IASA used to create the emergency bearer according to the configuration.
  • the MME determines a UPE/IASA in the local network as the UPE/IASA used to create the emergency payload. For example, an appropriate UPE/IASA is determined according to the location information of the user.
  • the MME sends an emergency bearer creation request message to the determined UPE/IASA, Notify the UPE/IASA to create an emergency 7
  • the MME may notify the determined UPE/IASA to create an emergency bearer by:
  • the MME sends a Create Bearer Request message to the UPE/IASA, and carries a specific APN (such as a globally dedicated emergency APN) in the Create Bearer Request message, and the UPE/IASA determines that the specific APN needs to be created according to the specific APN.
  • the bearer is an emergency bearer.
  • the MME sends a Create Bearer Request message to the UPE/IASA, and carries the emergency indication bit in the Create Bearer Request message.
  • the UPE/IASA determines that the bearer to be created is an emergency bearer according to the indication bit.
  • the MME sends a create request message to UPE/IASA (Create Bearer)
  • the UPE/IASA determines that the bearer to be created is an emergency bearer according to the bearer type.
  • Step 303 The UPE/IASA creates an emergency bearer according to the notification of the MME, and sends a Policy and Charging Rule Request message (Request Policy and Charging Rules) to the Policy and Charging Rule Function (PCRF) to obtain Emergency bearer PCC rules.
  • Policy and Charging Rule Request message Request Policy and Charging Rules
  • PCRF Policy and Charging Rule Function
  • the PCRF is a functional entity in the PCC network, and mainly performs policy control decision functions and flow charging control functions.
  • the UPE/IASA may first set an emergency identifier in the context of the bearer to identify the bearer as an emergency bearer.
  • an emergency identifier for example: Global
  • the globally dedicated emergency APN is used as the emergency identifier.
  • the emergency indicator can also be used as the emergency identifier. It can also define a type indicating that the bearer context is urgent. The emergency type is used as the emergency identifier.
  • UPE/IASA sends a policy and charging rule request message to the PCRF to obtain the PCC rules of the emergency bearer.
  • the identifier may be carried in the following manner to notify the PCRF that the bearer established is used for the IMS emergency service:
  • the PCC rules related to the IMS emergency service can be pre-configured in the UPE/IASA.
  • the UPE/IASA can use the pre-configured PCC rules without obtaining the PCRF.
  • Step 304 When the PCRF determines, according to the identifier in the policy and charging rule request message from the UPE/IASA, that the bearer is a bearer used for the IMS emergency service, the PCRF provides the PCC rule used by the pre-configured IMS emergency service to the UPE. /IASA, which sends policy and charging rule provisioning messages to UPE/IASA (Policy and Charging Rules Provision ⁇
  • the rule configuration method pre-configures the PCC rules corresponding to the IMS emergency services.
  • Step 305 The UPE/IASA executes the acquired PCC rule, and returns a bearer response message (Bearer Response) to the MME.
  • the application function entity is a functional entity in the PCC network and is used to provide various service applications.
  • the address of the AF used by a certain service may be configured in the UPE/IASA.
  • the address is the address of the Call Session Control Agent Function Entity (P-CSCF), and the address will be sent to the UE through the MME. So that the UE can use the services provided by the AF or P-CSCF.
  • P-CSCF Call Session Control Agent Function Entity
  • the AF address used by the IMS emergency service can be configured in the UPE/IASA.
  • the AF address used by the IMS emergency service is carried in the bearer response message and sent to the MME.
  • Step 306 The MME initiates a radio bearer setup request to the Evolved RAN, and the Evolved RAN establishes a radio bearer.
  • the wireless bearer of the access network can be established according to the relevant provisions in 3GPP TR23.882, and details are not described herein again.
  • Step 307 After the radio bearer is successfully established, the MME returns a bearer acknowledgement message (Bearer Ack) to the UPE/IASA.
  • Bearer Ack bearer acknowledgement message
  • Step 308 After the radio bearer is successfully established, the MME returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform a periodic tracking area update process. Therefore, in this step, the MME sets the period tracking area update timer to 0 in the emergency registration accept message, or carries the indicator bit to indicate the period tracking. The zone update timer is deactivated. After receiving such a message, the UE will not activate the periodic tracking area update timer, and does not perform the periodic tracking area update process. Step 309: After receiving the emergency registration accept message from the MME, the UE sends the message to the MME. Send an emergency registration completion message to confirm the completion of the emergency registration.
  • Embodiment 2 the method flow of the UE urgently registering to the SAE network in the first embodiment of the present invention is ended.
  • Embodiment 2 the method flow of the UE urgently registering to the SAE network in the first embodiment of the present invention is ended.
  • the architecture of the evolved network SAE is separated from the MME and the UPE, and the session management function is implemented in the MME entity.
  • the MME controls the establishment of the emergency bearer, and the radio bearer establishment process is initiated by the UPE/IASA entity.
  • the emergency registration process in the actual application may further include other steps not described in this embodiment, which are not described in this embodiment. For the steps, refer to the prior art and the technical solution according to the embodiment of the present invention, and details are not described herein again.
  • FIG. 4 is a schematic flow chart of a method for an UE to urgently register to a SAE network according to Embodiment 2 of the present invention. Referring to Figure 4, the method includes the following steps:
  • Step 401 The UE sends an emergency registration request message to the MME.
  • the manner in which the UE sends the emergency registration request message to the MME is the same as that in the first step 301 of the embodiment, and details are not described herein again.
  • Step 402 After receiving the emergency registration request message sent by the UE, the MME creates an emergency user context and an emergency bearer context, and notifies the corresponding UPE/IASA to create an emergency bearer.
  • the MME may set an emergency identifier in the user context and the bearer context in the same manner as in the step 302 of the embodiment to identify that the user context is an emergency user context, and the bearer is an emergency bearer.
  • the MME determines the UPE/IASA used to create the emergency 7 load.
  • the manner in which the MME determines the UPE/IASA is the same as that in the first step 302 of the first embodiment, and details are not described herein again.
  • the MME sends an emergency bearer creation request message to the determined UPE/IASA to notify the UPE/IASA to create an emergency bearer.
  • the MME sends a tight message to UPE/IASA
  • the urgent bearer creation request message is also consistent with the corresponding message in the step 302 of the first embodiment. Please refer to the related description in step 302 of the first embodiment.
  • Step 403 The UPE/IASA creates an emergency payload according to the notification of the MME, and sends a Policy and Charging Rules request message to the PCRF to obtain the PCC rule of the emergency bearer.
  • the UPE/IASA can set the emergency identifier in the bearer context in the same manner as in the step 303 of the first embodiment to identify the bearer as an emergency bearer.
  • UPE/IASA sends a policy and charging rule request message to the PCRF to obtain the PCC rules of the emergency bearer.
  • the method of carrying the identifier in the policy and charging rule request message to notify the PCRF to be used for the IMS emergency service is the same as the method in the step 303 of the first embodiment, and details are not described herein again.
  • the PCC rules related to the IMS emergency service can be pre-configured in the UPE/IASA.
  • the UPE/IASA can use the pre-configured PCC rules without obtaining the PCRF.
  • Step 404 When the PCRF determines, according to the identifier in the policy and charging rule request message from the UPE/IASA, that the bearer is a bearer used for the IMS emergency service, the PCRF provides the PCC rule used by the pre-configured IMS emergency service to the UPE. /IASA, which sends policy and charging rule provisioning messages to UPE/IASA (Policy and Charging Rules Provision ⁇
  • the PCC rules corresponding to the IMS emergency service can be pre-configured according to the configuration requirements of the existing PCC rules according to the related service requirements of the IMS emergency service.
  • Step 405 The UPE/IASA executes the acquired PCC rule, and initiates a wireless bearer setup request to the Evolved RAN, and the Evolved RAN establishes a radio bearer.
  • the radio bearer of the access network may be established according to the relevant provisions in 3GPP TR23.882, and details are not described herein again.
  • Step 406 After the radio bearer is successfully established, the UPE/IASA returns a bearer response message (Bearer Response) to the MME.
  • the AF address used by the IMS emergency service can be configured in the UPE/IASA.
  • the UPE/IASA carries the AF address used by the IMS emergency service in the 7-load response message and sends it to the MME.
  • Step 407 The MME returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform the periodic tracking area update process. Therefore, in this step, the MME sets the periodic tracking area update timer to 0 in the emergency registration accept message, or carries the indication bit to indicate that the periodic tracking area update timer is gone. activation. After receiving such a message, the UE will not activate the cycle tracking area update timer, and will not execute the cycle tracking area update process.
  • Step 408 After receiving the emergency registration accept message from the MME, the UE sends an emergency registration complete message to the MME to confirm the completion of the emergency registration.
  • Embodiment 3 the method flow of the UE urgently registering to the SAE network in the second embodiment of the present invention is ended.
  • the architecture of the evolved network SAE is separated from the MME and the UPE, and the session management function is implemented in the UPE entity.
  • the UPE/IASA controls the establishment of the emergency bearer, and the wireless bearer establishment process is initiated by the MME entity.
  • the emergency registration process in the actual application may further include other steps not described in this embodiment, which are not described in this embodiment. For the steps, refer to the prior art and the technical solution according to the embodiment of the present invention, and details are not described herein again.
  • FIG. 5 is a schematic flowchart of a method for an UE to urgently register to a SAE network according to Embodiment 3 of the present invention. Referring to Figure 5, the method includes the following steps:
  • Step 501 The UE sends an emergency registration request message to the MME.
  • the manner in which the UE sends the emergency registration request message to the MME is the same as that in the first step 301 of the first embodiment, and details are not described herein again.
  • Step 502 After receiving the emergency registration request message sent by the UE, the MME creates an emergency user context, and forwards the emergency registration request message to the corresponding UPE/IASA.
  • the MME may set an emergency identifier in the user context in the same manner as in step 302 of the first embodiment, to identify the user context as an emergency user context, and implement the The method in the first step 302 determines the UPE/IASA used to create the emergency bearer, and finally, forwards the emergency registration request message to the determined UPE/IASA.
  • Step 503 After receiving the emergency registration request message of the MME, the UPE/IASA creates an emergency bearer and sends a Policy and Charging Rules request message to the PCRF to obtain the PCC rule of the emergency bearer.
  • the UPE/IASA can set the emergency identifier in the bearer context in the same manner as in the step 303 of the first embodiment to identify the bearer as an emergency bearer.
  • UPE/IASA sends a policy and charging rule request message to the PCRF to obtain the PCC rules of the emergency bearer.
  • the method of carrying the identifier in the policy and the charging rule request message to notify the PCRF that the bearer is the bearer used by the IMS emergency service is the same as the method in the step 303 of the first embodiment, and details are not described herein again.
  • the PCC rules related to the IMS emergency service can be pre-configured in the UPE/IASA.
  • the UPE/IASA can use the pre-configured PCC rules without obtaining the PCRF.
  • Step 504 When the PCRF determines, according to the identifier in the policy and charging rule request message from the UPE/IASA, that the bearer is a bearer used for the IMS emergency service, the PCRF provides the PCC rule used by the pre-configured IMS emergency service to the UPE. /IASA, which sends policy and charging rules to the UPE/IASA (Policy and Charging Rules) Provision ⁇
  • the PCC rules corresponding to the IMS emergency service can be pre-configured according to the configuration requirements of the existing PCC rules according to the related service requirements of the IMS emergency service.
  • Step 505 The UPE/IASA executes the obtained PCC rule, and sends a request message indicating that the emergency bearer is created to the MME, and notifies the MME to create an emergency bearer.
  • the UPE/IASA can notify the MME to create an emergency bearer as follows:
  • the UPE/IASA sends a Create Bearer Request message to the MME, and carries a specific APN (such as a globally dedicated emergency APN) in the Create Bearer Request message, and the MME determines that the load needs to be created according to the specific APN. Emergency carrying.
  • a specific APN such as a globally dedicated emergency APN
  • the UPE/IASA sends a Create Bearer Request message to the MME, and carries an Emergency Indicator in the Create Request message.
  • the MME determines that the bearer to be created is an emergency bearer according to the indication bit.
  • the UPE/IASA sends a Create Bearer Request message to the MME, and sets the bearer type as an emergency bearer in the Create Bearer Request message.
  • the MME determines, based on the type of the load, that the payload needs to be created as an emergency bearer.
  • Step 506 The MME initiates a radio bearer setup request to the Evolved RAN, and the Evolved RAN establishes a radio bearer.
  • the radio bearer of the access network may be established according to the relevant provisions in 3GPP TR23.882, and details are not described herein again.
  • Step 507 After the radio bearer is successfully established, the MME returns a bearer creation response message (Create Bearer Response) to the UPE/IASA.
  • Step 508 After receiving the bearer creation response message from the MME, the UPE/IASA returns an emergency registration accept message to the MME.
  • the AF address used by the IMS emergency service is configured in the UPE/IASA.
  • the UPE/IASA carries the AF address used by the IMS emergency service in the bearer response message and sends it to the MME.
  • Step 509 After receiving the emergency registration accept message from the UPE/IASA, the MME returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform the periodic tracking area update process. Therefore, in this step, the MME sets the periodic tracking area update timer to 0 in the emergency registration accept message, or carries the indication bit to indicate that the periodic tracking area update timer is gone. activation. After receiving such a message, the UE will not activate the cycle tracking area update timer, and will not execute the cycle tracking area update process.
  • Step 510 After receiving the emergency registration accept message from the MME, the UE sends an emergency registration complete message to the MME to confirm the completion of the emergency registration.
  • Embodiment 4 the method flow of the UE urgently registering to the SAE network in the third embodiment of the present invention is ended.
  • Embodiment 4 the method flow of the UE urgently registering to the SAE network in the third embodiment of the present invention is ended.
  • FIG. 6 is a schematic flowchart of a method for an UE to urgently register to an SAE network according to Embodiment 4 of the present invention. Referring to Figure 6, the method includes the following steps:
  • Step 601 The UE sends an emergency registration request message to the MME.
  • the manner in which the UE sends the emergency registration request message to the MME is the same as that in the first step 301 of the embodiment, and details are not described herein again.
  • Step 602 After receiving the emergency registration request message sent by the UE, the MME creates an emergency user context, and forwards the emergency registration request message to the corresponding UPE/IASA.
  • the MME may set an emergency identifier in the user context in the same manner as in step 302 of the first embodiment, to identify the user context as an emergency user context, and implement the The method in the first step 302 determines the UPE/IASA used to create the emergency bearer, and finally, forwards the emergency registration request message to the determined UPE/IASA.
  • Step 603 After receiving the emergency registration request message of the MME, the UPE/IASA creates an emergency bearer and sends a Policy and Charging Rules request message to the PCRF to obtain the PCC rule of the emergency bearer.
  • the UPE/IASA can set the emergency identifier in the bearer context in the same manner as in the step 303 of the first embodiment to identify the bearer as an emergency bearer.
  • UPE/IASA sends a policy and charging rule request message to the PCRF to obtain the PCC rules of the emergency bearer.
  • the method of carrying the identifier in the policy and charging rule request message to notify the PCRF to be used for the IMS emergency service is the same as the method in the step 303 of the first embodiment, and details are not described herein again.
  • the PCC rules related to the IMS emergency service can be pre-configured in the UPE/IASA.
  • the UPE/IASA can use the pre-configured PCC rules without obtaining the PCRF.
  • Step 604 When the PCRF requests according to the policy and charging rules from the UPE/IASA
  • the PCRF provides the PCC rule used by the pre-configured IMS emergency service to the UPE/IASA, that is, sends the policy and charging rule provisioning message to the UPE/IASA (Policy).
  • Policy Policy and Charging Rules Provision
  • the PCC rules corresponding to the IMS emergency service can be pre-configured according to the configuration requirements of the existing PCC rules according to the related service requirements of the IMS emergency service.
  • Step 605 The UPE/IASA performs the acquired PCC rule, and initiates a wireless 7-layer establishment request to the Evolved RAN, and the Evolved RAN establishes a radio bearer.
  • the wireless bearer of the access network can be established according to the relevant provisions in 3GPP TR23.882, and details are not described herein again.
  • Step 606 After the radio bearer is successfully established, the UPE/IASA returns an emergency registration accept message to the MME.
  • the AF address used by the IMS emergency service is configured in the UPE/IASA.
  • the UPE/IASA carries the AF address used by the IMS emergency service in the emergency registration accept message and sends it to the MME.
  • Step 607 After receiving the emergency registration accept message from the UPE/IAS, the MME returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform the periodic tracking area update process. Therefore, in this step, the MME sets the periodic tracking area update timer to 0 in the emergency registration accept message, or carries the indication bit to indicate that the periodic tracking area update timer is gone. activation. After receiving such a message, the UE will not activate the cycle tracking area update timer, and will not execute the cycle tracking area update process.
  • Step 608 After receiving the emergency registration accept message from the MME, the UE sends an emergency registration complete message to the MME to confirm the completion of the emergency registration.
  • Embodiment 5 the method flow of the UE urgently registering to the SAE network in the fourth embodiment of the present invention is ended.
  • the MME and the UPE are integrated in the evolved network SAE, and the session management function is implemented in the MME/UPE unified entity, and the MME/UPE entity controls the establishment of the emergency bearer, and the radio bearer establishment process Initiated by the MME/UPE entity.
  • the emergency registration process in the actual application may further include other steps not described in this embodiment, which are not described in this embodiment. For the steps, please refer to the prior art and implement according to the main idea of the present invention, and details are not described herein again.
  • FIG. 7 is a schematic flowchart of a method for an UE to urgently register to a SAE network according to Embodiment 5 of the present invention. See Figure 7, which includes the following steps:
  • Step 701 The UE sends an emergency registration request message to the MME/UPE.
  • the manner in which the UE sends the emergency registration request message to the MME/UPE is the same as that in the first step 301 of the first embodiment, and details are not described herein again.
  • Step 702 After receiving the emergency registration request message sent by the UE, the MME/UPE creates an emergency user context and an emergency bearer, and notifies the corresponding IASA to create an emergency bearer.
  • the MME/UPE can set an emergency identifier in the user context and the context of the user in the same manner as in the step 302 of the first embodiment, to identify that the user context is an emergency user context, and the bearer is an emergency bearer.
  • the MME/UPE determines the IASA used to create the emergency bearer.
  • the manner in which the MME/UPE determines the IASA is the same as the manner in which the MME determines the UPE/IASA in the step 302 of the first embodiment, and details are not described herein again.
  • the MME/UPE sends a request message indicating that an emergency bearer is created to the determined IASA, and notifies the IASA to create an emergency bearer.
  • the emergency bearer creation request message sent by the MME/UPE to the IASA is also consistent with the message sent by the MME to the UPE/IASA in the step 302 of the first embodiment. For details, refer to the related description in step 302 of the first embodiment.
  • Step 703 The IASA creates an emergency bearer according to the notification of the MME/UPE, and sends a Policy and Charging Rules request message (Request Policy and Charging Rules) to the PCRF to obtain the PCC rule of the emergency bearer.
  • the IASA can first set an emergency identifier in the context of the payload to identify the bearer as an emergency bearer.
  • a specific APN can be used, for example, a globally dedicated emergency APN is used as an emergency identifier, and an emergency indicator can be defined as an emergency identifier.
  • An emergency bearer type can also be defined as an emergency identifier.
  • the IASA then sends a Policy and Charging Rule Request message to the PCRF to obtain the PCC rules for the emergency bearer.
  • the method of carrying the identifier in the policy and the charging rule request message to notify the PCRF that the bearer is the bearer used by the IMS emergency service is the same as the manner in which the UPE/IASA carries the identifier in the step 303 in the first embodiment. Let me repeat.
  • the IASA can also pre-configure the PCC protocol related to the IMS emergency service.
  • the IASA can use the pre-configured PCC rules without obtaining it in the PCRF.
  • Step 704 When the PCRF determines, according to the identifier in the policy and charging rule request message from the IASA, that the bearer is a bearer used for the IMS emergency service, the PCRF provides the pre-configured PCC rule used by the IMS emergency service to the IASA, that is, Send Policy and Charging Rules Provision to IASA.
  • the PCC rules corresponding to the IMS emergency service can be pre-configured according to the configuration requirements of the existing PCC rules according to the related service requirements of the IMS emergency service.
  • Step 705 The IASA executes the acquired PCC rule and returns a bearer response message (Bearer Response) to the MME/UPE.
  • the AF address used by the IMS emergency service is configured in the IASA.
  • the IASA carries the AF address used by the IMS emergency service in the bearer response message and sends it to the MME/UPE.
  • Step 706 After the MME/UPE receives the response message from the IASA, The Evolved RAN initiates a radio bearer setup and the Evolved RAN establishes a radio bearer.
  • the wireless bearer of the access network can be established according to the relevant provisions in 3GPP TR23.882, and details are not described herein again.
  • Step 707 After the radio bearer is successfully established, the MME/UPE returns a bearer acknowledgement message (Bearer Ack) to the IASA.
  • Bearer Ack bearer acknowledgement message
  • Step 708 The MME/UPE returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform the periodic tracking area update process. Therefore, in this step, the MME sets the periodic tracking area update timer to 0 in the emergency registration accept message, or carries the indication bit to indicate that the periodic tracking area update timer is gone. activation. After receiving such a message, the UE will not activate the cycle tracking area update timer, and will not execute the cycle tracking area update process.
  • Step 709 After receiving the emergency registration accept message from the MME/UPE, the UE sends an emergency registration complete message to the MME/UPE to confirm the completion of the emergency registration.
  • the method flow of the UE urgently registering to the SAE network in the fifth embodiment of the present invention is ended.
  • the foregoing describes in detail how to implement the UE emergency registration to the SAE network by using the five embodiments.
  • the following describes in detail how to implement the UE emergency registration to the GPRS or UMTS network by using the present invention.
  • an emergency registration method of the present invention is implemented in a GPRS or UMTS network as an example.
  • the session management function is implemented by the SGSN to control the establishment of the emergency bearer, and the radio bearer establishment procedure is initiated by the SGSN.
  • the emergency registration process in the actual application may further include other steps not described in this embodiment, which are not described in this embodiment.
  • FIG. 8 is a schematic flowchart of a method for UE to urgently register to a GPRS/UMTS network according to Embodiment 5 of the present invention. Referring to Figure 8, the method includes the following steps:
  • Step 801 The UE sends an emergency registration request message to the SGSN.
  • the manner in which the UE sends the emergency registration request message to the SGSN is the same as that in the first step 301 of the embodiment, and details are not described herein again.
  • Step 802 After receiving the emergency registration request message sent by the UE, the SGSN creates an emergency user context and an emergency PDP context, and notifies the corresponding GGSN to create an emergency PDP context.
  • the SGSN sets an emergency identifier in the user context to identify the user context as an emergency user context.
  • the emergency indicator may be used as an emergency identifier, or an emergency user context type may be defined as an emergency identifier;
  • the medium SGSN sets an emergency identifier to identify that the PDP context is an emergency PDP context (the 7 corresponding to the PDP context is an emergency), and a specific APN can be used, for example, a globally dedicated emergency APN is used as an emergency identifier, and an emergency indication can also be used.
  • the SGSN determines the GGSN used to create the emergency bearer.
  • the manner in which the SGSN determines the GGSN is the same as the manner in which the MME determines the UPE/IASA in the step 302 of the first embodiment, and details are not described herein again.
  • the SGSN sends an emergency PDP context creation request message to the determined GGSN, informing the GGSN to create an emergency PDP context.
  • the SGSN can notify the selected GGSN to create an emergency PDP context by:
  • the SGSN sends a Create PDP Context Request message to the GGSN, and carries a specific APN (such as a globally dedicated emergency APN) in the Create PDP Context Request message, and the GGSN determines the PDP to be created according to the specific APN.
  • the context is an emergency PDP context.
  • the SGSN sends a Create PDP Context Request message to the GGSN, and carries an emergency indicator bit in the Create PDP Context Request message.
  • the GGSN determines that the PDP context to be created is an emergency PDP context.
  • the SGSN sends a Create PDP Context Request message to the GGSN, and sets a PDP context type to an Emergency PDP Context in the Create PDP Context Request message, and the GGSN determines that the PDP context type needs to be created according to the PDP context type.
  • the PDP context is an emergency PDP context.
  • Defining a new message type Create Emergency PDP Context Request, which indicates that an emergency PDP context is created, and the SGSN sends the Create Emergency PDP Context Request message to the GGSN, and the GGSN determines that it needs to be created according to the message type.
  • the PDP context is an emergency PDP context.
  • Step 803 The GGSN creates an emergency PDP context according to the notification of the SGSN, and sends a Policy and Charging Rules request message (Request Policy and Charging Rules) to the PCRF to obtain the PCC rule of the emergency bearer.
  • a Policy and Charging Rules request message Request Policy and Charging Rules
  • the GGSN may first set an emergency identifier in the context of the emergency PDP to identify the payload as an emergency.
  • a specific APN can be used, for example: globally dedicated emergency APN as an emergency identifier, an emergency indication bit can also be defined as an emergency identifier, and an emergency PDP context type can be defined as an emergency identification.
  • the GGSN sends a policy and charging rule request message to the PCRF to obtain the PCC rule of the emergency bearer.
  • the method of carrying the identifier in the policy and charging rule request message to notify the PCRF to be used for the IMS emergency service is the same as the manner in which the UPE/IASA carries the identifier in the step 303 in the embodiment. This will not be repeated here.
  • the GG emergency service related PCC rules can also be pre-configured in the GGSN. Then, at this time, the GGSN can use the pre-configured PCC rules without being acquired in the PCRF.
  • Step 804 When the PCRF determines, according to the identifier in the policy and charging rule request message from the GGSN, that the bearer is a bearer used for the IMS emergency service, the PCRF provides the PCC rule used by the pre-configured IMS emergency service to the GGSN, that is, Send policy and charging rule provisioning messages to the GGSN (Policy and Charging Rules Provision ⁇
  • the PCC rules corresponding to the IMS emergency service can be pre-configured according to the configuration requirements of the existing PCC rules according to the related service requirements of the IMS emergency service.
  • Step 805 The GGSN executes the acquired PCC rule, and returns a Create PDP Context Response message to the SGSN.
  • the AF address used by the IMS emergency service is configured in the GGSN.
  • the GGSN sends the AF address used by the IMS emergency service to the SGSN by sending a PDP context response message.
  • Step 806 After receiving the bearer response message from the GGSN, the SGSN initiates radio bearer setup to the GERAN/UTRAN, and the GERAN/UTRAN establishes a radio bearer.
  • Step 807 After the radio bearer is successfully established, the SGSN returns an emergency registration accept message to the UE, and carries the AF address in the emergency registration accept message.
  • the UE does not need to perform the periodic routing area update process. Therefore, in this step, the MME sets the periodic routing area update timer to 0 in the emergency registration accept message, or carries the indication bit to indicate that the periodic routing area update timer is gone. activation. After receiving such a message, the UE will not activate the periodic routing area update timer and will not perform the periodic routing area update procedure.
  • Step 808 After receiving the emergency registration accept message from the SGSN, the UE sends an emergency registration complete message to the SGSN to confirm the completion of the emergency registration.
  • the embodiment of the present invention sends an emergency registration request message to the network side network element in the IP-CAN network by the UE; when the network side network element in the IP-CAN network receives the emergency from the UE When registering the request message, accepting the emergency registration request and creating an emergency bearer corresponding to the emergency registration request, so that the UE can create an IMS emergency service 7 while urgently registering to the IP-CAN network, thereby reducing IP-CAN The delay and message interaction created by the emergency in the network.
  • FIG. 9 is a schematic structural diagram of a system for an UE to urgently register to an IP-CAN network according to an embodiment of the present invention.
  • the system includes: a UE 910 and a network side network element 920.
  • the network side network element 920 further includes: a network side first network element 921 and a network side second network element 922.
  • the UE 910 is configured to send an emergency registration request message to the network side network element 920.
  • the network side network element 920 is configured to create an emergency according to the emergency registration request message from the UE 910.
  • the functions performed by the network side first network element 921 and the network side second network element 922 are as follows:
  • the network side first network element 921 is configured to create an emergency user context and an emergency bearer context according to the emergency registration request message from the UE 910, and send an emergency bearer creation request message to the network side second network element 922;
  • the network-side second network element 922 is configured to create an emergency bearer context according to the emergency bearer creation request message, obtain the PCC rule of the emergency bearer, and execute the PCC rule, and is configured to return the load response message to the network side first network element 921.
  • the network side first network element 921 is configured to create an emergency user context according to the emergency registration request message from the UE 910, and forward the emergency registration request message to the network side second network element 922;
  • the network-side second network element 922 is configured to create an emergency bearer context, obtain an emergency bearer PCC rule according to the emergency registration request message, and execute the PCC rule, and is configured to return an emergency registration accept message to the network side first network element 921.
  • the network side first network element 921 is configured to create an emergency user context and an emergency PDP context according to the emergency registration request message from the UE 910, and send an emergency PDP context creation request message to the network side second network element 922;
  • the network-side second network element 922 is configured to create an emergency PDP context according to the emergency PDP context creation request message, obtain the PCC rule of the emergency bearer, and execute the PCC rule, and use it to return the created PDP context to the network side first network element 921. Response message.
  • the UE 910 is configured to carry the emergency indication bit in the attach request message as an emergency registration request message to the network side first network element 921;
  • the attach request message for attaching the emergency type as an emergency registration request message is sent to the network side first network element 921;
  • the tracking area update request message for updating the type of emergency update is sent to the network side first network element 921 as an emergency registration request message;
  • the network side first network element 921 is configured to send the create bearer request message carrying the specific APN as the emergency bearer creation request message to the network side second network element 922;
  • the network-side second network element 922 is further configured to send an emergency bearer creation request message to the network-side first network element. 921.
  • the first network element 921 on the network side establishes a radio bearer of the access network according to the emergency bearer creation request message.
  • the network side second network element 922 is configured to send the create bearer request message carrying the specific APN as the emergency bearer creation request message to the network side first network element 921;
  • the network side first network element 921 is configured to send the create PDP context request message carrying the specific APN as the emergency PDP context creation request message to the network side second network element 922;
  • the network side first network element 921 is further configured to determine the network side second network element 922 used to create the emergency bearer.
  • the network-side first network element 921 is configured to configure the network-side second network element 922 used by the specific APN, and is used to determine according to the specific APN.
  • the network side second network element 922 used to create the emergency bearer configured to determine, according to the location information of the UE, the network side second network element 922 used to create the emergency bearer.
  • a PCRF may be further included in the system shown in FIG.
  • the PCRF may be configured to configure a PCC rule corresponding to the emergency bearer, and obtain a policy and a charging rule request message of the emergency bearer PCC rule according to the representation from the second network element 922 on the network side, and carry the corresponding PCC rule of the emergency bearer.
  • the policy and charging rule providing message is sent to the network side second network element 922;
  • the network side second network element 922 may be configured to send a policy and charging rule request message indicating that the emergency bearer PCC rule is obtained to the PCRF, and receive a policy and charging rule from the PCRF that carries the PCC rule corresponding to the emergency bearer. Provide a message.
  • the network side second network element 922 is configured to send the PCRF to the PCRF. Sending a policy and charging rule request message with the value of the IMS emergency indicator bit field set to True; if the bearer type field is added to the policy and charging rule request message, the network side second network element 922 is used for the PCRF Sending a policy and charging rule request message with the bearer type field set to an emergency bearer;
  • the network side second network element 922 is configured to send a policy and charging rule request message with the service type field set to the IMS emergency service to the PCRF.
  • the network side second network element 922 is configured to send a policy and charging rule request message with the APN field set to the global dedicated emergency access point name to the PCRF.
  • the second network element 922 on the network side can be further configured to configure an AF address used by the IMS emergency service, and the AF address is sent to the first network element on the network side in the message returned to the first network element 921 on the network side. 921.
  • the first network element 921 on the network side may send the obtained AF address to the UE in an emergency registration accept message.
  • the first network element on the network side is further configured to return to the UE 910 an emergency registration accept message carrying the periodic update timer set to 0 or carrying the indication bit identifier period update timer to be deactivated.
  • the IP-CAN network may include mobile communication networks such as GPRS, UMTS, and SAE.
  • the first network element on the network side may be the MME
  • the second network element 922 on the network side may be the UPE/IAA
  • the network side is the first.
  • the network element may be an MME/UPE
  • the network side second network element 922 may be an IASA.
  • the network side first network element may be an SGSN
  • the network side second network element 922 may be a GGSN.
  • FIG. 10 is a schematic structural diagram of a first network element on a network side in the system shown in FIG. 9.
  • the first network element on the network side includes: a first interface module 1001 and a first bearer creation module 1002.
  • the first interface module 1001 is configured to send an emergency registration request message from the UE to the first bearer creating module 1002.
  • the first bearer creation module 1002 is configured to create an emergency bearer according to the emergency registration request from the first interface module 1001.
  • each module in the first network element on the network side is as follows:
  • the first bearer creation module 1002 is configured to create an emergency user context and an emergency bearer context, and send an emergency bearer creation request message to the second network element on the network side through the first interface module 1001.
  • the first interface module 1001 is configured to send an emergency bearer creation request message to the second network element on the network side, and receive a bearer response message from the second network element on the network side.
  • the first network element on the network side may be the MME or the MME/UPE.
  • the first bearer creation module 1002 is configured to send the create bearer request message carrying the specific APN as the emergency bearer creation request message to the network side second network element by using the first interface module 1001;
  • the creating a bearer request message with the bearer type being an emergency bearer is sent to the network side second network element by using the first interface module 1001 as an emergency bearer creation request message;
  • the method is configured to send the emergency bearer request message to the second network element on the network side by using the first interface module 1001.
  • the first bearer creation module 1002 is configured to create an emergency user context, and forward the emergency registration request message to the second network element on the network side by using the first interface module 1001;
  • the first interface module 1001 is configured to send an emergency registration request message to the second network element on the network side, and receive an emergency registration accept message from the second network element on the network side.
  • the first network element on the network side can be the MME.
  • the first interface module 1001 is further configured to receive an emergency request message from the second network element on the network side.
  • the first 7- segment creation module 1002 is configured to create an emergency user context and an emergency PDP context, and send an emergency PDP context creation request message to the second network element on the network side by using the first interface module 1001;
  • the first interface module 1001 is configured to send an emergency PDP context creation request message to the second network element on the network side, and receive a create PDP context response message from the second network element on the network side.
  • the first network element on the network side can be an SGSN.
  • the first load creation module 1002 is configured to send the create PDP context request message carrying the specific APN as the emergency PDP context creation request message to the network side second network element by using the first interface module 1001;
  • the creating a PDP context request message with the bearer type being the emergency bearer is sent to the network side second network element by using the first interface module 1001 as the emergency PDP context creation request message;
  • the sending the emergency PDP context request message is sent to the network side second network element by using the first interface module 1001.
  • the first network element in the network side shown in FIG. 10 may further include: the second network element on the network side Fixed module
  • the network-side second network element determining module may be configured to determine the network-side second network element used to create the emergency bearer, and notify the determined network-side second network element to the first interface module 1001; the first interface module 1001, The network side second network element sending request message notified by the network side second network element determining module may be used.
  • the network-side second network element determining module in the network-side first network element shown in FIG. 10 can be used to configure the network-side second network used by the specific APN when determining the network-side second network element used for creating the emergency bearer.
  • a network side second network element used to create an emergency bearer configured to determine, according to location information of the UE, a network side second network element used to create an emergency bearer.
  • the first interface module is further configured to receive a message from the second network element on the network side that carries the AF address used by the IMS emergency service, and send the AF address to the first bearer creation module 1002.
  • the first bearer creation module 1002 is configured to carry the AF address in the emergency registration accept message, and send the same to the UE through the first interface module 1001.
  • the first bearer creation module 1002 is further configured to return, to the UE 910, the emergency registration accept message carrying the periodic update timer set to 0 or the periodic update timer to be deactivated by the first interface module 1001.
  • FIG. 11 is a schematic structural diagram of a second network element on the network side in the system shown in FIG. 9.
  • the second network element on the network side includes a second interface module 1101 and a second bearer creation module. 1102.
  • the second interface module 1101 is configured to receive a request message from the first network element on the network side, and send the request message to the second bearer creation module 1102.
  • the second bearer creating module 1102 is configured to create a corresponding emergency bearer according to the request message, and return a corresponding response message to the first network element on the network side by using the second interface module 1101.
  • each module in the second network element on the network side is as follows:
  • the second interface module 1101 is configured to receive an emergency bearer creation request message from the first network element on the network side, and send an emergency bearer creation request message to the second bearer creation module.
  • the second bearer creation module 1102 is configured to create an emergency bearer context according to the emergency bearer creation request message, obtain the PCC rule of the emergency bearer, and execute the PCC rule, and return the bearer response to the first network element on the network side by using the second interface module 1101. Message.
  • the second network element on the network side can be UPE/IAS A or IAS A.
  • the second interface module 1101 is configured to receive an emergency registration request message from the first network element on the network side, and send an emergency registration request message to the second bearer creation module 1102.
  • the second bearer creation module 1102 is configured to create an emergency bearer context according to the emergency registration request message, obtain the PCC rule of the emergency bearer, and execute the PCC rule, and return the emergency registration acceptance to the first network element on the network side through the second interface module 1102. Message.
  • the second network element on the network side can be UPE/IASA.
  • the second bearer creation module 1102 is further configured to send the emergency bearer to the first network element on the network side by using the second interface module 1101. Request message.
  • the second 7-id creating module 1102 is configured to send the create bearer request message carrying the specific APN as the emergency bearer creation request message to the first network element on the network side through the second interface module 1101;
  • the method for sending the create bearer request message carrying the emergency indicator bit as the emergency bearer creation request message to the first network element on the network side through the second interface module 1101;
  • the creating a bearer request message with the bearer type being an emergency bearer is sent to the network side first network element by using the second interface module 1101 as an emergency bearer creation request message;
  • the method is configured to send the emergency bearer request message to the first network element on the network side by using the second interface module 1101.
  • the second interface module 1101 is configured to receive an emergency PDP context creation request message from the first network element on the network side, and send an emergency PDP context creation request message to the second load creation module 1102.
  • the second bearer creation module 1102 is configured to create an emergency PDP context according to the emergency PDP context creation request message, obtain the PCC rule of the emergency bearer, and execute the PCC rule, and return to the first network element on the network side through the second interface module 1101. PDP context response message.
  • the second network element on the network side can be a GGSN.
  • the second 7-segment creation module 1102 sends a policy and charging rule request message indicating that the emergency bearer PCC rule is obtained to the PCRF through the second interface module 1101, to obtain the PCC rule of the emergency bearer. Specifically, if the IMS emergency indication bit field indicating that the established bearer is an emergency bearer is added to the policy and charging rule request message, the second bearer creating module 1102 is configured to send the IMS to the PCRF by using the second interface module 1101.
  • the policy and charging rule request message with the value of the emergency indicator bit field set to True; If the bearer type field is added to the policy and charging rule request message, the second bearer creating module 1102 is configured to send, by using the second interface module 1101, the policy and charging rule request that the bearer type field is set to an emergency bearer to the PCRF. Message
  • the second bearer creating module 1102 is configured to send, by using the second interface module 1101, the policy and charging rule that the service type field is set to the IMS emergency service to the PCRF. Request message.
  • the second bearer creating module 1102 is configured to send, by using the second interface module 1101, the policy and charging that the APN field is set to the global dedicated emergency access point name to the PCRF. Rule request message.
  • the second network element in the network side shown in FIG. 11 may further include a storage module.
  • the storage module may be configured to store an AF address used by the IMS emergency service, and configured to carry the AF address to the network through the second interface module 1101.
  • the message returned by the first network element is sent to the first network element on the network side.
  • the present invention transmits an emergency registration request message by the UE to the network side network element in the IP-CAN network; when the network side network element in the IP-CAN network receives the emergency registration request message from the UE Accepting the emergency registration request and creating an emergency bearer corresponding to the emergency registration request, so that the UE can create an IMS emergency service bearer while urgently registering to the IP-CAN network, thereby reducing emergency bearer creation in the IP-CAN network. Delay and message interaction.

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)

Abstract

La présente invention concerne un procédé pour l'enregistrement émergent dans un réseau d'accès à connexion IP (IP-CAN) de l'équipement utilisateur (UE). L'UE transmet les informations de requête de ré-enregistrement d'urgence à l'élément de réseau côté réseau dans le réseau IP-CAN ; lorsque l'élément réseau côté réseau dans le réseau IP-CAN accepte les informations de requête d'enregistrement d'urgence de l'UE, il accepte la requête d'enregistrement d'urgence et crée la porteuse d'urgence correspondant à la requête d'enregistrement d'urgence.
PCT/CN2008/070098 2007-01-15 2008-01-14 Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur WO2008086754A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710000969.9 2007-01-15
CN2007100009699A CN101227352B (zh) 2007-01-15 2007-01-15 用户终端紧急注册到ip连接接入网络的方法及***

Publications (1)

Publication Number Publication Date
WO2008086754A1 true WO2008086754A1 (fr) 2008-07-24

Family

ID=39635668

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070098 WO2008086754A1 (fr) 2007-01-15 2008-01-14 Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur

Country Status (2)

Country Link
CN (1) CN101227352B (fr)
WO (1) WO2008086754A1 (fr)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557573B (zh) * 2008-04-07 2012-06-20 电信科学技术研究院 紧急服务信息的获取方法及通信设备
CN101583114B (zh) * 2008-09-23 2011-09-21 中兴通讯股份有限公司 用户设备IP地址提供方法、Diameter路由代理
CN101577963A (zh) * 2008-10-17 2009-11-11 中兴通讯股份有限公司 一种用户注册失败后的处理方法
CN101742452B (zh) * 2008-11-10 2012-08-29 华为技术有限公司 承载管理方法、相关设备及网络***
WO2010105485A1 (fr) * 2009-03-20 2010-09-23 中兴通讯股份有限公司 Système et procédé conçus pour déconnecter un utilisateur après qu'il a passé un appel d'urgence
CN101730036B (zh) * 2009-03-24 2012-12-19 中兴通讯股份有限公司 附着状态改变方法、装置以及用户设备
CN102440012B (zh) * 2009-04-15 2014-01-01 华为技术有限公司 接收公共预警***pws消息的方法、装置和***
CN101998331B (zh) * 2009-08-21 2013-08-07 电信科学技术研究院 用户设备注册状态的识别方法和设备
CN102118722B (zh) * 2010-01-06 2015-04-15 电信科学技术研究院 终端可达定时器的取值的设置方法及***
CN103052053B (zh) 2010-02-12 2016-03-02 华为技术有限公司 优先级业务处理方法、装置和***
WO2011120235A1 (fr) * 2010-04-02 2011-10-06 华为技术有限公司 Procédé, appareil et système pour la mise en œuvre d'un délestage du trafic de service dans une architecture du type à évolution d'architecture système (sae, system architecture evolution)
EP2437555B1 (fr) * 2010-10-04 2013-09-11 HTC Corporation Séparation initié de réseau avec reconnexion
CN102438330A (zh) * 2011-12-06 2012-05-02 大唐移动通信设备有限公司 一种附着到e-tran的方法及移动性管理实体
RU2748165C1 (ru) * 2017-12-26 2021-05-20 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ и устройство передачи данных и компьютерный носитель данных

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859406A (zh) * 2006-02-14 2006-11-08 华为技术有限公司 一种多媒体广播/组播业务激活的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1266898C (zh) * 2004-03-29 2006-07-26 华为技术有限公司 一种实现多媒体广播/组播服务业务激活的方法
CN100563254C (zh) * 2006-03-21 2009-11-25 华为技术有限公司 一种演进网络中漫游用户数据路由方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859406A (zh) * 2006-02-14 2006-11-08 华为技术有限公司 一种多媒体广播/组播业务激活的方法

Also Published As

Publication number Publication date
CN101227352B (zh) 2011-02-09
CN101227352A (zh) 2008-07-23

Similar Documents

Publication Publication Date Title
WO2008086754A1 (fr) Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur
CN101087301B (zh) 用户接入网络的方法和***
US8787313B2 (en) Method, network system and destination network for transmitting QoS during a handover process between systems
JP5256305B2 (ja) 意思決定法、意思決定システム及びポリシー決定機能
WO2009036690A1 (fr) Procédé, système et dispositif pour accueillir l'adressage de l'adresse ip statique d'utilisateur dans un système d'évolution à long terme
WO2009094837A1 (fr) Procédé de sélection d'un serveur à fonction de règles de politiques et de facturation dans une situation sans itinérance
WO2009086734A1 (fr) Procédé pour sélectionner une entité à fonction de règles de politique et de facturation dans le scénario sans itinérance
US20100290392A1 (en) Session and Media Binding to Common Control
US20120102174A1 (en) Policy And Charging Control Method And System For Multi-PDN Connections Of Single APN
US20120124220A1 (en) Method for Implementing Policy and Charging Control in a Roaming Scene
US20110182244A1 (en) Method for supporting context management by home node-b
WO2011015140A1 (fr) Procédé, système et appareil pour radiomessagerie de télécommunication mobile
WO2012142884A1 (fr) Procédé et appareil pour le traitement d'informations de charge du réseau, de données de position d'utilisateur et de politique
WO2009117879A1 (fr) Procédé pour indiquer la gestion de support de la passerelle de desserte
WO2011134336A1 (fr) Procédé, dispositif et système de rapport d'événements de communication de type machine
CN107404715B (zh) 位置信息提供方法及装置
WO2010105462A1 (fr) Procédé de traitement du rattachement d'un équipement d'utilisateur, entité de gestion de la mobilité et équipement d'utilisateur associé
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
WO2011110020A1 (fr) Procédé et système pour sélectionner un contrôleur de politique et un agent de routage diameter
WO2013067907A1 (fr) Procédé, dispositif et système de traitement d'appel de terminal
WO2008092346A1 (fr) Procédé, système et appareil pour l'établissement d'un support de signalisation
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
WO2011120366A1 (fr) Procédé, dispositif et système d'obtention d'informations de charge d'une station de base radio
WO2016000793A1 (fr) Sélection de fonction de politique et de règles de chargement (pcrf)
WO2013135213A1 (fr) Procédé de traitement de session tdf et pcrf

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

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

Country of ref document: EP

Kind code of ref document: A1