WO2016119465A1 - 承载资源的预留方法及装置 - Google Patents

承载资源的预留方法及装置 Download PDF

Info

Publication number
WO2016119465A1
WO2016119465A1 PCT/CN2015/089077 CN2015089077W WO2016119465A1 WO 2016119465 A1 WO2016119465 A1 WO 2016119465A1 CN 2015089077 W CN2015089077 W CN 2015089077W WO 2016119465 A1 WO2016119465 A1 WO 2016119465A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
function entity
network function
bearer
dedicated bearer
Prior art date
Application number
PCT/CN2015/089077
Other languages
English (en)
French (fr)
Inventor
郑芳庭
周晓云
史旭刚
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016119465A1 publication Critical patent/WO2016119465A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and an apparatus for reserving a bearer resource.
  • FIG. 1 is a structural block diagram of a system architecture evolution SAE in the related art. As shown in FIG. 1 , the SAE includes the following network elements:
  • An evolved radio access network (Evolved RAN for short) is used to provide higher uplink and downlink rates, lower transmission delays, and more reliable wireless transmission.
  • the network element included in the E-RAN is an evolved base station (Evolved Node B for short), which provides radio resources for terminal access.
  • the Home Subscriber Server (HSS) is used to permanently store user subscription data.
  • Mobility Management Entity used to control the surface functional entity, a server that temporarily stores user data, and is responsible for managing and storing the UE context (such as UE/user identity, mobility management state, user security parameters, etc.) Assigning a temporary identifier to the user, when the UE is camped on the tracking area or the network is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering paging at the SAE.
  • MME Mobility Management Entity
  • the Serving Gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of the UE in idle state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and network internal routing information. It is the anchor point of the internal user plane of the 3GPP system. A user can only have one Serving GW at a time;
  • the packet data network gateway (Packet Data Network Gate, referred to as PDN GW) is responsible for the UE accessing the PDN gateway, assigning the user IP address, and is the mobility anchor of the 3GPP and non-3GPP access systems. Users can access multiple PDN GWs at the same time.
  • PDN GW Packet Data Network Gate
  • PCRF Policy and Charging Rule Functionality
  • QoS of Service quality of service
  • the functional entity can also control the establishment and release of bearers in the access network.
  • IP Multimedia Subsystem In the next-generation mobile network, IP Multimedia Subsystem (IMS) network can be deployed to provide IP-based voice and video services, thus replacing Circuit Switched (CS) in 2/3G networks. )area.
  • the voice service of the terminal is transmitted through the LTE bearer.
  • APN dedicated access point name
  • the network and the terminal establish a default bearer with a QoS Class Identifier (QCI) of 5 for the APN.
  • QCI QoS Class Identifier
  • the signaling required for the transmission user to register in the IMS network is called a signaling bearer.
  • a temporary bearer with a QCI of 1 is temporarily established for the terminal to transmit voice data, which is called a voice bearer.
  • the IMS network supports the video call service at the same time.
  • the network establishes two dedicated bearers with QCIs 1 and 2 for the calling and terminating users.
  • the dedicated bearer with QCI 1 is used to transmit voice.
  • a proprietary bearer with a QCI of 2 is used to transmit video.
  • two proprietary bearers with QCIs of 1 and 2 are released.
  • FIG. 2 is a flowchart of a method for establishing a QCI for a dedicated bearer of an evolved packet core network EPC of 1 and 2 in the related art. As shown in FIG. 2, the method establishes a QCI by an Evolved Packet Core (EPC). A dedicated bearer of 1 and 2, and triggered by the P-CSCF of the IMS network, the steps of the method include:
  • Step S201 The P-CSCF sends an authentication authorization request message to the PCRF to indicate two new service flow information and related features.
  • Step S202 The PCRF sends a re-authentication request message to the PGW, and delivers two new service flow rules to the PGW, including the characteristics of the two service flows and the QoS parameters, where the QCIs of the two service flows are 1 and 2, respectively;
  • Step S203 The PGW determines that it is necessary to establish a dedicated bearer for the two new service flows, and sends a create bearer request message to the SGW, where the message includes two dedicated bearers, and the QCIs are 1 and 2 respectively;
  • Step S204 The PGW returns a re-authentication response message to the PCRF.
  • Step S205 The PCRF returns an authentication authorization response message to the P-CSCF.
  • Step S206 The SGW sends a create bearer request message to the MME, where the message includes two dedicated bearers, and the QCIs are 1 and 2 respectively;
  • Step S207 The MME sends an E-RAB setup message to the eNodeB, indicating that two bearers with QCIs 1 and 2 are established, and the message includes two non-access strata (Non-Access-Statum, referred to as NAS) sent by the MME to the UE. Activating a proprietary EPS bearer context request message;
  • Step S208 The eNodeB sends an RRC connection reconfiguration to the UE.
  • the RRC connection is used by the eNodeB to create two bearers with QCIs 1 and 2, and sends a NAS activation private EPS bearer context request message to the UE;
  • Step S209 The UE sends an RRC connection reconfiguration complete to the eNodeB;
  • the UE determines to accept the dedicated bearer setup, locally creates a dedicated bearer, and returns an active private EPS bearer context accept message to the MME; note that the UE returns two active proprietary EPS bearer context accept messages for the two dedicated bearers;
  • Step S210 The UE activates the proprietary EPS bearer context accepting from the MME;
  • Step S211 The eNodeB returns an E-RAB setup response message to the MME, indicating which bearers are successfully established.
  • Step S212 The MME returns a create bearer response message to the SGW, indicating which dedicated bearers are successfully established.
  • Step S213 The SGW returns a create bearer response message to the PGW, indicating which dedicated bearers are successfully established.
  • Step S214 The PGW sends a credit control request-update message to the PCRF to establish a successful bearer, including the charging identifier of the newly-created bearer, the current location information of the user, and the like;
  • Step S215 The PCRF sends a credit control request-update message to the PGW.
  • Step S216 The PCRF sends a re-authentication request message to the P-CSCF, including information such as the charging identifier of the newly-created bearer and the current location information of the user.
  • Step S217 The P-CSCF sends a re-authentication response message to the PCRF.
  • the P-CSCF will complete the negotiation and establishment of the SIP session between the calling and called users.
  • the video call service establishes two dedicated bearers in one process at the same time.
  • each device may appear to accept only part of the establishment of a proprietary bearer. For example, only a dedicated bearer with a QCI of 1 is successfully established, or only a dedicated bearer with a QCI of 2 is successfully established.
  • a dedicated bearer with a QCI of 1 can be successfully established, and the service can be degraded into a voice call.
  • the service can be identified as a failure because only the image has no sound. The caller will not endure.
  • the general processing is that the IMS network determines that the service fails, and triggers the PCRF and the PGW to delete the established dedicated bearer; or the IMS continues the service connection, and then the user hangs up the service, thereby triggering the network to trigger The dedicated bearer just created is released.
  • the main purpose of the embodiments of the present invention is to provide a method and a device for reserving a bearer resource, so as to solve at least the problem that only a part of the dedicated bearer is successfully created when the network side establishes multiple dedicated bearers at the same time in the related art.
  • a method for reserving a bearer resource including: a network function entity acquiring a plurality of service flows and a dependency relationship between the plurality of service flows, where the service flows include: An independent service flow and an auxiliary service flow, the dependency being used to indicate that when the resource allocation of the independent service flow corresponding to the specified auxiliary service flow is successful, the resource is allocated to the designated auxiliary service flow; the network function entity is according to the dependency Relationship execution resource reservation.
  • the performing, by the network function entity, the resource reservation according to the dependency relationship includes: determining, by the network function entity, whether the resource is successfully allocated for the independent service flow; when the determination result is yes, the network function entity is The auxiliary service flow allocates resources; when the determination result is no, the network function entity does not allocate resources for the auxiliary service flow.
  • the network function entity allocates resources for the independent service flow, where the network function entity creates or modifies a dedicated bearer for the independent service flow; and/or, the network function entity is the auxiliary
  • the service flow allocation resource includes: the network function entity creates or modifies a dedicated bearer for the auxiliary service flow.
  • the creating, by the network function entity, the dedicated bearer for the independent service flow includes: when the network function entity establishes or modifies a dedicated bearer of the independent service flow, the network function entity Receiving a dedicated bearer setup or modification request for the auxiliary service flow; otherwise the network function entity rejects the dedicated bearer setup or modification request of the auxiliary service flow.
  • the method includes: if the network function entity releases the And the network function entity releases the resource corresponding to the auxiliary service flow according to the dependency relationship.
  • the network function entity releases the resource corresponding to the auxiliary service flow, and the network function entity deletes the dedicated bearer corresponding to the auxiliary service flow or modifies the dedicated bearer corresponding to the auxiliary service flow.
  • the network function entity comprises: a packet data network gateway PGW, a serving gateway SGW, a mobility management entity MME, and an evolved base station eNodeB.
  • the dependency relationship is determined by the policy and charging rule function PCRF according to an indication from the application function AF or a network policy configured by the PCRF itself.
  • a resource-reserving device which is located at a network function entity side, and includes: an obtaining module, configured to acquire a plurality of service flows and a dependency relationship between the plurality of service flows
  • the service flow includes: an independent service flow and an auxiliary service flow, where the dependency is used to indicate that the resource is allocated to the designated auxiliary service flow when the resource allocation of the independent service flow corresponding to the specified auxiliary service flow is successful;
  • An execution module is configured to perform resource reservation according to the dependency relationship.
  • the executing module includes: a determining unit, configured to determine whether the resource is successfully allocated for the independent service flow; and an allocating unit, configured to allocate resources for the auxiliary service flow when the determination result is yes; When the result is no, resources are not allocated for the auxiliary service flow.
  • the allocating unit is further configured to create or modify a dedicated bearer for the independent service flow; and/or create or modify a dedicated bearer for the auxiliary service flow.
  • the execution module further includes: a control unit, configured to receive a dedicated bearer setup or modification request of the auxiliary service flow when the network function entity successfully establishes or modifies the dedicated bearer of the independent service flow. Otherwise, the private bearer setup or modification request of the secondary service flow is rejected.
  • a control unit configured to receive a dedicated bearer setup or modification request of the auxiliary service flow when the network function entity successfully establishes or modifies the dedicated bearer of the independent service flow. Otherwise, the private bearer setup or modification request of the secondary service flow is rejected.
  • the device includes: a release module, if the network function entity releases the resource corresponding to the independent service flow, releasing the resource corresponding to the auxiliary service flow according to the dependency relationship.
  • the releasing module is further configured to delete the dedicated bearer corresponding to the independent service flow or modify the dedicated bearer corresponding to the independent service flow; or delete the dedicated bearer corresponding to the auxiliary service flow or Modifying the dedicated bearer corresponding to the auxiliary service flow.
  • the network function entity comprises: a packet data network gateway PGW, a serving gateway SGW, a mobility management entity MME, and an evolved base station eNodeB.
  • the dependency relationship is determined by the policy and charging rule function PCRF according to an indication from the application function AF or a network policy configured by the PCRF itself.
  • the network function entity is configured to perform resource reservation according to the dependency relationship of the specified auxiliary service flow in the plurality of service flows only when the independent service flow resource corresponding to the corresponding service flow is successfully allocated.
  • the method enables the network function entity to directly identify the relationship between the resource-specific bearers, and solves the problem that only a part of the dedicated bearer is successfully created when the network side establishes multiple dedicated bearers at the same time in the related art.
  • FIG. 1 is a structural block diagram of a system architecture evolution SAE in the related art
  • FIG. 2 is a flowchart of a method for establishing a QCI for a dedicated bearer of an Evolved Packet Core Network EPC of 1 and 2 in the related art
  • FIG. 3 is a flowchart of a method for reserving bearer resources according to an embodiment of the present invention
  • FIG. 4 is a structural block diagram of a device for creating a bearer resource according to an embodiment of the present invention.
  • FIG. 5 is a block diagram 1 of an optional structure of a device for creating a bearer resource according to an embodiment of the present invention
  • FIG. 6 is a flow chart of a method for a network to create all proprietary bearers successfully according to an alternative embodiment of the present invention
  • FIG. 8 is a flowchart of an eNodeB successfully creating only a subordinate proprietary bearer method according to an alternative embodiment of the present invention
  • FIG. 9 is a flow chart of a method for failure of a proprietary bearer modification in accordance with an alternative embodiment of the present invention.
  • FIG. 10 is a flowchart of a method for a network element to release a dedicated bearer according to an alternative embodiment of the present invention
  • FIG. 11 is a flowchart of a method for preempting an established private bearer by a new service according to an alternative embodiment of the present invention
  • FIG. 12 is a flowchart of a method for preempting a private bearer established by a new service according to an alternative embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for reserving a bearer resource according to an embodiment of the present invention. As shown in FIG. 3, the steps of the method include:
  • Step S302 The network function entity acquires a dependency relationship between multiple service flows and multiple service flows.
  • the service flow includes: an independent service flow and an auxiliary service flow, where the dependency is used to indicate that the resource is allocated to the designated auxiliary service flow when the resource allocation of the independent service flow corresponding to the specified auxiliary service flow is successful;
  • Step S304 The network function entity performs resource reservation according to the dependency relationship.
  • the network function entity is configured to perform resource reservation according to the dependency of the allocated resource according to the resource used to indicate the specified auxiliary service flow in the multiple service flows.
  • the method enables the network function entity to directly identify the relationship between the resource-specific bearers, and solves the problem that only a part of the dedicated bearer is successfully created when the network side establishes multiple dedicated bearers at the same time in the related art.
  • Step S11 The network function entity determines whether the resource allocation is successful for the independent service flow
  • Step S12 When the determination result is yes, the network function entity allocates resources for the auxiliary service flow, and when the determination result is no, the network function entity does not allocate resources for the auxiliary service flow.
  • the network function entity involved in this embodiment allocates resources for the independent service flow.
  • the method for allocating resources for the independent service flow may be implemented as follows: Create or modify a dedicated bearer for an independent service flow; the way to allocate resources for the auxiliary service flow can be implemented as follows: The network function entity creates or modifies a proprietary bearer for the auxiliary service flow.
  • the network function entity receives a dedicated bearer setup or modification request of the auxiliary service flow when the network function entity successfully establishes or modifies the dedicated bearer for the independent service flow; otherwise, the network function entity rejects A proprietary bearer setup or modification request for an auxiliary service flow.
  • the method in this embodiment may further include: The network function entity releases the resource corresponding to the independent service flow, and the network function entity releases the resource corresponding to the auxiliary service flow according to the dependency relationship.
  • an optional application scenario of releasing the corresponding auxiliary service flow resource is: when a resource abnormality occurs in the network function entity, such as resource congestion;
  • a resource abnormality occurs in the network function entity, such as resource congestion;
  • other scenario network function entities are also operations that can release resources corresponding to the independent service flow and release resources corresponding to the auxiliary service flow according to the dependency relationship.
  • the network function entity For the network function entity to release the independent service flow corresponding to the network function entity, the network function entity deletes the dedicated bearer corresponding to the independent service flow or modifies the dedicated bearer corresponding to the independent service flow; and/or, the network function entity releases the auxiliary service.
  • the resources corresponding to the flow include: the network function entity deletes the dedicated bearer corresponding to the auxiliary service flow or modifies the dedicated bearer corresponding to the auxiliary service flow.
  • the network function entity comprises: a packet data network gateway PGW, a serving gateway SGW, a mobility management entity MME, and an evolved base station eNodeB.
  • the dependency relationship for this embodiment can be determined in various ways, such as by the policy and charging rule function PCRF according to the indication from the application function AF or the network policy configured by the PCRF itself.
  • a device for reserving resources is provided, and the device is used to implement the foregoing embodiments and optional implementation manners, and details are not described herein.
  • the term “module” "unit” may implement a combination of software and/or hardware of a predetermined function.
  • the device described in the following embodiments is preferably soft It is implemented, but hardware, or a combination of software and hardware, is also possible and conceived.
  • FIG. 4 is a structural block diagram of a device for reserving a resource according to an embodiment of the present invention.
  • the device is located on a network function entity side.
  • the device includes: an obtaining module 42 configured to acquire multiple service flows and multiple A service flow dependency, where the service flow includes: an independent service flow and an auxiliary service flow, the dependency relationship is used to indicate that the designated auxiliary service flow is allocated when the resource allocation of the independent service flow corresponding to the specified auxiliary service flow is successful.
  • the resource execution module 44 is coupled to the acquisition module 42 and configured to perform resource reservation according to the dependency relationship.
  • the executing module 44 includes: a determining unit, configured to determine whether the resource is successfully allocated for the independent service flow; the allocation unit is coupled to the determining unit, and configured to allocate resources for the auxiliary service flow when the determination result is yes; When the judgment result is no, resources are not allocated for the auxiliary service flow.
  • the allocation unit can also be set to create or modify a dedicated bearer for an independent service flow; or create or modify a dedicated bearer for the auxiliary service flow.
  • the executing module 44 further includes: a control unit, configured to receive a dedicated bearer setup or modification request of the auxiliary service flow when the network function entity succeeds in establishing or modifying the dedicated bearer of the independent service flow; otherwise, rejecting the auxiliary service The flow's proprietary bearer establishes or modifies the request.
  • a control unit configured to receive a dedicated bearer setup or modification request of the auxiliary service flow when the network function entity succeeds in establishing or modifying the dedicated bearer of the independent service flow; otherwise, rejecting the auxiliary service The flow's proprietary bearer establishes or modifies the request.
  • FIG. 5 is a block diagram of an optional structure of a resource-reserving device according to an embodiment of the present invention. As shown in FIG. 5, the device may further include: a release module 52 coupled to the execution module 44, if the network function entity is released independently. The resource corresponding to the service flow releases the resource corresponding to the auxiliary service flow according to the dependency relationship.
  • the releasing module 52 may be configured to delete the dedicated bearer corresponding to the independent service flow or modify the dedicated bearer corresponding to the independent service flow; or delete the dedicated bearer corresponding to the auxiliary service flow or modify the auxiliary service flow.
  • Proprietary bearer may be configured to delete the dedicated bearer corresponding to the independent service flow or modify the dedicated bearer corresponding to the independent service flow; or delete the dedicated bearer corresponding to the auxiliary service flow or modify the auxiliary service flow.
  • the network function entity involved in this embodiment may be: a packet data network gateway PGW, a serving gateway SGW, a mobility management entity MME, and an evolved base station eNodeB.
  • PGW packet data network gateway
  • SGW serving gateway
  • MME mobility management entity
  • eNodeB evolved base station
  • the dependency relationship involved in this embodiment may be determined by the policy and charging rule function PCRF according to the indication from the application function AF or the network policy configured by the PCRF itself. It should be noted that this mode is also only an optional implementation of this embodiment. In this way, the dependency relationship can also be determined by other means as needed.
  • the present invention provides a method for reserving a bearer resource, which enables the network side to directly identify the dependencies between the dedicated bearers during the simultaneous establishment of multiple dedicated bearers, thereby simplifying the business process and
  • the device handles complexity and improves the user experience.
  • the network side reserves the resource of one service flow, and needs to increase whether the resource reservation of the service flow is determined to be successful according to another service flow; The process of bearer modification, bearer preemption, and bearer release.
  • the method in the optional embodiment of the present invention is applicable to an application entity (abbreviated as AF) that triggers a PGW through a PCRF to simultaneously establish a scenario of multiple dedicated bearers.
  • AF application entity
  • the steps of the method include:
  • Step S21 The AF sends an authentication authorization request message to the PCRF, and when the feature of the multiple service flows is included, the dependency indication between the multiple service flows is added, that is, some service flows are created only when other service flows are successfully created. It is called an auxiliary service flow; a service flow that does not depend on other service flows is called an independent service flow;
  • the PCRF determines the dependencies between multiple service flow rules according to its own policy.
  • Step S22 The PCRF sends a re-authentication request message to the PGW.
  • the dependency indication between multiple service flows is added. That is, some service flows need to be created when other service flows are successfully created. It is called an auxiliary service flow; a service flow that does not depend on other service flows is called an independent service flow;
  • Step S23 The PGW sends a Create Bearer Request message to the SGW; the dedicated bearer corresponding to the independent service flow is referred to as an independent dedicated bearer; and the dedicated bearer corresponding to the affiliate service flow is referred to as an affiliated proprietary bearer;
  • Step S24 The PGW receives the Create Bearer Response message returned by the SGW, and determines that if the independent dedicated bearer is not successfully activated, but the affiliated dedicated bearer is successfully activated, the affiliated proprietary bearer is not considered to be successfully created, and is notified.
  • the SGW deletes the activated subordinate proprietary bearer; if the independent dedicated bearer is successfully activated, but some of the attached proprietary bearers are not activated, proceed to step 5; the dedicated bearer is not successfully created may be due to the UE, eNodeB, MME, SGW or PGW Each device was not successfully created;
  • Step S25 The PGW sends a CCR-U message to the PCRF to indicate a related rule that is not successfully carried.
  • the relevant rule that is not successfully carried here corresponds to a rule corresponding to all the activated bearers that are not activated.
  • the PGW may notify the SGW of the dependency indication between the multiple dedicated bearers
  • the SGW may notify the MME of the dependency indication between the multiple dedicated bearers
  • the MME may depend on the dependencies between the multiple dedicated bearers.
  • the notification is notified to the eNodeB.
  • the SGW, the MME, and the eNodeB establish a dedicated bearer, they can successfully create all the dedicated bearers or only create independent independent bearers according to the local resources. If it is judged that the downstream node has only established the affiliated proprietary bearer, the downstream node is notified to deactivate the affiliated proprietary bearer.
  • the downstream node of the MME is an eNodeB
  • the downstream node of the SGW is an MME.
  • the method in this alternative embodiment is also applicable to a service release scenario in which the network side initiates a modification to a dedicated bearer after the establishment of multiple dedicated bearers, and the steps of modifying the bearer include:
  • Step S31 The network side initiates modification of the attached/independent dedicated bearer, and requires more resources to be reserved;
  • Step S32 The network element eNodeB/PGW determines that the modified dedicated bearer is an attached dedicated bearer, and depends on an independent dedicated bearer, and the network element cannot reserve more resources for the independent dedicated bearer.
  • the bearer is not modified and still retains the original resources.
  • the method in this alternative embodiment is also applicable to a service release scenario in which a dedicated bearer is released or preempted after the establishment of multiple dedicated bearers, and the steps of preempting or being released include:
  • Step S41 The eNodeB/MME/SGW/PGW network element, for example, when congestion occurs, it is decided to release a part of the dedicated bearer or the new service to preempt the original established dedicated bearer;
  • Step S42 When the network element decides to release or preempt a specific bearer according to its own policy, it is determined that if other private bearers depend on the dedicated bearer to be released, the dedicated bearer and all the dedicated bearers are dependent on the dedicated bearer. Other proprietary bearers are released together.
  • the method for identifying a bearer according to the dependency relationship is adopted in the present embodiment.
  • the network side establishes multiple dedicated bearers at the same time in the related art, only a part of the dedicated bearer may be successfully created, thereby affecting the user experience and avoiding the problem.
  • the service experience caused by the successful establishment of only some proprietary bearers is not high, and the complexity of business process exception processing and network element processing is simplified.
  • FIG. 6 is a flowchart of a method for successfully creating all dedicated bearers in a network according to an alternative embodiment of the present invention; as shown in FIG. 6, when a VoLTE user is calling, an embodiment in which two dedicated bearers are successfully created on the network side is shown. .
  • This scenario is also applicable to the scenario where the network side creates two dedicated bearers for the VoLTE user to be called.
  • Step S601 the VoLTE registered user initiates a caller request
  • Step S602 the P-CSCF sends an authentication authorization request message to the PCRF, indicating two new service flow information 1 and 2 and related features, and the service flow 2 includes an indication that the service flow is attached to the service flow 1;
  • step S603 the PCRF sends a re-authentication request message to the PGW, and sends rules 2 and 2 of the two new service flows to the PGW, including the characteristics of the two service flows and the QoS parameters, and the service flow rule 2 includes an indication that the The service flow is attached to the business flow rule 1;
  • Step S604 the PGW determines that it is necessary to establish the dedicated bearers 1 and 2 for the two new service flow rules 1 and 2, and the private bearer 2 is a subsidiary private bearer, and is attached to the private bearer 1;
  • Step S605 the PGW sends a create bearer request message to the SGW, where the message includes two dedicated bearers. 1 and 2;
  • Step S606 the PGW returns a re-authentication response message to the PCRF;
  • Step S607 the PCRF returns an authentication authorization response message to the P-CSCF;
  • Step S608 the SGW sends a create bearer request message to the MME, where the message includes two dedicated bearers 1 and 2;
  • step S609 the MME sends an E-RAB (E-UTRAN Radio Access Bearer) setup message to the eNodeB, indicating that two bearers 1 and 2 are established, and the message includes two NASs sent by the MME to the UE.
  • E-RAB E-UTRAN Radio Access Bearer
  • Step S610 the eNodeB initiates RRC (Radio Resource Control) reconfiguration to the UE, and sends a NAS layer activation private EPS bearer context request message to the UE;
  • RRC Radio Resource Control
  • Step S611 the UE returns to the RRC reconfiguration completion.
  • Step S612 the UE determines to accept the dedicated bearer setup, locally creates the dedicated bearer, and returns an active private EPS bearer context accept message to the MME, and the UE returns two active proprietary EPS bearer context accept messages for the two dedicated bearers;
  • Step S613 the eNodeB returns an E-RAB setup response message to the MME, indicating that the bearers 1 and 2 are successfully established;
  • Step S614 the MME returns a create bearer response message to the SGW, indicating that the bearers 1 and 2 are successfully established;
  • Step S615 the SGW returns a create bearer response message to the PGW, indicating that the bearers 1 and 2 are successfully established;
  • Step S616 the PGW determines that both the dedicated bearers 1 and 2 are successfully activated
  • Step S617 the PGW sends a credit control request-update message to the PCRF, including the charging identifier of the newly created bearer, the current location information of the user, and the like;
  • Step S619 The PCRF sends a re-authentication request message to the P-CSCF, which includes information such as a charging identifier of the newly-created bearer and a current location information of the user.
  • Step S620 The P-CSCF sends a re-authentication response message to the PCRF.
  • FIG. 7 is a flowchart of an eNodeB successfully creating an independent private bearer according to an alternative embodiment of the present invention. As shown in FIG. 7 , when a VoLTE user is calling, the network creates a dedicated bearer, and the eNodeB successfully creates an independent special. There is an embodiment of the bearer. This scenario is also applicable to the scenario where the network side creates a dedicated bearer for the VoLTE user.
  • the steps of the method include:
  • Step S701 the VoLTE registered user initiates a caller request
  • Step S702 the P-CSCF sends an authentication authorization request message to the PCRF, indicating two new service flow information 1 and 2 and related features, and the service flow 2 includes an indication that the service flow is attached to the service flow 1;
  • step S703 the PCRF sends a re-authentication request message to the PGW, and sends rules 2 and 2 of the two new service flows to the PGW, including the characteristics of the two service flows and the QoS parameters, and the service flow rule 2 includes an indication to identify the The service flow is attached to the business flow rule 1;
  • Step S704 the PGW determines that it is necessary to establish the dedicated bearers 1 and 2 for the two new service flow rules 1 and 2, and the private bearer 2 is a subsidiary private bearer, and is attached to the private bearer 1;
  • Step S705 the PGW sends a create bearer request message to the SGW, where the message includes two dedicated bearers 1 and 2, respectively corresponding to the new service flow rules 1 and 2;
  • Step S706 the PGW returns a re-authentication response message to the PCRF.
  • Step S707 the PCRF returns an authentication authorization response message to the P-CSCF;
  • Step S708 the SGW sends a create bearer request message to the MME, where the message includes two dedicated bearers 1 and 2;
  • step S709 the MME sends an E-RAB setup message to the eNodeB, indicating that two bearers 1 and 2 are established, and the message includes two NAS layer activation private EPS bearer context request messages sent by the MME to the UE;
  • step S710 the eNodeB determines that only the bearer 1 is created, the bearer 2 cannot be created, the RRC reconfiguration is initiated to the UE, and the NAS layer activates the proprietary EPS bearer context request message is sent to the UE.
  • Step S711 the UE returns to the RRC reconfiguration completion.
  • Step S712 the UE only accepts the establishment of the dedicated bearer 1, locally creates the private bearer 1, and returns an active private EPS bearer context accept message to the MME; and returns an active private EPS bearer context reject message to the MME for the private bearer 2;
  • step S713 the eNodeB returns an E-RAB setup response message to the MME, indicating that the bearer 1 is successfully established, and the bearer 2 fails to be created.
  • Step S714 the MME returns a create bearer response message to the SGW, indicating that the bearer 1 is successfully established, and the bearer 2 fails to be created.
  • Step S715 the SGW returns a create bearer response message to the PGW, and successfully establishes the bearer 1, and bears the bearer 2 Construction failed;
  • Step S716 the PGW determines that the independent private bearer 1 is created, and the independent private bearer 2 is not successfully created, and then considers that the dedicated bearer 1 can be successfully created;
  • Step S717 The PGW sends a credit control request-update message to the PCRF, including the charging identifier of the newly created bearer, the current location information of the user, the service flow rule 2 that is not successfully loaded, and the like;
  • Step S719 the PCRF sends a re-authentication request message to the P-CSCF, including the charging identifier of the newly-created bearer, the current location information of the user, the service flow 2 that is not successfully loaded, and the like;
  • Step S720 the P-CSCF sends a re-authentication response message to the PCRF.
  • FIG. 8 is a flowchart of an eNodeB successfully creating only a subordinate proprietary bearer according to an alternative embodiment of the present invention.
  • the network creates a dedicated bearer, and the eNodeB only successfully creates an affiliate.
  • An embodiment of a proprietary bearer This scenario is also applicable to the scenario where the network side creates a dedicated bearer for the VoLTE user.
  • the steps of the method include:
  • Step S801 the VoLTE registered user initiates a caller request
  • Step S802 the P-CSCF sends an authentication authorization request message to the PCRF, indicating two new service flow information 1 and 2 and related features, and the service flow 2 includes an indication that the service flow is attached to the service flow 1;
  • step S803 the PCRF sends a re-authentication request message to the PGW, and sends rules 2 and 2 of the two new service flows to the PGW, including the characteristics of the two service flows and the QoS parameters, and the service flow rule 2 includes an indication that the The service flow is attached to the business flow rule 1;
  • Step S804 the PGW determines that it is necessary to establish the dedicated bearers 1 and 2 for the two new service flow rules 1 and 2, and the private bearer 2 is a subsidiary private bearer, and is attached to the private bearer 1;
  • Step S805 the PGW sends a create bearer request message to the SGW, where the message includes two dedicated bearers 1 and 2, respectively corresponding to the new service flow rules 1 and 2;
  • Step S806 the PGW returns a re-authentication response message to the PCRF;
  • Step S807 the PCRF returns an authentication authorization response message to the P-CSCF;
  • Step S808 the SGW sends a create bearer request message to the MME, where the message includes two dedicated bearers 1 and 2;
  • step S809 the MME sends an E-RAB setup message to the eNodeB, indicating that two bearers 1 and 2 are established, and the message includes two NAS layer activation private EPS bearer context request messages sent by the MME to the UE;
  • step S810 the eNodeB determines that only the bearer 2 is created, the bearer 1 cannot be created, the RRC reconfiguration is initiated to the UE, and the NAS layer activates the proprietary EPS bearer context request message is sent to the UE.
  • Step S811 the UE returns to the RRC reconfiguration completion.
  • Step S812 the UE only accepts the establishment of the dedicated bearer 2, locally creates the private bearer 2, and returns an active private EPS bearer context accept message to the MME; and returns an active private EPS bearer context reject message to the MME for the private bearer 1;
  • step S813 the eNodeB returns an E-RAB setup response message to the MME, indicating that the bearer 2 is successfully established, and the bearer 1 creation fails.
  • Step S814 the MME returns a create bearer response message to the SGW, indicating that the bearer 2 is successfully established, and the bearer 1 creation fails.
  • Step S815 the SGW returns a bearer response message to the PGW, and successfully establishes the bearer 2, and the bearer 1 fails to be created.
  • Step S816 the PGW determines that the auxiliary dedicated bearer 2 is activated, and the independent private bearer 1 is not successfully created, and then the dedicated bearers 1 and 2 are considered to be failed to be created;
  • Step S817 the PGW sends a credit control request-update message to the PCRF, including the service flow rules 1 and 2 that are not successfully loaded;
  • Step S819 the PCRF sends a re-authentication request message to the P-CSCF, including service flows 1 and 2 that are not successfully loaded, and the like;
  • Step S820 the P-CSCF sends a re-authentication response message to the PCRF.
  • Step S821 the PGW initiates the release of the dedicated bearer 2 that has been successfully created, and initiates a delete bearer request message to the SGW, where the message includes the dedicated bearer 2.
  • step S822 the PGW triggers other processing of the bearer release process.
  • FIG. 9 is a flowchart of a method for modifying a proprietary bearer modification according to an alternative embodiment of the present invention. As shown in FIG. 9 , an embodiment of an eNodB network element resource reservation failure is used as an example, and a method for modifying a proprietary bearer fails. The steps include:
  • Step S901 the network has established dedicated bearers 1 and 2 for the UE, wherein the private bearer 1 is attached to the dedicated bearer 2, and the eNodeB stores the dependencies of the private bearers 1 and 2;
  • Step S902 the PCRF determines that the service rule flows 1 and 2 need to be updated, and improves the QoS parameters thereof;
  • Step S903 the PGW sends an update bearer request to the SGW, including new QoS parameters of the dedicated bearers 1 and 2.
  • Step S904 the SGW sends an update bearer request to the MME, including new QoS parameters of the dedicated bearers 1 and 2.
  • step S905 the MME sends an E-RAB modification message to the eNodeB, indicating that the two bearers 1 and 2 are modified, and the message includes two NAS layer modified EPS bearer context request messages sent by the MME to the UE.
  • Step S906 the eNodeB determines that the QoS cannot be upgraded for the bearer 1 due to insufficient resources, and the bearer 2 is attached to the bearer 1, and the QoS is not promoted for the bearer 2;
  • Step S907 the eNodeB returns an E-RAB modification response to the MME, where the message indicates that the bearer 1 and 2 modification fails;
  • Step S908 the MME returns an update bearer response to the SGW, where the message indicates that the update of the dedicated bearers 1 and 2 fails;
  • Step S909 the SGW returns an update bearer response to the PGW, where the message indicates that the update of the dedicated bearers 1 and 2 fails;
  • Step S910 the PGW returns a re-authentication response to the PCRF, where the message indicates that the traffic flow rules 1 and 2 fail to load.
  • FIG. 10 is a flowchart of a method for a network element to release a dedicated bearer according to an alternative embodiment of the present invention.
  • FIG. 10 an embodiment in which an eNodeB/MME/SGW/PGW network element is congested and a network element releases a dedicated bearer is shown.
  • the premise of the implementation of this process is that the affiliation of the user-specific bearer has been saved in the eNodeB/MME/SGW or the PGW network element.
  • the steps of the method include:
  • step S1001 the network element determines that the network traffic suddenly increases, and the device is congested
  • step S1002 the network element determines, according to its own policy, that the established dedicated bearer 1 needs to be deleted, so as to reduce the load of the device, for example, determining priorities, low-value users, low-value services, and the like;
  • Step S1003 Whether the other dedicated bearer in the network element searching device depends on deleting the dedicated bearer 1;
  • step S1004 the network element deletes the private bearer 1 and other proprietary bearers that depend on deleting the dedicated bearer 1.
  • FIG. 11 is a flowchart of a method for preempting an established private bearer by a new service according to an optional embodiment of the present invention.
  • the eNodeB/MME/SGW/PGW network element is congested, and the new service preemption is established.
  • An embodiment of a proprietary bearer is that the affiliation of the user-specific bearer has been saved in the eNodeB/MME/SGW or the PGW network element.
  • the steps of the method include:
  • step S1101 the network element determines that the network traffic suddenly increases, and the device is congested
  • Step S1102 The network element receives a high priority service establishment request.
  • Step S1103 The network element determines, according to its own policy, that the new service needs to preempt the established dedicated bearer 1 resource, and the policy, for example, determines the priority, the low value user, the low value service, and the like;
  • Step S1104 Whether the other dedicated bearer in the network element searching device depends on deleting the dedicated bearer 1;
  • Step S1105 The network element deletes the dedicated bearer 1 and other dedicated bearers that depend on deleting the dedicated bearer 1;
  • step S1106 the network element accepts a high priority service establishment request.
  • FIG. 12 is a flowchart of a method for preempting an established private bearer according to an alternative embodiment of the present invention.
  • the eNodeB network element is congested as an example, and the new service preempts the established dedicated bearer.
  • the dedicated bearers and new services that are preempted in this scenario may belong to the same UE or belong to different UEs.
  • the steps of the method include:
  • Step S1201 the eNodeB is in a congested state
  • Step S1202 the AF sends an authentication authorization request message to the PCRF, indicating the new service flow 3 information and related features;
  • step S1203 the PCRF sends a re-authentication request message to the PGW, and sends a rule 3 of the new service flow to the PGW, including the characteristics of the service flow 3 and the QoS parameters.
  • step S1204 the PGW determines that a dedicated bearer 3 needs to be established for the new service flow rule 3.
  • the PGW sends a create bearer request message to the SGW, and the message also includes the private bearer 3;
  • Step S1205 The PGW returns a re-authentication response message to the PCRF.
  • Step S1206 The PCRF returns an authentication authorization response message to the AF.
  • Step S1207 the SGW sends a create bearer request message to the MME, where the message includes the private bearer 3;
  • Step S1208 The MME sends an E-RAB setup message to the eNodeB, indicating that the bearer 3 is established, and the message is the same.
  • the NAS layer that is sent by the MME to the UE activates a proprietary EPS bearer context request message;
  • step S1109 the eNodeB determines that the new bearer 3 needs to preempt the established dedicated bearer 1 resource, and the policy is, for example, determining the priority, the low-value user, the low-value service, and the like, and the established bearer 2 is attached to the bearer 1,
  • Step S1210 the eNodeB initiates RRC reconfiguration of the bearer 3 to the UE, and sends a NAS layer activation private EPS bearer context request message to the UE;
  • Step S1212 the eNodeB initiates a release process of the bearer 1 and the bearer 2;
  • Step S1213 the RRC reconfiguration of the UE returning to bearer 3 is completed;
  • Step S1214 the UE returns an active proprietary EPS bearer context accept message of the bearer 3 to the MME;
  • Step S1215 the eNodeB returns an E-RAB setup response message to the MME, indicating that the bearer 3 is successfully established;
  • Step S1216 the MME returns a create bearer response message to the SGW, indicating that the bearer 3 is successfully established;
  • Step S1217 the SGW returns a create bearer response message to the PGW, and successfully establishes the bearer 3;
  • Step S1218 the PGW sends a credit control request-update message of the service flow rule 3 to the PCRF;
  • Step S1219 the PCRF returns a credit control response-update message to the PGW;
  • Step S1220 the PCRF sends a re-authentication request message of the new service flow 3 to the AF;
  • step S1221 the P-CSCF sends a re-authentication response message to the PCRF.
  • the dependencies between traffic flows are determined by the P-CSCF (i.e., AF) and provided to the PCRF.
  • the relationship of multiple traffic data flows may also be determined according to the network policy configured by the PCRF.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across multiple computing devices.
  • they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from this
  • the steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the network function entity is configured to perform resource reservation according to the dependency relationship of the resource allocation dependencies when the resource for specifying the auxiliary service flow in the plurality of service flows is allocated only when the independent service flow resource corresponding to the corresponding service flow is successfully allocated.
  • the network function entity can directly identify the relationship between the resource-specific bearers, and solves the problem that only a part of the dedicated bearer is successfully created when the network side establishes multiple dedicated bearers at the same time in the related art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供了一种承载资源的预留方法及装置，其中该方法包括：网络功能实体获取多个业务流及多个业务流间的依赖关系，其中，业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给指定辅助业务流分配资源；网络功能实体根据依赖关系执行资源预留。通过本发明，使得网络功能实体可以直接识别出资源专有承载之间的关系，解决了相关技术中网络侧同时建立多个专有承载时，只有部分专有承载创建成功的问题。

Description

承载资源的预留方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种承载资源的预留方法及装置。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)对下一代移动无线网络的项目叫系统架构演进(System Architecture Evolution，简称SAE)。图1是相关技术中系统架构演进SAE的结构框图，如图1所示，该SAE包括了如下网元：
演进的无线接入网(Evolved RAN简称为E-RAN)，用于提供更高的上下行速率，更低的传输延迟和更加可靠的无线传输。E-RAN中包含的网元是演进性基站(Evolved NodeB简称为eNodeB)，为终端的接入提供无线资源。
归属用户服务器(Home Subscriber Server简称为HSS)，用于永久存储用户签约数据。
移动管理实体(Mobility Management Entity，简称为MME)，用于控制面功能实体，临时存储用户数据的服务器，负责管理和存储UE上下文(比如UE/用户标识，移动性管理状态，用户安全参数等)，为用户分配临时标识，当UE驻扎在该跟踪区域或者该网络是负责对该用户进行鉴权；处理MME和UE之间的所有非接入层消息；触发在SAE的寻呼。
服务网关(Serving Gateway简称为SGW)，该网关是一个用户面实体，负责用户面数据路由处理，终结处于空闲状态的UE的下行数据。管理和存储UE的SAE承载(bearer)上下文，比如IP承载业务参数和网络内部路由信息等。是3GPP系统内部用户面的锚点，一个用户在一个时刻只能有一个Serving GW；
分组数据网网关(Packet Data Network Gatewa简称为PDN GW)，负责UE接入PDN的网关，分配用户IP地址，同时是3GPP和非3GPP接入系统的移动性锚点。用户在同一时刻能够接入多个PDN GW。
策略和合计费规则功能实体(Policy and Charging Rule Functionality简称为PCRF)，该功能实体主要根据业务信息和用户签约信息以及运营商的配置信息产生控制用户数据传递的服务质量(Quality of Service，简称为Qos)规则以及计费规则。该功能实体也可以控制接入网中承载的建立和释放。
在下一代移动网络中可以部署IP多媒体子系统(IP Multimedia Subsystem，简称为IMS)网络来提供基于IP的语音、视频等业务，从而取代2/3G网络中的电路交换(Circuit Switched，简称为CS)域。终端的语音业务通过LTE承载进行传输。目前主流运营商都选择为VoLTE分配专用接入点名称(Access Point name，简称为APN)，网络和终端为该APN建立一个QoS等级标识(QoS Class Identifier，简称为QCI)为5的默认承载，用于传输用户平时注册在IMS网络时所需要的信令，称为信令承载。当终端需要打电话或被呼叫时，临时为终端建立一个QCI为1的专有承载，用于传输语音数据，称为语音承载。当呼叫结束后，语音承载被释放。IMS网络同时支持视频通话业务，当用户进行视频通话时，网络为起呼和终呼用户同时建立QCI为1和2的两个专有承载，其中QCI为1的专有承载用于传输语音，QCI为2的专有承载用于传输视频。当视频通话结束后，QCI为1和2的两个专有承载被释放。
图2是相关技术中演进分组核心网EPC为1和2的专有承载建立QCI的方法流程图，如图2所示，该方法由演进分组核心网(Evolved Packet Core，简称为EPC)建立QCI为1和2的专有承载，并由IMS网络的P-CSCF触发，该方法的步骤包括：
步骤S201：P-CSCF发送鉴权授权请求消息给PCRF，指示两个新业务流信息及相关特征；
步骤S202：PCRF发送重鉴权请求消息给PGW，向PGW下发两个新业务流的规则，包含两个业务流的特征和QoS参数，其中两个业务流的QCI分别为1和2；
步骤S203：PGW判断需要为两个新业务流建立专有承载，发送创建承载请求消息给SGW，消息中同时包含两个专有承载，其QCI分别为1和2；
步骤S204：PGW向PCRF返回重鉴权应答消息；
步骤S205：PCRF向P-CSCF返回鉴权授权应答消息；
步骤S206：SGW向MME发送创建承载请求消息，消息中同时包含两个专有承载，其QCI分别为1和2；
步骤S207：MME向eNodeB发送E-RAB建立消息，指示建立QCI为1和2的两个承载，该消息同时包含MME发给UE的两条非接入层(Non-Access-Statum，简称为NAS)激活专有EPS承载上下文请求消息；
步骤S208：eNodeB发送RRC连接重配到UE；
其中，该RRC连接用于eNodeB创建QCI为1和2的两个承载，并将NAS激活专有EPS承载上下文请求消息发送给UE；
步骤S209：UE发送RRC连接重配完成到eNodeB；
其中，UE判断接受专有承载建立，本地创建专有承载，并向MME返回激活专有EPS承载上下文接受消息；注意UE会为两个专有承载返回两条激活专有EPS承载上下文接受消息；
步骤S210：UE从MME激活专有EPS承载上下文接受；
步骤S211：eNodeB向MME返回E-RAB建立响应消息，指示成功建立了哪些承载；
步骤S212：MME向SGW返回创建承载响应消息，指示成功建立了哪些专有承载；
步骤S213：SGW向PGW返回创建承载响应消息，指示成功建立了哪些专有承载；
步骤S214：PGW对建立成功的承载，向PCRF发送信用控制请求-更新消息，包含新建承载的计费标识、用户当前位置信息等；
步骤S215：PCRF向PGW发送信用控制请求-更新消息；
步骤S216：PCRF向P-CSCF发送重鉴权请求消息，包含新建承载的计费标识、用户当前位置信息等信息；
步骤S217：P-CSCF向PCRF发送重鉴权应答消息。
其中，P-CSCF接下来会完成主被叫用户间SIP会话的协商和建立。
从上面的流程可以看出，视频通话业务在一个流程中同时建立两个专有承载，按照目前3GPP协议的处理，在UE、eNodeB、MME、SGW、PGW各个设备中，多个承载之间是平等关系，各设备都可能出现只接受部分专有承载建立的情况。例如只成功建立了QCI为1的专有承载，或者只成功建立了QCI为2的专有承载。对于视频通话来说，只成功建立QCI为1的专有承载，可以将业务退化为语音通话；而只成功建立QCI为2的专有承载，则业务可以认同为失败，因为只有图像没有声音的通话用户不会忍受。目前对于相关技术中的这种异常，一般处理是由IMS网络判断业务失败，触发PCRF和PGW删除已建立的专有承载；或者IMS继续业务接续，后续由用户将业务挂断，从而触发网络将刚建立的专有承载进行释放。
针对相关技术中网络侧同时建立多个专有承载时，会出现只有部分专有承载创建成功的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例的主要目的在于提供一种承载资源的预留方法及装置，以至少解决相关技术中网络侧同时建立多个专有承载时，只有部分专有承载创建成功的问题。
根据本发明实施例的一个方面，提供了一种承载资源的预留方法，包括：网络功能实体获取多个业务流及所述多个业务流间的依赖关系，其中，所述业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给所述指定辅助业务流分配资源；所述网络功能实体根据所述依赖关系执行资源预留。
可选地，所述网络功能实体根据所述依赖关系执行资源预留包括：所述网络功能实体判断是否为所述独立业务流分配资源成功；在判断结果为是时，所述网络功能实体为所述辅助业务流分配资源；在判断结果为否时，所述网络功能实体不为辅助业务流分配资源。
可选地，所述网络功能实体为所述独立业务流分配资源包括：所述网络功能实体为所述独立业务流创建或修改专有承载；和/或，所述网络功能实体为所述辅助业务流分配资源包括：所述网络功能实体为所述辅助业务流创建或修改专有承载。
可选地，所述网络功能实体为所述独立业务流创建或修改专有承载包括：在所述网络功能实体为所述独立业务流的专有承载建立或修改成功时，所述网络功能实体接收辅助业务流的专有承载建立或修改请求；否则所述网络功能实体拒绝所述辅助业务流的专有承载建立或修改请求。
可选地，在所述网络功能实体建立与所述独立业务流对应的专有承载和/或所述辅助业务流对应的专有承载之后，所述方法包括：若所述网络功能实体释放所述独立业务流对应的资源，则所述网络功能实体根据所述依赖关系释放所述辅助业务流对应的资源。
可选地，所述网络功能实体释放所述独立业务流对应的资源包括：所述网络功能实体删除所述独立业务流对应的专有承载或修改所述独立业务流对应的专有承载；和/或，所述网络功能实体释放所述辅助业务流对应的资源包括：所述网络功能实体删除所述辅助业务流对应的专有承载或修改所述辅助业务流对应的专有承载。
可选地，所述网络功能实体包括：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。
可选地，所述依赖关系由策略和计费规则功能PCRF根据来自应用功能AF的指示或所述PCRF自身配置的网络策略决定。
根据本发明实施例的另一个方面，提供了一种承载资源的预留装置，位于网络功能实体侧，包括：获取模块，设置为获取多个业务流及所述多个业务流间的依赖关系，其中，所述业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给所述指定辅助业务流分配资源；执行模块，设置为根据所述依赖关系执行资源预留。
可选地，所述执行模块包括：判断单元，设置为判断是否为所述独立业务流分配资源成功；分配单元，设置为在判断结果为是时，为所述辅助业务流分配资源；在判断结果为否时，不为辅助业务流分配资源。
可选地，所述分配单元，还设置为为所述独立业务流创建或修改专有承载；和/或，为所述辅助业务流创建或修改专有承载。
可选地，所述执行模块还包括：控制单元，设置为在所述网络功能实体在所述独立业务流的专有承载建立或修改成功时，接收辅助业务流的专有承载建立或修改请求；否则拒绝所述辅助业务流的专有承载建立或修改请求。
可选地，所述装置包括：释放模块，若所述网络功能实体释放所述独立业务流对应的资源，则根据所述依赖关系释放所述辅助业务流对应的资源。
可选地，所述释放模块，还设置为删除所述独立业务流对应的专有承载或修改所述独立业务流对应的专有承载；或，删除所述辅助业务流对应的专有承载或修改所述辅助业务流对应的专有承载。
可选地，所述网络功能实体包括：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。
可选地，所述依赖关系由策略和计费规则功能PCRF根据来自应用功能AF的指示或所述PCRF自身配置的网络策略决定。
通过本发明实施例，采用网络功能实体依据用于指示多个业务流中的指定辅助业务流的资源只在与其对应的独立业务流资源分配成功时才能被分配资源的依赖关系执行资源预留的方式，使得网络功能实体可以直接识别出资源专有承载之间的关系，解决了相关技术中网络侧同时建立多个专有承载时，只有部分专有承载创建成功的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中系统架构演进SAE的结构框图；
图2是相关技术中演进分组核心网EPC为1和2的专有承载建立QCI的方法流程图；
图3是根据本发明实施例的承载资源的预留方法的流程图；
图4是根据本发明实施例的承载资源的创建装置结构框图；
图5是根据本发明实施例的承载资源的创建装置可选结构框图一；
图6是根据本发明可选实施例的网络创建所有专有承载都成功的方法流程图；
图7是根据本发明可选实施例的eNodeB只成功创建独立专有承载方法的流程图；
图8是根据本发明可选实施例的eNodeB只成功创建附属专有承载方法的流程图；
图9是根据本发明可选实施例的专有承载修改失败的方法流程图；
图10是根据本发明可选实施例的网元释放专有承载的方法流程图；
图11是根据本发明可选实施例的新业务抢占已建立的专有承载的方法流程图；
图12是根据本发明可选实施例的新业务抢占已建立的专有承载方法流程图。
具体实施方式
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本发明。
本实施例提供了一种承载资源的预留方法，图3是根据本发明实施例的承载资源的预留方法的流程图，如图3所示，该方法的步骤包括：
步骤S302：网络功能实体获取多个业务流及多个业务流间的依赖关系；
其中，业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给指定辅助业务流分配资源；
步骤S304：网络功能实体根据依赖关系执行资源预留。
在本实施例中，采用网络功能实体依据用于指示多个业务流中的指定辅助业务流的资源只在与其对应的独立业务流资源分配成功时才能被分配资源的依赖关系执行资源预留的方式，使得网络功能实体可以直接识别出资源专有承载之间的关系，解决了相关技术中网络侧同时建立多个专有承载时，只有部分专有承载创建成功的问题。
而对于本实施例涉及到的网络功能实体根据依赖关系执行资源预留的方式，在本实施例的一个可选实施方式中可以通过如下方式来实现：
步骤S11:网络功能实体判断是否为独立业务流分配资源成功；
步骤S12：在判断结果为是时，网络功能实体为辅助业务流分配资源，在判断结果为否时，网络功能实体不为辅助业务流分配资源。
而对于本实施例中涉及到的网络功能实体为独立业务流分配资源，在本实施例的一个可选实施方式中，该为独立业务流分配资源的方式可以通过如下方式来实现：网络功能实体为独立业务流创建或修改专有承载；为辅助业务流分配资源的方式可以通过如下方式来实现：网络功能实体为辅助业务流创建或修改专有承载。
此外，在本实施例中还涉及到在网络功能实体在为独立业务流的专有承载建立或修改成功时，网络功能实体接收辅助业务流的专有承载建立或修改请求；否则网络功能实体拒绝辅助业务流的专有承载建立或修改请求。
在本实施例的另一个可选实施例中，在网络功能实体建立与独立业务流对应的专有承载和/或辅助业务流对应的专有承载之后，本实施例的方法还可以包括：若网络功能实体释放独立业务流对应的资源，则网络功能实体根据依赖关系释放辅助业务流对应的资源。
需要说明的是，上述在释放独立业务流对应的资源之后，再释放对应的辅助业务流资源的一个可选应用场景为：在网络功能实体发生资源异常时，如资源拥塞；当然该场景仅仅是举例说明，其他的场景网络功能实体也是可以执行释放独立业务流对应的资源，并根据依赖关系释放辅助业务流对应的资源的操作。
而对于上述方式中网络功能实体释放独立业务流对应的资源包括：网络功能实体删除独立业务流对应的专有承载或修改独立业务流对应的专有承载；和/或，网络功能实体释放辅助业务流对应的资源包括：网络功能实体删除辅助业务流对应的专有承载或修改辅助业务流对应的专有承载。
可选地，网络功能实体包括：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。
对于本实施例的依赖关系可以由多种方式来决定，如由策略和计费规则功能PCRF根据来自应用功能AF的指示或PCRF自身配置的网络策略决定。
在本实施例中还提供了一种承载资源的预留装置，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”“单元”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软 件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本发明实施例的承载资源的预留装置结构框图，该装置位于网络功能实体侧，如图4所示，该装置包括：获取模块42，设置为获取多个业务流及多个业务流间的依赖关系，其中，业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给指定辅助业务流分配资源；执行模块44，与获取模块42耦合连接，设置为根据依赖关系执行资源预留。
可选地，执行模块44包括：判断单元，设置为判断是否为独立业务流分配资源成功；分配单元，与判断单元耦合连接，设置为在判断结果为是时，为辅助业务流分配资源；在判断结果为否时，不为辅助业务流分配资源。此外，分配单元，还可以设置为为独立业务流创建或修改专有承载；或，为辅助业务流创建或修改专有承载。
可选地，执行模块44还包括：控制单元，设置为在网络功能实体在独立业务流的专有承载建立或修改成功时，接收辅助业务流的专有承载建立或修改请求；否则拒绝辅助业务流的专有承载建立或修改请求。
图5是根据本发明实施例的承载资源的预留装置可选结构框图一，如图5所示，该装置还可以包括：释放模块52，与执行模块44耦合连接，若网络功能实体释放独立业务流对应的资源，则根据依赖关系释放辅助业务流对应的资源。
可选地，释放模块52，还可以设置为删除独立业务流对应的专有承载或修改独立业务流对应的专有承载；或，删除辅助业务流对应的专有承载或修改辅助业务流对应的专有承载。
对于本实施例涉及到的网络功能实体可以是：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。当然上述仅仅是举例说明，根据需要其他类型的网络功能实体也是在本实施例的保护范围之内。
对于本实施例涉及到的依赖关系可以由策略和计费规则功能PCRF根据来自应用功能AF的指示或PCRF自身配置的网络策略决定，需要说明的是该方式也仅仅是本实施例的可选实施方式，根据需要也可以由其他方式决定该依赖关系。
下面结合本发明可选实施例对本发明进行举例说明；
本可选实施例提供了一种承载资源的预留方法，通过该方法使得网络侧在多个专有承载同时建立过程中可以直接识别出专有承载之间的依赖关系，进而简化业务流程和设备处理复杂度，提高用户体验。
本可选实施例中网络侧对一个业务流的资源预留，需要增加判断此业务流是否依赖于另外一个业务流的资源预留是否成功；而网络侧资源预留的方式包括：承载建立、 承载修改、承载被抢占、承载被释放等过程。
承载建立的实现过程：
本发明可选实施例中的方法适用于应用实体(Application Function，简称为AF)通过PCRF触发PGW同时建立多个专有承载的场景。该方法的步骤包括：
步骤S21：AF向PCRF发送鉴权授权请求消息，包含多个业务流的特征时，增加多个业务流之间的依赖指示，即某些业务流是其他业务流创建成功时才需要创建的，称之为辅助业务流；不依赖于其他业务流的业务流称之为独立业务流；
可选的，在没有部署AF的场景下，由PCRF根据自身的策略，决定多个业务流规则之间的依赖关系。
步骤S22：PCRF向PGW发送重鉴权请求消息，下发多个业务流规则时，增加多个业务流之间的依赖指示；即某些业务流是其他业务流创建成功时才需要创建的，称之为辅助业务流；不依赖于其他业务流的业务流称之为独立业务流；
步骤S23：PGW向SGW发送创建承载请求消息；对应于独立业务流的专有承载称之为独立专有承载；对应于附属业务流的专有承载称之为附属专有承载；
步骤S24：PGW接收到SGW返回的创建承载响应消息，判断如有独立专有承载未被成功激活，但其附属专有承载激活成功，则认为附属专有承载也不应该被成功创建，并通知SGW删除激活的附属专有承载；如独立专有承载被成功激活，但部分附属专有承载未被激活，继续步骤5；专有承载未创建成功可能是由于UE、eNodeB、MME、SGW或PGW各设备未成功创建；
步骤S25：PGW向PCRF发送CCR-U消息，指示未被成功承载的相关规则，此处未被成功承载的相关规则对应的是所有未被激活的专有承载对应的规则。
可选的，PGW可以把多个专有承载之间的依赖指示通知给SGW，SGW可以把多个专有承载之间的依赖指示通知给MME，MME可以把多个专有承载之间的依赖指示通知给eNodeB。SGW，MME，eNodeB在建立专有承载时，可以根据本地资源情况，成功创建全部专有承载或只成功创建独立专有承载。如果判断下游节点出现了只建立附属专有承载的情况，及时通知下游节点去活附属专有承载。MME的下游节点为eNodeB，SGW的下游节点为MME。
承载修改的实现过程：
本可选实施例中的方法还适用于多个专有承载建立后，网络侧对专有承载发起修改的业务释放场景，该承载修改的步骤包括：
步骤S31：网络侧发起对附属/独立专有承载的修改，要求预留更多资源；
步骤S32：网元eNodeB/PGW等判断如被修改的专有承载是附属专有承载，依赖于某个独立专有承载，且本网元无法为独立专有承载预留更多的资源，则承载不被修改，仍然保持原来的资源。
承载被抢占或被释放的实现过程：
本可选实施例中的方法还适用于多个专有承载建立后，专有承载被释放或抢占的业务释放场景，该抢占或被释放的步骤包括：
步骤S41：eNodeB/MME/SGW/PGW网元，例如发生拥塞时，决定释放一部分专有承载或新业务抢占原有已建立的专有承载；
步骤S42：网元根据自身策略判定释放或抢占某个专有承载时，判断如有其他专有承载依赖于准备释放的专有承载，则将该专有承载和所有依赖于此专有承载的其他专有承载一并释放。
通过本可选实施例采用依据依赖关系识别出承载的方式，克服了相关技术中网络侧同时建立多个专有承载时，可能出现只有部分专有承载创建成功，从而影响用户体验的问题，避免了只成功建立部分专有承载导致的业务体验度不高，并且简化业务流程异常处理和网元处理复杂度。
实施例一
图6是根据本发明可选实施例的网络创建所有专有承载都成功的方法流程图；如图6所示，VoLTE用户做主叫时，网络侧创建两个专有承载都成功的一个实施例。本场景同样适用于VoLTE用户做被叫时，网络侧为其创建两个专有承载的场景。
步骤S601，VoLTE注册用户发起主叫请求；
步骤S602，P-CSCF发送鉴权授权请求消息给PCRF，指示两个新业务流信息1和2及相关特征，并且业务流2包含一个指示，标识该业务流附属于业务流1；
步骤S603，PCRF发送重鉴权请求消息给PGW，向PGW下发两个新业务流的规则1和2，包含两个业务流的特征和QoS参数，并且业务流规则2包含一个指示，标识该业务流附属于业务流规则1；
步骤S604，PGW判断需要为两个新业务流规则1和2建立专有承载1和2，且专有承载2为附属专有承载，附属于专有承载1；
步骤S605，PGW发送创建承载请求消息给SGW，消息中同时包含两个专有承载 1和2；
步骤S606，PGW向PCRF返回重鉴权应答消息；
步骤S607，PCRF向P-CSCF返回鉴权授权应答消息；
步骤S608，SGW向MME发送创建承载请求消息，消息中同时包含两个专有承载1和2；
步骤S609，MME向eNodeB发送E-RAB(E-UTRAN Radio Access Bearer，E-UTRAN无线接入承载)建立消息，指示建立两个承载1和2，该消息同时包含MME发给UE的两条NAS激活专有EPS承载上下文请求消息；
步骤S610，eNodeB向UE发起RRC(Radio Resource Control，无线资源控制)重配，并将NAS层激活专有EPS承载上下文请求消息发送给UE；
步骤S611，UE返回RRC重配完成；
步骤S612，UE判断接受专有承载建立，本地创建专有承载，并向MME返回激活专有EPS承载上下文接受消息，UE会为两个专有承载返回两条激活专有EPS承载上下文接受消息；
步骤S613，eNodeB向MME返回E-RAB建立响应消息，指示成功建立了承载1和2；
步骤S614，MME向SGW返回创建承载响应消息，指示成功建立了承载1和2；
步骤S615，SGW向PGW返回创建承载响应消息，指示成功建立了承载1和2；
步骤S616，PGW判断专有承载1和2都成功激活；
步骤S617，PGW向PCRF发送信用控制请求-更新消息，包含新建承载的计费标识、用户当前位置信息等；
步骤S618，PCRF向PGW返回信用控制应答-更新消息；
步骤S619，PCRF向P-CSCF发送重鉴权请求消息，包含新建承载的计费标识、用户当前位置信息等信息；
步骤S620，P-CSCF向PCRF发送重鉴权应答消息。
实施例二
图7是根据本发明可选实施例的eNodeB只成功创建独立专有承载方法的流程图；如图7所示，是VoLTE用户做主叫时，网络创建专有承载，eNodeB成功创建独立专 有承载的一个实施例。本场景同样适用于VoLTE用户做被叫时，网络侧为其创建两个专有承载的场景，该方法的步骤包括：
步骤S701，VoLTE注册用户发起主叫请求；
步骤S702，P-CSCF发送鉴权授权请求消息给PCRF，指示两个新业务流信息1和2及相关特征，并且业务流2包含一个指示，标识该业务流附属于业务流1；
步骤S703，PCRF发送重鉴权请求消息给PGW，向PGW下发两个新业务流的规则1和2，包含两个业务流的特征和QoS参数，并且业务流规则2包含一个指示，标识该业务流附属于业务流规则1；
步骤S704，PGW判断需要为两个新业务流规则1和2建立专有承载1和2，且专有承载2为附属专有承载，附属于专有承载1；
步骤S705，PGW发送创建承载请求消息给SGW，消息中同时包含两个专有承载1和2，分别对应新业务流规则1和2；
步骤S706，PGW向PCRF返回重鉴权应答消息；
步骤S707，PCRF向P-CSCF返回鉴权授权应答消息；
步骤S708，SGW向MME发送创建承载请求消息，消息中同时包含两个专有承载1和2；
步骤S709，MME向eNodeB发送E-RAB建立消息，指示建立两个承载1和2，该消息同时包含MME发给UE的两条NAS层激活专有EPS承载上下文请求消息；
步骤S710，eNodeB判断只能接受承载1创建，不能创建承载2，向UE发起RRC重配，并将NAS层激活专有EPS承载上下文请求消息发送给UE；
步骤S711，UE返回RRC重配完成；
步骤S712，UE只接受专有承载1建立，本地创建专有承载1，并向MME返回激活专有EPS承载上下文接受消息；对于专有承载2向MME返回激活专有EPS承载上下文拒绝消息；
步骤S713，eNodeB向MME返回E-RAB建立响应消息，指示成功建立了承载1，承载2创建失败；
步骤S714，MME向SGW返回创建承载响应消息，指示成功建立了承载1，承载2创建失败；
步骤S715，SGW向PGW返回创建承载响应消息，成功建立了承载1，承载2创 建失败；
步骤S716，PGW判断独立专有承载1被创建，独立专有承载2未被创建成功，则认为专有承载1可成功被创建；
步骤S717，PGW向PCRF发送信用控制请求-更新消息，包含新建承载的计费标识、用户当前位置信息，未成功装载的业务流规则2等；
步骤S718，PCRF向PGW返回信用控制应答-更新消息；
步骤S719，PCRF向P-CSCF发送重鉴权请求消息，包含新建承载的计费标识、用户当前位置信息，未成功装载的业务流2等；
步骤S720，P-CSCF向PCRF发送重鉴权应答消息。
实施例三
图8是根据本发明可选实施例的eNodeB只成功创建附属专有承载方法的流程图，如图8所示，该方法是VoLTE用户做主叫时，网络创建专有承载，eNodeB只成功创建附属专有承载的一个实施例。本场景同样适用于VoLTE用户做被叫时，网络侧为其创建两个专有承载的场景，该方法的步骤包括：
步骤S801，VoLTE注册用户发起主叫请求；
步骤S802，P-CSCF发送鉴权授权请求消息给PCRF，指示两个新业务流信息1和2及相关特征，并且业务流2包含一个指示，标识该业务流附属于业务流1；
步骤S803，PCRF发送重鉴权请求消息给PGW，向PGW下发两个新业务流的规则1和2，包含两个业务流的特征和QoS参数，并且业务流规则2包含一个指示，标识该业务流附属于业务流规则1；
步骤S804，PGW判断需要为两个新业务流规则1和2建立专有承载1和2，且专有承载2为附属专有承载，附属于专有承载1；
步骤S805，PGW发送创建承载请求消息给SGW，消息中同时包含两个专有承载1和2，分别对应新业务流规则1和2；
步骤S806，PGW向PCRF返回重鉴权应答消息；
步骤S807，PCRF向P-CSCF返回鉴权授权应答消息；
步骤S808，SGW向MME发送创建承载请求消息，消息中同时包含两个专有承载1和2；
步骤S809，MME向eNodeB发送E-RAB建立消息，指示建立两个承载1和2，该消息同时包含MME发给UE的两条NAS层激活专有EPS承载上下文请求消息；
步骤S810，eNodeB判断只能接受承载2创建，不能创建承载1，向UE发起RRC重配，并将NAS层激活专有EPS承载上下文请求消息发送给UE；
步骤S811，UE返回RRC重配完成；
步骤S812，UE只接受专有承载2建立，本地创建专有承载2，并向MME返回激活专有EPS承载上下文接受消息；对于专有承载1向MME返回激活专有EPS承载上下文拒绝消息；
步骤S813，eNodeB向MME返回E-RAB建立响应消息，指示成功建立了承载2，承载1创建失败；
步骤S814，MME向SGW返回创建承载响应消息，指示成功建立了承载2，承载1创建失败；
步骤S815，SGW向PGW返回创建承载响应消息，成功建立了承载2，承载1创建失败；
步骤S816，PGW判断附属专有承载2被激活，独立专有承载1未被创建成功，则认为专有承载1和2都应创建失败；
步骤S817，PGW向PCRF发送信用控制请求-更新消息，包含未成功装载的业务流规则1和2；
步骤S818，PCRF向PGW返回信用控制应答-更新消息；
步骤S819，PCRF向P-CSCF发送重鉴权请求消息，包含未成功装载的业务流1和2等；
步骤S820，P-CSCF向PCRF发送重鉴权应答消息。
步骤S821，PGW发起已经创建成功的专有承载2的释放，向SGW发起删除承载请求消息，消息中包含专有承载2。
步骤S822，PGW触发承载释放流程的其他处理。
实施例四
图9是根据本发明可选实施例的专有承载修改失败的方法流程图，如图9所示，是以eNodB网元资源预留失败为例，专有承载修改失败的实施例，该方法的步骤包括：
步骤S901，网络已经为UE建立专有承载1和2，其中专有承载1附属于专有承载2，eNodeB保存了专有承载1和2的依赖关系；
步骤S902，PCRF判断需要更新业务规则流1和2，提升其QoS参数；
步骤S903，PGW向SGW发送更新承载请求，包含专有承载1和2的新QoS参数；
步骤S904，SGW向MME发送更新承载请求，包含专有承载1和2的新QoS参数；
步骤S905，MME向eNodeB发送E-RAB修改消息，指示修改两个承载1和2，该消息同时包含MME发给UE的两条NAS层修改EPS承载上下文请求消息；
步骤S906，eNodeB判断由于资源不足，无法为承载1提升QoS，且承载2附属于承载1，也不应当为承载2提升QoS；
步骤S907，eNodeB向MME返回E-RAB修改响应，消息中指示承载1和2修改失败；
步骤S908，MME向SGW返回更新承载响应，消息中指示专有承载1和2的更新失败；
步骤S909，SGW向PGW返回更新承载响应，消息中指示专有承载1和2的更新失败；
步骤S910，PGW向PCRF返回重鉴权应答，消息中指示业务流规则1和2装载失败。
实施例五
图10是根据本发明可选实施例的网元释放专有承载的方法流程图，如图10所示是eNodeB/MME/SGW/PGW网元发生拥塞，网元释放专有承载的实施例。此过程实施的前提是eNodeB/MME/SGW或PGW网元中已保存了用户专有承载的附属关系。该方法的步骤包括：
步骤S1001，网元判断网络业务量突增，本设备发生拥塞；
步骤S1002，网元根据自身的策略，判断需要删除已建立的专有承载1，以减轻设备的负荷，策略例如判断优先级、低价值用户、低价值业务等；
步骤S1003，网元搜索设备中是否有其他专有承载依赖于删除专有承载1；
步骤S1004，网元删除专有承载1和依赖于删除专有承载1的其他专有承载。
实施例六
图11是根据本发明可选实施例的新业务抢占已建立的专有承载的方法流程图，如图11所示，是eNodeB/MME/SGW/PGW网元发生拥塞，新业务抢占已建立的专有承载的实施例。此过程实施的前提是eNodeB/MME/SGW或PGW网元中已保存了用户专有承载的附属关系。该方法的步骤包括：
步骤S1101，网元判断网络业务量突增，本设备发生拥塞；
步骤S1102，网元接收到一个高优先级业务建立请求；
步骤S1103，网元根据自身的策略，判断新业务需要抢占已建立的专有承载1资源，策略例如判断优先级、低价值用户、低价值业务等；
步骤S1104，网元搜索设备中是否有其他专有承载依赖于删除专有承载1；
步骤S1105，网元删除专有承载1和依赖于删除专有承载1的其他专有承载；
步骤S1106，网元接受高优先级业务建立请求。
实施例七
图12是根据本发明可选实施例的新业务抢占已建立的专有承载方法流程图，如图12示，是以eNodeB网元发生拥塞为例，新业务抢占已建立的专有承载的流程实施例。本场景中被抢占的专有承载和新业务可能属于同一UE，也可以是属于不同UE。该方法的步骤包括：
步骤S1201，eNodeB处于拥塞状态；
步骤S1202，AF发送鉴权授权请求消息给PCRF，指示新业务流3信息及相关特征；
步骤S1203，PCRF发送重鉴权请求消息给PGW，向PGW下发新业务流的规则3，包含业务流3的特征和QoS参数；
步骤S1204，PGW判断需要为新业务流规则3建立专有承载3，PGW发送创建承载请求消息给SGW，消息中同时包含专有承载3；
步骤S1205，PGW向PCRF返回重鉴权应答消息；
步骤S1206，PCRF向AF返回鉴权授权应答消息；
步骤S1207，SGW向MME发送创建承载请求消息，消息中同时包含专有承载3；
步骤S1208，MME向eNodeB发送E-RAB建立消息，指示建立承载3，该消息同 时包含MME发给UE的NAS层激活专有EPS承载上下文请求消息；
步骤S1109，eNodeB判断新承载3需要抢占已建立的专有承载1资源，策略例如判断优先级、低价值用户、低价值业务等，并且已建立的承载2附属于承载1，
步骤S1210，eNodeB向UE发起承载3的RRC重配，并将NAS层激活专有EPS承载上下文请求消息发送给UE；
步骤S1212，eNodeB发起承载1和承载2的释放流程；
步骤S1213，UE返回承载3的RRC重配完成；
步骤S1214，UE向MME返回承载3的激活专有EPS承载上下文接受消息；
步骤S1215，eNodeB向MME返回E-RAB建立响应消息，指示成功建立了承载3；
步骤S1216，MME向SGW返回创建承载响应消息，指示成功建立了承载3；
步骤S1217，SGW向PGW返回创建承载响应消息，成功建立了承载3；
步骤S1218，PGW向PCRF发送业务流规则3的信用控制请求-更新消息；
步骤S1219，PCRF向PGW返回信用控制应答-更新消息；
步骤S1220，PCRF向AF发送新业务流3的重鉴权请求消息；
步骤S1221，P-CSCF向PCRF发送重鉴权应答消息。
通过上述实施例可知，在同时建立多个专有承载时，采用多个专有承载之间有一定的依赖关系，网络侧在建立专有承载的时候能直接识别出这种依赖关系，进而可以增加了业务成功率，简化了流程处理和网络侧处理复杂度，减少了后续不必要的释放交互，并且减少建立感受度不好的业务概率，提高了用户体验。
在上述实施例中，业务流之间的依赖关系由P-CSCF(即AF)决定，并提供给PCRF。在其他实施例中(特别是在没AF的场景中)多个业务数据流的关系也可以根据PCRF配置的网络策略决定。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所 组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
上述仅为本发明的可选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
通过本发明，采用网络功能实体依据用于指示多个业务流中的指定辅助业务流的资源只在与其对应的独立业务流资源分配成功时才能被分配资源的依赖关系执行资源预留的方式，使得网络功能实体可以直接识别出资源专有承载之间的关系，解决了相关技术中网络侧同时建立多个专有承载时，只有部分专有承载创建成功的问题。

Claims (16)

  1. 一种承载资源的预留方法，包括：
    网络功能实体获取多个业务流及所述多个业务流间的依赖关系，其中，所述业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给所述指定辅助业务流分配资源；
    所述网络功能实体根据所述依赖关系执行资源预留。
  2. 根据权利要求1所述的方法，其中，所述网络功能实体根据所述依赖关系执行资源预留包括：
    所述网络功能实体判断是否为所述独立业务流分配资源成功；
    在判断结果为是时，所述网络功能实体为所述辅助业务流分配资源；在判断结果为否时，所述网络功能实体不为辅助业务流分配资源。
  3. 根据权利要求2所述的方法，其中，
    所述网络功能实体为所述独立业务流分配资源包括：所述网络功能实体为所述独立业务流创建或修改专有承载；和/或，
    所述网络功能实体为所述辅助业务流分配资源包括：所述网络功能实体为所述辅助业务流创建或修改专有承载。
  4. 根据权利要求3所述的方法，其中，所述网络功能实体为所述独立业务流创建或修改专有承载包括：
    在所述网络功能实体为所述独立业务流的专有承载建立或修改成功时，所述网络功能实体接收辅助业务流的专有承载建立或修改请求；否则所述网络功能实体拒绝所述辅助业务流的专有承载建立或修改请求。
  5. 根据权利要求3所述的方法，其中，在所述网络功能实体建立与所述独立业务流对应的专有承载和/或所述辅助业务流对应的专有承载之后，所述方法包括：
    若所述网络功能实体释放所述独立业务流对应的资源，则所述网络功能实体根据所述依赖关系释放所述辅助业务流对应的资源。
  6. 根据权利要求5所述的方法，其中，
    所述网络功能实体释放所述独立业务流对应的资源包括：所述网络功能实体删除所述独立业务流对应的专有承载或修改所述独立业务流对应的专有承载；和/或，
    所述网络功能实体释放所述辅助业务流对应的资源包括：所述网络功能实体删除所述辅助业务流对应的专有承载或修改所述辅助业务流对应的专有承载。
  7. 根据权利要求1至6任一项所述的方法，其中，所述网络功能实体包括：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。
  8. 根据权利要求1所述的方法，其中，所述依赖关系由策略和计费规则功能PCRF根据来自应用功能AF的指示或所述PCRF自身配置的网络策略决定。
  9. 一种承载资源的预留装置，位于网络功能实体侧，包括：
    获取模块，设置为获取多个业务流及所述多个业务流间的依赖关系，其中，所述业务流包括：独立业务流和辅助业务流，该依赖关系用于指示在与指定辅助业务流对应的独立业务流的资源分配成功时，给所述指定辅助业务流分配资源；
    执行模块，设置为根据所述依赖关系执行资源预留。
  10. 根据权利要求9所述的装置，其中，所述执行模块包括：
    判断单元，设置为判断是否为所述独立业务流分配资源成功；
    分配单元，设置为在判断结果为是时，为所述辅助业务流分配资源；在判断结果为否时，不为辅助业务流分配资源。
  11. 根据权利要求10所述的装置，其中，
    所述分配单元，还设置为为所述独立业务流创建或修改专有承载；和/或，为所述辅助业务流创建或修改专有承载。
  12. 根据权利要求11所述的装置，其中，所述执行模块还包括：
    控制单元，设置为在所述网络功能实体在所述独立业务流的专有承载建立或修改成功时，接收辅助业务流的专有承载建立或修改请求；否则拒绝所述辅助业务流的专有承载建立或修改请求。
  13. 根据权利要求11所述的装置，其中，所述装置包括：
    释放模块，若所述网络功能实体释放所述独立业务流对应的资源，则根据所述依赖关系释放所述辅助业务流对应的资源。
  14. 根据权利要求13所述的装置，其中，
    所述释放模块，还设置为删除所述独立业务流对应的专有承载或修改所述独立业务流对应的专有承载；或，删除所述辅助业务流对应的专有承载或修改所述 辅助业务流对应的专有承载。
  15. 根据权利要求9至14任一项所述的装置，其中，所述网络功能实体包括：分组数据网网关PGW、服务网关SGW、移动管理实体MME、演进性基站eNodeB。
  16. 根据权利要求9所述的装置，其中，所述依赖关系由策略和计费规则功能PCRF根据来自应用功能AF的指示或所述PCRF自身配置的网络策略决定。
PCT/CN2015/089077 2015-01-28 2015-09-07 承载资源的预留方法及装置 WO2016119465A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510043201.4A CN105992283A (zh) 2015-01-28 2015-01-28 承载资源的预留方法及装置
CN201510043201.4 2015-01-28

Publications (1)

Publication Number Publication Date
WO2016119465A1 true WO2016119465A1 (zh) 2016-08-04

Family

ID=56542329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/089077 WO2016119465A1 (zh) 2015-01-28 2015-09-07 承载资源的预留方法及装置

Country Status (2)

Country Link
CN (1) CN105992283A (zh)
WO (1) WO2016119465A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111194085A (zh) * 2018-11-16 2020-05-22 维沃移动通信有限公司 一种通道资源的控制方法、终端和通信网元
WO2022237505A1 (zh) * 2021-05-13 2022-11-17 华为技术有限公司 一种通信方法、设备及系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109362109B (zh) * 2018-11-26 2022-01-11 武汉虹信科技发展有限责任公司 S1切换过程恢复移动终端专有承载的方法和装置
CN112469114B (zh) * 2019-09-09 2022-11-18 成都鼎桥通信技术有限公司 一种会话初始协议注册方法和装置
CN112738854B (zh) * 2019-10-14 2021-11-12 大唐移动通信设备有限公司 一种语音切换方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1863149A (zh) * 2005-09-02 2006-11-15 华为技术有限公司 实现一组特定流的QoS控制的方法
CN101030963A (zh) * 2006-02-28 2007-09-05 华为技术有限公司 通信系统用资源预留方法和资源预留系统
EP2073463A1 (en) * 2007-12-21 2009-06-24 Nokia Siemens Networks S.p.A. Method and device for setting QoS parameters for predictive scheduling in wireless communication systems
CN102143139A (zh) * 2009-09-23 2011-08-03 阿瓦雅公司 对所利用带宽的基于优先级的动态优化

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1863149A (zh) * 2005-09-02 2006-11-15 华为技术有限公司 实现一组特定流的QoS控制的方法
CN101030963A (zh) * 2006-02-28 2007-09-05 华为技术有限公司 通信系统用资源预留方法和资源预留系统
EP2073463A1 (en) * 2007-12-21 2009-06-24 Nokia Siemens Networks S.p.A. Method and device for setting QoS parameters for predictive scheduling in wireless communication systems
CN102143139A (zh) * 2009-09-23 2011-08-03 阿瓦雅公司 对所利用带宽的基于优先级的动态优化

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111194085A (zh) * 2018-11-16 2020-05-22 维沃移动通信有限公司 一种通道资源的控制方法、终端和通信网元
CN111194085B (zh) * 2018-11-16 2023-12-26 维沃移动通信有限公司 一种通道资源的控制方法、终端和通信网元
WO2022237505A1 (zh) * 2021-05-13 2022-11-17 华为技术有限公司 一种通信方法、设备及系统

Also Published As

Publication number Publication date
CN105992283A (zh) 2016-10-05

Similar Documents

Publication Publication Date Title
US11979778B2 (en) Release of a second session of a wireless device by an access and mobility management function
WO2018145671A1 (zh) 跨系统的切换方法和装置、计算机存储介质
CN109548093B (zh) 网络切换的方法、装置及系统
US11297542B2 (en) Base station handover method, system, and computer storage medium
CN111771394A (zh) 用于ue上下文和pdu会话上下文管理的系统和方法
CN101425959B (zh) 一种承载处理方法和装置
CN103052053B (zh) 优先级业务处理方法、装置和系统
EP3624551A1 (en) Information processing method and apparatus
WO2016119465A1 (zh) 承载资源的预留方法及装置
CN114365518B (zh) 一种通过服务应用影响核心网络中数据业务路由的方法
KR102291766B1 (ko) 통신 시스템에서 데이터 흐름 전송을 위한 개선된 우선권 핸들링
WO2021092561A1 (en) Session management for a network slice
US20230109272A1 (en) Network Slice
US20220124564A1 (en) Policy control method and system, network element, and storage medium
CN101742453B (zh) 接入控制的方法、系统及接入控制网元
EP3297333A1 (en) Access method and corresponding access node, terminal and communication network
CN105359573B (zh) 用于在无线通信系统中卸载数据业务的方法和装置
US11102656B2 (en) Network access authorization method, related device, and system
KR20190004220A (ko) 5g 단말 서비스 연속성 관리를 위한 upf 장치 재배치 방법
US9420590B2 (en) Mobile gateway, control method for the same, and radio access network equipped with the same
CN115735371A (zh) 网络切片特定认证和授权
CN102685714A (zh) 一种支持双模双待终端同时通信的方法和系统
CN112105066B (zh) 一种局域网隧道建立、释放的方法及设备
WO2017128819A1 (zh) 基于应用的策略和计费控制方法及装置、存储介质
WO2023045472A1 (zh) 一种通信方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15879663

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15879663

Country of ref document: EP

Kind code of ref document: A1