CN101043504B - Method for creating, deleting and changing network side service flow - Google Patents
Method for creating, deleting and changing network side service flow Download PDFInfo
- Publication number
- CN101043504B CN101043504B CN2006100585932A CN200610058593A CN101043504B CN 101043504 B CN101043504 B CN 101043504B CN 2006100585932 A CN2006100585932 A CN 2006100585932A CN 200610058593 A CN200610058593 A CN 200610058593A CN 101043504 B CN101043504 B CN 101043504B
- Authority
- CN
- China
- Prior art keywords
- request
- data channel
- sfm
- service flow
- request response
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses a creating method for Network Side (NS) service flow comprising: after deciding to create the NS service flow by an Anchor Service Flow Authorization (SFA) entity, the NS executing: the Anchor SFA sending resource request and relevant parameters to a Service Flow Management (SFM) entity, after deciding to admit the SFM sending service flow creating request to a Mobile Station (MS), the MS keeping the relevant parameters and returning a dynamic service flow creating response message to the SFM; the SFM sending the resource request response to the Anchor SFA. The method further includes: the Anchor SFA sending data channel creating request and relevant parameters to the SFM, each node in the network creating the data channel according to the parameters; the SFM returning the data channel creating request response to the Anchor SFA, the Anchor SFA sending a confirmation message to the SFM; the SFM sending the service flow creating confirmation message. At the same time, the invention also discloses a method for deleting and changing the NS service flow.
Description
● technical field:
The present invention relates to service flow technical field in the wireless MAN, relate in particular to a kind of method of establishment, deletion and change of network side service flow.
● background technology:
Inserting of microwave global network (WiMAX) is a kind of wireless metropolitan area network technology based on the IEEE802.16 standard.WiMAX cellular logic framework mainly is made up of three parts and is client (MSS/SS), accessing business network (ASN) and is connected service network (CSN) and comprises strategic server (PF), AAA server (AAA Server), application server (AF) or the like logic entity as shown in Figure 1.The QoS reference model of the WiMAX draft standard definition of formulating at present is illustrated in fig. 2 shown below.
Wherein SFM is arranged in the management service flow entity that ASN is responsible for access control, establishment, activation, modification and the deletion of service flow, is made up of access control AC and the local resource information bank that is associated with AC.SFA is the service flow authorized entity that is arranged in ASN, mainly is the service flow of application is carried out the authentication and authorization action.The only corresponding AnchorSFA of each MS/SS, Anchor SFA be responsible for and PF between mutual.The SFA directly mutual with SFM is referred to as Serving SFA.Serving SFA and Anchor SFA may be same entities, when they are not same entity, may also have a plurality of SFA between them, are used for the relevant primitive of RelayQoS.These SFA are called Relay SFA.Serving SFA and Anchor SFA at any time must know mutually.Anchor SFA carries out other tactical management of ASN level according to local policy database LPD.AF is the application service entity that is arranged in ownership NSP.MS/SS is directly mutual by application layer protocol and AF.AF can initiate the WiMAX service flow request to PF, sends resource reservation request (RR-Request) to trigger PF to ASN.PF is the policy service entity that is arranged in ownership NSP.User information database in addition associated therewith wherein comprises the service strategy and the corresponding prefabricated qos parameter that allow access.
The network side Business Stream is created and is comprised prefabricated stream establishment and the establishment of other network side application service stream.Common ground all is to be initiated by network side, and user oriented is created service flow.The network side service flow visioning procedure as shown in Figure 3 in the existing draft standard.
The network side service flow constructive process is finished by RESV (RR), and corresponding idle message is that dynamic service flow is created message (DSA-Request/Reponse/Acknowledge).After but this process is finished, only set up and eated dishes without rice or wine to connect, the data channel (Data Path) in the ASN network is not set up, and business also can't normal transmission.
By as can be seen above-mentioned, the network side service flow constructive process is imperfect in the existing draft standard, can't realize transfer of data, and change and the deletion to network side service flow do not provide specific implementation process yet in the existing draft standard.
● summary of the invention:
In view of this, main purpose of the present invention is to provide a kind of method of establishment, deletion and change of network side service flow, and this method comprises:
A kind of creation method of network side service flow, after the establishment of network side service flow was carried out in anchor service flow authorized entity Anchor SFA decision, network side was carried out:
The resource request process: Anchor SFA sends resource request and relevant parameter to management service flow entity SFM, initiate the service flow creation request to mobile station MS after the SFM decision access, MS returns dynamic service flow request to create response message to SFM after keeping relevant parameter;
Resource request response process: SFM sends the resource request response to Anchor SFA;
Wherein, this method further comprises:
If data channel is not also set up, or data channel is based on service flow, then need data channel to set up request process: Anchor SFA sends data channel to SFM and sets up request and relevant parameter, and each node will be set up data channel according to described parameter in the network;
Data channel is set up request response process: SFM and is set up request response to Anchor SFA return data passage, and Anchor SFA sends acknowledge message to SFM;
Eat dishes without rice or wine affirmation process: SFM to MS transmission service flow creation confirmation.
Wherein, described resource request process, resource request response process, data channel are set up request process, data channel sets up the request response process and the affirmation process of eating dishes without rice or wine is independently carried out successively.
Wherein, described resource request process, the affirmation process of eating dishes without rice or wine, resource request response process, data channel are set up request process and the independently execution successively of data channel foundation request response process.
Wherein, carry out described resource request process and described data channel at first simultaneously and set up request process, carry out described resource request response process and described data channel then simultaneously and set up the request response process, carry out at last and eat dishes without rice or wine to confirm.
Wherein, described resource request process and data channel are set up request process and are carried out simultaneously and be specially:
SFM receive from Anchor SFA comprise that resource request, data channel are set up the stream request of request and relevant parameter after, preserve the wherein information of relevant data passage foundation, initiate the service flow creation request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow request to create response message to SFM after keeping relevant parameter.
Wherein, described resource request response process and data channel foundation request response process is carried out simultaneously and is specially:
SFM sets up request response, resource request response and relevant parameter with data channel and returns Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
Wherein, carry out described resource request process and described data channel at first simultaneously and set up request process, carry out then and eat dishes without rice or wine to confirm, carry out described resource request response process and described data channel at last simultaneously and set up the request response process.
Wherein, described resource request process and data channel are set up request process and are carried out simultaneously and be specially:
SFM receive from Anchor SFA comprise that resource request, data channel are set up the stream request of request and relevant parameter after, preserve the wherein information of relevant data passage foundation, initiate service flow creation request DSA-Request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow request to create response message to SFM after keeping relevant parameter.
Wherein, described resource request response process and data channel foundation request response process is carried out simultaneously and is specially:
SFM sets up request response, resource request response and relevant parameter with data channel and returns Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
Wherein, this method comprises:
The resource request process: Anchor SFA sends resource request and relevant parameter to management service flow entity SFM, SFM initiates the service flow removal request according to described parameter and local access strategy to mobile station MS after receiving resource request, and MS returns dynamic service flow removal request response message to SFM after keeping relevant parameter;
Resource request response process: SFM sends the resource request response to Anchor SFA;
Eat dishes without rice or wine affirmation process: SFM to MS transmission service flow deletion confirmation.
Wherein, this method further comprises:
If data channel is based on service flow creation, or there is not other service flow to use, then need to carry out data channel removal request process: Anchor SFA sends data channel removal request and relevant parameter to SFM, and each node will be according to described parameter deleted data passage in the network;
Data channel removal request response process: SFM is to Anchor SFA return data passage deletion response message, and Anchor SFA sends acknowledge message to SFM.
Wherein, described resource request process, resource request response process, data channel removal request process, data channel removal request response process and the affirmation process of eating dishes without rice or wine are independently carried out successively.
Wherein, described resource request process, the affirmation process of eating dishes without rice or wine, resource request response process, data channel removal request process and data channel removal request response process are independently carried out successively.
Wherein, carry out described resource request process and described data channel removal request process at first simultaneously, carry out described resource request response process and described data channel removal request response process then simultaneously, carry out at last and eat dishes without rice or wine to confirm.
Wherein, described resource request process and data channel removal request process are carried out simultaneously and are specially:
After SFM receives the stream request that comprises resource request, data channel removal request and relevant parameter from Anchor SFA, preserve the wherein information of relevant data passage deletion, initiate the service flow removal request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow deletion response message to SFM after keeping relevant parameter.
Wherein, described resource request response process and data channel removal request response process are carried out simultaneously and are specially:
SFM returns data channel removal request response message, resource request response and relevant parameter to Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
Wherein, carry out described resource request process and described data channel removal request process at first simultaneously, carry out then and eat dishes without rice or wine to confirm, carry out described resource request response process and described data channel removal request response process at last simultaneously.
Wherein, described resource request process and data channel removal request process are carried out simultaneously and are specially:
After SFM receives the stream request that comprises resource request, data channel removal request and relevant parameter from Anchor SFA, preserve the wherein information of relevant data passage deletion, initiate the service flow removal request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow deletion response message to SFM after keeping relevant parameter.
Wherein, described resource request response process and data channel removal request response process are carried out simultaneously and are specially:
SFM returns data channel removal request response message, resource request response and relevant parameter to Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
Wherein, this method comprises:
Anchor SFA sends resource request and relevant parameter to management service flow entity SFM, and SFM initiates service flow change request according to described parameter and local access strategy to mobile station MS after receiving resource request;
SFM receives from after the service flow of the MS change request response, sends the resource request response to Anchor SFA;
SFM sends service flow change confirmation to MS.
Wherein, this method further comprises:
Anchor SFA sends resource request and relevant parameter to management service flow entity SFM, and SFM initiates service flow change request according to described parameter and local access strategy to mobile station MS after receiving resource request;
SFM receives from after the service flow of the MS change response, sends service flow change confirmation to MS;
SFM sends the resource request response to Anchor SFA.
As seen, adopt method provided by the invention not only on existing standard draft basis, a kind of method of establishment, deletion and change of network side service flow is provided.Can after service flow creation, can realize transfer of data, and the specific implementation process of change of a kind of network side service flow and deletion is provided on this basis, greatly height to the flexibility of network-side service flow operation.
● description of drawings:
Fig. 1 is a WiMAX cellular logic Organization Chart
Fig. 2 is the QoS reference model among the WiMAX
Fig. 3 is the network side service flow visioning procedure in the existing draft
Fig. 4 a is a uplink service flow chart in the service flow creation mode 1 among the present invention.
Fig. 4 b is downlink business flow process figure in the service flow creation mode 1 among the present invention.
Fig. 5 is the flow chart of service flow creation mode 2 among the present invention.
Fig. 6 a is a uplink service flow chart in the service flow creation mode 3 among the present invention.
Fig. 6 b is downlink business flow process figure in the service flow creation mode 3 among the present invention.
Fig. 7 is the flow chart of service flow creation mode 4 among the present invention.
Fig. 8 a is that service flow is deleted downlink business flow process figure in the mode 1 among the present invention.
Fig. 8 b is that service flow is deleted uplink service flow chart in the mode 1 among the present invention.
Fig. 9 is the flow chart of service flow deletion mode 2 among the present invention.
Figure 10 a is that service flow is deleted downlink business flow process figure in the mode 3 among the present invention.
Figure 10 b is that service flow is deleted uplink service flow chart in the mode 3 among the present invention.
Figure 11 is the flow chart of service flow deletion mode 4 among the present invention.
Figure 12 a is a uplink service flow chart in the service flow changing mode 1 among the present invention.
Figure 12 b is downlink business flow process figure in the service flow changing mode 1 among the present invention.
Figure 13 is a flow chart in the service flow changing mode 2 among the present invention.
● embodiment:
The invention provides a kind of method of establishment, deletion and change of network side service flow, this method based on define in the WiMAX network standard draft to service quality (QoS, Quality ofService) reference model.When network side is initiated dynamic service when increasing (DSA), dynamic service change (DSC) and dynamic service and deleting (DSD) such management service flow request, this method is not only on the basis of existing standard draft, it is more complete to make dynamic service increase (DSA) constructive process, but also the complete procedure of dynamic service change (DSC) and dynamic service deletion (DSD) is provided.Compressed parameter and resource reservation type parameter are two important parameters among the present invention.
1. the data compression algorithm when compressed parameter is used to support user and network service.The specific implementation technology comprises PHS (referring to IEEE802.16d/e), ROHC (referring to RFC3095), these three kinds of compress techniques of ECRTP (referring to RFC3545).With the network side consult to decide, the compressed parameter that carries during service flow creation should comprise the parameter set of response compress technique requirement during being chosen in MS and networking of concrete compress technique.
2. the resource reservation type parameter is used to support RSVP.If MS and network side negotiation result are supported RSVP, the resource reservation type parameter that then carries when service flow creation should comprise the parameter set that RSVP requires.
The present invention is described in further detail below in conjunction with accompanying drawing.
Embodiment 1:
Present embodiment is according to the foundation order of the direction decision R1 and the R6 interface of Business Stream to be created.When Business Stream is up direction, to build the R6 interface earlier and build the R1 interface again, flow process is participated in Fig. 4 a; When Business Stream is down direction, to build the R1 interface earlier and build the R6 interface again, flow process is referring to Fig. 4 b.
The network side service flow constructive process comprises:
Step 401:
Anchor service flow authorized entity (Anchor SFA) is after travelling carriage (MS) network registration is finished, and network side can carry out the establishment of service flow.When network side sends resource request by V/H PF to Anchor SFA, perhaps the establishment of service flow is carried out in Anchor SFA oneself decision, with the constructive process of trigger network side service flow.After network side service flow was created and is triggered, service flow request was initiated to Anchor SFA by V/H-PF, or service flow request is directly initiated by Anchor SFA.Anchor SFA uses local policy and initiates service flow request message to SFM, carries the relevant parameter and the request to create information such as qos parameter set, a reduced rule parameter, resource reservation type parameter of resource request in the message.If service flow request is initiated from V/H-PF, then these parameters issue from PF, and Anchor SFA preserves relevant parameter.
Step 402:
After Serving SFA receives resource request message, whether satisfy resource request according to its application service strategy decision.If do not satisfy, then directly return the resource request response message to Anchor SFA, carry failure result in the message, finish constructive process; Otherwise,, and preserve relevant parameter according to the parameter request reserved resource in the resource request message.Send resource request message to management service flow entity (SFM) then.
Step 403:
After SFM receives resource request message, use local access strategy and initiate dynamic service flow request to create (DSA request) to MS, carry qos parameter set, a reduced rule parameter and resource reservation type parameter in the message, MS preserves relevant parameter
Step 404:
MS receives the DSA request message, preserves corresponding qos parameter, SFID, CID and compressed parameter, returns dynamic service flow request to create response message (DSA asks response) to SFM then, wherein carries the establishment result.
Step 405:
After SFM receives that DSA asks response, if the Business Stream that request is created is down direction then shown in Fig. 4 b, directly to MS initiation dynamic service flow affirmation (DSA affirmation) message, finishes and eat dishes without rice or wine to create, and then initiate the resource request response to network side; If the Business Stream that request is created is up direction then shown in Fig. 4 a, directly initiates Resource-Response to the Serving of network side SFA, carries the result of resource request in this message.
Step 406:
Serving SFA returns the resource request response to Anchor SFA, wherein carries the result of resource request.
Step 407:
When Anchor SFA receives the resource request response message, if service flow request is initiated by V/H-PF, then also need this message to be sent to V/H-PF by Anchor SFA, carry resource request result and relevant parameter in the message.If judge that whether data channel is based on service flow then or data channel is also set up, be then to initiate data channel to set up process to SFM; Otherwise need judge also whether Business Stream is up direction, confirm, finish the R1 interface and create if also need to initiate DSA to MS.Data channel is set up process and is initiated to Serving SFA by Anchor SFA.
Step 408:
Serving SFA transmits data channel to SFM and sets up request message.Message is wherein carried the relevant information of passage.
Step 409:
After SFM receives that data channel is set up request message, set up request response to Serving SFA return data passage, wherein carry data channel and set up the result.
Step 410:
Serving SFA receives after data channel is set up request response and is transmitted to AnchorSFA again.
Step 411:
After Anchor SFA receives that data channel is set up request response, if create successfully then send the data channel acknowledge message to Serving SFA, otherwise the resource of distributing before discharging.
Step 412:
Serving SFA transmits the data channel acknowledge message to SFM.This moment, R6 interface data passage was just set up well.
Step 413:
After SFM receives that data channel is confirmed, finished the R6 interface and created.If Business Stream is a up direction, SFM also needs to send the DSA acknowledge message to MS, finishes the R1 interface and sets up.
Embodiment 2:
Present embodiment considers that from the angle that realizes the time that common R1 interface is set up is longer, can build the R1 interface earlier so, builds the R6 interface again.If this moment, business was that up direction and the foundation earlier of R1 interface are finished, then BS needs buffer memory to finish up to the foundation of R6 interface from the data of MS, and flow process is referring to Fig. 5, and the network side service flow constructive process comprises:
The execution sequence of step 501～step 504 is identical with the execution sequence of step 401～step 404, no longer repeats here.
Step 505:
SFM sends dynamic service flow acknowledge message (DSA affirmation) to MS after receiving DSA request response, eats dishes without rice or wine to set up to finish.
The implementation of step 506～step 513 is the same with the implementation of step 405～step 412, no longer repeats here.
Embodiment 3:
Present embodiment is according to the foundation order of the direction decision R1 and the R6 interface of Business Stream to be created.When Business Stream is up direction, to build the R6 interface earlier and build the R1 interface again, flow process is participated in Fig. 6 a; When Business Stream is down direction, to build the R1 interface earlier and build the R6 interface again, flow process is referring to Fig. 6 b, and the network side service flow constructive process comprises:
Step 601:
Anchor service flow authorized entity (Anchor SFA) is after travelling carriage (MS) network registration is finished, and network side can carry out the establishment of service flow.Ask when network side sends stream by V/H PF to Anchor SFA, perhaps the establishment of service flow is carried out in Anchor SFA oneself decision, with the constructive process of trigger network side service flow.After network side service flow was created and is triggered, the stream request was initiated to Anchor SFA by V/H-PF, or service flow request is directly initiated by Anchor SFA.Anchor SFA uses local policy and initiates service flow request message to SFM, carries the relevant informations such as qos parameter set, a reduced rule parameter, resource reservation type parameter and request to create of resource reservation request in the message.If the stream request is initiated from V/H-PF, then these parameters issue from PF, and Anchor SFA preserves relevant parameter.Simultaneously Anchor SFA also wants that whether the judgment data passage is based on service flow or also foundation of data channel, set up process if then initiate data channel to SFM, Anchor SFA then will carry the relevant parameter of data channel simultaneously in the stream request message that SFM initiates, be used for the foundation of data channel.
Step 602:
After Serving SFA receives the stream request message, whether satisfy resource request according to its application service strategy decision.If do not satisfy, then directly return the stream request response to Anchor SFA, carry failure result in the message, finish constructive process; Otherwise, according to the parameter request reserved resource of stream in the request message, set up data channel, and preserve relevant parameter.Send the stream request message to management service flow entity (SFM) then.
Step 603:
After SFM receives the stream request message, use local access strategy and initiate dynamic service flow request to create (DSA request) to MS, carry qos parameter set, a reduced rule parameter and resource reservation type parameter in the message, MS preserves relevant parameter
Step 604:
MS receives the DSA request message, preserves corresponding qos parameter, SFID, CID and compressed parameter, returns dynamic service flow request to create response message (DSA asks response) to SFM then, wherein carries the establishment result.
Step 605:
After SFM receives that DSA asks response, if the Business Stream that request is created is down direction then shown in Fig. 6 b, directly to MS initiation dynamic service flow affirmation (DSA affirmation) message, finishes and eat dishes without rice or wine to create, and then initiate the resource request response to network side; If the Business Stream that request is created is up direction then shown in Fig. 6 a, directly initiates the resource request response to the Serving of network side SFA, carries the result of resource request in this message.
Step 606:
Serving SFA returns stream request response to Anchor SFA, wherein carries the result that resource reservation and data channel are set up.
Step 607:
When Anchor SFA receives stream request response, if the stream request is initiated by V/H-PF, then stream request response also needs to send to V/H-PF by Anchor SFA, carries resource reservation result and relevant parameter in the message, and V/H-PF returns stream acknowledge message (Flow affirmation) to Anchor SFA then; Otherwise directly returning Flow by Anchor SFA to Serving SFA confirms.
Step 608:
Serving SFA sends the Flow acknowledge message to SFM after receiving the Flow acknowledge message.
Step 609:
SFM also initiates dynamic service flow affirmation (DSA affirmation) message to MS after receiving the Flow acknowledge message again, finishes and eats dishes without rice or wine to create.
Embodiment 4:
Present embodiment considers that from the angle that realizes the time that common R1 interface is set up is longer, so whether builds the R1 interface earlier, builds the R6 interface again.If this moment, business was that up direction and the foundation earlier of R1 interface are finished, then BS needs buffer memory to finish up to the foundation of R6 interface from the data of MS, and flow process is referring to Fig. 7, and the network side service flow constructive process comprises:
The implementation of step 701～step 704 is the same with the implementation of step 601～step 604, has no longer repeated here.
Step 705:
SFM sends dynamic service flow acknowledge message (Flow affirmation) to MS after receiving DSA request response, eats dishes without rice or wine to set up to finish.
The implementation of step 706～step 709 is the same with the implementation of step 605～step 608, no longer repeats here.
Embodiment 5:
Present embodiment is according to the deletion order of direction decision R1 that waits to delete Business Stream and R6 interface.When Business Stream is down direction, to delete the R6 interface earlier and delete the R1 interface again, flow process is participated in Fig. 8 a; When Business Stream is up direction, to delete the R1 interface earlier and delete the R6 interface again, flow process is referring to Fig. 8 b, and the network side service flow delete procedure comprises:
The execution sequence of step 801～step 804 is identical with the execution sequence of step 401～step 404, just carries the parameter difference in the requests/response messages, and the function of execution is also different, but flow process is the same, will no longer repeat here.
Step 805:
After SFM receives DSD request response, if the Business Stream of request deletion be up direction then shown in Fig. 8 b, directly initiate the dynamic service flow deletion and confirm (DSD affirmations) to MS, finish the deletion of eating dishes without rice or wine, and then initiate resource request to network side and respond; If the Business Stream of request deletion is down direction then shown in Fig. 8 a, directly initiates the resource request response to the Serving of network side SFA, carries the result of resource request in this message.
The execution sequence of step 806～step 813 is identical with the execution sequence of step 406～step 413, just carries the parameter difference in the requests/response messages, and the function of execution is also different, but flow process is the same, will no longer repeat here.In addition, in step 807, after Anchor SFA receives the resource request response (if also need to send the resource request response, then after this) to PF, if judge that whether data channel is based on service flow or do not had other service flow and used, be then to initiate the data channel delete procedure to SFM
Embodiment 6:
Present embodiment considers that from the angle that realizes the time of common R1 interface deletion is longer, so whether deletes the R1 interface earlier, deletes the R6 interface again.Referring to Fig. 9, the network side service flow delete procedure comprises:
The execution sequence of step 901～step 904 is identical with the execution sequence of step 801～step 802, will no longer repeat here.
Step 905:
After SFM received DSD request response, SFM initiated DSD to MS and confirms to finish the deletion of eating dishes without rice or wine.
The execution sequence of step 906～step 913 is identical with the execution sequence of step 806～step 813, will no longer repeat here.
Embodiment 7:
Present embodiment is according to the deletion order of direction decision R1 that waits to delete Business Stream and R6 interface.When Business Stream is down direction, to delete the R6 interface earlier and delete the R1 interface again, flow process is referring to Figure 10 a; When Business Stream is up direction, to delete the R1 interface earlier and delete the R6 interface again, flow process is referring to Figure 10 b, and the network side service flow delete procedure comprises:
The execution sequence of step 1001～step 1004 is identical with the execution sequence of step 601～step 604, just carries the parameter difference in the requests/response messages, and the function of execution is also different, but flow process is the same, will no longer repeat here.In addition, in step 1001 when AnchorSFA initiates the stream request, if judge that whether data channel is based on service flow or do not had other service flow and used, be then to initiate the data channel delete procedure to SFM, in the stream request message, carry the required information of data channel deletion.
Step 1005:
After SFM received DSD request response, if this Business Stream is a up direction, then SFM confirmed to finish the deletion of eating dishes without rice or wine to MS initiation DSD, and then initiates stream to network side and ask response, referring to Figure 10 b; If this Business Stream is a down direction, then SFM directly initiates stream request response to network side, referring to Figure 10 a.
The execution sequence of step 1006～step 1009 is identical with the execution sequence of step 606～step 609, just carries the parameter difference in the requests/response messages, and the function of execution is also different, but flow process is the same, will no longer repeat here.
Embodiment 8
Present embodiment considers that from the angle that realizes the time of common R1 interface deletion is longer, so whether deletes the R1 interface earlier, deletes the R6 interface again, and flow process is referring to Figure 11, and the network side service flow delete procedure comprises:
The execution sequence of step 1101～step 1104 is identical with the execution sequence of step 1001～step 1004, will no longer repeat here.
Step 1105:
After SFM received DSD request response, SFM sent dynamic service flow acknowledge message (DSD affirmation) to MS, to finish the deletion of eating dishes without rice or wine.
The execution sequence of step 1106～step 1109 is identical with the execution sequence of step 1006～step 1009, will no longer repeat here.
Embodiment 9:
Present embodiment is according to the change order of direction decision R1 that waits to change Business Stream and R6 interface.When Business Stream was up direction, change R6 interface was changed the R1 interface more earlier, and flow process is participated in Figure 12 a; When Business Stream was down direction, change R1 interface was changed the R6 interface more earlier, and flow process is referring to Figure 12 b, and the network side service flow change procedure comprises:
The execution sequence of step 1201～step 1204 is the same with the execution sequence of step 401～step 404, is the parameter difference of carrying in the message, the function difference of execution, but flow process is the same, no longer repeats here.
Step 1205:
After SFM receives DSC-Response, if the Business Stream of request change be down direction then shown in Figure 12 b, directly initiate dynamic Service change stream and confirm (DSC affirmations) message to MS, finish the change of eating dishes without rice or wine, and then initiate resource request to network side and respond; If the Business Stream of request change is up direction then shown in Figure 12 a, directly initiates the resource request response to the ServingSFA of network side, carries the result of resource request in this message.
Step 1206:
Serving SFA is transmitted to Anchor SFA with the resource request response.
Step 1206:
SFM sends service flow change confirmation (DS affirmation) to MS.
Embodiment 10:
Present embodiment considers that from the angle that realizes the time of common R1 interface deletion is longer, and so whether elder generation's change R1 interface is changed the R6 interface again.Referring to Figure 13, the network side service flow change procedure comprises:
The execution sequence of step 1301～step 1304 is the same with the execution sequence of step 1201～step 1204, no longer repeats here.
Step 1305:
After SFM received DSC request response, SFM initiated DSC to MS and confirms, finishes the change of eating dishes without rice or wine.
Step 1306:
SFM initiates the resource request response to Serving SFA.
Step 1307:
Serving SFA is transmitted to Anchor SFA with the resource request response.
Claims (19)
1. the creation method of a network side service flow, after the establishment of network side service flow was carried out in anchor service flow authorized entity Anchor SFA decision, network side was carried out:
The resource request process: Anchor SFA sends resource request and relevant parameter to management service flow entity SFM, described relevant parameter comprises qos parameter set, a reduced rule parameter and resource reservation type parameter, initiate the service flow creation request to mobile station MS after the SFM decision access, MS returns dynamic service flow request to create response message to SFM after keeping described relevant parameter;
Resource request response process: SFM sends the resource request response to Anchor SFA;
It is characterized in that this method further comprises:
If data channel is also set up, or data channel is based on service flow, then needs data channel to set up process, and this process comprises that data channel is set up request process and data channel is set up the request response process;
Data channel is set up request process: Anchor SFA sends data channel to SFM and sets up request and described relevant parameter, and each node will be set up data channel according to described relevant parameter in the network;
Data channel is set up request response process: SFM and is set up request response to Anchor SFA return data passage, and Anchor SFA sends acknowledge message to SFM;
Eat dishes without rice or wine affirmation process: SFM to MS transmission service flow creation confirmation.
2. method according to claim 1 is characterized in that, described resource request process, resource request response process, data channel are set up request process, data channel sets up the request response process and the affirmation process of eating dishes without rice or wine is independently carried out successively.
3. method according to claim 1 is characterized in that, described resource request process, the affirmation process of eating dishes without rice or wine, resource request response process, data channel set up request process and data channel is set up the independently execution successively of request response process.
4. method according to claim 1, it is characterized in that, carry out described resource request process and described data channel at first simultaneously and set up request process, carry out described resource request response process and described data channel then simultaneously and set up the request response process, carry out at last and eat dishes without rice or wine to confirm.
5. method according to claim 4 is characterized in that, described resource request process and data channel are set up request process and carried out simultaneously and be specially:
SFM receive from Anchor SFA comprise that resource request, data channel are set up the stream request of request and described relevant parameter after, preserve the wherein information of relevant data passage foundation, initiate the service flow creation request according to described relevant parameter and local access strategy to mobile station MS, MS returns dynamic service flow request to create response message to SFM after keeping described relevant parameter.
6. method according to claim 4 is characterized in that, described resource request response process and data channel foundation request response process are carried out simultaneously and be specially:
SFM sets up request response, resource request response and described relevant parameter with data channel and returns Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
7. method according to claim 1, it is characterized in that, carry out described resource request process and described data channel at first simultaneously and set up request process, carry out then and eat dishes without rice or wine to confirm, carry out described resource request response process and described data channel at last simultaneously and set up the request response process.
8. method according to claim 7 is characterized in that, described resource request process and data channel are set up request process and carried out simultaneously and be specially:
SFM receive from Anchor SFA comprise that resource request, data channel are set up the stream request of request and described relevant parameter after, preserve the wherein information of relevant data passage foundation, initiate service flow creation request DSA-Request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow request to create response message to SFM after keeping described relevant parameter.
9. method according to claim 7 is characterized in that, described resource request response process and data channel foundation request response process are carried out simultaneously and be specially:
SFM sets up request response, resource request response and described relevant parameter with data channel and returns Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
10. the delet method of a network side service flow is characterized in that, this method comprises:
The resource request process: Anchor SFA sends resource request and described relevant parameter to management service flow entity SFM, SFM initiates the service flow removal request according to described parameter and local access strategy to mobile station MS after receiving resource request, and MS returns dynamic service flow removal request response message to SFM after keeping described relevant parameter;
Resource request response process: SFM sends the resource request response to Anchor SFA;
Eat dishes without rice or wine affirmation process: SFM to MS transmission service flow deletion confirmation; If data channel is based on service flow creation, or do not have other service flow to use, then need to carry out the data channel delete procedure, this process comprises data channel removal request process and data channel removal request response process;
Data channel removal request process: Anchor SFA sends data channel removal request and described relevant parameter to SFM, and each node will be according to described parameter deleted data passage in the network;
Data channel removal request response process: SFM is to Anchor SFA return data passage deletion response message, and Anchor SFA sends acknowledge message to SFM.
11. method according to claim 10 is characterized in that, described resource request process, resource request response process, data channel removal request process, data channel removal request response process and the affirmation process of eating dishes without rice or wine are independently carried out successively.
12. method according to claim 10 is characterized in that, described resource request process, the affirmation process of eating dishes without rice or wine, resource request response process, data channel removal request process and data channel removal request response process are independently carried out successively.
13. method according to claim 10, it is characterized in that, carry out described resource request process and described data channel removal request process at first simultaneously, carry out described resource request response process and described data channel removal request response process then simultaneously, carry out at last and eat dishes without rice or wine to confirm.
14. method according to claim 13 is characterized in that, described resource request process and data channel removal request process are carried out simultaneously and are specially:
After SFM receives the stream request that comprises resource request, data channel removal request and described relevant parameter from Anchor SFA, preserve the wherein information of relevant data passage deletion, initiate the service flow removal request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow deletion response message to SFM after keeping described relevant parameter.
15. method according to claim 13 is characterized in that, described resource request response process and data channel removal request response process are carried out simultaneously and are specially:
SFM returns data channel removal request response message, resource request response and described relevant parameter to Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
16. method according to claim 10, it is characterized in that, carry out described resource request process and described data channel removal request process at first simultaneously, carry out then and eat dishes without rice or wine to confirm, carry out described resource request response process and described data channel removal request response process at last simultaneously.
17. method according to claim 16 is characterized in that, described resource request process and data channel removal request process are carried out simultaneously and are specially:
After SFM receives the stream request that comprises resource request, data channel removal request and described relevant parameter from Anchor SFA, preserve the wherein information of relevant data passage deletion, initiate the service flow removal request according to described parameter and local access strategy to mobile station MS, MS returns dynamic service flow deletion response message to SFM after keeping described relevant parameter.
18. method according to claim 16 is characterized in that, described resource request response process and data channel removal request response process are carried out simultaneously and are specially:
SFM returns data channel removal request response message, resource request response and described relevant parameter to Anchor SFA as stream request response together, and Anchor SFA returns the stream confirmation to SFM.
19. the change method of a network side service flow is characterized in that, this method comprises:
Anchor SFA sends resource request and described relevant parameter to management service flow entity SFM, and SFM initiates service flow change request according to described parameter and local access strategy to mobile station MS after receiving resource request;
SFM receives from after the service flow of the MS change request response, sends the resource request response to Anchor SFA;
SFM sends service flow change confirmation to MS.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100585932A CN101043504B (en) | 2006-03-22 | 2006-03-22 | Method for creating, deleting and changing network side service flow |
| PCT/CN2007/000935 WO2007107123A1 (en) | 2006-03-22 | 2007-03-22 | Processing method and communication device for dynamic service flow and network-side service flow |
| US12/212,808 US8254317B2 (en) | 2006-03-22 | 2008-09-18 | Method for processing dynamic service flows and network-side service flows and a communication apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100585932A CN101043504B (en) | 2006-03-22 | 2006-03-22 | Method for creating, deleting and changing network side service flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101043504A CN101043504A (en) | 2007-09-26 |
| CN101043504B true CN101043504B (en) | 2011-08-10 |
Family
ID=38808692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006100585932A Expired - Fee Related CN101043504B (en) | 2006-03-22 | 2006-03-22 | Method for creating, deleting and changing network side service flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101043504B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101345679B (en) * | 2008-08-21 | 2013-01-16 | 中兴通讯股份有限公司 | QoS guarantee method and system of dynamic business, AAA and Anchor SFA |
| US9319320B2 (en) * | 2011-03-31 | 2016-04-19 | Nufront Mobile Communications Technology Co., Ltd. | Traffic flow establishment method and device and traffic flow modification method and device |
| CN105635986A (en) * | 2012-03-06 | 2016-06-01 | 北京新岸线移动多媒体技术有限公司 | Business flow modification method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6134434A (en) * | 1997-12-08 | 2000-10-17 | Qualcomm Incorporated | System and method for providing service negotiation in a communications network |
| CN1633202A (en) * | 2003-12-22 | 2005-06-29 | 华为技术有限公司 | Method for implementing mobile data service using dynamic service quality control |
-
2006
- 2006-03-22 CN CN2006100585932A patent/CN101043504B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6134434A (en) * | 1997-12-08 | 2000-10-17 | Qualcomm Incorporated | System and method for providing service negotiation in a communications network |
| CN1633202A (en) * | 2003-12-22 | 2005-06-29 | 华为技术有限公司 | Method for implementing mobile data service using dynamic service quality control |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101043504A (en) | 2007-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101090088B1 (en) | Heterogeneous network system, network node and mobile host | |
| CN101409951B (en) | Method for establishing load bearing and relevant apparatus | |
| CN101345679B (en) | QoS guarantee method and system of dynamic business, AAA and Anchor SFA | |
| CN100450291C (en) | Method of establishing interface link | |
| CN101156417B (en) | Method and system for allocating SFID in microwave access global intercommunication network | |
| EP1392077A1 (en) | Managing the Quality of Service (QoS) levels during transfer between a wireless local area network (WLAN) and a mobile telephone network | |
| CN100583905C (en) | Mobile terminal IP address distributing method | |
| CN107295575A (en) | The control method and device of a kind of service quality | |
| CN100515116C (en) | Method and system for delivering service quality parameters | |
| US8254317B2 (en) | Method for processing dynamic service flows and network-side service flows and a communication apparatus | |
| CN101287289A (en) | Signaling in convergence sublayer in WiMAX | |
| CN105359573B (en) | Method and apparatus for unloading data service in a wireless communication system | |
| CN101242645A (en) | Method and system for mobile terminal to enter from free status to activated status | |
| CN101478470B (en) | End-to-end service quality dynamic management system and method under heterogeneous network interconnecting scene | |
| CN107113893A (en) | A kind of carrying establishing method and device | |
| CN102577449B (en) | Method, device and system for activation and deactivation of priority service | |
| CN101043504B (en) | Method for creating, deleting and changing network side service flow | |
| CN1640177B (en) | Method and device for improving quality of service management in a mobile packet radio communication cellular system | |
| CN101043505B (en) | Method for creating, deleting and changing dynamic service flow | |
| CN101047710B (en) | Method for implementing terminal denetwork at agent mobile network protocol | |
| CN101808331B (en) | Dynamic business stream processing method and base station | |
| CN1997003B (en) | Processing method for service stream in the WiMAX multi-host system | |
| CN101351053A (en) | Method for processing dynamic service stream | |
| CN101242256A (en) | Carrier wave distributing method | |
| WO2012155613A1 (en) | Method and system for relay node handover |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110810 Termination date: 20130322 |