CN101400148B - Control method and equipment for special bearing establishment in default bearing establishing process - Google Patents
Control method and equipment for special bearing establishment in default bearing establishing process Download PDFInfo
- Publication number
- CN101400148B CN101400148B CN2007101516722A CN200710151672A CN101400148B CN 101400148 B CN101400148 B CN 101400148B CN 2007101516722 A CN2007101516722 A CN 2007101516722A CN 200710151672 A CN200710151672 A CN 200710151672A CN 101400148 B CN101400148 B CN 101400148B
- Authority
- CN
- China
- Prior art keywords
- dedicated bearing
- request
- bearing
- bearer
- foundation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
Abstract
The invention discloses a control method of special bearing building in default bearing building process, comprising that: control entity at the network side receives the special bearing building request in the default bearing building process; the control entity at the network side judges whether continuing building the special bearing according to the preset condition, if true, continuing building the special bearing; otherwise keeping the special bearing building request, till reaching all the preset conditions, continuing building the special bearing. The invention discloses a control device of special bearing building in the default bearing building process, realizing the control on the special bearing building in the in default bearing building process by the entity at the network side, ensuring successfully building the special bearing in attached flow.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of default bearer and set up control method and the equipment that dedicated bearing is set up in the process.
Background technology
In the prior art, (System Architecture Evolution, SAE) attachment flow in comprises the steps: as shown in Figure 1 in System Architecture Evolution
Step s101, subscriber equipment (User Equipment, UE) to evolution base station (Evolved NodeB, eNB) request (Attach Request) (IMSI or S-TMSI and old TAI is adhered in transmission, SelectedNetwork), wherein adhere to request (Attach Request:IMSI or S-TMSI and old TAI, SelectedNetwork) expression is adhered to and is comprised IMSI International Mobile Subscriber Identity (International Mobile Subscriber Identity in the request (Attach Request), IMSI) or Temporary Mobile Subscriber Identity (SAE-Temporary Mobile Subscriber Identity, S-TMSI), and tracing area sign (TrackingArea Identity, old TAI), selected network (Selected Network) below also adopts same format.
Step s102, evolution base station (evolved NodeB, eNB) to new Mobility Management Entity (newMobility Management Entity, new MME) request (Attach Request:IMSIor S-TMSI and old TAI is adhered in transmission, Selected Network, Cell Global identity (cellular global identity)).
Step s103, if new Mobility Management Entity (new MME) does not have the IMSI International Mobile Subscriber Identity (IMSI) of subscriber equipment (UE), send identification request (Identification Request (S-TMSI to old Mobility Management Entity (old MME) so, old TAI)) ask IMSI International Mobile Subscriber Identity (IMSI), if old Mobility Management Entity (old MME) has the IMSI International Mobile Subscriber Identity (IMSI) of this subscriber equipment (UE), so by sending identification response (Identification Response (IMSI, Authentication Quintets)) IMSI International Mobile Subscriber Identity (IMSI) is passed to new Mobility Management Entity (new MME), if no, just return an errored response.
Step s104, if old Mobility Management Entity (old MME) does not have the IMSI International Mobile Subscriber Identity (IMSI) of this subscriber equipment (UE), so new Mobility Management Entity (new MME) sends authentication request (Identification Request) request IMSI International Mobile Subscriber Identity (IMSI) to subscriber equipment (UE), and subscriber equipment (UE) is passed to new Mobility Management Entity (new MME) to IMSI International Mobile Subscriber Identity (IMSI) by returning authentication response (Identification Response) IMSI International Mobile Subscriber Identity (IMSI).
Step s105, if there is not the context of subscriber equipment (UE) in this network, authentication (authentication) process is necessary so.
Step s106 if the bearer context (bearer context) of any activation is arranged in new Mobility Management Entity (new MME), needs to send deleting bearing request (Delete Bearer Request) so and deletes these carryings.
Step s107, if connected (Attach) change or at this moment connected (Attach) for the first time since last time, Mobility Management Entity (MME) need be to attaching position register (Home Subscriber Server so, HSS) (Update Location, MME Identity, IMSI) message is come more new technological process of enable position to send out the renewal location.
Step s108, attaching position register (HSS) is sent out canceling position (Cancel Location (IMSI, Cancellation Type)) message to old Mobility Management Entity (old MME) and is deleted the user signing contract information on old Mobility Management Entity (old MME).Old Mobility Management Entity (oldMME) is sent out canceling position response (Cancel Location Ack (IMSI)) and is given attaching position register (HSS).
Step s109, if the carrying of any activation of subscriber equipment (UE) is arranged on old Mobility Management Entity (old MME), so old Mobility Management Entity (old MME) sends deleting bearing request (Delete Bearer Request) and gives relevant gateway (Serving GateWay, S-GW) and packet data network gateway (P-GW (GateWay of Packet Data Network (PDN (Packet Data Network)))) delete the carrying of activation, gateway (S-GW) and packet data network gateway (P-GW) send deleting bearing response (Delete Bearer Response) and give old Mobility Management Entity (old MME).
Step s110, attaching position register (HSS) sends insertion subscription data (Insert SubscriberData) (IMSI, Subscription Data) and all CAMEL-Subscription-Information is issued new Mobility Management Entity (new MME) for Mobility Management Entity (MME).
Step s111, new Mobility Management Entity (new MME) respond one and insert subscription data response (Insert Subscriber Data Ack) to attaching position register (HSS).
Step s112, (Access Point Network APN) carries out packet data network gateway and selects behavior (P-GW selection) to select packet data network gateway (P-GW) new Mobility Management Entity (new MME) according to signatory access point network.Mobility Management Entity (MME) sends sets up default bearer request (Create Default Bearer Request (IMSI, MME Context ID, bearer id, P-GW address)) to gateway (S-GW).When dedicated bearing needs indication (Dedicated BearerRequired Indication) when being changed to 1, service quality (Quality of Service, QoS) tabulation (list) expression since these specific transactions cause adhere to the needed service quality of dedicated bearing in (Attach) flow process, otherwise do not need this parameter.
Step s113, gateway (S-GW) is set up a record, sends then and sets up default bearer request (Create Default Bearer Request) (gateway (S-GW) chain of command Tunnel End Point Identifier (TEID-C; Tunnel Endpoint Identifier for control plane), gateway (S-GW) user face Tunnel End Point Identifier (TEID-U; Tunnel Endpoint Identifier for user plane), bearing identification (bearer id; Bearer Identifier)) give packet data network gateway (P-GW).
Step s114, packet data network gateway (P-GW) with the strategy with charging rule functions body (PCRF; Policy and Charging Rules Function) carries out asking in the mutual process to obtain the default strategy and the control (PCC that charges; Policy and Charging Control) rule (rule).
Step s115, packet data network gateway (P-GW) sends sets up default bearer response (Create DefaultBearer Response) (PDN GW Address for the user plane, the Tunnel End Point Identifier PDN GW TEID of Packet Data Network (Tunnel Endpoint Identifier) of the user plane, PDN GW TEIDof the control plane, PDN Address) to gateway (S-GW).
Step s116, gateway (S-GW) sends sets up default bearer response (Create Default BearerResponse (PDN Address, Serving GW address for User Plane, Serving GWContext ID)) to new Mobility Management Entity (new MME).
Step s117, new Mobility Management Entity (new MME) send to adhere to evolution base station (eNB) and accept to adhere to request (Attach Accept) (S-TMSI, PDN address, TA List).This message has comprised control messages context foundation request (the Context Setup Request of a S1-Mobility Management Entity (S1-MMS) simultaneously; Bearer id), this message comprises carrying needed service quality (QoS) and user's face Tunnel End Point Identifier (TEID-U) of gateway (S-GW) and user's face address of gateway (S-GW).
Step s118, evolution base station (eNB) send radio bearer and set up request (Radio BearerEstablishment Request; Bearer id) and adhere to acceptance (Attach Accept; S-TMSI, PDNaddress, TA List) message gives subscriber equipment (UE).
Step s119, subscriber equipment (UE) send radio bearer and set up response (Radio BearerEstablishment Response) message to evolution base station (eNB).
Step s120, evolution base station (eNB) send to adhere to and finish (Attach Complete; ENB TEID, eNB address for control plane) to new Mobility Management Entity (new MME).
Step s121, new Mobility Management Entity (new MME) sends more new bearer request (UpdateBearer Request; ENB address, eNB TEID) to gateway (S-GW).Evolution base station Tunnel End Point Identifier tabulation (eNB TEID list) is the evolution base station Tunnel End Point Identifier (eNB TEID) to dedicated bearing.This evolution base station Tunnel End Point Identifier (eNB TEID) is the Tunnel End Point Identifier (TEID) of default bearer.
Step s122, gateway (S-GW) send more new bearer response (Update Bearer Response) and give Mobility Management Entity (MME).
In said system architecture evolution (SAE) attachment flow, the interaction triggers of packet data network gateway among the step s114 (P-GW) and strategy and charging rule functions body (PCRF) is understood the foundation of some dedicated bearer.Dedicated bearing in the System Architecture Evolution (SAE) is set up flow process as shown in Figure 2:
Step s201, strategy sends strategy with charging rule functions body (PCRF) and gives packet data network gateway (P-GW) with control conclusion clause (PCC decision provision) (quality of service policy, QoS policy, the qos policy) message of chargeing.If do not have the strategy and control (PCC) framework that charges, packet data network gateway (P-GW) oneself produces a quality of service policy (QoS policy) so.
Step s202, packet data network gateway (P-GW) produces bearer quality of service (bearer QoS) with this quality of service policy (QoS policy), packet data network gateway (P-GW) is sent out one and is created dedicated bearing request (Create Dedicated Bearer Request) (Bearer QoS, UL TFT S5/S8TEID) gives gateway (Serving GW).
Step s203, gateway (Serving GW) send and create dedicated bearing request (CreateDedicated Bearer Request) (Bearer QoS, up (UL; Uplink) Traffic Profile (TFT, Traffic Flow Template), Tunnel End Point Identifier (S1-TEID)) message is given Mobility Management Entity (MME).
Step s204, a session management configuration of Mobility Management Entity (MME) structure (SessionManagement Configuration) cell comprises uplink traffic template (UL TFT).Mobility Management Entity (MME) sends carrying foundation request (Bearer Setup Request), and (Bearer QoS, SessionManagement Configuration S1-TEID) give evolution base station (eNB).
Step s205, evolution base station (eNB) mapping carrying quality services (bearer QoS) is to radio bearer quality services (Radio Bearer QoS), send radio bearer then and set up request (Radio BearerSetup Request) (Radio Bearer QoS, Session Management Configuration) to subscriber equipment (UE).Subscriber equipment (UE) uses uplink traffic template (TFT) to decide SDF to the mapping between the radio bearer (radio bearer).
Step s206, the NAS layer of subscriber equipment (UE) produce session management configuration (SessionManagement Response) cell.Subscriber equipment (UE) is set up response (Radio Bearer Setup Response) (Session ManagementResponse) so send out radio bearer to evolution base station (eNB).
Step s207, evolution base station (eNB) is sent out bearer update request (Bearer Setup Response) (S1-TEID, Session Management Response) to Mobility Management Entity (MME).
Step s208, Mobility Management Entity (MME) send out to gateway (Serving GW) and create (S1-TEID) message of dedicated bearing request (Create Dedicated Bearer Response).
Step s209, gateway (Serving GW) send out to packet data network gateway (PDN GW) and create dedicated bearing request (Create Dedicated Bearer Response) (S5/S8-TEID).
Step s210, if this dedicated bearing is to control conclusion clause (PCC Decision Provision) message trigger from the strategy that strategy and charging rule functions body (PCRF) are sent with charging, packet data network gateway (PDN GW) wants notification strategy and a clause response of charging rule functions body (PCRF) (Provision Ack) message to tell strategy and charging rule functions body (PCRF) strategy whether its is asked and the control conclusion (PCC decision) (quality of service policy (QoS policy)) of chargeing to be performed so.
As mentioned above, in present System Architecture Evolution (SAE) attachment flow, mutual (the step s114) of packet data network gateway (P-GW) and strategy and charging rule functions body (PCRF) can trigger the foundation of some dedicated bearer.But, to set up and terminal is received to adhere to and accepted message (step s118) before at radio bearer, terminal can't know that network is its IP address allocated.If dedicated bearer is based upon terminal and learns that network is that its IP address allocated sends to terminal before, can cause potential problem (can't finish the configuration of IP filter such as terminal in application layer).Therefore, the dedicated bearer that must have corresponding mechanism to guarantee that step s114 triggers is based upon that terminal sends to terminal after receiving the IP address among the step s118, sets up required condition and can satisfy to guarantee dedicated bearing.
Summary of the invention
Embodiments of the invention provide a kind of default bearer to set up dedicated bearing is set up in the process control method and equipment, and the dedicated bearing foundation that is used for process that default bearer is set up is controlled.
For achieving the above object, embodiments of the invention provide a kind of default bearer to set up the control method that dedicated bearing is set up in the process, may further comprise the steps:
The network controls entity is set up at default bearer and is received dedicated bearing foundation request in the process;
Described network controls entity is according to the pre-conditioned foundation that judges whether to continue described dedicated bearing, if then proceed the foundation of described dedicated bearing; Otherwise keep described dedicated bearing to set up request, until reaching the described foundation of proceeding described dedicated bearing when pre-conditioned.
Embodiments of the invention also provide a kind of network controls entity, and the dedicated bearing foundation that is used for process that default bearer is set up is controlled, and comprising:
The request receiving element is used for setting up process at default bearer and receives dedicated bearing foundation request;
Judging unit is used for when the described request receiver module receives dedicated bearing foundation request, according to the pre-conditioned foundation that judges whether to continue described dedicated bearing; If then notification handler module is proceeded the foundation of described dedicated bearing, otherwise the notice memory module keeps described dedicated bearing to set up request;
Processing unit is used for continuing according to the notice of described judge module the flow process of setting up of dedicated bearing;
Memory cell is used for keeping described dedicated bearing to set up request according to the notice of described judge module.
Compared with prior art, embodiments of the invention have the following advantages:
When default bearer is set up the foundation request that receives dedicated bearing in the process, at first dedicated bearing is set up required condition and judge and check, as set up the required address of dedicated bearing etc., the dedicated bearing that satisfies condition is proceeded to set up; Realized setting up effective control of in the flow process dedicated bearing being set up at default bearer, guaranteed that the foundation of dedicated bearing can be finished smoothly by the network controls entity.
Description of drawings
Fig. 1 is the attachment flow of System Architecture Evolution in the prior art (SAE);
Fig. 2 is that the dedicated bearing in the System Architecture Evolution in the prior art (SAE) is set up flow process;
Fig. 3 is a control method flow chart of setting up the foundation of dedicated bearing in the process in the embodiments of the invention one at default bearer;
Fig. 4 is a control method flow chart of setting up the foundation of dedicated bearing in the process in the embodiments of the invention two at default bearer;
Fig. 5 is a control method flow chart of setting up the foundation of dedicated bearing in the process in the embodiments of the invention three at default bearer;
Fig. 6 is a control method flow chart of setting up the foundation of dedicated bearing in the process in the embodiments of the invention four at default bearer;
Fig. 7 is a control method flow chart of setting up the foundation of dedicated bearing in the process in the embodiments of the invention five at default bearer;
Fig. 8 is the structural representation of network controls entity in the embodiments of the invention six.
Embodiment
In the embodiments of the invention one, provide a kind of and set up the control method of the foundation of dedicated bearing in the process at default bearer, its flow process may further comprise the steps as shown in Figure 3:
Step s301, network controls entity are set up at default bearer and are received dedicated bearing foundation request in the process.
Step s302, network controls entity if then carry out step s303, otherwise carry out step s304 according to the pre-conditioned foundation that judges whether to continue this dedicated bearing.
Step s303, proceed the foundation of described dedicated bearing.
Step s304, keep this dedicated bearing to set up request, when reaching pre-conditioned, proceed the foundation of described dedicated bearing.
In the embodiments of the invention two, for the Mobility Management Entity (MME) of network side is set up the process that foundation is controlled to dedicated bearing in the flow process at default bearer.Its principle is: before Mobility Management Entity (MME) is received " response is set up in carrying " message of evolution base station (eNB) transmission, Mobility Management Entity (MME) is preserved all dedicated bearers request of setting up at this access point network (APN) of this terminal that receives from gateway (S-GW), after " carrying set up response (Bearer Setup Response) or initial context set up finish (Initial Context Setup Complete) " message that Mobility Management Entity (MME) receives that evolution base station (eNB) sends or after the timer expiry, just can judge pre-conditioned, if condition is set up, send " setting up dedicated bearer request (Create Dedicated Bearer Request) " message to evolution base station (eNB) so.
This dedicated bearing set up flow process as shown in Figure 4, solid line wherein partly represents to set up the related procedure of default bearer, dotted portion represents to set up the related procedure of dedicated bearing, comprises the steps:
Step s401, Mobility Management Entity (MME) sends the default bearer request (Create Default Bearer Request) of setting up to gateway (Serving GW).
Step s402, gateway (Serving GW) sends the default bearer request (Create Default Bearer Request) of setting up to packet data network gateway (P-GW).
Step s403, packet data network gateway (P-GW) is carrying out asking to obtain default strategy and charging control rule (PCC rule) in the mutual process with strategy and charging rule functions body (PCRF).
Step s404, packet data network gateway (P-GW) send and set up default bearer response (CreateDefault Bearer Response) to gateway (S-GW).
Step s405, gateway (S-GW) send and set up default bearer response (Create Default BearerResponse) to Mobility Management Entity (MME).
Step s406, packet data network gateway (P-GW) sends to gateway (S-GW) and sets up dedicated bearing request (Create Dedicated Bearer Request (S5/S8-TEID, QoS, TFT, MSISDN, Linked Bearer ID)), this sets up the bearing identification (Bearer ID) that the parameter link bearing identification (Linked Bearer ID) that comprises in the dedicated bearer request refers to the default bearer on this packet data network gateway (PDN-GW).
Need to prove that step s406 is triggered by the strategy among the step s403 and charging rule functions body (PCRF) reciprocal process, so its order may be positioned at before the step s404, also may be positioned at after step s404 or the step s405.
Step s407, gateway (S-GW) sends the dedicated bearing request of setting up (Create Dedicated Bearer Request (S1-TEID, QoS, TFT, MSISDN)) to Mobility Management Entity (MME).
Need to prove that step s407 is positioned at after the step s406, but the sequential relationship of step s407 and step s404 and step s405 and uncertain.
After Mobility Management Entity (MME) is received the dedicated bearer request of setting up (Create Dedicated Bearer Request) of sending from gateway (S-GW), whether store link bearing identification (Linked Bearer ID) according to Mobility Management Entity (MME), and whether existed with this and linked the relevant evolution base station (eNB) of bearing identification (Linked Bearer ID) and user's face Tunnel End Point Identifier (TEID) of gateway (S-GW), if all exist, prove that so the default bearer foundation among step s408～s411 is finished, can proceed the foundation of dedicated bearing, promptly carry out step s412.Relevant explanation about this link bearing identification (Linked Bearer ID) is as follows: finish the foundation of default bearer (Default Bearer) when Mobility Management Entity (MME) after, can on Mobility Management Entity (MME), preserve context (Bearer Context) about this default bearer, the sign (Bear ID) that comprises default bearer in the context of this default bearer (Bearer Context), relevant evolution base station (eNB) and user's face Tunnel End Point Identifier (TEID) of gateway (S-GW), the foundation of all proprietary link bearing identifications (Linked Bearer ID) all needs the sign (Bear ID) of this default bearer, relevant evolution base station (eNB) and user's face Tunnel End Point Identifier (TEID) of gateway (S-GW).Therefore Mobility Management Entity (MME) needs to wait for the foundation that can proceed dedicated bearing after default bearer is set up.
If there is no, Mobility Management Entity (MME) keeps this to set up dedicated bearing request (Create Dedicated Bearer Request) message so, uses a kind of continuation that triggers dedicated bearing in following two kinds of methods to set up:
(1) puts a relevant default bearer of this dedicated bearing of expression and do not set up the flag bit of finishing, wait for then evolution base station (eNB) send the message that can bring this default bearer user plane information as: initial context sets up request (Initial Context Setup Request) or response (BearerSetup Response) is set up in carrying, if such message of receiving, judge whether to check the downlink user surface information that has brought this carrying in such message according to the flag bit of having put so, include but not limited to: user's face Tunnel End Point Identifier (TEID) of evolution base station (eNB), prove that so step s411 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s412.Remove this flag bit then.
(2) go up timer of startup at Mobility Management Entity (MME), when this timer to after date, Mobility Management Entity (MME) check with this dedicated bearing that keeps set up ask with whether link the relevant bearer context (Bearer Context) of bearing identification (Linked Bearer ID) complete, if it is complete, prove that then step s411 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s412, remove this timer then.If imperfect, the timer of then resetting.
Step s408, Mobility Management Entity (MME) sends carrying to evolution base station (eNB) and sets up request (Bearer Setup Request) message.
Step s409, eNB send radio bearer and set up request (Radio Bearer EstablishmentRequest) to subscriber equipment (UE).
Step s410, subscriber equipment (UE) sends radio bearer to evolution base station (eNB) and sets up response (Radio Bearer establishment Response) message.
Step s411, evolution base station (eNB) send carrying and set up response (Bearer Setup Response) message to Mobility Management Entity (MME).
Step s412, a session management configuration of Mobility Management Entity (MME) structure (SessionManagement Configuration) cell comprises uplink traffic template UL TFT.Mobility Management Entity (MME) sends sets up default request (Bearer Setup Request) (Bearer QoS, SessionManagement Configuration, S1-TEID,) to evolution base station (eNB), what session management configuration (Session Management Configuration) comprised is the NAS parameter, UL TFT is arranged, TI.
Step s413, evolution base station (eNB) sends radio bearer to subscriber equipment (UE) and sets up request message (Radio Bearer Setup Request).
Step s414, evolution base station (eNB) mapping bearer quality of service (bearer QoS) is to radio bearer service quality (Radio Bearer QoS), send radio bearer then and set up request (Radio BearerSetup Request) (Radio Bearer QoS, Session Management Configuration) to subscriber equipment (UE).Subscriber equipment (UE) uses uplink traffic template (TFT) to decide SDF to the mapping between the radio bearer (radio bearer).
Step s415, the NAS layer of subscriber equipment (UE) produce session management configuration (SessionManagement Response) cell.Subscriber equipment (UE) is set up response (Radio Bearer Setup Response) (Session ManagementResponse) so send radio bearer to evolution base station (eNB).
Step s416, evolution base station (eNB) sends carrying to Mobility Management Entity (MME) and sets up response (Bearer Setup Response) (S1-TEID, Session Management Response).
Step s417, Mobility Management Entity (MME) send to gateway (Serving GW) and set up dedicated bearing response (Create Dedicated Bearer Response) (S1-TEID, Bearer ID) message.
Step s418, gateway (Serving GW) to packet data network gateway (PDN GW) send set up proprietary default response (Create Dedicated Bearer Response) (S5/S8-TEID, BearerID).
By the description of the foregoing description two, realized default bearer being set up in the flow process dedicated bearing set up controlling by the Mobility Management Entity (MME) of network side, guaranteed that the foundation of the dedicated bearing in the attachment flow can be finished smoothly.
In the embodiments of the invention three, for the gateway (S-GW) of network side is set up the process that foundation is controlled to dedicated bearing in the flow process at default bearer.Its principle is: when gateway (S-GW) receives that " upgrade default bearer request (Update Default BearerRequest) " of sending from Mobility Management Entity (MME) before, gateway (S-GW) can be preserved all dedicated bearers request of setting up at this access point network (APN) of this terminal that comes from packet data network gateway (P-GW), receive that up to it " upgrading default bearer request message (Update BearerRequest) " that Mobility Management Entity (MME) sends is afterwards or after the timer expiry, just can judge pre-conditioned, if condition is set up, then send " setting up dedicated bearer request (Create Dedicated BearerRequest) " message to Mobility Management Entity (MME).
This dedicated bearing set up flow process as shown in Figure 5:
Step s501, subscriber equipment (UE) sends the default bearer request (Create Default Bearer Request) of setting up to Mobility Management Entity (MME).
Step s502, Mobility Management Entity (MME) sends the default bearer request (Create Default Bearer Request) of setting up to gateway (Serving GW).
Step s503, gateway (Serving GW) sends the default bearer request (Create Default Bearer Request) of setting up to Data packet network gateway (P-GW).
Step s504, packet data network gateway (P-GW) carries out information interaction (PCRF Interaction) with strategy and charging rule functions body (PCRF).
Step s505, packet data network gateway (P-GW) sends default bearer response (the Create Default Bearer Response) information of setting up to gateway (Serving GW).
Step s506, gateway (Serving GW) sends default bearer response (the Create Default Bearer Response) information of setting up to Mobility Management Entity (MME).
Step s507, packet data network gateway (P-GW) send to gateway (S-GW) and set up dedicated bearing request (Create Dedicated Bearer Request), comprise following parameter: (IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address).
After gateway (S-GW) is received the dedicated bearing request of setting up (Create Dedicated Bearer Request) of sending from packet data network gateway (P-GW), Linked Bearer ID according to the inside, whether had with this inside seeking and linked the relevant evolution base station (eNB) of bearing identification (Linked Bearer ID) and user's face Tunnel End Point Identifier (TEID) of packet data network gateway (P-GW), if all exist, prove that so step s512 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s513;
If there is no, gateway (S-GW) keeps this message so, whether proceeds the foundation of dedicated bearing then according to a kind of decision in following two kinds of methods, promptly carries out step s513.
(1) puts a relevant default bearer of this dedicated bearing of expression and do not set up the flag bit of finishing, wait for that then Mobility Management Entity (MME) sends more new bearer request (Update Bearer Request), if received, judge whether to check that according to the flag bit of having put bar message brought user's downlink user surface information so, include but not limited to: user's face Tunnel End Point Identifier (TEID) of evolution base station (eNB), if brought user's face Tunnel End Point Identifier (TEID) of the evolution base station (eNB) of this default bearer, prove that so step s512 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s513, remove this flag bit then.
(2) go up timer of startup at gateway (S-GW), when this timer to after date, gateway (S-GW) check with this dedicated bearing that keeps set up ask with whether link the relevant bearer context (Bearer Context) of bearing identification (Linked Bearer ID) complete, if it is complete, prove that then step s512 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s513, remove this timer then.If imperfect, the timer of then resetting.
Step s508, Mobility Management Entity (MME) sends more new bearer request (Bearer Setup Request) to evolution base station (eNB).
Step s509, evolution base station (eNB) sends radio bearer to subscriber equipment (UE) and sets up request (Radio Bearer Establishment Request).
Step s510, subscriber equipment (UE) sends radio bearer to evolution base station (eNB) and sets up response (Radio Bearer establishment Rsponse).
Step s511, evolution base station (eNB) sends carrying to Mobility Management Entity (MME) and sets up response (Bearer Setup Response).
Step s512, Mobility Management Entity (MME) sends more new bearer request (Update Bearer Request) to gateway (S-GW).
Step s513, gateway (S-GW) to Mobility Management Entity (MME) send the dedicated bearing request (Create Dedicated Bearer Request) of setting up (IMSI, S1-TEID, QoS, TFT, MSISDN).
In this step, gateway (S-GW) has received the more new bearer request (Update Bearer Request) that Mobility Management Entity (MME) sends, satisfied the condition of the continuation dedicated bearing foundation that relates among the step s507, then gateway (S-GW) sends the dedicated bearing request of setting up (Create Dedicated Bearer Request) to Mobility Management Entity (MME), continues the foundation of dedicated bearing.
Step s514, a session management configuration of Mobility Management Entity (MME) structure (SessionManagement Configuration) cell comprises uplink traffic template (UL TFT).Mobility Management Entity (MME) sends more new bearer request (Bearer Setup Request) (Bearer QoS, SessionManagement Configuration, S1-TEID, Bearer ID) gives evolution base station (eNB), what session management configuration (Session Management Configuration) comprised is the NAS parameter, UL TFT is arranged, TI.
Step s515, evolution base station (eNB) mapping carrying quality services (bearer QoS) is to radio bearer quality services (Radio Bearer QoS), send radio bearer then and set up request (Radio BearerSetup Request) (Radio Bearer QoS, Session Management Configuration BearerID) gives subscriber equipment (UE).Subscriber equipment (UE) uses uplink traffic template (TFT) to decide SDF to the mapping between the radio bearer (radio bearer).
Step s516, the NAS layer of subscriber equipment (UE) produce a session management configuration cell (SessionManagement Response).Subscriber equipment (UE) is so send out radio bearer update request (Radio Bearer Setup Response) (Session Management Response) to evolution base station (eNB).
Step s517, evolution base station (eNB) is sent out carrying to Mobility Management Entity (MME) and is set up response (Bearer Setup Response) (S1-TEID, Session Management Response).
Step s518, Mobility Management Entity (MME) send out to gateway (Serving GW) and set up dedicated bearing response message (Create Dedicated Bearer Response) (S1-TEID, Bearer ID).
Step s519, gateway (Serving GW) to packet data network gateway (PDN GW) send out set up dedicated bearing response (Create Dedicated Bearer Response) (S5/S8-TEID, BearerID).
By the description of the foregoing description three, realized default bearer being set up in the flow process dedicated bearing set up controlling by the gateway (S-GW) of network side, guaranteed that the foundation of the dedicated bearing in the attachment flow can be finished smoothly.
In the embodiments of the invention four, for the evolution base station (eNB) of network side is set up the process that foundation is controlled to dedicated bearing in the flow process at default bearer.Its principle is: before evolution base station (eNB) is received " radio bearer is set up response (Radio Bearer Establishment the Request) " message that sends from terminal, evolution base station (eNB) is preserved all dedicated bearers request of setting up at this access point network (APN) of this terminal that comes from Mobility Management Entity (MME), after it receives " radio bearer (default bearer) is set up response (Radio Bearer Establishment Response) " message that terminal sends or after the timer expiry, just can judge pre-conditioned, if pre-conditioned establishment then sends " setting up radio bearer (dedicated bearer) request (Radio Bearer Setup Request) " to terminal.
This dedicated bearing set up flow process as shown in Figure 6:
Step s601, new Mobility Management Entity (newMME) sends the default bearer request (Create Default Bearer Request) of setting up to gateway (Serving GW).
Step s602, gateway (Serving GW) sends the default bearer request (Create Default Bearer Request) of setting up to packet data network gateway (PDN GW).
Step s603, packet data network gateway (PDN GW) exchanges strategy and charging rule functions body mutual (PCRF Interaction) with strategy and charging rule functions body (PCRF).
Step s604, packet data network gateway (PDN GW) send to gateway (Serving GW) and set up default bearer response (Create Default Bearer Response).
Step s605, gateway (Serving GW) send to new Mobility Management Entity (new MME) and set up default bearer response (Create Default Bearer Response).
Step s606, new Mobility Management Entity (new MME) sends the carrying request (Bearer Setup Request) of setting up to evolution base station (eNB).
Step s607, packet data network gateway (P-GW) sends the dedicated bearing request (Create Dedicated Bearer Request) of setting up to gateway (S-GW), comprise following parameter: (IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address, Linked Bearer ID).
Step s608, gateway (S-GW) sends the dedicated bearing request of setting up (Create Dedicated Bearer Request) to Mobility Management Entity (MME), comprises following parameter: (IMSI, S1-TEID, QoS, TFT, MSISDN, Linked Bearer ID).
Step s609, Mobility Management Entity (MME) session management configuration cell of structure (SessionManagement Configuration) comprises uplink traffic template (UL TFT).Mobility Management Entity (MME) sends carrying and sets up request (Bearer Setup Request) (Bearer QoS, SessionManagement Configuration, S1-TEID, Bearer ID, Linked Bearer ID) give evolution base station (eNB), what comprise is the NAS parameter to session management configuration cell (Session Management Configuration), and UL TFT is arranged, TI
After evolution base station (eNB) is received the dedicated bearing request of setting up (Dedicated Bearer Setup Request) that Mobility Management Entity (MME) sends, check the RB Context that whether has the complete RB ID relevant on the evolution base station (eNB) with linking bearing identification (Linked Bearer ID), if exist, proceed the foundation of this dedicated bearing so, promptly carry out step s612.
If there is no, the default bearer that proves the packet data network gateway (P-GW) at this dedicated bearing place does not also have to set up to finish, preserve this message so, whether proceed the foundation of dedicated bearing then according to a kind of decision in following two kinds of methods, promptly carry out step s612.
(1) on evolution base station (eNB), puts a relevant default bearer of this dedicated bearing of expression and do not set up the flag bit of finishing, after waiting for that subscriber equipment (UE) is sent radio bearer foundation request (RadioBearer Setup Response) message, whether the RB ID that checks this message correspondence can mate with the link bearing identification (Linked Bearer ID) of this message of preserving, if coupling, the default bearer that then proves the packet data network gateway (P-GW) at this dedicated bearing place is built up, can carry out step s612 so, if do not match, wait for that then next bar radio bearer sets up response message (Radio BearerSetup Response).
(2) go up timer of startup at evolution base station (eNB), when this timer to after date, evolution base station (eNB) check with this dedicated bearing that keeps set up ask with whether link the relevant RB Context of bearing identification (LinkedBearer ID) complete, if it is complete, prove that then step s612 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s613, remove this timer then.If imperfect, the timer of then resetting.
Step s608, gateway (Serving GW) sends the dedicated bearing request (Create Dedicated Bearer Request) of setting up to new Mobility Management Entity (new MME).
Step s609, new Mobility Management Entity (new MME) send to evolution base station (eNB) and set up dedicated bearing request Create Dedicated Bearer Request.
Step s610, eNB sends radio bearer to subscriber equipment (UE) and sets up request Radio BearerEstablishment Request.
Step s611, subscriber equipment (UE) sends radio bearer to evolution base station (eNB) and sets up response Radio Bearer Establishment Response.
In this step, evolution base station (eNB) has received the radio bearer foundation response (Radio Bearer Establishment Response) that subscriber equipment (UE) sends, and has satisfied the condition of the continuation dedicated bearing foundation that relates among the step s609,
Step s612, evolution base station (eNB) mapping carrying quality services (bearer QoS) is to radio bearer quality services (Radio Bearer QoS), send radio bearer then and set up request (Radio BearerSetup Request) (Radio Bearer QoS, Session Management Configuration BearerID) gives subscriber equipment (UE).Subscriber equipment (UE) uses uplink traffic template (TFT) to decide SDF to the mapping between the radio bearer (radio bearer).
Step s613, the NAS layer of subscriber equipment (UE) produce session management configuration cell (SessionManagement Response) cell.Subscriber equipment (UE) is set up response (Radio Bearer Setup Response) (Session ManagementResponse) so send out radio bearer to evolution base station (eNB).
Step s614, evolution base station (eNB) is sent out carrying to Mobility Management Entity (MME) and is set up response (Bearer Setup Response) (S1-TEID, Session Management Response).
Step s615, Mobility Management Entity (MME) send out to gateway (Serving GW) and set up dedicated bearing response (Create Dedicated Bearer Response) message (S1-TEID, Bearer ID).
Step s616, gateway (Serving GW) to packet data network gateway (PDN GW) send out set up dedicated bearing response (Create Dedicated Bearer Response) (S5/S8-TEID, BearerID).
By the description of the foregoing description four, realized default bearer being set up in the flow process dedicated bearing set up controlling by the evolution base station (eNB) of network side, guaranteed that the foundation of the dedicated bearing in the attachment flow can be finished smoothly.
In the embodiments of the invention five, for the Mobility Management Entity (MME) of network side is set up the process that foundation is controlled to dedicated bearing in the flow process at default bearer.Its principle is: Mobility Management Entity (MME) is before receiving " default bearer is set up response (Create DefaultBearer the Response) " message that sends from gateway (S-GW), Mobility Management Entity (MME) is preserved all dedicated bearers request of setting up at this access point network (APN) of this terminal that comes from gateway (S-GW), when Mobility Management Entity (MME) receive that gateway (S-GW) sends " after default bearer sets up request information; Mobility Management Entity (MME) can carry default bearer and dedicated bearer simultaneously in setting up the radio bearer request information comprises that network is the IP address of terminal distribution.
This dedicated bearing set up flow process as shown in Figure 7:
Step s701, new Mobility Management Entity (new MME) sends default bearer to gateway (Serving GW) and sets up request (Create Default Bearer Request).
Step s702, gateway (Serving GW) sends default bearer to packet data network gateway (PDN GW) and sets up request (Create Default Bearer Request).
Step s703, packet data network gateway (PDN GW) exchanges (PCRF Interaction) with strategy and charging rule functions body (PCRF).
Step s704, packet data network gateway (P-GW) sends the dedicated bearing request (Create Dedicated Bearer Request) of setting up to gateway (S-GW), comprise following parameter: (IMSI, S5/S8-TEID, QoS, TFT, MSISDN, P-GW address, Linked Bearer ID).
Step s705, gateway (S-GW) sends the dedicated bearing request of setting up (Create Dedicated Bearer Request) to Mobility Management Entity (MME), comprises following parameter: (IMSI, S1-TEID, QoS, TFT, MSISDN, Linked Bearer ID).
After Mobility Management Entity (MME) is received the dedicated bearing request of setting up (Create Dedicated Bearer Request) of sending from gateway (S-GW), link bearing identification (LinkedBearer ID) according to the inside, whether had with this inside seeking and linked the relevant evolution base station (eNB) of bearing identification (Linked Bearer ID) and user's face Tunnel End Point Identifier (TEID) of gateway (S-GW), if all exist, prove that so step s712 is finished, so just can proceed the foundation of dedicated bearing, promptly carry out step s712; If have only user's face Tunnel End Point Identifier (TEID) of gateway (S-GW), illustrate that so default bearer is carrying out step s708, step s709, step s710 is among the step s711, so referring to the handling process among the embodiment two.
If user's face Tunnel End Point Identifier (TEID) of evolution base station (eNB) and gateway (S-GW) does not all have, Mobility Management Entity (MME) keeps this message so, and then wait is set up response (CreateDefault Bearer Response) with the consistent default bearer of bearing identification (Linked Bearer ID) that links in this message, by the time receive after this message, the dedicated bearing request of setting up that all being moved property management entities (MME) are kept is placed on carrying foundation request (Bearer SetupRequest) the inside together, and carry connection request message (Attach Accept), issue evolution base station (eNB).
Step s706, packet data network gateway (PDN GW) sends default bearer to gateway (Serving GW) and sets up response (Create Default Bearer Response).
Step s707, gateway (Serving GW) sends default bearer to new Mobility Management Entity (new MME) and sets up response (Create Default Bearer Response).
Step s708, if independent default bearer is set up, Mobility Management Entity (MME) sends carrying and sets up request (Bearer Setup Request) (SAE Bearer setup list) so, if the default bearer in attachment flow is set up, Mobility Management Entity (MME) sends initial context foundation and finishes (Initial Context Setup Complete) (SAE Bearer setup list) to evolution base station (eNB) so.
Step s709, evolution base station (eNB) mapping carrying quality services (bearer QoS) sends radio bearer foundation request (Radio BearerSetup Request) (Radio Bearer Setup List) then and gives subscriber equipment (UE) to radio bearer quality services (Radio Bearer QoS).Subscriber equipment (UE) uses uplink traffic template (TFT) to decide SDF to the mapping between the radio bearer (radio bearer).
Step s710, subscriber equipment (UE) sends radio bearer to evolution base station (eNB) and sets up response (Radio Bearer Setup Response).
Step s711, if independent default bearer is set up, evolution base station (eNB) sends carrying to Mobility Management Entity (MME) and sets up response (Bearer Setup Response) (eNB TEID, SessionManagement Response), if the default bearer in attachment flow is set up, evolution base station (eNB) is sent out initial context foundation to Mobility Management Entity (MME) and is finished (Initial ContextSetup Complete) (eNB TEID, eNB address) so.
Step s712, Mobility Management Entity (MME) send to gateway (Serving GW) and set up dedicated bearing response (Create Dedicated Bearer Response) (S1-TEID, Bearer ID) message.
Step s713, gateway (Serving GW) to packet data network gateway (PDN GW) send set up dedicated bearing response (Create Dedicated Bearer Response) (S5/S8-TEID, BearerID).
By the description of the foregoing description five, realized default bearer being set up in the flow process dedicated bearing set up controlling by the Mobility Management Entity (MME) of network side, guaranteed that the foundation of the dedicated bearing in the attachment flow can be finished smoothly.
Embodiments of the invention six provide a kind of network controls entity, and the dedicated bearing foundation that is used for process that default bearer is set up is controlled, and its structure comprises as shown in Figure 8:
Request receiving element 10 is used for setting up process at default bearer and receives dedicated bearing foundation request;
Judging unit 20 is used for when the described request receiver module receives dedicated bearing foundation request, according to the pre-conditioned foundation that judges whether to continue described dedicated bearing; If then notification handler module is proceeded the foundation of described dedicated bearing, otherwise the notice memory module keeps described dedicated bearing to set up request;
Processing unit 30 is used for continuing according to the notice of described judge module the flow process of setting up of dedicated bearing;
Also comprise:
Detecting unit 50, be used for described judging unit according to pre-conditioned notify described memory module to keep described dedicated bearing to set up request after, detect described pre-conditioned whether reaching in real time or regularly, notify described processing unit to continue the flow process of setting up of dedicated bearing when reaching.
Concrete, this network controls entity can be Mobility Management Entity MME or gateway S-GW or evolution base station eNB.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium, comprises that some instructions are used so that a network equipment is carried out the described method of each embodiment of the present invention.
More than disclosed only be several specific embodiment of the present invention, still, the present invention is not limited thereto, any those skilled in the art can think variation all should fall into protection scope of the present invention.
Claims (13)
1. a default bearer is set up the control method that dedicated bearing is set up in the process, it is characterized in that, may further comprise the steps:
The network controls entity is set up at default bearer and is received dedicated bearing foundation request in the process;
Described network controls entity is set up the foundation whether required condition judgment continues described dedicated bearing according to described dedicated bearing, if then proceed the foundation of described dedicated bearing; Otherwise keep described dedicated bearing to set up request, until reaching the foundation of proceeding described dedicated bearing when described dedicated bearing is set up required condition.
2. default bearer is set up the control method that dedicated bearing is set up in the process according to claim 1, it is characterized in that, after described network controls entity keeps described dedicated bearing to set up request, described until reaching the foundation of proceeding described dedicated bearing when described dedicated bearing is set up required condition, be specially:
When receiving the message that other entities send, described network controls entity is set up required condition and is checked whether reaching described dedicated bearing at every turn; Or
Described network controls entity starts a timer in this locality, when described timer expired, described network controls entity was set up required condition and checked whether reaching described dedicated bearing.
3. default bearer is set up the control method that dedicated bearing is set up in the process according to claim 1, it is characterized in that, when described network controls entity is Mobility Management Entity MME, described dedicated bearing is set up request for the dedicated bearing request of setting up that gateway S-GW sends, and comprises the link bearing identification in the described dedicated bearing request.
4. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 3, it is characterized in that, when described network controls entity was MME, described MME set up the step whether required condition judgment continues the foundation of described dedicated bearing according to described dedicated bearing, is specially:
Described MME judges local whether preserving and described user's face Tunnel End Point Identifier TEID of the relevant evolution base station eNB of bearing identification and the user's face TEID of S-GW of linking;
Satisfy described dedicated bearing and set up required condition if having simultaneously then to be judged as, proceed the foundation of described dedicated bearing, otherwise keep described dedicated bearing to set up request.
5. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 4, it is characterized in that, when described network controls entity is MME, described MME keeps described dedicated bearing to set up request, is specially until reaching the step of proceeding the foundation of described dedicated bearing when described dedicated bearing is set up required condition:
When described MME only preserves this locality user's face TEID of S-GW, described MME is receiving initial context foundation response or the carrying foundation response that eNB sends, and described initial context is set up response or carrying is set up when comprising user's face TEID of eNB in the response, be judged as and satisfy described dedicated bearing and set up required condition, and proceed the foundation of described dedicated bearing;
When described MME does not preserve this locality user's face TEID of the user's face TEID of eNB and S-GW, described MME receive S-GW with described link bearing identification consistent set up the default bearer response time, be judged as and satisfy described dedicated bearing and set up required condition, send the radio bearer that carries described default bearer and dedicated bearer information simultaneously and set up request, be used for carrying out simultaneously the foundation of described default bearer and dedicated bearing.
6. default bearer is set up the control method that dedicated bearing is set up in the process according to claim 1, it is characterized in that, when described network controls entity is S-GW, described dedicated bearing is set up request for the dedicated bearing request of setting up that packet data network gateway P-GW sends, and comprises the link bearing identification in the described dedicated bearing request.
7. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 6, it is characterized in that, when described network controls entity was S-GW, described S-GW set up the step whether required condition judgment continue the foundation of described dedicated bearing according to described dedicated bearing and is specially:
Described S-GW judges local whether preserving and described user's face TEID of the relevant eNB of bearing identification and the user's face TEID of P-GW of linking;
Satisfy described dedicated bearing and set up required condition if having simultaneously then to be judged as, proceed the foundation of described dedicated bearing, otherwise keep described dedicated bearing to set up request, until reaching the foundation of proceeding described dedicated bearing when described dedicated bearing is set up required condition.
8. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 7, it is characterized in that, when described network controls entity is S-GW, described S-GW keeps described dedicated bearing to set up request, is specially until reaching the step of proceeding the foundation of described dedicated bearing when described dedicated bearing is set up required condition:
Described S-GW is receiving the more new bearer request that MME sends, and described more new bearer request package is when drawing together user's face TEID of eNB, is judged as to satisfy described dedicated bearing and set up required condition, and proceeds the foundation of described dedicated bearing.
9. default bearer is set up the control method that dedicated bearing is set up in the process according to claim 1, it is characterized in that, when described network controls entity was eNB, described dedicated bearing was set up request for the dedicated bearing request of setting up that MME sends, and comprises the link bearing identification in the described dedicated bearing request.
10. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 9, it is characterized in that, when described network controls entity was eNB, described eNB set up the step whether required condition judgment continue the foundation of described dedicated bearing according to described dedicated bearing and is specially:
Described eNB judges local whether preserving and the described radio bearer context that links the relevant radio bearer sign of bearing identification;
Satisfy described dedicated bearing and set up required condition if having then to be judged as, proceed the foundation of described dedicated bearing, otherwise keep described dedicated bearing to set up request, until reaching the foundation of proceeding described dedicated bearing when described dedicated bearing is set up required condition.
11. set up the control method that dedicated bearing is set up in the process as default bearer as described in the claim 10, it is characterized in that, when described network controls entity is eNB, described eNB keeps described dedicated bearing to set up request, is specially until reaching the step of proceeding the foundation of described dedicated bearing when described dedicated bearing is set up required condition:
Described eNB is receiving the radio bearer foundation response that user terminal UE sends, and described radio bearer is set up response and is comprised with described when linking the radio bearer context that the relevant radio bearer of bearing identification identifies, be judged as and satisfy described dedicated bearing and set up required condition, and proceed the foundation of described dedicated bearing.
12. a network controls entity, the dedicated bearing foundation that is used for process that default bearer is set up is controlled, and it is characterized in that, comprising:
The request receiving element is used for setting up process at default bearer and receives dedicated bearing foundation request;
Judging unit is used for setting up the foundation whether required condition judgment continues described dedicated bearing according to described dedicated bearing when the described request receiving element receives dedicated bearing foundation request; If then the foundation of described dedicated bearing is proceeded in the notifier processes unit, otherwise the notice memory cell keeps described dedicated bearing to set up request;
Processing unit is used for continuing according to the notice of described judging unit the flow process of setting up of dedicated bearing;
Memory cell is used for keeping described dedicated bearing to set up request according to the notice of described judging unit.
13. as network controls entity as described in the claim 12, it is characterized in that, also comprise:
Detecting unit, be used for described judging unit is set up required condition and notified described memory cell to keep described dedicated bearing to set up request according to described dedicated bearing after, detect described dedicated bearing in real time or regularly and set up required condition and whether reach, notify described processing unit to continue the flow process of setting up of dedicated bearing when reaching.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101516722A CN101400148B (en) | 2007-09-26 | 2007-09-26 | Control method and equipment for special bearing establishment in default bearing establishing process |
| PCT/CN2008/072497 WO2009043283A1 (en) | 2007-09-26 | 2008-09-24 | Method and apparatus of controlling dedicated bearer establishment in the procedure of default bearer establishment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101516722A CN101400148B (en) | 2007-09-26 | 2007-09-26 | Control method and equipment for special bearing establishment in default bearing establishing process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101400148A CN101400148A (en) | 2009-04-01 |
| CN101400148B true CN101400148B (en) | 2010-06-09 |
Family
ID=40518337
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101516722A Active CN101400148B (en) | 2007-09-26 | 2007-09-26 | Control method and equipment for special bearing establishment in default bearing establishing process |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101400148B (en) |
| WO (1) | WO2009043283A1 (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101616058B (en) * | 2008-06-26 | 2012-04-18 | 电信科学技术研究院 | Method, device and system for establishing multiple PDN connection bearing |
| CN102238743A (en) * | 2010-05-05 | 2011-11-09 | 联芯科技有限公司 | Multiplex bearer management method and device |
| CN102036377B (en) * | 2011-01-26 | 2013-01-09 | 大唐移动通信设备有限公司 | Method, system and network element for initiating active paging |
| EP2727433B1 (en) * | 2011-07-01 | 2015-04-29 | Telefonaktiebolaget LM Ericsson (PUBL) | Method, apparatuses and computer program for controlling bearer related resources |
| CN103096179A (en) * | 2011-11-02 | 2013-05-08 | 中兴通讯股份有限公司 | Method and system for guaranteeing stream media file service quality |
| JP5986287B2 (en) * | 2012-03-28 | 2016-09-06 | ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． | Method and apparatus for establishing a direct tunnel |
| CN105873024B (en) * | 2015-01-21 | 2019-09-06 | 中国移动通信集团辽宁有限公司 | The method and device of gateway is parsed in a kind of LTE network |
| CN104754739B (en) * | 2015-03-23 | 2018-05-11 | 大唐移动通信设备有限公司 | The method and apparatus of the user plane tunneling termination mark TEID-U segment processings of terminal |
| WO2017028289A1 (en) * | 2015-08-20 | 2017-02-23 | 华为技术有限公司 | Method and apparatus for carrying communication by network terminal device |
| US10848956B2 (en) | 2015-10-09 | 2020-11-24 | Nec Corporation | Dedicated core networks (DCN) selection |
| JP6829308B2 (en) | 2016-10-12 | 2021-02-10 | 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． | Session management method and session management network elements |
| CN108924950B (en) * | 2017-04-21 | 2021-11-30 | 中兴通讯股份有限公司 | Method and device for establishing bearer |
| CN109548010B (en) * | 2017-07-31 | 2021-02-12 | 华为技术有限公司 | Method and device for acquiring identity of terminal equipment |
| US11197333B2 (en) | 2018-03-28 | 2021-12-07 | British Telecommunications Public Limited Company | Predictive bearers in a wireless communication network |
| US11337262B2 (en) | 2018-03-28 | 2022-05-17 | British Telecommunications Public Limited Company | Predictive bearers in a wireless communication network |
| EP3777461A1 (en) | 2018-03-29 | 2021-02-17 | British Telecommunications public limited company | Dedicated bearer management |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1980150A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for realizing bearing set-up based on tactics control |
| CN1980165A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for realizing set-up of bearing in communication network |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7634274B2 (en) * | 2002-12-31 | 2009-12-15 | Nokia Corporation | Connection establishment for PDP contexts |
| FI20031911A0 (en) * | 2003-12-29 | 2003-12-29 | Nokia Corp | A method and system for controlling an access network service in a real-time data service |
-
2007
- 2007-09-26 CN CN2007101516722A patent/CN101400148B/en active Active
-
2008
- 2008-09-24 WO PCT/CN2008/072497 patent/WO2009043283A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1980150A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for realizing bearing set-up based on tactics control |
| CN1980165A (en) * | 2005-12-06 | 2007-06-13 | 华为技术有限公司 | Method for realizing set-up of bearing in communication network |
Non-Patent Citations (1)
| Title |
|---|
| 3GPP TSG SSA.GPRS enhancements for E-UTRAN access (Release 8).3GPP TS 23.401 V1.1.0.2007,3(23401110),23-52. * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2009043283A1 (en) | 2009-04-09 |
| CN101400148A (en) | 2009-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101400148B (en) | Control method and equipment for special bearing establishment in default bearing establishing process | |
| CN101478743B (en) | Method and apparatus for EPS bearing management | |
| KR101519547B1 (en) | Method and apparatus for updating location information of user equipment | |
| CN101282511B (en) | Bearing processing method | |
| CN101094497B (en) | Method for switching mobile users between different access systems | |
| CN102333386B (en) | Terminal attachment method and equipment | |
| CN102868994A (en) | Method for supporting mobility of user equipment (UE) | |
| KR102094499B1 (en) | Method and apparatus for managing connectivity of a packet data network in a wireless communication system | |
| CN102917332B (en) | Method and device for achieving attachment of mobile equipment | |
| KR101341765B1 (en) | Wireless communication device of mobile communication system | |
| CN103686932A (en) | Method for ensuring correct establishment of local IP access service | |
| CN102857897A (en) | Method, device and system for managing MTC (machine type communication) devices | |
| CN101572862B (en) | Method and equipment for supporting intercommunication between 3G system and LTE system | |
| CN102056129A (en) | Establishing method and device of local Internet protocol (IP) access connection | |
| CN102238632A (en) | Distribution processing method, system and equipment | |
| CN103814622A (en) | Communication system, communication method and communication program | |
| CN101730073B (en) | Method and system for acquiring user contracting data | |
| CN101505474B (en) | Network side processing method in subscriber handover process, network element equipment and network system | |
| CN101330720A (en) | Method for processing access user, user access system and equipment | |
| KR101654491B1 (en) | Mobile communication system, data communication method, gateway device, and base station | |
| CN101227740A (en) | Apparatus, system and method for accessing SAE core network | |
| CN109040327A (en) | A kind of distribution method and device of IP address of mobile terminal | |
| CN102448046B (en) | Method, equipment and system for optimizing data route | |
| CN101610462A (en) | A kind of data message sending method, device and communication system | |
| CN101540994B (en) | Method and system for realizing continuous bearing among systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20090401 Assignee: Apple Computer, Inc. Assignor: Huawei Technologies Co., Ltd. Contract record no.: 2015990000755 Denomination of invention: Control method and device for special bearing establishment in default bearing establishing process Granted publication date: 20100609 License type: Common License Record date: 20150827 |
|
| LICC | Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model |