WO2009097818A1 - Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur - Google Patents

Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur Download PDF

Info

Publication number
WO2009097818A1
WO2009097818A1 PCT/CN2009/070333 CN2009070333W WO2009097818A1 WO 2009097818 A1 WO2009097818 A1 WO 2009097818A1 CN 2009070333 W CN2009070333 W CN 2009070333W WO 2009097818 A1 WO2009097818 A1 WO 2009097818A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency
bearer
request message
network side
emergency call
Prior art date
Application number
PCT/CN2009/070333
Other languages
English (en)
Chinese (zh)
Inventor
Qi Yu
Jinyi Zhou
Lan Liu
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 WO2009097818A1 publication Critical patent/WO2009097818A1/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 the field of communications technologies, and in particular, to a method, device, and system for emergency access of user equipment.
  • the Universal Mobile Telecommunication System is a third-generation mobile communication system that uses the Wideband Code Division Multiple Access (WCDMA) air interface.
  • UMTS includes a Radio Access Network (RAN) and a Core Network (CN).
  • the RAN is used to process all wireless related functions, and is composed of a Radio Network Controller (RNC) and a Base Station (NodeB).
  • RNC Radio Network Controller
  • NodeB Base Station
  • the CN processes all voice calls and data connections in the UMTS and implements switching and routing functions with the external network.
  • the CN mainly includes a Serving GPRS Support Node (SGSN) and a Gateway General Packet Radio Service Support Node ( Basic network element functional entities such as GGSN, Gateway GPRS Support Node.
  • the SGSN is mainly used to forward input/output Internet Protocol (IP) packets for mobile stations (MS, Mobile Stations) in the SGSN service area.
  • the GGSN is used to provide routing and encapsulation between data packets and external data networks.
  • the packet switching (PS) domain service is used, and the bearer network is an IP bearer.
  • the UE can access the network through an attach procedure.
  • the terminal needs to carry the International Mobile Equipment Identity (IMSI), and the identity of the user can be identified through the IMSI network, thereby determining whether the user can access the network and through the home user server ( HSS, Home Subscriber Server) interaction, get the user's contract data, and provide the corresponding service to the user.
  • IMSI International Mobile Equipment Identity
  • the embodiments of the present invention provide a method, a device, and a system for emergency access of a user equipment, which can implement any user to access the network under any conditions in an emergency.
  • An embodiment of the present invention provides a method for emergency access of a user equipment, where the method includes: receiving an attach request message, where the attach request message carries emergency call attribute information; and identifying the attach request according to the emergency call attribute information The call indicated by the message is an emergency call;
  • the core network side device capable of emergency access is selected, and an emergency bearer request message is sent to the core network side device.
  • the embodiment of the present invention provides a core network side device, where the core network side device includes: a receiving unit, configured to receive an attach request message, where the attach request message carries emergency call attribute information, according to the emergency call attribute information Identifying, by the call indicated by the attach request message, an emergency call;
  • a selection unit configured to select a core network side device 2 capable of emergency access
  • a sending unit configured to send an emergency bearer request message to the core network side device 2 selected by the selecting unit.
  • An embodiment of the present invention provides a network system, where the system includes the foregoing core network side device.
  • the embodiment of the present invention receives an attach request message by using a core network side device, where the message carries an emergency call. Attribute information, identifying the attach request message indication The call is an emergency call; the core network side device capable of emergency access is selected, and an emergency bearer request message is sent to the core network side device, thereby realizing an emergency session of the IMS domain, so that in an emergency, any user is in any condition Emergency access to the IMS domain can be achieved.
  • FIG. 1 is a simplified schematic diagram of an LTE/SAE network architecture in the prior art according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 4 is a flowchart of Embodiment 1 of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 5 is a flowchart of Embodiment 2 of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 9 is a flowchart of Embodiment 2 of a second method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 10 is a flowchart of Embodiment 2 of a second method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 12 is a flowchart of Embodiment 4 of a method for emergency access of a UE according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a core network side device according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of an access network side device according to an embodiment of the present invention.
  • the LTE/SAE network architecture in the prior art can be simplified.
  • the network architecture can be viewed in two parts.
  • Part 1 is user equipment (UE, User Equipment) 201 through RAN 202, mobility.
  • the management entity (MME, Mobility Management Entity) 203 accesses the SAE gateway (GW, Gateway) 204, at which point all nodes belong to the SAE system;
  • part 2 is the UE 201 through the RAN 207, serving the general packet radio service support node (SGSN, Serving GPRS) Support Node) 206, access service gateway (Serving Gateway, SGW) 204, in this case, the SGSN 206 to the UE 201 part belong to the UMTS system, and the SGW 204 to the Packet Data Network Gateway (PGW) 205 belong to the SAE system, so in this case, the processing between the UMTS and the SAE is consistent.
  • Sexual problems are possible.
  • a method for emergency access of a UE is described.
  • the method can implement user access in an emergency situation when the user does not have an IMSI or an IMSI, or user access in an emergency when the access is restricted. .
  • a flowchart of a method in an embodiment of the present invention includes the following steps:
  • FIG. 3 is a flowchart of a method for emergency access of the UE in the embodiment of the present invention, the UE usually has an emergency access in the evolved network, Detailed steps are explained through specific steps:
  • the UE After the UE establishes a radio resource control (RRC) connection with the eNB, the UE sends an attach request message to the eNB.
  • the parameters carried in the request message are: emergency call attribute information, PDN address Allocation, and protocol.
  • the configuration information (Protocol Configuration Options), the attachment type (Attach Type), and the user ID; wherein, the emergency call attribute information is used to indicate that the network side UE is to make an emergency call, for example, may be an emergency call indication, an emergency call type, or Specific requirements of the call, etc.
  • PDN Address Allocation indicates whether the UE performs IP address allocation and assigned address type
  • Protocol Configuration Options is used to transmit parameters between the UE and the PGW, and the MME and the SGW transparently transmit the parameter;
  • Attach type indicates the type of attachment
  • the user identifier is an International Mobile Equipment Identity (IMEI, International Mobile Equipment Identity);
  • the user identifier has two possibilities: IMSI; Global Unique Temporary Identity (GUTI) or Tracking Area Identity (TAI).
  • IMSI Global Unique Temporary Identity
  • TAI Tracking Area Identity
  • the UE informs the PGW to select a P-CSCF with specific processing capability through the Protocol Configuration Options (for example, support for establishing an emergency session directly using the anonymous user mode without IMS registration).
  • the PDN Address Allocation is set by the UE when it is normally attached, and can be set by the MME during emergency attach.
  • the UE may reserve air interface resources in advance for the emergency call/emergency call type
  • the UE Before sending the attach request message, the UE sends an RRC connection request message to the eNB to establish an RRC connection, and may add an "emergency attachment" to the eNB to make an emergency call in the "cause" of the RRC connection request message, or may indicate by a combination of multiple parameters. Emergency attachment".
  • the UE also indicates "emergency call type (eg, fire alarm, car accident)" through the dedicated parameter of the RRC connection request message; "specify to maintain RRC connection” by specifying a specific parameter in the RRC connection request message, it can be understood that the UE can also
  • the emergency call identification information is used to indicate the eNB emergency call.
  • the eNB selects the MME and forwards the attach request message to the MME, and the MME selects the pre-configured emergency call Qos information and the bearer establishment mode on the MME according to the emergency call attribute information in the attach request message.
  • Emergency Calls Qos messages can be: Qos information about emergency calls or QoS information related to specific emergency services and emergency call specific requirements.
  • Emergency call Qos information can be configured based on emergency call type or specific requirements for emergency calls.
  • the bearer can carry both signaling and service data; (2) establishing an emergency default bearer between the UE and the PGW, and possibly establishing an emergency dedicated bearer by the network node (eg, MME, PGW, PCRF, eNodeB) during or after the process;
  • the network node eg, MME, PGW, PCRF, eNodeB
  • the eNB pre-allocates user plane resources, such as a user plane address and a tunnel end point identifier (TEID, Tunnel End Point Identifier), according to the parameters of the RRC connection request message or the attach request message for indicating the emergency call.
  • the request is sent to the MME together; the eNB pre-schedules the air interface resource by using the emergency call QoS information configured on the eNB.
  • TEID tunnel end point identifier
  • the MME may request, by using an identity check message, an EIR (Equipment Identity Register) to confirm the identity of the user according to the needs of the operator. If the user is in the blacklist, the MME rejects the attach request.
  • EIR Equipment Identity Register
  • An authentication vector may be specifically configured for emergency access on the network element node MME to perform an authentication process.
  • the MME selects an SGW and a PGW, and sends a bearer setup request message to the selected SGW.
  • the MME can select the SGW and the PGW as follows:
  • the MME uses the local Em-APN (Emergency-Access Point Name) to obtain the PGW or SGW that can access the emergency service PDN.
  • Em-APN Error-Access Point Name
  • the SGW is configured in the MME.
  • the MME may select the local emergency call QoS information according to the specific emergency service type or the emergency service specific requirement indicated by the UE, and send a bearer setup request message to the SGW, where the carrying parameters include: emergency call Qos information, Em-APN, user identifier, PDN Address Allocation, Protocol Configuration Options, bearer ID, where the bearer ID is
  • the MME carries the parameter to the SGW in the establishment of the bearer request message.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, this is to be set to immediately assign an IP address, and the MME may request to assign a specific IP address for a specific type of emergency call.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and sends a bearer setup request message to the PGW, where the message carries parameters: an emergency call QoS information, an Em-APN, a user identifier, a bearer identifier, a PDN Address Allocation, and a Protocol Configuration Options.
  • the PGW can interact with the PCRF, and the PCRF can trigger the pre-establishment of the dedicated bearer according to the needs of the emergency service.
  • PCC Policy and Charging Control
  • the PGW allocates an uplink user plane and a control plane address and a TEID, and the PGW sends a bearer response message to the SGW, where the message carries parameters: a user plane and a control plane address and a TEID, a PDN Address Information, a bearer identifier, and a Protocol Configuration Options. ;
  • the PDN Address Information is an IP address assigned by the PGW to the UE.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and the SGW sends a bearer response message to the MME, where the message carries parameters: a user plane and a control plane address, and a TEID, a PDN Address Information, a Protocol Configuration Options, and a bearer identifier.
  • the MME sends an attach accept message to the eNB, where the message carries the parameter: Em-APN,
  • Protocol Configuration Options ⁇ Bearer ID, Tracking Area Identity (TAI) list, user plane address and TEID assigned by the SGW;
  • TAI Tracking Area Identity
  • the TAI list is a list of tracking area identifiers sent by the MME to the UE.
  • the eNB sends a radio bearer setup request to the UE.
  • the message carries the NAS message attachment acceptance;
  • the message is sent after waiting for the scheduling to complete.
  • the UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;
  • the eNB forwards the attach complete message to the MME, where the message carries the parameter: a bearer identifier.
  • the PGW may be triggered by the PGW or by the PCRF to establish a dedicated bearer
  • the UE performs an emergency registration of the IMS domain.
  • the UE may not have to perform IMS domain emergency registration. 315. An emergency session establishment of the IMS domain.
  • the emergency call QoS information can be configured on each network element node as needed.
  • it can include, but is not limited to, an eNB, an MME, a PGW, and a PCRF.
  • a specific message or an existing message needs to be used.
  • Other parameters such as the number of bearers that need to be established for an emergency call may be pre-configured at each network element node.
  • Qos information may be a set of Qos information that corresponds to a specific emergency or emergency service specific need.
  • the emergency bearer established between the eNB and the PGW triggered by the MME after receiving the attach request message, and the air interface side bearer established by the eNB after scheduling the air interface resource can implement an emergency session in the IMS domain, and implement The user is in emergency access.
  • FIG. 4 is a flowchart of Embodiment 1 of a method for emergency access of a UE according to an embodiment of the present invention.
  • the UE uses IMEI as a user identifier to establish an emergency bearer. The following detailed steps are specifically described:
  • the UE After the UE establishes an RRC connection with the eNB, the UE sends an attach request message to the eNB, where the message carries parameters: emergency call attribute information, IMEI, PDN Address Allocation, Protocol Configuration Options, and Attach Type;
  • the emergency call attribute information is used to indicate that the network side UE is to make an emergency call, for example, an emergency call indication, an emergency call type, or a specific requirement for an emergency call, etc.
  • PDN Address Allocation indicates whether the UE performs IP address allocation and allocation.
  • the address configuration type is used to transmit parameters between the UE and the PGW, and the MME and the SGW transparently transmit the parameter; the UE informs the PGW to select a P-CSCF with specific processing capability through the Protocol Configuration Options, such as supporting the use of the anonymous User mode directly establishes an emergency session without the need for an Internet Protocol Multimedia Subsystem (IMS, International Multimedia)
  • IMS Internet Protocol Multimedia Subsystem
  • Attach type indicates the type of attachment
  • PDN Address Allocation is set by the UE when it is normally attached, by emergency attachment
  • the UE may reserve air interface resources for emergency calls or different emergency call types.
  • the UE Before sending the attach request message, the UE sends an RRC connection request message to the eNB to establish an RRC connection, and may add an "emergency attachment" to the eNB to make an emergency call in the "cause" of the RRC connection request message, or may indicate by a combination of multiple parameters. Emergency attachment".
  • the UE also indicates "emergency call type (eg, fire alarm, car accident)" through the dedicated parameter of the RRC connection request message; "specify to maintain RRC connection” by specifying a specific parameter in the RRC connection request message, it can be understood that the UE can also
  • the emergency call identification information is used to indicate the eNB emergency call.
  • the eNB selects an MME and forwards an attach request message to the MME.
  • the eNB pre-allocates user plane resources, such as a user plane address and a TEID, according to the emergency call identification information in the RRC connection request message or the emergency call attribute information in the attach request message, and sends the MME along with the attach request message to the MME;
  • the emergency call QoS information on the eNB pre-schedules the air interface resources.
  • Emergency Calls Qos messages can be configured based on the type of emergency call or the specific requirements for an emergency call.
  • the MME may use an IMEI to perform an identity check to confirm the identity of the user according to the needs of the operator. If the user is in the blacklist, the MME rejects the attach request. 404.
  • the MME selects an SGW and a PGW, and sends a setup bearer request message to the selected SGW.
  • the MME selects the SGW and the PGW, and can have the following two methods:
  • the MME uses the local Em-APN to obtain the PGW, SGW that can access the emergency service PDN;
  • the MME When the MME receives the attach request, it triggers the establishment of an emergency bearer between the eNB, the SGW, and the PGW, and the bearer can carry signaling and bear the service data.
  • the MME may select the local emergency call QoS information according to the specific emergency service type or the emergency service specific requirement indicated by the UE, and send a setup bearer request message to the SGW, and the carrying parameters include: emergency call QoS information, Em-APN, IMEI, PDN Address Allocation, Protocol Configuration Options, bearer ID, and bearer ID are assigned by the MME.
  • the MME carries the parameter to the SGW in the setup bearer request message.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, this is to be assigned to immediately assign an IP address, and the MME may request to assign a specific IP address for a specific type of emergency call. Both of these parameters are forcibly set by the MME due to the need of emergency services, which can effectively ensure the reliability of the emergency bearer.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and sends a bearer setup request message to the PGW, carrying parameters: an emergency call Qos information, an Em-APN, an IMEK bearer identifier, a PDN Address Allocation ⁇ Protocol Configuration Options, and an SGW allocated user. Face and control plane address and TEID;
  • the PGW can interact with the PCRF; the PCRF can trigger the pre-establishment of the dedicated bearer according to the needs of the emergency service.
  • the PGW allocates an uplink user plane and a control plane address and a TEID, and sends a bearer response message to the PGW, where the message carries parameters: a user plane and a control plane address allocated by the PGW.
  • TEID PDN Address Information
  • bearer ID Protocol Configuration Options
  • the PDN Address Information is an IP address assigned by the PGW to the UE.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and the SGW sends a bearer response message to the MME, where the message carries parameters: a user plane and a control plane address, and a TEID, a PDN.
  • the MME sends an attach accept message to the eNB, where the message carries parameters: Em-APN, PDN Address Information ⁇ Protocol Configuration Options, bearer identifier, TAI list, user plane address and TEID allocated by the SGW;
  • the message should also carry the GUTI parameter.
  • the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;
  • the message is sent after waiting for the scheduling to complete.
  • the UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;
  • the eNB forwards an attach complete message to the MME, where the message carries a parameter: a bearer identifier.
  • the UE performs an emergency registration of the IMS domain.
  • the UE may not have to perform IMS domain emergency registration.
  • FIG. 5 is a flowchart of Embodiment 2 of a method for emergency access of a UE according to an embodiment of the present disclosure.
  • the UE still uses the IMEI as the user identifier. The difference is that multiple emergency bearers can be established at the same time. The following detailed steps are described in detail:
  • step 501 is the same as step 401 in the first embodiment, and will not be described again;
  • the eNB selects an MME and forwards an attach request message to the MME.
  • a default bearer is triggered between the eNB, the SGW, and the PGW, and the PCRF triggers the PGW to establish a dedicated bearer.
  • the eNB may allocate an uplink user plane address and a TEID for the default bearer in step 502 or step 512.
  • the eNB may pre-allocate user plane resources, such as a user plane address and a TEID, according to the parameters of the RRC connection request message or the attach request message for indicating the emergency call, and send the MME to the MME together with the attach request message;
  • the emergency call QoS information on the eNB pre-arranges the air interface resources.
  • Emergency Calls Qos messages can be configured based on the type of emergency call or the specific requirements for an emergency call.
  • step 503. It is the same as step 403 in the first embodiment, and is not described again.
  • the MME selects an SGW and a PGW, and sends a setup bearer request message to the selected SGW.
  • the MME selects the SGW and the PGW, and can have the following two methods:
  • the MME uses the local Em-APN to obtain the PGW, SGW that can access the emergency service PDN;
  • the MME may select the local emergency call QoS information according to the specific emergency service type or the emergency service specific requirement indicated by the UE, and send a setup bearer request message to the SGW, and the carrying parameters include: emergency call QoS information, Em-APN, IMEI, PDN Address Allocation, Protocol Configuration Options, bearer identifier; where the bearer identifier is assigned by the MME.
  • the MME carries the parameter to the SGW in the setup bearer request message.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, this is to be assigned to immediately assign an IP address, and the MME may request to assign a specific IP address for a specific type of emergency call. This parameter is forcibly set by the MME due to the need of emergency services, which can effectively ensure the reliability of the emergency bearer.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and sends a default bearer request message to the PGW, carrying parameters: emergency call Qos information, Em-APN, and IMEK bearer.
  • ID PDN Address Allocation ⁇ Protocol Configuration Options ⁇ User plane and control plane address and TEID assigned by SGW;
  • the PGW can interact with the PCRF.
  • the PCRF can trigger the pre-establishment of the dedicated bearer according to the needs of the emergency service.
  • the PGW allocates an uplink user plane and a control plane address and a TEID, and sends a bearer response message to the PGW, where the message carries parameters: a user plane and a control plane address and a TEID, a PDN address information, a bearer identifier, and a protocol configuration option allocated by the PGW;
  • the PDN Address Information is an IP address assigned by the PGW to the UE.
  • the PGW sends a dedicated bearer request message to the SGW, where the dedicated bearer Qos information may be configured by the network for the emergency call on the PGW, or may be from the PCRF or the MME.
  • the PGW sends a default bearer response and sends a dedicated bearer request message to the SGW.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and the SGW sends a default bearer response message to the MME, where the message carries parameters: a user plane and a control plane address, and a TEID, a PDN Address Information, a Protocol Configuration Options, and a bearer identifier.
  • the SGW further forwards the establishment of the dedicated bearer request message to the MME, and the SGW sends the default bearer response message together with the establishment of the dedicated bearer request message to the MME.
  • the MME sends an attach accept message to the eNB, where the message carries the parameters: Em-APN, PDN Address Information ⁇ Protocol Configuration Options, bearer identifier, TAI list, user plane address and TEID allocated by the SGW;
  • the message should also carry the GUTI parameter.
  • the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;
  • the message is sent after waiting for the scheduling to complete.
  • the UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attachment completion. 512.
  • the eNB forwards an attach complete message to the MME, where the message carries a parameter: a bearer identifier.
  • the eNB sends a bearer setup response message to the MME, where the message carries a parameter: a bearer identifier.
  • the eNB allocates a user plane address and a TEID to the default bearer in step 502 or 512, send an update bearer request message and establish a dedicated bearer response message to the SGW, otherwise, only the setup dedicated bearer response message is sent;
  • step 514 If the MME sends an update bearer request message to the SGW in step 513, the SGW returns an update bearer response message to the MME.
  • the SGW sends a setup bearer response message to the PGW.
  • step and step 514 are in no particular order.
  • the UE performs an emergency registration of the IMS domain.
  • the IMS registration can be carried on a dedicated bearer or on a default bearer.
  • FIG. 6 is a flowchart of Embodiment 3 of a method for emergency access of a UE according to an embodiment of the present invention.
  • the UE still uses the IMEI as the user identifier, and multiple emergency bearers can be established, but is established in the second embodiment.
  • the method of the bearer is different. The following is a detailed description of the specific steps: 601, which is the same as step 401 in the first embodiment of the method, and is not described again.
  • the eNB selects an MME and forwards an attach request message to the MME.
  • the network needs to configure the emergency call Qos information and the number of bearers used in the eNB in advance. Specifically, the eNB pre-allocates the user plane address and the TEID for the emergency bearer (including the dedicated bearer and the default bearer).
  • the eNB pre-allocates the user plane resource, such as the user plane address and the TEID, and sends it to the MME together with the attach request message; the eNB uses the configuration in the eNB.
  • the emergency call Qos information is pre-scheduled for air interface resources.
  • Emergency call QoS information can be configured based on the type of emergency call or specific requirements for emergency calls.
  • step 603 which is the same as step 403 in the first embodiment of the method, and is not described again.
  • the MME selects an SGW and a PGW, and sends a setup dedicated bearer request message and a default bearer request message to the selected SGW.
  • the MME selects the SGW and the PGW, and can have the following two methods:
  • the MME uses the local Em-APN to obtain the PGW, SGW that can access the emergency service PDN;
  • the MME allocates the bearer identifier, and can select the local emergency call Qos information according to the specific emergency service type or the emergency service specific requirement indicated by the UE.
  • the default bearer request message sent by the MME to the SGW carries the parameters: emergency call Qos information, Em-APN ⁇ IMEI, PDN Address Allocation ⁇ Protocol Configuration Options, and bearer identifier.
  • the MME carries the parameter to the SGW in the establishment of the default bearer request message.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately.
  • the parameter is set to immediately assign an IP address, and the MME can request to assign a specific IP address for a specific type of emergency call.
  • the MME establishes a dedicated bearer request message sent by the MME to carry the parameters: an emergency call QoS information, a linked bearer id, an IMEK bearer identifier, and a user plane address and a TEID pre-allocated for the emergency private bearer, where
  • the Bearer id is the identifier of the default bearer.
  • the MME sends a default bearer request message and establishes a dedicated bearer request message.
  • the SGW allocates a user plane and a control plane address respectively for the default bearer and the dedicated bearer.
  • the TEID sends the default bearer request message together with the establishment of the dedicated bearer request message.
  • the default bearer request message carries the parameters: emergency call QoS information, Em-APN, IMEI, bearer identifier, and PDN Address Allocation. , Protocol Configuration Options, user plane and control plane address and TEID assigned by the SGW;
  • the establishment of a dedicated bearer request message carries parameters: emergency call Qos information, linked
  • the Bearer id The Bearer id, the IMEK bearer ID, and the user plane address and TEID assigned by the SGW to the emergency private bearer.
  • the PGW can interact with the PCRF.
  • the PGW allocates an uplink user plane and a control plane address and a TEID for the default bearer and the dedicated bearer respectively, and sends a default bearer response message and a dedicated bearer response message to the PGW.
  • the default bearer response message carries parameters: a user plane and a control plane address allocated by the PGW, and a TEID, a PDN address information, a bearer identifier, and a protocol configuration option.
  • the PDN Address Information is an IP address allocated by the PGW to the UE.
  • the PBGW is used to carry the parameters of the PBG: the linked bearer id, the IMEK bearer identifier, and the user plane address and TEID allocated by the PGW for the emergency dedicated bearer. If the MME does not carry the emergency call QoS information in step 604, the PGW uses the PGW. The emergency call QoS information configured or obtained from the PCRF is sent to the SGW;
  • the SGW allocates a downlink user plane and a control plane address for the default bearer and the dedicated bearer, respectively.
  • the default bearer response message carries parameters: user plane and control plane address and TEID, PDN Address Information ⁇ Protocol Configuration Options, and bearer identifier.
  • the parameter carrying the private bearer response message carries: user plane and control plane address and TEID, bearer identifier, and linked bearer id. If the emergency call Qos information is carried in step 606, the SGW Carry this parameter.
  • the MME sends an attach accept message and a bearer setup request message to the eNB.
  • the attach accept message carries parameters: Em-APN, PDN Address
  • the attach accept message should also carry the GUTI parameter.
  • the bearer setup request message carries parameters: a bearer identifier, a user plane address allocated by the SGW, a TEID, and a linked bearer id.
  • the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;
  • the message is sent after waiting for the scheduling to complete.
  • the UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;
  • the eNB sends an attach complete message and a bearer setup response message to the MME, and the message carries the bearer identifier respectively.
  • the UE performs an emergency registration of the IMS domain.
  • the IMS domain registration can be carried on a dedicated bearer or on the default bearer.
  • the UE when the UE uses the IMSI as the user identifier and is in the roaming restricted area when the device is powered on, the UE can also establish an emergency bearer by establishing a bearer, and can establish an emergency bearer as well as multiple emergency bearers.
  • the method and the method are the same as the first embodiment, the second embodiment, and the third embodiment. The difference is that the UE needs to perform emergency registration before establishing an emergency session.
  • the UE may also use the old GUTI and the old TAI as the user identifier to establish one or more emergency bearers.
  • the old GUTI is the MME that the UE originally located is allocated to the UE.
  • Identification referring to FIG. 7, is a UE in an embodiment of the present invention.
  • the UE sends an attach request to the newly selected new MME by using the eNB;
  • the UE and the eNB need to establish an RRC connection, and the method for establishing the RRC connection and the parameters carried in the attach request message are the same as the specific method and method in step 1 of the first embodiment, and are not described again. .
  • the difference is that the UE uses the old
  • GUTI and the old TAI are used as user IDs.
  • the new MME obtains the old MME where the UE is located by using the old GUTI and the old TAI, and requests the old MME to obtain the IMSI.
  • the new MME requests the IMSI from the UE. 705.
  • the MMM may request the identity of the user by using the identity check according to the operator's requirement. If the user is in the blacklist, the MME rejects the attach request. ;
  • the new MME deletes the bearer on which the UE is activated.
  • IMSI is used as the user identity, the UE needs to perform emergency registration before establishing an emergency session.
  • the foregoing describes the emergency access method in the evolved network by using a specific embodiment.
  • the following describes the method for the UE to implement emergency access through the UMTS system:
  • FIG. 8 is a flowchart of a second method for emergency access of a UE according to an embodiment of the present invention.
  • the core network side is the SGW and the PGW.
  • the SGSN is equivalent to the MME in the evolved network, and the other is the GGSN on the core network side. The steps are described in detail:
  • the UE After establishing an RRC connection with the RNC, the UE sends an attach request message to the SGSN, where the message carries parameters: emergency call attribute information, Attach Type, Follow on Request, and user identifier.
  • the emergency call attribute information is used to indicate that the network side UE is to make an emergency call, which may be an emergency call indication, an emergency call type, or a specific request for an emergency call, etc.;
  • Follow on request indicates whether the network releases the S1 connection after the attachment is completed. , set by the UE during normal attachment, set by the SGSN during emergency attach; Attach type is used to indicate the type of attachment; for user identification, there are two cases:
  • the user identifier is IMEI
  • the user ID can be IMSI, but also P-TMSI and old
  • the UE Before the UE sends the attach request message, it needs to establish an RRC connection with the RNC. It may add an "emergency attachment" to the RNC emergency call in the "cause" of the RRC connection request message, or may indicate “emergency attachment” by a combination of multiple parameters.
  • the UE also indicates “emergency call type (eg, fire alarm, car accident)" through the dedicated parameter of the RRC connection request message; "specify to maintain RRC connection” by specifying a specific parameter in the RRC connection request message, it can be understood that the UE can also
  • the RNC emergency call is indicated by other emergency call identification information.
  • the RNC pre-schedules the air interface resource according to the emergency call QoS information configured on the RNC according to the parameter that the UE carried in the RRC connection request message or the attach request message is used to indicate the emergency call, and the emergency call QoS information may be according to the emergency call type or Specific requirements for emergency calls.
  • the SGSN requests the identity of the user to the EIR through the identity check message. If the user is in the blacklist, the SGSN rejects the attach request.
  • the SGSN sends an attach accept message to the UE.
  • the parameter should be carried in the attach accept message;
  • Follow on Request is set by the UE during normal attach, and can be set by the SGSN during emergency attach, indicating that the Iu connection is not released after the attach, to ensure The priority and reliability of the established emergency bearers;
  • step 803 the UE completes the message by attaching Received P-TMSI;
  • the core network side node is the SGW and the PGW.
  • the SGSN is equivalent to the MME in the evolved network, and the other is the core network side node is the GGSN. Specific implementations can be found in the specific embodiments below.
  • the UE performs registration in the IMS domain.
  • the SGSN When the UE performs emergency access through the UMTS network, the SGSN receives the attach request message sent by the UE, and selects the configured emergency call Qos information and the manner of the bearer to be established through the emergency bearer attribute information in the message, and receives the
  • the connection establishment request is sent to the selected core network side node GGSN or PGW capable of implementing emergency access, and the emergency bearer of the RNC to the selected core network side node is established, and is scheduled by the RNC.
  • a pre-allocated air interface resource is established to establish an air interface side bearer.
  • FIG. 9 is a flowchart of Embodiment 1 of a method for emergency access of a UE according to an embodiment of the present disclosure.
  • the UE does not have a UICC, and uses IMEI as the user identifier to establish an emergency bearer. The following detailed steps are described in detail:
  • the UE After the UE establishes an RRC connection with the RNC, the UE sends an attach request message to the SGSN, where the message carries parameters: emergency call attribute information, Attach Type, follow on request, IMEIo
  • the emergency call attribute information indicates that the network side UE is to make an emergency call
  • the emergency call attribute information may be: an emergency call indication, an emergency call type, or a specific request for an emergency call;
  • the Follow on request indicating that the network is attached. Whether the Iu connection is released afterwards, the Follow on request is set by the UE when it is normally attached, and can be set by the SGSN during emergency attach to enhance the priority and reliability of the established emergency bearer;
  • the Attach type indicates the type of attachment.
  • the UE needs to establish an RRC connection with the RNC before sending the attach request, and may add an "emergency attachment" to the "cause" of the RRC message to indicate the RNC emergency call, or may use multiple parameters.
  • the combination of numbers indicates “emergency attachment”.
  • the UE also indicates "emergency call type (eg, fire alarm, car accident)" through a dedicated parameter of the RRC message; “requires to maintain RRC connection" by a specific parameter in the RRC message. It can be understood that the UE can also use other emergency call identification information to indicate the RNC emergency call.
  • the UE According to the RRC connection request or the attach request, the UE carries a parameter for indicating an emergency call,
  • the RNC uses the Qos information configured on the RNC to pre-schedule the air interface resources.
  • the emergency call Qos information can be configured according to the emergency call type or for emergency call specific requirements.
  • the UE may reserve air interface resources in advance for the emergency call/emergency call type.
  • the SGSN may request the identity of the user by using the identity check message according to the requirement of the operator. If the user is in the blacklist, the SGSN rejects the attach request.
  • the SGSN sends an attach accept message to the UE.
  • this parameter is carried.
  • follow on request is set by the UE during normal attach, and is set by the SGSN during emergency attach, indicating that the Iu connection is not released after attachment.
  • the UE performs an emergency bearer setup by activating a Packet Data Protocol (PDP) context request message, where the PDP context request message carries parameters: an Em-APN or an emergency call attribute information, a bearer identifier, a request Qos information, a PDP address, and a protocol. Configuration Options? If the UE has special requirements for emergency calls such as Qos, it is indicated by emergency call attribute information such as voice and video. Of course, an emergency call can also be indicated by the emergency call attribute information.
  • PDP Packet Data Protocol
  • the Protocol Configuration Options are used to transfer parameters between the UE and the PGW, and the SGSN and SGW transparently pass the parameters.
  • the UE informs the PGW to select a P-CSCF with specific processing capability through the Protocol Configuration Options (for example: support the use of anonymous users to directly establish an emergency session without IMS registration).
  • the PDP address is left blank. 906.
  • the SGSN performs SGW and PGW selection, and sends a setup bearer request message to the selected SGW.
  • the SGSN uses the Em-APN or the locally configured Em-APN to obtain the PGW, SGW capable of accessing the emergency service PDN;
  • the network will be able to access the emergency PGW of the emergency service PDN and the emergency SGW is configured in the SGSN.
  • the SGSN may select to configure the local emergency call Qos information according to the specific emergency service type indicated by the UE or the emergency service specific requirement.
  • the SGSN allocates the user plane address and the TEID to the selected one.
  • the SGW sends a bearer setup request message carrying parameters: emergency call Qos information, Em-APN, IMEI, PDN Address Allocation ⁇ Protocol Configuration Options ⁇ bearer identifier, user plane address and TEID assigned by the SGSN.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, this must be set to immediately assign an IP address, and the SGSN can request to assign a specific IP address for a specific type of emergency call. The follow on request is judged by the SGSN to not release the Iu connection after attachment. These two parameters are mandatory by the SGSN due to the need for emergency services, which guarantees the priority and reliability of the established connection.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and sends a bearer setup request message to the PGW, where the message carries parameters: an emergency call QoS information or an Em-APN, an IMEK bearer identifier, a PDN Address Allocation ⁇ Protocol Configuration Options, and an SGW assignment.
  • User plane and control plane address and TEID are parameters: an emergency call QoS information or an Em-APN, an IMEK bearer identifier, a PDN Address Allocation ⁇ Protocol Configuration Options, and an SGW assignment.
  • the PGW interacts with the PCRF
  • the PGW allocates an uplink user plane and a control plane address and a TEID, and the PGW sends a create bearer response message to the SGW, carrying parameters: a PGW user plane and a control plane address, and a TEID, a PDN.
  • the PDN Address Information is an IP address assigned by the PGW to the UE.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and the SGW sends a create bearer response message to the SGSN, carrying parameters: a user plane and a control plane address, and a TEID, a PDN Address Information ⁇ Protocol Configuration Options, and a bearer identifier;
  • the radio access bearer (RAB, Radio Access)
  • Bearer is established, in this step, the RNC user plane address and TEID are sent to the SGSN;
  • the RAB bearer is an air interface bearer in the UMTS network, and the radio resource is generally referred to as an air interface bearer.
  • the UE responds by activating a PDP context accept message.
  • the IMSI can be used for emergency attach and bearer establishment.
  • the specific steps are substantially the same as the embodiment, except that the user identifier uses the IMSI.
  • Embodiment 10 is a flow chart of Embodiment 2 of the method for emergency access of a UE according to an embodiment of the present invention.
  • the UE uses IMEI as a user identifier to establish multiple emergency bearers. The following detailed steps are specifically described:
  • the UE After the UE establishes an RRC connection with the RNC, the UE sends an attach request to the SGSN, carrying parameters: emergency call attribute information, Attach Type, follow on Request, and IMEI.
  • the emergency call attribute information is used to indicate that the network side UE is to make an emergency call.
  • the emergency call attribute information may be an emergency call indication, an emergency call type, or a specific request for an emergency call;
  • follow on request indicates that the network is attached. Whether to release the Iu connection, the Follow on request is set by the UE when it is normally attached, and is set by the SGSN during emergency attach, which can ensure the priority and reliability of the connection to be established; Attach type indicates the type of attachment.
  • the UE needs to establish an RRC connection with the RNC before sending the attach request, and may add an "emergency attachment" to the "cause" of the RRC message to indicate the RNC emergency call, or may use multiple parameters.
  • the combination of numbers indicates “emergency attachment”.
  • the UE also indicates "emergency call type (eg, fire alarm, car accident)" through a dedicated parameter of the RRC message; "requires to maintain RRC connection" by a specific parameter in the RRC message.
  • the UE carries the parameter for indicating the emergency call, and the RNC pre-schedules the air interface resource using the emergency Qos configured on the RNC (the emergency Qos may be based on the emergency call type or the emergency call specific requirement).
  • the UE may reserve air interface resources in advance for the emergency call/emergency call type
  • the SGSN requests the identity of the user to the EIR through the identity check message. If the user is in the blacklist, the SGSN rejects the attach request.
  • the SGSN sends an attach accept message to the UE, if the SGSN allocates a new message to the UE.
  • the follow on request is set by the UE during normal attach, and is set by the SGSN during emergency attach, indicating that the Iu connection is not released after attachment.
  • step 1003 the UE indicates that the P-TMSI is received by using an attach complete message.
  • the UE performs an emergency bearer setup by activating a PDP context request message, and carries parameters: an Em-APN or emergency call attribute information, a bearer identifier, a request Qos information, a PDP address, and a Protocol Configuration Options.
  • the Protocol Configuration Options are used to transmit parameters between the UE and the PGW, and the SGSN and the SGW transparently transmit the parameters.
  • the UE informs the PGW through the Protocol Configuration Options that it selects a P-CSCF with specific processing capabilities (eg, supports the use of anonymous users to directly establish an emergency session without IMS registration).
  • the PDP address is left blank.
  • the SGSN performs SGW and PGW selection, and sends a setup bearer request message to the selected SGW.
  • the SGSN can use the following two methods to select SGW and PGW:
  • the SGSN uses the local configuration Em-APN to obtain the energy.
  • PGW SGW that is accessible to the emergency service PDN;
  • the "emergency PGW” and “emergency SGW” that can access the emergency service PDN are configured by the network in the SGSN.
  • the SGSN may select to configure the local emergency call Qos information according to the specific emergency service type indicated by the UE or the emergency service specific requirement.
  • the SGSN allocates a user plane address and a TEID for the pre-selected SGW and PGW.
  • a bearer setup request message is sent to the SGW, carrying parameters: emergency call Qos information, Em-APN, IMEK PDN Address Allocation, Protocol Configuration Options, bearer identity, SGSN user plane address, and TEID.
  • PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, this must be set to immediately assign an IP address.
  • the SGSN can request to assign a specific IP address for a specific type of emergency call. The follow on request is judged by the SGSN to not release the Iu connection after attachment. Both of these parameters are enforced by the SGSN due to the need for emergency services.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and sends a default bearer request message to the PGW, carrying parameters: emergency call QoS information, Em-APN, IMSK bearer identifier, PDN Address Allocation ⁇ Protocol Configuration Options ⁇ SGW allocation User plane and control plane address and TEID;
  • the PGW interacts with the PCRF
  • the PGW allocates an uplink user plane and a control plane address and a TEID, and the PGW sends a default bearer response message to the SGW, carrying parameters: a user plane and a control plane address allocated by the PGW.
  • the PDN Address Information is an IP address assigned by the PGW to the UE.
  • the SGW allocates a downlink user plane and a control plane address and a TEID, and the SGW sends a default bearer response message to the SGSN, carrying parameters: a user plane and a control plane address, and a TEID, PDN.
  • the RAB bearer is established.
  • the RNC user plane address and the TEID are sent to SGSN;
  • the UE responds by activating a PDP context accept message.
  • the PGW or the UE triggers the PGW to establish an emergency dedicated bearer.
  • the Qos information of the emergency proprietary bearer may come from the PGW, PCRF or SGSN.
  • the core network side node is the SGW and the PGW.
  • FIG. 11 is a flowchart of Embodiment 3 of the method for UE emergency access in the embodiment of the present invention.
  • the UE does not have a UICC, and uses an IMEI as a user identifier to establish an emergency bearer. The following detailed steps are specifically described:
  • the UE After the UE establishes an RRC connection with the RNC, the UE sends an attach request message to the SGSN, where the message carries parameters: emergency call attribute information, Attach Type, follow on request, IMEI;
  • the emergency call attribute information indicates that the network side UE is to make an emergency call, and the emergency call attribute information may specifically be an emergency call indication, an emergency call type, or a specific requirement for an emergency call;
  • Follow on request indicates whether the network is released after the attachment is completed. Iu connection, Follow on request is set by the UE when it is normally attached, and is set by the SGSN during emergency attach to ensure the priority and reliability of the connection to be established; Attach type is used to indicate the type of attachment.
  • the UE needs to establish an RRC connection with the RNC before sending the attach request. It may add an "emergency attachment” to the RNC emergency call in the "cause" of the RRC message, or may indicate “emergency attachment” by a combination of multiple parameters.
  • the UE also indicates "emergency call type (e.g., fire alarm, car accident)" by using a dedicated parameter of the RRC message; "requires to maintain RRC connection" by a specific parameter in the RRC message.
  • the UE According to the RRC connection request or the attach request, the UE carries a parameter for indicating an emergency call,
  • the RNC pre-schedules the air interface resources using the emergency call QoS information configured on the RNC, where, the emergency Calling Qos information can be configured based on the type of emergency call or specific requirements for emergency calls.
  • the UE may reserve air interface resources in advance for the emergency call/emergency call type.
  • the SGSN requests the identity of the user to the EIR through the identity check message. If the user is in the blacklist, the SGSN rejects the attach request.
  • the SGSN sends an attach accept message to the UE, if the SGSN allocates a new message to the UE.
  • the follow on request is set by the UE during normal attach, and is set by the SGSN during emergency attach, indicating that the Iu connection is not released after attachment.
  • step 1103 If the P-TMSI is carried in step 1103, the UE indicates that the P-TMSI is received by using an attach complete message.
  • the UE performs an emergency bearer setup by activating a PDP context request, and carries parameters: an Em-APN or emergency call attribute information, a bearer identifier, a PDP address, and a Protocol Configuration Options.
  • the Protocol Configuration Options are used to transmit parameters between the UE and the PGW, and the SGSN and the SGW transparently transmit the parameters.
  • the UE informs the PGW through the Protocol Configuration Options that it selects a P-CSCF with specific processing capabilities (eg, supports the use of anonymous users to directly establish an emergency session without IMS registration).
  • the PDP address is left blank.
  • the SGSN performs GGSN selection, and sends a bearer setup request message to the selected GGSN.
  • the SGSN can perform GGSN selection in two ways:
  • the SGSN After the SGSN identifies the emergency call, the SGSN obtains the GGSN capable of accessing the emergency service PDN by using the local configuration Em-APN;
  • the "emergency GGSN" capable of accessing the emergency service PDN is configured by the network in the SGSN.
  • the SGSN may select to configure the local emergency call Qos information according to the specific emergency service type indicated by the UE or the emergency service specific requirement.
  • the SGSN assigns a user plane address and a TEID to the selected GGSN.
  • Send the establishment to the SGSN Carry request message, carrying parameters: emergency call QoS information, Em-APN, IMEK PDP address, Protocol Configuration Options, bearer ID, user plane address and TEID assigned by SGSN.
  • the SGSN may require the assignment of a specific IP address for a particular type of emergency call.
  • the follow on request is judged by the SGSN to not release the Iu connection after attachment. Both of these parameters are forced by the SGSN due to the need for emergency services.
  • the GGSN allocates an uplink user plane and a control plane address and a TEID, and the GGSN sends a bearer response message to the SGSN, carrying parameters: a GGSN user plane and a control plane address, a TEID, a PDP address, a bearer identifier, and a Protocol Configuration Options.
  • the PDP address is an IP address assigned by the GGSN to the UE;
  • the GGSN interacts with the PCRF.
  • the RAB bearer is established, and the RNC user plane address and the TEID are sent to the SGSN in this step.
  • the UE responds by activating a PDP context accept message.
  • the IMSI can be used for emergency attach and bearer establishment.
  • the specific process is substantially the same as the flow of this embodiment, except that the user identifier uses the IMSI.
  • FIG. 12 it is a flowchart of Embodiment 4 of the method for UE emergency access in the embodiment of the present invention.
  • the UE does not have a UICC, and uses an IMEI as a user identifier to establish an emergency bearer. The following describes the specific steps:
  • the UE After the UE establishes an RRC connection with the RNC, the UE sends an attach request to the SGSN, carrying parameters: emergency call attribute information, Attach Type, follow on request, IMEI;
  • the emergency call attribute information is used to indicate that the network side UE is to make an emergency call, and the emergency call attribute information may specifically be an emergency call indication, an emergency call type, a specific request for an emergency call, etc.;
  • Follow on request indicates whether the network is released after the attachment is completed. Iu connection; Attach type Indicates the type of attachment.
  • Follow on request is set by the UE during normal attachment, and is set by the SGSN during emergency attachment to ensure the priority and reliability of the connection to be established.
  • the UE needs to establish an RRC connection with the RNC before sending the attach request, and may add an "emergency attachment" to the RNC emergency call in the "cause" in the RRC connection request message, or may indicate “emergency attachment” by a combination of multiple parameters.
  • the UE also indicates "emergency call type (e.g., fire alarm, car accident)" by using the dedicated parameter of the RRC connection request message; "requires to maintain RRC connection” by a specific parameter in the RRC connection request message. It can be understood that other emergency call identification information may also be carried in the RRC connection request message.
  • the UE carries the parameter for indicating the emergency call, and the RNC pre-schedules the air interface resource using the emergency Qos configured on the RNC (the emergency Qos may be based on the emergency call type or the emergency call specific requirement).
  • the UE may reserve air interface resources in advance for the emergency call/emergency call type
  • the SGSN requests the identity of the user to the EIR through the identity check message. If the user is in the blacklist, the SGSN rejects the attach request.
  • the SGSN sends an attach accept message to the UE, if the SGSN allocates a new message to the UE.
  • P-TMSI carries this parameter.
  • follow on request is set by the UE when it is normally attached, and is set by the SGSN when it is attached urgently, indicating that the Iu connection is not released after attachment;
  • step 1203 the UE indicates that the P-TMSI is received by using an attach complete message.
  • the UE performs an emergency bearer setup by activating a PDP context request, and carries parameters:
  • Em-APN or emergency call attribute information bearer identifier, request Qos information, PDP address, Protocol Configuration Options;
  • the Protocol Configuration Options are used to transfer parameters between the UE and the PGW, and the SGSN and SGW transparently pass the parameters.
  • the UE informs the PGW to select a P-CSCF with specific processing capability through the Protocol Configuration Options (for example: support the use of anonymous users to directly establish an emergency session without IMS registration).
  • the PDP address is left blank.
  • the SGSN performs GGSN selection, and sends a default bearer request to the selected GGSN. Message
  • the SGSG can perform GGSN selection in the following ways:
  • the SGSN After the SGSN identifies the emergency call, the SGSN obtains the GGSN capable of accessing the emergency service PDN by using the local configuration Em-APN;
  • the "emergency GGSN" that is capable of accessing the emergency service PDN by the network is configured
  • the SGSN may select the local emergency call Qos information according to the specific emergency service type indicated by the UE or the emergency service specific requirement.
  • the SGSN assigns a user plane address and a TEID to the selected SGSN.
  • the GGSN is configured to send a default bearer request message carrying parameters: emergency call Qos information, Em-APN, IMEK PDP address, Protocol Configuration Options, bearer identifier, SGSN user plane address, and TEID.
  • the SGSN may require the assignment of a specific IP address for a particular type of emergency call. The follow on request is judged by the SGSN to not release the Iu connection after attachment. Both of these parameters are enforced by the SGSN due to the need for emergency services.
  • the GGSN allocates an uplink user plane and a control plane address and a TEID, and the GGSN sends a default bearer response to the SGSN, carrying parameters: a user plane and a control plane address and a TEID, a PDP address, a bearer identifier, and a Protocol Configuration Options allocated by the GGSN.
  • the PDP address is an IP address assigned by the GGSN to the UE;
  • the GGSN interacts with the PCRF
  • the RAB bearer is established.
  • the RNC user plane address and TEID are sent to
  • the UE responds by activating a PDP context accept message.
  • the PGW or the UE triggers the PGW to establish an emergency dedicated bearer.
  • the Qos information of the emergency proprietary bearer may come from the GGSN, PCRF or SGSN.
  • the embodiments of the present invention provide a method, a device, and a system for emergency access of a UE, which are used to implement user access in an emergency situation.
  • the emergency call QoS information and the emergency bearer establishment mode are selected, and the core network side device capable of emergency access is selected, and a bearer setup request message is sent to the core network side device, where the message carries the user plane allocated by the access network side device.
  • the emergency bearer between the devices is used to establish an emergency session of the IMS domain to implement emergency access of the UE. In an emergency situation, emergency access of any UE under any conditions can be implemented to meet user requirements.
  • the network system includes: an access network side device 1301, a core network side device 1302, and a core network side device 21303, wherein: the access network side device 1301 is configured to receive an emergency call carried by the UE.
  • the attachment request message of the attribute information allocates user plane resources according to the emergency call attribute information, schedules the air interface resource, and establishes an air interface side emergency bearer;
  • the core network side device one 1302 is configured to receive an attach request message of the UE that carries the emergency call attribute information and the user plane resource allocated by the access network side device 1301, and selects the pre-configured emergency call Qos according to the emergency call attribute information.
  • Information and emergency bearer establishment mode selecting the core network side device 21303 capable of emergency access and transmitting an emergency bearer request message, the message carrying the user plane resource allocated by the access network side device, establishing the access network side The emergency bearer of the device 1301 to the selected core network side device 21303;
  • the core network side device 2303 is configured to establish an emergency bearer to the access network side device 1301 when receiving the emergency bearer request message. It can be seen that the core network side device receives an attach request message that is sent by the access network side device and carries the emergency call attribute information and the user plane resource allocated by the access network side device, and selects a pre-configured according to the emergency call attribute information. The emergency call QoS information and the emergency bearer establishment mode are selected, and the core network side device 2 capable of emergency access is selected, and the emergency bearer request message carrying the user plane resource is sent to the core network side device 2, and the access network is established.
  • An emergency bearer is sent from the side device to the core network side device 2, and the air interface resource is scheduled by the access network side device to establish an air interface side emergency bearer, so that an emergency bearer can be established between the UE and the core network side device 2
  • the user can establish an emergency session in the IMS domain to implement emergency access of the user to meet the needs of the user in an emergency situation.
  • the access network side device may be further configured to: before receiving the attach request message, receive a radio resource control RRC connection request message carrying the emergency call identifier information of the UE, and establish an RRC connection.
  • the access network side device is an evolved base station eNB
  • the core network side device 1 is the MME
  • the core network side device 1 is
  • the core network side device 2 is the SGW and the PGW
  • the MME receives the eNB.
  • the core network side device SGW and the PGW that are capable of emergency access, and establish an emergency bearer between the eNB, the SGW, and the PGW; if the UE is emergency access through the UMTS network, the access network side device
  • the core network side device is the SGSN
  • the core network side device 2 is the SGW and the PGW, or the GGSN
  • the SGSN receives the attach request message transmitted by the RNC, and selects the core network side device capable of emergency access.
  • the SGW and the PGW, or the GGSN establish an SGSN, a serving gateway SGW, and a packet data network gateway PGW, or an emergency bearer between the SGSN and the GGSN, and the establishment of the emergency bearer request message is triggered by the establishment of a packet data protocol PDP context request message.
  • the emergency call attribute information may be an emergency call indication, an emergency call type, and a specific requirement for an emergency call.
  • the network side device includes: a receiving unit 1401, a selecting unit 1402, and a sending unit 1403, where: the receiving unit 1401 is configured to receive an attach request message that is carried by the access network side device and carries the emergency call attribute information and the user identifier;
  • the selecting unit 1402 selects, according to the emergency call attribute information received by the receiving unit 1401, the pre-configured emergency call QoS information, the emergency bearer establishment mode, and the core network side device capable of emergency access;
  • a sending unit configured to send an emergency bearer request message to the selected core network side device, where the message carries the user plane resource allocated by the access network side device, and establishes the access network side device to the selected core network Emergency bearer between devices.
  • the core network side device When receiving the attach request message, the core network side device selects the pre-configured emergency call QoS information, the emergency bearer establishment mode, and the core network side device capable of emergency access according to the emergency call attribute information carried in the message, and And sending an establishment bearer request message to the selected core network side device, and establishing an emergency bearer of the access network side device to the selected core network side device, and matching with the air interface side bearer established by the access network side device, The emergency bearer of the UE to the selected core network side device implements emergency access of the UE.
  • the core network side device when the UE accesses through the evolved network, the core network side device is an MME; when the UE accesses through the UMTS network, the core network side device is specifically an SGSN.
  • the access network side device includes: a first receiving unit 1501, a resource allocating unit 1502, a resource scheduling unit 1503, and a first sending unit 1504.
  • the second sending unit 1505 where:
  • the receiving unit 1501 is configured to receive an attach request message of the UE that carries emergency call attribute information.
  • the resource allocation unit 1502 is configured to allocate a user plane resource according to the emergency call attribute information received by the receiving unit 1501.
  • the resource scheduling unit 1503 is configured to schedule the reserved air interface resource according to the emergency call attribute information received by the receiving unit 1501.
  • the first sending unit 1504 is configured to send the user plane resource allocated by the resource allocating unit 1502 along with the attach request message;
  • the second sending unit 1505 is configured to send a radio bearer setup request message after the resource scheduling unit 1503 completes resource scheduling, and establish an air interface side emergency bearer.
  • the access network side device may schedule the reserved air interface resource according to the emergency call attribute information in the message, and establish an air interface side emergency bearer, and cooperate with the core network side to establish an emergency.
  • the bearer is used to implement an emergency session and implement emergency access of the UE.
  • the access network side device When the UE accesses through the evolved network, the access network side device is an eNB; when the UE accesses through the UMTS network, the access network side device is an RNC.
  • the access network side device may also schedule the reserved air interface resources according to the emergency call identification information carried in the RRC connection request message when receiving the RRC connection request message, and the description will not be repeated.
  • the core network side device receives an attach request message transmitted by the access network side device, where the message carries the emergency call attribute information, the user identifier, and the user plane resource allocated by the access network side device, and selects according to the emergency call attribute information.
  • Pre-configured emergency call service quality Qos information and emergency bearer establishment method Pre-configured emergency call service quality Qos information and emergency bearer establishment method
  • the access network side device allocates air interface resources and establishes an air interface side emergency bearer.
  • the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

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

L'invention concerne un procédé, un dispositif et un système pour fournir un accès d'urgence à un dispositif utilisateur. Le procédé comprend les étapes suivantes : la réception d'un message de demande de pièce jointe, qui porte des informations d'attributs d'appel d'urgence (1) ; la reconnaissance de l'appel indiqué par le message de demande de pièce jointe comme étant un appel d'urgence, sur la base des informations d'attributs d'appel d'urgence (2) ; et la sélection d'un dispositif sur le côté du réseau fédérateur qui est disponible pour cet accès d'urgence, puis l'envoi d'un message de demande pour construire un palier d'urgence pour le dispositif choisi sur le côté réseau fédérateur (3). La présente invention permet à tout utilisateur d'accéder à un réseau lors d'une urgence.
PCT/CN2009/070333 2008-02-03 2009-02-02 Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur WO2009097818A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810006121.1 2008-02-03
CN2008100061211A CN101500213B (zh) 2008-02-03 2008-02-03 一种用户设备紧急接入的方法、设备和系统

Publications (1)

Publication Number Publication Date
WO2009097818A1 true WO2009097818A1 (fr) 2009-08-13

Family

ID=40947044

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070333 WO2009097818A1 (fr) 2008-02-03 2009-02-02 Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur

Country Status (2)

Country Link
CN (1) CN101500213B (fr)
WO (1) WO2009097818A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3291625A4 (fr) * 2015-04-30 2018-04-25 Samsung Electronics Co., Ltd. Procédé de formation de support pour la sécurité publique dans un système de communication sans fil, et dispositif associé
EP3406093A4 (fr) * 2016-01-22 2019-10-16 BlackBerry Limited Détermination de nom de point d'accès pour des services essentiels à la mission
RU2705452C1 (ru) * 2016-01-15 2019-11-07 Телефонактиеболагет Лм Эрикссон (Пабл) Обработка однонаправленного канала mbms

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3306966B1 (fr) 2009-04-17 2020-07-22 NEC Corporation Système de communication mobile, station de base, appareil de passerelle, appareil de réseau central et procédé de communication
CN101998329B (zh) * 2009-08-18 2013-08-07 电信科学技术研究院 一种保证紧急业务连续性的方法、设备和系统
CN102014376B (zh) * 2009-09-07 2015-03-11 华为技术有限公司 附着方法、寻呼方法、去附着方法及相关设备
US20110070862A1 (en) * 2009-09-22 2011-03-24 Te-Ming Chen Method of Handling Paging and Related Communication Device
AU2010302349B2 (en) 2009-10-02 2014-07-17 Blackberry Limited Determining establishment causes for emergency sessions
CN102045678B (zh) * 2009-10-15 2013-03-13 电信科学技术研究院 一种通信处理方法及装置
CN102158907B (zh) 2010-02-12 2013-01-23 华为技术有限公司 优先级业务处理方法、装置和系统
CN102223688B (zh) * 2010-04-16 2016-04-13 中兴通讯股份有限公司 一种处理mtc优先警报消息的方法和系统
CN101827345B (zh) * 2010-05-14 2015-06-10 中兴通讯股份有限公司 紧急eps业务的实现方法、系统和终端
CN102232309B (zh) * 2010-08-20 2013-10-09 华为技术有限公司 基于智能终端的网络优化方法、设备及系统
CN102413448B (zh) * 2010-09-25 2016-06-08 中兴通讯股份有限公司 Mtc设备发送优先告警数据的承载建立方法及系统
CN102790979B (zh) * 2011-05-18 2015-06-17 华为终端有限公司 在机器间通信中实现优先告警的方法及装置
CN103096283A (zh) * 2011-11-07 2013-05-08 中兴通讯股份有限公司 紧急呼叫业务的实现方法及装置
CN102752739B (zh) * 2012-06-26 2016-06-01 中国联合网络通信集团有限公司 空中开卡方法、终端、服务器及系统
CN102857574B (zh) * 2012-09-19 2015-04-29 中国联合网络通信集团有限公司 物联网信息处理方法和装置
CN104254055B (zh) * 2013-06-27 2018-03-27 电信科学技术研究院 一种紧急呼叫实现方法、设备及系统
CN104284318B (zh) * 2013-07-09 2017-12-15 普天信息技术研究院有限公司 一种td‑lte系统中紧急呼叫的识别方法
CN104852994B (zh) * 2014-02-13 2018-03-23 普天信息技术研究院有限公司 一种终端侧分组数据网服务器地址管理方法
CN104853331A (zh) * 2014-02-17 2015-08-19 普天信息技术有限公司 一种被叫紧急呼叫处理方法及系统
CN111182624A (zh) * 2014-03-10 2020-05-19 北京三星通信技术研究有限公司 一种用户位置信息汇报的方法
CN105578441B (zh) * 2014-10-15 2019-01-01 中国移动通信集团公司 一种网络服务质量参数的更新方法和装置
CN108353245A (zh) * 2015-11-27 2018-07-31 华为技术有限公司 一种信息内容传输方法和装置
WO2018000363A1 (fr) 2016-06-30 2018-01-04 华为技术有限公司 Procédé, dispositif et système de réseau de transmission de données
CN109314695B (zh) * 2016-07-04 2021-01-29 华为技术有限公司 确定用户面协议栈的方法、控制面网元和系统
WO2018049681A1 (fr) * 2016-09-19 2018-03-22 华为技术有限公司 Procédé et appareil de traitement de service de données, terminal et dispositif de réseau
CN107222933B (zh) * 2017-06-27 2020-11-17 努比亚技术有限公司 一种通信方法、终端和计算机可读存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003244284A (ja) * 2002-02-20 2003-08-29 Nec Corp 移動端末、緊急呼管理装置、緊急呼管理システム及び緊急呼の管理方法
WO2005004526A1 (fr) * 2003-07-04 2005-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Procede et agencement dans un systeme de telecommunication
CN1738484A (zh) * 2001-04-27 2006-02-22 诺基亚公司 处理网络识别紧急会话的方法和系统
CN1909718A (zh) * 2005-08-03 2007-02-07 中兴通讯股份有限公司 一种wcdma系统中的紧急呼叫处理方法
CN1933656A (zh) * 2005-09-16 2007-03-21 中兴通讯股份有限公司 宽带码分多址系统中的紧急呼叫处理方法
JP2007134841A (ja) * 2005-11-09 2007-05-31 Nec Corp 移動体通信システム、無線ネットワーク制御装置及びそれらに用いる発信者位置情報通知機能の実現方法
WO2007108960A2 (fr) * 2006-03-20 2007-09-27 Lucent Technologies Inc. Procédé permettant de passer des appels d'urgence sur un réseau avec une liaison de communication terrestre défectueuse

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1738484A (zh) * 2001-04-27 2006-02-22 诺基亚公司 处理网络识别紧急会话的方法和系统
JP2003244284A (ja) * 2002-02-20 2003-08-29 Nec Corp 移動端末、緊急呼管理装置、緊急呼管理システム及び緊急呼の管理方法
WO2005004526A1 (fr) * 2003-07-04 2005-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Procede et agencement dans un systeme de telecommunication
CN1909718A (zh) * 2005-08-03 2007-02-07 中兴通讯股份有限公司 一种wcdma系统中的紧急呼叫处理方法
CN1933656A (zh) * 2005-09-16 2007-03-21 中兴通讯股份有限公司 宽带码分多址系统中的紧急呼叫处理方法
JP2007134841A (ja) * 2005-11-09 2007-05-31 Nec Corp 移動体通信システム、無線ネットワーク制御装置及びそれらに用いる発信者位置情報通知機能の実現方法
WO2007108960A2 (fr) * 2006-03-20 2007-09-27 Lucent Technologies Inc. Procédé permettant de passer des appels d'urgence sur un réseau avec une liaison de communication terrestre défectueuse

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3291625A4 (fr) * 2015-04-30 2018-04-25 Samsung Electronics Co., Ltd. Procédé de formation de support pour la sécurité publique dans un système de communication sans fil, et dispositif associé
US10368263B2 (en) 2015-04-30 2019-07-30 Samsung Electronics Co., Ltd. Method for forming bearer for public safety in wireless communication system and device therefor
RU2705452C1 (ru) * 2016-01-15 2019-11-07 Телефонактиеболагет Лм Эрикссон (Пабл) Обработка однонаправленного канала mbms
US11026056B2 (en) 2016-01-15 2021-06-01 Telefonaktiebolaget Lm Ericsson (Publ) MBMS bearer handling
EP3406093A4 (fr) * 2016-01-22 2019-10-16 BlackBerry Limited Détermination de nom de point d'accès pour des services essentiels à la mission
US10716152B2 (en) 2016-01-22 2020-07-14 Blackberry Limited Access point name determination for mission critical services
US11240856B2 (en) 2016-01-22 2022-02-01 Blackberry Limited Access point name determination for mission critical services
US11729840B2 (en) 2016-01-22 2023-08-15 Malikie Innovations Limited Access point name determination for mission critical services

Also Published As

Publication number Publication date
CN101500213B (zh) 2011-04-20
CN101500213A (zh) 2009-08-05

Similar Documents

Publication Publication Date Title
WO2009097818A1 (fr) Procédé, dispositif et système pour fournir un accès d'urgence à un dispositif utilisateur
JP6699800B2 (ja) 方法、セッション管理機能ノード、ユーザプレーン機能ノード、ならびにセッション管理パラメータメンテナンス用ユーザ機器およびそのコンピュータ可読記録媒体
KR101575223B1 (ko) 사설기지국에서 로컬 브레이크 세션을 요청하는 방법 및 장치
KR100879811B1 (ko) 이동전화가 발신하는 호출들에서 안내들을 제공하는 기술
KR100651436B1 (ko) Ｉｕ 인터페이스 상의 멀티미디어 방송/멀티캐스트 서비스신호 베어러 연결 방법
US9730251B2 (en) Method for supporting an emergency call in a mobile communication system
US20100226314A1 (en) Method for user equipment performing direct communications via hnb access systems
WO2009049529A1 (fr) Procédé d'établissement de support de charge et dispositif associé
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2009082936A1 (fr) Procédé et appareil pour un appel d'urgence
AU2002246300A1 (en) Technique for providing announcements in mobile-originated calls
WO2008019631A1 (fr) Procédé et système de transfert de matériel d'utilisateur dans un système de communication mobile
WO2011098051A1 (fr) Procédé, appareil et système pour le traitement de services prioritaires
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
WO2011054320A1 (fr) Procédé, dispositif et système permettant de transférer un service de protocole internet du réseau fédérateur
WO2018059401A1 (fr) Procédé, dispositif et système de commutation de réseau, et procédé et dispositif d'accès au réseau
WO2010111814A1 (fr) Appareil et procédé pour déplacer une station mobile wcdma avec le moins de perte de paquets
WO2014048397A1 (fr) Procédé, système et dispositif de commutation de chemins de communication
WO2008014684A1 (fr) Procédé permettant la mise en oeuvre de l'équilibrage des charges
WO2012097706A1 (fr) Procédé et système de modification de support
WO2012122910A1 (fr) Procédé et système de communication à double canal
WO2009018777A1 (fr) Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué
WO2011130906A1 (fr) Procédé, dispositif et système de mise en œuvre de services
WO2012126302A1 (fr) Procédé et système prenant en charge la communication simultanée pour un terminal à double mode, à double veille
WO2012024989A1 (fr) Procédé et système pour une libération de porteuse

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

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

Country of ref document: EP

Kind code of ref document: A1