WO2009043283A1

WO2009043283A1 - Method and apparatus of controlling dedicated bearer establishment in the procedure of default bearer establishment

Info

Publication number: WO2009043283A1
Application number: PCT/CN2008/072497
Authority: WO
Inventors: Zhe Chen; Lan Liu; Jinyi Zhou; Qi Yu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-26
Filing date: 2008-09-24
Publication date: 2009-04-09
Also published as: CN101400148B; CN101400148A

Abstract

A method of controlling dedicated bearer establishment in the procedure of default bearer establishment is disclosed and includes: network side controlling entity receives dedicated bearer establishment request in the procedure of establishing default bearer; the network side controlling entity judges if establishment of dedicated bearer is continued based on the predetermined condition, if yes, the network side controlling entity continues establishing dedicated bearer, if no, the network side controlling entity holds the dedicated bearer establishment request, and does not continue establishing the dedicated bearer until the predetermined condition is arrived at. An apparatus of controlling dedicated bearer establishment in the procedure of default bearer establishment is disclosed. The invention realizes that the network side entity controls dedicated bearer establishment in the procedure of establishing default bearer and assures to fulfill successfully establishment of dedicated bearer in the procedure of attach.

Description

Control method and device for establishing dedicated bearer in default bearer establishment process

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a control method and device for establishing a dedicated bearer in a default bearer setup process. Background technique

In the prior art, the attaching process in the SAE (System Architecture Evolution) is as shown in FIG. 1 and includes the following steps:

Step slOl, UE (User Equipment, User Equipment) to the eNB (Evolved

The NodeB (Evolved Base Station) sends an Attach Request (IMSI or S-TMSI and old TAI, Selected Network), where the Attach Request (IMSI or S-TMSI and old TAI, Selected Network) indicates that the Attach Request includes the IMSI (International Mobile Subscriber). Identity, International Mobile Subscriber Identity) or S-TMSI (SAE-Temporary Mobile Subscriber Identity), and old TAI (Tracking Area Identity), Selected Network (selected network), the following also applies The same format.

Step si 02: The eNB sends an Attach Request (IMSI or S-TMSI and old TAI, Selected Network, Cell Global Identity) request to the new MME (Mobility Management Entity).

Step s10: If the new MME does not have the IMSI of the UE, send an identification request (S-TMSI, old TAI) to the old MME to request the IMSI, and if the old MME has the IMSI of the UE, respond to the Identification Response by sending an identity (IMSI) , Authentication Quintets ) 4 bar IMSI passed to new MME, if not, it will return an error response.

Step sl04: If the old MME does not have the IMSI of the UE, the new MME sends an Identification Request request IMSI to the UE, and the UE transmits the IMSI to the new MME by sending an Identification Response (IMSI).

Step s105, if there is no context of the UE in this network, then authentication The (authentication) process is necessary.

Step sl06, if there is any active bearer context in the new MME, then the delete bearer Request needs to be sent to delete these bearers.

Step sl07, if the MME has to send an Update Location Location (MMESI) message to the HSS (Home Subscriber Server) to initiate the location update process since the last Attach change or the first attach at this time.

Step sl08, the HSS sends a Cancel Location (IMSI, Cancellation Type) message to the old MME to delete the user subscription information on the old MME. Old MME sends a Cancel Location Ack (IMSI) to the HSS.

Step s109, if there is any active bearer of the UE on the old MME, the old MME sends a delete 7-requested Delete Bearer Request to the relevant S-GW (Serving Gate Way) and the P-GW (PDN (Packet Data) Network, packet data network) GateWay, packet data network gateway) to delete the active bearer, S-GW and P-GW send the delete bearer response Delete Bearer Response to the old MME.

Step s110, the HSS sends the insertion subscription data Insert Subscriber Data (IMSI, Subscription Data) to the MME to send all the subscription information to the new MME.

Step sill, new MME responds with an insert subscription data response Insert Subscriber Data Ack to HSS.

Step s 112, the new MME selects the P-GW according to the PPN selection operation performed by the subscribed APN (Access Point Network). The MME sends a default bearer request Create Default Bearer Request (IMSSI, MME Context ID, bearer id, P-GW address) to the S-GW. When the dedicated bearer needs to indicate that the Dedicated Bearer Required Indication is set to 1, the QoS (Quality of Service) list list indicates the QoS required for the dedicated bearer in the Attach process caused by these specific services, otherwise this is not required. parameter.

Step sll3, the S-GW establishes a record, and then sends a default bearer request Create Default Bearer Request (S-GW TEID-C (Tunnel Endpoint) Identifier for control plane, control plane tunnel endpoint identifier), S-GW TEID-U

( Tunnel Endpoint Identifier for user plane, bearer id (bearer Identifier)), to the P-GW.

Step sll4, the P-GW requests the default PCC (Policy and Charging Control) rule in the process of interacting with the Policy and Charging Rules Function (PCRF).

In the step si 15 , the P-GW sends a default bearer response (PDN GW Address for the user plane, PDN GW TEID ( Tunnel Endpoint Identifier) of the user plane, PDN GW TEID of the control plane , PDN Address ) to the S-GW.

Step si 16: The S-GW sends a Create Default Bearer Response (PDN Address, Serving GW address for User Plane, Serving GW Context ID) to the new MME.

Step si 17: The new MME sends an Attach Accept (S-TMSI, PDN address, TA List) to the eNB. At the same time, this message contains a S1-MME control message context establishment request Context Setup Request (bearer id). This message contains the required QoS and the TE-U of the S-GW and the user plane address of the S-GW.

Step sll8, the eNB sends a radio bearer setup request (bearer id) and an attach accept (S-TMSI, PDN address, TA List) message to the UE, and the UE can obtain the IP address assigned by the network.

Step s11: The UE sends a radio bearer setup response Radio Bearer Establishment Response response message to the eNB.

Step sl20, the eNB sends an Attach Complete (eNB TEID, eNB address for control plane) to the new MME.

In step s21, the new MME sends an Update Bearer Request (eNB address, eNB TEID) to the S-GW. The eNB TEID list is the eNB TEID for the dedicated bearer. This eNB TEID is the default 7-port TEID. Step s12: The S-GW sends an update bearer response Update Bearer Response to the SAE attach procedure. In step sll4, the interaction between the P-GW and the PCRF triggers the establishment of some dedicated bearers. The process of establishing a dedicated bearer in the SAE is as shown in FIG. 2: Step s201: The PCRF sends a PCC decision provision (QoS policy) message to the P-GW. If there is no PCC architecture, the P-GW itself generates a QoS policy.

Step s202: The P-GW uses the QoS policy to generate bearer QoS, and the P-GW sends a Create Dedicated Bearer Request (Bearer QoS, UL TFT, S5/S8 TEID) to the Serving GW.

Step s203: The Serving GW sends a Create Dedicated Bearer Request (Bearer QoS, UL (Uplink) TFT (Traffic Flow Template), SI-TEID message to the MME.

Step s204: The MME constructs a session management configuration Session Management Configuration cell, including a UL TFT. The MME sends a Bearer Setup Request (Bearer QoS, Session Management Configuration, SI-TEID) to the eNB.

Step s205: The eNB maps bearer QoS to Radio Bearer QoS, and then sends a Radio Bearer Setup Request (Radio Bearer QoS, Session Management Configuration) to the UE. The UE uses the upstream TFT to determine the mapping between the SDF and the radio bearer.

Step s206: The NAS layer of the UE generates a Session Management Response cell. The UE then sends a Radio Bearer Setup Response (Session Management Response) to the eNB.

Step s207: The eNB sends a Bearer Setup Response (SI-TEID, Session Management Response) to the MME.

Step s208: The MME sends a Create Dedicated Bearer Response (SI-TEID) message to the Serving GW.

In step s209, the Serving GW sends a Create Dedicated Bearer Response (S5/S8-TEID) to the PDN GW. Step s210: If the dedicated bearer is triggered by the PCC Decision Provision message sent from the PCRF, the PDN GW notifies the PCRF-Provision Ack message to tell the PCRF whether the PCC decision (QoS policy) it requests can be executed.

Summary of the invention

The embodiment of the invention provides a control method and device for establishing a dedicated bearer in a default bearer setup process, so as to implement control of the establishment of a dedicated bearer in the default bearer setup process.

To achieve the above objective, the embodiment of the present invention provides a control method for establishing a dedicated bearer in a default bearer setup process, including the following steps:

The network side control entity receives the dedicated bearer setup request in the default bearer setup process;

Determining, by the network-side control entity, whether to continue the establishment of the dedicated bearer according to a preset condition, and if yes, proceeding to establish the dedicated bearer; otherwise, maintaining the dedicated bearer setup request until the preset is reached The establishment of the proprietary bearer continues while the condition is met.

The embodiment of the present invention further provides a network-side control entity, which is used to control the establishment of a dedicated bearer in the process of establishing a default bearer, including:

a request receiving unit, configured to receive a dedicated bearer setup request in a default bearer setup process;

a determining unit, configured to: when the request receiving module receives the dedicated bearer setup request, determine whether to continue to establish the dedicated bearer according to a preset condition; if yes, the notification processing module continues to perform the establishment of the dedicated bearer, Otherwise, the notification storage module keeps the dedicated bearer setup request;

a processing unit, configured to continue the process of establishing a dedicated bearer according to the notification of the determining module;

a storage unit, configured to keep the dedicated bearer established according to the notification of the determining module Request.

Compared with the prior art, the embodiment of the invention has the following advantages:

When receiving the establishment request of the dedicated bearer in the default bearer setup process, first determine and verify the conditions required for the establishment of the dedicated bearer, such as establishing an address required for the dedicated bearer, etc., for the dedicated bearer that satisfies the condition. The continuation of the establishment is performed; the effective control of the establishment of the dedicated bearer in the default bearer establishment process by the network-side control entity is implemented, and the establishment of the dedicated bearer can be successfully completed. DRAWINGS

1 is an attachment process of a SAE in the prior art;

2 is a process of establishing a dedicated bearer in a SAE in the prior art;

3 is a flowchart of a control method for establishing a dedicated bearer in a default bearer setup process according to Embodiment 1 of the present invention;

4 is a flowchart of a control method for establishing a dedicated bearer in a default bearer setup process according to Embodiment 2 of the present invention;

5 is a flowchart of a control method for establishing a dedicated bearer in a default bearer setup process according to Embodiment 3 of the present invention;

6 is a flowchart of a control method for establishing a dedicated bearer in a default bearer setup process according to Embodiment 4 of the present invention;

7 is a flowchart of a control method for establishing a dedicated bearer in a default bearer setup process according to Embodiment 5 of the present invention;

FIG. 8 is a schematic structural diagram of a network side control entity in Embodiment 6 of the present invention. detailed description

In carrying out the process of the present invention, the inventors have found that the prior art has at least the following problems:

As described above, in the current SAE attach procedure, the interaction between the P-GW and the PCRF (step sll4) triggers the establishment of some dedicated bearers. However, in the establishment and end of the radio bearer Before receiving the attach accept message (step S118), the terminal cannot know the IP address assigned by the network. If the terminal sends the dedicated bearer setup to the terminal before it knows the IP address assigned by the network, it will cause potential problems (for example, the terminal cannot complete the configuration of the packet filter at the application layer).

A first embodiment of the present invention provides a control method for establishing a dedicated bearer in a default bearer setup process. The process is as shown in FIG. 3, and includes the following steps:

Step s301: The network side control entity receives the exclusive bearer setup request in the default bearer setup process.

In step s302, the network-side control entity determines whether to continue the establishment of the dedicated bearer according to the preset condition, and if yes, proceeds to step s303, otherwise proceeds to step s304.

Step s303, proceeding to establish the dedicated bearer.

In step s304, the dedicated bearer setup request is maintained, and the establishment of the dedicated bearer is continued until the preset condition is reached.

The second embodiment of the present invention is a process in which the MME on the network side controls the establishment of a dedicated bearer in the default bearer establishment process. The principle is: before the MME receives the "bearer setup response" message sent by the eNB, the MME saves all dedicated bearer setup requests for the APN received from the S-GW for the terminal until the MME receives the eNB. After the bearer setup response or the initial context setup completes the Initial Context Setup Complete message, or after the timer expires, the preset condition is judged. If the condition is met, the "Create Dedicated Bearer Request" message is sent to the eNB. .

The establishment process of the dedicated bearer is as shown in FIG. 4, wherein the solid line part indicates the related process of establishing the default bearer, and the dotted line part indicates the related process of establishing the dedicated bearer, including the following steps:

In step s401, the MME sends a Create Default Bearer Request to the Serving GW.

In step s402, the Serving GW sends a Create Default Bearer Request to the P-GW.

Step s403: The P-GW requests to obtain a default in the process of interacting with the PCRF. PCC rule.

Step s404, the P-GW sends a Create Default Bearer Response to the S-GW. Step s405: The S-GW sends a Create Default Bearer Response to the MME. Step s406: The P-GW sends a Create Dedicated Bearer Request (S5/S8-TEID, QoS, TFT, MSISDN, Linked Bearer ID) to the S-GW, and the parameter included in the dedicated bearer request is a Linked Bearer ID. Which is the default on the PDN-GW? Bearer ID.

It should be noted that step s406 is triggered by the PCRF interaction process in step s403, so the order may be before step s404 or after step s404 or step s405.

Step s407: The S-GW sends a Create Dedicated Bearer Request (Sla-TEID, QoS, TFT, MSISDN) to the MME.

It should be noted that step s407 is after step s406, but the timing relationship between step s407 and step s404 and step s405 is not determined.

After the MME receives the Create Dedicated Bearer Request sent from the S-GW, whether the MME stores the Linked Bearer ID and whether the eNB and the S-GW user plane TEID related to the Linked Bearer ID already exist. Then, it is proved that the default bearer establishment in steps s408 to s411 has been completed, and the establishment of the dedicated bearer can be continued, that is, step s412 is performed. The related explanation of the Linked Bearer ID is as follows: After the MME completes the establishment of the default bearer Default Bearer, the context Bearer Context about the default bearer is saved on the MME, and the Bearer Context includes the bearer ID of the default bearer. The user plane TEID of the relevant eNB and the S-GW. The establishment of all the dedicated link bearer identifiers of the Linked Bearer ID requires the bearer ID of the default bearer, the associated eNB, and the user plane TEID of the S-GW. Therefore, the MME needs to wait for the default bearer to be established before continuing to establish the dedicated bearer.

If it does not exist, the MME maintains the Create Dedicated Bearer Request message, and uses one of the following two methods to trigger the continued establishment of the dedicated bearer:

(1) Set a flag indicating that the default bearer associated with the dedicated bearer has not been established. The message, and then wait for the eNB to send a message that can bring the default bearer user plane information, such as: initial context setup request Initial Context Setup Request or load setup response Bearer Setup Response, if such a message is received, then according to the already set The flag bit determines whether to check the downlink user plane information of the bearer in such a message, including but not limited to: the user plane TEID of the eNB, then the proof step s411 has been executed, then the dedicated bearer can be continued. Once established, step s412 is performed. Then clear the flag.

(2) starting a timer on the MME, after the timer expires, the MME checks whether the bearer context Bearer Context related to the Linked Bearer ID carried by the dedicated bearer setup request is complete, if complete, After the verification step s411 has been executed, the establishment of the dedicated bearer can be continued, that is, step s412 is performed, and then the timer is cleared. If it is not complete, reset the timer.

Step s408: The MME sends a bearer setup request Bearer Setup Request message to the eNB.

Step s409, the eNB sends a radio bearer setup request. Radio Bearer

Establishment Request to the UE.

Step s410: The UE sends a radio bearer establishment response message to the eNB.

Step s411: The eNB sends a bearer setup response Bearer Setup Response message to step s412. The MME constructs a session management configuration session management configuration cell, including a UL TFT. The MME sends a Bearer Setup Request (Bearer QoS, Session Management Configuration, SI-TEID, ) ^ eNB. The Session Management Configuration contains the NAS parameters, including UL TFT, TI.

In step s413, the eNB sends a Radio Bearer Setup Request message to the UE. In step s414, the eNB maps the bearer QoS to the Radio Bearer QoS, and then sends a Radio Bearer Setup Request (Radio Bearer QoS, Session Management Configuration) to the UE. The UE uses the upstream TFT to determine the SDF to the radio bearer. The mapping between.

In step s415, the NAS layer of the UE generates a Session Management Response cell. The UE then transmits a Radio Bearer Setup Response (Session Management Response) to the eNB.

Step s416, the eNB sends a Bearer Setup Response (Sla-TEID,

Session Management Response ).

Step s417: The MME sends a Create Dedicated Bearer Response (Sc-TEID, Bearer ID) message to the Serving GW.

Step s418, the Serving GW sends a Create Dedicated Bearer Response (S5/S8-TEID, Bearer ID) to the PDN GW.

Through the description of the foregoing embodiment 2, the MME on the network side controls the establishment of the dedicated bearer in the default bearer establishment process, and ensures that the establishment of the dedicated bearer in the attach process can be successfully completed.

The third embodiment of the present invention is a process for controlling the establishment of a dedicated bearer in the default bearer establishment process by the S-GW on the network side. The principle is: Before the S-GW receives the "Update Default Bearer Request" sent from the MME, the S-GW will establish a request for all dedicated bearers of the APN from the P-GW for the terminal. The save condition is not determined until after it receives the "Update Bearer Request Update Bearer Request" issued by the MME or after the timer expires. If the condition is met, the MME is sent "Create Dedicated Dedicated Bearer Request". Bearer Request" message.

The establishment process of the dedicated bearer is as shown in Figure 5:

Step s501: The UE sends a Create Default Bearer Request to the MME.

Step s502: The MME sends a Create Default Bearer Request request to the Serving GW.

Step s503: The Serving GW sends a Create Default Bearer Request request to the P-GW.

Step s504: The P-GW performs PCRF interaction information interaction with the PCRF. Step s505, the P-GW sends a Create Default Bearer to the Serving GW. Response information.

Step s506: The Serving GW sends a Create Default Bearer Response message to the MME.

Step s507: The P-GW sends a Create Dedicated Bearer Request to the S-GW, including the following parameters: IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address.

After receiving the Create Dedicated Bearer Request sent from the P-GW, the S-GW searches for the user plane TEID of the eNB and the P-GW related to the Linked Bearer ID according to the Linked Bearer ID. Existence, then the proof step s512 has been executed, then the establishment of the dedicated bearer can be continued, that is, step s513 is performed;

If it does not exist, the S-GW keeps this message, and then decides whether to continue the establishment of the dedicated bearer according to one of the following two methods, that is, proceeds to step s513.

(1) Set a flag indicating that the default bearer associated with the dedicated bearer has not been established, and then wait for the MME to send an Update Bearer Request. If it is received, determine whether to check the message according to the flag that has been set. The downlink user plane information of the user is provided, including but not limited to: the user plane TEID of the eNB. If the user plane TEID of the eNB of the default bearer is brought, then the step s512 has been performed, then the special operation can be continued. With the establishment of the bearer, step s513 is performed, and then the flag bit is cleared.

(2) A timer is started on the S-GW. When the timer expires, the S-GW checks whether the Bearer Context associated with the Linked Bearer ID carried by the dedicated bearer setup request is complete, if complete. Then, it is proved that the step s512 has been executed, then the establishment of the dedicated bearer can be continued, that is, the step s513 is performed, and then the timer is cleared. If it is not complete, reset the timer.

Step s508: The MME sends a Bearer Setup Request to the eNB.

In step s509, the eNB sends a Radio Bearer Establishment Request to the UE. Step s510: The UE sends a Radio Bearer establishment Response to the eNB. In step s511, the eNB sends a Bearer Setup Response to the MME. In step s512, the MME sends an Update Bearer Request to the S-GW.

Step s513: The S-GW sends a Create Dedicated Bearer Request (IMSI, Sl-TEID, QoS, TFT, MSISDN) to the MME.

In this step, the S-GW receives the Update Bearer Request sent by the MME, and satisfies the condition for continuing the dedicated bearer establishment involved in the step s507. Then, the S-GW sends a Create Dedicated Bearer Request to the MME to continue the establishment of the dedicated bearer.

Step s514, the MME constructs a Session Management Configuration element including the UL TFT ₀ MME sends a Bearer Setup Request (Bearer QoS, Session Management Configuration, Sl-TEID, Bearer ID) to the eNB, and the Session Management Configuration includes the NAS parameter, and has the UL TFT. , TI.

Step s515: The eNB maps bearer QoS to Radio Bearer QoS, and then sends a Radio Bearer Setup Request (Radio Bearer QoS, Session Management Configuration, Bearer ID) to the UE. The UE uses the upstream TFT to determine the mapping between the SDF and the radio bearer.

Step s516, the UE layer of the UE generates a Session Management Response cell. The UE then sends a Radio Bearer Setup Response (Session Management Response) to the eNB.

In step s517, the eNB sends a Bearer Setup Response (S 1 -TEID, Session Management Response) to the MME.

Step s518, the MME sends a Create Dedicated Bearer to the Serving GW.

Response ( Sl-TEID, Bearer ID ) message.

In step s519, the Serving GW sends a Create Dedicated Bearer Response (S5/S8-TEID, Bearer ID) to the PDN GW.

Through the description of the foregoing embodiment 3, the S-GW on the network side controls the establishment of the dedicated bearer in the default bearer setup process, and ensures that the establishment of the dedicated bearer in the attach process can be successfully completed. Embodiment 4 of the present invention is a process in which an eNB on the network side controls the establishment of a dedicated bearer in a default bearer setup procedure. The principle is: "The eNB receives the "no" sent from the terminal. Before the line bearer establishes the response to the Radio Bearer Establishment Request message, the eNB saves all the dedicated bearer setup requests for the APN from the MME for the terminal until it receives the "radio bearer (default bearer) setup response sent by the terminal. Radio Bearer Establishment Response" After the message or after the timer expires, the preset condition is judged. If the preset condition is met, the "establish radio bearer (dedicated bearer) request Radio Bearer Setup Request" is sent to the terminal.

The establishment process of the proprietary bearer is shown in Figure 6:

Step s601, the new MME sends a Create Default Bearer Request to the Serving GW.

Step s602, Serving GW sends Create Default Bearer to PDN GW

Request.

Step s603, PDN GW and PCRF are interchanged PCRF Interaction„

Step s604, the PDN GW sends a Create Default Bearer Response to the Serving GW.

Step s605, Serving GW sends Create Default Bearer to new MME

Response.

Step s606, the new MME sends a Bearer Setup Request to the eNB.

Step s607: The P-GW sends a Create Dedicated Bearer Request to the S-GW, and includes the following parameters: IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address, and Linked Bearer ID.

Step s608: The S-GW sends a Create Dedicated Bearer Request to the MME, including the following parameters: IMSI, Sl-TEID, QoS, TFT, MSISDN, Linked Bearer

ID.

Step s609, the MME constructs a Session Management Configuration element including a UL TFT. The MME sends a Bearer Setup Request (Bearer QoS, Session Management Configuration, Sl-TEID, Bearer ID, Linked Bearer ID) to the eNB. The Session Management Configuration contains the NAS parameters, including UL TFT, TI.

After receiving the Dedicated Bearer Setup Request sent by the MME, the eNB checks Whether there is a complete RB Context of the RB ID associated with the Linked Bearer ID on the eNB, if yes, proceed with the establishment of the dedicated bearer, that is, proceed to step s612.

If it does not exist, it proves that the default bearer of the P-GW where the dedicated bearer is located has not been established yet, then save the message, and then decide whether to continue the establishment of the dedicated bearer according to one of the following two methods, that is, Go to step s612.

(1) A flag indicating that the default bearer related to the dedicated bearer is not established is set on the eNB, and after waiting for the UE to send a Radio Bearer Setup Response message, check whether the RB ID corresponding to the message can be saved. The Linked Bearer ID of the message matches. If it matches, the default bearer of the P-GW where the dedicated bearer is located is established. Then, step s612 can be performed. If it does not match, the next Radio Bearer Setup Response message is awaited. .

(2) starting a timer on the eNB, after the timer expires, the eNB checks whether the RB Context related to the Linked Bearer ID carried by the dedicated bearer setup request is complete, and if complete, the proof step After s612 has been executed, the establishment of the dedicated bearer can be continued, that is, step s613 is performed, and then the timer is cleared. If it is not complete, reset the timer.

Step s608, the Serving GW sends a Create Dedicated Bearer Request to the new MME.

Step s609, new MME sends Create Dedicated Bearer to the eNB

Request.

In step s610, the eNB sends a Radio Bearer Establishment Request to the UE. Step s611, the UE sends a Radio Bearer Establishment Response to the eNB. In this step, the eNB receives the Radio Bearer Establishment Response sent by the UE, and satisfies the continuing dedicated bearer involved in step s609. Established conditions.

In step s612, the eNB maps bearer QoS to Radio Bearer QoS, and then sends a Radio Bearer Setup Request (Radio Bearer QoS, Session Management Configuration, Bearer ID) to the UE. The UE uses the upstream TFT to determine the mapping between the SDF and the radio bearer. In step s613, the NAS layer of the UE generates a Session Management Response cell. The UE then sends a Radio Bearer Setup Response (Session Management Response) to the eNB.

Step s614: The eNB sends a Bearer Setup Response (S 1 -TEID, Session Management Response) to the MME.

In step s615, the MME sends a Create Dedicated Bearer Response (SI-TEID, Bearer ID) message to the Serving GW.

Step s616, the Serving GW sends a Create Dedicated Bearer Response (S5/S8-TEID, Bearer ID) to the PDN GW.

Through the description of the foregoing embodiment 4, the eNB of the network side controls the establishment of the dedicated bearer in the default bearer establishment process, and ensures that the establishment of the dedicated bearer in the attach process can be successfully completed. Embodiment 5 of the present invention is a process in which a MME on the network side controls the establishment of a dedicated bearer in a default bearer establishment procedure. The principle is: before the MME receives the "Default Default Response Response Create Default Bearer Response" message sent from the S-GW, the MME saves all the dedicated bearer setup requests for the APN from the S-GW for the terminal. After the MME receives the "Default Bearer Setup Request" message sent by the S-GW, the MME will simultaneously carry the information of the default bearer and the dedicated bearer in the establishment of the radio bearer request, including the IP address allocated by the network for the terminal.

The establishment process of the proprietary bearer is as shown in Figure 7:

Step s701, the new MME sends a Create Default Bearer Request to the Serving GW.

In step s702, the Serving GW sends a Create Default Bearer Request to the PDN GW.

Step s703, PDN GW is interchanged with PCRF PCRF Interaction„

Step s704: The P-GW sends a Create Dedicated Bearer Request to the S-GW, and includes the following parameters: IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address, and Linked Bearer ID. Step s705: The S-GW sends a Create Dedicated Bearer Request to the MME, and includes the following parameters: IMSI, Sl-TEID, QoS, TFT, MSISDN, and Linked Bearer ID.

After receiving the Create Dedicated Bearer Request sent from the S-GW, the MME searches for the user plane TEID of the eNB and the S-GW related to the Linked Bearer ID according to the Linked Bearer ID. If yes, Then, if the verification step s712 has been performed, then the establishment of the dedicated bearer can be continued, that is, the step s712 is performed; if only the user plane TEID of the S-GW is available, the default bearer is in progress s708, step s709, step s710, In step s711, then refer to the processing flow in the second embodiment.

If neither the eNB nor the S-GW has a user plane TEID, the MME keeps this message and waits for the Create Default Bearer Response that is consistent with the Linked Bearer ID in the message. After receiving the message, all MMEs are kept. The dedicated bearer setup request is placed in the Bearer Setup Request and carries an Attach Accept message to the eNB.

Step s706, the PDN GW sends a Create Default Bearer Response to the Serving GW.

In step s707, the Serving GW sends a Create Default Bearer Response to the new MME.

Step s708, if the independent default bearer is established, then the MME sends a Bearer

Setup Request (SAE Bearer setup list), if the default bearer is established in the attach procedure, the MME sends an Initial Context Setup Complete (SAE Bearer setup list) to the eNB.

Step s709, the eNB maps bearer QoS to Radio Bearer QoS, and then sends a Radio Bearer Setup Request (Radio Bearer Setup List) to the UE. The UE uses the upstream TFT to determine the mapping between the SDF and the radio bearer.

Step s710: The UE sends a Radio Bearer Setup Response to the eNB.

Step s711, if the independent default bearer is established, the eNB sends a Bearer Setup Response (eNB TEID, Session Management Response) to the MME, if yes After the default bearer is established in the attach procedure, the eNB sends an Initial Context Setup Complete (eNB TEID, eNB address) to the MME.

Step s712: The MME sends a Create Dedicated Bearer Response (Sc-TEID, Bearer ID) message to the Serving GW.

In step s713, the Serving GW sends a Create Dedicated Bearer Response (S5/S8-TEID, Bearer ID) to the PDN GW.

Through the description of the foregoing embodiment 5, the MME on the network side controls the establishment of the dedicated bearer in the default bearer establishment process, and ensures that the establishment of the dedicated bearer in the attach process can be successfully completed. The sixth embodiment of the present invention provides a network-side control entity, which is used to control the establishment of a dedicated bearer in the process of establishing a default bearer. The structure is as shown in FIG. 8 and includes:

The request receiving unit 10 is configured to receive a dedicated bearer setup request in a default bearer setup process;

The determining unit 20 is configured to: when the request receiving module receives the dedicated bearer setup request, determine, according to the preset condition, whether to continue to establish the dedicated bearer; if yes, notify the processing module to continue to establish the dedicated bearer Otherwise, the notification storage module keeps the dedicated bearer setup request;

The processing unit 30 is configured to continue the establishment process of the dedicated bearer according to the notification of the determining module;

The storage unit 40 is configured to maintain the dedicated bearer setup request according to the notification of the determining module.

Also includes:

The detecting unit 50 is configured to: after the determining unit notifies the storage module to keep the dedicated bearer setup request according to a preset condition, whether the preset condition is reached in real time or periodically, and notify the processing unit to continue when the method is reached. The process of establishing a proprietary bearer.

Specifically, the network side control entity may be a mobility management entity MME, or a service gateway S-GW, or an evolved base station eNB.

Through the description of the above embodiments, those skilled in the art can clearly understand To the present invention, it can be implemented by hardware, or by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present invention can be embodied in the form of a software product that can be stored in a non-volatile storage medium.

(may be a CD-ROM, a USB flash drive, a removable hard drive, etc.), including a number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A control method for establishing a dedicated bearer in a default bearer establishment process, comprising the steps of:

Determining, by the network-side control entity, whether to continue the establishment of the dedicated bearer according to a preset condition, and if yes, proceeding to establish the dedicated bearer; otherwise, maintaining the dedicated bearer setup request until the preset condition is reached. The establishment of the proprietary bearer continues.

2. The control method for establishing a dedicated bearer in the default bearer setup process according to claim 1, wherein the network-side control entity maintains the preset bearer establishment request The method of making the judgment is specifically as follows:

Each time the message sent by another entity is received, the network side control entity checks whether the preset condition is reached; or

The network-side control entity starts a timer locally, and the network-side control entity checks whether the preset condition is reached whenever the timer expires.

The method for controlling the establishment of a dedicated bearer in the default bearer setup process according to claim 1, wherein when the network-side control entity is the mobility management entity MME, the dedicated bearer setup request is a serving gateway. A dedicated bearer request is sent by the S-GW, where the dedicated bearer request includes a link bearer identifier.

The control method for establishing a dedicated bearer in the default bearer setup process according to claim 3, wherein when the network side control entity is an MME, the MME determines whether to continue the proprietary according to a preset condition. The steps for establishing the bearer are specifically as follows:

Determining, by the MME, whether the user plane tunnel end identifier TEID of the evolved base station eNB and the user plane TEID of the S-GW are stored locally;

If it is determined at the same time, it is determined that the preset condition is met, and the establishment of the dedicated bearer is continued, otherwise the dedicated bearer setup request is maintained.

5. The control of establishing a dedicated bearer in the default bearer establishment process according to claim 4 The method is characterized in that, when the network-side control entity is ΜΜΕ, the step of maintaining the dedicated bearer setup request until the preset condition is met, the step of continuing to establish the dedicated bearer is specifically:

When the user plane TEID of the S-GW is stored in the local area, the MME receives the initial context setup response or the bearer setup response sent by the eNB, and the initial context setup response or the bearer setup response includes the user of the eNB. When the TEID is met, it is determined that the preset condition is met, and the establishment of the dedicated bearer is continued;

When the MME does not store the user plane TEID of the eNB and the user plane TEID of the S-GW, the MME determines that the S-GW meets the establishment of the default bearer response that is consistent with the link bearer identifier. The preset condition is to send a radio bearer setup request that carries the default bearer and the dedicated bearer information, and is used to establish the default bearer and the dedicated bearer at the same time.

The control method for establishing a dedicated bearer in the default bearer setup process according to claim 1, wherein when the network-side control entity is an S-GW, the dedicated bearer setup request is a packet data network gateway. The P-GW sends a dedicated bearer request, where the proprietary bearer request includes a link bearer identifier.

The method for controlling the establishment of a dedicated bearer in the default bearer setup process according to claim 6, wherein when the network-side control entity is an S-GW, the S-GW determines whether to continue according to a preset condition. The step of establishing the dedicated bearer is specifically:

The S-GW determines whether the user plane TEID of the eNB related to the link bearer identifier and the user plane TEID of the P-GW are stored locally;

If it is determined at the same time, it is determined that the preset condition is met, and the establishment of the dedicated bearer is continued; otherwise, the dedicated bearer setup request is maintained, and the establishment of the dedicated bearer is continued until the preset condition is reached.

The method for controlling the establishment of a dedicated bearer in the default bearer setup process according to claim 7, wherein when the network-side control entity is an S-GW, the S-GW keeps the dedicated bearer established. The step of requesting to continue the establishment of the dedicated bearer when the preset condition is reached is specifically as follows:

Receiving, by the S-GW, an update bearer request sent by the MME, and the update When the request includes the user plane TEID of the eNB, it is determined that the preset condition is met, and the establishment of the dedicated bearer is continued.

The control method for establishing a dedicated bearer in the default bearer setup process according to claim 1, wherein when the network-side control entity is an eNB, the dedicated bearer setup request is established and established by the MME. The bearer request includes a link 7?

The method for controlling the establishment of a dedicated bearer in the default bearer setup process according to claim 9, wherein when the network side control entity is an eNB, the eNB determines whether to continue the proprietary according to a preset condition. The steps for establishing the bearer are specifically as follows:

Determining, by the eNB, whether a radio bearer context of the radio bearer identifier associated with the link bearer identifier is stored locally;

If yes, it is determined that the preset condition is met, and the establishment of the dedicated bearer is continued, otherwise the dedicated bearer setup request is maintained, and the establishment of the dedicated bearer is continued until the preset condition is reached.

The control method for establishing a dedicated bearer in the default bearer setup process according to claim 10, wherein when the network side control entity is an eNB, the eNB maintains the dedicated bearer setup request until reaching The step of continuing to establish the dedicated bearer when the preset condition is:

When the eNB receives the radio bearer setup response sent by the user terminal UE, and the radio bearer setup response includes the radio bearer context of the radio bearer identifier associated with the link bearer identifier, determining that the preset condition is met, And continue to establish the dedicated bearer.

12. A network-side control entity, configured to control establishment of a dedicated bearer in a default bearer establishment process, and the method includes:

a determining unit, configured to: when the request receiving module receives the dedicated bearer setup request, determine whether to continue to establish the dedicated bearer according to a preset condition; if yes, the notification processing module continues to perform the establishment of the dedicated bearer, Otherwise notify the storage module to keep the special Have a bearer setup request;

And a storage unit, configured to maintain the dedicated bearer setup request according to the notification of the determining module.

The network-side control entity according to claim 12, further comprising: a detecting unit, configured to: after the determining unit notifies the storage module to maintain the dedicated bearer setup request according to a preset condition, real time Or periodically detecting whether the preset condition is reached, and when notified, notifying the processing unit to continue the establishment process of the dedicated bearer.