CN104918322B

CN104918322B - Method for reporting user position information

Info

Publication number: CN104918322B
Application number: CN201410085933.5A
Authority: CN
Inventors: 许丽香; 王弘
Original assignee: Beijing Samsung Telecommunications Technology Research Co Ltd; Samsung Electronics Co Ltd
Current assignee: Beijing Samsung Telecommunications Technology Research Co Ltd; Samsung Electronics Co Ltd
Priority date: 2014-03-10
Filing date: 2014-03-10
Publication date: 2020-02-04
Anticipated expiration: 2034-03-10
Also published as: CN104918322A; CN111182624A

Abstract

The application discloses a method for reporting user position information, which comprises the following steps: the MME sends an access bearer releasing request message to the SGW; the SGW sends an access bearer release response message to the MME; the MME sends an S1UE context release command message to the eNB; the eNB sends an S1UE context release completion message to the MME, wherein the message comprises a global cell identity (ECGI) and a Tracking Area Identity (TAI) of a cell in which the UE is currently located; and the MME sends the user location information to the SGW for sending the ECGI and the TAI of the cell where the UE is located to the SGW. By the method and the device, when the UE context is released or the ERAB is released or the data session is ended, the operator can obtain the current UE position information from the access network and/or the core network, and the current UE position information can also be contained in the SGW and PGW charging data record CDR, so that the session can be subjected to performance analysis, user experience quality analysis and proper charging adjustment.

Description

Method for reporting user position information

Technical Field

The present invention relates to wireless communication technologies, and in particular, to a method for reporting user location information.

Background

Modern mobile communications are increasingly tending to provide users with high-rate transmission multimedia services, as shown in fig. 1, which is a system architecture diagram of System Architecture Evolution (SAE). Wherein:

a User Equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network that includes macro base stations (eNodeB/NodeB) that provide access to a radio network interface for UEs. A Mobility Management Entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE. Serving Gateway (SGW) 104 mainly provides the functions of the user plane, and MME103 and SGW104 may be in the same physical entity. A packet data network gateway (PGW) 105 is responsible for charging, lawful interception, etc., and may also be in the same physical entity as the SGW 104. A Policy and Charging Rules Function (PCRF) 106 provides quality of service (QoS) policy and charging criteria. The general packet radio service support node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides routing for the transmission of data. The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, the packet data context of the user equipment, etc.

The interface between eNB and MME is the S1 interface. The existing UE S1 release process is shown in fig. 2, and includes the steps of:

in step 201a, in some scenarios, the eNB may release the connection of the UE before requesting the MME to release the S1 context, for example, the eNB initiates the RRC connection release for CS Fallback redirection for circuit switched Fallback.

Step 201b, if the eNB detects that the signaling connection and radio bearer of the UE need to be released, the eNB sends S1UE a context release request message to the MME.

This step needs to be performed only during the eNB-initiated S1 release procedure. The start is step 202 if it is an MME initiated S1 release procedure.

Step 202, the MME sends an access bearer release request message to the SGW, requesting the SGW to release all S1 user plane bearers of the UE. This procedure may be triggered by an eNB-initiated S1UE context release request or an event with another MME.

Step 203, the SGW releases all eNB related information of the UE, including addresses and TEIDs. And the SGW sends an access bearer release response message to the MME.

In step 204, the MME sends S1UE a context release order message to the eNB.

In step 205, if the RRC connection is not released, the eNB sends an RRC connection release message to the UE. And after receiving the confirmation message of the UE, the eNB releases the UE context.

In step 206, the eNB sends S1UE context release complete message to the MME. The message contains the global cell identity ECGI and the tracking area identity TAI of the cell in which the UE is located. The UE signalling connection between MME and eNB is thus released.

The MME releases any eNB related information in the UE context stored in the MME, e.g., eNB address, eNB UE S1AP identity, but the MME stores MME context information for other UEs, e.g., S1 user plane configuration information for SGW. The non-GBR EPS bearer established for the UE is maintained in the MME and the SGW.

When the E-UTRAN radio access bearer is released or the data session is ended, the current location information of the user needs to be reported to the SGW and PGW charging data record CDR, so that the performance analysis, the user experience quality analysis, and the appropriate charging adjustment can be performed on the session. However, in the existing release process of S1, the existing technology cannot report the current location information of the UE to the SGW and the PGW, so that the operator cannot know the current location information of the user.

Disclosure of Invention

The invention provides a method for reporting user location information, which can report the current location information of UE to SGW and PGW in the releasing process of S1, so that the operator can know the current location information of the user, thereby performing performance analysis, user experience quality analysis and proper charging adjustment on the session.

A method for reporting user position information comprises the following steps:

the MME sends an access bearer releasing request message to the SGW;

the SGW sends an access bearer release response message to the MME;

the MME sends an S1UE context release command message to the eNB;

the eNB sends an S1UE context release complete message to the MME. The message comprises a global cell identity (ECGI) and a Tracking Area Identity (TAI) of a cell in which the UE is positioned;

and the MME sends the user location information to the SGW for sending the ECGI and the TAI of the cell where the UE is located to the SGW.

It should be noted that, if the SGW and the PGW are not in the same entity, the SGW may also send the received ECGI and TAI of the UE to the PGW.

A method for reporting user position information comprises the following steps:

the eNB sends an S1UE context release request message to the MME. The message comprises ECGI and TAI of the cell where the UE is located currently;

the MME sends an access bearer releasing request message to the SGW;

the SGW sends an access bearer release response message to the MME;

the MME sends an S1UE context release command message to the eNB;

the eNB sends an S1UE context release complete message to the MME.

It should be noted that, if the SGW and the PGW are not in the same entity, the SGW may also send the ECGI and TAI of the UE received from the MME to the PGW.

It should be noted that the bearer release request message sent by the MME to the SGW includes the ECGI and TAI of the cell in which the UE is currently located.

It can be seen from the above technical solutions that, by using the method for reporting user location information provided by the present invention, the current location information of the UE can be reported to the SGW and the PGW in the release process of S1, so that the operator can know the current location information of the user, and thus, the performance analysis, the user experience quality analysis, and the appropriate charging adjustment can be performed on the session.

Drawings

FIG. 1 is a diagram of a conventional SAE system architecture;

fig. 2 prior art S1 release process;

FIG. 3 is a diagram illustrating a first method for reporting user location information according to the present invention;

FIG. 4 is a diagram illustrating a second method for reporting user location information according to the present invention;

FIG. 5 is a diagram illustrating a third method for reporting user location information according to the present invention;

FIG. 6 is a flowchart illustrating an operation of the MME of the present invention.

Detailed Description

For the purpose of making the objects, technical means and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings.

Fig. 3 is a schematic diagram illustrating a method for reporting user location information according to the present invention. In the method, the MME obtains the current position information of the UE after the context release of S1UE is completed, and the MME further sends the user position information to the SGW. The SGW may further send to the PGW if the SGW and PGW are not in the same entity. The method comprises the following steps:

in some scenarios, the eNB may release the connection of the UE before requesting the MME to release the S1 context, for example, the eNB initiates RRC connection release for the CS Fallback redirection for circuit domain Fallback.

Step 301b, if the eNB detects that the signaling connection and radio bearer of the UE need to be released, the eNB sends S1UE a context release request message to the MME.

This step needs to be performed only during the eNB-initiated S1 release procedure. The start is step 302 if it is an MME initiated S1 release procedure.

At this time or before step 306, the MME receives the downlink data instruction from the SGW, and if the eNB does not know that there is downlink data, the eNB releases the context and radio/S1 resource of the UE. The MME sends downlink paging information to the eNB without sending paging information to all eNBs of the TA where the UE is located, so that air interfaces and S1, particularly paging resources of the air interfaces, are saved.

The eNB may transmit the paging message in all cells of the TA included in the paging message.

Further, the eNB receives the paging message from the MME at this time or before step 306, and the eNB may only send a page in the current cell where the UE is located, so as to further save paging resources on the air interface. If the paging response from the UE is not received within a certain time, the eNB transmits the paging message in all cells of the TA included in the paging message.

Step 302, the MME sends an access bearer release request message to the SGW requesting the SGW to release all S1 user plane bearers of the UE. This procedure may be triggered by an eNB-initiated S1UE context release request or an event with another MME.

Step 303, the SGW releases all eNB related information of the UE, including addresses and TEIDs. And the SGW sends an access bearer release response message to the MME.

The SGW may inform the MME by the release access bearer response how long there has been no data transmission on the bearer. The MME decides whether to trigger the S1UE context release procedure of step 304 according to this information. The MME may also perform system and network optimization based on this information, for example, if the eNB does not receive the S1UE context release request from the eNB at this time, the eNB informs the O & M of this information (how long the eNB has not transmitted data and initiated S1UE context release), so that the MME may set an eNB-side UE inactivity (inactivity) timer.

In step 304, the MME sends S1UE a context release order message to the eNB.

In step 305, if the RRC connection is not released, the eNB sends an RRC connection release message to the UE. And after receiving the confirmation message of the UE, the eNB releases the UE context.

In step 306, the eNB sends S1UE context release complete message to the MME. The message contains the global cell identity ECGI and the tracking area identity TAI of the cell in which the UE is located. The signaling connection of the UE between MME and eNB is thus released.

Step 307, the MME sends the user location information report to the SGW. The user location information report may be a new message or procedure or an existing message for sending the ECGI and TAI of the cell in which the UE is currently located to the SGW. The MME receives the ECGI and TAI of the cell in which the UE is located, which are transmitted from the eNB, in step 306. The SGW may also send the received ECGI and TAI of the UE to the PGW if the SGW and PGW are not in one entity. The SGW sends the received ECGI and TAI to the PGW, which may be a newly defined message or procedure or an existing message.

The SGW and/or PGW stores the received location information ECGI and TAI of the UE. The SGW and/or PGW perform performance analysis, user quality of experience analysis, and appropriate charging adjustments for the session. The SGW and/or PGW may also report the location information ECGI and TAI of the UE to the O & M for performance analysis, user quality of experience analysis, and appropriate charging adjustments for the session.

The current location information of the UE may be used for performance analysis, quality of experience analysis of the user, and appropriate charging adjustments for the session. This does not exclude that the location information of the UE may also be used for other purposes.

By the method, when the UE context is released or the ERAB is released or the data session is ended, the operator can obtain the current UE position information from the access network and/or the core network, and the current UE position information can also be contained in the SGW and PGW charging data record CDR, so that the session can be subjected to performance analysis, user experience quality analysis and proper charging adjustment.

Fig. 4 is a schematic diagram of a second method for reporting user location information according to the present invention. In the method, the MME obtains the current position information of the UE from the context release request of S1UE, and the MME sends the current position information of the user to the SGW through the release access bearing request message. If the SGW and the PGW are not in the same entity, the SGW may further send the user location information to the PGW. The method comprises the following steps:

in some scenarios, the eNB may release the connection of the UE before requesting the MME to release the S1 context, for example, the eNB initiates RRC connection release for CS Fallback redirection.

Step 401b, if the eNB detects that the signaling connection and radio bearer of the UE need to be released, the eNB sends S1UE a context release request message to the MME. The message contains the ECGI and TAI of the cell in which the UE is currently located.

The MME stores the received UE location information ECGI and TAI. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent procedure, for example, in a procedure of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (sessiondrop). As another method of the present invention, the MME may also send the current location information of the UE to the SGW in step 402. The SGW sends it to the PGW.

This step needs to be performed only during the eNB-initiated S1 release procedure. The S1 release procedure starts from step 402 if it is MME initiated.

At this time or before step 406, the MME receives the downlink data instruction from the SGW, and if the eNB does not know that there is downlink data, the eNB releases the context and radio/S1 resources of the UE. The MME sends downlink paging information to the eNB without sending paging information to all eNBs of the TA where the UE is located, so that air interfaces and S1, particularly paging resources of the air interfaces, are saved.

Further, the eNB receives the paging message from the MME at this time or before step 406, and the eNB may send the paging only in the current cell where the UE is located, so as to further save the paging resources on the air interface. If the paging response from the UE is not received within a certain time, the eNB transmits the paging message in all cells of the TA included in the paging message.

Step 402, the MME sends an access bearer release request message to the SGW requesting the SGW to release all S1 user plane bearers of the UE. This procedure may be triggered by an eNB-initiated S1UE context release request or an event with another MME. The message contains the ECGI and TAI of the cell in which the UE is currently located. The MME may also receive the ECGI and TAI of the cell where the UE is currently located from the eNB in step 401b, and send the information to the SGW in the request for releasing the access bearer.

The SGW may also send the received ECGI and TAI of the UE to the PGW if the SGW and PGW are not in one entity. The SGW sending the received ECGI and TAI to the PGW may be a release access bearer request message or a newly defined message or procedure or other existing message.

In step 403, the SGW sends a release access bearer response message to the MME.

The SGW may inform the MME by the release access bearer response how long there has been no data transmission on the bearer. The MME decides whether to trigger the S1UE context release procedure of step 404 based on this information. The MME may also perform system and network optimization based on this information, for example, if the eNB does not receive the S1UE context release request from the eNB at this time, the eNB informs the O & M of this information (how long the eNB has not transmitted data and initiated S1UE context release), so that the MME may set an eNB-side UE inactivity (inactivity) timer.

In step 404, the MME sends S1UE context release command message to the eNB.

In step 405, if the RRC connection is not released, the eNB sends an RRC connection release message to the UE. And after receiving the confirmation message of the UE, the eNB releases the UE context.

In step 406, the eNB sends S1UE context release complete message to the MME. The message contains the global cell identity ECGI and the tracking area identity TAI of the cell in which the UE is located. The signaling connection of the UE between MME and eNB is thus released. The MME stores the received UE location information ECGI and TAI. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent process, for example, in a process of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (session drop).

By the method, when the UE context is released or the ERAB is released or the data session is ended, the operator can obtain the current UE position information from the access network and/or the core network, and the current UE position information can also be contained in the SGW and PGW charging data record CDR, so that the session can be subjected to performance analysis, user experience quality analysis and proper charging adjustment. In a context release scene of UE, the method reports the current ECGI and TAI of the UE to MME and SGW/PGW by using the existing process. The method is particularly suitable for the case of S1UE context release initiated by eNB.

Fig. 5 is a third schematic diagram of a user location information reporting method according to the present invention. In the method, the MME obtains the current position information of the UE from the S1UE context release request and the S1UE context release completion, and the MME sends the user position information to the SGW through the access bearer release request and/or other processes. The SGW may further send to the PGW if the SGW and PGW are not in the same entity. The method comprises the following steps:

Step 501b, if the eNB detects that the signaling connection and radio bearer of the UE need to be released, the eNB sends S1UE a context release request message to the MME. The message contains the ECGI and TAI of the cell in which the UE is currently located. The MME stores the received ECGI and TAI of the UE. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent process, for example, in a process of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (session drop). As another method of the present invention, the MME may also send current location information of the UE to the SGW in step 502. The SGW sends it to the PGW.

This step needs to be performed only during the eNB-initiated S1 release procedure. The S1 release procedure starts from step 502 if it is MME initiated.

At this time or before step 506, the MME receives the downlink data indication from the SGW, and the eNB releases the context and/or radio resources of the UE if it is not clear that there is downlink data. The MME sends downlink paging information to the eNB without sending paging information to all eNBs of the TA where the UE is located, so that air interfaces and S1, particularly paging resources of the air interfaces, are saved.

Further, the eNB receives the paging message from the MME at this time or before step 506, and the eNB may send the paging only in the current cell where the UE is located, so as to further save the paging resources on the air interface. If the paging response from the UE is not received within a certain time, the eNB transmits the paging message in all cells of the TA included in the paging message.

Step 502, the MME sends an access bearer release request message to the SGW requesting the SGW to release all S1 user plane bearers of the UE. This procedure may be triggered by an eNB-initiated S1UE context release request or an event with another MME. The message contains the ECGI and TAI of the cell in which the UE is currently located. The MME may also receive the ECGI and TAI of the cell where the UE is currently located from the eNB in step 501b before sending the information to the SGW in the request for releasing the access bearer.

In step 503, the SGW sends a release access bearer response message to the MME. The SGW may inform the MME by the release access bearer response how long there has been no data transmission on the bearer. The MME decides whether to trigger the S1UE context release procedure of step 304 according to this information. The MME may also perform system and network optimization based on this information, for example, if the eNB does not receive the S1UE context release request from the eNB at this time, the eNB informs the O & M of this information (how long the eNB has not transmitted data and initiated S1UE context release), so that the MME may set an eNB-side UE inactivity (inactivity) timer.

In step 504, the MME sends S1UE context release command message to the eNB.

In step 505, if the RRC connection is not released, the eNB sends an RRC connection release message to the UE. And after receiving the confirmation message of the UE, the eNB releases the UE context.

In step 506, the eNB sends S1UE context release complete message to the MME. The message contains the global cell identity ECGI and the tracking area identity TAI of the cell in which the UE is located. The signaling connection of the UE between MME and eNB is thus released. The MME stores the received UE location information ECGI and TAI. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent process, for example, in a process of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (session drop). As another method of the present invention, the MME may send the current location information of the UE to the SGW in step 507. The SGW sends it to the PGW.

In step 507, the MME sends the user location information report to the SGW. The user location information report may be a new message or procedure or an existing message for sending the ECGI and TAI of the cell in which the UE is currently located to the SGW. The MME receives the ECGI and TAI of the cell in which the UE is located, which are transmitted from the eNB in step 506. The SGW may also send the received ECGI and TAI of the UE to the PGW if the SGW and PGW are not in one entity. The SGW sends the received ECGI and TAI to the PGW, which may be a newly defined message or procedure or an existing message. The step of sending the user location information to the SGW by using this step is not a necessary step of the present invention, and the MME may send the user location information to the SGW by using other existing processes, such as detach triggered by MME, detach triggered by HSS, or phone.

The MME may perform this step only when the ECGI or TAI received in step 506 is different from that in step 501b, or perform this step when the ECGI and TAI of the cell in which the UE is currently located are not included in the message in step 502.

FIG. 6 is a flowchart illustrating the operation of the MME of the present invention.

Step 601, the MME receives a message.

In step 602, if the S1UE context release request message is received from the eNB, step 603 is performed. It should be noted that step 603 may also be initiated by the MME.

If the MME receives the downlink data indication from the SGW, the eNB releases the context and/or radio resources of the UE without knowing the downlink data. The MME sends downlink paging information to the eNB without sending paging information to all eNBs of the TA where the UE is located, so that air interfaces and S1, particularly paging resources of the air interfaces, are saved.

Further, the eNB receives the paging message from the MME at this time, and the eNB may send a page only in the current cell where the UE is located, thereby further saving paging resources of an air interface. If the paging response from the UE is not received within a certain time, the eNB transmits the paging message in all cells of the TA included in the paging message.

If the S1UE context release request message contains the current location information ECGI and TAI,. The MME stores the received UE location information ECGI and TAI. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent process, for example, in a process of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (session drop). As another method of the present invention, the MME may send the current location information of the UE to the SGW in step 603. The SGW sends it to the PGW.

Step 603, the MME sends a release access bearer request message to the SGW. If the MME receives the current location information ECGI and TAI of the UE from the eNB in step 602, the MME sends this information to the SGW. The SGW and/or PGW perform performance analysis, user quality of experience analysis, and appropriate charging adjustments for the session. The SGW and/or PGW may also report the location information ECGI and TAI of the UE to the O & M for performance analysis, user quality of experience analysis, and appropriate charging adjustments for the session.

In step 604, if the MME receives the response from the SGW to release the access bearer, step 605 is performed.

In step 605, the MME decides to send S1UE context release command message to the eNB. If the MME receives information on how long the UE has no data at step 604, the MME uses this information to decide whether to send S1UE context release order message to the UE. The MME may also perform system and network optimization based on this information, for example, if the eNB does not receive the S1UE context release request from the eNB at this time, the eNB informs the O & M of this information (how long the eNB has not transmitted data and initiated S1UE context release), so that the MME may set an eNB-side UE inactivity (inactivity) timer.

In step 606, the MME receives the S1UE context release completion from the eNB, and executes step 607.

If the S1UE context release complete message contains the current location information ECGI and TAI of the UE. The MME stores the received UE location information ECGI and TAI. The MME reports the location information of the UE to the SGW and/or PGW in a subsequent process, for example, in a process of MME initiated Detach (Detach), or HSS initiated Detach, or call drop (session drop). As another method of the present invention, the MME may transmit the current location information of the UE to the SGW in step 607. The SGW sends it to the PGW. Step 607, the MME sends the UE location information report to the SGW. The user location information report may be a new message or procedure or an existing message for sending the ECGI and TAI of the cell in which the UE is currently located to the SGW. The MME receives the ECGI and TAI of the cell in which the UE is located, which are transmitted from the eNB in step 506. The SGW may also send the received ECGI and TAI of the UE to the PGW if the SGW and PGW are not in one entity. The SGW sends the received ECGI and TAI to the PGW, which may be a newly defined message or procedure or an existing message. The step of sending the user location information to the SGW by using this step is not a necessary step of the present invention, and the MME may send the user location information to the SGW by using other existing processes, such as detach triggered by MME, detach triggered by HSS, or phone.

By the method, when the UE context is released or the ERAB is released or the data session is ended, the operator can obtain the current UE position information from the access network and/or the core network, and the current UE position information can also be contained in the SGW and PGW charging data record CDR, so that the session can be subjected to performance analysis, user experience quality analysis and proper charging adjustment. In a context release scene of the UE, the MME can select which step to report the current ECGI and TAI of the UE to the MME and the SGW/PGW, so that the flexibility is increased.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A method for reporting user location information, the method comprising:

the mobile management entity sends a request message for releasing access bearing to a Service Gateway (SGW);

the mobile management entity receives a response message of releasing the access bearer sent by the SGW; sending S1UE context release command message to the base station;

the method comprises the steps that a mobile management entity receives an S1UE context release completion message sent by a base station, wherein the UE context release completion message comprises a global cell identity (ECGI) and a Tracking Area Identity (TAI) of a cell where the UE is located;

and the mobile management entity sends the user position information to the SGW for sending the ECGI and the TAI of the cell in which the UE is currently located to the SGW.

2. The method of claim 1, wherein the SGW is further configured to send the received ECGI and TAI of the UE to the packet data network gateway, PGW, if the SGW and PGW are not in the same entity.

3. A method for reporting user location information, the method comprising:

the mobility management entity receives an S1UE context release request message sent by a base station, wherein the UE context release request message contains ECGI and TAI of a cell where the UE is currently located;

and the mobile management entity sends an access bearer release request message to the SGW, wherein the access bearer release request message contains the ECGI and the TAI of the cell where the UE is currently located, and is used for sending the ECGI and the TAI of the cell where the UE is currently located to the SGW.

4. The method of claim 3, further comprising,

receiving an access bearer release response message sent by an SGW;

the mobility management entity sends S1a UE context release command message to the base station;

the mobility management entity receives S1UE context release complete message sent by the base station.

5. The method of claim 3, wherein the SGW sends the ECGI and TAI of the UE received from the mobility management entity to the PGW if the SGW and PGW are not in one entity.

6. A method for reporting user location information, the method comprising:

the mobile management entity sends an access bearer release request message to the SGW, wherein the access bearer release request message contains the ECGI and the TAI of the cell where the UE is currently located and is used for sending the ECGI and the TAI of the cell where the UE is currently located to the SGW;

the mobility management entity receives a release access bearer response message sent by the SGW,

sending S1UE context release command message to the base station;

the mobile management entity receives an S1UE context release completion message sent by the base station, wherein the UE context release completion message comprises a global cell identity (ECGI) and a Tracking Area Identity (TAI) of a cell in which the UE is located;

7. The method of claim 6, wherein the SGW further sends the ECGI and TAI of the UE received from the mobility management entity to the PGW if the SGW and the PGW are not in one entity.

8. A mobility management entity apparatus for reporting user location information, the apparatus comprising:

a module for sending a request message for releasing access bearer to a Serving Gateway (SGW);

a module for receiving an access bearer release response message sent by the SGW;

a module for sending S1UE context release command message to the base station;

a module for receiving a S1UE context release complete message sent by a base station, where the UE context release complete message includes a global cell identity ECGI and a tracking area identity TAI of a cell in which the UE is located;

and the module for sending the user location information to the SGW is used for sending the ECGI and the TAI of the cell where the UE is located to the SGW.

9. The apparatus of claim 8, wherein the SGW is further configured to send the received ECGI and TAI of the UE to the packet data network gateway, PGW, if the SGW and PGW are not in the same entity.

10. A mobility management entity apparatus for reporting user location information, the apparatus comprising:

a module for receiving an S1UE context release request message sent by a base station, where the UE context release request message includes an ECGI and a TAI of a cell in which the UE is currently located;

and a module for sending an access bearer release request message to the SGW, where the access bearer release request message includes the ECGI and TAI of the cell where the UE is currently located, and is used to send the ECGI and TAI of the cell where the UE is currently located to the SGW.

11. The apparatus of claim 10, further comprising,

a module for sending S1UE context release command message to the base station;

and a module for receiving the UE context release complete message sent by the base station S1.

12. The apparatus of claim 10, wherein the SGW sends the ECGI and TAI of the UE received from the mobility management entity to the PGW if the SGW and the PGW are not in one entity.

13. A mobility management entity apparatus for reporting user location information, the apparatus comprising:

a module for sending an access bearer release request message to the SGW, where the access bearer release request message includes the ECGI and TAI of the cell where the UE is currently located, and is used to send the ECGI and TAI of the cell where the UE is currently located to the SGW;

a module for receiving the release access bearer response message sent by the SGW,

a module for sending S1UE context release command message to the base station;

a module for receiving a S1UE context release complete message sent by the base station, where the UE context release complete message includes a global cell identity ECGI and a tracking area identity TAI of a cell in which the UE is located;

14. The apparatus of claim 13, wherein the SGW is further configured to send the ECGI and TAI of the UE received from the mobility management entity to the PGW if the SGW and the PGW are not in the same entity.