CN103582163B

CN103582163B - Bearing processing method, resource release method, apparatus and system

Info

Publication number: CN103582163B
Application number: CN201210271408.3A
Authority: CN
Inventors: 王静; 朱进国
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2012-08-01
Filing date: 2012-08-01
Publication date: 2018-10-23
Anticipated expiration: 2032-08-01
Also published as: CN103582163A; WO2014019515A1

Abstract

The invention discloses a kind of bearing processing method, resource release method, apparatus and systems, wherein the bearing processing method includes：First MME receives the request message from PGW, which is used to indicate the MME and establishes or change the carrying for local intercommunication, wherein the first MME is the service MME of the first user in corresponding two users of local intercommunication；First MME obtains the Tunnel Identifier that the second base station corresponding to the second user in corresponding two users of local intercommunication is carrying distribution；First MME binds the first base station corresponding to the first user and the communicating data carrying of the second base station according to the Tunnel Identifier.Through the invention, solve the problems, such as how to establish the often carrying path between the network element of intercommunicated wireless side in the related technology, the mode for establishing carrying is simple and practicable, efficient.

Description

Bearer processing method, bearer release method, device and system

Technical Field

The present invention relates to the field of communications, and in particular, to a bearer processing method, a bearer releasing method, an apparatus, and a system.

Background

In order to maintain the competitiveness of the third Generation mobile communication System in the communication field, provide a mobile communication service with faster rate, lower delay and more personalization for users, and at the same time, reduce the operation cost of operators, the standard working group of the third Generation Partnership Project (3 rd Generation Partnership Project, abbreviated as 3 GPP) is working on the research of the Evolved Packet System (EPS). Fig. 1 is a schematic structural diagram of an evolved packet domain system according to the related art, and as shown in fig. 1, the whole EPS system is divided into two parts, namely a radio access network and a core network. In the core Network, a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), a Policy and Charging Rule Function (PCRF), a Serving Gateway (S-GW), a Packet Data Gateway (PDN Gateway, P-GW), and a Packet Data Network (PDN for short, PDN). The functions of each part are described in detail below:

the home subscriber server is a permanent storage place of the user subscription data and is positioned in a home network subscribed by the user.

The mobility management entity is a storage place of the user subscription data in the current network and is responsible for non-access stratum signaling management from the terminal to the network, the security verification function of the terminal, the mobility management of the terminal, the tracking and paging management function and the bearing management in the idle mode of the user.

The serving GPRS support node is a service support point for a Global System for Mobile communications (GSM) Enhanced Data Rate for GSM evolution (EDGE) Radio Access Network (GERAN for short) and a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UMTS Terrestrial Radio Access Network, UTRAN for short) user to Access a core Network, and is similar to a mobility management entity in function and responsible for functions such as location update, paging management, bearer management, and the like of the user.

The service gateway is a gateway from a core network to a wireless system and is responsible for user plane bearing from a terminal to the core network, data caching in a terminal idle mode, a function of initiating a service request at a network side, legal monitoring and a function of routing and forwarding packet data; the service gateway is responsible for counting the condition of the user terminal using the wireless network, generating a bill of the terminal using the wireless network and transmitting the bill to the charging gateway.

The packet data gateway is a gateway of an evolution system and an external packet data network of the system, is connected to the Internet and the packet data network, and is responsible for functions of Internet Protocol (IP) address allocation, charging function, packet filtering, policy control and the like of a terminal.

The packet data network is an IP service network of an operator, and provides IP services for users through a core network of the operator.

The policy charging rule function entity is a server in the evolved system that is responsible for providing rules in charging control, online credit control, threshold control, and Quality of Service (QoS) policies.

The Radio access Network is composed of an Evolved node b (eNB) and a 3G Radio Network Controller (RNC), and is mainly responsible for receiving and transmitting Radio signals, and manages Radio resources, resource scheduling, and access control of an air interface by contacting the air interface with a terminal.

The serving GPRS support node is an upgraded SGSN, can support an S4 interface with a serving gateway, and performs interworking with a mobility management unit by using a GPRS Tunneling Protocol version 2 (referred to as GTPv 2). Whereas for SGSNs supporting 3G core networks the Packet Switching (PS) domain network architecture differs from that of fig. 1. At this time, the SGSN and the MME are connected by a Gn interface, and communicate by using a GPRS Tunneling Protocol version1 (GPRS Tunneling Protocol version1, abbreviated as GTPv 1). The SGSN, which cannot be connected to the serving Gateway, is connected to a Gateway GPRS Support Node (GGSN for short) through a Gn interface to directly perform packet data network access.

When a user accesses a service, a terminal initiates a PDN (Packet Data Network) connection establishment process, and an MME/SGSN selects a core Network service gateway and an anchor gateway according to an APN corresponding to the service used by the user reported by the terminal, and establishes a user plane channel between the terminal, a wireless base station and the core Network gateway (the service gateway and the anchor gateway). The user accesses the services of the external/internal network through the anchor gateway, and the services are not interrupted when the user moves in the service area of the anchor gateway. Fig. 2 is a diagram of a user plane path for a user terminal to receive/transmit data according to the related art. Wherein, path 1 represents that the user accesses the external Internet network, and path 2 represents that the user communicates with the user belonging to the service area of the anchor gateway.

As can be seen from fig. 2, the data received/transmitted by the ue is forwarded through the core network anchor gateway, even though two communicating ues may be located in the same/adjacent wireless side network element. At present, the data transmission mode is not optimized, and data are forwarded through the core network anchor point, so that the data transmission path is long, the time delay of user data transmission is increased, and the resource utilization rate of the core network is reduced. Especially after the popularization and development of terminal-to-terminal services (such as P2P, games, IMS voice or video services, etc.), the bottleneck in data routing is more prominent.

The concept of local interworking is therefore proposed in the standard domain, as shown in fig. 3. For users who access services mutually under the same wireless side network element (such as a macro base station, a home base station and the like) or adjacent wireless side network elements, a route optimization channel of the wireless side is established, so that the intercommunicated data can be directly/indirectly forwarded through the wireless side network elements. The route optimized channel for communicating the interworking data may be a routing channel for IP in IP or a point-to-point dedicated tunnel such as GTP or GRE. Fig. 3a is a schematic diagram of implementation of local interworking in a scenario where users are located in the same wireless side network element in the related art, as shown in fig. 3a, at this time, the wireless side network element directly forwards data intercommunicated between users locally, without passing through an upper layer core network element, so as to reduce resource occupation of the core network. Fig. 3b is a schematic diagram of implementation of local interworking in a scenario where a user is located in an adjacent wireless side network element in the related art, where, as shown in fig. 3b, the adjacent wireless side network elements refer to geographically close locations and are determined by planning of an operator. The intercommunication data is forwarded through a route optimization channel between adjacent wireless side network elements, and the channel can be per-device or per-bearer. The data may be based on IP routing or may be based on tunnel routing.

In order to realize local routing, a route optimization channel local to a base station or between base stations needs to be established. In the related technology, the anchor point of the data route judges the local intercommunication starting and indicates the establishment of the route optimization channel. Fig. 4 is a schematic diagram of a local interworking implementation process according to a related art, which takes a scenario in which a user is attached to an adjacent wireless side network element as an example, as shown in fig. 4, the local interworking implementation process in the related art includes the following steps:

step S402, the data of the two terminals which are communicated with each other are forwarded through the anchor point gateway.

Step S404, the anchor point gateway judges whether to execute local intercommunication according to the user subscription, the user position relation, the service type, the local strategy and the like.

Step S406, the anchor point gateway sends a signaling for starting local intercommunication to the control plane network element, and the message is forwarded to the wireless side network element through the control plane network element. The message includes the interworking peer wireless side network element information, the interworking data routing policy, and information such as a Transport Flow Template (TFT) for carrying the encapsulation.

Step S408, the wireless side network element establishes an optimized routing channel between the wireless side network elements according to the opposite end information, where the channel may be an IP routing channel, or a dedicated tunnel such as GTP, GRE, PMIP, or the like. Either on a per device basis or on a per bearer basis.

Step S410, after the route optimization channel is established, the interworking data can be forwarded between the wireless side network elements. And the wireless side network element transmits data used for intercommunication in the uplink data through an optimized path by adopting a data routing strategy, and the opposite wireless side network element uses TFT information for radio bearer matching.

However, how to establish per-bearer paths between interworking radio-side network elements is not disclosed in the related art at present.

Aiming at the problem of how to establish each bearing path between the network elements at the intercommunicating wireless sides in the related technology, no effective solution is provided at present.

Disclosure of Invention

The invention provides a bearer processing method, a bearer release method, a device and a system, aiming at the problem of how to establish each bearer path between network elements at intercommunicating wireless sides in the related art, so as to at least solve the problem.

According to an aspect of the present invention, there is provided a bearer processing method, including: a first MME receives a request message from a PGW, wherein the request message is used for instructing the MME to establish or modify a bearer for local interworking, and the first MME is a serving MME of a first user of two users corresponding to the local interworking; the first MME acquires a tunnel identifier distributed for the bearer by a second base station corresponding to a second user of the two users corresponding to the local intercommunication; and the first MME binds the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier.

Preferably, before the first MME receives the request message from the PGW, the method further includes: the PCRF confirms that the bearer needs to be established or modified according to the policy; and the PCRF informs the PGW to initiate the establishment or modification process of the bearer.

Preferably, the notifying, by the PCRF, the PGW of initiating the bearer establishment or modification procedure includes: and the PCRF informs the PGW to initiate the establishment or modification process of the bearer through an IP-CAN session.

Preferably, before the PCRF confirms the need to establish or modify the bearer for local interworking according to the policy, the method further includes: the PCRF receives a bearer resource modification request from a user; or, the PCRF receives a resource reservation indication from an application layer network element.

Preferably, the binding, by the first MME according to the tunnel identifier, the interworking data bearer between the first base station corresponding to the first user and the second base station includes: and the first MME sets the gateway tunnel identifier in the first base station to the tunnel identifier allocated by the second base station for the bearer through an RAB modification process.

Preferably, after the first MME obtains the tunnel identifier allocated to the bearer by the second base station corresponding to the second user of the two users corresponding to the local interworking, the method further includes: the first MME judges whether the bearer needs to be established or modified; if the judgment result is yes, the first MME binds the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier; and if the judgment result is negative, the first MME deletes the acquired tunnel identifier allocated to the bearer by the second base station.

Preferably, after the first MME binding, according to the tunnel identifier, an interworking data bearer between the first base station corresponding to the first user and the second base station, the method further includes: the first MME confirming that the bearer needs to be released; and the first MME informs a second MME of setting a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, wherein the second MME is a serving MME of a second user of the two corresponding users which are locally communicated.

Preferably, the notifying, by the first MME, the second MME of the tunnel identifier in the second base station being set to the tunnel identifier of the corresponding core network gateway includes: the first MME sends a bearer update request to the PGW, the PGW sends an invalidation notification to the second MME, and the invalidation notification is used for indicating the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway; or, the first MME sends a release binding request message to the second MME, where the release binding request message is used to notify the second MME to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway.

According to another aspect of the present invention, there is provided a bearer release method, including: a first MME confirms that a bearer for local interworking needs to be released, wherein the first MME is a serving MME of a first user in two users corresponding to the local interworking; and the first MME informs a second MME of setting a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, wherein the second MME is a service MME of a second user of the two corresponding users which are locally communicated, and the second base station is a service base station of the second user.

Preferably, the notifying, by the first MME, the second MME of the tunnel identifier in the second base station being set to the tunnel identifier of the corresponding core network gateway includes: the first MME sends a bearer update request to a PGW, and the PGW sends an invalidation notification to the second MME, wherein the invalidation notification is used for indicating the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway; or, the first MME sends a release binding request message to the second MME, where the release binding request message is used to notify the second MME to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway.

According to another aspect of the present invention, there is also provided a bearer processing apparatus, located in a first MME, including: a first receiving module, configured to receive a request message from a PGW, where the request message is used to instruct the first MME to establish or modify a bearer for local interworking, where the first MME is a serving MME of a first user of two users corresponding to the local interworking; an obtaining module, configured to obtain a tunnel identifier allocated to the bearer by a second base station corresponding to a second user of the two users corresponding to the local interworking; and the binding module is used for binding the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier.

Preferably, the binding module includes: a setting unit, configured to set, through an RAB modification process, a gateway tunnel identifier in the first base station to the tunnel identifier allocated by the second base station for the bearer.

Preferably, the apparatus further comprises: the judging module is used for judging whether the bearer needs to be established or modified; if the judgment result of the judgment module is yes, the binding module is further configured to bind, according to the tunnel identifier, an interworking data bearer between the first base station and the second base station, where the first base station corresponds to the first user; and in the case that the judgment result of the judging module is negative, the first MME further includes a deleting module configured to delete the acquired tunnel identifier allocated to the bearer by the second base station.

Preferably, the apparatus further comprises: a first confirmation module, configured to confirm that the bearer needs to be released; a first notifying module, configured to notify a second MME to set a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated.

According to another aspect of the present invention, a bearer processing system is provided, which includes the bearer processing apparatus located in the first MME, and further includes a PCRF and a PGW.

Preferably, the PCRF includes: the second confirmation module is used for confirming that the bearer needs to be established or modified according to the strategy; a second notifying module, configured to notify the PGW to initiate the bearer establishment or modification process.

Preferably, the PCRF further includes: a second receiving module, configured to receive a bearer resource modification request from a user; or for receiving a resource reservation indication from an application layer network element.

Preferably, the first notification module further comprises: a first sending module, configured to send a bearer update request to the PGW, where in this case, the PGW includes: a second sending module, configured to send an invalidation notification to the second MME, where the invalidation notification is used to instruct the second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway; or, the first sending module is configured to send a binding release request message to the second MME, where the binding release request message is used to notify the second MME that the tunnel identifier in the second base station is set as the tunnel identifier of the corresponding core network gateway.

According to another aspect of the present invention, there is provided a bearer release apparatus, located in a first MME, including: a third confirming module, configured to confirm that a bearer for local interworking needs to be released, where the first MME is a serving MME of a first user of the two users corresponding to the local interworking; a third notifying module, configured to notify a second MME to set a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated and correspond to each other, and the second base station is a serving base station of the second user.

Preferably, the third notification module comprises: a third sending module, configured to send a bearer update request to a PGW, where the bearer update request is used for the PGW to send an invalidation notification to the second MME, and the invalidation notification is used to instruct the second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway; or, the third sending module is configured to send a binding release request message to the second MME, where the binding release request message is used to notify the second MME that the tunnel identifier in the second base station is set as the tunnel identifier of the corresponding core network gateway.

According to the invention, a first MME is adopted to receive a request message from a PGW, wherein the request message is used for indicating the MME to establish or modify a load for local intercommunication, and the first MME is a service MME of a first user in two users corresponding to the local intercommunication; the first MME acquires a tunnel identifier distributed for the bearer by a second base station corresponding to a second user in two users corresponding to local intercommunication; the first MME binds the way of the interworking data bearer between the first base station and the second base station corresponding to the first user according to the tunnel identifier, solves the problem of how to establish each bearer path between the interworking wireless side network elements in the related technology, and has simple and easy way of establishing the bearer and high efficiency.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a schematic diagram of a structure of an evolved packet domain system according to the related art;

fig. 2 is a schematic diagram of a user plane path for a user terminal to receive/transmit data according to the related art;

FIG. 3a is a diagram illustrating a local interworking implementation in a scenario where users are located in the same wireless side network element according to the related art;

FIG. 3b is a diagram illustrating a local interworking implementation in a scenario where users are located in neighboring wireless side network elements according to the related art;

fig. 4 is a schematic diagram of a process for implementing local interworking according to a related art, which takes a scenario in which a user is attached to an adjacent wireless-side network element as an example;

fig. 5 is a flowchart of a bearer processing method according to an embodiment of the present invention;

fig. 6 is a block diagram of a bearer processing apparatus according to an embodiment of the present invention;

fig. 7 is a block diagram of a bearer processing system according to an embodiment of the present invention;

fig. 8 is a flowchart of a bearer release method according to an embodiment of the present invention;

FIG. 9 is a block diagram of a bearer release apparatus according to an embodiment of the present invention;

fig. 10 is a flowchart of a first implementation manner of specific bearer establishment according to a first embodiment of the present invention;

fig. 11 is a flowchart of a second implementation manner of specific bearer establishment according to the second embodiment of the present invention;

fig. 12 is a first flowchart of an implementation manner of local interworking by bearer binding according to a third embodiment of the present invention;

fig. 13 is a flowchart of a second implementation manner for implementing local interworking by bearer binding according to a fourth embodiment of the present invention;

fig. 14 is a flowchart of a fifth implementation manner of releasing the local interworking channel according to the first embodiment of the present invention;

fig. 15 is a flowchart of a second implementation manner of releasing the local interworking channel according to a sixth embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

In this embodiment, a bearer processing method is provided, and fig. 5 is a flowchart of a bearer processing method according to an embodiment of the present invention, as shown in fig. 5, the method includes the following steps:

step S502, a first MME receives a request message from a PGW, where the request message is used to instruct the MME to establish or modify a bearer for local interworking, where the first MME is a serving MME (referred to as a first MME herein) of a first user of two users corresponding to local interworking;

step S504, the first MME acquires a tunnel identifier distributed for the bearer by a second base station corresponding to a second user of the two users corresponding to local intercommunication;

step S506, the first MME binds, according to the tunnel identifier, an interworking data bearer between the first base station and the second base station corresponding to the first user.

In this embodiment, through the above steps, when it is determined that the bearer for local interworking needs to be established or modified, the first MME first obtains a tunnel identifier allocated to the bearer by the second base station corresponding to the second user of the local interworking opposite end, and then binds the interworking data bearer between the first base station corresponding to the first user of the local end and the second base station of the opposite end according to the tunnel identifier, so that data between the first user and the second user can be transmitted through the interworking bearer, thereby implementing establishment of the bearer based on local interworking, solving a problem how to establish each bearer path between interworking wireless side network elements in the related art, and having a simple and easy way of establishing the bearer, and high efficiency.

It should be noted that "first" and "second" are used herein for convenience of description only, and are not intended to limit the order or other specific meanings. As a preferred embodiment, the procedure of bearer establishment or modification may be initiated by the PCRF. For example, when the PCRF determines according to the policy that a bearer for local interworking needs to be established or modified, the PCRF may notify the PGW to initiate a bearer establishment or modification procedure.

Preferably, the PCRF may notify the PGW to initiate a bearer establishment or modification procedure by initiating an IP-CAN session with the PGW. The mode is convenient and direct, and the operability is strong.

As a preferred embodiment, the PCRF may determine that the bearer for local interworking needs to be established or modified according to a request of a user or a judgment of a network side. For example, when the user finds that the established bearer resource cannot meet the service requirement, the user may initiate a request for modifying the bearer resource, and in this case, when the PCRF receives the bearer resource modification request from the user, it may confirm that the bearer for local interworking needs to be established or modified. For another example, when a network element (e.g., an Application Function (AF) or an X-Call State Control Function (CSCF)) in an Application layer finds that local interworking needs to be performed according to an applied service, the AF/X-CSCF may notify the PCRF that a specific bearer resource dedicated for interworking between two users needs to be established.

After the PCRF notifies the PGW to initiate a bearer establishment or modification procedure, the PGW may initiate a request (or indication) message to create/modify a bearer to a serving MME (herein, simply referred to as first MME) of a first user of the two users that locally interwork. After receiving the request message of the PGW, the first MME may establish or modify a bearer according to the request message in the manner of steps S502-506. For example, the first MME may initiate a request for radio bearer establishment or modification to a first base station (e.g., eNB) where the first user is located according to the steps S502-506, the first eNB initiates RRC connection reconfiguration, and responds to the first MME after the RRC connection reconfiguration is completed, and then the first MME responds to the PGW with a message that bearer establishment or modification is completed, thereby completing the entire procedure of bearer establishment or modification.

Preferably, the first MME may set the gateway tunnel identifier in the first eNB to a tunnel identifier allocated by the second eNB for the Bearer through a modification procedure of a Radio Access Bearer (RAB). For example, it is described that a message sent by a first user to a second user is referred to as an uplink behavior example, after the first MME acquires a tunnel identifier a allocated to the bearer by a second eNB corresponding to the second user, the tunnel identifier a may be set as an uplink tunnel identifier of the first eNB; similarly, after acquiring the tunnel identifier B allocated to the bearer by the first eNB corresponding to the first user, the second MME may set the tunnel identifier B as the uplink tunnel identifier of the second eNB. Thereby, radio bearer binding between the first eNB and the second eNB is achieved.

As a preferred embodiment, in the process of establishing or modifying the locally interworking bearer, after the PCRF indicates that the locally interworking bearer needs to be established or modified, the PGW may determine whether the bearer needs to be established or modified actually according to information (e.g., user location, user subscription, local policy, and other factors) of the two locally interworking users, and if so, may perform a subsequent bearer establishment or modification process. Of course, the step of determining whether the bearer actually needs to be established or modified according to the information of the two locally interworking users may not be performed locally in the PGW, and preferably, may be performed in the MME. For example, if the location information is obtained at the first MME, after the first MME obtains the tunnel identifier allocated by the second eNB for the bearer, the first MME may also obtain the location information of the second eNB, and at this time, the first MME may determine whether to establish or modify the bearer; if the result of the determination is yes, the first MME may bind, according to the tunnel identifier, the interworking data bearer between the first base station and the second base station corresponding to the first user; and if the determination result is negative, the first MME may delete the obtained tunnel identifier allocated by the second eNB for the bearer.

As a preferred embodiment, after the above-mentioned locally interworking bearer is used, the bearer may be released, and the release process may be initiated by the MME. For example, after the first MME confirms that the bearer for local interworking needs to be released, the first MME may notify the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway, where the second MME is a serving MME of a second user of the two users corresponding to local interworking, and the second base station is a serving base station of the second user. Through the method, the second eNB is not bound with the radio bearer of the first eNB any more due to the change of the tunnel identifier, but is directly bound with the core network gateway, so that the release of the local interworking bearer is realized.

Preferably, there are various ways for the first MME to notify the second MME of setting the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway, for example, the first MME may directly notify the second MME through a release binding request message, or the first MME may also send a bearer update request to the PGW, and then the PGW sends a failure notification to the second MME, where the failure notification is used to instruct the second MME to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway, so that the second MME is also notified of setting the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway.

Corresponding to the foregoing method, in this embodiment, a bearer processing apparatus is provided, located in a first MME, and is configured to implement the foregoing embodiment and preferred embodiments, which have been already described and are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 6 is a block diagram of a bearer processing apparatus according to an embodiment of the present invention, as shown in fig. 6, the apparatus including: a first receiving module 62, an obtaining module 64, and a binding module 66, each of which is described in detail below.

A first receiving module 62, configured to receive a request message from a PGW, where the request message is used to instruct the first MME to establish or modify a bearer for local interworking, where the first MME is a serving MME of a first user of two users corresponding to local interworking; an obtaining module 64, connected to the first receiving module 62, configured to obtain a tunnel identifier allocated to a bearer by a second base station corresponding to a second user of the two users corresponding to the local interworking; and a binding module 66, connected to the obtaining module 64, for binding the interworking data bearer between the first base station and the second base station corresponding to the first user according to the tunnel identifier.

In this embodiment, through the above modules, when the first MME determines that the bearer for local interworking needs to be established or modified through the first receiving module 62, first, the obtaining module 64 obtains the tunnel identifier allocated to the bearer by the second base station corresponding to the second user of the local interworking opposite end, and then, according to the tunnel identifier, the interworking data bearer between the first base station corresponding to the first user of the local end and the second base station of the opposite end is bound through the binding module 66, so that data between the first user and the second user can be transmitted through the interworking bearer, the establishment of the bearer based on local interworking is realized, the problem of how to establish each bearer path between the interworking wireless side network elements in the related art is solved, and the bearer establishing manner is simple and easy to implement, and is efficient.

Preferably, the binding module may include: and the setting unit is used for setting the gateway tunnel identifier in the first base station as the tunnel identifier allocated to the bearer by the second base station through the radio access bearer RAB modification process.

Preferably, the first MME may further include: the judging module is used for judging whether the bearer needs to be established or modified; if the judgment result of the judgment module is yes, the binding module can be further used for binding the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier; and under the condition that the judgment result of the judging module is negative, the first MME may further include a deleting module, connected to the obtaining module, for deleting the obtained tunnel identifier allocated to the bearer by the second base station.

Preferably, the first MME may further include: a first confirmation module, configured to confirm that a bearer for local interworking needs to be released; and the first notification module is connected with the first confirmation module and used for notifying the second MME of setting the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway, wherein the second MME is a serving MME of a second user in two corresponding users which are locally communicated.

Fig. 7 is a block diagram of a structure of the bearer processing system according to an embodiment of the present invention, and as shown in fig. 7, the system includes the bearer processing device 60 located in the MME (in fig. 7, the bearer processing device in fig. 6 is taken as an example for explanation), and further includes a PCRF70 and a PGW 80.

Preferably, PCRF70 may include: the second confirmation module is used for establishing or modifying the load for local intercommunication according to the strategy confirmation requirement; and the second notification module is connected to the first confirmation module, and is configured to notify the PGW80 to initiate a bearer establishment or modification process.

Preferably, PCRF70 may further include: a second receiving module, configured to receive a bearer resource modification request from a user; or for receiving a resource reservation indication from an application layer network element.

Preferably, the first notification module in the first MME60 may include: a first sending module, configured to send a bearer update request to a PGW, where the PGW80 may include: a second sending module, configured to send an invalidation notification to the second MME, where the invalidation notification is used to instruct the second MME to set the tunnel identifier of the second base station to the tunnel identifier of the corresponding core network bearer; or, the first sending module may also be configured to directly send a binding release request message to the second MME, where the binding release request message may be used to notify the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway.

In this embodiment, a bearer release method is further provided, and fig. 8 is a flowchart of the bearer release method according to the embodiment of the present invention, as shown in fig. 8, the method includes the following steps:

step S802, a first MME confirms that a bearer for local interworking needs to be released, wherein the first MME is a service MME of a first user in two users corresponding to the local interworking;

step S804, the first MME notifies the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated and corresponding, and the second base station is a serving base station of the second user.

In this embodiment, through the above steps, due to the change of the tunnel identifier, the second eNB is not bound to the radio bearer of the first eNB any more, but is directly bound to the bearer of the core network, so that the release of the bearer for local interworking is implemented.

Preferably, there are various ways for the first MME to notify the second MME of setting the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway, for example, the first MME may directly notify the second MME, or the first MME may also send a bearer update request to the PGW, and then the PGW sends an invalidation notification to the second MME, where the invalidation notification is used to instruct the second MME to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway, so that the second MME is also notified to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway.

Corresponding to the above bearer release method, in this embodiment, a bearer release apparatus is further provided, where the bearer release apparatus is located in the first MME, and fig. 9 is a block diagram of a structure of the bearer release apparatus according to the embodiment of the present invention, and as shown in fig. 9, the apparatus includes: a third confirmation module 92 and a third notification module 94, each of which is described in detail below.

A third confirming module 92, configured to confirm that a bearer for local interworking needs to be released, where the first MME is a serving MME of a first user of the two users corresponding to the local interworking; a third notifying module 94, connected to the third confirming module 92, configured to notify the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated, and the second base station is a serving base station of the second user.

In this embodiment, through the above modules, due to the change of the tunnel identifier, the second eNB is not bound to the radio bearer of the first eNB any more, but is directly bound to the bearer of the core network, so as to implement the release of the bearer for local interworking.

Preferably, the third notification module 94 may include: a third sending module, configured to send a bearer update request to the PGW, where the bearer update request is used for the PGW to send an invalidation notification to the second MME, and the invalidation notification is used to instruct the second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway; or, the third sending module may be further configured to directly send a binding release request message to the second MME, where the binding release request message may be used to notify the second MME to set the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway.

The following description is given in conjunction with the preferred embodiments, which combine the above embodiments and their preferred embodiments.

In the following embodiments, a concept of a method for implementing local interworking based on bearer binding is proposed, which avoids the function enhancement performed by a wireless side network element in implementing bearer-level local interworking, and the wireless side network element of an interworking peer does not need to enhance a bearer mapping function to match interworking data to a radio bearer, and is a simpler method for implementing local interworking. The following is a description of a local interworking method based on bearer binding in a 3GPP network.

In the following preferred embodiment, the anchor gateway establishes a specific bearer for the interworking service, and this bearer is only responsible for transmitting service data between two interworking users. The anchor gateway may establish different specific bearers for interworking service data of different Qos levels.

The mobility management unit obtains mobility management unit information serving for the opposite-end user, an opposite-end user identifier and a specific bearing identifier distributed by the opposite-end mobility management unit from the anchor point gateway. And the mobility management unit acquires the specific bearer downlink tunnel identifier allocated by the wireless side network element attached to the opposite terminal user through signaling interaction. The mobility management unit completes interworking service bearer binding by replacing the uplink tunnel identifier of the specific bearer on the wireless side network element managed by the mobility management unit, and realizes local interworking establishment.

The mobility management unit directly or indirectly informs the mobility management unit serving the opposite terminal user to replace the specific bearing uplink identification attached to the wireless side network element of the opposite terminal user into the core network gateway tunnel identification, completes the binding release of the interworking service bearing and realizes the local interworking suspension.

If the mobility management units serving the interworking user are the same, that is, the first MME and the second MME are the same MME, the operation between the mobility management units becomes an internal operation of the network element.

Example one

The preferred embodiment is described with an LTE mobile communication network as a background, and the technical solution is also applicable to a 3G mobile communication network and can be protected equally.

Fig. 10 is a first flowchart of an implementation manner of specific bearer establishment according to a first embodiment of the present invention, as shown in fig. 10, the flowchart may include the following steps:

step S1002, when the user finds that the established bearer resource cannot meet the service requirement, initiates a bearer resource allocation request procedure. The user reports information such as Qos (quality of Service) and Packet filter applied for subsequent services to the network in the initiated message requesting modification of bearer resources.

And S1004-S1006, the core network element sends the resource information requested by the user to the anchor point gateway P-GW through the bearing resource command.

Step S1008, the anchor point gateway (P-GW) initiates an IP-CAN session modification process with the PCRF, and applies for resource allocation. The PCRF analyzes the resource request parameter, if the service corresponding to the request resource is the intercommunication service between two users, the PCRF establishes a special bearer specially used for the intercommunication user data transmission or modifies the current existing intercommunication user special bearer if the possibility of using the local intercommunication function subsequently exists. The PCRF may optionally consider information such as user subscription, user location, etc. when deciding to establish or modify a specific bearer, and may establish the specific bearer for the user if it is determined that local interworking is allowed to be used.

Step S1010, the anchor point gateway (P-GW) initiates a specific bearer establishment or modification process, and the message carries an indication or a trigger to notify the MME of reporting address, identifier, or number information.

Step S1012, the MME initiates a radio bearer establishment procedure corresponding to the specific bearer.

In step S1014, the eNB reconfigures the air interface RRC connection according to the radio bearer setup/modification message.

In step S1016, after the RRC air interface connection configuration is completed, the eNB replies a radio bearer setup/modification response message.

Step S1018, the MME replies a create/modify bearer response message, where the message carries the address, identifier, or number information of the MME.

Step S1020, the P-GW responds to the IP-CAN session modification message to the PCRF.

Through the process of this embodiment, a bearer-level data service channel dedicated to service data interworking between two users is established on the wireless side network element and the core network gateway. The P-GW may establish different specific bearers for interworking service data of different Qos levels.

Example two

Fig. 11 is a second flowchart of an implementation manner of specific bearer establishment according to the second embodiment of the present invention, and as shown in fig. 11, the flowchart may include the following steps:

step S1102, the user initiates an application layer service application based on the existing user plane bearer path.

In step S1104, if the application layer network element, such as AF or X-CSCF, finds that the service is an interworking service between two users according to the service applied, it considers that there is a possibility of using a local interworking function subsequently, and informs the PCRF of a specific bearer resource that needs to be dedicated to interworking between the two users through the resource reservation message. The AF or X-CSCF can optionally consider the information of user subscription, user position and the like when deciding to indicate the reservation of the specific bearing resource between the two interworking users, and can establish the specific bearing for the user under the scene of determining to use the local interworking function.

Step S1106, the PCRF formulates a specific bearer resource policy for two users to communicate with each other, and informs the P-GW to establish a specific bearer dedicated for communicating user data transmission or modify a currently existing specific bearer for communicating users through an IP-CAN session modification message.

Step S1108, the anchor point gateway (P-GW) initiates a specific bearer establishment or modification process, and the message carries an indication or a trigger to notify the MME of reporting address, identifier, or number information.

In step S1110, the MME initiates a radio bearer establishment procedure corresponding to the specific bearer.

In step S1112, the eNB reconfigures the air interface RRC connection according to the radio bearer setup/modification message.

In step S1114, after the RRC air interface connection configuration is completed, the eNB replies a radio bearer setup/modification response message.

Step S1116, the MME replies a create/modify bearer response message, where the message carries the address, identifier, or number information of the MME.

Step S1118, P-GW responds IP-CAN conversation modification message to PCRF.

EXAMPLE III

Fig. 12 is a first flowchart of an implementation manner of implementing local interworking by bearer binding according to a third embodiment of the present invention, and as shown in fig. 12, the flowchart may include the following steps:

step S1202, the uplink and downlink data of the interworking service between the two users are transmitted through a specific bearer established by the core network.

Step S1204, when P-GW finds that there is data transmission on the special bearer dedicated to the intercommunication of two users, it determines whether it can start the local intercommunication function, if the positions of the base stations attached to the two intercommunicated users are close and the user contract and the local policy allow the local routing of the intercommunication service, it instructs the mobility management unit (MME) to perform the local intercommunication bearer binding.

If the factors such as user location, user subscription, local policy and the like are considered in combination when establishing the specific bearer for interworking between two users, the determination process in this step may be omitted, and the P-GW may instruct a mobility management unit (MME) to perform local interworking bearer binding when detecting data transfer on the specific bearer.

In step S1206, the P-GW sends a local interworking notification message to one of the mobility management units (MMEs) (e.g. MME1 in the figure) serving the interworking user, where the message carries an interworking correspondent user identifier, an address or an identifier or a number of the mobility management unit (MME) (e.g. MME2 in the figure) serving the correspondent interworking user, and specific bearer identification information allocated to the mobility management unit (MME) (e.g. MME1, MME2 in the figure) serving the interworking user.

If there are multiple bearers established for the interworking service, the P-GW needs to inform the MME1 of the correspondence between bearer identities allocated by different MMEs for the specific bearer.

In step S1208, the MME1 finds the MME2 according to the MME2 address, identifier, or number information in the local interworking notification message, and sends an information acquisition request message to the MME. The message carries the user identifier of the interworking peer, the bearer identifier allocated by the MME2 for the specific bearer, and the tunnel identifier information allocated on the eNB1 for the specific bearer.

In step S1210, the MME2 queries the session management context according to the UE2 user identifier in the information acquisition request message and the specific bearer identifier allocated by the MME2, finds the tunnel identifier allocated by the eNB2 for interworking the specific bearer, and replies to the MME 1.

In step S1212, the MME1 binds the interworking data bearer from the eNB1 to the eNB2 by replacing the uplink tunnel identifier of the specific bearer on the eNB1 with the tunnel identifier allocated by the eNB2 for the specific bearer through the RAB modification procedure. The MME2 binds the interworking data bearer from eNB2 to eNB1 by replacing the uplink tunnel identity of the specific bearer on eNB2 with the tunnel identity allocated by eNB1 for the specific bearer through the RAB modification procedure.

Step S1214, after the RAB modification procedure is completed, the MME1 returns a local interworking notification response message to notify the P-GW that the establishment of the local interworking bearer level channel is successful.

Step S1216, after the local interworking channel is successfully established, the uplink and downlink data of the interworking service is sent through the bearer level data channel between the eNB1 and the eNB 2.

Example four

Fig. 13 is a second flowchart of an implementation manner of implementing local interworking by bearer binding according to a fourth embodiment of the present invention, and as shown in fig. 13, the flowchart may include the following steps:

step S1302, the uplink and downlink data of the interworking service between the two users are transmitted through a specific bearer established by the core network.

In step S1304, when the P-GW finds that there is data transmission on a specific bearer dedicated to interworking between two users, it considers that it is possible to implement interworking, and indicates one of the mobility management units (MMEs) (e.g. MME1 in the figure) serving the interworking user to perform the determination of local interworking through the local interworking notification message.

Step S1306, the P-GW sends a local interworking notification message to the MME1, where the message carries an interworking correspondent user identifier, an address or an identifier or a number of a mobility management unit (MME) (e.g. MME 2) serving the correspondent interworking user, and specific bearer identification information allocated to the mobility management unit (MME) (e.g. MME1, MME 2) serving the interworking user.

In step S1308, the MME1 finds the MME2 according to the obtained MME2 identification address or identification or number information, and sends an information acquisition request message to the MME. The message carries the interworking correspondent user identifier and the bearer identifier allocated by the MME2 for the specific bearer.

In step S1310, the MME2 replies an information acquisition response message, where the message carries the eNB2 id attached to the UE2 and the downlink tunnel id allocated by the eNB2 for the specific bearer.

In step S1312, the MME1 determines the location relationship between the eNB1 attached to the user 1 according to the location information (e.g. the eNB2 identifier) of the user 2, and if the location is close, it is considered that the establishment of the local interworking channel can be performed, otherwise, the eNB2 is optionally explicitly notified to delete the information transferred in step S1308.

The MME2 may also use local policy, user subscription, etc. information to make a determination whether local interworking is to be performed, depending on the preconditions for interworking a particular bearer establishment. The decision of the MME2 may be simplified if user subscriptions, local policies, etc. are taken into account when establishing bearers.

In step S1314, the MME1 sends a confirmation message to the MME2, and if it decides to perform establishment of the local interworking channel, sends the tunnel identifier allocated by the eNB1 for the specific bearer to the MME 2. If the establishment of the local interworking channel is not enabled, the MME2 may optionally be explicitly instructed to delete the information transferred in step 804, or the MME2 may set an information deletion timer to delete the information transferred in step 804 if the local interworking channel is not established for a period of time.

In step S1316, the MME1 binds the interworking data bearer from the eNB1 to the eNB2 by replacing the uplink tunnel identifier of the specific bearer on the eNB1 with the tunnel identifier allocated by the eNB2 for the specific bearer through the RAB modification procedure. The MME2 binds the interworking data bearer from eNB2 to eNB1 by replacing the uplink tunnel identity of the specific bearer on eNB2 with the tunnel identity allocated by eNB1 for the specific bearer through the RAB modification procedure.

Step 1318, after the RAB modification procedure is completed, the MME1 returns a local interworking notification response message to notify the P-GW that the establishment of the local interworking bearer level channel is successful.

Step S1320, after the local interworking channel is successfully established, the uplink and downlink data of the interworking service is sent through the bearer level data channel between the eNB1 and the eNB 2.

EXAMPLE five

Fig. 14 is a first flowchart of an implementation manner of releasing a local interworking channel according to a fifth embodiment of the present invention, and as shown in fig. 14, the flowchart may include the following steps:

in step S1402, the S1 connection of the user 1 needs to be released due to a wireless error or an authentication failure.

In step S1404, the MME1 notifies the MME2 to delete the bearer binding of the local interworking data channel through the release binding request message, where the message carries the identifier of interworking user 2 and the bearer identifier allocated by the MME2 for the specific bearer used for interworking.

In step S1406, the MME2 identifies the bearer according to the information obtained in step S1404, and renews the uplink tunnel of the specific bearer to the core network S-GW.

In step S1408, the MME2 initiates a bearer modification procedure to the eNB2, and replaces the uplink identifier of the specific bearer on the eNB2 with the tunnel identifier allocated by the S-GW.

At step S1410, MME2 replies to MME1 with a release binding response message.

In step S1412, the data sent by the UE2 is forwarded through the core network.

In step S1414, if the P-GW receives the data of the UE1, it considers that the local interworking channel is released, and sends the data of the UE1 to the corresponding core network bearer, and the subsequent core network triggers paging of the UE 1. When the UE1 enters the connected state, it is re-determined whether local interworking can be established.

EXAMPLE six

Fig. 15 is a second flowchart of an implementation manner of releasing a local interworking channel according to a sixth embodiment of the present invention, and as shown in fig. 15, the flowchart may include the following steps:

in step S1502, the S1 connection of user 1 needs to be released due to a wireless error or authentication failure.

Step S1504, MME1 sends an access bearer release request to S-GW1, deletes the related information of eNB1, and the message carries an indication to inform S-GW1 of sending a message to inform P-GW of local interworking failure.

In step S1506, S-GW1 sends a bearer update request message to the P-GW, notifying the P-GW of the local interworking failure. This may be embodied by adding a cause value or indication in the bearer update request message.

At step 1508, the P-GW sends an invalidation notification to another MME (e.g., MME2 in the figure) serving the interworking user.

In step S1510, MME2 replaces the uplink tunnel id of the specific bearer for interworking with the tunnel id allocated by S-GW 2.

In step S1512, the MME2 updates the tunnel identifier allocated by the S-GW2 to the eNB2 through the RAB modification procedure, at this time, the local interworking connection is broken, and the interworking data received by the subsequent eNB2 is forwarded through the core network.

In step S1514, after the MME2 completes the tunnel identifier update, it replies an invalidation notification response message to the P-GW.

In step S1516, the P-GW returns a bearer update response message to the S-GW 1.

In step S1518, the S-GW1 returns an access bearer release response message to the MME 1.

Step S1520, the UE2 sends the subsequent data through the bearer of the core network.

In step S1522, if the P-GW receives the data of the UE1, it determines that the local interworking channel is released, and sends the data of the UE1 to the corresponding core network bearer, and the subsequent core network triggers paging of the UE 1. When the UE1 enters the connected state, it is re-determined whether local interworking can be established.

In another embodiment, a software is provided, which is used to execute the technical solutions described in the above embodiments and the preferred embodiments.

In another embodiment, a storage medium is provided, wherein the software is stored in the storage medium, and the storage medium includes, but is not limited to, an optical disc, a floppy disc, a hard disc, a rewritable memory, and the like.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A bearer processing method is characterized by comprising the following steps:

a first mobility management unit (MME) receives a request message from an anchor gateway (PGW), wherein the request message is used for indicating the MME to establish or modify a bearer for local interworking, and the first MME is a serving MME of a first user of two users corresponding to the local interworking;

the first MME acquires a tunnel identifier distributed for the bearer by a second base station corresponding to a second user of the two users corresponding to the local intercommunication;

and the first MME binds the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier.

2. The method of claim 1, wherein before the first MME receives the request message from the PGW, further comprising:

the PCRF establishes or modifies the bearer according to the policy confirmation requirement;

and the PCRF informs the PGW to initiate the establishment or modification process of the bearer.

3. The method of claim 2, wherein the PCRF notifying the PGW of initiating the bearer establishment or modification procedure comprises:

and the PCRF informs the PGW to initiate the establishment or modification process of the bearer through an IP-CAN session.

4. The method of claim 2, wherein before the PCRF confirms the need to establish or modify the bearer for the local interworking according to the policy, the method further comprises:

the PCRF receives a bearer resource modification request from a user; or,

and the PCRF receives a resource reservation indication from an application layer network element.

5. The method of claim 3, wherein before the PCRF confirms the need to establish or modify the bearer for the local interworking according to the policy, the method further comprises:

the PCRF receives a bearer resource modification request from a user; or,

6. The method according to any of claims 1 to 5, wherein the binding, by the first MME, the interworking data bearer between the first base station corresponding to the first user and the second base station according to the tunnel identifier comprises:

and the first MME sets a gateway tunnel identifier in the first base station to the tunnel identifier allocated to the bearer by the second base station through a radio access bearer RAB modification process.

7. The method according to any of claims 1 to 5, wherein after the first MME obtains the tunnel identifier allocated to the bearer by the second base station corresponding to the second user of the two users corresponding to the local interworking, the method further comprises:

the first MME judges whether the bearer needs to be established or modified;

if the judgment result is yes, the first MME binds the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier;

and if the judgment result is negative, the first MME deletes the acquired tunnel identifier allocated to the bearer by the second base station.

8. The method according to any one of claims 1 to 5, wherein after the first MME binds an interworking data bearer between the first base station corresponding to the first user and the second base station according to the tunnel identifier, the method further comprises:

the first MME confirming that the bearer needs to be released;

and the first MME informs a second MME of setting a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, wherein the second MME is a serving MME of a second user of the two corresponding users which are locally communicated.

9. The method of claim 8, wherein the first MME notifying the second MME of setting the tunnel identifier in the second base station to the tunnel identifier of the corresponding core network gateway comprises:

the first MME sends a bearer update request to the PGW, the PGW sends an invalidation notification to the second MME, and the invalidation notification is used for indicating the second MME to set the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway; or,

and the first MME sends a binding release request message to the second MME, wherein the binding release request message is used for informing the second MME of setting the tunnel identifier in the second base station as the tunnel identifier of the corresponding core network gateway.

10. A bearer release method, comprising:

a first mobility management unit (MME) confirms that a bearer for local interworking needs to be released, wherein the first MME is a serving MME of a first user of two users corresponding to the local interworking;

and the first MME informs a second MME of setting a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, wherein the second MME is a service MME of a second user of the two corresponding users which are locally communicated, and the second base station is a service base station of the second user.

11. The method of claim 10, wherein the first MME informing a second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway comprises:

the first MME sends a bearer update request to an anchor gateway (PGW), the PGW sends a failure notification to the second MME, and the failure notification is used for indicating the second MME to set a tunnel identifier in the second base station as a tunnel identifier of a corresponding core network gateway; or,

12. A bearer processing apparatus, located in a first mobility management unit MME, includes:

a first receiving module, configured to receive a request message from an anchor gateway PGW, where the request message is used to instruct the first MME to establish or modify a bearer for local interworking, where the first MME is a serving MME of a first user of two users corresponding to the local interworking;

an obtaining module, configured to obtain a tunnel identifier allocated to the bearer by a second base station corresponding to a second user of the two users corresponding to the local interworking;

and the binding module is used for binding the interworking data bearer of the first base station and the second base station corresponding to the first user according to the tunnel identifier.

13. The apparatus of claim 12, wherein the binding module comprises:

a setting unit, configured to set, through a radio access bearer RAB modification process, a gateway tunnel identifier in the first base station to the tunnel identifier allocated by the second base station for the bearer.

14. The apparatus of claim 12, further comprising:

the judging module is used for judging whether the bearer needs to be established or modified;

if the judgment result of the judgment module is yes, the binding module is further configured to bind, according to the tunnel identifier, an interworking data bearer between the first base station and the second base station, where the first base station corresponds to the first user;

and in the case that the judgment result of the judging module is negative, the first MME further includes a deleting module configured to delete the acquired tunnel identifier allocated to the bearer by the second base station.

15. The apparatus of any one of claims 12 to 14, further comprising:

a first confirmation module, configured to confirm that the bearer needs to be released;

a first notifying module, configured to notify a second MME to set a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated.

16. A bearer handling system comprising a bearer handling apparatus according to any of claims 12 to 14, located in a first mobility management unit, MME, further comprising a policy charging rules function, PCRF, and an anchor gateway, PGW.

17. The system of claim 16 wherein the PCRF comprises:

the second confirmation module is used for confirming that the bearer needs to be established or modified according to the strategy;

a second notifying module, configured to notify the PGW to initiate the bearer establishment or modification process.

18. The system of claim 17 wherein the PCRF further comprises:

a second receiving module, configured to receive a bearer resource modification request from a user; or,

for receiving a resource reservation indication from an application layer network element.

19. A bearer handling system comprising the bearer handling apparatus in the first mobility management unit MME of claim 15, further comprising a policy charging rules function PCRF and an anchor gateway PGW.

20. The system of claim 19, wherein the first notification module further comprises:

a first sending module, configured to send a bearer update request to the PGW, where in this case, the PGW includes: a second sending module, configured to send an invalidation notification to the second MME, where the invalidation notification is used to instruct the second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway; or,

the first sending module is configured to send a binding release request message to the second MME, where the binding release request message is used to notify the second MME that the tunnel identifier in the second base station is set as the tunnel identifier of the corresponding core network gateway.

21. A bearer release apparatus, located in a first mobility management unit MME, includes:

a third confirming module, configured to confirm that a bearer for local interworking needs to be released, where the first MME is a serving MME of a first user of the two users corresponding to the local interworking;

a third notifying module, configured to notify a second MME to set a tunnel identifier in a second base station as a tunnel identifier of a corresponding core network gateway, where the second MME is a serving MME of a second user of the two users that are locally intercommunicated and correspond to each other, and the second base station is a serving base station of the second user.

22. The apparatus of claim 21, wherein the third notification module comprises:

a third sending module, configured to send a bearer update request to an anchor gateway PGW, where the bearer update request is used for the PGW to send an invalidation notification to the second MME, and the invalidation notification is used to instruct the second MME to set a tunnel identifier in the second base station to a tunnel identifier of a corresponding core network gateway; or,

the third sending module is configured to send a binding release request message to the second MME, where the binding release request message is used to notify the second MME that the tunnel identifier in the second base station is set as the tunnel identifier of the corresponding core network gateway.