WO2007073690A1

WO2007073690A1 - Worldwide interoperability for microwave access system and service flow arrangement method in the system

Info

Publication number: WO2007073690A1
Application number: PCT/CN2006/003602
Authority: WO
Inventors: Hongcheng Zhuang; Ke Zeng; Ming Zhou
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-12-27
Filing date: 2006-12-26
Publication date: 2007-07-05

Abstract

A WiMAX system and service flow arrangement method in this system. The WiMAX system includes a Service Flow Management module SFM, a Service Flow Authorization module SFA and a Policy Function module PF. The arrangement process of service flow includes: setting flow identification field beforehand in the service flow arrangement message, generating the service flow arrangement message by the first node when the first node in WiMAX system is triggered, recording at least one identification of the service flow which is to be arranged into the flow identification field of the message, and then sending the service flow arrangement message to the second node which is located in the signaling downstream of the message to trigger the second node to execute the service flow arrangement.

Description

Service flow configuration method in microwave access global interworking system and system

Technical field

The present invention relates to the technology of Worldwide Interoperability for Microwave Access (WiMax), and more particularly to a WiMAX system and a service flow configuration method in the system. Background of the invention

WiMAX technology is a broadband wireless access standard based on the 802.16 protocol that provides high-speed connectivity to the Internet. Unlike 3G systems, WiMax systems use IP packet switching technology entirely, without the need for voice-oriented circuit switching. Based on the above characteristics, the voice communication supported by the WiMax system adopts the VoIP method.

Because WiMax systems can carry multiple types of services, such as voice, video, HTTP, and email, and the quality of service (QoS) requirements vary from service to service, WiMAX systems use different service flows for the same mobile. The terminal (MS/MSS) provides different types of services. The service flow is divided according to packet information, such as a source address, a destination address, a port number, or a protocol number, and each service flow has a specified QoS parameter for guaranteeing the service quality of the service provided by the service flow. Each service flow is provided with an identifier indicating the service flow and its QoS parameters and the like.

In practice, you can do the following for the service flow:

1) Create (Create). When a new application appears, the system creates a service flow.

2) Approval (Admit). For a service flow, the system needs to determine if it can satisfy the QoS of the service flow.

3) Activate (Activate). Once a service flow is approved, it is activated for use.

4) Modify. When the QoS of a service flow cannot meet the needs of the application, The QoS parameters are modified.

5) Delete (Delete). At the end of an application, the service stream that supports the app is deleted. In a WiMAX system, network nodes that support and process service flows mainly include: Service Flow Management (SFM), Service Flow Authorization Module

(SFA, Service Flow Authorization) and Policy Function Module (PF, Police

Function)

The SFM is set on the base station side, and is configured to perform related operations on the service flow according to local radio resources. The SFA is used to perform an approval operation on the service flow according to the local policy. The module is further divided into a service SFA (Serving SFA) and an anchor SFA (Anchor SFA). The PF is located at the CSN and is used to store user information and control the QoS parameters of the service flow.

In the draft standard NWG-Stage-2 of WiMax, several processes are defined to provide services for users by using service flows. The two main processes are: PD (Policy Decision) process and resource reservation (RR, Resource). Reservation) process.

The PD process is implemented by using a Policy Decision (PD) message, which is used to set a service policy of the service flow, where the PD. The message includes a PD-Request and a Policy-Response (PD-Response).

The RR process is implemented by using a Resource Reservation (RR) message, and is used to reserve resources required for a service flow of a certain MS/MSS, where the RR message includes a resource reservation request (RR-Request) and a resource. Reserve response (RR-Response).

Figure 1 shows the specific process of the prior art policy decision (PD), including the following steps:

Step 101: The SFM is triggered to issue a PD-Request to the serving SFA. The PD-Request explicitly contains QoS parameters, or is set to a service type name.

In this step, the reason why the SFM is triggered is diverse. For example, MS/MSS sends a request to SFM, or SFM receives a dynamic service flow modification (Dynamic Service Flow) Modification) instructions, etc.

Steps 102 to 103: After receiving the PD-Request, the serving SFA is triggered to issue a PD-Request to the anchor SFA, and then the PD-Request is sent by the anchor SFA to the network service provider (NSP, Network Service) to which the MS/MSS belongs. Provider) PF.

Step 104: After receiving the PD-Request, the PF performs service flow configuration, and responds to the anchor SFA by using a policy decision response (PD-Response).

Steps 105 to 106: Anchor Point After receiving the PD-Response, the SF A is triggered to issue a PD-Response to the serving SFA, and then the PD-Response is sent to the SFM by the serving SFA, and the process of the policy decision ends.

Table 1 shows the field format of the PD message transmitted between the PF and the SFA in the prior art. Message direction parameter

PD-Request SFA to PF Mobile Terminal Network Access Identity (MS NAI) Transaction ID (Transaction ID)

Decision Action

Resource Description

PD-Response PF to SFA MS NAI

Transaction ID

Decision Result

Resource Description

Table I

Table 2 shows the field format of the PD message transmitted between the SFA and the SFM in the prior art. Message direction parameter

PD-Request SFM to SFA Mobile Terminal Identity (MS ID)

Transaction ID

Decision Action

Resource Description

PD-Response SFA to SFM MS ID

Both the PD-Request and the PD-Response sent in the above process contain a Decision Action field for passing the type of operation of the service flow configuration between network nodes.

In WiMAX systems, network nodes such as SFM, Serving SFA, Anchor SFA, and PF are connected step by step. For example, if the SFM sends a PD-Request to the serving SFA, the service SFA is referred to as the downstream node of the PD-Request signaling of the SFM. Similarly, the service SFA sends a PD-Response to the SFM, which is called the PD-Response signaling downstream node of the service SFA.

Figure 2 shows the specific process of resource reservation (RR) in the prior art, including the following steps:

Step 201: The PF sends an R-Request to the Anchor SFA, requesting to reserve resources for a service flow. The RR-Request requires execution of operations such as creation, activation, or deletion of a service flow.

Steps 202 to 203: After receiving the RR-Request, the Anchor SFA performs an application configuration (Apply Profile) and sends an RR-Request to the Serving according to the local policy.

SFA, then the Serving SFA sends an RR-Request to the SFM.

Step 204: After receiving the RR-Request, the SFM performs application permission control (Apply

Admission Control), detecting its own resource usage (such as bandwidth), and giving a configuration success/failure indication according to the resource usage, replying to the RR-Response

Serving SFA.

Steps 205 to 206: After receiving the RR-Response, the Serving SFA sends the RR-Response to the Anchor SFA, and then sends the RR-Response to the PF by the Anchor SFA. The resource reservation process ends.

Table 3 shows the field format of the RR message transmitted between the PF and the SFA in the prior art.

Table 3

Table 4 shows the field format of the RR message transmitted between the SFA and the SFM in the prior art, and the message direction parameter.

RR-Request SFA to SFM Mobile Terminal Identity (MS ID)

Transaction ID

Service Flow ID

Reservation Action

Direction

Resource Description Media Flow Description

Media Flow Type

Reduced Resources

QoS Priority

Accounting Extension

RR-Response SFM to SFA MS ID

Transaction ID

Service Flow ID

Reservation Result

Resource Description

Table 4

As seen from the above description, the service flow configuration is performed for a specific service flow. A series of network nodes in the WiMAX system, such as the service SFA, the anchor SFA, the PF, etc., only after knowing which service flow needs to be configured, correspondingly The operation can be executed. However, the policy specified by the existing protocol determines that the message cannot deliver the indication information of the service flow to be configured, so that the configuration of the service flow cannot be performed correctly.

In addition, in the existing defined field format, there is no specific parameter in the PD message and the RR message to describe the number of service flows processed in the above process and the feature information of each service flow. Therefore, when the sender of the above message sends a PD message or an RR message to the receiver, the receiver cannot directly know how many service flows need to be configured at the same time. If the receiver wants to know the information, it needs to calculate the size of the PD or RR message and the byte size occupied by the parameter set of a single stream in each message. Then, after a series of operations, the number of service flows can be obtained. . For WiMAX systems, a large amount of user data and signaling messages are processed at the same time. If a series of operations are performed on each PD and/or RR message, the number of service flows in the message can be indirectly known. Will consume unnecessary system resources. Furthermore, the PD and/or RR messages may contain variable length data items, or there may be cases where the parameter sets of the service flows are not equal in size, so that the system cannot accurately know the services included in the PD and/or RR messages. The number of streams. Summary of the invention

The main object of the present invention is to provide a method for configuring a service flow in a WiMAX system, so that the network node can correctly configure the corresponding service flow.

It is still another object of the present invention to provide a WiMAX system that enables network nodes in the system to properly configure corresponding service flows.

It is still another object of the present invention to provide a WiMAX system and service flow configuration method that enables the system to simultaneously configure multiple service flows, greatly reducing network load.

To achieve the above objective, the technical solution of the present invention is specifically implemented as follows: A method for configuring a service flow in a global interoperability WiMAX system, the method comprising: setting a flow identification field in a first service flow configuration message in advance, After the first node in the WiMAX system is triggered, the first node generates a first service flow configuration message, records the identifier of the at least one service flow to be configured in a flow identifier field of the message, and then the first service The flow configuration message is sent to the second node downstream of the signaling of the message, and the second node is triggered to perform the service flow configuration.

A microwave access global interworking WiMAX system, the WiMAX system includes a service flow management module SFM, a service flow authorization module SFA, and a policy function module PF;

The SFM is used to determine the operation type of the service flow configuration; if it is a creation operation, the SFM sets the flow identification field of the policy determination request generated by itself to be empty; if it is a modification or deletion operation, the SFM will modify or delete the service flow. The service flow identifier is recorded in the flow identifier field of the policy decision request generated by itself, and sent to the SFA;

The SFA is configured to map the service flow identifier in the policy decision request of the SFM to the flow identifier according to the preset correspondence, and record the flow identifier in the policy decision request generated by the SFA, and send the identifier to the PF.

A method for configuring a service flow in a global interoperability WiMAX system for microwave access, the method comprising: setting a flow number field in a service flow configuration message in advance, when a WiMAX system After the first node in the first node is triggered, the first node detects the number of service flows to be configured, records them in the number of flows field, and records the parameter sets of each service flow one by one in the service flow configuration message, and then The service flow configuration message is sent to a second node located downstream of the signaling of the message, and the second node is triggered to perform a service flow configuration.

The SFM is configured to set a flow number field of the service flow configuration message generated by itself according to the number of the detected service flows, and save the parameter set of each service flow in the service flow configuration message in sequence, and send the message to the SFA. ;

The SFA is configured to generate a service flow configuration message, and send the number of service flows and the parameter set of each service flow to the signaling downstream node of the message by using the message;

The PF is configured to configure each service flow, and records the number of service flows and the parameter set of each service flow in the flow number field of the service flow configuration message generated by itself, and sends the data to the SFA.

It can be seen from the foregoing technical solution that the method for configuring a service flow in the WiMAX system of the present invention sets a flow identification field in a policy decision message, and records an identifier of at least one service flow to be configured, so that the network node can clearly know the QoS parameters. The configured service flow, so that the corresponding operation is completed correctly.

Further, the present invention sets a Flow Number field in the policy decision message and/or the resource reservation message for recording the number of service flows to be configured. The sender of the above message will detect the service flow of this process before the message is sent, and fill in the number of service flows into the Flow Number field. In this way, the receiver only needs to read the field to accurately and quickly know the number of service flows configured in the current configuration, so the method improves the processing efficiency of the network node, reduces the network load, and largely Reduce the chance of errors in WiMAX systems. · BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a specific process of policy determination in the prior art;

2 is a specific process of resource reservation in the prior art;

3 is a specific process of policy determination in an embodiment of the present invention;

4 is a specific process of policy determination in still another embodiment of the present invention;

FIG. 5 is a specific process of resource reservation in still another embodiment of the present invention. Mode for carrying out the invention

The service flow configuration method of the present invention carries the identifier of the service flow to be configured in the service flow configuration message, and delivers the service flow configuration message step by step in the WiMAX system, so that any network node of the WiMAX system can correctly execute the service flow. Configuration.

The service flow configuration message refers to a policy decision (PD) message, a resource reservation (RR) message, and the like. The service flow configuration refers to performing operations such as creating, modifying, or deleting a specified service flow in a policy decision process or a resource reservation process.

For example, a flow identifier field is set in an existing PD message, and is used to record an identifier of a service flow to be configured. When any one of the network nodes in the WiMAX system is triggered to execute the policy decision, the network node configures the specified service flow, and records the identifier of the service flow in the flow identification field of the PD message generated by itself, and sends the message to the letter. Let the downstream node trigger the downstream node to perform the configuration of the service flow.

Further, the service flow configuration method of the present invention carries the number of service flows to be configured in the service flow configuration message, and sets a parameter set for each service flow, and then delivers the service flow configuration message step by step in the WiMAX system.

For example, a Flow Number field is set in an existing PD message or an RR message, which is used to record the number of service flows to be configured, and a parameter set of each service flow.

Based on the above settings, the process of configuring the service flow in one embodiment of the present invention is as follows: As shown in FIG. 3, the following steps are specifically included:

Step 301: The SFM is triggered to generate a policy decision request (PD-Request), and the service flow identifier (SFID, Service Flow Identification) of the service flow to be configured is recorded in the flow identifier field of the PD-Request, and then the PD-Request is Sent to the service SFA.

In this step, the SFM is triggered to determine the type of operation. If it is a create operation, the stream identification field of the PD-Request is set to null, and then the PD-Request is issued. If the modification or deletion is performed, the service flow identifier of the service flow to be modified or deleted is recorded in the flow identification field of the PD-Request.

The SFM is triggered to execute the policy decision, either for resource optimization purposes or for MS/MSS to issue dynamic service flow requests.

Step 302: After receiving the PD-Request, the service SFA is triggered to send a PD-Request to the anchor SFA, and then the PD-Request is sent by the anchor SFA to the PF.

In an example, after receiving the PD-Request of the SFM, the service SFA maps the SFID in the PD-Request to a flow identifier according to a preset correspondence, and records the flow identifier in its own generated Issued in the PD-Request. At this time, if the creation operation is performed, the flow identification field in the PD-Request sent by the service SFA is also empty because the flow identification field of the PD-Request sent by the SFM is empty. After the anchor SFA is triggered, the corresponding field of the service SFA is set according to the PD-Request of the service SFA, and a PD-Request is generated and sent to the PF.

In another example, after receiving the PD-Request of the SFM, the serving SFA sets its own corresponding field according to the PD-Request of the SFM, and generates a PD-Request to send to the anchor SFA. After the anchor SFA is triggered, the SFID in the PD-Request is mapped to the flow ID according to the preset correspondence, and the flow identifier is recorded in the PD-Request generated by itself and sent to the PF.

Relative to the PD-Request, the service SFA is the signaling upstream node of the anchor SFA. The PF is the signaling downstream node of the anchor SFA.

Step 303: After receiving the PD-Request, the PF configures the service flow indicated by the Flow ID, and returns a policy decision response (PD-Response) to the anchor SFA.

In this step, after the PF is triggered by the PD-Request, the type of operation of the current configuration is determined. If it is a create operation, a flow identifier is generated for the service flow to be created, and the record is sent in the flow identifier field of the PD-Response. If it is a modification or deletion operation, the flow identification record of the service flow to be modified or deleted is sent in the flow identification field of the PD-Response.

Step 304: After receiving the PD-Response of the PF, the SFA sends a PD-Response to the serving SFA, and then the PD-Response is sent to the SFM by the serving SFA, and the policy decision process ends.

In one example, the anchor SFA sets its own corresponding field according to the PD-Response of the PF and generates a PD-Response to send to the serving SFA. For PD-Response, PF is the signaling upstream node of the anchor SFA, and the service SFA is the signaling downstream node of the anchor SFA.

After receiving the PD-Response of the anchor SFA, the service SFA determines the type of operation of the current configuration. If the operation is created, the corresponding service flow identifier is generated for the flow identifier recorded in the PD-Response, and the service flow identifier is recorded in the PD-Response generated by itself. If it is a modification or deletion operation, the flow identifier is mapped to the service flow identifier according to the preset corresponding relationship, and then the service flow identifier is sent through the PD-Response generated by itself.

When the corresponding relationship between the service flow identifier and the flow identifier is set in advance, the service SFA may set the service flow identifier and the flow identifier to be the same, or add the own identifier to the service flow identifier to generate a corresponding flow identifier, and the specific setting is determined according to actual needs. .

In another example, the anchor point SFA determines the type of operation of the current configuration. If it is a creation If the operation is performed, the corresponding service flow identifier is generated for the flow identifier recorded in the PD-Response of the PF, and the service flow identifier is recorded in the PD-Response generated by itself. The service SFA sets its own corresponding field according to the PD-Response of the anchor SFA, and generates a PD-Response to send to the SFM. At this point, all network nodes in the WiMAX system can perform specific operations according to the identifier of the service flow to be configured, such as saving the service policy of the service flow. Further, the identifier of the service flow to be configured may be recorded in the flow identifier field of the service flow configuration message, so as to configure multiple service flows, save the signaling process, and improve network utilization.

In order to configure multiple service flows, the present invention adds a Flow Number field to the existing policy decision message and resource reservation message, which is used to record the number of service flows to be configured, and each service flow. A collection of parameters.

For the Policy Decision Request (PD-Request) and the Policy Decision Response (PD-Response), Tables 5 and 6 show the field formats of PD-Request and PD-Response in one embodiment of the present invention. Message Directions (Parameters)

(Message)

PD-Request SFA to PF Mobile Terminal Network Access Identifier (MS NAI)

Transaction ID (Transaction ID)

Flow Number

{

Flow ID (Flow ID)

Decision Action

Resource Description

}

PD-Response PF to SFA Mobile Terminal Network Access Identifier (MS NAI) Transaction ID

Flow Number

{

Flow ID (Flow ID)

Decision Result

Resource Description

}

Table 5

The parameter set of each service flow in the PD-Request includes: a flow ID, a decision action, and a resource description.

The parameter set of each service flow in the PD-Response includes: Flow ID, Decision Result, and Resource Description.

For the sake of distinction, the set of parameters for each service flow in the PD-Request is called The first policy determines parameters, and the set of parameters of each service flow in the PD-Response is referred to as a second policy decision parameter. Assume that the number of service flows to be configured in a policy decision process is 4, and the first policy decision parameters of the service flows fl, £2, and f4 are sequentially recorded in the PD-Request.

Based on the above configuration, the service flow configuration process in another embodiment of the present invention is as shown in FIG. 4, and specifically includes the following steps:

Step 401: After the SFM is triggered, detecting the number of service flows to be configured, recording them in the Flow Number field of the PD-Request generated by the SFM, and setting a first policy decision parameter for each service flow in the PD-Request. Then, the PD-Request carrying the above parameters is sent to the Serving SFA.

Step 402: After receiving the PD-Request of the SFM, the Serving SFA sends a PD-Request to the Anchor SFA, and then sends a PD-Request to the PF by the Anchor SFA.

In this step, when the PD-Request is transmitted between different network nodes, each network node processes the packet to conform to the message encapsulation format of the specific network node, but the PD-Request always carries multiple to be configured. A collection of parameters for a service flow.

In addition, when the network node such as Serving SFA and Anchor SFA is the receiver of the PD-Request, it parses the PD-Request sent by the upstream node of the signaling, and saves the number of service flows carried in the PD-Request and each The first policy of the service flow determines the parameters.

Step 403: After receiving the PD-Request, the PF separately configures multiple service flows, and returns PD-Response to the Anchor SFA.

The Flow Number field is also set in the PD-Response, and the second policy decision parameter of each service flow is recorded.

Step 404: After the Anchor SFA receives the PD-Response of the PF, it generates The PD-Response is sent to the Serving SFA, and the Serving SFA sends the PD-Response to the SFM. The policy decision process ends.

In this step, after receiving the PD-Response, the network nodes such as Anchor SFA and Serving SFA parse the PD-Response and save the number of service flows carried in it and the second policy decision parameter of each service flow.

At this point, all network nodes in the WiMAX system complete the configuration of the corresponding service flow, that is, the service policy in which the service flow is saved. Since the above process can simultaneously set a service policy for multiple service flows, the signaling process is largely saved and the network utilization is improved. The receiver of each PD-Request can quickly and accurately know how many service flows are processed simultaneously by reading the Flow Number field.

It should be noted that, in the above process, the PF may not be able to reply to the PD-Response because the PD-Request is not received, so steps 403-404 do not necessarily occur during the policy decision process.

For the resource reservation request (R-Request) and the resource reservation response (RR-Response), Tables 7 and 8 show the field formats of the RR-Request and the RR-Response in one embodiment of the present invention.

Message Direction Parameters

RR-Request PF to SFA MS NAI

Transaction ID

Flow Number

{

Flow ID (Flow ID)

Reservation Action

Direction

Resource Description Message Direction Parameters

Media Flow Description Media Flow Type Resource Reduced Resources QoS Priority Accounting Extension

}

RR-Response SFA to PF MS NAI

Transaction ID

Flow Number

{

Flow ID (Flow ID)

Reservation Result Resource Description

}

Table 7

The parameter set of the service flow in the RR-Request includes: a flow ID, a reservation action, a direction, a resource description, a media flow description, and a media flow description. Media Flow Type, Resource Reduced Resources, QoS Priority, and Accounting Extension.

The parameter set of the service flow in the RR-Response includes: a flow ID, a Reservation Result, and a Resource Description.

For the sake of distinction, the parameter set of the service flow in the RR-Request is referred to as the first resource reservation parameter, and the parameter set of the service flow in the RR-Response is referred to as the second resource reservation parameter. If you need to perform resource configuration for multiple service flows at the same time, the PF can initiate the resource reservation process shown in Figure 5, specifically:

Step 501: After detecting the number of service flows to be configured, the PF records the flow number of the RR-Request generated by the PF, and sets a first resource reservation parameter for each service flow in the RR-Request. , then send the RR-Request carrying the above information to the Anchor SFA.

Step 502: After receiving the RR-Request sent by the PF, the Anchor SFA sends it to the Serving SFA, and then sends the message to the SFM by the Serving SFA. In this step, after receiving the RR-Request, the network node parses the request, and saves the number of service flows carried in the request and the first resource reservation parameter of each service flow.

Step 503: After receiving the RR-Request, the SFM performs an application admission control (Apply Admission Control) to detect its own resource usage (such as bandwidth), and gives a configuration success/failure indication according to the resource usage, and passes the RR- Response Reply to Serving SFA.

A Flow Number field is also set in the RR-Response, and a second resource reservation parameter of each service flow is recorded.

Step 504: After receiving the RR-Response, the Serving SFA sends it to the Anchor SFA, and then the Anchor SFA sends the message to the PF, and the resource reservation process ends.

In this step, after receiving the RR-Response, the network node parses the response, and saves the number of service flows carried in the response and the second resource reservation parameter of each service flow.

In the above process, the SFM may not be able to make an RR-Response because the RR-Request is not received, so steps 503-504 do not necessarily occur during the resource reservation process.

In addition, the processes described in FIG. 4 and FIG. 5 can be used in combination. After setting the service policies of multiple service flows, the PF can directly initiate resource reservation for the service flows, which will not be described in detail here.

It can be seen from the foregoing embodiments that the WiMAX system and the service flow configuration method of the present invention carry the identifier of the service flow in the PD and/or the RR message, and increase the number of flows of the number of the service flows to be configured. The receiver can accurately and quickly know the service flow information of the current configuration, so the method improves the processing efficiency of the network node, reduces the network burden, and greatly reduces the probability of error occurrence of the WiMAX system.

Claims

Claim

A method for configuring a service flow in a global interoperability WiMAX system, the method comprising: setting a flow identification field in a first service flow configuration message in advance, when a first node in the WiMAX system is triggered After the first node generates a first service flow configuration message, the identifier of the at least one service flow to be configured is recorded in the flow identification field of the message, and the first service flow configuration message is sent to the message located in the message. The downstream second node is triggered to execute the service flow configuration by the second node.

The method according to claim 1, wherein the first node is a service flow management module SFM, the first service flow configuration message is a policy decision request, and the first node is to be configured with a service flow. The identification of the identifier in the flow identification field includes: SFM determines the operation type of the service flow configuration; if it is a creation operation, the SFM sets the flow identification field of the policy determination request generated by itself to be empty; if it is a modification or deletion operation, the SFM is to be modified. Or the service flow identifier of the deleted service flow is recorded in the flow identification field of the policy decision request.

The method according to claim 1, wherein the first node is an SFM, the first service flow configuration message is a policy decision request, and the second node is a service flow authorization module SFA;

The second node performing the service flow configuration includes: after receiving the policy decision request of the SFM, the SFA maps the service flow identifier in the policy decision request of the SFM to the flow identifier according to the preset correspondence, and the identifier is The record is issued in the policy decision request generated by the SFA.

The method according to claim 1, wherein the first node is an SFA, the first service flow configuration message is a policy decision request, and the second node is a policy function module PF; The second node performing the service flow configuration includes: after receiving the policy decision request of the SFA, the PF determines the operation type of the service flow configuration; if the operation is a creation operation, the PF generates a flow identifier for the service flow to be created, and records the flow identifier in the PF. The policy determines that the response is sent in the flow identification field. If it is a modification or deletion operation, the PF sends the flow identification record of the service flow to be modified or deleted in the flow identification field of the policy decision response of the PF.

The method according to claim 1, wherein the first node is a PF, the first service flow configuration message is a policy decision response, the second node is an SFA, and the second node performs The service flow configuration includes: after receiving the policy of the PF, the SFA determines the operation type of the service flow configuration; if the operation is a creation operation, the SFA generates a corresponding service flow identifier for the flow identifier in the PF policy decision response, and The service flow identifier record is sent in the policy decision response generated by itself; if it is a modification or deletion operation, the SFA maps the flow identifier to a service flow identifier according to a preset correspondence, and then records the service flow identifier in the The policy generated by the SFA determines the response to be issued.

The method according to claim 3 or 5, wherein the corresponding relationship is: the service flow identifier and the flow identifier are set to be the same; or, the corresponding SFA identifier is added to the service flow identifier to generate a flow identifier, The corresponding SFA identifier is deleted from the flow identifier to generate a monthly service flow identifier.

The method according to claim 1, wherein the method further comprises: setting a flow number field in the second service flow configuration message; and detecting, after the first node is triggered, the first node The current number of service flows to be configured is recorded in the flow number field, and the parameter set of each service flow is recorded one by one in the second service flow configuration message.

The method according to claim 7, wherein the second service flow configuration message is a policy decision request, a policy decision response, a resource reservation request, or a resource reservation response.

A microwave access global interworking WiMAX system, wherein the WiMAX system includes a service flow management module SFM, a service flow authorization module SFA, and a policy function module PF;

The SFM is used to determine the operation type of the service flow configuration. If the operation is a creation operation, the SFM sets the flow identification field of the policy decision request generated by the SFM to be empty; if it is a modification or deletion operation, the SFM will modify or delete the service flow. The service flow identifier is recorded in the flow identifier field of the policy decision request generated by itself, and sent to the SFA;

10. The system of claim 9 wherein:

The PF is further configured to determine an operation type of the service flow configuration; if the operation is a creation operation, the PF generates a flow identifier for the service flow to be created, and records the information in the flow identification field of the policy decision response of the PF to be sent to the SFA; Or deleting the operation, the PF records the flow identifier of the service flow to be modified or deleted in the flow identification field of the policy decision response of the PF, and sends it to the SFA;

The SFA is further configured to determine an operation type of the service flow configuration; if it is a creation operation, the SFA generates a corresponding service flow identifier for the flow identifier in the policy determination response of the PF, and records the service flow identifier in the self-generated The policy decision response is sent to the SFM; if it is a modification or deletion operation, the SFA maps the flow identifier to a service flow identifier according to a preset correspondence, and records the service flow identifier in the policy decision response generated by the SFA. Sent to SFM.

11. The system of claim 9 wherein:

The SFM is further configured to set a flow number field of the requested policy according to the number of the detected service flows, and determine the first policy of each service flow. The number order is saved in the policy decision request and sent to the SFA;

The SFA is further configured to send the number of service flows and the first policy decision parameter of each service flow to the PF through a policy decision request.

12. The system of claim 11 wherein:

The PF is further configured to determine a service policy according to the received policy, set a service policy for each service flow, and record the number of service flows in the flow number field of the policy determination response generated by itself, and the second of each service flow. The policy determines a parameter, and then sends the policy decision response to the SFA;

The SFA is further configured to send the number of the service flows and the second policy decision parameter of each service flow to the SFM through a policy decision response.

13. The system of claim 9 wherein:

The PF is further configured to: set a flow number field of the resource reservation request according to the number of the detected service flows, and save the first resource reservation parameter of each service flow in the resource reservation request, and send the SFA;

The SFA is further configured to send the number of the service flows and the first resource reservation parameters of each service flow to the SFM through a resource reservation request.

14. The system of claim 13 wherein:

The SFM is further configured to reserve resources for each service flow according to its own resource usage, and record the number of service flows in the flow number field of the resource reservation response generated by itself, and the second resource of each service flow. Reserving parameters, and then sending the resource reservation response to the SFA;

The SFA is further configured to send the number of the service flows and the second resource reservation parameters of each service flow to the PF through a resource reservation response.

A method for configuring a service flow in a global interoperability WiMAX system for microwave access, characterized in that the method comprises: setting a flow number field in a service flow configuration message in advance, After the first node in the WiMAX system is triggered, the first node detects the number of service flows to be configured, records them in the flow number field, and records the parameter sets of each service flow one by one in the service flow configuration message. And sending the service flow configuration message to the second node downstream of the signaling of the message, triggering the second node to perform service flow configuration.

The method according to claim 15, wherein the service flow configuration message is a policy decision request, and the parameter set of each service flow includes at least one of the following information: a flow identifier, a decision action, and a resource description. .

The method according to claim 15, wherein the service flow configuration message is a policy decision response, and the parameter set of each service flow includes at least one of the following information: a flow identifier, a determination result, and a resource description. .

The method according to claim 15, wherein the service flow configuration message is a resource reservation request, and the parameter set of each service flow includes at least one of the following information: a flow identifier, a reservation action, Direction, resource description, media stream description, media stream type, resource reduction flag, quality of service priority, and billing extension.

The method according to claim 15, wherein the service flow configuration message is a resource reservation response, and the parameter set of each service flow includes at least one of the following information: a flow identifier, a reservation result, and Resource description.

20, a microwave access global interworking WiMAX system, characterized in that the WiMAX system comprises a service flow management module SFM, a service flow authorization module SFA and a policy function module PF;

The SFA is configured to generate a service flow configuration message, by which the number of service flows and a parameter set of each service flow are sent to a signaling downstream node of the message; The PF is configured to configure each service flow, and records the number of service flows and the parameter set of each service flow in the flow number field of the service flow configuration message generated by itself, and sends the parameter set to the SFA.