WO2009097818A1

WO2009097818A1 - Method, device and system for providing emergency access for user device

Info

Publication number: WO2009097818A1
Application number: PCT/CN2009/070333
Authority: WO
Inventors: Qi Yu; Jinyi Zhou; Lan Liu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2008-02-03
Filing date: 2009-02-02
Publication date: 2009-08-13
Also published as: CN101500213A; CN101500213B

Abstract

A method, a device and a system for providing emergency access for a user device. The method involves: receiving an attachment request message, which carrying an emergency call attribute information (1); and recognizing the call indicated by the attachment request message to be an emergency call, based upon the emergency call attribute information (2); and selecting a device on the Core Network side that is available for this emergency access, then sending a request message for building an emergency bearing to the selected device on the Core Network side (3). The present invention makes it possible for any user to access to a network in an emergency.

Description

Method, device and system for emergency access of user equipment

The present application claims priority to Chinese Patent Application No. 200810006121.1, filed on February 3, 2008, entitled "A method, device and system for emergency access of user equipment", the entire contents of which are incorporated by reference. Combined in this application.

Technical field

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.

Background technique

The Universal Mobile Telecommunication System (UMTS) 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). 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.

In the LTE/SAE (Long Term Evolved/System Architecture Evolved), 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. In this normal 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.

However, in an emergency, such as a fire, earthquake, flood, alarm, ambulance, etc., if the user does not have an IMSI, or if there is an IMSI but is in an access restricted state, such as in a roaming area limit, the user The highest priority is required to access the network and perform specific emergency services. The inventors have found that there is no corresponding technical solution in the prior art to ensure that any user can access the network under any conditions in an emergency.

Summary of the invention

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;

And 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. As shown in the foregoing technical solution, 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.

DRAWINGS

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;

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; Figure

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.

detailed description

For convenience of description, the LTE/SAE network architecture in the prior art can be simplified. Referring to FIG. 1, 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.

A method for emergency access of a UE according to an embodiment of the present invention 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. .

Referring to FIG. 2, a flowchart of a method in an embodiment of the present invention includes the following steps:

Receiving an attach request message, where the attach request message carries emergency call attribute information;

2. Identify, according to the emergency call attribute information, that the call indicated by the attach request message is an emergency call;

3. Select a core network side device that can be urgently accessed, and send an emergency bearer request message to the core network side device.

The following is a description of the emergency access of the UE in the evolved network and the UMTS network: Referring to FIG. 3, which 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:

301. 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;

For user identification, there are two cases: (1) When the UE does not have an IMSI, the user identifier is an International Mobile Equipment Identity (IMEI, International Mobile Equipment Identity);

(2) When the UE has IMSI, the user identifier has two possibilities: IMSI; Global Unique Temporary Identity (GUTI) or Tracking Area Identity (TAI).

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;

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.

302. 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.

For emergency bearer establishment, the following methods are established:

(1) Establishing a universal emergency bearer between the UE and the PGW, 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;

(3) Several emergency bearers can be established synchronously between UE and PGW.

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.

303. 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.

It can be understood that whether the authentication process is required for emergency attachment depends on the operator's policy. An authentication vector may be specifically configured for emergency access on the network element node MME to perform an authentication process.

304. 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:

(1) After the MME identifies the emergency call, the MME uses the local Em-APN (Emergency-Access Point Name) to obtain the PGW or SGW that can access the emergency service PDN.

(2) "Emergency PGW" that will be able to access the emergency service PDN by the network, "emergency

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

Assigned by the MME.

If the eNB pre-allocates the user plane address and the TEID for the emergency bearer in step 302, The MME carries the parameter to the SGW in the establishment of the bearer request message. In this 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.

305. 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. User plane and control plane address and TEID allocated by the SGW;

306. If a Policy and Charging Control (PCC) network is deployed, 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.

307. 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.

308. 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.

309. The MME sends an attach accept message to the eNB, where the message carries the parameter: Em-APN,

PDN Address Information ^ Protocol Configuration Options ^ Bearer ID, Tracking Area Identity (TAI) list, user plane address and TEID assigned by the SGW;

If the MME allocates a GUTI to the UE, the message should also carry the GUTI parameter. The TAI list is a list of tracking area identifiers sent by the MME to the UE.

310. If the air interface resource scheduling is completed, the eNB sends a radio bearer setup request to the UE. Message, the message carries the NAS message attachment acceptance;

If the air interface resource scheduling is not completed, the message is sent after waiting for the scheduling to complete.

311. The UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;

312. The eNB forwards the attach complete message to the MME, where the message carries the parameter: a bearer identifier.

313. If multiple emergency bearers are established, the PGW may be triggered by the PGW or by the PCRF to establish a dedicated bearer;

314. The UE performs an emergency registration of the IMS domain.

When the UE uses the IMS domain anonymous user, the UE may not have to perform IMS domain emergency registration. 315. An emergency session establishment of the IMS domain.

For the emergency call QoS information, it can be configured on each network element node as needed. For example, it can include, but is not limited to, an eNB, an MME, a PGW, and a PCRF. When only one network element node is configured, a specific message or an existing message needs to be used. Add parameters to inform other required NE nodes. 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. For emergency calls, Qos information may be a set of Qos information that corresponds to a specific emergency or emergency service specific need.

It can be seen that, in the method, 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.

Different embodiments are described below by way of specific embodiments:

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:

401. 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)

Subsystem) Registration.

Attach type indicates the type of attachment;

PDN Address Allocation is set by the UE when it is normally attached, by emergency attachment

MME settings.

The UE may reserve air interface resources for emergency calls or different emergency call types.

402. 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.

403. 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:

(1) After the MME identifies the emergency call, the MME uses the local Em-APN to obtain the PGW, SGW that can access the emergency service PDN;

(2) The "emergency PGW" and "emergency SGW" that can access the emergency service PDN are configured by the network in 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.

If the eNB pre-allocates the user plane address and the TEID for the emergency bearer in step 402, the MME carries the parameter to the SGW in the setup bearer request message. In this 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.

405. 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;

406. If the PCC network is deployed, 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.

407. 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.

408. 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, Protocol Configuration Options, bearer ID;

409. 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;

If the MME allocates a GUTI to the UE, the message should also carry the GUTI parameter.

410. If the air interface resource scheduling is completed, the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;

411. The UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;

412. The eNB forwards an attach complete message to the MME, where the message carries a parameter: a bearer identifier.

413. The UE performs an emergency registration of the IMS domain.

When the UE uses the IMS domain anonymous user, the UE may not have to perform IMS domain emergency registration.

414. An emergency session establishment of the IMS domain.

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:

501 is the same as step 401 in the first embodiment, and will not be described again;

502. The eNB selects an MME and forwards an attach request message to the MME.

When the attach request is received, 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. Specifically, 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.

503. It is the same as step 403 in the first embodiment, and is not described again.

504. 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 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.

If the eNB pre-allocates the user plane address and the TEID for the emergency bearer in step 502, the MME carries the parameter to the SGW in the setup bearer request message. In this 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.

505. 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;

506. If a PCC network is deployed, 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.

507. 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.

508. 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.

At the same time, 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.

509. 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;

510. If the air interface resource scheduling is completed, the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;

511. 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.

If no user plane address and TEID are assigned to the default bearer in step 502, it is allocated in this step.

513. If 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;

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.

515. The SGW sends a setup bearer response message to the PGW.

It can be understood that this step and step 514 are in no particular order.

516. Optionally, 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.

517. An emergency session establishment of the IMS domain.

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. In this embodiment, 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.

602. The eNB selects an MME and forwards an attach request message to the MME.

Because it is an emergency call, 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).

According to the emergency call identifier information in the emergency call identifier or the attach request message in the RRC connection request message, 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.

603, which is the same as step 403 in the first embodiment of the method, and is not described again.

604. 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 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.

If the eNB pre-assigns the user plane address and the TEID to the default bearer in step 602, the MME carries the parameter to the SGW in the establishment of the default bearer request message. In this message, PDN Address Allocation indicates whether the IP address should be assigned immediately. In the case of an emergency call, 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. These two parameters are mandatory by the MME due to the need of emergency services, which can effectively guarantee the reliability of emergency bearers.

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.

605. 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 IMEK bearer ID, and the user plane address and TEID assigned by the SGW to the emergency private bearer.

606. If a PCC network is deployed, the PGW can interact with the PCRF.

607. 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.

SGW;

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;

608. The SGW allocates a downlink user plane and a control plane address for the default bearer and the dedicated bearer, respectively.

TEID, and sending a dedicated bearer response message and establishing a default bearer response message to the MME;

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.

609. 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

Information, Protocol Configuration Options, bearer ID, TAI table, user plane address and TEID assigned by the SGW. If the MME assigns a GUTI to the UE, 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.

610. If the air interface resource scheduling is completed, the eNB sends a radio bearer setup request message to the UE, where the message carries the NAS message attach and accept;

611. The UE sends a radio bearer setup response message to the eNB, where the message carries the NAS message attached;

612. The eNB sends an attach complete message and a bearer setup response message to the MME, and the message carries the bearer identifier respectively.

613. 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.

614. An emergency session establishment of the IMS domain.

It can be understood that, 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.

If the UE has the IMSI and the UE is in the roaming restricted area when the UE is powered on, 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. Method for Emergency Access A flowchart of Embodiment 4 is described in detail below through specific steps:

701-702, the UE sends an attach request to the newly selected new MME by using the eNB;

Before the acknowledgment request is sent, 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.

703. 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.

704. If the IMSI is not obtained in step 703, 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. ;

706-707. If the new MME has the bearer activated by the UE, the new MME deletes the bearer on which the UE is activated.

708-72 is substantially the same as 504-517 in the second embodiment of the method, except that the user identifier is IMSI, not ΙΜΕΙ, and is not described.

Similarly, since 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.

When the UMTS system is connected, there are two cases. One is that the core network side is the SGW and the PGW. In this scenario, 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:

801. 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:

(1) When the UE does not have IMSI or IMSI invalid, the user identifier is IMEI;

(2) When the UE has IMSI, the user ID can be IMSI, but also P-TMSI and old

RAI;

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.

802. According to the requirement of the operator, 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.

803. The SGSN sends an attach accept message to the UE.

If the SGSN allocates a new P-TMSI, 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;

804. If the P-TMSI parameter is carried in step 803, the UE completes the message by attaching Received P-TMSI;

805. Establish an emergency bearer according to the UE and the core network node.

When the UMTS system is accessed, there are two cases. One is that the core network side node is the SGW and the PGW. In this scenario, 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.

806. The UE performs registration in the IMS domain.

807. Establish an emergency session in the IMS domain.

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 When the activated PDP context request message sent by the user is sent, 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.

The following is a detailed description of the specific scenario:

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:

901. 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, and 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 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.

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.

902. 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.

903. The SGSN sends an attach accept message to the UE.

If the SGSN assigns a new P-TMSI 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.

904. If the P-TMSI is carried in step 903, the UE indicates to receive the P-TMSI by using an attach complete message.

905. 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.

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.

For SGW and PGW selection for the SGSN, the following two methods can be used:

(1) After the SGSN identifies the emergency call, the SGSN uses the Em-APN or the locally configured Em-APN to obtain the PGW, SGW capable of accessing the emergency service PDN;

(2) 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.

After the SGW and the PGW are selected, 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. In this message, 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.

907. 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;

908. If a PCC network is deployed, the PGW interacts with the PCRF;

909. 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.

Address Information, bearer ID, Protocol Configuration Options; The PDN Address Information is an IP address assigned by the PGW to the UE.

910. 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;

911, after the radio resource scheduling is completed, 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.

912. The UE responds by activating a PDP context accept message.

913. Perform an emergency registration of the IMS domain;

914. An IMS domain emergency session is established.

It can be understood that when the UE has the IMSI, 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.

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:

1001. 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.

According to the RRC connection request or the attach request, 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).

1002: According to the needs of the operator, 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.

1003. 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;

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.

1004. If the P-TMSI is carried in step 1003, the UE indicates that the P-TMSI is received by using an attach complete message.

1005. 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.

1006. 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:

(1) After the SGSN recognizes the emergency call, the SGSN uses the local configuration Em-APN to obtain the energy. PGW, SGW that is accessible to the emergency service PDN;

(2) The "emergency PGW" and "emergency SGW" that can access the emergency service PDN are configured by the network in the SGSN.

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. In this message, 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.

1007. 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;

1008. If a PCC network is deployed, the PGW interacts with the PCRF;

1009. 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.

TEID, PDN Address Information, bearer ID, Protocol Configuration Options;

The PDN Address Information is an IP address assigned by the PGW to the UE.

1010. 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.

Address Information, Protocol Configuration Options, bearer ID;

1011. The RAB bearer is established. In this step, the RNC user plane address and the TEID are sent to SGSN;

1012. The UE responds by activating a PDP context accept message.

1013. 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.

1014. Perform an emergency registration of the IMS domain;

1015. Establish an emergency session in the IMS domain.

In this embodiment, the core network side node is the SGW and the PGW. The following describes the case where the core network side node is the GGSN through another embodiment:

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:

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 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.

1102, according to the needs of the operator, 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.

1103. 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;

1104. If the P-TMSI is carried in step 1103, the UE indicates that the P-TMSI is received by using an attach complete message.

1105. 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.

1106. 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:

(1) 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;

(2) The "emergency GGSN" capable of accessing the emergency service PDN is configured by the network in the SGSN.

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.

1107. 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;

If a PCC network is deployed, the GGSN interacts with the PCRF.

1108. The RAB bearer is established, and the RNC user plane address and the TEID are sent to the SGSN in this step.

1109. The UE responds by activating a PDP context accept message.

1110. Optionally, performing an emergency registration of the IMS domain;

1111. Establish an emergency session in the IMS domain.

It can be understood that when the UE has the IMSI, 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.

Referring to 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:

1201. 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.

1202: According to the needs of the operator, 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.

1203. 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;

1204. If the P-TMSI is carried in step 1203, the UE indicates that the P-TMSI is received by using an attach complete message.

1205. 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.

1206. 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:

(2) The "emergency GGSN" that is capable of accessing the emergency service PDN by the network is configured

SGSN.

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.

1207. 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;

If a PCC network is deployed, the GGSN interacts with the PCRF;

1208. The RAB bearer is established. In this step, the RNC user plane address and TEID are sent to

SGSN;

1209. The UE responds by activating a PDP context accept message.

1210. 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.

1211. Optionally, perform an emergency registration of the IMS domain;

1212. Establish an emergency session in the IMS domain. 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. Receiving, by the core network side device, an attach request message transmitted by the access network side device, where the message carries the emergency call attribute information and the user plane resource allocated by the access network side device, and selects a pre-configuration 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 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. Resource, establishing an emergency bearer of the access network side device to the selected core network side device; and scheduling the air interface resource by the access network side device, and then establishing an air interface side emergency bearer, thereby establishing the UE and the selected core network side 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 method for the emergency access of the UE provided in the embodiment of the present invention is described in detail. The system and the device used in the embodiment of the present invention are described in detail below with reference to the accompanying drawings. Referring to FIG. 13, in the embodiment of the present invention, The network system structure is as follows: 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.

If the UE is emergency access through the evolved network, 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, and the MME receives the eNB. And 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 For the radio network controller RNC, the core network side device is the SGSN, the core network side device 2 is the SGW and the PGW, or the GGSN, and 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 following describes the above methods and devices in the network system:

14 is a schematic structural diagram of a core network side device according to an embodiment of the present invention, where the core 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.

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.

Specifically, 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 following describes an access network side device provided by an embodiment of the present invention:

15 is a schematic structural diagram of an access network side device according to an embodiment of the present invention. 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.

When receiving the attach request message of the UE, 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.

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.

A person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium. , including the following steps:

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;

Selecting a core network device capable of emergency access, and sending an emergency bearer request message, where the message carries the user identifier and the user plane resource allocated by the access network side device, and establishes the access network side device to the selected core. Emergency bearer of the network side equipment;

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.

The method, device and system for emergency access of a UE provided by the present invention are described in detail above. For those skilled in the art, according to the idea of the embodiment of the present invention, there will be a specific implementation manner and application scope. The details of the description are not to be construed as limiting the invention.

Claims

Claim

A method for emergency access of a user equipment, comprising:

Receiving an attach request message, where the attach request message carries emergency call attribute information; and identifying, according to the emergency call attribute information, the call indicated by the attach request message as an emergency call;

2. The method of emergency access of a user equipment according to claim 1, wherein the emergency call attribute information comprises at least one of the following:

Emergency call indication, type of emergency call, specific requirements for emergency calls.

The method for emergency access of a user equipment according to claim 1, wherein the call indicated by the attach request message is an emergency call, and further includes:

Select the configured emergency call quality of service Qos information.

The method for emergency access of a user equipment according to claim 3, wherein the sending an emergency bearer request message to the core network side device carries the emergency call Qos information.

The method for emergency access of the user equipment according to claim 1, wherein the call indicated by the attach request message is an emergency call, and further includes:

The emergency bearer establishment mode is selected; the emergency bearer establishment manner includes:

Establishing a universal emergency bearer, where the emergency bearer carries signaling and/or service data; establishing an emergency default bearer, and establishing an emergency dedicated bearer by the network side device during or after establishing the emergency default bearer process;

Several emergency default bearers and emergency private bearers are established synchronously.

The user equipment emergency access method according to claim 5, wherein when the policy charging control PCC network is deployed, the policy charging rule function entity PCRF triggers the core network side device to pre-establish a dedicated bearer. .

7. The method for emergency access of a user equipment according to claim 1, wherein: The core network side device capable of emergency access is specifically:

Use the local emergency access point name Em-APN to obtain core network side equipment capable of emergency access; or,

Core network-side devices that can be urgently accessed using network pre-configuration.

The method for emergency access of a user equipment according to claim 1, wherein if the attach request message is sent when the user equipment is emergency access through an evolved network, the core network capable of emergency access is selected. The side devices are a serving gateway SGW and a packet data gateway PGW;

If the attach request message is sent during emergency access by the universal mobile communication system UMTS network, the core network side device that can select emergency access is the SGW and the PGW, or the gateway general packet radio service support node GGSN.

The method for emergency access of a user equipment according to claim 8, wherein if the attach request message is sent by the user equipment when the user equipment accesses the emergency network, the attach request message carries an indication. Used to inform the PGW to select a proxy call session control function entity P-CSCF with specific processing capability;

If the attach request message is sent during emergency access through the UMTS network, the PDP context request message received by the serving general packet radio service support node SGSN carries an indication to inform the PGW or the GGSN to select a specific processing for the PDM context request message. The ability of the P-CSCF.

The method for emergency access of a user equipment according to claim 1, wherein the attach request message further carries a user identifier;

The user indication includes at least one of the following:

User ID is International Mobile Equipment Identity IMEI, International Mobile Subscriber Identity IMSI, Old World Unique Temporary Identity GUTI, Old Tracking Zone Identity TAI.

11. A core network side device, comprising:

a receiving unit, configured to receive an attach request message, where the attach request message carries emergency call attribute information, and according to the emergency call attribute information, identify that the call indicated by the attach request message is tight Urgent call

The core network side device 1 according to claim 11, further comprising:

The Qos configuration unit is configured to: after the receiving unit identifies that the call indicated by the attach request message is an emergency call, select the configured emergency call quality of service Qos information.

The core network side device 1 according to claim 12, further comprising:

The Qos sending unit is configured to add the emergency call quality of service Qos information selected by the Qos configuration unit to the emergency bearer request message.

The core network side device 1 according to claim 11, further comprising: an emergency bearer determining unit, configured to: after the receiving unit recognizes that the call indicated by the attach request message is an emergency call, select an emergency bearer to establish the way.

The core network side device 1 according to claim 11, wherein the selecting unit comprises:

a first selection unit, configured to obtain a core network side device 2 capable of emergency access by using a local emergency access point name Em-APN;

a second selection unit, configured to use a network pre-configured core network side device capable of emergency access

The core network side device 1 according to claim 11, further comprising: a user identifier adding unit, configured to add a user identifier in the establishing an emergency bearer request message sent by the sending unit.

A network system, comprising the core network side device 1 according to any one of claims 11 to 16.