WO2007025461A1

WO2007025461A1 - Procede et systeme de gestion de la qos d'un ensemble de flux speciaux

Info

Publication number: WO2007025461A1
Application number: PCT/CN2006/002179
Authority: WO
Inventors: Yong Huang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-09-02
Filing date: 2006-08-25
Publication date: 2007-03-08
Also published as: CN1863149A; CN100450087C

Abstract

L'invention porte sur un procédé de gestion de la QOS d'un ensemble de flux spéciaux dont le noyau comporte les étapes suivantes: (i) dans la prochaine génération à trames NGN, la couche de gestion de services transmet une demande de A method for realizing QOS management of a set of special streams. The kernel of the invention includes: first, in the next generation network NGN frame, the service control layer transmits a resource request to the bearing control layer, and the resource request message carries the stream relation indication information which indicates the relation between the service stream corresponding to the request and the other special streams; then the bearing control layer performs resource decision for the service stream corresponding to the request according to the stream relation indication information and the special stream information, and transmits it down to the data bearing layer to manage the QOS of the service stream. The invention increases the stream relation information for the stream having special relation, RACS reads the stream relation information and controls the service stream according to the stream relation. Thus the invention realizes control and management of QOS, and saves network resource.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a controllable QoS (Quality of Service) that supports a next-generation network (NGN). Method and system. Background of the invention

NGN is a packet-based network that provides telecommunication services; a variety of broadband capabilities and QoS-guaranteed transport technologies; and its service-related functions are independent of its transport technology. NGN allows users to freely access different service providers; NGN supports universal mobility.

The basic features of NGN are as follows: Packet transmission; Control functions are separated from bearer, call/session, application/service; Service provision is separated from the network, providing an open interface; Provides a wide range of services and applications, including real-time, using basic service component modules , streaming, non-real-time and multimedia services; with end-to-end QoS and transparent transmission capabilities; interoperability with traditional networks through open interfaces; universal mobility; allowing users to freely access different service providers; supporting diverse signage systems, It can be parsed into an IP address for IP network routing; the same service has uniform service characteristics; converged fixed and mobile services; business functions are independent of the underlying transport technology; adapt to all management requirements, such as emergency telecommunications, security and privacy Sexual requirements.

QoS is a security mechanism of the network, and is a technology used to solve problems such as network delay and congestion.

Classification and definition of QoS: The purpose of classifying and defining QoS is to enable the network to manage and allocate resources according to different types of QoS.

In the process of managing and allocating resources, the following mainly involves the following processing:

Admission control and negotiation processing, that is, allowing users to enter the network for multimedia information transmission and negotiate their QoS according to the usage of resources in the network.

In order to provide users with satisfactory QoS, it is necessary to make reservations for corresponding resources such as end systems, routers, and transmission bandwidth to ensure that these resources are not used by other applications.

Resource scheduling and management processing. After making a reservation for resources, whether these resources can be obtained depends on the corresponding resource scheduling and management system.

With the development of Internet networks, telecom services with QoS guarantees are also migrating to IP-based packet networks. Because the core idea of the Internet is to share and do its best, and the telecom service requires strict QoS guarantee, the two concepts are different. Therefore, it is necessary to study and design a new Internet architecture and QoS management architecture. Guarantee to run telecommunication services on the Internet.

The next generation network consists of three logical layers: data bearer layer, bearer control layer, and service control layer. The data bearer layer carries the user service data flow; the bearer control layer applies control behavior to each network element of the data bearer layer, so that the network has manageability and operational characteristics; and the bearer control layer provides a unified access interface to the service control layer. The differences between different bearer networks are shielded; the service control layer is responsible for service-related control, which provides management for various services for users.

The European Telecommunications Standards Institute (ETSI) TISPAN divides the access network bearer control plane in the NGN network into two systems, the Network Access Attachment Subsystem (NASS) and the Resource Admission Control Subsystem (RACS). The NASS stores the user's subscription information, and is mainly responsible for access authentication and accounting, address allocation, user network parameter configuration, and client device management of the access user. The RACS is mainly responsible for end-to-end Q0S routing and management.

The RACS architecture is shown in Figure 1. The following describes the RACS architecture.

In Figure 1, SPDF is a service-based session policy decision function module that provides a Gq' interface to the service control layer to provide bearer services for application functions (AF). This interface accepts service-based QOS requests from the service control layer. When a user requests a service, a session is established with the AF. The AF requests the QOS for the session according to the service request in the session, and the resource request is based on the media. Each media may include multiple flows. . The request includes the type of the service, the bandwidth, the quintuple information of the flow, the user identifier, the flow operation indication, and the like, that is, the service control layer requests the bearer control layer to set up a Q0S channel for its specific service.

SPDF holds policy rules, has the ability to make local policy decisions, and translates the information in the AF setup request into QOS parameters.

Through the Rq interface, SPDF passes the decision result and the Q0S parameter to the access resource admission control function (A-RACF). In Figure 1, A_RACF is responsible for the admission control of the Q0S. It receives the QOS request for the managed access network through the Rq interface, and obtains the subscriber's subscription data and location information from the NASS through the e4 interface, and determines whether the current network can be Provide Q0S for this user.

A- RACF sends a clear acceptance/non-acceptance response to SPDF after the Q0S is reserved or implemented.

For the implementable QOS request, the A-RACF passes the command to the RCEF and the access node AN through the Re and Ra interfaces according to the convection status indication in the request. The RCEF is located in the IP edge device of the access network and is responsible for the implementation of the Q0S.

In Figure 1, the SPDF implements QOS and performs network address translation or network parameter conversion operations to the C-BGF through the la interface. The RACS functional architecture can support management, control, and implementation of user end-to-end QOS. At the same time, it provides functional partitioning and interfaces for network operators and service providers. Provides the ability to authenticate and bill between different carriers. In the existing RACS functional architecture, the request from the service control layer AF to the SPDF in the bearer control layer is session-based, using the Gq' interface between them. In the message of the Gq' interface, there is only a description of the stream itself, such as media type, bandwidth information, etc., but there is no description about the relationship between streams.

For example, when a service Q0S having a specific flow relationship such as a multicast relationship or an anycast relationship, which is centered on one endpoint TO and reaches multiple endpoints T1, Τ2, Τ3, is created, it is difficult or impossible to implement. For example, for multicast, only three pipes from T1, Τ2, and Τ3 can be established from the endpoint TO to implement multicast services. This wastes bandwidth resources on the carrier layer, and the TO also needs to copy multiple points of information. For anycast, the setup request can only be sent to the bearer control layer by the AF three times, and the results of these requests are managed. The multicast refers to a communication mode in which a data packet sent from a source point is simultaneously received by a specific plurality of destination endpoints, and the packet is copied only on the branch routing device closest to the destination endpoint on the transmission channel; The anycast refers to a communication method in which a data message sent from a source point is received by any one of a plurality of destinations to achieve a communication destination.

In summary, the existing RACS functional architecture system cannot support the description of the relationship between flows, and thus cannot support resource management and admission control with specific relationship flows between each other. The management of these relationships by AF is complex and inefficient, and at the same time, it may also bring waste of bearer bandwidth. SUMMARY OF THE INVENTION It is an object of the present invention to provide a method and system that can control a flow having a specific relationship to implement QoS control of a specific set of flows, so as to solve the problem that the existing management process is complicated and resources may be wasted.

The object of the invention is achieved by the following technical solutions:

The present invention provides a method of implementing a specific set of flow QoS management, characterized in that:

The service control layer initiates a resource request to the bearer control layer, where the resource request carries flow relationship indication information indicating a relationship between the service flow corresponding to the request and other specific flows;

The bearer control layer transmits the flow relationship indication information when performing resource request control between different functional entities in the layer, and performs resource decision on the service flow corresponding to the request according to the flow relationship indication information and the specific flow information, and controls the data bearer. Layer, the QoS of the service flow is managed by the data bearer layer.

The interface that delivers the flow relationship indication information includes, but is not limited to, the Gq', Rq interfaces defined in the resource admission control subsystem RACS.

The method further includes: transmitting the identification information of the specific flow group and the flow relationship indication information at the same time. Methods for determining identification information for a particular flow group include, but are not limited to:

The identifier of the flow established by the first of the set of flows; or,

The application function of the service control layer AF additionally assigns a specific global unique identifier to the group of streams.

The relationship between the specific flows includes, but is not limited to, a multicast relationship or an anycast relationship.

The bearer control layer in the NGN network performs unified release, modification, or update management on the resources allocated for the specific flow group according to the identification information of the specific flow group.

The present invention also provides a method of implementing a specific set of flow QoS management, characterized in that:

The bearer control layer performs related control on the request data bearer layer, and delivers flow relationship indication information indicating the service flow corresponding to the request and other specific flows;

The data bearer layer may search for the relevant flow according to the flow relationship indication information, and implement a specific operation corresponding to the flow relationship indication information to implement control of a group of flows.

The interface that communicates the flow relationship indication information includes, but is not limited to, a Re, Ra, or la interface defined in the Resource Admission Control Subsystem RACS.

The identifier of the flow established by the first of the set of flows;

Or,

When the specific flow is a multicast service flow, the bearer control layer sends the control parameter of the multicast service flow to the data bearer layer with the IP forwarding function to implement the function, and simultaneously delivers the corresponding multicast receiving end point. The unicast IP address is given to this function. This function obtains the physical and logical ports of the receiving endpoint through the route query of the unicast IP address, and performs corresponding QoS management.

When the specific flow is a multicast service flow, the bearer control layer sends the control parameter of the multicast service flow to the network access function body that does not have the IP forwarding capability, and simultaneously delivers the user to the access device. Physical and / or logical access identification, this function identifies the user port through the user's physical and / or logical access identification, and performs corresponding QoS management.

When the specific flow is a multicast service flow, the QoS control/implementation function of the bearer control layer or the data bearer layer needs to maintain a count value for each multicast QoS flow, and when a requested multicast QoS is found in the function When the device managed by the device has the same ingress port and egress port, the function body count value is incremented by one; when receiving a request to release the multicast QoS flow, the count value is decremented by one; when the count value is zero, the release is The resources occupied by this multicast stream. The present invention also provides a system for implementing a specific flow QoS management, including a flow relationship indication information delivery unit, for transmitting a corresponding service flow and other specific flows in the process of performing flow QoS management information transmission. Flow relationship indication information of the relationship;

And a flow QoS management unit, configured to implement a QoS management operation on the corresponding service flow according to the flow relationship indication information and the corresponding flow QoS management information.

The flow relationship indicates that the information delivery unit is specifically disposed in the service control layer entity, and/or is disposed in the bearer control layer entity.

In the present invention, if the flow relationship indicates that the information transfer unit device is in the service control layer entity, it will transmit the flow relationship indication information through the GQ, and the Rq interface.

In the present invention, if the flow relationship indicates that the information transfer unit device is in the bearer control layer entity, it will transmit the flow relationship indication information through the Re, Ra or la interface.

In the present invention, a counter is further provided in the bearer control layer and/or the data bearer layer for counting the number of multicast streams having the same ingress port and egress port in the managed device, and when the counter is zero , triggers the release of the corresponding resource.

As can be seen from the technical solution provided by the present invention, the present invention adds flow relationship information to a flow having a specific relationship, so that the RACS can control the flow of the traffic relationship according to the flow relationship, thereby facilitating the traffic flow. It implements corresponding QoS control and management for a set of flows with a specific relationship such as multicast or anycast, and saves network resources. For example, flexible management of QoS of a set of session services can be implemented in the NGN network. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 shows the structure of the RACS in the bearer control layer;

2 is a flowchart of a specific implementation of multicast QoS implementation control in the present invention;

Figure 3 is a schematic diagram of multicast QoS implementation control and data flow;

FIG. 4 is a schematic diagram of a specific implementation structure of the system according to the present invention.

·

The core of the present invention is that the service control layer in the NGN architecture initiates a resource request with the flow relationship indication information to the bearer control layer, so that the bearer control layer can pair the flow according to the indication information of the flow relationship. Control is performed to achieve QoS control for a particular flow.

In the present invention, each of a group of streams that need to be transmitted has a specific relationship, such as a multicast relationship, anycast relationship Department and so on. This particular relationship between the streams is recorded in the stream relationship information transmitted with the set of streams. The bearer control layer applies control to each network element of the data bearer layer according to the flow relationship information to implement QoS control and management of the specific set of flows.

The so-called flow relationship refers to a relationship between a specific one stream or a plurality of streams and other streams, and the relationship may be a multicast relationship or an anycast relationship, but is not limited thereto, and may be other relationships, and the present invention is In the following description, only the management of the flow with the multicast relationship is taken as an example, but the specific implementation of the present invention is not limited to the multicast application instance.

In the present invention, the flow relationship information specifically includes:

Flow relationship indication: is a value used to indicate the relationship between different flows. It can usually be represented by an enumerated type. Different values can be used to indicate <independent, multicast, anycast...>. Required for the flow relationship.

Identification of a specific flow group: This identifier is a globally unique identifier used to identify a specific flow group information. For example, it can be a unified identifier for all multicast flows in a multicast group. This item is optional for the flow relationship. Whether to carry this option is related to different stream identification implementation technologies.

The implementation of the present invention mainly focuses on the RACS system and related interfaces in the bearer control layer. The structure of the RACS is shown in FIG.

The specific implementation of the method of the present invention will be further described in detail below with reference to the accompanying drawings.

An example of a specific implementation of the method of the present invention is shown in FIG. 2 and FIG. 3, and specifically includes:

Figure 2 shows the implementation flow of multicast QoS implementation control. Figure 3 shows the multicast Q0S implementation control and data flow diagram. The implementation control of QoS will be described in detail in conjunction with Figure 2 and Figure 3. First, the network structure of the application of the present invention will be described with reference to FIG. 3:

The data bearer layer in the NGN network includes the sequentially connected access node AN, the IP edge device IP EDGE, the core edge gateway function c-BGF, and the core network Core Network; the service control layer includes the AF; the bearer control layer includes the access resource admission The control function A-RACF and the service-based session policy determine the function SPDF.

The SPDF is connected to the AF through the Gq interface, and is connected to the c-BGF through the la interface;

The A-RACF is connected to the NASS through the e4 port, connected to the AN through the Ra port, connected to the RECF through the Re port, and connected to the SPDF through the Rq port.

In Figure 3, the dashed line indicates the control flow and the solid line indicates the data path.

A, B, and C in FIG. 3 are respectively three user terminals, wherein user terminals A and B access the network through the access device AN1, and the user terminal C accesses the network through the AN2.

The access devices AN1 and AN2 in this structure may not have IP forwarding capability. The specific implementation process of the method according to the present invention will be described below with reference to FIG. 2: Implementing a specific flow QoS management is mainly divided into two parts:

First, the service control layer initiates a resource request with the flow relationship indication information to the bearer control layer, and the bearer control layer performs resource decision on the service flow corresponding to the request according to the flow relationship indication information and the specific flow information in the layer. The detailed process is as described in step 201 and step 202;

Then, the bearer control layer sends the flow relationship indication information to the data bearer layer, and the data bearer layer performs the corresponding specific operation according to the flow relationship, and implements control of a set of flows, and the detailed process is as follows: step 203, step 204, and Step 205.

The above two parts can be regarded as independent control management processes. However, if the above two parts of operations are performed in sequence, the service control layer finally controls the data bearer layer through the bearer control layer to implement QoS management for a specific set of flows.

As shown in Figure 2, the details of the corresponding processing steps are as follows:

In step 201, the user terminal A establishes a contact with the server AF that provides the multicast service, and successfully establishes a QoS pipe from the AF to the A through the bearer control system. In the process of establishing the Q0S control of the A, the flow relationship indication is also carried as a group. The indication information of the broadcast, and may carry the flow group identification information (whether or not the flow group identification information is carried depends on different implementation methods). Here, for the sake of convenience, the server is referred to as AF on both the control plane and the data plane. Actually on the control plane, AF may contain a service control system such as IMS (IP Multimedia System);

The flow group identification information is a unique identifier for a group of flows, where, for multicast, the flow group identifier information is an identifier of a multicast tree formed by one multicast stream; The flow group identifier may use the flow identifier information when the first flow is established, or may be assigned a unique identifier information for identifying the flow of the group by the AF; The quintuple information finds the relevant stream, so the stream group identification information may also not carry the transmission.

Step 202: After the user terminal A establishes contact with the server AF and establishes a QoS pipeline from AF to A, the terminal user B also sends the same service flow request to the AF, and the service flow has a multicast feature, and goes to A. The stream originates from the same multicast stream.

After B passes AF authentication, AF requests QoS for user B. The AF transmits the flow relationship information about the user B to the SPDF through the Gq' port, and the flow relationship information includes a flow relationship indication, where the content indicated by the flow relationship is multicast.

Step 203: The SPDF performs local policy check according to the multicast corresponding policy according to the multicast flow relationship indication from the AF. After the local policy check, if SPDF agrees to implement the QoS with multicast relationship, it will pass the flow relationship information to the A-RACF through the Rq port along with the resource control request.

Step 204: The A-RACF receives the flow relationship information describing the flow relationship through the Rq port; from the NASS through the E4 port. Obtain the subscription data of user B and the access location information of B. The A-RACF checks whether the subscriber data of the subscriber B allows the QoS request, and also checks whether the current QoS resource can accept the QoS request. According to the multicast indication of the flow, the A-RACF checks according to the multicast corresponding policy.

If the check is passed, the A-RACF will send the QoS parameters of B and the multicast indication to all access devices that can reach B. In this embodiment, the access devices are AN1 and IP EDGE.

According to the resource request and the multicast indication of the flow, the C-BGF performs bearer setting according to the characteristics of the multicast, and ensures the user B's

Q0S.

Step 205: For AN1, because the IP route is not supported, the A-RACF simultaneously sends the access line identifier of the user B, that is, the physical and logical identifiers, to the AN1, and the AN1 searches for and identifies the flow originally established to the A, and adds the Flow to user B's multicast Q0S channel;

The manner in which the AN1 finds and recognizes the flow that the plaintiff establishes to the A includes: if only the multicast indication information is delivered, the quintuple of the flow may be used to determine that the established multicast stream to the A is identified; If the multicast indication and the identifier information about the multicast group flow are simultaneously transmitted, the identifier information may be used to find the corresponding stream to the A;

For IP EDGE, the A-RACF can pass User B's unicast address to IP EDGE and all associated intermediate IP devices based on the multicast indication. IP EDGE finds the flow of the original A application, and according to the unicast IP address of user B, can find the access port of user B on the IP EDGE, and establish the Q0S flow to user B; wherein, the way of identifying the original A application flow is identified. The lookup used in AN1 recognizes that the corresponding stream is handled in the same way.

In this embodiment, IP EDGE finds that user B is on the same port as the original user A, and does not need to make a new bandwidth allocation. It only needs to add a count of the flow shared by the AB to be used for the release operation of the multicast stream. Just fine. The above is the process when user B applies for a multicast service flow.

Similarly, when user C applies for this multicast service flow, A-RACF performs the same operation as B. Different from B, because the physical port of C is different from A and B, IP EDGE will allocate a Q0S channel from C IP EDGE uplink port to user C port.

When the bearer control layer delivers control for a multicast service flow (including gating and Q0S control) to the data bearer device with IP forwarding capability, the unicast IP address of the multicast receiving endpoint is simultaneously sent to the device. The device obtains the physical and logical ports of the receiving endpoint through the route query of the unicast IP address.

When the bearer control layer delivers control for a multicast industry stream (including gating and QOS control) to a terminal access device that does not have IP forwarding capability, the physical and logical access identifier of the user on the device is simultaneously delivered. The device identifies the user port through the physical and logical access identifier of the user. For a Q0S implementation function, maintain a count for each multicast Q0S stream. When a requested group is found When the broadcast QOS has the same ingress port and egress port in the device managed by this function, the function body count is incremented by one and returns successfully. When a request to release the multicast Q0S stream is received, the count is decremented by one. When the count is reduced to zero, the resources occupied by the multicast stream are released. The present invention provides a system for implementing a specific flow QoS management. The specific implementation structure is as shown in FIG. 4, and mainly includes the following processing units:

The flow relationship indication information delivery unit is configured to: in the process of performing the flow QoS management information transfer, the flow relationship indication information of the corresponding service flow and the other specific flow relationship, where the flow relationship indication information includes: Stream, multicast stream or anycast stream, etc.;

And a flow QoS management unit, configured to implement a QoS management operation on the corresponding service flow according to the received flow relationship indication information and the corresponding flow QoS management information.

In the system of the present invention, the flow relationship indication information transmission unit is set in the service control layer entity, or is set in the bearer control layer entity, and of course, may be simultaneously set in the service control layer and the bearer control layer. In the entity, where

If the flow relationship indicates that the information delivery unit device is in the service control layer entity, it will transmit the flow relationship indication information through the Gq' and Rq interfaces;

If the flow relationship indicates that the information transfer unit device is in the bearer control layer entity, it will transmit the flow relationship indication information through the Re, Ra or la interface. In the system of the present invention, when the flow relationship indicates that the information delivery unit is disposed in the service control layer entity, the corresponding flow QoS management unit is disposed in the bearer control layer, and:

The flow relationship indication information delivery unit is configured to: when the service control layer initiates a resource request to the bearer control layer, the resource request carries a flow relationship indication for indicating a relationship between the service flow corresponding to the request and other specific flows. Information

a flow QoS management unit, configured to control the bearer control layer to transmit the flow relationship indication information when performing resource request control between different functional entities in the layer, and according to the flow relationship indication information and the specific flow information, the service corresponding to the request The flow makes resource decisions, controls the data bearer layer, and manages the QoS of the service flow by the data bearer layer.

In the system of the present invention, a counter is further provided in the bearer control layer and/or the data bearer layer for counting the number of multicast streams having the same ingress port and egress port in the managed device, and When the counter is zero, the resource information allocated for the corresponding multicast stream is triggered to be released, thereby facilitating flexible management of resources.

- in the system of the present invention, when the flow relationship indicates that the information transfer unit is set to the bearer control layer entity In the middle, the corresponding flow QoS management unit is set in the data bearer layer, and:

The flow relationship indication information delivery unit is configured to enable the control bearer control layer to request the data bearer layer to perform the related control process, and also send the flow relationship layer indicating the flow relationship indication information between the service flow corresponding to the request and the other specific flow to the data bearer layer. ;

And a flow QoS management unit, configured to control the data bearer layer to search for the related flow according to the flow relationship indication information, and implement a specific operation corresponding to the flow relationship indication information, so as to implement control on a set of flows. The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Rights request

A method for implementing a specific flow QoS management, comprising: a service control layer initiating a resource request to a bearer control layer, where the resource request carries a service flow corresponding to the request and other specific Flow relationship indication information of the flow relationship;

The bearer control layer transmits the flow relationship indication information when the resource request control is performed between different functional entities in the layer, and performs resource decision on the service flow corresponding to the request according to the flow relationship indication information and the specific flow information, and controls the data bearer layer. The QoS of the service flow is managed by the data bearer layer.

2. The method for implementing a specific flow QoS management according to claim 1, wherein: the interface for transmitting the flow relationship indication information includes, but is not limited to, Gq defined in the resource admission control subsystem RACS, Rq interface.

3. A method of implementing a set of specific flow QoS management according to claim 1, wherein said method further comprises:

The identification information of the specific flow group is simultaneously transmitted with the flow relationship indication information.

4. A method for implementing a specific flow QoS management according to claim 3, wherein the method for determining identification information of a specific flow group includes but is not limited to:

The identifier of the flow established by the first of the set of flows;

Or,

A method for implementing a specific flow QoS management according to any one of claims 1 to 4, characterized in that the relationship between the specific flows includes, but is not limited to, a multicast relationship or an anycast relationship.

The method for implementing a specific flow QoS management according to any one of claims 1 to 4, wherein the method further comprises: carrying a control layer in the NGN network according to the specific flow The identification information of the group is uniformly released, modified or updated for the resources allocated for the specific flow group.

7. A method of implementing a set of specific flow QoS management, characterized by:

The bearer control layer requests the data bearer layer to perform related control, and sends, to the data bearer layer, flow relationship indication information indicating the service flow corresponding to the request and other specific flows;

The data bearer layer searches for the related stream according to the flow relationship indication information, and implements a specific operation corresponding to the flow relationship indication information to implement control of a group of flows.

8. A method of implementing a set of specific flow QoS management according to claim 7, wherein: The interface that communicates the flow relationship indication information includes, but is not limited to, a Re, Ra, or la interface defined in the resource admission control subsystem RACS.

The method for implementing a specific flow QoS management according to claim 7, wherein the method further comprises:

10. A method for implementing a specific flow QoS management according to claim 9, wherein the method for determining identification information of a specific flow group includes, but is not limited to, adopting a flow established by the first one of the flow groups. Identification

Or, . The application function AF of the service control layer additionally assigns a specific global unique identifier to the group of streams.

A method for implementing a specific flow QoS management according to claim 7, wherein the relationship between the specific flows includes, but is not limited to, a multicast relationship or an anycast relationship.

The method for implementing a specific flow QoS management according to claim 7, wherein: when the specific flow is a multicast service flow, the bearer control layer controls parameters of the multicast service flow. When the function is implemented on the data bearer layer that implements the IP forwarding function, the unicast IP address of the corresponding multicast receiving endpoint is sent to the function body. The function body obtains the receiving endpoint by querying the route of the unicast IP address. Physical and logical ports, and perform corresponding QoS management.

The method for implementing a specific flow QoS according to claim 7, wherein: when the specific flow is a multicast service flow, the bearer control layer controls parameters of the multicast service flow. When the network access function is not provided with the IP forwarding capability, the physical and/or logical access identifier of the user on the access device is simultaneously delivered, and the function identifies the user by using the physical and/or logical access identifier of the user. Port, and perform corresponding QoS management.

When the specific flow is a multicast service flow, the QoS control/implementation function of the bearer control layer or the data bearer layer needs to maintain a count value for each multicast QoS flow when a requested multicast QoS is found in the function. When the device managed by the device has the same ingress port and egress port, the function body count value is incremented by one; when receiving a request to release the multicast QoS flow, the count value is decremented by one; when the count value is zero, the release is The resources occupied by this multicast stream.

15. A system for implementing a set of specific flow QoS management, comprising:

The flow relationship indication information delivery unit is configured to deliver the pair in the process of performing flow QoS management information transmission Flow relationship indication information of the relationship between the business flow and other specific flows;

The system for implementing a specific flow QoS management according to claim 15, wherein the flow relationship indication information transmission unit is specifically disposed in a service control layer entity, and/or is disposed in a bearer control layer. In the entity.

17. The system for implementing a set of specific flow QoS management according to claim 16, wherein if the flow relationship indicates that the information transfer unit device is in the service control layer entity, it will pass the Gq' and Rq interfaces. The flow relationship indication information is delivered.

18. The system for implementing a specific flow QoS management according to claim 16, wherein if the flow relationship indicates that the information transfer unit device is in a bearer control layer entity, it will pass Re, Ra or la. The interface performs flow relationship indication information transmission.

The system for implementing a specific flow QoS management according to claim 18, wherein a counter is further set in the bearer control layer and/or the data bearer layer for counting in the managed device. The number of multicast streams with the same inbound and outbound ports, and when the counter is zero, triggers the release of the corresponding resources.